I downloaded and installed the unofficial xposed by abforce for my zte axon 7 lineage os 7.1.2 and i started having problems like its would spam my screen with bank app, facebook, snapchat, TWRP, xposed installer et literally ever app would notify me that it had stopped. So i decided to remove it via the xposed installer, i used the correct uninstalller (arm64) but after reboot im not stuck in a continuous boot. It's juts keeps on booting. Last time i had this problem with a continious boot i re-installed gapps and that worked. But in this case, it is not working. I re-installed magisk as well but it's still just booting. I can boot into twrp recovery and stuff.. It's been booting for around 30mins now and it still won't boot. I have a backup of my system when i first got lineage OS with no gapps though.
Wipe system and install rom zip and gapps. install magisk too if you want
WesTD said:
Wipe system and install rom zip and gapps. install magisk too if you want
Click to expand...
Click to collapse
Will i not lose all my data? I have around like 20GB of data.
WesTD said:
Wipe system and install rom zip and gapps. install magisk too if you want
Click to expand...
Click to collapse
Dw, saved my life, thanks so much
Okay well now Im having problems with all my apps just crashing on me every now and then. It seems to happen for every app even the ones I had never experienced crashes on. Why would this be happening. ?
SugnaB said:
Okay well now Im having problems with all my apps just crashing on me every now and then. It seems to happen for every app even the ones I had never experienced crashes on. Why would this be happening. ?
Click to expand...
Click to collapse
Dunno, just wipe system and do that again. if you can wipe data too, then do so
Related
Hi everyone !
So I flashed OOS 3 MM two days ago, but encountered a weird bootloop.
I flashed rom+super SU with the MM recovery, the rom boots fine I can use it, then when I reboot into recovery to install something like xposed, it gets stuck in a bootloop : rom boots, I get a launching applications windows with optimizing apps etc... then it reboots with the red dot logo, and again the same optimizing windows, etc...
I tried wiping cache/dalvik, I get the same loop.
I tried wiping cache and data, the phone boots fine like a fresh install, but then I have to install SU and everything else again, and when I reboot, same loop again...
What did I do wrong ?
Follow the instructions of this link: http://forum.xda-developers.com/one...de-install-t3350639/post66164888#post66164888
luisito68 said:
Follow the instructions of this link: http://forum.xda-developers.com/one...de-install-t3350639/post66164888#post66164888
Click to expand...
Click to collapse
I've seen this post thank you, but I have access to TRWP recovery, this is not the issue.
I just can't have the rom booting after installing something like xposed... which is weird since ppl say they can install it np (using v80 SDK 23).
Well since OOS 3 is nothing but beta for now don't expect much more out of it. CM13 is more stable.
Skickat från min ONE A2003 via Tapatalk
Hey guys, I ran into a rather odd issue yesterday and can't for the life of me figure out how to get my phone back to normal..
I upgraded TWRP to 3.0.2-0, wiped data, system, dalvik/cache, and attempted to install AOSiP 4.1 + Banks 4/08 Gapps, but after the boot, I get "Unfortunately SetupWizard has stopped", and after getting through the setup, "Unfortunately Theme Provider has stopped", if I click the Theme app it FC's.
This happens on EVERY single ROM I try to install, except Resurrection Remix. (The ROM I was on before flashing AOSiP.) I have tried going back to stock MHC19Q and starting fresh, but I still get FC's. I have also tried every recent TWRP, and MultiROM TWRP. Nothing is working.
Please help...
Edit: @big nu has the same issue..
https://tapatalk.com/shareLink?url=...share_tid=3357511&share_fid=3793&share_type=t
Are you fastbooting the factory images or trying to flash the stock firmware through twrp? If you haven't, fastboot the images including the recovery.
Eric214 said:
Are you fastbooting the factory images or trying to flash the stock firmware through twrp? If you haven't, fastboot the images including the recovery.
Click to expand...
Click to collapse
I fastboot everything. I flashed the stock image from my PC but still no luck...
Perhaps any layers installed?
If so, try removing them from inside TWPR and see if it boots then without FCs.
Casmo said:
Perhaps any layers installed?
If so, try removing them from inside TWPR and see if it boots then without FCs.
Click to expand...
Click to collapse
No Layers were previously installed at all. I was last on a CMTE ROM. I checked /Vendor, just to be sure..
adzcache said:
No Layers were previously installed at all. I was last on a CMTE ROM. I checked /Vendor, just to be sure..
Click to expand...
Click to collapse
So you fastbooted back to stock and booted into the stock system? And you get those issues in the stock firmware?
Sent from my Nexus 6P
jesssiii said:
So you fastbooted back to stock and booted into the stock system? And you get those issues in the stock firmware?
Sent from my Nexus 6P
Click to expand...
Click to collapse
Yes, exactly. I don't understand how this is even possible,
especially after wiping and going back to stock many times.
Literally every ROM installation ends the same.
adzcache said:
Yes, exactly. I don't understand how this is even possible,
especially after wiping and going back to stock many times.
Literally every ROM installation ends the same.
Click to expand...
Click to collapse
1) When you fastboot flash back to stock after a custom rom, what is your process? Do you perform a factory reset in TWRP prior to using fastboot?
2) Are you verifying the MD5 of the factory image prior to flashing?
3) What is the file name of the factory image you are using?
4) Are you able to reproduce this issue with different gapps packages, say Open gapps or an older/newer version of Banks gapps?
4) Are you downloading each of these files over WiFi or Mobile Data onto your phone?
5) Are you also checking the MD5 of each zip prior to flashing?
Based on your post, it looks like you are using one gapps zip and experiencing this issue on every rom. This sounds like a corrupt gapps zip.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
1) When you fastboot flash back to stock after a custom rom, what is your process? Do you perform a factory reset in TWRP prior to using fastboot?
2) Are you verifying the MD5 of the factory image prior to flashing?
3) What is the file name of the factory image you are using?
4) Are you able to reproduce this issue with different gapps packages, say Open gapps or an older/newer version of Banks gapps?
4) Are you downloading each of these files over WiFi or Mobile Data onto your phone?
5) Are you also checking the MD5 of each zip prior to flashing?
Based on your post, it looks like you are using one gapps zip and experiencing this issue on every rom. This sounds like a corrupt gapps zip.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
1. Yes, before flashing the stock image I boot into TWRP and factory reset, I have also tried wiping everything including internal storage in my many attempts to save this phone.
2. No, in all my years on an Android I have never had to check an MD5 and to be perfectly honest I don't really understand how to check MD5's.
3. angler-mhc19q-factory-f5a4e7a1.tgz
4. Yes every Gapps package causes the same outcome. I have tried Slim Gapps, OpenGapps, and Banks Gapps, I have tried downloading them first on my phone, then tried downloading everything fresh from my PC and moving them to my internal storage.
5. Again, not to sure on how to verify these MD5's..
I have tried multiple ROMs, and multiple Gapps. All flashes end the same. I also tried every newer version of TWRP and gone back to stock over 6 times in the past 2 days.
Edit: I'm starting to think that this issue could be related to my Google Account and restoring my device through the Setup, because I have flashed a ROM (DU 04/08) and made it through the setup with no FC's, so long as I don't sign into my Google Account. If I sign in FC's galore and occasional random reboots. I am also experiencing very slow download speeds on LTE and WiFi when downloading Gapps or a different ROM.
adzcache said:
1. Yes, before flashing the stock image I boot into TWRP and factory reset, I have also tried wiping everything including internal storage in my many attempts to save this phone.
2. No, in all my years on an Android I have never had to check an MD5 and to be perfectly honest I don't really understand how to check MD5's.
3. angler-mhc19q-factory-f5a4e7a1.tgz
4. Yes every Gapps package causes the same outcome. I have tried Slim Gapps, OpenGapps, and Banks Gapps, I have tried downloading them first on my phone, then tried downloading everything fresh from my PC and moving them to my internal storage.
5. Again, not to sure on how to verify these MD5's..
I have tried multiple ROMs, and multiple Gapps. All flashes end the same. I also tried every newer version of TWRP and gone back to stock over 6 times in the past 2 days.
Edit: I'm starting to think that this issue could be related to my Google Account and restoring my device through the Setup, because I have flashed a ROM (DU 04/08) and made it through the setup with no FC's, so long as I don't sign into my Google Account. If I sign in FC's galore and occasional random reboots. I am also experiencing very slow download speeds on LTE and WiFi when downloading Gapps or a different ROM.
Click to expand...
Click to collapse
Did you figure out any way to get around the FCs when signing into your account?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Did you figure out any way to get around the FCs when signing into your account?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yes sir, I found a more or less, temporary fix to get around the FC's. I wiped my phone completely, several times, and flashed the stock MHC19Q image a few times and used TWRP 3.0.2-0 to flash DU 04/08, Nano OpenGapps 04/14, and totally avoided signing into my Google Account. After rebooting I signed into Google. No FC's!!! Yay! Then waited 3 hours for my contacts to be synced. (App data was also gone from Settings>Accounts for some reason for 3+ hours) after 3 hours of waiting, everything seems to be working again... For the time being. I'm now scared to flash a ROM other then DU, and my Restorations on 3.0.2-0 have taken over 300+ seconds, but before (3.0.0-1) a restoration was just over 60 seconds...
Weird stuff going on here for sure but at least I got DU! ?
adzcache said:
Yes sir, I found a more or less, temporary fix to get around the FC's. I wiped my phone completely, several times, and flashed the stock MHC19Q image a few times and used TWRP 3.0.2-0 to flash DU 04/08, Nano OpenGapps 04/14, and totally avoided signing into my Google Account. After rebooting I signed into Google. No FC's!!! Yay! Then waited 3 hours for my contacts to be synced. (App data was also gone from Settings>Accounts for some reason for 3+ hours) after 3 hours of waiting, everything seems to be working again... For the time being. I'm now scared to flash a ROM other then DU, and my Restorations on 3.0.2-0 have taken over 300+ seconds, but before (3.0.0-1) a restoration was just over 60 seconds...
Weird stuff going on here for sure but at least I got DU!
Click to expand...
Click to collapse
I had a problem like that. What I did was
Boot into Recover - TWRP 2.8 something
Did the Wipe Data / Factor Reset
Flashed The Rom - For me it was Pure Nexus - April 7, 2016
Flashed The Kernel - For Me Element X
Then wiped Davlik/Cache
Then after that I rebooted let it do what it had to do to boot up. Then rebooted to recovery
Then flashed the GAPPS - for me i used BaNkS-Dynamic-GApps-6.x.x-10-20-15
Then wiped DAvlik/Cache
Then rebooted and let it do its thing again. - I did not get any system startup failed.
Maybe you can not flash the GAPPS all together because the phone is a smart phone but it can still be DUMB.. LOL
Then I did not do a restore of apps from the automatic thing when it asks I just went to pla stoer and let it download what I needed from the my app section.
I'm still facing issues, but at least there are painfully long fixes to make everything work normally... Just pissed, every other android phone I have had, never faced such a persistent issue with rooting and flashing custom ROMs. Especially after restoring to stock..
Sorry to bump this thread, just hoping someone may have a suggestion that may fix up this rather odd issue I've been plagued with?
Quick fix for anyone else facing this:
Downgrade to MHC19I and when flashing recovery, flash TWRP 3.0.0-1, then format userdata in fastboot, copy your files over via PC and flash ROM + Gapps.
Hi guys,
So I wanted to update my phone to a newer ROM, was using an Android 6.0 ROM that I liked a while ago so I decided to get an updated Android 7.1. The ROM worked fine and OpenGaps Pico installed fine.
Once I knew everything worked I downloaded the Aroma package from the OpenGapps app and then ran the install.
Unfortunately the install crashes almost instantly, then the phone reboots into recovery and runs the installer again. So I am stuck in a bootloop of it failing to install.
It says at the top "Running OpenRecoveryScript - Installing Zip"
Put battery into phone, power on, boots into TWRP recovery, crashes on "Starting AROMA Installer", reboots, LOOP.
Many thanks,
Ollie
OllieCrook said:
Hi guys,
So I wanted to update my phone to a newer ROM, was using an Android 6.0 ROM that I liked a while ago so I decided to get an updated Android 7.1. The ROM worked fine and OpenGaps Pico installed fine.
Once I knew everything worked I downloaded the Aroma package from the OpenGapps app and then ran the install.
Unfortunately the install crashes almost instantly, then the phone reboots into recovery and runs the installer again. So I am stuck in a bootloop of it failing to install.
It says at the top "Running OpenRecoveryScript - Installing Zip"
Put battery into phone, power on, boots into TWRP recovery, crashes on "Starting AROMA Installer", reboots, LOOP.
Many thanks,
Ollie
Click to expand...
Click to collapse
Which version of TWRP do you have?
zlazaar said:
Which version of TWRP do you have?
Click to expand...
Click to collapse
TWRP 3.1.1-0
OllieCrook said:
TWRP 3.1.1-0
Click to expand...
Click to collapse
SEE multiple forum posts .
TWRP 3 + may be your problem use an older version .
OllieCrook said:
TWRP 3.1.1-0
Click to expand...
Click to collapse
It's known that TWRP 3.0.1 can't handle Aroma installer.
I'm not sure if later versions were fixed.
v2.8.7 will not fail for sure.
zlazaar said:
It's known that TWRP 3.0.1 can't handle Aroma installer.
I'm not sure if later versions were fixed.
v2.8.7 will not fail for sure.
Click to expand...
Click to collapse
Thanks! I didn't really look into things, just update everything together. I just ended up making my own gapps config.
i have the same problem, but my note 3 only enter to recovery and try to flash this gapps aroma and crash and reboot and do the same thing, dont enter to system, dont enter to download mode, only boots to recovery and crash, any solution? help me, I think he just passed on to a better life
Sorry for my bad english.
TH3-JUL10 said:
i have the same problem, but my note 3 only enter to recovery and try to flash this gapps aroma and crash and reboot and do the same thing, dont enter to system, dont enter to download mode, only boots to recovery and crash, any solution? help me, I think he just passed on to a better life
Sorry for my bad english.
Click to expand...
Click to collapse
just ODIN it to default stock rom.
then after do the new rom flash procedure from start.
Hey all!
Those of you monitoring the unofficial LineageOS thread may have seen me talking about this already. I've been having issues with Magisk. I'm running their beta versions for 13.0.
So here's the story...
I have wanted to pass SafetyNet since May, when I got this phone and rooted it. I obviously went to Magisk, and when I realized that 11.6 was not passing SafetyNet, I decided to try the 13 betas. These didn't pass either, but since they were more recent than 11.6, I stuck with them. But when I heard of the Universal SafetyNet Fix Module, I immediately tried it.
Bottom line, these are my issues:
1. Magisk will not install the module. I go to Magisk Manager -> Modules -> + and select the ZIP for the module. Magisk gives me a toast saying "Installation error!" (See screenshot).
2. Okay, so now I want to start fresh and see if it works then. I boot into TWRP, flash the lastest Magisk uninstaller (08 June), and boot. Nope! Stuck on the "device unlocked" screen with ID: bad key.
3. Uhh.. maybe the stock boot image will work? I go to TWRP and flash the stock boot.img taken from the stock firmware. Still ID: bad key and I'm stuck again.
And I can boot successfully if I flash a Magisk 13.0 beta.
So, does anybody have any solutions? I think I may just have to reflash stock firmware.. not my top choice. Thank you for any help and reading through my long post :good: :highfive:
Try to install magisk v12, it always worked for me on every rom with safetynet fix ( try also the previous uninstaller )
eskamhl said:
Try to install magisk v12, it always worked for me on every rom with safetynet fix ( try also the previous uninstaller )
Click to expand...
Click to collapse
Will give it a shot and update when I see results.
Edit: Nope. I've a feeling that I'll have to start from scratch by flashing stock firmware.
Try flashing the safetynet fix in trwp.
triggerlord said:
Try flashing the safetynet fix in trwp.
Click to expand...
Click to collapse
Tried already. Still no.
Well, as far as I can see you messed up your installation. Start from scratch:
1. Go to TWRP and wipe system, data, cache and dalvik cache.
2. Install LineageOS, GAPPS, Magisk 12 and the stable version of the safetynet fix
3. Reboot and setup your nice and clean system again.
Bottom-line: don't keep messing with an already messed up system. Start clean again. And really: don't install stock boot.img on LineageOS: that's asking for trouble! To be honest: I'm astonished it even booted!!
smitharro said:
Well, as far as I can see you messed up your installation. Start from scratch:
1. Go to TWRP and wipe system, data, cache and dalvik cache.
2. Install LineageOS, GAPPS, Magisk 12 and the stable version of the safetynet fix
3. Reboot and setup your nice and clean system again.
Bottom-line: don't keep messing with an already messed up system. Start clean again. And really: don't install stock boot.img on LineageOS: that's asking for trouble! To be honest: I'm astonished it even booted!!
Click to expand...
Click to collapse
Lol, was doing this all on the stock ROM. See my original response to triggerlord's post.
Edit: issues fixed with a clean install of the pure Nexus ROM. I'm assuming this would be the case with a clean install of the stock ROM, but I am definitely not switching anytime soon (this ROM is amazing!)
I'm a total noob at rooting. I tried rooting my Xiaomi Redmi Note 7 today and everything was going surprisingly well until I decided to reboot my device.
My device is now stuck at fastboot, this may have been caused because I updated Magisk.
I can access TWRP but don't know what to do with it. I don't care about my data, I just want my device to work again.
Could anyone suggest any solutions? Thank you in advance!
Did you try rebooting it fron twrp?. twrp >reboot>reboot into system.
Anon-cross said:
Did you try rebooting it fron twrp?. twrp >reboot>reboot into system.
Click to expand...
Click to collapse
Yeap, didn't work.
I just flashed the stock ROM using MiFlash and it worked fine.
Half a hour later, I messed up again and stuck at fastboot for a second time, so I flashed the stock ROM once again and it works like a charm now.
My second failure made me realize what the problem was (well, kind of).
So, the first time I got a bootloop, I thought that it was due to the fact that I had updated Magisk (I read some similar issues online, that's why I thought so).
But that's not the case because the second time, I installed the latest version of Magisk and the same thing happened.
So, the only action that could have caused the bootloop, which was performed both the first and the second time, is the removal of a system app using System App Remover.
I clearly removed something that I wasn't supposed to. It was one of those system apps but don't know exactly which one cause I removed all of them in bulk and then tried to reboot:
GetApps (com.xiaomi.mipicks)
Games (com.xiaomi.glgm)
Mi Credit (com.xiaomi.payment)
Thanks for helping, I hope my answer helps someone else.
My only problem now, is that I'm unable to install updates to the stock MIUI ROM, but that's fine, rooting the device was worth it anyway.
I faced the same problem today
Install twrp ,root and install system app remover
delete some apps i did not need it
when i reboot the phone stuck at fastboot
I reboot to twrp and do a factory reset, format data didnt help
Return again to recovery and unroot
The phone boot to system
I dont understand why this happened because i
remove the same apps before with xiaomi adb fasboot tools didnt face any problem
Aures Batna said:
I faced the same problem today
Install twrp ,root and install system app remover
delete some apps i did not need it
when i reboot the phone stuck at fastboot
I reboot to twrp and do a factory reset, format data didnt help
Return again to recovery and unroot
The phone boot to system
I dont understand why this happened because i
remove the same apps before with xiaomi adb fasboot tools didnt face any problem
Click to expand...
Click to collapse
Sounds strange.
I thought it was the removal of specific apps, but could it be the System Apps Remover that causes the issue?
I wonder if using Titanium would make any difference but I'm not willing to risk it for a third time, I'm good now.
Test orangefox, maybe the older magisk 19.4 and the magisk module debloater.