Installation of e/OS on CMF Phone 1

[aibd]

@eguy

export PATH=“$HOME/eguy/platform-tools:$PATH” ?

That would be wrong, loosely speaking you define your /home directory twice.

[eguy]

@aibd

That would be wrong, loosely speaking you define your /home directory twice.

I noticed there was already

export PATH=“$HOME/platform-tools:$PATH”

in the file

I had added the other with eguy but now have deleted it.

I’ll restart and

@aibd

Logout / login or restart the PC and try

fastboot --version
adb --version

OR, should I have only one instance of it?

I’ll restart and see while I await your reply

[eguy]

@aibd

eguy@antix112:~
$ adb --version
Android Debug Bridge version 1.0.41
Version 36.0.0-13206524
Installed as /home/eguy/platform-tools/adb
Running on Linux 6.1.105-antix.1-amd64-smp (x86_64)
eguy@antix112:~
$ fastboot --version
fastboot version 36.0.0-13206524
Installed as /home/eguy/platform-tools/fastboot
eguy@antix112:~

[aibd]

@eguy

OR, should I have only one instance of it?

Do not include a duplicate line. Perhaps check with ^F FIND that you have one correct line.

Inclusion in ~/.bashrc might not work on every machine. But let’s just try to fully know where we stand.

[eguy]

@aibd

Do not include a duplicate line. Perhaps check with ^F FIND that you have one correct line.

Inclusion in ~/bashrc might not work on every machine. But let’s just try to fully know where we stand.

One (the original that I think I put in previously while getting everything wrong!! ) has the # at the beginning of the line

# export PATH=“$HOME/platform-tools:$PATH”

the other, that I put in a couple of minutes ago from your instruction, does not

export PATH=“$HOME/platform-tools:$PATH”

but it seems to work? @aibd

which one should I remove? or leave it as is?

@aibd

I have a couple of things to do during the afternoon, so I will tend to defer to @piero if he is available to help at this time.

I’m off to bed now, so thank you both

peace

[aibd]

Congratulations you passed the stage where we know you have the “ADB console” the Terminal works predictably with adb and fastboot.

FYI. A hash at start of line causes the line to be disregarded.

Aside, example python

Comments starts with a #, and Python will ignore them:

#This is a comment
print("Hello, World!")

Comments can be placed at the end of a line, and Python will ignore the rest of the line:

print("Hello, World!") #This is a comment

So it could equally be deleted.

---

The next thing to do when you return is to check the device status.

Just to confirm, the phone is running Android just fine and USB debugging is enabled (as Requirements).

Start this session in home directory, I actually always start with

fastboot --version
fastboot devices

Then this becomes a permanent part of my notes. (All Terminal output is saved to a note in my Journal.)

Now run

fastboot oem device-info

fastboot flashing get_unlock_ability

and please send the whole output.

[eguy]

@aibd

Congratulations you passed the stage where we know you have the “ADB console” the Terminal works predictably with adb and fastboot.

thank you

@aibd

FYI. A hash at start of line causes the line to be disregarded.

Aside, example python

Comments starts with a #, and Python will ignore them:

#This is a comment
print("Hello, World!")

Comments can be placed at the end of a line, and Python will ignore the rest of the line:

print("Hello, World!") #This is a comment

So it could equally be deleted.

thank you.

@aibd

Start this session in home directory, I actually always start with

fastboot --version
fastboot devices

I presume with phone in fastboot mode? (which I did)

@aibd

Now run

fastboot oem device-info

terminal still ‘thinking’ and blinking after five or so minutes. No ‘result’ ‘reply’ output as yet.

Cleared command and tried

@aibd

fastboot flashing get_unlock_ability

Same, no output yet, only blinking cursor.

eguy@antix112:~
$ fastboot --version
fastboot version 36.0.0-13206524
Installed as /home/eguy/platform-tools/fastboot
eguy@antix112:~
$ fastboot devices
0011334AT003017 fastboot
eguy@antix112:~
$ fastboot oem device-info
eguy@antix112:~
$ fastboot flashing get_unlock_ability

also tried :

eguy@antix112:~
$ fastboot getvar all

blinking cursor, no output

what if I try:

fastboot flashing unlock first?

[aibd]

The phone must have no Google account no passwords, and no PIN screenlock, perhaps this could account for lack of reaction.

[eguy]

believe me, NO google account!

No passwords or PIN screenlock.

I looked around and tried this:

eguy@antix112:~
$ adb reboot bootloader

• daemon not running; starting now at tcp:5037
• daemon started successfully
  eguy@antix112:~
  $ fastboot oem device-info
  eguy@antix112:~ (I cancelled command after long wait)
  $ fastboot reboot
  Rebooting FAILED (Status read failed (No such device))
  fastboot: error: Command failed (I pulled the pin on phone so as to reboot manually as nothing was happening)
  eguy@antix112:~
  $

is it safe and ok to try this:

fastboot oem unlock

or

fastboot flashing unlock

[aibd]

Seems tetris also has this step, from developer options, enable OEM unlock

@eguy

$ adb reboot bootloader

Good to “cross check” but you missed

fastboot devices

after the change.

There is one more check to try on the phone, that USB preferences are set to file transfer.

We are trying at this stage only to collect information that it is safe to proceed.

As

fastboot oem device-info and fastboot flashing get_unlock_ability

[eguy]

eguy@antix112:~
$ adb reboot bootloader
eguy@antix112:~
$ fastboot devices
0011334AT003017 fastboot
eguy@antix112:~

$ fastboot flashing unlock
eguy@antix112:~
$ fastboot oem unlock
eguy@antix112:~
$

cancelled both.

@aibd

We are trying at this stage only to collect information that it is safe to proceed.

As

fastboot oem device-info and fastboot flashing get_unlock_ability

yes. I have been looking around here and there, specifically any quirks for CMF Phone1 but also not doing anything without your ‘permission’ and instruction.

Thank you.

(One of daughters has come for visit so I got waylaid for a while)

I’ll reboot and check the file transfer but everytime i do , it is still on file transfer.

@aibd yes file transfer ok.

[eguy]

I recall somewhere a suggestion to run in recovery mode and that ‘unlocks’ etc? Any thoughts?

[eguy]

@aibd

hallo again,

i keep wondering if I should downgrade to version 14 from 15.The Nothing CMF P1 does appear to have some ‘issues’.

I have some of the files and some info on it.

your thoughts, please?

I realise you have a life and might be busy and you can’t spend all your time helping me and I DO appreciate all the time you have given me. Thanks.

[aibd]

There is still one thing unconfirmed by you.The instructions include that within Developer options there is both USB debugging and OEM unlock.

Please can you confirm this is what you have seen and done?

Without seeing a response from

fastboot flashing get_unlock_ability

I do not like to send an unlock command on someone else’s phone. I will wait for a second opinion from @piero

Another command to try is

fastboot getvar all

This is expected a long output, but might possibly give a clue.

About downgrade, seems a last option to me.

Note, an oversight

The command fastboot oem unlock does not appear in fastboot --help I understand it does not work on Mediatek. tetris has Mediatek Dimensity 7300

[eguy]

@aibd

There is still one thing unconfirmed by you.The instructions include that within Developer options there is both USB debugging and OEM unlock.

Please can you confirm this is what you have seen and done?

yes. Checked often. Is it worth doing the revoke action again?

[aibd]

Switch off and back on again seems harmless.

[eguy]

@aibd

Another command to try is

fastboot getvar all

This is expected a long output, but might possibly give a clue.

no output

@aibd

Note, an oversight

The command fastboot oem unlock does not appear in fastboot --help I understand it does not work on Mediatek. tetris has Mediatek Dimensity 7300

I do not understand what that means. Do i need to? I am happy to trust your judgement and instruction.

NOTE

i tried this command and nothing came from it

$ fastboot reboot
Rebooting

[aibd]

@eguy

Do i need to?

It is simply a possible explanation for tetris not responding to that command.

@eguy I wonder if you ever did Factory reset? I assume you already backed up anything useful on the phone, so doing a Factory reset and observing if there is any resistance from the phone might be illuminating. Remember that Developer options > both USB debugging and OEM unlock have to be done again after Factory reset.

Review

The reason for my being over cautious goes back to Post #39 where you reported (and @piero noticed)

p.s. I did quickly run commands to check
$ fastboot flashing unlock
… OKAY [ 5.021s]
$ fastboot flashing unlock_critical
… OKAY [ 5.021s]

But it seems significant to me that you did not use the “Approve by button” from the

install page

• Ask for unlock with fastboot flashing unlock
• Approve with volume +
• Unlock critical with fastboot flashing unlock_critical
• Approve with volume +
• Reboot the device fastboot reboot
• The device proceeds with a factory reset

So I would really like to see some confirmation of the lock status before telling you to move to the assumed next stage of unlocking.

Are you able to see evidence on the device that it is locked?

[aibd]

@aibd

you did not use the “Approve by button” from the

You very kindly deleted another view of my “review”, thank you.

Do you understand my point that throwing two unlock commands without “Approve” is a simple “User error”? If that is definitely what you did, unconfirmed by you.

This would be a very simple explanation of failure of the launch script command. Lots of other things are to my mind not relevant. I think that this last little episode, now, is just about being over cautious.

[eguy]

sorry it’s not a clear picture