Develop Bugs

Very very hard brick

Hello ..
I have a big problem !! I try to flash the Smartzen rom for try and after when my phone reboot..I have a bootloop
But the problem it's -> I don't acces to the bootloader and the recovery
I make power and volume + and i have vibration and just that
When i put the phone with the usb cable the phone doesn't charge.. and sometimes yes
And sometimes the phone reboot with a bootloop
I can't flash a new rom because my pc don't recognize the phone( just the sound when a device is connected) (it's normal i don't have access to bootloader)
And on the tutorial for the unbrick it's say " Ash back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables. " but i don't have that...i have NOTHING
What is the solution please ?? Because i don't see any solution..

quadeur06 said:
Hello ..
I have a big problem !! I try to flash the Smartzen rom for try and after when my phone reboot..I have a bootloop
But the problem it's -> I don't acces to the bootloader and the recovery
I make power and volume + and i have vibration and just that
When i put the phone with the usb cable the phone doesn't charge.. and sometimes yes
And sometimes the phone reboot with a bootloop
I can't flash a new rom because my pc don't recognize the phone( just the sound when a device is connected) (it's normal i don't have access to bootloader)
And on the tutorial for the unbrick it's say " Ash back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables. " but i don't have that...i have NOTHING
What is the solution please ?? Because i don't see any solution..
Click to expand...
Click to collapse
If you cant access bootloader i would suggest to use xfstk to reflash the bootloader. follow this guide. I had same problem and successfully recovered from a hard brick.
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256

sharkie545 said:
If you cant access bootloader i would suggest to use xfstk to reflash the bootloader. follow this guide. I had same problem and successfully recovered from a hard brick.
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Click to expand...
Click to collapse
Thank to you're answer...but xfstk doesnt launch on my computer and i see that on the tutorial
back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables. "
I dont have that

quadeur06 said:
Thank to you're answer...but xfstk doesnt launch on my computer and i see that on the tutorial
back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables. "
I dont have that
Click to expand...
Click to collapse
Basically as long as you followed the drivers install process correctly under device manager for a quick seccond you will see under IntelSOC you will see moorefield appear then disconnect. If that is good then your on your way.
Simply open xfstk follow the steps link to the proper files for your device, then hit begin download. While the counting is going down, turn on your phone as described in the steps and it should begin flashing.
here is a good video tutorial that helps - credit to timbernot
http://forum.xda-developers.com/zenfone2/general/unbrick-vid-tutorial-restore-serial-t3411064

sharkie545 said:
Basically as long as you followed the drivers install process correctly under device manager for a quick seccond you will see under IntelSOC you will see moorefield appear then disconnect. If that is good then your on your way.
Simply open xfstk follow the steps link to the proper files for your device, then hit begin download. While the counting is going down, turn on your phone as described in the steps and it should begin flashing.
here is a good video tutorial that helps - credit to timbernot
http://forum.xda-developers.com/zenfone2/general/unbrick-vid-tutorial-restore-serial-t3411064
Click to expand...
Click to collapse
Thank you my friends so much!!

same prob here. in my case, I have installeds all things successfuly bt xfstk cant flash after first step. 20 tries and then stop the process. any help?

vyaskd said:
same prob here. in my case, I have installeds all things successfuly bt xfstk cant flash after first step. 20 tries and then stop the process. any help?
Click to expand...
Click to collapse
Usually when this happens xfstk lost communication with the device. Typically I encountered this when xfstk continued to flash the OS file.
In this case the fix is
To Go to Options to change the value in the Value section Override Flag GP 0x80000807. (Note the guide calls for 5 0's but only 4 0's will work)

sharkie545 said:
Usually when this happens xfstk lost communication with the device. Typically I encountered this when xfstk continued to flash the OS file.
In this case the fix is
To Go to Options to change the value in the Value section Override Flag GP 0x80000807. (Note the guide calls for 5 0's but only 4 0's will work)
Click to expand...
Click to collapse
I've done this already before flashing, as told in guide. any other trick to make fone stay connected for little longer? may be some change in xxx807 value?

vyaskd said:
I've done this already before flashing, as told in guide. any other trick to make fone stay connected for little longer? may be some change in xxx807 value?
Click to expand...
Click to collapse
This happened to me too - I solved it the dumbest way possible. The first time I set it up and ran it and it got through the first part and then failed to do the second. I just happened to have to go pick up a pizza at the time, so I went and got the pizza, came back, touched nothing, ran xFSTK again, and it worked! After that, I always ran it once, let it fail, then waited 10 minutes touching nothing, and ran it again. That always works for me (don't know why, and I know it doesn't make sense, but hey it works for me all the time)

Zenfone 2 Brick - NO LED - NO SCREEN - JUST VIBRATION

Hi, i couldnt find anything on google and youtube, so im here to ask you.
Every bricked situation has a USB Logo on screen or Android logo with ERROR message, BUT i have nothing on the screen. Just opening vibration and it keeps vibrate over and over again in 5-10 min. I dissambled my phone and disconnect battery from mainboard and re-connect it. It just keep vibrate when i re-connect it and it begins a loop. No led when charging, no adb connection (device not found error). Like i said, it keeps vibrate after 5-10 min last vibration. The time it vibrates again, adb finds my device but then it just lost connection.
HOW IT HAPPENED?
1. I was using official android 5 rom with root, I didnt get android 6 update
2. I tried to flash it via Recovery mode but it just didnt get in Recovery mode and it shows an ERROR message on screen. So i googled it and found a few solutions like wipe cache
3. I get in Recovery mode and tried to wipe cache again, but it stuck like 10 min so i forced close my phone. AAND no system i have.. It just didnt opening, ASUS logo with loading circle..
4. I flashed TWRP via ADB
5. so i tried to flash android 6 zip file via TWRP
6. it stucked, i waited over 10-20 min and i forced it to close(it stucked in "Splash screen installing", i though it must last like 1 min or 2 min maybe, its not the system its just opening animation)
7. NOW I HAVE A BRICKED PHONE WITH NO LED NO SCREEN JUST OPENING VIBRATION, cannot connect to adb, cannot get in recovery mode, nothing
Please give me some advices, im ready to try everything that can return my phone back.
English is not my native language, sorry for the huge grammer mistakes. I'm in a hurry and cant think about how can i make a sentence with perfect grammar.

up

This is the best guide : unbrick

Same PRoblem
if u get the solution please send it to me too at [email protected]

please update the links... i can't download the files i need.... thank you in advance...

This happened to me also . In my case i leaved my phone on charge (it was on low battery ) its keeps vibrating in 30 sec - 1 min interval , After some hours of this it finally booted to recovery (but i then rebooted bootloader then safe thing happens . Again after some hours it booted to recovery ) ,then i flashed stock ROM ,it failed but bootloader was back.
Hit Thanks if i helped.

Well, this happened with me, I needed open My phone and unplud batery cable and plug again. Easy to do.

same situation
I am facing the same issue at the moment.If you did fix it ,please reply with the solution or mail it to me at [email protected]
Thanks in advance

ZE551ML keeps vibrating, won't start.

Hi everyone,
Yesterday, as usual, i plugged my zenphone to its charger, but it almost instantly turned off and won't restart since.
The phone keeps vibrating every minute as if it was booting, but the screen doesn't light up, nor the led while charging.
I've read a lot of thread with similar problems, which were solved by replugging the battery, but this solution won't work for me.
Here is what i've tried so far:
-Changing the charger/cable
-Replugging the battery
-Leaving the battery unplugged over night, then replug
-Leaving the phone rest for 8 hours
-Pressed every possible combination of button for 20 sec
None of the above solutions changed anything.
I don't think that it could be a battery problem, the phone shut down at arround 40% and my multimeter still indicates a voltage of 4.20V at the battery.
Hope you guys will be able to help me !
Thanks

4.2 means battery more than 80 percent. you seems bricked. use the following guide step by step read everything carefully. any question post there in the thread. please search around before starting new thread.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

@Solasmeryl
Was you in M when you bricked ?
If you was and are getting 'continuing to os ' error in xFSTK .
Try this > in xFSTK
1) fwr dnx = your normal file you used before
2)Ifwi = try this >
http://www.mediafire.com/file/xjhv9gfiv5sn7xx/tmp_17491-ifwi_ann_a0-mofd_v1-ze551ml1929259488.bin
3) is skipped = per usual
4) OS = your usual posignbin you used before
If you get bootloader now , it will be 0094.0183 for M , flash M raw file.
Then you flash M raw file (twice) in AFTools, raw M = 4.21.40.184
First flash for approx 3 to 4 mins, where on-screen cmds pauses on "RESULT=OK" on phone.
Close flashtools , force close.
Open flashtools again , input raw , press vol+ (once) and serial now is corrected , flash till it boots into system.approx 8 mins
Notes..
If serial number is correct after xFSTK flash , you only flash raw once only. Flash Twice if serial is 0123456789ABCDEF
.
.
When connecting to xFSTK. Connect data lead.
Press power and vol-, press download , connect phone, release vol- and power
If fail , press vol + and power till first of two vibes , release buttons , hit download button in xFSTK at the same time you release buttons on phone , tricky but you can do it .
There's AFT and links to needed files in my unbrick thread in my signature , even a video showing flashing procedure

Fixed LINK , added M .184 ifwi for xFSTK

@timbernot
Hi, thank you for helping me out, i didn't though my problem could be a brick, but my symptoms are the same.
I was running CM 13, so yeah, the android version was M.
I tried your IFWI file but it doesn't seem to have fixed anything, except, the phone doesn't vibrate anymore now.
I don't know i just accidentally destroyed the vibration motor or if the IFWI file has anything to do with it.

Solasmeryl said:
@timbernot
Hi, thank you for helping me out, i didn't though my problem could be a brick, but my symptoms are the same.
I was running CM 13, so yeah, the android version was M.
I tried your IFWI file but it doesn't seem to have fixed anything, except, the phone doesn't vibrate anymore now.
I don't know i just accidentally destroyed the vibration motor or if the IFWI file has anything to do with it.
Click to expand...
Click to collapse
Nothing to do with Motor i`m afraid
Battery dead , will be the main cause .
Leave connected to charger for a good few hrs :good:
Each flash in xFSTK uses approx 10% battery , more if you sit there watching it `continuing to os`
See my video in link -- the button process and connection -- i do it just the once , admittedly i have unbricked many zens and know exactly when to press dload in xFSTK :good:
https://www.youtube.com/watch?v=PmbRaJijIBs&feature=youtu.be
ps cm13 was based on LP mainly , only the latter versions and cm 14 had bootloader upgrades.
So return to original flashing files

Solasmeryl said:
@timbernot
Hi, thank you for helping me out, i didn't though my problem could be a brick, but my symptoms are the same.
I was running CM 13, so yeah, the android version was M.
I tried your IFWI file but it doesn't seem to have fixed anything, except, the phone doesn't vibrate anymore now.
I don't know i just accidentally destroyed the vibration motor or if the IFWI file has anything to do with it.
Click to expand...
Click to collapse
Just FYI, if you were on cm13 official then your base was LP not MM. Even though it's an MM rom
Sent from my ASUS_Z00A using Tapatalk

timbernot said:
Nothing to do with Motor i`m afraid
Battery dead , will be the main cause .
Leave connected to charger for a good few hrs :good:
Each flash in xFSTK uses approx 10% battery , more if you sit there watching it `continuing to os`
See my video in link -- the button process and connection -- i do it just the once , admittedly i have unbricked many zens and know exactly when to press dload in xFSTK :good:
https://www.youtube.com/watch?v=PmbRaJijIBs&feature=youtu.be
ps cm13 was based on LP mainly , only the latter versions and cm 14 had bootloader upgrades.
So return to original flashing files
Click to expand...
Click to collapse
Ok, so i charged up the phone, went back to the original file as suggested. Vibrations are back, but i still can't figure out how to pass the "Continuing to OS" error :/
Here is how i seem to understand the steps:
1. I Click begin download (which start the 120sec timer)
2. I press Power and Vol - for 4 sec then release
3. I Connect the phone to the PC, hear the windows "device connect" sound
4.Messages show up in xFSTK, sometimes errors, sometimes the download begins, and back to the "Continuing to OS"
5.The phone vibrates, the software attemps 20 reconnect then aborts.
I've also tried a lot of different combinations such as pressing power after plugging, not pressing power at all, etc (The software indicates 41 tries).
It just seems that the phone is completely dead :/
Thans a lot for the help, i really hope that i doesn't bother you too much by making mistakes !

Do you usual flash , soon as you see continuing to os Press power and vol + , at first of of two vibes - release and hit download.
Note , if only one vibe , re press and keep pressed vol+ and power immediately.
Do press download first like in the video..but you have to double click it to stop and to begin again at the exact time of releasing at first of two vibes
Ps , depending on pc speeds etc etc , it is wise to come off the internet , disable anti virus , clean pc from junk, c cleaner free is good and do a reboot.
Also , some people report it just flashing after hrs of failures by just leaving phone connected after a failure with xFSTK still open, then restarting flash after a good break of half hr plus

@Solasmeryl
Hows it going ??

timbernot said:
@Solasmeryl
Hows it going ??
Click to expand...
Click to collapse
No change :/ even tho i've tried every button timing possible i guess.
I've noticed that pressing Power and Vol- before plugging in the phone always leads to an error. The only way to get to the continuing to os is by pressing these buttons while the phone is already connected, and then hit download.
Could there be any other software problem that could **** things up and that i forgot to mention ?

Solasmeryl said:
No change :/ even tho i've tried every button timing possible i guess.
I've noticed that pressing Power and Vol- before plugging in the phone always leads to an error. The only way to get to the continuing to os is by pressing these buttons while the phone is already connected, and then hit download.
Could there be any other software problem that could **** things up and that i forgot to mention ?
Click to expand...
Click to collapse
Can you ignore xFSTK for a moment
try this without being connected to pc either.
(A)Press and keep pressed power and vol+ . Does your phone vibrate (twice) ?

timbernot said:
Can you ignore xFSTK for a moment
try this without being connected to pc either.
(A)Press and keep pressed power and vol+ . Does your phone vibrate (twice) ?
Click to expand...
Click to collapse
Yes, the phone vibrates twice

Solasmeryl said:
Yes, the phone vibrates twice
Click to expand...
Click to collapse
Well , somehow you gotta release both buttons and hit download at the same time at first vibrations of the two .
Do what you need regarding pressing power and vol- to connect initially . Then go about trying to get the above two vibes process while downloading . Be fast to double click download at the first of two vibes --
Thats it !
That is all anyone has to do :good:
One other thing to try is - just try power , on its own(like power off), press and keep pressed after initial connection download process, once it vibrates - release and -- go for the power and vol+ 2 vibe process again. Get ready to hit download !
---------- Post added at 05:42 PM ---------- Previous post was at 05:25 PM ----------
If that doesnt work ^^^ i will begin to start asking questions about the settings you have applied
Double check this ->
(fast forward to 18:30 mins in of this video for settings to be modified in XFSTK re... changing GP over ride to 0x80000807 ) . Make sure you modified the correct CRC+ box at the bottom
https://www.youtube.com/watch?v=PmbRaJijIBs&feature=youtu.be

timbernot said:
Well , somehow you gotta release both buttons and hit download at the same time at first vibrations of the two .
Do what you need regarding pressing power and vol- to connect initially . Then go about trying to get the above two vibes process while downloading . Be fast to double click download at the first of two vibes --
Thats it !
That is all anyone has to do :good:
One other thing to try is - just try power , on its own(like power off), press and keep pressed after initial connection download process, once it vibrates - release and -- go for the power and vol+ 2 vibe process again. Get ready to hit download !
---------- Post added at 05:42 PM ---------- Previous post was at 05:25 PM ----------
If that doesnt work ^^^ i will begin to start asking questions about the settings you have applied
Double check this ->
(fast forward to 18:30 mins in of this video for settings to be modified in XFSTK re... changing GP over ride to 0x80000807 ) . Make sure you modified the correct CRC+ box at the bottom
https://www.youtube.com/watch?v=PmbRaJijIBs&feature=youtu.be
Click to expand...
Click to collapse
Hi, sorry for the delay, i had a lot of work the past two days.
I've tried everything you said, double checked every parameter, and even tried the manipulation on another computer, but there is no change.
The weird thing is, that if i plug the phone into the computer, it gets detected, but there is no vibe, so no way to know when to click on download. I only get vibes on boot if it is not connected in USB.
Moreover, i don't really understand what you mean by " double click at the first 2 vibes", since the button gets "gray" after 1 press, and there is no way to double click it.
I'm sorry, you have put a lot of effort into helping me, but i really think that my phone may be more damaged than a simple brick :/

Solasmeryl said:
Hi, sorry for the delay, i had a lot of work the past two days.
I've tried everything you said, double checked every parameter, and even tried the manipulation on another computer, but there is no change.
The weird thing is, that if i plug the phone into the computer, it gets detected, but there is no vibe, so no way to know when to click on download. I only get vibes on boot if it is not connected in USB.
Moreover, i don't really understand what you mean by " double click at the first 2 vibes", since the button gets "gray" after 1 press, and there is no way to double click it.
I'm sorry, you have put a lot of effort into helping me, but i really think that my phone may be more damaged than a simple brick :/
Click to expand...
Click to collapse
Hi there ,
From first line of original post >
"..............Hi everyone,
Yesterday, as usual, i plugged my zenphone to its charger, but it almost instantly turned off and won't restart since.........................."
And last reply ..........
"..........................The weird thing is, that if i plug the phone into the computer, it gets detected, but there is no vibe, so no way to know when to click on download. I only get vibes on boot if it is not connected in USB..........................."
Suggests it will be USB board /port /cable :good:
Do the same again with data cable connected to phone but not connected to anything to rule out cable :good:

sukhwant717 said:
4.2 means battery more than 80 percent. you seems bricked. use the following guide step by step read everything carefully. any question post there in the thread. please search around before starting new thread.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
sukhwant717,
I registered (not only) but basically to say thank you.

kefalva said:
sukhwant717,
I registered (not only) but basically to say thank you.
Click to expand...
Click to collapse
Glad to know it helped

timbernot said:
Hi there ,
From first line of original post >
"..............Hi everyone,
Yesterday, as usual, i plugged my zenphone to its charger, but it almost instantly turned off and won't restart since.........................."
And last reply ..........
"..........................The weird thing is, that if i plug the phone into the computer, it gets detected, but there is no vibe, so no way to know when to click on download. I only get vibes on boot if it is not connected in USB..........................."
Suggests it will be USB board /port /cable :good:
Do the same again with data cable connected to phone but not connected to anything to rule out cable :good:
Click to expand...
Click to collapse
I'm not sure to really understand your last sentence ? Do you mean like removing the 2 power cables inside the USB ?
I've tried with different USB cables, and no change either :/

Solasmeryl said:
I'm not sure to really understand your last sentence ? Do you mean like removing the 2 power cables inside the USB ?
I've tried with different USB cables, and no change either :/
Click to expand...
Click to collapse
You can now only pray it is the USB board and not Mainboard , order a new USB board and a `new` Data cable, do not use old data cables with new board just incase your phones charge port has altered pins on either or both cables or data cable has changed pins on usb or vice versa :good:
ps , make sure it is a quality data cable you order too, some sell data when only a charge cable

[GUIDE] QDLoader 9008 fix | EDL Mode fix

Hi everyone,
If your phone does not react on any of yours actions. You may have the same problem. This is an instruction how to fix it.
If you have a last version of Windows 10 you can easily check if it is your case (You will have "Qualcomm HS-USB QDLoader 9008" device at your Windows devices' list.
How to Fix:
1. Download Drivers Qualcomm_QDLoader_HS-USB_Driver_64bit_Setup.zip and install it.
2. Download firmware link1 or link2
3. Install the driver
4. Unpack a firmware archive
5. Power off your phone by pressing Voice Down + Power Buttons (If your phone would be in this state too long the script would not works).
6. Start update_image_EDL.bat script - it will recreate all of the partitions
7. After the script will finish you will see the bootloader
8. Start script flashall_AFT.cmd - it will install firmware to the new partitions
9. Download fresh official firmware from asus site and put the archive at your memory card.
10. Start bootloader
11. Go to a standard recovery mode and install this firmware form the card
12. restart and repeat 10-11 (it will install software at the second state)
13. The problem is fixed. Congratulations!
Common problems:
Exception: System.DLLNotFoundException: DLL "QMSL_MSVC10R.dll": Module was not found. (HRESULT: 0x8007007E) can not be loaded.
Solution: You need to install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package MFC. Thanks to Genim

can you please update the post with the links to the software? thanks

admirdante said:
can you please update the post with the links to the software? thanks
Click to expand...
Click to collapse
I tried, but this was my first message, so I could not manage to do it (I need at least 10 messages). However, I report it to a moderator teams. I hope they will do it for me.

Hi OP,
I have edited the links into first post for you. Enjoy.
Jerry
Forum Moderator

Thank you so much OP. You saved my phone. It's been in Edl mode for about 2 months. Now it's up and running again.
Guys if I can add one thing to the OP post .. Make sure you plug the phone in and let it charge for awhile before attempting. Once you get to the fastboot mode it will not allow you to continue if your battery is too low. I understand that you can't tell what percentage the battery is but just let it charge for 2 hours and then do the whole process. I had to stop when I got to the fastboot stuff. And then continue after 2 hours on the charge.

st3wart said:
Thank you so much OP..
Click to expand...
Click to collapse
You are welcome. It took some time, so I decided to publish it.
st3wart said:
I understand that you can't tell what percentage the battery is but just let it charge for 2 hours and then do the whole process.
Click to expand...
Click to collapse
In fact I can. I intentionally bricked my phone 3 times to write the simplest possible tutorial (my first solution was too long, because I could not understand why the problem was fixed).
I could not implement this solution when I had 6 per cent of battery, but it worked ok when I had 11 per cent. I can guess, that if it more than 10% - it is ok to implement this tutorial.

st3wart said:
Thank you so much OP. You saved my phone.
Click to expand...
Click to collapse
I'm glad it worked for you! I made it into FastBoot Mode, but when I select Recovery, it puts me back into FastBootMode.
Am I missing something or did something not work properly? Don't know how to flash the official firmware now.

In fastboot mode... Go to the extracted files and double click on the flashall_aft file and sit back and wait until it finishes.

st3wart said:
In fastboot mode... Go to the extracted files and double click on the flashall_aft file and sit back and wait until it finishes.
Click to expand...
Click to collapse
I did click it. It opened and closed cmd too fast for me to read though.

That's what it did when my battery was low... Go plug your phone in with the original charger for an hour and then go directly to your PC and plug it in and double click that file and it should do it's job.
Also check to make sure your antivirus isn't blocking the file. Mine blocked access to it for whatever reason.

I did click it. It opened and closed cmd too fast for me to read though.
Click to expand...
Click to collapse
It looks like st3wart's answer is correct. I faced the same behavior when my phone had 6 per cent of battery. This problem was fixed as soon as my phone had 11 per cent of the battery. Thus you should try to charge it before starting the script.
Furthermore, if you would still face this problem you can copy files fastboot_.log and test1.txt and share all of logs with us (or just find the error by yourself).

error from fastboot_.log:
"Writing 'partition:0'...
FAILED (remote: Warning: battery's capacity is very low)"
I did charge it for 2+ hrs with the original charger though. When I unplug it, turn it off and back on again it gives a low battery error. When I plug it back in, it goes straight back into FastBootMode.
But it seems to not charge the battery for some reason.

I did charge it for 2+ hrs with the original charger though.
Click to expand...
Click to collapse
Did you charge it in EDL mode?
For some reasons it did not work for me either. I just booted to bootloader, then power-off the phone and saw the animation of charging. You can also try to flash TWRP (using their instructions) and charge your phone in this mode.
If it does not work - please check your charger.

goldman1993 said:
Did you charge it in EDL mode?
Click to expand...
Click to collapse
As soon as I charge the phone, the FastBoot screen comes up. When I select power off, it comes right back into FastBootMode. Is there a way to force shut down so i can charge it?
Also tried installing twrp, but when I select RecoveryMode it puts me back into FastBootMode again.

When I select power off, it comes right back into FastBootMode. Is there a way to force shut down so i can charge it?
Click to expand...
Click to collapse
It is a bit abnormal behavior. I'm not sure, why it happens, to be honest. Have you tried to use different cable or charger (I'm not sure what is the reason, so I would try to change something)?

Genim said:
As soon as I charge the phone, the FastBoot screen comes up. When I select power off, it comes right back into FastBootMode. Is there a way to force shut down so i can charge it?
Also tried installing twrp, but when I select RecoveryMode it puts me back into FastBootMode again.
Click to expand...
Click to collapse
Press power button for long time to power off.
Then try flashing every image of that link:
https://forum.xda-developers.com/ze...ne-6-proton-kernel-v1-0-t3963948/post80405617

goldman1993 said:
Have you tried to use different cable or charger?
Click to expand...
Click to collapse
I have.
I unplugged the phone and let the battery run comepletely empty until the phone shut off.
Then I plugged it back in and it charged for a minute (could see the charging symbol).
It then turned itself back on into FastBoot and stopped charging again.
---------- Post added at 07:29 PM ---------- Previous post was at 07:29 PM ----------
EMJI79 said:
try flashing every image of that link
Click to expand...
Click to collapse
I did flash them, but for some images it gave me the following error:
FAILED (remote: 'Error flashing partition : volume full')

Genim said:
I did flash them, but for some images it gave me the following error:
FAILED (remote: 'Error flashing partition : volume full')
Click to expand...
Click to collapse
Not good...

Then I plugged it back in and it charged for a minute (could see the charging symbol).
It then turned itself back on into FastBoot and stopped charging again.
Click to expand...
Click to collapse
Well, we can try to brick it one more time (put it into EDL mode). Then you can try to power it up in this state and unbrick it one more time.
Firstly you need to load to bootloader and write
.\fastboot.exe --set-active=b
Then you need to reboot your phone.
I believe, that you would not successfully load to bootloader (IT would be the same EDL mode), so you can try to charge it in this state or try tutorial one more time. (After a 30 minutes of your charging process you can try tutorial one more time).

goldman1993 said:
.\fastboot.exe --set-active=b
Click to expand...
Click to collapse
I ran that command and it bricked the phone again.
But I did wait too long before running the script. I'm getting an Sahara error.
How should I proceed? Can I just run that line again?

Question How to fix Poco F3 stuck in Fastboot?

I recently installed ArrowOS to my F3 and everything went well. Then I tried returning back to MIUI, flashing it through recovery didn't work so I used the MiFlash tool. Unfortunately I accidentally chose the Erase all and lock option but I exited the application halfway. Now my phone is stuck in fastboot and doesn't turn off, holding down the power button only resets and returns to fastboot. I tried reflashing MIUI both in fastboot and Miflash but both failed. I also checked if my phone was still unlock through MiUNlock and said it was unlocked, though the unlock icon isn't present when the phone is resetted. Is there a way to fix my issue, I'm really concerned if this will permanently break my device and possibly burin in the fastboot logo on my display. Any bit of advice and help is appreciated.

Lol , help you how?
Guess what's wrong ?
What error? Post everything first
Your phone is not locked if you removed it before end

Rstment ^m^ said:
Lol , help you how?
Guess what's wrong ?
What error? Post everything first
Your phone is not locked if you removed it before end
Click to expand...
Click to collapse
I'm stuck in fastboot and restarting does not work since it only goes back to fastboot.

AM3471_ said:
I'm stuck in fastboot and restarting does not work since it only goes back to fastboot.
Click to expand...
Click to collapse
Open mi flash , send error message

Rstment ^m^ said:
Open mi flash , send error message
Click to expand...
Click to collapse
Its just stuck in this step in both keep data and wipe all data.

Looks like usb cable contact issue to me , could even be locked if your halfway is 10min into flash or something... It also happens when you flash consecutively without rebooting
Check pc usb port , plug into usb 2.0 port
Check cable , use original cable
Reboot phone before every flash attempt
If one firmware doesn't work download and try another one ( Only if it spits out crc error : step 7/9 , any other error or lower step like 4/9 re insert usb cable into phone and don't touch it , the phone is losing contact ). Crc error is a real bich , you are on your own figuring that out , don't even bother with guides like removing crc check.
You are failing at the very first step , open mi flash logs from it's dropdown menu and either send screenshot or zip the whole folder and attach it here

1. Make sure ur device is unlocked bootloader
2. Download and extract this file https://t.me/PocoF3ID/494392
3. Double click hentai_go_away.bat it will help you out of fastboot and get you to twrp. From there u can install whatever rom u want.

armuttaqin said:
1. Make sure ur device is unlocked bootloader
2. Download and extract this file https://t.me/PocoF3ID/494392
3. Double click hentai_go_away.bat it will help you out of fastboot and get you to twrp. From there u can install whatever rom u w
Click to expand...
Click to collapse
He already used twrp and messed everything up , it won't work even if he gets into it.

Here are the logs of the Miflash, I used two versions the first being more recent.

AM3471_ said:
Its just stuck in this step in both keep data and wipe all data.
Click to expand...
Click to collapse
Reboot phone by holding power button for 10-15seconds , hold power down as well , don't let it try booting up at all.
Your best bet is to boot it straight into fastboot , not let it fail the boot and enter fastboot by itself

Rstment ^m^ said:
Looks like usb cable contact issue to me , could even be locked if your halfway is 10min into flash or something... It also happens when you flash consecutively without rebooting
Check pc usb port , plug into usb 2.0 port
Check cable , use original cable
Reboot phone before every flash attempt
If one firmware doesn't work download and try another one ( Only if it spits out crc error : step 7/9 , any other error or lower step like 4/9 re insert usb cable into phone and don't touch it , the phone is losing contact ). Crc error is a real bich , you are on your own figuring that out , don't even bother with guides like removing crc check.
You are failing at the very first step , open mi flash logs from it's dropdown menu and either send screenshot or zip the whole folder and attach it here
Click to expand...
Click to collapse
I used two version of Miflash, the first being the newest.

AM3471_ said:
I used two version of Miflash, the first being the newest.
Click to expand...
Click to collapse
Sorry I accidentally resent.

Rstment ^m^ said:
Reboot phone by holding power button for 10-15seconds , hold power down as well , don't let it try booting up at all.
Your best bet is to boot it straight into fastboot , not let it fail the boot and enter fastboot by itself
Click to expand...
Click to collapse
It only boots to fastboot, and trying to shut it off only restarts it to fastboot.

I reflashed miui and this error popped up.

AM3471_ said:
Sorry I accidentally resent.
Click to expand...
Click to collapse
Reboot phone , remove usb cable from phone , rotate it 180° and plug it in again. Don't touch the phone at all after that. Move away from pc table , click start and watch it from distance.
Fastboot commands are not going through correctly from what I've seen in the logs of one folder.
Send screenshot if it errors out again, and logs...
Honestly idk what to tell you , bring the phone under light and inspect the usb port, same with pc port and cable , if all is good keep rebooting the phone and plugging in the cable in and put after every flash.
I had the same issue before , my usb port had water dmg and would act the same way. Flashing fine one time , and other time erroring out in many different ways.

AM3471_ said:
I reflashed miui and this error popped up.View attachment 5509325
Click to expand...
Click to collapse
Send logs for that

This is 100℅ bad connection between phone and pc imo. Somerhing is not quite right , either you have junk in pc/phone/cable ports or there's corrosion covering the pins inside
37216a9f]:err:sending sparse 'super' 3/9 (781964 KB)...
[8:14:35 pm 37216a9f]:err:FAILED (data transfer failure (Unknown error))

Rstment ^m^ said:
Send logs for that
Click to expand...
Click to collapse
This will be my last post for now, I need to get some sleep since its late here, if i dont find any fix tomorrow I'll just send to a repair shop.

Rstment ^m^ said:
This is 100℅ bad connection between phone and pc imo. Somerhing is not quite right , either you have junk in pc/phone/cable ports or there's corrosion covering the pins inside
37216a9f]:err:sending sparse 'super' 3/9 (781964 KB)...
[8:14:35 pm 37216a9f]:err:FAILED (data transfer failure (Unknown error))
Click to expand...
Click to collapse
I'll try using a different PC tomorrow to see what the problem is.

AM3471_ said:
This will be my last post for now, I need to get some sleep since its late here, if i dont find any fix tomorrow I'll just send to a repair shop.
Click to expand...
Click to collapse
That's not the log file for error above... But I found similar one in folders above.
Clean the ports before you sleep... Power off everyrhing , phone pc , remove usb cable from charger and clean them all with cotton - if you have 97℅ or higher alchohol you can soak the cotton in it and clean the ports.
If not just send it back to service... They will prolly replace your motherboard if the flashing fails on their end as well , usb port will only be replaces at the very end of their troubleshooting.