Hi there, i could use some help here, i unlocked bootloader recently and were able to install Openkirin Roms (8.0) , and EMUI 9, i had no issues at all besides of No compile nunber, id face unlock, and no notch options,
then i wanted to try OpenKirin roms for emui 9, (i think it would work with emui 9.1, wich is the Version i were, and thats might be my mistake) so i got bootloop , and the phone is bricked.
So i try to go to Fastboot mode so i can reinstall my rom. but there is no way to access to it.
While the phone is off, i press VOL DOWN while i connect the USB cable nothing happens.
So i though eRecovery may save the day, but it doesnt recognise the files i pasted in Dload folder (with emui 8.0). is there a way to get the firmware 9.0 files but the one that works with erecovery. (by the way my erecovery is the one of emui 9 it has white background)
ane-lx3C521.
----
After a couple hours later, i waited for my phone to fully charge 100%, then in Erecovery options you choose SHUTDOWN, and then like always , press volume down while connect USB cable
and fastboot mode comes on screen.
The phone shouldnt be BATTERY LOW (wich percentage i dont know.) . Thats all , not a big deal.
Related
Hello there,
i need help with unbricking my Bq Aquaris X5 Cm Edition (codenname: paella).
I flashed Twrp, was not able to flash SU.zip. And flahsing LineageOs failed with "error7"
after i was unable to flash lineage and doing other stuff i had no system installed any more so i flashed cm unnofical gohan version with the flashall.bat.
And then i rebooted and had the mess. The phone does not want to turn on. Only thing that the phones give me as a "sign of life" is the red LED when i plug in the charging cable and give him power.
Im not able to get into fastboot or recovery mode. So my questions is: Is there ANY way to get that phone back to life?
Istn the normal way flahsing old bootloader and then original firmware?
But for that i need to get to fastboot mode which im not reaching.
LaCereb said:
Hello there,
i need help with unbricking my Bq Aquaris X5 Cm Edition (codenname: paella).
I flashed Twrp, was not able to flash SU.zip. And flahsing LineageOs failed with "error7"
after i was unable to flash lineage and doing other stuff i had no system installed any more so i flashed cm unnofical gohan version with the flashall.bat.
And then i rebooted and had the mess. The phone does not want to turn on. Only thing that the phones give me as a "sign of life" is the red LED when i plug in the charging cable and give him power.
Im not able to get into fastboot or recovery mode. So my questions is: Is there ANY way to get that phone back to life?
Istn the normal way flahsing old bootloader and then original firmware?
But for that i need to get to fastboot mode which im not reaching.
Click to expand...
Click to collapse
I'm in the same situation with a BQ X5 plus, I think the only way is to get the phone to the BQ service center
Did you get the phone working again ?
Nope i handed it over to the support and got a New one because guarentee was still valid
LaCereb said:
Hello there,
i need help with unbricking my Bq Aquaris X5 Cm Edition (codenname: paella).
I flashed Twrp, was not able to flash SU.zip. And flahsing LineageOs failed with "error7"
after i was unable to flash lineage and doing other stuff i had no system installed any more so i flashed cm unnofical gohan version with the flashall.bat.
And then i rebooted and had the mess. The phone does not want to turn on. Only thing that the phones give me as a "sign of life" is the red LED when i plug in the charging cable and give him power.
Im not able to get into fastboot or recovery mode. So my questions is: Is there ANY way to get that phone back to life?
Istn the normal way flahsing old bootloader and then original firmware?
But for that i need to get to fastboot mode which im not reaching.
Click to expand...
Click to collapse
yes you have to install qualcomm drivers and see in what mode the phone are.
9006, 900E or 9008
solved
I HAD the same problem with my BQ Aquaris X Pro.
Running the lineage OS 15.1, rooted with AddonSu installed.
This is how I was able to wake it up again.
1) I unplugged the phone from the USB loading cable
(don't know if this step is needed - the battery was definitely not totally empty, when this red flashing LED thing occurred. However, i don't think the phone charges when the LED red light flashes.).
2) I took the sim card out (don't know if this step is needed).
3) I pressed for about 2 [minute] power and volume (don't know if up or down) button together. And then it woke up again.
Maybe this is the special boot recovery mode option mentioned here?
What ever it is, it worked for me.
+ https : / / wiki.lineageos.org/devices/bardockpro
Good luck!
ElmBeech
R3 Pro (3GB/32GB, 2015817 version) came with some chinese/sellers custom ROM (and locked bootloader). It was heavy and bloated, so I decided to update it. Tried latest global stable (fastboot) ROM via miflash, flash was successful but that's was a lie - it stuck on mi logo...
Then I tried various other ROMs, global and developers, latest and older, some xiaomi.eu, manhit, etc. (for locked bootloader) and all I've got was either just a mi logo or mi logo with "powered by android" animation beneth. I left it for hours after flash and still nothing.
Then I found some ways to flash twrp, did that successfully, booted into it, wonder around in terminal and file manager, tried some recovery ROMs - but the result is the same - just logo or logo + animation.
I can get into fastboot (but it doesn't realy matters since bootloader is locked), download (EDL) mode, that Xiaomi menu (with Power and Vol+, with "shortcuts" to all the modes, hardware tests - btw. everything works there, etc.), twrp, charge battery (with some ROMs phone just gets warm and I know it's charging, there are no LED and/or animation, but in some everything works just like it should), but just can't boot into OS.
And I'm going nuts!
Here are some logs from the last ROM (i don't even know anymore which one is it) - pastebin.com/qaKVzxue and pastebin.com/dM3nEVj0
I'm not so experienced in looking at that but seems like every other thing in there, like cpu, i2c (touch/sensor), sound, battery, etc. is broken/faulty which is not true - everything was fine before update, and everything IS still fine according to inbuilt (xiaomi) hardware tests.
So somehow it seems that all the ido ROMs I tried are wrong for this device? Or am I missing something (quite possibly, I'm tired and pissed off)
Last night I did a backup of efs/nvram and then wiped internal memory/partitions, flashed latest global ROM, restored efs/nvram - phone stuck, but this time not on MI logo but freakin' penguin logo (like here en.miui.com/thread-377870-1-1.html). Same logo is for fastboot mode, no more bunny. Then flashed twrp and phone now shows mi logo with "powered by android" animation beneath, like before...
I don't know how this works with Xiaomi phones, but looks like it worked with some factory/seller special combination of ROM and bootloader. Then I did update and something stuck, maybe differences between ROM and bootloader, or some inside/hidden security mechanism that stops boot process? And because I can't find original firmware and/or bootloader is locked (maybe even updated?) it's now stuck...
Either that or some HW fault, but it would be insane that official ROM update with official tools and in factory download mode with full battery can cause such problem!
Can you go to twrp recovery?
Yes, like I said in the first post. I can do anything but boot android/MIUI. It's either because of locked bootloader or somehow official ROM installed officialy (via MiFlash in EDL mode) bricked phone, which is catastrophic bug i.e. epic design/implementation fail by Xiaomi.
Try this
https://forum.xda-developers.com/redmi-3/help/bootloop-bootloader-locked-options-t3331139
Sorry to intrude, I have pretty much the same problem.
Phone is stuck in bootloop and I can only access fastboot mode and EDL mode (but in EDL the phone does not connect to pc) and when I try to flash a stock ROM (since I know it is a software issue due to an unfortunate update) it says "locked device". So I tried to unlock it via MiUnlock... but phone cannot be verified 'cause "account not bound to this device" and obviously I cannot change any options since I cannot use my phone.
Please, help
it was happened to me about 3 days ago when i play around with the twrp & rooting thingy... tried everything from youtube to various forum solutions... just one link really works when you only have fastboot options and your phone bootloader is still unlocked. just follow the steps in the OP... key things here is downloading the tool to read your phone as mentioned in the OP i.e [TOOL]Minimal ADB and Fastboot [1-6-17]
1) Download Tool -> https://forum.xda-developers.com/showthread.php?t=2317790
2) Follow all the steps in the OP -> http://en.miui.com/thread-277276-1-1.html
3) Enjoy your phone from back from the dead.. LOL!
4) Remember here, the key is NEVER GIVE UP and PATIENT!
NOTE : The Device will start, wait till completion , it can take up to 10 Minutes. -> for me around 15-20 minutes for I have flashed the current beta rom of MIUI8 7.6.8
cheers, guys!
blx-
I had a similar situation.
Officially unlocked boot loader. Flashed TWRP using fastboot. Only got the mi logo and a boot loop on start up.
Could not turn on. Could not boot into TWRP.
When the phone was boot looping I could still get into fastboot mode by holding power+volume down.
I booted from fastboot mode into TWRP by opening the command prompts and using
"fastboot boot twrp2.img"
That got the phone available from windows explorer. I was able to move a new ROM image to the SD card and install from TWRP.
Currently running lineage 14.1 -20190112.
I lost a bunch of **** but my phone seems to turn on for the moment.
Note, I still cannot boot into TWRP using the phone only. I can only boot in from fast boot as above.
Hello,i got a huawei y6 2017 MYA-L11 model, i unlocked the bootloader and installed twrp, i made a backup of my stock rom and then wiped to install some custom roms.But now my phone is not working, everytime i start the phone it goes only to twrp even when i restore.I see that the backup exist in internal storage (contains system,data and boot) and says the restore was successful but the device boots always in twrp menu.Please help.
Any help guys?It doesnt seem so difficult problem for the level of this forum.
Try resetting the phone by pressing up volume button when on warning screen to get to erecovery. Use the option to shut down phone. Then try starting the phone again after a minute or two.
BTW what rom were you trying to install?
I tried every possible combination in the warning screen the only place i can go is twrp.I tried to install aokp,lineage 14.1, slim7, xeonHD nothing worked.
Where did you get those roms, I don't think they are for the y6 2017!
Anyway try pressing and holding the volume up button when at warning screen until the phone turns off. It will come back on and go to erecovery after the warning screen.
If that doesn't help then get SPFlashtool and stock rom and flash it.
I didnt know that y6 and y6 2017 was different.When i hold volume up the warning screen keeps repeating like forever and the phone doesnt go off.
Do i need spflashtool,can i do it from twrp install?
Anyway thanks for the help,it seems this phone cant take any custom roms,i should had bought a sumsung,can you suggest me some brands/devices that can be easily rooted/twrped with much custom roms in low range price.
We all make mistakes.
You will be able to fix it with the spflashtool if you download the rom.
Just have a look on here for an alternate device, I wouldn't know off hand which would be a good buy.
Tip: Read, read and then read some more before attempting anything with your phone!
Problem, the phone cant stay off when the usb is connected to the pc or electricity,when i press power off it reboots to warning screen and twrp,if it is closed when i plug the usb it starts into twrp all the time.
When i put the scatter file and press download this error appears
ERROR:S_COM_PORT_OPEN_FAIL(1013)
[COM]Failed to open COM port.
I m on linux
Use this tut to set up for linux.
You will just have to time plugging in the usb cable., I managed it so I know it can be done!
Yesterday everything was working good untill i installed a Magisk Module ( AR Core platform) and my device went to bootloop , i booted to TWRP to reflash a new OS , i wiped the current OS ( i dont keep backups) .. i did'nt realise that my battery was low and after i rebooted the phone to flash new OS it is now always stuck in FastBoot . No matter what i do . Then i relocked my bootloader , got the Red Warning , pressed volume buttons STOCK Recovery appeared but i can't boot into it either. what should i do ? the phone is not charging in FASTBOOT Mode , neither when i switch it off and plug it in charger (it boots into fastboot). I even tried the batch file method cycle to charge it for 10+ hours but still no luck. Need Urgent Help
RohitBora said:
Yesterday everything was working good untill i installed a Magisk Module ( AR Core platform) and my device went to bootloop , i booted to TWRP to reflash a new OS , i wiped the current OS ( i dont keep backups) .. i did'nt realise that my battery was low and after i rebooted the phone to flash new OS it is now always stuck in FastBoot . No matter what i do . Then i relocked my bootloader , got the Red Warning , pressed volume buttons STOCK Recovery appeared but i can't boot into it either. what should i do ? the phone is not charging in FASTBOOT Mode , neither when i switch it off and plug it in charger (it boots into fastboot). I even tried the batch file method cycle to charge it for 10+ hours but still no luck. Need Urgent Help
Click to expand...
Click to collapse
The same problem :/
hi i was doing this
and i followed everithing but in the part that i select reboot it restarts, get to the "samsung" text and then power off, then i tried to start it up with the power button but it not respond, even connecting it to my pc doesnt work. i cant go back to stock rom because i cant boot into recovery.
download and recovery mode not working, it doenst even show the samsung text or something. the screen doesnt react.
do you solved your problem ?
I got a same problem, bro. i changed rom several times. more then 10 custom i've tried, and the dead boot a10 got after trying installing pixel experience 11. my a10 A105G real dead boot. pc cannot recognising, and of course odin can not indentifying port.
Lucky for me, I tried to open the case, release battery connection. and reconnectthe battery. amazing. i try to enter download mode.... and... its work for me.
hope some ppl like us can find good solution for the dead boot A10 aftertry installing a costum rom.