Database Users

Kate CM13 Flash/Repair guide.

Dwl99 put a great guide together, the link is here:
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-special-edition-kate-t3523371
Another guide I found useful is http://en.miui.com/thread-363264-1-1.html
Full URL of original post is:
https://forums.whirlpool.net.au/forum-replies.cfm?t=2566258&p=6&#r120
Now, I did it in a slightly different way, I prefer my way because I believe it is safer but here goes:
0. Update Miui to latest version Using the OTA update or Fastboot/Miflash method mentioned above. (I have a guide in this thread)
Once up to date:
1. Unlock the boot loader using the official method, this can take two 2 three days using en.miui.com/unlock/
Download the unlock tool. - Enable unlock boot loader options in developer options on MIUI (This can be done by tapping 10 times quickly on "Miui Version" in the about phone section of the phone. After this, go to additional settings >Developer options > enable developer options and unlock boot loader.
Next simply follow the guide on the MIUI unlock tool to unlock boot loader.
2. Flash TWRP ZCX Version: http://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448
This version of TWRP allows you to see and backup ALL partitions of your Xiaomi device.
Make sure you boot into this TWRP after flashing so it sticks (otherwise your phone will not boot)
Use the settings to back up ALL partitions to your EXTERNAL SD card. Keep that safe for the future in case you break your phone or lose imei or whatever.
I recommend transferring this backup to a PC or desktop. - Once this is done, you can breathe easy, you will always have a complete full backup of your device should you break it, you can relax in the future.
3. After backing up all of the partitions to the external SD card:
Download some files on https://forums.whirlpool.net.au/forum-replies.cfm?t=2566258&p=6&#r120
The 4 main files you need are: 1 CM13 rom file, 2 TWRP Cofface Version, 3 the KATE version of CM13 firmware files (Whirlpool has this on his guide at the bottom edit) and 4 your favourite version of the Google apps @ opengapps.org
The version you will need is ARM64 version 6 for CM13.
Transfer these files to your phone external storage (We will be wiping internal storage).
4. Flash the Cofface edition of TWRP to your Phone either using Fastboot or TWRP.
The reason for this is I have found ZCX version, whilst awesome for seeing and backing up all parts of the MIUI phone, actually breaks non MIUI flashes because it is designed primarily to work well with MIUI Roms (hence we use them to back up)
All TWRP versions can be found here: http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708/
Once Cofface TWRP is flashed you can move onto step 5 – Flashing Roms.
*NOTE* I have read some people recommend ALKA TWRP to A) backup all partitions, but also B, to flash CM as it does all things. I am only sharing my personal experience of what I have done here, and Alka could work well, but I have not tested it.
All I can say is flashing CM13 with ZCX TWRP Broke my device. – But it was great for making backups.
5. Flashing. Here all you need to do is boot into Cofface TWRP and go to Wipe. Choose advanced options. And wipe ALL partitions you see (Don’t worry, Cofface will not let you wipe out your boot loader, Recovery, IMEI or anything else that is critical) – First flash CM13. Then next, flash the Kate CM13 firmware, and third flash Opengapps. 1 after another (I actually added all three zips in that order and let them flash all together)
6. Reboot and enjoy. You now have an Unrooted CM13 with google apps a working fingerprint reader working radio etc. Happy days.
7. – EMERGENCY FIX EMERGENCY FIX!!! – As I mentioned earlier, TWRP zcx broke my device when I flashed the Roms. I was facing a device decryption error and 0mb data problem.
I fixed this with this URL http://en.miui.com/thread-344450-1-1.html
There is a file there called TWRP_Kenzo_Fix.zip and a batch script that will restore your phone and rebuild the partitions and install Cofface twrp for you!!! So that’s a good option if you break it.
Hope that helps

ZCX-TWRP works perfect for CM-ROMs. I've flashed so many ROMs without any problem!

x720 partial unlocked bootloader? [SOLVED]

So I got my 6GB/64GB x720 yesterday. It had Google Play Store already installed (ordered it from HonorBuy) and asked me to install a 7MB OTA, so it seems it had a recent version of EUI on it. My idea was to put LineageOS 14.1 on it or if it wasn't stable enough for me, at least a debloated and rooted stock. So searched XDA and followed this HowTo. No Errors, flashboot oem device-info said, bootloader unlocked, perfekt. Installed TWRP, downloaded recent LineageOS and followed the guides to flash (wipe, ...). Unfortunately flashing never finished, I always had a full progress-bar and it stayed there without doing anything (ok, the device got hot). Thinking of a broken download, I redownloaded the ROM but same problem. So I started downloading other ROMs from XDA: Resurection Remix and OmniROM. Flashing-process went thru, but couldn't flash gapps and ROMs didn't boot at all. I was always only getting to the LeEco-Bootlogo with the chinese writings. So next thought was, maybe for some reason I can't install Lineage-based ROMs, let's figure out later and get a debloated stock ROM. So I downloaded MAURO V2.2_Free and gave it another try. Looked more promising, as the bootlogo was a little different, no more chinese writing but english. Unfortunately this was all I could see of MAURO as I only got a bootloop... so again reflashed MAURO and this time a single line in TWRP-output came to my eye "boot.img could not be written". I checked flashboot oem device-info after every flash and it always told me, bootloader is unlocked, but there seems to be something else that I'm missing that obviously still keeps the bootloader locked. I wiped the phone several times, even sdcard... nothing helped. The only method that worked for me to get a working rom running was by this guide, manualy flashing every bit of stock ROM with flashboot. With MAURO-ROM, I also tried to flash boot.img manually with flashboot, but that didn't work, either.
Anyone of you experienced the same? What am I missing? Or is this some new protection implemented by LeEco for the most recent devices? Any help really appreciated!
regards
CDFS

I have the same phone from Honorbuy, I flashed twrp using the tool by Mauronofrio and from the twrp wiped all and flashed the custom rom, all went ok, no errors at all! Glad to see you have solved anyway!

Thanks for the answer... no, it's not solved for me... still a lot of bloat on the phone I can't get rid of. Do you have a link for the tool you mentioned? Could be worth a try...

Hi! I've used this tool installing it on a Windows 7 64 system:
https://forum.xda-developers.com/le-pro3/development/tool-tool-one-mauronofrio-t3580611
Then turned ON the (original LeEco stock rom) usb debug option by the rom's developer options, then downloaded the LineageOS 14.1 by Team Superluminal in the phone's internal SD (the only SD it have!) + Arm64 nano Gapps, then with the tool gave a reboot in sideload mode. Then flashed the twrp recovery by the tool, restarted in recovery mode then executed a backup of ALL the "backupable" stuff (all the original rom and data and efs), then in wipe/advanced options I wiped dalvik, system, cache, data. Then in Advanced/file manager I wiped all the SD files with a dot ( . ) at the beginning of their names, then flashed the custom rom + gapps, reboot system, wait some minutes, done!

No luck with this tool, it doesn't even find my device. Any other ideas? I've read something for the x727, where they had to flash a 19s bootloader first, but I don't want to fiddle with flashing files that are not 100% meant for the x720...
CDFS

Solved! As I could install TWRP I just went the next step and installed SuperSU (rooted the phone) in order to at least debloat stock rom. During the installation of SuperSU I saw, that SuperSU obviously patches somehow the bootloader. After checking that SuperSU worked in the ROM, I was curious if this could be the missing part I was searching for. I tried to install a LineageOS-based ROM and BINGO! it just went straight through! From my previous phones I was used to just install TWRP, wipe anything and flash desired ROM. This seems to be different on this device... so the proper procedure to be able to flash any ROMs is: Install TWRP, root stock ROM, reboot so SuperSU is fully functional, then go back into TWRP, wipe, flash what you want.
CDFS

I hate to say it, but it's still not solved. After testing Resurrection Remix, I wanted to test turbos ROMs, so went to TWRP, wiped and flashed... and got the same behaviour as before, ROM not booting. Also installing SuperSU via TWRP again didn't help, so brought back the phone to stock 023S manualy with the guide by Presterin, installed TWRP again and also SuperSU. No Errors, but flashing a different ROM didn't worked. So for now I'm back to stock, rooted it and tried to debloat it by myself. The only difference between the successful flashing and the failed was the stock version: I had the 026S-update when I rooted the phone and successfuly could flash another ROM. My guess would be that LeEco changed something in the bootloader, but I have no chance to verify this. Anyone from the devs maybe who could look into this? If you need dumos, logs or anything like that, I would be happy to help.
CDFS

This seems unrelated to bootloader.
Anyway:
1. Make sure you got the latest firmware, if not sure:
1.1. Download latest OFFICIAL ROM
1.2. Rename the rom to a 'update.zip' and place it on phone's root directory.
1.3. Reboot to fastboot and flash STOCK RECOVERY
1.4. Reboot to recovery and flash, also check wipe data.
DO NOT FLASH STOCK ROM WITH TWRP! THIS WILL NOT WORK!
That's it, you should have the latest firmware now.
After booting to stock rom, reboot a few times is recommended.
2. Download latest OFFICIAL TWRP
2.1. Flash TWRP with fastboot.
2.2. Reboot to TWRP.
2.3. Download any custom rom of your choice.
2.4. Wipe.
2.5 Flash.
Done.

You can try to flash a stock, old rom using the "Qfil/FlashOne" way as suggested by Tryzex (read his thread and other related threads), then once you have got a stable, full working phone, you can (hopefully!) wait for a LeEco OTA automatic update that can "repair" the file system/partition structure (also bootloader I hope!).
Btw, to debloat it isn't necessary to root the phone, you can keep the phone unrooted & debloated using the file manager embedded in twrp recovery to delete/replace any file/app you want. I'm sorry I can't help you better, cheers and... good luck!
PS
I see now the post from Voron00, it's a good hint!

@voron00 thx for the steps described. I'm using the most recent, official TWRP (3.1.1). Latest Official Stock seems to be 023S on their site, even though there is a 026S update. However, I did this 026S-update and rooted again, but was to cusious if flashing would work now... so I tried flashing turbos MIUI... guess what? It worked. So for whatever reason I seem to have trouble when flashing from a 023S, but no problems when flashing from 026S. I don't quite understand why you think that my problem is not related to the bootloader? As mentioned in the OP, I could see in the logs that while flashing, some roms had thrown errors regarding writing the bootpartition.
CDFS

Seems as I found the culprit, somehow. At least I could flash two other ROMs without any problems. Obviously I mixed and partly missinterpreted some steps found in different threads and howtos. I had "rm -rf for formating" ticked all the time in TWRP. My flashing procedure is now as follows:
1. in TWRP settings check that "rm -rf instead of format" is NOT ticked
2. wipe Cache, System and Data
3. repair filesystem for Cache, System and Data and check that no errors occur
4. in TWRP settings tick "rm -rf instead of format"
5. flash ROM
6. wipe Dalvik
CDFS

"rm -rf" clears all the files and directories without formatting the partition. If your partition is damaged you need a real format to obtain a reliable partition (if the "disk" isn't faulty). Perhaps in your case a real format was required to solve the problem! I always used the real format and assumed other users even so. I see you finally solved the problem!

Any newer or best TWRP for X727?

It's been a year already since I checked this sub and I am still using the TWRP that flickers and is chinese. Is there like an upgraded version for our device? Specifically for the non elite variant US version?
I think I might have screwed my phone because after I flashed a new rom(RR) my internal storage won't mount on recovery and when I connect it to pc. But I can see it in my phone when I'm on system(thank god) This is weird because I have not put any security lock on my phone before backing it up. So I am assuming that I need to update my TWRP to something latest to solve this issue, but I haven't been keeping up to this sub, i don't know if there's a newer compatible of TWRP.
And I also forgot why I did not went with the official one from TWRP. Maybe because it messes up the bootloader? or something like that, forgot since it's been a year already and I remember reading into a guide to use the chinese twrp.
[Solved]
If this happens to your device and you happen to use the chinese screen flicker fest TWRP, just go on and flash the latest official TWRP for our device. And you're going to be able to see your internal storage again.
you can either flash it ADB or from your recovery, but I flashed mine through TWRP

drckml said:
It's been a year already since I checked this sub and I am still using the TWRP that flickers and is chinese. Is there like an upgraded version for our device? Specifically for the non elite variant US version?
I think I might have screwed my phone because after I flashed a new rom(RR) my internal storage won't mount on recovery and when I connect it to pc. But I can see it in my phone when I'm on system(thank god) This is weird because I have not put any security lock on my phone before backing it up. So I am assuming that I need to update my TWRP to something latest to solve this issue, but I haven't been keeping up to this sub, i don't know if there's a newer compatible of TWRP.
And I also forgot why I did not went with the official one from TWRP. Maybe because it messes up the bootloader? or something like that, forgot since it's been a year already and I remember reading into a guide to use the chinese twrp.
Click to expand...
Click to collapse
Stop reading out of date articles, and use the latest Twrp here: https://twrp.me/leeco/leecolepro3.html
The Chinese bootloader issue is no longer an issue
* So to be clear about you issue you cannot boot to recovery.
* You do see you phone when you connect it to the computer...Right?
* BTW, I also have an X727
Your issue is most likely due to corruption and encryption
Backup whatever data you can and then use the All in One ( "AIT " ) tool to remove encryption ( NOTE: this is going to erase your data.
Next Using AIT install Twrp and magisk 17.1 or the easier way to resolve this may be to temporarily go back to stock.
Option 1
Try flashing the latest Twrp and magisk 17.1, using either ADB or AIT
After flashing boot into TWRP recovery
1. Go to "Wipe" and then to "Advanced Wipe".
2. Mark "Dalvik / ART Cache", "System", "Data" and "Cache".
3. "Swipe to Wipe" and proceed back the main menu.
4. Go to "Install".
5. Select the ROM zip file and then press "Add more Zips" and select the Gapps zip file, and then the Magisk file.
6. "Swipe to confirm Flash" and wait for some time.
7. After the flashing is finished, just reboot to recovery, check boxes to keep Twrp installed
8. Boot to system go through setup.
Option 2
You could flash my Recovery which includes Twrp and Root. ( Instructions at Link Below)
Afterwards you will be able to update the Twrp, and Root, then Flash whatever you want.
Le Eco Pro 3 X727 Twrp Backup : Clean Full Stock X727 recovery EUI 5.8.21s
https://forum.xda-developers.com/showpost.php?p=75021582
Option 3
Use All in One tool to restore my recovery, Flash a Stock Rom , or simply Flash TWRP/ROOT and then your Rom> Gapps> Magisk once again > Reboot to Recovery ( Check Boxes, for Twrp manager installation) Reboot to recovery > do not choose to make you drive read only! Clear Cache ( Not Dalvik) Reboot to system > Finished.
However, there is a faster way: @mauronofrio created a tool called: "TOOL ALL IN ONE"" and its great!
https://forum.xda-developers.com/and...ctory-t3358711
Its an excellent tool for keeping your drivers and adb up to date. Plus it will give ADB system wide privileges.
Mauronofrio's tool can also unencrypt your storage
After install the All in One Tool
Make sure to check for the AIT program for updates, to the tool itself and to ADB.
Next, click button to allow ADB privileges system wide.
Get more information here:*https://toolaio.tk**
XDA page for Le pro 3 : https://forum.xda-developers.com/le-...1#post71627491
* The all is one tool is excellent and you can use it to install everything you want.
* You can use it to unlock the bootloader.
* Remove Encryption
* Install TWRP,
* Install your Rom, Gapps and Magisk etc.
* The tool will also update your existing installation of ADB, Android Drivers, and provide system wide ADB privileges.
Of course use ADB or AIT once the phone is restored but you would be better off buying an OTG adapter and a USB 3.0 USB Flash drive. This way you can quickly make changes on the fly. I recommend buying at least 32GB usb 3.0 drive. Absolutely, the OTG adapter is the best method, because you will have all of your files available for quick installation and you can make numerous nandroid backups of your favorite rom installations. So If you get bored with one Rom, you can quickly restore another Rom in 5 to 10 minutes.
Again , if you do not use an OTG drive. Just use ADB or AIT for flashing your files, the steps are same as with any other phone.
Finally, look past any typos, I don't have time to proofread after spending so much time on a single post.

Thanks for the detailed response!
my issue was, I can go to recovery but it is not mounting my internal storage. It was showing as 0mb. I am aware that this is usually happens when you encrypt your device and back it up in the recovery and try to restore. But I never put any encryption on my device let alone it doesn't even ask me for a password when I am on the recovery. Anyway, I solved it by just flashing the latest official TWRP on our device. And I'm glad that I am finally away from the buggy chinese twrp.
I was just worried if there was any dangers on flashing the official latest twrp because I am seeing a lot of people getting bricked. So much for the halfassed allowing us to unlock our bootloader in this device by leeco.
Anyway, I really appreciate all that detailed guide. I will keep them in reference in the future.

drckml said:
Thanks for the detailed response!
my issue was, I can go to recovery but it is not mounting my internal storage. It was showing as 0mb. I am aware that this is usually happens when you encrypt your device and back it up in the recovery and try to restore. But I never put any encryption on my device let alone it doesn't even ask me for a password when I am on the recovery. Anyway, I solved it by just flashing the latest official TWRP on our device. And I'm glad that I am finally away from the buggy chinese twrp.
I was just worried if there was any dangers on flashing the official latest twrp because I am seeing a lot of people getting bricked. So much for the halfassed allowing us to unlock our bootloader in this device by leeco.
Anyway, I really appreciate all that detailed guide. I will keep them in reference in the future.
Click to expand...
Click to collapse
That's great!
In the future
If you have an encryption issue again, and you have latest tarp and magisk.
Just format storage and reboot to recovery, then wipe and issue will be resolved.

flashing custom rom on A/B device

Why,in custom ROMs section on 6t forum,every one of custom rom developer in his OP states DIFFERENT "Flashing instructions"?
Not a single rom dev,in his OP have same flashing instructions as some other dev! As I read more,it looks like half of them are wrong instructions,or that they don't have this device,or they don't know.
- flashing on both slots a&b?
flash OOS rom,them twrp.zip,reboot to TWRP (to any of slots),and internal will be encrypted and unreadable.Theres no way to flash on both slots in one take in TWRP or in two takes in row(with in TWRP,reboot to TWRP different slot).There's need for at least one full boot to Operating System,then back to TWRP,and internal will be visible and decrypt ed.
Many custom ROMs need OOS on both slots to be able to make them run,but this looks like nonsense to me.
- changing slots in TWRP?
let's say you flash magisk while in slot A,go to "reboot" and change slot to B, but dont reboot to TWRP.Now flash magisk.it will flash on same slot as first time,there was no slot changing.
- delete wipe "system" in TWRP,or worse "factory reset"?
it's mistake that costs me a lot of time,Ill never do it again.As all custom ROMs now have script that wipes all unnecessary files,there's no need to wipe system and screw your phone for few hours until you fix it.For me,a big No No.
best way of flashing custom os over OOS?
for me,I go into TWRP,flash custom rom,flash TWRP zip,then I reboot into TWRP and flash gapps and magisk.if internal is crypted and I can't flash gapps and magisk,I do a boot into rom,and back to TWRP to finish my flashing.wiola,it boots and works,clean rom and all is fine.
Flash back to OOS?I just go into TWRP,flash OOS ,flash twrp.zip,reboot to twrp and flash magisk.if internal is crypted,I boot into OOS,them back to TWRP,and flash everything else what I need(like magisk and kernel)
a/b devices are nothing new,but it looks to me Like on 6t is all overcomplicated.
So,tell me how you guys do it and what are yours ways of doing it right?

shawek said:
Why,in custom ROMs section on 6t forum,every one of custom rom developer in his OP states DIFFERENT "Flashing instructions"?
Not a single rom dev,in his OP have same flashing instructions as some other dev! As I read more,it looks like half of them are wrong instructions,or that they don't have this device,or they don't know.
- flashing on both slots a&b?
flash OOS rom,them twrp.zip,reboot to TWRP (to any of slots),and internal will be encrypted and unreadable.Theres no way to flash on both slots in one take in TWRP or in two takes in row(with in TWRP,reboot to TWRP different slot).There's need for at least one full boot to Operating System,then back to TWRP,and internal will be visible and decrypt ed.
Many custom ROMs need OOS on both slots to be able to make them run,but this looks like nonsense to me.
- changing slots in TWRP?
let's say you flash magisk while in slot A,go to "reboot" and change slot to B, but dont reboot to TWRP.Now flash magisk.it will flash on same slot as first time,there was no slot changing.
- delete wipe "system" in TWRP,or worse "factory reset"?
it's mistake that costs me a lot of time,Ill never do it again.As all custom ROMs now have script that wipes all unnecessary files,there's no need to wipe system and screw your phone for few hours until you fix it.For me,a big No No.
best way of flashing custom os over OOS?
for me,I go into TWRP,flash custom rom,flash TWRP zip,then I reboot into TWRP and flash gapps and magisk.if internal is crypted and I can't flash gapps and magisk,I do a boot into rom,and back to TWRP to finish my flashing.wiola,it boots and works,clean rom and all is fine.
Flash back to OOS?I just go into TWRP,flash OOS ,flash twrp.zip,reboot to twrp and flash magisk.if internal is crypted,I boot into OOS,them back to TWRP,and flash everything else what I need(like magisk and kernel)
a/b devices are nothing new,but it looks to me Like on 6t is all overcomplicated.
So,tell me how you guys do it and what are yours ways of doing it right?
Click to expand...
Click to collapse
I agree with you!!! This is a mess

even though I have flashed thousands of roms over the years, since I got rid of my Nexus 6, I havent had a phone that I could flash roms on, so, after dumping my Note 8 for this great phone, I was very hesitant to flash a custom rom, for all the reasons you have mentioned..
So, my question is, can you flash ANY of these custom roms by using the clear method that you mentioned in the OP?
If on one of the beta releases, is the procedure the same as I am showing below, or, do you always have to first return to stock OOS?
In my years of flashing dozens of phones, you never had to go back to "stock" if you wiped everything before flashing, but, it seems like on several of these roms, you are instructed to first return to "stock", THEN flash the new custom rom...
Plus, some roms say to wipe everything before you flash, and others say not to wipe system, or not to wipe data...
Unless I am nuts, I always thought that you wipe everything before converting to a totally new rom, but, maybe I am wrong here too..
"for me,I go into TWRP,flash custom rom,flash TWRP zip,then I reboot into TWRP and flash gapps and magisk.if internal is crypted and I can't flash gapps and magisk,I do a boot into rom,and back to TWRP to finish my flashing.wiola,it boots and works,clean rom and all is fine."
These instructions seem pretty clear and concise, hopefully, they are correct, and we can just use this exact method and be done with it!
No mention of wiping in your directions...what do YOU wipe before flashing a new custom rom?
Hopefully, this gets cleared up once and for all, and we can ask the MODS to make a sticky of the ACTUAL CORRECT INSTRUCTIONS>>
thanks

wase4711 said:
"for me,I go into TWRP,flash custom rom,flash TWRP zip,then I reboot into TWRP and flash gapps and magisk.if internal is crypted and I can't flash gapps and magisk,I do a boot into rom,and back to TWRP to finish my flashing.wiola,it boots and works,clean rom and all is fine."
These instructions seem pretty clear and concise, hopefully, they are correct, and we can just use this exact method and be done with it!
No mention of wiping in your directions...what do YOU wipe before flashing a new custom rom?
Hopefully, this gets cleared up once and for all, and we can ask the MODS to make a sticky of the ACTUAL CORRECT INSTRUCTIONS>>
thanks
Click to expand...
Click to collapse
-if on custom rom,probably it's good to first go to stock OOS and then to another custom rom.but this is also strange to me,as I don't understand what are benefits of this.i also read this,Google heh.i tried going from AOSCP to PixelEcpirince without flashing OOS in-between process,all was fine.
-I haven't been on Beta OOS yet,only stable.But that thing bout "before flashing custom rom,flash stable OOS even if your on Beta OOS" is also a big question to me.they are practically the same,both are latest OOS,one maybe more stable them other,but this also can be discussed hehe
-i don't wipe anything!! when my custom rom boots,I go into it's settings, without setting my Google account and other stuff, and I do "factory reset"( not in TWRP,in custom rom's settings!).Phone reboots,and all is fine,clean beginning,TWRP works,root works.About unwantedFolders in internal storage,I delete them manualy.

Only thing in my experience to wipe in TWRP is DATA,but this is also questionable,as I run into problems also doing data wipe I TWRP.
Now ROMs(maybe only for a/b devices) have scripts that wipe previous System during flashing new rom,so we don't have to do a Clean Flash anymore.
I'm also confused,more I read,less I understand ?

I like the idea of wiping via factory reset, once the rom boots, but, if it does NOT boot, then you wouldnt be able to do it that way..
I guess flashing an OOS based rom over an OOS based rom would always allow you to boot, if done right..
But, roms like RR, Carbon, AICP, and a couple others that have shown up here recently were never really OOS based roms, but AOSP based, at least I thought so..
the more I think about this, the more confusing it seems to get..

wase4711 said:
I like the idea of wiping via factory reset, once the rom boots, but, if it does NOT boot, then you wouldnt be able to do it that way..
I guess flashing an OOS based rom over an OOS based rom would always allow you to boot, if done right..
But, roms like RR, Carbon, AICP, and a couple others that have shown up here recently were never really OOS based roms, but AOSP based, at least I thought so..
the more I think about this, the more confusing it seems to get..
Click to expand...
Click to collapse
This is from the pixel 2 xl forum another a/b device
First time installing Pixel Dust ROM, or coming from another ROM:
As mentioned above, you are required to flash stock ROM before installing this custom ROM.
1. Flashing Stock ROM:
Follow these instructions: https://developers.google.com/android/images#taimen
2. Flashing PixelDust ROM:
Reboot to twrp
Wipe Dalvik cache and Data partitions
Flash ROM
Flash twrp zip
Reboot to System and enjoy the Pixel Dust Goodness!
Flashing Magisk:
You cannot flash Magisk during the initial install. You must boot into PixelDust ROM at least once!
Reboot to Recovery
Flash Magisk-v17.x.zip
Reboot to System

shawek said:
Why,in custom ROMs section on 6t forum,every one of custom rom developer in his OP states DIFFERENT "Flashing instructions"?
Not a single rom dev,in his OP have same flashing instructions as some other dev! As I read more,it looks like half of them are wrong instructions,or that they don't have this device,or they don't know.
- flashing on both slots a&b?
flash OOS rom,them twrp.zip,reboot to TWRP (to any of slots),and internal will be encrypted and unreadable.Theres no way to flash on both slots in one take in TWRP or in two takes in row(with in TWRP,reboot to TWRP different slot).There's need for at least one full boot to Operating System,then back to TWRP,and internal will be visible and decrypt ed.
Many custom ROMs need OOS on both slots to be able to make them run,but this looks like nonsense to me.
- changing slots in TWRP?
let's say you flash magisk while in slot A,go to "reboot" and change slot to B, but dont reboot to TWRP.Now flash magisk.it will flash on same slot as first time,there was no slot changing.
- delete wipe "system" in TWRP,or worse "factory reset"?
it's mistake that costs me a lot of time,Ill never do it again.As all custom ROMs now have script that wipes all unnecessary files,there's no need to wipe system and screw your phone for few hours until you fix it.For me,a big No No.
best way of flashing custom os over OOS?
for me,I go into TWRP,flash custom rom,flash TWRP zip,then I reboot into TWRP and flash gapps and magisk.if internal is crypted and I can't flash gapps and magisk,I do a boot into rom,and back to TWRP to finish my flashing.wiola,it boots and works,clean rom and all is fine.
Flash back to OOS?I just go into TWRP,flash OOS ,flash twrp.zip,reboot to twrp and flash magisk.if internal is crypted,I boot into OOS,them back to TWRP,and flash everything else what I need(like magisk and kernel)
a/b devices are nothing new,but it looks to me Like on 6t is all overcomplicated.
So,tell me how you guys do it and what are yours ways of doing it right?
Click to expand...
Click to collapse
You make it overcomplicated.
To flash both slots you only need to do a complete reboot to make sure the OS is not hosed.
You do that so if it is you can use the other slot. This is not necessary.
You flash in TWRP, change the slot and reboot into TWRP and flash the other slot.
It could be easier if TWRP allowed flashing on the inactive slot.
But, even if you are rooted and want to upgrade it is suggested to upgrade both slots.
I think it's just a minor pain. There are bigger problems.

tech_head said:
You make it overcomplicated.
To flash both slots you only need to do a complete reboot to make sure the OS is not hosed.
You do that so if it is you can use the other slot. This is not necessary.
You flash in TWRP, change the slot and reboot into TWRP and flash the other slot.
It could be easier if TWRP allowed flashing on the inactive slot.
But, even if you are rooted and want to upgrade it is suggested to upgrade both slots.
I think it's just a minor pain. There are bigger problems.
Click to expand...
Click to collapse
it's not a minor pain if most of time that I go to flash custom rom,I lost all my 60-80gigs of internal data, cuz of failed decryption,or failed rom flash,or failed TWRP flash.There were times when I did Factory reset in TWRP,flashed OOS,flashed TWRP.zip,did reboot to recovery,and I lost recovery.I was left with bootloader (fastboot) and had to fastbooting OOS few times(which led to full wipe of internal storage).OOS wasn't even flashed,or TWRP wanst even flashed.And I just followed instructions.
this are the things that I'm talking about.Even if I follow instructions, instructions are not detailed.
now I probably know how to do it right,,but still...I learned it hard way,and still learning
thanks for your opinion and answer:good:

shawek said:
it's not a minor pain if most of time that I go to flash custom rom,I lost all my 60-80gigs of internal data, cuz of failed decryption,or failed rom flash,or failed TWRP flash.There were times when I did Factory reset in TWRP,flashed OOS,flashed TWRP.zip,did reboot to recovery,and I lost recovery.I was left with bootloader (fastboot) and had to fastbooting OOS few times(which led to full wipe of internal storage).OOS wasn't even flashed,or TWRP wanst even flashed.And I just followed instructions.
this are the things that I'm talking about.Even if I follow instructions, instructions are not detailed.
now I probably know how to do it right,,but still...I learned it hard way,and still learning
thanks for your opinion and answer:good:
Click to expand...
Click to collapse
I understand now.
The instructions are not clear for most of this stuff and you can screw up.
If something fails to flash, there are very few reasons to ever completely wipe. Even a factory reset does not require a complete wipe of data.
I would suggest at all times keeping a boot image of the current OS you are using.
I would also suggest keeping a TWRP.img on your computer. You can always boot from a TWRP image even if it's not the one you want to install.
That will at least get decryption and the ability to flash.
I don't flash custom ROMs, because the stock one with root does what I need. Also the fingerprint sensor is not guaranteed under custom ROMs and I need that to work.

no verify opt on most after data wipe or that brands version of it, then reboot to twrp verify is still not there because twrp will say no os installed the avb changed things every phone is different depending on their security Samsung for one

Try this guide. Read the first paragraph if you have problems with decryption.

Boot twrp
Wipe dalvik and data
Flash rom+twrp
Reboot SYSTEM!
Boot back to recovery
Factory reset
Flash gapps+magisk
Reboot and done
No data loss or PC needed...

So here's some food for thought. I read somewhere that when you install a ROM zip via TWRP it actually Installs to the Inactive Slot. And when you reboot to TWRP after reflashing the Installer it Switches Slots and then you can Flash GAPPS etc. But what if someone were to flash the ROM twice ; once to each slot? Would be noice if We can use this to Multi-Boot Two ROMs at once....

Mannan Qamar said:
So here's some food for thought. I read somewhere that when you install a ROM zip via TWRP it actually Installs to the Inactive Slot. And when you reboot to TWRP after reflashing the Installer it Switches Slots and then you can Flash GAPPS etc. But what if someone were to flash the ROM twice ; once to each slot? Would be noice if We can use this to Multi-Boot Two ROMs at once....
Click to expand...
Click to collapse
I think that question was asked in one of the threads in here "can use this to Multi-Boot Two ROMs at once" and I don't think it's possible. I'm sorry I don't remember the thread it was in. You might try Google.

It's wise to do the oos in both slots which you can switch slots without rebooting fyi because when you flash a custom ROM no matter if you switch back to a it'll flash magisk and probably gapps in the inactive slot. If you try to return the custom ROM to slot a after it flashes it will say insufficient room for gapps and such. So to me it seems this makes it a clean slate so it can flash to inactive slot. Hope that clears up why they encourage the double oos flash

Everyone, I think you have almost helped me figure out how I screwed up my 6T. I made a post needing help but this thread I believe is the answer. I wanted to install lineage16 but opted for Resurrection Remix since that dev claimed the fingerprint reader worked. To make a long story short, I flashed the latest .15 OxyOS update first, switched partitions via TWRP and flashed it again, them flashed TWRP and rebooted to recovery. Flashed Remix then TWRP again and rebooted to Remix. Now I have no room for anything in storage although it's only 25% full and my file explorer cannot access any storage not can I update apps through play store or anything. I have the latest OxyOS on my OTG flash drive as well as TWRP and magisk, but every time I find a thread on hope to do an installation, it varies and I keep coming back to this storage issue. Can someone PLEASE link me out tell me where to find the correct process to now start from the beginning and get my phone back working on the OxyOS .15 stock rom? Thank you very much and I'm glad I found this thread because it finally makes sense as to how misinformation is causing many people to have issues.

SuperUnkn0wn0ne said:
Everyone, I think you have almost helped me figure out how I screwed up my 6T. I made a post needing help but this thread I believe is the answer. I wanted to install lineage16 but opted for Resurrection Remix since that dev claimed the fingerprint reader worked. To make a long story short, I flashed the latest .15 OxyOS update first, switched partitions via TWRP and flashed it again, them flashed TWRP and rebooted to recovery. Flashed Remix then TWRP again and rebooted to Remix. Now I have no room for anything in storage although it's only 25% full and my file explorer cannot access any storage not can I update apps through play store or anything. I have the latest OxyOS on my OTG flash drive as well as TWRP and magisk, but every time I find a thread on hope to do an installation, it varies and I keep coming back to this storage issue. Can someone PLEASE link me out tell me where to find the correct process to now start from the beginning and get my phone back working on the OxyOS .15 stock rom? Thank you very much and I'm glad I found this thread because it finally makes sense as to how misinformation is causing many people to have issues.
Click to expand...
Click to collapse
You may have solved this by now, but I found that using the MSM Download Tool has enabled me to return to stock OxygenOS even after getting stuck in a boot loop. I've not been able to successfully flash RR or LineageOS however, still getting stuck in said boot loop...

.

.

HMSS013 said:
Had my new OP5 rooted and almost everything was right in the world, but i flew too close to the sun by uninstalling a few apps I thought were expendable and eventually Google Play Services started crashing. When all troubleshooting failed I ended up flashing a fresh copy of OxygenOS (5.1.7) to my device, but every attempt to re-root the device has failed.
The first obstacle I ran into was that there was no access to Internal Storage in TWRP, I was able to fix that by Wipe > Format Data and then using Advanced Wipe to clean Dalvik/Cache/System/Data for good measure.
My next issue was that TWRP returned Error 7 when attempting to flash the stock OOS rom... after some digging I was able to clean the 'asserts' line from the updater-script file and now the rom will flash.
The headache has been getting the device re-rooted, and I feel like I've tried everything. I have to flash the SuperSU or Magisk zip (both fail to root the device) before reboot because the dm-verity encrypts on first boot and after that I can't access any storage to flash from internal memory. The three different dm-verity patches I've found don't prevent it. I also tried 'fastboot oem disable_dm_verity' to try and stop it but after talking with the device fastboot returns 'unknown command'.
My final effort to get around it was to flash a kernel that didn't force dm-verity (blu_spark kernel) but that returns Error 1: 'Unsupported Android Version' when I attempt to flash it.
I've tried dozens of variations on this, including a Lineage OS rom instead and also trying to sideload certain zips, but still no dice. Any and all help would be appreciated.
Click to expand...
Click to collapse
Which rom do you want to install?

HMSS013 said:
The first obstacle I ran into was that there was no access to Internal Storage in TWRP, I was able to fix that by Wipe > Format Data and then using Advanced Wipe to clean Dalvik/Cache/System/Data for good measure.
Click to expand...
Click to collapse
Hi, this one is because of your TWRP. Please flash Codework's TWRP and try that with it. It should solve your issue for sure. (same thing happened to me while I tried installing custom roms and every time I needed to wipe everything to see my internal storage again)
This guide can help you out with Error 7 on TWRP https://forum.xda-developers.com/showthread.php?t=2522762
I do believe your this issue you're having caused by TWRP. Also after rooting the phone, install magisk app. (you don't need to install supersu, it comes with magisk). After rebooting into system reboot your phone again once more it should show up on magisk app that you've successfully rooted your phone. Remember after flashing magisk you need to reboot twice in order for phone to realize it. Please try the steps I told you and let me know.
Also you don't need to flash dm-verity patch at all.
Try clean flash instructions with Codework's TWRP and root it with latest Magisk.

.

.

HMSS013 said:
I actually really like the Oreo version of OxygenOS, so when I had to resort to re-flashing to fix this mess I dug up one of the stock (5.1.7) roms, it served me well (assuming I can get it rooted, lol).
I'd be willing to move to Lineage if I absolutely have to, but if not, I'd really like to keep Oreo if at all possible.
Click to expand...
Click to collapse
For 5.1.7 try this twrp https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk along with magisk 17.1.
Clean flash is recommended. If it didn't help, please list your steps again(detailed).
Don't use supersu and skip the other suggestions for now please.

.