Hi. My eMMC has been bricked for quite a while - I can't get a keyboard to type in my password.  I'm finally getting around to wanting to boot that way again instead of continuing to use the software on my SD card.  I have found the following directions.  I have installed TowBoot and want to know if that will change anything.  Also, I assume that the OS I download to the SD card has to be prepared by Etcher or something like that, right? 

Here's what I found on the wiki:

1. Boot an operating system from the microSD card. If there is already a bootloader on the eMMC installed see the section Boot order to bypass it.
   
2. Download or copy the desired image to the microSD card as file
   
3. Check if the eMMC appears under
   
   Code:

   lsblk
   . If it doesn't appear in the output of the command, the eMMC wasn't initialized due to applying the above explained bypass method for a too long time during the boot
   
4. Important: Typically the image will be compressed in an archive file to reduce the download size (such as .gz or .xz). Extract the image from its archive file to get the file with the file extension .img.
   
5. Flash the image file using
   
   Code:

   sudo dd if=IMAGE.img of=/dev/mmcblk2 bs=1M status=progress conv=fsync
   (replace IMAGE.img with the filename of the image you want to flash and make sure it has the file extension .img).
   
6. Reboot the PinePhone Pro
   

Will this work with my incoming (not yet shipped, ordered yesterday), PBP?

https://www.amazon.com/gp/product/B07ZVK...UTF8&psc=1

Is it possible to add spi_flash ship to this board then use it to boot to usb? If so how?
if not why?

Has my Pinebook Pro camera broken, or has some update messed with the camera? Running Cheese immediately gives the error shown in the attached screen shot.

Attached Files

Thumbnail(s)
   

Is there any OS that is actually working and stable? I am going down the list installing every OS but there's always a problem to be found, some more than others but none of them work enough to make the device live up to it's name - the Pine "Phone".

If anyone has had any luck with an OS please let me know. I have installed more than half the available OS's and am on the precipice of giving up.

Thanks.

Hello, what are the main differences between megi's and sunxi64 kernels, what are the functionalities advantages, privacy and security trade-offs between them?
I've been using arch with megi's kernel and would like to know more about the possible privacy and security problems regarding the wifi firmware as described here: https://linmob.net/how-about-more-libre-...ath9k-htc/

My screen bottom side has loosed its tactile function (I don't know if it's a hardware screen issue or just a bad connection of the screen). But, meanwhile, I have a problem to start my mobile because the OK button, when decrypting the device at the starting process (my device is encrypted) is very hard to touch (I should try dozens of times). I wonder if I can set:

an inversion of top/bottom sides, at mobile start, or always (when I'm in the graphical screes, auto rotate help me, there is not a major issue)

"Cancel" the bottom last centimeter of the screen.

Are there any settings file where I can modify these parameters?

At Settings > Sound I have NO output or input device so I suppose my device sound is not available...

Hi guys,
  I am developing a board to use the Ox64 for a commercial application and while mapping out the planned pin usage and creating a KiCAD part I found a mismatch between the four documents I was referencing:

• PINE64_Ox64-Schematic-202221007.pdf from the wiki.
  
• PINE64_Ox64_placement-Bottom-202221007.pdf from the wiki.
  
• BL808_DS_en_1.1(open).pdf from the wiki.
  
• Ox64 Pin Assignments spreadsheet, probably from the original announcement blog.
  

1. Pin 4 on the schematic is labelled as GPIO12 but on the bottom placement is labelled as GP21.
   
2. Pin 5 on the schematic is labelled as GPIO13 but on the bottom placement is labelled as GP31.
   
3. Pin 6 on the schematic is labelled as GPIO41 but on the bottom placement is labelled as GP14.  There is no GPIO41 pin on the BL808C datasheet.
   
4. Pin 7 on the schematic is labelled as GPIO40 but on the bottom placement is labelled as GP4.  There is no GPIO40 pin on the BL808C datasheet.
   
5. Pin 12 on the schematic is labelled as GPIO20 but on the bottom placement is labelled as GP2.
   

1. Pin 4 is actually GPIO12.
   
2. Pin 5 is actually GPIO13.
   
3. Pin 6 is possibly GPIO5.  Low confidence in this guess.
   
4. Pin 7 is possibly GPIO4.  Low confidence in this guess.
   
5. Pin 12 is actually GPIO20.
   

- Qt6 efforts continues
- Greg Goncharov created some nice wireframes.
- @felixonmars is packaging Glacier to ArchLinux.
- some strange Qt bug
- Fosdem 2023 invitation

http://nemomobile.net/pages/nemomobile-i...mber-2022/