Eos installer: Device (FP6) is found but doesn't upload

/e/OS Devices Fairphone
, , ,
22

If you had booted into Fastboot mode your phone can respond to

fastboot devices

but not to adb devices

adb and fastboot are different languages.

The documentation image shows different to your actions.

23

yes,

adb commands only works when device is booted into “recovery” mode or into “normal system” mode
when
fastboot commands only works when the device is booted in “bootloader / fastboot” mode

24

Okay, Thanks for explaining. So my screenshot didn’t say so much (except that the cable (A to C data cable) cannot be the problem because then the “offline” device would not be seen. Still the problem remains:

grafik

does not show any entry, no matter in which mode. And I’m still “feeling” that the message “DEVICE STATE locked” on the phone’s screen might have a reason and could be a hint. Any comments about that?

25

the bootloader is still locked because you are not abble to use fastboot commands to unlock it..
please follow the linked guide to install windows fastboot drivers to be abble to use fastboot commands !
Eos installer: Device (FP6) is found but doesn't upload - #19 by piero

26

Hello again, sorry, currently I’m really frustrated. The last problem probably was because I had not rebooted my computer and thus the updates which I had done were not activated. Yes, stupid, but when working on a job like this (“blind”) you are like in a tunnel.

Anyway, today I could unlock the bootloader and start the script. Unfortunately I received an error message:

grafik
grafik585×445 20.8 KB

whetever “Too many links” might mean. The script tells me to take the battery out before trying it again. Great idea: I need a TX5 driver for that (Thank you, Fairphone!) which I don’t have - there are several TX driver sets in my possession but they all start with TX10. WTF! I tried it without taking the battery out but fastboot devices brings no entry and the script says:

grafik
grafik463×179 3.57 KB

Please, can you tell me what went wrong? Yes, I will go shopping for a TX5 driver but that can take some time, I live in the country not a city, perhaps I’ll have to buy it online.

27

Hello
First forget about the TX-5 and simply reboot the phone using the buttons or fastboot reboot
And also forget about adb commands they are not usefull for today’s job

Please share the return of the bootloader status commands.

fastboot oem device-info

fastboot flashing get_unlock_ability
28

Those sort of messages are seen from time to time. The battery removal is somewhat “worst case” but in this situation the phone can be quite unstable. As above just get the phone back to stable Fastboot mode by the simplest means.

Why did it happen. First look at the whole USB chain. It has been reported that certain USB will not carry fastboot commands. You will need a good quality (full capacity) data cable, so not a thin, skinny cable. Avoid USB hubs including any USB hub that might be hidden in the PC / laptop; for best results check, if necessary with a manual, that you are connecting to a USB-2 port soldered to the motherboard.

Mingw-w64 might be an issue (??)

Does your PC have plenty of RAM to hold the image while processing? Personal view this sort of flashing job may be hard work for many home PCs. If you try again perhaps ensure no other programs are running except perhaps a simple monitor (in case this reveals anything topping out).

29

Thanks, both say and don’t come back before I use Ctrl-C.

30

so have a look there

31

I simply tried it again after a longer period. The results look better:

grafik
grafik456×203 6.15 KB

1 Like
32

Excuse me, I don’t want to be the smartbrain. Still I don’t think the cable can be the problem, because everything worked up to one step in the middle. I have a USB hub but am using a direct plug because I really did read the hints. I cannot use a plug from the backside because the cable isn’t very long. My computer is a this year’s model with loads of memory. I’ll simply try again now.

1 Like
33

Now I get:

grafik
grafik517×134 5.49 KB

However, the phone itself in the fastboot screen says DEVICE STATE - unlocked

34

no FRP lock by a connected Gogol account through the FairphoneOS ?

35

Sorry, I don’t get that. Can you please ask the same for a dummy?

36

i simply asked if you had ever configured a Gogol account on the device, it is still connected, it can leads to complications

37

I don’t even know what a Gogol account is - no, surely not. What is a FRP lock?

38

Factory Reset Protection :
if a Gogol account is registred on the phone
reinitialisation attempt of the phone leads to a unusable phone

39

Now I understand what you mean with “Gogol”. Maybe that’s normal for you but I didn’t understand it. I looked up about FRP now. My phone is brandnew but had Android installed. This probably doesn’t mean it has a “Gogol” account. I didn’t apply for one but had to install some “Gogol” software (Android Studio) on my PC - not my phone! - because some misleading information on the web told me I had to do that to install the “platform tools”. That was wrong and unintended but should not affect the phone. I hope!

1 Like
40

Missing further information, today I tried it again - hope springs eternal. Unfortunately I cannot proceed, in the best case I end up with:

grafik
grafik556×259 7.73 KB

Does anyone know what “Too many links” could mean? Can anyone give me a hint how to find out whether there is a FRP lock (which I don’t believe because there was no “Gogol” account on the phine)? Any helpful ideas? Thanks a lot!

41

Are you sure your cable (USB-A to USB-C), the USB-Port and the installed drivers for adb, fastboot and or recovery are fine?