Fairphone 2 doesn't start into fastboot - Fairphone 2

Hi dear developers, just bought an old FP2, usb-debugging succeeded, but the fone does not boot into fastboot, only the "Fairphone"-logo appears and it's even not possible to shut it down, except by removing the battery.
Any ideas how to fix this?
Thx along, greetings, draftflash!

Ouh f... that IS the fastboot-mode!!!
Impossible to reach the bootloader on FP2 [SOLVED]
Yes, that is the exact description how Fastboot mode looks like. Fastboot mode means that your phone becomes a passive recipient of commands.
forum.fairphone.com
never guessed it!

Related

Reflashing bootloader on Mi4C?

Hi everyone,
I'm having this "locked bootloader" issue as probably hundreds other people do, since January update appeared. In my case the phone became unusable, stuck on MI logo, and also there is no recovery available.
I can only use fastboot.
I understand that some people managed to completely erase the eMMC and reflash the bootloader while the phone is connected to the computer in "Qualcomm HS-USB QDLoader 9008" or "QHS_USB Bulk" mode.
I can't figure out how to boot the phone in either of these modes! When connected through fastboot the MI4C is being recognized as "Marshall London Bootloader Interface". When I just turn it on and it's stuck on MI logo, it isn't recognized by device manager at all.
I'm on Windows 10 64 bit. Anyone has any idea what needs to be done to access these modes on Mi4C?
Many Thanks!
dsafro said:
Hi everyone,
I'm having this "locked bootloader" issue as probably hundreds other people do, since January update appeared. In my case the phone became unusable, stuck on MI logo, and also there is no recovery available.
I can only use fastboot.
I understand that some people managed to completely erase the eMMC and reflash the bootloader while the phone is connected to the computer in "Qualcomm HS-USB QDLoader 9008" or "QHS_USB Bulk" mode.
I can't figure out how to boot the phone in either of these modes! When connected through fastboot the MI4C is being recognized as "Marshall London Bootloader Interface". When I just turn it on and it's stuck on MI logo, it isn't recognized by device manager at all.
I'm on Windows 10 64 bit. Anyone has any idea what needs to be done to access these modes on Mi4C?
Many Thanks!
Click to expand...
Click to collapse
You need a working phone with USB debug enabled, then " adb reboot edl" from cmd... Sorry but if you are in a boot loop there is no knows way to access the Qualcomm mode...
There is no way for you to go into EDL mode. You need to apply for unlock permission from Xiaomi if you want to fix your mi4c yourself.
I applied for permission on Feb 1, and I got it today (Feb 18) despite the Chinese New Year holidays. I haven't even received my mi4c from China yet, and am not even a diamond member at miui.com, either. Good luck!!
dsafro said:
Hi everyone,
I'm having this "locked bootloader" issue as probably hundreds other people do, since January update appeared. In my case the phone became unusable, stuck on MI logo, and also there is no recovery available.
I can only use fastboot.
I understand that some people managed to completely erase the eMMC and reflash the bootloader while the phone is connected to the computer in "Qualcomm HS-USB QDLoader 9008" or "QHS_USB Bulk" mode.
I can't figure out how to boot the phone in either of these modes! When connected through fastboot the MI4C is being recognized as "Marshall London Bootloader Interface". When I just turn it on and it's stuck on MI logo, it isn't recognized by device manager at all.
I'm on Windows 10 64 bit. Anyone has any idea what needs to be done to access these modes on Mi4C?
Many Thanks!
Click to expand...
Click to collapse
Did you try flashing it with Miflash? I got bricked yesterday, so I reflashed system this way, but via Qualcomm HS-USB QDLoader. Also, my phone did not react to anything except bootloader mode (holding buttons for a long long time), no charging, no lights - nothing.
Me too
Me too. :crying:
Hi,
I have the same problem of the bootloader locked. Not let me do anything. It is blocked. I've tried to give instructions by ADB, but will not let me load any file since it claims to be the phone locked.
I have applied the code unlock via SMS to Xiaomi, but they are very slow. Yesterday I wrote and asked you to unlock it. They asked me 2 days more waiting, at least.
This is still horrible, a shame.
I read the post of a colleague who manages to unlock it but has to be the phone working. For those who stayed with my at startup, there is no solution.
Regards.

[Completed] Usb debugging from windows 10?

Hello to You all!
Having a hell of a problem here and I cant solve it by myself, tryed like 10 times over the past year and its time to realize I´ve been beaten...
I wonder if its possible to enable usb debugging in bootloader mode? I have this Mediapad x2 that i tryed to unlock the bootloader on a year ago and though the bootloader unlocked (shown as "unlocked" in bootloader mode) the phone never restarted again... It loops at the bootscreen. Vol down gets me to bootloader though, both vol up/down gets me to auto restore but even if I have the right file on the SD-card the phones autorestore hangs at 90%...
All manual commands like "fastboot flash system system.img" or "fastboot flash recovery TWRP.img" only give´s me "FAILED (remote: Command not allowed)"...
I THINK it must be the USB debugging that doesn´t allow me to write, I´m not that advanced in this area...
Any help appreciated mates, I really liked this phone.
Thank You.
XDA Visitor said:
Hello to You all!
Having a hell of a problem here and I cant solve it by myself, tryed like 10 times over the past year and its time to realize I´ve been beaten...
I wonder if its possible to enable usb debugging in bootloader mode? I have this Mediapad x2 that i tryed to unlock the bootloader on a year ago and though the bootloader unlocked (shown as "unlocked" in bootloader mode) the phone never restarted again... It loops at the bootscreen. Vol down gets me to bootloader though, both vol up/down gets me to auto restore but even if I have the right file on the SD-card the phones autorestore hangs at 90%...
All manual commands like "fastboot flash system system.img" or "fastboot flash recovery TWRP.img" only give´s me "FAILED (remote: Command not allowed)"...
I THINK it must be the USB debugging that doesn´t allow me to write, I´m not that advanced in this area...
Any help appreciated mates, I really liked this phone.
Thank You.
Click to expand...
Click to collapse
Hello,
Do you have correct fastboot drivers installed on your system? Please run it with administrative privileges.
Please register for XDA account to post and reply in the forum.
Regards
Vatsal,
Forum Moderator.
Thread closed as you already posted it here https://forum.xda-developers.com/general/xda-assist/1-year-problem-failed-remote-command-t3535310

Your device is corrupt. It can't be trusted and it will not boot

Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
C666PO said:
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
Click to expand...
Click to collapse
Yes,there are several unbrick tools on the forum i used this one and it worked for me!
I am not able to share links so im posting a few screew shots but if you google oneplus 7 pro unbrick you ahould find this thread easy
C666PO said:
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
Click to expand...
Click to collapse
I replied to you from the xda labs app and i couldnt attach a link but it works from the browser so i apologise for my first reply hope this one is more helpfull
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3934659/amp/

Pixel Bootloader Phone doesnt start

Hello all,
I have a Pixel1.
I was going to flash it and open the bootloader before. Everything prepared and plugged into the PC.
Via "fastboot reboot bootloader" I wanted to put the device into the bootloader to unlock it afterwards.
However, the device now does nothing.
Neither Power+Volume down does anything.
If I connect the device to the PC, the device is shown in the device manager as QUSB bulk.
Can anyone help me?
Letty said:
Hello all,
I have a Pixel1.
I was going to flash it and open the bootloader before. Everything prepared and plugged into the PC.
Via "fastboot reboot bootloader" I wanted to put the device into the bootloader to unlock it afterwards.
However, the device now does nothing.
Neither Power+Volume down does anything.
If I connect the device to the PC, the device is shown in the device manager as QUSB bulk.
Can anyone help me?
Click to expand...
Click to collapse
It's in emergency download mode (edl mode)
It may boot normally after battery dies.
If not you would need a blankflash for sailfish
I don't think there is one available for your device.
Edit: or mmcblk0.img for sailfish

Fastboot, Samsung Galaxy A51

Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?
M3DUS4 said:
Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?
Click to expand...
Click to collapse
this could be because the galaxy A51 wasnt built with fastboot, and the code to launch this option was just reused from a different device, or because something isnt connecting properly.
Hello, I have the same ... Android 11 (and currently 12) (from Frija). So it is not the fault of incorrect configuration or with connecting. Only something is wrong with this phone ...
I have this device and this solved it for me:
Enable OEM unlocking in developer settings
Shut down the phone
Hold volume up and volume down
Plug in a USB cable connected to a computer (the computer being turned on)
Keep holding
You're in download mode!
Side note: This might not work in USA or Canada, I am from europe and it works here. I have no idea if it works in another region. Also, you can't just flash a recovery.img on Samsung since there is no real "fastboot", you have to use download mode and Odin.
But I know how to enter download mode... Problem is Fastboot mode...
There is no fastboot mode on a modern Samsung device. If there is, it's fake and you cannot flash anything with it. As you can see even from Wikipedia, Odin is the Samsung replacement of fastboot.
So no fastboot, only download mode.
If a guide is saying to use fastboot, it is not compatible with Samsung.
If you would tell me why you specifically need fastboot, I'll be happy to tell you how you can do it with Odin, if possible.
Because I have Samsung Galaxy A51 5G (A516B) with new Android 12 and I can't do a root! Because I can't upload TWRP (custom recovery) because I haven't OEM unlock option in Deveoper Option. I tried trick with set back date by 7days but not succes. Everything I;ve metioned here - I did at my phone with Android 11.
And... I have read that I can turn this fu**ing OEM option by comend at ADB: fastboot oem unlock.
Phew ...
So this fastboot method is the last method to do a root with my phone.
Upload TWRP by Odin in download mode -ends red warning - of corse...
Have you any ideas?
I would be grateful for help...
I have read this fastboot method at:
How to Unlock Bootloader On Samsung Galaxy Phones [EASY GUIDE]
Are you looking for a Complete tutorial on How To Unlock Bootloader on Samsung Galaxy Phones? If yes, then you have come to the right place.
www.guidetoroot.com
Yeah, that guide is not relevant on any modern Samsung device. Besides, even if it was, which it isn't, you would first need to enable OEM unlocking from the Developer Settings.
But the fact that you don't have an option for OEM unlock is weird, since I have the exact same device model and it is there for me.
May I ask what is your region and is your phone locked to a telephone carrier?
My region is PLS - Poland. And not - phone is not locked. Have you the newest system Android 12?
Yes, I do. It's weird that there isn't even an option for you.
I'll try to come up with some new ideas if I have time...
I'll be glad for it...
Hej, do you have any idea?
stanwin said:
Hej, do you have any idea?
Click to expand...
Click to collapse
Have you tried everything listed here?
BloodyFruitDestroyer said:
Have you tried everything listed here?
Click to expand...
Click to collapse
Yes, I did. Evething exept the last one...
You could try it. It might be risky, but it's the only option I personally can come up with right now.
I've tried this option but Odin stuck on "files verification". Any help?
have any of you encountered this problem?
And how did you solve it?
You can also try searching for combination firmware for your device online

Categories

Resources