Is the method for installing xposed in the general section still valid?
Il installed xposed about 6 times in my life in my g4.
The first 4 went smooth.
The last 2 were done in the past few days, and each resulted in a bootloop.
I just got my phone working with a non rooted kdz, I'm gonna flash a rooted 13b image later and hopefully would like to install xposed,
Anybody know why xposed install made my phone crash and bootloop the last 2 times?
Im gona istall xposed on 5.1 with the rooted img provide these by @Prime
I read throughout the page of installing xposed and some mentioned using an older version of flash fire. I thought that was the problem. But I tried an older flashfire yesterday (and did not check auto mount)
But still resulted in a bootloop.
So basicly, my question(s) is does the "how to install xposed" still work?
What's the correct method?
Am I missing something?
Is there a newer way?
I triple checked that I was using the correct files when flashing btw.
See this thread:
http://forum.xda-developers.com/verizon-g4/general/guide-install-xposed-verizon-g4-t3182267
Is the bootloop you are experiencing the one with the dead bugdroid. If so how did you recover from the loop.
Hello,
I'm having big issues while trying to install paranoid on my op3.
I downloaded the newest version (6.0.3), wiped everything (even my local storage ), installation worked without errors, but I'm not able to boot. After the oneplus logo there is only a black screen without any boot animation or something like that.
I tried installing with and without gapps (opengapps nano), after failing several times I also tried the older version of paranoid (6.0.2). Also no success.
After that I installed another OS (LineageOs) which is running fine on my phone...
Does anyone here has got an idea for me or is there someone having the same issues?
Thanks!
JanK411 said:
Hello,
I'm having big issues while trying to install paranoid on my op3.
I downloaded the newest version (6.0.3), wiped everything (even my local storage ), installation worked without errors, but I'm not able to boot. After the oneplus logo there is only a black screen without any boot animation or something like that.
I tried installing with and without gapps (opengapps nano), after failing several times I also tried the older version of paranoid (6.0.2). Also no success.
After that I installed another OS (LineageOs) which is running fine on my phone...
Does anyone here has got an idea for me or is there someone having the same issues?
Thanks!
Click to expand...
Click to collapse
Same issue here. Asked on Reddit too, no replies... I really want to try this ROM!
Got it look at this post I made: https://forum.xda-developers.com/on...g-paranoid-t3549173/post70839964#post70839964
Pachriksu said:
Got it look at this post I made: https://forum.xda-developers.com/on...g-paranoid-t3549173/post70839964#post70839964
Click to expand...
Click to collapse
Oh, just read it, you solved my problem! Right now I'm configuring my paranoid )
Thank you!!
I've rooted my sammy (on Marshmallow) and tried to get Xposed working by following this post but to no avail.
I got as far as using TWRP to flash xposed*.zip (SDK23 & Arm version) as a precursor to installing Xposed but could not boot successfully after flashing.
So my question is, how do you get Xposed working on this Samsung?
I followed this posting and it seemed to all go well. When I open up the Xposed installer there is a green tick, status is version 88 is active but the menus which present okay but none of the options seem to do anything and I still can't get Amplify to work! I have rebooted several times.
Well there goes 4 hours of my life I'm not going to get back
First time messing with this phone
followed the instructions for unlocking bootloader, installing TWRP, and rooting here: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
Successfully unlocked bootloader, flashed TWRP, but now hung up on SuperSU.
Flashed SuperSU VV2.82 zip from http://www.supersu.com/download in TWRP
Wiped dalvik and cache
reboot
Now it's been about 10 minutes. Blank screen and blue LED.
Hold power until it reboots again, Android sometimes has issues with new boot.imgs at first
l3ones said:
Hold power until it reboots again, Android sometimes has issues with new boot.imgs at first
Click to expand...
Click to collapse
I did, three times.
I ended up flashing the latest complete OTA to get it back to being able to boot.
Are you on Oreo? I don't know if SuperSU is compatible with it. I switched to Magisk a few weeks ago.
Macusercom said:
Are you on Oreo? I don't know if SuperSU is compatible with it. I switched to Magisk a few weeks ago.
Click to expand...
Click to collapse
was on the latest stock OTA, which was 8.0.0
Flashed Mgisk after flashing the latest OTA, and everything is working swimmingly
Exact Same thing happened to me last night.
And I lost my internal sdcard.
Eventually flashed stock recovery didn't do anything different so flash twrp again and got sdcard back.
It was a strange one.
Now I'm waiting for an update or the right file for root.
Maybe this has something to do with Keymaster?
So, I've been trying to get my OP5t working for a solid six hours straight, and I'm just about to loose my mind.
I'm sorry if this isn't the right place to post this. I've always just sorta lurked about in here.
Here's the deal for my OP5t.
Now I'm stuck in a situation where I can get my phone to boot on all of the OOS versions I've mentioned, but always without root. And If I do manage to get it booting, I end up loosing TWRP and having to reflash it through fastboot.
Since I've always just relied on Titanium backup (yes I know, how silly) I've never had any trouble restoring my backups, but since I've now lost root and being unable to obtain it again, I'm locked out of all my sweet app data. It's all a bit messy now, and I think I'm begging to repeat previous steps and combinations, but here's a list of what I've tried. I really hope some white knight comes to the rescue.
It all happened when I tried doing a clean flash wiping caches, data and system of OOS 5.0.3 (coming from the latest official OOS Nougat build). It all started when I tried to flash the magisk 15.3 after this boot, which resulted in ERROR 1.
- I've tried installing both the old version the previous nougat build and the two most recent stable oreo ones. Wiping thoroughly inbetween even, since at this point I have nothing left to loose.
- Whenever I try to flash magisk 15,1 /3 or 4 I get error 1. Whenever I try to flash supersu (s.82 included the modded SR5 version) I Just don't get root or end up in an endless +1 screen (before the spinner) for 12+ minutes.
- I've tried flashing the stock boot.img
- I've tried all of the above in combination with bluspark recovery 8.61 and 69 + the r100 kernel
- I've tried using codeworks cheesburger and dumpling recoveries
What am I missing here? I assume my phone is encrypted since it asks for a code to open TWRP.
I've never had any issues so grave that I couldn't just search my way through it, but this time I'm at my wits end, and just about ready to settle(tm) for no root.
I've never tried exporting a log, but I sense that I do that from TWRP and then grab it via a file manager from some folder?
Use codeworkx dumpling TWRP, dirty flash your ROM, boot it once, then reboot to recovery and flash Magisk 15.3. Should be all you need.
For Nougat, I think it's better to flash Magisk 14, on some ROMs.
New apps
Great information provided by many users. I have just joined this group and read many experts advice. Thanks
Latest SuperSU (beta 2.85 i believe) don't work on OP5T Oreo update (stable or Open Beta). Don't know why, but I had to use Magisk. ANd I must say, I'm pretty happy with it, too!
Elfomze said:
So, I've been trying to get my OP5t working for a solid six hours straight, and I'm just about to loose my mind.
I'm sorry if this isn't the right place to post this. I've always just sorta lurked about in here.
Here's the deal for my OP5t.
Now I'm stuck in a situation where I can get my phone to boot on all of the OOS versions I've mentioned, but always without root. And If I do manage to get it booting, I end up loosing TWRP and having to reflash it through fastboot.
Since I've always just relied on Titanium backup (yes I know, how silly) I've never had any trouble restoring my backups, but since I've now lost root and being unable to obtain it again, I'm locked out of all my sweet app data. It's all a bit messy now, and I think I'm begging to repeat previous steps and combinations, but here's a list of what I've tried. I really hope some white knight comes to the rescue.
It all happened when I tried doing a clean flash wiping caches, data and system of OOS 5.0.3 (coming from the latest official OOS Nougat build). It all started when I tried to flash the magisk 15.3 after this boot, which resulted in ERROR 1.
- I've tried installing both the old version the previous nougat build and the two most recent stable oreo ones. Wiping thoroughly inbetween even, since at this point I have nothing left to loose.
- Whenever I try to flash magisk 15,1 /3 or 4 I get error 1. Whenever I try to flash supersu (s.82 included the modded SR5 version) I Just don't get root or end up in an endless +1 screen (before the spinner) for 12+ minutes.
- I've tried flashing the stock boot.img
- I've tried all of the above in combination with bluspark recovery 8.61 and 69 + the r100 kernel
- I've tried using codeworks cheesburger and dumpling recoveries
What am I missing here? I assume my phone is encrypted since it asks for a code to open TWRP.
I've never had any issues so grave that I couldn't just search my way through it, but this time I'm at my wits end, and just about ready to settle(tm) for no root.
I've never tried exporting a log, but I sense that I do that from TWRP and then grab it via a file manager from some folder?
Click to expand...
Click to collapse
Same kind of problem here. After clean flashing Oreo can't root anymore. Flashing Magisk ends up in Bootloop. Tried various combinations of TWRPs and Magisk versions, no use. :/
Kunjuuuz said:
Same kind of problem here. After clean flashing Oreo can't root anymore. Flashing Magisk ends up in Bootloop. Tried various combinations of TWRPs and Magisk versions, no use. :/
Click to expand...
Click to collapse
Okay so I managed to figure it out. The problem seemed to be that where one TWRP version could flash magisk, another wouldn't be able to decrypt the phone properly, which I think is what caused the bootloops/non sticky root for me (though I'm by no means sure of this).
I managed to get it worked out by fiddling around a bit more with the different versions and using the a Remix ROM to remove the pin (which I probably should've done initially). I also noticed that I didn't originally pay attention to the fact that codeworks' (non universal) recoveries are aimed at 8.0 and 8.1 respectively, which might have complicated things a bit more for me.
Sorry for spamming up the thread. I hope you figure things out though
The latest SuperSu does not work with 8.1 for us and some other (or all other) 8.1 phones.
And... SuperSu is no longer in development.
Rumor has it a slightly older SuperSu version works in 8.1 but I never got around to trying it and forget the version # now.
And Lineage has not released a SuperSu/superuser for 8.1 yet.
It bums me out because I want that Magisk alternative.
Not a fan of Magisk yet.
Elfomze said:
Okay so I managed to figure it out. The problem seemed to be that where one TWRP version could flash magisk, another wouldn't be able to decrypt the phone properly, which I think is what caused the bootloops/non sticky root for me (though I'm by no means sure of this).
I managed to get it worked out by fiddling around a bit more with the different versions and using the a Remix ROM to remove the pin (which I probably should've done initially). I also noticed that I didn't originally pay attention to the fact that codeworks' (non universal) recoveries are aimed at 8.0 and 8.1 respectively, which might have complicated things a bit more for me.
Sorry for spamming up the thread. I hope you figure things out though
Click to expand...
Click to collapse
Locking the bootloader, wiping, and unlocking the bootloader again fixed the issue for me.
I'm having issues with certain "secure" apps not working on Pie with Magisk after updating from Oreo (Google Pay in stores, Zelle, Chase, etc.) even though safetynet and everything else checks out perfectly. I'm thinking about doing a clean install but I'm not sure what's causing the issue and I'd like to avoid it again if at all possible... I followed a guide on XDA and everything works right except for this issues and the only things different from when I was on Oreo are:
* Installed TWRP instead of just fastbooting into it for flashing
* Installed Sultan's kernel, per the guide (not 100% sure how to get back to stock on that either, unless it'll happen when flashing the update from Google)
I think everything else was the same, other than updating Magisk from 16.1 to 18.0 (and later downgrading to 17.2 after reading that 18 had some issues with hiding). Anyone have a similar issue and found a solution or have advice on troubleshooting? I'm planning on trying a fresh install and only fastbooting into TWRP to install Magisk instead of installing it, and staying on the stock kernel to see if that helps but trying to avoid bricking my phone too.
Thanks
Join the crowd... It's been a few weeks since this started. There are a few work around methods but they don't seem to be consistent or permanent. Most are just waiting until magisk gets updated to fix whatever Google did to detect modified systems.