Related
I cannot root with magisk without losing data and wifi. Tried everything. Any advice? Using phhsuperuser.
jacksummers said:
I cannot root with magisk without losing data and wifi. Tried everything. Any advice? Using phhsuperuser.
Click to expand...
Click to collapse
Did you try making the ROM permissive?
jacksummers said:
I cannot root with magisk without losing data and wifi. Tried everything. Any advice? Using phhsuperuser.
Click to expand...
Click to collapse
hello, have you tried to go via BTS P off 2 (link : https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681), I tried before since P beta 2 the wifi does not work, the everything works I'm the benzo in case you know how to activate the finger print I'm interested thank you
chris_stan said:
hello, have you tried to go via BTS P off 2 (link : https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681), I tried before since P beta 2 the wifi does not work, the everything works I'm the benzo in case you know how to activate the finger print I'm interested thank you
Click to expand...
Click to collapse
I had everything working fine with benzo.fingerprint too. Make sure u have your boot.img matching the vendor img as well. And everything the same on both slots. System.img too
jacksummers said:
I had everything working fine with benzo.fingerprint too. Make sure u have your boot.img matching the vendor img as well. And everything the same on both slots. System.img too
Click to expand...
Click to collapse
Edit. U cant have root with magisk. Only root that works and still gives u working data and wifi is phhsuperuser
jacksummers said:
I had everything working fine with benzo.fingerprint too. Make sure u have your boot.img matching the vendor img as well. And everything the same on both slots. System.img too
Click to expand...
Click to collapse
Good evening and thanks for the explanations
Here is how I proceeded:
1 / BTS to stock with mounting identical A and B partitions
2 / boot on one of the partitions then settings with activation of adb in the options developers
3 / reboot on bootloader (vol- + power)
4 / fastboot -w
5 / fastboot erase system
6 / fastboot flash -u system benzo2.img
(apply on partition B)
it does not change that system partition on partition B?
7 / fastboot reboot
8 / activation of wifi and reboot on bootloader
from here I have some ****
9 / fastboot flash boot twrp-sep.img (to avoid touch problems from what I read) on the partition B
10 / reboot on recovery
11 / flash boot and boot replacement on B
12 / flash magisk 17.1 on B
13 / fastboot reboot
14 / install Universal SafetyNetFix module
Here is the question from step 13, it switches the partition B complete on A and starts on this one or not
You can see my great non-mastery of partition systems A / B
So I do not have the proper vendor
thanks for the help in advance
on the screenshot it looks good though
Disclaimer :
YOU are choosing to make these modifications
and YOU are the only one responsible for any damages done to your device
==== Notes/Prerequisets/Links ====
* you should have already unlocked your bootloader (if not then start the process as soon as possible because it's going to take a while).
* backup your stuff, make sure you have sufficient charge just in case anything went wrong.
* download the unoffical TWRP port from Here (get the latest version)
* get the latest magisk from Here
* install device usb drivers
* set up fastboot properly Method A, Method B (using chocolaty)
- - - - - - - - - - - -
instructions :
1- shutdown your device completely.
2- enter fastboot mode by pressing and holding the Vol Down + Power Button button until you see xiaomi's mi bunny with a blue "fastboot" text underneath it.
3- connect your device to your pc via usb cable.
4- on your pc check if you have fastboot configured properly and your device recognized by typing:
Code:
fastboot devices
if it's detected then you're good to proceed to the next step.
5- flash the twrp recovery image by using the usual fastboot commands.
Code:
fastboot flash recovery recovery.img
in our case it should look something like:
Code:
fastboot flash recovery recovery-TWRP-3.3.0-0517-XIAOMI8LITE-CN-wzsx150.img
6- unplug usb cable and hold the Vol up + Power Button (don't let go of the buttons untill the devices vibrates) and let it boot to the twrp recovery you just installed.
7- if you rebooted successfully, you should be at TWRP splash screen, if greeted with a slider slide it and continue.
8- in the main menu of TWRP, go to "Install" choose the magisk zip file you downloaded and flash it, when done reboot the device.
9- congratulations friend, you're now rooted and have TWRP as your recovery Happy Flashing :highfive:
- - - - - - - - - - - -
Optional : install Orange Fox Recovery from Here (Supports Encryption and MIUI OTA updates).
- - - - - - - - - - - -
2020-02-25 Last upated and working on MIUI Global Stable 11.0.8 Pie
just in case
Is it possible to just accesss the TWRP to edit build.prop enabling camera2 Api?
If I remember is something about:
fastboot boot twrp.img
and then:
setprop persist.camera.HAL3.enabled 1
Without the need of root the device.
Thanks for the guide!
antonioli84 said:
Is it possible to just accesss the TWRP to edit build.prop enabling camera2 Api?
If I remember is something about:
fastboot boot twrp.img
and then:
setprop persist.camera.HAL3.enabled 1
Without the need of root the device.
Thanks for the guide!
Click to expand...
Click to collapse
Sorry for the late reply
No problem
+
I'm not really sure if you could do it with TWRP's built in file manager without root
You could try
I've seen people do it with adb but haven't had the chance to try it yet
take a look here : https://www.google.iq/amp/s/amp.red...gswg/camera2_api_without_root/#ampf=undefined
And here (this has some very useful info)
https://www.google.iq/amp/s/forum.x...o/guide-enable-camera2-api-root-t3690366/amp/
malek_anas_97 said:
Sorry for the late reply
No problem
+
I'm not really sure if you could do it with TWRP's built in file manager without root
You could try
I've seen people do it with adb but haven't had the chance to try it yet
take a look here : https://www.google.iq/amp/s/amp.red...gswg/camera2_api_without_root/#ampf=undefined
And here (this has some very useful info)
https://www.google.iq/amp/s/forum.x...o/guide-enable-camera2-api-root-t3690366/amp/
Click to expand...
Click to collapse
Thank you for the reply. I've done it in Mi A1 but I don't know if it's the same procedure because of the MIUI. One of the links says that we have to change something in kernel to do it.
It would be good expert people try it to see what method works. It's sad that the Mi 8 Lite doesn't have a proper forum until now.
antonioli84 said:
Thank you for the reply. I've done it in Mi A1 but I don't know if it's the same procedure because of the MIUI. One of the links says that we have to change something in kernel to do it.
It would be good expert people try it to see what method works. It's sad that the Mi 8 Lite doesn't have a proper forum until now.
Click to expand...
Click to collapse
i enabled it in stock miui by adding "persist.camera.HAL3.enabled=1" to my build prop and then rebooting
malek_anas_97 said:
i enabled it in stock miui by adding "persist.camera.HAL3.enabled=1" to my build prop and then rebooting
Click to expand...
Click to collapse
Thanks for the reply.
What method did you use to change build.prop?
Can't find a similar guide for the Mi 8, is it the same process as for the lite ?
antonioli84 said:
Thanks for the reply.
What method did you use to change build.prop?
Click to expand...
Click to collapse
i'm rooted with magisk
with a file manager, i use this one https://play.google.com/store/apps/details?id=nextapp.fx&hl=en
+
this addon https://play.google.com/store/apps/details?id=nextapp.fx.rr
the file is in /system/build.prop
webvan said:
Can't find a similar guide for the Mi 8, is it the same process as for the lite ?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=YI2CtIIPVaI
malek_anas_97 said:
i'm rooted with magisk
with a file manager, i use this one https://play.google.com/store/apps/details?id=nextapp.fx&hl=en
+
this addon https://play.google.com/store/apps/details?id=nextapp.fx.rr
the file is in /system/build.prop
Click to expand...
Click to collapse
Thank you man. I would like to know if anyone can do the trick without root. I've bought a Mi 8 Lite for my wife and it would be nice to her receive the updates from Xiaomi and use the GCam the same way she receives in Mi A1.
malek_anas_97 said:
7- if you rebooted successfully, you should be at TWRP splash screen
you will be greeted with a slider slide it and continue
Click to expand...
Click to collapse
Hi Malek,
When you first boot to TWRP, were you asked for the decryption password? If yes, did you just format data to skip this? I was asked for the password and my screen PIN did not work. Just wondering if there is no other choice that to format data.
Official Xiaomi Mi 8 Lite (Platina) telegram group 24/7 support and latest ROM news posted here first!
Rules :
1 - English only.
2 - Be polite.
3 - Don't spam.
Gp Link : https://t.me/joinchat/DXcdlA0r5XYI-ooJlO8IlQ
Please Join
chan200606 said:
Hi Malek,
When you first boot to TWRP, were you asked for the decryption password? If yes, did you just format data to skip this? I was asked for the password and my screen PIN did not work. Just wondering if there is no other choice that to format data.
Click to expand...
Click to collapse
to this point i don't really understand how encryption works on this device
it's on by default i guess
so what i finally did the other day to be kinda sure of what's happening
i flashed stock rom in Mi Flash with the clean all option checked
i set up the phone for the first time without setting any fingerprint or security or anything
after that i flashed twrp
from twrp i flashed dm verity and encryption disable
get it from here https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
(make aure to read the first post)
then formatted data
after that the booted up and i set it up normally
and then booted to twrp again to flash latest magisk
now when i check if my device is encrypted using this adb command "adb shell getprop ro.crypto.state"
i get "unencrypted"
so i guess it works? i don't know lol
malek_anas_97 said:
i flashed stock rom in Mi Flash with the clean all option checked
i set up the phone for the first time without setting any fingerprint or security or anything
after that i flashed twrp
from twrp i flashed dm verity and encryption disable
Click to expand...
Click to collapse
It looks like your phone was not encrypted (or was encrypted with MIUI's default password) when you flashed TWRP, as you had clean flashed stock then set up without setting security. That you could start TWRP to flash "dm versity and encryption disable", without being asked to input a password first, shows that TWRP was able to handle the default encryption (or no encryption) of the clean MIUI install.
In my case I already have a screen PIN set up on my phone before trying to install TWRP, and this version of TWRP can't handle it. Another difference is that I have not actually flashed TWRP onto the phone but have merely booted to TWRP via fastboot. I wouldn't have thought that this would affect TWRP's ability to decrypt the DATA partition though.
In hindsight I should have just done the minimum setup after the phone was wiped by the bootloader unlocking process before installing TWRP. I guess that unless there is another version of TWRP out that can handle the screen PIN encryption, my only option is to wipe clean the phone so that I can repeat what you did. However, now that I have reinstalled everything on the phone, I am a bit reluctant to do this just to get root. I think I will wait until there is an AOSP ROM available and do the wipe/format at the time of switching. Hopefully I don't have to wait too long!
chan200606 said:
In my case I already have a screen PIN set up on my phone before trying to install TWRP, and this version of TWRP can't handle it. Another difference is that I have not actually flashed TWRP onto the phone but have merely booted to TWRP via fastboot. I wouldn't have thought that this would affect TWRP's ability to decrypt the DATA partition though.
Click to expand...
Click to collapse
An update: I've now got over this encryption thing. It is indeed the screen PIN that was causing me problems. While I had tried removing the PIN and all fingerprints last time, I had powered down the phone immediately after removing the PIN and booted into fastboot mode. Today I thought I better try it one more time: after removing the PIN, reboot the phone to system first before powering it down and restarting in fastboot mode. This cycles the phone system at least once without the PIN so hopefully any traces of the PIN would really be wiped. And indeed it works - the booted TWRP (i.e. not flashed to phone) has no problems reading my phone and I could install Magisk.
So I now have stock recovery + Magisk on my Mi8 Lite, which is the minimum I wished to do to it. Maybe at a later date I would flash TWRP onto the phone as well.
i cant unlock my mi 8 lite, say user portrait scores too low or black, i activate all need, oem, usb, sync device. no work, any help?
Everything is ok for global rom.
For the language twrp asked directly at first launch for it and you don't need anymore magisk, you can install it directly from twrp. ( advance/install root ) it'll install the version 17.1 and you can update it from the app on the phone.
No problem for reboot into twrp ( volume up + power) even with fingerprint.
kax001 said:
i cant unlock my mi 8 lite, say user portrait scores too low or black, i activate all need, oem, usb, sync device. no work, any help?
Click to expand...
Click to collapse
i really have no idea why this is happening to you
i searched online and it seems like you're not the only one having this
vonclutch said:
Everything is ok for global rom.
For the language twrp asked directly at first launch for it and you don't need anymore magisk, you can install it directly from twrp. ( advance/install root ) it'll install the version 17.1 and you can update it from the app on the phone.
No problem for reboot into twrp ( volume up + power) even with fingerprint.
Click to expand...
Click to collapse
yeah i know there's no problem in turning the phone off then rebooting manually with the buttons
but i was talking about using "fastboot reboot recovery" command to reboot to recovery from fastboot directly
anyways glad everything worked for you friend : )
Hi All
Note: This procedure is for Windows PC only.
I can see there is a similar thread to help on rooting your device.
I created this thread it make it more easier and focussed just on rooting your device rather with additional information.
This menthod is to root your device without TWRP.
There is a detailed guide by @Freak07 which you can find here.
Prerequisite:
1. Your device bootloader is unlocked
2. You have enabled your Developer Options and enabled USB debugging (Settings > System > About phone > Software information, tap build number 7 times to enable Developer options)
3. Flash Tools, download from here and extract to your PC
4. Latest Magisk Manager which you can download from the relevant thread (search or click here)
BOOT IMAGES
Stock Boot images:
Firmware WW_16.1220.1906.174_0 >>>> Click here
Firmware WW_16.1220.1908.189_1.1.1 >>>> Click here
Patched Boot images:
Firmware WW_16.1220.1906.174_0 (patched with Magisk 19.3 stable version) >>>> Click here
Firmware WW_16.1220.1908.189_1.1.1 (patched with Magisk 19.3 stable version) >>>> Click here
Steps to Root:
1. Connect your device with USB cable
2. Go to the folder where you copied Flash Tools and double click to run cmd-here.exe
3. In the command prompt run the command adb devices, this will run the Deamon and show your device under List of devices attached. If doesn't show your device, check your device is connected and USB debugging is enabled.
4. Now run the command adb reboot bootloader to boot your device in to Fastboot mode
5. Now flash the patched boot image with the command fastboot flash boot magisk_patched.img
Restart your device with the fastboot command fastboot reboot and enjoy your ROOTED device
It works great, thanks!!
But then I installed miracast magisk module and now everytime I flash magisk patched boot, my phone is stuck on Asus logo so I have to flask stock boot to use my phone.
I think I should flash system image but when I unzip firmware from Asus site ( https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/ ) on my mac,
It doesn't show any system image (or even boot image), only "compatibility" , "payload" and some other stuff.
Can you tell me what I am doing wrong?
EMJI79 said:
But then I installed miracast magisk module and now everytime I flash magisk patched boot, my phone is stuck on Asus logo so I have to flask stock boot to use my phone.
I think I should flash system image but when I unzip firmware from Asus site ( https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/ ) on my mac,
It doesn't show any system image (or even boot image), only "compatibility" , "payload" and some other stuff.
Can you tell me what I am doing wrong?
Click to expand...
Click to collapse
Hi ASUS firmware for Zenfone do not have system img and instead it is the payload.bin which holds all system files. You can extract system image using python based tools.
You can remove the module if you flash TWPR and using file manger in TWRP to remove magix folder. This will remove magisk completely. Or, reset system via stock recovery. Completely switch off your device. Now, press and hold volume up button and press power button. It will help you to boot in to stock recovery. Or you can follow the guide here
If you still want to flash stock firmware, this link may help.
smohanv said:
Hi ASUS firmware for Zenfone do not have system img and instead it is the paylod.bin which holds all system files. You can extract system image using python based tools.
You can remove the module if you flash TWPR and using file manger in TWRP to remove magix folder. This will remove magisk completely. Or, reset system via stock recovery. Completely switch off your device. Now, press and hold volume up button and press power button. It will help you to boot in to stock recovery. Or you can follow the guide here
If you still want to flash stock firmware, this link may help.
Click to expand...
Click to collapse
If I just reset system via stock recovery, will I lose user data?
EMJI79 said:
If I just reset system via stock recovery, will I lose user data?
Click to expand...
Click to collapse
Yes you do. But you will not loose the files and folder in internal storage like photos etc..
You have to install all user applications again.
I would suggest you to follow the thread to flash TWRP and just remove magisk folder in TWRP file manager.
smohanv said:
Yes you do. But you will not loose the files and folder in internal storage like photos etc..
You have to install all user applications again.
I would suggest you to follow the thread to flash TWRP and just remove magisk folder in TWRP file manager.
Click to expand...
Click to collapse
I will do that.
Just another question: can I just boot in Twrp without installing it?
EMJI79 said:
I will do that.
Just another question: can I just boot in Twrp without installing it?
Click to expand...
Click to collapse
You can boot in to TWRP without permanently flashing it.
Take few cautions before you attempt to boot in to TWRP using this option,
1. Remove fingerprint in security settings (settings > Security & lock screen > Fingerprint)
2. Remove screen lock PIN in settings > security & lock screen > screen lock > select NONE here and also make sure Fingerprint is not enabled in this screen
How to boot in to TWRP:
Download TWRP from here
Use the command in Fastboot > fastboot boot twrp-3.3.1-15-ASUS_I01WD.img
Now you can use file manager in TWRP and remove magisk folder. You have to mount system folder to do so.
EMJI79 said:
I will do that.
Just another question: can I just boot in Twrp without installing it?
Click to expand...
Click to collapse
Did you try the method I explained here >> https://forum.xda-developers.com/showpost.php?p=80100285&postcount=8
smohanv said:
Did you try the method I explained here >> https://forum.xda-developers.com/showpost.php?p=80100285&postcount=8
Click to expand...
Click to collapse
I will do that now. I just came back home.
Thanks.
---------- Post added at 04:28 PM ---------- Previous post was at 03:58 PM ----------
Do you think I can this:
https://magiskroot.net/uninstall-magisk-module-twrp/
edit: it's for older versions of Magisk
Still I can't see the Magisk modules or Magisk folder in /data or /system/data , it appears empty
EMJI79 said:
I will do that now. I just came back home.
Thanks.
---------- Post added at 04:28 PM ---------- Previous post was at 03:58 PM ----------
Do you think I can this:
https://magiskroot.net/uninstall-magisk-module-twrp/
edit: it's for older versions of Magisk
Still I can't see the Magisk modules or Magisk folder in /data or /system/data , it appears empty
Click to expand...
Click to collapse
Are you able to boot in TWRP recovery as I mentioned. Please confirm.
Have you mounted system in twrp. It won't go anywhere. You should find it. I have done this several times.
Read here for some more help.
https://magiskroot.net/uninstall-magisk-module-twrp/
Sent from ASUS ZenFone 6 (2019) using Tapatalk
smohanv said:
Are you able to boot in TWRP recovery as I mentioned. Please confirm.
Have you mounted system in twrp. It won't go anywhere. You should find it. I have done this several times.
Read here for some more help.
https://magiskroot.net/uninstall-magisk-module-twrp/
Sent from ASUS ZenFone 6 (2019) using Tapatalk
Click to expand...
Click to collapse
Yes I am able to boot in TWRP and browse inside the files.
I am checking system square in TWRP mount section however I tried to mount data also and it isn't possible.
I will try the advised link later today, thanks for the help.
EMJI79 said:
Yes I am able to boot in TWRP and browse inside the files.
I am checking system square in TWRP mount section however I tried to mount data also and it isn't possible.
I will try the advised link later today, thanks for the help.
Click to expand...
Click to collapse
Yes. I did try as well. It seems like TWRP is loading in READ ONLY mode. I doubt whether you can flash the uninstall mod as well. But worth trying as you can save all your installed apps.
smohanv said:
Yes. I did try as well. It seems like TWRP is loading in READ ONLY mode. I doubt whether you can flash the uninstall mod as well. But worth trying as you can save all your installed apps.
Click to expand...
Click to collapse
Which method from the link do you advise to try first?
smohanv said:
Yes. I did try as well. It seems like TWRP is loading in READ ONLY mode. I doubt whether you can flash the uninstall mod as well. But worth trying as you can save all your installed apps.
Click to expand...
Click to collapse
Check this link and follow. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
smohanv said:
Check this link and follow. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
Click to expand...
Click to collapse
No luck, can't flash anything in TWRP ...
Guess I have to wait TWRP is updated.
Mauronofrio telling that one have to install 3.3.1-15 to write on data:
https://forum.xda-developers.com/ze...cial-twrp-recovery-asus-t3937844/post80108953
EMJI79 said:
Mauronofrio telling that one have to install 3.3.1-15 to write on data:
https://forum.xda-developers.com/ze...cial-twrp-recovery-asus-t3937844/post80108953
Click to expand...
Click to collapse
yes. I can see that there is an installer (magisk module) which has to be flashed in magisk in order for TWRP to write on data partition.
In your case, you cannot boot your device with rooted image as you have a module which is causing bootloop. Catch 22 sistuation.
In this situation I think you have only one option left which is resetting your device loosing all installed apps. Sorry mate. Could not help you at this time.
New Update
smohanv said:
yes. I can see that there is an installer (magisk module) which has to be flashed in magisk in order for TWRP to write on data partition.
In your case, you cannot boot your device with rooted image as you have a module which is causing bootloop. Catch 22 sistuation.
In this situation I think you have only one option left which is resetting your device loosing all installed apps. Sorry mate. Could not help you at this time.
Click to expand...
Click to collapse
Hello Smohanv,
Say I want to update to the latest Firmware that got released yesterday, and I am currently rooted via the method you introduced on the first page with firmware 16.1220.1906.174_0, how do I go about it?
If I do the Manual update, will I loose root? Or should I wait for you to release a patched one, and then do the manual update?
Thanks.
Damionix said:
Hello Smohanv,
Say I want to update to the latest Firmware that got released yesterday, and I am currently rooted via the method you introduced on the first page with firmware 16.1220.1906.174_0, how do I go about it?
If I do the Manual update, will I loose root? Or should I wait for you to release a patched one, and then do the manual update?
Thanks.
Click to expand...
Click to collapse
Yes you will loose root. Why do you go for build 171 when 189 is available now.
Official link: >>> https://www.asus.com/us/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
New build can be downloaded from here >>> Download
EMUI 8 Stock ROMs:
3.2.1-0 by pretoriano80 (with data decryption on Android 8 )
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
EMUI 8 Custom ROMs:
3.2.1.0 by Catuva21:
https://mega.nz/#!JlkRVY7b!Hz0QTmbgmMNeCaU-PmVRBGKsdd9pslmWNkOZpE6I8ZA
3.2.3-0 by Askuccio
https://mega.nz/#!h9903SqS!aRXc9x6Kuz_GclVy_3ZExCLDSdnp7Ee8VIgfqOG9x8k
Chinese ROMs (inc. KangVip):
3.2.1-0
https://mega.nz/#!sp0UyCDR!bq10MAyh0sddUCPi0zecQzrmLfCESFvNlCiQ3vkPMqI
EMUI 9.1 Stock ROM & Custom ROMs:
3.2.1-0 GAGUGA Edition
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
EMUI 9.1 Custom ROMs:
3.4.0-0-emui9_eR by @S_mak
https://mega.nz/#!B8kWgJDC!_hj7xkTzF9Uj66wKjtrWPHEV5Dbkk7Q256tuiKg7FQU
On [A12], [A12.1] GSIs use 3.4.0-0-emui9_eR .
Do you mean you can install these over erecovery partition?
adamfirari said:
Do you mean you can install these over erecovery partition?
Click to expand...
Click to collapse
These TWRPs allow you to install any compatible TWRP over eRecovery.
Hi!
Is there a recovery that is able to make a full backup (modem nvm ecc..)?
TureX said:
Hi!
Is there a recovery that is able to make a full backup (modem nvm ecc..)?
Click to expand...
Click to collapse
Hello,
I never use Nandroid backup, so I don't know. Test it and let us know
hi all,
addonsu.zip works?
my output trying to flash via twrp
...
Installing su addon...
set_metadata: Error on lstat of "/system/addon.d/51-
addon.su": No such file or directory
Updater procedd ended with ERROR: 7
Error installing zip file '/sdcard/Download/addonsu-
16.0-arm-signed.zip'
...
twrp seems work fine, i can flash los and gapps without problem...
thank you
wax_77 said:
hi all,
addonsu.zip works?
my output trying to flash via twrp
...
Installing su addon...
set_metadata: Error on lstat of "/system/addon.d/51-
addon.su": No such file or directory
Updater procedd ended with ERROR: 7
Error installing zip file '/sdcard/Download/addonsu-
16.0-arm-signed.zip'
...
twrp seems work fine, i can flash los and gapps without problem...
thank you
Click to expand...
Click to collapse
HI!
Which vendor are you using? And which twrp shared are you using? Does lineageos 16 official boot keeping twrp installed?
Thanks in advance
wax_77 said:
hi all,
addonsu.zip works?
my output trying to flash via twrp
...
Installing su addon...
set_metadata: Error on lstat of "/system/addon.d/51-
addon.su": No such file or directory
Updater procedd ended with ERROR: 7
Error installing zip file '/sdcard/Download/addonsu-
16.0-arm-signed.zip'
...
twrp seems work fine, i can flash los and gapps without problem...
thank you
Click to expand...
Click to collapse
Hello,
I successfully installed the addonsu-16.0-arm64 using
TWRP
You have to enable root in Developer options. Works fine...
Hi there,
which TWRP can I use to downgrade to Oreo via HuRupdater?
Thanks.
Fjord1 said:
Hi there,
which TWRP can I use to downgrade to Oreo via HuRupdater?
Thanks.
Click to expand...
Click to collapse
3.2.1-0 by pretoriano80 .
Note: If you don't have the required files stored somewhere, then it's just an academic question - Firmware finder is ďead.
-Alf- said:
Firmware finder is ďead.
Click to expand...
Click to collapse
It makes me sad...
And what about dload method?
Fjord1 said:
downgrade to Oreo
Click to expand...
Click to collapse
Fjord1 said:
dload method
Click to expand...
Click to collapse
you will get absolutely no success, it may even brick your phone.
Hi all. I am trying to recover content from a MediaTab T5 with a Damaged screen (no picture). I've managed to install these recoveries and reboot into them. However none of them provide an adb interface for shell access, only a virtual usb cd rom drive appears. How can I obtain recovery adb access? I need to enable USB debugging and push adbkey...
Anyone have any clues how I can work around this please. Is patched boot img the only way forward?
OK good news I Successfully booted into recovery and have adb access. I think the key was to power on with vol+, but WITHOUT the USB cable attached. If USB cable is attached then it tries to boot to system regardless
-Alf- said:
Hello,
I never use Nandroid backup, so I don't know. Test it and let us know
Click to expand...
Click to collapse
hi, I was just wondering incase something goes wrong, can you link me some thread or guide to go back to stock firmware (I do have the full firmware files)
Mahad Habib said:
hi, I was just wondering incase something goes wrong, can you link me some thread or guide to go back to stock firmware (I do have the full firmware files)
Click to expand...
Click to collapse
I'm not sure I fully understand your question :
- go back to stock from custom ROM?
- what full FW do you have?
-Alf- said:
I'm not sure I fully understand your question :
- go back to stock from custom ROM?
- what full FW do you have?
Click to expand...
Click to collapse
yes that's my question.
the one I have is
"Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.144(C185) Firmware Android 8.0.0 EMUI 8.0.0"
I know this works because I used it to downgrade.
Mahad Habib said:
yes that's my question.
the one I have is
"Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.144(C185) Firmware Android 8.0.0 EMUI 8.0.0"
I know this works because I used it to downgrade.
Click to expand...
Click to collapse
Yes, you can revert to stock flashing this Service ROM , if yot are running EMUI 8. For EMUI 9.1 use Service ROM 9.1.0. This process will erase all your data and lock the BL again!
Or, simply flash SYSTEM.img extracted from Service ROM using Huawei
update extractor. This procedure will not erase your data ,bootloader remains unlocked etc.
Hey Alf,
Were you able to flash any of the recoveries over the erecovery?
The 3.2.1-0 GAGUGA Edition has a built in option but it didn't work for me, no failures but when I hold down vol + I still get erecovery. I tried flashing 3.4.0-0-emui9_eR by @S_mak to erecovery_ramdisk but got a command not allowed.
PRA-LX1 on a C432 base, got CAOS11 system and Magisk in recovery. Since the recovery partition is occupied by Magisk having TWRP on erecovery would be ideal.
Thank you for your posts, they've been useful.
hopeless_bricker said:
Hey Alf,
Were you able to flash any of the recoveries over the erecovery?
The 3.2.1-0 GAGUGA Edition has a built in option but it didn't work for me, no failures but when I hold down vol + I still get erecovery. I tried flashing 3.4.0-0-emui9_eR by @S_mak to erecovery_ramdisk but got a command not allowed.
PRA-LX1 on a C432 base, got CAOS11 system and Magisk in recovery. Since the recovery partition is occupied by Magisk having TWRP on erecovery would be ideal.
Thank you for your posts, they've been useful.
Click to expand...
Click to collapse
flash TWRP , run command
fastboot flash recovery_ramdisk (TWRP's_name).img
(Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP),
- Copy TWRP file to the SD card, and also copy to card Stock Recovery_ramdisk.
- Enter TWRP, select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe.
- Go back, find Stock recovery_ramdisk file, (or magisk-patched recovery_ramdisk on EMUI 9) , mark Recovery, swipe. Reboot system.
P.S.: as far as i know the PRA-LX1 hasn't received an upgrade to Pie (correct me if I'm wrong) , so i don't understand
hopeless_bricker said:
Since the recovery partition is occupied by Magisk
Click to expand...
Click to collapse
-Alf- said:
flash TWRP , run command
fastboot flash recovery_ramdisk (TWRP's_name).img
(Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP),
- Copy TWRP file to the SD card, and also copy to card Stock Recovery_ramdisk.
- Enter TWRP, select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe.
- Go back, find Stock recovery_ramdisk file, (or magisk-patched recovery_ramdisk on EMUI 9) , mark Recovery, swipe. Reboot system.
P.S.: as far as i know the PRA-LX1 hasn't received an upgrade to Pie (correct me if I'm wrong) , so i don't understand
Click to expand...
Click to collapse
I got it wrong, it's a ANE-LX3! Mixed up with my other phone, sorry. In principle that method works, thank you. I didn't get to actually test it because it seems the Magisk recovery overrides the boot procedure so it always boots to recovery automatically.
Handy but I can't boot into the erecovery with the button combo now.
P.S.: I'm having issues with audio device switching. If I get a phone call with headphones inserted it routes to the speaker and I can't change it. If I remove the headphones then the mic doesn't work. I also have a bit inconsistent connection over bluetooth, sometimes it is connected but still plays over the speakers. I have the Huawei switch method enabled in the phh options. Did you experience this?
A lot of people rooted are having issues with DEX with either systemUI closing, systemuidex closing or the app only staying open on PC pr TV for a few seconds.
Please can anyone who is rooted please let me know if they can access DEX and if so - is it working for you?
Please show a pic of magisk front screen with version number and state your exact rooting procedure
Hopefully we can then find out what is breaking dex
UNLESS anyone knows what sort of log may diagnose the issue? I have a dumpstate/logcat but not sure what part im looking at
exocetdj said:
A lot of people rooted are having issues with DEX with either systemUI closing, systemuidex closing or the app only staying open on PC pr TV for a few seconds.
Please can anyone who is rooted please let me know if they can access DEX and if so - is it working for you?
Please show a pic of magisk front screen with version number and state your exact rooting procedure
Hopefully we can then find out what is breaking dex
UNLESS anyone knows what sort of log may diagnose the issue? I have a dumpstate/logcat but not sure what part im looking at
Click to expand...
Click to collapse
We're do I get root how to for the u version
The only version that is rooted is the B version. The international, European, and North American versions are not able to be rooted.
We have root on the B variant
I believe the issue is related to having the "Data" folder being decrypted - This "Decrypting" process is on step # 4 under the 2nd process "PROCESS IF COMING FROM STOCK A12"
I have tried the process without the "Formatting the data" step which allows me to boot with root + Dex working. The only issue is that I'm limited to storage, It's fixed to 32gb out of the original size(512gb). Is there a way to resolve the limited storage issue?
Note: If we decrypt the data(Format data via twrp), we are restricted to:
- Cannot share pics in Samsung Gallary
- Dex's system ui constantly crashes
- Cannot install apps such as games that requires external downloads from installing an apk
- GMail cannot download embed files from an email
- ETC anything related to storage within the data, we cannot access/delete/edit when the data is decrypted
lilplanet said:
I believe the issue is related to having the "Data" folder being decrypted - This "Decrypting" process is on step # 4 under the 2nd process "PROCESS IF COMING FROM STOCK A12"
I have tried the process without the "Formatting the data" step which allows me to boot with root + Dex working. The only issue is that I'm limited to storage, It's fixed to 32gb out of the original size(512gb). Is there a way to resolve the limited storage issue?
Note: If we decrypt the data(Format data via twrp), we are restricted to:
- Cannot share pics in Samsung Gallary
- Dex's system ui constantly crashes
- Cannot install apps such as games that requires external downloads from installing an apk
- GMail cannot download embed files from an email
- ETC anything related to storage within the data, we cannot access/delete/edit when the data is decrypted
Click to expand...
Click to collapse
Thats some great info thanks very much
although that would also effect the download and install of Magisk potentially and that works - do you have an example of an app or game doing this so i can test?
i can confirm i cannot share pics directly from gallery but can within apps such as telegram
Downloading docs from Gmail is buggered
Dex is RIP.
@ianmacd do you think there is something we could be missing - we are effectively doing the disabler's job manually on F926B and its not unreasonable to think we may have missed something - could running the multidisabler be useful to see if it picks something up (even if it completely breaks things) so that we can then do the required modification manually?
exocetdj said:
Thats some great info thanks very much
although that would also effect the download and install of Magisk potentially and that works - do you have an example of an app or game doing this so i can test?
i can confirm i cannot share pics directly from gallery but can within apps such as telegram
Downloading docs from Gmail is buggered
Dex is RIP.
@ianmacd do you think there is something we could be missing - we are effectively doing the disabler's job manually on F926B and its not unreasonable to think we may have missed something - could running the multidisabler be useful to see if it picks something up (even if it completely breaks things) so that we can then do the required modification manually?
Click to expand...
Click to collapse
Me again
BVA9 STOCKRooted !
No sharing issues , and 100% working DEX
I used your BL file , extracted recovery from your AP File to make an Odin flashable TWRP.tar to sideload and flash your app-debug.zip
pvillasuso said:
Me again
BVA9 STOCKRooted !
No sharing issues , and 100% working DEX
I used your BL file , extracted recovery from your AP File to make an Odin flashable TWRP.tar to sideload and flash your app-debug.zip
Click to expand...
Click to collapse
whats your internal storage size? and have you reset device since you last managed to get this working?
Yes , I have reseted the phone.
When flashing to stock I used CSC ( the one that wipes data )
Did a stock recovery factory reset and also format data when I used the twrp recovery .
There is something with wrong with your AP file Bro , because I first used that file , and I tried the camera and had the sharing issue . Same happened with your older build , So I think the problem is there.
I Have the 256gb version
pvillasuso said:
Yes , I have reseted the phone.
When flashing to stock I used CSC ( the one that wipes data )
Did a stock recovery factory reset and also format data when I used the twrp recovery .
There is something with wrong with your AP file Bro , because I first used that file , and I tried the camera and had the sharing issue . Same happened with your older build , So I think the problem is there.
I Have the 256gb version
Click to expand...
Click to collapse
Ok sounds promising
Please can you provide a step by step procedure here and if i can replicate it i will amend the first post and files in the rooting thread
looks like formatting in TWRP could be the issue then - and we need to format at a different stage? (please still provide full process)
exocetdj said:
looks like formatting in TWRP could be the issue then - and we need to format at a different stage? (please still provide full process)
Click to expand...
Click to collapse
Yes , do that factory reset from stock recovery .
I also think the twrp format is not working as expected
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this:
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
******
So I'm sure the BL file helped me to flash TWRP , because I tried it alone (TWRP) and it didn't work ( got bootloops ending in download mode ).
What I didn't try , now that Im reading myself , was to do a factory reset from stock , after doing that initial setup , and tried to flash that TWRP file right after that.
links to files :
AP_twrp_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
AP_stockrecovery_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
pvillasuso said:
Yes , do that factory reset from stock recovery .
I also think the twrp format is not working as expected
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this:
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
******
So I'm sure the BL file helped me to flash TWRP , because I tried it alone (TWRP) and it didn't work ( got bootloops ending in download mode ).
What I didn't try , now that Im reading myself , was to do a factory reset from stock , after doing that initial setup , and tried to flash that TWRP file right after that.
links to files :
AP_twrp_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
AP_stockrecovery_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
do you have stock recovery or TWRP installed now you have root?
exocetdj said:
do you have stock recovery or TWRP installed now you have root?
Click to expand...
Click to collapse
Stock recovery now
I can try to flash twrp , and can go back to stock recovery if it doesnt work
exocetdj said:
do you have stock recovery or TWRP installed now you have root?
Click to expand...
Click to collapse
the key is that if you install TWRP now and dex and file sharing etc etc is still working then i need to look at these files
As far as im aware = the DEX issues are a result of having TWRP installed
exocetdj said:
the key is that if you install TWRP now and dex and file sharing etc etc is still working then i need to look at these files
As far as im aware = the DEX issues are a result of having TWRP installed
Click to expand...
Click to collapse
Well, then I can try to install twrp , and launch DEX to see how it goes
Be right back and let you know
edit :
Flashed TWRP successfully !
No sharing issues , Dex working fine !
pvillasuso said:
Well, then I can try to install twrp , and launch DEX to see how it goes
Be right back and let you know
edit :
Flashed TWRP successfully !
No sharing issues , Dex working fine !
Click to expand...
Click to collapse
ok so i am now rooted with stock recovery and everything is working - Dex, sharing etc etc
so i am missing TWRP
please can you go into finer detail into what you then did to install TWRP i need to have as much information as possible - please also confirm if you can mount data and flash files in TWRP if not then there is not really much point in having TWRP installed - i am thinking this is unlikely as you have not disabled forcencryption
I have managed to follow this far
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
I am now rooted with stock recovery - i find it hard to see how we can just install TWRP and use it normally and mount /data without having to at least destroy user data each boot as forcencrypt has NOT been disabled
what is making things far too hard is a process that follows things like this:
"
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this: "
there are just too many variables - for instance, forceencryption could have been disabled without you realizing when doing the random bits - did you reflash my AP files at any point?
exocetdj said:
ok so i am now rooted with stock recovery and everything is working - Dex, sharing etc etc
so i am missing TWRP
please can you go into finer detail into what you then did to install TWRP i need to have as much information as possible - please also confirm if you can mount data and flash files in TWRP if not then there is not really much point in having TWRP installed - i am thinking this is unlikely as you have not disabled forcencryption
I have managed to follow this far
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
I am now rooted with stock recovery - i find it hard to see how we can just install TWRP and use it normally and mount /data without having to at least destroy user data each boot as forcencrypt has NOT been disabled
what is making things far too hard is a process that follows things like this:
"
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this: "
there are just too many variables - for instance, forceencryption could have been disabled without you realizing when doing the random bits - did you reflash my AP files at any point?
Click to expand...
Click to collapse
I agree with you about the variables
In short
I was rooted with stock BL6 and twrp
So I flashed to this newest stock , and tried to keep my setup and get rooted again
I flashed HOMECSC and after that gave a shot with newest twrp ( to flash newest app-debug.zip )
I ended with a download mode bootloop
So I used your guide with your files , everything went fine .. except for the sharing and dex issues
This is when the forceencryption could have been disabled , exactly !
Then , I did the steps above , back to 100% stock ( steps above ) , without your AP File this time .
TWRP , is useless at this point , it cant mount data , it is the same behaviour as with BL6 version
Edit : Nice that you could replicate it !
"ok so i am now rooted with stock recovery and everything is working - Dex, sharing etc etc "
pvillasuso said:
I agree with you about the variables
In short
I was rooted with stock BL6 and twrp
So I flashed to this newest stock , and tried to keep my setup and get rooted again
I flashed HOMECSC and after that gave a shot with newest twrp ( to flash newest app-debug.zip )
I ended with a download mode bootloop
So I used your guide with your files , everything went fine .. except for the sharing and dex issues
This is when the forceencryption could have been disabled , exactly !
Then , I did the steps above , back to 100% stock ( steps above ) , without your AP File this time .
TWRP , is useless at this point , it cant mount data , it is the same behaviour as with BL6 version
Click to expand...
Click to collapse
Thanks for the info
looks like using TWRP at a starting point is the only way thats going to be of any use - rooted stock is the way forward!!!
exocetdj said:
Thanks for the info
looks like using TWRP at a starting point is the only way thats going to be of any use - rooted stock is the way forward!!!
Click to expand...
Click to collapse
Sure Bro , no problem