This thread is now defunct. I have moved to iPhone. Sorry about this.
Take care everybody.
Regards,
Magnetox
Appreciate this! If I'm already unlocked, is it possible to remove the -w in the flash-all script before running for a rooted install without wiping user data?
Wi1son said:
Appreciate this! If I'm already unlocked, is it possible to remove the -w in the flash-all script before running for a rooted install without wiping user data?
Click to expand...
Click to collapse
I would leave it as is, but if you want to try it, go ahead (might brick).
Hi ! Thanks for it.
Just a question After flash the Rom when the phone reboot before copy magisk manager can restore my Google backup ?
And how I do when they had an update ?
Thanks
ggkameleon said:
Hi ! Thanks for it.
Just a question After flash the Rom when the phone reboot before copy magisk manager can restore my Google backup ?
And how I do when they had an update ?
Thanks
Click to expand...
Click to collapse
Yes that should be fine. Just restore normally. But don't forget magisk otherwise it won't have proper root.
Might be a silly question, but, does this stock image work with Google Fi?
Also, a little confused with some of the directions...
In step 1 it says "Download the appropriate rar package for your system and install."
Does this mean download my stock image from Google and install it with Magisk, or... ?
In step 9 it says, " Once in fastboot, and the bootloader, run "fastboot devices" from the "BRAMBLE" folder. "
Does this mean to run "fastboot devices" as a command inside the command prompt from the "BRAMBLE" folder or to open one of the tools inside the platform tools folder?
Also, in step 11, where do I find the "appropriate flash-all command on your operating system"?
These are just a bit confusing to me. Don't want to brick my phone, so any help is appreciated.
Thanks
SpecialKCF22 said:
Also, a little confused with some of the directions...
...
Thanks
Click to expand...
Click to collapse
Download the WinRAR package in the mega.nz folder for your OS.
Both, platform tools should be in that BRAMBLE folder. Example fastboot.exe should be in BRAMBLE.
You will find this in your BRAMBLE folder when you properly extract platform tools and the .rar into the BRAMBLE folder.
SpecialKCF22 said:
Might be a silly question, but, does this stock image work with Google Fi?
Click to expand...
Click to collapse
It's just stock with root, so if the Pixel 4a 5g works normally it will too.
Magnetox said:
Download the WinRAR package in the mega.nz folder for your OS.
Both, platform tools should be in that BRAMBLE folder. Example fastboot.exe should be in BRAMBLE.
You will find this in your BRAMBLE folder when you properly extract platform tools and the .rar into the BRAMBLE folder.
Click to expand...
Click to collapse
You're not very detailed and you didn't answer the questions. I'll pass on this method. Thanks
SpecialKCF22 said:
You're not very detailed and you didn't answer the questions. I'll pass on this method. Thanks
Click to expand...
Click to collapse
Feel free to PM
Magnetox said:
Yes that should be fine. Just restore normally. But don't forget magisk otherwise it won't have proper root.
Click to expand...
Click to collapse
So, will update delete the magisk app? Or what do you mean when write "don't forget magisk"?
Ryav said:
So, will update delete the magisk app? Or what do you mean when write "don't forget magisk"?
Click to expand...
Click to collapse
I mean don't forget to install it and assure you have proper root after.
Does this one works with Google pay. My rooted build of RD1A.200810.022.A4 doesn't pass the safety check on magisk manager. Thank you
imFonk said:
Does this one works with Google pay. My rooted build of RD1A.200810.022.A4 doesn't pass the safety check on magisk manager. Thank you
Click to expand...
Click to collapse
MAGISK MODULE ❯ Universal SafetyNet Fix 1.1.0
Thanks for this! FYI for anyone curious the newest Magisk 8.07 does work, you don't need to use the linked file.
dadozer said:
Thanks for this! FYI for anyone curious the newest Magisk 8.07 does work, you don't need to use the linked file.
Click to expand...
Click to collapse
Yes feel free to do this. The APK that is linked works fine as well and will update itself with your permission.
Magnetox said:
Hey everybody,
Here is the latest Android 11 January 2021 update rooted (I will keep it updated). It's all clean. It is the Google stock system image with root applied (comes with GAPPS). You can cleanly flash your device with this as long as your fastboot (bootloader) is working.
Download LINK:
File folder on MEGA
mega.nz
Steps:
1) Download the appropriate rar package for your system and install.
2) Download the appropriate platform-tools package for your operating system (this contains ADB and Fastboot) and extract it in a folder we'll call "BRAMBLE" (we will use this folder for the install).
3) Download the bramble-rq1a.210105.003.rar file (this is the stock rom). Extract it to the "BRAMBLE" folder. You will want to see all the files (ie. the flash-all.sh) all in the folder the same folder that contains the ADB and Fastboot tools.
4) Download MagiskManager-v8.0.4.apk, this will be used after the install and installed on the device.
5) Enable USB debugging and OEM unlocking (the bootloader unlock) in developer options (smash on build a bunch of times in a row real fast to enable developer options in about phone).
7) Navigate to the "BRAMBLE" folder with a terminal or command prompt (depending on your operating system) and run "adb devices" with root or administrator access in your terminal or command prompt on your computer (respectively there). Allow the USB debugging to connect to your computer forever on your phone, something should pop up. It should appear in the terminal or command prompt. If not you need to accept USB debugging on your phone (forever).
8) Put in the command "adb reboot bootloader" once your device appears.
9) Once in fastboot, and the bootloader, run "fastboot devices" from the "BRAMBLE" folder. This should return your device. If not, something is wrong and restart. Another way of reaching fastboot is restarting your phone and holding VOLUME DOWN.
10) Make sure your device is unlocked, run "fastboot flashing unlock".
11) In the "BRAMBLE" folder, run the appropriate flash-all command on your operating system. This will take a while and completely reflash the system with the Stock ROM with root. You will see the progress as it appears.
12) Once it's done, your phone will reboot. Just wait for it to start up and do as you normally would on a new flash.
13) Move the MagiskManager-v8.0.4.apk onto the phone, and install it. It will confirm you have partial root and ask you to apply something more and reboot. Do so.
14) When rebooted, your phone will be fully flashed and rooted. Feel free to download a root verification app, I recommend this one. It should be working fine. Grant root permission forever to it.
If you have any questions, feel free to ask. You can install the ElementalX kernel on this rom for Pixel 4a 5g. Download this. It's a great kernel tool and it will help you with full root access download and install the kernel. It's the kernel I'm using.
Regards,
Magnetox
Click to expand...
Click to collapse
i could not install magisk, the 13th step in your guide might not be complete.
i managed to root, and got to pass safety net, and google pay working.
i have to move the boot.img from the zip file included in the package you provided, move it to internal storage, patch it in magisk manager.
then i moved the patched boot.img to my pc, did adb reboot bootloader, then fastboot flash [patched boot.img] and then only i was fully rooted.
i also flash the safetynet-fix-v1.1.1.zip module in magisk to pass satefynet.
hope it could help out, i digged all night yesterday to get this done lol.
MegaJuif said:
i could not install magisk, the 13th step in your guide might not be complete.
i managed to root, and got to pass safety net, and google pay working.
i have to move the boot.img from the zip file included in the package you provided, move it to internal storage, patch it in magisk manager.
then i moved the patched boot.img to my pc, did adb reboot bootloader, then fastboot flash [patched boot.img] and then only i was fully rooted.
i also flash the safetynet-fix-v1.1.1.zip module in magisk to pass satefynet.
hope it could help out, i digged all night yesterday to get this done lol.
Click to expand...
Click to collapse
I updated it with the latest 8.0.7 magisk. Hope this fixes it. (Uploading now)
Upload complete! (Magisk 8.0.7)
Related
Hi everyone,
I tried using a script which automated the install for the the custom recovery, but I started to get messages that it ran out of disk space (I can't link to the file due to my noob status). I probably should have come here first before using that script, but such as life..
I have no important data on the phone, if I lose it all that's ok.
It rebooted and my p500 waits with the following
"Fastboot mode started"
"udc_start()"
It also gives some info when USB is connected ie.
"- suspend -"
"- reset -"
Do I have a paperweight?
thanks and sorry for the newb post ..
edit: so I found this : http://forum.xda-developers.com/showthread.php?t=1003790 and
http://forum.xda-developers.com/showthread.php?t=875881
and have gotten it to the yellow emergency mode, not sure how to flash it from here though.
edit2: dling the stock firmware from http://forum.xda-developers.com/showthread.php?t=1073827
edit3: there's this as well.. http://forum.xda-developers.com/showthread.php?t=1088046 If I try this method, will it screw up again from too little free disk space?
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
thank you very much, I appreciate it haha
Your phone has booted in fastboot mode. Go to development section and read a tutorial how to recover from fastboot.
Sent from my LG-P500 using XDA Premium App
setTopbox said:
thank you very much, I appreciate it haha
Click to expand...
Click to collapse
Then did u unbricked now
Mahesh
go here....
http://forum.xda-developers.com/showthread.php?t=1088046
or here
http://forum.xda-developers.com/showthread.php?p=13813493
How to install Android SDK /ADB
http://lgoptimusonep500.blogspot.com/2011/01/how-to-install-android-sdk-adb.html
dislplin01 said:
I'm to drunk to guide our give you the link to fix it but I will tell you, you can fix it just hold on we will help you ; ) and we don't by the time I wake up I will help you its ok ))
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Most honest post I've seen on the entire forum.
Sent from my Kyocera Echo.
mvgadagi said:
Then did u unbricked now
Mahesh
Click to expand...
Click to collapse
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
setTopbox said:
I got the phone working again - thanks! I guess it's not a great idea to install the custom recovery
with low disk space?
Click to expand...
Click to collapse
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
shhbz said:
well if u ever wish to install recovery just download rom manger from market (latest) and install recovery from rom manger option make sure u hav eusb debugging enabled. it works easy
Click to expand...
Click to collapse
Erm... reading all the posts about fastboot after using ROM Manager for this, I guess I would rather stick with the custom script using flash_image.
doktornotor said:
Hmmm. Well, should not matter? /recovery uses a separate partition. Perhaps you flashed a corrupt (incomplete) image?
Click to expand...
Click to collapse
hmm, I'm not sure (when I dl'd the file I did compare the hash as per instructions). I used the following instructions:
manast.com/2011/05/07/how-to-install-custom-recovery-on-lg-optimus-one-p500
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
setTopbox said:
I then went into a terminal emulator, and ran "sh /sdcard/rf.sh". At that point the output of the script started to say "disk full" (and then it reboot into the fastboot prompt).
Click to expand...
Click to collapse
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
doktornotor said:
No idea about that script. Using flash_image and never had any issue with "disk full", frankly the message does not make sense. All you need is to copy the recovery image to SD and run as root:
Code:
# flash_image recovery /sdcard/recovery.img
Done.
Click to expand...
Click to collapse
I'm getting permission denied when trying to use flash_image. Gingerbreak says the device is rooted, and the terminal does ask for superuser permission when i open it (su works in the terminal). I also tried chmod 755 flash_image but that didn't work either.
the permissions for flash_image are r-xr-x any thoughts ?
edit: apparently the sdcard is mounted with -noexecute ? So I tried copying flash_image to / but it's read only. Is there somewhere where I can execute this?
This rf.sh script seems most notorious, I too went into fastboot after that. Doktornotor's method worked (in fact I think he/she was the one who bailed me out back then as well).
If you got into fastboot, most probably you have a rooted phone.
To use flash_image you need to get the flash_image.sh on the root of your sd card. Search the forum for Amon-Ra custom recovery, and you shall find this file in that thread (it is required for Amon ra setup). Log in to your adb console, and use fastboot to push the new image in the recovery partition.
Unless your recovery.img or flash_image.sh is corrupted, it will work for sure.
Keep in mind, fastboot is a very powerfull tool, if you can access it, you're safe.
Cheers,
Alex
did you get out??
just flash stock firmware with kdz worked for me bro
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Dr.Alani said:
Buddy,
You do not need to flash anything with KDZ. The ROM is fine nothing happened to it. All your issue is with the recovery being flashed wrongly for some reason.
I had the same issue just yesterday and I managed to flash the recovery through fastboot.
What you need to do is:
1. Install android SDK from Google.
2. Connect the phone while it is on fastboot.
3. If your windows does not find the fastboot drivers online, use the drivers in this link:
http://www.megaupload.com/?d=39ZR16W1
4. extract the .zip file that you copied to your SD. The one that contains the recovery.
5. Copy the recover.img (or whatever the name of the .img file in the .zip file) to the folder inside the android sdk where fastboot.exe is located (I think its the tools folder)
6. Copy the adbwinapi.dll file from the android SDK\platform-tools\ to the folder containing fastboot.
7. issue the command (and replace recovery.img with the .img file name you have):
fastboot flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
setTopbox said:
I appreciate the information. When I'm in adb, su won't allow me to gain root access on the phone. The phone itself is rooted using gingerbreak though.
Click to expand...
Click to collapse
I do not see how you need to use adb.
Sent from my LG-P500 using XDA App
So what I am trying to do is get my feet wet with doing some dev work and basically I'm trying to figure out how to (without flashing anything, i want to remove the stuff myself):
De-bloat the stock sense rom and/or just remove all of the HTC garbage and use a different launcher all together without if affecting the system (Im not too sure what is acceptable to remove and what needs to stay in the /system/app/ dir)
Remove the annoying WiFi in the status bar
any and all help is much appreciated and even just pointing me in the right direction
Well you are going to have to flash something.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Well you are going to have to flash something.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I guess what I was trying to say was I wanted to be able to do the work myself rather than flashing a zip someone else made to get rid of like lets say the wifi in status bar
.torrented said:
I guess what I was trying to say was I wanted to be able to do the work myself rather than flashing a zip someone else made to get rid of like lets say the wifi in status bar
Click to expand...
Click to collapse
Here's state of the art for today:
1. Hack DNA to make it look like non-Verizon to the htcdev.com site. Here's a new painless method: http://forum.xda-developers.com/showthread.php?t=2109862
2. Go to htcdev.com and follow link to unlock bootloader. Note that this will WIPE YOUR "SD CARD". It's the only thing that does that. No problem with ROMs, etc. Not even a "factory reset" wipes the "SD", but the bootloader unlock does. You can do a backup before rooting if you install ADB on your PC. See 3a.
3. Install ADB on your PC http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ and test the connection with "adb devices" command.
a. Consider backup of DNA before unlocking http://forum.xda-developers.com/showthread.php?t=1420351
4. Install a recovery.
a. Dowload a recovery to your PC, either Clockworkmod http://forum.xda-developers.com/showthread.php?t=2051547 or TWRP http://forum.xda-developers.com/showthread.php?t=1994662. Extract the recovery.img file to a folder on your desktop,
b. Connect your DNA to your PC. Open a command prompt in the folder with the recovery by shift-right clicking in that folder and selecting "open command prompt here".
c. Type "adb reboot bootloader" without quotes and enter. DNA will reboot into bootloader. enter "fastboot flash recovery recovery.img" and you're there. You're done with the PC.
5. Install superuser and busybox.
a. Download superuser http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip to your "SD card".
b. Reboot to recovery. You can start recovery during a boot by holding down the volume down button during power up of phone.
c. Use the install zip function to install the above zip. Find links to wipe cach partition and Dalvik cache. Reboot and you're rooted.
d. Install busybox from market.
6. Change to a kernel that can write to system. Most reliable is LK 0.9.5. This will also save you considerable battery life. http://forum.xda-developers.com/showthread.php?t=2106178
a. Download the zip to your DNA and unzip it. There is a boot.img file and another zip file with "kernel modules".
b. Download flash image GUI from market. Use it to find the boot.img file and flash, ignoring the warning about modules. (hard way is use ADB and fastboot flash boot boot.img)
c. Use recovery to install the modules zip package with the install zip function. Wipe cache and Dalvik cache
and reboot.
7. Install Titanium Backup. With this, you can simply freeze or uninstall any app, system/bloat or otherwise, but it requires the system write kernel to change system files.
6. Stronly consider switching ROMs to Viper. All the good of stock but better in so many ways.
yearn2burn said:
Here's state of the art for today:
1. Hack DNA to make it look like non-Verizon to the htcdev.com site. Here's a new painless method: http://forum.xda-developers.com/showthread.php?t=2109862
2. Go to htcdev.com and follow link to unlock bootloader. Note that this will WIPE YOUR "SD CARD". It's the only thing that does that. No problem with ROMs, etc. Not even a "factory reset" wipes the "SD", but the bootloader unlock does. You can do a backup before rooting if you install ADB on your PC. See 3a.
3. Install ADB on your PC http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ and test the connection with "adb devices" command.
a. Consider backup of DNA before unlocking http://forum.xda-developers.com/showthread.php?t=1420351
4. Install a recovery.
a. Dowload a recovery to your PC, either Clockworkmod http://forum.xda-developers.com/showthread.php?t=2051547 or TWRP http://forum.xda-developers.com/showthread.php?t=1994662. Extract the recovery.img file to a folder on your desktop,
b. Connect your DNA to your PC. Open a command prompt in the folder with the recovery by shift-right clicking in that folder and selecting "open command prompt here".
c. Type "adb reboot bootloader" without quotes and enter. DNA will reboot into bootloader. enter "fastboot flash recovery recovery.img" and you're there. You're done with the PC.
5. Install superuser and busybox.
a. Download superuser http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip to your "SD card".
b. Reboot to recovery. You can start recovery during a boot by holding down the volume down button during power up of phone.
c. Use the install zip function to install the above zip. Find links to wipe cach partition and Dalvik cache. Reboot and you're rooted.
d. Install busybox from market.
6. Change to a kernel that can write to system. Most reliable is LK 0.9.5. This will also save you considerable battery life. http://forum.xda-developers.com/showthread.php?t=2106178
a. Download the zip to your DNA and unzip it. There is a boot.img file and another zip file with "kernel modules".
b. Download flash image GUI from market. Use it to find the boot.img file and flash, ignoring the warning about modules. (hard way is use ADB and fastboot flash boot boot.img)
c. Use recovery to install the modules zip package with the install zip function. Wipe cache and Dalvik cache
and reboot.
7. Install Titanium Backup. With this, you can simply freeze or uninstall any app, system/bloat or otherwise, but it requires the system write kernel to change system files.
6. Stronly consider switching ROMs to Viper. All the good of stock but better in so many ways.
Click to expand...
Click to collapse
While all of this is very very helpful, I failed to mention that this isn't my first rodeo, While I have firm understanding of ADB and rooting and flashing, my approach was more of the "behind the scenes" kind of stuff like what goes on inside of the ROM (tweaking files and what not) I'm at the stage where im trying to learn how to cook a rom(i guess some would say). I've already done so with CM10.1 for my Nexus 7(compiled from sauce), im farily comfortable with linux and my way around the OS. I've got the kitchen setup as well as apktool and what Im trying to learn is how to use these tools to their full extent.
like to make the boot.img unsecure, create a "flashable signed zip", remove non essential apps, the starter stuff
A little bit of background about me: I love computers, im going to school for a Computer Science degree, this kind of work has always interested me and I cant seem to get enough of it, ever since ive discovered this site i cant keep away and i love this communty, I've always wanted to just do more than flash someone else's work, i want to give back and start being able to do things.
Like i said before thanks to everyone for any information its all much appreciated!
I posted this a while ago in the [sm-a320fl][7.0][firmware] thread. Now in a new thread, so everybody will find it.
I'm not responsible for any damage. My phone was not branded.
This tutorial is only for SM-A320FL, also known as Galaxy A3!
Make sure you read the whole tutorial before doing anything.
Make a backup of your data. You need to make a factory reset!
Also read the additional information in the separated threads! Knox will be tripped after that, so you can't use it any more. And no more Warranty!
You can find a Android 7 version with the latest security patch with google or just use the linked one. Make sure the CSC is correct for your country/language.
1. Download the following stuff:
Android 7 A320FLXXU1BQH7_A320FLOXA1BQH7_A320FLXXU1BQG6.zip thx to tys0n
Latest Odin3
twrp_3.1.1-1_sm-a320f_11917 thx to ashyx
[*]Boot image patch no-verity-no-encrypt_ashyx thx to ashyx
[*][UNOFFICIAL] Material Design Xposed Installer [09/09/17] thx to DVDandroid
Xposed Installer 3.1.5 thx to rovo89
Magisk thx to topjohnwu
2. Flash Android 7 via Odin. There are enough tutorials on how to do that. Basicly unzip the Android 7 zip file and assign the AP_... file to the AP slot, the BL_... file to the BL slot and so on.
2.a Unlock OEM: Settings -> Developer Options -> OEM unlocking More Information
3. Flash TWRP via Odin; Thread with additional informations
Instructions summary:
Flash with ODIN 3.10.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst holding POWER + HOME.
You should now see TWRP recovery.
Click to expand...
Click to collapse
4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System.
4. Format Data in TWRP. To do that click on Wipe -> Format Data in TWRP. After that all your data is lost! Reboot to System.
5. Copy the Xposed Installer APK file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP.
6. Copy the Magisk ZIP file to your SD card and install it via TWRP. Reboot to System.
7. Open the Magisk Manager and enable root access via SuperUser within the Manager.
8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed.
8. Open Xposed Installer and install the latest Xposed framework. Follow the steps displayed.
9. Now you should have root access, Magisk and Xposed up and running.
Quotes and additional information:
[RECOVERY][ROOT][TWRP 3.1.1-1] Galaxy A3 - SM-A320F/FL/Y (2017) by ashyx
[*][UNOFFICIAL] Material Design Xposed Installer [09/09/17] by DVDandroid
[2017.9.6] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu
[*][2017.9.9][Magisk][SDK 21-25] Xposed v87.3 - Universal Systemless Compatibility by topjohnwu
[OFFICIAL] Xposed for Lollipop/Marshmallow/Nougat/Oreo by rovo89
---------- Post added at 11:22 AM ---------- Previous post was at 11:07 AM ----------
khanvict90 said:
Any body else have lag with the patern unlock screen ?
Click to expand...
Click to collapse
I had the same problem and it drove me crazy. It appeared every time after I rooted my phone with the old "flash the SuperUser.zip via TWRP" method.
After I rooted my phone via Magisk (Tutorial above), there is no more annoying lag. :good:
Trying to install sdk25/sdk25 and getting an error:
Wrong Android version:
This file is for: SDK25
Please download the correct package
for your Android version
Failed
Installation error
simple_s said:
8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed.
Click to expand...
Click to collapse
Anyway, I face the lockscreen lag even if I use Magisk to root my phone. So, sadly no luck for me...
Thanks for the tutorial.
I have two questions.
1. is it needed to use the Xposed installer by DVDandroid, or does the official one do the same job when using Xposed Magisk module?
2. I read you end in a bootloop when using the Magisk way on the Superman ROM thread for S7
https://forum.xda-developers.com/showpost.php?p=74048136&postcount=11120
answer here
https://forum.xda-developers.com/showpost.php?p=74054639&postcount=11125
does this also happen with A320FL? I installed Xposed in system because of that and have no problems.
y2klol said:
Trying to install sdk25/sdk25 and getting an error:
Wrong Android version:
This file is for: SDK25
Please download the correct package
for your Android version
Failed
Installation error
Click to expand...
Click to collapse
Please read the tutorial! You need SDK 24 if you are on Android 7.
Pat750 said:
Thanks for the tutorial.
I have two questions.
1. is it needed to use the Xposed installer by DVDandroid, or does the official one do the same job when using Xposed Magisk module?
Click to expand...
Click to collapse
I didn't try that. Maybe it will work.
Pat750 said:
2. I read you end in a bootloop when using the Magisk way on the Superman ROM thread for S7
https://forum.xda-developers.com/showpost.php?p=74048136&postcount=11120
answer here
https://forum.xda-developers.com/showpost.php?p=74054639&postcount=11125
does this also happen with A320FL? I installed Xposed in system because of that and have no problems.
Click to expand...
Click to collapse
In my opinion it will do the same thing and get stuck in a boot loop. Didn't try it.
simple_s said:
Please read the tutorial! You need SDK 24 if you are on Android 7.
In my message I stated that I tried both sdk24 and sdk25 neither worked. I only posted the error message for sdk25 but it was the same for 24.
Click to expand...
Click to collapse
y2klol said:
Trying to install sdk25/sdk25 and getting an error:
Wrong Android version:
This file is for: SDK25
Please download the correct package
for your Android version
Failed
Installation error
Click to expand...
Click to collapse
y2klol said:
In my message I stated that I tried both sdk24 and sdk25 neither worked. I only posted the error message for sdk25 but it was the same for 24.
Click to expand...
Click to collapse
In your original post you wrote SDK25 twice. So it is not obvious you meant SDK24 and SDK25.
I'm sorry that it didn't work for you. Did you use all the files in the tutorial? What phone do you have and what Android 7 version?
Is it normal that the system takes a while to boot after flashing no verity no encrypt?
Should i hard reset? It is been like 5 mins
ii_Troy said:
Is it normal that the system takes a while to boot after flashing no verity no encrypt?
Should i hard reset? It is been like 5 mins
Click to expand...
Click to collapse
I had the same issue - turns out I missed the formatting step in TWRP.
Before flashing no verity, go to Wipe > Format Data Partition (I cant remember the exact wording)
simple_s said:
In your original post you wrote SDK25 twice. So it is not obvious you meant SDK24 and SDK25.
I'm sorry that it didn't work for you. Did you use all the files in the tutorial? What phone do you have and what Android 7 version?
Click to expand...
Click to collapse
Oh yes, I did. My apologies. It's A5 (2017) and the firmware is A520FXXS2BQJ1 - Galaxy A5 SM-A520F OPS Australia (Optus). Do I have to use the one posted? What is that?
y2klol said:
Oh yes, I did. My apologies. It's A5 (2017) and the firmware is A520FXXS2BQJ1 - Galaxy A5 SM-A520F OPS Australia (Optus). Do I have to use the one posted? What is that?
Click to expand...
Click to collapse
I only tried this tutorial on an A3. Especially the firmware and the TWRP are specialised for the A3. I think the A5 has also quite a different hardware.
Maybe someone in this thread can help you. They root A5:
A5 Root
All works great on my Galaxy A320FL, thanks !!
atlantix1 said:
Anyway, I face the lockscreen lag even if I use Magisk to root my phone. So, sadly no luck for me...
Click to expand...
Click to collapse
its because you fllashed no verify no encrypt this zip should only be flash when you root with super su ...
am i the only one here finding this tutorial poorly written? example:
"4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System."
if you that and you decide to root with magisk you are fked you are gonna face the lock screen delay after you enter the password.
"5. Copy the XposedInstaller_by_dvdandroid_09_09_17.apk file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP."
do we install it?? do we just leave it there???
"8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed. "
witch means = find the module and install it, then enable it, then reboot. now go to exposed and install it then reboot again, now you do have it.
by the way sorry for my bad english .
Hi there.
I found something interesting by accident.
Maybe it is not necessary to install the Xposed Framework via Magisk.
Just use the Magisk Manager as a Super SU replacement and install the Xposed Framework (latest version is 89) directly via the new Xposed Installer (latest version is 3.1.5).
Official Xposed by rovo89
It seems that the phone is running a little bit smoother.
Also it seems that the boot patch is causing some problems.
Maybe the whole tutorial needs to be overlooked. But unfortunately I have now time right now.
nekos95 said:
am i the only one here finding this tutorial poorly written? example:
"4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System."
if you that and you decide to root with magisk you are fked you are gonna face the lock screen delay after you enter the password.
"5. Copy the XposedInstaller_by_dvdandroid_09_09_17.apk file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP."
do we install it?? do we just leave it there???
"8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed. "
witch means = find the module and install it, then enable it, then reboot. now go to exposed and install it then reboot again, now you do have it.
by the way sorry for my bad english .
Click to expand...
Click to collapse
Sorry to hear that. Maybe you can write a new and better one.
simple_s said:
Sorry to hear that. Maybe you can write a new and better one.
Click to expand...
Click to collapse
i kinda just did ... insteed of being ironic you should fix what you did wrong here , you might not realising this but not everyone here has experience to figure things out by himself and your tutorial is causing issues .
nekos95 said:
am i the only one here finding this tutorial poorly written? example:
"4. Now install via TWRP the Boot image patch no-verity-no-encrypt_ashyx. To do that, just copy the zip file to your SD card. Go to TWRP and install it with the Install option within TWRP. Reboot to System."
if you that and you decide to root with magisk you are fked you are gonna face the lock screen delay after you enter the password.
"5. Copy the XposedInstaller_by_dvdandroid_09_09_17.apk file to your SD card and install the APK. Make sure you have third party sources enabled. Reboot to TWRP."
do we install it?? do we just leave it there???
"8. Open the Magisk Manager and search for Xposed Framework SDK 24. You need the SDK 24 or else it won't work. Install Xposed. "
witch means = find the module and install it, then enable it, then reboot. now go to exposed and install it then reboot again, now you do have it.
by the way sorry for my bad english .
Click to expand...
Click to collapse
Sorry I have to replay again. I had just a few minutes this morning.
At point 5 I clearly wrote that you have to install the apk!
At point 8 it should be clear that you have to follow the instructions from Xposed. Everybody knows that and has nothing to do with the basic tutorial.
nekos95 said:
i kinda just did ... insteed of being ironic you should fix what you did wrong here , you might not realising this but not everyone here has experience to figure things out by himself and your tutorial is causing issues .
Click to expand...
Click to collapse
Xposed, Root and what not is nothing for beginners. I clearly mentioned that you have to read a lot of stuff. This is not for beginners. Instead of whining and telling me how to do stuff, just write your own thread. Link everything and mention resources. Not everything in this world is baby save. You have to educate yourself!
I overlooked the whole tutorial. I think it is better now and baby save.
Hello,
I cannot get this to work.
Flashing Android 7.0 works
Installing TWRP works
Installing the xposed apk works
but after flashing the magisk zip file i get the message "verification failed" when trying to boot
How can i fix this?
Edit: I managed to fix it. I had to format after install TWRP
BananaOctopus said:
Hello,
I cannot get this to work.
Flashing Android 7.0 works
Installing TWRP works
Installing the xposed apk works
but after flashing the magisk zip file i get the message "verification failed" when trying to boot
How can i fix this?
Edit: I managed to fix it. I had to format after install TWRP
Click to expand...
Click to collapse
Thank you for your help. I updated my phone to the newest Android 7 version today. I had the same problem and solved it with your method. So I implemented this step into the tutorial.
Hi all, I would really appreciate some help in understanding the instructions on installing Magisk root, from this thread: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814 I have already unlocked the bootloader and have highlighted the parts I'm confused about in red:
H. Get HWOTA8_Mate10 Package - I downloaded this.
Magisk
A. Install Magisk by running magisk/magisk.bat and follow instructions. - This I'm stuck on. How do I run magisk.bat. Do I simply have to have the phone connected to PC, and then click the magisk.bat file that is in the HWOTA8 package? Does the phone have to be in fastboot mode. is an adb command involved etc?
B. Install Magisk module (Huawei-Prop-Fix-v1.4_2018012501.zip) to fix background root check and result in safetynet failure. Do I do this after Magisk is installed? So I install Magisk manager apk, then I install this module?
THANKS SO MUCH!
A. You need to have the phone connected to the PC in fastboot. You might need the drivers fix, it can be found in the thread. Just run the bat and follow the instructions.
B. Put the zip in your phone after rooting with Magisk, open the Magisk manager app, slide right go to modules and install the zip. Voil
Safe0716 said:
A. You need to have the phone connected to the PC in fastboot. You might need the drivers fix, it can be found in the thread. Just run the bat and follow the instructions.
B. Put the zip in your phone after rooting with Magisk, open the Magisk manager app, slide right go to modules and install the zip. Voil
Click to expand...
Click to collapse
Thanks a ton Safe0716! I just ran the bat now and believe it was successful. I can see the Magisk manager app has been automatically installed (do I need to install something on top of this?).
I have also loaded the zip file onto internal memory, but before I install that zip as a Magisk module, can I ask what the purpose of that zip is?
The instruction says "Install Magisk module (Huawei-Prop-Fix-v1.4_2018012501.zip) to fix background root check and result in safetynet failure" . The way its written makes it sound like the zip will cause it to result in safetynet failure (for some reason) - or is the purpose of the zip to PREVENT safetynet failure?
Thanks again!
shadders said:
Thanks a ton Safe0716! I just ran the bat now and believe it was successful. I can see the Magisk manager app has been automatically installed (do I need to install something on top of this?).
I have also loaded the zip file onto internal memory, but before I install that zip as a Magisk module, can I ask what the purpose of that zip is?
The instruction says "Install Magisk module (Huawei-Prop-Fix-v1.4_2018012501.zip) to fix background root check and result in safetynet failure" . The way its written makes it sound like the zip will cause it to result in safetynet failure (for some reason) - or is the purpose of the zip to PREVENT safetynet failure?
Thanks again!
Click to expand...
Click to collapse
It's meant to prevent safetynet failure. Without flashing this zip you won't be able to hide root for some apps, let's say you won't be able to use snapchat, netflix etc...
shadders said:
Thanks a ton Safe0716! I just ran the bat now and believe it was successful. I can see the Magisk manager app has been automatically installed (do I need to install something on top of this?).
I have also loaded the zip file onto internal memory, but before I install that zip as a Magisk module, can I ask what the purpose of that zip is?
The instruction says "Install Magisk module (Huawei-Prop-Fix-v1.4_2018012501.zip) to fix background root check and result in safetynet failure" . The way its written makes it sound like the zip will cause it to result in safetynet failure (for some reason) - or is the purpose of the zip to PREVENT safetynet failure?
Thanks again!
Click to expand...
Click to collapse
It adds checks that Magisk doesn't check for. Basically Huaweis own props. So it "prevents" failure. It doesn't force safetynet to say OK even though it would fail otherwise, it just adds props to check for that otherwise would make safetynet fail.
And to add to your questions, all bats by mankindtw tell you what to do when you run them, in case you want to use HWOTA8 in the future to update or rebrand.
Safe0716 said:
It's meant to prevent safetynet failure. Without flashing this zip you won't be able to hide root for some apps, let's say you won't be able to use snapchat, netflix etc...
Click to expand...
Click to collapse
Thanks for helping me out Safe0716 I appreciate it I installed the zip and it seems to pass SafetyNet so I'm all set with root (the process was a lot more involved than previous phones I've had but its finally done). Its just a shame that we can't go further and install xposed on this phone!
shadders said:
Thanks for helping me out Safe0716 I appreciate it I installed the zip and it seems to pass SafetyNet so I'm all set with root (the process was a lot more involved than previous phones I've had but its finally done). Its just a shame that we can't go further and install xposed on this phone!
Click to expand...
Click to collapse
Yeah unfortunately it isn't working yet, but I'm sure somebody will figure it out !
ante0 said:
It adds checks that Magisk doesn't check for. Basically Huaweis own props. So it "prevents" failure. It doesn't force safetynet to say OK even though it would fail otherwise, it just adds props to check for that otherwise would make safetynet fail.
And to add to your questions, all bats by mankindtw tell you what to do when you run them, in case you want to use HWOTA8 in the future to update or rebrand.
Click to expand...
Click to collapse
Thanks for that info, I now have a better understanding. And ah in terms the bats, yes I saw when I clicked on it that it did indeed have helpful instructions! But I assumed there was certain things I had to do before running it, e.g. fastboot mode, and so was scared to click on it!
Should be helpful in the future. Now that I am rooted with Magisk, does that mean I can no longer accept OTAs and updates will have to go through HWOTA8? If so, will updating through HWOTA8 wipe the system, or preserve user data? Thanks!
shadders said:
Thanks for that info, I now have a better understanding. And ah in terms the bats, yes I saw when I clicked on it that it did indeed have helpful instructions! But I assumed there was certain things I had to do before running it, e.g. fastboot mode, and so was scared to click on it!
Should be helpful in the future. Now that I am rooted with Magisk, does that mean I can no longer accept OTAs and updates will have to go through HWOTA8? If so, will updating through HWOTA8 wipe the system, or preserve user data? Thanks!
Click to expand...
Click to collapse
I haven't received any yet... But I tend to update as soon as an update is pushed to http://pro-teammt.ru/firmware-database/
which is long before it's actually pushed to the public (long being 2 weeks+).
Userdata is preserved when you update FullOTA updates and bootloader remains unlocked. So you just need to reflash Magisk after it's done updating.
Magisk data (modules) is kept too as that's kept in /data/
Requirements / Downloads
Huawei VTR-L09 with unlocked bootloader (I not tested in other version)
Minimal ADB & Fastboot
Patched Recovery_Ramdisk VTR-L09
Rooting your device
1. Unzip Minimal ADB & Fastboot to any folder of your PC
2. Download the patched file for your device and copy it to Minimal ADB & Fastboot folder.
3. Start your smartphone in fastboot mode pressing [Vol-]+[Power] and connect it to your PC.
4. Open a Powershell window in your Minimal ADB & Fastboot folder by [Shift]+[Rightclick].
5. Flash the Recovery_Ramdisk:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
Adjusting Magisk Manager and patching files by yourself
1. Download Magisk Manager to your phone and install.
2. Check "force encryption" and "AVB 2.0" boxes.
To patch yourself recovery_ramdisk:
3. a) copy the ORIGINAL RECOVERY_RAMDISK VTR-L09 PIE version 9.0.1.165 C432 to anywhere on your P10
b) Patch your *.img, that you have copied in any folder to your smartphone by pressing "Install" --> "Install" --> "Patch boot image" in Magisk Manager.
4. Transfer the patched file (You will find it in your download folder of your smartphone. It will be called "patched_boot.img".) to your PC, start Smartphone in fastboot mode and flash:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
(You must adapt the file name to the real name of your file, e.g. patched_boot.img)
AFTER FLASHING YOUR PATCHED BOOT ON FASTBOOT, UNPLUG YOUR USB, PRESS [VOL+] + [Power], KEEP VOL+ UNTIL REBOOTS, IT WILL REBOOT ON YOUR SYSTEM ROOTED.
To actualize Magisk:
4.b) Choose in Magisk Manager: "Install" --> "Install" --> "Direct Install (Recommended)" --> Restart
espaciosalter20 said:
Requirements / Downloads
Huawei VTR-L09 with unlocked bootloader (I not tested in other version)
Minimal ADB & Fastboot
Patched Recovery_Ramdisk VTR-L09
Rooting your device
1. Unzip Minimal ADB & Fastboot to any folder of your PC
2. Download the patched file for your device and copy it to Minimal ADB & Fastboot folder.
3. Start your smartphone in fastboot mode pressing [Vol-]+[Power] and connect it to your PC.
4. Open a Powershell window in your Minimal ADB & Fastboot folder by [Shift]+[Rightclick].
5. Flash the Recovery_Ramdisk:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
Adjusting Magisk Manager and patching files by yourself
1. Download Magisk Manager to your phone and install.
2. Check "force encryption" and "AVB 2.0" boxes.
To patch yourself recovery_ramdisk:
3. a) copy the ORIGINAL RECOVERY_RAMDISK VTR-L09 PIE version 9.0.1.165 C432 to anywhere on your P10
b) Patch your *.img, that you have copied in any folder to your smartphone by pressing "Install" --> "Install" --> "Patch boot image" in Magisk Manager.
4. Transfer the patched file (You will find it in your download folder of your smartphone. It will be called "patched_boot.img".) to your PC, start Smartphone in fastboot mode and flash:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
(You must adapt the file name to the real name of your file, e.g. patched_boot.img)
AFTER FLASHING YOUR PATCHED BOOT ON FASTBOOT, UNPLUG YOUR USB, PRESS [VOL+] + [Power], KEEP VOL+ UNTIL REBOOTS, IT WILL REBOOT ON YOUR SYSTEM ROOTED.
To actualize Magisk:
4.b) Choose in Magisk Manager: "Install" --> "Install" --> "Direct Install (Recommended)" --> Restart
Click to expand...
Click to collapse
hi, I followed your guide, the root with magisk works, but the display at the extreme edges left and right are not working at touch.
do you have any advice for me.
Thank you
L29
Guide works fine with L29 too, sent email with patched recovery to OP.:good:
Worked on my VKY-L29, thanks a lot!
Update: Need some help! After any reboot magisk uninstall itself and lose the root, so it's impossible to install any module since I need to restart after installing them. Anyone with this problem? Someone knows what can it be causing this?
Piombofed said:
hi, I followed your guide, the root with magisk works, but the display at the extreme edges left and right are not working at touch.
do you have any advice for me.
Thank you
Click to expand...
Click to collapse
Idem here with my p10 vtr-l09c432 with firmware 9.0.1.163.
If i boot normal, i have android 9 without root and touch work fine.
If i boot with [vol+] + [power] from recovery workaround android start with right privileges and magisk work fine but from now the touchscreen no work at extreme left and right border for all height display, boring problem in keyboard and navigation top bar.
ps: i have manual patched my original extract recovery_ramdisk.img from update.app with magisk 18 and beta19, some result.
_neoxxx_ said:
Idem here with my p10 vtr-l09c432 with firmware 9.0.1.163.
If i boot normal, i have android 9 without root and touch work fine.
If i boot with [vol+] + [power] from recovery workaround android start with right privileges and magisk work fine but from now the touchscreen no work at extreme left and right border for all height display, boring problem in keyboard and navigation top bar.
ps: i have manual patched my original extract recovery_ramdisk.img from update.app with magisk 18 and beta19, some result.
Click to expand...
Click to collapse
Try also to report the problem directly on the magisk developer's forum, maybe if many of them report it, you can try to correct or make a Patch.
_neoxxx_ said:
Idem here with my p10 vtr-l09c432 with firmware 9.0.1.163.
If i boot normal, i have android 9 without root and touch work fine.
If i boot with [vol+] + [power] from recovery workaround android start with right privileges and magisk work fine but from now the touchscreen no work at extreme left and right border for all height display, boring problem in keyboard and navigation top bar.
ps: i have manual patched my original extract recovery_ramdisk.img from update.app with magisk 18 and beta19, some result.
Click to expand...
Click to collapse
I've seen this before on custom ROMs; the workaround I've used is, as root:
stop aptouch
If that does it, a magisk module that provides an empty file for /vendor/bin/aptouch_daemon (or a late start script that runs the above command) would correct it as well.
irony_delerium said:
I've seen this before on custom ROMs; the workaround I've used is, as root:
stop aptouch
......
Click to expand...
Click to collapse
You are rock bro!!
"stop aptouch" executed from root shell terminal work like a charm and touchscreen work again.
I reply with this solution in my open issues on official magisk github.
.. go to automate this at boot.
Now my question is: why aptouch is involved in root privilege escalation?
Update: i just add this to /system/etc/init/init.system.rc at end of file:
Code:
# Aptouch_daemon fix
service aptouch /system/bin/true
class late_start
disabled
oneshot
.. now at every boot my touch work again.
Does this problem appear for every vtl l29?
Do I have to invoke the command every boot?
Do this kind of "dual boot" will be "fixed"?
I hope will be fixed if possible, or rooting on pie will be annoying
RealPsygnosis said:
...
Do I have to invoke the command every boot?
Do this kind of "dual boot" will be "fixed"?
I hope will be fixed if possible, or rooting on pie will be annoying
Click to expand...
Click to collapse
.. Why? i reboot my phone every 3/4 weeks.
Only plus [vol+]..
No twrp or root annoying..
_neoxxx_ said:
You are rock bro!!
"stop aptouch" executed from root shell terminal work like a charm and touchscreen work again.
I reply with this solution in my open issues on official magisk github.
.. go to automate this at boot.
Now my question is: why aptouch is involved in root privilege escalation?
Update: i just add this to /system/etc/init/init.system.rc at end of file:
Code:
# Aptouch_daemon fix
service aptouch /system/bin/true
class late_start
disabled
oneshot
.. now at every boot my touch work again.
Click to expand...
Click to collapse
Congratulations, with stop aptouch magisk and touch working perfectly, the only problem with the script, copying and pasting doesn't work for me .. Do you have a solution? Thank you
Sorry for my English
Edit: I was writing the script directly from the phone, doing from pc now works perfectly..Thanks a lot
_neoxxx_ said:
You are rock bro!!
"stop aptouch" executed from root shell terminal work like a charm and touchscreen work again.
I reply with this solution in my open issues on official magisk github.
.. go to automate this at boot.
Now my question is: why aptouch is involved in root privilege escalation?
Update: i just add this to /system/etc/init/init.system.rc at end of file:
.. now at every boot my touch work again.
Click to expand...
Click to collapse
I don't think it's that it's involved in root. It's probably that something else isn't processed quite correctly, but I haven't figured out what yet myself. I've just disabled it in all of my custom builds since I determined that was causing problems and didn't seem to provide any functionality to a custom ROM, and it doesn't end up causing any problems.
That init snippet is actually pretty much the same as I use for disabling it. (You don't actually need to append it to an existing file, either - you can create a new one in /system/etc/init, so long as it has the '.rc' extension it'll be picked up by init.)
Root huawei p10 plus.
Hi guys. I read the guide to root my huawei p10 plus. But this is possible without bootloader unlock, or I need to first enable the bootloader unlock? Thank you soo much. Cheers
---------- Post added at 02:23 PM ---------- Previous post was at 02:19 PM ----------
Hello guys. I read the guide to root my huawei p10 plus, but I need to unlock bootloader first or I can do it with a bootloader disable? Thank you so much. Cheers
A way to install zips ??
Hi all guys, I followed this guide to root my P10 vtr-l09 with PIE and it works actually everything like a glance. I also edit init script for fixing the touch problem when started as root, thank to you all!!
But I wonder how I can install an installable .zip, for instance, with this configuration.
In other words ... In Oreo I had my device rooted, and I had TWRP 3.2.1 + Magisk. When I wanted to flash any installable .zip, I booted in twrp and install. Now, since I didn't find a TWRP 3.2.3+ suitable for Vtr-L09 (for Pie), I used this method for rooting my device .. but I can't install a flashable .zip as I wish.
Any suggestions?
( Sorry if this may appear as a dumb question to anybody... :laugh: )
Thanks in advance, and thanks for your hard work.
G.
Hello,
I'm unable to modify the init.system.rc file.
I tried nano directly on the phone (with su before) => Read-only file system
I tried with my computer (with su before) => Read-only file system
How do you mofify it please ?
Christian
---------- Post added at 12:50 PM ---------- Previous post was at 12:37 PM ----------
christrodr said:
Hello,
I'm unable to modify the init.system.rc file.
I tried nano directly on the phone (with su before) => Read-only file system
I tried with my computer (with su before) => Read-only file system
How do you mofify it please ?
Christian
Click to expand...
Click to collapse
Solved using a file explorer.
But why can't we do this via the commandline and su ?
Christian.
christrodr said:
Hello,
I'm unable to modify the init.system.rc file.
I tried nano directly on the phone (with su before) => Read-only file system
I tried with my computer (with su before) => Read-only file system
How do you mofify it please ?
Christian
---------- Post added at 12:50 PM ---------- Previous post was at 12:37 PM ----------
Solved using a file explorer.
But why can't we do this via the commandline and su ?
Christian.
Click to expand...
Click to collapse
You can - but you have to make sure that system is mounted r/w. A file explorer will remount the filesystem for writing so it can modify the file. And, of course, on the command line, you're best off doing it through /sbin/.core/mirror/system (iirc), not /system - you may end up modifying the tmpfs mounted by Magisk depending on what you've got installed as far as modules go.
irony_delerium said:
You can - but you have to make sure that system is mounted r/w. A file explorer will remount the filesystem for writing so it can modify the file. And, of course, on the command line, you're best off doing it through /sbin/.core/mirror/system (iirc), not /system - you may end up modifying the tmpfs mounted by Magisk depending on what you've got installed as far as modules go.
Click to expand...
Click to collapse
Ok,
Thanks for the explanation.
gabolander said:
Hi all guys, I followed this guide to root my P10 vtr-l09 with PIE and it works actually everything like a glance. I also edit init script for fixing the touch problem when started as root, thank to you all!!
But I wonder how I can install an installable .zip, for instance, with this configuration.
In other words ... In Oreo I had my device rooted, and I had TWRP 3.2.1 + Magisk. When I wanted to flash any installable .zip, I booted in twrp and install. Now, since I didn't find a TWRP 3.2.3+ suitable for Vtr-L09 (for Pie), I used this method for rooting my device .. but I can't install a flashable .zip as I wish.
Any suggestions?
( Sorry if this may appear as a dumb question to anybody... [emoji23] )
Thanks in advance, and thanks for your hard work.
G.
Click to expand...
Click to collapse
Any suggestions?
Inviato dal mio VTR-L09 utilizzando Tapatalk
gabolander said:
Any suggestions?
Inviato dal mio VTR-L09 utilizzando Tapatalk
Click to expand...
Click to collapse
Go to the mate9 forums and find unofficial build topic for RR, in that topic you have twrp which works on P10 but just for .zip installation. Backup doesn't work because of encryption and i didn't tried .img installation.
Here is the link to topic: https://forum.xda-developers.com/mate-9/development/rom-resurrection-remix-v7-0-t3911232
Papolak said:
Guide works fine with L29 too, sent email with patched recovery to OP.:good:
Click to expand...
Click to collapse
can you send em here too ?? this is my telegram acc https://t.me/d0nf1rd