Hey there,
a few days ago I received my new OP3T.
Cause I don't really like to stock OxygenOS I installed TWRP, wiped system, dalvik cache and cache and flashed the Ressurection Remix (RR) v5.8.0 and the Open GApps mini Pack for Android 7.1 (ZIP over TWRP).
The installations wen't without any problem, but now when I'm trying to reboot into RR it always just sends me into TWRP again.
I also tried to reinstall the stock OxygenOS (again without any errors while installing) but still, RR or OxygenOS won't boot and I'm always just going back into TWRP.
After a bit of googling I also found this post https://forum.xda-developers.com/showthread.php?t=2451696 (although my problem didn't occur because of an OTA update) and tried to execute the commands on the TWRP Terminal and the ADB Terminal,
but the commands always return "dd: can't open '/dev/block/platform/msm_sdcc.1/by-name/fota': No such file or directory" and "dd: can't open '/dev/block/platform/msm_sdcc.1/by-name/misc': No such file or directory".
I don't really now what else I could try, therefore I hope anybody here is able to help me.
Thanks in advance!
Ok, fixed it by using this recovery tool https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
It restores everything to stock. Afterwards I've been able to just flash RR again and it worked like a charm.
did you had to use the dm-verity and forced encryption disabler ?
jackgreyhat said:
did you had to use the dm-verity and forced encryption disabler ?
Click to expand...
Click to collapse
No, the dm-verity disabler is only needed if you wan't to disable the forced device encryption of OxygenOS (RR has no forced encryption therefore I didn't need to use the disabler). After resetting everything to stock with the mentioned tool I just flashed RR with TWRP again and it worked.
I have no idea what caused the problem in the first place.
Hello out there,
my problem is a bit annoying. Everything is fine if I use my OP3T with Oxygen (4.0.3) and TWRP (3.0.3-1). But I want to use LineageOS with TWRP and cant, because my TWRP isnt working after flashing lineage.
"Normal"-Setup:
- TWRP 3.0.3-1
- Oxygen 4.0.2 or 4.0.3 (doesn't matter)
- supersu 2.79
- Encrypted Device
"Lineage"-Setup:
- TWRP 3.0.3-1
- lineageOS (lineage-14.1-20170214-nightly-oneplus3-signed.zip OR lineage-14.1-20170208-nightly-oneplus3-signed.zip - tried both, doesnt matter)
- supersu 2.79
- openGApps for 7.1 nano
- Encrypted Device
My Problem is, that I can boot up lineage and use it, but if I reboot into my TWRP to flash something or make some Backups, it asks for my encryption-passphrase, it says it is okay and boots into the twrp main-windows. After that I can't touch anything (stuck in mainmenu) and after a few seconds it results into a black screen (plus white LED) and I am forced to reboot the device. After that reboot I have to reconfigure lineage (seems to loose data).
Does anyone have an idea how to fix this annoying "bug"?
Thank you very much!
Atomique
EDIT: I found that Thread after searching for a issue like that in the lineageOS official Thread - I will try this and report! - Thank you! https://forum.xda-developers.com/on.../recovery-official-twrp-oneplus-3-3t-t3543391
I had the exact same problem when I hab LineageOS installed! It would always lose all its data. After flashing and reflashing a hundred times, I ended up reverting my OP3T back to stock using a OnePlus forum guide (I'm a new user, so I can't post the link). I am now back to OOS 4.0.3 but can't even get SuperSU to work. Whenever I flash it (with or without the dm-verity fix) the phone is stuck booting forever.
I found the post you linked to aswell but haven't tried flashing LineageOS using the new TWRP. But I can tell that the new version doesn't help rooting OOS...
Did you have any luck flashing LineageOS by now?
Edit: With the newest Lineage Version I always get an error when trying to flash it. Do you have the same problem? The nightly from two weeks ago seems to work better.
Use latest TWRP 3.0.4.1
nitinvaid said:
Use latest TWRP 3.0.4.1
Click to expand...
Click to collapse
That's what I'm doing... Could the dm-verity be a problem? There are two versions, one with opt and one with force in the name.
Thank you for your replies! The link (TWRP 3.0.4-1) worked like a charme!
@Tafelbomber: I would recommend you to start from scratch. But please be warned: you will loose your data! Make a backup first!
1. Delete everything with fastboot -w
2. Flash the recovery noted in my first post with fastboot flash recovery <twrp-filename.img>
3. Optional: Restart into the TWRP and flash the OOS 4.0.3 to make sure that you have a clean OS installed befor flashing lineage
4. Flash lineage OS + additional ZIPs (like supersu, betterbatterystats, Gapps etc)
5. Clean Dalvik and Cache!
6. Reboot and have fun. --> Sometimes you get problems with the encryption chain (Red Error --> in my case the fastboot -w did it for me)
Good luck - I will close this thread - thanks again for your help!
Atomique
EDIT: I want to close this thread, but I don't know how.
Can anyone help me with the steps to update to Android Oreo (OOS 5) from OOS 4.5.1 retaining root?
Below are the current setup of my phone
Rooted - Yes (Magisk version 14.0)
Recovery - TWRP version 3.1.1-2
Current Rom - Stock OOS 4.5.1
I haven't had any problems in updating earlier but now when I try to flash the full oreo rom from TWRP, I am getting error 7.
Below are the steps I followed.
Downloaded the full OTA zip.
Rebooted to recovery.
Unistalled Magisk.
Tried to flash the Oreo OTA zip. At this point TWRP showed error 7.
Reinstalled Magisk and rebooted to system.
Phone is working fine.
you need to use latest twrp for oreo, for example blue spark version, search for it on xda...
Follow this guide here:
https://forums.oneplus.net/threads/how-to-install-oos-5-0-over-rooted-4-5-1.684519/#post-17134194
It's exactly what you need.
All Oreo ROM threads clearly state under the "Instructions" heading, that you need either AkhilNarangs Modified TWRP or Blu_Sparks TWRP V50. Using stock TWRP would result in an error.
If the error may still persist, try flashing a different firmware.
Just to get some more clarity.
I have the original OTA full zip. Should I download the zip file from your thread?
Can I install the custom version of TWRP using the official TWRP app? I am bit confused on how to install it.
Is it important that I should use Magisk 14.3 or will v 14 have the same effect?
Hey there,
I can tell you how I have done it yesterday (successfully).
1. Update TWRP - I prefer blu sparks version 8.52 (Link: https://forum.xda-developers.com/devdb/project/dl/?id=27225); you can do it by using your installed TWRP Version (Install .img)
2. Dirty flash OOS 4.5.1 again (to remove root / magisk) - once finished DO NOT reboot into system, reboot into Recovery/TWRP to verify the new version and afterwards to system
3. flash OOS 5.0 (Oreo) - dirty flash is okay
4. flash magisk Version 14.3
These are the steps I have followed yesterday and all is running perfect and without any problems.
BR
Which recovery is mentioned in this linked discussion resp. in the linked download? Is it blu_spark TWRP?
Regards
Clark
This worked perfectly for me.
Glad to hear that everything is good ?
I did the same and I was suddenly encrypted and no chance to get my data back. Still forcing clean my phone because I cannot format the device. I get always an error message in TWRP like: unable to format to remove encryption
I go crazy...
Enter recovery and wipe data and then cache.
Then reflash the rom and probably you will be good to go.
It's been a year and a half since last time i had messed around with custom roms.
I am currently on stock 8.0 Oxygen OS. What would be the steps to install OmniROM 8.1?
I'm thinking the following.
1. unlock bootloader
2. Flash TWRP
3. Root
4. Wipe/format
5. flash OMNI rom 8.1?
Do I first need to update to 8.1 somehow?
You may want to update to the latest Open Beta firmware, which you can get the standalone files from here ( https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166)
Flash this before flashing the ROM.
Also you may want to flash the Root method after flashing the ROM. Your best choice is Magisk, since it's getting ready updates and it has many extra features. SuperSU is old and not done by chainfire anymore, so don't flash SSU.
Also remember to wipe these specific partitions:
System
Data
Cache
Dalvik Cache.
I'm not sure by what you mean by "Updating to 8.1" as OOS is still on 8.0, even the Open Beta's. Flash the latest Firmware from Recovery and you should be good go.
Also, don't forget to grab NezorFlame's unofficial GAPPS, since OpenGAPPS still hasn't been updated to 8.1.
(https://sourceforge.net/projects/unofficial-opengapps-8-1/files/arm64/)
Also just keep in mind, unlocking your bootloader will wipe your internal storage. This is a security feature and cannot be bypassed.
IMO, there are better ROMs than Omni. You should try Z-Unleashed or Resurrection Remix 6.0.0. They're the best ROMs with the best customization and usage per user for now.
Good luck, and happy flashing!
You don't need to wipe data if you're going to unlock bootloader, since as mentioned earlier, unlocking BL deletes all of yor data.
Dalvik Cache isn't used anymore (we are on ART now), so no need to wipe it separately, it even reside in /data partition.
Also no need to flash firmware files if you're on OOS 5.
ROM, GApps and Magisk will be enough.
przemcio510 said:
Also no need to flash firmware files if you're on OOS 5.
Click to expand...
Click to collapse
Well, most of the ROMs recommend Open Beta 22 firmware, since this is the FW the developers build the recently updated ROMs on. He may experience issues if he's on OOS 5.0 fw.
Hey,
So after a lot of observation and reading I think LOS 17.1 seems stable enough to be used for a daily driver.
Right now I am on the normal stock ROM, without any modifications, no TWRP, no root whatsoever.
However, I have unlocked the bootloader a few months ago, so that's done already.
Current state of the phone:
Code:
MIUI version: 11.0.1.0 (QFKMIXM) - Is this the global version?
Device model: Mi 9T Pro (128GB, 6GB RAM)
I want to install TWRP, I want to root the phone, I want to install all needed modules for a proper camera etc, I want to install LineageOS 17.1 (latest build) and lastly I want to install Immensity Kernel (latest build) because I have heard it works well with LOS and provides lots of battery improvements.
I did lots of tinkering with my phone a couple years back, but I haven't done so in a while, and neither have I done anything with this device, so to make sure I am not breaking anything I decided its the best to ask here.
What steps do I have to provide in which order? Can someone provide my a detailed explanation of all the needed steps?
Also, can I install MicroG on it, or do I have to use GApps?
My guess is, first TWRP and root, then ROM and then kernel?
Also, I have read about some issues with Magisk and Android 10, is that still a problem, or is that solved by now?
Anything else I need to look out for?
Cheers
KuroRyu said:
Hey,
So after a lot of observation and reading I think LOS 17.1 seems stable enough to be used for a daily driver.
Right now I am on the normal stock ROM, without any modifications, no TWRP, no root whatsoever.
However, I have unlocked the bootloader a few months ago, so that's done already.
Current state of the phone:
I want to install TWRP, I want to root the phone, I want to install all needed modules for a proper camera etc, I want to install LineageOS 17.1 (latest build) and lastly I want to install Immensity Kernel (latest build) because I have heard it works well with LOS and provides lots of battery improvements.
I did lots of tinkering with my phone a couple years back, but I haven't done so in a while, and neither have I done anything with this device, so to make sure I am not breaking anything I decided its the best to ask here.
What steps do I have to provide in which order? Can someone provide my a detailed explanation of all the needed steps?
Also, can I install MicroG on it, or do I have to use GApps?
My guess is, first TWRP and root, then ROM and then kernel?
Also, I have read about some issues with Magisk and Android 10, is that still a problem, or is that solved by now?
Anything else I need to look out for?
Cheers
Click to expand...
Click to collapse
Make sure you are in the latest version of MIUI first.
For TWRP flash the latest Mauronofrio TWRP, he has the official TWRP, but his unofficial, latest version is probably a better option at its a little bit more up to date.
Once you've flashed TWRP you will need to boot immediately in to TWRP without allowing the phone to boot into MIUI, otherwise the phone will detect that recovery had been modified and will restore stock recovery.
When you've booted into TWRP, format data (needs to be format and not only wipe), then wipe cache and dalvik.
Reboot into TWRP, to ensure that the newly formatted data partition is correctly mounted.
Now flash lineage and a GApps package. I've only used Open GApps Pico, but I believe microG should be OK. If you use Open GApps it is still in beta and packages larger than the micro package are likely to cause issues, so stick with micro, pico or nano. (For clarification, micro G is a GApps package, what you are really asking is do you need to use Open GApps or not)
The latest Magisk is fine now. It is recommended to boot into LOS first at least once before flashing Magisk. I can't remember the details but sometimes you may get issues if you flash Magisk after flashing a ROM, without booting to the ROM first. You may be fine if you don't boot the ROM first, but since I've forgotten the reasons and can no longer find it, I now boot the ROM before flashing Magisk, just to be safe.
From here, you should be OK to flash different kernels, personally I've never felt the need to, as I'm happy with the performance of things as they are. My battery life is similar to what it was on stock MIUI. If you want to try kernels other than Immensity, just double check first that it is for AOSP ROMs. There are some kernels that have been created that are only compatible with Stock MIUI.
For the camera, I believe the latest advice for ANX Cam is still version 158 along with the 48MP fix for Q ROMs. There are a few later versions, which are not appropriate for this phone. I don't believe there has been a later version for this phone.
Edit: just noticed your question in the quote.
You have the global version of the phone. AFAIK 11.0.1 is still the latest version of the global version of MIUI.
Robbo.5000 said:
Make sure you are in the latest version of MIUI first.
For TWRP flash the latest Mauronofrio TWRP, he has the official TWRP, but his unofficial, latest version is probably a better option at its a little bit more up to date.
Once you've flashed TWRP you will need to boot immediately in to TWRP without allowing the phone to boot into MIUI, otherwise the phone will detect that recovery had been modified and will restore stock recovery.
When you've booted into TWRP, format data (needs to be format and not only wipe), then wipe cache and dalvik.
Reboot into TWRP, to ensure that the newly formatted data partition is correctly mounted.
Now flash lineage and a GApps package. I've only used Open GApps Pico, but I believe microG should be OK. If you use Open GApps it is still in beta and packages larger than the micro package are likely to cause issues, so stick with micro, pico or nano. (For clarification, micro G is a GApps package, what you are really asking is do you need to use Open GApps or not)
The latest Magisk is fine now. It is recommended to boot into LOS first at least once before flashing Magisk. I can't remember the details but sometimes you may get issues if you flash Magisk after flashing a ROM, without booting to the ROM first. You may be fine if you don't boot the ROM first, but since I've forgotten the reasons and can no longer find it, I now boot the ROM before flashing Magisk, just to be safe.
From here, you should be OK to flash different kernels, personally I've never felt the need to, as I'm happy with the performance of things as they are. My battery life is similar to what it was on stock MIUI. If you want to try kernels other than Immensity, just double check first that it is for AOSP ROMs. There are some kernels that have been created that are only compatible with Stock MIUI.
For the camera, I believe the latest advice for ANX Cam is still version 158 along with the 48MP fix for Q ROMs. There are a few later versions, which are not appropriate for this phone. I don't believe there has been a later version for this phone.
Edit: just noticed your question in the quote.
You have the global version of the phone. AFAIK 11.0.1 is still the latest version of the global version of MIUI.
Click to expand...
Click to collapse
Do I also need the force encrypt file? Some people mention it needs to be flashed too?
How do I properly install twrp? I boot into fastboot mode, and then I can flash it, I assume?
In the thread it also states that one should first flash vbmeta?
EDIT: Ok, I flashed vbmeta and twrp, booted into twrp, formated data and wiped dalvik and cache.
Now should I flash LOS next and then gapps ..? Which GApp package is the right one for 17.1? It is not linked in the LOS thread?
I've read that some people had issues when flashing the wrong gapps package
EDIT2: Ok, so far I have persisted TWRP and installed magisk. I flashed LOS 17.1 (latest build) and booted into it. I did not flash gapps yet as I dont know which gapps package to use. Also I would prefer to use microG if possible, but I dont think its possible to install it easiely? If it is, please let me know.
Now, the issue is, for some reason after the clean install of LOS17.1 I still see google apps like google drive (remember, I did not flash gapps). This shouldn't be the case? I did format data and cleared dalvik and cache, so it is a bit weird that this happens...
Also I constantly get "android.process.media keeps stopping" .. I assume that is because some applications try to access google service, which are not correctly available? What did I do wrong?
So my questions are:
1) Is it possible to use microG (opensrc implementation of google services), rather than gapps? If so, how?
2) If I need to use GApps, which one to flash?
3) Why were google apps still present on my device after flashing and formatting data ..?
KuroRyu said:
Do I also need the force encrypt file? Some people mention it needs to be flashed too?
How do I properly install twrp? I boot into fastboot mode, and then I can flash it, I assume?
In the thread it also states that one should first flash vbmeta?
EDIT: Ok, I flashed vbmeta and twrp, booted into twrp, formated data and wiped dalvik and cache.
Now should I flash LOS next and then gapps ..? Which GApp package is the right one for 17.1? It is not linked in the LOS thread?
I've read that some people had issues when flashing the wrong gapps package
EDIT2: Ok, so far I have persisted TWRP and installed magisk. I flashed LOS 17.1 (latest build) and booted into it. I did not flash gapps yet as I dont know which gapps package to use. Also I would prefer to use microG if possible, but I dont think its possible to install it easiely? If it is, please let me know.
Now, the issue is, for some reason after the clean install of LOS17.1 I still see google apps like google drive (remember, I did not flash gapps). This shouldn't be the case? I did format data and cleared dalvik and cache, so it is a bit weird that this happens...
Also I constantly get "android.process.media keeps stopping" .. I assume that is because some applications try to access google service, which are not correctly available? What did I do wrong?
So my questions are:
1) Is it possible to use microG (opensrc implementation of google services), rather than gapps? If so, how?
2) If I need to use GApps, which one to flash?
3) Why were google apps still present on my device after flashing and formatting data ..?
Click to expand...
Click to collapse
There is no need to flash force encrypt files or vbmeta.
I have never used MicroG so couldn't give any answers about that, however Open GApps are open source too. For android 10 it is still in beta. The beta files can be found here https://sourceforge.net/projects/opengapps/files/arm64/beta/20191209/. Pico is the smallest package that gives Google Play, personally I recommend going with that, then installing any other Google stuff from the play store, should you want them.
No idea why you would be seeing Google apps. I can only suggest formatting data again in TWRP.
If that doesn't work I would start again. Fastboot flash the latest MIUI 11.0.1 global ROM, boot into it once, there is no need to go through the set-up. Then go through the steps given before.
This time don't flash vbmeta, it is not needed.
The fastboot ROM can be found here http://bigota.d.miui.com/V11.0.1.0....M_20191111.0000.00_10.0_global_11d3a1700a.tgz
Edit:
Having seen some of your other posts, I'll give you some more info.
vbmeta is mainly used to persist TWRP. However flashing Magisk will persist TWRP and flashing a custom ROM will persist TWRP. You would only need to flash vbmeta if you wanted to stay on MIUI and not use Magisk. (There are other uses for vbmeta, but you don't need them, so I'll not go into them)
Is widevine L1 available on the ROM? Is the FOD working well?