Related
Hello
I unlocked my bootloader, then installed CWM, rooted then installed unofficial EMUI 4 ROM.
But I was EMUI 3.1 before...
So my Honor 6 didn't work after that and never couldn't boot the ROM
When I try to install CWM again by Multi-Tool, flashing error says that I need to check the confirmation dialog on my device but I cant't access to my device because there is no ROM :|
I installed EMUI 4 stock recovery and now what can I do for reinstall the rom -_-
Is there any way at all?
Have you tried downloading EMUI 3.0 stock ROM and using the three button method after placing it on your SD card? which is power + vol up + vol down?
In order to get back to full stock ROM follow these steps, since you already flashed recovery of a build number I don't know, do it again by following the procedure:
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
Enjoy your out of the box device..!!
DigiGoon said:
In order to get back to full stock ROM follow these steps, since you already flashed recovery of a build number I don't know, do it again by following the procedure:
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
Enjoy your out of the box device..!!
Click to expand...
Click to collapse
Hi Digicoon,
I tried your method to restore to stock ROM after successfully installing KangVip Rom.
Actually this custom rom was intended for Mate7, but beeing a simple port from Honor6Plus (as stated by the developer) I installed on my device without any problem. The only thing I noticed was that my device was no more a Honor6Plus PE-TL10, but a DUK-AL20 which I think is Mate7 model number, right?
The ROM works good but I wanted to revert it back to stock.
Anyway, I tried downloading the kitkat stock rom for my Honor6Plus (it should be PE-TL10_EMUI3.0_Android4.4_V100R001CHNC00B260.zip) , extracted the UPDATE.APP and the four files you stated above, flashed them via fastboot and then put the entire dload folder inside the root of my SD card.
The phone hangs on the boot screen and then boot loop... no way to restore it.
I reverted it back to custom rom (via nandroid backup), even tried to flash the stock recovery.img to use the "Three buttons method" but with no luck, every time it stucks on boot logo and bootloop.
Do you have any idea what could it be? Maybe a "partitions" problem, due to different model number?
Thanks in advance and Merry Christmas
Also work for rooted L04 (TWRP) back to lollipop?
DigiGoon said:
In order to get back to full stock ROM follow these steps, since you already flashed recovery of a build number I don't know, do it again by following the procedure:
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
Enjoy your out of the box device..!!
Click to expand...
Click to collapse
Does this also work in my case?
I have a rooted L-04 with TWRP and the latest b831-software. Now that I realised GPS is not working anymore I want to go back to Lollipop.
Has anyone tried it?
Thanks for your help.
Zox37 said:
Hello
I unlocked my bootloader, then installed CWM, rooted then installed unofficial EMUI 4 ROM.
But I was EMUI 3.1 before...
So my Honor 6 didn't work after that and never couldn't boot the ROM
When I try to install CWM again by Multi-Tool, flashing error says that I need to check the confirmation dialog on my device but I cant't access to my device because there is no ROM :|
I installed EMUI 4 stock recovery and now what can I do for reinstall the rom -_-
Is there any way at all?
Click to expand...
Click to collapse
how i can root my device honor 6
my model H60-L04C900B521
i unlocked my boot loader via official site
but i cant root my device
i dont have a rom on device
my device stuck on bootloop
Hey Guys,
I've tried to root my phone and while falshing the TWRP Recovery an Error occured.
Code:
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.754s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.763s
So I thought I could exit the menu by typing "fastboot reboot". Now I'm stuck in in that startup window "Your device has been unlocked and can´t be trusted" and have 3 options:
(1) Press Power Key to continue.
(2) Press Vol...
(3) ...
If I press the power button its just rebooting and everything starts from beginning and if I'm trying to recover it my phone cant connect to the wifi "Getting package info failed".
HiSuite and usb debugging aren´t working.
Did I broke my Phone or is there a way to fix it?
Sorry for my bad englich ^^.
Thank you! Musark.
Hi,
Musark said:
fastboot boot twrp.img
Click to expand...
Click to collapse
this is the wrong command for flashing a recovery. You should type: "fastboot flash recovery twrp.img".
In case you still get this error then:
Musark said:
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
It's usually because your bootloader is still or again locked.
LinuxKernel said:
Hi,
this is the wrong command for flashing a recovery. You should type: "fastboot flash recovery twrp.img".
In case you still get this error then:
It's usually because your bootloader is still or again locked.
Click to expand...
Click to collapse
I followed the tutorial "How to Root Honor 6X [100% Working]" from CyberKey (can't post links at the moment).
Everything was fine until I wanted to boot my phone.
At least i want to use my Phone.
I rode a lot about dload but I've only found tutorials where i need access to my phone.
Could someone give me a link for a tutorial?
Musark said:
I followed the tutorial "How to Root Honor 6X [100% Working]" from CyberKey (can't post links at the moment).
Everything was fine until I wanted to boot my phone.
Click to expand...
Click to collapse
It's because the tutorial you followed is wrong when it comes to flashing the twrp recovery. It seems like you flashed the recovery image to the wrong partition (boot).
If you want to install a custom rom:
1. Put your phone into fastboot mode
2. Use the command: fastboot flash recovery twrp.img
3. Flash any custom rom
If you want to get the stock rom running again:
Way1:
1. Download the right stock recovery for your phone (marshmallow recovery if you want to flash marshmallow and nougat recovery if you want to install the nougat stock rom)
2. Put your phone into fastboot mode
3. Use the command: fastboot flash recovery recovery.img
4. Download the right firmware for your phone and extract the files
5. Create the "dload" folder on your external sd card
6. Put the update.app from the extracted files into your "dload" folder
7. Power off your phone
8. Hold volume up + volume down + power button until the honor logo appears. Wait until the phone boots into stock recovery and installs the stock rom.
Way2.
1. If you know which version of stock rom you had installed, e.g. B360 you can download the same firmware version again.
2. Use huawei firmware extractor to extract recovery.img and boot.img
3. Put your phone into fastboot mode
4. Use the command: fastboot flash recovery recovery.img
5. Use the command: fastboot flash boot boot.img
6. Reboot your phone (fastboot reboot)
In general you can also install any rom via fastboot:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
fastboot flash recovery recovery.img
LinuxKernel said:
If you want to get the stock rom running again:
Way1:
1. Download the right stock recovery for your phone (marshmallow recovery if you want to flash marshmallow and nougat recovery if you want to install the nougat stock rom)
2. Put your phone into fastboot mode
3. Use the command: fastboot flash recovery recovery.img
4. Download the right firmware for your phone and extract the files
5. Create the "dload" folder on your external sd card
6. Put the update.app from the extracted files into your "dload" folder
7. Power off your phone
8. Hold volume up + volume down + power button until the honor logo appears. Wait until the phone boots into stock recovery and installs the stock rom.
Click to expand...
Click to collapse
Wow Thanks, I've only 1 question. My computer isnt noticing that my phone is connected with him via usb.
How can i access my sd card without HiSuite or usb debugging? I could also put my sd card in a diffrent phone, but i think thats not the usual way.
Musark said:
Wow Thanks, I've only 1 question. My computer isnt noticing that my phone is connected with him via usb.
How can i access my sd card without HiSuite or usb debugging? I could also put my sd card in a diffrent phone, but i think thats not the usual way.
Click to expand...
Click to collapse
If you have no running rom on your phone, then as far as I know only via TWRP or as you already mentioned by another phone.
My phone is working fine now thanks.
Musark said:
My phone is working fine now thanks.
Click to expand...
Click to collapse
Good, next time, try installing it through TWRP app (if you are rooted) it's easier
LinuxKernel said:
It's because the tutorial you followed is wrong when it comes to flashing the twrp recovery. It seems like you flashed the recovery image to the wrong partition (boot).
If you want to install a custom rom:
1. Put your phone into fastboot mode
2. Use the command: fastboot flash recovery twrp.img
3. Flash any custom rom
If you want to get the stock rom running again:
Way1:
1. Download the right stock recovery for your phone (marshmallow recovery if you want to flash marshmallow and nougat recovery if you want to install the nougat stock rom)
2. Put your phone into fastboot mode
3. Use the command: fastboot flash recovery recovery.img
4. Download the right firmware for your phone and extract the files
5. Create the "dload" folder on your external sd card
6. Put the update.app from the extracted files into your "dload" folder
7. Power off your phone
8. Hold volume up + volume down + power button until the honor logo appears. Wait until the phone boots into stock recovery and installs the stock rom.
Way2.
1. If you know which version of stock rom you had installed, e.g. B360 you can download the same firmware version again.
2. Use huawei firmware extractor to extract recovery.img and boot.img
3. Put your phone into fastboot mode
4. Use the command: fastboot flash recovery recovery.img
5. Use the command: fastboot flash boot boot.img
6. Reboot your phone (fastboot reboot)
In general you can also install any rom via fastboot:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
i tried all previous mensioned method
i got stock firm ware and some custom rom from huawei support and xda developers
i tried dload method saying system update failed
itried fastboot flash recovery twrp.img
done
but i tried adb reboot recovery saying device not found
tried fastboot reboot done
my previous version was BLN-L22C675B360
please provied me with suitable firm ware and way to flash it
or tell me atleast how to go to twrp on fastboot mode when adb reboot recovery saying device not found
Thanks in advance
rom link plz
Musark said:
My phone is working fine now thanks.
Click to expand...
Click to collapse
give me rom link please on message or how did u get access to twrp tell me
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!
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.
12S Ultra unofficial TWRP - link MEGA
Credit - UnofficialTWRP
They released TWRP under 12S Pro, but the code name is Thor which stands for 12S Ultra, and after flashing, I do confirm this is for 12S Ultra.
now they have a proper 12S Ultra section!
Download the image and rename as recovery.img for simplicity.
fastboot boot recovery.img (or full file name)
in TWRP, go to "Advanced" and "flash this twrp."
edit: the recovery image file is too large to be flashed directly via fastboot, so you need to boot first then flash using twrp!
edit2: backup and restore function may not be working properly on this version of twrp! I get boot loops everytime I do a full system backup and full restore after bricking the device, especially on the data partition. Clean installing rom then restoring data only still get boot loops. so use it with caution.
I suggest you to use 3rd party backup apps to do backups on apps and data, and stick to the flashing and other functions only for twrp.
original source unofficialtwrp.com
Nabicook said:
12S Ultra unofficial TWRP - link MEGA
Credit - UnofficialTWRP
They released TWRP under 12S Pro, but the code name is Thor which stands for 12S Ultra, and after flashing, I do confirm this is for 12S Ultra.
Download the image and rename as recovery.img for simplicity.
fastboot boot recovery.img (or full file name)
in TWRP, go to Advanced and flash this twrp.
original source unofficialtwrp.com
Click to expand...
Click to collapse
Awesome thanks. But why not Fastboot flash recovery recovery.img?
No. You must type fastboot flash boot recovey. img
dungnghien said:
No. You must type fastboot flash boot recovey. img
Click to expand...
Click to collapse
No I'm pretty sure it's:
fastboot flash recovery twrp.img
However my question was why the method outlined by @Nabicook vs this method. Is it because of the dual partition?
GodKingKnight said:
Awesome thanks. But why not Fastboot flash recovery recovery.img?
Click to expand...
Click to collapse
Because not only it is the method unofficialtwrp suggested, but also the size of the recovery img file is too large to be flashed via fastboot.
I already tried
fastboot flash recovery recovery.img
fastboot flash recovery_a recovery.img
and so on, but all failed.
only way to properly install this version of twrp is to boot first then let twrp to install itself to both a/b partitions.
Hi!
I'm following your guide...and after uploading recovery nothing happens
rebooting into recovery through ADB or just using buttons...still sends me into fastboot mode
What can I do?
joiliko said:
Hi!
I'm following your guide...and after uploading recovery nothing happens
rebooting into recovery through ADB or just using buttons...still sends me into fastboot mode
What can I do?
Click to expand...
Click to collapse
are you sure you did
fastboot boot (your recovery file name).img
it should automatically boot into twrp without touching anything from fastboot mode.
then install twrp through the advanced option in twrp
Nabicook said:
are you sure you did
fastboot boot (your recovery file name).img
Click to expand...
Click to collapse
Great many thanks! I was actually doing flash boot
Nabicook said:
then install twrp through the advanced option in twrp
Click to expand...
Click to collapse
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
joiliko said:
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
Click to expand...
Click to collapse
yeah you can try flashing stock boot img, and if that doesnt work, you can download fastboot rom and flash stock rom using flash all without wiping data(there is .bat file that says something like install without formatting).
That will fix any kind of brick issues of xiaomi device, and you just redo the twrp part.
joiliko said:
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
Click to expand...
Click to collapse
How to Extract payload.bin and get stock boot image file
To extract the payload.bin file from Android stock firmware and get stock boot image file, you should refer to the instructions given in here.
www.droidwin.com
My idea worked!
I used the method above to extract boot.img & flashed it successfully
Can someone tell me why wipe data and settings dosent work on my 12s ultra every time reboots the twrp after i press the icon... Im try at 7.5 version the same and on 7.2