the battery that i’ve been mostly using has 99% charge and was able to hold a charge for 4-8 hours normally before i started trying this. i keep restarting in regular mode and it keeps showing 99%. Battery 2( charged to 66% ) is brand new has never been used before today. I’ll try booting that up normal, charging it and then trying to reflash when it’s at 99% next.
also tried on devuan ceres(13.0?) on different machine, same result
There are 2 way to put the phone on: Burn Mode.
One way as you described it above.
Second way is keeping the vol+ pressed before connect the cable, but the cable need to be connected on host first, have u tried the way?
I have given up on that method of reflashing.
Instead I use a micro-SD card with a clean L5 image burned onto it.
If you want help with that I can share step-by-step instructions
tried :
[getting to Searching… as per above]
unplug cable, unplug battery, plug battery, hold vol+, plug cable, release vol+
result: red light
unplug cable, hold vol+, plug cable, release vol+
result: red light
aha i do turn out to have a microsd card. actually i’d appreciate that.
guess i’ll need to acetone out the anti-interdiction glitter to get access to the sd slot . . . i’ll work on that.
does it have an sd card in it?
honestly i’m not sure i’ve gotta find some acetone and melt the nail polish to get access to it
You can open the disks app and see
looks like no
charged second battery to 97% and tried, no luck.
Red light means Burn Mode, second step it to do a: lsusb to confirm that L5 is on Burn Mode, it will say Nxp or something like that
nothing in lsusb or uuu -lsusb and nothing in kern.log or syslog indicating usb event
Given that you apparently have a working bootable phone … how about just connecting the normally booted phone to your host computer via USB and confirming that your host computer sees the phone at all (using lsusb)?
If the host can’t see the phone when the phone is in normal mode, I have my doubts that it is going to work when the phone is in serial download mode. (In other words, don’t worry about the Vulcan death grip and don’t worry about uuu / the flash script until the phone at least shows up when booted normally.)
FWIW, as my computer doesn’t have a USB-C port, I have never used serial download mode via the Purism-supplied USB-C to USB-C cable. Instead I have always used a USB 3.0 USB-A socket on the host computer with an Irvine-supplied cable that is USB-A M to USB-C M, and that has always worked for me. This also has the advantage of reducing the number of orientations for the USB-C plug(s).
neither lsusb on either {ubuntu, devuan} computers on {tried multiple cables/multiple usb plugs} can see anything
{although i’m getting an apparmor complaint in ubuntu computer’s logs about lsusb being denied, it displays all other usb devices plugged in shrug}
(phone does charge off said usb connection)
Have your tried the sd method?
still working on getting access to acetone to melt the anti-interdiction nail polish so i can get access to the sd plug
That could be relevant. USBGuard?
You realise that the µSD card goes in the SIM tray on the side? So you could never have used this as a mobile phone?? (OK, I admit that I have not used the Anti-Interdiction service, so I don’t know which things get covered in glitter polish.)
i have not