Hey all,
So ever since I updated my OPO to Cm12.1, I've been having boot issues. Essentially, what happens is when booting the phone, the phone is forever stuck on the OnePlus Logo without going ahead to the Cyanogen Logo and then the phone starting up. The way I deal with this is, I boot up into stock recovery and then "Clear Cache Partition" and then I reboot a couple of times, and this works and has worked for me over the last couple of weeks. However, I wanted to know how can I get rid of this issue once and for all, so I'm able to boot the phone normally without having to clear the cache partition all the time.
Thanks
Did you wipe properly when updating?
I think so,do you think that's the reason I'm having issues?
What would you recommend to sort it all out?
dialsquare1886 said:
I think so,do you think that's the reason I'm having issues?
What would you recommend to sort it all out?
Click to expand...
Click to collapse
It's possible. I'd perform a full wipe (system, data, cache, dalvik cache) and flash again.
If you don't mind, could you share links that describe the easiest way to do all those things.
Thanks!
dialsquare1886 said:
If you don't mind, could you share links that describe the easiest way to do all those things.
Thanks!
Click to expand...
Click to collapse
Here's one I prepared earlier:
http://forum.xda-developers.com/showthread.php?t=2839471
Related
Ok bizarre problem guys. I have an international 6810 running Paranoid Android 2.13. I was browsing Facebook on Sunday morning via the app when the tablet rebooted mid scroll.
When it boots it gets right to the 'almost loaded' part of the boot animation where the brightness drops a little bit. However instead of booting to android (and if you've cleared dalvik cache the next thing you would see is the 'Upgrading - 1 of 200' messages there), it reboots and does this cycle endlessly.
I can get into bootloader and recovery (which is currently the first one I installed - CWM 5.5.0.4) and I can Wipe Cache fine, however as soon as try to Wipe Dalvik Cache the tablet reboots, which leads me to think there might be something wrong with the Dalvik Cache? This also (obviously) means I'm unable to do a Wipe Data/Factory Reset as that also attempts to wipe Dalvik Cache and causes a reboot.
I am able to flash roms (though I've only tried reflashing PA 2.13 so far and it will not boot with the same issue described above) and other zips successfully (i can run Aroma scripts without issue and have tried the emmc_scan_all_partitions_once.zip without problem (from a Galaxy Note thread and linked to in the 'How to avoid Superbrick' 7.7 thread)).
I'm looking at the 'Superbrick' thread wondering if I need to move my cache to another area but I'm loathe to do so if its something simple!
Anyone have any ideas?
FYI: After another day of searching I've found this post that appears to be having the same issue: http://forum.xda-developers.com/showpost.php?p=28533566&postcount=155
Gonna try that out and see what happens, will update after.
Uvaavu said:
FYI: After another day of searching I've found this post that appears to be having the same issue: http://forum.xda-developers.com/showpost.php?p=28533566&postcount=155
Gonna try that out and see what happens, will update after.
Click to expand...
Click to collapse
Ok what was described the thread linked above worked fine - seems I needed to overwrite /data to get rid of some sort of corruption. Everything back to normal now, on newest PA.
Uvaavu said:
Ok what was described the thread linked above worked fine - seems I needed to overwrite /data to get rid of some sort of corruption. Everything back to normal now, on newest PA.
Click to expand...
Click to collapse
I'm facing the same problem with mine. Stuck in bootloop until i wipe Dalvik Cache.
What exactly did you do to make it stop bootloop-ing?
So I bought a Nexus 5 off of craigslist for a pretty good price about a week ago and he had already rooted and installed a custom recovery onto the phone. He had some sort of rom that I didn't like so I decided to flash my own. So I downloaded cyanogen mod (the latest nightly build at the time) and flashed it along with g apps and rebooted the phone. When I it was turning on it said "upgrading apps xxx out of xxx." I was very confused because coming from a Nexus 4 and flashing many ROMs I have never seen this before. When the phone finally powered on it started giving me errors every 5 seconds and I realized soon after that I had my previous apps from the old rom still installed and everything else was in place. I managed to get into settings after clicking ok to errors every 5 seconds and saw that my ROM did indeed change to Cyanogen Mod. I decided to try to factory reset the phone through the settings menu and that fixed the phone seemingly until today. I tried installing another rom but this one is giving me multiple errors and then rebooting my phone. I could not get into the settings to factory reset the phone through there.
I was thinking that maybe the recovery was broken but I'm not sure of how to fix it. I tried to find a flashable recovery but only found IMG versions which I don't know how to install. Is there a possibility of any other issues? I am resetting/wiping cache/wiping dalvik cache every time in that order. When I'm installing the roms it says something about e:/ volume not existing or not being found could that be the problem? I don't recall ever seeing this on my nexus 5. If anyone knows how I could fix this issue I would greatly appreciate your help.
Thanks, Alex:laugh::laugh:
alexdzk said:
So I bought a Nexus 5 off of craigslist for a pretty good price about a week ago and he had already rooted and installed a custom recovery onto the phone. He had some sort of rom that I didn't like so I decided to flash my own. So I downloaded cyanogen mod (the latest nightly build at the time) and flashed it along with g apps and rebooted the phone. When I it was turning on it said "upgrading apps xxx out of xxx." I was very confused because coming from a Nexus 4 and flashing many ROMs I have never seen this before. When the phone finally powered on it started giving me errors every 5 seconds and I realized soon after that I had my previous apps from the old rom still installed and everything else was in place. I managed to get into settings after clicking ok to errors every 5 seconds and saw that my ROM did indeed change to Cyanogen Mod. I decided to try to factory reset the phone through the settings menu and that fixed the phone seemingly until today. I tried installing another rom but this one is giving me multiple errors and then rebooting my phone. I could not get into the settings to factory reset the phone through there.
I was thinking that maybe the recovery was broken but I'm not sure of how to fix it. I tried to find a flashable recovery but only found IMG versions which I don't know how to install. Is there a possibility of any other issues? I am resetting/wiping cache/wiping dalvik cache every time in that order. When I'm installing the roms it says something about e:/ volume not existing or not being found could that be the problem? I don't recall ever seeing this on my nexus 5. If anyone knows how I could fix this issue I would greatly appreciate your help.
Thanks, Alex:laugh::laugh:
Click to expand...
Click to collapse
Did you wipe data and cache before flashing the new rom?
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
I see your doing a clean install. I'd return it to stock and start over, especially considering you bought the phone used. Who knows what's been on it. See this http://forum.xda-developers.com/showthread.php?p=47156064
mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
jd1639 said:
I see your doing a clean install. I'd return it to stock and start over, especially considering you bought the phone used. Who knows what's been on it. See this http://forum.xda-developers.com/showthread.php?p=47156064
Click to expand...
Click to collapse
I'll try this then if it doesnt work ill try the factory reset/ relock whatever, thanks.
mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
no its CWM
You didn't wipe/factory reset.
Sent from my Nexus 5 using Tapatalk
mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
housry23 said:
You didn't wipe/factory reset.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, I did. I said it in my post.
alexdzk said:
Yes, I did. I said it in my post.
Click to expand...
Click to collapse
I see. Well, if you really did do a factory reset before flashing a new Rom, then maybe you have an old version recovery, or something is borked with your phones partitions. Honestly, buying a used one like that, I would do a full factory restore by flashing the stock images(sticky in general for directions) but don't relock the bootloader. This will erase everything and repartition the phone. Then install recovery and flash away.
Sent from my Nexus 5 using Tapatalk
housry23 said:
I see. Well, if you really did do a factory reset before flashing a new Rom, then maybe you have an old version recovery, or something is borked with your phones partitions. Honestly, buying a used one like that, I would do a full factory restore by flashing the stock images(sticky in general for directions) but don't relock the bootloader. This will erase everything and repartition the phone. Then install recovery and flash away.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I fixed the issue by flashing a new recovery through adb already and it works fine now thank you. I guess it was really my recovery that was broken.
alexdzk said:
I fixed the issue by flashing a new recovery through adb already and it works fine now thank you. I guess it was really my recovery that was broken.
Click to expand...
Click to collapse
Good. Glad you got it worked out. Was probably an old build of whatever recovery and because of the way KitKat changed things, there were a lot of problems wiping when the phone first came out. If you find any more good deals on your local Craigslist, PM me. I want a black n5 instead of my white one.
Sent from my Nexus 5 using Tapatalk
Hi, my first post ever.
I sadly say i think my Nexus 5 is dead, it stops in the google logo.
Today my screen had random touches all over it while I was using it, I mean it cannot be used, so i thought it could be the ROM, so I changed to CM11, the problem was still there. My decision was to Wipe all data, but i did not check well and I marked the wipe SYSTEM, now my phone can not start.
Any help..
JrT7 said:
Hi, my first post ever.
I sadly say i think my Nexus 5 is dead, it stops in the google logo.
Today my screen had random touches all over it while I was using it, I mean it cannot be used, so i thought it could be the ROM, so I changed to CM11, the problem was still there. My decision was to Wipe all data, but i did not check well and I marked the wipe SYSTEM, now my phone can not start.
Any help..
Click to expand...
Click to collapse
Try flashing the stock firmware from Google.
https://developers.google.com/android/nexus/images
JrT7 said:
Hi, my first post ever.
I sadly say i think my Nexus 5 is dead, it stops in the google logo.
Today my screen had random touches all over it while I was using it, I mean it cannot be used, so i thought it could be the ROM, so I changed to CM11, the problem was still there. My decision was to Wipe all data, but i did not check well and I marked the wipe SYSTEM, now my phone can not start.
Any help..
Click to expand...
Click to collapse
chill out.... if the google logo comes up the device is not messed up just flash stock and you will be good to go.
Use this link here
JrT7 said:
Hi, my first post ever.
I sadly say i think my Nexus 5 is dead, it stops in the google logo.
Today my screen had random touches all over it while I was using it, I mean it cannot be used, so i thought it could be the ROM, so I changed to CM11, the problem was still there. My decision was to Wipe all data, but i did not check well and I marked the wipe SYSTEM, now my phone can not start.
Any help..
Click to expand...
Click to collapse
flash the factory img via fastboot or adb push a rom to your phone(via adb while in recovery). i can't help you in how to do it, so search, its easy to find.
Thanks everybody, i am going to check all them.
Stock firmware helps!
Don't worry...
JrT7 said:
Hi, my first post ever.
I sadly say i think my Nexus 5 is dead, it stops in the google logo.
Today my screen had random touches all over it while I was using it, I mean it cannot be used, so i thought it could be the ROM, so I changed to CM11, the problem was still there. My decision was to Wipe all data, but i did not check well and I marked the wipe SYSTEM, now my phone can not start.
Any help..
Click to expand...
Click to collapse
If you haven't wiped your internal storage, try restoring a nandroid backup if you have any...
else follow this thread...
read carefully before starting..
http://forum.xda-developers.com/showpost.php?p=48605477&postcount=1
i dont use this forum as i have a different phone and i dont particularly want to sift through every thread to find an answer so i thought id ask to find out for myself
my partner owns a stock unrooted totally unmolestered original moto g running android lollipop and earlier today it started to lag and flashed up with an error she didnt have time to read, not long after it completely froze so i tried to turn it off and on again. after trying to turn it on again it has gone in to a bootloop and will not start properly.
any help on a solution would be much appreciated if anyone can help me ASAP.
cheers
Boot to recovery and try wiping cache. If that doesn't work, you may have to do a full wipe which means losing all files on the phone.
audit13 said:
Boot to recovery and try wiping cache. If that doesn't work, you may have to do a full wipe which means losing all files on the phone.
Click to expand...
Click to collapse
any guides on how to wipe the cache without rooting it? im assuming id have to use fastboot or adb or whatever but the internet hasnt exactly helped me with any solutions
Just wipe by booting into stock recovery.
http://www.android.gs/enter-recovery-mode-motorola-moto-g/
I have a nexus 5 on T-mobile running 5.1.1, every time I am on the phone whether it is a hangouts voice call or regular call it gets very hot around 150 F ... ive already tried booting into safe mode still does it...anyone know what I can do or why it does this??
Hardware is damaged
dicecuber said:
Hardware is damaged
Click to expand...
Click to collapse
I don't really understand how it could be hardware?
Android.is.better94 said:
I don't really understand how it could be hardware?
Click to expand...
Click to collapse
Can be as simple as a burned connection on a board. But finding it is another story.
Sent from my Nexus 5 using XDA Free mobile app
Full wipe and flash.
Full wipe.
Full wipe.
Full wipe.
NOT FACTORY RESET. FULL WIPE.
Hope that came across clearly. You might honestly have a "virus" on your phone. I had issues somewhat similar to this after installing a sketchy apk off google because I couldn't afford it at the time. A full wipe and reinstall of my ROM fixed the issue.
I am firmly convinced it was a bitcoin miner malware app or something along those lines.
I am not saying that is definitely the issue, but it can't hurt to try a full wipe and reflash at this point.
fwayfarer said:
Full wipe and flash.
Full wipe.
Full wipe.
Full wipe.
NOT FACTORY RESET. FULL WIPE.
Hope that came across clearly. You might honestly have a "virus" on your phone. I had issues somewhat similar to this after installing a sketchy apk off google because I couldn't afford it at the time. A full wipe and reinstall of my ROM fixed the issue.
I am firmly convinced it was a bitcoin miner malware app or something along those lines.
I am not saying that is definitely the issue, but it can't hurt to try a full wipe and reflash at this point.
Click to expand...
Click to collapse
Can you give an explaination of what you mean when you say "Full Wipe"? How do you achieve this?
Thanks
unlock, and install custom recovery twrp.
boot into recovery, and use the wipe -> reformat option. it will require you to type the word 'yes' before formatting the device if you are at the right screen.
be prepared to immediately flash a rom, as this will completely and entirely wipe the device. the device will not boot without flashing a rom after formatting.