I have taken the L5 out of the box after 3 mothns. I run all updates from Purism store. Then it asked me to restart the phone so I did. When it shutdown it didn’t turn back on. So I pressed the power button to turn it back on and green LED lit up and it vibrated for quarter of a second. Nothing comes up on the screen. And then green light comes on and phone vibrates again. It is completely stuck in this process.
I have tried taking the battery out and also plugging in the charger but nothing helps. I have emails purism support about this problem 1 week ago and didn’t get any response.
Is there anything I can do or is the phone completely kaput?
I have taken the battery out again and this time I get Green, Orange light and then vibration. And then it just keep repeating the process. Still nothing on the screen.
After power then green/orange light, wait five seconds. If you don’t see anything, the phone has almost certainly booted OK, but has not lit the screen.
Hold power button down five seconds, then release.
Go back to 1.
You may have to repeat this a number of times before the screen lights up. Doing this in a dark room can help you see if the screen is lit before it actually displays anything. This also helps if you had the screen brightness very low before restart.
but it doesn’t seem to be doing anything. At stage 4 after I re-insert the battery while keep holding the Volume UP button and then releasing the Volume Up button the script keeps saying “Searching…” for 30mins now. Nothing is happening.
Yes but uuu has to be an adequate version. (In the middle of my one and only reflash, reflashing from amber to byzantium, uuu crapped out because uuu was too old. Easy fix. No drama.)
And the Python script may have (has?) Python package dependencies.
Are you using a Debian family distro? non-Debian family distro? or PureOS Live Boot? (Strongly recommended to avoid the second of those three options.)
Regardless, if you use the lsusb command on the host computer after you put the phone in Serial Download mode connected to the host computer via USB do you see
Bus 999 Device 999: ID 1fc9:012b NXP Semiconductors i.MX 8M Dual/8M QuadLite/8M Quad Serial Downloader
?
(Bus number and device number will differ from what I have shown.)
That will at least tell you whether what you are doing with the phone has worked - and should fault isolate a mass of random variation including: USB port version and type, USB cable and cable type, USB cable orientation.
NB: No need to run any scripts at this stage. If you don’t see the above then no relevant script will ever work - so if you don’t see the above then that’s what you need to tackle first.
Ok, I have tried again and this time I used USB-C to C cable that came with the phone and the flashling finally worked. Although the official guide says to use USB-A to C which didn’t work for me.
Family-wise, that is fine. I should have mentioned also that it has to be a reasonably up-to-date release of your distro of choice.
That’s the magical procedure in the instructions that starts with …
Press and hold the **Volume Up** button while performing the following actions:
I think the official guide may go beyond the strict requirements. It would surely work if you use the Purism-supplied USB-C to USB-C cable.
I personally have only ever used USB-A to USB-C because I have no USB-C port on my host computer and that has always worked. (I use a cable that came with a portable disk that has a USB-C interface. So that cable may be no good for charging a battery but obviously is required at least to provide basic power e.g. 500 mA and obviously provides data, otherwise it wouldn’t be much good as a cable for a portable disk.)
An advantage of USB-A to USB-C over USB-C to USB-C is that the former only has two orientations while the latter has four. Of course if all USB-C-related stuff on the planet were standards-compliant then the orientation wouldn’t matter. Unfortunately in the real world …
In any case, the instructions do or did say that if you are having problems getting the phone connected to your host computer (never mind about flashing anything) then try different USB ports / cables / orientations etc.
That sounds overly complicated. I guess there’s a compatibility issue there somewhere.