What happens when you try to dirty flash Omni 6 with TWRP 3.0.2?3.0.2-0 has problem installing OMNI 6 with dirty flash and preserving gapps. just FYI.
3.0.0-0 works just fine.
Recovery.log or it didn't happen [emoji6]
What happens when you try to dirty flash Omni 6 with TWRP 3.0.2?3.0.2-0 has problem installing OMNI 6 with dirty flash and preserving gapps. just FYI.
3.0.0-0 works just fine.
What happens when you try to dirty flash Omni 6 with TWRP 3.0.2?
Recovery.log or it didn't happen [emoji6]
I know it's really hard to believe
It flashes fine with no error, but Gapps FC. btw it does not happen with 3.0.0-0
Well, I was saying in post #657 in this thread that 3.0.2-0 and 3.0.0-1 were having SELinux issues. 3.0.1-0 is likely to have the same problems but I didn't check it.
- just uninstall the twrp app should do the trick. (Meaning you can only use twrp in recovery mode)...
This is wear things get confusing. The flash took. I wiped what I was suppose to.....eventually I wiped EVERYthing (after 8 attempts). When I boot into Recovery I have v3.0.2-0. When I boot into the System I have v2.8.4.0.
I just booted back into recovery and TWRP v3.0.2-0 shows up on the screen that says, "Unmodified System Partition" and swipe to allow modifications.
I have done this over and over. I am hoping someone here can tell me what I am doing wrong.
My other option would be to restore my Titanium backup, and try installing TWRP some other way.
Two more questions question: after fixing TWRP, can I restore my backup to get my apps back?
Now would be a good time to install a custom ROM that is STABLE, and I can do fun things with. I have read many reviews. Is there a custom ROM that is fun, stable and would upgrade my nexus to marshmellow or nougat - and have all my features work. I need my camera.
Thank you,
LoriAnn - the new girl
------------------------- just uninstall the twrp app should do the trick. (Meaning you can only use twrp in recovery mode)
- yes you can restore your apps
- if you want a very stable ROM, stick to KitKat. And forget about Nougat as the camera is not working on any of them ATM.
Probably you have inadvertently flashed the old recovery in system partition... No big deal, flashing a good rom from TWRP 3.0.2.0 will straighten things up.------------------------
Yes....I was always in recovery mode. TWRP would switch back and forth between versions. Now I am wondering if I could have two versions in my internal memory. I am going into file explorer to see if I can see anything.
Is it possible to have two versions of TWRP in internal memory......would it be on the SD Card portion or in the System partition? I will explore and see what I can find.
Isn't KitKat very old? I had Manta.....which I liked but I wanted to try flashing a custom ROM. I flashed aosp with khaon kernel..........
but i will put this in another thread.
ANYWAY, after I flashed the ROM - when I go into recovery I have TWRP v.3
Thank you for replying!!
I just got one of these and unlocked the bootloader then rooted and flashed the latest TWRP. I'm having a issue with making backups. It's just not making them. It said it was backing up and completed but when I look on the internal memory there is no TWRP folder with a backup. There is a file only named TWRP and says 0b. Should I roll back to 3.0.1?
Thanks for any replies.
I've seen that happen sometimes: check /data/media/TWRP (as root or booted under TWRP).I just got one of these and unlocked the bootloader then rooted and flashed the latest TWRP. I'm having a issue with making backups. It's just not making them. It said it was backing up and completed but when I look on the internal memory there is no TWRP folder with a backup. There is a file only named TWRP and says 0b. Should I roll back to 3.0.1?
Thanks for any replies.
Sent from my Nexus 10 using Tapatalk
Thank you. It was under "data/media/0"I've seen that happen sometimes: check /data/media/TWRP (as root or booted under TWRP).
Sometimes, TWRP puts its directory there instead of /data/media/0/TWRP.
I've never found out why
If that's the case, it's okay to move the directory to its right location and symlink the bad location.
Has anybody tried to do a restore with TWRP 3.1 yet? 3.1 installed without issue and made a back-up without issue. However, when attempting to restore using 3.1 it is taking a long, long time. Previous version of TWRP did not take this long. Also, experiencing the same long time for restore on my Nexus 9. So just curious if it is just me or others also.
What are advantages of enabling rm -rf instead of formatting ? Thanks
sourceWhat's new in 2.6.3.0:
- Proper backup and restore of SELinux contexts (thanks to Tassadar)
- Pull in some ROM information for backup name generation
- Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
- Add 1200x1920 theme (thanks to Tassadar)
- A few other fixes and tweaks
What's new in 2.6.1.0:
- Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
- Initial support for f2fs file system formatting (Moto X)
- Update SuperSU install for 4.3 ROMs
- Fixed a permissions bug on files created during backup
- Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
- Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
- Ignore lost+found folder during backup and size calculations
- Various other minor bug fixes and tweaks