Related
I've been reading about bricked devices and want to downgrade from N to MM. I seen a thread in the 5X forum about it but want to be be sure before I attempt it with my 6P. Anyone have trouble downgrading? Can I just flash the factory image like usual? Thanks in advance.
Sent from my Nexus 6P using Tapatalk
Advice for now - Don't even bother unless your ready for a soft bricked device until the issue is resolved and considering we dont even have a factory image it could be weeks away.
its your descision but there are two threads now attempting to fix this and people have had mixed results, the only seemingly helpful thing is to back up 100% of your devices partitions / efs and absolutely everything from your MM build and store it safe on your PC for when your device eventually soft bricks.
just don't bother ! if your on MM stay for another month or so or lump it with stock rooted N, don't attempt to go back !
hutzdani said:
Advice for now - Don't even bother unless your ready for a soft bricked device until the issue is resolved and considering we dont even have a factory image it could be weeks away.
its your descision but there are two threads now attempting to fix this and people have had mixed results, the only seemingly helpful thing is to back up 100% of your devices partitions / efs and absolutely everything from your MM build and store it safe on your PC for when your device eventually soft bricks.
just don't bother ! if your on MM stay for another month or so or lump it with stock rooted N, don't attempt to go back !
Click to expand...
Click to collapse
Yeah, so many stories of expensive paperweights when trying the downgrade. I suspect they're having some major issues with the 6p factory image, since the 5x has been posted for nearly two weeks. I've got mine working pretty well, with really good battery and ARISE sound actually working system-wide. I suspect we may see the factory image when this month's security update is rolled out - at least I hope so, given we're already into September.
That's what I figured. Looks like I'm staying on N. Thanks!
Sent from my Nexus 6P using Tapatalk
@dutchy716, you should be fine. Only people I saw who bricked either flashed the OTA package over a custom ROM (never, ever do this even on "stock debloated" ROMs) or restored a MM nandroid backup while being on N. I have gone back to MM plenty of times (at this point, close to 10). The steps to downgrade and not brick have always been the same and from what I've seen it's only been user error that put people in that position. Make sure you're using the latest TWRP which at this point and time is 3.0.2-1. This guide assumes you know ADB/fastboot and have drivers correctly installed. Follow sticky guide 'how to' links in general if this isn't the case. Using a PC, download and extract the 6.0.1 factory image.
Step 0.5: If you don't already have it, fastboot flash TWRP 3.0.2-1
Step 1: Reboot to TWRP
Step 2: Wipe > Factory Reset / Wipe > Advanced > System, Data, Cache & Dalvik
Step 3: Reboot to bootloader, swipe to ignore TWRP warning of no OS installed if you wiped system partition from advanced section.
Step 4: Fastboot time;
fastboot devices
fastboot flash bootloader bootloader-angler-angler-03.54.img
-use volume & power keys to reboot back to bootloader
fastboot flash radio radio-angler-angler-03.61.img
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Step 5: Reboot to recovery. When you see the android on its back alongside a red triangle & exclamation mark; hold down the power button & while holding power, press and release volume up. This will bring up the stock recovery menu. Use volume keys to select wipe cache partition and power to confirm. Then select reboot system now.
Let the phone boot and you're now on complete stock 6.0.1. Follow the steps exactly and I guarantee you won't have issues. Don't take shortcuts to save time (oh I can skip so and so step, do this order instead, etc.). At this point you can reboot once again to bootloader and;
fastboot devices
fastboot flash recovery twrp-3.0.2-1-angler.img
Boot to TWRP & flash your favorite MM ROM.
Notes: This method does NOT wipe user data. Any pictures you've taken, files you've downloaded, etc. will all still be there. You do not need 'cache' or 'userdata' when flashing the factory images. Skip both of those. A factory reset from stock recovery will wipe all userdata from internal storage as will fastboot flashing userdata.img. That is why we do it from TWRP before starting and skip flashing it in fastboot. Cache will build itself as it boots. So long as you wipe it from TWRP/STOCK recovery you will be fine.
That'll do it.
Edit: Just look for yourself. This post is surrounded by "bricked after restoring nandroid posts" Do not restore a 6.0 nandroid over a 7.0 ROM. It appears there's an issue with backup & restore from TWRP at this time so just don't do it. Downgrade the way I posted to avoid data loss and bricks. All of my sensors, sim, data, etc. all work perfect.
Great thanks! I'll give it a go
Sent from my Nexus 6P using Tapatalk
RoyJ said:
@dutchy716, you should be fine. Only people I saw who bricked either flashed the OTA package over a custom ROM (never, ever do this even on "stock debloated" ROMs) or restored a MM nandroid backup while being on N. I have gone back to MM plenty of times (at this point, close to 10). The steps to downgrade and not brick have always been the same and from what I've seen it's only been user error that put people in that position. Make sure you're using the latest TWRP which at this point and time is 3.0.2-1. This guide assumes you know ADB/fastboot and have drivers correctly installed. Follow sticky guide 'how to' links in general if this isn't the case. Using a PC, download and extract the 6.0.1 factory image.
Step 0.5: If you don't already have it, fastboot flash TWRP 3.0.2-1
Step 1: Reboot to TWRP
Step 2: Wipe > Factory Reset / Wipe > Advanced > System, Data, Cache & Dalvik
Step 3: Reboot to bootloader, swipe to ignore TWRP warning of no OS installed if you wiped system partition from advanced section.
Step 4: Fastboot time;
fastboot devices
fastboot flash bootloader bootloader-angler-angler-03.54.img
-use volume & power keys to reboot back to bootloader
fastboot flash radio radio-angler-angler-03.61.img
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Step 5: Reboot to recovery. When you see the android on its back alongside a red triangle & exclamation mark; hold down the power button & while holding power, press and release volume up. This will bring up the stock recovery menu. Use volume keys to select wipe cache partition and power to confirm. Then select reboot system now.
Let the phone boot and you're now on complete stock 6.0.1. Follow the steps exactly and I guarantee you won't have issues. Don't take shortcuts to save time (oh I can skip so and so step, do this order instead, etc.). At this point you can reboot once again to bootloader and;
fastboot devices
fastboot flash recovery twrp-3.0.2-1-angler.img
Boot to TWRP & flash your favorite MM ROM.
Notes: This method does NOT wipe user data. Any pictures you've taken, files you've downloaded, etc. will all still be there. You do not need 'cache' or 'userdata' when flashing the factory images. Skip both of those. A factory reset from stock recovery will wipe all userdata from internal storage as will fastboot flashing userdata.img. That is why we do it from TWRP before starting and skip flashing it in fastboot. Cache will build itself as it boots. So long as you wipe it from TWRP/STOCK recovery you will be fine.
That'll do it.
Edit: Just look for yourself. This post is surrounded by "bricked after restoring nandroid posts" Do not restore a 6.0 nandroid over a 7.0 ROM. It appears there's an issue with backup & restore from TWRP at this time so just don't do it. Downgrade the way I posted to avoid data loss and bricks. All of my sensors, sim, data, etc. all work perfect.
Click to expand...
Click to collapse
Works fine, thanks!
RoyJ said:
@dutchy716, you should be fine. Only people I saw who bricked either flashed the OTA package over a custom ROM (never, ever do this even on "stock debloated" ROMs) or restored a MM nandroid backup while being on N. I have gone back to MM plenty of times (at this point, close to 10). The steps to downgrade and not brick have always been the same and from what I've seen it's only been user error that put people in that position. Make sure you're using the latest TWRP which at this point and time is 3.0.2-1. This guide assumes you know ADB/fastboot and have drivers correctly installed. Follow sticky guide 'how to' links in general if this isn't the case. Using a PC, download and extract the 6.0.1 factory image.
Step 0.5: If you don't already have it, fastboot flash TWRP 3.0.2-1
Step 1: Reboot to TWRP
Step 2: Wipe > Factory Reset / Wipe > Advanced > System, Data, Cache & Dalvik
Step 3: Reboot to bootloader, swipe to ignore TWRP warning of no OS installed if you wiped system partition from advanced section.
Step 4: Fastboot time;
fastboot devices
fastboot flash bootloader bootloader-angler-angler-03.54.img
-use volume & power keys to reboot back to bootloader
fastboot flash radio radio-angler-angler-03.61.img
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Step 5: Reboot to recovery. When you see the android on its back alongside a red triangle & exclamation mark; hold down the power button & while holding power, press and release volume up. This will bring up the stock recovery menu. Use volume keys to select wipe cache partition and power to confirm. Then select reboot system now.
Let the phone boot and you're now on complete stock 6.0.1. Follow the steps exactly and I guarantee you won't have issues. Don't take shortcuts to save time (oh I can skip so and so step, do this order instead, etc.). At this point you can reboot once again to bootloader and;
fastboot devices
fastboot flash recovery twrp-3.0.2-1-angler.img
Boot to TWRP & flash your favorite MM ROM.
Notes: This method does NOT wipe user data. Any pictures you've taken, files you've downloaded, etc. will all still be there. You do not need 'cache' or 'userdata' when flashing the factory images. Skip both of those. A factory reset from stock recovery will wipe all userdata from internal storage as will fastboot flashing userdata.img. That is why we do it from TWRP before starting and skip flashing it in fastboot. Cache will build itself as it boots. So long as you wipe it from TWRP/STOCK recovery you will be fine.
That'll do it.
Edit: Just look for yourself. This post is surrounded by "bricked after restoring nandroid posts" Do not restore a 6.0 nandroid over a 7.0 ROM. It appears there's an issue with backup & restore from TWRP at this time so just don't do it. Downgrade the way I posted to avoid data loss and bricks. All of my sensors, sim, data, etc. all work perfect.
Click to expand...
Click to collapse
Okay, it's been a while for me and I don't want to mess my phone up.
I have a Nexus 6P and the bootloader is still locked, phone is not rooted, and running official 7.0 from the beta signup a couple weeks ago.
I'd like to go back to MM because my battery life has been atrocious. Now my questions:
1. Do I have to unlock the bootloader first before I attempt the steps above?
2. Where is the best place to extract the last MM factory image to use during fastboot?
srt4mn said:
Okay, it's been a while for me and I don't want to mess my phone up.
I have a Nexus 6P and the bootloader is still locked, phone is not rooted, and running official 7.0 from the beta signup a couple weeks ago.
I'd like to go back to MM because my battery life has been atrocious. Now my questions:
1. Do I have to unlock the bootloader first before I attempt the steps above?
2. Where is the best place to extract the last MM factory image to use during fastboot?
Click to expand...
Click to collapse
Yes in order to use fastboot, you need to unlock the bootloader. This will wipe all userdata off of the phone so backup to your PC first. I just unzip everything in platform-tools.
RoyJ said:
Yes in order to use fastboot, you need to unlock the bootloader. This will wipe all userdata off of the phone so backup to your PC first. I just unzip everything in platform-tools.
Click to expand...
Click to collapse
Thanks! I'll give it a shot here after I figure out this bootloader usb data cable issue.
EDIT:
Got back to 6.0.1 after following your instructions, thanks again!!
Worked like a charm. Thanks @RoyJ!
No problem, glad it worked for everyone.
I have been running Weta 7.1 for a week and went back to Pure Nexus using TWRP 3.0.2-3. I went into recovery, wiped everything except internal storage, flashed the vendor image, then flashed the rom and gapps,then flashed the vendor image again. The phone booted up just fine. I never back up or restore the EFS partition.
bmwkeith said:
I have been running Weta 7.1 for a week and went back to Pure Nexus using TWRP 3.0.2-3. I went into recovery, wiped everything except internal storage, flashed the vendor image, then flashed the rom and gapps,then flashed the vendor image again. The phone booted up just fine. I never back up or restore the EFS partition.
Click to expand...
Click to collapse
So your in PN MM with new nougat modem and bootloader ?
dutchy716 said:
I've been reading about bricked devices and want to downgrade from N to MM. I seen a thread in the 5X forum about it but want to be be sure before I attempt it with my 6P. Anyone have trouble downgrading? Can I just flash the factory image like usual? Thanks in advance.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Hey so I actually bricked my first Nexus 6p doing this but I have been fine with my replacement. The Key is to update your twrp to 3.0.2-2 (make sure you do this). I then from Android 7 did a full backup in Twrp and then in the bootloader flashed the MTC20F factory image and it rebooted just fine. I guess in Twrp 3.0.2-1 there is an efs partition problem that is causing the bricks; my old bricked nexus 6p was on 3.0.2-1. So just please make sure you flash 3.0.2-2 twrp
ariefabuzaky said:
So your in PN MM with new nougat modem and bootloader ?
Click to expand...
Click to collapse
Yes, and everything is working fine.
ariefabuzaky said:
So your in PN MM with new nougat modem and bootloader ?
Click to expand...
Click to collapse
This is also how I downgraded mine. Also works on 3.0.2-0 if you were wondering.
rndll said:
This is also how I downgraded mine. Also works on 3.0.2-0 if you were wondering.
Click to expand...
Click to collapse
Yes. Already try it and everything is working fine.
What about downgrading a stock android 7.0 without TWRP and unlocked bootloader to MM?
Does anyone have a guidance for this, too?
Edit: Solved.
NedbuR said:
What about downgrading a stock android 7.0 without TWRP and unlocked bootloader to MM?
Does anyone have a guidance for this, too?
Edit: Solved.
Click to expand...
Click to collapse
Did you sideload 7.0 or upgrade from the beta program?
Sent from my Nexus 6P using Tapatalk
Hello everyone,
I have moto xt1572, it unlockbootloader and rooted. I am using TruPureXMM rom.
Yesterday I flash Dual Stock rom using ADB/Fastboot. After flashed, my phone's internal storage was interrupted. When I boot into TWRP, it show 0 MB, it look like the patition not fomat yet. And I can't flash any rom.zip.
I found there are topic: Restore to stock tool.
So is that work for my XT1572 case
Please help me to fix that.
Thank you so much
Were you using the sd card as internally adopted? That can cause the issue you got when you change rom's. I don't think there is a solution to this.
I've never had a similar problem with this phone, but on some other devices I've had no amount of wiping in TWRP was as effective as a full wipe in the stock recovery. Wiping with stock recovery would fix the internal file system, encryption issues, etc. You might try fastboot flashing the stock recovery and giving it a try, if TWRP isn't working for you.
I fixed this problem by follow guide from this page Rootjunky.
1st
I use RSD lite but it fails
2nd
I use fastboot/adb follow guide
- download file MotoXPureClarkbatchfiles.zip.
- Download stock firmware of moto XT1572
- Extract MotoXPureClarkbatchfiles.zip and stock firmware in same folder
- Boot my phone in bootloader mode, then connect to PC
- And run file FullRestore.bat
It's worked.
Hi
Trying to flash TWRP but no ADB & Fastboot directory under Windows 10 program files/x86?!? Also should GApps go here? 32bit? What if SD card & internal storage is merged? End result is Lineage OS...
Could anyone link a good guide?
Which adb/fastboot utility did you install? If you install Minimal ADB 1.4.2, on my computer it's present under C:\Program Files (x86)\Minimal ADB and Fastboot. For 1.4.2: https://www.androidfilehost.com/?fid=745425885120698566
If you're trying to flash TWRP (ensure you've got either TWRP 3.0.2 or a more recent version, 3.1.1 for example, and that it's for athene devices), you could follow this guide: https://forum.xda-developers.com/showpost.php?p=67031805&postcount=3 Also, double check you've unlocked your bootloader before attempting any of this: https://forum.xda-developers.com/showpost.php?p=67031801&postcount=2 Bear in mind unlocking your bootloader will wipe your device and void your warranty.
Once you've flashed TWRP, then reboot straight to recovery - this is to ensure TWRP is not overwritten by the stock recovery. Once you've booted to the recovery, then TWRP should stick and you may reboot as normal.
EDIT - instead of flashing TWRP, you may wish to boot to TWRP (and look at step 4 below):
Copy the TWRP image file to your adb folder.
Boot into the bootloader and connect your device to your computer.
Open your adb client and verify your device is communicating by executing 'fastboot devices' without the quotes. You should get a response with your device's serial number.
To boot in TWRP, execute in the adb terminal 'fastboot boot <name of TWRP image>' without the quotes. E.g if your TWRP is twrp-3.1.1-athene_shreps.img, then the command you'd use is 'fastboot boot twrp-3.1.1-athene_shreps.img' (without quotes).
Afterwards, you'll be able to flash LineageOS and GApps. The main instructions for flashing a custom ROM are usually listed in the first post of each custom ROM (here's the link for the official LineageOS: https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101)
If you have your SD card and internal storage merged, then unless you can save the encryption key from your stock, your SD card will be wiped/inaccessible. SD cards mounted as portable storage appear to operate okay under both custom and stock ROMs. Thus, back up your SD card to your computer. You may wish to re-format your SD card as portable storage (and from what I've read on the Lenovo Motorola forums, that might help your SD card last longer, as it's not being subjected to encryption as it would be with adoptable storage).
1)You'll be flashing the LineageOS and GApps (can use either OpenGApps or BeanGApps) zips using TWRP. You need 7.1 arm Gapps (32 bit).
2)Download LineageOS and GApps to your device. Do not unzip them.
3)Reboot to TWRP recovery. Tap the Backup option on the main menu.
4)Back up your device in TWRP (make a note this is your stock backup). If you want this backup to be OTA friendly for stock updates, then do not 'swipe to allow modifications'. Back up the stock ROM, verify you've got the backup then reboot to TWRP, and then 'swipe to allow modifications'.
5)Go back to the main menu, and tap the 'Wipe'.
6)Under 'Advanced Wipe', select Dalvik/ART cache, system, data and cache. Double check these are the only ones you have ticked.
6a)Swipe to wipe.
7)Go back to the TWRP main menu.
8)Tap Install and locate your LineageOS and GApps zips.
9)Flash LineageOS first and then GApps.
10)Reboot to LineageOS.
If your device screen goes to sleep whilst in TWRP, press on the volume keys to wake up your device.
If you wish to revert back to near stock, you can flash your TWRP backup of your stock ROM (though this will revert any messages to the point when your backup was taken, you may wish to use Titanium Backup or MyPhoneExplorer to backup). If you decide to revert completely to stock, then if you were on the June 2017 stock update, please only flash the June 2017 or later stock firmwares: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
@echo92 if he would decide to flash back to a clean StockRom (by fastboot) in order to start with a complete unmodified System (stock boot, stock kernel & stock recovery) wouldn't it be better not to "flash" but just to "boot" once into TWRP and take a backup of the clean StockRom in order to save the stockrecovery too? So he could simply restore his clean stock if he wants to take a future OTA.
If he "flashes" TRWP permanently onto StockR he would backup Stock with modified recovery and might wonder, why he couldn't install an OTA.
Please correct me, if I'm wrong.
bullfinch110 said:
@echo92 if he would decide to flash back to a clean StockRom (by fastboot) in order to start with a complete unmodified System (stock boot, stock kernel & stock recovery) wouldn't it be better not to "flash" but just to "boot" once into TWRP and take a backup of the clean StockRom in order to save the stockrecovery too? So he could simply restore his clean stock if he wants to take a future OTA.
If he "flashes" TRWP permanently onto StockR he would backup Stock with modified recovery and might wonder, why he couldn't install an OTA.
Please correct me, if I'm wrong.
Click to expand...
Click to collapse
Oh definitely, that's an option, booting into TWRP and backing up the stock ROM. As I understand it, you have to back up your device without allowing TWRP to modify your system partition. If the backup is taken after that, I recently read that enabling that will cause an OTA to fail (since the type of OTA monitors if the system was ever mounted as read/write), even if the backup you took had no other changes.
It honestly depends on how much flashing the opening poster is planning on doing, if it's simply just LineageOS and OpenGApps, then might be worth booting into TWRP. However, to keep updated then you'd have to perform the updates when you've got a PC available (to be able to boot into TWRP), in which case the inconvenience of booting into TWRP with a PC might outweigh the downside of a custom recovery. For custom ROMs, we might have a similar issue ironically, where a user downloads an update for custom ROMs and cannot flash the update because they do not have TWRP on their device (albeit this issue is easier to fix). I concur that simply booting into TWRP may be more suitable for new users and those that do not realise the requirements/downsides of having a custom recovery. I'll add in the option of booting to TWRP in the previous post As the saying goes, with great power comes great responsibility.
Also, if the user flashes other files (e.g. a custom logo.bin to hide the bootloader warning), then the OTA would fail anyway, and custom logos aren't backed up by TWRP. For a logo.bin though, that can be easily replaced by a stock logo.bin (from the appropriate stock ROM) flashable in fastboot or in TWRP.
If the xda pros would establish a new status, like "Recognized Explainer", you were the first who 'd deserve it.
Thx!!!
I have successfully installed Lineage Flo (2013) on a Nexus 7! This practice (fell at every hurdle) & your post should bring the matter to a swift finish.
Many thx.
So, I searched the internet for a method to flash a CustomROM on the OnePlus 6T. But somehow none of them worked, so I worked on one myself that at least works for me.
There are 2 methods, use Method A if you don't have a custom ROM installed and still use OxygenOS. Use Method B if you are using a custom ROM and want to have another one:
Method A: From OxygenOS to CustomROM
1. boot in twrp
2. in twrp, do a factory reset
3. flash latest oos zip(flashable ota, link will be below)
4. flash twrp installer zip(i recommend mauronofrio´s twrp, link wil be below)
5. check current slot, then reboot in twrp
6. check if slot changed, then do a factory reset
7. flash latest oos zip
8. flash twrp installer zip
9. reboot recovery, and check if slot changed
10. factory reset
11. flash custom rom zip
12. flash twrp installer zip
13. reboot twrp(check current slot)
14. check if slot changed(if yes:it worked, if no:repeat)
15. additional: flash magisk&gapps
then,your rom is ready to use
Method B: From Custom ROM to another Custom ROM
1. reboot to twrp
2. in twrp, do a factory reset
3. then select advanced wipe: wipe system,cache,data. DON’T WIPE VENDOR
4. flash custom rom zip
5. flash twrp installer zip
6. check which slot you´re in
7. reboot twrp
8. if slot changed, everything worked
9. flash gapps and magisk if you want
then, your rom is ready to use
So, I hope I have spared you many problems and wish you much fun with your Devices.
Links:
Mauronofrio TWRP: click here
OxygenOS Stable OTA 10.3.1: click here
DirtryElectro said:
So, I searched the internet for a method to flash a CustomROM on the OnePlus 6T. But somehow none of them worked, so I worked on one myself that at least works for me.
.......
Links:
Mauronofrio TWRP: click here
OxygenOS Stable OTA 10.3.1: click here
Very important note: Download the FULL OTA, not the local-upgrade OTA!
Click to expand...
Click to collapse
Some of those steps are unnecessary. Like doing a Factory Reset each time you boot to TWRP as that will mess up your Encryption. And in Method B, you mention to Wipe System. DO NOT UNDER ANY CIRCUMSTANCES WIPE SYSTEM ON THE 6T. IT WILL MESS UP YOUR DEVICE. This is the method I use to flash ROMs.
1. Boot to TWRP
2. Flash the latest version of Stable OOS for your Device and latest TWRP Installer for your Device. -> Reboot to Recovery.
3. Flash the latest version of Stable OOS for your Device and latest TWRP Installer for your Device. -> Reboot to Recovery.
4. Flash ROM + TWRP ,Format Data (Go to Wipe, in the lower right corner Format Data, type in 'YES' and hit Enter) -> Reboot to System
5. After first Boot, You can Reboot to Recovery & Flash Magisk (Optional).
These are for EvolutionX that has Gapps built-in so you don't need to flash Gapps. Otherwise you can Skip the Format Data after ROM flash in Step 4, Reboot to Recovery, Flash Gapps and then Format Data. I use these and they have worked flawlessly for me. Also when switching from one AOSP based ROM to another, it's generally recommended to flash OOS Before.
DarthVader said:
Some of those steps are unnecessary. Like doing a Factory Reset each time you boot to TWRP as that will mess up your Encryption. And in Method B, you mention to Wipe System. DO NOT UNDER ANY CIRCUMSTANCES WIPE SYSTEM ON THE 6T. IT WILL MESS UP YOUR DEVICE. This is the method I use to flash ROMs.
1. Boot to TWRP
2. Flash the latest version of Stable OOS for your Device and latest TWRP Installer for your Device. -> Reboot to Recovery.
3. Flash the latest version of Stable OOS for your Device and latest TWRP Installer for your Device. -> Reboot to Recovery.
4. Flash ROM + TWRP ,Format Data (Go to Wipe, in the lower right corner Format Data, type in 'YES' and hit Enter) -> Reboot to System
5. After first Boot, You can Reboot to Recovery & Flash Magisk (Optional).
These are for EvolutionX that has Gapps built-in so you don't need to flash Gapps. Otherwise you can Skip the Format Data after ROM flash in Step 4, Reboot to Recovery, Flash Gapps and then Format Data. I use these and they have worked flawlessly for me. Also when switching from one AOSP based ROM to another, it's generally recommended to flash OOS Before.
Click to expand...
Click to collapse
these are just the steps which worked for me, but ok
DarthVader said:
Some of those steps are unnecessary. Like doing a Factory Reset each time you boot to TWRP as that will mess up your Encryption. And in Method B, you mention to Wipe System. DO NOT UNDER ANY CIRCUMSTANCES WIPE SYSTEM ON THE 6T. IT WILL MESS UP YOUR DEVICE. This is the method I use to flash ROMs.
1. Boot to TWRP
2. Flash the latest version of Stable OOS for your Device and latest TWRP Installer for your Device. -> Reboot to Recovery.
3. Flash the latest version of Stable OOS for your Device and latest TWRP Installer for your Device. -> Reboot to Recovery.
4. Flash ROM + TWRP ,Format Data (Go to Wipe, in the lower right corner Format Data, type in 'YES' and hit Enter) -> Reboot to System
5. After first Boot, You can Reboot to Recovery & Flash Magisk (Optional).
These are for EvolutionX that has Gapps built-in so you don't need to flash Gapps. Otherwise you can Skip the Format Data after ROM flash in Step 4, Reboot to Recovery, Flash Gapps and then Format Data. I use these and they have worked flawlessly for me. Also when switching from one AOSP based ROM to another, it's generally recommended to flash OOS Before.
Click to expand...
Click to collapse
this helped me greatly! following the instructions above had my files corrupt when id factory reset. i dont have an otg usb. so the instructions above kind of troubled me. again, thank you!
Beefybeardedbear said:
this helped me greatly! following the instructions above from OP had my files corrupt when id factory reset. i dont have an otg usb. so the instructions from OP kind of troubled me. again, thank you!
Click to expand...
Click to collapse
I believe I have everything set up correctly to root and install a custom Rom. However, every time I boot into TWRP and zip Magisk I end up with no OS installed. I have to then install the stock rom via USB OTG. Ideas?
follow guide - unlock bootloader, enable usb debugging, boot into fastboot and flash recovery (official 3.3.1.0 works for me), go to recovery, factory reset, format data, restart twrp, copy magisk, rom, gapps and flash them in that order, reboot to system