Linux Phones

3457 readers

37 users here now

The Discussion on Linux-based Phones.

Benefits:

Hardware freedom.
Perfect operating-system competition.
Full utilization of specs.
Phone lifespan raises to 10+ years.
Less e-waste.

Linux Mobile Distros:

Sailfish🇫🇮
FuriOS🇺🇸
Ubuntu Touch🇩🇪
Postmarket OS🇨🇭
Mobian
Pure OS🇺🇸
Plasma Mobile🇩🇪
LuneOS
openSUSE Mobile🇩🇪
Nemomobile
Droidian
Mobile NixOS
ExpidusOS
Maemo Leste
Manjaro Arm
Tizen
WebOS

Linux Mobile Hardware:

Jolla Phone🇫🇮
Shift Phone🇩🇪
FLX1🇺🇸
Fairphone 5🇳🇱
Volla Phone🇩🇪
Librem 5🇺🇸

⚙️Contribute

🧼Go Clean From the Duopoly:

💻Related Communities:

📰News:

💬Messager:

!matrix@programming.dev

⌚️Watch:

founded 2 years ago

MODERATORS

The used OnePlus 6 I bought is stuck on a black screen, detected as "Qualcomm CDMA Technologies MSM QUSB_BULK_CID:0402_SN:B48453B9" (sopuli.xyz)

submitted 1 month ago* (last edited 1 month ago) by sbeak@sopuli.xyz to c/linuxphones@lemmy.ca

9 comments fedilink hide all child comments

Holding down the power button, the power button + volume up, and the power button + both volume buttons does not do anything. What does "Qualcomm CDMA Technologies MSM QUSB_BULK_CID:0402_SN:B48453B9" mean?

I followed the guide using a prebuilt postmarketOS image (v25.12 w/ Phosh). I ran fastboot erase dtbo, fastboot flash boot (.img file), fastboot flash userdata (another .img file), and finally fastboot reboot. I saw a few Tux penguins in the corner and saw the postmarketOS logo. Then, the display turned off. After that, I rebooted in fastboot mode and retried the fastboot flash step and did fastboot reboot. Now my device seems to be unresponsive and appears as "Qualcomm CDMA Technologies MSM QUSB_BULK_CID:0402_SN:B48453B9" (in Android, it was seen as "OnePlus 6", while in fastboot mode, it was seen as "Google Android device")

Has anyone ran into this issue and know how to fix this?

edit: I did unlock the bootloader using "fastboot oem unlock" before flashing anything

you are viewing a single comment's thread
view the rest of the comments

[–] sbeak@sopuli.xyz 3 points 1 month ago (1 children)

I think it's because, after the black screen after the logo appears, I tried to reflash the boot image and used fastboit reboot again. Not sure why the device is in "EDL mode"

[–] hexagonwin@lemmy.today 3 points 1 month ago* (last edited 1 month ago)

i don't think the boot image (kernel+ramdisk) has anything to do with aboot (qualcomm lk bootloader), but my qualcomm/android knowledge is mostly stuck in ~2014 so i'm not sure about this. sorry. i can just recommend going to pmOS chatrooms or XDA forums..