Hello,
I've recently rooted my oneplus one and most of my issues are away. But since i have installed some xposed mods, when i reboot. First it gets in some sort of" bootloop" (i waited some minutes and it didn't get out of the boot animation) so then I hold the powerbutton and boot it again and then it just boots normally.... And this happends every time i (re)boot! Can I fix this?
(Here is some information if u need it... Sorry im noob)
-CM12
-Android 5.1.1
-Rooted
-Android sdk 22
Xposed apps:
-Adblocker
-Bootmanager
-Android apps theme engine pro
-DS battery saver
-Force fast scroll
-Gravitybox [LP]
-Greenify
-Materialize xposed installer
-Screenoffanimation
-Smooth progress bars
-Snapchat full caption
-Snappprefs
-Spotify skip
-Xuimod
Edit: i just rebooted and got me in a real bootloop i think.... I tried restarting several times and it did not fix. So i flashed a incremental update that i had on my phone and now it rebooted. Do i have/had a softbrick? I was experiencing some lag before that reboot that was the reason i rebooted cause my phone froze.
You can get help on xposed threads but xposed does some nasty things to your phone that's why many developers doesn't even consider a log if you are using xposed...try by using them one at time and eliminate the cause of bootloop
Related
REPORT BUGS OF ALL CUSTOM ROMS
Guys report bugs of custom roms here so devs can solve and shortout.
Post bug with custom rom name with its version.
And explain your problem clearly so dev can understand it by seeing one time without asking you again.
bugs
In color os after after rebooting 2 or 3 times if we turn on the wifi it stucks at obtaining IP address.It keeps saying that.
chanti548 said:
In color os after after rebooting 2 or 3 times if we turn on the wifi it stucks at obtaining IP address.It keeps saying that.
Click to expand...
Click to collapse
which version?
version 1.2 and the problem still occurs even after applying patch
In sgalaxy v2 when I tried to install xposed framework for the first time it installed and phone booted up properly but it always restarted in 2-3 min so I disabled it from recovery....
And now when I am trying to install it again it is causing bootloop any help please????
In pixel plus ui 5.1 everytime i open an app it keeps on hangging or lagging and when i open a game it also keeps on lagging and worst force close please fix this my device is redmi note 9 pro global
hello xda developers, i have a issue regarding oneplus 7 pro, I installed pixel experience rom, it worked very well for 2 day, then I rooted it, after 1 day of rooting while scrolling through Instagram my device crash and stopped working, it doesn't turn on normally, it goes to fast boot mode from their also it just turn on the oneplus bootup screen and shows a pixaleted (shown in photo and video) screen and automatically switch off. i have tried to factory reset from recovery and also re-install the rom but still same response. what should i do?
Hello, Newbie Here!
So I recently flashed the Resurrection Remix ROM Build 6.8 and Kernel 6.2.
The Build is rather stable and In my honest opinion better than CM12.1 which I was on previously.
So the normal functions of the phone are normal and I feel this is a much stable build. I use a ASUS Zenfone 5(ASUS_T00F)
But I face random reboots where the phone restarts itself and gets stuck at the boot. Only when i try to force reboot from the bootloop screen does the phone restart normally and even that takes three or four attempts. First I thought it was just getting used to the new Kernel then when this started occurring frequently I became more aware that this might just be a potential risk.
Today afternoon, My Phone was literally stuck at bootloop for 2 hours.... Only when I tried to do three-four manual forced reboots by pressing my power key and with each instance entering the TWRP mode and doing a dalvik and cache wipe only then was I able to boot up my phone normally.....It totally drained the battery though. I was at 78% and when my phone finally booted up I was shocked to see just 1% charge left.
Everytime this issue occurs...either the phone is completly stuck in bootloop or goes to the "Android is upgraing your apps" notification and then again comes back to the bootloop.
I have also done two fresh flashes before this as well so I know its got nothing to do with a dirty flash.
I then started googling for the same issue that other Zenfone 5 users might be experiencing but to my shock...No threads on it could be found with the issue that Im experiencing.
Pretty frustrated right now I have no clue what to do.
Donot want to go back to STOCK ROM..It sucks.
Please help Guys!
Thread closed / Duplicate
i installed cm 12.1 few months ago. recently with the regular nightly updates my phone got upgraded to marshmallow 6.0. from then i had a dialogue box appearing "google play services have stopped" constantly on my phone screen. so my friend advised me to flash the latest gapps for arm 6.0 pico and i did it. the phone now started showing "unfortunately setup wizard has stopped" persistantly. my frnd told me to flash cm13 along with gapps so i tried flashing them together but the process never ended. so i waited till the battery drained. i tried flashing the cm 13 alone and even that did not seem to end (not even for 30+ minutes!).. i waited for the battery to drain and now when i charge it i get a bootloader unlocked warning screen and nothing else.. i tried going to booot menu (vol dwn + pwr) but that got me to the same screen again.. help me plz.. and if there's anything i can do to save my device, provide me the download links too !! plzzz
rao141 said:
i installed cm 12.1 few months ago. recently with the regular nightly updates my phone got upgraded to marshmallow 6.0. from then i had a dialogue box appearing "google play services have stopped" constantly on my phone screen. so my friend advised me to flash the latest gapps for arm 6.0 pico and i did it. the phone now started showing "unfortunately setup wizard has stopped" persistantly. my frnd told me to flash cm13 along with gapps so i tried flashing them together but the process never ended. so i waited till the battery drained. i tried flashing the cm 13 alone and even that did not seem to end (not even for 30+ minutes!).. i waited for the battery to drain and now when i charge it i get a bootloader unlocked warning screen and nothing else.. i tried going to booot menu (vol dwn + pwr) but that got me to the same screen again.. help me plz.. and if there's anything i can do to save my device, provide me the download links too !! plzzz
Click to expand...
Click to collapse
Hello,
Are you able to boot to the recovery (TWRP)?
-Vatsal
Hi,
I have an XT1032.
1. In stock, locked bootloader, I let the OTA 5.0 and 5.1 updates run (so it's on 5.1's bootloader and radio now).
2. After a week, I realised I don't like 5.1, as GPS has issues for me in navigation apps.
3. I unlocked bootloader, installed TWRP and downgraded using the optimised 4.4.4 zip + NoMoto v004.zip.
4. Got scrolling lines at first boot, but no other problems for about 2 weeks. I LOVED 4.4.4 compared to 5.1, much better GPS performance!
5. After two weeks, my device went crazy: it went into a boot loop, where the boot logo kept appearing for 10 seconds, then launcher screen (pattern lock), then boot anim, then pattern lock etc. There was no way to power off the device, it always kept turning on.
6. I went into recovery and did a factory restore, it fixed it.
7. After I set up the phone again, in a few hours, I got the boot loop AGAIN.
----
8. After this I decided to install 5.1 optimised, which works perfectly.
However, as GPS is better on 4.4.4, I'd still like to go back to 4.4.4.
My questions:
1. What can be the crazy lockscreen - bootlogo - lockscreen - bootlogo loop?
2. How can I fix it (if I install 4.4.4 again)?
3. Is it related to having the bootloader from 5.1? The scrolling lines are not a problem but this boot loop is.
You love KitKat? Install my Slimkat! No more scrolling lines! http://forum.xda-developers.com/moto-g/development/slimkat-lollipop-bootloader-t3341258
Hi Guys,
Prelude : 2 months back, my pure stock Moto G experienced i guess a battery drain and refused to start the next time onwards. When it was powered on, it just got stuck on the M Logo of the bootup. After the help from @lost101 & others, i was able to flash the custom recovery & rom and got the phone to bootup atleast although faced the same issue which i'll be writing below now.
Since that event has happened, everytime I flash a custom rom, the installation happens without any glitch which includes the rom.zip & gapps_pico.zip. Now when the ROM bootups, the startup screen shows up after which it starts optimizing apps. That's where is the issue starts.
For eg. optimizing app x (single digit) of 101, it doesn't goes beyond that point even after waiting for 15-20 mins or so, and i've to manually reboot using the power button after which again the optimizing apps screen comes up and this time the figure is optimizing app xx of 16/17, and in this turn the phone successfully boots up to the setup screen and works as normal. But after a few moments when i'm done setting up all my apps and everything, random issues turn up for eg. the notification quick tiles won't drop down. And when i restart the handset, again it shows the optimizing apps screen, the phones boots up to home screen but random issues pertain.
I've tried ROM's like Stock Debloated (5.1.1) , CrDroid, CyanPOP, RessurectionRemix all based on 6.0.1.
Before installing any ROM, i do an advanced wipe and all format the data. Right now the handset is running CyanPOP but the main issue is i'm unable to access the notification dropdown. It doesn't goes beyond the header.
One more thing, I installed RR (xt1022 specfic) with same pico_gapps on my Moto E & the rom booted up in no time and working as smooth as butter till date with no issues whatsoever.
I'll be helpful if some one can diagnose the issue. Thanks
BBThumbHealer.
Did you try flash stock firmware and then flash a costum ROM ?
@Eurofighter_ty : when the issue first happened, what I remember is that I tried installing the debloated stock ROM of 5.1.1 and not the pure stock having all the unnecessary gapps. And similar issue was encountered. Same thing happened with other custom ROMs.
Today I've now reverted to a previous version of CrDroid 6.0.1 released in April and it at least runs fine when in use although a reboot causes the same issue. However, CrDroid June update and CyanPOP had the issue in which the quick tiles didn't drop down along with refusal of bootup.
Try to flash the stock ROM via fastboot with all files