Hello everybody, i would like to get some help.
I have OB11 on both slots, rebooted recovery, wiped everything as should and still every custom rom fails to boot. Does someone know the correct method of installing?
Thanks.
I've seen about 7 of theese threads. All they have in common is: no one followed the guide on OP, 2nd is none of them installed oos rom on both slots (this you did, but perhaps ob11 isn't recommended, perhaps stable is)
1. Make sure you have the recommended OOS on both slots (ob11 isn't for all roms, some wants stable.
2. Wipe data, dalvik, cache (nothing else)
3. Flash rom you want (some says it's more stable on both slots aswell, for me it works either way)
4.flash twrp
5. Reboot to twrp
6. Flash gapps (if you want it, nano is recommended for some, micro for some. Read the OP)
7. Flash magisk
8.reboot to system
Related
I was on CM12 stock 5.0.2 (version 12.0-YNG1TAS2I3) and i wanted to root my phone , so I unlocked bootloader and rooted the phone but now I want to flash a new Rom but I ve read in a couple of rom threads that we have to flash another 5.1nightly before flashing a ROM and I am not sure I understand this part.
I would be grateful if someone could help me with the process of flashing a 5.1 rom and gaaps for the first time on a freshly rooted phone
P.S : ( I also want to use calaukin's gaaps modified by mohit (http://forum.xda-developers.com/oneplus-one/themes-apps/gapps-modified-slim-gapps-calkulin-t3082242).
Flashing the CM12.1 nightly first ensures that your firmware is up to date. The process goes like this:
1. Download the latest CM12.1 nightly and install it with your custom recovery (no need to flash gapps, but make sure you perform a full wipe (system, data, cache, dalvik cache) first).
2. Boot the phone up once.
3. Boot back into your custom recovery and perform a full wipe.
4. Install your chosen ROM + gapps.
5. Boot phone.
6. Enjoy.
Heisenberg said:
Flashing the CM12.1 nightly first ensures that your firmware is up to date. The process goes like this:
1. Download the latest CM12.1 nightly and install it with your custom recovery (no need to flash gapps, but make sure you perform a full wipe (system, data, cache, dalvik cache) first).
2. Boot the phone up once.
3. Boot back into your custom recovery and perform a full wipe.
4. Install your chosen ROM + gapps.
5. Boot phone.
6. Enjoy.
Click to expand...
Click to collapse
Thank you so much . I followed your guide too so thank you for the support .
It is not necessary to flash nightly first, most ROM threads provide a separate firmware flashable .zip (just make sure it is flashed correctly, cause people reported issues with newer TWRP than 2.8.6.0)
davebugyi said:
It is not necessary to flash nightly first, most ROM threads provide a separate firmware flashable .zip (just make sure it is flashed correctly, cause people reported issues with newer TWRP than 2.8.6.0)
Click to expand...
Click to collapse
I used to share your opinion. But, while a lot of ROM threads do provide a firmware zip, they aren't maintained, it's usually uploaded and forgotten about. Flashing the nightly ensures that you're on the very latest firmware available.
So I am being cautious here.
They mention this:
you will need to flash a latest cm12 nightly before flashing this build AFTER my RR 5.3.0 builds to avoid reboots and bootloops!
I have no idea what this means. Is this valid for in my case? I am currently running stock (just got my One this week).
Thanks!
It's instructing you to flash the nightly so that you're on the right firmware (it's included in the CM nightly). So you'd do this:
1. Download the nightly to your phone.
2. Boot into TWRP recovery and perform a full wipe (system, data, cache, dalvik cache) from the advanced wipe menu.
3. Install the nightly with the install menu.
4. Boot the phone up once.
5. Boot back into TWRP and perform another full wipe.
6. Install your chosen ROM (plus gapps).
7. Reboot into your new ROM and enjoy.
Before you do any of this I'd suggest you make a nandroid backup with TWRP, and also backup your EFS if you haven't done so already. You'll probably benefit from looking at my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Thanks so much!!!
Since a lot of people have had trouble flashing Custom ROMs, I decided to create a guide that should work on every device (whether A/B partition or not) except on Samsung devices. For bypassing Decryption Issues, adb sideload the .zip files.
GUIDE
I am assuming you have unlocked your Bootloader, flashed TWRP and have some knowledge on ADB.
[This is known as a clean install or clean flash]
Turn off Lockscreen Security
Reboot to Recovery
Factory Reset
Format Data
Copy the .zip files from your PC to your phone / Plug in your USB OTG
Flash the ROM and then the Recovery Installer (No Magisk/SuperSU after)
Reboot to Recovery
Flash GApps and Magisk/SuperSU
Reboot to System
[This is known as a dirty flash]
To update the custom ROM or fix a error (Bootloop after successful first boot, No Service, etc.)
I am assuming you used my guide to flash the custom ROM
These are basically the same steps but without wiping or formatting data
Turn off Lockscreen Security
Reboot to Recovery
Flash the ROM (has to be the same ROM, updated is recommended, older versions may cause issues) and then the Recovery Installer (No Magisk/SuperSU after)
Reboot to Recovery
Flash GApps and Magisk/SuperSU
Reboot to System
LINKS:
Official GApps Website - GApps Github
Official TWRP Website - TWRP Github
Magisk Forum - Magisk Thread - Magisk Github
Official SuperSU Website - SuperSU Forum - SuperSU Thread - SuperSU Github
I recommend the Nano variant of GApps since I have had no error with it.
Enjoy!
[Disabler-ONLY]
`This is basically the same guide just if you want to flash Zackptg5's "Universal DM-Verity, ForceEncrypt, Disk Quota Disablers" or any other disabler which requires different steps.
[This is known as a clean install or clean flash]
Turn off Lockscreen Security
Reboot to Recovery
Format Data
Copy the .zip files from your PC to your phone / Plug in your USB OTG
Flash the ROM and then the Recovery Installer (No Magisk after)
Reboot to Recovery
Flash the Disabler, Magisk and then GApps
Reboot to System
Profit
Dirty Flash? You can't. Usually when using a Disabler you have to clean install your custom ROM.
To update use the method in the first post but for step number 5 Flash the Disabler, Magisk and then GApps
This is a bit much to do. Just use twinnfamous' twrp and you can flash a custom easily. Plus, I flash havoc over crdroid, then back and forth again. So you can flash over. Just have to wipe data and cache after ROM flash and twrp flash then reboot to recovery.
Basically:
Fastboot boot twrp (twinnfamous' 0.7)
Be on 9.0.7 firmware as most custom ROMs use this base right now I think..
Anyway, then flash twrp (twinnfamous' 0.7 installer zip)
Reboot to recovery
Now flash custom ROM
Flash twrp zip
Reboot to recovery
(You'll now be on the opposite slot as before, which means you are on the slot which your new custom ROM was installed)
Wipe > custom > data and cache wipe
Install opengapps nano and magisk 18.0
Reboot system
You'll boot right into the ROM setup screen with no decryption issues along the way as long as you do exactly as I said.
Have fun flashing!
dpryor88 said:
This is a bit much to do. Just use twinnfamous' twrp and you can flash a custom easily. Plus, I flash havoc over crdroid, then back and forth again. So you can flash over. Just have to wipe data and cache after ROM flash and twrp flash then reboot to recovery.
Basically:
Fastboot boot twrp (twinnfamous' 0.7)
Be on 9.0.7 firmware as most custom ROMs use this base right now I think..
Anyway, then flash twrp (twinnfamous' 0.7 installer zip)
Reboot to recovery
Now flash custom ROM
Flash twrp zip
Reboot to recovery
(You'll now be on the opposite slot as before, which means you are on the slot which your new custom ROM was installed)
Wipe > custom > data and cache wipe
Install opengapps nano and magisk 18.0
Reboot system
You'll boot right into the ROM setup screen with no decryption issues along the way as long as you do exactly as I said.
Have fun flashing!
Click to expand...
Click to collapse
You wasted that post just for this? I assure you that my tutorial guarantees success when using a official or unofficial version of TWRP or custom ROM, I also used the method you posted about but it did not work. Also what do you mean by "9.0.7"?
The GApps version you use doesn't have to be Nano and Magisk doesn't have to be v18.0. I'm sure you just copy-pasted this, my method should always succeed. The TWRP doesn't have to be from @twinnfamous , it can be from any developer. This is not a OnePlus 6T only guide.
This flashing process is difficult in my view. Why are you making the simple custom rom flashing process so difficult for the noobs.
_Masked_ said:
You wasted that post just for this? I assure you that my tutorial guarantees success when using a official or unofficial version of TWRP or custom ROM, I also used the method you posted about but it did not work. Also what do you mean by "9.0.7"?
The GApps version you use doesn't have to be Nano and Magisk doesn't have to be v18.0. I'm sure you just copy-pasted this, my method should always succeed. The TWRP doesn't have to be from @twinnfamous , it can be from any developer. This is not a OnePlus 6T only guide.
Click to expand...
Click to collapse
Why are you angry? Haha.
And you linked this from the op6t forums so I'm commenting on that phone. And that's how it's done on that phone. And it does matter which twrp you use for THAT phone because one doesn't decrypt correctly.
Copy and paste? No... And nano is always best if you read xda basically anywhere. Not that I said you HAVE to use nano anyway.. it was just in my steps. And that works for me with any/every ROM. So don't be so opposed to other suggestions. Your method is really weird and involves way too much use of a computer/fastboot. Kind of defeats the purpose of using twrp, don't you think?
Ashwinrg said:
This flashing process is difficult in my view. Why are you making the simple custom rom flashing process so difficult for the noobs.
Click to expand...
Click to collapse
What is making it difficult is encryption/decryption not working right in twrp yet (just a guess). I was having a hell of a time getting anywhere myself and kept getting my storage all jumbled from encryption until I found this thread which put it together for me with the adb sideload part, that bypasses encryption or at least lets you flash what you want when the folder names get all wonky.
Thanks OP for laying it out so clearly for me, I am an old dinosaur that was hesitating on messing with this a/b nonsense until I got my 6T and got the itch again. My trusty dusty nexus 6 is so much easier but it's also been around and has one system and a solid twrp for it.
Cheers! :good:
raiderep said:
What is making it difficult is encryption/decryption not working right in twrp yet (just a guess). I was having a hell of a time getting anywhere myself and kept getting my storage all jumbled from encryption until I found this thread which put it together for me with the adb sideload part, that bypasses encryption or at least lets you flash what you want when the folder names get all wonky.
Thanks OP for laying it out so clearly for me, I am an old dinosaur that was hesitating on messing with this a/b nonsense until I got my 6T and got the itch again. My trusty dusty nexus 6 is so much easier but it's also been around and has one system and a solid twrp for it.
Cheers! :good:
Click to expand...
Click to collapse
Sorry for the late reply, but yes this is for bypassing TWRP Decryption issues.
_Masked_ said:
Since a lot of people have had trouble flashing Custom ROMs, I decided to create a guide that should work on every device (whether A/B partition or not) except on Samsung devices.
GUIDE
I am assuming you have unlocked your Bootloader, flashed TWRP and have some knowledge on ADB.
[This is known as a clean install or clean flash]
Turn off Lockscreen Security
Reboot to Recovery
Format Data (Wipe)
Flash ROM and then the Recovery Installer (No Magisk after)
Reboot to Recovery
Go to Advanced, ADB Sideload then sideload GApps, the Recovery Installer and Magisk
Reboot to System
Profit
I recommend the Nano variant of GApps since I have had no error with it.
Enjoy
Click to expand...
Click to collapse
this step means need do with pc not by twrp
ayed78 said:
this step means need do with pc not by twrp
Click to expand...
Click to collapse
This is to bypass Decryption issues.
Ashwinrg said:
This flashing process is difficult in my view. Why are you making the simple custom rom flashing process so difficult for the noobs.
Click to expand...
Click to collapse
I mean I could make a tool for flashing a custom ROM but I'm sure that there's a tool for that already.
bump. (ignore)
_Masked_ said:
Turn off Lockscreen Security
Reboot to Recovery
Factory Reset
Format Data
Copy the .zip files from your PC to your phone / Plug in your USB OTG
Flash the ROM and then the Recovery Installer (No Magisk/SuperSU after)
Reboot to Recovery
Flash GApps and Magisk/SuperSU
Reboot to System
Click to expand...
Click to collapse
So when are we required to wipe system in addition to just a factory reset? And when do we need to format data?
Krullendhaar said:
So when are we required to wipe system in addition to just a factory reset? And when do we need to format data?
Click to expand...
Click to collapse
Just follow the steps, in order.
Hi.
What if I want to flash a custom kernel on a clean Rom flash? When should I do it? Together with Magisk and Gapps?
What do you mean by "Recovery Installer"? That's the only thing I don't understand.
Thank you for this guide.
Santi3598 said:
What do you mean by "Recovery Installer"? That's the only thing I don't understand.
Thank you for this guide.
Click to expand...
Click to collapse
Same here, I do not understand why I should flash a recovery img when twrp does seem to stay installed after flashing everything. Maybe the custom rom I use does include twrp ?
Custom rom means bugs, possible privacy leak and overall less polished. Developer that are working on them are fantastic but they are most of the time nowhere near as what offer the stock one.
What you need is to check adb, doesn't need root but you can still remove apps (even system one) and do more tweaks.
If needed, check how to patch boot image with magisk, it works on all phone and get you root.
With that, you're free to debloat your device.
Hey just one little question: is it ok to dirty flash with encrypted data folder ?
Santi3598 said:
What do you mean by "Recovery Installer"? That's the only thing I don't understand.
Click to expand...
Click to collapse
Me neither, is it safe to assume that the step can be left out if TWRP is already there and I use it to flash the ROM?
Santi3598 said:
Thank you for this guide.
Click to expand...
Click to collapse
+1
I tend to mess things up when flashing new ROMs on my Oneplus6. And I usually end up using the MSMdownloadtool to 'fix my phone' again.
* Does MSMdownloadtool install OOS on both slots?
* What do you advise to do before installing a custom (v10) rom?
* I tried doing a fastboot OOS install by mauronofrio, it didnt work. I got into bootloops after running/finishing the flash all bat file. So I used MSMdownloadtool again. I wondered if the fastboot OOS installer guide by mauronofrio installs OOS on both slots??
* Does the fastboot OOS installer do the same thing as MSMdownloadtool?
* In a lot of guides for clean install custom rom I read as first step: wipe system/data. But then I wonder why do you have to install the correct OOS version first, THEN wipe it, and then install custom ROM. Does an OOS installation leave some hidden (essential) files/partitions behind or something?
* Do you guys switch slots in twrp / or do you reboot to switch slots / or do you use the fastboot --set-active a/b command?
* Why does gapps only have to be installed on 1 slot and not on both?
* Why don't custom ROMS install themselves on both slots straight away, like when you flash the twrp installer zip.. ?
Im currently running carbonROMv8 ROM, its running fine so Im not looking to change yet. But im sure im gonna have to use msmdowndtool again when I wanna try out some other ROM in the future. I dont really feel like im having any control off the flashing process. It either works or it doesnt and when it doesnt I cant explain why..
dumbl3 said:
I tend to mess things up when flashing new ROMs on my Oneplus6. And I usually end up using the MSMdownloadtool to 'fix my phone' again.
* Does MSMdownloadtool install OOS on both slots?
* What do you advise to do before installing a custom (v10) rom?
* I tried doing a fastboot OOS install by mauronofrio, it didnt work. I got into bootloops after running/finishing the flash all bat file. So I used MSMdownloadtool again. I wondered if the fastboot OOS installer guide by mauronofrio installs OOS on both slots??
* Does the fastboot OOS installer do the same thing as MSMdownloadtool?
* In a lot of guides for clean install custom rom I read as first step: wipe system/data. But then I wonder why do you have to install the correct OOS version first, THEN wipe it, and then install custom ROM. Does an OOS installation leave some hidden (essential) files/partitions behind or something?
* Do you guys switch slots in twrp / or do you reboot to switch slots / or do you use the fastboot --set-active a/b command?
* Why does gapps only have to be installed on 1 slot and not on both?
* Why don't custom ROMS install themselves on both slots straight away, like when you flash the twrp installer zip.. ?
Im currently running carbonROMv8 ROM, its running fine so Im not looking to change yet. But im sure im gonna have to use msmdowndtool again when I wanna try out some other ROM in the future. I dont really feel like im having any control off the flashing process. It either works or it doesnt and when it doesnt I cant explain why..
Click to expand...
Click to collapse
Yoo.. So Many Questions. Will try to explain in easiest way..
1. Yes. It Does Flash OOS in Both Slot via Qualcomm Download Mode which is mainly for Manufactures to restore Device..
2. Let me clear that Most people's who face issue in booting custom ROM have their data encrypted by previous or stock ROM.
Here is Link Thread to know how to decrypt your device..
https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643
My own Instructions to Flash Custom ROM (Strictly for Decrypted Device):-
Boot Into Recovery
Wipe Cache, Data & System
Flash Latest Stable/Beta OOS10 & Recovery
Reboot Into Recovery(Ignore No OS Installed Warning)
Flash Latest Stable/Beta OOS10 & Recovery again
Reboot Into Recovery
Now flash Custom ROM + Recovery(If Not Included)
Reboot Into Recovery
Flash Gapps(If not included in ROM), Magisk & No-Verity zip(to keep Device dencrypted)
Reboot & Done
For Installing Update on Same Custom ROM :-
Download the Update
Reboot Into Recovery
Flash Update ZIP & Recovery
Reboot Into Recovery
Flash Gapps(If not included in ROM), Magisk & No-Verity zip(to keep Device dencrypted)
Reboot & Done
3. Fastboot Don't always work if You try to Upgrade/Downgrade Android Version as it won't flash Critical Partitions.. Meanwhile MSMDownload tool Use Download mode which is more powerful.
4. Nope. Both are Different AS both use different mode to flash ROM.
5. Clean install required while flashing new custom ROM because Not All ROM uses Same Base. Some uses Stable OOS or some uses Beta OOS... Now, your answer is in these two build Types...
In my Opinion, Custom ROM have nothing to do with your System partition but it most like to related to Vendor Partition... Both Stable & Beta OOS Have little difference in Vendor partition data..
When any dev Build Any ROM, he uses any one of those Build as base for which he tweak/fix bugs.. That's why always Use Dev specified OOS build for avoid Bootloop/bugs..
6. I prefer last option as it's more reliable..
7. It's like when you clean install any ROM.. When you install Any ZIP, It get installed in an Inactive Slot which make those ZIP data Allowed to use in Active slot..
But when you update ROM for 1st time, You install Gapps as well.. So i don't think you need to Install Gapps on 2nd Update as it already installed in both slots.
1st time when Clean installed & 2nd time when Updated 1st time...
8. It's Because how A/B Partition works... Any zip you flash get installed in inactive slot & this applies to both Stock OOS & Custom ROM...
That's why we have to flash OOS twice before flashing any custom ROM.. Which confirms you will have same Vendor partition regardless to your current slot so when you flash custom ROM it will get booted anyways even after an update..
Hope that's helpful.. Any question or help, you can DM or reply here..
Thanks for your reply. It clears a few things up I think. I got a few follow up questions.
I don't really feel comfortable walking around with a decrypted phone. I have already been pick-pocketed once and also lost two smartphones. I would say the chances are likely that also my OP6 is gonna get lost at some point. Having it decrypted would leave it very vulnerable for people trying to access my files.
* So lets say I decrypt my phone. Is it possible then to encrypt the phone again after I have flashed a new ROM (for example LineageOS 17.1)?
dumbl3 said:
Thanks for your reply. It clears a few things up I think. I got a few follow up questions.
I don't really feel comfortable walking around with a decrypted phone. I have already been pick-pocketed once and also lost two smartphones. I would say the chances are likely that also my OP6 is gonna get lost at some point. Having it decrypted would leave it very vulnerable for people trying to access my files.
* So lets say I decrypt my phone. Is it possible then to encrypt the phone again after I have flashed a new ROM (for example LineageOS 17.1)?
Click to expand...
Click to collapse
Well, In my Opinion Every Device is Vulnerable to Hackers.. Doesn't matter if it's bootloader is Locked or Unlocked...
Your device is more Vulnerable at the time you unlocked bootloader because after that you can execute advanced commands with fastboot.....
If your device have pin/pattern, Thief gone reset your device anyway to reset pass.. Eventually your data get wiped as well....
Well, you can encrypt your data but you might face issue while migrating to other ROM if you face any bug + decrypting your encrypted device again is time taking process if you have alot of data..
I mean there is difference between someone being able to reset/delete my data than someone being able to read my data. As far as I know a thief cannot just read my data after he has stolen my device which is encrypted with unlocked bootloader. Sure, he can connect it to his computer and fastboot delete my sh!t but I don't care I got backups of my most important data anyway, as long as he/she cannot just read my device data its fine by me. But how would I encrypt my device again after I installed, lets say, LineageOS 17.1?
dumbl3 said:
I mean there is difference between someone being able to reset/delete my data than someone being able to read my data. As far as I know a thief cannot just read my data after he has stolen my device which is encrypted with unlocked bootloader. Sure, he can connect it to his computer and fastboot delete my sh!t but I don't care I got backups of my most important data anyway, as long as he/she cannot just read my device data its fine by me. But how would I encrypt my device again after I installed, lets say, LineageOS 17.1?
Click to expand...
Click to collapse
you can.. But do it only if you gone use it for long term....
Not fine to waste your whole day transfer your date from mobile to PC then PC to mobile..
Hi All,
since a couple of days the new LineageOS 19.1 is available for the Moto g7 Power.
A manual upgrade is needed to get it onto the phone.
Since I did the installation but not yet a manual upgrade of LOS to a new major version I have some questions about it:
When reading the upgrade guide there is no info about .... :
will I lose apps or any data when simply sideloading the new version?
will I have to newly install/sideload Magsik?
are there any other important things to consider when doing such an upgrade?
Thanks a lot in advance.
Cheers
1. From my experience of dirty flashing roms via twrp, I can tell you that if you flash a newer lineage zip after ONLY wiping the cache and dalvik partitions, you'll keep your data and settings etc.
2. You most likely won't have to flash the newer version of gapps (as it gets updated upon restart).
Magisk and (maybe) magisk mods are cleared as the boot image gets replaced when flashing a rom.
3. Make a full TWRP backup of your current rom just incase things go sideways with the new one (during installation, or if you want to revert back later).
Since "dirty flashing" via twrp is basically sorta sideloading, I'd assume that these would apply for you as well. I can confirm the magisk one, as that will get removed regardless.
PhotonIce said:
1. From my experience of dirty flashing roms via twrp, I can tell you that if you flash a newer lineage zip after ONLY wiping the cache and dalvik partitions, you'll keep your data and settings etc.
2. You most likely won't have to flash the newer version of gapps (as it gets updated upon restart).
Magisk and (maybe) magisk mods are cleared as the boot image gets replaced when flashing a rom.
3. Make a full TWRP backup of your current rom just incase things go sideways with the new one (during installation, or if you want to revert back later).
Since "dirty flashing" via twrp is basically sorta sideloading, I'd assume that these would apply for you as well. I can confirm the magisk one, as that will get removed regardless.
Click to expand...
Click to collapse
Great, all worked fine, thanks!