So, yeah, I want to use some of xposed's tweaks, but I heard it causes bootloop on zenfone. I'll be doing a backup with adb before I try anything, but does it cause a bootloop? And if it does, how can I recover without reflashing ROM?
v79 sdk21 for x86, flashed with TWRP, works just fine with current stock firmware, no bootloop. Older versions will bootloop because of the google monthly security patches.
kanagawaben said:
v79 sdk21 for x86, flashed with TWRP, works just fine with current stock firmware, no bootloop. Older versions will bootloop because of the google monthly security patches.
Click to expand...
Click to collapse
yep ^^
as long you follow the instruction and having the latest version it should be ok.
I had a bootloop once, but it happen cause i got the wrong version.
Now im use v78 sdk23 on cm13, its works fine. Dont be scare to try,
de5ta said:
I had a bootloop once, but it happen cause i got the wrong version.
Now im use v78 sdk23 on cm13, its works fine. Dont be scare to try,
Click to expand...
Click to collapse
But what did you do once you were in bootloop.... i flash the entire rom and i took an entire day to download , i was so ****ed up then , i had chills when i was in bootloop (phone was only month old); Is there any easy way to get phone out of bootloop qhen any module is responsible for it?
Same to me, i flash my pre root rom to get back from bootloop.
Most poeple suggest to backup your rom first before install xposed, they say it can restore when u get bootloop.
There is an uninstall zip for bootloops
http://forum.xda-developers.com/showthread.php?p=58828974
Sent from my Z00D using Tapatalk
I wonder,
why my device feels laggy when using xposed?
using v79-sdk21-x86, rooted & busybox
XPosed is like nuclear power, you can do as much great things with that you can do bad things.
Up to you if xposed is safe.
Related
OK, so I've always rooted my phone via Method 2, using the method of a tethered CWM recovery to root,. and have always unrooted prior to installing an update. I did the exact same thing with my phone when the new update .139 came out. I always also had XposedFramework installed via the ADB method where I just ran InstallXposedFramework.bat and InstallXposedInstaller.bat to install it. Now, little did I know I should have read the thread on .139 firmware BEFORE installing the latest update and Xposed because apparently that causes a bootloop. So now, I'm stuck with a bootloop. I've tried running RemoveXposedFramework.bat to get me out of the situation but to no avail, phone still goes into a bootloop.
So is there anyway I can get out of this bootloop without completely wiping my phone? My bootlocker is still locked and can only get into a tethered CWM recovery. And if I truly do need to wipe my to get everything working again, how should I do this? Any help would be useful right now.
I had the same issue. Just install the .139 again. It works fine for me without wipes
Anyone found a fix yet for this yet?
RGoody said:
Anyone found a fix yet for this yet?
Click to expand...
Click to collapse
xposed v78 works with .139
RGoody said:
Anyone found a fix yet for this yet?
Click to expand...
Click to collapse
If you're referring to getting rid of the bootloop itself, from the help of another forum member, I got it fixed to get out of the bootloop. Here's the link. I managed to keep all of the data on my phone's internal memory as well. You lose root but it's easy to re-root it again.
In terms of Xposed Framework working with .139, supposedly V78 of Xposed works.
Toronadian said:
If you're referring to getting rid of the bootloop itself, from the help of another forum member, I got it fixed to get out of the bootloop. Here's the link. I managed to keep all of the data on my phone's internal memory as well. You lose root but it's easy to re-root it again.
In terms of Xposed Framework working with .139, supposedly V78 of Xposed works.
Click to expand...
Click to collapse
I was able to get out of the bootloop by re-sideloading .139, and for the xposed, yeah, I found a very useful post on the Zenfone 2 subreddit about how v78 fixes the bootloop. I had been trying to flash v74. All good now.
For all those who are stuck in bootloop when trying to install xposed after upgrading to latest version. I got my bootloop issue solved without any data loss. In the zip file containing xposed installer there is also a file which will remove xposed. Execute it when the phone is in bootloop.
Now the phone will reboot but will again be stucked in bootloop. To solve this download zenfone 1 Click Root Tool. Run the unroot file when the phone is in bootloop. After that your phone will reboot and will work fine but you will have lost root and xposed. You can re-root your phone and there will be no bootloop. But installing xposed will result in bootloop.
I will check if latest version of xposed works without bootloop and update. For now no xposed on latest firmware
There is no need to sideload the latest version. I got dead android while trying to apply update again.
Sorry I forgot to post the link of how I was able to flash the zip of the new firmware previously. It seems like you already fixed this but I'll still post it anyway.
http://forum.xda-developers.com/zenfone2/general/guide-fix-bootloop-rooted-zenfone-2-t3191244
Hi everyone,
Stuck in BootLoop After Installing BETA-SuperSU-v2.68-20160228150503.zip. I installed using TWRP. Install looks it went fine then I rebooted and bootloop.
HTC M9 (t-mobile)
Unlocked
TWRP version - twrp-3.0.0-2-hima
After installing "BETA-SuperSU-v2.68-20160228150503.zip" my phone is stuck in bootloop. It has rebooted at least 5 times. I then was able to get into HTC download mode.
What can I do now? I have a full nandroid backup.
cloves said:
Hi everyone,
Stuck in BootLoop After Installing BETA-SuperSU-v2.68-20160228150503.zip. I installed using TWRP. Install looks it went fine then I rebooted and bootloop.
HTC M9 (t-mobile)
Unlocked
TWRP version - twrp-3.0.0-2-hima
After installing "BETA-SuperSU-v2.68-20160228150503.zip" my phone is stuck in bootloop. It has rebooted at least 5 times. I then was able to get into HTC download mode.
What can I do now? I have a full nandroid backup.
Click to expand...
Click to collapse
Restore your boot partition or dirty flash rom
Fixed
Thanks thicklizard for the quick reply,
Ended up booting back into twrp and installing BETA-SuperSU-v2.65-20151226141550.zip (aka version 2.65). Connected phone the PC while I was in TWRP, copied older zip file then installed. That fixed the issue and now I am rooted.
cloves said:
Thanks thicklizard for the quick reply,
Ended up booting back into twrp and installing BETA-SuperSU-v2.65-20151226141550.zip (aka version 2.65). Connected phone the PC while I was in TWRP, copied older zip file then installed. That fixed the issue and now I am rooted.
Click to expand...
Click to collapse
Im having the same issues i flashed over the supersu 2.65 but still stock... what older zip file did u install?
willardwellls said:
Im having the same issues i flashed over the supersu 2.65 but still stock... what older zip file did u install?
Click to expand...
Click to collapse
Flashed via twrp 3.0.0-2
This is the file:
https://download.chainfire.eu/752/SuperSU
FYI, if you are flashing a ROM, sometimes they have superSU already built in. So no need to flash your own superSU. That is the case with Viper ROM. Also make sure your firmware matches the firmware that the rom is using.
I had the same problem with SuperSU 2.76. I wiped dalvik cache and cache twice, flashed SuperSU 2.64 and no more bootloop. No backup, stock ROM. I almost crapped myself a little. About to give this thing it's first ROM flash.
Just had the same problem. Put on 2.65 and it's now booting into the OS. Thanks!
Thanked God i found this post, tried latest stable also beta seems bootloop never ends. Try v2.6 all become alive. Many thanks Sir
Same problem after installing latest SuperSu version from TWRP recovery: eternal bootloop. I didn't know what was wrong and tried different supersu versions but I became reluctant to keep trying that method after the second time... Gladly, I found your thread before doing anything else (even posting myself a thread) and now I can continue my evil rooting plans :victory: Thank you for asking and thanks for replying you prevented me to re-lock my phone and do everything from scratch. It's my first root
You're welcome guys, rooting this htc has been the best thing i have done. Let's keep the HTC community in here alive and well!
I recommend once you get the root part done backup then install xposed framework. No ads, YouTube play back without screen being on, best software once you are rooted.
Sent from my HTC One M9 using Tapatalk
cloves said:
You're welcome guys, rooting this htc has been the best thing i have done. Let's keep the HTC community in here alive and well!
I recommend once you get the root part done backup then install xposed framework. No ads, YouTube play back without screen being on, best software once you are rooted.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I beg to differ about xposed. One wrong mod and you're phone is bricked.
Beamed in by telepathy.
I have not had any problems with exposed and that's why I said make a backup on your card. I have installed multiple Xposed modules and have not had any issues I have not seen anybody break the phone either. As I mentioned make a trip back up what is the point of rooting your phone if you're not going to use it to its full potential that's just me
Sent from my HTC One M9 using Tapatalk
Me too - Bootloop
I have an AT&T HTC One M9. Bootloader is HtcDev Unlocked, S-On, and TWRP is installed...
I previously messed up my phone bad by trying to install a OS ROM that didn't work right... So, I used my PC to overwrite it with the HTC OTA version, and that worked. I went into the M9 and tried to download and run SunShine, to get S-OFF, but it said it couldn't temproot, I don't know why, it's pissing me off, and SunShine suggested I root the device with another means. I downloaded SuperSU 2.69 and tried that, it installed okay (I guess) and said it might loop a few times. Try 100! Infinite loop. I tried SuperSU 2.65, but it said, "it's already patched!" and the system ROM had not been backed up. (I'm assuming SuperSU patches whatever is in the system partition?)
Anyhow, it's currently stuck in an infinite loop. I'm going to try re-putting the HTC OTA system ROM on it (great, I lose another half-day at this), and then re-try SuperSU 1.65.
Any idea why SunShine won't S-OFF a device? Why won't temproot work? Any other (good) way to root it?
Twrp question?
I have twrp 3.0.0 installed I make a backup of system and boot... when I boot in the first time on twrp displays a message saying something about OTA protection if I want to receive otas and protect the recovery??? What is that... sorry for my bad English is not my mother language...
thanks dude
Skorpyun812 said:
I had the same problem with SuperSU 2.76. I wiped dalvik cache and cache twice, flashed SuperSU 2.64 and no more bootloop. No backup, stock ROM. I almost crapped myself a little. About to give this thing it's first ROM flash.
Click to expand...
Click to collapse
i am stuck and say my phone going to crab but your post save me
cheers
---------- Post added at 10:53 AM ---------- Previous post was at 10:51 AM ----------
White91 said:
I have twrp 3.0.0 installed I make a backup of system and boot... when I boot in the first time on twrp displays a message saying something about OTA protection if I want to receive otas and protect the recovery??? What is that... sorry for my bad English is not my mother language...
Click to expand...
Click to collapse
i think your s-on on bootloader mape it off then install recovery
I was using SR3-SuperSU-v2.79 and flashed SuperSU v2.82 but
phone wouldnt boot up , so I reflashed SR3-SuperSU-v2.79 and
phone now boots ok but I dont have root,
I'm using TWRP blu-spark 3.1.0 v26
Petesky said:
I was using SR3-SuperSU-v2.79 and flashed SuperSU v2.82 but
phone wouldnt boot up , so I reflashed SR3-SuperSU-v2.79 and
phone now boots ok but I dont have root,
I'm using TWRP blu-spark 3.1.0 v26
Click to expand...
Click to collapse
Flash your rom then supersu, Magisk is also a nice option.
Puddi_Puddin said:
Flash your rom then supersu, Magisk is also a nice option.
Click to expand...
Click to collapse
I thought I might have to do that , is there a link to the latest SuperSU that works
on oneplus 3
Petesky said:
I thought I might have to do that , is there a link to the latest SuperSU that works
on oneplus 3
Click to expand...
Click to collapse
Well you already have the version number.. Not too hard to search is it?
http://lmgtfy.com/?iie=1&q=latest+stable+supersu
Well that was clever
I already did that and tried 2 that didnt work ,
SuperSU282 and SuperSU-v2.82-SYSTEMMODE , I asked for one that worked on the oneplus 3,
But done a fresh install of 4.1.3 , flashed SR3-SuperSU-v2.79 again and its working good, updated binaries and no DM_verity error
Petesky said:
Well that was clever
I already did that and tried 2 that didnt work ,
SuperSU282 and SuperSU-v2.82-SYSTEMMODE , I asked for one that worked on the oneplus 3,
But done a fresh install of 4.1.3 , flashed SR3-SuperSU-v2.79 again and its working good, updated binaries and no DM_verity error
Click to expand...
Click to collapse
Well there is no Supersu that specially works for the Oneplus 3. That is why I always recommend to try things yourself. Take a backup of system and boot and you basically can keep trying things without risking that your phone doesn't boot or you loose data.
Good point
just update the 2.79 via playstore to 2.82
I was trying to get help on Reddit but I wasn't able to get any help.
I was able to find the Twrp image to Boot into but Magisk isn't installing when I go to try to install it.
I'm using 13.4 for my pixel XL and I tried 13.3
Any ideas why they aren't working? No errors in Twrp when installing.
DudeThatsErin said:
I was trying to get help on Reddit but I wasn't able to get any help.
I was able to find the Twrp image to Boot into but Magisk isn't installing when I go to try to install it.
I'm using 13.4 for my pixel XL and I tried 13.3
Any ideas why they aren't working? No errors in Twrp when installing.
Click to expand...
Click to collapse
Hello,
Not sure if Magisk is even working on O but you would want to flash a kernel like ElementalX first or the modified stock. Flash the kernel, then Magisk but again I am not sure if it is actually working yet. If you do get it installed and working be sure to report back to all. Also if you had SU + SUhide prior then you will want to flash the Magisk remover first, then kernel then Magisk.
Cheers
jschill31 said:
Hello,
Not sure if Magisk is even working on O but you would want to flash a kernel like ElementalX first or the modified stock. Flash the kernel, then Magisk but again I am not sure if it is actually working yet. If you do get it installed and working be sure to report back to all. Also if you had SU + SUhide prior then you will want to flash the Magisk remover first, then kernel then Magisk.
Cheers
Click to expand...
Click to collapse
Yup. Just verified it doesn't work. I booted into twrp, installed ElementalX, then Magisk 13.4 and rebooted, still doesn't work.
Then I booted into twrp, installed ElementalX and Magisk 13.3 and rebooted. Nothing.
I also installed TWRP RC2 and it works fine. If you want I can upload the bootable image for twrp and RC2 that I used. At least now I have a way of testing it out (well, to keep testing it out, when I'm at work).
DudeThatsErin said:
Yup. Just verified it doesn't work. I booted into twrp, installed ElementalX, then Magisk 13.4 and rebooted, still doesn't work.
Then I booted into twrp, installed ElementalX and Magisk 13.3 and rebooted. Nothing.
I also installed TWRP RC2 and it works fine. If you want I can upload the bootable image for twrp and RC2 that I used. At least now I have a way of testing it out (well, to keep testing it out, when I'm at work).
Click to expand...
Click to collapse
So you have twrp installed with no issues?
humdrum2009 said:
So you have twrp installed with no issues?
Click to expand...
Click to collapse
Correct
I'm using a 6p with a pixel on the way. I had it working on the 6p with Oreo. I'm pretty sure I had to download an apk as well as flash the zip. Have you done this?
the pixel has a special magisk version because of boot a/b system stuff from my understanding. So it doesn't matter if it works on any other google phone.
It sucks too because i heavily rely on magisk due to how good it is on hiding...goodwin_c is my only hope. hanging on a thread here...
If you mention other root hiding methods just know that no...they all suck lol
j_mullet said:
I'm using a 6p with a pixel on the way. I had it working on the 6p with Oreo. I'm pretty sure I had to download an apk as well as flash the zip. Have you done this?
Click to expand...
Click to collapse
Zizzy2020 said:
the pixel has a special magisk version because of boot a/b system stuff from my understanding. So it doesn't matter if it works on any other google phone.
It sucks too because i heavily rely on magisk due to how good it is on hiding...goodwin_c is my only hope. hanging on a thread here...
If you mention other root hiding methods just know that no...they all suck lol
Click to expand...
Click to collapse
What Zizzy2020 said. It is annoying. I can't wait for the next magisk to be released.
Check out this post, it works like a charm.
Hello,
This one is a funny one, as on my OnePlus 2 rooting was easy but ever since I got my OnePlus 5T I've always had issues, rooting it in the first place was troublesome but managed to get Magisk running with OOS and I have decided to migrate to Resurrection Remix (What I used to run on OnePlus2) when I format my data and flash RR and gapps it runs perfectly fine, but when I flash Magisk it states it has successfully changed the boot.img and when I restart the system it ends up going to the bootloader, I can then run the Magisk uninstaller and my RR will run normally again.
Magisk definitely seems to be the issue but I don't know why, I have gone back to stock firmware and locked my bootloader and tried again from stock and still, after installing the latest RR with Magisk after the first initialisation I get no errors it just doesn't boot.
Has anyone got any idea of what I could do wrong, I have found myself following guides online with no luck. As no one seems to have an issue similar.
An advice?
As far as I know.magisk should be flashed only after booting into system and completing the initial setup
Hi dude,
maybe you will find your answer in this thread!
https://forum.xda-developers.com/on...x-os-6-0-0-t3747038/post76922486#post76922486
rakuyo said:
As far as I know.magisk should be flashed only after booting into system and completing the initial setup
Click to expand...
Click to collapse
I do install it after the intial set up and it still doesn't load :/
nicorvienne said:
Hi dude,
maybe you will find your answer in this thread!
https://forum.xda-developers.com/on...x-os-6-0-0-t3747038/post76922486#post76922486
Click to expand...
Click to collapse
Thanks this was my solution, just needed to flash a custom kernel.
NarcoticNoble said:
Thanks this was my solution, just needed to flash a custom kernel.
Click to expand...
Click to collapse
You are welcome!