Related
⚠ This project is no longer maintained. See below. ⚠
You are encouraged to migrate to the official nightly builds (huge thanks to @anishpratheepan and to the LOS team for bringing that up). If you update from an unofficial build, it is highly recommended that you opt-in for build signature check after the flash:
Open Settings
Privacy => Trust
Check "Build signature" at the very bottom
Note that you should be able to update from unofficial to official builds seamlessly, without wiping anything.
-----
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Unlock your bootloader
Backup everything, especially the "persist" partition
Make sure you're on a recent version of OxygenOS.
Download the latest build
Run the following commands:
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot fastboot
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot reboot recovery
Wipe all data from recovery.
(Optional) If you need GApps, NikGApps Core are known to work ("Apply update" => "Update from ADB", and then run adb sideload <NikGapps-xxx-arm64-11-yyy.zip>). Note that other variants than Core can crash.
Reboot.
Downloads:
https://drive.google.com/drive/folders/1V17qsn_wMpwPgJHMhCjfYYmZEPGzPvP2
Known issues:
Displays "Charging slowly" when it's actually not
Build signed with public keys for now
Reporting Bugs:
Make sure the bug you want to report isn't already known
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][instantnoodle][11] LineageOS 18.1, ROM for the OnePlus 8
Contributors
KennyG9, LuK1337
Source Code:
Since February 2021 (based on the official LineageOS device tree):
Device tree: https://github.com/LineageOS/android_device_oneplus_instantnoodle
Kernel: https://github.com/LineageOS/android_kernel_oneplus_sm8250
Proprietary blobs: https://github.com/TheMuppets/proprietary_vendor_oneplus
Before February 2021 (based on LuK1337's work on instantnoodlep with minor adjustments to the device tree):
Device tree: https://gitlab.com/nlr/android_device_oneplus_instantnoodle
Kernel: https://github.com/luk1337/android_kernel_oneplus_sm8250
Proprietary blobs: https://github.com/luk1337/proprietary_vendor_oneplus
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2021-01-07
Last Updated 2021-02-10
Very cool. Stoked. Can you add link for gapps as I know lineage needs to work properly.
mattie_49 said:
Very cool. Stoked. Can you add link for gapps as I know lineage needs to work properly.
Click to expand...
Click to collapse
I don't have GApps myself and I don't want to flash them on my personal device. I'm fine with adding a link in the original post provided that one or two person can confirm it works and provide instructions. I think NikGApps are the best candidate.
KennyG9 said:
I don't have GApps myself and I don't want to flash them on my personal device. I'm fine with adding a link in the original post provided that one or two person can confirm it works and provide instructions. I think NiksGApps are the best candidate.
Click to expand...
Click to collapse
Fair enough. Thank you for bringing this to the op8 community.
I made an attempt to bundle OpenGApps into the build: https://drive.google.com/file/d/1edechrEwpX5L5SjE6OlsAjRckT-UF69t/view (using https://github.com/opengapps/aosp_build). It bootlooped on my device but I suspect that's because it requires a factory reset which I didn't want to do. Flashing instructions are identical, just make sure you have flashed OOS 11 at some point. If that happens to work for some of you, I'll try to publish both flavors with every release.
KennyG9 said:
I made an attempt to bundle OpenGApps into the build: https://drive.google.com/file/d/1edechrEwpX5L5SjE6OlsAjRckT-UF69t/view (using https://github.com/opengapps/aosp_build). It bootlooped on my device but I suspect that's because it requires a factory reset which I didn't want to do. Flashing instructions are identical, just make sure you have flashed OOS 11 at some point. If that happens to work for some of you, I'll try to publish both flavors with every release.
Click to expand...
Click to collapse
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?
mobile_sensei said:
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?
Click to expand...
Click to collapse
LOS builds only contain a few subset of all the partitions that exist on the OP8 (system, boot, product, dtbo, and some others). The OP8 also contains a lot of other proprietary partitions (ABL, AOP, bluetooth, modem, etc…) that only the manufacturer is able to provide updates for. As far as I understand, those blobs must also be updated to be able to run Android 11 without issues. If you don't update them, it'll likely bootloop or refuse to boot and it's not recommended anyways.
I'm not sure upgrading from 17.1 to 18.1 without wiping is even possible, but if you want to give it a shot, I think your best bet is to extract all the proprietary images from a recent OOS build, then flash them and flash LOS 18.1 over that. You may avoid the annoying MSM step, but my bet is that you'll have to wipe anyways if you want to boot, so I strongly advise that your backup all your data and apps before. In deeper details, you need to :
- get a recent and official OOS 11 build from here : https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300
- extract the payload.bin from the image using a tool like this one : https://github.com/LineageOS/scripts/blob/master/update-payload-extractor/extract.py
- reboot to bootloader (adb reboot bootloader)
- flash the stock recovery you just extracted (fastboot flash recovery recovery.img)
- reboot into stock fastboot (fastboot reboot fastboot)
- flash all the blobs you just extracted (fastboot flash abl abl.img && fastboot flash aop aop.img && fastboot flash bluetooth bluetooth.img && ………)
- follow LOS 18.1 flashing instructions from the first post
mobile_sensei said:
"Flash OOS 11 at some point"
What about upgrading from 17.1 ?
Also - Why no OOS 10 - 18.1?
Click to expand...
Click to collapse
Yes I agree here.
I and need step by step exact instructions how to flash any rom here.
I am not even gonna try to flash this rom because I know my device is gonna end up at the Qualcomm dump mode.
I can't get anything booted if I flash anything coming from OOS11, don't ask because I have no idea why.
The only way to get my device booting stock rom at this point is to flash stock rom in EDL mode with the msm tool
[OP8][OOS 21AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
My device is OnePlus 8 5G - 12GB/256GB Interstellar Glow- Firmware : Firmware: OxygenOS - GE / EN / FR / ES
IN2010
Inspected 2020.06.18
As TWRP isn't working completely is there way to do the equivalent full system backup with all partitions without TWRP perhaps via fastboot? Because I know I'm not gonna be able to flash a rom its gonna be the same story over and over again setting up the same stock rom over again ..it gets old.
Because custom software for OnePlus 8 is not at the stage of flash and forget I think a unified toolkit in a zip is needed.
It can be separate or bundled with each rom release and regularly updated that I can extract and cd into, and run the fastboot commands from to help making flashing roms and debug as accurate as we possibly can starting with all of us using the same exact toolkit to begin with.
Driver used
Developer framework ie fastboot, adb executable
Payload dumper
Readme File
Bat/sh file for automation
perhaps payload/img files
bundled with rom Gapps with dev, flavor and release because this seem to be subject to not booting
This would make sure everyone is 100% following the same exact instructions making debugging much easier, in this case it seem like gapps one piece of the puzzle possibly preventing rom from booting, in my case I'm can't even make it to square one getting stuck at Qualcomm dump mode..
Spoiler
KennyG9 said:
LOS builds only contain a few subset of all the partitions that exist on the OP8 (system, boot, product, dtbo, and some others). The OP8 also contains a lot of other proprietary partitions (ABL, AOP, bluetooth, modem, etc…) that only the manufacturer is able to provide updates for. As far as I understand, those blobs must also be updated to be able to run Android 11 without issues. If you don't update them, it'll likely bootloop or refuse to boot and it's not recommended anyways. I'm not sure upgrading from 17.1 to 18.1 without wiping is even possible, but if you want to give it a shot, I think your best bet is to extract all the proprietary images from a recent OOS build, then flash them and flash LOS 18.1 over that. You may avoid the annoying MSM step, but my bet is that you'll have to wipe anyways if you want to boot, so I strongly advise that your backup all your data and apps before. In deeper details, you need to : - get a recent and official OOS 11 build from here : https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300 - extract the payload.bin from the image using a tool like this one : https://github.com/LineageOS/scripts/blob/master/update-payload-extractor/extract.py - reboot to bootloader (adb reboot bootloader) - flash the stock recovery you just extracted (fastboot flash recovery recovery.img) - reboot into stock fastboot (fastboot reboot fastboot) - flash all the blobs you just extracted (fastboot flash abl abl.img && fastboot flash aop aop.img && fastboot flash bluetooth bluetooth.img && ………) - follow LOS 18.1 flashing instructions from the first post
Click to expand...
Click to collapse
Good information, I didn't finish my reply during breakfast and noticed you wrote one more.
The only thing I am not comfortable with is that there are links to tools that I have to download from the internet.
Its one factor subject to being sourced from random google searches.
Like the fastboot binary from xda although old doesn't work on op8, I found out the hard way and I am now downloading this directly from Android developer page.
But a lot of headache could be eliminated trying to figure out where and which binaries should be used, what work and what does not.
Is fastboot/adb bundle too old or driver not installed?
Did all of us follow the exact same installation steps in detail the rom developer did?
I hope you understand.
This device has been the most problematic I've ever dealt with
SUPERUSER said:
Yes I agree here.
I and need step by step exact instructions how to flash any rom here.
I am not even gonna try to flash this rom because I know my device is gonna end up at the Qualcomm dump mode.
I can't get anything booted if I flash anything coming from OOS11, don't ask because I have no idea why.
The only way to get my device booting stock rom at this point is to flash stock rom in EDL mode with the msm tool
[OP8][OOS 21AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
My device is OnePlus 8 5G - 12GB/256GB Interstellar Glow- Firmware : Firmware: OxygenOS - GE / EN / FR / ES
IN2010
Inspected 2020.06.18
As TWRP isn't working completely is there way to do the equivalent full system backup with all partitions without TWRP perhaps via fastboot? Because I know I'm not gonna be able to flash a rom its gonna be the same story over and over again setting up the same stock rom over again ..it gets old.
Because custom software for OnePlus 8 is not at the stage of flash and forget I think a unified toolkit in a zip is needed.
It can be separate or bundled with each rom release and regularly updated that I can extract and cd into, and run the fastboot commands from to help making flashing roms and debug as accurate as we possibly can starting with all of us using the same exact toolkit to begin with.
Driver used
Developer framework ie fastboot, adb executable
Payload dumper
Readme File
Bat/sh file for automation
perhaps payload/img files
bundled with rom Gapps with dev, flavor and release because this seem to be subject to not booting
This would make sure everyone is 100% following the same exact instructions making debugging much easier, in this case it seem like gapps one piece of the puzzle possibly preventing rom from booting, in my case I'm can't even make it to square one getting stuck at Qualcomm dump mode..
Good information, I didn't finish my reply during breakfast and noticed you wrote one more.
The only thing I am not comfortable with is that there are links to tools that I have to download from the internet.
Its one factor subject to being sourced from random google searches.
Like the fastboot binary from xda although old doesn't work on op8, I found out the hard way and I am now downloading this directly from Android developer page.
But a lot of headache could be eliminated trying to figure out where and which binaries should be used, what work and what does not.
Is fastboot/adb bundle too old or driver not installed?
Did all of us follow the exact same installation steps in detail the rom developer did?
I hope you understand.
This device has been the most problematic I've ever dealt with
Click to expand...
Click to collapse
I don't have a definitive answer to everything, but here are some remarks:
- Not sure what exactly your problems were and I'm unaware of any way to backup partitions using fastboot unfortunately. As far as I know, it was not possible to restore nandroid backups using mauronofrio's TWRP on Android 10 either. I think the best you can achieve for now is software and data backup (using "adb pull" and "OAndBackup+" or something else). I can also attest that I had way more weird partitioning issues when using TWRP than LOS' fastboot. Since I stopped using TWRP, I never had to use MSM again.
- What you may attempt to reduce the risk of bricking your device is to take advantage of the A/B partitioning. You can flash everything on the unused slot and switch back to the working slot if anything goes wrong. This can be done by running "fastboot getvar current-slot" to get the current slot, then "fastboot --set-active=a" to switch to slot a (or "fastboot --set-active=b" to switch to slot b, depending on which slot was active).
- I second your reluctance on using tools coming from untrusted sources. Please, don't get fastboot/adb from XDA, use the official Android builds. I can't help you regarding the drivers as I use Linux which ships with drivers, but if you use Windows try to get those drivers from either Microsoft, OnePlus or Qualcomm directly. My instructions to avoid flashing Android 11 with MSM makes you use an official image from OnePlus (which you have to trust anyways) + an open-source tool that's made by LOS developers (which you have to trust anyways). At this point, I think the weakest point of trust if you don't want to build LOS yourself is me.
- Regardless of what you attempt, always make sure you have backups of your valuable data, apps and persist partition. Especially given how capricious this device is .
working great so far. any way to re-enable the 90Hz refresh rate?
edit: found it in display options!
LuK1337 said:
OP8 is no longer supported so RIP.
Click to expand...
Click to collapse
New flash method for both 8p and 8t does not allow to use it on instantnoodle, migrated yesterday from there to this build and it's working perfect with NikGapps-core and Magisk, great job @KennyG9
any way to get the OP camera app working? tried several versions available on APKMirror, but all seem to crash. maybe there are some dependencies?
Does OnePlus 8 tmobile version work with dual sim on this rom?
veridiam said:
any way to get the OP camera app working? tried several versions available on APKMirror, but all seem to crash. maybe there are some dependencies?
Click to expand...
Click to collapse
There's a lot of proprietary software/firmware (apart from the camera apk itself) that its not included in LOS. There have been some ports in the past (e.g. OnePlus6 OOS Camera port or oxy-ify) but all of them seem dead, maybe because google camera port working out of the box.
Creating a magisk module should be doable, but you need to start the app, let it crash and add the missing dep N times until you have all of them
@LuK1337 , please accept pull request: https://github.com/luk1337/android_kernel_oneplus_sm8250/pull/1
Running great. I would mention that only nikgapps core works. The rest for me ended in a crash whilst setting up.
passion8059 said:
Running great. I would mention that only nikgapps core works. The rest for me ended in a crash whilst setting up.
Click to expand...
Click to collapse
Thanks, just updated first post to mention that.
KennyG9 said:
Thanks, just updated first post to mention that.
Click to expand...
Click to collapse
Would you be able to look into face unlock? Handy feature for me especially at work.
passion8059 said:
Would you be able to look into face unlock? Handy feature for me especially at work.
Click to expand...
Click to collapse
Face unlock is an OxygenOS feature and I don't think AOSP or LineageOS supports something like that officially as it's quite terrible security-wise. GApps also dropped support for face unlock in Android 10 because of security concerns. So unless I'm missing something it probably won't happen anytime soon unless through some third-party module, sorry. It's not just about porting some blobs, it's a whole new OS feature.
Is WiFi calling and LTE calling working?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Follow the instructions here
Downloads:
Builds: d1, d2s, d2x
GApps: https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_exynos9820
Requirements:
Any Q or R based firmware installed on your device.
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk
Magisk
As this ROM has a working ramdisk sideloading the magisk apk is enough, just as it is
on every other device, no bootimage with magisk included or installing to recovery is needed!
Features
SELinux enforcing
AES-256-XTS FBE encryption
Latest Linux 4.14.x kernel
All cameras are working
Ramdisk is working
Dolby atmos is working
Known issues
VoLTE/VoWiFi
You tell me
This may be a silly question but what distinguishes this from Ivan's Lineage OS 18.1 Rom?
[ROM][Signature Spoofing]LineageOS 18.1 for Note10+ 5G/Note10+/Note10 Exynos
Awesome
forum.xda-developers.com
KiwiNote+ said:
This may be a silly question but what distinguishes this from Ivan's Lineage OS 18.1 Rom?
[ROM][Signature Spoofing]LineageOS 18.1 for Note10+ 5G/Note10+/Note10 Exynos
Awesome
forum.xda-developers.com
Click to expand...
Click to collapse
The main differences are these:
- It's open source
- SELinux is enforcing
- File based encryption on /data
- Merged upstream 4.14.x kernel
- It has a ramdisk (which makes installing e.g magisk a lot easier)
Hello,
Stuck at boot screen.
after side-loading the zip as well as MindTheGapps (x64 version).
Mind you I also added FDroid because I wasn't sure if it's included. Was that bad?
files used were:
"lineage-18.1-20210611-recovery-beyond0lte.img" (of course renamed and .tar'ed flashed with odin)
"lineage-18.1-20210611-UNOFFICIAL-beyond0lte.zip"
"MindTheGapps-11.0.0-arm64-20210412_124247.zip"
"F-Droid.apk" (most recent version)
I have attached a pic of the boot screen just do be clear what I mean. Pressing "vol down + power" does reboot(cannot even turn it off) however neither "vol up + bixby" nor "vol down + bixby" has any effect so I cannot access the phone via heimdall, odin, ADB or fastboot.
are there any options left to try or do I own a shiny new paperweight?`
any help is appreciated.
PL
PortentousLad said:
Hello,
Stuck at boot screen.
after side-loading the zip as well as MindTheGapps (x64 version).
Mind you I also added FDroid because I wasn't sure if it's included. Was that bad?
files used were:
"lineage-18.1-20210611-recovery-beyond0lte.img" (of course renamed and .tar'ed flashed with odin)
"lineage-18.1-20210611-UNOFFICIAL-beyond0lte.zip"
"MindTheGapps-11.0.0-arm64-20210412_124247.zip"
"F-Droid.apk" (most recent version)
I have attached a pic of the boot screen just do be clear what I mean. Pressing "vol down + power" does reboot(cannot even turn it off) however neither "vol up + bixby" nor "vol down + bixby" has any effect so I cannot access the phone via heimdall, odin, ADB or fastboot.
are there any options left to try or do I own a shiny new paperweight?`
any help is appreciated.
PL
Click to expand...
Click to collapse
First, you posted this in the wrong thread, this one is meant for Note10 series, the one for S10 series is over here:
[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
Could you please provide more information on your issue?
Like which firmware version were you on before flashing the ROM etc,
Also I don't quite understand why you list F-Droid.apk in used files, that's not something you sideload in recovery, so it booted up before I guess?
Also if BL splash is still shown I'm quite sure you can still enter DL mode ... just keep in mind your phone needs to be connected to a PC in order for it to work (force reboot and immediately press and hold combination for DL mode while it's connected to a PC)
Linux4 said:
First, you posted this in the wrong thread, this one is meant for Note10 series, the one for S10 series is over here:
[ROM][UNOFFICIAL][RAMDISK][11] LineageOS 18.1 for Galaxy S10e/S10/S10+/S10 5G Exynos
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
Click to expand...
Click to collapse
...Well that explains it I guess.
Linux4 said:
Could you please provide more information on your issue?
Like which firmware version were you on before flashing the ROM etc,
Click to expand...
Click to collapse
yeah... the wrong one.
Linux4 said:
Also I don't quite understand why you list F-Droid.apk in used files, that's not something you sideload in recovery, so it booted up before I guess?
Click to expand...
Click to collapse
that was me being more stupid and no I did not try to boot before.
Linux4 said:
Also if BL splash is still shown I'm quite sure you can still enter DL mode ... just keep in mind your phone needs to be connected to a PC in order for it to work (force reboot and immediately press and hold combination for DL mode while it's connected to a PC)
Click to expand...
Click to collapse
that does nothing. I'll keep trying a bit before I move one.
Thanks for your quick response anyway.
I did the installation by sideload (ROM + Gapps) but when "trying to boot" the device returns to the DL screen.
even restarting to exit the DL screen, the device insists on returning to it.
Galaxy Note 10 (D1)
stenncell said:
I did the installation by sideload (ROM + Gapps) but when "trying to boot" the device returns to the DL screen.
even restarting to exit the DL screen, the device insists on returning to it.
Galaxy Note 10 (D1)
Click to expand...
Click to collapse
Could you please provide more information?
Like I'm pretty sure you get some error message on DL mode screen
As you're actually the first one trying this on d1 (only found a tester for d2s before) you might want to PM me and/or join my telegram group for further debugging if needed
Linux4 said:
Could you please provide more information?
Like I'm pretty sure you get some error message on DL mode screen
As you're actually the first one trying this on d1 (only found a tester for d2s before) you might want to PM me and/or join my telegram group for further debugging if needed
Click to expand...
Click to collapse
i joined the telegram group... i will try to install again.
Linux4 said:
The main differences are these:
- It's open source
- SELinux is enforcing
- File based encryption on /data
- Merged upstream 4.14.x kernel
- It has a ramdisk (which makes installing e.g magisk a lot easier)
Click to expand...
Click to collapse
Thanks for providing the ROM! Does it support signature spoofing?
tempe222 said:
Thanks for providing the ROM! Does it support signature spoofing?
Click to expand...
Click to collapse
I don't include out-of-tree patches, sorry
However in my S10 Series thread there's another solution for this one
Anyways, read the OP, download links are taken down temporarily as some users apparently had problems with getting it to boot
Will be up again next week hopefully (will get a device myself by that time)
Fixed builds are now up
Hi I am new here, I have two questions:
1. Installing using twrp is: just wipe internal storage and install file?
2. Why zipfile from Ivan's version is like ~1,2gb and this .bin file is only ~700MB?
Donkey666 said:
Hi I am new here, I have two questions:
1. Installing using twrp is: just wipe internal storage and install file?
2. Why zipfile from Ivan's version is like ~1,2gb and this .bin file is only ~700MB?
Click to expand...
Click to collapse
1. Do not use TWRP (read the instructions in post #2!) it will eventually corrupt your data when using encryption which we do here
Use lineage recovery instead
2. I only have the proprietary blobs from stock that are *actually needed* probably it's different in ivan's ROM
Also it's a zip too idk why you say it's a ".bin"
Linux4 said:
1. Do not use TWRP (read the instructions in post #2!) it will eventually corrupt your data when using encryption which we do here
Use lineage recovery instead
2. I only have the proprietary blobs from stock that are *actually needed* probably it's different in ivan's ROM
Also it's a zip too idk why you say it's a ".bin"
Click to expand...
Click to collapse
@Linux4
I managed to install your version, its more stable than ivans version so thank you man great job, on ivans version had microphone issues and telephoto2x did not work, this one feels very good and probably usable as a daily driver phone..
I have a question for you, is there a way to add option in settings that blocks notification&quick-access-tiles from being accessed from locked screen?
And S-pen question: is there a way to make keyboard appear when I tap whit S-pen on txt field (it puts cursor there but keyboard does not apper until I tap there with finger.)
@Linux4
I notice S-pen issue, aside from seeing this icon when hovering over clickable button there are scrolling issues, something like one in four attemps fails to regognize gesture, you can open gsmarena.com a try scrolling there and it is very unrelialable and often instead of scroll it taps on some link over there, I tried ivans version and this issue wasnt there, (the hand logo also wasnt there) so maybe you can somehow take S-pen module from him, probably after that this build will be 99.9% complete
Donkey666 said:
View attachment 5367685
@Linux4
I notice S-pen issue, aside from seeing this icon when hovering over clickable button there are scrolling issues, something like one in four attemps fails to regognize gesture, you can open gsmarena.com a try scrolling there and it is very unrelialable and often instead of scroll it taps on some link over there, I tried ivans version and this issue wasnt there, (the hand logo also wasnt there) so maybe you can somehow take S-pen module from him, probably after that this build will be 99.9% complete
Click to expand...
Click to collapse
You know that both this and the other keyboard thing aren't even really device specific issues (actually rather stylus specific, it's the same on another device with SPen I have)?
It's just that AOSP doesn't have good support for these pens, they're basically handled like a mouse
Scrolling is fine for me on my own device tho and I do not get that hand icon (which is due to it being a "mouse") on the post reply button (tho in some other places I do get it)
I'm going to mess with that stuff in the future maybe
Linux4 said:
You know that both this and the other keyboard thing aren't even really device specific issues (actually rather stylus specific, it's the same on another device with SPen I have)?
It's just that AOSP doesn't have good support for these pens, they're basically handled like a mouse
Scrolling is fine for me on my own device tho and I do not get that hand icon (which is due to it being a "mouse") on the post reply button (tho in some other places I do get it)
I'm going to mess with that stuff in the future maybe
Click to expand...
Click to collapse
Yea you are right, I did pay closer attention to S-pen behavior and you are right, it is basicaly a mouse.. And issue solved, had magnetic case and that messed up S-pen behavior..
Hello I think that I accidentally bricked my phone.
I wanted to install LineageOS and followed this tutorial in order to install twrp:
Root Twrp Install Xiaomi Redmi 6 Redmi 6A Miui 11 Android 9 Pie.zip
drive.google.com
I only used this tutorial to install twrp.
The tutorial looks weird but it worked good. I need to say that i didn't manage to install anything with this twrp.
I wanted to install LineageOS from this tutorial:
LineageOS-17.1 For Xiaomi Redmi 6/6A [cereus/cactus][ABANDONED]
LineageOS-17.1 (STABLE)
samarv-121.github.io
I cleared the data, cache, system according to the tutorial.
I wanted to flash the new os but then the twrp said that this phone is "cactus" not "cereus" and the corner of the phone showed 6A, I noticed this only now.
But I think that my phone is cereus (My phone is Xiaomi Redmi 6) so I concluded that twrp must be wrong and went to obtain another twrp from this tutorial:
[RECOVERY][UNOFFICIAL] TWRP for Xiaomi Redmi 6 (cereus) by TWRPBuilder
TWRP Recovery 3.2.3-0 For Xiaomi Redmi 6 (cereus) by TWRPBuilder #include /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed...
forum.xda-developers.com
According to this post twrp can "flash itself": https://android.stackexchange.com/questions/175153/how-to-update-twrp-from-within-twrp
So I believed it and attempted to flash it. I then proceeded to "Boot into Recovery".
TWRP warned me that the device has no system, if I want to proceed, and this is my biggest failure, I pressed yes.
Now the phone has black screen and it keeps vibrating for roughly 20 seconds, than it abruptly stops for a second and then continues to vibrate again and loops in this behavior.
I tried connecting it to pc, no change
I tried pressing and holding power, no change
I tried holding power button and volume up, the device seems to be longer in "no vibration phase", nothing else noticed
I tried holding power button and volume down, device doesn't seem to react
I tried holding all buttons, device seems to be longer in "no vibration phase"
I might have tried the combinations wrong, I remember that pressing some combinations caused the device to be briefly recognized by computer, but I can't find that combination now.
So I am stuck with possibly bricked phone with no OS and possibly no recovery.
Do you know anything that could help me? I really want to repair this phone, if only for the sake of repairing it and restoring confidence in my abilities. The sounds of it vibrating slowly drives me mad.
Thanks in advance for your time and for any tips and responses!
I recognized this pattern.
If I press
volume up + power
or
volume up + volume down + power
then
device gets briefly recognized by windows, then gets disconnected and resumes anomalous cycle.
yellowfoxstaris said:
Hello I think that I accidentally bricked my phone.
I wanted to install LineageOS and followed this tutorial in order to install twrp:
Root Twrp Install Xiaomi Redmi 6 Redmi 6A Miui 11 Android 9 Pie.zip
drive.google.com
I only used this tutorial to install twrp.
The tutorial looks weird but it worked good. I need to say that i didn't manage to install anything with this twrp.
I wanted to install LineageOS from this tutorial:
LineageOS-17.1 For Xiaomi Redmi 6/6A [cereus/cactus][ABANDONED]
LineageOS-17.1 (STABLE)
samarv-121.github.io
I cleared the data, cache, system according to the tutorial.
I wanted to flash the new os but then the twrp said that this phone is "cactus" not "cereus" and the corner of the phone showed 6A, I noticed this only now.
But I think that my phone is cereus (My phone is Xiaomi Redmi 6) so I concluded that twrp must be wrong and went to obtain another twrp from this tutorial:
[RECOVERY][UNOFFICIAL] TWRP for Xiaomi Redmi 6 (cereus) by TWRPBuilder
TWRP Recovery 3.2.3-0 For Xiaomi Redmi 6 (cereus) by TWRPBuilder #include /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed...
forum.xda-developers.com
According to this post twrp can "flash itself": https://android.stackexchange.com/questions/175153/how-to-update-twrp-from-within-twrp
So I believed it and attempted to flash it. I then proceeded to "Boot into Recovery".
TWRP warned me that the device has no system, if I want to proceed, and this is my biggest failure, I pressed yes.
Now the phone has black screen and it keeps vibrating for roughly 20 seconds, than it abruptly stops for a second and then continues to vibrate again and loops in this behavior.
I tried connecting it to pc, no change
I tried pressing and holding power, no change
I tried holding power button and volume up, the device seems to be longer in "no vibration phase", nothing else noticed
I tried holding power button and volume down, device doesn't seem to react
I tried holding all buttons, device seems to be longer in "no vibration phase"
I might have tried the combinations wrong, I remember that pressing some combinations caused the device to be briefly recognized by computer, but I can't find that combination now.
So I am stuck with possibly bricked phone with no OS and possibly no recovery.
Do you know anything that could help me? I really want to repair this phone, if only for the sake of repairing it and restoring confidence in my abilities. The sounds of it vibrating slowly drives me mad.
Thanks in advance for your time and for any tips and responses!
Click to expand...
Click to collapse
Try flashing stock firmware using mi flash tool for your device
yellowfoxstaris said:
But I think that my phone is cereus (My phone is Xiaomi Redmi 6) so I concluded that twrp must be wrong
Click to expand...
Click to collapse
Why do you think you are right? How confident are you with this?
TWRP detect phone model and prevent flashing different ROMs for different model.
It read out your phone code: cactus, and you accuse it wrong. Base on what?
The 2 phone looks similar, but the camera on the back looks different.
Look here for comparation:
https://www.gsmarena.com/compare.php3?idPhone1=9237&idPhone2=9217#diff-
Take a photo of the phone back, especially the camera module and post it here, so people can see which phone it is.
First get to fastboot mode.
If you cannot, then find Xiaomi repair center to help you.
Redmi 6 (Cerus) forum:
https://forum.xda-developers.com/c/xiaomi-redmi-6.7874/
Redmi 6A (Cactus) forum:
https://forum.xda-developers.com/c/xiaomi-redmi-6a.7881/
Okay, I managed to open the back of phone and disconnect battery.
After this phone stopped to vibrate and seemed to be turned off.
If turned on normally or attempted to access recovery, the phone resumed the anomalous state.
While turned off I pressed volume down and power then fastboot screen emerged.
I downloaded latest TWRP from official website, at the time of writing current version was 3.5.2
TeamWin - TWRP
This is the Team Win website and the official home of TWRP! Here you will find the list of officially supported devices and instructions for installing TWRP on those devices.
twrp.me
TWRP 3.5.2 Released
TWRP 3.5.2 is out now for most currently supported devices.
twrp.me
I managed to flash it and boot into recovery.
Currently fastboot and recovery are accessible.
I will notify if I manage to flash system and resume full functionality.
=======================================
pl1992aw said:
Why do you think you are right? How confident are you with this?
Click to expand...
Click to collapse
I am like 60% sure. The site I bought the from phone states it is Redmi 6 (it is as reliable site as it can get). I will attempt to flash custom ROM for Redmi 6.
yellowfoxstaris said:
Okay, I managed to open the back of phone and disconnect battery.
After this phone stopped to vibrate and seemed to be turned off.
If turned on normally or attempted to access recovery, the phone resumed the anomalous state.
While turned off I pressed volume down and power then fastboot screen emerged.
I downloaded latest TWRP from official website, at the time of writing current version was 3.5.2
TeamWin - TWRP
This is the Team Win website and the official home of TWRP! Here you will find the list of officially supported devices and instructions for installing TWRP on those devices.
twrp.me
TWRP 3.5.2 Released
TWRP 3.5.2 is out now for most currently supported devices.
twrp.me
I managed to flash it and boot into recovery.
Currently fastboot and recovery are accessible.
I will notify if I manage to flash system and resume full functionality.
=======================================
I am like 60% sure. The site I bought the from phone states it is Redmi 6 (it is as reliable site as it can get). I will attempt to flash custom ROM for Redmi 6.
Click to expand...
Click to collapse
Don't flash yet.
Use
XiaomiADBFastbootTools (Java)
https://github.com/Szaki/XiaomiADBFastbootTools
It need java se, follow his instruction.
During fastboot, plug the phone to PC, PC need to have internet connected.
Then start the XiaomiADBFastbootTools.
It will show you what model it is with the code name it read from the system.
Like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then go to the correct forum and use the correct TWRP.
You may manage to install official TWRP, but it may not work properly when flashing.
pl1992aw said:
Don't flash yet.
Use
XiaomiADBFastbootTools (Java)
https://github.com/Szaki/XiaomiADBFastbootTools
It need java se, follow his instruction.
During fastboot, plug the phone to PC, PC need to have internet connected.
Then start the XiaomiADBFastbootTools.
It will show you what model it is with the code name it read from the system.
Like this
Then go to the correct forum and use the correct TWRP.
You may manage to install official TWRP, but it may not work properly when flashing.
Click to expand...
Click to collapse
Thank you, I will attempt to identify the model right away.
It seems it is indeed Redmi 6.
Should I keep this TWRP:
TWRP 3.5.2 Released
TWRP 3.5.2 is out now for most currently supported devices.
twrp.me
or should I try to find another one?
Also my endgame with this device is...
Since I am already neck deep in flashing left and right, I would like to:
* install twrp or similar recovery tool
* install custom OS, preferably open source (currently I have might sights on LineageOS)
* root the result
I do not ask of you to be helped in this endeavor, I just think it is appropriate to know this in order to understand the whole picture and how I got into this in the first place.
yellowfoxstaris said:
View attachment 5347499
It seems it is indeed Redmi 6.
Should I keep this TWRP:
TWRP 3.5.2 Released
TWRP 3.5.2 is out now for most currently supported devices.
twrp.me
or should I try to find another one?
Also my endgame with this device is...
Since I am already neck deep in flashing left and right, I would like to:
* install twrp or similar recovery tool
* install custom OS, preferably open source (currently I have might sights on LineageOS)
* root the result
I do not ask of you to be helped in this endeavor, I just think it is appropriate to know this in order to understand the whole picture and how I got into this in the first place.
Click to expand...
Click to collapse
You can try:
Xiaomi Redmi 6
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
It is listed in the official site.
First read the custom OS firmware requirement. Flash the official ROM of the firmware requirement, to prevent system corruption. (Or if there's Xiaomi.eu ROM alternatively) Boot to MIUI once to check if it's fine to boot up.
If you have success MIUI, then you can think to use custom ROMs.
Go here to look for ROMs:
Xiaomi Redmi 6 ROMs, Kernels, Recoveries, & Other
Improve your Xiaomi Redmi 6's battery life, performance, and look by rooting it and installing a custom ROM, kernel, and more.
forum.xda-developers.com
Thanks for all the advices! I will slowly work my way through them.
I managed to flash a clean official ROM. The phone booted and works as expected.
It's different ROM Firmware than required, but it's calming to know, that I can restore the device to "default state".
I will now attempt to flash LineageOS via this tutorial:
[ROM][UNOFFICIAL] Lineage OS 17.1
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from...
forum.xda-developers.com
Okay, I managed to get my phone back in a working order.
I will sum up here what happened and what I did for future generations.
Symptom: Phone is Xiaomi Redmi 6. (this tutorial might work for another models, but I will presume that you have this phone) Phone has black screen and vibrates for cca 20 seconds then stops and vibrates again.
Background: If you tried flashing your phone and you got into this state, don't panik, you can still save it!
Prerequisites:
Flashing of your phone is unlocked.
Your computer has ADB and Fastboot Drivers.
If you broke your phone via flashing, you most likely have those two checked. If not, please find another tutorials to get into this state.
I will now write tutorial, each step is labeled by a number, if needed I will write some short comment for each step.
1. Follow this tutorial and open back of your phone.
2. Disconnect your battery. (You don't need to unglue your battery in order to do so!)
(Now your phone shouldn't vibrate and should be turned off, take a breather, you don't need to listen to the vibrations anymore, from this state, you can access fastboot, but we need to prepare a few more tools. In theory you can close phone now, but I would recommend to do it after the phone is in fully working order.)
3. Download Xiaomi ADB/Fastboot Tools.
GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot - GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
github.com
4. Follow the tutorial on the github to install Java JRE.
GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot - GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
github.com
5. On your phone hold VOLUME DOWN + POWER. (Your phone should boot to Fastboot screen.)
6. Turn on Xiaomi ADB/Fastboot Tools and connect phone to computer.
7. Verify which architecture you have and download appropriate official ROM. (You can download it from Xiaomi Tools!)
8. Unpack the downloaded ROM (I had to unpack it twice).
9. Click select ROM folder in Xiaomi tools and select folder which you unpacked. (It should contain sh files, bat files, py files and folder "images")
10. Flash ROM.
Now if everything goes well, congratulations, you may pat yourself on the back, your phone should now work as it worked before. Whatever you did before, please be more careful this time.
I will now describe what I continued to do.
Follow optional steps ONLY if you want to install LineageOS.
I am including following steps only because I want to complete steps for what I did. If you wanted only to recover your phone, you are good to go.
I originally followed this tutorial:
[ROM][UNOFFICIAL] Lineage OS 17.1
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from...
forum.xda-developers.com
OPTIONAL STEPS:
(you have been warned)
1. Download OriginalROM
Download Redmi 6 (cereus) V11.0.4.0.PCGMIXM MIUI 11 Stable Full Rom | XiaomiROM.com
The Stable update V11.0.4.0.PCGMIXM has been officially released for Redmi 6 (codename is cereus). Before updating, please make sure you have …
xiaomirom.com
2. Download LineageOS from previously stated tutorial.
3. Download TWRP.
Download TWRP for cereus
Download TWRP Open Recovery for cereus
eu.dl.twrp.me
4. Download Magisk.
Release Magisk v21.4 · topjohnwu/Magisk
Update: v21.4 adds more regression hot fixes. Happy 2021! v21.3 adds a workaround for devices with buggy F2FS Linux kernel drivers. This F2FS bug may cause bootloops on many devices. Checkout the f...
github.com
5. Download Open GApps.
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
(so far you basically followed previously mentioned tutorial)
(from now on, I had to deviate from tutorial a little bit)
6. Depending if you are on the Windows/Linux/Else edit appropriate files in Original Rom which are named (Flash All, etc) so they don't contain "fastboot reboot" (this will be found to the end of file).
6. Via Xiaomi tools, flash Original ROM.
7. Reboot from Fastboot to Fastboot.
8. Flash TWRP.
9. Boot into recovery.
10. Connect phone and copy LinageOS, Magisk and GApps.
11. Flash LinageOS, Magisk and GApps (I did it in this order, I don't know, if it makes difference.)
12. Enjoy your phone.
For me, if I flashed rom without editing the files, the phone booted and user data were created, and then TWRP was unable to flash them. You can probably get around this via wiping out user data or another way.
I hope that this helped you and good luck with flashing!
Thanks to:
pl1992aw and Austinredstoner for getting me out of this mess
EinTim32 for creating the original tutorial
Szaki for Xiaomi tools
TWRP, Magisk and LineageOS developers for creating amazing software!
yellowfoxstaris said:
Okay, I managed to get my phone back in a working order.
I will sum up here what happened and what I did for future generations.
Symptom: Phone is Xiaomi Redmi 6. (this tutorial might work for another models, but I will presume that you have this phone) Phone has black screen and vibrates for cca 20 seconds then stops and vibrates again.
Background: If you tried flashing your phone and you got into this state, don't panik, you can still save it!
Prerequisites:
Flashing of your phone is unlocked.
Your computer has ADB and Fastboot Drivers.
If you broke your phone via flashing, you most likely have those two checked. If not, please find another tutorials to get into this state.
I will now write tutorial, each step is labeled by a number, if needed I will write some short comment for each step.
1. Follow this tutorial and open back of your phone.
2. Disconnect your battery. (You don't need to unglue your battery in order to do so!)
(Now your phone shouldn't vibrate and should be turned off, take a breather, you don't need to listen to the vibrations anymore, from this state, you can access fastboot, but we need to prepare a few more tools. In theory you can close phone now, but I would recommend to do it after the phone is in fully working order.)
3. Download Xiaomi ADB/Fastboot Tools.
GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot - GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
github.com
4. Follow the tutorial on the github to install Java JRE.
GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot - GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
github.com
5. On your phone hold VOLUME DOWN + POWER. (Your phone should boot to Fastboot screen.)
6. Turn on Xiaomi ADB/Fastboot Tools and connect phone to computer.
7. Verify which architecture you have and download appropriate official ROM. (You can download it from Xiaomi Tools!)
8. Unpack the downloaded ROM (I had to unpack it twice).
9. Click select ROM folder in Xiaomi tools and select folder which you unpacked. (It should contain sh files, bat files, py files and folder "images")
10. Flash ROM.
Now if everything goes well, congratulations, you may pat yourself on the back, your phone should now work as it worked before. Whatever you did before, please be more careful this time.
I will now describe what I continued to do.
Follow optional steps ONLY if you want to install LineageOS.
I am including following steps only because I want to complete steps for what I did. If you wanted only to recover your phone, you are good to go.
I originally followed this tutorial:
[ROM][UNOFFICIAL] Lineage OS 17.1
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from...
forum.xda-developers.com
OPTIONAL STEPS:
(you have been warned)
1. Download OriginalROM
Download Redmi 6 (cereus) V11.0.4.0.PCGMIXM MIUI 11 Stable Full Rom | XiaomiROM.com
The Stable update V11.0.4.0.PCGMIXM has been officially released for Redmi 6 (codename is cereus). Before updating, please make sure you have …
xiaomirom.com
2. Download LineageOS from previously stated tutorial.
3. Download TWRP.
Download TWRP for cereus
Download TWRP Open Recovery for cereus
eu.dl.twrp.me
4. Download Magisk.
Release Magisk v21.4 · topjohnwu/Magisk
Update: v21.4 adds more regression hot fixes. Happy 2021! v21.3 adds a workaround for devices with buggy F2FS Linux kernel drivers. This F2FS bug may cause bootloops on many devices. Checkout the f...
github.com
5. Download Open GApps.
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
(so far you basically followed previously mentioned tutorial)
(from now on, I had to deviate from tutorial a little bit)
6. Depending if you are on the Windows/Linux/Else edit appropriate files in Original Rom which are named (Flash All, etc) so they don't contain "fastboot reboot" (this will be found to the end of file).
6. Via Xiaomi tools, flash Original ROM.
7. Reboot from Fastboot to Fastboot.
8. Flash TWRP.
9. Boot into recovery.
10. Connect phone and copy LinageOS, Magisk and GApps.
11. Flash LinageOS, Magisk and GApps (I did it in this order, I don't know, if it makes difference.)
12. Enjoy your phone.
For me, if I flashed rom without editing the files, the phone booted and user data were created, and then TWRP was unable to flash them. You can probably get around this via wiping out user data or another way.
I hope that this helped you and good luck with flashing!
Thanks to:
pl1992aw and Austinredstoner for getting me out of this mess
EinTim32 for creating the original tutorial
Szaki for Xiaomi tools
TWRP, Magisk and LineageOS developers for creating amazing software!
Click to expand...
Click to collapse
I dont know if it booted to fastboot cause no display only vibrate every 20 seconds . And when i charge it, no show of icon of battery.
Problem solve.. thanks !!
Yuhuu!
Try this up guys:
Fix HardBrick Redmi 6A (no recovery and no fastboot, only black screen)Fix without need Authotization stuff
----------------------------------------------------------------------- Finally I could fix my redmi 6A after suffering hardbrick. I couldnot enter to recovery neither to fastboot mode. My redmi 6A just give me a black screen with vibration on...
forum.xda-developers.com
ligodligerem said:
Problem solve.. thanks !!
Click to expand...
Click to collapse
How did you get into fastboot? I got the same problem and can't get into fastboot. Only vibrates spontaneously each 20s.
watch this.. it solved my problem. and dont miss any instruction so that u got 100% of recovering your phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lenovo Tab3 8 Tablet
Models: TB3-850F/M
TWRP 3.6.0_9-0OVERVIEW
The TWRP ports currently available for the Lenovo Tab3 8 are outdated by a number of years and are lacking in official support for more recent Android release versions. TWRP 3.6.0_9-0 was originally compiled using the Android 9 tree, and therefore supports all Android versions up to, and including, Android 9 Pie. This custom recovery build also includes improved manageability of Android supported filesystem standards, better protection against data loss and corruption, added functions, and improved theming support. Likewise, I've made several bug fixes and cleaned up the codebase. To read a more in-depth list on the changeling of TWRP 3.6.0, visit this link the official TeamWin site here: TWRP 3.6.0 Release Notes
REQUIREMENTS
First and foremost, you need an unlocked bootloader. There are a plethora of guides hosted here on XDA that provide detailed instructions for standard bootloader unlocking. If your tablet is not yet unlocked, go ahead and complete that task and return here once finished. Secondly, you will need a Windows PC or laptop with the SDK platform tools installed or, alternatively, the Minimal ADB & Fastboot tools (link provided below). Note that a Linux or Mac machine may also be used; for purposes of this guide, however, I will be focusing solely on a Windows setup. Next, you will need an internet connection to download the files provided in the links below. Lastly, you will need the factory supplied or a quality equivalent USB-A to micro USB data syncing/charging cable.
COMPATIBILITY
This TWRP custom recovery is compatible with both hardware variants (80 & 81) of the TB3-850F model, as well as the TB3-850M 4G-LTE supported model.
DISCLAIMER
Installing a custom recovery on an Android mobile device is an invasive procedure in terms of the modifications made to the stock partition index. Flashing the partitions of your device is a task that encompasses the inherent risk of bricking or otherwise rendering your device inoperable. By proceeding further, you are assuming sole responsibility for the integrity and operability of your tablet. Follow the instructions carefully, employ some patience, and things should go smoothly. I would encourage inexperienced members to read this guide in full prior to starting the instructions.
INSTRUCTIONS:
Download the Minimal ADB & Fastboot tools from the below link and install the program on your Windows PC & laptop. Next, open your Windows File Explorer, open your C: drive, then open Program Files x86. Copy the Minimal ADB & Fastboot folder and paste it to your desktop. (Copying the directory to the desktop isn't required, but does configure the ADB & Fastboot path to a more convenient directory from which to work);
Download TWRP 3.6.0_9-0 from the below link and save the image file in your ADB & Fastboot folder on your computer;
Boot your tablet into fastboot mode as follows: with your tablet booted into the Android OS, ensure ADB Debugging is enabled in the Developer Options menu. Connect the tablet to your PC using a sufficient USB-A to micro USB syncing/charging cable;
Open the ADB & Fastboot folder on your computer. Double click cmd-here.exe to open a command window, and execute the following command:
Code:
adb reboot bootloader
Your tablet may prompt you to authorize the ADB connection;
If properly connected your Tab3 8 will boot into fastboot mode, which will be indicated by the status displayed on the tablet. To verify proper fastboot communication between your computer and tablet, execute this command:
Code:
fastboot devices
If everything is set up properly, the command window will return an alphanumeric string consistent with your tablet S/N;
If your S/N isn't displayed, or if your are given a WAITING... notification, your tablet is not being recognized correctly. Change USB ports, try a different data syncing cable, and/or update your fastboot drivers;
Once a solid connection has been verified, execute the following command to flash TWRP to your tablet:
Code:
fastboot flash recovery twrp.img
(The TWRP file you downloaded below is named twrp.img. The above flashing command assumes that you have left the filename unchanged.);
You may now boot your tablet into TWRP recovery mode by executing:
Code:
fastboot boot twrp.img
Task complete. You should now running TWRP 3.6.0_9-0 on your Lenovo Tab3 8 device.
DOWNLOADS:
• TWRP 3.6.9_9-0 Lenovo Tab3 8
• Minimal ADB & Fastboot Tools v1.4.3
THANKS & MENTIONS:
First and foremost, thanks to TeamWin Recovery Project for providing the base build, and for their many years of hard work and contributions to the custom Android community. Thanks to the XDA members who remain dedicated to the Lenovo Tab3 8 and its continuing development projects. Although I'm slow, I have two more projects in the works for our beloved tablets. Thank you for your patience my friends.BUGS:Please leave a comment detailing any bugs or instabilities you may encounter. I will diligently try to patch and fix any reported bugs.
Hi,
I flashed TWRP v3.4.1-0 from your link but I end up in a boot loop where I fail to mount any of the partitions.
The DL Link for TWRP v3.6.0_9-0 seems to be broken. Do you have an alternate for that?
Note: I'm working on a TB3-850F.
Thanks!
Okay I think dm-veriry is to blame. If you mounted /system after installing TWRP, dm-veriry will be triggered and the device will boot loop.
You need to flash a dm-verity disabler. I'll get you a link .
Any chance you might also have a link to the updated twrp you had linked above? It's a dead link now.
Diznatch52 said:
Any chance you might also have a link to the updated twrp you had linked above? It's a dead link now.
Click to expand...
Click to collapse
Sure. I'll fix the link
Ok link is fixed. Follow these steps.
Warning: This will wipe all data from your device.
Download the no-veriry_opt encrypt file linked below and save it to an external micro SD card. Insert the micro SD in your TB3-850F;
Install TWRP v3.6.0_9-0 and reboot recovery;
Select Wipe, Format Data, and swipe to commence.
Select Install and navigate to the saved location of the no-verity zip you downloaded in Step 1. Select the zip and swipe to commence installation.
Reboot system
no-verity_opt-encrypt_v6.1.zip
If you want root access of the Android OS, install a Magisk systemless root script after Step 4.
Awesome! I'll give it a shot.
Diznatch52 said:
Awesome! I'll give it a shot.
Click to expand...
Click to collapse
Download Magisk v24.3 from this link https://mega.nz/file/4c43FbwS#Qd-pKoupa8LZ-EI9qe5Zsr3L4rSz8NDv2Ojknrd8sCk
Install it after Step 4 if you want root. After you are booted, you can update Magisk to the latest v25.2 using the Direct Install option.
For some reason, after this process, running `adb reboot recovery` brings me to an android crash screen. Any idea why?
To confirm, this procedure did work and you were able to boot into the OS? Once you confirm I'll try to resolve your ADB issue.
Yes.
Diznatch52 said:
Yes.
Click to expand...
Click to collapse
Ok download the official TWRP App, grant it root permission, and flash the TWRP v3.6.0_9-0 to the recovery partition. Reboot your tablet and then try the adb reboot recovery command again.
When you flashed the original TWRP with fastboot, did you immediately boot into recovery and flash TWRP again using the Install>Image option?
As soon as I unbrick this again, I'll give it a shot
Edit: booting into recovery now gives me twrp! Thanks so much!
Now time to see if I have better luck flashing lineageOS
IT WORKED!
Thank you so much!
Anytime friend. Glad it worked out.
Update: December 13, 2022.
I am presently working on bumping TWRP up to v3.7.0_9-0.
The v3.7.0 base build includes Python support for Android Oreo & newer versions.; keymaster API V1 fixes; fixes on copying sepolicy on devices with no /vendor partition; several fixes on custom theme support as well as perfected ROM multiboot functionality. Also, I am updating my implementation of PIGZ compression for data transfer speed improvements and enhanced protection against data corruption. Stability improvements and minor bug fixes also included.
I will keep the OP updated with an ETA.
Diznatch52 said:
IT WORKED!
Thank you so much!
Click to expand...
Click to collapse
I have a build of LineageOS 14.1 that I optimized, fixed some bugs and removed settings entries on SIM cards & mobile networks. Open source libraries have been updated and the security patch level bumped up to June, 2022. GApps have been removed and several performance enhancements have been added. I'm without a working 850F at this time, but I should have a working device soon. I will post the LOS 14.1 build as soon as I can fully test it.
Diznatch52 said:
IT WORKED!
Thank you so much!
Click to expand...
Click to collapse
I have a build of LineageOS 14.1 that I optimized, fixed some bugs and removed settings entries on SIM cards & mobile networks. Open source libraries have been updated and the security patch level bumped up to June, 2022. GApps have been removed and several performance enhancements have been added. I'm without a working 850F at this time, but I should have a working device soon. I will post the LOS 14.1 build as soon as I can fully test it.
Oh, I nearly forgot, would you care to list your stock firmware build number please. Thanks
That would be incredible. I don't know if I still have access to my stock firmware build. I've already got a version of LOS 14.1 (could admittedly be snappier) installed. If you tell me how to find it, happy to send it over.
I just meant on your 850F, go to device settings, about tablet, and let me know your build number. Thx
Code:
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Droidian is a GNU/Linux distribution based on top of Mobian, a Debian-based distribution for mobile devices. The goal of Droidian is to be able to run Mobian on Android phones.This is accomplished by using well-known technologies such as libhybris and Halium.## What works
WIFI
Audio
Video Playback
USB-OTG
Cellular Data
Calls/SMS
Bluetooth
Wireguard
Flashlight
GPU (Works well in WayDroid, partially in Droidian)
See full list here
## What doesn't work
Camera
VoWifi
You tell us
Old UNOFFICIAL installation steps
Spoiler
This steps and UNOFFICIAL build of droidian have been abandonned and is deprecated, you're on your own there ! We recommand to follow official steps below
## Required Files
ADB commands and stuff
TWPR Treble : https://mega.nz/folder/UgdQRYSD#8s-_u2HJQZDEqNnFOnejxQ
You'll find it in : Recovery_(System-As-Root_Compatible) > twrp-op3treble-3.3.1-1.img
Latest firmware for your phone (at the writing time: 9.0.6) : https://github.com/nvertigo/firmware-3t/tree/master/archive (like version oxygenos-9.0.6-no-alipay-firmware-3.zip or oxygenos-9.0.6-firmware-3.zip if using a OP3)
WARNING ! Firmware are device-specific, be careful to take a OP3 or OP3T depending on your device !
LineageOS Treble: https://drive.google.com/drive/folders/1vnJEKkhO3xqH-fWWG55-yxwx5K1EeKq7
You only need the file LineageOS Treble
droidian-api28-arm64.zip : https://github.com/droidian-images/droidian/releases
NOTE: As we are flashing LineageOS 16 (android 9), pay attention to use and flash Droidian API28 (which is the version for Android 9)
Please do not use generic halium anymore, @Bettehem made a special version combining both files for OnePlus 3/T here : https://gitlab.com/Bettehem/op3-halium-waydroid Please prefer this version
Below, generic halium files that this tutorial does not recommend
halium-boot.img : https://mirrors.lolinet.com/firmware/halium/oneplus3/halium-boot.img
halium-ramdisk.zip : https://mirrors.lolinet.com/firmware/halium/GSI/tools/halium-ramdisk.zip
GSI patch by @Bettehem : https://gitlab.com/Bettehem/op3-gsi-fix-droidian
You can have alpha version from CI/CD artifact : https://gitlab.com/Bettehem/op3-gsi-fix-droidian/-/jobs/artifacts/main/browse?job=makezip
## Installation
First treblize your phone with the instructions from here: https://github.com/OP3-Halium/Documentation#treblelizing-your-op3t--firmware--twrp
Basically, all you have to do is :
Flash the special TWRP Treble previously downloaded
Boot it up and go to "Advanced" -> "Terminal", Type treblize and run
Reboot to recovery
Click to expand...
Click to collapse
Then follow the instructions here: https://github.com/OP3-Halium/Documentation#installing-using-erfan-gsi
Basically after you've treblized your device and installed the latest firmware, the install steps are as follows:
Flash the custom LineageOS Treble,so you get the /vendor partition populated.
Reboot to check that everything works. If so, reboot back in to recovery.
Go to advanced wipe and wipe everything except /vendor.
Reboot back into recovery.
Flash the droidian .zip (adb sideload droidian-api28.zip)
Deprecated steps
Flash halium-boot.img
⚠ This shouldn't be done with adb sideload, instead use those two lines :
adb push ./halium-boot.img /tmp/
adb shell "dd if=/tmp/halium-boot.img of=/dev/block/bootdevice/by-name/boot"
Flash halium-ramdisk.zip.
Now just flash @Bettehem's halium-boot.img
Flash @Bettehem's op3-gsi-fix-droidian.zip
⚠ Do NOT flash the regular op3-gsi-fix.zip which is for ubports and not this project ⚠
### Out of storageA note from @Bettehem 's GSI fix :
It was made possible to move the user's home dir to the phone's userdata partition, so you can utilize the full 64/128GB storage on the device. By default when you install Droidian, the user's home dir is on the 8GB system image, and that's not very much space for both the OS and your home dir
So after installing and booting the device, you can perform the first time setup if you want or skip it for now. Then open a terminal and run the command move-home
Click to expand...
Click to collapse
OnePlus3 is officially supported by Droidian now, here's the updated step by step install :
## Required Files
Download the latest recovery flashable zip droidian-OFFICIAL-phosh-phone-oneplus_oneplus3-api28-arm64_XXXX.zip: https://github.com/droidian-images/droidian/releases
## InstallationThe step-by-step installation comes from this guide : https://github.com/Droidian-oneplus3/device-page#requirements
Treblize your device:
Instructions here: https://forum.xda-developers.com/t/treble-unofficial-lineageos-16-0-treble-for-oneplus-3-3t.3830455/
After you have installed the custom twrp and you have a /vendor partition, install the custom LineageOS 16 build from the guide.
With LineageOS 16 installed, reboot and verify that everything works. Then reboot back into TWRP.
In TWRP, go Wipe -> Advanced Wipe -> Select everything except Vendor and USB-OTG, then Swipe to Wipe.
Reboot into recovery
Flash the droidian .zip using the recovery's install menu or adb sideload
Reboot
Congrats, you're all done, just restart your phone and enjoy using Droidian
## Troubleshoots
It had been reported some failing with the sideload function to flash parts of this tutorial.
If you enconter those problems, we recommend you to push the files to the device using adb push /path/to/your/file /tmp/ and then use TWRP's own install method
## Notes:
### First bootThe first boot can take up to 30 seconds. If you see the green droidian's logo on boot, don't worry for the following black screen, just your phone doing its stuff. Once you're os finally booted and ready to use, you'll have the screen showing time and icons.
### Default passwordThe default password is 1234.
### Wrong UI scaleSome applications aren't designed to fit well on to tiny mobile screens, so if you encounter a problem where buttons/text doesn't properly fit on the screen, do the following:
1. Open the application which doesn't fit well on your screen
2. Open the Mobile Settings application and navigate to the Compositor menu
3. Turn on the toggle for the application which doesn't scale well
Now every time you open the application, it should get scaled down to fit your screen.
### Status
Droidian GSIs are experimental! Bugs and missing features are expected.
OnePlus 3 isn't officially supported by Droidian
OnePlus3 is offically supported since 19/06/2023
@Bettehem's patch is a WIP
### SSH accessConnect your phone to your computer and type ssh [email protected]<OP3-WIFI-IP>, the password is 1234
### ApplicationsYou can find a list of mobile-friendly Linux applications at LinuxPhoneApps
# Credits
Thanks the Droidian team and the Mobian team for bringing Debian on mobile https://droidian.org | https://mobian-project.org
Thanks to the HaliumProject for all the hard work they do making this whole possible https://halium.org
Thanks to everyone contributing on https://github.com/OP3-Halium for those comprehensive tutorials
Thanks to simonsmh, dianlujitao, chenxingyu, for working and building the LOS Treble (Source Code: https://github.com/OP3Treble )
A huge and special thanks to @Bettehem (Telegram, Gitlab, XDA) for developing the patch and did help me to have it up and running on my phone
Thanks to you for giving a try to this and following this tutorial
# Troubleshooting## WiFi not connectingDroidian detects two wifi cards, and only one seems to work at a time.
If Droidian is trying to connect using the wrong card, you can easily change it by running the command nmtui, then select "Activate a connection" and then select the WiFi network you want to connect to.
## Mobile data not workingIn settings go to mobile network and press the "Unlock" button. Then close the settings app and open again, because the UI doesn't get updated automatically.
You should now be able to manage your mobile connection from here. To get correct Acces Point Name (APN) settings for your carrier, look here: https://apn.how
After you have set up the APN settings, then just toggle the "Mobile Data" setting off and back on again. If mobile data still doesn't work, you may want to restart the ofono service by running this command: sudo systemctl restart ofono.service. Then reopen settings and toggle the "Mobile Data" setting off and on again.
## Changing audio deviceThere's a known issue with changing the audio device inside the Settings app. You can use something like pavucontrol, ncpamixer or even just run pactl/pacmd commands directly.
You need to change the sinks port from the primary_output sink for it to work. Changing the port from the deep_buffer sink doesn't work.
# Random screenshots
I'm working on getting this installed. Can't seem to get past bootloader (oneplus icon).
Attempting to build on my system and see if that helps.
@undrwater Are you on OP3 or OP3T ? And did you exactly follow each step for the tutorial ? 'cause it all worked fine for me ^^"
RoiArthurB said:
@undrwater Are you on OP3 or OP3T ? And did you exactly follow each step for the tutorial ? 'cause it all worked fine for me ^^"
Click to expand...
Click to collapse
I'm on 3t. And while I have some confidence that I followed the directions exactly, there's room for doubt.
I'll try again when I can look at it without distractions.
undrwater said:
I'm on 3t. And while I have some confidence that I followed the directions exactly, there's room for doubt.
I'll try again when I can look at it without distractions.
Click to expand...
Click to collapse
The problem may come from the firmware link I did put before. It wasn't for 3T, so I just updated it and it would prevent similar errors
Please tell me when you'll retry and if now it works well
Actually, looking somewhat closer, I think the issue is finding the correct droidian zip to sideload. several are available, and the few I've tried fail with:
E: No hybris-mobian image found
Click to expand...
Click to collapse
/vendor is populated, lineage is flashed and booted halium boot image dd'ed.
undrwater said:
Actually, looking somewhat closer, I think the issue is finding the correct droidian zip to sideload. several are available
Click to expand...
Click to collapse
Hey, the good version is Droidian API 28 ('cause you're using a base Android 9) ARM64 (which is the Snapdragon in OP3/T)
My OP3 seems to boot into droidian but I have no display, I can tell booting finished because I get sounds when I adjust the volume or connect a charger. Does anyone have an idea why this might be?
Steps I took:
- Flashed latest firmware
- Installed treble TWRP
- ran treblize in TWRP console
- wiped all partitions with advanced wipe (including vendor)
- sideloaded / installed lineage 16 zip and rebooted to test
- wiped all partitions other than vendor in TWRP
- sideloaded / installed "droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip"
- installed hallium-boot in bootloader using "fastboot flash boot hallium-boot.img"
- rebooted
the-blind-bandit said:
My OP3 seems to boot into droidian but I have no display, I can tell booting finished because I get sounds when I adjust the volume or connect a charger. Does anyone have an idea why this might be?
Steps I took:
- Flashed latest firmware
- Installed treble TWRP
- ran treblize in TWRP console
- wiped all partitions with advanced wipe (including vendor)
- sideloaded / installed lineage 16 zip and rebooted to test
- wiped all partitions other than vendor in TWRP
- sideloaded / installed "droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip"
- installed hallium-boot in bootloader using "fastboot flash boot hallium-boot.img"
- rebooted
Click to expand...
Click to collapse
Hi, you need to install op3-gsi-fix-droidian.zip to get it working on the OnePlus 3.
You can download it from here: https://gitlab.com/Bettehem/op3-gsi-fix-droidian/-/jobs/artifacts/main/browse?job=makezip
So after flashing the droidian-api28-arm64.zip, just flash op3-gsi-fix-droidian.zip and you should be good to go.
Also remember to run the move-home command in terminal after booting for the first time. It will allow you to use all of the storage on the device
Bettehem said:
Hi, you need to install op3-gsi-fix-droidian.zip to get it working on the OnePlus 3.
You can download it from here: https://gitlab.com/Bettehem/op3-gsi-fix-droidian/-/jobs/artifacts/main/browse?job=makezip
So after flashing the droidian-api28-arm64.zip, just flash op3-gsi-fix-droidian.zip and you should be good to go.
Also remember to run the move-home command in terminal after booting for the first time. It will allow you to use all of the storage on the device
Click to expand...
Click to collapse
Thank you. I'm not sure how I missed that in the OP, I saw the bit in red for step 7 and just stopped there I guess
Anyway it's working now and OMG it's actually kinda good. Last time I tried a linux distro for an android phone, which wasn't that long ago, it froze almost all of the time. This seems quite responsive and actually has quite a good keyboard too. My hope for linux on phones (other that android) has been restored
the-blind-bandit said:
Thank you. I'm not sure how I missed that in the OP, I saw the bit in red for step 7 and just stopped there I guess
Anyway it's working now and OMG it's actually kinda good. Last time I tried a linux distro for an android phone, which wasn't that long ago, it froze almost all of the time. This seems quite responsive and actually has quite a good keyboard too. My hope for linux on phones (other that android) has been restored
Click to expand...
Click to collapse
Yeah I like Droidian quite a lot. I have been using it as my daily driver for some time now. Only camera doesn't work but hopefully I'll solve that issue at some point in the near future
I'm having problems with installing.
I followed the steps as instructed, treblized the phone (3T) and installed Linage 16. Lineage is booting fine. I checked the vendor partition which is populated.
After the wiping step (vendor left untouched) I installed droidian (tried droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip and droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-nightly_20221003.zip) and halium-boot.img. I also installed the patch "op3-gsi-fix-droidian.zip".
Droidian isn't loading. When using the halium-boot.img (15.41 mb) linked in this thread, the phone shows the bootscreen (1+) and reboots after some time. Using the halium-boot from this instruction: https://github.com/OP3-Halium/Documentation (15.8 mb) the phone just shows the 1+ logo without rebooting ...
what am i missing?
prosch said:
I'm having problems with installing.
I followed the steps as instructed, treblized the phone (3T) and installed Linage 16. Lineage is booting fine. I checked the vendor partition which is populated.
After the wiping step (vendor left untouched) I installed droidian (tried droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip and droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-nightly_20221003.zip) and halium-boot.img. I also installed the patch "op3-gsi-fix-droidian.zip".
Droidian isn't loading. When using the halium-boot.img (15.41 mb) linked in this thread, the phone shows the bootscreen (1+) and reboots after some time. Using the halium-boot from this instruction: https://github.com/OP3-Halium/Documentation (15.8 mb) the phone just shows the 1+ logo without rebooting ...
what am i missing?
Click to expand...
Click to collapse
Hi, this tutorial recommand using Bettehem's halium-boot file.
If you did checked the Github's documentation, you should have saw a note part for flashing the halium-boot.zip ( https://github.com/OP3-Halium/Documentation#note ) describing 3 differents methods to do it. Did you follow them all or how did you do it ? It may be recommended to use the old technic :
Flash halium-boot.img ⚠ This shouldn't be done with adb sideload, instead use those two lines :
Code:
adb push ./halium-boot.img /tmp/
adb shell "dd if=/tmp/halium-boot.img of=/dev/block/bootdevice/by-name/boot"
Click to expand...
Click to collapse
I used fastboot and the TWRP push method, no difference. I used all the files linked in this tutorial and all of those in the github documentation. After flashing, when rebootIng, TWRP complains that there is noch OS installed... Lineage Installation is no problem. I just tried the ubports installer to install Ubuntu Touch. This stops while pushing the files... Installing OxygenOS works... kinda strange
Update: It's working now. I also had to do "format data / factory reset" after step 2 and repair the fs of cache, system and data to ext4 after rebooting. Using the files from the OP3-Halium-Documentation Droidian is now loading.
I'm installing Droidian, but for some reason I'm getting a booting Ubuntu Touch. I flash in the following order:
* wipe everything but /vendor
* `ubports_GSI_installer_v10.zip`
* `droidian-devtools-api28-arm64_20220804.zip`
* `op3-gsi-fix-droidian.zip`
If I try to wipe `/system` before flashing `droidian-devtools-api28-arm64_20220804.zip`, I'm getting an error: `No hybris-mobian image found`
What am I doing wrong?
marmistrz said:
I'm installing Droidian, but for some reason I'm getting a booting Ubuntu Touch. I flash in the following order:
* wipe everything but /vendor
* `ubports_GSI_installer_v10.zip`
* `droidian-devtools-api28-arm64_20220804.zip`
* `op3-gsi-fix-droidian.zip`
If I try to wipe `/system` before flashing `droidian-devtools-api28-arm64_20220804.zip`, I'm getting an error: `No hybris-mobian image found`
What am I doing wrong?
Click to expand...
Click to collapse
You shouldn't be installing ubports_GSI_installer if you want Droidian. UBports is Ubuntu Touch.
To get Droidian running, follow the instructions on this page or https://github.com/OP3-Halium/Documentation#installing-droidian
For Droidian, you shouldn't be using ubports or droidian-devtools, as neither of those are used in this installation.
droidian-devtools is optionally used with very old droidian images and is not at all needed in the newer ones so don't use it.
Hi, I installed droidian on op3t as described, it works from beginning. I used "droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip" an made an "apt-get (update, upgrade, dist-upgrade) to get the latest bookworm version.
The only problem atm: the phone cannot suspend. The blue LED blinks and if it ends the screen with the PIN login turns on (that does happen in a loop). Any hints?
sfoslino said:
Hi, I installed droidian on op3t as described, it works from beginning. I used "droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-24_20220804.zip" an made an "apt-get (update, upgrade, dist-upgrade) to get the latest bookworm version.
The only problem atm: the phone cannot suspend. The blue LED blinks and if it ends the screen with the PIN login turns on (that does happen in a loop). Any hints?
Click to expand...
Click to collapse
Hi, I'm not sure why it does that but I'll try to investigate
Bettehem said:
Hi, I'm not sure why it does that but I'll try to investigate
Click to expand...
Click to collapse
If I remember right it could sleep if I disable wifi. I tried to work around with a script running 'onsuspend' but had no luck, always a probleme because the wifi adapter was shown twice in phosh settings.