Installing custom ROM (Havoc) from scratch - OnePlus 7 Pro Questions & Answers

I am going to give it one more go, before I go mad
On the OnePlus 7Pro.
Dirty flash = without wiping anything?
Clean flash = with wiping, but what?
Going to go back to a full stock mode: https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
Then the following steps;
- Unlock bootloader.
- Get the latest version of havoc: https://sourceforge.net/projects/havoc-os/files/guacamole/
- Get Gapps
- Get TWRP
- Get Magisk
- Reboot and use adb to flash twrp.img
- wipe what? Some variations I have come across, so just asking.
- Flash OOS (some say, but which version).
- Reboot to recovery, or flash custom ROM and TWRP.zip?
- flash custom ROM and TWRP on other slot without wiping anything?
- Reboot to recovery.
- Flash Gapps and Magisk (on slot it is on after last reboot, or doesn't it matter?)
- Reboot system.

Follow these steps. they always worked for me.
1. flash twrp.img using adb
2. sideload twrp using adb sideload
3. reboot recovery
4. format data(one where you type YES)
5. reboot recovery
6. flash oos & twrp
7. reboot recovery
8. flash oos and twrp
9. reboot recovery
10. format data
11. reboot recovery
12. flash rom and twrp
13. reboot recovery
14. flash gapps(if necessary)
15. flash magisk(do remember that some roms require first boot before magisk is flashed)
16. dlash dm verity(if you want to stay decrypted).
17. reboot system

pranacrockz said:
Follow these steps. they always worked for me.
1. flash twrp.img using adb
2. sideload twrp using adb sideload
3. reboot recovery
4. format data(one where you type YES)
5. reboot recovery
6. flash oos & twrp
7. reboot recovery
8. flash oos and twrp
9. reboot recovery
10. format data
11. reboot recovery
12. flash rom and twrp
13. reboot recovery
14. flash gapps(if necessary)
15. flash magisk(do remember that some roms require first boot before magisk is flashed)
16. dlash dm verity(if you want to stay decrypted).
17. reboot system
Click to expand...
Click to collapse
Going to try this later, after being out of the game for a while this new "A/B" stuff is just totally defeating me. I've had to restore the phone with that M2M program, or whatever it is called, like 4 times. Ugh. Really miss the old days.

Do step 4 again(format data) if you are still getting stuck on startup or a bootloop, then reboot. That is what I had to do with my Havoc install to get the ROM to boot.

pranacrockz said:
Follow these steps. they always worked for me.
1. flash twrp.img using adb
2. sideload twrp using adb sideload
3. reboot recovery
4. format data(one where you type YES)
5. reboot recovery
6. flash oos & twrp
7. reboot recovery
8. flash oos and twrp
9. reboot recovery
10. format data
11. reboot recovery
12. flash rom and twrp
13. reboot recovery
14. flash gapps(if necessary)
15. flash magisk(do remember that some roms require first boot before magisk is flashed)
16. dlash dm verity(if you want to stay decrypted).
17. reboot system
Click to expand...
Click to collapse
Why are you using adb twice to install twrp on some nonsense that's unnecessary. All your is open cmd in the folder where you have twrp.img or whatever you named it boot to fastboot
fastboot boot nameoffile.img
Flash twrp installer after it boots and you're done.
And before you try to say that commands doesn't work like everyone I'm going cut you off and let you know that it does no problem cause i always use it. You don't need sideload or flash anything with adb. One simple fastboot command will do it.

pranacrockz said:
Follow these steps. they always worked for me.
1. flash twrp.img using adb
2. sideload twrp using adb sideload (how come sideload again if I used the fastboot command?)
3. reboot recovery
4. format data(one where you type YES)
5. reboot recovery
6. flash oos & twrp
7. reboot recovery
8. flash oos and twrp
9. reboot recovery
10. format data (where I type yes again?)
11. reboot recovery
12. flash rom and twrp
13. reboot recovery
14. flash gapps(if necessary)
15. flash magisk(do remember that some roms require first boot before magisk is flashed)
16. dlash dm verity(if you want to stay decrypted).
17. reboot system
Click to expand...
Click to collapse
Thanks for the reply.
I have a few questions, see above in the quote.
Besides that, when I come from stock, do I need to flash the OOS twice on both slots, and if so, why is that?

Locklear308 said:
Going to try this later, after being out of the game for a while this new "A/B" stuff is just totally defeating me. I've had to restore the phone with that M2M program, or whatever it is called, like 4 times. Ugh. Really miss the old days.
Click to expand...
Click to collapse
Same here

With you guys on the "wow this has become a confusing process" boat.
The thing that gets me is with 100% of tuts, they say format data and then say format data again later when I think they mean wipe data the second time. Am I right?
The process even seems more straight forward following the dual boot twrp tutorial.
I don't have a need to update my custom rom yet so I just would like a clear understanding.
Before someone says "well you've already done it" I fluked it somehow. Lol

dennisb71 said:
Thanks for the reply.
I have a few questions, see above in the quote.
Besides that, when I come from stock, do I need to flash the OOS twice on both slots, and if so, why is that?
Click to expand...
Click to collapse
10. To clarify, yes you have to format(where you type yes)
As far as sideload is concerned, I followed it from a guide written by some dev. But it is not necessary. You may skip it
If coming from stock, you may skip those steps. You just have to ensure that both slots have oos

pranacrockz said:
10. To clarify, yes you have to format(where you type yes)
As far as sideload is concerned, I followed it from a guide written by some dev. But it is not necessary. You may skip it
If coming from stock, you may skip those steps. You just have to ensure that both slots have oos
Click to expand...
Click to collapse
I feel it's gonna be a long weekend again
Wish I could say....here's 20 euro's, please get the ROM running as it should.

pranacrockz said:
Follow these steps. they always worked for me.
1. flash twrp.img using adb
2. sideload twrp using adb sideload
3. reboot recovery
4. format data(one where you type YES)
5. reboot recovery
6. flash oos & twrp
7. reboot recovery
8. flash oos and twrp
9. reboot recovery
10. format data
11. reboot recovery
12. flash rom and twrp
13. reboot recovery
14. flash gapps(if necessary)
15. flash magisk(do remember that some roms require first boot before magisk is flashed)
16. dlash dm verity(if you want to stay decrypted).
17. reboot system
Click to expand...
Click to collapse
I tried the same steps for my onePlus 7 but post flashing oos and twrp and all the steps at step 12 while i try flashing custom rom i.e Pixel experience in my case i get the belowmessage
"Flashing A/B zip to inactive slot B .
To flash additional zips, please reboot recovery to switch to the uploaded slot.
Error installing zip file '/sdcard/PixelExperience_gucamoleb-11.0-20210217-1706-BETA-OFFICIAL.zip'
updating partition details......
...done'"
But while doing step 6 i.e flash oos and twrp despite the below message
"Flashing A/B zip to inactive slot B .
To flash additional zips, please reboot recovery to switch to the uploaded slot"
It gets flashed without issues.
Just to let u know my phone got bricked so i installed the official firmware using the below command.
fastboot -w update images.zip
Any help on this will be appreciated as i m kinda stuck with the stock rom.

Related

How do you upgrade to a newer OOS version with official TWRP

Hey guys,
I'm not sure if any one of you have tried doing this without getting a PC involved. Since there is no recovery partition and recovery is part of the boot partition. How would you go about upgrading to a newer version.
Would you flash the full OOS zip(Let's say the 5.1.8) through TWRP and then you would patch the boot image through TWRP without booting back into system.
Or would you go about upgrading through the settings->updates->upgrade, reboot to system, reboot to fastboot and go through the TWRP flashing again by booting the twrp and then patching the system with twrp?
There are several threads here explaining these questions...
With PC:
Update via settings. Then directly reboot to fastboot to boot twrp. There flash twrp.zip and magisk.zip. Reboot system.
OR
Without PC:
Update via twrp then directly flash twrp.zip. Reboot to twrp (the installed one then gets loaded) and flash magisk. Reboot system.
It's up to you what option you choose.
pdppdp said:
There are several threads here explaining these questions...
With PC:
Update via settings. Then directly reboot to fastboot to boot twrp. There flash twrp.zip and magisk.zip. Reboot system.
OR
Without PC:
Update via twrp then directly flash twrp.zip. Reboot to twrp (the installed one then gets loaded) and flash magisk. Reboot system.
It's up to you what option you choose.
Click to expand...
Click to collapse
So correct me if i was wrong i have to download full rom package and then i have to flash it via twrp and flash twrp installer zip(not the twrp image) then flash magisk and reboot so is this process correct and also will i loose data like photos on internal storage apps i have downloaded it will help me great if you reply to this iam planning to update to 5.1.8 from 5.1.6
Yes almost. After rom installation you flash twrp.zip and reboot recovery and then magisk.
I did it that way some hours ago and did not loose data.
Sorry: had to edit 2 times.
1) download full zip (with oxygen updater or here on the dedicated section)
2) flash via twrp (wait and don't panic it takes some time)
3) instantly flash twrp.zip
4) reboot to recovery for auto switching slot
5) flash magisk
6) reboot to system
7) you're updated/rooted with twrp
Hitman478™ said:
1) download full zip (with oxygen updater or here on the dedicated section)
2) flash via twrp (wait and don't panic it takes some time)
3) instantly flash twrp.zip
4) reboot to recovery for auto switching slot
5) flash magisk
6) reboot to system
7) you're updated/rooted with twrp
Click to expand...
Click to collapse
Thank you
---------- Post added at 01:14 PM ---------- Previous post was at 01:13 PM ----------
pdppdp said:
Yes almost. After rom installation you flash twrp.zip and reboot recovery and then magisk.
I did it that way some hours ago and did not loose data.
Sorry: had to edit 2 times.
Click to expand...
Click to collapse
Thank you
Hitman478™ said:
1) download full zip (with oxygen updater or here on the dedicated section)
2) flash via twrp (wait and don't panic it takes some time)
3) instantly flash twrp.zip
4) reboot to recovery for auto switching slot
5) flash magisk
6) reboot to system
7) you're updated/rooted with twrp
Click to expand...
Click to collapse
Worked perfectly for me. Thanks!
ahamling27 said:
Worked perfectly for me. Thanks!
Click to expand...
Click to collapse
Here to thanks :good:

Unable to flash anything other than oos

I know, there've been plenty of "please help, I can't flash xx" threads. If there's a duplicate out there, please point me towards it.
I've been trying to get havoc or omni on my phone recently for fun but have had no luck. I've tried multiple different ways, maybe someone can tell me what I'm doing wrong or if there is actually something wrong with my device.
Method 1:
-Use the Oneplus Recovery tool to get a fresh start
-allow OOS to update itself to 9.0.3
-unlock bootloader
-boot twrp-3.2.3-x_blu_spark_v9.91_op6
-flash havoc (for example), flash twrp right after
-reboot to recovery (using button in twrp)
->this results in the phone restarting, shows bootloader unlocked screen, and then goes to black screen/white LED
Method 2:
-bootloader unlocked
-extract 9.0.3 full rom, use flash-all.bat
-fastboot set_active other
-flash-all.bat again (to get the other slot)
-boot twrp-3.2.3-x_blu_spark_v9.91_op6
-flash havoc (for example), flash twrp right after
-reboot to recovery (using button in twrp)
->this results in the phone restarting, shows bootloader unlocked screen, and then goes to black screen/white LED
After this black screen/white led issue, I can get into fastboot but I can't boot the twrp image.
I'm at wits end... I really have no clue what to do. Any ideas? I'm open to try any suggestions.
I should note, when I get 9.0.3 on there, either from method 1 or 2 it's possible to boot and use it.
Try these steps:
(Make sure You have unlocked BL)
Fastboot boot twrp_blue_spark.img
Now go to wipe and choose format data, type yes.
Copy this: OxygenOS 9.0.3 OTA.zip
To Your internal storage.
Now flash it.
Now go to reboot in TWRP and choose reboot bootloader.
Now fastboot boot twrp.img again.
Flash OxygenOS OTA zip again.
Now go to reboot in TWRP, choose reboot bootloader.
Fastboot boot twrp.img again.
Copy latest Havoc OS 2.1 to Your internal storage.
Flash it.
Reboot without flashing anything else.
Should work now:fingers-crossed:
Like 99% you didn't read the "how to" oos needs to be flashed on both slot a and B from twrp rather than fastboot
whizeguy said:
Like 99% you didn't read the "how to" oos needs to be flashed on both slot a and B from twrp rather than fastboot
Click to expand...
Click to collapse
I've tried flashing it on both slots a ton of times from twrp. Never got it to work.
Gibsonflyingv said:
I've tried flashing it on both slots a ton of times from twrp. Never got it to work.
Click to expand...
Click to collapse
Boot to twrp
Flash OOS 9.0.3 (if it's recommended to use that)
Flash twrp
Reboot to twrp
Flash OOS again
Flash twrp
Reboot to twrp
Wipe data, cache / dalvik
Flash custom rom
Flash twrp
Reboot to twrp
Flash gapps
Flash magisk
Done.
I've read this 4 times, should be right (high fever now so I just wanted to make sure)

[GUIDE] A faster and updated guide to root, magisk and return to stock

#Prerequisites:
Stock Rom: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
TWRP: https://dl.twrp.me/ali/twrp-3.3.0-0-ali.img
Dejello TWRP: https://drive.google.com/open?id=1QWYIcti-wJPPMAc8Ol5pnoO3b8CqtKFn (Unofficial) //Only for custom roms, when you need to install GApps.
Magisk: https://github.com/topjohnwu/Magisk/releases/download/v19.0/Magisk-v19.0.zip
Magisk Manager: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.1.1/MagiskManager-v7.1.1.apk
DM Verity Disabler: https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_04.03.19.zip
Unlocked Bootloader: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Minimal ADB/Fastboot (Windows only): https://androidfilehost.com/?fid=962187416754459552
Moto USB Drivers (drivers only, no manager): https://motorolausbdriver.com/wp-content/uploads/Motorola_Mobile_Drivers_v6.4.0.zip
Windows hint:
For all what you want to do with your Motorola phone, you need the above provided Minimal ADB/Fastboot environment.
Download and extract it,
Move the files you want to flash into the folder
Open CMD (Windows Key and R - then type cmd) and navigate into the extracted folder.
//It's easier when you type cd into the cmd and drag the folder from your adb/fastboot environment into the cmd window and hit enter.
And that's it. The patched boot image is no longer needed.
Rooting the Moto G6
1. Boot into fastboot mode (Vol - and Power simultaneously) and connect it to your computer
2. Open Terminal (Linux)/CMD (Windows) and go into the folder where your recovery image lies.
3. Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
4. If it asks for a password hit cancel, go to wipe, data wipe and confirm it with yes. Then reboot again into recovery.
5. Repeat the wiping and reboot another time into recovery.
6. Connect your phone to your Computer while in recovery and copy magisk and dm-verity disabler to your phone.
7. Go to Install and flash dm-verity disabler first, then magisk.
Thats it. You're rooted.
Update/Go back to Stock.
//Download the stock rom you want to use and extract it to your Desktop.
//Latest ROM (Android 9) is ALI_RETAIL_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
1. Go into recovery mode (twrp), choose wipe - wipe data and confirm with yes.
2. Back to the wipe main screen, advanced wipe and hit everything.
3. Wipe it two times.
4. Boot into download mode and connect your phone to your computer.
5. Open Terminal or CMD in the folder of your stock firmware and hit the following commands (hint: it's easier to use a bash/batch file):
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
fastboot flash dsp adspso.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot erase cache
fastboot reboot
Wait until it finished, disconnect your phone, wait and set it up.
That's it.
Simple and easy.
So... When do you tell people about installing ADB and fastboot? Moto drivers? Ya skipped some stuff dude.
madbat99 said:
So... When do you tell people about installing ADB and fastboot? Moto drivers? Ya skipped some stuff dude.
Click to expand...
Click to collapse
For my own experience it worked without moto drivers. On Windows 7 and Windows 10 testing systems.
Personally I use Arch, which natively supports adb and fastboot, provided by the android-tools package.
But thank you for your hint, I added it.
And for root not need boot.img file?
cecogor said:
And for root not need boot.img file?
Click to expand...
Click to collapse
No, Magisk is patching the stock boot.img, which is already on your device.
The patched images are not needed anymore for Magisk.
ThisIsRussia said:
No, Magisk is patching the stock boot.img, which is already on your device.
The patched images are not needed anymore for Magisk.
Click to expand...
Click to collapse
Ok, I see.
I remark one more thing - "Disable_Dm-Verity_ForceEncrypt_02.04.2019" i much more biger then "Force_Encryption_Disabler_For_ALI_Oreo_v2" - 4MB vs 100kB. What is different here?
cecogor said:
Ok, I see.
I remark one more thing - "Disable_Dm-Verity_ForceEncrypt_02.04.2019" i much more biger then "Force_Encryption_Disabler_For_ALI_Oreo_v2" - 4MB vs 100kB. What is different here?
Click to expand...
Click to collapse
Due to OS changes and it's a feature bundle.
It edits DM-Verity, ForceEncrypt and Disk Quota.
Can't get root
The install by the instructions went perfectly but I can't get root. I did one thing differently than on the root instructions and I think I did it correctly, where you have;
Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
I did "fastboot flash recovery twrp-3.2.3-0-ali.img" which I thought you meant because stock recovery would already be installed or am I missing something here. I followed all the rest of the instructions perfectly and everything seemed to wipe reboot and install fine but when I boot back into android I don't have root. In fact I tried it four times and never got root. Do you have any ideas what could be wrong? Thanks for any help but I do have Android 9 running just fine. I'd like to get this rooted rather than go back to 8 because it seems to run so much better.
mward7221 said:
The install by the instructions went perfectly but I can't get root. I did one thing differently than on the root instructions and I think I did it correctly, where you have;
Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
I did "fastboot flash recovery twrp-3.2.3-0-ali.img" which I thought you meant because stock recovery would already be installed or am I missing something here. I followed all the rest of the instructions perfectly and everything seemed to wipe reboot and install fine but when I boot back into android I don't have root. In fact I tried it four times and never got root. Do you have any ideas what could be wrong? Thanks for any help but I do have Android 9 running just fine. I'd like to get this rooted rather than go back to 8 because it seems to run so much better.
Click to expand...
Click to collapse
You Need install magisk Manager wich is linked above and restart device.
Then open magisk Manager from Menu.
ThisIsRussia said:
You Need install magisk Manager wich is linked above and restart device.
Then open magisk Manager from Menu.
Click to expand...
Click to collapse
I tried all that and couldn't get it to work, I downloaded everything from your links above but no go. Someone posted a no-verity boot image in another thread. post 598 I believe and I flashed that file, flashed Magisk 18.1 in twrp and now I have root so I'm set, Thanks for your reply
ThisIsRussia said:
For my own experience it worked without moto drivers. On Windows 7 and Windows 10 testing systems.
Personally I use Arch, which natively supports adb and fastboot, provided by the android-tools package.
But thank you for your hint, I added it.
Click to expand...
Click to collapse
Of course on Linux no drivers are needed. But most running Linux don't need instructions. It's usually windows users needing such instructions.
That's the only reason I chimed in.
Carry on.
Nice guide.
ThisIsRussia said:
Update/Go back to Stock.
//Download the stock rom you want to use and extract it to your Desktop.
//Latest ROM (Android 9) is ALI_RETAIL_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
1. Go into recovery mode (twrp), choose wipe - wipe data and confirm with yes.
2. Back to the wipe main screen, advanced wipe and hit everything.
3. Wipe it two times.
4. Boot into download mode and connect your phone to your computer.
5. Open Terminal or CMD in the folder of your stock firmware and hit the following commands (hint: it's easier to use a bash/batch file):
Click to expand...
Click to collapse
When updating a rooted phone from Android 8 to Android 9 do you have to wipe (in TWRP) and use the following?
Code:
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
kmssd said:
When updating a rooted phone from Android 8 to Android 9 do you have to wipe (in TWRP) and use the following?
Click to expand...
Click to collapse
If you Change major OS Version, you always need a clean Flash and rerooting.
ThisIsRussia said:
For my own experience it worked without moto drivers. On Windows 7 and Windows 10 testing systems.
Personally I use Arch, which natively supports adb and fastboot, provided by the android-tools package.
But thank you for your hint, I added it.
Click to expand...
Click to collapse
I would change official TWRP to Dejello's unofficial TWRP as official one won't install Gapps
https://drive.google.com/open?id=1QWYIcti-wJPPMAc8Ol5pnoO3b8CqtKFn
Hi ppl, sorry for that questions, I make a lot of roots, on mine Samsung S3, Sony ZQ, and many other, But in last times I dont make it with magisk.... so someone can explain some things for me?
First work on XT1925-3? 4/64gb variant?
TWRP is need or only ADB? I just want to make only by adb...
If its okay now:
1. Boot into fastboot mode (Vol - and Power simultaneously) and connect it to your computer
Click to expand...
Click to collapse
>> Here is ok,
2. Open Terminal (Linux)/CMD (Windows) and go into the folder where your recovery image lies.
Click to expand...
Click to collapse
>> Here is ok too
3. Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
Click to expand...
Click to collapse
>> Here is ok too, similar to flash my Sony
4. If it asks for a password hit cancel, go to wipe, data wipe and confirm it with yes. Then reboot again into recovery.
Click to expand...
Click to collapse
>> I belive if I have pass on phone? if I remove the phone only need a reboot in recovery?
5. Repeat the wiping and reboot another time into recovery.
Click to expand...
Click to collapse
>> The phone will be need a wipe two wipes? or only one?
6. Connect your phone to your Computer while in recovery and copy magisk and dm-verity disabler to your phone.
Click to expand...
Click to collapse
>> Here is mine question, the phone wont wakeup for now, but in recovery mode will be open folder to that? I remeber on my S3 in twrp I mount the storage to acess, in ADB method is same?
7. Go to Install and flash dm-verity disabler first, then magisk.
Click to expand...
Click to collapse
>> Okay, install DM, after that, wakeup phone, and after that flash magisk? Magisk maneger is same thing? So, is Flash DM > reboot into recovery or wakeup? after, flash magisk, reboot again? install magisk maneger?
So, sorry for that all questions, and if I trade some words, I have dyslexia and I'm backing to root world after a long time.
brunogroa said:
Hi ppl, sorry for that questions, I make a lot of roots, on mine Samsung S3, Sony ZQ, and many other, But in last times I dont make it with magisk.... so someone can explain some things for me?
First work on XT1925-3? 4/64gb variant?
TWRP is need or only ADB? I just want to make only by adb...
If its okay now:
>> Here is ok,
>> Here is ok too
>> Here is ok too, similar to flash my Sony
>> I belive if I have pass on phone? if I remove the phone only need a reboot in recovery?
>> The phone will be need a wipe two wipes? or only one?
>> Here is mine question, the phone wont wakeup for now, but in recovery mode will be open folder to that? I remeber on my S3 in twrp I mount the storage to acess, in ADB method is same?
>> Okay, install DM, after that, wakeup phone, and after that flash magisk? Magisk maneger is same thing? So, is Flash DM > reboot into recovery or wakeup? after, flash magisk, reboot again? install magisk maneger?
So, sorry for that all questions, and if I trade some words, I have dyslexia and I'm backing to root world after a long time.
Click to expand...
Click to collapse
Here are the steps I use to flash/root my wifes Moto G6 xt1925-6 (pie)
1. Make sure dev options are on and usb debugging is on.
2. adb reboot bootloader
3. Extract the image file directly into the same directory as adb and fastboot.
4. Launch cmd as admin, CD to the directory where adb and fastboot is.
5. via CMD launch flash_all.bat which will run through and do all the flashing of the necessary parts.
6. I actually did the first time setup, making sure usb debugging is on again and also making sure I dont have any pw or security enabled.
7. adb reboot bootloader.
8. fastboot flash recovery recovery.img
9. fastboot flash boot no-verity_boot.img
10. boot into twrp and then format, I did a Format data, then a factory data reset.
11. back in twrp copy magisk over to phone, and install via twrp
12. reboot system and it should boot up again.
13. make sure to do first time setup and enable usb debugging and make sure magisk manager is installed, updated, and configured how you want it.
14. I usually do core only mode, magisk hide, and also hide the magisk manager package via the settings. under general settings.
Stuck on Booting screen
Unlocked bootloader on Moto G6 xt1925-6 RETUS. Loaded TWRP fine. Did factory reset twice to remove data encryption. Installed Disable_Dm-Verity_ForceEncrypt_03.28.19.zip followed by Magisk 18.1.zip. Boots back to recovery fine but stays at boot screen when booting to system.
Any suggestions.
Stephen
theseeker2654 said:
Here are the steps I use to flash/root my wifes Moto G6 xt1925-6 (pie)
1. Make sure dev options are on and usb debugging is on.
2. adb reboot bootloader
3. Extract the image file directly into the same directory as adb and fastboot.
4. Launch cmd as admin, CD to the directory where adb and fastboot is.
5. via CMD launch flash_all.bat which will run through and do all the flashing of the necessary parts.
6. I actually did the first time setup, making sure usb debugging is on again and also making sure I dont have any pw or security enabled.
7. adb reboot bootloader.
8. fastboot flash recovery recovery.img
9. fastboot flash boot no-verity_boot.img
10. boot into twrp and then format, I did a Format data, then a factory data reset.
11. back in twrp copy magisk over to phone, and install via twrp
12. reboot system and it should boot up again.
13. make sure to do first time setup and enable usb debugging and make sure magisk manager is installed, updated, and configured how you want it.
14. I usually do core only mode, magisk hide, and also hide the magisk manager package via the settings. under general settings.
Click to expand...
Click to collapse
Ohh sure... So need twrp to do, I Will trie this, thx a lots, here is the same with pie
Tom Swift said:
Unlocked bootloader on Moto G6 xt1925-6 RETUS. Loaded TWRP fine. Did factory reset twice to remove data encryption. Installed Disable_Dm-Verity_ForceEncrypt_03.28.19.zip followed by Magisk 18.1.zip. Boots back to recovery fine but stays at boot screen when booting to system.
Any suggestions.
Stephen
Click to expand...
Click to collapse
On top of using the disabler download and flash the no verity boot.img from the link below. Works great on my xt1925-6 with pie.
Also, use Magisk 19.0
https://drive.google.com/file/d/1JLMVRBCsMnr7RYxdRFjFLOwVSy8r8hSQ/view
The DM Verity Disabler link not working:
https://zackptg5.com/downloads/Disab...02.04.2019.zip

Unable to flash TWRP. Lost Recovery, OS and only have unlocked bootloader.

Hi,
I was on Oxygen OS 10.0.0. Rooted with twrp-3.3.1-4-enchilada and magisk 20.1. (I had used this guide to do it. https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213) Today I downloaded the zip for 10.0.1 from the Oxygen Updater app and tried to flash it like I have done for OOS 9 in the past as usual. I went to recovery (I did not backup), I just wiped my data (not internal storage), cache and system. After that I tried to install the new zip but I got an error. It just said error unable to install. Didn't mention why. I tried flashing the older OOS 10 zip and got the same error.
So I thought I will try flashing on the other slot. I was on slot B. I switched to slot A and got the same error.
So I thought I will try to sideload. When I tried that I got the same error. So I thought I will try to reflash the twrp img itself. I went to fastboot mode and tried runnning this command
fastboot boot twrp-3.3.1-14-enchilada-Q-mauronofrio.img
It showed me this error
Sending 'boot.img' (65536 KB) OKAY [ 1.609s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Now I don't have any recovery at all. I have just the unlocked bootloader and no OS nor recovery. What can I do to flash TWRP again and install either OOS 10.0.1 zip or 10.0.0 zip? Any help will be great.
Thanks
Arnavzz said:
Hi,
I was on Oxygen OS 10.0.0. Rooted with twrp-3.3.1-4-enchilada and magisk 20.1. (I had used this guide to do it. https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213) Today I downloaded the zip for 10.0.1 from the Oxygen Updater app and tried to flash it like I have done for OOS 9 in the past as usual. I went to recovery (I did not backup), I just wiped my data (not internal storage), cache and system. After that I tried to install the new zip but I got an error. It just said error unable to install. Didn't mention why. I tried flashing the older OOS 10 zip and got the same error.
So I thought I will try flashing on the other slot. I was on slot B. I switched to slot A and got the same error.
So I thought I will try to sideload. When I tried that I got the same error. So I thought I will try to reflash the twrp img itself. I went to fastboot mode and tried runnning this command
fastboot boot twrp-3.3.1-14-enchilada-Q-mauronofrio.img
It showed me this error
Sending 'boot.img' (65536 KB) OKAY [ 1.609s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Now I don't have any recovery at all. I have just the unlocked bootloader and no OS nor recovery. What can I do to flash TWRP again and install either OOS 10.0.1 zip or 10.0.0 zip? Any help will be great.
Thanks
Click to expand...
Click to collapse
So basically what happened there is TWRP doesn't boot with the oxygenos 10 bootloader. You will need to use the MSM download tool to unbrick your device.
Sent from my ONEPLUS A6003 using Tapatalk
Kaleshwar said:
So basically what happened there is TWRP doesn't boot with the oxygenos 10 bootloader. You will need to use the MSM download tool to unbrick your device.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
But how is that? I was on stable OOS 10 before rooting following this link https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213. As per this, the first step is to flash twrp and that image did flash back when I did it. Any idea why it doesn't work now?
Also, do you have any links for the MSM download tool and any guide if there is?
Thanks
Arnavzz said:
But how is that? I was on stable OOS 10 before rooting following this link https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213. As per this, the first step is to flash twrp and that image did flash back when I did it. Any idea why it doesn't work now?
Also, do you have any links for the MSM download tool and any guide if there is?
Thanks
Click to expand...
Click to collapse
The problem isn't TWRP it's the bootloader. That's all I know. And for the MSM download tool. See attached link below.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Sent from my ONEPLUS A6003 using Tapatalk
Do not boot the twrp from fastboot it won't work
Just do
Fastboot flash boot twrp.img
Then reboot the device to twrp it will boot to trwp and then flash the new a10 zip and immediately afterwards flash the twrp zip
chintu1234 said:
Do not boot the twrp from fastboot it won't work
Just do
Fastboot flash boot twrp.img
Then reboot the device to twrp it will boot to trwp and then flash the new a10 zip and immediately afterwards flash the twrp zip
Click to expand...
Click to collapse
This doesn't work. It flashes successfully but when I select Reboot Recovery and press the power button, it boots back to the bootloader.
Maybe wrong twrp img
Try the older 3.3.1-12 twrp.img and then try
Also try the following as well
Fastboot flash boot_a twrp.img
Fastboot flash boot_b twrp.img
And try just reboot not reboot to recovery
Kaleshwar said:
The problem isn't TWRP it's the bootloader. That's all I know. And for the MSM download tool. See attached link below.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Thanks so much for that! I have been able to recover the phone using MSM download tool. Now will update to 10 using the phones OTA.
However, I have one question, if I update to OOS 10.0.1, do you think this original post on rooting OOS 10, will work for it? https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213 Or do you suggest to not root and wait?
Arnavzz said:
Thanks so much for that! I have been able to recover the phone using MSM download tool. Now will update to 10 using the phones OTA.
However, I have one question, if I update to OOS 10.0.1, do you think this original post on rooting OOS 10, will work for it? https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213 Or do you suggest to not root and wait?
Click to expand...
Click to collapse
You can try it . Looks pretty solid.
Sent from my ONEPLUS A6003 using Tapatalk
Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules first to avoid issues (in TWRP if you cannot boot to system. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242)
Update through local update to 10.3.2 is what I prefer to do. Then I do the following.
Reboot to let phone finish whatever. reboot into bootloader.
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-18-enchilada-Q-mauronofrio.img - ( https://sourceforge.net/projects/ma...3.3.1-18-enchilada-Q-mauronofrio.img/download )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3.2 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP (https://sourceforge.net/projects/ma...-enchilada-installer-mauronofrio.zip/download ) or Blu zip (https://github.com/engstk/android_device_oneplus_enchilada/releases)
5. Reboot to recovery
6. Flash Magisk 20.3 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://mega.nz/#!PO5x1bYA!dKq3pbxUdpb16zhuqM_idqvWNLnsu4Ky4IAmYQiQUDw
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
I had similar situation last evening.
I made the mistake of having a factory reset on rooted 9.0.8 and then trying to flash the 10.0.1
I got the same error, so I had to connect my mobile to my laptop, fastboot to the newest TWRP, flash the TWRP, flash the 9.0.9, flash the 10.0.1, flash magisk 20.x and then everything was working.
xpakage said:
Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules
Update through local update 10.3 or current ROM
Reboot
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-16-enchilada-Q-mauronofrio.img - ( https://androidfilehost.com/?fid=4349826312261678088 )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP ( https://androidfilehost.com/?fid=4349826312261678087 ) or Blu zip (https://github.com/engstk/op6/releases/download/r112/blu_spark_r112-oos_op6-op6t_0dd5f9228.zip)
5. Reboot to recovery
6. Flash Magisk 20.1 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://drive.google.com/file/d/1w44cUg815g-H1h_6gObUVPLDTc_dtiMX/view
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Click to expand...
Click to collapse
This worked for me.. Finally. PS - I did in a slightly different order. I installed twrp first, booted into twrp, made sure I was in slot A. If I wasnt, I rebooted to recovery. If I still wasnt I set slot to A manually then rebooted to recovery again. Flashed the stock boot img you linked to boot, then rebooted to recovery slot b (same process I did to get to slot a) then flashed the stock boot img to boot again THEN finally installed magisk. Booted to system, where it hanged a bit, rebooted before getting into android, but booted in just fine after that..
For some reason if you don't flash stock img to slot A (and maybe slot B too, I did this for good measure) before installing magisk everything dies a horrible death and breaks, which can't even be recovered from /boot /system backups..
EDIT: Tried to reboot into recovery, which reverted back to stock for some reason after doing the above steps. So I proceeded to install the bluspark recovery, rebooted into recovery, made sure I was in slot b, made a back up of the boot image, then flashed bluspark kernel. Got stuck at the unlocked bootloader screen. Rebooted into recovery, restored my /boot back. Still stuck when I try to boot into system. Fixed it by booting back into recovery in slot A flashing stock boot img, then into slot b stock boot, then magisk, but also installed bluspark kernel here because I had a feeling I would lose twrp from flashing to stock boot img, and that the issue was caused by twrp (both twrp-3.3.1-16-enchilada-installer-mauronofrio and twrp-3.3.1-x_blu_spark_v9.108_op6 have this issue). Guess what? Turns out I was right. Having twrp breaks everything after you install magisk, so you need to flash the stock boot img before flashing magisk for some reason.. and cant install twrp again unless you dont mind bricking your phone.
EDIT2: F2FS works, just boot into recovery via fastboot (this should be slot b), change /data to f2fs, boot back into fastboot then into recovery again by fastboot (slot b again), flash stock boot img > magisk > bluspark kernel > f2fs_fstab.zip > f2fs_optimize.zip > factory reset/wipe (from twrp before rebooting), done just reboot into system. You of course lose twrp because magisk doesnt like twrp on oos 10.x for some reason, and will need to set everything up again to cause of the wipe. If you dont factory reset/wipe from twrp before booting into system your system will crash and reboot every time you boot into android, then have to do all the steps I listed again.
EDIT3: Never mind, I was wrong, f2fs makes almost all your apps and storage unusable. Not sure if it's cause of the rom (OOS10.3.0) or because we have to flash stock boot.img and get rid of twrp before booting into system. Either way, f2fs has never really been stable or fun to get working so better to stick to ext4.. that few percent performance boost isnt worth it.
EDIT4: This is my last update. After experimenting with different things, bricking my phone, restoring it via fastboot rom, many many times, I've verified the simplest and cleanest way to install magisk.. Do note you wont be able to keep twrp.
Method A - If you already have twrp
Boot recovery into slot a, flash your rom's stock boot.img, then boot into your recovery in slot b (dont boot into slot a recovery because slot a wont have twrp anymore), flash your rom's stock boot.img, magisk and (optional) your kernel of choice (or not) in that order, then you can boot boot into system. That's it.
Method B - If you don't have twrp
Boot into fastboot, and from your cmd/terminal run fastboot flash boot yourtwrp.img (I suggest Mauronofrio's twrp-3.3.1-16-enchilada-Q-mauronofrio.img or newer). Use your volume buttons to select boot into recovery. Make sure your active slot is B, (if it isnt, install twrp (bluspark and Mauronofrio's twrp both work great) by zip, then follow the steps above in method A). Once you've verified you're in slot B flash your rom's stock boot.img, magisk and (optional) your kernel of choice (or not) in that order, then you can boot into system. That's it.
Maybe @mauronofrio or @eng.stk can verify why magisk or twrp bricks the system when you install them together on OOS 10.
not working
sir i follow your steps but phone is stuck on boot i have official version a10 10.3.0 update on 25.12.19
pls tell me how i get root access....
gauravkapoor99150 said:
sir i follow your steps but phone is stuck on boot i have official version a10 10.3.0 update on 25.12.19
pls tell me how i get root access....
Click to expand...
Click to collapse
U need to flash the magisk v22 zip file through the .108 TWRP recovery
Sent from my ONEPLUS A6003 using Tapatalk
RASTAVIPER said:
U need to flash the magisk v22 zip file through the .108 TWRP recovery
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
sir can you send me a link
lemon07r said:
Maybe @mauronofrio or @eng.stk can verify why magisk or twrp bricks the system when you install them together on OOS 10.
Click to expand...
Click to collapse
@mauronofrio wrote the following in his TWRP thread a while ago:
So little update, after some tests i'm sure there is a compatibility problem between twrp and magisk, i was able to get only one of them, so actually i don't know how to proceed, i need to understand if it is a twrp problem or a magisk problem, TWRP is in stand-by for now.
There are not problems on Android Pie, if you need of the twrp on android Q just flash in boot partition the Q .img (fastboot flash boot twrp.img) and then reboot from fastboot in recovery. Before publishing the twrp I had not tested magisk and twrp together.
On Android 10 use only magisk 19.4
Click to expand...
Click to collapse
xpakage said:
Put the TWRP zip and stock boot img on phone (a TWRP img is not a TWRP zip)
Remove Magisk modules first to avoid issues (in TWRP if you cannot boot to system. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242)
Update through local update to 10.3.2 is what I prefer to do. Then I do the following.
Reboot to let phone finish whatever. reboot into bootloader.
1. Fastboot TWRP img - fastboot flash boot twrp-3.3.1-18-enchilada-Q-mauronofrio.img - ( https://sourceforge.net/projects/ma...3.3.1-18-enchilada-Q-mauronofrio.img/download )
2. Use volume up to recovery and power button to boot to recovery
3. Flash 10.3.2 stock boot img while in TWRP (or current ROM stock boot img).
4. Flash TWRP zip while in TWRP (https://sourceforge.net/projects/ma...-enchilada-installer-mauronofrio.zip/download ) or Blu zip (https://github.com/engstk/android_device_oneplus_enchilada/releases)
5. Reboot to recovery
6. Flash Magisk 20.3 while in TWRP
(Flash a Q kernel if you want one other than stock)
7. Reboot system
You are now rooted
Stock boot 10.3 img
https://mega.nz/#!PO5x1bYA!dKq3pbxUdpb16zhuqM_idqvWNLnsu4Ky4IAmYQiQUDw
Most stock boot imgs
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Click to expand...
Click to collapse
Basically worked for me, too, with 2 exceptions:
- this tool to remove magisk modules etc. wouldn't be flashed, always ended in an unnamed error; probably the cause for some other problems?
- flashing boot.img (V 10.3.4 from this thread) didn't work for me, I always ended up in twrp's splash screen
- got it solved by dirty flashing the full V 10.3.4 ROM (again from the above thread)
Many thanks once again!

G7 ThinQ G710EM Magisk, TWRP, No Force Encryption

Hi, today I experienced unexpected update to Android 10 even I had turned off auto updates and I bricked my phone trying to roll back. So while trying to revive my phone I tested few things and found a way to sort it all out.
Now my phone has TWRP on RAMDISK and no problems with Force Encryption. I didn't tested backup and restore yet so feel free to post results in comments.
1. Install stock ROM, In my case it was 20k, let it fully boot after flash
2. Flash patched boot (for example 20k patched with Magisk 21.1) and boot system to check if you have root:
a. "fastboot flash boot_a magisk_patched.img"
b. "fastboot flash boot_b magisk_patched.img"
3. Boot TWRP G710EM "fastboot boot TWRP_G710EM.img"
4. FORMAT DATA (option where you gonna have to type "YES"), reboot but be careful DO NOT LET SYSTEM BOOT, so keep holding Vol- button while connected to PC and boot TWRP
5. Flash Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip, reboot and once again boot TWRP
6. In Advanced, Flash TWRP to RAMDISK, choose TWRP_G710EM.img and wait until end
7. Reboot. Your phone probably reboots to recovery so in Advanced, Repair Recovery Bootloop
8. Flashing TWRP to RAMDISK can damage Magisk so flash latest zip through TWRP.
9. Done.

Categories

Resources