Related
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:
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 ROM
* 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. No tested yet, be the tester and,
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.img 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 hold power button untill the phone turned off,after that press power button while holding vol down(-) button simultaneously and you will boot into TWRP recovery mode.
Enjoy !
Downloads
Test Build : https://androidfilehost.com/?fid=6006931924117887773
Official TWRP Website : Not submitted yet
Version Information
ROM OS Version: 9.0 Pie
Source Code: Device Tree
Based On: TWRP
Credits
Omni Team for minimal TWRP source
@chankruze (myself) for device tree and compilation.
SUPPORT
Official Telegram Group
Official Telegram Channel
Works very well. Just flashed the latest update with it. Thank you very much
Works real good so far.backed up,restored,formatted flash.everything I've tried so far works.was having trouble with forced encryption on stock rom but finally got past it.thanks for ur time to make this for community.
1. BlissOS latest GSI with device PIN selected during setup:
Data partition shows as 0mb in TWRP and asks for password to decrypt. Can't decrypt it with selected phone PIN.
Removing PIN from phone did not help either (still asked for password)
2. phh-AOSP 9v114 with device PIN and secure start-up selected during setup:
Data partition asks for pattern(?) to unlock in TWRP, even though pattern was not set.
Also the header at the top changes/flashes colors when on pattern screen.
3. Factory reset and setup with PIN but with secure start-up disabled:
This time it doesn't ask for pattern but password again. And can't decrypt with PIN.
4 .Factory reset again and setup without any kind of pin/pattern/password.
TWRP still asks for password to decrypt data.
5. Factory reset and setup pattern
TWRP asks for password
6. Repeat steps but this time with stock ROM from Umidigi. Same problems.
Code:
E:Decrypt took too long, killing process
Failed to decrypt data.
Unable to decrypt with default password. You may need to perform a Format Data
Unable to mount storage
Unable to mount /data/media/TWRP/.twrps
marcukial said:
was having trouble with forced encryption on stock rom but finally got past it
Click to expand...
Click to collapse
Why not share your solution?
@shookica
https://forum.xda-developers.com/showpost.php?p=79740894&postcount=263
marcukial said:
@shookica
https://forum.xda-developers.com/showpost.php?p=79740894&postcount=263
Click to expand...
Click to collapse
So you just flashed Magisk over stock ROM if I understand correctly from that post?
You say you flashed disable dm-verity but after that you restored from a full backup. That means the disable dm-verity package was removed anyway.
I tried flashing Magisk as well and even disabling persist force encrypt in Magisk app but that didn't solve my issue.
In any case I would like to be able to backup my data partition without flashing magisk and disable dm verity forceencrypt, simply by entering the password I set in Android.
That is how it is supposed to work anyway from my understanding.
shookica said:
So you just flashed Magisk over stock ROM if I understand correctly from that post?
You say you flashed disable dm-verity but after that you restored from a full backup. That means the disable dm-verity package was removed anyway.
I tried flashing Magisk as well and even disabling persist force encrypt in Magisk app but that didn't solve my issue.
In any case I would like to be able to backup my data partition without flashing magisk and disable dm verity forceencrypt, simply by entering the password I set in Android.
That is how it is supposed to work anyway from my understanding.
Click to expand...
Click to collapse
Yes.lol...i know that's what's so crazy.i gave up trying when I flashed the backup and just flashed magisk maybe something got left behind that didn't get wiped I don't know.i was shocked when I checked in settings/security and phone not encrypted. Rebooted to recovery and no password prompt all storage visible.
Code:
/*
* Your warranty is now void.
*
* We're 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 recovery
* 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.
*
*/
OrangeFox Recovery Project FOR PDX206 R10.0
About OrangeFox Recovery:
OrangeFox Recovery
wiki.orangefox.tech
What`s working:
Data Encryption (Need to format data for the first time)
Fastbootd
ADB Sideload
Flashing ROM
mount point at /system
mount point at /product
mount point at /vendor
mount point at /ODM
Bugs:
SD Card (Permanent)
[Some SD Card May can read/write]
Download:
AFH
How to flash:
Flash it at fastboot or fastbootd using this command
Code:
fastboot flash recovery X.img
Then Reboot
Code:
// For fastbootd
fastboot reboot fastboot
// For recovery
fastboot reboot recovery
About Encryption (Read First!):
Encryption
wiki.orangefox.tech
Source:
Recovery DT
Feel free to donate me:
Paypal
You are the best man!
Nice thank you so much for that! Finally a working custom recovery for us, and much better than TWRP lol
I spotted some bugs anyway
1. We can't modify the splashscreen
2. We can't select our sd card for backup or even mount it (i'm still in fat32 (from previous LOS installation and in stock rom)
Hey, thanks a lot for that ken442266 !
I have 2 questions:
* Does it work if I updated my Xperia 5 ii with Android 11 ?
* When you write SD card isn't recognized, is it whatever possible to backup a rom backup from internal memory?
* Is it possible, with OrangeFox recovery, to root your Xperia 5 ii with Magisk onto Android 11 stock rom?
Thanks a lot for your help,
Yoannjap
Yoannjap said:
Hey, thanks a lot for that ken442266 !
I have 2 questions:
* Does it work if I updated my Xperia 5 ii with Android 11 ?
* When you write SD card isn't recognized, is it whatever possible to backup a rom backup from internal memory?
* Is it possible, with OrangeFox recovery, to root your Xperia 5 ii with Magisk onto Android 11 stock rom?
Thanks a lot for your help,
Yoannjap
Click to expand...
Click to collapse
Hi Yoannjap,
I can answer all three of these from my personal experience.
1. This works for me on Ken's Pixel Experience 11 Rom, which is android 11 based. However, it is using an android 10 vendor as a basis. I have yet to test it over Android 11 from stock.
2. You can do backups to internal storage, my SD card doesn't work yet and I was able to do that just fine.
3. Magisk should be flashable, but Magisk currently doesn't work with Stock android 11. I have it working with Pixel Experience 11 however.
Bootloop after installing the patched boot image on Android 11 on Sony Xperia 5 II (needed system_ext removed from fstab) · Issue #3752 · topjohnwu/Magisk
ISSUE DESCRIPTION After trying to install Magisk with the patched magisk_boot.img from the latest Canary (and Beta) version of the Manager, the device is unable to boot and goes into the bootloop. ...
github.com
Here is an issue a few other user's have commented on about Magisk on Stock A11
Jayram2000 said:
Hi Yoannjap,
I can answer all three of these from my personal experience.
1. This works for me on Ken's Pixel Experience 11 Rom, which is android 11 based. However, it is using an android 10 vendor as a basis. I have yet to test it over Android 11 from stock.
2. You can do backups to internal storage, my SD card doesn't work yet and I was able to do that just fine.
3. Magisk should be flashable, but Magisk currently doesn't work with Stock android 11. I have it working with Pixel Experience 11 however.
Bootloop after installing the patched boot image on Android 11 on Sony Xperia 5 II (needed system_ext removed from fstab) · Issue #3752 · topjohnwu/Magisk
ISSUE DESCRIPTION After trying to install Magisk with the patched magisk_boot.img from the latest Canary (and Beta) version of the Manager, the device is unable to boot and goes into the bootloop. ...
github.com
Here is an issue a few other user's have commented on about Magisk on Stock A11
Click to expand...
Click to collapse
Thanks a lot for your response
1. Ok, I am very looking forward an OrangeFox recovery fully based on an Android 11 stock ROM (included a A11 vendor partition.
2. I also hope someday a version of OrangeFox could arrive with microSD compatibility...
3. finally, thanks for the link of the bootloop of Android 11 when you try installing MagiSK.
Good luck,
Yoannjap
However, do you know if OrangeFox R11 version works with Android 11 ROM on Xperia 5 II?
And sorry I asked you the same on your Kernel patched with Magisk.
Could you help me and other users, giving the complete step by step process from unlocking phone to get Orangefox and this new Kernel with Magisk installed on it?
Yoannjap said:
However, do you know if OrangeFox R11 version works with Android 11 ROM on Xperia 5 II?
Click to expand...
Click to collapse
It works with Pixel Experience 11, although its uses a Q vendor as a basis.
Yoannjap said:
And sorry I asked you the same on your Kernel patched with Magisk.
Could you help me and other users, giving the complete step by step process from unlocking phone to get Orangefox and this new Kernel with Magisk installed on it?
Click to expand...
Click to collapse
There's already a guide by @Miustone for unlocking and flashing firmwares and images: https://forum.xda-developers.com/t/...g-with-magisk-and-flashing-firmwares.4177209/
Process is still the same.
any chance of getting the device trees for this build?
I tried to flash this rec on 58.1.A.5.159 /A11 /xperia 5 ii.
Fortunately, it can run normally and there is no boot loop.
this rec still can manage magisk modules on A11.
However i found two issues:
1. The background theme does not work properly on A11.
2. Like running on Android 10, this rec resolution seems a bit wrong.
Thanx for sharing,man! is there anything new updates for A11 stock rom 222? Tried Orange Fox 10R, not working on my AS52 . Issued as mount problem, cant find device and so on.Any suggestions? if i want to install Los u posted before how do i do? Get lower version stock rom first or wait for new recovery supported?Many thanx
Does anyone have a mirror? The GitHub repository is no longer available.
This custom recovery it's working on xperia 5 ??
This custom recovery it's work on xperia 5 ??
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
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.