So every time I have dirty flashed Euphoria OS, it has frozen at the Google boot screen. This has forced me to wipe system, install the rom, install gapps, and reconfigure settings. What am I doing wrong that can't I update normally without having to wipe system?
stynatu46 said:
So every time I have dirty flashed Euphoria OS, it has frozen at the Google boot screen. This has forced me to wipe system, install the rom, install gapps, and reconfigure settings. What am I doing wrong that can't I update normally without having to wipe system?
Click to expand...
Click to collapse
What works for me is to wipe cache and davlik before I dirty flash the Rom.
Then after flashing the Rom, SuperSu......... etc wipe cache and davlik again before rebooting.
I have never had any problems dirty flashing Euphoria with this method on both Nexus 5 and Nexus 4.
One more thing. I always make sure to have the latest TWRP installed before I attempt any dirty flash.
Latest version as of this post is TWRP 2.8.5.2
joegestes said:
What works for me is to wipe cache and davlik before I dirty flash the Rom.
Then after flashing the Rom, SuperSu......... etc wipe cache and davlik again before rebooting.
I have never had any problems dirty flashing Euphoria with this method on both Nexus 5 and Nexus 4.
Click to expand...
Click to collapse
I usually do both of those things. I will say that I used ROM Installer to update it, but then dirty flashed with twrp and it still didn't work. Maybe next week I should just straight out flash with TWRP first?
Okay I just did this today and the thing STILL happens. I'd flash the update, wipe dalvik/cache, then reboot system. Then it hangs on Google boot screen for at least 10 minutes. Then I go back to TWRP, wipe system, data, cache, and flash it again and then starts to work, but all my apps are gone. Why can't I just flash the update and have it done with it instead of constantly tinkering around? Am I doing something wrong? is this what a dirty flash is?
I noticed this in your Log
"<6>[ 0.514020] [email protected]: Power-off reason: Triggered from UVLO (Under Voltage Lock Out)"
Are you undervolting?
Ignore. Wrong thread.
Bump
stynatu46 said:
Okay I just did this today and the thing STILL happens. I'd flash the update, wipe dalvik/cache, then reboot system. Then it hangs on Google boot screen for at least 10 minutes. Then I go back to TWRP, wipe system, data, cache, and flash it again and then starts to work, but all my apps are gone. Why can't I just flash the update and have it done with it instead of constantly tinkering around? Am I doing something wrong? is this what a dirty flash is?
Click to expand...
Click to collapse
See if this helps.
If you have many apps, try waiting 10 minutes or longer after wiping cache/davlik before rebooting into android. Or you could try a double wipe.
Apparently, it can take quite a while for cache to clear even if TWRP shows complete.
joegestes said:
See if this helps.
If you have many apps, try waiting 10 minutes or longer after wiping cache/davlik before rebooting into android. Or you could try a double wipe.
Apparently, it can take quite a while for cache to clear even if TWRP shows complete.
Click to expand...
Click to collapse
I've tried this several times yesterday, I think I waited 20 minutes and rebooted again to do the same thing. I also don't have that many apps, I only have 4 rows filled in my app drawer
Okay everyone, I found the problem! All I had to do was uninstall the driver/app for CF.lumen before flashing because it tampered with the /system partition making it unable to boot. I then installed it again after the flash was done.
Related
So I haven't changed anything on my phone in a little while. Running CM 10.1 (from about a month ago) with no issues.
Today, my phone on my desk at work reboots. Ok, whatevs. Boot animation, CM animation, get to home screen, it says 'Loading Widget' then reboots. It's been doing this for about an hour now.
Any ideas of what to do, short of re-flashing? (which I realize isn't that bad, compared to problems that a lot of people have).
Thanks
If it isn't booting properly, I wouldn't think there's any other option apart from flashing again.
Sent from my Evita
Just dirty flash (wipe cache and Dalvik, then flash) and see if it boots. Or restore a nandroid, if you have it. Either would have taken about 5 minutes.
Of those fail, then full wipe and reflash.
redpoint73 said:
Just dirty flash (wipe cache and Dalvik, then flash) and see if it boots. Or restore a nandroid, if you have it. Either would have taken about 5 minutes.
Of those fail, then full wipe and reflash.
Click to expand...
Click to collapse
Managed to get it to reboot into bootloader, wiped cache and dalvik, and then it worked! (didn't flash anything).
No idea what broke it, but it's working now. Thanks for the responses
ok so here is what i have done and what has happened. so far google and the search box keep taking me to threads with similar problems but those fixes dont work or do not apply to me afaik.
so i started on cm11s stock rooted on the One. (bootloader is already unlocked)
checking the PA rom thread it said if you are flashing from cm11 make sure to flash to cm12 first, then flash gapps.
once that is working get into recovery mode (twrp in my case) clear cache and dalvik then flash PA rom
done that then ended up in an android apps loading bootloop. i have flashed GAPPS also but still remaining in the bootloop.
now if i go back to cm12 i can get to the homescreen and use it a little. but once i plug the usb cable in (connected to PC) it reboots. it also reboots randomly. i have since just wiped the entire phone. now once im on the homescreen i try to access the internal storage in windows and the device appears but does not show anything. i am trying to copy the PA rom zip and Gapps zip to the phone to try flashing again. since it has been crapping itself i have been using adb sideload to flash files.
so what am i missing, what have i forgot to do along the way?
cm11 to cm12 then PA as per instructed is giving me a bootloop (with wiping cache+dalvik when supposed to)
any help is appreciated,
cheers,
kanjo
kanjo said:
ok so here is what i have done and what has happened. so far google and the search box keep taking me to threads with similar problems but those fixes dont work or do not apply to me afaik.
so i started on cm11s stock rooted on the One. (bootloader is already unlocked)
checking the PA rom thread it said if you are flashing from cm11 make sure to flash to cm12 first, then flash gapps.
once that is working get into recovery mode (twrp in my case) clear cache and dalvik then flash PA rom
done that then ended up in an android apps loading bootloop. i have flashed GAPPS also but still remaining in the bootloop.
now if i go back to cm12 i can get to the homescreen and use it a little. but once i plug the usb cable in (connected to PC) it reboots. it also reboots randomly. i have since just wiped the entire phone. now once im on the homescreen i try to access the internal storage in windows and the device appears but does not show anything. i am trying to copy the PA rom zip and Gapps zip to the phone to try flashing again. since it has been crapping itself i have been using adb sideload to flash files.
so what am i missing, what have i forgot to do along the way?
cm11 to cm12 then PA as per instructed is giving me a bootloop (with wiping cache+dalvik when supposed to)
any help is appreciated,
cheers,
kanjo
Click to expand...
Click to collapse
The PA thread actually says to flash PA over the top of CM12 while only wiping cache and dalvik cache? No wiping system or data? I'd put money on that being the cause of your problems. The only reason to flash CM12 first is to have the proper updated firmware installed in preparation for PA. Leaving the system and data partitions intact before flashing a different ROM (PA over CM12) is asking for trouble.
Go into TWRP and perform a full wipe (system, data, cache, dalvik cache), then flash the PA zip and the gapps zip and reboot. Don't flash CM12 again because the firmware was updated the first time you flashed it.
EDIT: Exactly which thread are you getting these instructions from? Neither of the PA threads that I'm aware of contain those instructions.
Heisenberg said:
The PA thread actually says to flash PA over the top of CM12 while only wiping cache and dalvik cache? No wiping system or data? I'd put money on that being the cause of your problems. The only reason to flash CM12 first is to have the proper updated firmware installed in preparation for PA. Leaving the system and data partitions intact before flashing a different ROM (PA over CM12) is asking for trouble.
Go into TWRP and perform a full wipe (system, data, cache, dalvik cache), then flash the PA zip and the gapps zip and reboot. Don't flash CM12 again because the firmware was updated the first time you flashed it.
Click to expand...
Click to collapse
was coming back just now to update whats happening.
i finally got PA to boot. after many many fresh installs of cm12. one booted without a loop. i went back to twrp did a factory reset (wipe of dalvik and cache) (device was already freshly wiped of all data) had tried this many times but it finally booted.
now i have some weird things happening., ie. if i go into settings and enable or disable ADB the phone reboots... it didn't have that happen when i was on cm11. so not sure why it is happening now.
further if i install GAPPS i get a boot loop of android is upgrading. not sure why. the only boot that seems to work is when i run PA no gapps and no SUroot. any ideas why this is happening? or for how long the android is upgrading is meant to loop. ive seen some people say it is normal and could last 10 minutes. ive sat through multiple sessions of this some 1hour+ long. so not sure what is going wrong. i dont usually have much trouble flashing roms. this one is puzzling.
**edit**
forgot to add when it does boot. well when it did,. its now on a Android is upgrading loop after flashing GAPPS and enabling root......
anyway when it did boot the homescreen would show an error saying "settings has stopped" not sure why that is happening either.
kanjo said:
was coming back just now to update whats happening.
i finally got PA to boot. after many many fresh installs of cm12. one booted without a loop. i went back to twrp did a factory reset (wipe of dalvik and cache) (device was already freshly wiped of all data) had tried this many times but it finally booted.
now i have some weird things happening., ie. if i go into settings and enable or disable ADB the phone reboots... it didn't have that happen when i was on cm11. so not sure why it is happening now.
further if i install GAPPS i get a boot loop of android is upgrading. not sure why. the only boot that seems to work is when i run PA no gapps and no SUroot. any ideas why this is happening? or for how long the android is upgrading is meant to loop. ive seen some people say it is normal and could last 10 minutes. ive sat through multiple sessions of this some 1hour+ long. so not sure what is going wrong. i dont usually have much trouble flashing roms. this one is puzzling.
**edit**
forgot to add when it does boot. well when it did,. its now on a Android is upgrading loop after flashing GAPPS and enabling root......
anyway when it did boot the homescreen would show an error saying "settings has stopped" not sure why that is happening either.
Click to expand...
Click to collapse
Just to be clear, you've wiped system, data, cache, and dalvik cache directly before flashing PA? No CM flashes since wiping all of those partitions?
Also, which thread are you getting those install instructions from? Neither of the PA threads that I'm aware of contain those instructions.
ill try to clean up what has happened here;
have tried booting to twrp. wiped all data,
flashed PA
booted. with weird errors (settings has stopped and reboots on usb plugged in or adb turned off or on)
tried to flash gapps and enable root
now bootloop of android is upgrading.
going to go back to twrp. wipe all data and flash PA again without gapps and without root. will report back in about 10 minutes. will flash by using TWRP and ADB sideload.
do i need to reflash cm12 if i clear all data in twrp? i saw you mention above once i have flashed cm12 once it will have the need FW files to go to lolipop (in this case PA rom) at the moment i am trying to sideload PA rom after wiping data, system, cache and dalvik. is this why i am having the issue?
im dead tired so i admit i can be making mistakes though everything i have done seems to be what i am meant to do. flashed from cm11 to cm12, cleared all data, then flashed PA+gapps and root. = upgrading boot loop and errors mentioned above. tried flashing just PA and it booted with same errors, flashed gapps and errors.
all the files MD5s look good. not sure what is wrong.
--edit--
okay now i am at homescreen on PA.
when enabling/disabling adb in dev settings i get a reboot. is this normal now? does it need to reboot to mount the filesystem or something?
when it does boot after enabling adb i get "settings has stopped"
going to go to TWRP and flash GAPPS now and leave root not installed. will report back in a sec.
kanjo said:
ill try to clean up what has happened here;
have tried booting to twrp. wiped all data,
flashed PA
booted. with weird errors (settings has stopped and reboots on usb plugged in or adb turned off or on)
tried to flash gapps and enable root
now bootloop of android is upgrading.
Click to expand...
Click to collapse
Please define wiped all data.
kanjo said:
do i need to reflash cm12 if i clear all data in twrp? i saw you mention above once i have flashed cm12 once it will have the need FW files to go to lolipop (in this case PA rom)?
Click to expand...
Click to collapse
You only need to flash CM12 once, ever. The wipes don't remove the firmware.
Right now this is the exact (and only) process you need to follow:
1. Boot into TWRP.
2. Wipe system, cache, dalvik cache, and data.
3. Flash ROM + gapps together.
4. Reboot phone.
Heisenberg said:
Please define wiped all data.
You only need to flash CM12 once, ever. The wipes don't remove the firmware.
Right now this is the exact (and only) process you need to follow:
1. Boot into TWRP.
2. Wipe system, cache, dalvik cache, and data.
3. Flash ROM + gapps together.
4. Reboot phone.
Click to expand...
Click to collapse
this is what i am trying to do now. but when i flash PA and GAPPS i get android is upgrading x of xxx apps and reboot, repeat.
no idea why.
kanjo said:
this is what i am trying to do now. but when i flash PA and GAPPS i get android is upgrading x of xxx apps and reboot, repeat.
no idea why.
Click to expand...
Click to collapse
Not sure why that's happening of you're following the correct process. Maybe try with a different ROM.
Heisenberg said:
Not sure why that's happening of you're following the correct process. Maybe try with a different ROM.
Click to expand...
Click to collapse
balls, was hoping to us PA, haven't used it since my old s3 and figured it was the rom for me again. will have to check the rom comparison spreadsheet and look into others.
right now i have sideloaded PA alone. will copy PA and gapps to the internal storage to make things easier.
but it doesnt look like it is going to work for me.
going to try it once more like you said but locally rather than through sideload. though the internal storage is deciding when it does and doesnt want to show up.
TWRP
wipe system, cache, dalvik cache, and data.
and flash them both in tandem.
and for the fun of it when it asks if i want to install root i will let it go right ahead.
maybe this time it will work. if not then its a different rom for me. sadly.
okay so now **** got retarded. TWRP has been replaced by the stock cm11 recovery and i am too pissed off to think straight and cannot remember how to get this son of a ***** rooted again let alone to flash TWRP. i dont want to use any toolkits they all seem broken as hell.
can anyone point me in the right direction because ive just about lost my **** and this phone is going to meet my fist head on very shortly...
**edit**
done. after all this i am now on cm11 stock rooted ....seriously. hours upon hours, just to get back to where i started.
man i love when things go smoothly. anyway cheers for your help @Heisenberg . n
So it seems my lollipop custom hyperdrive rom has come down with a odd hangup suddenly where if I install a new app and then reboot it suddenly comes to a freezing halt after awhile, unless I go back and uninstall the most recently installed app's again and reboot. I've tried clearing dalvik and art cache and regular cache.... My question was what is clearing system, I know if I clear data I loose all my user installed app's info, is system the same thing but preinstalled app's when ya first boot up the rom and your defined choices in settings? What else am I able to do before trying a dirty flash or clean install altogether to get rid of this odd bug?
n1nj4Lo said:
So it seems my lollipop custom hyperdrive rom has come down with a odd hangup suddenly where if I install a new app and then reboot it suddenly comes to a freezing halt after awhile, unless I go back and uninstall the most recently installed app's again and reboot. I've tried clearing dalvik and art cache and regular cache.... My question was what is clearing system, I know if I clear data I loose all my user installed app's info, is system the same thing but preinstalled app's when ya first boot up the rom and your defined choices in settings? What else am I able to do before trying a dirty flash or clean install altogether to get rid of this odd bug?
Click to expand...
Click to collapse
Wiping system partiton would mean that you dont have an OS like in computer if you format the C drive(hypothetically), your pc wont boot up but your data(in hard drive D or E) would be there. Only wipe system from TWRP if you will subsequently flash another ROM. You could do a factory reset instead(goto TWRP click Wipe then Swipe To Factory Reset . If that doesnt solve your problem, flash a stock ROM or switch to a diff custom one.
Details first:
Oneplus One 64GB
Have never changed the kernel (so, stock? I think?)
TWRP 3.0.2.0
LineageOS 14.1 - "nightly" (weekly?) 2017-05-01
Phone is (was) encrypted
I'm not quite sure what to make of this:
Yesterday my phone wouldn't turn the screen on. I had received a notification, the notification light was flashing, and I had just used it, but double-tapping the screen or pressing the power button wouldn't turn the screen on. I wasn't overly worried, I've encountered bugs like this before, so I held the power button to restart the phone.
The OS wouldn't move past the boot animation.
The phone very happily booted into the recovery though.
Here's what I've attempted so far, in this order:
Wipe cache & dalvik cache.
Wipe cache, dalvik cache, and data.
Wipe cache, dalvik cache, data, and internal storage.
Restore nandroid backup
Fresh install of OS and Gapps
Fresh install of recovery in fastboot and then #5
Fresh install of a different OS (SlimRom 7.1.2 Beta 2017-04-21) and Gapps
Nothing is getting me back into Android, but as you can read, fastboot and recovery load up with no worries.
Does anyone have any idea as to what might be wrong? I'm about to load a new kernel on and see if that does anything, but I'm not holding my breath.
Any help would be greatly appreciated, thank you.
NoSyt15 said:
Details first:
Oneplus One 64GB
Have never changed the kernel (so, stock? I think?)
TWRP 3.0.2.0
LineageOS 14.1 - "nightly" (weekly?) 2017-05-01
Phone is (was) encrypted
I'm not quite sure what to make of this:
Yesterday my phone wouldn't turn the screen on. I had received a notification, the notification light was flashing, and I had just used it, but double-tapping the screen or pressing the power button wouldn't turn the screen on. I wasn't overly worried, I've encountered bugs like this before, so I held the power button to restart the phone.
The OS wouldn't move past the boot animation.
The phone very happily booted into the recovery though.
Here's what I've attempted so far, in this order:
Wipe cache & dalvik cache.
Wipe cache, dalvik cache, and data.
Wipe cache, dalvik cache, data, and internal storage.
Restore nandroid backup
Fresh install of OS and Gapps
Fresh install of recovery in fastboot and then #5
Fresh install of a different OS (SlimRom 7.1.2 Beta 2017-04-21) and Gapps
Nothing is getting me back into Android, but as you can read, fastboot and recovery load up with no worries.
Does anyone have any idea as to what might be wrong? I'm about to load a new kernel on and see if that does anything, but I'm not holding my breath.
Any help would be greatly appreciated, thank you.
Click to expand...
Click to collapse
Did you tried flashing stock Cyanogen Os through fastboot?
Mr.Ak said:
Did you tried flashing stock Cyanogen Os through fastboot?
Click to expand...
Click to collapse
No, but I tried flashing a different OS, so I wouldn't think that would work? Especially considering Cyanogen is gone and not supporting anymore.
Either way, I worked it out in the end!
I thought I'd tried everything, but turns out I hadn't: I didn't try formatting the phone. Doing so "removed" the previous encryption, which meant that with a fresh flash I could boot again. After that I restored my backup, re-encrypted, and I'm good to go!
So it must've been something wrong with the decryption/boot process(?)
Anyway, thanks for your help!
I installed cm12.1 rom for my samsung galaxy note 8 gt-n5110 and after i turned it on this was what happened. It constantly showed text boxes like "unfortunately, google app has stopped" and after i closed it another one showed up and now i cant control it anymore! I cant even finish the setup! What can i do?
Im new to these firmware stuff btw.
sunglassesman said:
I installed cm12.1 rom for my samsung galaxy note 8 gt-n5110 and after i turned it on this was what happened. It constantly showed text boxes like "unfortunately, google app has stopped" and after i closed it another one showed up and now i cant control it anymore! I cant even finish the setup! What can i do?
Im new to these firmware stuff btw.
Click to expand...
Click to collapse
Try a smaller Gapps package than the one that you flashed with the ROM. The package you used is probably too large to fit in the system partition along with the ROM.
Or, you didn't factory reset, wipe cache and wipe dalvik cache when you flashed the ROM. Failing to do those wipes will cause bugs due to the new system conflicting with the saved system data/settings from the previous system. In other words, data left over from the old ROM is causing problems with the new ROM.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Try a smaller Gapps package than the one that you flashed with the ROM. The package you used is probably too large to fit in the system partition along with the ROM.
Or, you didn't factory reset, wipe cache and wipe dalvik cache when you flashed the ROM. Failing to do those wipes will cause bugs due to the new system conflicting with the saved system data/settings from the previous system. In other words, data left over from the old ROM is causing problems with the new ROM.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Hey thanks for replying but it seems like i cant even finish the setup. Therefore i cant load any files into my device. Any suggestions?
sunglassesman said:
Hey thanks for replying but it seems like i cant even finish the setup. Therefore i cant load any files into my device. Any suggestions?
Click to expand...
Click to collapse
Boot back into recovery, then factory reset, wipe cache and wipe dalvik cache, then reboot.
If that doesn't work, try booting back into recovery then flash the ROM then the Gapps then factory reset, wipe cache and wipe dalvik cache then reboot.
If that doesn't work, try booting back into recovery, then select the "Wipe" option, then choose the "advanced wipes" option, then choose the system partition, then swipe the slider at the bottom to run the wipe, then try flashing just the ROM but don't flash the Gapps, factory reset, wipe cache and wipe dalvik cache then reboot. After you get the device booted, you can delete the Gapps file then download a smaller package and put it in your phone's internal storage then boot back into recovery and select the "Install" option, at this point, you already have the ROM installed so no need to flash it again, but you do need to flash the new Gapps file, then factory reset, wipe cache and wipe dalvik cache.
Do you see how important it is to factory reset, wipe cache and wipe dalvik cache every time you flash? It is a vital step.
Sent from my SM-S767VL using Tapatalk
Hey thanks for all these but my device is using cwm right now so can you pls rewrite the instructions for me?
Also i cant finish the setup with all these popups so theres no way i can load files into it.
And yeah i guess i didnt wipe data or caches away after i finished flashing the files.
Thank you so much.