Related
Team Win Recovery Project 3.0.4-1 (unreleased)
Notice #1: Please don't wipe your data partition if TWRP cannot decrypt it. Instead, make an effort to gather logs to help solve the issue!
Notice #2: Themes from 3.0.0 to 3.0.3 are incompatible with 3.0.4. Sorry! (small theme engine changes regarding backlight control)
This is a unified build for both the OnePlus 3 and the OnePlus 3T!
WARNING: The OnePlus 3 & 3T stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/oneplusthree.html
Use 3.0.4-1 for now, rather than the builds on twrp.me until an official release happens. You will have problems with 3.0.3 on Nougat!
For now, please download the build from:
https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-1-oneplus3.img
Officially 3.0.4 has not been released yet, but it has critical fixes for this device on Nougat, so please be patient.
There is a download link there, as well as instructions on how to flash it.
You can find up to date fastboot & adb binaries here!
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
Extract/install adb & fastboot to your computer.
{
"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"
}
Download TWRP for OnePlus 3 & 3T (oneplus3).
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Up] + [Power] buttons while your device reboots or boots from power off.
Once you're in fastboot mode, you need to unlock your bootloader. To do this, run the command:
fastboot oem unlock
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Once your bootloader is unlocked, you're ready to flash TWRP. To do this, run the command (replacing twrp.img with the actual image name):
fastboot flash recovery twrp.img
Once the image is flashed, you should use your volume keys to navigate to RECOVERY and the press the power key to select it.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If your device asks for a password to mount internal storage, and your password doesn't work or you haven't set one, see below under known issues for a fix!
If you want to be rooted with SuperSU:
Download the latest SuperSU Stable by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
---or (not both) ---
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up. (SuperSU will reboot you a few times)
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TWRP
To update TWRP, simply download the new twrp.img on your phone, then boot into your current TWRP and flash it.
To flash a twrp.img, navigate to [Install] -> [Flash Image] -> select your twrp.img -> [x] Recovery -> Flash!
After that, just use [Reboot] -> [Recovery] to reboot into the updated TWRP.
CHANGES
v3.0.4-1 (build.nethunter.com) - Fix crash when trying to reboot that resulted in TWRP restarting, CAF kernel updates
v3.0.4-0 (build.nethunter.com) - Capability restoration for Nougat, F2FS backport support, EXT4 decryption support
v3.0.3-0 (twrp.me) - Same as 3.0.3-1-rc2. In sync with the OnePlus 3T device tree (3.0.3-1).
v3.0.3-1-rc2 (build.nethunter.com) - Redo the device tree for OOS 4.0, including dynamic encryption support (pull libs from ROM)
FEATURES
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
Allows OnePlus full OTA flashing
KNOWN ISSUES
F2FS takes a long time to boot, see below.
If your device is taking more than 10 minutes to boot, you probably have a misc flag enabled that disables passing cmdline, see below.
Reboot buttons don't work in TWRP (restarts TWRP) - disable Ask to install TWRP App on settings page, fix on the way. - fixed in 3.0.4-1
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Personally, I'd have tried this after 15 minutes.
WHY DOES F2FS MAKE TWRP SO SLOW?
When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!
I suggest switching your data partition to ext4 - all the f2fs hype is merely from benchmarks that don't actually represent real world use (ie. you're not writing thousands of files per second)
For someone who doesn't do lots of write access to their data partition, ext4 can actually be advantageous (it has faster access times and reads!)
WHY WON'T MY DATA DECRYPT / WHY IS MY PASSWORD INVALID IN TWRP?
In order for encryption to work in TWRP, it must pull the encryption libraries from your current ROM. It does this during TWRP boot logo. If you have no ROM installed, then it will fall back to the default OxygenOS 4.0.2 encryption libraries included in the TWRP image.
The crypto daemon in recovery will not be able to decrypt unless the version of the encryption key matches the version of the libraries. This is an unusual restriction that was added by OnePlus.
You can usually fix this by simply booting into your ROM and changing your boot up password. You can change it back or remove it if you want immediately after. This will generate a new crypto key which should be compatible when you next enter TWRP.
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-7.1)
Device tree: https://github.com/TeamWin/android_device_oneplus_oneplus3 (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_oneplus_msm8996 (twrp-7.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project for the OnePlus 3 & 3T, Tool/Utility for the OnePlus 3
Contributors
jcadduono, Team Win
Source Code: https://github.com/jcadduono/android_device_oneplus_oneplus3
Version Information
Status: Stable
Current Stable Version: 3.0.4-1
Stable Release Date: 2017-01-21
Created 2017-01-23
Last Updated 2017-02-07
Reserved
ONEPLUS FULL OTA ZIPS
You can flash these zips in TWRP to update your device or save yourself from a broken or soft-bricked state.
They are official zips distributed by OnePlus.
For the OnePlus 3 only:
OxygenOS 3.2.8: http://s3.amazonaws.com/oxygenos.on...6_OTA_017_all_1611182000_fbe1471194d64b3e.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...en_16_OTA_035_all_1612310359_e10cadfb2af7.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...16_OTA_039_all_1701140133_89fcc9baba94e4c.zip
OxygenOS 4.0.3: http://otafsc.h2os.com/patch/amazon...ygen_16_OTA_041_all_1702081756_0f1e56a75f.zip
For the OnePlus 3T only:
OxygenOS 3.5.3: https://s3.amazonaws.com/oxygenos.o...8_OTA_027_all_1611222319_884473ff95304c30.zip
OxygenOS 3.5.4: http://oxygenos.oneplus.net.s3.amaz...8_OTA_029_all_1612131737_17e7161d2b234949.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...ygen_28_OTA_037_all_1701041831_a2ba632ce9.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_039_all_1701140132_400a7.zip
OxygenOS 4.0.3: http://otafsc.h2os.com/patch/amazon...3TOxygen_28_OTA_041_all_1702081824_e3a712.zip
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.
jcadduono said:
Team Win Recovery Project 3.0.4-0 (unreleased)
Click to expand...
Click to collapse
Nice mate as always.
Pm: you might need yo check the format of the first post, everything is written 3 times. :laugh:
peshellas said:
Nice mate as always.
Pm: you might need yo check the format of the first post, everything is written 3 times. :laugh:
Click to expand...
Click to collapse
Never quote full op, this is spamming.
For 3 times same content, open xda in browser, it's xda app bug.
RohanAJoshi said:
Never quote full op, this is spamming.
For 3 times same content, open xda in browser, it's xda app bug.
Click to expand...
Click to collapse
You re Right mate, i know, i have been here since the very old days, I thought i had deleted ot, and continued, apparently not. Thanks for the tip, didn't know about the bug.
ext4 decrypted fine on OnePlus 3 OOS 4.0.2.
Is flashing twrp-data-fstype-swap-x.x.zip still necessary when switching between f2fs and ext4?
The instructions and the link are not stated in OP anymore.
fbf2201 said:
Is flashing twrp-data-fstype-swap-x.x.zip still necessary when switching between f2fs and ext4?
The instructions and the link are not stated in OP anymore.
Click to expand...
Click to collapse
Both EXT4 and F2FS should work out of the box now.
No flashing needed.
Hello and thanx for the hard job.
I wanted to try a clean install starting from stock, hoping to correct my issue with twrp black screen.
I need your help. Here is what I've done :
- Restore stock with the unbrick tool
- Update to Nougat 7.0 and OOS4.0.2 via oneplus update
- Unlock bootloader
- Flash twrp 3.0.4-0 via fastboot
- Flash no-verity-opt-encrypt-5.0
- Flash RR rom
- Wipe data and Dalvik
- Reboot.
This is the first time it made it to me. It ask me a password when it boot. I saw a lot of post about that, but I can't understand how to solve it.
Can someone help me please ? My phone is OP3T
Hello, thanks for the super-useful tool. TWRP has been my goto recovery for as long as I have been rooting (days of htc-hd2). I am experiencing the following issues with v3.0.2-1 (all my checkpoint backups are in that version).
* Device = op3
* If it helps, this was a OOS 4.0.1 backup. I was trying to restore it because of a 4.0.2 upgrade failure attempt
* restore hangs at 100% after the backup is complete.
* After waiting for nearly 15 mins, I used the power down to restart the phone - i had lost recovery
* tried to re-install recovery. but when twrp boots - it doesn't get to main menu
* Oddly enough op recovery installs and boots into fine. Which is what I am on.
I am currently on stock recovery without root unable to restore backup ups in twrp and in titanium backup
any thoughts?
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
ScratMan38 said:
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
Click to expand...
Click to collapse
Its a unified version
ScratMan38 said:
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
Click to expand...
Click to collapse
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
cultofluna said:
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
Click to expand...
Click to collapse
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
cultofluna said:
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
Click to expand...
Click to collapse
it's unified. even if it says op3 it will work for the 3t. read the op. a lot of 3t stuff baked in. works fine. only issue now is the black screen with LED light when booting into recovery. at least for me
Renosh said:
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
Click to expand...
Click to collapse
Thanks your reply was really helpful:laugh:
the 3.0.4.0 is recommend version or have some problem must need? for now i'm use 3.0.3.1 is good with f2fs data partition, OS version is RR-N-v5.8.0-20170117-oneplus3t-Official, i want to dirty flash update to RR-N-v5.8.0-20170122-oneplus3t-Official, i need update TWRP to 3.0.4.0 first? or i can keep use 3.0.3.1?
Renosh said:
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
Click to expand...
Click to collapse
Abaddon said:
it's unified. even if it says op3 it will work for the 3t. read the op. a lot of 3t stuff baked in. works fine. only issue now is the black screen with LED light when booting into recovery. at least for me
Click to expand...
Click to collapse
There was two links in the OP, one for 3.0.3-1 mentioning "unified", and one for 3.0.4 with only "oneplus3".
As I knew the dev was working on both version and still supplies 3.0.3-1 test releases in Op3T thread that were newer than the 3.0.4 he built ; and as the changelog did not mention the unification for 3.0.4, for sure, OP was not clear at all.
Is this 3.0.3.x or 3.0.4.0 backward compatible with Marshmallow ROMs?
chancex said:
the 3.0.4.0 is recommend version or have some problem must need? for now i'm use 3.0.3.1 is good with f2fs data partition, OS version is RR-N-v5.8.0-20170117-oneplus3t-Official, i want to dirty flash update to RR-N-v5.8.0-20170122-oneplus3t-Official, i need update TWRP to 3.0.4.0 first? or i can keep use 3.0.3.1?
Click to expand...
Click to collapse
You want to update a custom rom which by definition has no issue with dm-integrity (only present in stock boot image), so if you don't have any issue keep your recovery.
It seems though that latest version has a minimized risk of issues with f2fs so why not updating it?
cultofluna said:
Thanks your reply was really helpful[emoji23]
Click to expand...
Click to collapse
He was right, the thread's title says clearly 3 and 3T.
It seems there are some conflicting reports on the issue. Some people say that rooting Oreo can't be done because there is an issue with Magisk/SuperSU preventing it, while others says they've managed to root their Oreo A8.
I would just like to get an idea of anyone who has tried to root Oreo. Please share your experience to date.
Did it fail or was it successful?
Is everything running smoothly?
What method and steps did you use?
I'm sure I'm not the only one who would appreciate the feedback.
it failed
no natter what i did
on modifying the /system through twrl, on reboot, the os locks the sim, uninstalls the Samsung apps like pay/health etc and then re encrypts the phone
shunsai said:
It seems there are some conflicting reports on the issue. Some people say that rooting Oreo can't be done because there is an issue with Magisk/SuperSU preventing it, while others says they've managed to root their Oreo A8.
I would just like to get an idea of anyone who has tried to root Oreo. Please share your experience to date.
Did it fail or was it successful?
Is everything running smoothly?
What method and steps did you use?
I'm sure I'm not the only one who would appreciate the feedback.
Click to expand...
Click to collapse
Yep
https://forum.xda-developers.com/ga...--other-development/root-magisk-oreo-t3825096
Used Ashyx TWRP and no-verity-opt-encrypt_ashyx, from corsicanu's thread. I've used Magisk v16.0 stable as well as beta v16.7.
Root is working for ADB, Termux and Xposed (installed as Magisk module). Root is not working for Titanium (says it can't detect root; used Magisk busybox) and for Stericson's Busybox (says unverified binary and won't install). Another thing I've noticed is that microG's UnifiedNlp "self check" says NO to "UnifiedNlp is registered in system".
Magisk was showing as "not installed" in Magisk Manager for a while, but switched to green (installed) after a few reboots. Not sure what I've done to change it. I suspect it's a certain combination of TWRP and no-verity-opt-encrypt that does the trick, because I've been alternating between Mesa's and Ashyx's versions. Magisk root was working even when Manager was saying "not installed".
I will retry with a clean reinstall of Oreo 8.0.0, Mesa's TWRP and no-verity-opt-encrypt-6.0.zip from his TWRP thread. I'm on official ROM A530FXXU2BRG1.
I haven't tested SuperSU much, I will try it more thoroughly. (Personally I don't care about systemless and hiding from SafetyNet or *Pay stuff, so whatever root method works is fine with me.)
Whatever you do, a piece of advice: follow whatever guide you're using carefully, because not doing all the steps properly can end up in a mess (eg. bootloops, or you get a screen asking for password to decrypt phone that won't go away). Also, it seems that mixing flashable stuff from different sources is a bad idea unless you know what you're doing.
Same as above. Best working combination I've found is Mesa's TWRP and no-verity, with Magisk 16.7 and Manager 5.8.3.
Root works with mostly everything I've thrown at it, with the following notable exceptions:
* Titanium Backup triggers the popup to ask for root, but says "Sorry, I could not acquire root privileges."
* UnifiedNlp's self check says "can't integrate with system".
* As soon as you flash Magisk, MTP and ADB stop working. When you connect to the PC there's no popup for either "allow connection" or ADB fingerprint.
Mesa's kernel fixes the MTP issue, and PC connection "allow" popup starts working again.
On the flip side, attempting to enter developer settings while running Mesa's kernel crashes the settings app. I've used a terminal app (Termux) to enable ADB manually (or you can enable it before you flash the kernel):
Code:
settings put global development_settings_enabled 1
settings put global adb_enabled 1
Here's everything I've gathered about the process (or as I like to call it, "how to get root on A8 2018 in 20 easy steps"):
* Start the phone, enable OEM lock from developer settings. Never disable it again, it prevents the phone from booting if any of the partitions are unofficial.
* Use Odin 3.13 or later, earlier versions can't deal with the new LZ4 compression Samsung applies to the partition images. Heimdall is very old and will not work. If you're on Linux, use a virtual machine to run Odin under Windows. VirtualBox is excellent (remember to connect the phone from VB's USB menu when in download mode).
* Power+VolDn+VolUp from any situation will force reboot. Power+VolDn+VolUp immediately after start enters download mode.
* Flash BL, AP, CP and CSC from an official ROM to bring the device to factory status.
* At this point you phone is functional, if you don't want root and just want to use it, stop here.
* If you intend to continue, I recommend that you don't boot to system.
* Reboot and re-enter download mode, flash Mesa's TWRP.
* Reboot and immediately press Power+VolUp to enter TWRP. Do NOT boot to system just yet, you can trip the anti-theft protection.
* [Always] swipe to allow modifications when entering TWRP.
* You may want to grab a TWRP backup of various partitions at this moment. Recovery is obviously not official anymore, but you can grab boot, system, efs, baseband, modem etc. Very good idea. If your SD card is not large enough for system (has 3.5 GB) at least grab the others.
* From Wipe menu, choose format data. Boot to RECOVERY. Do not install TWRP app.
* From Mount menu, verify that Data is mounted.
* Flash in this order: RMM fix and no-verity.
* Reboot to system, let it work (Samsung logo and blue led flashing). Yes, it may take a lot of time, let it work.
* At this point you have a clean system with custom recovery but no root. Check that stuff is still working fine.
* During phone setup, do NOT check "send diagnostic data".
* Reboot to TWRP, flash Magisk.
* Again, the first boot may take a long time, let it work.
wirespot said:
Same as above. Best working combination I've found is Mesa's TWRP and no-verity, with Magisk 16.7 and Manager 5.8.3.
Root works with mostly everything I've thrown at it, with the following notable exceptions:
* Titanium Backup triggers the popup to ask for root, but says "Sorry, I could not acquire root privileges."
* UnifiedNlp's self check says "can't integrate with system".
* As soon as you flash Magisk, MTP and ADB stop working. When you connect to the PC there's no popup for either "allow connection" or ADB fingerprint.
Mesa's kernel fixes the MTP issue, and PC connection "allow" popup starts working again.
On the flip side, attempting to enter developer settings while running Mesa's kernel crashes the settings app. I've used a terminal app (Termux) to enable ADB manually (or you can enable it before you flash the kernel):
Here's everything I've gathered about the process (or as I like to call it, "how to get root on A8 2018 in 20 easy steps"):
* Start the phone, enable OEM lock from developer settings. Never disable it again, it prevents the phone from booting if any of the partitions are unofficial.
* Use Odin 3.13 or later, earlier versions can't deal with the new LZ4 compression Samsung applies to the partition images. Heimdall is very old and will not work. If you're on Linux, use a virtual machine to run Odin under Windows. VirtualBox is excellent (remember to connect the phone from VB's USB menu when in download mode).
* Power+VolDn+VolUp from any situation will force reboot. Power+VolDn+VolUp immediately after start enters download mode.
* Flash BL, AP, CP and CSC from an official ROM to bring the device to factory status.
* At this point you phone is functional, if you don't want root and just want to use it, stop here.
* If you intend to continue, I recommend that you don't boot to system.
* Reboot and re-enter download mode, flash Mesa's TWRP.
* Reboot and immediately press Power+VolUp to enter TWRP. Do NOT boot to system just yet, you can trip the anti-theft protection.
* [Always] swipe to allow modifications when entering TWRP.
* You may want to grab a TWRP backup of various partitions at this moment. Recovery is obviously not official anymore, but you can grab boot, system, efs, baseband, modem etc. Very good idea. If your SD card is not large enough for system (has 3.5 GB) at least grab the others.
* From Wipe menu, choose format data. Boot to RECOVERY. Do not install TWRP app.
* From Mount menu, verify that Data is mounted.
* Flash in this order: RMM fix and no-verity.
* Reboot to system, let it work (Samsung logo and blue led flashing). Yes, it may take a lot of time, let it work.
* At this point you have a clean system with custom recovery but no root. Check that stuff is still working fine.
* During phone setup, do NOT check "send diagnostic data".
* Reboot to TWRP, flash Magisk.
* Again, the first boot may take a long time, let it work.
Click to expand...
Click to collapse
Were you able to test from a non-tripped Knox and if so was it tripped by your process?
I don't have another phone with the e-fuse not tripped so I can't test, but USB works perfectly fine until you flash root and also after you flash Mesa's kernel.
Pipsname said:
Were you able to test from a non-tripped Knox and if so was it tripped by your process?
Click to expand...
Click to collapse
Un-tripped Warranty Bit and Root are two thing that can't stay together lol
---------- Post added at 06:01 PM ---------- Previous post was at 06:00 PM ----------
wirespot said:
On the flip side, attempting to enter developer settings while running Mesa's kernel crashes the settings app.
Click to expand...
Click to collapse
Never heard about this issue; Could you please share a log of the error to look at it to fix it? A new version of the kernel is under-the-hood so would be nice to fix all the possible issues
BlackMesa123 said:
Un-tripped Warranty Bit and Root are two thing that can't stay together lol
Click to expand...
Click to collapse
I am currently rooted on 7.1.1 with no tripped Knox so I was wondering if it was possible with Oreo.
Pipsname said:
I am currently rooted on 7.1.1 with no tripped Knox so I was wondering if it was possible with Oreo.
Click to expand...
Click to collapse
Rooted without tripping Warranty Bit? And how since bootloader checks binary signatures at each boot lol
BlackMesa123 said:
Never heard about this issue; Could you please share a log of the error to look at it to fix it? A new version of the kernel is under-the-hood so would be nice to fix all the possible issues
Click to expand...
Click to collapse
Kernel log? Would an export from logcat do?
wirespot said:
Kernel log? Would an export from logcat do?
Click to expand...
Click to collapse
Nah a simple logcat is what I need lol. Use Logcat Extreme if you don't wanna use adb
BlackMesa123 said:
Nah a simple logcat is what I need lol. Use Logcat Extreme if you don't wanna use adb
Click to expand...
Click to collapse
Lel I use matlog
In some hour (or maybe less lol) the new version of my custom kernel will be released, with a good present for you all... ?
BlackMesa123 said:
In some hour (or maybe less lol) the new version of my custom kernel will be released, with a good present for you all... ?
Click to expand...
Click to collapse
I can't open the therd image.
BlackMesa123 said:
Rooted without tripping Warranty Bit? And how since bootloader checks binary signatures at each boot lol
Click to expand...
Click to collapse
I used your guide.
https://forum.xda-developers.com/ga...recovery-twrp-3-2-2-0-galaxy-a8-2018-t3818201
Pipsname said:
I used your guide.
https://forum.xda-developers.com/ga...recovery-twrp-3-2-2-0-galaxy-a8-2018-t3818201
Click to expand...
Click to collapse
Lol that's faked userspace warranty bit prop. Go in Download Mode and you see Warranty Bit is actually blown
BlackMesa123 said:
Lol that's faked userspace warranty bit prop. Go in Download Mode and you see Warranty Bit is actually blown
Click to expand...
Click to collapse
Well would you look at that! Thank you.
Is Magisk 16.7 Beta?
Samsung Galaxy (SM-A530F/DS) A8 (2018), Android 8.0.0.
After 129 hours I got OEM Unlock. I installed TWRP 3.2.3-0. In TWRP > Wipe>Format Data and follow the instructions in screen. After I flashed latest no-verity-opt-encrypt zip and RMM Bypass zip. Reboot System.
In TWRP I flashed MCK-Oreo_A8_BRG1_v1-fix.zip. Reboot System.
In TWRP I flashed Magisk 16.7 Beta. Reboot System.
I installed Magisk Manager 5.8.3. and I got this:
This TWRP recovery Is compiled from source & will be supported officially soon
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 project
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Prerequisites
1. Unlocked bootloader.
Bugs
1. Not tested yet
2. If you have found a bug, please consider posting it to my GitHub Issues.
Instructions
1. Go to the fastboot mode.
2. Download the recovery image and transfer it to the adb folder.
3. Open the cmd/terminal and change directory into the adb folder.
4. Now confirm/check that device is connected by typing:-
Code:
fastboot devices
If you got your device seriel number there then you are ready to continue otherwise try connecting device again and make sure USB debugging is on and you have granted permission to the PC to debug.
5. After that we will flash this TWRP recovery to the recovery partition by below command:-
Code:
fastboot flash recovery twrp-name.img
BooM ! TWRP flashed successfully.
6. Now unplug your device and then use your device key combo to boot into TWRP recovery mode.
Enjoy !
Downloads
Android File Host: https://www.androidfilehost.com/?w=files&flid=296748
Official TWRP Page: Yet to submit
Contributors
chankruze
Source Code: https://github.com/N00bTree/android_device_ulefone_Armor_6
Version Information
Status: stable
Thank you! I can confirm this also works on the Armor 6E.
i have been able to flash it but its pretty useless as i cant decrypt it and no other options show up
mentalik said:
i have been able to flash it but its pretty useless as i cant decrypt it and no other options show up
Click to expand...
Click to collapse
I had same problem, I flashed https://androidfilehost.com/?fid=6006931924117895653 and formatted internal data.
thanks that solved it for me
jonezy82 said:
I had same problem, I flashed https androidfilehost.com ?fid=6006931924117895653 and formatted internal data.
Click to expand...
Click to collapse
How do i even flash that? twrp is refusing to let me do anything.
Yoosk said:
How do i even flash that? twrp is refusing to let me do anything.
Click to expand...
Click to collapse
EDIT: Have you tried to select "cancel" when you get into twrp?
You can get past of decryption by selecting "cancel".
You need to format your internal storage, then flash that .zip from usb-otg usbstick.
FYI: I got my phone screwed once, I just flashed stock firmware with sp_flash_tool and it formatted storage for me.
[SOLUTION FOUND! SOLUTION IN THE FIRST ANSWER]
https://forum.xda-developers.com/showpost.php?p=83545573&postcount=2
Hello everybody.
I need help about how to install GSIs on my device. I am trying to install GSIs on my Samsung Galaxy A7 (2018) (SM-A750G) device.
After learning about the requirements to use GSIs I was able to see that my device is Treble (A-Only) compatible, so I looked for GSIs A-Only and with ARM64 architecture (the architecture of the CPU of my device).
Once everything was prepared and the OEM Unlock was done I tried to use fastboot from my PC to install GSIs but I not obtain results and I tried to use the "traditional" way with TWRP and after flashing the image (.img) in System with TWRP I did not obtain either any result. I was getting bootloops or stuck at startup (even for hours). This forced me to reinstall the official Samsung firmware (downloaded from samfw [dot] com) and I am currently using that same one.
I used this reference guide as it is the closest I could find: https://forum.xda-developers.com/galaxy-a7/how-to/guide-guide-how-to-flash-gsi-t3933968
Could someone tell me what I may be doing wrong, or what is wrong with my device?
Thank you very much.
Solution
After "struggling" with the bootloop, I finally managed to find an answer.
APPEARINGLY a kernel problem. My solution was the following:
* In an SD Card, place; Magisk-phh, Quantum Kernel (GSI and ONEUI), the RMM Bypass, the boot fix and the GSI. Put the memory card inside the device.
* Enter in the recovery mode pressing the VOLUME UP + VOLUME DOWN keys and inserting a USB cable connected to a PC.
* Install stock firmware using Odin.
[DO NOT START THE SYSTEM YET]
* Unplug the USB, and restart (or close and open) Odin.
* Install TWRP using Odin.
[IMPORTANT: Disable Odin's "Auto Restart" AND DO NOT ALLOW THE SYSTEM TO START UP ON FINISH. Automatically go to TWRP by pressing the POWER + VOLUME UP keys for a few seconds until you see the Samsung startup].
* Flash the RMM Bypass zip.
* Reboot in recovery.
* Format (not wipe) /data.
* Wipe normally the partitions.
* Flash Quantum kernel (WARNING: The version I used was the "ONEUI" version, not the one that says GSI).
* Start the system (just seeing the welcome screen is enough).
* Go to TWRP again.
* Flash the GSI (in my case I used the one provided by Google, I don't know if this will work with other GSIs).
* Flash Magisk-phh.
* Flash RMM Bypass again.
* Flash Quantum Kernel (this time YES the one that says GSI).
* Flash the boot fix.
After this, the bootloop disappeared and I was able to use the GSI without any problem. I'm not sure why this is, I can only say that it is the only thing that worked for me.
The links of the tools that I used are the following (I don't know if this works with other tools):
Android 10 GSI: https://developer.android.com/topic/generic-system-image/releases#android-gsi-10
Quantum Kernel: https://forum.xda-developers.com/ga...ernel-quantum-kernel-v1-0-updated-20-t4085585
phh-magisk: https://sourceforge.net/projects/expressluke-gsis/files/Extras/phh-magisk-ten/
RMM Bypass: https://drive.google.com/file/d/1UvqcYUbVTFomAmKCVkMyfTWeuz1sEz8n/view
Boot Fix: https://forum.xda-developers.com/galaxy-a7/how-to/guide-guide-how-to-flash-gsi-t3933968
Odin: https://samsungodin.com/
I hope it has been helpfull.
"The links of the tools that I used are the following (I don't know if this works with other tools):"
@gsosacristian
where did you get twrp for A7 2018?
me-droid said:
"The links of the tools that I used are the following (I don't know if this works with other tools):"
@gsosacristian
where did you get twrp for A7 2018?
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-a7/development/recovery-twrp-3-2-3-1-galaxy-a7-2018-t3876798 i took from this link everything works
The link for the boot fix image is expired. Do you still have it by any chance? I want to use it for GSI 13 but I'm not even sure that it will work
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.