The titel already says it

Android with the 5.10 kernel

Googletv (from adt3 source)

rooted

multiple markets for apps

HDR, 4K etc etc...

Based on PixelPropsUtils, GamesProps will spoof the device needed to unlock the FPS of the following games:
* Free Fire - Spoof Asus ROG Phone 1 will unlock 90 FPS
* COD Mobile - Spoof Xperia 5 || will unlock 120 FPS (only on multiplayer mode)
* PUBG Mobile - Spoof OnePlus 8 Pro will unlock 90 FPS
* Wild Rift - Spoof OnePlus 8 Pro will unlock 120 FPS
* Cyber Hunter - Spoof OnePlus 8 Pro will unlock 90 FPS
* Fortnite - Spoof OnePlus 8 Pro will unlock 90 FPS

https://drive.google.com/file/d/12L2KvIo...share_link

I have a Pine Phone that isn't usable.  The MicroSD card reader isn't working and I messed up MANJARO that came preinstalled so now, when I turn on the phone, it's stuck at the loading screen (the K with the gear) and nothing else happens.

Anyone know how to get into this thing? 

At my disposal I have: an HP laptop running Windows 11, a Nokia N900 (with an generally unusable microUSB port) running Maemo, the Pine Phone keyboard (last I tried it wasn't being recognized by the phone because I've not applied a shim to the keyboard so it makes better contact with POGO pins), two MicroSD cards.  Any suggestions are appreciated. 

My current thought: use SSH to get into the device and flash eMMC with a different OS. Windows 11 has a built in SSH protocol.  Is this possible?

I would like to install box86 on Manjaro in an armv7h Arch chroot (not Debian) without qemu and binfmt. I tried following https://forum.armbian.com/topic/16584-in...-on-arm64/, but that didn't work. Any suggestions?

Hi,
   I have a rockpro64 v2.1 (2018-07-02) and use Armbian system. 
   In my local test, rockpro64 needs about 36seconds before start kernel. And the 5G device connected with the PCIE slot would be power on at that time.
   The 5G device would obey PBL->SBL->Kernel start progress. And the PCI driver would detect 5G device at 3.5 second after host kernel start even if the 5G device still in PBL stage. This would lead to the true VID/PID of PCIE device are not enumerated because device has difference VID/PID between PBL and Kernel stage.

    For reference, USB interface would be power on during about 10seconds. So could we ajust the power on time slot for PCIE slot to avoid above issue?

Recently bought my pinephone and have been testing various OS options.  I love the hardware switches but didn't want to have to remove the back.  As you can see, my solution also provides access to the SD card.

Trying to install slackwareaarch64 on pinebook pro, following well documented video and web page, I have installed slackwareaarch64 on 3 rockpro64 successfully. This is one of the newer(?) PBP will itty bitty emmc switch.

Installed slackware u-boot, this boots but cannot find slackware installer on sd card in sd card slot.

dmesg shows

Quote:[ 3026.994975] mmc1: Skipping voltage switch
[ 3027.001231] mmc1: error -5 whilst initialising SD card
[ 3027.024964] mmc_host mmc1: Bus speed (slot 0) = 300000Hz (slot req 300000Hz, actual 300000HZ div = 0)
[ 3027.062065] mmc_host mmc1: Bus speed (slot 0) = 200000Hz (slot req 200000Hz, actual 200000HZ div = 0)
[ 3027.101480] mmc_host mmc1: Bus speed (slot 0) = 100000Hz (slot req 100000Hz, actual 100000HZ div = 0)
[ 3027.434979] dwmmc_rockchip fe320000.mmc: Unexpected CMD11 timeout

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)