TWRP Problem with installing Magisk and GSuit and startin sideload - Nexus 6P Q&A, Help & Troubleshooting

Hi guys, I have a Nexus 6P, and I'm stuck with a problem.
I have twrp 3.40-0 recovery and I from it when I try to start the ADB sideload it doesen't start and in the top menu there is a red text with "Failed" in the console there isn't any error. I've tried re-flashing the twrp recovery and even using the version before but the sideload won't start.
The other problem is: I uploaded to my phone a Havoc ROM, Gsuit and Magisk, so from the recovery I install the Havoc ROM and then I try to install the Gsuit and Magisk but it gives me updater error (Error is: "Updater process ended with ERROR: 1
Error insaling zip file '/data/media..") .
I've tried reloading the file onto the phone (enabling the debug mode in the new os) but again when I try to install them from the recovery the same error shows up again.
What can I do? (Magisk worked because before flashing the new ROM I have installed it and it worked)
Thanks for your help

vondetaconadis said:
Hi guys, I have a Nexus 6P, and I'm stuck with a problem.
I have twrp 3.40-0 recovery and I from it when I try to start the ADB sideload it doesen't start and in the top menu there is a red text with "Failed" in the console there isn't any error. I've tried re-flashing the twrp recovery and even using the version before but the sideload won't start.
The other problem is: I uploaded to my phone a Havoc ROM, Gsuit and Magisk, so from the recovery I install the Havoc ROM and then I try to install the Gsuit and Magisk but it gives me updater error (Error is: "Updater process ended with ERROR: 1
Error insaling zip file '/data/media..") .
I've tried reloading the file onto the phone (enabling the debug mode in the new os) but again when I try to install them from the recovery the same error shows up again.
What can I do? (Magisk worked because before flashing the new ROM I have installed it and it worked)
Thanks for your help
Click to expand...
Click to collapse
hmm reflash bootloader, radio and vendor then re flash twrp as well wipe your data Wipe> Format data type Yes
Reboot to recovery then follow these steps:
Flash rom and gapps
Wipe > Format data > Yes
Reboot recovery
Flash magisk
Reboot system
Edit: Mine method doesn't need side loading, also u can check your drivers.
Sent from my angler using XDA Labs

Ata Ur Rehman said:
hmm reflash bootloader, radio and vendor then re flash twrp as well wipe your data Wipe> Format data type Yes
Reboot to recovery then follow these steps:
Flash rom and gapps
Wipe > Format data > Yes
Reboot recovery
Flash magisk
Reboot system
Edit: Mine method doesn't need side loading, also u can check your drivers.
Sent from my angler using XDA Labs
Click to expand...
Click to collapse
After I flash Havoc and Gsuit, and format data, when I try to flash Magisk it gives me updater error: 1 (even if I try to delete magisk from file manager of twrp)
EDIT: I was able to flash Magisk after checking system in Mount

Related

From Philz to Flyme (official firmware) MX4

Good evening everyone.
I write because I have a problem with the installation of the CM on my meizu MX4.
I ran perfectly the procedure of unlocking the bootloader, and once unlocked, I flashed the recovery Philz. Later I tried to flash the CM with adb, but in at end it always says "Installation Aborted". I tried with the patched recovery and with cofface, but I just can not flash it.
I then tried to do a wipe cache but no with any recovery that I flashed always appears to me:
"E: Can not mount / cache / recovery / command
E: Can not mount / cache / recovery / log
E: Can not open / cache / recovery / log
E: Can not mount / cache / recovery / last_log
E: Can not open / cache / recovery / last_log "
I read here http://forum.xda-developers.com/meizu-mx/general/tutorial-bootloader-unlocking-mx4-m1-t3201715 that I could flash the patched rom deleting the file uboot.img and preloader.bin but I can not find anywhere the second file, and also I'm afraid to brick the phone ... someone has already done it?
Tell me that at least in the future I will be able to install the CM. Loved and hated Flyme.
Sorry for the English and thanks in advance for your reply.
Why you don't install CM from the recovery?
Sent from my D6603 using Tapatalk
I has this problem also when try to wipe cache. I fix cache mount with "wipe for new rom" option in wipe menu on philz recovery.
After that install cyanogen .zip with recovery.
Now i'm back to flyme but i flash patched flyme4.5.6i-twrp.zip found on 4pda forum, with twrp recovery for mx4.
Here is link for tutorial *4pda.ru/forum/index.php?showtopic=689760&st=780#entry43612111*
My MX4 is now on Flyme international version (original was A firmware) and i still have unlocked bootloader and custom recovery.
Everything works fine without any bug.
artlov I installed the recovery and then I did:
1) install zip
2) install zip from sideload
3) MX4 connect to pc
4) open CDM and write "adb devices" enter
5) "adb sideload cm12 ect * enter *
6) sull'mx4 appeared the word "installation aborted" after loading on pc
Now i have flyme 4.2.8.2A with philz recovery.
mmdag82 i don't find on philz the option "wipe for new rom"
"Clean to Install a New Rom" is exactly name of option under Wipe menu
And then i can try to flash CM? By terminal or with file zip on mx4's memory?
Thank you for your answers!
With zip file on mx4 memory
did you tried factory reset because you must do that befor adb sideload and i woildn't do Clean to Install a New Rom because it will delete everything about current system
Yeeah! CM installed! Thanks a lot guys!
MX4 not read sim card with CM...
federicolucchesi said:
artlov I installed the recovery and then I did:
1) install zip
2) install zip from sideload
3) MX4 connect to pc
4) open CDM and write "adb devices" enter
5) "adb sideload cm12 ect * enter *
6) sull'mx4 appeared the word "installation aborted" after loading on pc
Now i have flyme 4.2.8.2A with philz recovery.
mmdag82 i don't find on philz the option "wipe for new rom"
Click to expand...
Click to collapse
There is a solution. Try to reflash the patched recovery.
Now reflash 4.2.1.2 with clean.
Reboot, and reroot, reinstall flashify and terminal.
Do again the tuto step by step.
Try and tell me
Edit : Sorry, i didn't saw you have done ^^
I've done! Not reads SIM but i think is problem of card, cause i tried other SIM that weren't chopped from old SIM card and them run perfectly!
Hey,
hope somebody can help me.
I wanted to install flymeos on my arale until the cm-version is usable for me.
I am only able to install version 4.0.4 i or a but i cannot upgrade nor directly flash a version later than that...
I tried several recoveries (philz, cofface, twrp) and several versions (4.2.8.2i/a, 4.5.6i). Any ideas?
-----------------
EDIT: Recovery logs always tell me that there is no space on /custom left. Do i have to reformat my arale with a android scatter? I installed 4.0.4 and ran fastboot -w. Thought this would be sufficient. /custom is only 4.8M big...

[A2017G] Cant install superSu through twrp

I installed the twrp 3.0.2.2 and after installed a kernel which made the phone stuck on zte logo.
I tried to flash to the stock files using this guide:
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but when i try to install the superSu the twrp stuck after extracing files, then the phone just shuts down.
what can I do?
Shakedbuk said:
I installed the twrp 3.0.2.2 and after installed a kernel which made the phone stuck on zte logo.
I tried to flash to the stock files using this guide:
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but when i try to install the superSu the twrp stuck after extracing files, then the phone just shuts down.
what can I do?
Click to expand...
Click to collapse
Update your twrp, there's no need to use that old version... my phone reboots when it wants when it has opd twrp versions
Download twrp 3.1.1-0
Put it on your phone, maybe via adb or through mtp if you have it
Go to Install -> hit the button on the right that says 'Install image'
Find the TWRP.img and install it, it will prompt you where to install it, put 'recovery'
Followed you instructions, but now i cant get into TWRP or the OS ):
Tried to flash it with axon7tool on pc, but got the same result, but when I tried to flash the 3.0.2. again, it worked.
Shakedbuk said:
Followed you instructions, but now i cant get into TWRP or the OS ):
Tried to flash it with axon7tool on pc, but got the same result, but when I tried to flash the 3.0.2. again, it worked.
Click to expand...
Click to collapse
Don't use axon7tool for this... you already have TWRP, the only thing you have to use axon7tool for is to install twrp when you have the stock recovery. after you have twrp on the phone just try not to use the PC except for maybe miflash
I tried both of this options.
Flashing new version of twrp through the old twrp resulted in black screen when i try to get to recovery.
So I flashed the old twrp from the pc, tried to flash the new one using the same method but it the same as i flashed it through the old twrp. (which mean that when i get to the recovery i get black screen)
ATM the situation is the same, system wont boot stuck on zte logo, twrp is 3.0.2.2 (there is another method to flash newer twrp?)
There is another option?
After wiping system in twrp i was able to install supersu, which means i completed this guide
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but still stuck on zte logo after i reboot , any help?
Shakedbuk said:
After wiping system in twrp i was able to install supersu, which means i completed this guide
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but still stuck on zte logo after i reboot , any help?
Click to expand...
Click to collapse
Wait, what did you do? Did you install everything again after wiping system?
Ya, afte i wiped the system it allowed me to install the supersu without interrupts, but it did not helped.
Anyway i manged to install purefusion os, system booted up, after that the new twrp updated successfully.
Shakedbuk said:
Ya, afte i wiped the system it allowed me to install the supersu without interrupts, but it did not helped.
Anyway i manged to install purefusion os, system booted up, after that the new twrp updated successfully.
Click to expand...
Click to collapse
You installed SuperSU without a system, and the phone did not boot up? Amirite?
what i did was wipe system dalvik cache, cache, after that install bootstack and the system files, and after that the supersu.
before i wiped the system, when i tried to install the supersu the twrp collapsed, after that it installed it but did not helped to make the system boot.

Installation failed while doing system update

Hi,
I have OnePlus 5, which previously I installed TWRP,
I tried to install the last update from OnePlus through TWRP (Recovery ==> Install option) but were given error 7
I gave up and installed the image from Oxygen Recovery and as of now no more TWRP
But when I try to update using (System Update option) on the mobile itself, it starts to download, then reboot to recovery, starts for a while then gives an error message as installation failed
Any idea what I should do
I have no issue to wipe the device
I have the same problem, can't figure it out either, really need help.
Will let you know if I figure something out.
I believe this has been posted in the wrong forum.
Please, next time post this is the correct. Ill have a mod move it. It belongs in Questions & Answers,
As for your problem. Which exact recovery are you using?
Give this twrp a try
https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
malibusa said:
Hi,
I have OnePlus 5, which previously I installed TWRP,
I tried to install the last update from OnePlus through TWRP (Recovery ==> Install option) but were given error 7
I gave up and installed the image from Oxygen Recovery and as of now no more TWRP
But when I try to update using (System Update option) on the mobile itself, it starts to download, then reboot to recovery, starts for a while then gives an error message as installation failed
Any idea what I should do
I have no issue to wipe the device
Click to expand...
Click to collapse
After rebooting to recovery, click Wipe, then advanced Wipe, check Dalvik/Art Cache and Cache, swipe to wipe ........then go back and Install the Rom, it should not give that error.

Did Factory Reset in Custom Rom now i have a TWRP Bootloop. (Mediatek)

Hello Guys it´s me again. (i know im annoying )
Well, i did a Factory Reset in dotOS and it Rebooted into TWRP.
However, Normally a Phone would then Perform the Action in the Recovery but in this Case it did not do it. So i Reflashed the Rom.
After that it Rebooted into TWRP again. I Tried to Access the Bootloader with Vol Down + Power. That also Booted into TWRP. After that i Selected Bootloader in the TWRP Reboot Options. That Booted the Phone into the Mode where i Flashed the Recovery but it did not Give me the Options like META MODE, FACTORY MODE etc, when i tapped the Volume Buttons. Only a Black Background with White text Saying :
> FASTBOOT mode...
> device unlocked
I Tried to Restore my Stock TWRP Backup but that did not Solve the Issue. I also tried to Reflash dotOS but same issue.
What else Can i do to get this fixed ? I never had a Problem Like this on any Sony or Samsung Device i tinkered with. Thats why im asking that much.
@Marc_Xperia Do not forget to install no-verity-opt-encrypt zip file or simple disable *system verifier* in kernel ramdisk.
TheHitMan said:
@Marc_Xperia Do not forget to install no-verity-opt-encrypt zip file or simple disable *system verifier* in kernel ramdisk.
Click to expand...
Click to collapse
I Tried that but still no luck. Might Revert to stock and try it that why. If i can find the VCOM Driver...
Marc_Xperia said:
Hello Guys it´s me again. (i know im annoying )
Well, i did a Factory Reset in dotOS and it Rebooted into TWRP.
However, Normally a Phone would then Perform the Action in the Recovery but in this Case it did not do it. So i Reflashed the Rom.
After that it Rebooted into TWRP again. I Tried to Access the Bootloader with Vol Down + Power. That also Booted into TWRP. After that i Selected Bootloader in the TWRP Reboot Options. That Booted the Phone into the Mode where i Flashed the Recovery but it did not Give me the Options like META MODE, FACTORY MODE etc, when i tapped the Volume Buttons. Only a Black Background with White text Saying :
> FASTBOOT mode...
> device unlocked
I Tried to Restore my Stock TWRP Backup but that did not Solve the Issue. I also tried to Reflash dotOS but same issue.
What else Can i do to get this fixed ? I never had a Problem Like this on any Sony or Samsung Device i tinkered with. Thats why im asking that much.
Click to expand...
Click to collapse
It's very simple
-boot into recovery
-wipe
-advanced wipe
-clear / format cache & dalvik
-reboot _choose reboot recovery
-select mtp file transfer mode in twrp
-push LATEST* magisk zip
-push clean copy of dotOs
-then do FULL WIPE (all) but not your sd or internal sd/data
-install first dotOs zip
-install magisk zip
-wipe cache
-reboot
* If you fail check what is selected under the mount section & report back
If problem persists flash an older version of recovery using SPflashtools and then older version of dotOs with magisk
_do full wipe first
#some new recoveries had errors so make sure you are running ABSOLUTE latest or OLDEST version of twrp
# I haven't tried the last or latest version of dotOs yes ( older versions worked 100%)
KevMetal said:
It's very simple
-boot into recovery
-wipe
-advanced wipe
-clear / format cache & dalvik
-reboot _choose reboot recovery
-select mtp file transfer mode in twrp
-push LATEST* magisk zip
-push clean copy of dotOs
-then do FULL WIPE (all) but not your sd or internal sd/data
-install first dotOs zip
-install magisk zip
-wipe cache
-reboot
* If you fail check what is selected under the mount section & report back
If problem persists flash an older version of recovery using SPflashtools and then older version of dotOs with magisk
_do full wipe first
#some new recoveries had errors so make sure you are running ABSOLUTE latest or OLDEST version of twrp
# I haven't tried the last or latest version of dotOs yes ( older versions worked 100%)
Click to expand...
Click to collapse
Do you have Some Links on the ABSOULTE latest or OLDEST Version of TWRP ? I dont trust the one i Have anymore.
I Used this one : https://androidfilehost.com/?fid=890129502657592740
Marc_Xperia said:
Do you have Some Links on the ABSOULTE latest or OLDEST Version of TWRP ? I dont trust the one i Have anymore.
I Used this one : https://androidfilehost.com/?fid=890129502657592740
Click to expand...
Click to collapse
Download this tool .
https://www.androidfilehost.com/?fid=817550096634801704
Extract the .rar
Inside the folder there is recovery by XNlogos with zero errors
This tool can also inject recovery using fastboot or unlock bootloader in automated manner & flash custom boot( with verity encrypt DISABLED)

Always boot in recovery mode after an update

Hi,
I was updating my OP6T to the new version (Magisk + Xxx NoLimits), but after the reboot post-update the device started to reboot to recovery after it booted. So I've tried to delete Magisk but the problem was still present, so I've decided to download the latest Oxygen ROM from the OnePlus and flash it from TWRP, but after flashing, the device started to always boot to recovery (before the OnePlus boot animation).
At least i tried to restore a nandroid backup of 1 month ago (System, Boot and Data), but still the device after the restore still boot to recovery before the boot animation.
I've only tried the system reboot (I've not tried to force boot another slot).
Do you have a solution to try before formatting the internal storage?
Thanks
Edit: After unistalling magisk and reflashing it again, now the device boots again, but immediately after (when the lock screen appear) the device reboot automatically to recovery again
Try this:
- in twrp , dirty flash the rom you are using (Oxygen os)
- factory reset
- flash twrp (the latest the better)
- flash Magisk 19.1
Reboot to system.
If this not working, Format data will work.
null0seven said:
Try this:
- in twrp , dirty flash the rom you are using (Oxygen os)
- factory reset
- flash twrp (the latest the better)
- flash Magisk 19.1
Reboot to system.
If this not working, Format data will work.
Click to expand...
Click to collapse
Factory reset from TWRP?
yes
null0seven said:
yes
Click to expand...
Click to collapse
So, do you mean the classic Wipe data, cache and dalvik?
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
TWRP Users
1. Boot into TWRP and Flash the Latest Magisk Uninstaller
2. Flash the latest Full Oxygen OS Zip
3. Flash the TWRP installer Zip
4. Reboot to RECOVERY to make sure TWRP stays and continue to root.
5. Flash the Latest Magisk to maintain root
6. Reboot System and Enjoy the latest firmware without any data loss
Click to expand...
Click to collapse
I am guessing you skipped the first step...
Try this:
Flash the OTA zip
Reboot (you will be unrooted and with stock recovery)
Boot to TWRP through ADB
Flash magisk unistaller
Reboot
Boot to TWRP through ADB
Flash OTA zip
Flash TWRP
Reboot to TWRP
Flash magisk
Galeanatur said:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
I am guessing you skipped the first step...
Try this:
Flash the OTA zip
Reboot (you will be unrooted and with stock recovery)
Boot to TWRP through ADB
Flash magisk unistaller
Reboot
Boot to TWRP through ADB
Flash OTA zip
Flash TWRP
Reboot to TWRP
Flash magisk
Click to expand...
Click to collapse
I don't have the OTA but the full rom, isn't simplier to update with the full ROM?
I think I'm going to try the null0seven's solution
null0seven said:
Try this:
- in twrp , dirty flash the rom you are using (Oxygen os)
- factory reset
- flash twrp (the latest the better)
- flash Magisk 19.1
Reboot to system.
If this not working, Format data will work.
Click to expand...
Click to collapse
Ok, I've done this and actually is even worse, the device started to boot in recovery again and TWRP doesn't recognize that the internal storage is crypted, so i can't even access the internal storage (it shows only strange folders), so, now I can't flash the nandroid backup anymore.
I also mean FULL rom .zip.
Format data in twrp or in Fastboot. Or use MSM tool .
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
all of them will wipe ALL in youre phone, but it will work.
null0seven said:
I also mean FULL rom .zip.
Format data in twrp or in Fastboot. Or use MSM tool .
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
all of them will wipe ALL in youre phone, but it will work.
Click to expand...
Click to collapse
So I've to Full wipe and then adb sideload the ROM? Because at the current state I can't even boot the device, it always starts in TWRP
Edit: I've also tried the blue_spark's version but nothing changed, TWRP can't recognize the encrypted storage
you can try this first.
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
fuji97 said:
Hi,
I was updating my OP6T to the new version (Magisk + Xxx NoLimits), but after the reboot post-update the device started to reboot to recovery after it booted. So I've tried to delete Magisk but the problem was still present, so I've decided to download the latest Oxygen ROM from the OnePlus and flash it from TWRP, but after flashing, the device started to always boot to recovery (before the OnePlus boot animation).
At least i tried to restore a nandroid backup of 1 month ago (System, Boot and Data), but still the device after the restore still boot to recovery before the boot animation.
I've only tried the system reboot (I've not tried to force boot another slot).
Do you have a solution to try before formatting the internal storage?
Thanks
Edit: After unistalling magisk and reflashing it again, now the device boots again, but immediately after (when the lock screen appear) the device reboot automatically to recovery again
Click to expand...
Click to collapse
When you're saying you're flashing the full ROM after wiping, are you meaning the xxx no limit? If so this isn't an os rom it's just a magisk module rom that's an add on to oxygen os. You need to wipe and flash the latest oxygen os rom, stable or beta which ever you're using, then flash TWRP, flash your os again on the other slot, flash TWRP, flash magisk, if your system boots fine then flash the xxx no limits rom in twrp.
ebproject said:
When you're saying you're flashing the full ROM after wiping, are you meaning the xxx no limit? If so this isn't an os rom it's just a magisk module rom that's an add on to oxygen os. You need to wipe and flash the latest oxygen os rom, stable or beta which ever you're using, then flash TWRP, flash your os again on the other slot, flash TWRP, flash magisk, if your system boots fine then flash the xxx no limits rom in twrp.
Click to expand...
Click to collapse
No, I flashed the full ROM downloaded from the OnePlus server
Have you tried formatting data?
Cablespider said:
Format data.
Click to expand...
Click to collapse
So, full format data and flash rom + TWRP + Magisk?
fuji97 said:
No, I flashed the full ROM downloaded from the OnePlus server
Click to expand...
Click to collapse
You're best bet is to use the MSM tool
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Ok, I've decided to use MSM to recover the device, I've lost the internal storage, but at least the device is working again.
Thank you to everyone who helped me in this thread
fuji97 said:
Ok, I've decided to use MSM to recover the device, I've lost the internal storage, but at least the device is working again.
Thank you to everyone who helped me in this thread
Click to expand...
Click to collapse
Maybe it was a Magisk module that caused it. I removed pixel module from Magisk and it done the same to me.

Categories

Resources