Hello,
I have unlocked the bootloader. I tried to do the steps with Magisk, this is it:
-Install Magisk.
-Patch AP.
-Copy it to PC.
-ReFlash with ODIN.
But when I do that, I got errors during installation on Download mode and the phone bricks. So I don't know if I am doing something wrong or happens that this device can't be rooted.
I have been searching but can't find any reliable information about, could you please give me some information or help?
Thank you!
Bump!
Got this error following installation instructions:
ODIN MODE (AVB Fail)
vbm*** Error verifying vbmeta image: HASH_MISMATCH (3)
vbmeta: VERIFICATION_DISABLED bit is set
CUSTOM VBMETA
VBMETA G715FNXXU8CUE1, 4000301 4R
Finally, I have successfully rooted Samsung Galaxy Xcover Pro (SM-G715FN/DS, Europe Version, Android 11, Firmware version: G715FNXXS9CUF2).
I also had the same HASH_MISMATCH error before. But the method described in this post worked for me:
tys0n said:
It's pretty simple and straight forward. I won't go in on details about odin, drivers etc as there's many guides about that already.
Or join the A40 tg group for any assistance with firmware, odin etc.
You'll need to unlock bootloader first, and it will TRIP KNOX.
Please read up on what it means before you proceed if you're not sure about it. It can't be reversed.
Download and install latest Magisk manager to your phone. https://github.com/topjohnwu/Magisk/releases
Download and install 7zip ZS to your pc. https://github.com/mcmilk/7-Zip-zstd/releases
Get the firmware for your phone and extract the AP file from the firmware zip. (Use samfirm or frija for fast download)
Open the AP*.tar.md5 with 7zip ZS and click on the boot.img.lz4, then drag the boot.img out of there.
Copy the boot.img to your phone, open Magisk Manager and click install, and again install, then "select and patch a file".
Browse to the boot.img you just copied to your phone and let Magisk do it's magic.
You'll find a magisk_patched.img in your download folder when it's done.
Copy it over to your pc, rename it to boot.img and make a .tar archive with boot.img in it.
Open Odin, put the tar in AP slot, connect your phone in download mode and hit start in Odin.
Open Magisk Manager again once the phone is booted to finish the setup.
Done.
Click to expand...
Click to collapse
After doing this procedure, the system didn't boot. An option to execute Factory Reset appeared instead. I chose this option and confirmed to wipe all data.
After the factory reset, the system booted correctly and the phone was rooted. During the first boot I had to wait very long (maybe about ~15 minutes) while Samsung logo splash screen was displayed, but finally the system booted correctly. I also needed to install Magisk apk again, because all data was wiped.
After I bought the phone, the "OEM unlocking" option was missing in "Developers options". But after using my phone for 7 days this options appeared.
Additionally I enabled "MigskHide" option in Magisk and installed this: https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.2.0 . After doing this SafetyNet passes successfully.
Awesome! The bad thing is that I already sold Xcover Pro because I need root yes or yes but well, I hope it will be useful for people in the future! Maybe even somebody try to port LineageOS.
d5sword said:
Finally, I have successfully rooted Samsung Galaxy Xcover Pro (SM-G715FN/DS, Europe Version, Android 11, Firmware version: G715FNXXS9CUF2).
I also had the same HASH_MISMATCH error before. But the method described in this post worked for me:
After doing this procedure, the system didn't boot. An option to execute Factory Reset appeared instead. I chose this option and confirmed to wipe all data.
After the factory reset, the system booted correctly and the phone was rooted. During the first boot I had to wait very long (maybe about ~15 minutes) while Samsung logo splash screen was displayed, but finally the system booted correctly. I also needed to install Magisk apk again, because all data was wiped.
After I bought the phone, the "OEM unlocking" option was missing in "Developers options". But after using my phone for 7 days this options appeared.
Additionally I enabled "MigskHide" option in Magisk and installed this: https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.2.0 . After doing this SafetyNet passes successfully.
Click to expand...
Click to collapse
I have the xcover pro g7151u but Magisk cannot flash the boot.img file my AP version is "G715U1UEU9BUF4", I leave this answer in case someone can solve it later
-SpaceCowboy- said:
I have the xcover pro g7151u but Magisk cannot flash the boot.img file my AP version is "G715U1UEU9BUF4", I leave this answer in case someone can solve it later
Click to expand...
Click to collapse
-SpaceCowboy- said:
I have the xcover pro g7151u but Magisk cannot flash the boot.img file my AP version is "G715U1UEU9BUF4", I leave this answer in case someone can solve it later
Click to expand...
Click to collapse
Update: At the beginning in download mode it only appreciates the FRP lock status, but not the others, after flashing the stock ROM to the last one the KG status has appeared in "Cheking" mode but there is no OEM unlock status, this means That the bootloader is no longer blocked or that it will never have the option again?
-SpaceCowboy- said:
Update: At the beginning in download mode it only appreciates the FRP lock status, but not the others, after flashing the stock ROM to the last one the KG status has appeared in "Cheking" mode but there is no OEM unlock status, this means That the bootloader is no longer blocked or that it will never have the option again?
Click to expand...
Click to collapse
You can't root without an unlocked bootloader. And you can no longer unlock your bootloader on the version that you have - it's been updated too far
On my rooted SM-G715FN, I have:
CURRENT BINARY: Custom (0x3)
KG STATE: Checking
FRP LOCK: OFF
OEM LOCK: OFF(U)
Secure Download: Enabled
Click to expand...
Click to collapse
In Developer Options, I have `OEM Unlocking` enabled.
iBowToAndroid said:
You can't root without an unlocked bootloader. And you can no longer unlock your bootloader on the version that you have - it's been updated too far
Click to expand...
Click to collapse
Why it is not possible to unlock bootloader on his phone? I have unlocked bootloader on my phone without problems.
d5sword said:
Why it is not possible to unlock bootloader on his phone? I have unlocked bootloader on my phone without problems.
Click to expand...
Click to collapse
Because his phone is not SM-G715FN
The ADB removal method worked for me. There's a "Debloat" text file up on GitHub that makes this a breeze.
Link: https://github.com/khlam/debloat-samsung-android tellthebell
Once in debug mode, USB connected, and drivers installed:
ADB shell < commands.txt
Obviously, the text file must reside in the same folder as ADB.
travis659 said:
El método de eliminación de ADB funcionó para mí. Hay un archivo de texto "Debloat" en GitHub que hace que esto sea muy sencillo.
Enlace: https://github.com/khlam/debloat-samsung-android tellthebell
Una vez en modo de depuración, USB conectado y controladores instalados:
Shell ADB <comandos.txt
Obviamente, el archivo de texto debe residir en la misma carpeta que ADB.
Click to expand...
Click to collapse
i think only working in snapdragon devices, no? the Xcover use Exynos
d5sword said:
Finally, I have successfully rooted Samsung Galaxy Xcover Pro (SM-G715FN/DS, Europe Version, Android 11, Firmware version: G715FNXXS9CUF2).
I also had the same HASH_MISMATCH error before. But the method described in this post worked for me:
After doing this procedure, the system didn't boot. An option to execute Factory Reset appeared instead. I chose this option and confirmed to wipe all data.
After the factory reset, the system booted correctly and the phone was rooted. During the first boot I had to wait very long (maybe about ~15 minutes) while Samsung logo splash screen was displayed, but finally the system booted correctly. I also needed to install Magisk apk again, because all data was wiped.
After I bought the phone, the "OEM unlocking" option was missing in "Developers options". But after using my phone for 7 days this options appeared.
Additionally I enabled "MigskHide" option in Magisk and installed this: https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.2.0 . After doing this SafetyNet passes successfully.
Click to expand...
Click to collapse
Just wanted to say a huge thank you to yourself and tys0n.
I purchased an Xcover Pro brand new from Microless global for an absolute steal...as in a price that was simply too good to be true. It was only upon setting up the device that I realised why they were offering such a low price.
The device was encumbered by an unavoidable corporate knox enrollment service. Sadly I suspect most people who purchase from them won't realise just how much control of their device they are handing to some random company if they just press OK during setup, but I wasn't having it. Ignoring the enrolment promp was not possible; you couldn't even access the home button or recent button until you'd authorised under knox and handed control of the device over to some faceless entity.
Thanks to the efforts of those in this thread I have been able to unlock BL, root the SM-G715FN/DS and freeze all of the knox bull****. The device now belongs to me.
The only thing I'd like to ad for those that come here looking for answers is that the process above is spot on, but I had to use this tool to create my .tar file. Simply creating a .tar archive with the .img file in it wasn't good enough for my device; it rejected that as an unauthorised file.
Use this tool once you've patched the boot.img with magisk and renamed it.
[Script][Tool] how to create a tar.md5 file from img For Odin
for how want to use Odin to flash the ClockWorkMod Recovery img or any image files like "boot.img", this is a tool to create a tar.md5 file from the img file. unzip the file tool, and put your img files into the same directory of the batch file...
forum.xda-developers.com
Props to mkh.mourad and testament to the usefulness of XDA that a file from 2013 got me over the line.
I'm certainly no developer, but given the relative ease with which we got this far, I hope it's not too far down the road until we get TWRP and can start mucking around with some roms. Please post here if you have any ideas. This device has real potential as a very long term solution.
Hello,
I did all as described, however I am stuck in ODIN during flashing attempt.
I unlocked the OEM lock first, then I unlocked the bootloader (using long press Vol+ option, prior to download mode, what wipes the device).
I updated the system prior to attemt this procedure, downloaded the match image from sammobile.
Can please someone help to get through this step?
Thank you, Tomas.
TomasNM said:
Hello,
I did all as described, however I am stuck in ODIN during flashing attempt.
I unlocked the OEM lock first, then I unlocked the bootloader (using long press Vol+ option, prior to download mode, what wipes the device).
I updated the system prior to attemt this procedure, downloaded the match image from sammobile.
Can please someone help to get through this step?
Thank you, Tomas.
Click to expand...
Click to collapse
The "KG" status must be in "checking" so that you can flash a custom binary, you must leave the phone on 168 hours in a row with an internet connection otherwise it will not disappear
SpaceCowboy,
thank you for the advice, I waited a bit and today I managed to root the phone successfully.
However, I tried to install some Magisk modules and the phone stuck on initial screen (Samsung Galaxy Xcover Pro), even not get to the "SAMSUNG" screen.
Only solution was to wipe all data in recovery.
Any ideas how to install Magisk modules without risk?
Trying to root mine but just ran into a little problem.
Development mode lacks an OEM unlock option.
Psyckosama said:
Trying to root mine but just ran into a little problem.
Development mode lacks an OEM unlock option.
Click to expand...
Click to collapse
What's your Baseband Version?
iBowToAndroid said:
What's your Baseband Version?
Click to expand...
Click to collapse
g715u1uescbuj1
Psyckosama said:
g715u1uescbuj1
Click to expand...
Click to collapse
OEM unlock doesn't exist on US models. This model is bootloader unlockable via paid 3rd party services, but only up until bootloader revision 7. Since you're fully updated, you have revision 12
Related
Found this while trolling through the Chinese forums, none of this is my work, I have translated the instructions as best I can.
Disclaimers; I have not tried this, it may brick the global rom, the custom recovery is likely only in Chinese language.
You need:
Boot Loader unlock code (currently probably not possible to get)
Huawei USB drivers
Recovery image (attached)
Magisk package (attached)
files: https://mega.nz/#!PM0EmYLA!384hZjmJ9ExNc7Q8rSqssHunWSO7AxQ3GA4qet6RX4E
Extract files to a folder, open command prompt and change into this folder.
Unlock bootloader (BL unlock will clear the phone data, please do a backup)
- Obtain an official unlock code
- double-click to open the "Huawei Toolbox.exe"
- click "unlock bootloader "
- enter the unlock code in the pop up window , click OK, and wait for the phone to unlock complete restart.
Flash the third-party recovery
- Turn off the phone and connect the computer. Press and hold the “Volume Down” button and “Power button” until the phone displays the android page and release your finger.
- open command prompt and run:
fastboot flash recovery_ramdisk twrp.img
- after seeing the two OKAY feedback from the command line, the flash is successful.
Enter recovery to flash root image (this step will clear all data of the mobile phone including memory card, please make a backup in advance)
- long press “Volume Up” and “Power” ", until you see the a twrp logo, release the keys and wait to enter recovery mode
- After entering recovery, click the second item “Clear”, click “Format Data Partition” in the lower left corner, slide the slider to enter the clear, wait for the progress bar to complete
- Return to the recovery homepage, click on the last item "Advanced", select the last item "Remove data forced encryption", slide the slider to release, wait for completion
Copy the root package to the phone
- In Command Prompt type or copy the following commands
adb push magisk-installer.zip /sdcard
adb push magisk.apk /sdcard
Install Image
- Whilst still in recovery mode, click the first item to install the magisk-installer.zip package from the sdcard , slide the slider to install, wait for the flash to complete, and restart the phone
- After reboot is complete, click “File Manager”, select the apk file “magisk.apk” just copied from the memory card when install is finished, open the magisk app and click “No, thank you” in the pop-up window
- Return to the command line tool, type the code to execute, and wait for the phone to automatically restart
Fastboot reboot recovery
- after the restart, open "magisk", it should show that the installation is complete, that is, ROOT is achieved.
Anything in that forum on how to manually update phone?
technotika said:
Anything in that forum on how to manually update phone?
Click to expand...
Click to collapse
That is actually what I was looking for
But none, problem is the v20 (china version) seems to get OTA way before us, they all got v143 2 weeks ago.
I did find the menu to do it, but it only supports if the image is stored on an sdcard, and when I click it it says no sdcard found. so its impossible.
Tried same with similar results. One day eh? ?
İ have V20 chinese version. İ want to root but could not find a way. Can you share the chinese forum maybe i can find how to unlock bootloader
greenblueye said:
İ have V20 chinese version. İ want to root but could not find a way. Can you share the chinese forum maybe i can find how to unlock bootloader
Click to expand...
Click to collapse
If you read what I wrote in the first post you would see you cannot root without a bootloader unlock code.
Tested! Work bootloader code on Russia services (Cost 20USD)
belam00r said:
Tested! Work bootloader code on Russia services (Cost 20USD)
Click to expand...
Click to collapse
Nice! Did unlocking bootloader factory reset your device?
Yes of course. All new Huawei and Honor do a reset after unlocking
i get bootloader unlock code from funkiehuwai for 20$
any one tried this instructions and have success?
I just wonder comments below will work?
*adb push magisk-installer.zip /sdcard
*adb push magisk.apk /sdcard
because there is no sd card support for view20?
when i opened huawei-toolbox.exe its in chinese and im afraid to continue other instructions
Did anyone use TWRP and which version?
Did the View 20 Boot correctly?
I read in a Forum, that with the view 20 doesn´t boot correctyl with TWRP. The reason should bei the Storage...
Best regards
Unlocked Bootloader
belam00r said:
Tested! Work bootloader code on Russia services (Cost 20USD)
Click to expand...
Click to collapse
Does that mean you rooted you device (with the files from above) or you just unlocked the bootloader?
I was able to unlock my bootloader with a code from funkyhuawei (about 18 €, site seems to be down currently). I did not use the unlock tool above, mainly because its chinese
- Enabled "USB debugging" and "OEM unlock" in developer settings
- Connected phone to PC, opened adb and used "adb reboot bootloader"
- Unlocked via "fastboot oem unlock *16digit code*"
This worked out fine. However, as far as i understand it magisk is installed over twrp (recovery_ramdisk), removing twrp but granting you root. This makes me kind of nervous since twrp has been a nice safety net on several occasions. This is why I stopped after unlocking the bootloader. Maybe someone has more experience on this? Why is there so little interest in rooting this phone?
Regards
root achieved
I don't know if nobody's interested or nobody wants to try rooting this phone. However, I just went ahead and tried it. I used this guide: https://topjohnwu.github.io/Magisk/install.html#emui-9 (posted in https://forum.xda-developers.com/honor-view-20/help/root-t3900266). https://androidhost.ru/search.html is were I got the firmware from (posted in https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). I downloaded the 9.0.1.137 firmware, since this corresponds to the one currently installed on my phone.
In summary:
I extracted recovery_ramdis.img from the update.app with the huawei extractor. In order to see this image file, I had to uncheck "verify header checksum" under settings->extract.
I then transferred this file to my phone (download folder), downloaded newest magisk manager and installed it. I then pushed INSTALL next to magisk (which was not installed of course), Install again and then Patch boot image file. Choose your transferred recovery_ramdis.img and go ahead. Transfer patched file (now called patched_boot.img) back to PC.
For the next step, bootloader has to be unlocked already! Turn on "Enable OEM unlock" and "USB debugging" in the developer options and reboot to fastboot. Open ADB as usual and connect cable to phone. Type "fastboot flash recovery_ramdisk *path to patched_boot.img*" and wait for success.
A few things to keep in mind:
-Had a bootloop with the newest version of the viper4android module!
-The root was done without custom recovery, therefore a magisk module leading to a bootloop requires you to factory reset and do everything again if you want root to work (at least i couldn't get it to work again by reflashing orginial recovery_ramdis.img followed by patched_boot.img).
-For rooting to work you have to boot phone to recovery (in this case resulting in a "normal boot"). This means pressing volume up and holding it when booting the phone. For restart you could use an app which lets you boot to recovery automatically.
-While the above my sound annoying, permanently gives you the chance to boot you phone unrooted. This is nice, especially when you have a bootloop due to a magisk module (which I had).
-According to the first link, you could install a custom recovery into the second recovery partition of Huawei/Honor devices (erecovery_ramdis). there is no official twrp available for Honor View 20 at the moment.
-After unlocking my bootloader (see post above) I had "device not verified" in google play store. After rooting, my device is verified again
Regards
garris_bibop said:
I don't know if nobody's interested or nobody wants to try rooting this phone. However, I just went ahead and tried it. I used this guide: https://topjohnwu.github.io/Magisk/install.html#emui-9 (posted in https://forum.xda-developers.com/honor-view-20/help/root-t3900266). https://androidhost.ru/search.html is were I got the firmware from (posted in https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). I downloaded the 9.0.1.137 firmware, since this corresponds to the one currently installed on my phone.
In summary:
I extracted recovery_ramdis.img from the update.app with the huawei extractor. In order to see this image file, I had to uncheck "verify header checksum" under settings->extract.
I then transferred this file to my phone (download folder), downloaded newest magisk manager and installed it. I then pushed INSTALL next to magisk (which was not installed of course), Install again and then Patch boot image file. Choose your transferred recovery_ramdis.img and go ahead. Transfer patched file (now called patched_boot.img) back to PC.
For the next step, bootloader has to be unlocked already! Turn on "Enable OEM unlock" and "USB debugging" in the developer options and reboot to fastboot. Open ADB as usual and connect cable to phone. Type "fastboot flash recovery_ramdisk *path to patched_boot.img*" and wait for success.
A few things to keep in mind:
-Had a bootloop with the newest version of the viper4android module!
-The root was done without custom recovery, therefore a magisk module leading to a bootloop requires you to factory reset and do everything again if you want root to work (at least i couldn't get it to work again by reflashing orginial recovery_ramdis.img followed by patched_boot.img).
-For rooting to work you have to boot phone to recovery (in this case resulting in a "normal boot"). This means pressing volume up and holding it when booting the phone. For restart you could use an app which lets you boot to recovery automatically.
-While the above my sound annoying, permanently gives you the chance to boot you phone unrooted. This is nice, especially when you have a bootloop due to a magisk module (which I had).
-According to the first link, you could install a custom recovery into the second recovery partition of Huawei/Honor devices (erecovery_ramdis). there is no official twrp available for Honor View 20 at the moment.
-After unlocking my bootloader (see post above) I had "device not verified" in google play store. After rooting, my device is verified again
Regards
Click to expand...
Click to collapse
Well done good job:good:
İ have chinese version PCT-AL10 9.0.1.144 right now. Do you think i can use the same way? İ wonder from which version to extract recovery_ramdis.img
I have my view20 rooted
Thanks for the instructions.
greenblueye said:
I have my view20 rooted
Thanks for the instructions.
Click to expand...
Click to collapse
You're welcome Be careful with sound improvement modules in Magisk! Had another bootloop with the Zirene module...
Which firmware did you get the recovery_ramdisk from in the end?
garris_bibop said:
You're welcome Be careful with sound improvement modules in Magisk! Had another bootloop with the Zirene module...
Which firmware did you get the recovery_ramdisk from in the end?
Click to expand...
Click to collapse
I get recovery-ramdisk from firmware PCT-AL10 9.0.1.129 . my phone is on version 9.0.1.144 but it worked:good:
After root i can not auto update software. 9.0.1.166 version is seen on ota but after download it says update is unsuccessful. Do you have any suggestion?
I think thats to be expected when rooted. Go for manual update I guess (https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). Personally I wouldn't bother with every update unless theres interesting new features and/or security updates. just to be on the safe side I would reflash the original recovery_ramdisk before updating! And backup your data!
NM Card
Hello !
Unless I'm mistaken, the View20 must be able to use nano sd cards (NM Card)
Caution!!
This will delete all your personal data, please backup before you proceed.
If you haven't unlocked you bootloader before, unlock it before your (I am not sure if we can do it in locked bootloader). You can check @SkaboXD post for unlocking bootloader.
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
You will get an orange state warning at bootscreen after unlocking bootloader
Download below tool and patch and extract it
Nokia OST Tool : https://drive.google.com/open?id=1FKTq0WjG_m5x9QcsE8gs6KNldTByXAvZ
Nokia OST Tool Patch : https://drive.google.com/open?id=1R8R1FhdLdddpnZh6P-oeVynSLHjp6rvt
Replace OnlineUpdateTool.exe inside C:\Program Files (x86)\OST LA with the patched OnlineUpdateTool.exe from Nokia OST Tool Patch. Also delete OnlineUpdateTool.exe.config from C:\Program Files (x86)\OST LA
Dowload your firmware
Indian version https://drive.google.com/file/d/183WNykeXjRpr1R10J7Bgqd7-hkboJlGr/view
Global version https://drive.google.com/file/d/14Iycvr-SMtZIpnWrMm2KGM8D8tV7CA65/view
You can choose other firmware, but make sure it is from a reliable source, or else you will end up in something worse.
Now lauch OST Tool by clicking OnlineUpdateTool.exe which you just replaced. Connect your phone to PC, and switch it off. It will automatically enter fastboot mode (if failed enter fastboot mode by pressing power + volume down).
Now extract your firmware, which gives a .nb0 file. Choose this file in OST Tool and click 'Next'.
Its gonna take a while to complete flashing.
You can lock your bootloader by "fastboot.exe -i 0x2e04 oem lock"
Thanks @SkaboXD for guidance
Let me know if there is any concern
Blaze? said:
Caution!!
This will delete all your personal data, please backup before you proceed.
If you haven't unlocked you bootloader before, unlock it before your (I am not sure if we can do it in locked bootloader). You can check @SkaboXD post for unlocking bootloader.
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
You will get an orange state warning at bootscreen after unlocking bootloader
Download below tool and patch and extract it
Nokia OST Tool : https://drive.google.com/open?id=1FKTq0WjG_m5x9QcsE8gs6KNldTByXAvZ
Nokia OST Tool Patch : https://drive.google.com/open?id=1R8R1FhdLdddpnZh6P-oeVynSLHjp6rvt
Replace OnlineUpdateTool.exe inside C:\Program Files (x86)\OST LA with the patched OnlineUpdateTool.exe from Nokia OST Tool Patch. Also delete OnlineUpdateTool.exe.config from C:\Program Files (x86)\OST LA
Dowload your firmware
Indian version https://drive.google.com/file/d/183WNykeXjRpr1R10J7Bgqd7-hkboJlGr/view
Global version https://drive.google.com/file/d/14Iycvr-SMtZIpnWrMm2KGM8D8tV7CA65/view
You can choose other firmware, but make sure it is from a reliable source, or else you will end up in something worse.
Now lauch OST Tool by clicking OnlineUpdateTool.exe which you just replaced. Connect your phone to PC, and switch it off. It will automatically enter fastboot mode (if failed enter fastboot mode by pressing power + volume down).
Now extract your firmware, which gives a .nb0 file. Choose this file in OST Tool and click 'Next'.
Its gonna take a while to complete flashing.
You can lock your bootloader by "fastboot.exe -i 0x2e04 oem lock"
Thanks @SkaboXD for guidance
Let me know if there is any concern
Click to expand...
Click to collapse
Does it work with locked bootloader? Thank you!
RazOne said:
Does it work with locked bootloader? Thank you!
Click to expand...
Click to collapse
I am not sure about the case
For safer side unlock your bootloader, you can always lock your bootloader after downgrade, as mentioned in the post.
RazOne said:
Does it work with locked bootloader? Thank you!
Click to expand...
Click to collapse
I don't know for sure but I think it will. However you would probably have to flash a 7.x ota before you can flash ost.
That said,I would probably advise you to try moving your date backwards by a year or so, cos once your phone boots after flashing ost, you will be prompted to update to 8.x before you can do anything else
Hi! I tried doing this with locked bootloader, but the OST LA always gives 0xc6da error code.
I could perhaps opt to unlock bootloader, but the options is greyed out in developer options.
Any solution?
usedusername said:
Hi! I tried doing this with locked bootloader, but the OST LA always gives 0xc6da error code.
I could perhaps opt to unlock bootloader, but the options is greyed out in developer options.
Any solution?
Click to expand...
Click to collapse
What android version are you on?
If you're on any version other than 7.x you have to flash a 7.x update in recovery before you can flash ost
redweaver said:
What android version are you on?
If you're on any version other than 7.x you have to flash a 7.x update in recovery before you can flash ost
Click to expand...
Click to collapse
I'm in latest Oreo 8.1, April security update 2019. TA-1032 build 4.43E SP02 with stock recovery. All completely untouched.
So that mean I have to find a 7.x zip file and update through recovery by SD card, then only I can flash using OST, is this correct?
usedusername said:
I'm in latest Oreo 8.1, April security update 2019. TA-1032 build 4.43E SP02 with stock recovery. All completely untouched.
So that mean I have to find a 7.x zip file and update through recovery by SD card, then only I can flash using OST, is this correct?
Click to expand...
Click to collapse
I believe so. Either way whether locked or unlocked, you have to be on 7.x before you can flash ost. That said I think it's a good idea to be sure first. @bigrammy can OST be flashed on Android 7.x locked bootloader?
redweaver said:
I believe so. Either way whether locked or unlocked, you have to be on 7.x before you can flash ost. That said I think it's a good idea to be sure first. @bigrammy can OST be flashed on Android 7.x locked bootloader?
Click to expand...
Click to collapse
Hi redweaver,
I never use OST only SPFlashTool.
I unlocked the bootloader when on 7.0 and it seems to have remained unlocked ever since.
The methods I use 99% of the time are #1 SPFlashTool and #2 TWRP I rarely use fastboot for flashing anything.
I see no reason why one cannot roll back to 7.0 using SPFlashTool in "Firmware Upgrade" mode regardless of bootloader being locked or unlocked.
bigrammy said:
Hi redweaver,
I never use OST only SPFlashTool.
I unlocked the bootloader when on 7.0 and it seems to have remained unlocked ever since.
The methods I use 99% of the time are #1 SPFlashTool and #2 TWRP I rarely use fastboot for flashing anything.
I see no reason why one cannot roll back to 7.0 using SPFlashTool in "Firmware Upgrade" mode regardless of bootloader being locked or unlocked.
Click to expand...
Click to collapse
Hi bigrammy, thanks for the tip!
I used SPFlashTool and managed to rollback to Android 7.1.1! However, during the setup page, it prompts me to update software straightaway...
EDIT: I just skipped the software update process! Just remove your SIM cards prior to starting the setup, then select "Don't use any networks" or some sort of options to finalize the setup.
usedusername said:
Hi bigrammy, thanks for the tip!
I used SPFlashTool and managed to rollback to Android 7.1.1! However, during the setup page, it prompts me to update software straightaway...
EDIT: I just skipped the software update process! Just remove your SIM cards prior to starting the setup, then select "Don't use any networks" or some sort of options to finalize the setup.
Click to expand...
Click to collapse
frp reset should stop any forced prompts for a network connections and hopefully allow you time to root it and disable the auto updates process etc. :fingers-crossed:
bigrammy said:
frp reset should stop any forced prompts for a network connections and hopefully allow you time to root it and disable the auto updates process etc. :fingers-crossed:
Click to expand...
Click to collapse
I only removed my SIM card to skip the software update process, then I continued setting up all my accounts like usual
As for the auto system updates, I just disable the "automatic system updates" option in Developer settings. The updates are still available for download, but it does not pop notifications anymore.
I downgraded only because the latest 8.1 was very slow, and might update only when Pie becomes available.
Thanks for the help!
bigrammy said:
Hi redweaver,
I never use OST only SPFlashTool.
I unlocked the bootloader when on 7.0 and it seems to have remained unlocked ever since.
The methods I use 99% of the time are #1 SPFlashTool and #2 TWRP I rarely use fastboot for flashing anything.
I see no reason why one cannot roll back to 7.0 using SPFlashTool in "Firmware Upgrade" mode regardless of bootloader being locked or unlocked.
Click to expand...
Click to collapse
I am using android 3 nokia 8.1 TA-1032 built 4.43E SP02. Please help me downgrade to 7.x.
Please give clear instructions because I use google translate difficult translation.
Nhattrungtn said:
I am using android 3 nokia 8.1 TA-1032 built 4.43E SP02. Please help me downgrade to 7.x.
Please give clear instructions because I use google translate difficult translation.
Click to expand...
Click to collapse
Use sp flash tool if you do not know how to use it then I will not help with that and you will need to use google. I do not use Windows OS so I cannot help with that also.
1. In sp flash tool swap DA_SWSEC_CRYPTO20.bin with this DA_SWSEC_CRYPTO20.bin
2. Load the scatter.txt contained in this NE1-0-139M-000C-V2.7z
3. In sp flash tool under DownLoad choose the Firmware Upgrade option DO NOT USE the Format All and Download.
Now Unlock the bootloader if you wish.
PS: I will be at work for the next few days so will not be able to help during this time.
If you are not sure about anything then I suggest you wait and read all you can first. Or better still stay on the stock 8.1
Blaze said:
Caution!!
This will delete all your personal data, please backup before you proceed.
If you haven't unlocked you bootloader before, unlock it before your (I am not sure if we can do it in locked bootloader). You can check @SkaboXD post for unlocking bootloader.
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
You will get an orange state warning at bootscreen after unlocking bootloader
Download below tool and patch and extract it
Nokia OST Tool : https://drive.google.com/open?id=1FKTq0WjG_m5x9QcsE8gs6KNldTByXAvZ
Nokia OST Tool Patch : https://drive.google.com/open?id=1R8R1FhdLdddpnZh6P-oeVynSLHjp6rvt
Replace OnlineUpdateTool.exe inside C:\Program Files (x86)\OST LA with the patched OnlineUpdateTool.exe from Nokia OST Tool Patch. Also delete OnlineUpdateTool.exe.config from C:\Program Files (x86)\OST LA
Dowload your firmware
Indian version https://drive.google.com/file/d/183WNykeXjRpr1R10J7Bgqd7-hkboJlGr/view
Global version https://drive.google.com/file/d/14Iycvr-SMtZIpnWrMm2KGM8D8tV7CA65/view
You can choose other firmware, but make sure it is from a reliable source, or else you will end up in something worse.
Now lauch OST Tool by clicking OnlineUpdateTool.exe which you just replaced. Connect your phone to PC, and switch it off. It will automatically enter fastboot mode (if failed enter fastboot mode by pressing power + volume down).
Now extract your firmware, which gives a .nb0 file. Choose this file in OST Tool and click 'Next'.
Its gonna take a while to complete flashing.
You can lock your bootloader by "fastboot.exe -i 0x2e04 oem lock"
Thanks @SkaboXD for guidance
Let me know if there is any concern
Click to expand...
Click to collapse
Hi, the firmware mentioned link is broken and not available anymore. Kindly provide any alternative link if available.
Thankyou
Asus rog phone 5 guide
note: you follow this guide on your own responsibility. also You should note that unlocking via the official Asus app will void warranty and blacklist the device for future otas.
bootloader unlock:
! note that unlocking the bootloader will erase the phone, back up your data before starting !
- install asus unlock application from asus website (direct link)
- open the app, scroll to the bottom accept the user agreement
-scroll to the bottom, click on agree. enter your pin
- your phone should now reboot and you should see the warning message indicating that you have unlocked bootloader
! now if you don't see the warning screen and your phone was not formatted, this means this unlock method didn't work and you should seek other methods !
updating to the latest ww firmware
- download the latest firmware zip from asus website (direct link) to Version WW-18.0830.2101.86.
-move the .zip file to your main storage directory.
the phone should detect the update file, if it doesn't reboot your device and it should detect it.
after updating, set up your device, then install magisk app (download link)
extract the boot.img from the above software downloaded from asus, using payload dumper (google it).
then copy the extracted boot.img to your phone.
install magisk.
open magisk
click install.
choose patch boot.img
once the patch is completed, copy the patched boot.img to you pc
for further info, magisk patching guide
on your PC you need to install your device drivers, and ADB & fastboot. and enable usb debugging on your device
flashing patched boot image
- open adb, approve the request on your device
- enter the command
Code:
adb devices
you should see your device and authorized. if not find a guide how to access your device
-next reboot to bootloader using the command
Code:
adb reboot bootloader
- in bootloader flash the boot.img from above using the following command
Code:
fastboot flash boot boot.img
where boot image should be the address to the location of your boot image.
if you boot image is on your D:/ drive and in a folder called rootstuff.
your command should look like this.
Code:
fastboot flash boot D:\rootstuff\boot.img
once you flash the patched boot.img, reboot your phone.
open magisk app, check your root status you should be rooted.
congratulations
Check pm's.
m8822 said:
- open the app, scroll to the bottom accept the user agreement
-scroll to the bottom, click on agree. enter your pin
- your phone should now reboot and you should see the warning message indicating that you have unlocked bootloader
Click to expand...
Click to collapse
hello and thank you very much for the detailed guide.
i was ready to do all that, i always unlock and root my devices so i'm savvy just enough to try, or so i thought.
after using asus unlock tool and rebooting, my phone ended up showing the indicated warning message but proceeded in a bootloop which is not generally a great problem, you can always flash partitions with fastboot !
But in my case the phone doesn't get recognised by "fastboot devices" command in bootloader mode nor in fastbootd (yes i have the latest adb & fastboot package installed with the latest platform tools)
so now i've got a very espensive and fancy paper holder.
if any of you encountered the same problem or maybe knows a way to get the device to be recognised by my pc I'll be very happy to donate for your trouble.
i already downloaded the latest firmware and extracted it with payload_dumper.py.
thank you very much to any of you who will take time to look into my issue.
also may i suggest adding a step to your guide ?
before flashing boot.img it might be a good idea to try it first using
Code:
Fastboot boot boot.img
i've had problems in the past with some bad patched boot.img images and this may be a way to avoid problems.
sorry if this sound patronising. just wanted to help
sabnack said:
also may i suggest adding a step to your guide ?
before flashing boot.img it might be a good idea to try it first using
Code:
Fastboot boot boot.img
i've had problems in the past with some bad patched boot.img images and this may be a way to avoid problems.
sorry if this sound patronising. just wanted to help
Click to expand...
Click to collapse
Thanks, is your currently rooted now? I tried module "Fullscreen/Immersive Gesture" to hide the annoying,ugly gesture indicator (thank Apple & Google for great idea). All worked except gesture swipe up from bottom to open desktop. Do you know any module to hide that pill
hilary trump said:
Do you know any module to hide that pill
Click to expand...
Click to collapse
I'm sorry i don't know but i will gladly look into that issue as soon as i can boot my phone, currently i'm stuck in a bootlop and my phone doesn't get recognised. i put all my hopes in the unbrick tool at this point, whenever it will be out.
I will let you know
hilary trump said:
Thanks, is your currently rooted now? I tried module "Fullscreen/Immersive Gesture" to hide the annoying,ugly gesture indicator (thank Apple & Google for great idea). All worked except gesture swipe up from bottom to open desktop. Do you know any module to hide that pill
Click to expand...
Click to collapse
the root guide worked on another rog 5, however mine is completely nricked and i myslef is waaiting for unbrick tools
sabnack said:
hello and thank you very much for the detailed guide.
i was ready to do all that, i always unlock and root my devices so i'm savvy just enough to try, or so i thought.
after using asus unlock tool and rebooting, my phone ended up showing the indicated warning message but proceeded in a bootloop which is not generally a great problem, you can always flash partitions with fastboot !
But in my case the phone doesn't get recognised by "fastboot devices" command in bootloader mode nor in fastbootd (yes i have the latest adb & fastboot package installed with the latest platform tools)
so now i've got a very espensive and fancy paper holder.
if any of you encountered the same problem or maybe knows a way to get the device to be recognised by my pc I'll be very happy to donate for your trouble.
i already downloaded the latest firmware and extracted it with payload_dumper.py.
thank you very much to any of you who will take time to look into my issue.
Click to expand...
Click to collapse
Connect your phone with the side port it will work.
sorankira said:
Connect your phone with the side port it will work.
Click to expand...
Click to collapse
yes it did work, i flashed every partition and now i'm locked again, recovery doesn't work, could you please dump yours and post it ? hope i'm not asking too much.
EDIT: nevermind i finally solved it, i flashed a raw img of the system, it works now, thanks for your time
m8822 said:
Asus rog phone 5 guide
note: you follow this guide on your own responsibility. also You should note that unlocking via the official Asus app will void warranty and blacklist the device for future otas.
bootloader unlock:
! note that unlocking the bootloader will erase the phone, back up your data before starting !
- install asus unlock application from asus website (direct link)
- open the app, scroll to the bottom accept the user agreement
-scroll to the bottom, click on agree. enter your pin
- your phone should now reboot and you should see the warning message indicating that you have unlocked bootloader
! now if you don't see the warning screen and your phone was not formatted, this means this unlock method didn't work and you should seek other methods !
updating to the latest ww firmware
- download the latest firmware zip from asus website (direct link) to Version WW-18.0830.2101.86.
-move the .zip file to your main storage directory.
the phone should detect the update file, if it doesn't reboot your device and it should detect it.
after updating, set up your device, then install magisk app (download link)
extract the boot.img from the above software downloaded from asus, using payload dumper (google it).
then copy the extracted boot.img to your phone.
install magisk.
open magisk
click install.
choose patch boot.img
once the patch is completed, copy the patched boot.img to you pc
for further info, magisk patching guide
on your PC you need to install your device drivers, and ADB & fastboot. and enable usb debugging on your device
flashing patched boot image
- open adb, approve the request on your device
- enter the command
Code:
adb devices
you should see your device and authorized. if not find a guide how to access your device
-next reboot to bootloader using the command
Code:
adb reboot bootloader
- in bootloader flash the boot.img from above using the following command
Code:
fastboot flash boot boot.img
where boot image should be the address to the location of your boot image.
if you boot image is on your D:/ drive and in a folder called rootstuff.
your command should look like this.
Code:
fastboot flash boot D:\rootstuff\boot.img
once you flash the patched boot.img, reboot your phone.
open magisk app, check your root status you should be rooted.
congratulations
Click to expand...
Click to collapse
Mine causes bootloop
sorankira said:
Mine causes bootloop
Click to expand...
Click to collapse
What ? Why!
what happened? Did you get this after unlocking the bootloader or after boot.img?
My troubkeshooting will consiste of flashing raw, but i am not sure if that will lock your bootloader
sorankira said:
Mine causes bootloop
Click to expand...
Click to collapse
can you enter recovery and fastbootd ? if you only get access to bootloader, flashing a raw image does work !
then you can apply ota update zips from booted android and subsequently patch boot.img extracted from payload.bin from the ota update.
worked for me and i thought i bricked my device. let us know if we can do something to help.
sabnack said:
can you enter recovery and fastbootd ? if you only get access to bootloader, flashing a raw image does work !
then you can apply ota update zips from booted android and subsequently patch boot.img extracted from payload.bin from the ota update.
worked for me and i thought i bricked my device. let us know if we can do something to help.
Click to expand...
Click to collapse
I fixed the bootloop but without root access
sorankira said:
I fixed the bootloop but without root access
Click to expand...
Click to collapse
i believe you already have version WW-18.0830.2101.86 for WW only ( i just checked, i believe it was you who posted it here ). you can use this guide to extract boot.img from the payload.bin from the "UL-ASUS_I005_1-ASUS-18.0830.2101.81-1.1.64-user.zip" then if you continue by following the guide at the top of this thread you will be rooted in 15 minutes at most.
sabnack said:
i believe you already have version WW-18.0830.2101.86 for WW only ( i just checked, i believe it was you who posted it here ). you can use this guide to extract boot.img from the payload.bin from the "UL-ASUS_I005_1-ASUS-18.0830.2101.81-1.1.64-user.zip" then if you continue by following the guide at the top of this thread you will be rooted in 15 minutes at most.
Click to expand...
Click to collapse
Yes i used this method, and causes bootloop sadly.
sorankira said:
Yes i used this method, and causes bootloop sadly.
Click to expand...
Click to collapse
oh ! dammit it's weird... you could try to patch the boot image with another phone.
or maybe the update file isn't right for your phone. i don't get it
Somebody successfully succeeded with the bootloader & Rooting this Asus ROG 5 phone?
my experience rooting was as follows:
I bought the rog phone 5 I005DA in china, in which the store changed the rom CN to WW version WW-18.0830.2101.86 and blocked the bootloader.
When my hands arrived I updated the firmware to WW-18.0840.2103.26 (the last one available).
I followed all the steps in this post and I was successful with root.
(Attention, extract the boot.img from the firmware that you currently have installed on the phone)
miguel.jackass said:
my experience rooting was as follows:
I bought the rog phone 5 I005DA in china, in which the store changed the rom CN to WW version WW-18.0830.2101.86 and blocked the bootloader.
When my hands arrived I updated the firmware to WW-18.0840.2103.26 (the last one available).
I followed all the steps in this post and I was successful with root.
(Attention, extract the boot.img from the firmware that you currently have installed on the phone)
Click to expand...
Click to collapse
how did you open the bootloader? using asus app?
because it did not work before i rooted i was on 2101.86 at the time. i tried goind down to 2100.95 also did not work.
i had to rent a guy to do it via edl. which he is not sharing the method because he wants to make money
m8822 said:
how did you open the bootloader? using asus app?
because it did not work before i rooted i was on 2101.86 at the time. i tried goind down to 2100.95 also did not work.
i had to rent a guy to do it via edl. which he is not sharing the method because he wants to make money
Click to expand...
Click to collapse
I updated the firmware to the latest official version, extract the boot.img from the last official firmware, and installed the official unlock tool from the ASUS website, I just had to follow the tutorial.
My way of installing TWRP and ROOT on A20e (only tested on a202f).
Everything is working both on TWRP and MAGISK.
Versions:
-Magisk (v26.1)
-MagiskManager (v26.1)
-TWRP (3.6.1_9.0)
_________________________________________________
Download attached files:
-TWRP and ROOT(magisk) Odin is included!
_________________________________________________
#Factory reset is recommended!
#Make sure BOOTLOADER is unlocked!
#If you don't need MAGISK stop at step 6 and reboot to system
[TWRP Installation]
1. Extract required files, open ODIN (as Administrator) click on the "AP" button and choose TWRP-3.6.1_9.0.tar file.
2. In the "Options" menu untick "Auto-Reboot" .
3. On your phone boot into the "Download Mode" then in ODIN you can press the START button. (make sure you are connected to PC)
4. If everything is fine there should be green "PASS!" text in ODIN.
[ If your flashing failed make sure the bootloader is unlocked and check if cable is properly connected ]
[Don't let the phone boot into system because it will replace TWRP with stock recovery.img]
6. Boot into TWRP and FORMAT DATA (Wipe/Format Data) to remove encryption.
# If you don't need MAGISK you can reboot to system. Otherwise continue reading the guide.
[MAGISK Installation]
7. From TWRP reboot into RECOVERY again.
8. Connect your phone to PC or if you moved Magisk-v26.1.zip and Magisk-v26.1.apk to SD card then use SD card.
9. Flash the Magisk-v26.1.zip file and reboot to system.
10. When you boot into system install the Magisk apk.
11. Open it and finish the installation process.
12. Reboot
ENJOY!
[UPDATE]
-Updated versions of both TWRP and MAGISK
# TWRP 3.5.2_9-0 --> TWRP 3.6.1_9-0
# Magisk v23 --> Magisk v24.3
-Remodifed VBMETA
For ANY help contact me on Telegram: https://t.me/SerbianGeek
does encryp work on this ? dont need to backup just hide data part if fone is stole
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
/dev/null/ said:
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
Click to expand...
Click to collapse
No problems on my end, pal.
SerbianGeekster said:
No problems on my end, pal.
Click to expand...
Click to collapse
this phone is really a PITA. every time i try to do something it's 1 step forward and 2 steps back. never suffered so much. i flashed it like 20 times. all i want is a working twrp on stock rom and pass safetynet
/dev/null/ said:
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
Click to expand...
Click to collapse
to bypass this error:
1. connect to wifi
2. change the date to 2 august 2019
3. boot into download mode
4. flash twrp
Thank you! It worked! No problems got me.
I kinda feel like idiot that I couldn't install it with that ease before
OH **** IT WORKED !!!
I've been at this for hours, thank you so much !!!
Hello,
I have a Samsung A20e running with the a202fxxu4cvk1 firmware (a11 version). I would like to install twrp and then to root it. I tried several tutorials (Odin, OEM unblocked, USB debugging, time change) but twrp installation fails with message 'custom recovery blocked by frp'.
Can anyone help me?
I duckduckgoed, and found this XDA thread, where the second post says the following :
Nemirtingas said:
FRP: https://www.samsung.com/us/support/frp/
FRP Just locks your phone if you alter the boot or recovery image and you had a google account registered. To unlock it you have to wipe data (factory reset) and reflash stock boot.img and recovery.img before using it again. If your cousin wants to flash my ROM (lineageos-13.0) he'd better not, its not stable and he will encouter random reboots and codecs bugs. The best thing to do is to remove FRP from his phone and flash Magisk (a root manager like SuperSU) and debloat it.
For more information, find the Grandprimevelte group on Telegram.
Click to expand...
Click to collapse
The rest of the posts mention the need for a modified boot.img, else your phone would brick after adding a Google account, but I don't know about that... I have MicroG on mine with a Google account and no problems.
Anyway, frp seems to be a related to having a Google account on your phone.
fjunk said:
Hello,
I have a Samsung A20e running with the a202fxxu4cvk1 firmware (a11 version) /.../ Custom recovery blocked by frp'.
Can anyone help me?
Click to expand...
Click to collapse
Hello..I was wrong. My issue is not related to frp but OEM. OEM is unlocked according to developper menu but is not effective. Not able to upload any custom rom or bootloader.
I read that there was issue (use of a volume up button in download mode).
Any idea?
fjunk said:
Hello..I was wrong. My issue is not related to frp but OEM. OEM is unlocked according to developper menu but is not effective. Not able to upload any custom rom or bootloader.
I read that there was issue (use of a volume up button in download mode).
Any idea?
Click to expand...
Click to collapse
Indeed, my issue is that in download mode I can only do a volume down button and power button to reboot in system mode. No option to unlock bootloader.
I think you only need to do that once, afterwards, download mode doesn't warn you.
What error message do you get exactly when trying to flash TWRP, at what point, and what gives it (phone, odin) ?
lPolarisl said:
I think you only need to do that once, afterwards, download mode doesn't warn you.
What error message do you get exactly when trying to flash TWRP, at what point, and what gives it (phone, od
Click to expand...
Click to collapse
Many thanks for your update. Attached are pictures of the mobile and the Odin result. The error is an OEM issue (red text on the top of the mobile screen). In other forums, I can see that the download mode has an option to unlock OEM bootloader. I can't see it on my phone.
Putting the camera so that it covers the error message, what an amazing idea xD
I have never encountered this error, so let's start from the beginning.
Have you enabled the developer options, and activated "allow USB debugging" on the phone ? Also, if there is an option "allow OEM unlock", activate that as well (not all Samsung phones have it).
Have you installed the proper ADB and Samsung drivers ? Which version of Odin are you using ?
lPolarisl said:
Putting the camera so that it covers the error message, what an amazing idea xD
I have never encountered this error, so let's start from the beginning.
Have you enabled the developer options, and activated "allow USB debugging" on the phone ? Also, if there is an option "allow OEM unlock", activate that as well (not all Samsung phones have it).
Have you installed the proper ADB and Samsung drivers ? Which version of Odin are you using ?
Click to expand...
Click to collapse
Thanks for your reply.
That's sure that it doesn't really help to hide the error message. Usb debugging is enabled (I am able to run adb commands) and OEM is unlocked on the preference setting. I did the test with Odin 3.13 but same results with newer version. I installed an A11 firmware (a202fxxu4cvk1).
Don't t know how to go ahead. It seems that I don't have the possibility to unlock OEM in the download mode interface....
Wait, what is that about the firmware ? What did you flash, how and why ?
also, try a patched version of Odin from this post (I have 3.13.1_3B)
lPolarisl said:
Wait, what is that about the firmware ? What did you flash, how and why ?
also, try a patched version of Odin from this post (I have 3.13.1_3B)
Click to expand...
Click to collapse
I bought a refurbished mobile phone (blackmarket). It came with a 9.0 version. I tried to update to a custom rom without success so I installed the latest 'official' version
Download Samsung Galaxy A20e SM-A202F XEF France A202FXXU4CVK1 firmware
Fast download latest Samsung Galaxy A20e firmware SM-A202F from France with A202FXXU4CVK1 and Android version 11
www.sammobile.com
I uploaded this version using Odin. I also tried the patched Odin version. I read that the patched version only works with a10 version.
Huh...
I have no idea how that behaves, but I hardly see why it would cause a problem.
What else could you try... Restore factory settings maybe ?
Pressing volume up when starting in download mode ? (Note, this supposedly relocks the bootloader if it has been unlocked, if that happens and your phone isn't 100% on stock, it will brick.)
Hi everyone sorry for the truble and probably the bad english this is not my main language .
I have an old Samsung s7 with android 8.0 that i wanted to root with magisk.
I first tried with twrp but i don't know why i couldn't "install" it, when flashing with odin it failed and made my phone go in like"emergency recovery mode ".
Next i tried without TWRP which i founded is the recommended method.
I did everything the guides i found said but when i am flashing the patched boot.img after the phone boot and i open magisk it isn't installed.
Ramdisk went from yes to no.
I don't know what to do i am sure i used the correct boot img. I transferred them via google driver in .tar maybe this broke something?
paoloooooo said:
I did everything the guides i found said
Click to expand...
Click to collapse
please mention the exact steps, we don't have crystal ball.
sorry,
I extracted boot.img from the ap file (it's the correct one i am sure because i used it to flash stock firmware).
Then i transferred the boot.img via google drive to the phone and used magisk to patch it, it said no error and everything worked fine . After that via google drive i brought back the patched file to the pc and used odin to flash it with BL CP HOME-CSC.
When i flash it with BL CP HOME-CS and the patched file the phone boot and ask me to go to factory reset i say yes, then after everything i reinstall magisk and ramdisk went from yes to no but it still says magisk not installed.
I don't know if i made myself clear
so I understood you enabled OEM unlocking, unlocked bootloader in download mode (what was factory resetting device) and after finishing initial welcome setup, you again ensured OEM is unlocked in developer settings. only then, you flashed Magisk, device is still working but Magisk provides no root, because ramdisk is gone.
What is the Samsung ROM version (for example G930FXXU8EVG3)?
What Magisk version you installed?
What options you set in Magisk before patching boot.img? Haven't used Magisk for a while, maybe no options have been asked.
i have enabled OEM unlocking but bootloader mode i don't have the option to activate it (in the passage before going to dowload mode) but the guide i looked said it wasn't needed if there wasn't the option.
I am using magisk 25.2 and they ask no option when patching .
download platform-tools, enable usb-debugging, install ADB drivers, confirm 'adb devices' on phone and push the ROM to phone storage.
Code:
adb devices
adb push path\to\pc\AP_[device_model_sw_ver].tar.md5 /sdcard/Download
uninstall Magisk and install older version Magisk-v24.2.apk
In case you want to use TWRP later, disable the encryption checkbox (only when asked) and disable avb/dm-verity checkbox (only when asked) in the options before patching (not sure these options exist though).
Device should have ramdisk, so do not enable the recovery option for now.
patch the whole AP_[device_model_sw_ver].tar.md5 file with Magisk. notice the file name when finished.
copy the patched file back to PC and rename it AP_[device_model_sw_ver]_magisk_patched_boot.tar
Code:
adb pull /sdcard/Download/magisk_patched.tar path\to\pc\AP_[device_model_sw_ver]_magisk_patched_boot.tar
flash the patched AP file together with BL CP CSC (will factory reset) and wait long time for first boot. finish the initial setup and install (older) Magisk apk again.
if rooting was successful, update Magisk from within the Magisk app.
i tried and did everything but when i try to flash with odin it crashes
please understand I won't answer "please help" or "tried everything" posts. give more information. the patched firmware does not flash? or is that general odin issue?
edit: given instructions were straight from magisk documentation
https://topjohnwu.github.io/Magisk/install.html#instructions
except for using older Magisk. I forgot to tell you how to install. did you figure it out yourself?
In the Magisk-v24.2.apk, do not update to recent version (yet).
In the settings, select Update Channel: custom. then select Custom Channel, copy-paste this link.
https://raw.githubusercontent.com/topjohnwu/magisk-files/4868c83/beta.json
you can now patch the rom file with older Magisk.
ok i managed to do every step you told me i patched the file with v24.2 of magik and falshed with odin, everything went fine. But there is still the same problem the app says that is not installed but ramdisk went from yes to no
You're more likely to get the help you need if you ask your question in the right place. We have a Galaxy S7 section. This is why Rule #1 is to search before posting! We will move your thread there.
An unlocked bootloader is absolutely necessary to root. Rooting means you're modifying images on the device; a locked bootloader will prevent flashing modified images. If you haven't unlocked your bootloader, that's your first step.
I personally haven't had any luck patching the AP file in Magisk either. My suggestion is to flash a custom recovery such as TWRP, then flash Magisk in TWRP. Use the latest version of Magisk - 25.2.
paoloooooo said:
But there is still the same problem the app says that is not installed but ramdisk went from yes to no
Click to expand...
Click to collapse
Hm.. then maybe it's true your device does not have boot ramdisk? or the patching failed and removed ramdisk somehow?
try again with "Recovery Mode" option enabled when patching. note you have to press the volume button for recovery mode each time you boot.
@V0latyle recent versions of Magisk running Zygisk may have incompatibilities
https://forum.xda-developers.com/t/...ices-with-old-kernel-3-19-s7-included.4447029
Magisk-v23.0.apk is last version without Zygisk (but afaik you still can disable Zygisk in recent Magisk).
https://raw.githubusercontent.com/topjohnwu/magisk-files/afe2c30/stable.json
aIecxs said:
Hm.. then maybe it's true your device does not have boot ramdisk? or the patching failed and removed ramdisk somehow?
try again with "Recovery Mode" option enabled when patching. note you have to press the volume button for recovery mode each time you boot.
@V0latyle recent versions of Magisk running Zygisk may have incompatibilities
https://forum.xda-developers.com/t/...ices-with-old-kernel-3-19-s7-included.4447029
Magisk-v23.0.apk is last version without Zygisk (but afaik you still can disable Zygisk in recent Magisk).
https://raw.githubusercontent.com/topjohnwu/magisk-files/afe2c30/stable.json
Click to expand...
Click to collapse
Zygisk is disabled by default, you have to manually enable it when setting up Magisk after root
V0latyle said:
You're more likely to get the help you need if you ask your question in the right place. We have a Galaxy S7 section. This is why Rule #1 is to search before posting! We will move your thread there.
An unlocked bootloader is absolutely necessary to root. Rooting means you're modifying images on the device; a locked bootloader will prevent flashing modified images. If you haven't unlocked your bootloader, that's your first step.
I personally haven't had any luck patching the AP file in Magisk either. My suggestion is to flash a custom recovery such as TWRP, then flash Magisk in TWRP. Use the latest version of Magisk - 25.2.
Click to expand...
Click to collapse
OEM unlocking should be like the boot loader.
i tried using TWRP and i followed this video doing all the steps
but after the final reboot magisk app is not there and if i try to install it manually it's the same as the immage i already posted.
I found out searching online that after root ramdisk should go from yes to no and that worked. But i don't know why it never says that's installed
paoloooooo said:
OEM unlocking should be like the boot loader.
i tried using TWRP and i followed this video doing all the steps
but after the final reboot magisk app is not there and if i try to install it manually it's the same as the immage i already posted.
I found out searching online that after root ramdisk should go from yes to no and that worked. But i don't know why it never says that's installed
Click to expand...
Click to collapse
It seems like you misunderstand several critical concepts.
First, OEM unlocking DOES NOT unlock the bootloader itself. It simply allows you to. After enabling OEM unlocking, you have to follow the process to boot the device into unlock mode, then you have to follow the prompts to unlock the bootloader, which will wipe the device.
Second, the Ramdisk indication in Magisk simply indicates whether or not the device has ramdisk. This does not change, regardless of whether or not the boot image or system has been patched with Magisk. The only thing you need to look for is Installed: <Magisk version>. If Installed: N/A then you do not have root.
All you need to do is install TWRP, and if you're going to be using the factory firmware, flash the Multidisabler. Then, install Magisk through TWRP. When you reboot to system, you should have root; you'll need to install the Magisk app, but once you do, you should see the version of Magisk next to Installed as described above.
@V0latyle I think paoloooooo is right (see his screenshot) and bootloader is unlocked (otherwise phone wouldn't boot after flashing magisk_patched.tar)
aIecxs said:
@V0latyle I think paoloooooo is right (see his screenshot) and bootloader is unlocked (otherwise phone wouldn't boot after flashing magisk_patched.tar)
Click to expand...
Click to collapse
I thought a locked bootloader will prevent flashing anything custom?
right. but afaik it's possible to flash on semi-locked bootloader after the OEM toggle was enabled, but vaultkeeper still armed. at least that is the mistake you're refering to, many people struggle with...
guys thanks for everything i literally don't know why but i tried one last time with patching immages and it had the same error as the immages.
2 days after, i looked into it again and i don't know how but magisk was installed.
Thanks for everything and sorry choosing wrong section and not being very explicative.
aIecxs said:
right. but afaik it's possible to flash on semi-locked bootloader after the OEM toggle was enabled, but vaultkeeper still armed. at least that is the mistake you're refering to, many people struggle with...
Click to expand...
Click to collapse
Yeah, it would seem that a user would have to do things one of two ways:
Unlock bootloader, flash custom recovery, IMMEDIATELY boot into recovery (do not allow boot to system), wipe /system and format /data, install custom OS...this should prevent KG from interfering
Unlock bootloader, flash multidisabler, wipe data, boot to system, connect to Internet, ensure OEM Unlocking toggle is still visible, if it is KG should be disabled
paoloooooo said:
Hi everyone sorry for the truble and probably the bad english this is not my main language .
I have an old Samsung s7 with android 8.0 that i wanted to root with magisk.
I first tried with twrp but i don't know why i couldn't "install" it, when flashing with odin it failed and made my phone go in like"emergency recovery mode ".
Next i tried without TWRP which i founded is the recommended method.
I did everything the guides i found said but when i am flashing the patched boot.img after the phone boot and i open magisk it isn't installed.
Ramdisk went from yes to no.
I don't know what to do i am sure i used the correct boot img. I transferred them via google driver in .tar maybe this broke something?
Click to expand...
Click to collapse
i have the exact problem I just want to install twrp but when flashing with odin it fails. can anyone help me install twrp?