Database Info

[Q] Boot loop?

Well i have been using the cm7 nightlies with no problem. Today i decided to flash the RC1 since im sick of having to flash everyday. So i flashed the rom with rom manager and my phone was stuck in a boot loop.
So i had to do a battery pull and then restore the rom i had just backed up. After restoring i reboot the phone and am stuck in a boot loop again. I did another battery pull did a full data wipe, wiped cache and dalvik cache. And reinstalled the nightly 41 and am no longer in a boot loop.
So i tried to install RC1 again and everything was fine after flashing rom and gapps. i thought everything was fine so i rebooted into recovery to flash the 1.2.2 BFS Netarchy kernel. Before flashing i wiped cache, and dalvik cache. And of course now im stuck into a boot loop again. Has anyone else experienced this problem? i believe i am doing everything right. This is the first time i have ever experienced this problem.

B2L said:
Well i have been using the cm7 nightlies with no problem. Today i decided to flash the RC1 since im sick of having to flash everyday. So i flashed the rom with rom manager and my phone was stuck in a boot loop.
So i had to do a battery pull and then restore the rom i had just backed up. After restoring i reboot the phone and am stuck in a boot loop again. I did another battery pull did a full data wipe, wiped cache and dalvik cache. And reinstalled the nightly 41 and am no longer in a boot loop.
So i tried to install RC1 again and everything was fine after flashing rom and gapps. i thought everything was fine so i rebooted into recovery to flash the 1.2.2 BFS Netarchy kernel. Before flashing i wiped cache, and dalvik cache. And of course now im stuck into a boot loop again. Has anyone else experienced this problem? i believe i am doing everything right. This is the first time i have ever experienced this problem.
Click to expand...
Click to collapse
try flashing the kernel without wiping the dalvik or cache.
personal, i dont use or recommend using rom manager, as it creates issues of its own. i download everything myself and flash in recovery without rom managers aid.

I'm trying that now. Thanks for the quick reply. I have even tried installing the rom without using rom manager and it still did the same thing to me. Hopefully this works.

Wifi Xoom Freezes on Team EOS Screen

I currently have a Wifi Xoom running EOS Wingray-62, and Gapps 10.5.
I have been on the nightly builds for awhile. The EOS ICS is great, and keeps getting better!!!!
Yesterday I turned my Xoom on and it got stuck at the Team EOS splash page.
I did a quick reboot, hoping this would fix the problem, but it didn't.
I can still get to ClockWorkMod, so I have done the following:
Wipe Data/Factory Reset
Wipe Cache Partition
Wipe Dalvik Cache
Still no luck....
Any idea's what I am doing wrong?

Kenar said:
I currently have a Wifi Xoom running EOS Wingray-62, and Gapps 10.5.
I have been on the nightly builds for awhile. The EOS ICS is great, and keeps getting better!!!!
Yesterday I turned my Xoom on and it got stuck at the Team EOS splash page.
I did a quick reboot, hoping this would fix the problem, but it didn't.
I can still get to ClockWorkMod, so I have done the following:
Wipe Data/Factory Reset
Wipe Cache Partition
Wipe Dalvik Cache
Still no luck....
Any idea's what I am doing wrong?
Click to expand...
Click to collapse
probably a bad download, restore a backup and redownload and try again

I checked to see if I had a bad download.
I downloaded the newest wifi nightly, and completed the following steps:
Wipe Data/Factory Reset
Wipe Cache Partition
Wipe Dalvik Cache
Loaded EOS-wingray-75.zip
Loaded GAPPS 10.5
I did get the new EOS splash screen in the lower right hand corner, but it just sits there.
Any ideas?

try to flash eos 1.0 wifi
Wipe Data/Factory Reset
Wipe Cache Partition
Wipe Dalvik Cache
flash eos 1.0 wifi
flash the gapps in the same cwm session!! then reboot
or try to flash an older version instead of 75
check md5 before flashing

Thanks for the reply....
I flashed an older version of the EOS nightly that had worked in the past.
The Xoom still didn't make it past the splash screen.
For fun, I also flashed CM9, and Bugless Beast for the Xoom Wifi. Still didn't make it past the splash screen.
Thanks for your help.

do you have anything important on your internal memory? If not, you could always try to "fastboot oem unlock" again, as that would clear your internal memory.
(For me, getting stuck at the boot-logo could always be fixed by wiping /data. With Tiamat recovery however, "wipe /data" will not really wipe /data as to conserve contents of /sdcard [which is linked to a folder beneath /data])
"fastboot erase userdata" might also do the trick, but I'm not positive on that one.

My Xoom is working again....
I was able to use the fastboot oem unlock command.
Thanks for all your help.

[Q] After Soft Brick, Device Won't Accept Rom Flashes

I've got a problem that seems to be unique. (Or maybe I'm just special...)
Short story:
-Compiled latest CyanogenMod for my phone, put CM zip and gapps zip on the device and went into recovery (CWM 6.0.2.3) to flash them.
-Wiped Data/Factory Reset, Wiped Cache, Wiped Dalvik Cache
-Flashed CyanogenMod and Gapps
-Rebooted
The device was obviously soft-bricked, so I followed these instructions to unbrick:
http://forum.xda-developers.com/showthread.php?t=1840030
This guide worked, and I was able to boot into TouchWiz.
Upon completion of that^ wonderful adventure, I embarked on a mission to get CyanogenMod back on my device.
I followed these instructions:
http://forum.xda-developers.com/showthread.php?t=1875914
...okay for the most part.
I used the command line utility to root the device, I used EZ-Unlock to unlock the bootloader, and I used RomManager to flash the rom.
Finally! I should work, right? Ya....no
I wiped data, caches, and the VM's cache, flashed and ended up with a soft-bricked device again. I went through all the steps 2 more times and I still can't flash! HELP??
P.S. I've tried other ROMs, Gapps, and I even flashed CWM Recovery to give it a shot.

Parrot mac said:
I've got a problem that seems to be unique. (Or maybe I'm just special...)
Short story:
-Compiled latest CyanogenMod for my phone, put CM zip and gapps zip on the device and went into recovery (CWM 6.0.2.3) to flash them.
-Wiped Data/Factory Reset, Wiped Cache, Wiped Dalvik Cache
-Flashed CyanogenMod and Gapps
-Rebooted
The device was obviously soft-bricked, so I followed these instructions to unbrick:
http://forum.xda-developers.com/showthread.php?t=1840030
This guide worked, and I was able to boot into TouchWiz.
Upon completion of that^ wonderful adventure, I embarked on a mission to get CyanogenMod back on my device.
I followed these instructions:
http://forum.xda-developers.com/showthread.php?t=1875914
...okay for the most part.
I used the command line utility to root the device, I used EZ-Unlock to unlock the bootloader, and I used RomManager to flash the rom.
Finally! I should work, right? Ya....no
I wiped data, caches, and the VM's cache, flashed and ended up with a soft-bricked device again. I went through all the steps 2 more times and I still can't flash! HELP??
P.S. I've tried other ROMs, Gapps, and I even flashed CWM Recovery to give it a shot.
Click to expand...
Click to collapse
Whatever happened to people just rebooting into recovery and flashing something else?
Sent from my SCH-I535 using xda app-developers app

Parrot mac said:
I've got a problem that seems to be unique. (Or maybe I'm just special...)
Short story:
-Compiled latest CyanogenMod for my phone, put CM zip and gapps zip on the device and went into recovery (CWM 6.0.2.3) to flash them.
-Wiped Data/Factory Reset, Wiped Cache, Wiped Dalvik Cache
-Flashed CyanogenMod and Gapps
-Rebooted
The device was obviously soft-bricked, so I followed these instructions to unbrick:
http://forum.xda-developers.com/showthread.php?t=1840030
This guide worked, and I was able to boot into TouchWiz.
Upon completion of that^ wonderful adventure, I embarked on a mission to get CyanogenMod back on my device.
I followed these instructions:
http://forum.xda-developers.com/showthread.php?t=1875914
...okay for the most part.
I used the command line utility to root the device, I used EZ-Unlock to unlock the bootloader, and I used RomManager to flash the rom.
Finally! I should work, right? Ya....no
I wiped data, caches, and the VM's cache, flashed and ended up with a soft-bricked device again. I went through all the steps 2 more times and I still can't flash! HELP??
P.S. I've tried other ROMs, Gapps, and I even flashed CWM Recovery to give it a shot.
Click to expand...
Click to collapse
You're special indeed. You are not following the directions put forth by the ROM developers in flashing their ROMs. Also some ROMs don't require you to flash Gapps as it is already part of the ROM. There is also a chance that you are flashing the wrong gapps. Give me a list of ROMs that you failed to flash that way I know for sure how to help.

prerequisites
which Cyanogenmod are you flashing? and by soft bricking, what were the symptoms? like could you get back to CWM? or TWRP?
Parrot mac said:
I've got a problem that seems to be unique. (Or maybe I'm just special...)
Short story:
-Compiled latest CyanogenMod for my phone, put CM zip and gapps zip on the device and went into recovery (CWM 6.0.2.3) to flash them.
-Wiped Data/Factory Reset, Wiped Cache, Wiped Dalvik Cache
-Flashed CyanogenMod and Gapps
-Rebooted
The device was obviously soft-bricked, so I followed these instructions to unbrick:
http://forum.xda-developers.com/showthread.php?t=1840030
This guide worked, and I was able to boot into TouchWiz.
Upon completion of that^ wonderful adventure, I embarked on a mission to get CyanogenMod back on my device.
I followed these instructions:
http://forum.xda-developers.com/showthread.php?t=1875914
...okay for the most part.
I used the command line utility to root the device, I used EZ-Unlock to unlock the bootloader, and I used RomManager to flash the rom.
Finally! I should work, right? Ya....no
I wiped data, caches, and the VM's cache, flashed and ended up with a soft-bricked device again. I went through all the steps 2 more times and I still can't flash! HELP??
P.S. I've tried other ROMs, Gapps, and I even flashed CWM Recovery to give it a shot.
Click to expand...
Click to collapse

jwattt said:
which Cyanogenmod are you flashing? and by soft bricking, what were the symptoms? like could you get back to CWM? or TWRP?
Click to expand...
Click to collapse
I have the same problem like OP does. Plus mine does not accept Jellybean OTA at all. I flashed liquid smooth and the phone shows samsung logo for half a second and shuts off.

ajrty33 said:
Whatever happened to people just rebooting into recovery and flashing something else?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
i feel u on that i seen cwm then rom manager....

Update/dirty flashing Euphoria OS freezes at the Google boot screen

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.

[Q] flashing from cm11 to 12 nightly then PA bootloop help needed

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