Yes, I have done all that and more, like using different wall outlet, holding upo to sky like Fabookers do when they can’t connect
Now, nothing happens. I can make a orange/red light appear for 30 seconds (your and my method), but that’s all it does. All I did was plug in the adapter and let it sit over night as usual.
Mmmm, I doubt it.
{Sidebar}
I wish I could say the same. I never had either phone. No needs for a cell, and enjoyed my privacy and wasn’t attached at the hip to any cell phone like most people. I have several desk/laptops and all private. No ads, no stalkers. Most business require a person use a cell. Our local transit is doing away with cash and join the tap-it group.
Desktops seem to be going the way of of the Dodo bird. Not many new laptops that can accept OS versions like Pure, Pop, Ubuntu and so on. Yeah, I know about Pop. Too bad. {/Sidebar}
I’ll wait a bit to see if any others respond. I have a feeling that repairs will be costly. Maybe there is a simple solution like Press the volume down while holding the start button and facing north sing ‘Hey Jude’ .
So so disappointed in this - this device. Help has been exceptionally great.
~s
For what it’s worth: Did you try to boot without the battery while being connected to a power supply?
This way we can exclude a defect battery causing your boot problems.
Leave power plugged in - remove battery and there is flashing orange, maybe red, blinking light.
Will not boot. Blinking light still blinks.
Since it’s off anyway, - removed power @ device, replaced battery.
Booted to green light and enter encrypt password stage and went blank
Blink stopped, screen went blank and light stays on but changed to orange.
From same position as #2 above, removed battery, light blinks orange. Won’t boot.
Replaced battery, orange light stays on.
Perhaps it is a very dead battery and just needs some time-out in the corner to pout or power-up. I’ll give it a hour and report back.
Thanks very much for the tip - it did something and booted - not enough juice maybe.
~s
UPDATE:
Continuing from Step 3 above:
Light went out but unsure how long it stayed on. Max time on might be 30 minutes.
No lights and device is not hot, not even warm as it usually is during charge.
Won’t boot. (Power plugged in, battery was in too.)
Removed battery, Light blinked orange.
Booted light flashed between green and red to encrypt, then through blocked to desktop.
Battery reads 0%.
Light blinks orange or red - hard to tell.
mobile and Wi-Fi work.
Replacing battery
Whew! It didn’t blow up. Desktop is visible.
Battery level now 88% Wow. that was a fast charge from o% to 88% in under 2 minutes. Not getting hopes up yet.
Going to remove power adapter:
Removed. - No more blinking light.
Desktop in tact… All is as it was.
Going to power down and boot again.
Powered Off OK.
Booted and made it to desktop.
Plugging in power adapter:
Desktop active re/orange light solid now.
Amazing, from 0% charge, to 88% in under 5 minutes and after plugging in power adapter, charge now reads 99%.
Now headed back to @amarok Post #16 w/ @irvinewade edits above and start over flashing the L5.
I still think it needs a exorcism.
My theory is, that at times, just moving the L5 slightly will turn screen black and moving it a bit screen returns. Ergo, possible it lost connection during flash process that released the internal Kraken.
I’ve renamed my L5 from Problem Child to Pandora’s Cell
pure1@pure-pc:~$ sudo apt install uuu
[sudo] password for pure1:
Reading package lists… Done
Building dependency tree
Reading state information… Done
uuu is already the newest version (1.2.91+0git6b465-0pureos+librem5.2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
pure1@pure-pc:~$
But before that even I wanted the output from which uuu
Looks older than what I have but, as you observe, there isn’t anything later for you to install.
As it happens, it doesn’t matter - because both switches are invalid. It’s just that uuu outputs its version before complaining about the invalid switch. You can use: uuu --anyoldrubbish as long as the switch is indeed invalid.
OK and thank you for filling in my knowledge gap about UUU’s cmd line switches. I could not find the --version switch but assumed you had knowledge of some hidden options.
I tried to read it but it TMI. I started to see things trying to understand it all.
At least, I hope it wasn’t Trump.
I have it back working now - so it seems.: this is what I think happened.
I just hit the power button to ‘sleep’ the phone and leave it sit on a heat sink. When I sat down last time, I may have moved the power supply cable a bit.
Over night, the power may have drained right out. When I tapped the power button to wake it, that is when I tried all kinds of things, probably too soon and was prepared to provide it with it’s last rights and hold services for it.
Now it is back to normal sitting on the heat sink with a slow-blinking blue light.
Have bottle of wine, some chocolate and legal something else - ready to go
~s
edited typo
Wait for Known USB Device Appear…
Error: Unknown Command:FB: reboot
2024-03-21 12:58:04,107 INFO Cleaning up.
Traceback (most recent call last):
File “./scripts/librem5-flash-image”, line 538, in
sys.exit(main())
File “./scripts/librem5-flash-image”, line 521, in main
flash_image(uuu_target, args.debug)
File “./scripts/librem5-flash-image”, line 351, in flash_image
subprocess.check_call([‘uuu’, uuu_target])
File “/usr/lib/python3.7/subprocess.py”, line 347, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘[‘uuu’, ‘./tmp_librem5-flash-image_u0hff3br/flash_librem5r4.lst’]’ returned non-zero exit status 255.
pure1@pure-pc:~/librem5-flash-image$
I hope I live long enough to see this to the end
~s
Really? I think I know. The script says
ERROR: Unknown Command:FB: reboot.
To me it means there is a commend to “reboot” and that command is not recognized by the script. So, IMO, the script needs some very serious intervention.
That “loose” cable is not confirmed. It’s only that at times, moving the phone, the screen has blinked off a few times, and froze before. I swapped out to another cable that hasn’t produce the same so far.
The part of of the Post 16 (Step x Step to flashing) that says
and then Step 5 sub part that says:
is where being a octopus would be handy, but it’s the only time the phone was moved and there was no screen blinking, script didn’t stop until the error. Actually, the script continued right after the error with:
2024-03-21 12:508:04,107 INFO Cleaning up…
@irvinewade
Summary:
Had nothing to do with the error. The error is caused by scrip readings command that wasn’t/isn’t there. So, there appears a need to fix that too. This is really over the top of annoying. But I can get 2048 score!