install supersu on redmi 8a? - Xiaomi Redmi 8A Questions & Answers

Can Redmi 8a be installed Supersu? I've tried many times, the twrp flash process was successful, but there was no change at all, not even rooted.

oimumio said:
Can Redmi 8a be installed Supersu? I've tried many times, the twrp flash process was successful, but there was no change at all, not even rooted.
Click to expand...
Click to collapse
magisk necessary. at the same time you need to patch the boot https://patcher.yaalex.tk/
Sorry for my bad english. I am not literate and in Russian )))

before that I say thank you for your answer, dmitrypershin2015. Nice to meet you.
I tried root with magisk and it really works. but for my application, I can't get deeper access to the system if I use Magisk.

oimumio said:
before that I say thank you for your answer, dmitrypershin2015. Nice to meet you.
I tried root with magisk and it really works. but for my application, I can't get deeper access to the system if I use Magisk.
Click to expand...
Click to collapse
turn off the modules and turn on the mode ,, core " the Magisk Manager
Sorry for my bad english. I am not literate and in Russian )))

thank you for your answer, dmitrypershin2015.
I removed the module and activated core only mode, but I still can't access the system...

oimumio said:
thank you for your answer, dmitrypershin2015.
I removed the module and activated core only mode, but I still can't access the system...
Click to expand...
Click to collapse
what is your specific problem? and you boot.img patches?
Sorry for my bad english. I am not literate and in Russian )))

dmitrypershin2015 said:
what is your specific problem? and you boot.img patches?
Sorry for my bad english. I am not literate and in Russian )))
Click to expand...
Click to collapse
there is no su folder in the system root that will be run by my application. Magisk did not create the folder. I think so.
I've made patched_boot.img from https://patcher.yaalex.tk/. boot file that I took from /dev/block/by-name/boot.img
but, I will try to make a command in my application running android cmd to copy the files that I need into the executable folder.

oimumio said:
there is no su folder in the system root that will be run by my application. Magisk did not create the folder. I think so.
I've made patched_boot.img from https://patcher.yaalex.tk/. boot file that I took from /dev/block/by-name/boot.img
but, I will try to make a command in my application running android cmd to copy the files that I need into the executable folder.
Click to expand...
Click to collapse
what does the magisk manager show?
Sorry for my bad english. I am not literate and in Russian )))
---------- Post added at 01:16 PM ---------- Previous post was at 01:13 PM ----------
oimumio said:
there is no su folder in the system root that will be run by my application. Magisk did not create the folder. I think so.
I've made patched_boot.img from https://patcher.yaalex.tk/. boot file that I took from /dev/block/by-name/boot.img
but, I will try to make a command in my application running android cmd to copy the files that I need into the executable folder.
Click to expand...
Click to collapse
On some new build rom, writing to the ,, vendor "section is not possible without disabling encryption through the patch
Sorry for my bad english. I am not literate and in Russian )))

dmitrypershin2015 said:
what does the magisk manager show?
Sorry for my bad english. I am not literate and in Russian )))
---------- Post added at 01:16 PM ---------- Previous post was at 01:13 PM ----------
On some new build rom, writing to the ,, vendor "section is not possible without disabling encryption through the patch
Sorry for my bad english. I am not literate and in Russian )))
Click to expand...
Click to collapse
magisk creates a folder with the name sbin, not su. I think so, the su folder created by Magisk is Sbin.
And I rooted my device not to install ROMs other than stock ROMs that were given from Xiaomi.
by the way, thanks for all your suggestions.

Related

[FLASHABLE MOD] {ALL} Viper4Arise Magisk Simple installer

Viper4Arise
This is a universal flashable zip for viper4arise / viper4andoird and will require your device to be running Magisk for this to work.
This is the latest build of the viper4arise.apk + the 2.5.0.4 Drivers (packed by topjohnwu )
What this flashable zip includes:​
Code:
*Viper4Arise.Apk
*Viper4Android Drivers ( Requires a Magisk Rom) V 2.5.0.4 but topjohnwu mislabeled as 2.5.0.5
*Viper4Arise - Profiles
*Viper4Arise - DDC
*Viper4Arise - Kernel
Just go ahead and flash this via TWRP and re-boot, you should now have a Viper-app The Magisk module and all the profiles ready to go and no additional setup needed.
Credits go to @topjohnwu and the Arise team that made all this happen, just a easy zip of the stuff for anyone who has had trouble doing the work manually.
Download Link :
https://www.androidfilehost.com/?fid=529152257862713236
sources:
Viper4Arise:
https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Magisk:
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
No mirrors found on download.. Gonna keep trying
---------- Post added at 02:47 AM ---------- Previous post was at 02:40 AM ----------
storm68 said:
No mirrors found on download.. Gonna keep trying
Click to expand...
Click to collapse
Tried it. File downloaded as corrupt
storm68 said:
No mirrors found on download.. Gonna keep trying
---------- Post added at 02:47 AM ---------- Previous post was at 02:40 AM ----------
Tried it. File downloaded as corrupt
Click to expand...
Click to collapse
If you feel like it, you can extract the zip and then re-zip it. The contents are fine, but the zip itself isn't working.
uploaded the wrong zip. sorry guys
correct link is updated in OP, The zip should be ViperAllinONE.zip
again my fault, i uploaded the drivers only zip that was faulty lol
No mirrors found again.... Very weird.
storm68 said:
No mirrors found again.... Very weird.
Click to expand...
Click to collapse
androidfilehost is having problems i just kept trying till they showed up
jerrycoffman45 said:
androidfilehost is having problems i just kept trying till they showed up
Click to expand...
Click to collapse
Got it!
---------- Post added at 11:46 PM ---------- Previous post was at 11:04 PM ----------
You said magisk module? I don't see any in magisk. Am I doing something wrong... Everything else is fine.
storm68 said:
Got it!
---------- Post added at 11:46 PM ---------- Previous post was at 11:04 PM ----------
You said magisk module? I don't see any in magisk. Am I doing something wrong... Everything else is fine.
Click to expand...
Click to collapse
you have to be on a Magisk rom, or flash Magisk version 11.6 from its thread to use this, as i relys on Magisk for the drivers to be installed.
Viper4Arise's packages are flash-able as is without Magisk, but for myself and LS997 handset they caused issues, required selinux set to permissive, and it would seem like it would get randomly disabled after a song change and being very un-reliable. The app, the profiles the kernel and ddc all come from my zip the magisk part is not included with this mod.
storm68 said:
Got it!
---------- Post added at 11:46 PM ---------- Previous post was at 11:04 PM ----------
You said magisk module? I don't see any in magisk. Am I doing something wrong... Everything else is fine.
Click to expand...
Click to collapse
you have to be on a Magisk rom, or flash Magisk version 11.6 from its thread to use this, as i relys on Magisk for the drivers to be installed.
Viper4Arise's packages are flash-able as is without Magisk, but for myself and LS997 handset they caused issues, required selinux set to permissive, and it would seem like it would get randomly disabled after a song change and being very un-reliable. The app, the profiles the kernel and ddc all come from my zip the magisk part is not included with this mod.
Magisk can be found here : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
should be able to flash it overtop of any rom and it work fine, if you have superuser it will use it as the root method, if you have nothing it will root your phone and provide magisksu for root management. Magisksu is considered fully system-less root, where supersu is a system modification, Supersu changed ownership late last year and is now owned by a Company and not a XDA dev and seems to be becoming a OLD root method. Magisk has been named the new root method by many as it can pass safety-net checks, provide root and work with almost all the current root stuff, but done a slighly diffrent way. Some old root apps may have issues with system-less and thats on the app devs to get their apps updated to support 2017 root methods.
Team DevDigitel said:
you have to be on a Magisk rom, or flash Magisk version 11.6 from its thread to use this, as i relys on Magisk for the drivers to be installed.
Viper4Arise's packages are flash-able as is without Magisk, but for myself and LS997 handset they caused issues, required selinux set to permissive, and it would seem like it would get randomly disabled after a song change and being very un-reliable. The app, the profiles the kernel and ddc all come from my zip the magisk part is not included with this mod.
Magisk can be found here : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
should be able to flash it overtop of any rom and it work fine, if you have superuser it will use it as the root method, if you have nothing it will root your phone and provide magisksu for root management. Magisksu is considered fully system-less root, where supersu is a system modification, Supersu changed ownership late last year and is now owned by a Company and not a XDA dev and seems to be becoming a OLD root method. Magisk has been named the new root method by many as it can pass safety-net checks, provide root and work with almost all the current root stuff, but done a slighly diffrent way. Some old root apps may have issues with system-less and thats on the app devs to get their apps updated to support 2017 root methods.
Click to expand...
Click to collapse
Great info. Thanks
I flashed this, but Viper isn't processing
aaronfrickinaustin said:
I flashed this, but Viper isn't processing
Click to expand...
Click to collapse
Yep, same issue as the original magisk port. I have to use a combination of the old system install zip and this module to get viper to process audio. Probably because there are a bunch of audio conf files missing from the ported version.
Florian:
I have a LG G7 and have flashed the last version of viper4arise. Now I have the problem that the drivers are indeed active, but it comes only disturbing noises. as if you connect a plug incorrectly in a system.
the magisk modules do not sound good to me. That sounds like you're constantly switching between loud and quiet. So like constant fluctuations

[Q] Hot to Root Lava A97

Hi,
I am Using LAVA A97 device recently launched. I need to root this mobile to apply some tweaks. I tried various methods like flashing the zip from the SD card and sideload. The error I got always is "Signature Verification Failed". I tried finding custom recoveries and even tried porting custom recoveries but all stopped at the boot image.
Please help me to root this device or port me a custom recovery. I will provide you the files you needed.
Have you tried enabling OEM bootloader setting in developer options?
vshlkmr said:
Have you tried enabling OEM bootloader setting in developer options?
Click to expand...
Click to collapse
Ya I allowed oem unlocking in developer options. But when i boot to fastboot mode and enter command
Code:
fastboot oem unlock
it struck on the boot screen. I have waited for an hour but nothing happened. I just removed battery and rebooted my mobile.
I can give you the stock rom can you make it pre rooted
Please tell me the procedure to add su files in marshmallow system.img and flash it
Bro, I used to root androids way before, then I moved to windows phone and have just recently bought this lava a97. Although I can give you an easiest way to root a device, you can try it with this phone and let me know if it works.
Find a stock rom of any device you want to root, extract the boot.img (use cygwin if you are on windows), there will be a line "ro_secure=1" just change the one to zero, repack the boot.img and either reflash the entire modified rom or just the boot.img.
Then you can simply install super su and then any root checker app to see if the phone is rooted.
Although this method used to work flawlessly on indian branded phones running android 4 series but not sure it will work now, but it's worth a try.
---------- Post added at 08:51 AM ---------- Previous post was at 08:46 AM ----------
karljsamuel said:
Please tell me the procedure to add su files in marshmallow system.img and flash it
Click to expand...
Click to collapse
Rooted phones use su binaries (small block of codes that perform a specialized function) which are granted to be used by any other app that requires them through superuser app. Just pushing in the superuser app won't give you root, you also need those binaries (which on various phones are transfered via adb or through zip flashing into the /bin directory)
---------- Post added at 08:55 AM ---------- Previous post was at 08:51 AM ----------
You can do one thing, extract the stock rom, extract the system.img partition, and then copy the binaries directly to the /bin folder (you can lift those binaries from any rooting zip file from the corresponding bin folder), then copy the superuser app to /system/apk , repack everything, then edit the boot.img as I told earlier, then flash this modified rom onto the phone.
---------- Post added at 08:58 AM ---------- Previous post was at 08:55 AM ----------
Try googling for cygwin, if you are running Windows 10 x64 bit, you can also enable bash for ubuntu... These tools will make packing, editing and repacking of the images easier, but am not sure how to flash the image again back onto the phone
vshlkmr said:
Bro, I used to root androids way before, then I moved to windows phone and have just recently bought this lava a97. Although I can give you an easiest way to root a device, you can try it with this phone and let me know if it works.
Find a stock rom of any device you want to root, extract the boot.img (use cygwin if you are on windows), there will be a line "ro_secure=1" just change the one to zero, repack the boot.img and either reflash the entire modified rom or just the boot.img.
Then you can simply install super su and then any root checker app to see if the phone is rooted.
Although this method used to work flawlessly on indian branded phones running android 4 series but not sure it will work now, but it's worth a try.
---------- Post added at 08:51 AM ---------- Previous post was at 08:46 AM ----------
Rooted phones use su binaries (small block of codes that perform a specialized function) which are granted to be used by any other app that requires them through superuser app. Just pushing in the superuser app won't give you root, you also need those binaries (which on various phones are transfered via adb or through zip flashing into the /bin directory)
---------- Post added at 08:55 AM ---------- Previous post was at 08:51 AM ----------
You can do one thing, extract the stock rom, extract the system.img partition, and then copy the binaries directly to the /bin folder (you can lift those binaries from any rooting zip file from the corresponding bin folder), then copy the superuser app to /system/apk , repack everything, then edit the boot.img as I told earlier, then flash this modified rom onto the phone.
---------- Post added at 08:58 AM ---------- Previous post was at 08:55 AM ----------
Try googling for cygwin, if you are running Windows 10 x64 bit, you can also enable bash for ubuntu... These tools will make packing, editing and repacking of the images easier, but am not sure how to flash the image again back onto the phone
Click to expand...
Click to collapse
I tried the above mentioned steps in my Ubuntu 16.04 with Android Kitchen and Superr's Kitchen. With Android kitchen, I unpacked the system.img and the kitchen made the boot image and made the ro.secure=0. Then I added the necessory files from @Chainfire SuperSU.zip as per the update-binary script mentioned and repacked system.img with Superr's Kitchen. When I flashed modified system.img and boot.img with flash tool.
The superSU app said that su binaries are not installed and it cant install them also it asked me to reroot the mobile phone.
I also tried with Dirtycow exploit also but not worked.
Mobile is running Marshmallow API 23
Can you make me a custom recovery. I followed the steps mentioned in this forum to port a custom recovery but it struck in the boot logo.
The Stock Firmware file Now I have in my mobile can be downloded from Google Drive.
Boot.img Recovery.img and build.prop file is uploaded as Zip to Google Drive
How are you flashing the files back to phone? What software you using? And maybe superuser cannot find the binaries bcoz maybe lava a97 picks it's binaries from someplace else (like maybe /system/bin)
vshlkmr said:
How are you flashing the files back to phone? What software you using? And maybe superuser cannot find the binaries bcoz maybe lava a97 picks it's binaries from someplace else (like maybe /system/bin)
Click to expand...
Click to collapse
Flashed with SPD upgrade tool.
The su binaries and apk files are placed as mentioned by chainfire in the update-binary provided by him for flashing the zip via custom recovery.
It told me to run su --install but the adb shell does not work after customising the rom
karljsamuel said:
Flashed with SPD upgrade tool.
The su binaries and apk files are placed as mentioned by chainfire in the update-binary provided by him for flashing the zip via custom recovery.
It told me to run su --install but the adb shell does not work after customising the rom
Click to expand...
Click to collapse
Is USB debugging enabled?? Also switch the phone to cd rom and install the drivers
While installing the modified system.img it give me error
- exec '/system/bin/sh' failed: No such file or directory (2) -
Even there is no such file in the stock rom. only a file named sh0 was present
I reflashed the rom and adb shell is working properly without the /system/bin/sh file
How to root lava a97
Hey bro I read your thread and also I myself tried many ways to root my lava a97
Did u got any method to root it??
Please tell
karljsamuel said:
Ya I allowed oem unlocking in developer options. But when i boot to fastboot mode and enter command
Code:
fastboot oem unlock
it struck on the boot screen. I have waited for an hour but nothing happened. I just removed battery and rebooted my mobile.
I can give you the stock rom can you make it pre rooted
Click to expand...
Click to collapse
Lava A97 is CortexA7 device
use fastboot tools to flash TWRP and then flash SuperSU.zip
I'm gonna port TWRP for Lava A97 soon
And will test it.
pm me and I'll give you TWRP after success in testing
OK?
---------- Post added at 09:40 AM ---------- Previous post was at 09:35 AM ----------
vshlkmr said:
Bro, I used to root androids way before, then I moved to windows phone and have just recently bought this lava a97. Although I can give you an easiest way to root a device, you can try it with this phone and let me know if it works.
Find a stock rom of any device you want to root, extract the boot.img (use cygwin if you are on windows), there will be a line "ro_secure=1" just change the one to zero, repack the boot.img and either reflash the entire modified rom or just the boot.img.
Then you can simply install super su and then any root checker app to see if the phone is rooted.
Although this method used to work flawlessly on indian branded phones running android 4 series but not sure it will work now, but it's worth a try.
---------- Post added at 08:51 AM ---------- Previous post was at 08:46 AM ----------
Rooted phones use su binaries (small block of codes that perform a specialized function) which are granted to be used by any other app that requires them through superuser app. Just pushing in the superuser app won't give you root, you also need those binaries (which on various phones are transfered via adb or through zip flashing into the /bin directory)
---------- Post added at 08:55 AM ---------- Previous post was at 08:51 AM ----------
You can do one thing, extract the stock rom, extract the system.img partition, and then copy the binaries directly to the /bin folder (you can lift those binaries from any rooting zip file from the corresponding bin folder), then copy the superuser app to /system/apk , repack everything, then edit the boot.img as I told earlier, then flash this modified rom onto the phone.
---------- Post added at 08:58 AM ---------- Previous post was at 08:55 AM ----------
Try googling for cygwin, if you are running Windows 10 x64 bit, you can also enable bash for ubuntu... These tools will make packing, editing and repacking of the images easier, but am not sure how to flash the image again back onto the phone
Click to expand...
Click to collapse
Thanks alot bro???
TWRP port test failed
Hey bro i have rooted my lava a97 IPS
Recovery- cyanogen recovery ported by me
And flash super su
Can anyone Provide me the recovery & Su files Please?
---------- Post added at 04:42 AM ---------- Previous post was at 04:40 AM ----------
Mrutunjaya said:
Hey bro i have rooted my lava a97 IPS
Recovery- cyanogen recovery ported by me
And flash super su
Click to expand...
Click to collapse
I Also Want 2 Root My Device Please Can U Help Me?

Easy Upgrade to Unapproved EMUI 5 Update

Sometimes Huawei releases an update package without approving it. For instance, my device (VIE-L29C636) is getting a B382 update, but the update isn't approved for installation. Here's how to update to those update packages.
NOTE: Using this method, you can also safely upgrade your device even if it is rooted, or has some files system partitions altered. (Of course after finished this process, your device will become unrooted and any alteration to the system partitions mentioned below will revert).
Prerequisites:
Your device is already running EMUI 5 (do not attempt this procedure on EMUI 4 ROM, as the partition layout may differ, and the various firmware (modem, sensor hub, etc.) may not compatible.
Unlocked Bootloader AND FRP.
Latest TWRP from OpenKirin (more on that, including download link, click here).
Huawei Update Extractor, for extracting UPDATE.APP.
imgtool, to convert the sparse android image into an ext4 raw image file.
Method:
Download your preferred update package from Firmware Finder app (Make sure to select the one which has 'FullOTA' designation on it. The package doesn't have to be a 'PV' package). Choose 'update.zip' and the other zip that has your region name on it (for instance, on my C636, look for the zip which has 'spcseas' on it's name). I will refer this 2nd zip as 'regional zip'.
Extract the 'UPDATE.APP' from both zip archive.
Using the Update Extractor on a Windows PC, Extract BOOT, SYSTEM, PRODUCT and VENDOR partitions from UPDATE.APP retrieved from 'update.zip', and extract CUST and VERSION from UPDATE.APP retrieved from your regional zip. You should end up with BOOT.IMG, SYSTEM.IMG, PRODUCT.IMG, VENDOR.IMG, CUST.IMG and VERSION.IMG.
Convert PRODUCT.IMG, VENDOR.IMG and VERSION.IMG to an ext4 image using imgtool, for example:
Code:
imgtool PRODUCT.IMG extract
Beware of overwriting the converted image. imgtool is hardcoded to output the converted file to 'extracted/image.img' folder. ALWAYS rename the image.img to something like 'product.ext4.img' after conversion.
Reboot your device to bootloader mode. Flash BOOT.IMG, SYSTEM.IMG and CUST.IMG via fastboot. For example:
Code:
fastboot flash boot BOOT.IMG
Reboot your device to recovery mode. Type
Code:
fastboot reboot
and hold the Vol Up button on your device to enter recovery mode.
Upload the *.ext4.img converted earlier to your device (doesn't matter where, but I recommend using a safe place like '/sdcard', or USB OTG or external micro SD card). you can use 'adb push', MTP or OTG to upload/copy the ext4.img files to your device.
for each *.ext4.img files, flash it to the appropriate named partitions in
Code:
/dev/block/platform/hi_mci.0/by-name/*
. You can use adb shell on your PC, and a command line program called dd on your device. For faster transfer, try to adjusting the block size to 8M. Example commands (execute from adb shell):
Code:
dd if=/sdcard/product.ext4.img bs=8M of=/dev/block/platform/hi_mci.0/by-name/product
dd if=/sdcard/vendor.ext4.img bs=8M of=/dev/block/platform/hi_mci.0/by-name/vendor
dd if=/sdcard/version.ext4.img bs=8M of=/dev/block/platform/hi_mci.0/by-name/version
Exit TWRP (reboot to system), wait for several minutes for the system to build up it's AOT cache, and enjoy your new EMUI 5 with newer security patch, newer kernel and various features and bug fixes .
EDIT: I apologize that IMGTOOL isn't available in binary form for windows. You can try to use Linux virtual machines to run the IMGTOOL. Any modern GNU/Linux distro should be able to run the IMGTOOL.
Be Alert, by follow this so called "Easy Upgrade", you need to full backup of your data. It is because after upgrade, all data will be reset.
jhleo1 said:
Be Alert, by follow this so called "Easy Upgrade", you need to full backup of your data. It is because after upgrade, all data will be reset.
Click to expand...
Click to collapse
In my case (upgrading from VIE-L29C636B370 to B382), it doesn't erase user data at all. And there is no reason it should erase the data.
But as always, backup your data before performing this procedure, in case something goes wrong.
How to extract product version Vendors use imgtool..
syaif fabian said:
How to extract product version Vendors use imgtool..
Click to expand...
Click to collapse
I'm sorry, I forgot to mention that IMGTOOL is only available as binary in GNU/Linux OS. I think you have to use a VM running a GNU/Linux distro to extract product.img, version.img and/or vendor.img using the IMGTOOL.
@jnakoda
Thank you so much my friend. I was in great trouble as my System Update, File Explorer and Huawei ID apps was deleted from phone due to some experiment. I followed your guide and successfully flashed rom again and boom I got all files back.
Now going to experiment this on B382 firmware
And for those who are curious about this, I successfully used this process for 'meafnaf' region on P9 Plus (VIE-L29)
Once again thanks a lot @jnakoda
---------- Post added at 09:15 PM ---------- Previous post was at 09:10 PM ----------
syaif fabian said:
How to extract product version Vendors use imgtool..
Click to expand...
Click to collapse
imgtool is for converting .img files to ext4 raw image files.
To extract files, you need to use "Huawei Update Extractor" which is mentioned in OP.
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
jhleo1 said:
Be Alert, by follow this so called "Easy Upgrade", you need to full backup of your data. It is because after upgrade, all data will be reset.
Click to expand...
Click to collapse
I confirm in my case (reflashing VIE-L29C185B380), data was not removed. But its better to backup your data first.
faakher said:
@jnakoda
Thank you so much my friend. I was in great trouble as my System Update, File Explorer and Huawei ID apps was deleted from phone due to some experiment. I followed your guide and successfully flashed rom again and boom I got all files back.
Now going to experiment this on B382 firmware
And for those who are curious about this, I successfully used this process for 'meafnaf' region on P9 Plus (VIE-L29)
Once again thanks a lot @jnakoda
---------- Post added at 09:15 PM ---------- Previous post was at 09:10 PM ----------
imgtool is for converting .img files to ext4 raw image files.
To extract files, you need to use "Huawei Update Extractor" which is mentioned in OP.
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
I confirm in my case (reflashing VIE-L29C185B380), data was not removed. But its better to backup your data first.
Click to expand...
Click to collapse
Good Evening i had tried the guide but in my VIE-L09 doesn't work. What can i do? Bootloop infinity
This is easier: https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
Image works on P9 Plus too. Used it for VIE-L09C432B380.
great post, but as a simple user, i have no idea how to do this steps.
i have a p9 plus c605 b361 and rooted, and i cant update to anything
Every time I want to update to a newer version do I need to repeat the steps?
Or I can directly install new updates from finder without confirmation?
maahmd said:
Every time I want to update to a newer version do I need to repeat the steps?
Or I can directly install new updates from finder without confirmation?
Click to expand...
Click to collapse
heeey...anyone here ?!!?
For Windows users, you can use https://github.com/KinglyWayne/simg2img_win (works great).
maahmd said:
Every time I want to update to a newer version do I need to repeat the steps?
Or I can directly install new updates from finder without confirmation?
Click to expand...
Click to collapse
AYahooo said:
For Windows users, you can use https://github.com/KinglyWayne/simg2img_win (works great).
Click to expand...
Click to collapse
what this is ?!
---------- Post added at 06:51 PM ---------- Previous post was at 06:45 PM ----------
Steve2016 said:
This is easier: https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
Image works on P9 Plus too. Used it for VIE-L09C432B380.
Click to expand...
Click to collapse
What version? EVA L09: eva_l09b391_nocheckrecovery.img, or EVA L19: eva_l19b391_nocheckrecovery.img ??
maahmd said:
What version? EVA L09: eva_l09b391_nocheckrecovery.img, or EVA L19: eva_l19b391_nocheckrecovery.img ??
Click to expand...
Click to collapse
If this Recovery by Atarii really work on VIE too - it's logical that you use for VIE-L09 the L09 version of this recovery
Steve2016 said:
This is easier: https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
Image works on P9 Plus too. Used it for VIE-L09C432B380.
Click to expand...
Click to collapse
Tecalote said:
If this Recovery by Atarii really work on VIE too - it's logical that you use for VIE-L09 the L09 version of this recovery
Click to expand...
Click to collapse
I know this but I have a version vie-l29c185 So I do not know which version I chose
maahmd said:
I know this but I have a version vie-l29c185 So I do not know which version I chose
Click to expand...
Click to collapse
If you would say earlier which version you have and if you would search a little bit, then you can find L29:
https://forum.xda-developers.com/showpost.php?p=75234976&postcount=62
Tecalote said:
If you would say earlier which version you have and if you would search a little bit, then you can find L29:
https://forum.xda-developers.com/showpost.php?p=75234976&postcount=62
Click to expand...
Click to collapse
i well try this or this now https://forum.xda-developers.com/p9-plus/how-to/easy-upgrade-to-unapproved-emui-5-update-t3649532
maahmd said:
i well try this or this now https://forum.xda-developers.com/p9-plus/how-to/easy-upgrade-to-unapproved-emui-5-update-t3649532
Click to expand...
Click to collapse
Try it with the Link I give you.
There's no risk. If it works is good, if not, nothing will be changed. (only Recovery, which can be changed after)
Tecalote said:
Try it with the Link I give you.
There's no risk. If it works is good, if not, nothing will be changed. (only Recovery, which can be changed after)
Click to expand...
Click to collapse
Ok i will do it now if it does not work ..do you have a download link RECOVRY bised for p9 plus ?
Or I will pull it out of the update file
I'll tell you the result
maahmd said:
Ok i will do it now if it does not work ..do you have a download link RECOVRY bised for p9 plus ?
Or I will pull it out of the update file
I'll tell you the result
Click to expand...
Click to collapse
I don't know what you mean now
Download the Nocheck Recovery for L29 from the Link I give you
https://forum.xda-developers.com/showpost.php?p=75234976&postcount=62
and do the instructions from the OP
https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
But with the RIGHT Firmware for your VIE-L29 device (3 zips from Firmware Finder /FullOTA)
After updating Firmware Bootloader is closed and Root is gone.
You have to open again (Factoryreset low-level wipe - if it doesn't do 100% do it manually from settings /advanced settings /backup restore /Factoryreset with wipe of internal storage - this is important! ) and flash TWRP and Root again

Allcall Rio , need help

I recently bought this new chinese phone ( out from 3 months, android 7.0 ) but after many hours i still was not able to root this, tried all 1click junk and nothing worked, tried PC apps.. followed many guides, nothing worked.
I would like at least to install TWRP, but of course, device is not supported, and i dont know where to get proper IMG file for my phone.
any help would be appreciated.. thanks
Edit: Tried Mtk tools, since its a mt6580, it does detect phone but there are errors,
TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64
Uknown rom structure, backup not possible
innersphere1 said:
I recently bought this new chinese phone ( out from 3 months, android 7.0 ) but after many hours i still was not able to root this, tried all 1click junk and nothing worked, tried PC apps.. followed many guides, nothing worked.
I would like at least to install TWRP, but of course, device is not supported, and i dont know where to get proper IMG file for my phone.
any help would be appreciated.. thanks
Edit: Tried Mtk tools, since its a mt6580, it does detect phone but there are errors,
TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64
Uknown rom structure, backup not possible
Click to expand...
Click to collapse
no way to root this??
Hi, I also just aquired the allcall rio.
Can you help me out with a few things,
1. does the back come off in order to reach the battery?
2. on a normal phone pressing the middle button normally gains you access into the app menu, for some reason i can only access the home screen with the apps being accessed by sliding the home screen to multi home screens, is this normal?
3. have you rooted your phone and if so can you leadme to where you done this?
I like the phone, just wondering whether what iv stated are normal features or a fault with mine
Thanks in advance for any help / info
Cheers
Rooted / ish
innersphere1 said:
no way to root this??
Click to expand...
Click to collapse
Hey,
I have not found a root method but iv found a way to access all sysytem files and folders.
Go to app store and download ROOT BROWSER by JRummy Apps.
Open the app once installed and it will ask you to download files to make it work, it downloads quickly from inside the app.
When its finished you can then access the phones root files as tho your phone was rooted.
Its better than nothing for now and im sure there would be a way to insert the nesscerry files for rooting into the correct folders.
Hope it works for you
ronyon78 said:
Hey,
I have not found a root method but iv found a way to access all sysytem files and folders.
Go to app store and download ROOT BROWSER by JRummy Apps.
Open the app once installed and it will ask you to download files to make it work, it downloads quickly from inside the app.
When its finished you can then access the phones root files as tho your phone was rooted.
Its better than nothing for now and im sure there would be a way to insert the nesscerry files for rooting into the correct folders.
Hope it works for you
Click to expand...
Click to collapse
So can you modify files in /system with ROOT BROWSER?
---------- Post added at 07:51 AM ---------- Previous post was at 07:26 AM ----------
innersphere1 said:
no way to root this??
Click to expand...
Click to collapse
SP flash to flash a custom TWRP recovery .
I have ported one recovery image from TWRP 3.0.0-0 for Tecno W4 using carliv image kitchen. And it works like charm.
I would put the link up If I could, but right now I still need to make a few more posts to gain the privilege .
innersphere1 said:
no way to root this??
Click to expand...
Click to collapse
Hi again, I've found the better way to get root using Magisk, available here in XDA.
first download the 0808 firmware from allcall's official website and flash it with SP flash.
wireless upgrade to 20170819, unlike 0728 and 0808, this version has remove all bloatware and malware
take boot.img from the firmware folder and put it to phone storage
install Magisk Manager v5.3, hit install, patch the boot image.
copy the patched boot.img to PC and SP flash it. (no need to unlock bootloader)
done!
everything for allcall rio
ALLCALL RIO- SOFTWARE+TWRP+PHILZ+SUPER SU+FLASH TOOL+SN WRITE TOOL needrom download success:good:
---------- Post added at 04:42 PM ---------- Previous post was at 04:39 PM ----------
AllCall-RIOWCDMA-1GB+16GB-7.0-20171207 by radu13
ciroradu said:
ALLCALL RIO- SOFTWARE+TWRP+PHILZ+SUPER SU+FLASH TOOL+SN WRITE TOOL needrom download success:good:
---------- Post added at 04:42 PM ---------- Previous post was at 04:39 PM ----------
AllCall-RIOWCDMA-1GB+16GB-7.0-20171207 by radu13
Click to expand...
Click to collapse
Can you help me rooting my allcall rio I just can't tryied every root apk and pc softwares

[GUIDE] [EMUI 9] Magisk Root Huawei P10 VTR-L09 for Android PIE

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

Categories

Resources