Honor H60-L11 [Android 6] Successfully installed SuperSU via TWRP but failed to root - Honor 6, 6 Plus Q&A, Help & Troubleshooting

Hello,
Today I flashed TWRP recovery and successfully installed SuperSU, both the lasted version. The log in the end shows
Code:
unmounting /system and /vendor
done
updating partition details...
...done
and I press the button [Reboot system].
Although during the installation, it showed "the first reboot may take a few minutes, and loop blah blah..." But actually, there was just one reboot and no SuperSU icon in my phone. So I manually installed SuperSU app from google play. But SuperSu warned me that my phone is unrooted.
Can anyone help me with that? Now my phone remains the same, no errors. Why I can install SuperSu but cannot root my Android phone?

Related

Damn guys, please help me [huawei crr-l09]

So, lets start.
I have the mentioned Huawei Mate S, i flashed the TWRP bootloader and just wanted to root my device..
that have i done untill now:
- found a page (cant post the link cause i am new here) to root [search: "huawei-mate-s-root-twrp-recovery-v2-8-7-0/" in google and take the first page to get there (theandroidsoul .com) ]
- downloaded everything mentioned (TWRPand i got the SuperSU-File)
- first i loaded into bootloader, then made a backup of my system.
- then i installed the System again with the SuperSU.zip File
- i tried to boot the system, but it was stuck for 8 hours in the Huawei System Boot Page while i slept
- then i rebooted into the recoverymode of TWRP and restored the system again from the backup, but this time without installing the SuperSU. I could reboot but my phone wasnt rooted, so i tried again:
- this time i just installed the zip-file using the twrp-recoverymode
- didnt work
- and then i think i made a mistake, i tried to do a factory reset but after like 15 minutes i thought it would be stuck and i rebooted
- after the reboot no matter what i did there was always that problem: "E: unable to mount "/cache" "
- i tried a a couple different things and now i am at this point:
-> my android system isnt booting so its stuck in the bootpage
-> i dont have the backup (dont know where it went) anymore so i cant restore with that
-> i cant wipe the /cache cause everytime it says: "E: unable to mount "/cache" "
WHAT CAN I DO? maybe flash a custom rom?
PLEASE HELP, THANK YOU! <3
ccas
edit: phone is listed in pc so i can transfer any files, but its empty, there is only one file called "TWRP"
Flashing a custom ROM may fix it.
If not, I'd try to flash the original firmware. Huawei must have some software available that allows you to do it.

ROOT problem!

When i flashed supersu with TWRP i got problem....Twrp failed to mount system then i just wipe system and this removed app my apps without supersu so...root checker says im rooted but in systemless mode so m question is do i need to reFlash it or i have root...Game killer working btw.

Dilemma: Magisk and Xposed boot loop

Dear all,
I'm in quite a dilemma. I have an FRD-L09 with the following environment:
Oreo Firmware (FRD-L09C432B521)
Unlocked FRD and Bootloader
TWRP 3.2.1 from 7to.cn (the one which can mount /system writable) (this one: https://forum.xda-developers.com/ho...p-ish-twrp-3-2-1-honor-9-running-gsi-t3818442)
I did not go the "Fix DataEncryption" way because, to me, it's pretty convenient that nobody is able to access /data even with TWRP, so if the phone gets stolen, my data is protected
I installed Magisk 17.1 and Magisk Manager which worked perfectly fine.
Then I downloaded and installed the corresponding Xposed Module for Magisk (apparently system-less, so Xposed-Uninstaller.zip doesn't work). This resulted in a boot loop.
I'm not able to suppress Xposed loading with the usual "press a device button many times in a row".
If I uninstall Magisk (i.e. flash stock recovery.img extracted from update.app), the system boots up normally, so it's Magisk+Xposed that causes the boot loop
BUT: Now I'm unable to remove the Xposed module from /data/magisk.img because 1. of course I can't access /data from a booted system without root and 2. I can't access /data from TWRP because I want to leave it protected.
Also, the "Fix DataEncryption" option apparently wipes the /data partition which I'd really like to avoid.
With other TWRP releases, I cannot access /data even after entering my lockscreen PIN or the "default_password" as decryption password, so I'm pretty certain that the encryption key is derived by other means - I think I remember reading that it's stored somewhere in hardware, which is also why, for Custom ROMs, encryption on Honor 8 is always an issue.
So does anyone have any clue how I can either access /data from TWRP while keeping it encrypted, or delete magisk.img via any other way?
I'll be happy about any hint!
EdRoxter said:
Dear all,
I'm in quite a dilemma. I have an FRD-L09 with the following environment:
Oreo Firmware (FRD-L09C432B521)
Unlocked FRD and Bootloader
TWRP 3.2.1 from 7to.cn (the one which can mount /system writable) (this one: https://forum.xda-developers.com/ho...-ish-twrp-3-2-1-honor-9-running-gsi-t3818442)
I did not go the "Fix DataEncryption" way because, to me, it's pretty convenient that nobody is able to access /data even with TWRP, so if the phone gets stolen, my data is protected
I installed Magisk 17.1 and Magisk Manager which worked perfectly fine.
Then I downloaded and installed the corresponding Xposed Module for Magisk (apparently system-less, so Xposed-Uninstaller.zip doesn't work). This resulted in a boot loop.
I'm not able to suppress Xposed loading with the usual "press a device button many times in a row".
If I uninstall Magisk (i.e. flash stock recovery.img extracted from update.app), the system boots up normally, so it's Magisk+Xposed that causes the boot loop
BUT: Now I'm unable to remove the Xposed module from /data/magisk.img because 1. of course I can't access /data from a booted system without root and 2. I can't access /data from TWRP because I want to leave it protected.
Also, the "Fix DataEncryption" option apparently wipes the /data partition which I'd really like to avoid.
With other TWRP releases, I cannot access /data even after entering my lockscreen PIN or the "default_password" as decryption password, so I'm pretty certain that the encryption key is derived by other means - I think I remember reading that it's stored somewhere in hardware, which is also why, for Custom ROMs, encryption on Honor 8 is always an issue.
So does anyone have any clue how I can either access /data from TWRP while keeping it encrypted, or delete magisk.img via any other way?
I'll be happy about any hint!
Click to expand...
Click to collapse
Re-install EMUI 8 with eRecovery.
ThePS4Gamer said:
Re-install EMUI 8 with eRecovery.
Click to expand...
Click to collapse
Yeah, I really hoped I could do something without wiping my /data partition, but I guess I'll have to back up my data and do a factory reset and start over...
PS: eRecovery only offers EMUI 5 on the Honor 8 - EMUI 8 is only installable via HiSuite.
EdRoxter said:
Yeah, I really hoped I could do something without wiping my /data partition, but I guess I'll have to back up my data and do a factory reset and start over...
PS: eRecovery only offers EMUI 5 on the Honor 8 - EMUI 8 is only installable via HiSuite.
Click to expand...
Click to collapse
Solution is simple.
Requirement:
TWRP(which Twrp? honor view 10's. Research how to install)
Solution:
-install magisk pached boot img to ramdisk and twrp to recovery_ramdisk
-boot in Twrp
-then navigate to Advance->Terminal
-write below command:
touch /cache/.disable_magisk && chmod 0777 /cache/.disable_magisk && sync && reboot
Behind the scene: It will enable magisk core only mode, then uninstall malfunctioning modules from magisk manager and disable core only mode, reboot and mtv enjoy
spica1234 said:
touch /cache/.disable_magisk && chmod 0777 /cache/.disable_magisk && sync && reboot
Behind the scene: It will enable magisk core only mode, then uninstall malfunctioning modules from magisk manager and disable core only mode, reboot and mtv enjoy
Click to expand...
Click to collapse
Thank you so much! This was exactly was I was looking for, but googling for "disable Magisk boot" and the like didn't bring up any results other than a bunch of tutorials on how to remove Magisk modules from TWRP with uninmod, which obviously didn't work for me because I couldn't mount /data from TWRP.

Error 7 while flashing lineage-16 on redmi 3s prime

Device Information: Redmi 3S Prime - 3GB - 32GB - 6.0.1 Marshmallow
Bootloader is unlocked and phone is rooted. I used TWRP, Magisk and lazyflasher and verified with Root Checker app.
Now I am trying to install lineage-16.0-nightly-land via adb sideload and getting error as shown in the screenshot [https://imgur#com/X16jONh]. Let me know if it is not readable I will write it here.
Basically it is showing
E1001: Failed to update system image.
Updater process ended with ERROR: 7
These are the steps I have followed:
1) Unlocking bootloader this was just standard.
2) After that to root the phone I did
2.1) `fastboot flash recovery recovery.img`
2.2) `fastboot boot recovery.img`
2.3) Wiped "Wipe->Advance Wipe->Cache"
2.4) Installed "no-verity-opt-encrypt-6.1.zip" (downloaded from [https://build.nethunter#com/android-tools/no-verity-opt-encrypt/)
2.5) Got error similar to above "E1001: Failed to update system image. Updater process ended with ERROR: 7". I ignored this error and moved on to install Magisk.
2.6) Successfully Installed Magisk.
2.7) Rebooted the phone. Installed Root Checker from playstore and confirmed that the phone is rooted.
3) Flashing lineageos
3.1) Wiped "Wipe->Advance Wipe->Cache, Dalvik Cache, System, Data"
3.2) Tried installing lineageos and got error similar to above "E1001: Failed to update system image. Updater process ended with ERROR: 7"
3.3) I then tried the adb sideload method. First I checked if my device is being listed by doing `adb devices` on terminal. It was being listed.
3.4) Then I formatted the data as instructed here [https://wiki.lineageos#org/devices/land/install#installing-lineageos-from-recovery]
3.5) “Advanced”, “ADB Sideload”, then swiped to begin sideload.
3.6) Did `adb sideload lineage-16.0-20200715-nightly-land-signed.zip` and got the error as shown on the image link [https://imgur#com/X16jONh]
What should I do to resolve this error? Please Help.
Please let me know if any other detail is required.
Since I am new user, I am not allowed to post links. As a workaround I have replace .com and .org with #com and #org. Please correct them. Sorry for the trouble.

Problem rooting refurbished google Pixel 1 with magisk (failed to mount system/root)

Hi,
I just got a second hand Google Pixel 1 and I ran into some trouble trying to install magisk on it : I keep getting those two error messages in TWRP when flashing the TWRP.zip and magisk.zip :
"Failed to mount system/root (invalid argument)"
"failed to mount vendor (invalid argument)"
The two installations are still considered successful by TWRP but rebooting after flashing the magisk.zip keeps the phone in bootloop.
Any idea how I could fix this please ?
Information on the device and software used :
- android 10 installed on the phone when i got it ;
- bootloader unlocked, usb debugging on ;
- Flashing TWRP with "twrp-installer-3.4.0-0-sailfish" preloaded in the phone and the corresponding img ;
- magisk manager installed and using magisk 20.4 zip preloaded in the phone for flashing ;
- all commands made in cmd.exe from windows 10 computer ;
- adb and google drivers installation all ok.
please ask if I didn't give enough information.
Thanks in advance !
dantafas said:
Hi,
I just got a second hand Google Pixel 1 and I ran into some trouble trying to install magisk on it : I keep getting those two error messages in TWRP when flashing the TWRP.zip and magisk.zip :
"Failed to mount system/root (invalid argument)"
"failed to mount vendor (invalid argument)"
The two installations are still considered successful by TWRP but rebooting after flashing the magisk.zip keeps the phone in bootloop.
Any idea how I could fix this please ?
Information on the device and software used :
- android 10 installed on the phone when i got it ;
- bootloader unlocked, usb debugging on ;
- Flashing TWRP with "twrp-installer-3.4.0-0-sailfish" preloaded in the phone and the corresponding img ;
- magisk manager installed and using magisk 20.4 zip preloaded in the phone for flashing ;
- all commands made in cmd.exe from windows 10 computer ;
- adb and google drivers installation all ok.
please ask if I didn't give enough information.
Thanks in advance !
Click to expand...
Click to collapse
Guide
Do #9 in the guide using the Canary Magisk Manager.
Ok thanks I'll try that !

Categories

Resources