i tried rooting my phonw using magisk zip but when i tried it camw up saying filw integrity issue and that i had to reset the phone, have i done something wrong or have Samsung in newer updated made it harder to root? i had root previously so hence it was easy for TWRP but i have never had that happen. I'm only running stock now after a Lineage OS update caused my phone to get stuck booting. Phone is a Samsung galaxy A5 (2017)
elderwolf123 said:
i tried rooting my phonw using magisk zip but when i tried it camw up saying filw integrity issue and that i had to reset the phone, have i done something wrong or have Samsung in newer updated made it harder to root? i had root previously so hence it was easy for TWRP but i have never had that happen. I'm only running stock now after a Lineage OS update caused my phone to get stuck booting. Phone is a Samsung galaxy A5 (2017)
Click to expand...
Click to collapse
This will give you an idea as to why
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Related
Okay, I just replaced my Google Galaxy Nexus with the Verizon Galaxy S4 (SCH-I545) Build JSSI5J.I545VRUEMK2
first I downloaded the odin and stock rom to have on hand, just in case...
I first tested to see if I could use odin to go from stock rom to stock rom, just as a test and we are all set there..
second I rooted the phone...awesome great, right? Wrong
after rooting and confirming root with root checker, I loaded Rom Manager, flashed it with the latest recovery...rebooted to recovery and bam I get an error message "android system recovery <3e>"
I have even manually downloaded the recovery from CWM
I have tried rooting with both saferoot&disableKNOX as well as I545ALL-IN-ONE-TOOL, the VerizonGalaxyS4RootMDK, and I have done the LOKI method, I still get the same recovery error message.
So as far as I can get is a rooted device, I cannot get a custom recovery loaded successfully even though CWM say the flash is successful
Anyone, have any ideas where I am going wrong? this is driving me crazy and I am pulling all my hair out...oh wait, I don't have any...lol
Please help, it would be much appreciated!
xanuri said:
Okay, I just replaced my Google Galaxy Nexus with the Verizon Galaxy S4 (SCH-I545) Build JSSI5J.I545VRUEMK2
first I downloaded the odin and stock rom to have on hand, just in case...
I first tested to see if I could use odin to go from stock rom to stock rom, just as a test and we are all set there..
second I rooted the phone...awesome great, right? Wrong
after rooting and confirming root with root checker, I loaded Rom Manager, flashed it with the latest recovery...rebooted to recovery and bam I get an error message "android system recovery <3e>"
I have even manually downloaded the recovery from CWM
I have tried rooting with both saferoot&disableKNOX as well as I545ALL-IN-ONE-TOOL, the VerizonGalaxyS4RootMDK, and I have done the LOKI method, I still get the same recovery error message.
So as far as I can get is a rooted device, I cannot get a custom recovery loaded successfully even though CWM say the flash is successful
Anyone, have any ideas where I am going wrong? this is driving me crazy and I am pulling all my hair out...oh wait, I don't have any...lol
Please help, it would be much appreciated!
Click to expand...
Click to collapse
Have you tried UNLOCKING your device first? Sometimes this happens when the phone is locked to a certain company and when you try to do custom roms they aren't successful sometimes due just this fact, at least for me this worked on my Verizon S4 (I don't care much about warranties anymore once I change roms)
Hope this works
firemex said:
Have you tried UNLOCKING your device first? Sometimes this happens when the phone is locked to a certain company and when you try to do custom roms they aren't successful sometimes due just this fact, at least for me this worked on my Verizon S4 (I don't care much about warranties anymore once I change roms)
Hope this works
Click to expand...
Click to collapse
after rooting and during boot, I get the "Samsung Custom" with a unlocked padlock screen...so I assume that means it is unlocked??
firemex said:
Have you tried UNLOCKING your device first? Sometimes this happens when the phone is locked to a certain company and when you try to do custom roms they aren't successful sometimes due just this fact, at least for me this worked on my Verizon S4 (I don't care much about warranties anymore once I change roms)
Hope this works
Click to expand...
Click to collapse
Or are you talking about CARRIER unlocking the SIM? If so do you happen to have a reference for doing this to a Verizon Phone?
xanuri said:
Okay, I just replaced my Google Galaxy Nexus with the Verizon Galaxy S4 (SCH-I545) Build JSSI5J.I545VRUEMK2
first I downloaded the odin and stock rom to have on hand, just in case...
I first tested to see if I could use odin to go from stock rom to stock rom, just as a test and we are all set there..
second I rooted the phone...awesome great, right? Wrong
after rooting and confirming root with root checker, I loaded Rom Manager, flashed it with the latest recovery...rebooted to recovery and bam I get an error message "android system recovery <3e>"
I have even manually downloaded the recovery from CWM
I have tried rooting with both saferoot&disableKNOX as well as I545ALL-IN-ONE-TOOL, the VerizonGalaxyS4RootMDK, and I have done the LOKI method, I still get the same recovery error message.
So as far as I can get is a rooted device, I cannot get a custom recovery loaded successfully even though CWM say the flash is successful
Anyone, have any ideas where I am going wrong? this is driving me crazy and I am pulling all my hair out...oh wait, I don't have any...lol
Please help, it would be much appreciated!
Click to expand...
Click to collapse
i got exact same problem only i can root my device so far any solution ?
Verizon locked bootloaders. I tried this with twrp and had that issue too
Sent from my SCH-I545 using xda app-developers app
I realize this a 2-year-old post, but would you happen to still have the stock firmware (I545VRUEMK2) for this thing? I have an older Jellybean unit that I need to fix (and want to keep JB as I can root it easily).
Thanks
I have rooted many mobile devices and flashed numerous ROMS. However I recently purchased a Galaxy Note 10.1 2014 edition and have not been able to get very far in my attempts to root, etc. I have tried Odin and CF-Auto-Root and although it appears to be successful the device is not rooted. I want to install TWRP and then the knox free stock ROM. I am able to push the necessary files to the sdcard with ADB and I can see that the files are in /sdcard using ES File explorer. However when I boot into recovery mode /sdcard is red and at the top of the list and it will not let me navigate to it to install any zip files. I though at first it might be because of the MobileIron I use for company email but I did a factory reset and still have this problem. I just need to root the device so I can use Titanium BU to remove the Samsung apps I don't want. Any help with this would be most appreciated. What do I need to do?
~metafizik
Ultimately I think the first thing I need to resolve is that even though the Odin rooting process appears to be working according to Odin(PASS). The fact is that regardless which combination of Odin 3.07/3.09 and CF-Auto-Root (tried 2 versions) even though Odin says it was successful it turns out the device is not getting rooted. This should be a no brainer but for for whatever reason this device will not root so far.
Bumping this as I have not received any replies. I am hoping that someone has run across a similar situation and can offer some guidance.
Thank you,
~metafizik
metafizik said:
Ultimately I think the first thing I need to resolve is that even though the Odin rooting process appears to be working according to Odin(PASS). The fact is that regardless which combination of Odin 3.07/3.09 and CF-Auto-Root (tried 2 versions) even though Odin says it was successful it turns out the device is not getting rooted. This should be a no brainer but for for whatever reason this device will not root so far.
Click to expand...
Click to collapse
Did you install super su?Did you try to flash twrp.If your not rooted twrp will ask to root.Have you tried to install a root app and see if the permissions pop up?
When you say recovery do you mean the stock one?Im pretty sure i had same problem.It was rooted but i thought it wasnt.
mikep2323 said:
Did you install super su?Did you try to flash twrp.If your not rooted twrp will ask to root.Have you tried to install a root app and see if the permissions pop up?
When you say recovery do you mean the stock one?Im pretty sure i had same problem.It was rooted but i thought it wasnt.
Click to expand...
Click to collapse
This is a very strange deal. As previously stated I have tried various combinations of Odin and CF-Auto-Root and the Odin process completes with PASS. However when I boot the OS and run Titanium it is never able to gain root access and Root Checker says it is not rooted. Unfortunately even after doing a factory reset the MobileIron Admin console at work says it is rooted so I can't use it for company email. I have definitely tripped the Knox bit. Also I want to install TWRP and have pushed the file to /sdcard and can see it there using a file explorer app. However when I boot into stock recovery I cannot see any of the zip files I have copied there. I also tried to flash TWRP with Odin and again it completes with PASS but TWRP never gets installed. And yes I installed SuperSU but did so from the Play Store.
I purchased this device just last week. I am wondering if maybe Samsung has changed things in the past few weeks and locked these friggin things down even more? This is the first device of many I have owned that I couldn't root or install a custom recovery or ROM. In any case this will definitely be my last Samsung device. I would however like to do whatever I so desire with it since I paid good money for it.
I have resolved all of the problems I was having. They were all due to Knox and my inexperience with it. I was fortunate to have customized my Note 2 before it received the Knox updates. All is well and there is no new unknown vodoo lurking in the latest iteration of Samsung devices.
So, I got a Samsung Galaxy A5 2017 (SM-A520F)
I've recently installed Nougat 7.0 after having another OS. I also rooted that OS, but I got some problems like camera not starting etc..
Then I come back installing Nougat and everything works fine. But I would like to root it as well. I install TWRP ricovery and everything it's fine. Then I install Super SU and there everything it's fine, it says "done", but it also come up with a message like "Couldn't mount /data". And when I boot my phone it says "Unable to restart. Verification failed bla bla..." and there is also a reset button. But if I use it, it brings me back to TWRP and there... it can't wipe everything and there's again "couldn't mount /storage" or something similar.
Now, I also tried using different recoveries like TWRP 3.1-0-0 unofficial, different installations of TWRP 3.0-2-0 but still, nothing. I then tried using another installation of nougat, the september one, nothing again. Finally, I used another SuperSU and nothing. Is there any solution?
I also forgot to mention that previously I had nougat and I successfully rooted it! But, camera and other things didn't work.
Sorry for my bad english, I'm italian thanks in advance!
Have you tried the cwm a520f recovery?
This worked for me.
Also try installing the "no-verity-no-encrypt_ashyx.zip"
Hi7m3up said:
Have you tried the cwm a520f recovery?
This worked for me.
Also try installing the "no-verity-no-encrypt_ashyx.zip"
Click to expand...
Click to collapse
I've just tried, the installation doesn't reports error but it doesn't work anyway: same error.
When this happened to me it seemed to be when I used supersu v2.79 size 5.62 Mb however when I downloaded it from another site the size of the zip file changed to 5.67 Mb (same version v2.79)
Also I found although I'm not 100% that when I used twrp recovery that the same thing happened to me each time and I used cwm recovery to root then changed to twrp after root was gained.
It might be worth mentioning I think I pressed the factory reset when the no-verity-no-encrypt screen appeared and changed recovery to cwm it took me a few goes to get root but I'd start with supersu file make sure it's 5.67mb
AN1MuSS said:
I've just tried, the installation doesn't reports error but it doesn't work anyway: same error.
Click to expand...
Click to collapse
That's because you need to FORMAT your data partition after flashing.
So, I got an A50, and I'm really happy that I did. However, switching from a phone that had TWRP and Magisk is something I am not finding easy, even if the phone is much faster than my old one. So, of course, after thoroughly reading my warranty, which had no mention of not covering software device damage, I decided to to go ahead and try to flash TWRP and then install Magisk. I went ahead and easily figured out that my model is SM-A505FN (which would have been all that I needed for my old phone). Seeing that there were successful attempts at installing TWRP and Magisk on this model, I decided to try it out, but quickly found myself with a soft bricked phone, so off to finding a Stock ROM I went. After booting it up again I did more digging, but that yielded no result, however, I decided to try using Magisk manager to patch the AP file and then tried patching that. Sadly, no luck. I even went as far as trying a few of those programs that would root your phone from your PC, but that proved to be a waste of time as even that didn't work (which I suspected would happen, but whatever).
While fondling with the phone, I noticed something in the recovery. It wrote a50xx and then I realized that that must have been the reason for nothing working. And now we get to the title of this post. Has anybody been successful at rooting or flashing TWRP on an a50xx device, and, if so, would you be so kind as to elaborate on how you did it?
If not, I guess I should either wait, or look into trying to port TWRP to a50xx myself.
Edit: In case I do decide to port TWRP, any help or pointers are welcome.
Hello @BrainReader,
Same problem here! I tried rooting my device (sm-a505fn as well) by flashing the ap-file using magisk manager. I kept ending in a bootloop. I tried the latest version v20.x and even tried v19.3 which should work stable according to this thread: https://forum.xda-developers.com/galaxy-a50s/how-to/guide-root-galaxy-a50s-magisk-v19-3-t4001271.
I hope this thread gets more attention and someone finds a solution for rooting the a50!
Kind regards,
Shademaster639
I have a rooted a505fn twrp is not working but rooting with magisk works fine. Every magisk version above 19.3 is giving problems. The latest magisk give very much reboots. What I did I first installed the newest software with Odin. Then install magisk 19.3 after that I set in magisk the update channel to get no further then 19.3.
That patch the AP file and reflash everything with the patched version.
It works without problems.
You must flash complete firmware stock
Then reflash complete firmware with mm agisk ap
Hi, this is My first post here, so be gentle.
My old Oneplus died and I bought a used Samsung Galaxy S9. I tested the phone with an original OS and it worked fine.
Yesterday I decided to root it (there are a few features that need root and I need those features almost daily). I searched for information about the procedure (this wasn't My first root) and found a few threads where this guide was suggested:
How to Root Samsung Galaxy S9 and Galaxy S9 Plus (Exynos)
Do you want to root your Galaxy S9/S9 Plus flagship? Well, you just landed in the right place for the job. This tutorial will help you install TWRP recovery and root Samsung Galaxy S9 and Galaxy S9…
www.thecustomdroid.com
Long story short: I followed those instructions and managed to root my S9. It booted up as it should and everything was working fine. I used Magisk V25.0 and root checker informed that the phone was rooted successfully.
Today I decided to debloat it and after that, I would start to use it as my main phone.
I ran across many threads that suggested using the "ADB + Fastboot" method for debloading the device. At this point, I started to feel uncomfortable because I had some issues with ADB back in the day when I was rooting my Oneplus. I decided to try it and guess what - it didn't work. I still don't know why, but ADB fastboot wasn't able to find my S9. I double-check that everything was as it should be, usb-debugging was ON and my PC did see my phone when connected to the PC via USB cable.
So I gave up on that and decided that maybe I'll just shut those unwanted apps down from the phone's settings (settings ---> apps etc).
At this point, I power off the phone. Just a basic thing to me when sleeping or something like that.
Now, the phone is in bootloop.
I can boot in the TRWP mode and flash magisk/wipe data etc. but nothing seems to help. It won't boot to OS. I've tried to root it again with the instructions above and everything went fine, but bootloop stays. I've wiped cache partition and performed a factory reset - did not help.
Can someone help me...? Is there a way to flash stock OS or somehow get the device work again? My experience with rooting is low, but I've successfully rooted five phones before this. I've experienced a few bootloops before, but those were my mistakes that were fixed with re-flashing magisk or something similar. Now I simply don't know what is the issue. =(
PS. This is a great forum and I've found tons of help from the XDA forum. Thank you to everyone, who has shared his/her information and helped with smartphones in the past! Great society.
Slerba said:
Hi, this is My first post here, so be gentle.
My old Oneplus died and I bought a used Samsung Galaxy S9. I tested the phone with an original OS and it worked fine.
Yesterday I decided to root it (there are a few features that need root and I need those features almost daily). I searched for information about the procedure (this wasn't My first root) and found a few threads where this guide was suggested:
How to Root Samsung Galaxy S9 and Galaxy S9 Plus (Exynos)
Do you want to root your Galaxy S9/S9 Plus flagship? Well, you just landed in the right place for the job. This tutorial will help you install TWRP recovery and root Samsung Galaxy S9 and Galaxy S9…
www.thecustomdroid.com
Long story short: I followed those instructions and managed to root my S9. It booted up as it should and everything was working fine. I used Magisk V25.0 and root checker informed that the phone was rooted successfully.
Today I decided to debloat it and after that, I would start to use it as my main phone.
I ran across many threads that suggested using the "ADB + Fastboot" method for debloading the device. At this point, I started to feel uncomfortable because I had some issues with ADB back in the day when I was rooting my Oneplus. I decided to try it and guess what - it didn't work. I still don't know why, but ADB fastboot wasn't able to find my S9. I double-check that everything was as it should be, usb-debugging was ON and my PC did see my phone when connected to the PC via USB cable.
So I gave up on that and decided that maybe I'll just shut those unwanted apps down from the phone's settings (settings ---> apps etc).
At this point, I power off the phone. Just a basic thing to me when sleeping or something like that.
Now, the phone is in bootloop.
I can boot in the TRWP mode and flash magisk/wipe data etc. but nothing seems to help. It won't boot to OS. I've tried to root it again with the instructions above and everything went fine, but bootloop stays. I've wiped cache partition and performed a factory reset - did not help.
Can someone help me...? Is there a way to flash stock OS or somehow get the device work again? My experience with rooting is low, but I've successfully rooted five phones before this. I've experienced a few bootloops before, but those were my mistakes that were fixed with re-flashing magisk or something similar. Now I simply don't know what is the issue. =(
PS. This is a great forum and I've found tons of help from the XDA forum. Thank you to everyone, who has shared his/her information and helped with smartphones in the past! Great society.
Click to expand...
Click to collapse
I manage to solve this all by my self.
I flashed to stock firmware using frija and odin. After flashing updated all the apps and rebooted couple of times (just to be sure that phone works). After that flashed TWRP with odin, rebooted to recovery and rooted with Magisk (followed step-by-step guide fron xda forum).
Now this works like a dream.