Hi guys, I'm running the TugaPower rom, everything was fine until yesterday, I just woke up and it's stuck on the TugaPower logo, I've wiped cache and dalvik cache but the problem still continues..
Erdy232 said:
Hi guys, I'm running the TugaPower rom, everything was fine until yesterday, I just woke up and it's stuck on the TugaPower logo, I've wiped cache and dalvik cache but the problem still continues..
Click to expand...
Click to collapse
Strange.
What version you were on?
Mr.Ak said:
Strange.
What version you were on?
Click to expand...
Click to collapse
I was on N19. I just wiped system,data,dalvik and cache and flashed N22. Result = Bootloop
I re-wiped and flashed N19 now, Result = Stuck on TugaPower logo again...
Erdy232 said:
I was on N19. I just wiped system,data,dalvik and cache and flashed N22. Result = Bootloop
I re-wiped and flashed N19 now, Result = Stuck on TugaPower logo again...
Click to expand...
Click to collapse
For some reason,clean flashing N22 gives bootloop.
Now as you've flashed N19 try dirty flashing N22 on it i.e. Without wiping anything.
Mr.Ak said:
For some reason,clean flashing N22 gives bootloop.
Now as you've flashed N19 try dirty flashing N22 on it i.e. Without wiping anything.
Click to expand...
Click to collapse
That's what I did after re-installing the default recovery and OxygenOS, and now it works!
Erdy232 said:
That's what I did after re-installing the default recovery and OxygenOS, and now it works!
Click to expand...
Click to collapse
Then add "(fixed)" to the thread title.
Related
After flashing to Alpha 11.. My device cnt boot and just stucked at the cyanogenmod circle logo.. Help please.. I have never went through this situation before went flashing for alpha 1-10..
RaptorJD said:
After flashing to Alpha 11.. My device cnt boot and just stucked at the cyanogenmod circle logo.. Help please.. I have never went through this situation before went flashing for alpha 1-10..
Click to expand...
Click to collapse
It's bootloop. Try to go back to recovery mode and do full wipe (wipe data, cache, dalvik cache, and format system (optional)). And flash that ROM again.
CAUTION
It will delete all your installed app and data, so please do Nandroid backup first.
Click to expand...
Click to collapse
Good luck..
I don't really like posyting questions like this, but I was hoping to get CM11 installed on this device but it just won't boot. I've tried one of the unofficial nightlies, and the official M1 release. Is anyone else having this problem? It's just stuck at the bootlogo with the spinning arrow. Yes, I have wiped data, cache and dalvik. I flashed through CWM, too.
EDIT: Got it working by flashing with TWRP.
abtekk said:
I don't really like posyting questions like this, but I was hoping to get CM11 installed on this device but it just won't boot. I've tried one of the unofficial nightlies, and the official M1 release. Is anyone else having this problem? It's just stuck at the bootlogo with the spinning arrow. Yes, I have wiped data, cache and dalvik. I flashed through CWM, too.
EDIT: Got it working by flashing with TWRP.
Click to expand...
Click to collapse
Thanks for the update - i'm having issues with this as well.
I swithed from Dalvik to ART but com.process.ui interupted error appeare.
How can i switch again to dalvik if device not boot.
I've installed CM11 with ION [Dec 30, 2013] on Sensation XE
Boot into recovery and reflash your ROM.
shal3r said:
Boot into recovery and reflash your ROM.
Click to expand...
Click to collapse
I already try but always error.
I use nova launcher. It can generate this error?
Please explain what exactly you tried and what error you got.
I found reports in forums from other users who solved same issue by reflashing ROM or doing factory reset (wipe data) and then reflashing.
[Solved]
I flash 01/04 version and 50 kernel and then phone start correctly.
Runtime is stay switched to ART.
.
I wonder why reflash the ROM doesn't work but it can be worked by update...
DobbyDook said:
I flash 01/04 version and 50 kernel and then phone start correctly.
Runtime is stay switched to ART.
Click to expand...
Click to collapse
HI, change [Q][Solved] to [SOLVED]
thank i'll Download 50Kernel.
Have a nice weekend
Hi amigos,
Recently while in school, my phone randomly glitched out so I rebooted it. When rebooting, the phone would read "Android is starting". Then I tried wiping caches in TWRP but that didn't fix the problem. After I got home, I decided to dirty flash my ROM again (HalogenOS). Same problem. Then I tried a clean flash, and that resulted in the same problem. So then, after trying to restore multiple backups and flash many ROM's I got it to boot onto AOSP Oreo. So the phone is working fine, however, does anyone have a good reason behind this? I even wiped the entire phone but that didn't do anything either. I think it happens whenever I try a Lineage based ROM because Omni also booted fine. Any ideas? I want those sweet blobs in XOS
valvze said:
Hi amigos,
Recently while in school, my phone randomly glitched out so I rebooted it. When rebooting, the phone would read "Android is starting". Then I tried wiping caches in TWRP but that didn't fix the problem. After I got home, I decided to dirty flash my ROM again (HalogenOS). Same problem. Then I tried a clean flash, and that resulted in the same problem. So then, after trying to restore multiple backups and flash many ROM's I got it to boot onto AOSP Oreo. So the phone is working fine, however, does anyone have a good reason behind this? I even wiped the entire phone but that didn't do anything either. I think it happens whenever I try a Lineage based ROM because Omni also booted fine. Any ideas? I want those sweet blobs in XOS
Click to expand...
Click to collapse
Isn't "Android is starting" a normal process? Or was it just stuck there?
Which twrp you're using?
Did you flashed just the ROM or also the gapps?
It's stuck there. I'm using 3.1TWRP an yes I used gapps.
valvze said:
It's stuck there. I'm using 3.1TWRP an yes I used gapps.
Click to expand...
Click to collapse
Try flashing without gapps.
valvze said:
It's stuck there. I'm using 3.1TWRP an yes I used gapps.
Click to expand...
Click to collapse
Maybe you could try fastbooting cyanogen os and then try to flash twrp and lineage rooms again.
Mr.Ak said:
Try flashing without gapps.
Click to expand...
Click to collapse
Ok I'll try that, thanks
sethu surya teja said:
Maybe you could try fastbooting cyanogen os and then try to flash twrp and lineage rooms again.
Click to expand...
Click to collapse
Ok I'll try that as well, thanks
Had some time custom rom.
Yesterday flashed stock
Everythong was fine. Decided to go back to custom
Unlocked bootloader
Formatted data
Recovery reboot
Factory Reset
Flashed RROS
Step by step with instructions
So it isn't even show a bootanimation
Just stuck with black screen
What to do? I know i can go back to stock with dload, but i want custom
LOL
Just UPD
Installed for fun unstable AOSP 8.0 and it is worked
Strange
Installed RROS above and caught bootloop
All in all animation appeared
Rommco05 said:
maybe you should be before in emui and after again install RROS
Click to expand...
Click to collapse
nothing like this worked
Tried lot of times
Solved this problem by flashing vendor.zip from LOS Rom
lofik said:
nothing like this worked
Tried lot of times
Solved this problem by flashing vendor.zip from LOS Rom
Click to expand...
Click to collapse
The Reason Why You Had The Problem Is Because You Installed RROS 5.8.4 Instead Of 5.8.3. You Needed To Install RROS 5.8.3 First And THAN Flash RROS, 5.8.4.
I Had The Same Issue On RROS By Flashing 5.8.4 First.