Trouble Installing on Oneplus One (Solved)

Edward Wilhelm · 4 Dec 2020, 19:16

@Lakotaubp

okay ran:

sudo apt update and sudo apt-get install commands from above again

then:

adb devices
List of devices attached

daemon not running; starting now at tcp:5037
daemon started successfully
******** device

next ran sudo fastboot OEM unlock
it returned that it was waiting for any device

then I ran the installer and it returned:
fastboot: usage: unknown command OEM

Edward Wilhelm · 12 Apr 2020, 19:18

Does anyone have a liveboot OS that has everything needed to run install out of the box?

Lakotaubp · 12 Apr 2020, 19:20

@Edward-Wilhelm Sorry. Put your device in fastboot then run in terminal sudo fastboot oem unlock

Edward Wilhelm · 12 Apr 2020, 19:22

@Lakotaubp
It still returned:
fastboot: usage: unknown command OEM

Lakotaubp · 12 Apr 2020, 19:24

@Edward-Wilhelm Have you tried a few usb cables and ports

Lakotaubp · 12 Apr 2020, 19:29

And I guess fastboot devices still returns the same error as before.

Rondarius · 12 Apr 2020, 19:34

what happens if you write oem instead of OEM?

Edward Wilhelm · 12 Apr 2020, 19:37

@Rondarius
It returns:
< waiting for any device >

and then waits for a response

Edward Wilhelm · 12 Apr 2020, 19:50

@Lakotaubp
I have now tried two different cables in two different ports

Lakotaubp · 4 Dec 2020, 20:09

@Edward-Wilhelm What needs sorting is the udev rules. That link that came up after your error message shows you how. It's something I have never done I must admit.

http://developer.android.com/tools/device.html

Edward Wilhelm · 12 Apr 2020, 20:57

@Lakotaubp
Okay. My brother let me use his computer that is running pop os. I installed snap, fastboot, the ubuntu installer from within snap etc. I ran the installation on the phone and everything appeared to be working. It prompted me in the gui to run unblock oem which I did. The phone went through several different screens including loading 142 of something, and an android graphic that said erasing. It rebooted itself a couple times. The phone screen is now black, but a light on the front of the phone is flashing various colours. The installer says "flashing firmware...". It has been stuck like this for a while now. Do you think the installation process is working? How long should it stay like this?

Edward Wilhelm · 12 Apr 2020, 21:42

I rebooted the phone and it is now stuck on a screen saying
"powered by ubuntu
supported by ubports"
What do I do?

Edward Wilhelm · 12 Apr 2020, 21:54

If you guys could help me get this phone working I would be more than happy to make a donation and I would be ever grateful. I know that you all are not doing this to get rich. I have now spent many many hours trying to get this to work, and now I have nothing to show for this, except a broken phone.

Lakotaubp · 13 Apr 2020, 07:19

@Edward-Wilhelm Looks like your getting somewhere at last. Let me catch up a bit and will see what we can do. Your nearly there now. Normally restarting the installer does the trick from here and choose the wipe option. As long as the installer is showing pushing files all is ok.If not just check adb devices still detects the device for me please.

Edward Wilhelm · 13 Apr 2020, 14:16

@Lakotaubp
The device is no longer recognized by the computer.

Also big thanks to @Lakotaubp and @Keneda for all the help so far. You have been awesome.

Lakotaubp · 13 Apr 2020, 14:36

@Edward-Wilhelm Is that on your Mint or your brothers pop one. Not sure why that happened.

Edward Wilhelm · 13 Apr 2020, 14:37

@Lakotaubp
Pop os with the snap version of the installer

Lakotaubp · 13 Apr 2020, 14:39

@Edward-Wilhelm and you installed both ADB and fastboot on the pop one? Can you double check that. T

Edward Wilhelm · 13 Apr 2020, 14:43

@Lakotaubp
I did this:

sudo apt update
sudo apt-get install android-tools-adb android-tools-fastboot

Then you type

adb devices

Edward Wilhelm · 13 Apr 2020, 14:53

@Lakotaubp
running adb devices gives:
List of devices attached

daemon not running; starting now at tcp:5037
daemon started successfully