So I'm currently using RennovateICE because it was a super easy magisk install and didn't conflict with anything.
I've been looking at HavocOS and it's looks absolutely amazing. My question is, anyone who's tried it, is it better than the standard OOS and is it stable?
I also haven't flashed roms in a long time, so if I make a backup through TWRP first I can do a full restore of my current system as is if I want to revert back from Havoc OS correct?
Also if anyone can suggest their favorite rom etc I'd love to hear it, really in a mood to mess with my phone now that it's rooted.
DQScott95 said:
So I'm currently using RennovateICE because it was a super easy magisk install and didn't conflict with anything.
I've been looking at HavocOS and it's looks absolutely amazing. My question is, anyone who's tried it, is it better than the standard OOS and is it stable?
I also haven't flashed roms in a long time, so if I make a backup through TWRP first I can do a full restore of my current system as is if I want to revert back from Havoc OS correct?
Also if anyone can suggest their favorite rom etc I'd love to hear it, really in a mood to mess with my phone now that it's rooted.
Click to expand...
Click to collapse
To go back to oos from aosp you have to wipe internal storage because the monthly security patches usually change the encryption, aosp will always be on the most up to date security patch and oos is usually 1-2 months behind. There are ways to force in encryption but you have to wipe internal storage for it anyway, to go from oos to aosp you won't need to wipe internal storage. If you plan on trying a bunch of custom roms I recommend an app called Syncthing to backup your internal storage.
I've used havoc and aosip and I really like the customization of havoc, it's pretty stable for how new this phone is, but there's certain things that make oos better. If you use android auto, wifi calling, or certain streaming apps (most people mention twitch but I have issues with vimeo) then oos is better. Also some people have issues with the phone not being unlocked after installing some Magisk roms.
I've rocked havoc for about 2 weeks and just switched back to oos yesterday to try the new update out. I may try aoscp soon but really oos is pretty awesome especially with the Magisk roms we've got on here.
I feel like havoc has better idle drain than oos, but if I use YouTube music with the screen of oos has quite a bit better battery life, and I use android auto daily so having the stability there is also nice.
explosivequack said:
To go back to oos from aosp you have to wipe internal storage because the monthly security patches usually change the encryption, aosp will always be on the most up to date security patch and oos is usually 1-2 months behind. There are ways to force in encryption but you have to wipe internal storage for it anyway, to go from oos to aosp you won't need to wipe internal storage. If you plan on trying a bunch of custom roms I recommend an app called Syncthing to backup your internal storage.
I've used havoc and aosip and I really like the customization of havoc, it's pretty stable for how new this phone is, but there's certain things that make oos better. If you use android auto, wifi calling, or certain streaming apps (most people mention twitch but I have issues with vimeo) then oos is better. Also some people have issues with the phone not being unlocked after installing some Magisk roms.
I've rocked havoc for about 2 weeks and just switched back to oos yesterday to try the new update out. I may try aoscp soon but really oos is pretty awesome especially with the Magisk roms we've got on here.
I feel like havoc has better idle drain than oos, but if I use YouTube music with the screen of oos has quite a bit better battery life, and I use android auto daily so having the stability there is also nice.
Click to expand...
Click to collapse
This is exactly the kind of comment I was hoping for. Is the customization and feel of Havoc less than standard OOS? Just looking at all of the features it looks kind of mind blowing how much is in Havoc, but the screen shots don't really show off any of the custom features. Is there anything (on the customization end) that really draws you to Havoc.
For example, in renovateice I have the battery bar up top and a couple of other little things to improve overall visuals around the phone.
Also how does HavocOS OTA's work? It says it supports OTA's in the description.
And my last question, just to refresh my memory. When I do a nandroid backup, exactly what options do I need to check to make a complete backup of my current system to restore? So that my phone is 100% how it is right now as am typing this out.
DQScott95 said:
This is exactly the kind of comment I was hoping for. Is the customization and feel of Havoc less than standard OOS? Just looking at all of the features it looks kind of mind blowing how much is in Havoc, but the screen shots don't really show off any of the custom features. Is there anything (on the customization end) that really draws you to Havoc.
For example, in renovateice I have the battery bar up top and a couple of other little things to improve overall visuals around the phone.
Also how does HavocOS OTA's work? It says it supports OTA's in the description.
And my last question, just to refresh my memory. When I do a nandroid backup, exactly what options do I need to check to make a complete backup of my current system to restore? So that my phone is 100% how it is right now as am typing this out.
Click to expand...
Click to collapse
The customization of havoc is far superior to oos even with the Magisk modules, the modules get things pretty dang close, but there's a few things havoc has that probably won't be implemented into oos. When I was on havoc I really liked the customizations for the quicksettings, and a lot of people really like the always on display, I'm more of an ambient display person and oos has a bit better implementation of that.
Havoc has battery bar as well, and the color can be changed and a gradient effect can be added. Really the only thing that I wanted that I could get on oos is the dashed circle with percentage in it, but that's only because I didn't spend enough time trying to figure out how to get EdXposed to work stabily.
I don't think the ota system is implemented yet because they are still unofficial builds, but it's just an option in the setting, as of now you'll have to dirty flash in twrp.
The nandroid backup hopefully someone else can answer because I haven't done one of those since my nexus 5 probably, usually I just use titanium backup and set everything up from scratch.
Again tho, if you want to go from aosp back to oos you'll need to wipe the internal storage, I'd recommend backing up your whole sd card to your pc in case anything happens.
If you want some video guides there's a guy on YouTube called koogly who does things on the op6t, but everything is basically the same because they're both relevant a/b system devices.
Edit: I never had issues with stability or random reboots on either havoc or oos, a couple reasons I decided to go back is because if you turn nfc on on havoc it turns on and off until you reboot, the alarm volumes are much quieter, and the vibration strength in the 7/5 build is turned way up.
explosivequack said:
The customization of havoc is far superior to oos even with the Magisk modules, the modules get things pretty dang close, but there's a few things havoc has that probably won't be implemented into oos. When I was on havoc I really liked the customizations for the quicksettings, and a lot of people really like the always on display, I'm more of an ambient display person and oos has a bit better implementation of that.
Havoc has battery bar as well, and the color can be changed and a gradient effect can be added. Really the only thing that I wanted that I could get on oos is the dashed circle with percentage in it, but that's only because I didn't spend enough time trying to figure out how to get EdXposed to work stabily.
I don't think the ota system is implemented yet because they are still unofficial builds, but it's just an option in the setting, as of now you'll have to dirty flash in twrp.
The nandroid backup hopefully someone else can answer because I haven't done one of those since my nexus 5 probably, usually I just use titanium backup and set everything up from scratch.
Again tho, if you want to go from aosp back to oos you'll need to wipe the internal storage, I'd recommend backing up your whole sd card to your pc in case anything happens.
If you want some video guides there's a guy on YouTube called koogly who does things on the op6t, but everything is basically the same because they're both relevant a/b system devices.
Edit: I never had issues with stability or random reboots on either havoc or oos, a couple reasons I decided to go back is because if you turn nfc on on havoc it turns on and off until you reboot, the alarm volumes are much quieter, and the vibration strength in the 7/5 build is turned way up.
Click to expand...
Click to collapse
So a dirty flash just to update Havoc wouldn't erase my data or anything right?
DQScott95 said:
So a dirty flash just to update Havoc wouldn't erase my data or anything right?
Click to expand...
Click to collapse
Yeah
explosivequack said:
Yeah
Click to expand...
Click to collapse
Thanks for all of your help. So just to confirm :
If I just wanna test this for a bit, I can make a nandroid backup, wipe data, dalvik only, flash HavocOS, TWRP, GAPPS and Magisk, and I'll officially be on Havoc with root and twrp at that point correct?
Then if for some reason want to go back to my current OOS, then I have to wipe System, data, and dalvik then restore my backup, flash twrp and magisk again, then I'm back to normal correct?
Im so sorry for all of the questions. The last time I was flashing roms was on my LG Motion!! Just trying to get comfortable with the process again and talking about it helps alot.
DQScott95 said:
Thanks for all of your help. So just to confirm :
If I just wanna test this for a bit, I can make a nandroid backup, wipe data, dalvik only, flash HavocOS, TWRP, GAPPS and Magisk, and I'll officially be on Havoc with root and twrp at that point correct?
Then if for some reason want to go back to my current OOS, then I have to wipe System, data, and dalvik then restore my backup, flash twrp and magisk again, then I'm back to normal correct?
Im so sorry for all of the questions. The last time I was flashing roms was on my LG Motion!! Just trying to get comfortable with the process again and talking about it helps alot.
Click to expand...
Click to collapse
Nah no problem, I spent time learning so might as well make it usefup.
Your first part is correct, however for flashing back to oos your internal storage will be encrypted with the newest security patch (july) while oxygen os uses June in this case. This means that all of your pictures and music and everything will be encrypted and oxygen will not be able to read or decrypt the storage. This means that when you want to flash back to oos you will have to completely wipe your internal storage, basically setting the phone to how it was from the box.
If you use an app called Syncthing it makes backing up and restoring super easy.
explosivequack said:
Nah no problem, I spent time learning so might as well make it usefup.
Your first part is correct, however for flashing back to oos your internal storage will be encrypted with the newest security patch (july) while oxygen os uses June in this case. This means that all of your pictures and music and everything will be encrypted and oxygen will not be able to read or decrypt the storage. This means that when you want to flash back to oos you will have to completely wipe your internal storage, basically setting the phone to how it was from the box.
If you use an app called Syncthing it makes backing up and restoring super easy.
Click to expand...
Click to collapse
Is it possible to decrypt like on 5t and forward no verify so that I can freely go back and forth between AOSP and oos without wiping internal?
Which app do I use, syncthing or syncthing-fork?
explosivequack said:
Nah no problem, I spent time learning so might as well make it usefup.
Your first part is correct, however for flashing back to oos your internal storage will be encrypted with the newest security patch (july) while oxygen os uses June in this case. This means that all of your pictures and music and everything will be encrypted and oxygen will not be able to read or decrypt the storage. This means that when you want to flash back to oos you will have to completely wipe your internal storage, basically setting the phone to how it was from the box.
If you use an app called Syncthing it makes backing up and restoring super easy.
Click to expand...
Click to collapse
You're amazing, thank you so much for all the help. I just download the sync app and I'm gunna back up and possibly test out Havoc later tonight when I'm off work
harpin14789 said:
Is it possible to decrypt like on 5t and forward no verify so that I can freely go back and forth between AOSP and oos without wiping internal?
Which app do I use, syncthing or syncthing-fork?
Click to expand...
Click to collapse
People in the havoc forums have talked about doing this and they say it's working, I haven't done it myself so I'm not sure how difficult it is or if you lose out on anything but it might be worth checking out if you plan on switching a lot.
I'm using Syncthing on the phone and synctrayzor on my pc.
Edit: may have seen the no verify in the twrp section.
DQScott95 said:
You're amazing, thank you so much for all the help. I just download the sync app and I'm gunna back up and possibly test out Havoc later tonight when I'm off work
Click to expand...
Click to collapse
Best of luck and happy flashing.
This is the xda thread that's the source of the no_verity.zip that disables forced encryption upon initial boot up of a freshly-wiped internal storage.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I used its previous version successfully to become unencrypted and therefore move between OOS and Havoc at will on the OP6, and have used it since OOS 9.5.6 on the OP7pro without issue. As soon as the AOSP roms mature and I can confirm full functionality on Verizon, I'll leave OOS.
One last tip: keep your internal storage backed up on a USB otg drive that's loaded with the latest OOS, TWRP installer zip, Magisk, and no_verity zip. After the 6T, I don't leave home without that if any flashing is a possibility...
DQScott95 said:
So I'm currently using RennovateICE because it was a super easy magisk install and didn't conflict with anything.
I've been looking at HavocOS and it's looks absolutely amazing. My question is, anyone who's tried it, is it better than the standard OOS and is it stable?
I also haven't flashed roms in a long time, so if I make a backup through TWRP first I can do a full restore of my current system as is if I want to revert back from Havoc OS correct?
Also if anyone can suggest their favorite rom etc I'd love to hear it, really in a mood to mess with my phone now that it's rooted.
Click to expand...
Click to collapse
Havoc has tons of customization and is probably my favorite rom along with Resurrection Remix but the fingerprint scanner and double tap issues made me try AOSIP which was much more stable and has similar features. On both roms the fingerprint scanner didn't work as well as stock and it was annoying. AOSIP has an always on fingerprint scanner which is really cool. I ended up going back to stock OOS and flashed Renovate. Basically if you don't mind the fingerprint scanner not working well and the speakers being slightly lower in volume then you'll like Havoc. Give AOSIP a try as well, you won't be disappointed.
Related
OK, so on boot I get this warning, "KERNEL IS NOT SEANDROID ENFORCING" after upgrading to latest stock firmware and re installing TWRP. I also note that when I try and do anything in TWRP it tells me that the /data partition can not be mounted and a couple of other errors. I understand that this is because the stock ROM encrypts the /data directory, no reason to doubt this, but it wasn't there before I flashed the stock ROM upgrade - done because I had a new version notification driving me made.
I have seen that I can wait for TWRP to add something to it's tools to fix this, if they are even looking at it. Or I can re-partition data via TWRP.
If I do the latter, if I use TWRP to make a copy of the data partition and restore after, would I be reintroducing the encryption?
If it does fix it and the TWRP restore introduces the encryption back, would Titanium restore everything without encryption?
Is it even a fix?
Advise sort here please....
did u ever solve this i also have it but im on holiday and unable to get access to any stock firmware... files are too big for international downloads. it will cost me like £30 to download the one file i need to flash using odin and it bothers me this could happen again after.
I modified the build.prop file to allow tethering to work something along the lines of tether_required_dun 0 to the bottom as described in many posts but the phone went immediately into boot loo.
TWRP is on and working correctly.
phone was rooted.
oem unlock ticked
i can adb to the phone correctly
i used to get recorevy is not seandroid enforcing. that changed to kernel is not seandroid enforcing. and i can now no longer boot.
bit of a strange one...
twiztednibbz said:
did u ever solve this i also have it but im on holiday and unable to get access to any stock firmware... files are too big for international downloads. it will cost me like £30 to download the one file i need to flash using odin and it bothers me this could happen again after.
I modified the build.prop file to allow tethering to work something along the lines of tether_required_dun 0 to the bottom as described in many posts but the phone went immediately into boot loo.
TWRP is on and working correctly.
phone was rooted.
oem unlock ticked
i can adb to the phone correctly
i used to get recorevy is not seandroid enforcing. that changed to kernel is not seandroid enforcing. and i can now no longer boot.
bit of a strange one...
Click to expand...
Click to collapse
I did but I am not happy about the fix.
I had to wipe the data partition in the advance mode and reformat it. I always do things three times to make sure. SO effectively has to start from scratch with the phone set up. I didn't use the back up as it may have reintroduced the problem, so after I wiped the old backup and created a new, and then built the phone and created another new backup in TWRP.....
I still find certain apps don't work, like Cerberus - hidden, Cool Tool, APM+........
Hope it helps you.
jonners59 said:
I did but I am not happy about the fix.
I had to wipe the data partition in the advance mode and reformat it. I always do things three times to make sure. SO effectively has to start from scratch with the phone set up. I didn't use the back up as it may have reintroduced the problem, so after I wiped the old backup and created a new, and then built the phone and created another new backup in TWRP.....
I still find certain apps don't work, like Cerberus - hidden, Cool Tool, APM+........
Hope it helps you.
Click to expand...
Click to collapse
Hi mate.
Yes unfortunately same boat here... ended up putting superman on but i lost all the last 2 weeks worth of holiday photos ive just taken and i leave in 3 days ffs. The rest i had pretty much backed up before i left. Just not often u get the chance to film a live octopus feeding in rock pools on a beach among the 3000 photos ive taken.
Ah well theae things happen. It is weird because everywhere i read people have great success doing what i did even on a stock rom non rooted so dont know why mine went pair shaped.
I spose the benefits are this rom is far superior to stock. Everything seems to work so far. Superman 1.17. Dont know of youve tried it but since your in same boat on a fresh install its really worth a look. Sorry to hear of ya loss.
twiztednibbz said:
Hi mate.
Yes unfortunately same boat here... ended up putting superman on but i lost all the last 2 weeks worth of holiday photos ive just taken and i leave in 3 days ffs. The rest i had pretty much backed up before i left. Just not often u get the chance to film a live octopus feeding in rock pools on a beach among the 3000 photos ive taken.
Ah well theae things happen. It is weird because everywhere i read people have great success doing what i did even on a stock rom non rooted so dont know why mine went pair shaped.
I spose the benefits are this rom is far superior to stock. Everything seems to work so far. Superman 1.17. Dont know of youve tried it but since your in same boat on a fresh install its really worth a look. Sorry to hear of ya loss.
Click to expand...
Click to collapse
Do you not put pics on external SD or have sync to google or OneDrive etc.... I was lucky in that respect as I keep nothing of any note on the internal storage and docs/etc are all sync'd It's the days of re doing settings that p me off. And Titanium never puts it back as you want really.
I think the prob is encryption. I believe that the stock ROM encrypts the data drive.
I am on stock, rooted. I am not happy with the stock and can't wait for a non stock build to come out - I don't think there are any yet, that are not built on the stock. Superman is modified stock, yes? How do you find it and what are the differences?
jonners59 said:
Do you not put pics on external SD or have sync to google or OneDrive etc.... I was lucky in that respect as I keep nothing of any note on the internal storage and docs/etc are all sync'd It's the days of re doing settings that p me off. And Titanium never puts it back as you want really.
I think the prob is encryption. I believe that the stock ROM encrypts the data drive.
I am on stock, rooted. I am not happy with the stock and can't wait for a non stock build to come out - I don't think there are any yet, that are not built on the stock. Superman is modified stock, yes? How do you find it and what are the differences?
Click to expand...
Click to collapse
Same as you really but I moved everything before i left for my vacation. ive never actually worked out how to get the camera to save direct to the sd card if thats even poasible upto now so i just move them all every two weeks onto the sandisk extreme.
I cant use the auto sync in this country because the file sizes are so large of the photos that it would cost me more then buying a brand new dslr camera to upload one holiday on the fly. Lol
Yeah that totally grates me too tbh but these pictures really got my goat your right about titanium too. All the other ones are the same. The only backup program thats ever worked properly for me is the lg g4 h815 built in one its brilliant.
You are correct about the encryption i didnt think using that command would soft brick the phone or i wouldnt have done it before backing up. You have to format the data partition to remove the encryption which in turns wipes all your data.
I was on stock h3g uk rooted software but it was so locked down even with root it made life difficult. I dont like to stray too far away from the stock experience these days most are quite adept.
Superman is modified stock a lot of it is based on the nougat rom that is due out after MM. It also has the edge features and swipe bar etc.
Its slick fast and totally brilliant. Android pay doesnt work i dont believe but there is very little else.
No bugs to my knowledge
There are audio and volume enhancements as well. Camera enhancements. Kustom kernels.
It uses aroma inataller so you can choose what you want to install as well.
Definately the best rom ive tried for many years. Turned my boring galaxy into a sharp snappy customisable device that i am over the moon with. If only samsung employed some of these people...
Honestly if you can live with the one or two things that dont work its so much better.
You mention things don't work. what does not work?
Hi. I tried to restore a Nandroid backup taken using OOS Pie stable and bluspark twrp. I had disabled any kind of lockscreen security before backing up and restoring. I did not install a single user mod (which is required for the pixel 2 at least). After restoring, all my internal storage is completely messed up with filenames that are random strings that look encrypted. Rebooting the phone always lands me in recovery and flashing the OTA zip does nothing. Plz halp
darkfire404 said:
Hi. I tried to restore a Nandroid backup taken using OOS Pie stable and bluspark twrp. I had disabled any kind of lockscreen security before backing up and restoring. I did not install a single user mod (which is required for the pixel 2 at least). After restoring, all my internal storage is completely messed up with filenames that are random strings that look encrypted. Rebooting the phone always lands me in recovery and flashing the OTA zip does nothing. Plz halp
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6/how-to/how-to-restore-backup-twrp-t3807546
hope this helps, cheers.
vtec303 said:
https://forum.xda-developers.com/oneplus-6/how-to/how-to-restore-backup-twrp-t3807546
hope this helps, cheers.
Click to expand...
Click to collapse
Thanks! That sort of mitigated the issue. The device was stuck on the boot animation and I had to flash the latest stable OTP image again but after that, it started to boot and all my data was preserved. The only caveat was that the standard bootloader is unlocked message was replaced with an ominous "Your device is corrupted" message
/rant
On a side note, for all their claims of being super dev friendly, oneplus is making it annoyingly hard to mess around with their devices by not releasing full device images. It's not easy to restore to stock after ****ing around with stuff. When I used to mess around with my pixel, the stock images made it so easy to restore to stock with no problems for all the stuff I did with it, I had never run into issues where it forced me into crash dump mode or left me booting only to fastboot.
/end rant
/rant 2
XDA auto censors swearing wut?
/end rant
Hi all,
As you all know Android rolled out the new 9 pie Update on all xiaomi devices.
After updating my mi a2 lite became the crappiest phone on earth as all the bugs started appearing(phone was rebooting multiple times, image was broken, sd xcard not recognised and battery life draining fast as hell).
Because of that I decided to root my phone and install Havoc 2.0. Fair enough, I used the rom for a bit but honestly I am not really happy about it too as doesn't seem really stable at all (many functions are there but not working, the camera app is crap, the volume bar appears every time I touch the fingerprint sensor and the fingerprint lock isn't working as well). At this point I wanted to revert and get back to the stock oreo 8.1 so I booted the recovery twrp to restore the firmware backup that I did at the beginning before installing havoc but this disappeared!!!!!
Reading again the procedure i followed I noticed that one of the steps was to wipe the caches and, as the procedure was saying, the system as well(I know.... I am an idiot for relying on what the procedure said)!
Obviously this deleted my previous backup completely leaving me empty hands without any stock firmware/rom.
Is there any chance to revert back to the stock (maybe downloading all the pieces and then force flashing them?) or I am screwed?
I know, I should have followed one of your tutorial (and I am sorry for asking now for your assistance) but now I think you are the only one that can actually help me.
Best regards,
D.
manna.davide87 said:
Hi all,
As you all know Android rolled out the new 9 pie Update on all xiaomi devices.
After updating my mi a2 lite became the crappiest phone on earth as all the bugs started appearing(phone was rebooting multiple times, image was broken, sd xcard not recognised and battery life draining fast as hell).
Because of that I decided to root my phone and install Havoc 2.0. Fair enough, I used the rom for a bit but honestly I am not really happy about it too as doesn't seem really stable at all (many functions are there but not working, the camera app is crap, the volume bar appears every time I touch the fingerprint sensor and the fingerprint lock isn't working as well). At this point I wanted to revert and get back to the stock oreo 8.1 so I booted the recovery twrp to restore the firmware backup that I did at the beginning before installing havoc but this disappeared!!!!!
Reading again the procedure i followed I noticed that one of the steps was to wipe the caches and, as the procedure was saying, the system as well(I know.... I am an idiot for relying on what the procedure said)!
Obviously this deleted my previous backup completely leaving me empty hands without any stock firmware/rom.
Is there any chance to revert back to the stock (maybe downloading all the pieces and then force flashing them?) or I am screwed?
I know, I should have followed one of your tutorial (and I am sorry for asking now for your assistance) but now I think you are the only one that can actually help me.
Best regards,
D.
Click to expand...
Click to collapse
Wiping system is not what wiped your backup, your backup was stored on internal storage or on external sdcard, it does not get stored in system. The only you could have wiped the backup is if you also chose the option to wipe the internal storage when you wiped cache and system.
Factory reset and the normal wipes in TWRP do not wipe /data/media, /data/media is where your user data is stored. Only specifically choosing the option to wipe internal storage can wipe /data/media.
And you aren't an idiot for following instructions, you're an idiot for following instructions incorrectly. If you had wiped cache and system but left internal storage alone, you wouldn't be in the mess you're in.
Have you tried doing a Google search for:
"Return to stock (your model number)"
If it's available, that should find the instructions, tools and files you need.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Wiping system is not what wiped your backup, your backup was stored on internal storage or on external sdcard, it does not get stored in system. The only you could have wiped the backup is if you also chose the option to wipe the internal storage when you wiped cache and system.
Factory reset and the normal wipes in TWRP do not wipe /data/media, /data/media is where your user data is stored. Only specifically choosing the option to wipe internal storage can wipe /data/media.
And you aren't an idiot for following instructions, you're an idiot for following instructions incorrectly. If you had wiped cache and system but left internal storage alone, you wouldn't be in the mess you're in.
Have you tried doing a Google search for:
"Return to stock (your model number)"
If it's available, that should find the instructions, tools and files you need.
Click to expand...
Click to collapse
Hi, first of all thanks for replying.
Interbal storage hasn't been wiped out, i am sure about it as the proceedure was saying not to do it. (I've selected just the first 3 options and internalbstorage is the 4th so I am def8nitely sure about it). Might be somewhere else then?
I did a second back up now and I see it so at this point I am not really sure where this could be!
Is 12 hours that I am searching proceedures but everything is very confusing.
manna.davide87 said:
Hi, first of all thanks for replying.
Interbal storage hasn't been wiped out, i am sure about it as the proceedure was saying not to do it. (I've selected just the first 3 options and internalbstorage is the 4th so I am def8nitely sure about it). Might be somewhere else then?
I did a second back up now and I see it so at this point I am not really sure where this could be!
Is 12 hours that I am searching proceedures but everything is very confusing.
Click to expand...
Click to collapse
Mate @Droidriven you're a monster!
I found it in data/media in the internal storage! thanks a lot mate!
I'll run it and see if all comes back as usual.
Infinite thanks!
Good to go.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Good to go.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Do you mind me asking you one last thing?
At this point, having the original backup, I can try another custom Rom before reverting everything to Oreo.
My question are 2:
-Because you seem very driven, do you know any stable custom rom that I can run on this Xiaomi MI A2 lite?
-Do you know if I can Install the old Havoc on and purge this pie version?
Thanks again,
Davide
manna.davide87 said:
Do you mind me asking you one last thing?
At this point, having the original backup, I can try another custom Rom before reverting everything to Oreo.
My question are 2:
-Because you seem very driven, do you know any stable custom rom that I can run on this Xiaomi MI A2 lite?
-Do you know if I can Install the old Havoc on and purge this pie version?
Thanks again,
Davide
Click to expand...
Click to collapse
I don't know anything about any of the ROMs for your device, I don't have your device.
Sent from my LGL84VL using Tapatalk
Hey guys.
Got a Oneplus 6 running lastest OTA with latest TWRP installed.
Before flash this latest OTA, I was running latest open Beta, flashed by TWRP, with no problems.
Just booted on TWRP today to flash latest Beta again, but when I drawed the patterns, TWRP restarts. Tryed some more times, same thing, put the right patterns, TWRP imagem boots into it again.
Rebooted into system, but the system said wrong pattern now. Can't boot in system anymore too.
Booted in TWRP again, went to File Manager, and deleted these files inside /data/system (Guess I ****ed up even more here)
locksettings.db-wal
locksettings.db-shm
locksettings.db
Now I can boot in system, but it stay stuck on Initializing system on screen, and I can access only configuration using the status bar. Tryed to set the same pattern on security, still don`t work on TWRP decrypting, and system keeps saying Initializing.
Got pretty stuck here, don't know nothing else to try, anyone have any clue on what I can do?
When asked for the pattern in TWRP instead of trying to enter it choose the "do not decrypt /data" option. Then you can format (not wipe) /data. Obviously you'll lose everything, including on internal storage.
And also, it may happen again if you don't flash the no_verity zip. That stops the ROM re-encrypting /data. See this thread for more info.
Looks like some Security Patch downgrade stuff. You flashed an older build, encryption gets messed up because the Security Patch date is older than the one previously installed, you'll have to format your Data partition to decrypt the storage.
As said above, running decrypted will prevent those situtations
Although some may advice running decrypted to avoid situations, I won't recommend it, especially if you're using TWRP. A person with a good knowledge would be able to do what you did and remove lockscreen security, compromising your important accounts.
And: instead of a pattern, it's recommended to use a PIN (at least 8 digits) or password (at least 6 letters/digits/specialchars)
remewer said:
Although some may advice running decrypted to avoid situations, I won't recommend it, especially if you're using TWRP. A person with a good knowledge would be able to do what you did and remove lockscreen security, compromising your important accounts.
Click to expand...
Click to collapse
To be honest, altough what you said is absolutely true, finding yourself in a situation where someone steals your phone, sees he can't enter it, but happens to know how to use TWRP to remove the lockscreen security or sideload your data is pretty far fetched.
Frankly, loosing your data over a bad flash seems a bit more threatening.
Totone56 said:
To be honest, altough what you said is absolutely true, finding yourself in a situation where someone steals your phone, sees he can't enter it, but happens to know how to use TWRP to remove the lockscreen security or sideload your data is pretty far fetched.
Frankly, loosing your data over a bad flash seems a bit more threatening.
Click to expand...
Click to collapse
Not threatening if you back up those data. Which everyone should do regardless if you're going to flash a ROM or not.
remewer said:
Not threatening if you back up those data. Which everyone should do regardless if you're going to flash a ROM or not.
Click to expand...
Click to collapse
Agreed, that is what i personally do. I like being able to flash anything and potentially having to format the whole storage without any worry. Using Google Photos, Keep, Doc, ect, using Spotify and syncing every contact really makes life easier.
remewer said:
Not threatening if you back up those data. Which everyone should do regardless if you're going to flash a ROM or not.
Click to expand...
Click to collapse
Which is fine if you are only getting this issue directly after ROM flashing or at some other predictable time. But when I was getting it, my lockscreen code/pattern was initially working fine after flashing the ROM, then it would stop working at some seemingly random moment. So the only way I could reliably have any data stored was to run with /data unencrypted. Which I agree is not ideal.
Hey Guys,
this could propably be posted in r/TIFU as well since I think I screwed up big time today -.-
I basically just wanted to update my rooted OP7P to 10.0.5 (EU) using the latest OTA - so I followed the usual steps as always:
Uninstall Magisk
Install OTA - No Reboot
Install TWRP retention script in Magisk
Re-Install Magisk
Reboot
This procedure worked fine the last 2 times an OTA was released but this time I'm not able to boot into the system anymore. TWRP is still in places but won't read the data partition anymore - it also doesn't ask for my pattern to decrypt it. Problem is that idiot-me of course didn't do a backup before (yea, I know -.-) and obviously doesn't want to loose the data on it.
I of course checked the forum and googled my ass of trying to find a non-destructive way to access the system but couldn't find anything fitting my scenario. So my last resort is to ask you guys directly: Did anybody ever encounter such a situation and if yes, how did you resolve it? Right now any support would be much appreciated
//Edit: Symptoms and current behaviour:
Boot into system (partition A) ends in the OP logo cirling endlessly
Boot into system (partition B) sends me directly to TWRP
TWRP doesn't ask for encryption pattern
The answer to TWRP's initial question (Keep System r/o) is not persisted
Fastboot/ADB are working (but obviously w/o access to /data)
I'm technically running a stock OxygenOS with Renovate ICE. I know technically its instuctions say to install the OTA directly from within TWRP and and then re-flash TWRP and Magisk but that wasn't neccessary the last times... one idea of mine is to just do that now and see where it leads me but I really don't wanna risk my data.
the.cybertronic said:
Hey Guys,
this could propably be posted in r/TIFU as well since I think I screwed up big time today -.-
I basically just wanted to update my rooted OP7P to 10.0.5 (EU) using the latest OTA - so I followed the usual steps as always:
Uninstall Magisk
Install OTA - No Reboot
Install TWRP retention script in Magisk
Re-Install Magisk
Reboot
This procedure worked fine the last 2 times an OTA was released but this time I'm not able to boot into the system anymore. TWRP is still in places but won't read the data partition anymore - it also doesn't ask for my pattern to decrypt it. Problem is that idiot-me of course didn't do a backup before (yea, I know -.-) and obviously doesn't want to loose the data on it.
I of course checked the forum and googled my ass of trying to find a non-destructive way to access the system but couldn't find anything fitting my scenario. So my last resort is to ask you guys directly: Did anybody ever encounter such a situation and if yes, how did you resolve it? Right now any support would be much appreciated
//Edit: Symptoms and current behaviour:
Boot into system (partition A) ends in the OP logo cirling endlessly
Boot into system (partition B) sends me directly to TWRP
TWRP doesn't ask for encryption pattern
The answer to TWRP's initial question (Keep System r/o) is not persisted
Fastboot/ADB are working (but obviously w/o access to /data)
I'm technically running a stock OxygenOS with Renovate ICE. I know technically its instuctions say to install the OTA directly from within TWRP and and then re-flash TWRP and Magisk but that wasn't neccessary the last times... one idea of mine is to just do that now and see where it leads me but I really don't wanna risk my data.
Click to expand...
Click to collapse
The bad news is once twrp loses access to data. The only fix is to format data and everything will be fixed.
So... you're basically telling me I ****ed up completely and my data is gone? Never was a profile picture more fitting than yours right now :/
What I'm wondering is that, from a technical perspective and on a working phone, the decryption takes place not during the boot but only after you've entered your code/passphrase/pattern on OS level. Meaning the system should theoretically be able to boot up to there without /data access. TThat's why I had the idea to flash a clean stock Oxygen from TWRP (no root), boot the system and hopefully be able to access the data this way. Respectively any encryption can be broken somehow, can't it? Even if it might take quite some time to do so this should theoretically be possible...
I mean... I definetly don't know enough about Android internals to understand its encryption mechanics completely but from a technical perspective it should be possible.... like the saying "there is no such thing as 100% security"
the.cybertronic said:
So... you're basically telling me I ****ed up completely and my data is gone? Never was a profile picture more fitting than yours right now :/
What I'm wondering is that, from a technical perspective and on a working phone, the decryption takes place not during the boot but only after you've entered your code/passphrase/pattern on OS level. Meaning the system should theoretically be able to boot up to there without /data access. TThat's why I had the idea to flash a clean stock Oxygen from TWRP (no root), boot the system and hopefully be able to access the data this way. Respectively any encryption can be broken somehow, can't it? Even if it might take quite some time to do so this should theoretically be possible...
I mean... I definetly don't know enough about Android internals to understand its encryption mechanics completely but from a technical perspective it should be possible.... like the saying "there is no such thing as 100% security"
Click to expand...
Click to collapse
Dude try flashing the stock rom from twrp onto both slots by mounting an otg drive..or adb sideload(very slow I think..still worth a try if you don't wanna lose data)..stock rom can manage the encryption I suppose.
Encryption is an issue when you flash different roms(I think so..I am no expert,just my experience so far).
Breaking encryption is not like what you think..it might take ages to break using brute force (again from what I heard..I lost my data a lot of time flashing roms without twrp backup..nowadays I just backup my apps using tb coz restorings the apps is really a pain in the ass process)
the.cybertronic said:
So... you're basically telling me I ****ed up completely and my data is gone? Never was a profile picture more fitting than yours right now :/
What I'm wondering is that, from a technical perspective and on a working phone, the decryption takes place not during the boot but only after you've entered your code/passphrase/pattern on OS level. Meaning the system should theoretically be able to boot up to there without /data access. TThat's why I had the idea to flash a clean stock Oxygen from TWRP (no root), boot the system and hopefully be able to access the data this way. Respectively any encryption can be broken somehow, can't it? Even if it might take quite some time to do so this should theoretically be possible...
I mean... I definetly don't know enough about Android internals to understand its encryption mechanics completely but from a technical perspective it should be possible.... like the saying "there is no such thing as 100% security"
Click to expand...
Click to collapse
The reason that format is the only answer is because when twrp does not ask for password. It believes you are unencrypted. What has happened is the file that store your password and encryption key is corrupted so any answer you give is wrong.
There's nothing you can do but format data. I've encountered this issue already.
You can try to salvage personal photos and videos using an otg drive (external ssd, hdd, sd card reader...), also back in 6t days I had this encryption problem twice, I remember that one time flashing the stock rom from the otg fixed it but I don't remember if I rebooted to recovery of the other slot.
Anyway, for the others, if he used DM verity removal and so decrypted data, he would have never face this problem again?
Joker123## said:
Dude try flashing the stock rom from twrp onto both slots by mounting an otg drive..or adb sideload(very slow I think..still worth a try if you don't wanna lose data)..stock rom can manage the encryption I suppose.
Encryption is an issue when you flash different roms(I think so..I am no expert,just my experience so far).
Breaking encryption is not like what you think..it might take ages to break using brute force (again from what I heard..I lost my data a lot of time flashing roms without twrp backup..nowadays I just backup my apps using tb coz restorings the apps is really a pain in the ass process)
Click to expand...
Click to collapse
vegetaleb said:
You can try to salvage personal photos and videos using an otg drive (external ssd, hdd, sd card reader...), also back in 6t days I had this encryption problem twice, I remember that one time flashing the stock rom from the otg fixed it but I don't remember if I rebooted to recovery of the other slot.
Anyway, for the others, if he used DM verity removal and so decrypted data, he would have never face this problem again?
Click to expand...
Click to collapse
I just tried flashing the stock Oxygen yesterday but to no satisfying result... afterwards it just showed a clean default-structure on the SD. Long story short: I accepted the fate that my data is gone and learned a valuable lesson... first thing I installed after rooting was Titanium^^
Zhuang zhuang said:
There's nothing you can do but format data. I've encountered this issue already.
Click to expand...
Click to collapse
As hard as it is to admit, you were completely right... I just lost 6 months worth of photos incl. my last vacation in Vietnam - fml.
the.cybertronic said:
I just tried flashing the stock Oxygen yesterday but to no satisfying result... afterwards it just showed a clean default-structure on the SD. Long story short: I accepted the fate that my data is gone and learned a valuable lesson... first thing I installed after rooting was Titanium^^
As hard as it is to admit, you were completely right... I just lost 6 months worth of photos incl. my last vacation in Vietnam - fml.
Click to expand...
Click to collapse
For future reference, brick means a brick. Like, can't boot to fastboot/twrp/or use msmtool
the.cybertronic said:
As hard as it is to admit, you were completely right... I just lost 6 months worth of photos incl. my last vacation in Vietnam - fml.
Click to expand...
Click to collapse
In the recent OS (10.0.5 & beta 13) I think Oneplus they add something that prevent user from using the TWRP retention script. I always use this solution for lower version and have no issue but with both 10.0.5 and beta 13 have the same issue
Zhuang zhuang said:
In the recent OS (10.0.5 & beta 13) I think Oneplus they add something that prevent user from using the TWRP retention script. I always use this solution for lower version and have no issue but with both 10.0.5 and beta 13 have the same issue
Click to expand...
Click to collapse
damn, good to know if I ever install OOS again - I now switched to Havoc... even though I had to skip rooting it all together after I couldn't get Magisk running with the latest safety net changes (thanks Google -.-)