Related
SuperMan-Rom V1.8.1 Aroma - AP will not boot (integrity verification failed)
On My S7 edge, thought I'd give it another go at trying to root since this rom claims to be almost stock with an option to get rid of all the samsung rubbish (like s-voice) that you don't use ever.
Followed all the steps to root, ON STOCK OS, entered developer mode, allowed OEM, allowed USB debugging, turn off verify installs by USB abd. Now It seems the phone is prepped and ready to go.
Flashed TWRP with latest ODIN 3.11, made a backup of stock OS, back in download mode and flashed required bootloader and modem (BL and CP), boot again into recovery to flash AP (SuperMan-Rom_SM-G93XF_V1.8.1.zip). Went through all the process and it seems fine until 1st boot.
***Every try is showing "Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."***
Have I Done something wrong to be showing this error every time????
I had the same error message. The cause was that my device was encrypted. TWRP can't handle encryption on the S7 yet. Reboot into TWRP and look at the logs. If it says it couldn't mount /data, then this is probably the same issue I had.
To fix it, I restored the backup OS from TWRP, made a backup of all apps and data to external SD using Titanium Backup and wiped the encrypted partition in TWRP (which removes the encryption and all data). There may be better ways, but this one worked for me.
@Davebnly You need to take backup of the Internal Storage data and then do a wipe using TWRP, Since TWRP cannot handle the Samsung's Encryption the only way to bypass this is by formatting again. This is already mentioned in the Official TWRP Installation post here.
I have this same error after flashing a custom ROM. I did not take a backup of the old stock ROM as it's a new phone and I didn't think I needed to!
Can anyone tell me, if I flash the stock ROM will it let me into the device again?
Is there anyway to wipe the encrypted drive without installing stock ROM?
*UPDATE: I just logged into recovery and did a factory reset and it loaded the custom ROM. Not as lengthy a solution as I expected!
Do these exact steps, Do not miss.
1. Reboot to recovery.
2. Do a data wipe (WIPE>FORMAT DATA) And Say "Yes"
3.Go to Reboot and Reboot back to recovery.
4.Download DM Verify Disabler https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ , Get the latest.
5.Copy in to the phone and flash it.
6.Go to Reboot and Reboot back to recovery.
7.Now Flash any rom as you wish.
8.Make Sure to Wipe Dalvik, Cache after.
Enjoy!!
Shameera_N said:
Do these exact steps, Do not miss.
Click to expand...
Click to collapse
Man, you just saved my life!
Thanks you very much.
Shameera_N said:
Do these exact steps, Do not miss.
1. Reboot to recovery.
2. Do a data wipe (WIPE>FORMAT DATA) And Say "Yes"
3.Go to Reboot and Reboot back to recovery.
4.Download DM Verify Disabler , Get the latest.
5.Copy in to the phone and flash it.
6.Go to Reboot and Reboot back to recovery.
7.Now Flash any rom as you wish.
8.Make Sure to Wipe Dalvik, Cache after.
Enjoy!!
Click to expand...
Click to collapse
Hi, I'm sorry but what does all that mean? Reboot to recovery??? The only option on my phone is the button to RESET DEVICE and I have two weeks worth of photos and videos that I have not backed up yet! Please help!!! FYI, I have the same exact message telling me to erase all my data because I need to reset my device. Nooo, I am so scared right now.
Hello guys .
This is a guide to flash lineage os 15.1 or any other oreo rom on mi a1 without any fuss, bugs, wiping internal storage. And update it by dirty flashing it. I personally use this method and others have also used resulted in booting safely with zero bugs in the rom, no force closes.
So here you go :-
1- boot to twrp
2- wipe system,cache,data
3- check on which slot you are.
4- if you are on A, change to B (after wiping).
5- boot to bootloader and boot to twrp which I gave.
6- wipe slot B also. (System,cache,data)
7. Don't touch slots and boot to recovery.
8- just flash los15.1 rom from there and nothing else.
9- go to bootloader and again boot to twrp
10- flash gapps and boot to bootloader.
11- again boot to twrp which I gave and flash magisk.
12- reboot.
Enjoy. You have los 15.1 without wiping internal or downgrading to nougat or wiping internal storage.
So now here's the guide to update it. (Dirty flash)
(Remember to remove your pattern, pin, password before flashing or backing up)
1- Backup your data using twrp which I linked down below.
2- boot to twrp which I gave you.
3- wipe system,cache,data
4- check on which slot you are.
5- if you are on A, change to B (after wiping).
6- boot to bootloader and boot to twrp which I gave.
7- wipe slot B also. (System,cache,data)
8- Don't touch slots and boot to recovery which i have
linked down below .
9- just flash los15.1 rom from there and nothing else.
10- go to bootloader and again boot to twrp which I gave.
11- flash gapps and boot to bootloader.
12- again boot to my twrp and flash magisk.
12- reboot. Let it boot completely and skip the setup.
13- boot to twrp i linked down.
14-just restore your data backup and reboot.
Congo you have successfully updated your rom without wiping data and also whosoever is facing bugs like fp not working and other bugs use this method. Everything will surely work.
Anyone who has a problem can message me on telegram. Username- droidreboot
Hit the Thanks button if it helped
Have a good day.
Twrp link- https://www.androidfilehost.com/?fid=818070582850498337
*Thread Updated. Now we can use 1 recovery. It'll do all work*
It actually works and doesn't raise or gives any bugs/issues. Great work bro!
bikramsingh.97 said:
It actually works and doesn't raise or gives any bugs/issues. Great work bro!
Click to expand...
Click to collapse
Thanks ??
Nobitaa said:
Hello guys .
This is a guide to flash lineage os 15.1 or any other oreo rom on mi a1 without any fuss, bugs, wiping internal storage. And update it by dirty flashing it. I personally use this method and others have also used resulted in booting safely with zero bugs in the rom, no force closes.
So here you go :-
1- boot to twrp which I gave you.
2- wipe system,cache,data
3- check on which slot you are.
4- if you are on A, change to B (after wiping).
5- boot to bootloader and boot to twrp which I gave.
6- wipe slot B also. (System,cache,data)
7. Don't touch slots and boot to deadman's recovery.
8- just flash los15.1 rom from there and nothing else.
9- go to bootloader and again boot to twrp which I gave.
10- flash gapps and boot to bootloader.
11- again boot to twrp which I gave and flash magisk.
12- reboot.
Enjoy. You have los 15.1 without wiping internal or downgrading to nougat or wiping internal storage.
So now here's the guide to update it. (Dirty flash)
(Remember to remove your pattern, pin, password before flashing or backing up)
1- Backup your data using twrp which I linked down below.
2- boot to twrp which I gave you.
3- wipe system,cache,data
4- check on which slot you are.
5- if you are on A, change to B (after wiping).
6- boot to bootloader and boot to twrp which I gave.
7- wipe slot B also. (System,cache,data)
8- Don't touch slots and boot to deadman's recovery.
9- just flash los15.1 rom from there and nothing else.
10- go to bootloader and again boot to twrp which I gave.
11- flash gapps and boot to bootloader.
12- again boot to my twrp and flash magisk.
12- reboot. Let it boot completely and skip the setup.
13- boot to twrp i linked down.
14-just restore your data backup and reboot.
Congo you have successfully updated your rom without wiping data and also whosoever is facing bugs like fp not working and other bugs use this method. Everything will surely work.
Hit the Thanks button if it helped
Have a good day.
Twrp link- https://drive.google.com/file/d/1eM-tMUcEWx_e0iTdnXwSyOk7B1mgO1Zi/view?usp=sharing
Click to expand...
Click to collapse
after updating the latest OS, apps which are installed in before build will erased ah?
bikramsingh.97 said:
It actually works and doesn't raise or gives any bugs/issues. Great work bro!
Click to expand...
Click to collapse
dvishalkhatri said:
after updating the latest OS, apps which are installed in before build will erased ah?
Click to expand...
Click to collapse
If you're updating none of your apps or data will get erased. But if you are moving from stock oreo to this rom, it's like resetting your device. That's it. ?
not working while booting in dead man recovery 0mb internal error
Nobitaa said:
If you're updating none of your apps or data will get erased. But if you are moving from stock oreo to this rom, it's like resetting your device. That's it. ?
Click to expand...
Click to collapse
Actually at start I didn't backup the data in twrp that's y it happened
dvishalkhatri said:
Actually at start I didn't backup the data in twrp that's y it happened
Click to expand...
Click to collapse
Backup and restore backup only if you are updating. Not upgrading from stock rom to any oreo rom. ?
[email protected] said:
not working while booting in dead man recovery 0mb internal error
Click to expand...
Click to collapse
Place rom in memory card. Bug in deadman recovery
Nobitaa said:
Only update
Click to expand...
Click to collapse
While updating from previous ROM i tried to update but all apps got erased ... After i tried the data backup in TWRP then only i got my apps back...
[email protected] said:
not working while booting in dead man recovery 0mb internal error
Click to expand...
Click to collapse
Use sd card
Thanks and If I want to flash the same stock rom or other rom without wipe data do I need to wipe both system a/b slot?
now i am in big trouble my phone is not booting it's restarting and i'm not able to restore the backup while restoring backup it's showing no partition selected please help please
dvishalkhatri said:
While updating from previous ROM i tried to update but all apps got erased ... After i tried the data backup in TWRP then only i got my apps back...
Click to expand...
Click to collapse
Not possible. I'm personally using this method. I'll try making a video tutorial on this.
Nobitaa said:
Not possible. I'm personally using this method. I'll try making a video tutorial on this.
Click to expand...
Click to collapse
Ok sure...
Nobitaa said:
Not possible. I'm personally using this method. I'll try making a video tutorial on this.
Click to expand...
Click to collapse
Your tutorial says wipe data and data contain all apps!
[email protected] said:
now i am in big trouble my phone is not booting it's restarting and i'm not able to restore the backup while restoring backup it's showing no partition selected please help please
Click to expand...
Click to collapse
Message me on telegram. Username- droidreboot
samuele94 said:
Thanks and If I want to flash the same stock rom or other rom without wipe data do I need to wipe both system a/b slot?
Click to expand...
Click to collapse
You have ro to wipe data if you are changing roms. Like if you are on lineage, and you wanna install resurrection remix then you'll have to wipe system cache data in both slots. And if developer of lineage pushes an update and you're on lineage then you don't have to wipe data. I mean if updating you have to make a backup then wipe. Then after first boot restore that. Don't do this if you're changing roms. You'll get a bootloop
samuele94 said:
Your tutorial says wipe data and data contain all apps!
Click to expand...
Click to collapse
It says if you're upgrading from stock then wipe data. And if you're updating from old lineage build to new first make a backup then wipe and after first boot restore the backup. Read carefully.
Nobitaa said:
You have ro to wipe data if you are changing roms. Like if you are on lineage, and you wanna install resurrection remix then you'll have to wipe system cache data in both slots. And if developer of lineage pushes an update and you're on lineage then you don't have to wipe data. I mean if updating you have to make a backup then wipe. Then after first boot restore that. Don't do this if you're changing roms. You'll get a bootloop
Click to expand...
Click to collapse
But ,sorry, for reinstall the same rom i need to wipe both system partition (a/b) before flash?
I was running lineage-16.0-20181203_184022-UNOFFICIAL-enchilada just fine with open gapps nano and Magisk 17.1.
I attempted to upgrade to lineage-16.0-20181208_183559-UNOFFICIAL-enchilada, but I ran into issues with gapps force closing.
I attempted to restore my TWRP nandroid backups, but the attempts at restoring them just put me in a bootloop into TWRP.
Therefore, I am attempting to get back to OOS 9.0.2, OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9, with a clean flash, following the process:
Fastboot into TWRP with fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
Wipe -> Advanced Wipe -> Cache, System, Data, Internal Storage
adb push OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9.zip and twrp-3.2.3-x_blu_spark_v9.86_op6.zip
Install -> OOS 9.0.2 and then TWRP
Reboot into System
No matter how many times I try this, the first boot fails with a vibration from the phone and it reboots into the blu_spark TWRP.
I have also tried the above process from inside the installed TWRP instead of from a fastbooted TWRP. I have also tried the above process with lineage-16.0-20181203_184022-UNOFFICIAL-enchilada.zip instead of OOS.
What could possibly be wrong? Isn't this a completely clean install?
MaxRabbit said:
I was running lineage-16.0-20181203_184022-UNOFFICIAL-enchilada just fine with open gapps nano and Magisk 17.1.
I attempted to upgrade to lineage-16.0-20181208_183559-UNOFFICIAL-enchilada, but I ran into issues with gapps force closing.
I attempted to restore my TWRP nandroid backups, but the attempts at restoring them just put me in a bootloop into TWRP.
Therefore, I am attempting to get back to OOS 9.0.2, OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9, with a clean flash, following the process:
Fastboot into TWRP with fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
Wipe -> Advanced Wipe -> Cache, System, Data, Internal Storage
adb push OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9.zip and twrp-3.2.3-x_blu_spark_v9.86_op6.zip
Install -> OOS 9.0.2 and then TWRP
Reboot into System
No matter how many times I try this, the first boot fails with a vibration from the phone and it reboots into the blu_spark TWRP.
I have also tried the above process from inside the installed TWRP instead of from a fastbooted TWRP. I have also tried the above process with lineage-16.0-20181203_184022-UNOFFICIAL-enchilada.zip instead of OOS.
What could possibly be wrong? Isn't this a completely clean install?
Click to expand...
Click to collapse
Try installing magisk too.
mikex8593 said:
Try installing magisk too.
Click to expand...
Click to collapse
Thanks for the suggestion. Tried installing magisk in between OOS and the TWRP, and then also tried installing OOS, TWRP, rebooting, and installing magisk. No luck either way.
Well, this was a nightmare. Finally fixed it by:
fastbooting into twrp
wiping everything in twrp
flashing oos 9.0.2
NOT installing twrp
bootlooping into oneplus recovery
clearing ALL data through oneplus recovery (after backing up via ADB)
reboot
phone booted up just fine
Wow. Never seen those particular steps mentioned.
After that, I was able to flash OOS 9.0.2 again, then flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada & TWRP, boot LOS, reboot into TWRP, wipe everything, flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada again, boot into LOS, reboot into TWRP, restore my system, data, and boot backups from TWRP, and I'm finally back up and running with a fully working backup.
MaxRabbit said:
Well, this was a nightmare. Finally fixed it by:
fastbooting into twrp
wiping everything in twrp
flashing oos 9.0.2
NOT installing twrp
bootlooping into oneplus recovery
clearing ALL data through oneplus recovery (after backing up via ADB)
reboot
phone booted up just fine
Wow. Never seen those particular steps mentioned.
After that, I was able to flash OOS 9.0.2 again, then flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada & TWRP, boot LOS, reboot into TWRP, wipe everything, flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada again, boot into LOS, reboot into TWRP, restore my system, data, and boot backups from TWRP, and I'm finally back up and running with a fully working backup.
Click to expand...
Click to collapse
this could have been done in twrp. all you had to do was format data
the correct way is this.
fastbooting into twrp
flashing oos 9.0.2
flashing twrp, to keep twrp.
format data.
install any mod you want, like root.
reboot
this is require only when going from aosp to oos again.
MrSteelX said:
this could have been done in twrp. all you had to do was format data
the correct way is this.
fastbooting into twrp
flashing oos 9.0.2
flashing twrp, to keep twrp.
format data.
install any mod you want, like root.
reboot
this is require only when going from aosp to oos again.
Click to expand...
Click to collapse
How come that would have worked, but wiping system and data and then installing OOS 9.0.2 doesn't? Shouldn't you end up at the same point either way, with a clean OOS 9.0.2 in system and wiped data?
Format is the answer.
MaxRabbit said:
How come that would have worked, but wiping system and data and then installing OOS 9.0.2 doesn't? Shouldn't you end up at the same point either way, with a clean OOS 9.0.2 in system and wiped data?
Click to expand...
Click to collapse
just simply flash oss9.0.2 two time using twrp then get hold of 9.0.2 boot img go back to twrp and the select flash image flash the image and let it boot.
if it works toss a thanks.
MaxRabbit said:
Well, this was a nightmare. Finally fixed it by:
fastbooting into twrp
wiping everything in twrp
flashing oos 9.0.2
NOT installing twrp
bootlooping into oneplus recovery
clearing ALL data through oneplus recovery (after backing up via ADB)
reboot
phone booted up just fine
Wow. Never seen those particular steps mentioned.
After that, I was able to flash OOS 9.0.2 again, then flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada & TWRP, boot LOS, reboot into TWRP, wipe everything, flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada again, boot into LOS, reboot into TWRP, restore my system, data, and boot backups from TWRP, and I'm finally back up and running with a fully working backup.
Click to expand...
Click to collapse
Thank you for this. I was trying to dirty flash 9.0.2 to fix a notification issue and ended up in the same situation as you. Format ended up fixing it. Only crappy part is I lost about all my text messages with my SO. Google said it has a 2mb backup for SMS so I'm hoping it got all 30k+ of it
MrSteelX said:
this could have been done in twrp. all you had to do was format data
the correct way is this.
fastbooting into twrp
flashing oos 9.0.2
flashing twrp, to keep twrp.
format data.
install any mod you want, like root.
reboot
this is require only when going from aosp to oos again.
Click to expand...
Click to collapse
Tried this and it ended up causing the exact same problem. The folks installing the new OB8/9 seems to be having similar issues. Not sure what's going on.
its because of security patch. 9.0.2 has nov sec patch, lineage you flashed has dec sec patch. i have experienced this in pixel rom. just flash lineage Nov build, then wipe data and system and flash OOS 9.0.2 and twrp.
do a clean flash
MaxRabbit said:
I was running lineage-16.0-20181203_184022-UNOFFICIAL-enchilada just fine with open gapps nano and Magisk 17.1.
I attempted to upgrade to lineage-16.0-20181208_183559-UNOFFICIAL-enchilada, but I ran into issues with gapps force closing.
I attempted to restore my TWRP nandroid backups, but the attempts at restoring them just put me in a bootloop into TWRP.
Therefore, I am attempting to get back to OOS 9.0.2, OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9, with a clean flash, following the process:
Fastboot into TWRP with fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
Wipe -> Advanced Wipe -> Cache, System, Data, Internal Storage
adb push OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9.zip and twrp-3.2.3-x_blu_spark_v9.86_op6.zip
Install -> OOS 9.0.2 and then TWRP
Reboot into System
No matter how many times I try this, the first boot fails with a vibration from the phone and it reboots into the blu_spark TWRP.
I have also tried the above process from inside the installed TWRP instead of from a fastbooted TWRP. I have also tried the above process with lineage-16.0-20181203_184022-UNOFFICIAL-enchilada.zip instead of OOS.
What could possibly be wrong? Isn't this a completely clean install?
Click to expand...
Click to collapse
You know if all else fails you could always download the Qualcomm MSM tool and boot into Qualcomm mode (with the phone off hold vol down button for about 10-15 seconds and plug into computer), you won't see anything on the screen, load up the tool and it shall put u back to full stock. This will solve all and any sort of bricking which if you flash alot you will by default probably learn how to use
fastboot into twrp
Flash TWRP within twrp
Format all data.
Reboot recovery
transfer OOS
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot recovery
Flash kernel/magisk/etc
Reboot system.
I just want to tell you that I love you. The format data finally fixed this for me.
MrSteelX said:
this could have been done in twrp. all you had to do was format data
the correct way is this.
fastbooting into twrp
flashing oos 9.0.2
flashing twrp, to keep twrp.
format data.
install any mod you want, like root.
reboot
this is require only when going from aosp to oos again.
Click to expand...
Click to collapse
heelo guys
im having a problems flashiing roms. i tryed Paranandroid, RR and crDroid...
after i flash them i get bootloop into TWRP. whac can i be doing wrong?
the steps i do are this:
flash ROM -Flash TWRP - REBOOT to TWRP - Flash Gapps - Flash Magisk - Then bootloop
can anyone please help me?
anyone? please?
first install OOS 10 on both slots (i have open beta 4)..than boot to OOS 10, not setup! Then boot TWRP and factory reset, not FORMAT DATA!!! Then reboot TWRP and install ROM, TWRP, reboot, install Gapps and Magisk (optional)
mcboums said:
first install OOS 10 on both slots (i have open beta 4)..than boot to OOS 10, not setup! Then boot TWRP and factory reset, not FORMAT DATA!!! Then reboot TWRP and install ROM, TWRP, reboot, install Gapps and Magisk (optional)
Click to expand...
Click to collapse
hello mate
and when i install Rom, do i need to install on both slots or i can have one has backup (its what i have been doing till now)?
and when i factory reset, what will i lose?
Well, it is difficult to say. Usually, every ROM has its thread, its instructions and its community that helps with problems related to installing that ROM.
It could be a few things:
1) I do not see any mention about wiping data. Usually you need to wipe data and wipe system partition in twrp before you install a new ROM. Maybe that is the issue. However, what you need to wipe is ROM specific.
2) Check prerequisites, what ROM version you need to be running before you flash. Sometimes that matters.
3) OnePlus 6 has these A/B slots that I do not fully understand. From what I have read, if you are running on slot A, update installs on slot B, and then you reboot to slot B and cycle continues. BUT DO NOT TRUST ME ON THIS. You should read yourself. Anyway, sometimes people recommend flashing both slots A and B. For some ROMs. For LineageOS, for example, that is not necessary.
oh, factory reset damn i would want to configure everything again
I think first.
You have to WIPE data, all. Factory wipe option.
Then boot into twrp
First, flash OOS, followed by TWRP
Reboot to Recovery using twrp itself.
And then again flash OOS and TWRP.
Reboot to recovery again (using the option in twrp itself)
Finally, then install your rom followed by gapps etc etc
Then it should work....
is there anyway to do this without factory reset?
no
Hello everybody,
I bought a Oneplus 7 Pro a few days ago and I'm preparing it for my daily usage. It's my fourth Android smartphone, and the third Oneplus. So far, I managed to flash everyone of them, with no major issues.
And then, the Oneplus 7 Pro suddenly appeared
I used this tutorial to unlock the bootloader and flash the custom recovery.
From my understanding, the custom recovery is flashed in the Recovery Ramdisk and available for both A & B slots.
For now, I have A and B slots with stock OSS, unlocked bootloader, custom recovery and Magisk. All of this is working.
There began my problems. I want to flash a custom ROM without Gapps and I fail to do it. All instructions around ROM threads seems different to me, I don't get the thing about A & B slots, when I flash one rom, it boots as usual on the stock ROM, if I flash both slots, It causes bootloops and if I manage to launch the recovery, my internal storage isn't detected and I can't restore any backup.
I already used MSMDownload to restore the phone completely once.
Can somebody explain to my dumb person how to do it proprely ? Thanks in advance ! :fingers-crossed:
TL;DR : I fail to flash a custom ROM and make it work.
Yes I had same issues when rooted, it means you lost root. You can try tool all in one to flash recovery and magesik via fastboot. If that doesn't restore your access, on twrp you will have to type in format, then mount, then add rom to storage(this method wipes everything beware)
djhulk2 said:
Yes I had same issues when rooted, it means you lost root. You can try tool all in one to flash recovery and magesik via fastboot. If that doesn't restore your access, on twrp you will have to type in format, then mount, then add rom to storage(this method wipes everything beware)
Click to expand...
Click to collapse
For now, my phone is working nicely. But that's the process of flashing a new ROM that fails. Recovery and Magisk are already and working.
Factory reset
Flash rom
Flash twrp installer
Reboot recovery
Format data
Reboot system
i boot all roms with these steps
WesTD said:
Factory reset
Flash rom
Flash twrp installer
Reboot recovery
Format data
Reboot system
i boot all roms with these steps
Click to expand...
Click to collapse
Thanks, I will try.
When you flash the ROM, does TWRP tell you that if you want to continue you need to reboot recovery ? If so, do you ? Do you reboot recovery on the same slot, or do you flash both ?
draentor said:
Thanks, I will try.
When you flash the ROM, does TWRP tell you that if you want to continue you need to reboot recovery ? If so, do you ? Do you reboot recovery on the same slot, or do you flash both ?
Click to expand...
Click to collapse
Nope, it doesnt tell you anything. Just reboot recovery from reboot menu. Don't touch the slot options
Thanks for your advices.
I'm trying right now, here's my steps :
- Wipe Data, Cache, Dalvik Cache (the standard Factory Reset)
- Install ROM : TWRP logs show that he's flashing on inactive slot A, then B. After that logs said " To flash additional zips, please reboot recovery to switch to the updated slot ". I'm going back on the menu
- Install TWRP Installer like previously
- Reboot Recovery : TWRP ask me if I want to install the TWRP App, I dismiss. After reboot of the recovery, it asks if I want to keep System Read Only, I swipe to allow modifications
- Wipe Data : Can't do it because TWRP is unable to mount storage. And after further investigations, I'm now on slot A, not B as before.
- Reboot recovery to slot B
- Wipe Data on slot B
- Reboot system
And It still booting on the stock Oxygen OS Rom, not the custom one installed before. I'm lost
The problem is that you are not performing factory reset.
Wipe data is not enough,you gotta go to wipe-format data-enter yes and swipe.
That is why you are getting bootloops and twrp unable to mount storage problem.
A/B is pretty simple.
You got two slots for many partitions like system vendor boot and all,but a single data partition.
Flash a rom from one slot,it always gets flashed to the other slot no matter what.So next time you reboot to recovery or system it's gonna be on the other slot.So here is the problem..one rom cannot decrypt data which was initially encrypted by another rom..so you gotta perform a data format instead of wipe.Thats it.
draentor said:
Thanks for your advices.
I'm trying right now, here's my steps :
- Wipe Data, Cache, Dalvik Cache (the standard Factory Reset)
- Install ROM : TWRP logs show that he's flashing on inactive slot A, then B. After that logs said " To flash additional zips, please reboot recovery to switch to the updated slot ". I'm going back on the menu
- Install TWRP Installer like previously
- Reboot Recovery : TWRP ask me if I want to install the TWRP App, I dismiss. After reboot of the recovery, it asks if I want to keep System Read Only, I swipe to allow modifications
- Wipe Data : Can't do it because TWRP is unable to mount storage. And after further investigations, I'm now on slot A, not B as before.
- Reboot recovery to slot B
- Wipe Data on slot B
- Reboot system
And It still booting on the stock Oxygen OS Rom, not the custom one installed before. I'm lost
Click to expand...
Click to collapse
lol i wrote all steps but you didn't do all of them. Use swipe to wipe for factory reset and you didn't format data
Joker123## said:
The problem is that you are not performing factory reset.
Wipe data is not enough,you gotta go to wipe-format data-enter yes and swipe.
That is why you are getting bootloops and twrp unable to mount storage problem.
A/B is pretty simple.
You got two slots for many partitions like system vendor boot and all,but a single data partition.
Flash a rom from one slot,it always gets flashed to the other slot no matter what.So next time you reboot to recovery or system it's gonna be on the other slot.So here is the problem..one rom cannot decrypt data which was initially encrypted by another rom..so you gotta perform a data format instead of wipe.Thats it.
Click to expand...
Click to collapse
Thanks for the explanation !
WesTD said:
lol i wrote all steps but you didn't do all of them. Use swipe to wipe for factory reset and you didn't format data
Click to expand...
Click to collapse
Well yes, I didn't understood the difference between Wipe and Format Data.
So let's resume :
Unlock Bootloader
Advanced -> Install Recovery Ramdisk : Install TWRP
Install -> Flash TWRP Installer
Install -> Flash Magisk
Reboot -> System : Reboot on stock OxygenOS Rooted
Then
Wipe -> Factory Reset : Wipe Data, Cache and Dalvik Cache, that means you just have to swipe on TWRP.
Install -> Flash ROM : Use the install function and install the ROM
Install -> Flash TWRP Installer : Don't reboot, go back and install as the previous step
Reboot -> Recovery : Reboot TWRP and it automatically load the other slot
Wipe -> Format Data : Click and type yes
Reboot -> System : Just reboot and it should load the installed ROM
is wiping internal storage compulsory?
aaryan45 said:
is wiping internal storage compulsory?
Click to expand...
Click to collapse
How would you do it ? This is an open discussion, I can't find one and only way of doing it
aaryan45 said:
is wiping internal storage compulsory?
Click to expand...
Click to collapse
Not wiping.. formatting..that is compulsory if your current data is encrypted
After multiple tries to verify the process :
Wipe -> Factory Reset + : Wipe Data, System, Cache and Dalvik Cache
Install -> Flash ROM : Use the install function and install the ROM
Install -> Flash TWRP Installer : Don't reboot, go back and install as the previous step
Reboot -> Recovery : Reboot TWRP and it automatically load the other slot
Wipe -> Format Data : Click and type yes
Reboot -> System : Just reboot and it should load the installed ROM
Install -> Magisk
Reboot -> System
Install -> Whathever you want
Reboot -> System
It worked !