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
Related
Really seeking input those who are rooted/have been rooted for awhile. I know x64 support for Xposed is a recent thing, but I've tried multiple builds of it for 5.X.X and even with @rovo89's latest build (v75/sdk21/arm64 from here: http://forum.xda-developers.com/showthread.php?t=3034811 I have no luck. After flashing Xposed, the phones boots up (usually very slowly, it'll sometimes even play the boot animation frame by frame) then it freezes at the end of the boot animation.
Tried reboots, wiping cache, etc. Luckily the uninstaller from the thread fixes everything. I assumed it would work due to it working on other M9 models but maybe I'm doing something wrong? Has anybody else managed to get Xposed working?
All help appreciated!
Same problem.
V78 did not work too.
I really need Xposed.
Tapatalk を使用して私の SO-01G から送信
I´ve read that its on alpha stage but hope soon goes beta at least.
Sure then will work on our great B3!
V79 is coming.
It worked perfect.
Best Xposed
v79 is the first version that will work, personally I installed v81 of sdk21 and it works very well. Just download the zip and flash it in twrp.
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.
Hey guys,
I have a HTC M9
I am trying to install the Xposed Framework on my Rooted M9 with stock ROM but inside the Xposed app it tells me that it's not installed.
I have TWRP installed.
I rooted my phone with SuperSU v2.65 (After trying a couple of versions that would result in boot loop)
I checked my phones CPU (ARM64) and downloaded "xposed-v86-sdk23-arm64" as well as "XposedInstaller_3.0_alpha4.apk".
I booted into TWRP and Installed the xposed-v86-sdk23-arm64 Framework, it gets to Placing Files and then my phone reboots (I don't know if this is normal or not).
My phone reboots and I open XposedInstaller, under Framework it says "The latest version of Xposed is currently not active, Did you install the Framework and reboot?"
Inside the Framework menu it says "The Xposed Framework is not installed. Please download the latest ZIP file from XDA and flash it manually via reocvery."
The options Install/Update, Uninstall, Recovery (Flash zip automatically) are grayed out.
When I press the Soft Reboot button the phone does restart but no change.
When I try to press the Reboot option I get this error:
Code:
sush: <stdin>[8]: /data/user/0/de.robv.android.xposed.installer/cache/busybox-xposed: not found
Reboot failed please use the device's normal reboot function.
I have restarted the phone normally a couple of times with no change.
I'm new to rooting but I don't find this stuff too difficult to understand, I had a lot of problems trying to get my phone to root in the beginning, I had to try a few SuperSU versions before I could get my phone past boot looping. When I run Root Check it tells me that my phone is Rooted.
I'm not sure what other information I can post to help yous help me but if there's anything you need to know just ask and I'll reply asap.
Cheers guys
I basically want access to Xposed so I can use the FakeGPS and the Hide Mock Location modules.
EDIT (29/07 2:00PM)
I re-downloaded xposed-v86-sdk23-arm64 and tried flashing it again, I read somewhere someone mentioning to clear the caches after the install has finished but when I start the install and it reaches "Placing Files" the phone automatically reboots itself, so I held Volume down and Power to go straight back into Download Mode > Boot Mode > Recovery Mode and cleared the caches, let the phone boot up and still have the exact same problem as the above post.
Seeing as though I haven't gotten any advice yet I am going to try an older version of the Installer app, I have 2 seperate backups of my device so if anything goes wrong I can restore, wish me luck!
I have almost the same problem, with the exception that I don't get to see errors.
I have it rooted with superSU 2.64 (beta) and with TWRP 3.0.2.
Start the flash process using TWRP and after a couple of seconds it just black screens and reboots. Some times it survives and boots, sometimes it doesn't boot.
Since I have backed up my whole system before rooting, I can return back to normal.
The funny thing is, I have managed to install Xposed on the first run, but after restoring a back up, it refuses.
No idea what to do
Wolf_vx said:
I have almost the same problem, with the exception that I don't get to see errors.
I have it rooted with superSU 2.64 (beta) and with TWRP 3.0.2.
Start the flash process using TWRP and after a couple of seconds it just black screens and reboots. Some times it survives and boots, sometimes it doesn't boot.
Since I have backed up my whole system before rooting, I can return back to normal.
The funny thing is, I have managed to install Xposed on the first run, but after restoring a back up, it refuses.
No idea what to do
Click to expand...
Click to collapse
You have described my situation perfectly.
I have a back up I can restore through TWRP if I soft brick it, which at this moment I just did.
I tried flashing the same superSU version again seeing as though it was the only one I could get to work (didn't try your version though) and then installed the latest Framework version right after without rebooting, cleared the two caches and rebooted, I get past the first boot screen, I see my mobile providers boot screen, I then get to the screen with One in big letters and it stops there, I'll try a few more reboots before I restore.
Xposed isn't stable on the m9 and is why I have avoided installing it. Some people get it running first time, no issues. Some people brick their phones. It really is a roll of the dice.
I'd stay away from it if i were you. Htc's can't be easily recovered.
Beamed in by telepathy.
it doesn't brick the phone, but there are a few tutorials with other methods of flashing xposed, should be inside software development of android forum. please try those solutions and please stop creating two threads, with nearly same problem. both things can be asked in one thread, thanks
stock rom has often problems. you need to install busybox to have it working properly
1. I started with fully working Samsung Galaxy Note 2 GT-N7100 (Rooted)
2. I'm a newbie to flashing ROM, and read numerous articles to build awareness (and have never used a forum before - so please be gentle!)
3. Installed ClockworkMod Recovery using "ROM Manager"
4. Flashed Slim6 (Slim-6.0.1.alpha.0.1-UNOFFICIAL-20160522-1030) ROM, then Gapps, then re-booted and all OK (Note2 seemed to work fine)
5. Kernel is now3.0.101-Haxynox
6. Spotted (and surprised) that Note 2 no longer rooted (and in particular, want to use Titanium Backup)
7. So, flashed CWM6-root-note2.tar using ODIN, resulting in "Pass"
8. Note2 still not Rooted, and suspect that I should have flashed SuperSu after Slim6 ROM and before Gapps
9. So, tried to reboot to ClockworkMod reccovery using "ROM Manager" but hangs. Tried using VOL+ and HOME and POWER (many times, and for different intervals) but see Samsung logo followed by some "stripes" on the screen (rather like the horizontal hold needs to be adjusted for those that are old enough to remember such things!), but it will not boot into recovery mode.
10. In addition, Odin no longer appears to see the Note2
11. Note2 will boot conventionally, but I'm extremely keen not to have to live without rooting and flashing capability
12. I've searched hard for hints for this particular issue, but would really appreciate some advice, at least so that I don't make my beautiful Note2 any worse (and hope I've not missed any posts that I should have spotted!).
13. Please let me know if I've missed any key information.
Thanks in advance.
Flash the tar version of TWRP for your phone using Odin. You can root by flashing supersu from TWRP.
CWM is very outdated and cannot be used to flash current custom ROMSs.
Many thanks, I've moved over to TWRP and it seems much better.
I also tried to find a more "suitable" (reliable) ROM and chose Resolution Remix, especially as services kept stopping on Slim6.
So now I can get to recovery mode, but still I have issues. Mainly...
a) I've so far failed to flash a compatible Gapps file
b) I've flashed supersu and busybox (Root_SuperSU.0.98-Busybox.1.20.2-signed.zip) but root is still not available. Sometimes I see a "Grant" prompt but it hangs for ages when I grant. The SuperSU app can be seen, but is not responsive. Titanium Backup responds eventually to confirm that Root is not available.
c) Downloading from the Playstore is problematic (sometime very slow to download, usually extremely slow to install - go for a walk type of slow!)
d) Typically the pre-installed applications "stop" shortly/immediately after trying to start them (for example, "Browser", "Clock",...), but then appear after "OK"ing the Close infor box
e) Is my choice of ROM reasonable? And/or is there a ROM which has ROOT "baked in"? (Or, should I go back to JellyBean as being more suitable for a Note2?)
f) Is there some "fine tuning" to the flash process that I need to learn about?
Any hints/tips would be welcome, and many thanks for your initial suggestion to move to TWRP
Is the ROM pre-rooted? If yes, don't flash supersu.
You performed a full wipe, including data, before flashing the ROM?
Phone is running these latest bootloader and modem?
Various versions of gapps are here and flash there version that matches your ROM and processor: http://opengapps.org
Many thanks for your further questions/prompts...
a) Yes, I believe I had done a full wipe before flashing, but haven't touched bootloader and modem so they may well be "old"
b) More reading suggests that Cyanogenmod 13 is a very popular ROM, so flashed this with TWRP
c) Found that with this ROM there were no issues when flahsing openGapps
d) Eventually discovered/realised that CM13 is pre-rooted (but has to be enabled in Settings) and that flashing supersu was causing problems
So, with the benefit of hindsight, if I'd used TWRP/CM13/OpenGapps without flashing supersu, it would have been straightforward! I've certainly learned a lot and you supporting questions have led me to what seems to be a nice, stable implementation of Marshmallow - thanks again.
I'm still looking for a quick/easy way to take a screenshot (just used a palm-swipe before), and a free "real" FM radio, but pretty much everything else works.
Great!!!
Glad you got the phone working on CM. We're all here to help and learn from each other.
Last time I looked, which was a while ago, there was no custom AOSP or CM rom that supported radio functions. If you want the FM radio, look into custom ROMs based on a stock Samsung kernel.
I have been happily running a stock, de-odexed, rooted QB3 ROM for almost a year. I also have xposed 87.1 installed. Recovery is TWRP 3.02. When I first installed this ROM, I had some problems getting LTE to work, but I was able to resolve that issue using Galaxy Tools 3.12 to get into the Hidden Menu. A few days ago, this problem suddenly returned. Galaxy Tools 3.12 did not get me into the hidden menu, which seemed weird. So I installed the GTUpdate2_v3.1.8.apk. When I opened the app, it said I needed to reboot. I did so, and my phone will no longer boot. I did nothing, other than install GTUpdate2_v3.1.8.apk and reboot. Does anyone know what the install of the Galaxy Tools update may have done to make my phone un-bootable? Is there a way to remove GTUpdate2_v3.1.8.apk from the file manager in the TWRP Recovery? Any idea will be greatly appreciated. TIA!