I'll try to be as short as I can:
I rooted my phone (with temp TWRP recovery), freezed some bloatware, installed link2sd and used it for a while, then I decided to update it, so I removed root, unfreezed bloatware and uninstalled link2sd: OTA update ended with an error, and it never showed again, so I downloaded the latest firmware from Asus and manually applied the update.
Everything seems to work fine, except one (BIG) thing: I totally loose the ability to access recovery via VOL UP + Power: everytime I try to do it, it stucks on bootlogo until I turn it off.
The weird thing is that I can flawlessly go into recovery via "adb reboot bootloader"!!
What the hell is happened? Is there a solution? I don't want to be stuck in a bootloop one day without being able to enter recovery...
SOLVED!
Hi, I'd like to report that after last update, manually applied via recovery mode (loading the whole Asus firmware from the sd card), everything's fine, although I don't know why.
Maybe because I did a factory reset (thing that didn't worked in the past) and not rooted the phone again, but who knows.
PROBLEM SOLVED.
So at first I used Kingroot to rood my device, and it failed, but then i just realized few days later that Kingroot was installed and used root checker to check and said that it does have root access. After that decided to change the Kingroot to SuperSU by following this video https://www.youtube.com/watch?v=WevWdErXWy4 (It's the SuperSU Me app). I then updated SuperSU binaries and restarted the phone, and now its stuck at the loading screen. I tried hard resetting my phone but it would only show the screen with the android logo and shapes in its belly for about 2 second and go back to the stuck logo screen. Now I'm wondering if there's any fix for it, and if there's no fix then I'm going to try resetting it through this http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/ guide and I was wondering if I should download and use the bell stock factory firmware (I have a virgin mobile version).
Edit: fixed to be more clear.
I Nid 2P said:
So at first I used Kingroot to rood my device, and it failed, but then i just realized few days later that Kingroot was installed and used root checker to check and said that it does have root access. After that decided to change the Kingroot to SuperSU by following this video https://www.youtube.com/watch?v=WevWdErXWy4 (It's the SuperSU Me app). I then updated SuperSU binaries and restarted the phone, and now its stuck at the loading screen. I tried hard resetting my phone but it would only show the screen with the android logo and shapes in its belly for about 2 second and go back to the stuck logo screen. Now I'm wondering if there's any fix for it, and if there's no fix then I'm going to try resetting it through this http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/ guide and I was wondering if I should download and use the bell stock factory firmware (I have a virgin mobile version).
Edit: fixed to be more clear.
Click to expand...
Click to collapse
if you can get into recovery you can probably do it without unbricking. to you have stock recovery or twrp or what? If you have stock recovery then boot into recovery and just run it and itll hard reset your phone, if you have twrp or something just download the flashable rom of your choice (there are stock modded roms too if you like stock) put it on an sdcard and wipe and install that rom.
if you don't know how to get into recovery then make sure your phone is off (if ur not sure do a battery pull and put it back in). hold volume down and power button until the screen comes on. when it comes on let go of vol down and power and then push vol and power again and hold again until you see the writing)
btw if you do a stock recovery hard wipe then you will lose root.
I also faced this problem...
Sent from my SM-E500H using Tapatalk
Problem solved. I just flashed the stock firmware onto my phone and it fixed the stuck on logo problem.
So I just did a clean install of my own Lineage 14.1 build and Magisk 15.3 (and the latest beta) do not work. I flash it, it's successful, I reboot and there is no Magisk Manager, and if I install it myself, when I open it, it just hangs on the Magisk icon forever. I uninstalled Magisk 15 and installed a copy of 14.2 I had and it works fine, so I tried updating through the app, which actually worked briefly and showed 15.3 being installed, but all of the options for MagiskSU and stuff were gone, and after another reboot Magisk Manager just hangs again.
I can't seem to find anyone else with this issue and I find it hard to believe that I'm the only one? Does anyone know what's going on here?
I've had issues with Magisk hanging at the boot screen randomly from updates and modules. After trial and error, I have found when I update or install/uninstall a module, I wait around 10 minutes when at the boot screen. If it doesn't get past the boot screen after this time, I hold the power button till it reboots and only then will it boot into Android.
So my Oneplus 3 was getting old and slow, so I thought "Why not root it". I found THIS guide on the forum made by someone who seems to know what he's doing. I used the supplied SuperSU file, but a newer TWRP recovery(this one). I followed the tutorial and in the end my phone booted right up. Then I noticed something strange; there was no SuperSU installed. I tried downloading it from the play store, but it said I had no root. I then booted it back into the bootloader, and tried getting into the recovery. Instead of being greeted by TWRP I got the stock recovery. I chose english and then exit, power off. My phone was plugged into the computer, so the charging animation booted up. I unplugged the phone and boom. Nothing happens. It doesn't respond to anything. Everything is black. Is there any way to save the phone or is it bricked? Any sort of help would be greatly appreciated.
*Edit: I waited about an hour and tried powering the phone on again. Like a miracle it booted right up, TWRP still missing. I then reinstalled TWRP and SuperSU, but root still doesn't work. Any ideas? *
You use the arm or arm64 version of supersu
Pangi123 said:
So my Oneplus 3 was getting old and slow, so I thought "Why not root it". I found THIS guide on the forum made by someone who seems to know what he's doing. I used the supplied SuperSU file, but a newer TWRP recovery(this one). I followed the tutorial and in the end my phone booted right up. Then I noticed something strange; there was no SuperSU installed. I tried downloading it from the play store, but it said I had no root. I then booted it back into the bootloader, and tried getting into the recovery. Instead of being greeted by TWRP I got the stock recovery. I chose english and then exit, power off. My phone was plugged into the computer, so the charging animation booted up. I unplugged the phone and boom. Nothing happens. It doesn't respond to anything. Everything is black. Is there any way to save the phone or is it bricked? Any sort of help would be greatly appreciated.
*Edit: I waited about an hour and tried powering the phone on again. Like a miracle it booted right up, TWRP still missing. I then reinstalled TWRP and SuperSU, but root still doesn't work. Any ideas? *
Click to expand...
Click to collapse
If you are on Oreo, SuperSU may not work. Use Magisk.
tnsmani said:
If you are on Oreo, SuperSU may not work. Use Magisk.
Click to expand...
Click to collapse
Thank you! Magisk works perfectly!
Magisk v20 worked stable on Galaxy A50 but If you want to use Magisk v19.3 you can patch and downgrade it using Magisk Manager - Custom Channel Update https://www.youtube.com/watch?v=vcF0pfdQyW8
-----------------------------------------------------------
Complete Guide for Rooting Samsung Galaxy A50 using Magisk v20 / v19.3 ( tested on SM-A505F ):
* Download the firmware Galaxy A50 (SM-A505F).
* Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5. Copy AP tar file and MagiskManager apk to your phone.
* Install Magisk Manager on your phone.
* In Magisk Manager: Install → Install → Select and Patch a File
* Select the AP tar file. Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar. Copy magisk_patched.tar the tar file to your PC
* Enter Download Mode : Turn Power Off. Press and hold Volume Up key + Power Key,* When Samsung Logo appears release Power Key only, keep pressing Volume Up key until Android Recovery Mode Appears.
* Select Wipe data / Factory reset, Select Reboot to bootloader.* Connect your Samsung Galaxy to PC using USB Cable.
*Flash magisk_patched.tar as AP in ODIN, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do. Checked "Auto Reboot" and "F. Reset Time" only in options.
* Magisk is now successfully flashed to your device and Rebooting!
* After the device is booted up, do the usual initial setup. It need more time and patient.
* Connect the phone to Internet copy Magisk Manager apk to your phone and Install it
* Open Magisk Manager. It will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
* Done! You can use Root Checker to check it, Enjoy!
New video Install and Root with Magisk v20 / v19.3 https://youtu.be/ILvgki0pFHE
To prevent loosing magisk root after reboot. Reboot the phone from Magisk or Fully Power Off, you can watch this video https://youtu.be/Ea8s16usBOM
Rooting with TWRP+Magisk ( ASH2 baseband version only ), you can watch this video https://youtu.be/kYwJAKBzX1E
well donw
thanks i rooted latest stock F2 firmware
it works
FYI: To prevent loosing magisk root after reboot. Reboot the phone from Magisk or Fully Power Off, you can watch this video https://youtu.be/Ea8s16usBOM
Oh I wish I could get magisk on my phone. Unfortunatly I can't find the firmware, for my phone, anywhere on the internet (A505W). Will do directly once I can!
I had it finally rooted like this since yesterday thanks to this process. Got it in root mode running today all day. THE PROBLEM IS: It doesnt stay on anymore after i reboot once again. It starts, I can put in the pincode of sim, but after 10 seconds it reboots. Without sim also reboots after 10 secs. This goes on and on and on. I read on web delete cache can help. I can sometimes boot normally once thanks to that. Root mode is hopeless, then it always reboots. I used the right stock rom. Didnt make changes of system apps etc. I havent tried factory reset yet, but i'm tired of reinstalling all apps and settings again and i asume it just will happen again. Who knows what is causing this?
Edit: It kept rebooting in any way. Used the factory reset at the end. Booted it up once without root. Set up Wifi and google account. Tried to reboot in root mode and voila: stuck in bootscreen with red letterd 'custom binnary not allowed'. Can't startup, can't go to recovery, can't flash the magisk patched zip (same red letters). Flashed stock rom and wait for the possibility to flash magisk patched again.
Edit 2: Booting in the stock rom probably registers something to let u flash something else again. Magisk patched flashed again. Booted normally, magisk up to date and working. Just gonna install fake gps, smali and magisk hide app again. Not in the mood to test reboot then again. It probably fails again. But i can spoof again for now.
Edit 3: After trying some more things, I think the conclusion is: U can only use Root mode once with this, until it reboots.
I wonder if I'm the only one with this.
jarno389 said:
I had it finally rooted like this since yesterday thanks to this process. Got it in root mode running today all day. THE PROBLEM IS: It doesnt stay on anymore after i reboot once again. It starts, I can put in the pincode of sim, but after 10 seconds it reboots. Without sim also reboots after 10 secs. This goes on and on and on. I read on web delete cache can help. I can sometimes boot normally once thanks to that. Root mode is hopeless, then it always reboots. I used the right stock rom. Didnt make changes of system apps etc. I havent tried factory reset yet, but i'm tired of reinstalling all apps and settings again and i asume it just will happen again. Who knows what is causing this?
Click to expand...
Click to collapse
Have you attempted to change your IMEI recently?
Ertogrul said:
Have you attempted to change your IMEI recently?
Click to expand...
Click to collapse
Nope, the only thing i want root for is spoofing with gps joystick.
jarno389 said:
I had it finally rooted like this since yesterday thanks to this process. Got it in root mode running today all day. THE PROBLEM IS: It doesnt stay on anymore after i reboot once again. It starts, I can put in the pincode of sim, but after 10 seconds it reboots. Without sim also reboots after 10 secs. This goes on and on and on. I read on web delete cache can help. I can sometimes boot normally once thanks to that. Root mode is hopeless, then it always reboots. I used the right stock rom. Didnt make changes of system apps etc. I havent tried factory reset yet, but i'm tired of reinstalling all apps and settings again and i asume it just will happen again. Who knows what is causing this?
Click to expand...
Click to collapse
I have tried everything but failed, I have tested on some device but it's only happen to A50
will this work with a505gn?
redymedan said:
I have tried everything but failed, I have tested on some device but it's only happen to A50
Click to expand...
Click to collapse
That's seem pretty unstable as it is right now. Was tempting to try this on my A505W, but I'm reluctant now.
Now I'm just wondering why the heck my root is still active with 2 random reboots. Last 20 runs the random reboots made it lose root and got stuck with constant rebooting.
When i started the recovery of samsung backup, it rebooted again (3rd time) (again root is somehow still active). Screw it, gonna forget about the backup and keep it like this. I think the random rebooting seems to happen often when installing much apps.
jarno389 said:
I had it finally rooted like this since yesterday thanks to this process. Got it in root mode running today all day. THE PROBLEM IS: It doesnt stay on anymore after i reboot once again. It starts, I can put in the pincode of sim, but after 10 seconds it reboots. Without sim also reboots after 10 secs. This goes on and on and on. I read on web delete cache can help. I can sometimes boot normally once thanks to that. Root mode is hopeless, then it always reboots. I used the right stock rom. Didnt make changes of system apps etc. I havent tried factory reset yet, but i'm tired of reinstalling all apps and settings again and i asume it just will happen again. Who knows what is causing this?
Edit: It kept rebooting in any way. Used the factory reset at the end. Booted it up once without root. Set up Wifi and google account. Tried to reboot in root mode and voila: stuck in bootscreen with red letterd 'custom binnary not allowed'. Can't startup, can't go to recovery, can't flash the magisk patched zip (same red letters). Flashed stock rom and wait for the possibility to flash magisk patched again.
Edit 2: Booting in the stock rom probably registers something to let u flash something else again. Magisk patched flashed again. Booted normally, magisk up to date and working. Just gonna install fake gps, smali and magisk hide app again. Not in the mood to test reboot then again. It probably fails again. But i can spoof again for now.
Edit 3: After trying some more things, I think the conclusion is: U can only use Root mode once with this, until it reboots.
I wonder if I'm the only one with this.
Click to expand...
Click to collapse
Read my First post, I have updated it for fixing lost magisk root after reboot
I cannot pass through the flashing of image modified by Magisk. During the flash some red text appears on top saying that custom binary (VBMETA) blocked ... then there is a front camera, so I can not read it all and then "Lock" word. The flashing stops and odin waits forever. The only thing I can do is to interrupt and then reflash the whole firmware with odin since it ends up at the "error has occured while updating the device software".
My device is SM-A505FN, firmware XEZ-A505FNXXU1ASE3, OEM unlocked, tried Magisk Manager 7.3.2.
(w) said:
I cannot pass through the flashing of image modified by Magisk. During the flash some red text appears on top saying that custom binary (VBMETA) blocked ... then there is a front camera, so I can not read it all and then "Lock" word. The flashing stops and odin waits forever. The only thing I can do is to interrupt and then reflash the whole firmware with odin since it ends up at the "error has occured while updating the device software".
My device is SM-A505FN, firmware XEZ-A505FNXXU1ASE3, OEM unlocked, tried Magisk Manager 7.3.2.
Click to expand...
Click to collapse
Flash whole stock rom. Boot and login. Connect to wifi. Wait few minutes. Flash magisk rom again.
(w) said:
I cannot pass through the flashing of image modified by Magisk. During the flash some red text appears on top saying that custom binary (VBMETA) blocked ... then there is a front camera, so I can not read it all and then "Lock" word. The flashing stops and odin waits forever. The only thing I can do is to interrupt and then reflash the whole firmware with odin since it ends up at the "error has occured while updating the device software".
My device is SM-A505FN, firmware XEZ-A505FNXXU1ASE3, OEM unlocked, tried Magisk Manager 7.3.2.
Click to expand...
Click to collapse
You need to unlock the bootloader from Download Mode, Watch this video https://youtu.be/o1xZ-E3jhUg
redymedan said:
You need to unlock the bootloader from Download Mode, Watch this video https://youtu.be/o1xZ-E3jhUg
Click to expand...
Click to collapse
Oh, thanks, I was not able to find this trick, there are lot of infos everywhere and it's hard to find out. Thanks. So both volumes holding and plugin cable.
Thanks again
redymedan said:
Solved: Lost Magisk Root After Reboot
To prevent loosing magisk root after reboot. Reboot the phone from Magisk or Fully Power Off, you can watch this video https://youtu.be/Ea8s16usBOM
Click to expand...
Click to collapse
So what would happen if, by a mistake of mine, my battery dies. Do I have to reflash magisk again and factory wipe everytime? Or is the problem occur only with the "reboot" function of android since it work while fully powering it off.
AliasGprime said:
So what would happen if, by a mistake of mine, my battery dies. Do I have to reflash magisk again and factory wipe everytime? Or is the problem occur only with the "reboot" function of android since it work while fully powering it off.
Click to expand...
Click to collapse
Mine is still rooted since friday. It sometimes reboots randomly. Then i have to reset with volume down and power button or else is keeps restarting. Root is still active then. Battery also died yesterday. Could start up with power key only and root is still active. I still don't understand why but im good.
(I used the root mode function with volume up and power key till logo popsup only once after the flashing of magisk patcher to let it install magisk manager. )
I'm still wondering if I'm the only one with random reboots or constant reboots
Worked great for my SM-A505G.
In summary, after installing Magisk:
(Powering up normally) → (System with NO Magisk)
(Volume UP + Power) → (Splash screen) → (Release all buttons) → (System with Magisk)
(Volume UP + Power) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
Hi there,
Yesterday I rooted my A505W (Canadian Variant) and got random reboots like almost every one else. It got so bad, I decided to go back to un rooted stock. Before flashing stock firmware I took a look in build.prop file, hoping I might find something that does not belong there after rooting. And I think I found it. At the very end there is line like this:
ro.expect.recovery_id=0xf1dee4214a6ffec6b8
2cec9a13222d4f34c7fd10000000000000000
000000000
Comment it out to lool like this:
#ro.expect.recovery_id=0xf1dee4214a6ffec6b8
#2cec9a13222d4f34c7fd10000000000000000
#000000000
Wanted to delete it, but it was enough to comment it out whit #
Since last night I don’t have any reboots, it looks like commenting it out did the trick. So try it for yourself an see if it helps.
One more thing, if you need to reboot your device do not do it from Magisk, because it will keep rebooting, just power down and boot with the key combination. As I said since last night I have no random reboots.