is guide tested on galaxy a30 a305f .
first we need to unlock the bootloader :
1. go to Setting>About>Software>Build Number and Tap on the build number repeatedly so that the Developer mode will turn on.
2. In the developer options, there is an OEM unlock option then enable that option.
3. enter download mode and press and hold volum up to unlock bootloader ! This will wipe your phone data entirely so make sure you have made a backup of important files.
now we can root this devices
we need :
1.odin 13.3.1
2.official firmware for your device
3.7zip ZS
4.magisk canary release or download from attached file
5.computer
1.download the firmware and extracted the files to your desktop
2.extract the boot.img.lz4 from the AP file
3.install the 7zip ZS , right click on boot.img.lz4 shoose 7zip ZS and extract the boot.img
4.copy the boot.img in your phone and install the magisk canary release
5.open magisk manager Install → Install → Select and Patch a File
6.select the file boot.img magsik will patche the boot image and store the output to [Internal Storage]/Download/magisk_patched.img
7. now copy the magisk_patched.img to you computer and reboot to download mode
8. rename magisk_patched.img to boot.img
9.right click on boot.img 7zip >add to archive and select format .tar
10.open odin unchek auto-reboot and select AP section and select the boot.img.tar and flash it .
11.We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode, and as soon as the screen turns off, immediately press Power + Volume Up to boot to recovery partition. Just as mentioned in the previous section, since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
12.In the stock recovery menu, use volume buttons to navigate through menus, and the power button to select the option. Select Wipe data/factory reset to wipe the data of the device.
13.This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press Volume Up. After vibrate , release all buttons . phone will boot normal
14. After the device is booted up, do the usual initial setup.
15. install the magisk canary release again , it will ask you to install the zip click install , after a few moments the device will reboot .
16.Voila! Enjoy Magisk
this tutorial was tested by me and it work on my device !
this is my first thread
Please add the part that you need to press the volume up button everytime you reboot the device.
messi2050 said:
Please add the part that you need to press the volume up button everytime you reboot the device.
Click to expand...
Click to collapse
no just the first time , after that always reboot with root .
bleedboy said:
no just the first time , after that always reboot with root .
Click to expand...
Click to collapse
Perfect.
OEM Unlocking option is missing
I already in dev mode, but oem unlocking is unavailable
monaACE said:
I already in dev mode, but oem unlocking is unavailable
Click to expand...
Click to collapse
what about unlocking in download mode
bleedboy said:
what about unlocking in download mode
Click to expand...
Click to collapse
Any link?
How to enter download mode? Jold power and volume up button? ?️
Root Galaxy A30
I have try 6-7 times but it always failed. Any ideas. I have follow all the instructions but when flash with odin it fails
ValaTarot said:
How to enter download mode? Jold power and volume up button? ?️
Click to expand...
Click to collapse
volume up + volume down and put the usb cable
seekunto said:
I have try 6-7 times but it always failed. Any ideas. I have follow all the instructions but when flash with odin it fails
Click to expand...
Click to collapse
did u unlock the bootloader ?
bleedboy said:
did u unlock the bootloader ?
Click to expand...
Click to collapse
yes. It's give the following when trying to flash:
Initialization
Get pit for mapping
Firmware update start
NAND write start
Singledownload
Boot.img
RQT_CLOSE!
Complete (write) operation Failed
Failed
bleedboy said:
did u unlock the bootloader ?
Click to expand...
Click to collapse
Complete (write) operation Failed
hisam1987 said:
Complete (write) operation Failed
Click to expand...
Click to collapse
it worked for me...i flashed stock firmware via odin, then unlocked bootloader in download mode and i saved the boot image as boot.tar not boot.img.tar and did rest of the instructions....everything passed smoothly, before that i had the same flash failed problem..its time to install viper yay lol...thanks so much bleedboy.
welcome enjoy ?
lazinezz said:
it worked for me...i flashed stock firmware via odin, then unlocked bootloader in download mode and i saved the boot image as boot.tar not boot.img.tar and did rest of the instructions....everything passed smoothly, before that i had the same flash failed problem..its time to install viper yay lol...thanks so much bleedboy.
Click to expand...
Click to collapse
welcome enjoy ??
hisam1987 said:
Complete (write) operation Failed
Click to expand...
Click to collapse
try to flash the stock rom and repeat the instruction !
seekunto said:
yes. It's give the following when trying to flash:
Initialization
Get pit for mapping
Firmware update start
NAND write start
Singledownload
Boot.img
RQT_CLOSE!
Complete (write) operation Failed
Click to expand...
Click to collapse
flash the stock firmware with odin and repeat the instriction
Failed
lazinezz said:
it worked for me...i flashed stock firmware via odin, then unlocked bootloader in download mode and i saved the boot image as boot.tar not boot.img.tar and did rest of the instructions....everything passed smoothly, before that i had the same flash failed problem..its time to install viper yay lol...thanks so much bleedboy.
Click to expand...
Click to collapse
I tried all the ways but still the problem
Thank you
---------- Post added at 12:14 PM ---------- Previous post was at 12:08 PM ----------
bleedboy said:
try to flash the stock rom and repeat the instruction !
Click to expand...
Click to collapse
I tried all the ways but still the problem
Thank you
hisam1987 said:
I tried all the ways but still the problem
Thank you
---------- Post added at 12:14 PM ---------- Previous post was at 12:08 PM ----------
I tried all the ways but still the problem
Thank you
Click to expand...
Click to collapse
try to flash only the stock boot img from your firmware ! after that flash the patched one .
Related
hi i just got a honor 6x and i have been following guides and at one point i had lineage os 13 on the phone but it would only boot to the password screen
so then i side loaded resurrection os 5.7 and it didnt have wifi so i tried upgrading emui and now i can't install any rom it just hangs at "patching ssytem unconditonally"
i have TWRP running on the phone. i just want to go back to stock OS. please help how do i do this?
unknown command [errno] update_huawei_pkg_from_ota_zip from zip failed
when i try to flash the stock huawei rom
i can run fastboot and twrp but nothing else works. i will paypal 15 dollars to someone who can help me
You can download the full firmware directly from honor, unzip it, and place the update.app file in a dload folder that you create on your sd card. Power of the phone then hold volume up, down, and power at the same time to initiate an automatic flash of the room you downloaded. This will erase everything, so be aware.
1.Download full rom from huawei support site then extract update.app
2.place it in dload folder using twrp (in twrp enable MTP)
3.Now extract the recovery.img from update.app using huawei extractor and flash it using fastboot flash recovery recovery.img
4.now power off phone then start phone holding Volume Up ,Volume Down & power button simultaneously
5.it will start updating
Rommco05 said:
Which is your model number and which twrp u have installed?
Click to expand...
Click to collapse
l24 and twrp-3.1.1-0-berlin.img
siddhrsh said:
1.Download full rom from huawei support site then extract update.app
2.place it in dload folder using twrp (in twrp enable MTP)
3.Now extract the recovery.img from update.app using huawei extractor and flash it using fastboot flash recovery recovery.img
4.now power off phone then start phone holding Volume Up ,Volume Down & power button simultaneously
5.it will start updating
Click to expand...
Click to collapse
I tried this method and it hangs on "your device is booting now..."
i also tried again after flashing system.img and boot.img from the huawei extractor. not sure what im doing wrong
do i have to flash anything else? i am on linux btw
juicyapply said:
I tried this method and it hangs on "your device is booting now..."
i also tried again after flashing system.img and boot.img from the huawei extractor. not sure what im doing wrong
do i have to flash anything else? i am on linux btw
Click to expand...
Click to collapse
flash recovery only after placing the update.app in dload folder
---------- Post added at 10:45 PM ---------- Previous post was at 10:44 PM ----------
juicyapply said:
I tried this method and it hangs on "your device is booting now..."
i also tried again after flashing system.img and boot.img from the huawei extractor. not sure what im doing wrong
do i have to flash anything else? i am on linux btw
Click to expand...
Click to collapse
flash recovery only after placing the update.app in dload folder then reboot your device using 3 button
Rommco05 said:
BLN-L24C567? If yes flash via twrp this two zips, after make reboot recovery in twrp. Should by now in stock recovery and here tap factory reset and after reboot. Now you will be hopefully in emui. Follow only if is correct your fw number which is mentioned here
http://update.hicloud.com:8180/TDS/...24_hw_usa/update_data_full_BLN-L24_hw_usa.zip
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1279/g104/v82815/f1/full/update.zip
Click to expand...
Click to collapse
by flash, you mean press the top left install button?
Rommco05 said:
Yes, download them and put to sdcard or inter memory. Flash first region and after update zip
Click to expand...
Click to collapse
The region flashes sucessfully but update.zup fails on '32k crc check'
Rommco05 said:
Any news juicyapply ?
Click to expand...
Click to collapse
update_huawei_pkg_from_ota_zip: update pcakage from zip failed
updater process ended with ERROR: ?
Errror installinc zip file '/sdcard/update.zip'
3.1.0-2 is the twrp version
it just says your device is booting now forever
i put it on stock recovery, i can put it back on twrp though
juicyapply said:
i put it on stock recovery, i can put it back on twrp though
Click to expand...
Click to collapse
No, just do a reset in stock recovery.
venugopalu007 said:
No, just do a reset in stock recovery.
Click to expand...
Click to collapse
it doesn't boot to stock recovery, even when i hold down volume and power buttons
i got the recovery using the extractor using huawei
oh my god ok now it is stuck at blue honor screen for an hour after update installed automatically without pressing anything. i just pressed volume and power buttons and it started updating. no menu was provided
now it says your device failed verificitaion
so now the bootloader is locked again and the update installed, but it still doesn't boot and when i try to update again it says verification failed
juicyapply said:
now it says your device failed verificitaion
Click to expand...
Click to collapse
I had the same problem once.
You can try to flash the cust partition of your phone. The "device verification failed"-message should disappear then. It's not enough to only flash boot, system and recovery. If there is a problem with the cust partition of your phone you can also have problems with flashing stock roms via "dload"-method.
1. Download the right stock firmware via the huawei firmware finder. You usually have two .zip files (e.g. update.zip & update_full_BLN-L21_hw_eu.zip). The image file for the cust partition can be found in the update_full_BLN-L21_hw_eu.zip (choose the right one for your model).
2. Unpack update_full_BLN-L21_hw_eu.zip and extract the cust partition with the huawei firmware extractor.
3. Put your phone into fastboot mode
4. Use the following command: fastboot flash cust cust.img
5. Try to boot into your stock rom.
Before following guide check this:
If you never unlocked bootloader or you flashed Android 7.1.1 nb0 with locked bootloader, then you need to go back to Android 7.0, after that unlock then lock bootloader. If you want to update, use OTA, don't flash nb0 because it have stock LK inside.
Here is the explanation why:
bigrammy said:
In theory and put simply as possible it should not work on a never unlocked before device if the LK does it's job properly.
The LK does all the checking down the secure boot chain prior to allowing the recovery or boot.img to boot.
If a device has been officially Unlocked then the LK should write (normally hidden) 1 bite identifiers to partitions like secro, misc, oem, etc etc (Depends on the OEM where and how) so when you flash a new ROM the new LK should still look for these bite's and if it see's them then it will allow the none stock .img's like twrp to boot normally.
So to sum up
1. Nokia made a huge screw up and the Nokia 3 is a totally insecure device like most of cheap MediaTek Chinese phone's out there.
2. The LK knows the bootloader was officially Unlocked before and therefore ignores the secure boot chain.
Click to expand...
Click to collapse
Downloads:
SP Flash Tool:
https://spflashtool.com/download/
VCOM Drivers:
https://spflashtool.com/download/MediaTek_USB_VCOM_drivers.zip
Scatter file (extracted from nb0, use this scatter to avoid renaming issue):
https://mega.nz/#!qJh1TSLL!5afi-7NYqKT3H62tqBISYSAdBDgN6eIM20WRSbtq3qE
Compatible DA (Download Agent):
https://mega.nz/#!xd8B3AJQ!PW82IpLzMzyNQk55BdwMnRMPlKQA0Yzj_8k_xN5r9XM
Stock boot.img and Stock recovery.img:
https://forum.xda-developers.com/nokia-3/development/link-stock-boot-img-stock-recovery-img-t3785576
TWRP 3.1.0-0 by mediafire007:
https://onedrive.live.com/?authkey=...126&parId=768DA1AA966F93C9!3122&action=locate
TWRP 3.2.1-0 by SkaboXD:
https://mega.nz/#!qIhFkKia!AkUMvQJ0PGVnSePabTvOgO-oUAMZahlCNaZfy2gE4vE
Magisk ZIP:
https://github.com/topjohnwu/Magisk/releases/download/v16.0/Magisk-v16.0.zip
Magisk Manager APK:
https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
unSU script:
https://forum.xda-developers.com/attachment.php?attachmentid=4410561&d=1517853382
First Step: Installing and setting SP Flash Tools
Install VCOM Drivers (video tutorial): https://youtube.com/watch?v=w3whZ2QMGvo
Then extract SP Flash Tool to Desktop. Open extracted folder and open flash_tool.exe. Create new folder on Desktop and call it ''magisk twrp sp flash tool'' or something like that and move scatter to that folder. Then go back to SP Flash Tool and load scatter file. Close SP Flash Tool. Now copy/move DA_SWSEC_CRYPTO20.bin (Compatible DA that you downloaded) and replace it to sp flash tool folder. Then open sp flash tool and load DA that you replaced.
Second Step: Flashing TWRP and Magisk
Extract twrp to ''magisk twrp sp flash tool'' folder. Rename it to NE1-0-215H-00WW-recovery so SP Flash Tool can recognize it. Turn off your phone. Now open SP Flash Tool, tick recovery, select Download only mode and click Download. Hold power + vol up button at the same time and quickly connect phone to USB. Then it will go to META mode and downloading will begin first with red bar and second with yellow bar. When download completes, green tick/circle mark will appear. Now you have TWRP. Rename NE1-0-215H-00WW-recovery to twrp-recovery.img so you can remember file name.
If you don't have root, just flash Magisk ZIP with TWRP.
If you have SuperSU and you want to switch to Magisk, flash unSU script with TWRP which uninstalls SuperSU, then you need to flash stock boot.img. Switch from install zip to install image and click on stock boot.img. Tick boot partition and flash. When it's done with flashing, you can flash Magisk.
OPTIONAL
If you are for some reason scared to flash TWRP or don't want to mess with recovery partition, this is step for you.
Second Step: Flashing Magisk without touching recovery partition
If you want to switch from SuperSU to Magisk, unroot SuperSU in SuperSU options. Transfer stock boot.img to your device from PC. Go to your phone and install Magisk Manager APK and open it. Click install then click "Patch boot image file" then select stock boot.img then it starts downloading Magisk ZIP and patching boot.img. You will get patched_boot.img in /sdcard/MagiskManager. Now transfer stock boot.img and patched boot.img back to PC and move it to "magisk twrp sp flash tool" folder. Rename stock boot.img to NE1-0-215H-00WW-boot. Turn off your phone. Now open SP Flash Tool, tick boot, select Download only mode and click Download. Hold power + vol up button at the same time and quickly connect phone to USB. Then it will go to META mode and downloading will begin first with red bar and second with yellow bar. When download completes, green tick/circle mark will appear. Close SP Flash Tool. Rename NE1-0-215H-00WW-boot to stock-boot.img and rename patched-boot.img to NE1-0-215H-00WW-boot. Turn off your phone. Now open SP Flash Tool, tick boot, select Download only mode and click Download. Hold power + vol up button at the same time and quickly connect phone to USB. Then it will go to META mode and downloading will begin first with red bar and second with yellow bar. When download completes, green tick/circle mark will appear. TA-DA you have Magisk root. Rename NE1-0-215H-00WW-boot to patched-boot.img so you can remember file name.
What about OTA?:
If you want to have OTA updates, remember to flash stock recovery back if you flashed TWRP. With installed update you will not lose:
- Data (apps, internal storage data)
- Xposed framework (if flashed directly to system)
- Xposed modules
you will lose:
- Magisk
- Magisk modules
- Xposed framework (if you flashed it systemlessly)
To gain root, just flash Magisk again.
Comment if links need to be updated.
Credits:
@sp flash Tool developers for providing SP Flash Tool
@blackpanther0582 for nb0 and scatter file
@Max brackenz for Download Agent
@mediafire007 for TWRP
@topjohnwu for Magisk
@osm0sis for unSU script
@bigrammy for useful tips
I very happy to hearing a New Guide to root Nokia 3 ^^
---------- Post added at 05:47 PM ---------- Previous post was at 05:44 PM ----------
I will try it when I get up
Does the boot.img work regardless of whether one is on nougat or Oreo?
redweaver said:
Does the boot.img work regardless of whether one is on nougat or Oreo?
Click to expand...
Click to collapse
both boot.img work, i tested.
Try to flash official firmware 7.0 via SPFlashTool with uncheck in preloader and use Download Only, then my Phone just virable
---------- Post added at 08:41 AM ---------- Previous post was at 08:03 AM ----------
ERROR: S_BROM_CMD_STARTCMD_FAIL (0x7D5)
[BROM] Can not pass bootrom start command! Possibly target power up too early
[HINT]:
Elvaa said:
Try to flash official firmware 7.0 via SPFlashTool with uncheck in preloader and use Download Only, then my Phone just virable
---------- Post added at 08:41 AM ---------- Previous post was at 08:03 AM ----------
ERROR: S_BROM_CMD_STARTCMD_FAIL (0x7D5)
[BROM] Can not pass bootrom start command! Possibly target power up too early
[HINT]:
Click to expand...
Click to collapse
You inserted USB late, try again
You inserted USB late, try again
Click to expand...
Click to collapse
Not good. I was know that before you comment. But I use format tab, with default choose, I click start. It successfully. Now I can't see the Phone virable
---------- Post added at 10:11 AM ---------- Previous post was at 09:29 AM ----------
Except the Bootloader Format selected
---------- Post added at 10:15 AM ---------- Previous post was at 10:11 AM ----------
My Windows found Ports COM (when Plugin phone with PC). I try Remove cable, click Download, press UP volume + Power button, Insert cable. But It show AUTH_HANDLE_IS_NOT_READY. Then I click Download again, it show me the ERROR similar after I using format tab
Elvaa said:
Not good. I was know that before you comment. But I use format tab, with default choose, I click start. It successfully. Now I can't see the Phone virable
---------- Post added at 10:11 AM ---------- Previous post was at 09:29 AM ----------
Except the Bootloader Format selected
---------- Post added at 10:15 AM ---------- Previous post was at 10:11 AM ----------
My Windows found Ports COM (when Plugin phone with PC). I try Remove cable, click Download, press UP volume + Power button, Insert cable. But It show AUTH_HANDLE_IS_NOT_READY. Then I click Download again, it show me the ERROR similar after I using format tab
Click to expand...
Click to collapse
Not good,never use format unless you know what you're doing . You can try and see if you can flash OST , if that doesn't work, there's a post by SkaboXD on recovering his phone using spflashtool. Hopefully one of those methods will work
I may found my problem. I can't authentic by hand for my phone. Because If I press UP + Power button, It said ERROR s_auth_handle_is_not_ready (5000). If then I click download again, it said ERROR ERROR: S_BROM_CMD_STARTCMD_FAIL (0x7D5) if I still press two button too up to 7sec. It said similar ERROR when I click download and remove cable
---------- Post added at 10:40 AM ---------- Previous post was at 10:38 AM ----------
redweaver said:
Not good,never use format unless you know what you're doing . You can try and see if you can flash OST , if that doesn't work, there's a post by SkaboXD on recovering his phone using spflashtool. Hopefully one of those methods will work
Click to expand...
Click to collapse
Except Bootloader
Works in variant TA-1028 on official Oreo. Great guide tnx
I waited a week for this guide when I saw you talking to each other in the Nokia 3 TWRP thread..
And when I lost hope that you're going to make the thread I had to break down what you were saying amd make my own way..
It took me 6 hours to get all the tools and files and figure it out..
Thank you anyways <3
Any video tutorials for this? Iam a noob
DHruV07 said:
Any video tutorials for this? Iam a noob
Click to expand...
Click to collapse
currently no, but it would be great if someone make it.
Is there any slowdowns with the magisk ? Can it run viper4android as module afterwards?
Thank you skabo as always!
Thank you
Nikola Jovanovic said:
Is there any slowdowns with the magisk ? Can it run viper4android as module afterwards?
Thank you skabo as always!
Thank you
Click to expand...
Click to collapse
Thanks bro,
No slowdowns, it even works better than SuperSU. For example i couldn't install Nethunter because SuperSU misses some lib for sh execution. With Magisk it works perfectly.
Also you have magisk modules unlike SuperSU (i didn't tested it though).
Nice Tread.
It will be interesting to see if this works for someone who as never unlocked the bootloader previously which is why I held off since there were no volunteers to test it.
bigrammy said:
It will be interesting to see if this works for someone who as never unlocked the bootloader previously which is why I held off since there were no volunteers to test it.
Click to expand...
Click to collapse
Me too.
Thank you
bigrammy said:
It will be interesting to see if this works for someone who as never unlocked the bootloader previously which is why I held off since there were no volunteers to test it.
Click to expand...
Click to collapse
well it should work for them too, but where to find someone who never unlocked bootloader.
SkaboXD said:
well it should work for them too, but where to find someone who never unlocked bootloader.
Click to expand...
Click to collapse
I've never unlocked a Nokia (HMD) device bootloader and to be honest, after reading all the issues and problems some have been having trying to unlock their Nokia 3's, I don't think I want to try.
I am getting very frustrated about the fact my TA 1020 (UK) is still stuck on Android 7.1.1 and the march security update.
I've tried all the hacks suggested like taking the Sim out and resetting, connecting to Indian vpns and pressing check for updates every hour over a 14 hour period.
My Nokia 3 is an unlocked (Sim free) version as well.
bubba1601 said:
I've never unlocked a Nokia (HMD) device bootloader and to be honest, after reading all the issues and problems some have been having trying to unlock their Nokia 3's, I don't think I want to try.
I am getting very frustrated about the fact my TA 1020 (UK) is still stuck on Android 7.1.1 and the march security update.
I've tried all the hacks suggested like taking the Sim out and resetting, connecting to Indian vpns and pressing check for updates every hour over a 14 hour period.
My Nokia 3 is an unlocked (Sim free) version as well.
Click to expand...
Click to collapse
did you cleaned Google services data after that?
Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Rooting your phone may void warranty so don't root your device unless you know what you are doing.
Before Installing Magisk
Your device is non-A/B and uses system-as-root, so Magisk will be installed to the recovery partition of your device.
Installing Magisk for the first time REQUIRES a full data wipe, backup before continue( I would recommend to use SmartSwitch app for backup )
You have to have your bootloader unlocked before following the instructions.
Unlocking Bootloader
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot your device to download mode. Turn off your device and hold volume up + volume down button, connect usb cable to PC
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk.
Enable developer options, and confirm that the OEM unlocking option exists and grayed out!
Your bootloader now accepts unofficial images in download mode.
Instructions
Method 1
1. Download the latest firmware for your device.
2. Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
3. Install the latest Magisk Manager
4. In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
5. Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar, Copy the patched file to your PC.
6. Download and extract odin(link given below).
7. Install Samsung USB drivers if not installed automatically.
8. Reboot into download mode, odin will indicate blue in id:com if the device is connected.
9. Flash magisk_patched.tar as AP in Odin, together with the BL, CP and CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck “Auto Reboot” in Options!
10. Magisk is now successfully flashed to your device! But there are still several steps
before you can properly use the device.
11. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press and hold Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press and hold the Volume up + Power button to enter stock recovery.
12. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
13. This time, we can finally boot to the system with Magisk.
Important: Select Reboot system now, and immediately press the Volume up + power button after seeing the bootloader warning screen, release all buttons so it can boot to the magisk system.
14. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
15. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
16. You shall see Magisk Manager in your app drawer; if not, manually install the APK and continue to the next step. The app will automatically upgrade to the full Magisk Manager when you open it.
17. Enjoy Magisk
Method 2
INS Only
*To Make Things Easier*
1. Download the firmware(already patched) from the link given below
2. Unzip the firmware to any folder on your PC.
3. Download and extract odin(link given below).
4. Install Samsung USB drivers if not installed automatically.
5. Reboot into download mode, odin will indicate blue in id:com if the device is connected.
6. Flash AP, BL, CP and CSC files from extracted firmware. Do not load HOME_CSC and also leave USERDATA empty in odin.
Important: Uncheck “Auto Reboot” in Options!
7. Continue steps from 10 to 17 from method 1
Method 3: Rooting with TWRP[Thread]
1. Download Twrp based on ASL2 firmware only which already have magisk patched.
2. Go to download mode
3. Using odin flash TWRP in AP slot.
4. Reboot to twrp and format data.
4. Now you have Magisk + Twrp
Note: Magisk will be disabled when you reboot the device normally. To get into Magisk enabled system, Turn off your phone and use Volume up + power buttons to turn on and release it as soon as you see Samsung Galaxy M30S logo. This will boot into magisk system, I would recommend Smalipatcher module to reboot directly into magisk system.
Updates: For each and every updates, either magisk or system update always patch the firmware with magisk and flash using odin(data will not be wiped if HOME_CSC used instead of CSC)
Downloads
Patched Firmware INS only
Odin
Samsung USB Drivers
NOTICE: Flash TWRP To Fix Reboot Issues After Patching ROM
????
Thankyou bro
But I think u should also post the process to patch the firmware.
Is this verified did u tried it physically? If yes then also make a video thanks
Gurjotjatt said:
Is this verified did u tried it physically? If yes then also make a video thanks
Click to expand...
Click to collapse
Yes Verified root, will try to post video soon
santhoosh said:
Yes Verified root, will try to post video soon
Click to expand...
Click to collapse
Ok thanks I will be waiting for your video:good:
---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------
santhoosh said:
Yes Verified root, will try to post video soon
Click to expand...
Click to collapse
And if I root will I receive updates? Like nextyear m30s will get andriod 10..will I be able to update ..Cruz I think magisk offers OTA updates to!?..am I right?
santhoosh said:
Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Rooting your phone may void warranty so don't root your device unless you know what you are doing.
Before Installing Magisk
Your device is non-A/B and uses system-as-root, so Magisk will be installed to the recovery partition of your device.
Installing Magisk for the first time REQUIRES a full data wipe, backup before continue( I would recommend to use SmartSwitch app for backup )
You have to have your bootloader unlocked before following the instructions.
Unlocking Bootloader
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot your device to download mode. Either use adb reboot download, or Turn off your device and hold volume up + volume down button, connect usb cable to PC
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk.
Enable developer options, and confirm that the OEM unlocking option exists and grayed out!
Your bootloader now accepts unofficial images in download mode.
Instructions
1. Download the firmware from the link given below.
2. Unzip the firmware to any folder on your PC.
3. Download and extract odin(link given below).
4. Install Samsung USB drivers if not installed automatically.
5. Reboot into download mode, odin will indicate blue in id:com if the device is connected.
6. Load AP, BL, CP and CSC files from extracted firmware. Do not load HOME_CSC and also leave USERDATA empty in odin.
Important: Uncheck “Auto Reboot” in Options!
7. Now Start Flashing!
8. Magisk is now successfully flashed to your device! But there are still several steps
before you can properly use the device.
9. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press and hold Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press and hold the Volume up + Power button to enter stock recovery.
10. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
11. This time, we can finally boot to the system with Magisk.
Important: Select Reboot system now, and immediately press the Volume up + power button after seeing the bootloader warning screen, release all buttons so it can boot to the magisk system.
12. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
13. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
14. You shall see Magisk Manager in your app drawer; if not, manually install the APK and continue to the next step. The app will automatically upgrade to the full Magisk Manager when you open it.
15. Enjoy Magisk
Click to expand...
Click to collapse
Where is the step for patching magisk, if you flash it on AP slot you must insert the Magisk_patched.tar file, it look like you did not do it by your self. The latest Magisk v20.1 may be does not work. the problem is random boot loop.
You can watch this video below it will show you clearly steps by steps, you just need to change the firmware that match your M30s model number.
redymedan said:
Where is the step for patching magisk, if you flash it on AP slot you must insert the Magisk_patched.tar file, it look like you did not do it by your self. The latest Magisk v20.1 may be does not work. the problem is random boot loop.
You can watch this video below it will show you clearly steps by steps, you just need to change the firmware that match your M30s model number.
://www.youtube.com/watch?v=ILvgki0pFHE
Click to expand...
Click to collapse
To make things easier I have already patched the firmware that I have attached, And it is patched with magisk latest v20.1 which is working fine.
Gurjotjatt said:
Ok thanks I will be waiting for your video:good:
---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------
And if I root will I receive updates? Like nextyear m30s will get andriod 10..will I be able to update ..Cruz I think magisk offers OTA updates to!?..am I right?
Click to expand...
Click to collapse
For every update either it may be magisk or firmware update, you need to patch firmware and flash it manually
shamsud said:
????
Thankyou bro
But I think u should also post the process to patch the firmware.
Click to expand...
Click to collapse
Post Updated with patch method
Please help: no "OEM unlocking" in Developer options of my M30s -- i.e. there is literally nothing between ""Enable Bluetooth HCI snoop log" and ""Running services" lines.
Thus after "adb reboot download" pressing Volume Up -- does nothing as well...
_hunter said:
Please help: no "OEM unlocking" in Developer options of my M30s -- i.e. there is literally nothing between ""Enable Bluetooth HCI snoop log" and ""Running services" lines.
Thus after "adb reboot download" pressing Volume Up -- does nothing as well...
Click to expand...
Click to collapse
Yes there is OEM unlocking in developers mode it's like 6the option
Gurjotjatt said:
Yes there is OEM unlocking in developers mode it's like 6the option
Click to expand...
Click to collapse
OK... funny thing: it is there now. The only thing is changed: I "gave up" on rooting -- and started setting up phone -- inserted SIM-card and attached my Google account. -- might be worth adding this to the first post.
Another issue: Odin flashing failed "in the middle" with small red text like "User firmware disabled".
Now phone is not bootable -- text appears:
And error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.
Click to expand...
Click to collapse
But the Smart Switch says "unsupported device"...
And "adb devices" can't see the phone now...
_hunter said:
Another issue: Odin flashing failed "in the middle" with small red text like "User firmware disabled".
Now phone is not bootable -- text appears:
But the Smart Switch says "unsupported device"...
And "adb devices" can't see the phone now...
Click to expand...
Click to collapse
Ok, can I know which firmware you used and odin version, also did you unlocked your bootloader properly?
its not workimg for my m30s i have followed every step
but its still showing cts profile:false
santhoosh said:
Ok, can I know which firmware you used and odin version, also did you unlocked your bootloader properly?
Click to expand...
Click to collapse
Resolved that issue flashing original (without Magisk patching) firmware.
Confirmed afterwards that you only can see "OEM unlocking" when your Google account attached.
But yes: it's appears that bootloader still was locked -- that "OEM unlocking" -- it's not grayed-out.
So, the question is: how you're supposed to unlock it?
-- "reboot download" and long pressing Volume Up there -- from the first post -- does nothing
-- "reboot recovery" + wipe data + reboot to bootloader -- from the "movie" -- does nothing
Comment if someone got success in Rooting m30s..!!
_hunter said:
Another issue: Odin flashing failed "in the middle" with small red text like "User firmware disabled".
Now phone is not bootable -- text appears:
But the Smart Switch says "unsupported device"...
And "adb devices" can't see the phone now...
Click to expand...
Click to collapse
I have the same problem.
Gurjotjatt said:
Comment if someone got success in Rooting m30s..!!
Click to expand...
Click to collapse
Considering we have Magisk available -- rooting is rather trivial. Setback is with unlocking bootloader
Finally Rooted
After couple of tries and disappearing OEM Unlocking button, finally I was successful in rooting using the method from this post. It took me some time to master booting directly into recovery after flashing patched images using Odin!
Also, did not realized that you need to connect USB cable to PC and press volume up and down at same time to get the bootloader unlock option.
Thank You OP.
341 redmi 10x 5G
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
https://unofficialtwrp.com/wp-content/uploads/2019/11/vbmeta.zip
1 flash miui recovery img
Go to fastboot and type fastboot flash recovery recovery1.img
After that hold power button and volume up button until you see a Chinese menu with three options first select option two after that option one and after that option two after wiping data you will see that three options again select option one and select option one then hold volume down button until you see fastboot
Type fastboot reboot fastboot
Wait
You will see fastbootd then rename corvus image to system.img
Then type
Fastboot flash system.img
Click power button
Wait
When you see corvus boot animation hold power button and volume down button until you see fastboot
Rename twrp image to recovery.img
Then type
Fastboot flash recovery recovery.img
Fastboot flash vbmeta vbmeta.img
Fastboot flash misc misc.bin
Fastboot boot recovery.img
In twrp flash permissiver 5 then reboot to system
Done.
If you want gapps download magisk app
Downloading Magisk App... | Magisk Manager
The download will automatically start in 5 seconds, please click here to access the download URL directly. If you are confused and want to know how to install the Magisk Manager on your phone you can click here.
magiskmanager.com
When it's download rename it to magisk.zip
Go to twrp
Flash it
Reboot to system rename it to magisk.apk and install it after that download this file
https://sourceforge.net/projects/magiskgapps/files/r/Core/MagiskGApps-core-V1.0.zip/download
After that go to magisk in modules go to install from storage and select zip you downloaded flash it with magisk after reboot you will see play store is added to your app drawer install Google apps you need from play store
https://sourceforge.net/projects/tipzbuilds/files/GSIs/CorvusROM/Alpha/20210329/Corvus_v15.0-RavenClaw-treble_arm64_ab-nonlite-29032021-Unofficial-1117.img.xz/download
While this technique certainly appears to have been researched. Running though the instructions has resulted in my device caught in a boot-loop. A pretty serious one too. I can no longer access the bootloader or recovery/
I fear the state my device is in is 'soft bricked/ I have no clue have to resolve this and without access to the bootloader I can't rollback anything.
Some friendly notes for Hsnmastoor:
You should re-format the post. Writing the instructions then at the end supply the links and file attachments in the order in which they should be run As it is, the instructions are confusing .
If anyone has any ideas how to correct the boot loop, plug me in
resirch26 said:
While this technique certainly appears to have been researched. Running though the instructions has resulted in my device caught in a boot-loop. A pretty serious one too. I can no longer access the bootloader or recovery/
I fear the state my device is in is 'soft bricked/ I have no clue have to resolve this and without access to the bootloader I can't rollback anything.
Some friendly notes for Hsnmastoor:
You should re-format the post. Writing the instructions then at the end supply the links and file attachments in the order in which they should be run As it is, the instructions are confusing .
If anyone has any ideas how to correct the boot loop, plug
Click to expand...
Click to collapse
You flashed permissive in twrp?
Hsnmastoor said:
You flashed permissive in twrp?
Click to expand...
Click to collapse
If not flash it
Hsnmastoor said:
If not flash it
Click to expand...
Click to collapse
sim card inactive
Hsnmastoor said:
You flashed permissive in twrp?
Click to expand...
Click to collapse
I can't flash anything. I no longer have access to the bootloader or recovery. Phone is stuck in a bootloop.
resirch26 said:
I can't flash anything. I no longer have access to the bootloader or recovery. Phone is stuck in a bootloop.
Click to expand...
Click to collapse
Hold power button and volume down for fastboot. Power with volume up for recovery
dothaison said:
sim card inactiv
Click to expand...
Click to collapse
Can you check IMEI?
Hsnmastoor said:
Bạn có thể kiểm tra IMEI không?
Click to expand...
Click to collapse
I can't test IMEI
Hsnmastoor said:
Can you check IMEI?
Click to expand...
Click to collapse
can you give me nvdata backup? . I have lost my IMEI.
Hsnmastoor said:
Can you check IMEI?
Click to expand...
Click to collapse
I have lost IMEI. Can you give me a backup nvram ? thank you.
dothaison said:
I have lost IMEI. Can you give me a backup nvram ? thank you.
Click to expand...
Click to collapse
Nvram.img
drive.google.com
Has anyone flashed this successfully?
any bugs? i flashed crdroid. it's too buggy
Hi everybody,
Still mad at myself for buying this phone (with MediaTek SOC) because of the lack of custom ROM support. Never had this issue before with any of my phones. If only i knew this before. The hardware of the phone is great, but the software makes it really frustrating to work with.
So i've tried a lot of things to either mod the original (Chinese) ROM so it's at least functional. And i have also tried multiple of these GSI ROM install methods. Everytime without succes.
I've tried your previous method with the 'GSI installer' and the one from this guide. Neither of them worked. (Boot loop). I have a feeling i run into trouble because (if i'm correct) the original ROM uses a 'super' partition and not a 'system' partition.
If i remember correctly the GSI installer couldn't continue because it couldn't find the system partition.
In this guide (for corvus) i figured i'd flash the system.img to my super partition. Of cource that doesn't work either. If only it was that simple.
Everytime it fails i have to flash back to a standard xiaomi ROM and start all over again. Because for some reason the TWRP backups also dont work for me.
So maybe i'm missing a step in the guide or i've already tried so much to mod my phone i've changed settings/partitions that shouldn't have been changed for this guide to work.
My bootloader is unlocked, i have/had TWRP 3.41 installed.
After a fail i flash back to the original ROM using Xiaomi ABD/Fastboot Tools (xiaomiABDFastbootTools.jar)
Any help would be appreciated!
I never had issue when I flashed the GSI from the crdroid guide did you make sure that you put the GSI installer.zip and the image file rename to system.img to the root internal storage??
Yes i did. It could also find the system.img file, but just wasn't able to flash it.
Can you tell mw what ROM you were flashing from?
Abducted23 said:
Yes i did. It could also find the system.img file, but just wasn't able to flash it.
Can you tell mw what ROM you were flashing from?
Click to expand...
Click to collapse
First I flashed crdroid. but did not like it. then I flashed blissrom using the same guide for crdroid. i just downloaded the rom posted on the guide. while for the bliss rom the arm64-bgN
Did you wipe data first before flashing?
Requirements:
-Tested working on firmware A125USQS3BVA2
-A MTK bootloader unlocking tool, tested working with UnlockTool
-This is for A125U on binary 3 ONLY
Special thanks to @Boster27 for translate guide and test method
Steps:
1- Boot into Download Mode (vol+ & vol- & pwr) and flash this custom BL file BL_A125.tar with ODIN patched using the BL button. The device will reboot to an error screen, this is normal.
2- Boot into BROM mode using Test Points (picture attached, needs light dissasembly). Using UnlockTool or your MTK tool of choice, head to the Samsung section and select A125, then on the BROM tab, choose Unlock Bootloader.
After this the device should reboot into recovery and perform a factory reset automatically. In case it doesn't, go into recovery manually (vol+ & pwr) and perform a factory reset. After this the device should boot normally.
3- Once the setup process is complete, connect to Wifi and enable Developer Options to confirm that OEM Unlock is enabled and unlocked. Install the latest version of Magisk Manager and use it to patch the AP file for the corresponding firmware.
4- Boot into Download Mode, make sure the AutoReboot option is unchecked in ODIN, and flash the magisk_patched.tar AP file, and the stock CP, CSC and USERDATA files. Then manually boot into recovery and perform a factory reset. After this the device should boot normally.
5- Once the setup process is complete again, connect to Wifi and enable Developer Options to confirm that OEM Unlock is still enabled and unlocked. Install the latest Magisk app and launch the app.
It should show a dialog asking for additional setup. Let it do its job and the app will automatically reboot your device.
And done! Phone is rooted on binary 3!
Hello
Thanks for the input.
I have a problem when I write the BL_A125.tar it bricks and I can't get into recovery mode to do a wipe.
Attached image of the error.
Thank you
I was able to do it, thanks.
I wrote full firmware, wiped and started from scratch, everything went ok, thanks
marioz17 said:
magisk_patched.tar AP file, and the stock CP, CSC and USERDATA files.
Click to expand...
Click to collapse
link to these files please
mfeliu07 said:
I was able to do it, thanks.
I wrote full firmware, wiped and started from scratch, everything went ok, thanks
Click to expand...
Click to collapse
magisk_patched.tar AP file, and the stock CP, CSC and USERDATA files.
do you have the link for the full firmware
unruly1981 said:
magisk_patched.tar AP file, and the stock CP, CSC and USERDATA files.
do you have the link for the full firmware
Click to expand...
Click to collapse
Yes here is https://samfw.com/firmware/SM-A125U/AIO/A125USQS3BVA2
marioz17 said:
Yes here is https://samfw.com/firmware/SM-A125U/AIO/A125USQS3BVA2
Click to expand...
Click to collapse
thank u
marioz17 said:
Yes here is https://samfw.com/firmware/SM-A125U/AIO/A125USQS3BVA2
Click to expand...
Click to collapse
does it have the magisk_patched.tar ?
unruly1981 said:
does it have the magisk_patched.tar ?
Click to expand...
Click to collapse
You need to patch the AP from firmware with magisk app
Did you have to take the phone apart. or can you just use the software.
timandolly said:
Did you have to take the phone apart. or can you just use the software.
Click to expand...
Click to collapse
Need to take apart, but this phone is so easy to open
Would this work on the S127DL? The Tracfone Galaxy A12.
Wish39 said:
Would this work on the S127DL? The Tracfone Galaxy A12.
Click to expand...
Click to collapse
i need the phone to test but you can try if the phone can enter BROM mode with testpoint
marioz17 said:
i need the phone to test but you can try if the phone can enter BROM mode with testpoint
Click to expand...
Click to collapse
Ok when I get one then I will try. Do you also have a unlockable BL for the Galaxy A21 (A215U, A215W, A215U1, S215DL)? I have a S215DL that I can test for that, but it is on binary 6.
Wish39 said:
Ok when I get one then I will try. Do you also have a unlockable BL for the Galaxy A21 (A215U, A215W, A215U1, S215DL)? I have a S215DL that I can test for that, but it is on binary 6.
Click to expand...
Click to collapse
I want this phone to be my next project
mfeliu07 said:
Hello
Thanks for the input.
I have a problem when I write the BL_A125.tar it bricks and I can't get into recovery mode to do a wipe.
Attached image of the error.
Thank you
View attachment 5591207
Click to expand...
Click to collapse
Did you add the ap ,modem and csc when you used the modded bootloader.
mfeliu07 said:
Hello
Thanks for the input.
I have a problem when I write the BL_A125.tar it bricks and I can't get into recovery mode to do a wipe.
Attached image of the error.
Thank you
View attachment 5591207
Click to expand...
Click to collapse
I got the same how did you fix?
timandolly said:
I got the same how did you fix?
Click to expand...
Click to collapse
You write the BL_A125.tar, disconnect the battery and unlock the booloader, after this it enters without problems and is deleted.
If it doesn't, disconnect battery and force enter recovery with volume up and power, do a factory reset
timandolly said:
Did you add the ap ,modem and csc when you used the modded bootloader.
Click to expand...
Click to collapse
This after unlocking booloader
mfeliu07 said:
You write the BL_A125.tar, disconnect the battery and unlock the booloader, after this it enters without problems and is deleted.
If it doesn't, disconnect battery and force enter recovery with volume up and power, do a factory reset
Click to expand...
Click to collapse
Thanks for helping. I rooted 4 note 4s and they all finally give out so I am going to try a newer phone