Related
It is posible to get Magisk 15.3 working on b183 (EU version)?
I did:
1. flash b120 with HWOTA
2. flash b183 with Firmware Finder
3. install TWRP-3.1.1.1_120_130_170 (this one should preserve navigation buttons and camera flash working)
4. format data
5. install magisk 15.3
6. got bootloop
I also tried to format data after flashing Magisk, nothing changed... Recovery boot and system in TWRP didn't help, I had to flash b120 and than b183 again.
EDIT:
Problem solved:
1. flash b120 (https://yadi.sk/d/Y2yuM--73Lb9Kk) with HWOTA (https://forum.xda-developers.com/showpost.php?p=74999398&postcount=129)
2. flash b183 with FF
3. unlock bootloader
4. extract BOOT.img from b183 UPDATE.APP (Huawei Update Extractor: https://forum.xda-developers.com/showthread.php?t=2433454)
5. install Magisk Manager app
6. in Magisk Manager patch BOOT.img with Magisk zip (click Install -> Patch Boot Image File), copy patched_boot.img to PC
7. reboot into fastboot and flash patched_boot.img (command: "fastboot flash boot patched_boot.img")
8. DONE! Nav buttons working, camera flash working, Magisk working...
PS.: Sorry for my bad English.
Have you tried to use Magisk.zip with sideload method ??
k1ks said:
Have you tried to use Magisk.zip with sideload method ??
Click to expand...
Click to collapse
No. Is the difference between flash in TWRP and with sideload?
copantok said:
No. Is the difference between flash in TWRP and with sideload?
Click to expand...
Click to collapse
TRwp available isnt fully functionnel and dont manage encrypted data . Its the problem.
Do not flash it within a twrp ==> Bootloop...
Sideload method is an alternative , work with SuperSu Sr3/4/5 2.82.
Installing supersu sr5 from usb-otg or sdcard once in twrp is working.
Concerning magisk, i did not tried but :
Could you try just after installing magisk on twrp, to boot straight to bootloader to flash stock recovery, then boot straight to stock recovery and perform a wipe & format. Then you could finally boot to system.
oslo83 said:
Installing supersu sr5 from usb-otg or sdcard once in twrp is working.
Concerning magisk, i did not tried but :
Could you try just after installing magisk on twrp, to boot straight to bootloader to flash stock recovery, then boot straight to stock recovery and perform a wipe & format. Then you could finally boot to system.
Click to expand...
Click to collapse
This worked!!! (but I lost nav buttons and camera flash, probably due to TWRP while flashing Magisk)
Tomorrow I will try again reinstall b120 with HWOTA (to get nav buttons and flash working) then b183 with FF and install Magisk with Magisk Manager (extract BOOT.img from UPDATE.app, patch it with Magisk Manager and flash patched boot with fastboot, without TWRP).
Thank you!!!
Keep us informed.
---------- Post added at 02:24 ---------- Previous post was at 02:21 ----------
By the way, with this twrp the capacitives buttons are not broken on B183:
https://mega.nz/#!WVhkwQjY!ND1Qo3kmoXP0qI_IlRHVXdxHZ3fES-ze_mPsSc_Bpg4
SOLVED!
After flashing b120 (HWOTA) and b183 (FF), unlock, patched BOOT.img with Magisk Manager and flashed patched_boot.img with fastboot. Magisk working, nav buttons working, camera flash working!
On B183 with magisk 15.3 root is working fine but i don't manage to get magisk hide to work nor safetynet...
This may be known to many but there are many users who were struggling with this.
Hello Folks,
Was getting few requests on XDA, Telegram and Facebook for this. As title says, there were few users reporting OTA failures while they were rooted with Magisk. Yes, that's obvious, it will fail as you have modified the boot.img (ramdisk) and stock recovery (Recovery_ramdisk.img) while rooting and installing TWRP.
Please follow below steps to update via OTA if you were rooted or using magisk.
Uninstall busybox binaries and Xposed framework (if you are using by any chance)
Uninstall Magisk (inside the app or by flashing the magisk uninstaller via TWRP)
Download update.app of your current firmware and extract stock recovery and boot file via Huawei extractor
Flash stock recovery of your actual variant as fastboot flash recovery_ramdisk recovery.img
Flash stock boot as fastboot flash ramdisk ramdisk.img
Boot to system.
Perform OTA update and reboot.
Root your phone again if you want.
Enjoy.
You could just :
1.patch the new ramdisk's update via magiskmanager then,
2.update via HuRUpdater without removing your root before,
3.then reboot straight to fastboot, and flash your new patched ramdisk
4.reboot to your rooted updated firmware with magisk module still working and root mods still applyied.
PS: I don't know about xposed frameworks
shashank1320 said:
This may be known to many but there are many users who were struggling with this.
Hello Folks,
Was getting few requests on XDA, Telegram and Facebook for this. As title says, there were few users reporting OTA failures while they were rooted with Magisk. Yes, that's obvious, it will fail as you have modified the boot.img (ramdisk) and stock recovery (Recovery_ramdisk.img) while rooting and installing TWRP.
Please follow below steps to update via OTA if you were rooted or using magisk.
Uninstall busybox binaries and Xposed framework (if you are using by any chance)
Uninstall Magisk (inside the app or by flashing the magisk uninstaller via TWRP)
Download update.app of your current firmware and extract stock recovery and boot file via Huawei extractor
Flash stock recovery of your actual variant as fastboot flash recovery_ramdisk recovery.img
Flash stock boot as fastboot flash ramdisk ramdisk.img
Boot to system.
Perform OTA update and reboot.
Root your phone again if you want.
Enjoy.
Click to expand...
Click to collapse
Do we need to keep "Enable OEM Unlock" checked or unchecked in developer settings?
mohsyn said:
Do we need to keep "Enable OEM Unlock" checked or unchecked in developer settings?
Click to expand...
Click to collapse
Doesn't matter unless you are rooting
shashank1320 said:
Doesn't matter unless you are rooting
Click to expand...
Click to collapse
Thanks
I am unable to download OTA update through system
I have the zips downloaded using firmware finder but both the dload and copying the zips to /data/update/HWoUC folder fails
dload method keeps throwing erecovery on screen and does nothing
my recovery + ramdisk + kernal are all stock
magisk completely removed
bootloader unlocked
frp unlock
am i missing something or is there some other manual update method
mohsyn said:
Thanks
I am unable to download OTA update through system
I have the zips downloaded using firmware finder but both the dload and copying the zips to /data/update/HWoUC folder fails
dload method keeps throwing erecovery on screen and does nothing
my recovery + ramdisk + kernal are all stock
magisk completely removed
bootloader unlocked
frp unlock
am i missing something or is there some other manual update method
Click to expand...
Click to collapse
It should be hwouc folder directly under root of internal memory and not data/update/hwouc
Hello,
i'm trying to root a Sharp B10 (SH-A01) with Magisk.
It would be nice if i could do this without unlocking because i want to keep the stock rom anyway.
First problem is that i can't find a custom recovery (TWRP, CWM) for this device from where i could install Magisk.
Then i found out that Magisk gives the possibility to root a device through the Magisk Manager App by patching the boot.img.
But the second problem is that i can't find the boot.img either. I spotted the boot partition on the device and tried to pull with adb but i would need an already rooted device to give the needed permissions.
Is there anything else I could do to get this thing rooted besides compiling my own TWRP for the device?
thanks a lot,
paul
Hello, i search the same.
paulquappe said:
Hello,
i'm trying to root a Sharp B10 (SH-A01) with Magisk.
It would be nice if i could do this without unlocking because i want to keep the stock rom anyway.
First problem is that i can't find a custom recovery (TWRP, CWM) for this device from where i could install Magisk.
Then i found out that Magisk gives the possibility to root a device through the Magisk Manager App by patching the boot.img.
But the second problem is that i can't find the boot.img either. I spotted the boot partition on the device and tried to pull with adb but i would need an already rooted device to give the needed permissions.
Is there anything else I could do to get this thing rooted besides compiling my own TWRP for the device?
thanks a lot,
paul
Click to expand...
Click to collapse
Neither Magisk nor TWRP is needed to root Android: Chainfire's SuperSu does the job. You flash its ZIP via stock recovery "adb sideload"
jwoegerbauer said:
Neither Magisk nor TWRP is needed to root Android: Chainfire's SuperSu does the job. You flash its ZIP via stock recovery "adb sideload"
Click to expand...
Click to collapse
Hi,
thanks for your answer.
I already managed to root this device. I got the boot.img with Wwr_MTK & SP flash tool (windows tools...), patched it with the magisk app and than flashed the patched boot.img
1. Unlock your bootloader enter in download mode Vol+ + Vol- + USB conected to pc (Keep in mind that by doing this you will lose your files, it is advisable to make a backup of your photos, music, etc.)
2. Once you start your cell phone install magisk manager, Choosing the boot.img file of your rom into the app (Tip: Only!!! If your model is SM-A015M Android 11 I leave you my own modified boot.img to flash:
File on MEGA
mega.nz
Otherwise, you can download the firmware (3.79 gb) and extract the boot.img from the firmware of your model SM-A015 M / F ... Android 10, Android 11... etc. And No need for pc
https://samfrew.com/model/SM-A015M/
3. The image will begin to flash
4. When it restarts you will have Root on the cell phone!
------------------------------------------------------------------------------------------------------------------------------------------------
Extra: If you need the custom recovery I give you the link with my TWRP which is installed through the Odin program on a PC (this step does not delete your files)
File on MEGA
mega.nz
Keep in mind that to install TWRP you must deactivate the DM-VERITY & FORCEENCRYPT DISABLER I leave it in a link:
Zackptg5 - Android
zackptg5.com
This is a module that can be installed via magisk, which is necessary to decrypt the system ... so once TWRP is installed, it is advisable to uninstall it via Magisk to avoid R / W errors
I know two ways to get root access on Android.
use magisk manager to patch boot.img and then flash the patched boot.img
install twrp and use it to flash magisk directly
For the first method I have to get the boot.img from the manufacture's firmware. Using XperiFirm I downloaded the firmware my phone is currently running on but I can not find any boot.img file in it.
Looking at this Guide it says the boot_X-FLASH-ALL-A2CD.sin file is the boot.img file. But when I try to patch the boot_X-FLASH-ALL-A2CD.sin file with magisk manager then magisk manager says "No boot image found". What am I missing here?
For the second option I would have to install twrp first. But there is no twrp for the sony xperia 1 yet: https://twrp.me/Devices/Sony/
hi guys i'm trying to unlock the bootloader and install a custom recovery and custom rom i've never done it if anyone can help me and all the necessary files thanks a lot
Well first downgrade to rui 2.0 and then using deep testing apk unlock the bootlorder and then flash custom recovery (ofox better) . Install your custom rom of your choice then ur good to go
Pranav060 said:
Bene, prima eseguire il downgrade a rui 2.0 e quindi utilizzare l'apk di deep testing per sbloccare il bootlorder e quindi eseguire il flashing del ripristino personalizzato (ofox migliore). Installa la tua rom personalizzata di tua scelta, quindi sei a posto
Click to expand...
Click to collapse
unfortunately I can't find the realme ui 2.0 downgrade file when I install what is written in the guides it tells me verification failed and I can't downgrade
andrea34334343 said:
unfortunately I can't find the realme ui 2.0 downgrade file when I install what is written in the guides it tells me verification failed and I can't downgrade
Click to expand...
Click to collapse
I have this version of realme ui 3
Hi, maybe my experience will be useful to you. I have Realme 7 pro with android 12 rmx2170_11_f.24. I was doing root to my device. What I was doing? First I downloaded deeptest rui3.apk. When I get confirmation from manufacturer I start deep test in app. Then I use ADB to send command for unlock bootloader. I completed this task. Then I downloaded and flash TWRP 3.6.2_12 (because it's can work with android 12. I tried 3.5.2_10 it's not worked). Also you need vbmeta file from rmx2170_11_f.24 to don't make your phone brick. First flash vbmeta then recovery. After recovery you need to install Magisk from TWRP to keep TWRP working after reboot. But, when I tryed install Magisk I was getting TWRP error 1: cannot write /system. How I fix it? I reboot device and install Magisk 25.2 via Android. Then you need patch boot.img from rmx2170_11_f.24 via Magisk and you get Magisk patched boot.img. Then you need flash TWRP again and reboot to recovery. In TWRP you need chose flash img button and flash Magisk patched boot.img to boot partition. Doing this you keep TWRP working and then you can flash custom ROM's to your phone.
Mod edit: 4pda link removed.
here you can get f24 ROM ( you need vbmeta and boot.img from this ROM). ROM is ~2 Gb size. Maybe you need registration on website to download. Also get TWRP 3.6.2. I'll pin deep test rui3.apk and Magisk 25.2 for you here. You can rename Magisk.zip to Magisk.apk and install via Android. I gaved you roadmap how to make this. Hope you can do it. By the way, hello from Ukraine)
s_svyrydenko said:
Hi, maybe my experience will be useful to you. I have Realme 7 pro with android 12 rmx2170_11_f.24. I was doing root to my device. What I was doing? First I downloaded deeptest rui3.apk. When I get confirmation from manufacturer I start deep test in app. Then I use ADB to send command for unlock bootloader. I completed this task. Then I downloaded and flash TWRP 3.6.2_12 (because it's can work with android 12. I tried 3.5.2_10 it's not worked). Also you need vbmeta file from rmx2170_11_f.24 to don't make your phone brick. First flash vbmeta then recovery. After recovery you need to install Magisk from TWRP to keep TWRP working after reboot. But, when I tryed install Magisk I was getting TWRP error 1: cannot write /system. How I fix it? I reboot device and install Magisk 25.2 via Android. Then you need patch boot.img from rmx2170_11_f.24 via Magisk and you get Magisk patched boot.img. Then you need flash TWRP again and reboot to recovery. In TWRP you need chose flash img button and flash Magisk patched boot.img to boot partition. Doing this you keep TWRP working and then you can flash custom ROM's to your phone.
Mod edit: 4pda link removed.
here you can get f24 ROM ( you need vbmeta and boot.img from this ROM). ROM is ~2 Gb size. Maybe you need registration on website to download. Also get TWRP 3.6.2. I'll pin deep test rui3.apk and Magisk 25.2 for you here. You can rename Magisk.zip to Magisk.apk and install via Android. I gaved you roadmap how to make this. Hope you can do it. By the way, hello from Ukraine)
View attachment 5867277 View attachment 5867279
Click to expand...
Click to collapse
Thanks for helping me out and passing me the necessary files
{Mod edit: Quoted post has been deleted. Oswald Boelcke, Senior Moderator}
You wrote in the wrong trend write in a new post
s_svyrydenko said:
Hi, maybe my experience will be useful to you. I have Realme 7 pro with android 12 rmx2170_11_f.24. I was doing root to my device. What I was doing? First I downloaded deeptest rui3.apk. When I get confirmation from manufacturer I start deep test in app. Then I use ADB to send command for unlock bootloader. I completed this task. Then I downloaded and flash TWRP 3.6.2_12 (because it's can work with android 12. I tried 3.5.2_10 it's not worked). Also you need vbmeta file from rmx2170_11_f.24 to don't make your phone brick. First flash vbmeta then recovery. After recovery you need to install Magisk from TWRP to keep TWRP working after reboot. But, when I tryed install Magisk I was getting TWRP error 1: cannot write /system. How I fix it? I reboot device and install Magisk 25.2 via Android. Then you need patch boot.img from rmx2170_11_f.24 via Magisk and you get Magisk patched boot.img. Then you need flash TWRP again and reboot to recovery. In TWRP you need chose flash img button and flash Magisk patched boot.img to boot partition. Doing this you keep TWRP working and then you can flash custom ROM's to your phone.
Mod edit: 4pda link removed.
here you can get f24 ROM ( you need vbmeta and boot.img from this ROM). ROM is ~2 Gb size. Maybe you need registration on website to download. Also get TWRP 3.6.2. I'll pin deep test rui3.apk and Magisk 25.2 for you here. You can rename Magisk.zip to Magisk.apk and install via Android. I gaved you roadmap how to make this. Hope you can do it. By the way, hello from Ukraine)
View attachment 5867277 View attachment 5867279
Click to expand...
Click to collapse
Please provide twrp link.
UNOFFICIAL TWRP RMX2170 TRIAL FOR ANDROID 12
give me
boot img .vbmeta and .persist img