So, this is the second time I have tried installing xposed, first I did it with the stock ROM, and that bootlooped it, and then I tried slim pickens, that also boot looped. So now I am just installing the recovery, I was attempting to install just arm and v84, and help? I really want to modify my phone so it looks good
Related
UPDATE: After completely wiping everything(recovery, ROM, bootloader, etc), and putting it back in with fastboot I no longer have this problem. My recovery probably just got corrupted or something while getting sent over to the device.
Got my Nexus 7 3 days ago, had it unlocked and all that jazz within the hour(thanks to the people who put the stuff together). It's great, but I have a problem with flashing .zip files in recovery. It doesn't matter what type of thing I'm wanting to flash(ex-kernel,rom, or even the uber-simple 720p camera mod), if I don't do a full wipe before flashing, then it just ends up boot looping my device. The boot loop doesn't turn the phone all the way off, just the boot animation. Sometimes the launcher will pop up for half a second and then go back to the boot animation.
For example, whenever I flashed the rasbeanjelly rom, I first flashed that, then rebooted(got excited and forgot about gapps) and checked it out. Remembering about gapps, I went back to recovery and flashed gapps. Then it boot looped the animation. After flashing gapps again(trying different combos of wiping cache/davlik), I flashed the rasbeanjelly rom again, and then gapps immediately afterwards. Still a bootloop. So I did a full wipe(including data this time), sideloaded my .zips, and then it flashed and rasbeanjelly booted up with gapps just fine.
This exact same problem has been happening with every .zip that I try to flash(running TWRP, yes all my stuff is updated). If I want to flash a kernel, I have to flash it when I flash my ROM or else I'll get boot loop. I can't really make any modifications without having to completely wipe my device(which is annoying because I carry a lot of data around on my stuff)
I'm asking if there is a way to flash a .zip without having to completely wipe my device. I'm not a noob to android at all(ROM cooker over at androidforums), but I can't figure it out, I'd love to make stuff for the grouper but this is kind of a big roadblock for me. Logcat isn't helping either. Hopefully I just skimmed over something and it's a simple fix. Thank you for your tips/suggestions/solutions.
EDIT: forgot to mention something. When I flash a new ROM and get it going, I always make a full backup in recovery. If I flash something, and boot loop it, I can't restore it correctly. Recovery says that it restores all good, but it still boot loops(even though I just restored a backup of a non-boot looping system from no more than 5 minutes ago).
If I read your post correctly, you've only tried this on one ROM. Try the same thing on CM10 or PA or whatever you want.
korockinout13 said:
If I read your post correctly, you've only tried this on one ROM. Try the same thing on CM10 or PA or whatever you want.
Click to expand...
Click to collapse
I've actually used several, and it seems to be happening on all of them. I've tried flashing things with PA, CM10, Stock, and RasberryJelly. The kernels I have attempted to flash have been Trinity, Motley, and Franco. All with no success and boot looping me :/
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 am on 6.0.1 CyanogenMod13. I haven't done a whole lot root-wise but just today I was looking to get something from xposed and it turned out I didn't even have it installed, so I downloaded it and installed it but needing to flash the .zip I tried to boot into TWRP recovery. Somehow it got uninstalled or something because I could only get into the LG stock screen asking if I wanted to wipe everything. So I tried to install TWRP using Flashify, I installed and on the reboot it gave me a "Can't Enter Recovery Or Update" and some more things about it on the top left above the boot logo. I can't do anything recovery-wise. I'm looking to sell my G2 but I want to make it stock or at least a clean install and I can't do any of that. What can I do??
NinjaChachi said:
I am on 6.0.1 CyanogenMod13. I haven't done a whole lot root-wise but just today I was looking to get something from xposed and it turned out I didn't even have it installed, so I downloaded it and installed it but needing to flash the .zip I tried to boot into TWRP recovery. Somehow it got uninstalled or something because I could only get into the LG stock screen asking if I wanted to wipe everything. So I tried to install TWRP using Flashify, I installed and on the reboot it gave me a "Can't Enter Recovery Or Update" and some more things about it on the top left above the boot logo. I can't do anything recovery-wise. I'm looking to sell my G2 but I want to make it stock or at least a clean install and I can't do any of that. What can I do??
Click to expand...
Click to collapse
Same happened to me still cant fix it but you could try going back to stock (wouldn't work for me driver problems on windows 10)
http://forum.xda-developers.com/showthread.php?t=2432476
bump
homegrown1982 said:
Same happened to me still cant fix it but you could try going back to stock (wouldn't work for me driver problems on windows 10)
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
This got me down to 4.4.2 but when trying to install TWRP it gives me the same Boot certification error and I can't
EDIT: I used AutoRec on 4.4.2 and I have TWRP working!
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!