I have SM-N920CD variant and on stock Android M 6.0.1, Region:THR CSC:N920COJV2BPBA
I tried to flash TWRP through Odin in order to root and flash SkyHigh kernel but got stuck on Samsung logo bootscreen after flashing, I re-flashed my stock firmware to revive my phone and got it back working. I tried two different versions of Odin "Odin3 v3.10.7 and Odin3_v3.10.6" but still same results, I also used different PCs and downloaded TWRP twice.
Am I doing anything wrong or it is just me?
Did you try booting back to recovery and cleaning cache and rebooting. Sounds a little too basic I know but it has worked for me often enough. Just a thought.
Sent from my SM-N920G using Tapatalk
MSAKK said:
I have SM-N920CD variant and on stock Android M 6.0.1, Region:THR CSC:N920COJV2BPBA
I tried to flash TWRP through Odin in order to root and flash SkyHigh kernel but got stuck on Samsung logo bootscreen after flashing, I re-flashed my stock firmware to revive my phone and got it back working. I tried two different versions of Odin "Odin3 v3.10.7 and Odin3_v3.10.6" but still same results, I also used different PCs and downloaded TWRP twice.
Am I doing anything wrong or it is just me?
Click to expand...
Click to collapse
Try flashing again - this time ensure keep system as "read-only" option when you first flash TWRP. Then in TWRP recovery mode (straight after flashing & before rebooting), ensure that "system" is ticked/selected in the "Mount" option in TWRP menu - now reboot to system (you will need to tick/select "system" in Mount option each time if you boot into TWRP recovery mode).
swarup.siddharth said:
Did you try booting back to recovery and cleaning cache and rebooting. Sounds a little too basic I know but it has worked for me often enough. Just a thought.
Sent from my SM-N920G using Tapatalk
Click to expand...
Click to collapse
I can't even get to recovery, I can either get to download mode or stuck on bootscreen. I think it is the recovery getting messed up.
elmor0 said:
Try flashing again - this time ensure keep system as "read-only" option when you first flash TWRP. Then in TWRP recovery mode (straight after flashing & before rebooting), ensure that "system" is ticked/selected in the "Mount" option in TWRP menu - now reboot to system (you will need to tick/select "system" in Mount option each time if you boot into TWRP recovery mode).
Click to expand...
Click to collapse
I tried to enter recovery before rebooting and after flashing but with no luck. I assume to use the typical method (power+up+home). Am I missing something?
MSAKK said:
I tried to enter recovery before rebooting and after flashing but with no luck. I assume to use the typical method (power+up+home). Am I missing something?
Click to expand...
Click to collapse
Start all over again by re-flashing back to stock ROM/stock recovery and try again via Odin to flash TWRP - Make sure to go into recovery (TWRP) mode away straight away by 'power+vol up+home' buttons rather than booting into system.
Then mount system on in TWRP before rebooting to system - This worked for me, no probs since.
Also, ensure you have the correct TWRP .tar for your model (and ??maybe try an older Odin version for flashing TWRP).
Flash this TWRP through Odin:
https://dl.twrp.me/noblelte/twrp-3.0.0-0-nobleltezt-nobleltezt.img.tar.html
elmor0 said:
Start all over again by re-flashing back to stock ROM/stock recovery and try again via Odin to flash TWRP - Make sure to go into recovery (TWRP) mode away straight away by 'power+vol up+home' buttons rather than booting into system.
Then mount system on in TWRP before rebooting to system - This worked for me, no probs since.
Also, ensure you have the correct TWRP .tar for your model (and ??maybe try an older Odin version for flashing TWRP).
Click to expand...
Click to collapse
I tried that but nothing happened, it kept me on download mode otherwise system is booting.
Is it possible to enter recovery directly from download mode without power off?
Battlehero said:
Flash this TWRP through Odin:
https://dl.twrp.me/noblelte/twrp-3.0.0-0-nobleltezt-nobleltezt.img.tar.html
Click to expand...
Click to collapse
That is the download link I have been using.
Sent from my SM-N920C using XDA Free mobile app
I don't think you can go from download mode directly to TWRP recovery mode without power off.......... Try re-booting from download mode but before it re-starts quickly hold 'power+vol up+home'.
Have you tried starting from scratch i.e back to stock recovery, and tried flashing with an older version of Odin?
elmor0 said:
I don't think you can go from download mode directly to TWRP recovery mode without power off.......... Try re-booting from download mode but before it re-starts quickly hold 'power+vol up+home'.
Have you tried starting from scratch i.e back to stock recovery, and tried flashing with an older version of Odin?
Click to expand...
Click to collapse
I tried from scratch but with same results. Could it be ROM related?
elmor0 said:
Start all over again by re-flashing back to stock ROM/stock recovery and try again via Odin to flash TWRP - Make sure to go into recovery (TWRP) mode away straight away by 'power+vol up+home' buttons rather than booting into system.
Then mount system on in TWRP before rebooting to system - This worked for me, no probs since.
Also, ensure you have the correct TWRP .tar for your model (and ??maybe try an older Odin version for flashing TWRP).
Click to expand...
Click to collapse
i have tried that, and got an issues related to mount the storage as well, but able to overcome all that
and now the phone went from stuck on "Samsung" logo, into a loopboot
all this with the Samsung Stock ROM
but at the moment i install Lineage ROM, it works immediately
tried my best to make it work with samsung stock rom, but i couldn't
Related
Hi all,
I'm trying to install Cyanogenmod following techbeasts.com tutorial but I'm stuck at the first step : installingTWRP (or CWM).
I followed precisely all the instructions (I allow debugging mode, I installed samsung drivers, I start the phone in download mode, I connect it with OEM cable, I start Odin, it sees the phone, I select the tar.md5 file.), Odin confirms it went well (green box writing "PASS"), but when I try to boot the recovery mode by holding Volume up + Home + Power it seems to boot another recovery software that doesn't offer a backup or a flashing options: "Android system recovery <3e>"
Can't get it to run TWRP or CWM... Can't install the supersu package.
What I'm I doing wrong? Can someone help?
Try to untick Auto Reboot option from odin. I had similiar issues and reason was if you have updated your phone with OTA-updates then it installs some kind of backup script. When your phone boots again after you had installed twrp it installs stock recovery during boot. So untick autoreboot, flash twrp and force boot straight to recovery without letting phone boot to OS. You can also try to pull battery out, put it back and then boot into recovery mode.
Sorry my english and try to understand.
adbhitman said:
Try to untick Auto Reboot option from odin. I had similiar issues and reason was if you have updated your phone with OTA-updates then it installs some kind of backup script. When your phone boots again after you had installed twrp it installs stock recovery during boot. So untick autoreboot, flash twrp and force boot straight to recovery without letting phone boot to OS. You can also try to pull battery out, put it back and then boot into recovery mode.
Sorry my english and try to understand.
Click to expand...
Click to collapse
Great it worked, thanks a lot !
But now I'm stuck on the next step : flashing CM11
I rooted my phone, booted TWRP, chose "install>cm11" (the zip downloaded from nova fusion) but it says "failed" after a few sec...
I would post my TWRP log but the forum prevents me doing so...
Well I get few things that you could check first.
1. Do factory reset for example from twrp. Factory reset is needed/recommended before installing custom rom from offical OS.
2. Sometimes just installing fails almost immediately if you have ticked check zip signature.
After you have installed new rom clear cache and davilk cache just in case. I'll do that every time if I install or update custom roms. Also don't forget to install right gapps package after you have installed rom.
Sorry my english and try to understand.
ok just realized i downloaded the wrong cm image (the odin one, not the recovery)
everything running smooth now
Okay happy to hear that everything is fine now. Happy playing with custom roms
Finally decided to root my own device to find out that the recovery is not working when I try going into it on the bootloader mode. It is a rooted device and I've tried flashing the twrp recovery through the command prompt and also through the flashify app. It only works when I try booting in from the flashify app but doesn't work through the bootloader, when trying it through the bootloader i select the recovery and the phone turns off. Anyone have a clue of how I could try to make it work, I would appreciate any help. Thanks
Blue.F150 said:
Finally decided to root my own device to find out that the recovery is not working when I try going into it on the bootloader mode. It is a rooted device and I've tried flashing the twrp recovery through the command prompt and also through the flashify app. It only works when I try booting in from the flashify app but doesn't work through the bootloader, when trying it through the bootloader i select the recovery and the phone turns off. Anyone have a clue of how I could try to make it work, I would appreciate any help. Thanks
Click to expand...
Click to collapse
Looks like a system error which can be solved only if you flash the factory image again
which command did yu use "fastboot flash recovery (twrp File name ).img
If it didn't work, flash cwm and then twrp 8.6.0. Maybe it'll work Or flash twrp img while ur in twrp itself. Or download advanced reboot if ur using stock rom.
james11705 said:
Looks like a system error which can be solved only if you flash the factory image again
which command did yu use "fastboot flash recovery (twrp File name ).img
If it didn't work, flash cwm and then twrp 8.6.0. Maybe it'll work Or flash twrp img while ur in twrp itself. Or download advanced reboot if ur using stock rom.
Click to expand...
Click to collapse
Yea it was the fastboot flash recovery trwp.... then tried it and didnt work. Thanks I'll try out the other options you gave me. I tried reflashing stock everything and booting into recovery now it didnt work again with the stock recovery.
Blue.F150 said:
Yea it was the fastboot flash recovery trwp.... then tried it and didnt work. Thanks I'll try out the other options you gave me. I tried reflashing stock everything and booting into recovery now it didnt work again with the stock recovery.
Click to expand...
Click to collapse
Like flashing the full firmware? It should work, because something is wrong with ur recovery system.
james11705 said:
Like flashing the full firmware? It should work, because something is wrong with ur recovery system.
Click to expand...
Click to collapse
I have the same problem. Flashed the stock firmware. Then flashed TWRP in fastboot, but whenever i select recovery from the fastboot menu, the phone just shuts off. Only way to get into recovery is by Flashify app too...
I followed the steps in this guide attempting to flash a rom. https://forum.xda-developers.com/tm...lopment/rom-stock-debloated-deodexed-t3423387
I was able to flash the BL and modem no problem. I proceeded to flash twrp and have been stuck at boot since. I can only go back into DL mode. Read a few places that said to reinstall rom. How do i go about installing a rom via odin? Any help is greatly appreciated.
jleed88 said:
I followed the steps in this guide attempting to flash a rom. https://forum.xda-developers.com/tm...lopment/rom-stock-debloated-deodexed-t3423387
I was able to flash the BL and modem no problem. I proceeded to flash twrp and have been stuck at boot since. I can only go back into DL mode. Read a few places that said to reinstall rom. How do i go about installing a rom via odin? Any help is greatly appreciated.
Click to expand...
Click to collapse
Okay. Here's what you do...
First, boot to DOWNLOAD MODE. Once in Download Mode, press the keys again like you are booting to Download Mode (VOLUME DOWN + HOME + POWER)
Watch the screen while holding the keys. When the screen goes blank, switch to the key combination for booting RECOVERY (VOLUME UP + HOME + POWER) and hold them until the TWRP screen appears. If the TWRP screen does not appear then we know TWRP didn't stick when you flashed it via Odin.
If the TWRP screen appears, release the keys and let it continue to boot to TWRP.
If TWRP does not boot, then I'd suggest flashing the stock firmware for your device. You can download the stock firmware for your device from www.sammobile.com or from www.updato.com
Sammobile.com is a very slow download unless you pay for a premium account. Updato is much faster. Make sure to select the correct region for your device before downloading the firmware.
Which version of Odin are you using? I've been using 3.12.3 and haven't had any problems at all with this version.
Once you habe downloaded the stock firmware, open Odin. Boot your device to Download Mode and then connect your USB cable. Make sure Odin shows you are connected.
Next, click the OPTIONS TAB in Odin and un-check
AUTO REBOOT. Then, select the AP TAB in Odin and navigate to the firmware file you have downloaded. Let Odin do its thing to verify the file and click START to begin the flash. Once the flash is complete, disconnect the USB Cable and press the key combination for booting to Download Mode again. Once the screen goes black, switch to the key combination for booting RECOVERY. Once in recovery you can select the reboot option to boot your device normally and start fresh from there and attempt to flash TWRP again.
Also, which Note 5 do you have?
fast69mopar said:
Okay. Here's what you do...
First, boot to DOWNLOAD MODE. Once in Download Mode, press the keys again like you are booting to Download Mode (VOLUME DOWN + HOME + POWER)
Watch the screen while holding the keys. When the screen goes blank, switch to the key combination for booting RECOVERY (VOLUME UP + HOME + POWER) and hold them until the TWRP screen appears. If the TWRP screen does not appear then we know TWRP didn't stick when you flashed it via Odin.
If the TWRP screen appears, release the keys and let it continue to boot to TWRP.
If TWRP does not boot, then I'd suggest flashing the stock firmware for your device. You can download the stock firmware for your device from www.sammobile.com or from www.updato.com
Sammobile.com is a very slow download unless you pay for a premium account. Updato is much faster. Make sure to select the correct region for your device before downloading the firmware.
Which version of Odin are you using? I've been using 3.12.3 and haven't had any problems at all with this version.
Once you habe downloaded the stock firmware, open Odin. Boot your device to Download Mode and then connect your USB cable. Make sure Odin shows you are connected.
Next, click the OPTIONS TAB in Odin and un-check
AUTO REBOOT. Then, select the AP TAB in Odin and navigate to the firmware file you have downloaded. Let Odin do its thing to verify the file and click START to begin the flash. Once the flash is complete, disconnect the USB Cable and press the key combination for booting to Download Mode again. Once the screen goes black, switch to the key combination for booting RECOVERY. Once in recovery you can select the reboot option to boot your device normally and start fresh from there and attempt to flash TWRP again.
Also, which Note 5 do you have?
Click to expand...
Click to collapse
Hey, thanks for your response. So I was able to get my System back to working. I had to downoad the stock firmware through sammobile. I ended up paying for the fast download (30days of service) Well ill keep updato in mind if this every happens again. Im on N920TUVU4EQE1 For the n920T since i had already flashed the modem and bootloader before i flashed twrp. I'm on Odin 3.12.3 as well.
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
Apparently the kernel i was using wasnt allowing twrp to install. So now i have to figure out how to root my new stock firmware and install recover so i can flash a rom.
jleed88 said:
Hey, thanks for your response. So I was able to get my System back to working. I had to downoad the stock firmware through sammobile. I ended up paying for the fast download (30days of service) Well ill keep updato in mind if this every happens again. Im on N920TUVU4EQE1 For the n920T since i had already flashed the modem and bootloader before i flashed twrp. I'm on Odin 3.12.3 as well.
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
Apparently the kernel i was using wasnt allowing twrp to install. So now i have to figure out how to root my new stock firmware and install recover so i can flash a rom.
Click to expand...
Click to collapse
What you have to do is this...
Flash TWRP, swipe to allow system modifications and then flash the no_verity_opt_encrypt_5.1.zip available from
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
This zip will disable dm-verity and forced encryption in the fstab and allow you to boot normally.
Once this had been done you can flash the root zip of your choice and go to town with debloating, custom ROM's and custom kernels.
jleed88 said:
Hey, thanks for your response. So I was able to get my System back to working. I had to download the stock firmware through sammobile. I ended up paying for the fast download (30days of service) Well ill keep updato in mind if this every happens again. Im on N920TUVU4EQE1 For the n920T since i had already flashed the modem and bootloader before i flashed twrp. I'm on Odin 3.12.3 as well.
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
Apparently the kernel i was using wasnt allowing twrp to install. So now i have to figure out how to root my new stock firmware and install recover so i can flash a rom.
Click to expand...
Click to collapse
fast69mopar said:
What you have to do is this...
Flash TWRP, swipe to allow system modifications and then flash the no_verity_opt_encrypt_5.1.zip available from
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
This zip will disable dm-verity and forced encryption in the fstab and allow you to boot normally.
Once this had been done you can flash the root zip of your choice and go to town with debloating, custom ROM's and custom kernels.
Click to expand...
Click to collapse
When i flashed TWRP i unchecked the Auto-Reboot option. did a key combo to get to twrp but it didnt ask me to swipe to allow system modification. So i went ahead and flashed no_verity_opt_encrypt_5.1.zip with success. Proceeded to flash SuperSU-v2.66 and it got stuck at -Creating paths. I rebooted to recovery and found this guide https://forum.xda-developers.com/galaxy-s6/general/root-s6-nougat-supersu-t3570740
Coming from sickmade 6.0.1 and through all the struggles i am now at stock ROOTED firmware EQG3 andriod 7.0! I just had to take my time and search around a bit. You guys are all amazing. Hopefully if someone has this problem they will find this thread.
jleed88 said:
When i flashed TWRP i unchecked the Auto-Reboot option. did a key combo to get to twrp but it didnt ask me to swipe to allow system modification. So i went ahead and flashed no_verity_opt_encrypt_5.1.zip with success. Proceeded to flash SuperSU-v2.66 and it got stuck at -Creating paths. I rebooted to recovery and found this guide https://forum.xda-developers.com/galaxy-s6/general/root-s6-nougat-supersu-t3570740
Coming from sickmade 6.0.1 and through all the struggles i am now at stock ROOTED firmware EQG3 andriod 7.0! I just had to take my time and search around a bit. You guys are all amazing. Hopefully if someone has this problem they will find this thread.
Click to expand...
Click to collapse
Glad it's working for you. Good job. Now you can make your Note 5 your own. I'm an S6 Edge Plus user. We use the exact same ROM as the Note 5. We just use a different kernel. Happy flashing. If you run into any issues don't hesitate to ask me or anyone else here at XDA. This is a great place to read and learn especially with your Note 5. If a problem has occurred before you can bet that someone has posted about it and you will find a solution.
the phone initially booted up normally. and i power off try to enter recovery mode but i got bootloop , is there any way to get into odin mode , recovery mode is broken ( i flashed recovery with odin it took 15 minutes so i click stop and it crashed ) my phone is sm m20
Hello. I have a Samsung tab S2 T719 that is perma stuck in bootloop. Originally the recovery mode was working but i probally messed that up aswel by flashing some TWRP custom recovery.. it now bootloops even when i turn it on in recovery mode. I am not sure if the tablet has USB debugging on.. also, I just tried to flash another stock nougat firmware on to it via odin and it passed but when i turn it on it has the same bootloop issue. Is there anything i can do to it ? the tablet is in brilliant condition physically and it would be a shame to sell it for parts or bin it >_< Regards
You need the correct recovery mode before ROM. After flashing TWRP, go to TWRP, backup EFS, format data, then flash ROM. Don't boot after flashing TWRP, just go directly from download mode to recovery mode
sarjarim said:
You need the correct recovery mode before ROM. After flashing TWRP, go to TWRP, backup EFS, format data, then flash ROM. Don't boot after flashing TWRP, just go directly from download mode to recovery mode
Click to expand...
Click to collapse
I flashed a working TWRP now and thats all dandy and it works and then i followed ur steps and after i flashed the rom i tried to turn it on and it continues the endless bootloop after it says ''installing applications''... it did exactly the same with all roms i tried.
Could u try another ROM, if it's still bootloop then maybe hardware problem.
Hi I bring you how to root and install twrp on A70 any version ,I think its work on all new samsung device:good:
note :
1-first unlock your bootloader https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
2-in all step Remove auto reboot in odin
requirement files :
PeaZip
https://www.peazip.org/download-installer-p-windows.html
TWRP recovery.img mack it tar with PeaZip
https://github.com/Grarak/android_device_samsung_a70q-twrp/releases
vbmeta.tar Vbmeta.img- https://www.androidfilehost.com/?fid...26312261811717
Stock recovery.img from your stock rom [ you can download your device rom and extract stock recovery ] and mack it tar with PeaZip
Magisk 20.1- https://www.androidfilehost.com/?fid...26312261797449
Odin3- https://www.androidfilehost.com/?fid...26312261811763
Samfirm- https://www.androidfilehost.com/?fid...26312261811762
Lets start
1- in stock roms maybe work on custom roms
2-boot in to download mode and flash vbmeta.tar via odin in ap
3-after that reboot to recovery by pressing vol+ and power and clear data and cache in stock recovery
4- reboot again in to download mod and now flash twrp via odin in ap
5-reboot to twrp recovery by pressing vol+ and power and slide right to modify. Click wipe, click format data, type yes after that go back and reboot to recovery. slide right to modify, click mount, if mount system partition read-only is checked, back out and reboot back to recovery and check mount again, it should now be unchecked. . Now click Vendor so its checked and system should be unchecked, back out.
6- Copy Magisk 20.1 to the External sd card. In TWRP click install, select storage and choose micro sd card, click on magisk and slide right to confirm. (you must have vendor checked in mount or it wont flash properly). when done, click all way back click reboot to download.
7- now flash stcok recovery tar file via odin and reboot your device to system
8-after your device start run Magisk and update it by install options
well done you have twrp and rooted device :fingers-crossed::good::fingers-crossed:
i think this method work on all new samsung device and just you have own your device file like
twrp /stock recovery /vbmeta
note : if your twrp Stuck on twrp logo you have to install stock recovery and repeat from step 2
tested device A705FN:fingers-crossed:
thanks to :good:
MarvinMod
Grarak
and other to help me in this method
thanks a lot. i will test it today and check back here tomorrow
edit: i cant flash twrp via odin. download mode says "only official released binaries are allowed"
bootloader unlocked
oem unlock grayed
vmeta flashed
wipe data cache
but cant flash twrp. tried to download latest version but still no joy
i have 705FN with A705FNXXU5BTC2 rom installed
thewalekk said:
thanks a lot. i will test it today and check back here tomorrow
edit: i cant flash twrp via odin. download mode says "only official released binaries are allowed"
bootloader unlocked
oem unlock grayed
vmeta flashed
wipe data cache
but cant flash twrp. tried to download latest version but still no joy
i have 705FN with A705FNXXU5BTC2 rom installed
Click to expand...
Click to collapse
Hi i think you have to first flash 4file rom on your device
Plez check this maybe help you
https://forum.xda-developers.com/sa...torial-root-november-security-update-t3715661
Your bootloader must be updated
seli1987 said:
Hi i think you have to first flash 4file rom on your device
Plez check this maybe help you
https://forum.xda-developers.com/sa...torial-root-november-security-update-t3715661
Your bootloader must be updated
Click to expand...
Click to collapse
Hi thanks for the reply. But the day before i read this post, i flashed the latest firmware from sammobile which is the rom i told in the post (BTC2). Doesnt latest firmware include latest BL? Where can i find the current version of my BL in my phone?
thewalekk said:
Hi thanks for the reply. But the day before i read this post, i flashed the latest firmware from sammobile which is the rom i told in the post (BTC2). Doesnt latest firmware include latest BL? Where can i find the current version of my BL in my phone?
Click to expand...
Click to collapse
Try again flash 4 file frimware and let device start to system after that reboot to download mod and flash vbmeta.tar and let your device start to system
After that reboot to stock recovery and wipdata and cach and reboot to download mod and now flash twrp
The wrong is with your bootloader if you cant fix it try to search your problem in google
You are not only one have this problem
I did every thing from scratch. Even lock and unlock the bootloader.
I am tring to make sence. Vbmeta is "verified boot". So the idea is trick the phone with our own bootloader so that we can flash twrp.
Since i cant flash twrp, vbmeta should be updated.
Am i right?
thewalekk said:
I did every thing from scratch. Even lock and unlock the bootloader.
I am tring to make sence. Vbmeta is "verified boot". So the idea is trick the phone with our own bootloader so that we can flash twrp.
Since i cant flash twrp, vbmeta should be updated.
Am i right?
Click to expand...
Click to collapse
Unlock bootloader, factory reset, unsure oem is unlocked and grayed out in settings >developer options.
Then flash vbmeta, manual reboot to download mode, flash twrp, boot to twrp, factory reset in twrp , flash magisk zip then factory reset again, now boot system.
The vbmeta you flash is empty and allows flashing third party zips.
Hiii, i did almost everthing, but when i boot in recovery and go to mount, system partition read-only is checked. already tried 4 for times reboot to recovery but still checked.
Yes, i slide right to allow to modify. Any suggestion ?
BubSystemS said:
Hiii, i did almost everthing, but when i boot in recovery and go to mount, system partition read-only is checked. already tried 4 for times reboot to recovery but still checked.
Yes, i slide right to allow to modify. Any suggestion ?
Click to expand...
Click to collapse
Go ahead with the steps. Ignore mount system.
Let's see what happens
Worst scenario, you soft brick the phone or bootloop which can be fixed by flashing stock rom again.
Make sure you have stock rom and you backup your data
Any way to pass SatefyNet?
Instal this path in Magisk:
https://github.com/kdrag0n/safetynet-fix/releases/download/v1.1.0/safetynet-fix-v1.1.0.zip