Hi
My phone stopped working a couple of days ago, I had been running a custom rom for 2 mths. I tried to restart and boot to recovery TWRP as I was going to reflash the rom. It charegs with no lights, for a day I couldnt boot to TWRP if it did it stayed on the start screen with no options. Today I can get options in TWRP so I tried to start fresh install but intstallation stops at step 1 ?
I have no idea what happened to the phone or why it just died, but dont understand why I can get into TWRP but cant flash rom etc. Also sometimes it say system destroyed message? but still can get into TWRP ?
Any ideas or help will much appreciated really would like to fix this rather than write the phone off.
Thanks
i think flashing firmware is the only option
ranjodhricky said:
i think flashing firmware is the only option
Click to expand...
Click to collapse
Hi, yeah I think thats what I try, is this flashing stock rom via MI flash or a different process?
try miflash if doesn't work try QFil
update
ranjodhricky said:
try miflash if doesn't work try QFil
Click to expand...
Click to collapse
Hi, been playing with this when i have time over the last few weeks.
I have been trying to flash firmware, I dont seem to be able to get QFIL to work for me, it wont reconsise the port. However MIFlash does but I get errors, sometimes it flashes but doesnt end? other times i have had error flashing modem_a or error flashing modem_b (maybe device is locked).
In ADB it says already unlocked. Also I can only boot into fastboot, not recovery so i cant intall anything from adb sideload, it wont boot into bootloader just powers off if i try this. I guess theres no recovery on it now as I cannot boot into it.
Any ideas on where to go from here , EDL? I really didnt want to attempt to open the phone.
Thanks
Try miflash 2019 with stock rom pie latest with edl mode
if bootloader unlocked You can enter edl mode via fastboot with the command 'fastboot oem edl'
Yincen said:
Try miflash 2019 with stock rom pie latest with edl mode
if bootloader unlocked You can enter edl mode via fastboot with the command 'fastboot oem edl'
Click to expand...
Click to collapse
Thanks, tried this, says success then just carries on , so i have to disconnect. However when then trying to boot the device it shows Android one logo and if im lucky after a few attempts it goes to the screeen saying Hi There, where you choose your language to set up the phone. However it nows seem to be unresponsve and frozen on that screen.
Im beginning to think its could be hardware issue and phone is just faulty, i really dont want to bin it as its imacculate condition seems a real shame, but it is 3 years old i guess.
Any further help or ideas much appreciated.
healy2k said:
Thanks, tried this, says success then just carries on , so i have to disconnect. However when then trying to boot the device it shows Android one logo and if im lucky after a few attempts it goes to the screeen saying Hi There, where you choose your language to set up the phone. However it nows seem to be unresponsve and frozen on that screen.
Im beginning to think its could be hardware issue and phone is just faulty, i really dont want to bin it as its imacculate condition seems a real shame, but it is 3 years old i guess.
Any further help or ideas much appreciated.
Click to expand...
Click to collapse
try doing a factory reset from Recovery , good luck
Related
Bricked Zenfone5 via bad ROM flash
Sounds pretty bad but thats what has happened
What happened: phone shut off before the rom finished flashing
What's the diagnosis: booting into droidboot fails completely, shows a usb figure and right after that the ASUS startup animation and then turned itself off
What can still be done: plugging in while pressing volume down still elicits a ringtone on my PC, I'm assuming this is flash mode?
What I'm assuming I should do: do something akin to flashing but via flash mode ( which I've been doing on my XperiaL dozens of times), but I can't find a way to flash anything on the Zenfone5
If I'm sorely mistaken please correct me, any help is highly appreciated
What I used to do on XperiaL: open flash tool, flash rom in flash mode
You can plug your zf5 into PC, open droidboot and reflash the stock rom
Sorry for my bad English
KiraiPie said:
Sounds pretty bad but thats what has happened
What happened: phone shut off before the rom finished flashing
What's the diagnosis: booting into droidboot fails completely, shows a usb figure and right after that the ASUS startup animation and then turned itself off
What can still be done: plugging in while pressing volume down still elicits a ringtone on my PC, I'm assuming this is flash mode?
What I'm assuming I should do: do something akin to flashing but via flash mode ( which I've been doing on my XperiaL dozens of times), but I can't find a way to flash anything on the Zenfone5
If I'm sorely mistaken please correct me, any help is highly appreciated
What I used to do on XperiaL: open flash tool, flash rom in flash mode
Click to expand...
Click to collapse
you can try this
https://translate.google.co.in/tran...restaurar-img-droidboot-zenfone-5/&edit-text=
kloroform said:
you can try this
Click to expand...
Click to collapse
Thanks for the reply, but I can't boot to ANYTHING and by that I literally mean ANYTHING, so recovering from recovery does not fit the problem.
Luckily I found this, and eventually fixed my phone.
KiraiPie said:
Thanks for the reply, but I can't boot to ANYTHING and by that I literally mean ANYTHING, so recovering from recovery does not fit the problem.
Luckily I found this, and eventually fixed my phone.
Click to expand...
Click to collapse
I had seen that method earlier, good to know that this is a working method and resolved your problem
Hey, can you help me using that method? I'm stuck on trying how to figure out how to make CloverviewPlus device come out.
Hi,
I'm using TRWP 2.8 on my nexus10. While flashing a new ROM TRWP hangs (30 Minutes) and I have to turn off the device. Now I only can start the bootloader, nothing more. I have tried to get an adb connection but no device is found. I have tried it from my mac and also from a win10 .
Is my device now dead for ever ??
Thx
harvey
harvey186 said:
Hi,
I'm using TRWP 2.8 on my nexus10. While flashing a new ROM TRWP hangs (30 Minutes) and I have to turn off the device. Now I only can start the bootloader, nothing more. I have tried to get an adb connection but no device is found. I have tried it from my mac and also from a win10 .
Is my device now dead for ever ??
Thx
harvey
Click to expand...
Click to collapse
Turn it on and let the battery run completely empty. Recharge and try again.
mr.natural said:
Turn it on and let the battery run completely empty. Recharge and try again.
Click to expand...
Click to collapse
I know this trick and I have tried it two times. But it's still the same. And by the way, I can't stop booting. Either it's booting til the "Google" is shown or when I push the volume button it's booting into the boot loader. But it never stops booting.
harvey186 said:
Hi,
I'm using TRWP 2.8 on my nexus10. While flashing a new ROM TRWP hangs (30 Minutes) and I have to turn off the device. Now I only can start the bootloader, nothing more. I have tried to get an adb connection but no device is found. I have tried it from my mac and also from a win10 .
Is my device now dead for ever ??
Thx
harvey
Click to expand...
Click to collapse
you ****ed up the partitions most likely. If you can get fastboot then restore stock firmware (fresh start that sh*t my n****). If you can't get any fastboot connection at all, try reinstalling the drivers and sh*t. If that doesn't fix it, I think you're ****ed.
heres a new one for 100$ https://www.amazon.com/gp/product/B06XNX91YB/
Galaxyninja66 said:
you ****ed up the partitions most likely. If you can get fastboot then restore stock firmware (fresh start that sh*t my n****). If you can't get any fastboot connection at all, try reinstalling the drivers and sh*t. If that doesn't fix it, I think you're ****ed.
heres a new one for 100$ https://www.amazon.com/gp/product/B06XNX91YB/
Click to expand...
Click to collapse
Thx for help. Yesterday I have found a solution. While the black boot screen which the Google shows I get a adb connection to the N10. So I was able the start 'adb reboot recovery' and the device was booting into TWRP And now I was able to flash OmniROM 7.2.1
harvey186 said:
Thx for help. Yesterday I have found a solution. While the black boot screen which the Google shows I get a adb connection to the N10. So I was able the start 'adb reboot recovery' and the device was booting into TWRP And now I was able to flash OmniROM 7.2.1
Click to expand...
Click to collapse
You can better use TWRP 3.1.1 for manta. File: https://androidfilehost.com/?fid=961840155545587690
So this phone is basically brand new about 4 days old and then it just turned off on me. when I booted it up it went into the emui huawei erecovery. I go into download latest version and recovery and connect to my wifi
it loads for a bit and comes back saying 'getting package info failed'. Honestly I'm pretty novice about everything like this so any help would be appreciated. I am planning on returning it to the store in the coming days but I do not have a warranty.
Ova11 said:
So this phone is basically brand new about 4 days old and then it just turned off on me. when I booted it up it went into the emui huawei erecovery. I go into download latest version and recovery and connect to my wifi
it loads for a bit and comes back saying 'getting package info failed'. Honestly I'm pretty novice about everything like this so any help would be appreciated. I am planning on returning it to the store in the coming days but I do not have a warranty.
Click to expand...
Click to collapse
Fastboot working?
Adi5 said:
Fastboot working?
Click to expand...
Click to collapse
What's that? Sorrry but I really dont know much about this
fastboot is a method used where you connect your phone to a PC to flash custom recoverys etc.
The eRecovery has never managed to download anything for me, always failed.
How is the phone 4 days old but you have no warrenty?
Make a factory reset
I have got the same problem. My pin from phone just stopped working, so I went to erecovery mode. It says getting package info failed. I do not really know what to do. Fastboot works.
Hi. How do you do a fast boot? My phone is stuck on erecovery and i cant get out. I did an update and it went to erecovery, package download failed, only options then is shutdown and reboot. Please help.
Tamz213 said:
Hi. How do you do a fast boot? My phone is stuck on erecovery and i cant get out. I did an update and it went to erecovery, package download failed, only options then is shutdown and reboot. Please help.
Click to expand...
Click to collapse
Lol how do you do a fastboot? Bro, I'm sorry, I shouldn't laugh but I do because I've been kinda there and done kinda that. People here, I KNOW, are more than willing to help you but you've gotta come with at least the most basic knowledge. None of us were born knowing, but just research a little, and before long you'll get the ropes believe me it's not hard.
I hope THIS just helped.
Hi i have a honor 8 lite bricked, tried emui .8.0 chinese rom, it worked but when I tried getting back to stock, it was bricked.
Couldnt go to my twrp recovery,
fastboot fails with remote: command not allowed.
flashing recovery using fastboot fails with partition length gets error.
the only thing I could do is huawei e recovery which is failing with getting package info failed.
In fastboot, I could lock and unlock bootloader, please help
you have to use sth like "fastboot flash recovery_ramdisk xxx.img
google this.
As long as fastboot is running you are NOT lost at all
i shut down my device by tapping power off. then removed sim card and sd card after screen went black. but when i tried to power on, it doesnt respond.. i tried holding the power button for 10s, it gives me a black screen and vibrates and instantly closes again.. so i cant boot into recovery, i cant boot to fastboot, and its unreadable on pc, it doesnt charge, no bootlogo, nothing. just bricked..
.
i dont know why, but it just bricked by itself.. i've been using mokee 9 date of 1/1/2020 thats the last update i installed, with add on su and everything was working perfectly and even if i reboot multiple times..
bootloader was unlocked so xiaomi centers wont help me..
how is it possible to make it boot again? i mean like wtf even happened? i did nothing.. i didnt flash anything and system was READ ONLY before powering off.. all i did was remove sim and sd cards... even after flashing mokee updates yesterday, it booted normally and idk what's going on..
any help?
EDIT: the phone's hard disk IC was damaged. I went to a tech guy and he changed it but then the motherboard broke entirely after flashing the qcn file for imei. Device out of warranty of course because of the damn bootloader. Thank you xiaomi for the great phone that only lasted one month before dying completely.
attempt 2
in attempt 1 i tried force reboot as mentioned, didnt work
attempt 2 : i tried force reboot while plugged to pc, this showed up
attempt 3
i tried to flash a new firmware, but device unreadable. must be on fastboot mode for mi flasher to be able to read it. im starting to lose hope.. the device is new though it makes me sad
on some topic of a bricked phone online, someone mentioned that he should try EDL mode, by cmd command FASTBOOT OEM EDL
so i tried it many times until it said successful. but still didnt fix anything, because it didnt actually boot into EDL mode, had to open my device physically and use test points. so attempt 4 failed
does this mean fastboot works?
after attempt 4, it said successful so if fastboot works like that then i can flash stock boot.img or something.. right? which image should i start with
forum
boody shaban said:
on some topic of a bricked phone online, someone mentioned that he should try EDL mode, by cmd command FASTBOOT OEM EDL
so i tried it many times until it said successful. but still didnt fix anything. so attempt 4 failed
Click to expand...
Click to collapse
this is the forum of the bricked phone similar to mine, except that i didnt try any flash like him it just happened randomly
https://c.mi.com/thread-2334646-1-0.html
attempt 5
attempt 5 failed, i tried flashing whole firmware one by one, i started with vbmeta, then recovery but it failed. idk what to do
notice
i have noticed that it only flashes small img files, if its 100kb or more it will fail. maybe due to device restart because the only way to make it read in fastboot mode is to force restart multiple times until it flashes. what to do now?
attempt 6
so according to this video
https://www.youtube.com/watch?v=yJoIiLE_w3w
he installed a driver (name in attachment) then refreshed on mi flash so his device became readable on mi flasher
i tried that but it didnt work.
final attempt.. out of hope
found the possible solution. its called a deep flash cable, i will just go to any tech guy and ask him for help.
see attachment for info.
boody shaban said:
found the possible solution. its called a deep flash cable, i will just go to any tech guy and ask him for help.
see attachment for info.
Click to expand...
Click to collapse
In order to enter test point / EDL / 9008 mode, you have to physically open your device and connect two points on the phone's board. Search on YouTube for Redmi 7a EDL. If you get to EDL mode, you can flash original stock firmware via MiFlash.
Reason for brick
cg730620 said:
In order to enter test point / EDL / 9008 mode, you have to physically open your device and connect two points on the phone's board. Search on YouTube for Redmi 7a EDL. If you get to EDL mode, you can flash original stock firmware via MiFlash.
Click to expand...
Click to collapse
Yes, I hate tearing up my device so I took it to a professional. He failed to open ADL but he did the 9008. Now he waits some kind of credit. Not sure if for the app to work or for the bootloader to unlock, although it was already unlocked but maybe somehow got locked..
Any way, expected reason for brick is either latest magisk module, or kernel tweaks..
I gave the device to a professional, but he also failed to flash it even with test point. He said he was searching for a file.. I dont remember its name, something like IMOH..
Now I need to know any possible reason that might brick my phone again to avoid it
cg730620
Click to expand...
Click to collapse
cg730620 said:
.
Click to expand...
Click to collapse
The app he used was called ultimate multi tools
test point attempt failed
i did the test point, booted to 9008 mode but still nothing.
i think i know why the phone got bricked by itself, it got ARB stands for AUTOROLLBACK
read more about it here https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
bootloader got automatically locked again.
Never lock the bootloader if:
- your phone was delivered Chinese version and you flashed Global firmware
- your phone was delivered Global version and you flashed Chinese firmware
- you changed system, vendor, boot or recovery partition
- you installed a custom or modified stock rom
ARB isn't an issue with this phone I suppose. Because I was on 11.0.5 and rolled back to 10.2.5 without problems.
Have you tried MiFlash Pro?
See here:
https://forum.xda-developers.com/redmi-7a/how-to/miflash-pro-t4030809
---------- Post added at 04:01 AM ---------- Previous post was at 03:38 AM ----------
boody shaban said:
i did the test point, booted to 9008 mode but still nothing.
Click to expand...
Click to collapse
It seems that error is related to your computer. Reinstall drivers and MiFlash.
QDLoader Drivers:
http://www.mediafire.com/file/0jfq2r7adylnltu/QDLoader_HS-USB_Driver.zip/file
ADB driver:
http://www.mediafire.com/file/qskct06xyx1iivs/ADB%2Bdriver%2Bv1.17%2Blite.zip/file
MiFlash:
http://www.mediafire.com/file/bdjugf3zx7037yl/MiFlash2018-5-28-0.zip/file
Read about a similar problem here:
https://xiaomi.eu/community/threads/mi5-bricked-i-bricked-my-new-mi5-with-miui8.32439/
cg730620 said:
Never lock the bootloader if:
- your phone was delivered Chinese version and you flashed Global firmware
- your phone was delivered Global version and you flashed Chinese firmware
- you changed system, vendor, boot or recovery partition
- you installed a custom or modified stock rom
ARB isn't an issue with this phone I suppose. Because I was on 11.0.5 and rolled back to 10.2.5 without problems.
Have you tried MiFlash Pro?
See here:
https://forum.xda-developers.com/redmi-7a/how-to/miflash-pro-t4030809
---------- Post added at 04:01 AM ---------- Previous post was at 03:38 AM ----------
It seems that error is related to your computer. Reinstall drivers and MiFlash.
QDLoader Drivers:
http://www.mediafire.com/file/0jfq2r7adylnltu/QDLoader_HS-USB_Driver.zip/file
ADB driver:
http://www.mediafire.com/file/qskct06xyx1iivs/ADB%2Bdriver%2Bv1.17%2Blite.zip/file
MiFlash:
http://www.mediafire.com/file/bdjugf3zx7037yl/MiFlash2018-5-28-0.zip/file
Read about a similar problem here:
https://xiaomi.eu/community/threads/mi5-bricked-i-bricked-my-new-mi5-with-miui8.32439/
Click to expand...
Click to collapse
but im sure i have all drivers installed in fact i used mi flash more than once and it worked perfectly fine, and i swear i didnt try to lock it or anything, what happened is, mokee auto updates installed add on magisk and it was the latest version so i think this might have bricked it. idk..
ok i downloed all the drivers and reinstalled them, same error : "library not registered"
Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.