Hi,Guys! I want to build a rooted boot.img without flashing supersu.zip into my device.
Maybe use update-binary of supersu will be done?!?
Tks My friends!
Related
After the last update of android 5.0.2, 14.5.A.0.270, my phone does not have root access.
How can i root my phone again?
mafiagalou said:
After the last update of android 5.0.2, 14.5.A.0.270, my phone does not have root access.
How can i root my phone again?
Click to expand...
Click to collapse
Get stock rom ftf, prf creater, nuts dual recovery and super su flashable zip
Create flashable signed zip using prf creater by adding stock ftf and two zips in the prf creater
Now flash back .108 firmware, install root and recovery
Flash flaahable signed zip created by prf creater and you have pre rooted with recovery rom...
kathanpatel1001 said:
Get stock rom ftf, prf creater, nuts dual recovery and super su flashable zip
Create flashable signed zip using prf creater by adding stock ftf and two zips in the prf creater
Now flash back .108 firmware, install root and recovery
Flash flaahable signed zip created by prf creater and you have pre rooted with recovery rom...
Click to expand...
Click to collapse
how can I downgrade to .108 firmaware?
Download .108 stock firmware .ftf file for your z1 then flash it via flash tool..
Have you tried rooting your phone with KingRoot ?
quadrazid said:
Have you tried rooting your phone with KingRoot ?
Click to expand...
Click to collapse
I tried kingroot but this is fake root. Failed
"Download .108 stock firmware .ftf file for your z1 then flash it via flash tool.. "
where to find .270 kernel ?
For me kingroot worked perfectly. You must have an Internet connection when you use this app. Next thing to do is recovery installation, I recommend XZDualRecovery 2.8.15. In the last step, install SuperSU v2.49 beta (latest 2.46 don't working) through recovery. SuperSU will remove two kingroot apps, the one which remained remove by yourself.
ejeycorp said:
For me kingroot worked perfectly. You must have an Internet connection when you use this app. Next thing to do is recovery installation, I recommend XZDualRecovery 2.8.15. In the last step, install SuperSU v2.49 beta (latest 2.46 don't working) through recovery. SuperSU will remove two kingroot apps, the one which remained remove by yourself.
Click to expand...
Click to collapse
I do it but everytime need SU kod update????
Hi guys,
I made a mistake and I installed a MM kernel on the OOS 4.0.1 .
Do you know if there is a zip file with stock kernel so I can install it using TWRP.
Thank you
vlc_marcos said:
Hi guys,
I made a mistake and I installed a MM kernel on the OOS 4.0.1 .
Do you know if there is a zip file with stock kernel so I can install it using TWRP.
Thank you
Click to expand...
Click to collapse
If you have twrp then flash the full ota zip over again. This install the boot image again.
If you have a backup you can restore only the boot partition to fix it.
I have a problem with SuperSU and magisk. I flash in twrp the root zip and then magisk, after that when I want to update it says this;
! Boot img patched by other programs
! please restore stock boot img
Click to expand...
Click to collapse
I don't have any custom rom, i'm actually oos 5.0.3. I first try to root but dm-verity was triggered and then followed all the steps to disable it.
Any solutions?
Nube420 said:
I have a problem with SuperSU and magisk. I flash in twrp the root zip and then magisk, after that when I want to update it says this;
Click to expand...
Click to collapse
Magisk is a root zip. It sounds like you are flashing SuperSU and Magisk. You can only use one or the other, not both!
Reflash stock ROM (or at least stock boot.img). Then flash Magisk. That's it.
Getting the error message that boot.img is modified is normal and expected in your case. SuperSU patched the boot image. Now Magisk is looking for the stock image to patch, and finding a patched one.
When getting a custom ROM and wanting to root it with Magisk, should I patch and flash the boot.img of the specific ROM or the boot.img of the factory FW
hazoky01 said:
When getting a custom ROM and wanting to root it with Magisk, should I patch and flash the boot.img of the specific ROM or the boot.img of the factory FW
Click to expand...
Click to collapse
Flash TWRP or orange fox and then Magisk zip in the recovery
That's it
But of course the bootloader has to be unlocked
The boot img of the current ROM you're using like example boot img of Pixel Experience if you're using that. Usually the boot img is inside the ROM zip when you installed it. But this method is for devices without custom recovery. Of course it will work but I suggest to follow what Laptapper suggested to flash a custom recovery (orange fox r12.1_2 or twrp 3.7.0) and just flash magisk.zip.
So, should I flash the whole rom with the patched boot.img, or can I only flash the patched file ?
If for some reason install fails, can this damage the hardware or only soft-brick will happen ?
EDIT:
Is it safe to flash boot.img with ADB ?
EDIT:
Flashed *.tar file, there is root and apps work, but in magisk app, SU is inactive, can't press it...