hey guys, i could not find anything similar to what i'm about to ask in the forum, and if it is there but i missed it somehow, i apologize! as of lately i have been working entirely too much and sleeping very little!
lol so here it is, i have the hammerhead d820 version, and it is currently running the 6.0.1 version of android. I rooted it with nrt, and now i would like to flash a custom rom for my very first time! so, i just want to know if i would be able to go from the current version of android that i am running, (marshmellow) would i be able to skip nougat and just flash oreo?
or is that not going to work?
- a confused chick
lol thanks for the help!
Flashing new ROM in almost all cases completely wipes /system partition (and /boot partition) and overwrites it with new ROM data so it doesn't matter what was flashed before as everything there is replaced.
As root is usually installed to /system partition it will be gone after reflashing, unless new ROM already contains root (if not just root it again).
After flashing new ROM through custom recovery (TWRP/CWM) make sure to do factory reset (wipe /data partition). It wipes all your data from the phone so make a backup before, but is often necessary for new ROM to even boot or work reliably.
Halamix2 said:
Flashing new ROM in almost all cases completely wipes /system partition (and /boot partition) and overwrites it with new ROM data so it doesn't matter what was flashed before as everything there is replaced.
As root is usually installed to /system partition it will be gone after reflashing, unless new ROM already contains root (if not just root it again).
After flashing new ROM through custom recovery (TWRP/CWM) make sure to do factory reset (wipe /data partition). It wipes all your data from the phone so make a backup before, but is often necessary for new ROM to even boot or work reliably.
Click to expand...
Click to collapse
Oh wow i have been so insanely busy over the past month and a bit that i did not even see your reply til just now!!
what a piss off my hammerhead ended up being.... I had the damn thing for less than a month, the p.o.s ended up just refusing to take any charge at all.
well off to the box of fail with you, hammerhead! Was great to almost get to know ya, hahaha... *sigh*
Anyways i am now using the Galaxy SM-G903W (the s5 neo, and you bet i have root privileges! and a phone that i previously owned for a short time, the HUAWEI RIO-AL00 (MAIMENG 4) has made it's way back into my "teck desk"
P.s; to the mods and to all of my fellow devs and anyone that is a part of the forum..
PLEASE accept my sincere apology for how many different topics that i seemingly have managed to squish into the thread here that i originally created... I am going to continue my search to attempt to answer my questions, and if nothing jumps out at me please, everybody stay tuned for the next thread created by yours truly;
Xo cheers =)
Sent from my s5neoltecan using XDA Labs
Related
Hey guys. I just bought a Verizon Galaxy S3 from eBay. I rooted it, flashed a custom rom, bricked it, etc. Now I'm back to stock. I have a new SIM card but it's not activated yet. It will be activated in a couple days. I was going to flash Synergy Rom until I read that it does this thing when you flash their custom kernel; it auto picks what carrier your phone has and flashes the files accordingly. Since I don't have a carrier, I was wondering what would happen if I flashed it. I'm signed in on my gmail which I use on my original Galaxy S also. That one has T-Mobile. I'm a little worried that it will somehow know that my gmail is attached to T-Mobile and flash T-Mobile files. I know I could just use stock kernel and not go through all this, but I figured if the question hasn't been asked, then it should be asked.
One last thing. I was reading that I should wipe cache, dalvik, and (I could but I didn't have to)-wipe /system, before flashing a new rom.
I was wondering if I should wipe /system or if that would ruin the custom bootloader + SU, or custom bootchain, or anything else I did to my phone.
(I know I said I'm back at stock but then I went ahead and flashed the custom bootchain and "SU+Bootloader_FIXED.zip".)
So what is the question? Is your bootloader unlocked? Some ROMs mention to have this unlocked for whatever reason I'm unsure.
You don't need to be activate to flash (I didn't have sim interested when I flash synergy)
For a wipe I did the following.
Wipe cache partition
Wipe dalvik cache
Format /system
Format /data
Format cache
Reply
I guess basically what my question is, is what is inside "/system"?
And, should I wait to flash the custom kernel that comes with synergy rom until i have an activated SIM in my phone; so the auto checker in the kernel detects that I have verizon? Or does it not look at my SIM to determine that, rather at some other part of my phone?
I believe the OS is in /system and if you didn't wipe this you put a ROM on top of another ROM. Follow my procedure when you flash a fresh ROM.
Maybe someone can further explain your question about the auto checker because this is not something i've heard of.
Alright, so I just did what you said and started flashing Synergy Rom. One thing that I immediately noticed was, that it took longer to write to /system, which I'm guessing is good, because it actually had the chance to write all the files it needed.
Also, because I left the custom bootchain on there, it flashed the stock kernel while doing the rom installation and it went through OK. Which didn't happen the first time; probably because I flashed the stock bootchain and then the rom.
I'm booting into the phone now. For the first time in 3 days it's not stuck on the Samsung boot logo!
Thank you so much for that recommendation!!
It seems as if it's working
:good::good:
I will need help flashing without a sim card, i will be getting my gs3 soon and flashing it to page plus. Therefore my 4g doesn't work and i have no sim card. So i will using aosp ROMs cuz i just flat out hate touch wiz. Can any of you gs3 veterans help? Please and thank you!
Sent from my SPH-D710 using Xparent Skyblue Tapatalk 2
Long time lurker (though I can't say I always understood everything I read), first time poster.
I've had several iPhones in the past and I finally decided to try the other option. I got a Verizon GS3 last November and I couldn't be happier.
However, like many others, I'm looking to get more from my phone. I do like TouchWiz (I have used a Nexus 4 for a week and didn't like the stock android), so I want to stay with about the same UI that I have now. I did some research and found that Synergy is probably the best option for me in terms of getting a bit more from my phone but still staying with (mostly) the same UI. Of course, getting rid of all the annoying Verizon apps is a huge bonus too.
This is what I have done already:
Used this method to root and unlock my bootloader: http://forum.xda-developers.com/showthread.php?t=2332825
Used TWRP to make a full backup of my phone to an external SD card
Used Titanium Backup to make a full backup of my apps to an external SD card
Here are my questions:
I have the latest Verizon OTA installed (June 20th, I535VRBMF1). I have read all the posts from the last 14 days on the Synergy thread and I think I understand that since my phone has a newer firmware than the one in the latest synergy ROM, I will need to downgrade my firmware before installing the ROM to avoid camera and wifi problems. Is this correct? Someone linked there to I535VRBMB1_firmware.zip. How do I install this firmware? I have ODIN but when I choose PDA it will not let me choose the zip file. When I extract it, ODIN doesn't find anything too.
What kind of wipe should I perform before I flash to Synergy? Should I take my SD card out for the wipe or leave it in? Do I even need to wipe?
Can I install the ROM from ROM Manager or should I always use recovery mode and TWRP?
Is it recommended to just restore my Titanium full backup after the wipe? Should I have backed up everything except verizon apps if I don't want these? Should I just restore those apps where I want my old data (like game progress)?
Thanks in advance for any help. I have learned a lot from these forums but I feel I need a bit more clarifications before I proceed with a task that may be damaging for my device.
Slartibartfast_ said:
Long time lurker (though I can't say I always understood everything I read), first time poster.
I've had several iPhones in the past and I finally decided to try the other option. I got a Verizon GS3 last November and I couldn't be happier.
However, like many others, I'm looking to get more from my phone. I do like TouchWiz (I have used a Nexus 4 for a week and didn't like the stock android), so I want to stay with about the same UI that I have now. I did some research and found that Synergy is probably the best option for me in terms of getting a bit more from my phone but still staying with (mostly) the same UI. Of course, getting rid of all the annoying Verizon apps is a huge bonus too.
This is what I have done already:
Used this method to root and unlock my bootloader: http://forum.xda-developers.com/showthread.php?t=2332825
Used TWRP to make a full backup of my phone to an external SD card
Used Titanium Backup to make a full backup of my apps to an external SD card
Here are my questions:
I have the latest Verizon OTA installed (June 20th, I535VRBMF1). I have read all the posts from the last 14 days on the Synergy thread and I think I understand that since my phone has a newer firmware than the one in the latest synergy ROM, I will need to downgrade my firmware before installing the ROM to avoid camera and wifi problems. Is this correct? Someone linked there to I535VRBMB1_firmware.zip. How do I install this firmware? I have ODIN but when I choose PDA it will not let me choose the zip file. When I extract it, ODIN doesn't find anything too.
What kind of wipe should I perform before I flash to Synergy? Should I take my SD card out for the wipe or leave it in? Do I even need to wipe?
Can I install the ROM from ROM Manager or should I always use recovery mode and TWRP?
Is it recommended to just restore my Titanium full backup after the wipe? Should I have backed up everything except verizon apps if I don't want these? Should I just restore those apps where I want my old data (like game progress)?
Thanks in advance for any help. I have learned a lot from these forums but I feel I need a bit more clarifications before I proceed with a task that may be damaging for my device.
Click to expand...
Click to collapse
1 - You can roll back to MB1, or flash a kernel that supports the camera w/MF1. The camera not working seems to be the primary issue. I know Ktoonsez kernel works as do a couple of others.
2 - Wipe system, cache and Dalvik. You don't need to do anything with your card.
3 - At least the first time, I'd recommend using TWRP in recovery mode to flash your new ROM. Someone else may have a different opinion, but you'll already be in TWRP to wipe everything.
4 - Different people have different experiences with TiBU. Most would recommend not restoring system data, but apps(non-system) and app. data is usually okay.
lvgdgts said:
1 - You can roll back to MB1, or flash a kernel that supports the camera w/MF1. The camera not working seems to be the primary issue. I know Ktoonsez kernel works as do a couple of others.
2 - Wipe system, cache and Dalvik. You don't need to do anything with your card.
3 - At least the first time, I'd recommend using TWRP in recovery mode to flash your new ROM. Someone else may have a different opinion, but you'll already be in TWRP to wipe everything.
4 - Different people have different experiences with TiBU. Most would recommend not restoring system data, but apps(non-system) and app. data is usually okay.
Click to expand...
Click to collapse
I appreciate your detailed response!
I'm probably going to attempt this tomorrow. Will report back with what my results. It looks like BoneStock might be another good option for me + save me the kernel replacement or firmware flash. I have some reading to do now
Slartibartfast_ said:
Here are my questions:
I have the latest Verizon OTA installed (June 20th, I535VRBMF1). I have read all the posts from the last 14 days on the Synergy thread and I think I understand that since my phone has a newer firmware than the one in the latest synergy ROM, I will need to downgrade my firmware before installing the ROM to avoid camera and wifi problems. Is this correct? Someone linked there to I535VRBMB1_firmware.zip. How do I install this firmware? I have ODIN but when I choose PDA it will not let me choose the zip file. When I extract it, ODIN doesn't find anything too.
Click to expand...
Click to collapse
Just to add onto lvgdgts' post: files ending with ".zip" are flashed in recovery, files ending with ".tar" or ".tar.md5" are flashed via Odin.
SlimSnoopOS said:
Just to add onto lvgdgts' post: files ending with ".zip" are flashed in recovery, files ending with ".tar" or ".tar.md5" are flashed via Odin.
Click to expand...
Click to collapse
Thanks!
I decided to go with BoneStock 3.1. Whole process took less than half an hour. Used TWRP manager to wipe+install the ROM. Restore from Titanium restored 95% of my stuff, only needed to manually restore my text messages.
Thanks for the help!
I was tinkering with my TF101 and sort of accidentally (lol) overwrote my installation of Timduru's KatKiss-4.3.1_029.zip with his KatKiss-4.4.2_016.zip without wiping anything before doing so. (Actually didn't have any data to speak of - as I formatted and wiped in proper fashion on the install of KatKiss-4.3.1_029), and it hadn't been run for more than a couple of days.
I've developed a severe addition to ROM experimentation, and so may install and backup every few days it seems. Don't have a nickname for that habit yet, but I sense that they are many similar addicts around this site.
What I would like to know, since all seems, at least to this n00b, to be just fine - what "might" happen w/ my TF101 since the overwrite of a newer ROM?
Staying put, until I hear from a forum guru, or at least anyone with more experience than me (and that will include most all members).
Thanks,
Cal
If you overwrite a ROM with a different one (different android version, or by a different developer) you may run into issues where it will not boot, or it may run poorly, random reboots, sleep o death.
When changing ROMs it is HIGHLY recommended to wipe the system, caches and the data partition (wiping data is not the same as FORMAT DATA in TWRP). There are some system settings stored in the /data/ partition that may conflict with different ROMs.
Most of TimDuru's KatKiss ROMs you can forward flash (even to new versions of Android) but you CANNOT go backwards. I flashed from 4.2.2 to 4.3 without wiping data and had no issues. However, if you tried to flash from 4.3 to 4.2.2 without wiping data, it will not boot until you wipe the data partition.
I have not tried this with the 4.4 version of his ROM (I am still on 4.3 for now.)
Oh, and yes, the addiction is called CrackFlashing.
Always ALWAYS make a backup in TWRP before flashing a new ROM or even an upgrade to the current ROM. If you want to go back to 4.3, make a backup and then use Titanium Backup Pro version to extract any apps and data from the 4.4 version and restore to 4.3. Do not restore any system settings or apps.
frederuco said:
<snipped a bit>
When changing ROMs it is HIGHLY recommended to wipe the system, caches and the data partition (wiping data is not the same as FORMAT DATA in TWRP). There are some system settings stored in the /data/ partition that may conflict with different ROMs.
Most of TimDuru's KatKiss ROMs you can forward flash (even to new versions of Android) but you CANNOT go backwards. I flashed from 4.2.2 to 4.3 without wiping data and had no issues. However, if you tried to flash from 4.3 to 4.2.2 without wiping data, it will not boot until you wipe the data partition.
Oh, and yes, the addiction is called CrackFlashing.
Always ALWAYS make a backup in TWRP before flashing a new ROM or even an upgrade to the current ROM. <some stuff snipped>
Click to expand...
Click to collapse
Ahh...then the addiction is obviously not curable unless one destroys the tablet, BUT the new ROM may be just fine as is, I take it. That was what I was hoping to hear.
Thanks, and any idea when a new experimental ROM will come from Tim? Just felt a slight twitch. I've tried the other team's creations and seem to only feel really satisfied with Kits - (guess 'CrackFlashing' addiction picks a really hard one to withdraw from).
Many thanks!
Cal
Cal-123 said:
Ahh...then the addiction is obviously not curable unless one destroys the tablet, BUT the new ROM may be just fine as is, I take it. That was what I was hoping to hear.
Thanks, and any idea when a new experimental ROM will come from Tim? Just felt a slight twitch. I've tried the other team's creations and seem to only feel really satisfied with Kits - (guess 'CrackFlashing' addiction picks a really hard one to withdraw from).
Many thanks!
Cal
Click to expand...
Click to collapse
I think it will be a while until timduru starts to work in a experimental rom , since there is no Android 5 yet.
But Tim has marked katkiss as stable and for my daily use it is. But you could try 4.4.2.
schwigi said:
I think it will be a while until timduru starts to work in a experimental rom , since there is no Android 5 yet.
But Tim has marked katkiss as stable and for my daily use it is. But you could try 4.4.2.
Click to expand...
Click to collapse
Read the original post again -- I've been on the 4.4.2_16 forever now it seems!! The urge to try something new is over-bearing! :silly: :victory:
Ah-Ha! I see that Tim's put up a new 'stable' one. KK 4.4.2_17! Yeah!! This should be a super easy fix for the 'crack-itis' I have developed...as I will overwrite this one also.
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,
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 -.-)