So, i recently have tried flashing Xposed on the MM 6.0.1 on G920P a.k.a Sprint S6
( ALL_SPT_G920PVPU3CPB6_G920PSPT3CPB6_CL7280193_QB8664149_REV02_user_low_ship.tar )
I have root and recovery, but Xposed doesnt seem to comply with me.
from multiple sources or builds.
And each Xposed file that i've tried so far that i've been flashing over and over again, rinse and repeat.
( Flash Stock through Odin, Go through setup process on the phone, Reboot Back to Download mode to Flash TWRP, Reboot, Back to TWRP to Flash Xposed, Once flashed i Restart it again, back to the s6 screen to becoming a black screen bootloop, thus having me restart the whole flashing process again )
from android file host website. And Default xda unofficialy build on this website.
xposed-v79-sdk23-arm64-by-romracer-20151218
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - ABDYASAR 7.8MB
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - SANOC 7.8mb
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 -WANAM 7.8MB
xposed-v80-sdk23-arm64-by-romracer-20160202
It would go from the Galaxy S6 Boot Menu startup to black screen and bootloop back to the original BootMenu or screen.
NO LED cycles nothing, but i can access Download Mode and Recovery But Updating Nor Uninstalling doesn't do anything to the rom, it just keeps boot looping unless i Flash the Stock back into place.
I'd like to have Xposed working i havent found a version for me that would work for this but i would really appreciate if everyone could help out.
IAmTechFreq said:
So, i recently have tried flashing Xposed on the MM 6.0.1 on G920P a.k.a Sprint S6
( ALL_SPT_G920PVPU3CPB6_G920PSPT3CPB6_CL7280193_QB8664149_REV02_user_low_ship.tar )
I have root and recovery, but Xposed doesnt seem to comply with me.
from multiple sources or builds.
And each Xposed file that i've tried so far that i've been flashing over and over again, rinse and repeat.
( Flash Stock through Odin, Go through setup process on the phone, Reboot Back to Download mode to Flash TWRP, Reboot, Back to TWRP to Flash Xposed, Once flashed i Restart it again, back to the s6 screen to becoming a black screen bootloop, thus having me restart the whole flashing process again )
from android file host website. And Default xda unofficialy build on this website.
xposed-v79-sdk23-arm64-by-romracer-20151218
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - ABDYASAR 7.8MB
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - SANOC 7.8mb
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 -WANAM 7.8MB
xposed-v80-sdk23-arm64-by-romracer-20160202
It would go from the Galaxy S6 Boot Menu startup to black screen and bootloop back to the original BootMenu or screen.
NO LED cycles nothing, but i can access Download Mode and Recovery But Updating Nor Uninstalling doesn't do anything to the rom, it just keeps boot looping unless i Flash the Stock back into place.
I'd like to have Xposed working i havent found a version for me that would work for this but i would really appreciate if everyone could help out.
Click to expand...
Click to collapse
Did it work. Ive only noticed a tad bit longer boot up the 1st time but all good.
i've tried most of them and i tried v80.0 or v80 and i got one part success half i didnt which was from it i got to the LTE spectrum screen and it just would go past that before it would just be the led flashing and bglank screen, i waited about and hour and still nothin changed from that screen.
Nevermind i made an update
This is what i've managed so far.... what am i missing here?
So here's what i"d take place in order to attempt a flash of Xposed Framework.
I start with Pre- Downloading the files for the MM 6.0.1 Stock Rom, it's in the forums Somewhere.
TWRP ( New_S6_Spr_TWRP_MM_Bootloader2 ) a.k.a 3.0.1
(This is a special version only for the Sprint SM-G920P and is meant to be flashed with Odin)
SuperSU 2.68 a.k.a ( BETA-SuperSU-v2.68-20160228150503 )
and obviously, Odin ( Odin3 v3.10 )
The steps that are taken place.
1st. I'd Boot my device into download/odin mode.
or
( while the device is powered off, i press and hold the home+power+volume down buttons.
and from there I'd be taken to a light blueish screen saying "Warning", and i follow through by pressing volume up)
2nd.
Once the device is in download/odin mode, and ready to go, i'd take my phone, plug it into my windows PC and open Odinv3 and from there
i'd select in odin, or i'd click the "AP" button and select the, tar file.
After that has been flashed thoroughly, I'd then proceed with the follow on screens, the 1st reboot and it updates or it says
Optimizing app 1 to 30.... the 2nd reboot where the hand free activation commences and
from that 3rd time it reboots and boots up again, i'd follow up with my login information.
3rd. once my device has been fully booted from the 2nd part, i'd then shut it down or restart it into "download mode again" and connect it to my pc again
and from there i'd load odin, and search or i'd find where I downloaded the special "TWRP .tar" or recovery file
and select the "Ap" option again and press start Afterwards.
After it flashes, right when its done i automatically hold the home+power+volume up buttons,
turn the device off and hold home+power+volume up and your should get some red text in the upper left hand corner with recovery not enforcing, that's okay dont be worried,
and from there it should boot into and be brought into TWRP...finally lol.
Now that's where you can flash SuperSU
4th. I'd leave my phone connected to my pc until, it's fully booting into twrp or i'd just connect it once im in the recovery.
I let my pc detect my phone and i'd copy both of these files.
SuperSU 2.68
and
Xposed
4th. After its copied, i'd go back into my phone, i tap install, and i select supersu and let it run, afterwards, i press reboot.
And let it sit for about another 2 minutes to do its own thing. Afterwards. once the phone is fully booted up.
I'd then go back into recovery, and flash Xposed and i'd wait about another 2-3 minutes for it to cycle
from the LTE Spectrum Screen to the, torquise colored screen where it's finally optimizing apps from 0 to 331.
5th. Once done, i'd finally have my advantage to install what i'd like which i'm doing as of right now still testing it out.
P.S if you do what i do for the SnapPrefs Module then i'd take in high note that before you flash the Xposed to download latest Snapchat 9.26
log in, once logged in then proceed with the rest and download XInstaller to downgrade from 9.26 to 9.17.1.0 to take full advantage of Snapprefs coolness.
upon note so far, after installing the modules, i rebooted my phone and it boots until it hits the LTE Spectrum screen and it has a light blueish pusling cycle and im stuck here.
maybe i can try another version. to be continued...
If you need any help feel free, i will try as best as i can, as i am a n00b but i have plenty of free time and have some decent knowledge about this.
After , i went back into recovery, i went to uninstall xposed thru the other flash file and its says optimizing 0 to 36 items and it booted so far, mayber after i flash the cache again and reinstall i should be fine but until further notice...tbc
Alright after a good amount of time i;ve finally concluded that the versions i;ve tired from xposed were the ones from the OFFICIAL thread and id always bootloop with that puling blue led and black screen, BUT with Wanams Xposed Version 80, and 79 they worked EXCEPT i can only get to the LTE SPecturm white boot screen and it does nothing from there BUT when i flash 80.1 it completely pulls through with the boot and completes but i had forgotten to mention that for some people on aanother thread that Xinstaller may leave you with bootloops and as it did for me thats exactly what happened. But i m still confused as to why the officials dont work by wanams does even after wiping cache,and dalvik cache multiple times and uninstall and reinstalling xposed.
Does yours still bootloop or did it finally pull through?
I have a HTC One m8(Marshmallow 6.0) from Verizon. It's unlocked and I'm using it on the cricket network. I got S-off(sunshine) and put the latest TWRP on it. However ever root method(kingroot, kingoroot, etc) I try it's not working. Don't want to pay One Click Root $30 to root it. Any suggestions? Thanks
Download SuperSU from the app store and try the built in methods.
If neither work, you need the root installation zip and to flash it through TWRP>Install
I just rooted on a Verizon HTC One M8 with Marshmallow and was navigating to this forum to find a good rom and radio.
I got it done by downloading the supersu zip file and used TWRP to flash it. I wasn't rooted so I had to do it this way ... none of the apps will work if you aren't already rooted. Make sure you have downloaded the supersu .zip file and not the .adk file, otherwise it won't be available in supersu to flash.
I did that and now it's stuck on the verizon red screen. I tried factory resetting(fastboot). And that didn't work. The only way i seem to be able to get the phone to turn on is to let it die and charging it to like 2% and go into fastboot mode and if i reboot it.... it goes to the verizon red screen and just stays there.
Msmala85 said:
I did that and now it's stuck on the verizon red screen. I tried factory resetting(fastboot). And that didn't work. The only way i seem to be able to get the phone to turn on is to let it die and charging it to like 2% and go into fastboot mode and if i reboot it.... it goes to the verizon red screen and just stays there.
Click to expand...
Click to collapse
Try flashing current stable SuperSU 2.78 in zip version (flash with TWRP) from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Also, you need to be on a relatively recent TWRP version. Current is 3.0.2
https://dl.twrp.me/m8/
Also, no need to let the battery die, to restart to bootloader. Force a reboot by holding Power+Vol up for a minute or so. Once the screen goes dark to reboot, slide your finger from vol up, to vol down, to boot into bootloader.
Also, you should always do a TWRP backup before trying to root, so you can revert if something like this goes wrong.
HI i flashed this aosp rom
https://forum.xda-developers.com/lg-g3/orig-development/rom-pixel-g3-aosp-t3571499
i flashed the rom, the gapps file and mr bump, and figured i would get root later.
After setting up my D855 i decided to get root, so i pressed to reboot to recovery and there was none!!! the phone kept "recovery bootloopin" and showing the tre triangle with android logo for a split second, then the screen turned black-off then egain and again, untill i pulled the battery and it booted normally.
i tried kingroot and similar options but nothing worked. I tried to adb flash recovery but it was my first time with adb and could make it work. PLease HELP!!!
bamiasHELLAS said:
HI i flashed this aosp rom
https://forum.xda-developers.com/lg-g3/orig-development/rom-pixel-g3-aosp-t3571499
i flashed the rom, the gapps file and mr bump, and figured i would get root later.
After setting up my D855 i decided to get root, so i pressed to reboot to recovery and there was none!!! the phone kept "recovery bootloopin" and showing the tre triangle with android logo for a split second, then the screen turned black-off then egain and again, untill i pulled the battery and it booted normally.
i tried kingroot and similar options but nothing worked. I tried to adb flash recovery but it was my first time with adb and could make it work. PLease HELP!!!
Click to expand...
Click to collapse
I would just reflash the kdz and start again, it would be way easier that way if you have the time.
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.