hi to everyone. I don't know if everybody has this problem I'm having but after installing xposed in lollipop I get a boot loop if I don't do a devilk-cache wiped. everything works well till I do a reboot then I need to do a wipe of devil-cache again. if anyone has a solution for this or do I need to wait for an updated version?
exactly the same here
yes every time need to wipe d-cache in order to reboot
is there any solution for this problem jet any information about it will be appreciated thanks
Same problem here, I just removed xposed. Will wait till there's a fix
Related
ok im stock with no nvflash backup need help with bootloop.
tried to clear cache rebooted, loop still there.
restored, loop still there.
reapplied latest update, loop still there(recover doesnt come up now just update indicator.).
help please.
thanks in advance for any assitance.
love this forum.
ps: have rma want to try to fix personaly first.
also will be installing vegan or cyanogen on it when fixed.
update
nv flashed and got it booting.
other threads helped alot
update:2
new update i can get it to boot but if i install anything it gets stuck.
Hey guys,
I have a Samsung GT-I9300 (International).
I rooted my phone in order to get cwm recovery.
I placed the CM10.1.zip and the gapps.zip on my extsdcard.
I access cwm and install both via the menu.
Then I did a factory reset ´cause everywhere is written i have to do it to get past the bootscreen.
But apparently it doesn't work.
I tried every possible way to get it up and running.
reset -> flash -> reset
reset -> flash
flash -> reset
flash...
I searched on Google for hours but nothing helped so far.
Hope you guys can helpme =)
arough
flashing
arough007 said:
Hey guys,
I have a Samsung GT-I9300 (International).
I rooted my phone in order to get cwm recovery.
I placed the CM10.1.zip and the gapps.zip on my extsdcard.
I access cwm and install both via the menu.
Then I did a factory reset ´cause everywhere is written i have to do it to get past the bootscreen.
But apparently it doesn't work.
I tried every possible way to get it up and running.
reset -> flash -> reset
reset -> flash
flash -> reset
flash...
I searched on Google for hours but nothing helped so far.
Hope you guys can helpme =)
arough
Click to expand...
Click to collapse
follow this guide step by step if problem still occurs contact me
1.Flash rom
2.Flash gapps (if isnt included to rom)
3.Wipe data&cache
4.Wipe cache
5.Wipe dalvik cache
6.Reboot (first start may take several minutes so be patient)
(its always possible that rom just isnt booting so try some other rom if this guide doesnt help)
press thanks if i helped
god damn it!
nothing works...
flashing kernel via Odin works 1 out of 10 times...
flashing rom works not at all
the whole day I'm trying to get CM on my phone -.-
I once flashed my kernel and everything worked perfectly, but no it just an enormous ****storm
and on top of it I freakin deleted my backup and now I can't even get back my old system
hell of a day
from where do I start flashing the rom if I do it a second time?
just "overflash" the old one or start from stock?
EDIT:// HOLY KAMOLY!
It justed worked! I just restarted it for the 42624726th time and now it works like a charm =)
I hope if I update it any time soon I don't have to pray to the almighty flying spaghetti-monster again
there shouldnt be any problem updating cyanogenmod just remember latest cyanogenmod is experimental and you should not flash any kernel anyway feel free to ask if your having problems
What recovery are you using?
Details help.
Hello! So as a lot of you may have heard, a lot of people are having problems with lollipop ROMs bootlooping on first boot and not starting up at all! So, I have the same issue. I have a t0ltetmo (Galaxy Note 2 on T-Mobile). And whenever I install a lollipop ROM with the gapps, it says "android is upgrading", and when that's done, it goes into an immediate endless bootloop! I can't get it to work at all! Any ideas? Thanks guys!
you can post your question here:http://forum.xda-developers.com/galaxy-note-2/help/qa-cyanogenmod-12-unofficial-t2976843
Thank you! I'll move this over there.
H4X0R46 said:
Hello! So as a lot of you may have heard, a lot of people are having problems with lollipop ROMs bootlooping on first boot and not starting up at all! So, I have the same issue. I have a t0ltetmo (Galaxy Note 2 on T-Mobile). And whenever I install a lollipop ROM with the gapps, it says "android is upgrading", and when that's done, it goes into an immediate endless bootloop! I can't get it to work at all! Any ideas? Thanks guys!
Click to expand...
Click to collapse
Try to boot device without gapps
Then if you device is started good, go into recovery, wipe cache and wipe dalvik cache. Then flash gapps.
I recommend you to download pico PA gapps. That is the smallest package. Only playstore and google play services, that is enougt. Try this.
Give feedback
Paget96 said:
Try to boot device without gapps
Then if you device is started good, go into recovery, wipe cache and wipe dalvik cache. Then flash gapps.
I recommend you to download pico PA gapps. That is the smallest package. Only playstore and google play services, that is enougt. Try this.
Give feedback
Click to expand...
Click to collapse
I haven't yet tried it with the PA gapps like you said, although I should also add that the ROM doesn't boot without gapps either! I even went as far as formatting my internal memory completely to rule out that it wasn't a file on the internal memory! Same thing, "android is upgrading" (which i've never seen a ROM do after installation) and then a bootloop.
EDIT: I have been using these lollipop gapps. https://s.basketbuild.com/gapps
Bump. Still haven't been able to get this working no matter what I try!
Sony Xperia Z2, locked bootloader, rooted SuperSU.
I was running MM but wanted to update my phone to latest Firmware .575 Marshmellow. Unfortunately, I made the rookie mistake of not making a backup because I was running low on space. Flashed, wiped cache/dalvik and then It went as far as home screen and then boot looped. I could only get into recovery TWRP.
Did a factory reset, clear cache/dalvik again. Nothing worked. Could only get as far as agreeing to terms screen and then boot loop.
Flashed an older firmware (.232) Lollipop that was pre rooted, same issue (don't know what I expected really)
Recovery is still there, I decided to just turn it off and ask someone because the internet is not giving me answers and I think I did enough damage. Please help!
Maybe too late, but..
What about when you wipe only cache and dalvik cache and flash again 575 zip and after that, flash bootloop fix, then restart phone to system from recovery menu?
Monipeev said:
Maybe too late, but..
What about when you wipe only cache and dalvik cache and flash again 575 zip and after that, flash bootloop fix, then restart phone to system from recovery menu?
Click to expand...
Click to collapse
I haven't tried the bootlop fix bit. I have tried this one though after going back to 570 and it still bootlooped. I'm back to 570 now.
Maybe a more stable flashable version will be revealed soon...one can only wait and see.
Hi there
I'm totally happy with this device but had an issue today for no apparent reason.
I was using it normally, I put it in my pocket (80% battery) and when I took it out, it was stuck on MI logo screen. Maybe screen wasn't properly blocked or something. But I find all the situation quite shocking since I normally set manual updates for system, and apps, playstore, etc.
I haven't done any flashing opperation recently since I'm not much into this kind of things nor installed any new app recenlty. However the phone was rooted (previos bootloader unlocking) quite a while ago by using "magisk method keeping stock recovery for OTA".
The phone is permanently on with MI logo on screen. I tried using power off button for a long time to see if I could turn it off but it didn't work.
I have access to Fast Boot and to Stock Recovery (3.0).
Is there any way to enter the system again without losing all data? If not, can I recover data before "flashing" anything or before using "wipe all data" option in recovery mode?
Thank you for any possible answer.
Reinstall twrp and boot into twrp from Command Window and Flash Lazy flasher you'll be booted into Your phone
notoriouslion said:
Reinstall twrp and boot into twrp from Command Window and Flash Lazy flasher you'll be booted into Your phone
Click to expand...
Click to collapse
Thanks a lot mate, with this small guidance and not much idea about this things I flashed lazyflasher, wiped cache and dalvik (couldn't with stock recovery) and reboot into system.
Just out of curiosity, by flashing this lazyflasher have I done permanent changes on the system, or just through the first immediate boot they disappear?
What do you think could cause a bootlop if not an update? May an app installed a while ago causing something like this?
xdaforo said:
Thanks a lot mate, with this small guidance and not much idea about this things I flashed lazyflasher, wiped cache and dalvik (couldn't with stock recovery) and reboot into system.
Just out of curiosity, by flashing this lazyflasher have I done permanent changes on the system, or just through the first immediate boot they disappear?
What do you think could cause a bootlop if not an update? May an app installed a while ago causing something like this?
Click to expand...
Click to collapse
It happens sometimes for Unknown reasons and Lazyflasher will not harm your device and I would suggest you to flash Another Rom
xdaforo said:
Thanks a lot mate, with this small guidance and not much idea about this things I flashed lazyflasher, wiped cache and dalvik (couldn't with stock recovery) and reboot into system.
Just out of curiosity, by flashing this lazyflasher have I done permanent changes on the system, or just through the first immediate boot they disappear?
What do you think could cause a bootlop if not an update? May an app installed a while ago causing something like this?
Click to expand...
Click to collapse
Did you run any root apps ? If /system changes you need Lazyflasher I think. You could alternatively reflash the ROM (without wiping data)