suicidal_orange

The instructions worked fine once I fixed the snapshot thing, as above. Without knowing what your expectations are it's hard to say much more 🙃

Just in case anyone else hits this error when running flash_all.sh: Sending sparse 'userdata' 1/5 (765895 KB) OKAY [ 16.362s] Writing 'userdata' FAILED (remote: 'Flashing of userdata is not allowed in snapshotted state') fastboot: error: Command failed The fix is this fastboot snapshot-update cancel

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.

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

Glad you wrote this, I was considering trying it too but sounds a bit scary.

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.

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.

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".

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 🙃

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 ful

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 🙃

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 l

I've bought a Cubot King Kong Mini 2 and put Lineage on it - loving how small it is and with a weird keyboard (MessagEase) there are no downsides. Safe to say the Pro1 X will never be my daily phone even if it arrived tomorrow and I was lucky enough to have everything work perfectly. This message is as useful as their "update" so doesn't seem wrong to post it here 😞

Me too! Hopefully sometime this year 🤣

I'm sure the donation link works great, but does the work the donation is rewarding? Ducksoup and MrPib have installed it so that's a good start...