Develop Bugs

[Q] Gnex Brick Mount Fastbood Write Fail help :'(

Hi everybody,
ok I will try to make this short
I have an experienced user level ROM, recovery, boot, ..
My phone is BRICKED! Is it?
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I can't start in recovery mode
- I can't start bootloader mode
- I have a connection with a laptop (win XP, as win8.1 didnt work for me)
- The computer can communicate with the phone in fastboot mode
- The computer cant communicate with the phone in Odin mode (at the moment Odin PC SoftWare doesn't recognize the phone)
- I am sure the drivers are installed correctly now. Thanks to the guide with fully stripped drivers.
- Using different, multiple different, no thousand different methods I tried flashing the stock OS (Yakju 4.3)
- I like SkipSoft Android ToolKit (Although I used fastboot and adb commands, I find the toolkit to do the same thing..)
- I always get an Error, when the process of flashing starts.
> PC says : Error
> Phone (in fastboot mode) says: FAILWrite Fail
INTERESTING:
- While I still was able to get into Recovery, the phone couldnt mount the sdcard (=> the internal drive)
- Some of the methods I use make the phone CRASH
> means the screen stops at its position and slowly turns completely purple
- The phone power button doesnt start the phone, to get the phone doing something at all I have to trick it:
..> I plug it into the wall charger
..> I take the battery out
..> I put the battery back in
..> I wait
..> I can get into 3 routines:
^Normal starting routine (of course stuck at google start up, since no Rom is installed)
^fastboot mode (VOL + & - & Power)
^odin mode (VOL - & Power)
..> Then I can just plug the USB cable into the PC
- 2 days ago I had (every single version) of Odin PC Software recognizing the phone (phone was in Odin mode), but it also failed after trying the recommended and unrecommended settings. Ended with an error message.
HOW:
I left my phone overnight in the car (Temp: -2 deg C), while Im sure spotify and maybe other consuming apps were playing.
Next day, my phone battery was empty and I couldnt start my normal ROM. (I had Slim Rom installed)
It was stuck at the "Google" start up display.
First intentions showed that it might be more than just the Software :/
Many days and so many hours of work, research and reading in forums, I decided to take a shot and ask here.
I appreciate everything xda-members have done for me already. Though I never needed to register for my earlier questions.
Phone data:
Product Name - tuna
Variant - maguro 16gb
HW version - 9
Bootloader Version - primemd04
baseband version -
carrier info - none
serial number - -a3c208 ***
signing - production
lock state- unlocked

BUMP!!! I have absolutely the same problem!! I can access everything, i enter the recovery trying to WIPE every single thing data,system,cache,storage etc.. but it seems it doesnt work. The information stays. I tried to "softbrick unroot & stock" with a nexus kit, everything seems ok, but after it finishes installing, it boots up on GOOGLE and after 10-15 min it starts to BOOT MY OLD CUSTOM ROM THAT I HAD BEFORE, after another 15-20 min it finally boots up and the system is EXTREMELY choppy and unresponsive and after a few minutes it restarts itself. I tried ODIN and I faced the same problem, it goes well to ~45% and then it freezes, and after a short delay odin gives FAILED. I tried several more things that i found on the internet and xda but nothing helps. Probably a corrupted partition or something. THE DAMN STORAGE DOESNT WANT TO DELETE ITSELF FFS!! PLEASE IF YOU KNOW ANY FIX/ALREADY FIXED YOURS PLEASE HELP!!! I need my phone!

can you give us more information about the error message?
valkata1212 said:
Click to expand...
Click to collapse
your issue sounds like this one, can you confirm?

Soulaysahmi said:
can you give us more information about the error message?
your issue sounds like this one, can you confirm?
Click to expand...
Click to collapse
Similar, only difference is with fastboot i can successfully flash system.img but nothing happens. With odin it fails at around 45% and then freezes. Only difference is that i cannot boot to old stock and i dont have this pulpish problem. I simply reboot on my old custom ROM configuration with all my last known icons widgets.. but the phone is choppy and unresponsive as hell.

I only get an error without any further message after flashing any of the images...
Any idea anyone? Isn't it some hardware issue?

Noo man i dont think its hardware problem, for me it all happened when my phone suddenly restarted itself and after that it bootloops forever and i have those problems

Anyone?

does erase work?

yes

can you get into recovery?

oxxomexico said:
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I can't start in recovery mode
- I can't start bootloader mode
- I have a connection with a laptop (win XP, as win8.1 didnt work for me)
- The computer can communicate with the phone in fastboot mode
- The computer cant communicate with the phone in Odin mode (at the moment Odin PC SoftWare doesn't recognize the phone)
- I am sure the drivers are installed correctly now. Thanks to the guide with fully stripped drivers.
Click to expand...
Click to collapse
ka

how do you know that erase works, I mean that what you erased has really been erased?

One of the erase command in the toolkit was succesful, I guess. But I will recheck every error or successful message later tonight.

still NOT working
2 months have passed and I was too busy with other things.
now back to it. the problem hasnt changed.
i try fastboot flash command:
[fastboot flash bootloader x.img]
- in Computer Terminal: 'FAILED(remote:Write Fail) '
- on phone: ' FASTBOOT STATUS - FAILWriteFail '
any idea, please?

How to root TP-LINK NEFFOS Y5L ANDROID 6.1

Hi everyone. Just like in the title of my post. I've just bought a TP-LINK NEFFOS Y5L smartphone, and I started to looking information, how I can get root for this device. And I found it:
https://morfitronik.pl/android-root-smartfona-neffos-y5l-tp-link/
Sad that this site is`t online anymore, but u can find it on github or gitlab.
I've flash this recovery, and it's working fine. The next step to root was to download the zip package from the chainfire site (currently abandoned, but u may use magisk from xda) :
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Latest MAGISK:
https://github.com/topjohnwu/Magisk/releases/download/v16.0/Magisk-v16.0.zip
Well, I've done it. It's working, and I have root on Android 6.1.
Here it is :
View attachment recovery-neffos-y5l-tp-link-twrp.apk
u will have to change extention of file from *.apk to *.img due to xda registration of size file uploaded.
Tutorial how to do this:
https://youtu.be/SfkbkcXSa2M
And if u want to buy me a beer, that is my account number:
PL 37 1020 4317 0000 5402 0389 9689
IBAN BPKOPLPW
Thanks a lot for your support.

How did you flash that twrp recovery...:laugh:

I just flash this recovery via fastboot mode.

TuanPengarah said:
How did you flash that twrp recovery...:laugh:
Click to expand...
Click to collapse
U may also try to boot your phone in this recovery throu fastboot boot image.img

Hello,
I am a bit new... It seems I can't use flashboot mode.
I have DL ADB, then when I key : /adb devices, I see my Y5L.
Then I try to relaunch my device by pressing the VOL + / Restart button => I reach a picture of android and 3 japanese (or chinese characters).
When I plug the device to my PC, it seems that nothing happen (like it was not recognised by the PC).
Du you have any idea?
Best regards

Hello. It is a very annoying thing, but also very simple to solve. If u see the broken robot when u trying to enter to recovery, u must push and hold power button and short press vol+. But if you want to go to recovery or fastboot mode, u don't have to power down your phone. Just go to cmd (or whatever) console and write:
" adb reboot recovery" to boot up you device in recovery mode or
"and reboot bootloader" to boot into fastboot mode
Seeia.

Greetings!
The custom TWRP link does not seem to work as it should be. Either that or I am missing something
Could you please re-upload the recovery file?
Thanks!
"edit: I found it"

Can someone write a tutorial please, it's the first time i try to root with TWRP and i don't understand if the bootloader method for emample is from the device or from the pc because i can enter to the official android device (Y5L ANDROID 6.0.1 ) recovery menu but when i choose to boot at bootloader the phone freeze at the logo. Thanks a lot for any help.

Calaad said:
Hello,
I am a bit new... It seems I can't use flashboot mode.
I have DL ADB, then when I key : /adb devices, I see my Y5L.
Then I try to relaunch my device by pressing the VOL + / Restart button => I reach a picture of android and 3 japanese (or chinese characters).
When I plug the device to my PC, it seems that nothing happen (like it was not recognised by the PC).
Du you have any idea?
Best regards
Click to expand...
Click to collapse
1. pressing the VOL up + Power button => reached a picture of android and 3 Chinese characters (means no command !)
2. pressing again the VOL up + Power button => then you will reached recovery mode.

I had seem this polish method but I get afraid because there is no method to recovery to original rom.
I hope to see a custom rom in next days.

thanks

Hi, I'm trying to install the custom bootloader but after running:
abd reboot bootloader
the phone gets stuck on the tp-link logo.
Trying with volume-up + power shows the broken android logo, from there, holding power + vol-up gets me to recovery but neither fastboot nor adb detect the device. Selecting the "reboot to bootloader" option there ends in the same lock on the tp-link logo.
(I did activate the "unlock bootloader" in developer options.)
Any ideas on how to proceed? thx in advance.

TieSKey said:
Hi, I'm trying to install the custom bootloader but after running:
abd reboot bootloader
the phone gets stuck on the tp-link logo.
Trying with volume-up + power shows the broken android logo, from there, holding power + vol-up gets me to recovery but neither fastboot nor adb detect the device. Selecting the "reboot to bootloader" option there ends in the same lock on the tp-link logo.
(I did activate the "unlock bootloader" in developer options.)
Any ideas on how to proceed? thx in advance.
Click to expand...
Click to collapse
Yeah i also had this problem, open at the android menu your phone and make sure you have enable developer settings and USB Debugging, install Wondershare MobileGo at your pc ( you don't need to install the app at your phone) and connect your phone with the pc, wait to find the drivers at the charge usb selection and after that swap from your phone to all 4 settings of usb connections, mobilego will download 4 drivers total and after that it will read it.
I cant post a link but if you have Chrome to translate from polish to english there is a new simple tutorial, go at the first link at the op post and at the site click at the red text at the beginning next to "twrp" text and translate to english for guide.

sixdiceray said:
Yeah i also had this problem, open at the android menu your phone and make sure you have enable developer settings and USB Debugging, install Wondershare MobileGo at your pc ( you don't need to install the app at your phone) and connect your phone with the pc, wait to find the drivers at the charge usb selection and after that swap from your phone to all 4 settings of usb connections, mobilego will download 4 drivers total and after that it will read it.
I cant post a link but if you have Chrome to translate from polish to english there is a new simple tutorial, go at the first link at the op post and at the site click at the red text at the beginning next to "twrp" text and translate to english for guide.
Click to expand...
Click to collapse
That worked fine. Weird there's no official drivers for download.
Thx.

TieSKey said:
That worked fine. Weird there's no official drivers for download.
Thx.
Click to expand...
Click to collapse
NP and maybe there is but i didn't find any official mobile app management tool from tplink to download.

Thx!

A little offtopic but, any idea on how to enable diagnostic usb port on this device? Nothing in this guide worked so far: https://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059

hi
Why does not this mobile display the number of unread messages (sms)?
Why can not I choose one or two SIM cards in my message program?
Why does not the percentage of battery remaining up the screen?
Why does gps work too slowly?

I Have Successfully installed TWRP But when restart TWRP I got blank image
I have successfully install but when reboot recovery I got blank image that have don't show TWRP Logo

How to root!?
Whit out pc?

Fastboot on European LG G7 Fit?

Hello
I have a question. I'm trying to enable Fastboot mode on my Lg G7 Fit. But when I try to activate Fastboot with the command "adb reboot fastboot" the device boots normally. What do I have to do to get into fastboot mode?

With the phone shutdown, have you tried holding VolumeDown while connecting to PC?

slvjpn said:
With the phone shutdown, have you tried holding VolumeDown while connecting to PC?
Click to expand...
Click to collapse
Yes. However, first the LG G7 Fit logo is displayed, then the battery level and if I hold down even longer, the phone starts quite usual.

Micro-USB?
Edit: When searching I noticed one thing: On the website of Hardreset It is said that I have to plug in a MICRO USB CABLE, but the phone only has Usb-C. Has that something to do with my problem? (I guess not)

This is one for the "absurdly easy once you know how" department.
* Turn off phone, unplug USB.
* Press (and hold, obviously) Volume-Up.
* Plug in USB.
* Fastboot logo appears.
* Run "fastboot whatever".

smurfix said:
This is one for the "absurdly easy once you know how" department.
* Turn off phone, unplug USB.
* Press (and hold, obviously) Volume-Up.
* Plug in USB.
* Fastboot logo appears.
* Run "fastboot whatever".
Click to expand...
Click to collapse
Sorry, but I repeat myself. Unfortunately this manual is only for non EU smartphones. If it worked, I would not ask. By pressing the volume-up button I enter the download mode. Volume Down does nothing

You're right, I was confused. Sorry.
So it seems that we need to figure out how to mimic LG's firmware upgrade protocol sufficiently to replace the recovery partition. (And get a TWRP for the phone.)
Both are nontrivial. I found https://www.sciencedirect.com/science/article/pii/S1742287615000535 that has some minimal info on the first step but I had no luck so far reproducing that.

smurfix said:
You're right, I was confused. Sorry.
So it seems that we need to figure out how to mimic LG's firmware upgrade protocol sufficiently to replace the recovery partition. (And get a TWRP for the phone.)
Both are nontrivial. I found https://www.sciencedirect.com/science/article/pii/S1742287615000535 that has some minimal info on the first step but I had no luck so far reproducing that.
Click to expand...
Click to collapse
Hmmm ... I understand only half of what was there, however, the website says this here: "The firmware update process runs only when smartphones enter a special mode firmware update, or the download mode. Only the bootloader and USB function can operate in this mode and a new system firmware can be flashed. " Could it be that the bootloader can be accessed via download mode?
Edit: No, you can't. Pressing the button combination for Fastboot in Download Mode does nothing. Fazit: There is no Fastboot+Bootloader on european G7 Fit's.
Edit edit: Android 9 Update coming soon. I hope that the Fastboot Mode will be added...

This is fastboot mode for LG? Last LG I had was a Nexus so I dont know how it should look like.
Volume UP while connecting phone brings up this mode.
Fastboot list devices command freezes..so it doesent work atm.
Android 9 UK or IT flashed over HUN version.

Gansterdrift said:
Edit edit: Android 9 Update coming soon. I hope that the Fastboot Mode will be added...
Click to expand...
Click to collapse
Unfortunately not. After the update to 9, fastboot is still absent. 'adb reboot bootloader" just reboots the phone

Boot loop issue: cannot get into fastboot from "no command" screen

Hey everyone,
A2 lite phone is in bootloop - allegedly (not my phone) "out of nowhere". The user does not do any fancy things like flashing, and this has not been done either.
Phone is on continuous boot loop, and sometimes (really seems randomly), the device starts up in the "no command" mode and stays there for a while. I read that we could go into fastboot mode by pressing "power button and tapping volume up key", but this doesn't do anything.
I've tried this thread: https://www.the***********.com/boot-xiaomi-mi-a2-fastboot-mode-recovery-mode/
But I'm not even getting into fastboot.
I'm almost thinking that the volume buttons are just broken, though from the feedback of the buttons this doesn't seem realistic.
EDIT: ok, now I'm somehow able to get it into fastboot.... sometimes. Now I'm here:
I switched the partition from a to b, but it still goes into bootloop. Then I switched it back to a, still bootloop. Then back to b. Still bootloop! But at least now sometimes I'm able to get into fastboot. No matter what kind of commands I'm typing in the cmd console, after about 10 seconds on the fastboot screen, the phone just reboots.
idk, it looks almost as if both partitions have the bad android 10...
Do you guys have any idea? Please let me know if more info is helpful.

You go into fastboot mode by holding Vol Down + Power button. So try holding Vol Down and Power button at the same time to go into fastboot mode. (Don't tap it)
Go here and grab the image you prefer (latest should do the trick) : https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Then go ahead and follow this guide here to flash the stock ROM : https://c.mi.com/oc/miuidownload/detail?guide=2
This will wipe the data on the device, but it seems like you have no other option at this point. Cheers.

Thanks! I've tried that now. It starts flashing the device until... after about 10 seconds, the phone reboots from Fastboot mode .

As per this page: https://twrp.me/xiaomi/xiaomimia2lite.html
I've tried to do a recovery via TWRP. If I execute `fastboot boot path/to/twrp.img` then I go from fastboot to TWRP (the teamwin logo), but right after that the phone already reboots.
https://www.xda-developers.com/how-to-install-twrp/ - I don't know if it means anything, but when I execute `adb reboot bootloader`, the console returns `error: no devices/emulators found. If I execute `adb devices`, it does not list my device. However, if I execute `fastboot devices`, my device is listed.
I installed ADB usb drivers, so when I get my phone connected in fastboot, it shows up as Android Bootloader Interfacee in device manager. So not sure what's going on here, but it's all weird.
What I'm facing is very, very similar to https://www.reddit.com/r/Xiaomi/comments/4ltzt9/xiaomi_mi_note_boot_loop_even_in_fastboot/ <-- but that thread is a bit of a dead end (and 3 y/o)...

daize said:
after about 10 seconds, the phone reboots from Fastboot mode .
Click to expand...
Click to collapse
Hmm, it should never do that, maybe it's a hardware issue that we can not fix via Fastboot ?
daize said:
As per this page: https://twrp.me/xiaomi/xiaomimia2lite.html
when I execute `adb reboot bootloader`, the console returns `error: no devices/emulators found. If I execute `adb devices`, it does not list my device. However, if I execute `fastboot devices`, my device is listed.
Click to expand...
Click to collapse
When the device is in Fastboot mode, it will only be recognized as Fastboot. Only when it's properly booted, the device can be recognized in ADB, so no issues there.
I assume your bootloader is already unlocked as you have successfully booted into TWRP. You might try EDL (Emergency Download Mode) flash as a last resort :
Download MiFlash (20160401) from here : https://www.xiaomiflash.com/download/
You're downloading that particular version because it is able to EDL flash on your phone. Install the MiFlash you've downloaded and open it, then put the phone into fastboot mode. Connect it to your PC and use this code to take the phone into EDL mode:
Code:
fastboot oem edl
After you hit enter, you will see the screen turn off and notification LED blinking, this is normal. This means the phone is in EDL mode. Open the MiFlash you've installed (likely in C:\Program Files\Xiaomi\MiPhone) and browse to the ROM location and connect the phone. Choose "Flash All" and start flashing.
After the EDL flash is complete the phone will not reboot. It will stay in EDL mode. You need to disconnect the phone from PC and hold power button (about 10-15 seconds) to boot the phone. If the phone boots properly, you can go into fastboot and connect it to PC, then use:
Code:
fastboot oem lock
to relock your bootloader. Try it and let me know. :fingers-crossed:

Thanks for the continued help!
I've followed your steps - When I run fastboot oem edl, the console returns "... okay [ 0.0202s] finished. total time: 0.022s" and the phone turns to a black screen (no notification led blinking). Then... after a couple of seconds, goes back into the boot loop .
Something maybe to note: every time that my phone starts up, it (1) shows a screen saying "Your device software can'tbe checked for corruption.Please lock the bootloader.", and then slides down to the typical "androidone" white screen before it reboots again.

daize said:
every time that my phone starts up, it (1) shows a screen saying "Your device software can'tbe checked for corruption.Please lock the bootloader.", and then slides down to the typical "androidone" white screen before it reboots again.
Click to expand...
Click to collapse
The screen with the ugly text is normal, since you have an unlocked bootloader, it's there to warn you that the device's software might've been tampered with. On the main subject though, I'm out of ideas. You might try booting the phone by holding Power + Vol Up, which should normally boot into stock recovery or wipe the data on the device. But I'm slowly beginning to think that this might be a hardware issue rather than a software issue that I can help you to fix.
Under normal circumstances, EDL flash is the way to fix any problems you might encounter with the software, that's why it's called the Emergency Download mode. But since we're past that stage, I believe I will not be able to assist you further. Hope you can fix your device my dude/dudette!

If the phone gets out of fastboot mode your phone does not get recognized from your computer. Try to delete fastboot and minimal adb and download the latest version. [https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445]
Open MiFlash, click Driver left on the top and install them.
Set path to the downloaded firmware. Now boot into fastboot, once that is done connect your USB cable to both, computer and phone. If this doesn't work try different USB-Ports and USB-cables. Some work, some don't. This might be the reason for leaving the fastboot mode.
Click refresh and see if your device appears

@marstonpear thanks for your help so far <3 @Cappucinto, thanks for chiming in! What do you mean with this: "Open MiFlash, click Driver left on the top and install them." <-- in MiFlash, I do not see an option to select driver...

@marstonpear thanks for your help so far <3
 @Cappucinto, thanks for chiming in! What do you mean with this: "Open MiFlash, click Driver left on the top and install them." <-- in MiFlash, I do not see an option to select driver...

What did change now after installing these drivers: https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445]
I did try some other USB cables. The one I've been trying triggers the windows sound for "new device successfully connected" when I boot the phone up in fastboot, and then of course gives the "device disconnected" sound when the phone then reboots. With another USB cable in this case, windows just states: "USB device not recognized". So it seems like the cable I haven't been using is defect .

I'm unable to use MiFlash at the moment so I can't explain the whole procedure with installing the drivers in MiFlash. But there has to be something like "Install > Drivers" or something. Maybe someone else can help out.
Try to use the working cable again, open a command prompt and type: fastboot devices
Then wait for an answer, post it here and see if the phone reboots again or if it stays in fastboot

daize said:
Hey everyone,
A2 lite phone is in bootloop - allegedly (not my phone) "out of nowhere". The user does not do any fancy things like flashing, and this has not been done either.
Click to expand...
Click to collapse
The response by marstonpear below makes sense.
marstonpear said:
You go into fastboot mode by holding Vol Down + Power button. So try holding Vol Down and Power button at the same time to go into fastboot mode. (Don't tap it)
Click to expand...
Click to collapse
Although u shd consider this link, i tried to arrange it step by step:
https://forum.xda-developers.com/sho...php?p=79365091
Follow the instructions, as dat was how i revived mine. Hopefully it may help u.
Note; wen using twrp, preferably use " twrp - offain "
Miflash tool:
Link 1: https://www.xiaomiflash.com/download/
Preferably use Link 1 & choose either 2016, 2017 or 2018 versions. They come preloaded with the drivers u need
Link2: https://xiaomibuzz.com/downloads/download-xiaomi-mi-firmware-flash-tool-latest-version-2018.html
Lets know how it goes

Cappucinto said:
I'm unable to use MiFlash at the moment so I can't explain the whole procedure with installing the drivers in MiFlash. But there has to be something like "Install > Drivers" or something. Maybe someone else can help out.
Try to use the working cable again, open a command prompt and type: fastboot devices
Then wait for an answer, post it here and see if the phone reboots again or if it stays in fastboot
Click to expand...
Click to collapse
Hey there When I get into fastboot and run `fastboot devices`, a code returns <tab> fastboot.
... and then the phone restarts I'm trying but I guess I'm beyond the stage of being upset, haha.
@agbadino https://forum.xda-developers.com/sho...php?p=79365091 <-- that first link seems to be broken, could you check again? I'd love to try your steps!

daize said:
@agbadino https://forum.xda-developers.com/sho...php?p=79365091 <-- that first link seems to be broken, could you check again? I'd love to try your steps!
Click to expand...
Click to collapse
Sorry bout d previous link. I believe this shd take u directly to the tutorial:
https://forum.xda-developers.com/mi...tboot-mode-t3920925/post79365091#post79365091
remember to use "twrp offain for daisy". It works better than the regular twrp for daisy
It my take and procedure that worked for me at the time. Good luck tho

Thanks! Sadly, when I get to the `fastboot oem edl` step, it fails. I get into fastboot, I quickly enter `fastboot oem edl`. CMD says finished, the screen turns off. I immediately refresh in MiFlash (COM3 is the device), I start flashing. After 4 seconds, the device turns off (windows sound "device disconnected"). The flashing runs for a total of 7-9s says "the operation completed successfully.(0x000000000: cmd <?xml version="1.0" ?><data .. etc etc
So I don't really know what to do if I can't get into EDL mode .

daize said:
Thanks! Sadly, when I get to the `fastboot oem edl` step, it fails. I get into fastboot, I quickly enter `fastboot oem edl`. CMD says finished, the screen turns off. I immediately refresh in MiFlash (COM3 is the device), I start flashing. After 4 seconds, the device turns off (windows sound "device disconnected"). The flashing runs for a total of 7-9s says "the operation completed successfully.(0x000000000: cmd <?xml version="1.0" ?><data .. etc etc
So I don't really know what to do if I can't get into EDL mode .
Click to expand...
Click to collapse
Try getting another chord and try again.

Tried some other cables. Every time I run fastboot oem edl, it keeps saying "finished", and then reboots the phone in about 5 seconds. One time, it said "Catastrophic failure" as "status" for the flashing.
Otherwise, it most often says "The operation completed successfully.(0x00000000: cmd <?xml version="1.0"?><data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="16" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="NUM_DISC_SECTORS-1." value="CRC32(NM_DISK_SECTORS-1.,92)" what="Update"/></data>)
But then still continues in the bootloop...

Can't access Fastboot mode/ADB

So, I flashed Derpfest A12 ROM, It boots fine but gets stuck on "getting your Android 12 Ready" screen with the animation. I can access wifi and visiblity options but not settings. I flashed TWRP from the official website to install the recovery. But now when I reboot and press Volume Down, TWRP is stuck on boot animation. So I thought just reset using fastboot and start again and pressed volume up and power button but it does NOT work. I tried the volume buttons again in the rom [i can change volume in the starting screen] and they are working. I can press volume down and power button to reboot into recovery and it works fine but gets stuck. So, I just want to have access to adb or fastboot to reset this phone but neither seems possible. I Cant enable advanced reboot in the starting screen. Fastboot doesnt work. ADB not recognizing as it is a new rom and havent enabled it [i enabled in the previous rom]. Thanks for you Help in Advance!
P.S. I have tinkered POCO F1 fairly so I am not totally new to this scene!
EDIT: Thanks for all the replies! But I solved the problem, Idk how but i got access to fastboot mode after some tries and reflashed everything and now it works, also I use linux and the adb drivers and fastboot were in repos so it was easy.

hello,
I am a novice and use a translation tool to write to you (sorry if there are errors...).
Ok I already installed roms (but a long time ago on a OnePlus One...
I have an OP5T, I want to install lineage Os 19.1 on it.
I followed the tutorial on the lineage wiki.
I installed ADB and fastboot well, as well as universal adb driver.
I'm on windows 11, it works.
I enabled debug mode
The adb reboot bootloader command works, so the tel is well seen by the pc and the tel restarts in fastboot mode.
Then nothing, no command (oem unlock) works, the computer does not seem to see such after restarting in fastboot mode.
I read some topic on the net that say that the phone must be in "battery charging" mode and not "file transfer". Me to be visible by adb I have to put it in file transfer mode, otherwise it is not seen.
If I put in recharge mode, same thing to do.
Do you have a tip or should I give up?

ezivoco_163 said:
The adb reboot bootloader command works, so the tel is well seen by the pc and the tel restarts in fastboot mode.
Then nothing, no command (oem unlock) works, the computer does not seem to see such after restarting in fastboot mode.
I read some topic on the net that say that the phone must be in "battery charging" mode and not "file transfer". Me to be visible by adb I have to put it in file transfer mode, otherwise it is not seen.
If I put in recharge mode, same thing to do.
Do you have a tip or should I give up?
Click to expand...
Click to collapse
You need to install not just the adb drivers, but the fastboot ones as well, see this guide for example. This driver is the one needed for fastboot.
My devices have always been in file transfer mode btw, I've never heard of it needing to be in charging mode only.

No, you don't have to be in "charging only" vs "data transfer".
Still, those of us who distain to be plebian keep our devices in "charging only" (with ADB on) as MTP is beneath our contempt.
(Actually, the problem is that the USB VID/PID sometimes changes with each mode and that you may not have a driver loaded for ADB only.)

Nimueh said:
You need to install not just the adb drivers, but the fastboot ones as well, see this guide for example. This driver is the one needed for fastboot.
My devices have always been in file transfer mode btw, I've never heard of it needing to be in charging mode only.
Click to expand...
Click to collapse
Renate said:
No, you don't have to be in "charging only" vs "data transfer".
Still, those of us who distain to be plebian keep our devices in "charging only" (with ADB on) as MTP is beneath our contempt.
(Actually, the problem is that the USB VID/PID sometimes changes with each mode and that you may not have a driver loaded for ADB only.)
Click to expand...
Click to collapse
ok thanks, i a going to try this