Hey there,
I've been using an old beta of OmniROM Oreo for months now, but wanted to try the 9.0 ROMs that are out there. I followed the instructions in both the Lineage and Omni threads and updated to the TWRP that's needed, then flashed the chiron firmware that's needed, then wiped all and formatted data, then installed the ROM. When I went to flash the rom, TWRP told me that my filesystem was read only and suggested I leave it that way for security. I said OK, everything installed fine, but when it restarts it fails to boot the OS and then reboots into recovery (TWRP). I have tried flashing the firmware, different ROMs, etc., but not getting anywhere.
I'm assuming this is related to leaving the filesystem read-only, but not really sure.
Anyone know what I did wrong? And how to fix it?
Thanks
Related
I got my op3 phone loaded up with twrp version 3.0.2-1 but many errors occurred after I flashed this version.
Current problems on my phone right now:
-"The dm-verity is not started in enforcing mode" occurs every time I turn on the phone.
-Twrp won't read any of my files inside the "sdcard" folder wether it's just regular folder, .zip files, and even .img files.
-It also looks like only 1 version works of twrp works on my phone right now since any twrp versions after 3.1.0 causes the twrp program to froze and doesn't completely move past welcome screen of twrp.
I believe I had the same problem. Contact OnePlus on their support page. In a chat support window, tell the operater about your problem, and ask for an appointment with a level 2 technician. They should schedule you an appointment with a technician who should be able to wipe your phone no matter what state/condition it's in. They fixed my phone in a matter of minutes. But PLEASE, try to remember to be respectful and co-operative, it usually gets you better service no matter who you are dealing with.
For dm - verity problem, it's not a problem tough... Just a security breach as seen by Google.
BTW here is the fix...It's easy , follow the thread :
https://forum.xda-developers.com/oneplus-3/how-to/fix-easy-method-removing-dm-verity-t3544339
Can't comment on twrp as I'm on the 3.0.2-1, haven't tried 3.1. Hope it helps, Thanks!
Use TWRP 3.0.4-1. 3.0.2 can't decrypt internal storage, at least not on mine it couldn't.
Also if you have f2fs file system, TWRP takes a loooooong time to boot. Just wait, even though it seems hung. Takes several minutes. If you have ext4, it's quick. Use the app 'Diskinfo' to check
I had TWRP 3.1 and it would not do OTA of lineage, it would wipe the device when I tried and would not restore backed ROMs, stay away from TWRP 3.1. So, i went back to 3.0.4.1 via fastboot. My suggestion is flash the stock recovery from Oxygen 3.8 marshmallow (this can be found in the archived OnePlus 3 tool kit on XDA) and then sideload the stock marshmallow Oxygen 3.2.8 (download from OnePlus support page) and start all over.
mremghz said:
I had TWRP 3.1 and it would not do OTA of lineage, it would wipe the device when I tried and would not restore backed ROMs, stay away from TWRP 3.1. So, i went back to 3.0.4.1 via fastboot. My suggestion is flash the stock recovery from Oxygen 3.8 marshmallow (this can be found in the archived OnePlus 3 tool kit on XDA) and then sideload the stock marshmallow Oxygen 3.2.8 (download from OnePlus support page) and start all over.
Click to expand...
Click to collapse
That doesn't make sense..
The latest recovery works fine here, atleast the official one. If you are in F2fs and encrypted keep in mind it takes a long long time since F2fs is really bad at this.. Depending in how full your internal storage is it can take up to 10 minutesm
Twrp 3.0.4.1 or
3.1.0 x v.26 blu_spark.
To get OTA you need to be stock, only Oos official stuff.
I do have my oneplus 3 formatted as f2fs, but it is not encrypted. I don't know what happened to it when I tried to do an update with lineage os it basically factory reset the phone (and no I didn't wipe anything but the cache) and it would not install any zips from my internal sd card. I had to go back to fastboot and reflash TWRP 3.0.4.1 recovery. Then I wiped the device and reinstalled lineage, now it works perfectly fine.
They are lineage nighty OTA updates.
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Does anyone know what the problem could be?
I would suggest you clean flash OOS first before going to Freedom.
I think RR is based on Lineage OS while Freedom is based on stock OOS.
Envoyé de mon iPhone en utilisant Tapatalk
Wrong forum.
danecr7 said:
I would suggest you clean flash OOS first before going to Freedom.
I think RR is based on Lineage OS while Freedom is based on stock OOS.
Envoyé de mon iPhone en utilisant Tapatalk
Click to expand...
Click to collapse
RR is based on CM. I'm just scared to flash OOS in case it goes wrong because stock OOS will overwrite TWRP with its stock recovery and then I'll be screwed because I'll have no way to restore from a backup if it goes wrong
RazorBlade123 said:
Wrong forum.
Click to expand...
Click to collapse
Yeah I thought it seemed a little out of place but I don't know where to post it? Is there a general questions forum?
evilkitty69 said:
RR is based on CM. I'm just scared to flash OOS in case it goes wrong because stock OOS will overwrite TWRP with its stock recovery and then I'll be screwed because I'll have no way to restore from a backup if it goes wrong
Click to expand...
Click to collapse
I don't think that there is a risk in flashing stock OOS. But if the custom recovery is overwritten then flash it back, your backup files are stored in your internal memory and unless you wipe it you are safe.
danecr7 said:
I don't think that there is a risk in flashing stock OOS. But if the custom recovery is overwritten then flash it back, your backup files are stored in your internal memory and unless you wipe it you are safe.
Click to expand...
Click to collapse
Even when I tried flashing other CM based ROMs, including ones I'd flashed before, it failed, only flashing RR actually worked. I don't know why this is the case but I'm not sure flashing OOS without knowing what the issue is, is the solution because if I lose TWRP there's no telling whether I'll be able to flash it back in fastboot if the phone isn't working properly
evilkitty69 said:
Even when I tried flashing other CM based ROMs, including ones I'd flashed before, it failed, only flashing RR actually worked. I don't know why this is the case but I'm not sure flashing OOS without knowing what the issue is, is the solution because if I lose TWRP there's no telling whether I'll be able to flash it back in fastboot if the phone isn't working properly
Click to expand...
Click to collapse
I once flashed RR based on android 7.1.1 and because I did not like it very much I wanted to go back to Freedom but at that time it was based on android 7.0.1 thus I was unable to boot. Maybe you are facing the same issue. But in my case I hardbricked my device and used the unbricking tool from OP3 forum.
If you download the latest OOS zip file you can flash it through TWRP and you won't lose you custom recovery.
danecr7 said:
I once flashed RR based on android 7.1.1 and because I did not like it very much I wanted to go back to Freedom but at that time it was based on android 7.0.1 thus I was unable to boot. Maybe you are facing the same issue. But in my case I hardbricked my device and used the unbricking tool from OP3 forum.
If you download the latest OOS zip file you can flash it through TWRP and you won't lose you custom recovery.
Click to expand...
Click to collapse
All of the ROMs I tried with were android 6.0.1, I'm avoiding touching android 7 because I'm not a fan
The strange thing is that in TWRP under "mount", system is unchecked and it won't stay checked when I reboot or try to flash something and then the flash fails. Strangely however, I can flash RR afresh and it will work but nothing else works
Therefore I don't think OOS would work either
Hello,
Since I got my XT1635-02 in April I have tried to use LineageOS and/ or AOKP. The problem is, when I flash either, I get an endless bootloop.
When I got the phone I:
Unlocked the bootloader
Flashed TWRP - the latest 3.1.1-0
Flashed Lineage ROM
I don't use Gapps - or I'd rather not - but at this stage I have flashed the Pico package
Then flash su-addon.
I've tried different combinations; only flashing LineageOS/AOKP but got the same result.
Stock images work fine for me. I even got to the point where I had to write a little bash script to flash all of the components in the correct order for the RETUS Nougat image.
Last month, by some fluke I got LineageOS to boot. However, I have no idea what I did differently, it just seemed to work that one time. However, I have been living off of that install for about 3 weeks and the OTAs even worked perfectly.
Today I got bored and decided to flash AOKP.
Booted in to TWRP
Wiped Dalvik, Sys, Data, Cache
Flash AOKP
Reboot
Bootloop.
Is there something wrong with my phone or is there something wrong with my process?
Any suggestions welcome. Thank you.
I remember that problem with Razr. Some custom roms were booting fine, some bootlooping.
The first workaround was to flash working one then without reboot flash desired one.
Later we figured out that wiping/formating partitions was the problem. Bootlooping rom couldn't read the file system. Solution was to not wipe or to wipe to the correct file system.
Sent from my XT1635-02 using Tapatalk
I think you may be on to something because I had flashed LineageOS after flashing the stock Nougat image. Still, would like a surefire way to just run a ROM. I've never had this issue on any other device.
I had it on Razr and just started to happen after one CM nightly build. Turned out that devs changed FS.
Last weekend, I decided to flash a new ROM since the one I have been using is no longer being developed. I flashed a LineageOS nightly build because I used to like Cyanogenmod and heard Lineage is a continuation. I do like the ROM overall, but for some reason it encrypted my phone during install. I did not want it to do this, it just did it without asking me (when I first got my phone, I remember I was having problems with it being encrypted, with my recovery and such).
Is there any way to reinstall LineageOS without it encrypting the phone? If not, how do I decrypt the phone again and get back to basically stock + root? I downloaded the most up-to-date stock 7.1.2 ROM from Google, and was going to just flash that, but it wouldn't let me in TWRP (said the zip was not valid). I also tried rolling back to an older backup (not LineageOS), but the phone never booted.
FYI - I use Linux Mint and have the latest adb/fastboot, and the latest TWRP for Nexus 5x.
Thank you if you can help.
cspctec said:
Last weekend, I decided to flash a new ROM since the one I have been using is no longer being developed. I flashed a LineageOS nightly build because I used to like Cyanogenmod and heard Lineage is a continuation. I do like the ROM overall, but for some reason it encrypted my phone during install. I did not want it to do this, it just did it without asking me (when I first got my phone, I remember I was having problems with it being encrypted, with my recovery and such).
Is there any way to reinstall LineageOS without it encrypting the phone? If not, how do I decrypt the phone again and get back to basically stock + root? I downloaded the most up-to-date stock 7.1.2 ROM from Google, and was going to just flash that, but it wouldn't let me in TWRP (said the zip was not valid). I also tried rolling back to an older backup (not LineageOS), but the phone never booted.
FYI - I use Linux Mint and have the latest adb/fastboot, and the latest TWRP for Nexus 5x.
Thank you if you can help.
Click to expand...
Click to collapse
If you want to flash stock rom you have to flash it via fastboot. The instruction is on the Google download side. But if I remember right you have to wipe everything so make a backup of important data.
If I format my "userdata" with fastboot to get rid of the encryption, do you know if it will delete my ROM backups? I think the encryption is why I'm having trouble going to another ROM from LineageOS. I REALLY wish the ROM would simply ask you before deciding to encrypt the phone. I have no reason to encrypt my phone, and I don't want it encrypted.
ok Im using latest twrp, this occurs with Lineage 17.1 and CrDroid 6.12.
Both install and run perfect, twrp backups run with no errors and restores are fine until it hits the boot animation and just sits there for ever,
thing is do the same process for stock rom and no problems
twrp backup includes boot, system and data
samsungs annoying partition encryption defeated
rooted or not makes no difference
just seems to be the Lineage base roms
Other than that, Lineage roms are fantastic,(especially for freedom from google)
I really hope someone has a fix or tell me what the hell im missing.
Regards Darin