Finally looking at my Pro1x, getting nowhere

[suicidal_orange 103]

I received my Pro1x maybe a month ago, switched it on (eventually...) to confirm it works and put it back in the box.  Today I decided to try and play with it.  Tried to backup using adb as detailed here but before step 5 I saw a dead (sleeping?) robot in the middle of the screen.  So I tried to setup edl to use this guide instead but it wont install (log of the end of output attatched)  Tried to update my system in the hope of fixing that as it has been neglected for months and that failed too...  So back to adb.  Which is now broken with the error below

adb: error while loading shared libraries: libprotobuf.so.28.2.0: cannot open shared object file: No such file or directory

Any Arch Linux experts know where this file should have come from?  Thinking I will now be wiping my computer instead of the phone this weekend 😅

install.log

[claude0001 1,343]

On 10/4/2024 at 7:58 PM, suicidal_orange said:

adb: error while loading shared libraries: libprotobuf.so.28.2.0: cannot open shared object file: No such file or directory

https://archlinux.org/packages/extra/x86_64/protobuf/

?

[suicidal_orange 103]

2 hours ago, claude0001 said:

https://archlinux.org/packages/extra/x86_64/protobuf/

?

Thanks, reinstalled that but hasn't fixed adb.  I have tried lots to fix the computer but definitely need to reinstall.  Problem is I don't have anything installed to burn a dvd and my only USB stick died long ago while being used to record TV.  Installing Gentoo in a chroot will take while but might be my best option 🙃

[suicidal_orange 103]

Computer fixed, back to looking at this.

I now see that before I can backup using adb I need a recovery (suggested from Lineage) but there is a big warning to backup before flashing.  Even though 2 years on I see no mention of a successful method of restoring?  I'm sure this would have made sense many years ago when the Pro1x should have arrived but I've not done anything phone related for a long time so it is confusing.

Which is the correct thing to do?

1 - Flash something and forget the backup.  The phone is so old it will never be sold and I have no interest in carrying a full fledged Google tracker.

2 - Try to install edl while my computer is still blank so it doesn't matter if it breaks everything

3 - Flash something (that really should be mentioned in the FAQ) to get a recovery without damaging the partition that needs backing up

Edited October 11 by suicidal_orange

[Hook 3,034]

If you are on Stock, you do have a recovery.  When you get the dead robot you need one more step.  (This link is about the Pro 1, but I believe it is the same for the Pro1x-- not that I can test being on LOS 21)  Whether getting to recovery helps or not, I don't know, but there is a stock recovery already.

 

[Hook 3,034]

I found some old notes from when I tested my Pro1x for the 5 minutes it was on stock.  The above works but the only difference is that, for the Pro1x, holding volume down when booting takes you to the dead robot.  Then the procedure documented takes you to recovery.

[suicidal_orange 103]

Dead robot passed - thanks!

Now looking at recovery, looks just like Hook's screenshot:

Next should be step 5 - select advanced and enable ADB?

Tried choosing "Apply update from ADB" but

adb shell find /dev/block/platform -name “by-name” -exec ls -Al -Z –color {} \;
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: closed

"adb reboot recovery" did reboot the phone back to the dead robot 🙃

[Hook 3,034]

That instruction at step 5 sounds like it is referring to the LOS recovery. It looks like you have ADB able to interact with your phone. What do you get if you do "adb devices?"  Reboot into system (Stock Android) and issue the command "Adb devices"  if it comes back with something like "unauthorized". look on the Pro1x for a dialog box asking you to approve the connection.  Then "adb devices" should return an identifier for the Pro1x.  If so, adb is enabled.

Even with LOS, I rarely need that enable adb step for anything.  I only use it if I'm having trouble.  Most of the time I don't.

 

 

[suicidal_orange 103]

Thanks Hook.  adb devices works in stock but

adb shell find /dev/block/platform -name “by-name” -exec ls -Al -Z –color {} \;
find: -exec without \;

"adb reboot recovery" works.  Skip dead robot.  Then "adb devices" returns unauthorized.  Skip step 5 then.

adb shell find /dev/block/platform -name “by-name” -exec ls -Al -Z –color {} \;
error: closed

Probably because it is not authorised.  Chosing ADB sideload makes "adb devices" return "sideload", but as above the find thing still doesn't work.  Is "closed".

[suicidal_orange 103]

After some messing with AUR I managed to get EDL installed and have made the backups.

Anyone know if this applies to the Pro1x? (found in /e/os install guide)

Warning: Make sure that you can send and receive SMS and place and receive calls (also via WiFi and LTE, if available),
otherwise it will not work on /e/OS as well. Additionally, some devices require that VoLTE/VoWiFi be utilized once on 
stock to provision IMS.

 

[zegoo 13]

Hi. This warning is very important and is regarding many phones in fact. Your provider has to populate your phone with IMS files on first try as i know. If you don't verify if VoWifi and VoLTE are working fine from stock, you could not get this working well after flashing a new rom. That's already happened to me ☹️ many times.

[suicidal_orange 103]

Interesting!  Used both SIM slots just to be safe.

Got annoyed by the constant network traffic (google unstoppable updates...) before i managed to get VoWifi to do anything but never used it anyway, so no big loss if it doesn't work.

[EskeRahn 5,464]

(you can switch off google's automatic waste of bandwidth aka 'updates', though it is hidden deep in setting in the app, and by default is turned on - I guess the purpose is so stealing our data is less obvious among the constant traffic.... Oh and note even when you switch it off they turn it on themselves, so you have to do it repeatedly - bloody crooks...)

[zegoo 13]

In case of ... To solve issues regarding IMS populating, PIXEL IMS apk could be use to setup/recover IMS configuration. It worked for me to set VoWiFi on my Sony XZ1C under LOS 20.

[suicidal_orange 103]

I just followed this guide this guide including ColdCamel's addition to flash stock android without GMS.  On restarting it said it failed and offered a factory reset which I did that as there was nothing on my Pro1x.  When it rebooted the loading screen was still /e/os, as is the setup wizard.  I tried to go through the wizard to get back in and re-enable adb to try flashing again but can't get past location services screen - when I press next I see the screen about the keyboard briefly (in a dark theme which I was using before 🙃) then it goes back to location.  I tapped quickly hoping to hit "next" on keyboard screen as it is in the same place but after a few seconds of trying the phone restarted, and suggested a factory reset...

Rebooted to recovery, flashed again, no change.

Help?!

Edited Saturday at 12:31 AM by suicidal_orange

[suicidal_orange 103]

Flashed Droidian, it got as far as

I: Flashing data/userdata.img
Sending sparse 'userdata' 1/5 (765895 KB)          OKAY [ 16.361s]
Writing 'userdata'                                 FAILED (remote: 'Flashing of userdata is not allowed in snapshotted state')
fastboot: error: Command failed

Unsurprisingly it didn't boot but it did replace the startup screen with a beautiful green one!

Tried stock without GMS again and the fxtec logo bootscreen is back.  And there was no startup wizard!  There is a google search box on the homescreen though so this is not an acceptable ROM for me.