I made a mistake when installing xposed on my G935F and am now stuck in a bootloop.
I downloaded the xposed uninstaller to undo my install and fix my mistake, but I'm unable to boot into recovery.
Do I have to reflash it via odin?
Note: I downloaded the sdk 23 arm64 version, but I didn't wipe data like the guide said to do (didn't see that guide until after I flashed, I was following another guide).
Thanks.
Why are you unable to boot into recovery? And not wiping data would not prevent the phone booting as long as you installed the correct Xposed framework. Did you install Wanam's arm64 version here or the official one? If you installed the official version in rovo89's thread then that is why you're getting a boot loop. Unless things have changed, that doesn't work on Touchwiz roms and causes bootloops, hence why Wanam made a separate version.
Beefheart said:
Why are you unable to boot into recovery? And not wiping data would not prevent the phone booting as long as you installed the correct Xposed framework. Did you install Wanam's arm64 version here or the official one? If you installed the official version in rovo89's thread then that is why you're getting a boot loop. Unless things have changed, that doesn't work on Touchwiz roms and causes bootloops, hence why Wanam made a separate version.
Click to expand...
Click to collapse
I used the official one version.
I have no idea, but I tried the recovery boot sequence so many times and I can't get it to boot into recovery. What should I do?
Reset your phone (volume down & power for 7-10 seconds) then remove your fingers and press volume up & home & power to boot into recovery. If you have TWRP installed (and I assume you do unless you used Flashfire to flash Xposed) there is no reason it shouldn't work. Installing Xposed, even if you used the incorrect version, would have absolutely no effect on the recovery partition.
Beefheart said:
Reset your phone (volume down & power for 7-10 seconds) then remove your fingers and press volume up & home & power to boot into recovery. If you have TWRP installed (and I assume you do unless you used Flashfire to flash Xposed) there is no reason it shouldn't work. Installing Xposed, even if you used the incorrect version, would have absolutely no effect on the recovery partition.
Click to expand...
Click to collapse
That still doesn't work for me.
I used flashfire the first time and it didn't work (some guide on xda said to use it). It booted fine after that. I then reverted back to flashify and booted into twrp to flash it, and after that it just sat on the S7 edge boot screen endlessly.
I kept trying and managed to boot into recovery. I flashed the xposed uninstaller and its now running again. Thanks for the help!
l33t p1mp said:
I kept trying and managed to boot into recovery. I flashed the xposed uninstaller and its now running again. Thanks for the help!
Click to expand...
Click to collapse
Use this Xposed
https://www.dropbox.com/s/2q69cpwxz...arm64-custom-build-by-wanam-20160504.zip?dl=0
"And on that bombshell!"
Sent from my Echoe powered AEL driven G935F
Related
So I went to far with my S4 with xposed frameworks and got it stuck in boot loop. Being a fool I never installed a custom recovery. What I'm wondering is whether it is safe or not to install a custom recovery to fix my problem by uninstalling xposed fireworks?
A recovery and a rom are two independant things. So just flash away.
Lennyz1988 said:
A recovery and a rom are two independant things. So just flash away.
Click to expand...
Click to collapse
Thank you very much, i thought the rom and recovery where two separate things but wasn't 100% sure and didn't want to risk hard bricking it. Worked like a charm and so did the xposed disabler. Back to normal now
I'm running ResurrectionRemix-M-v5.6.5-20160316 with the latest TWRP recovery and Xposed.
The last time I used the recovery was on 22/03 to make a backup of my ROM (I've entered the recovery more than a dozen times before this backup with no issues).
Today I wanted to switch from Ressurrection Remix to crDroid (Ressurrection for some reason becomes laggy after use and only a reboot resolves this issue).
I downloaded all of the zips I required (ROM, GAPPS, SU etc.)
I selected to reboot to recovery using the advanced reboot option.
The phone rebooted and displayed recovery booting in blue as per the norm.
The TWRP splash screen showed for around 10 sec or so then the phone rebooted (this never happened before).
Thinking that this was a bug with the recovery, I tried turned off the phone via the power menu once my I got into MM and then removed the battery and used the power + up button combo to enter recovery however still no go.
Next I tried flashing the TWRP 3.0.0.tar file via odin, still no luck.
The question I have is how do I resolve the issue?
Try flashing a different version of TWRP.
Or flash an twrp.img file via the app Flashify.
Ok to downgrade?
GDReaper said:
Try flashing a different version of TWRP.
Or flash an twrp.img file via the app Flashify.
Click to expand...
Click to collapse
So it's ok to downgrade to say 2.8.60 with F2FS support?
Fixed!!!
jdhot2 said:
So it's ok to downgrade to say 2.8.60 with F2FS support?
Click to expand...
Click to collapse
I found a custom version of the recovery made by the JDC team http://forum.xda-developers.com/gal.../jdcteam-twrp-touch-recovery-3-0-0-0-t3312115.
I flashed the recovery using flashify.
All fixed now
I had Magisk 16.0, but Magisk Hide didn't work very well. I wanted to see if it would work with Magisk 14. Not it's stuck in a boot loop. It shows the "Samsung Galaxy S8 powered by android" for a few seconds then reboots. I can still boot into TWRP recovery and access the storage. Download mode works too. I tried uninstalling Magisk and flashing the stock boot image. Neither worked. Is there anhthing I can do to make my phone work again without losing my data?
Update: if I have to flash the stock ROM, I'm planning to do the next thing: back up my data partition to an external hard drive with TWRP. After I flash the ROM and wipe everything, I want to reinstall TWRP and restore that backup. Would this cause any issues?
vladone97 said:
I had Magisk 16.0, but Magisk Hide didn't work very well. I wanted to see if it would work with Magisk 14. Not it's stuck in a boot loop. It shows the "Samsung Galaxy S8 powered by android" for a few seconds then reboots. I can still boot into TWRP recovery and access the storage. Download mode works too. I tried uninstalling Magisk and flashing the stock boot image. Neither worked. Is there anhthing I can do to make my phone work again without losing my data?
Click to expand...
Click to collapse
I think you cant, since your phone is bootlooped there is no way to get your data back ..
You should backup your data even before root your phone ..
Just flash latest TWRP img.tar from odin, disable auto reboot from the options on odin , after the success flash you need to press the buttons to enter recovery mode .
https://android.gadgethacks.com/how...-s8-into-recovery-mode-download-mode-0177223/
StonebridgeGr said:
I think you cant, since your phone is bootlooped there is no way to get your data back ..
You should backup your data even before root your phone ..
Just flash latest TWRP img.tar from odin, disable auto reboot from the options on odin , after the success flash you need to press the buttons to enter recovery mode .
https://android.gadgethacks.com/how...-s8-into-recovery-mode-download-mode-0177223/
Click to expand...
Click to collapse
I already have TWRP.
I am having issues installing the xposed framework. I have rooted with Magisk successfully and I'm on the ElementalX kernel. When I try to install the xposed framework via TWRP, when I reboot back into the OS, it gets stuck in a hello moto bootloop. I can boot into the OS without issue by clearing the dalvik cache and the normal cache after installation, but when I get into the Xposed installer app, it says it's installed but not running. There is no log, so I assume it is because the Xposed folder doesn't have permissions. I give it permissions and reboot by pressing restart in the power menu, but when I do that, it gets in the bootloop again.
I would appreciate any help on this.
MineMasterHD said:
I am having issues installing the xposed framework. I have rooted with Magisk successfully and I'm on the ElementalX kernel. When I try to install the xposed framework via TWRP, when I reboot back into the OS, it gets stuck in a hello moto bootloop. I can boot into the OS without issue by clearing the dalvik cache and the normal cache after installation, but when I get into the Xposed installer app, it says it's installed but not running. There is no log, so I assume it is because the Xposed folder doesn't have permissions. I give it permissions and reboot by pressing restart in the power menu, but when I do that, it gets in the bootloop again.
I would appreciate any help on this.
Click to expand...
Click to collapse
I had this problem also, I would typically just long press the power button and let it complete a second normal boot, and then xposed would work after the second boot completed. (The second boot after initial bootloop would load up just fine.) However, after a few reboots, my phone became unstable and I had to reflash the stock ROM. I'm not sure how stable OREO xposed is on this device yet. It may have just been my modules. (GravityBox, Flat Color Keyboard, Bars, and Status Icons)
Drkmatr1984 said:
I had this problem also, I would typically just long press the power button and let it complete a second normal boot, and then xposed would work after the second boot completed. (The second boot after initial bootloop would load up just fine.) However, after a few reboots, my phone became unstable and I had to reflash the stock ROM. I'm not sure how stable OREO xposed is on this device yet. It may have just been my modules. (GravityBox, Flat Color Keyboard, Bars, and Status Icons)
Click to expand...
Click to collapse
I also have a Moto G5 plus and when I tried to reboot it a second time it was still stuck in its boot loop so I had to enter TWRP to flash the uninstall and if I try to install Xposed via Magisk I have to factory reset, I don't think it's me ROM because it's the same as a stock ROM (had to install the ROM because the one it came with got corrupted or something when I tried to install Xposed where I still had the boot loop problem). I am running 8.1.0 Oreo.
I think a lot of my problem was i was using a sprint variant also. I think a lot of other users are using the verizon/t-mobile variants. I never really did get xposed to work properly on oreo on the sprint variant of this phone no matter what i tried.
Any news on this issue?
I just updated to 8.1 and would like to get xposed up and running like I had it on Nougat. Has there been any fixes yet to this. Thanks to anyone for a reply.
I get bootloop when I install magisk & xposed.
I am using Xposed since months
Working fine
One thing you is that we've to do soft reboot instead of regular reboot
So i started to update viper4android and i accidentally pressed volume up which tries it to install via AROMA now my phone is stuck on bootloop, it just keeps rebooting to recovery trying to install the viper4android, is there any possible way to get out of this or my phone is dead?
Any help will be appreciated,
TIA
a safe haven said:
So i started to update viper4android and i accidentally pressed volume up which tries it to install via AROMA now my phone is stuck on bootloop, it just keeps rebooting to recovery trying to install the viper4android, is there any possible way to get out of this or my phone is dead?
Any help will be appreciated,
TIA
Click to expand...
Click to collapse
You didn't specify your exact phone model, so assuming KLTE
AFAIK aroma does not work well with our TWRP
Can you pull the battery and then boot directly to recovery so you can wipe system/cache/Dalvik and then flash the ROM again?
If recovery is messed up, can you pull battery, then boot to download mode so you can reflash TWRP in Odin/Heimdall, or better yet flash latest stock Rom (caution if you have a g900V/A with stock locked bootloader) in Odin/Heimdall, followed by TWRP?
Post again if you need more help, and try to include as many specifics as possible eg exact phone model, TWRP version, Rom zip filename, Gapps, etc. I'll try to help if I can
I am very sorry for not posting the model number, mine is G900I (KLTEDV), everytime i turn on the phone it just keeps booting onto the recovery and goes to install the viper4android but it fails to do that and reboots again and again, its impossible to do anything basically, not booting onto the rom or anything. Recovery version is TWRP 3.2.2-0, it opens up directly to the zip file which is viper4androidfx-aroma.zip and tries to flash it and crashes and the whole process starts again, pulling the battery didnt break the chain it just keeps rebooting to do that again!
I reflashed a new twrp recovery ver 3.2.3-0, but it still tries to flash that zip file again! Even after deleting the file itself it still tries to flash it and keeps rebooting!
How do i get rid of this twrp loop!? This is so weird!
P.S: After reflashing twrp the phone boots to the rom normally but i cant access recovery anymore, whenever i go to recovery it goes on in an infinite bootloop (cleared cache and dalvik cache using es explorer root), I am also on LineageOs 16.0, tried stock recovery but the stock recovery also keeps bootlooping.
P.S this viper4android is a magisk module!
NVM, solved it by flashing stock rom! Thanks!