So, got the 4.4.2 update , downloaded it and then it asked for a reboot. I did reboot. I am completely stock , no root nothing. Now the update was installing but in the end I got error :/ the image was robot kinda looking like he had heart attack... anyways, it gave me 4 options, so i cliked volume button .. I don't know all the options but from the 2 of them, one was reboot and other was clear cache or something. I thought clearing cache may **** up something on phone so I tried scrolling back on the top.. but to my surprise from volume buttons phone didn't let me go up at all :/
I didn't had any choice but to choose clear cache.. I thought it may help. But it didn't... so I forced reboot it with power button hold for 10 seconds.. Now phone is working but no sim on it starts.. no signal whatsoever. If I try to open my gallery, it doesn't open. says "No storage, no external storage available" .. when I try to connect usb to phone and try to backup my pics and stuff from pc it doesn't open anything. PC does show "Internal memory" but there's nothing in it. My phone doesn't let me even use wifi. So I thought it was time to factory reset, but to my surprise when I click erase everything, it does nothing. So, I thought of rebooting and clicking "power+volume down" , still nothing.. it shows the same robot pic having heart attack... I doesn't have knowledge of root and stuff for now, I am a simple user of nexus 5 who is still on stock. Any help please? I am worried here now
Think you're gonna need to follow one of the guides to flash stock system again
Sent from my Nexus 5 using Tapatalk
nevermind. Working again.
What did you do to get it Woking I got mine in a box ready to RMA if you got a suggestions I'm open to try one more time beforrv I be without my phone for s long time
Sent from my Inspire 4G using Xparent Green Tapatalk 2
How did you get it working?? F**k mine has no signal at all too! Damn I am really pissed!
---------- Post added at 04:09 AM ---------- Previous post was at 03:59 AM ----------
I did a factory reset and its working now. What a headache Google!
Mistake 1: not allowing the phone adequate time to clear the cache when finished installing the ota. If you force the phone to restart during this process, it will corrupt your cache which causes all of those issues listed above (loss of signal, no baseband info, loss of access to mountable storage, etc).
Cache clearing takes considerably longer than on any other device I've owned prior to this phone, so messing with the phone during that important cache clearing process is the issue.
Mistake 2: reflashing the entire phone to stock. In the event you become impatient and decide to force your device to restart, you DONT HAVE TO revert to stock to get the phone working. What you have to do is restore functionality to the cache portion of the phone. All of your files are in fact still on the phone and accessible, you just have to unbreak your phone. You do this by procuring cache.IMG from the stock image of the phone (available on googles websites), and then you fastboot flash the file in the boot loader (look up adb commands to do this). Once this is done, reboot the phone and everything should be hunky dory after your applications cache is rebuilt and android boots.
Note: you might need to check for root again. Also if you corrupted your cache you will have to set all of your ringtones and notifications again because this cache corruption process unlinked the ability of yours apps that use notifications to "see" the sound files you have on your SD card.
Sent from my Nexus 5 using xda app-developers app
delete
What a savior ... wiped the cache again , gave adequate time this time and it booted again fine
I had the exact same problem! Cleared cache in recovery mode in 4.4.4 and then thought it stalled because it was running for 1 minute (which normally took 2 seconds in previous devices) so I forced a restart. Then I had all sorts of errors: couldn't connect with my SIM card, couldn't download our see my pictures, screen rotation but working, constant Google Playstore crash popups, and more.. I thought I'd bricked it. A few more attempts to clear cache in recovery mode, still took longer than 1 minute (also the same errors in my recovery mode like stated above: "E: failed to mount /cache" ... that sort of things)
A few days later I'd had it. My steps for the SOLUTION:
1. Cleared cache in my settings: settings -> storage -> cache (don't know if this has influenced the outcome but I did it).
2. Went back to recovery mode, errors still displaying, but tried again to clear cache. The only difference now was that I left it running without touching my Nexus 5 for about 10 MINUTES(!).
..........To my surprise it ended with "clearing cash complete" WOW! So I rebooted and everything worked fine again! The only thing was that I had to set some notification sound again. That wasn't too hard
Let me know if it helped in your case
xybur said:
Mistake 1: not allowing the phone adequate time to clear the cache when finished installing the ota. If you force the phone to restart during this process, it will corrupt your cache which causes all of those issues listed above (loss of signal, no baseband info, loss of access to mountable storage, etc).
Cache clearing takes considerably longer than on any other device I've owned prior to this phone, so messing with the phone during that important cache clearing process is the issue.
Mistake 2: reflashing the entire phone to stock. In the event you become impatient and decide to force your device to restart, you DONT HAVE TO revert to stock to get the phone working. What you have to do is restore functionality to the cache portion of the phone. All of your files are in fact still on the phone and accessible, you just have to unbreak your phone. You do this by procuring cache.IMG from the stock image of the phone (available on googles websites), and then you fastboot flash the file in the boot loader (look up adb commands to do this). Once this is done, reboot the phone and everything should be hunky dory after your applications cache is rebuilt and android boots.
Note: you might need to check for root again. Also if you corrupted your cache you will have to set all of your ringtones and notifications again because this cache corruption process unlinked the ability of yours apps that use notifications to "see" the sound files you have on your SD card.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I did that. The fastboot flash cache.img and still have the error...
Try flashing a stock rom, including the userdata.img file. Flash the userdata file last, right after flashing, boot into recovery and perform a factory reset.
. You do this by procuring cache.IMG from the stock image of the phone (available on googles websites),
where to get the cache.img from.
i have searched the folder of the stock rom after extraction,couldn't find one.
and my phone is soft bricked.
also its a asus zenfone 5(501 cg) with 4.4.2 not a nexus but with similar problem(rebooted phone without waiting for cache wipe to finish )
please reply asap
thanks
Related
hey all,
on friday I rooted my NS again to check out cm7 rc1. before i was totally stock @ 2.3.2. friday evening i wanted to show my iphone friends the nexus s with cm7. the first one took it and did take some photos. then he smiled and gave it back to me. force close: SORRY: Android.process(???) has stopped unexpectedly.
this error was looping all the thime. i pressed okay and one sec later it was there again. i tried to flash the rom again in recovery, but the error was still there. i did date and cash wipes and some factory resets and then the error was gone.
on sunday i was travelling home on train and suddenly the error was back. i tried again some wipes and then i deceided to restore my nandroid backup. so i was back on 2.3.2. during sunday afternoon and evening i got these errors:
- NS is freezing while it is in standby... if i grab the phone and want to unlock it but the display keeps black -> i have to put out the battery..
- NS is beside my keyboard and suddenly all four buttons are on. display is still black. unlock not possible--> battery again
- NS is freezing while using facebook or twitter app
today... i unrooted it again and went back to a nandroid (2.3.1) guided _here_.
after unrooted again NS wanted to update to 2.3.2 which i confirmed.
about to hours later the errors i explained came back.
am i the first one who bricked NS?
please give me some help how to get it back working correctly, because i love this phone so hard.
I did another factory reset and now the phone is hanging at the google Logo. The four buttons are powered.
This is looping, too.
Yesterday I tried some things to kill these errors. I did:
- factoy reset (in settings menu)
- fastboot erase userdata 2x
- wipe cache, wipe data, wipe devliak
Today the phone was with out a problem, but just a moment ago I wanted to unlock it by pressing the power button but the display didn't react as usal. It is still black and the only thing I can do is to take out the battery....
Last step I can do is to send it back to my girlfriends sister in US so that she can bringt it to Samsung US to get it serviced.
"bricking" the phones involves the phone not being able to turn on or do anything, period. your phone isnt a brick. after doing a "factory reset" you want to reflash whatever rom you are using. it seems like youre having problems with a bad app or some bad data.
thx simms22. i just flashed the newest cm7 nightly with rom manager (incl. wipe). i set up all my apps and 20 min later the error come.
to figure out if it is a bad app problem i do a factory reset now and won't log into google account and see if the error appears.
simms22 said:
it seems like youre having problems with a bad app or some bad data.
Click to expand...
Click to collapse
i did a factory reset and skipped google setup after first boot.
i just entered sim code and let nexus s in idel mode.. about 15 mins later the four buttons were lightened but i couldn't unlock the phone. battery out... and i could power it on.
so it's some kind of bad data problem? but how to find and/or clean this bad data? thx again for your help.
edit: I found a lot on google for "full wipe bad data". I'm reading now! But I may have to ask you something
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. then i mounted usb and copied this nandroid 2.3.1 to it and flashed it. I booted and installed system update 2.3.2. now testing again without apps.
edit3: the hole day no problems. I only installed twitter and in the evening 2.3.3 manually. This morning again the phone was not unlockable. I had to take out the battery... on my way to work I did a wipe from stock recovery but shortly later the phone freezed while I used the slider to unlock it. oh man that sucks I thought it was fixed.
I make some coffee now and start google'ing. If you have some tipps, please throw them to me.
maybe reflashing radio?
stiefa00 said:
i did a factory reset and skipped google setup after first boot.
i just entered sim code and let nexus s in idel mode.. about 15 mins later the four buttons were lightened but i couldn't unlock the phone. battery out... and i could power it on.
so it's some kind of bad data problem? but how to find and/or clean this bad data? thx again for your help.
edit: I found a lot on google for "full wipe bad data". I'm reading now! But I may have to ask you something
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. then i mounted usb and copied this nandroid 2.3.1 to it and flashed it. I booted and installed system update 2.3.2. now testing again without apps.
edit3: the hole day no problems. I only installed twitter and in the evening 2.3.3 manually. This morning again the phone was not unlockable. I had to take out the battery... on my way to work I did a wipe from stock recovery but shortly later the phone freezed while I used the slider to unlock it. oh man that sucks I thought it was fixed.
I make some coffee now and start google'ing. If you have some tipps, please throw them to me.
maybe reflashing radio?
Click to expand...
Click to collapse
are you using any of the custom kernels?
no, I'm using stock kernel and never flashed a custom kernel.
stiefa00 said:
no, I'm using stock kernel and never flashed a custom kernel.
Click to expand...
Click to collapse
im going to have you try wiping once again. wipe data/factory reset. only this time reupdate to android 2.3.3 right after the factory reset in recovery. dont boot after wiping, update after wipe, then reboot.
--> stock recovery -> wipe / factory reset -> reflashed update (ota2.3.3) -> testing now without installing apps
thanks simms!
Edit: the phone got a freeze while I wanted to unlock it -.-
Edit2: I'm testing now in airplane mode. Maybe the error doesn't come...
stiefa00 said:
--> stock recovery -> wipe / factory reset -> reflashed update (ota2.3.3) -> testing now without installing apps
thanks simms!
Edit: the phone got a freeze while I wanted to unlock it -.-
Edit2: I'm testing now in airplane mode. Maybe the error doesn't come...
Click to expand...
Click to collapse
im now thinking it might not software related. if it was software, a wipe and reupdate should have fixed it. maybe you should check into a warranty replacement. .
In airplane mode the error is there, too.
Okay thx 4 ur help. I'm starting a service request. Bad day -.-
Sent from my Nexus S using XDA App
stiefa00 said:
In airplane mode the error is there, too.
Okay thx 4 ur help. I'm starting a service request. Bad day -.-
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
the only other thing i can think of that might cause something like that after wiping is something bad on your "sd" storage. copy everything you need off your "sd" storage and try wiping that.
stiefa00 said:
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. Then nandroid restore...
Click to expand...
Click to collapse
I think I allready did this? Or do you talk about this 1gb sd. If so, how to format this one?
Could I find something usefull with logcat?
Sent from my Nexus S using XDA App
According to this thread I think you will have to get it replaced:
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=44db6d8e31129d4c&hl=en
Holy sh** what an anoying link. -.-
BUT: thanks dude.. now I know waaazzz up
Can anyone suggest a troubleshooting method without a factory reset. This is what I am experiencing:
Everytime I reboot the Sensation will boot up and go through the normal process. About 3 or 4 minutes it will just reboot. Often when this happens I note that I don't have to re-enter my pin (a clue?). This rebooting will go on repeatedly but eventually (if I leave the phone alone) I will at some point end up with the phone up and running.
There are no random reboots, it is only this situation that causes the problem and it's obviously some point 3 or 4 mins into the process that is causing the problem.
I've noticed that if I reboot to recovery and then select reboot from there it is usually successful.
I am s/off via wire trick method, and rooted. recovery is 4 ext and I am still on stock rom.
I'd like to find out what is happening at the point of the reboot, is there a good way to do this?
louiscar said:
Can anyone suggest a troubleshooting method without a factory reset. This is what I am experiencing:
Everytime I reboot the Sensation will boot up and go through the normal process. About 3 or 4 minutes it will just reboot. Often when this happens I note that I don't have to re-enter my pin (a clue?). This rebooting will go on repeatedly but eventually (if I leave the phone alone) I will at some point end up with the phone up and running.
There are no random reboots, it is only this situation that causes the problem and it's obviously some point 3 or 4 mins into the process that is causing the problem.
I've noticed that if I reboot to recovery and then select reboot from there it is usually successful.
I am s/off via wire trick method, and rooted. recovery is 4 ext and I am still on stock rom.
I'd like to find out what is happening at the point of the reboot, is there a good way to do this?
Click to expand...
Click to collapse
boot into recovery and wipe dalvik cache n then do a normal reboot n check wad happens
you can also make a nandroid backup n install a custom and check wheather the problem exisit by doing backup ull not loose ur data n u can return to stock again just by restoring the backup ... try and let me know
louiscar said:
Can anyone suggest a troubleshooting method without a factory reset. This is what I am experiencing:
Everytime I reboot the Sensation will boot up and go through the normal process. About 3 or 4 minutes it will just reboot. Often when this happens I note that I don't have to re-enter my pin (a clue?). This rebooting will go on repeatedly but eventually (if I leave the phone alone) I will at some point end up with the phone up and running.
There are no random reboots, it is only this situation that causes the problem and it's obviously some point 3 or 4 mins into the process that is causing the problem.
I've noticed that if I reboot to recovery and then select reboot from there it is usually successful.
I am s/off via wire trick method, and rooted. recovery is 4 ext and I am still on stock rom.
I'd like to find out what is happening at the point of the reboot, is there a good way to do this?
Click to expand...
Click to collapse
Hi,
Have you installed a new ROM recently?
Did you fully wipe the phone before you did this?
If not,try re-installing the ROM you are on.
No wipes.
You will not lose settings or data.
shrex said:
boot into recovery and wipe dalvik cache n then do a normal reboot n check wad happens
you can also make a nandroid backup n install a custom and check wheather the problem exisit by doing backup ull not loose ur data n u can return to stock again just by restoring the backup ... try and let me know
Click to expand...
Click to collapse
What I noticed is that the problem didn't exist when rebooting from ADB or fastboot either.
Anyway your suggestion so far looks promising. I've tried a normal restart from the phone and a battery change both of which would usually end up with the rebooting problem. Both of these tests haven't caused it so I'll keep testing but thanks for the suggestion.
What is does the Dalvik cache do and how would this have caused this kind of problem? I'm interested in the whys. The problem appeared soon after installing a couple of things as I remember and I did try to backtrack without much success.
malybru said:
Hi,
Have you installed a new ROM recently?
Did you fully wipe the phone before you did this?
If not,try re-installing the ROM you are on.
No wipes.
You will not lose settings or data.
Click to expand...
Click to collapse
No I've not installed any Roms, I'm on stock.
Revived thread - as it's happening again
I'd like to revive this thread - perhaps I should post a new one but since it's here ...
This problem has returned with a vengeance. It took me about 3 hours of fighting to get this phone to stop rebooting. It seems clearing the dalvik cache isn't a solution anymore (if it was in the first place).
What I've observed is that if I take the sd card out it doesn't reboot. When the card is in I have several shortcuts on one of my home screens which often will not refresh for ages (ie. android icons for anything moved to sd card). When the icons start to appear the reboot will happen shortly after. All the time I'm waiting for this to happen the phone is very sluggish.
I don't think this is an incompatible sd card but maybe it is, however, if I can get this to stop rebooting then all is ok till I attempt another reboot.
Ideally I'd like to track this down to find out if there is an app which is misbehaving. Are there any tools that can help me do that.
Any suggestions would be most welcome.
Backup all your data and do a factory reset
This problem might be due to 3rd party app as you phone without sd card dosent reboots
Might be some of ur app is seriously miss-behaving
After a factory rest install each app n check ( I know it's time consuming)
Hit thanks button if you find me helpful
sent from amazing HTC sensation using xda premium
shrex said:
Backup all your data and do a factory reset
This problem might be due to 3rd party app as you phone without sd card dosent reboots
Might be some of ur app is seriously miss-behaving
After a factory rest install each app n check ( I know it's time consuming)
Hit thanks button if you find me helpful
sent from amazing HTC sensation using xda premium
Click to expand...
Click to collapse
Yeah hoped to avoid that for 2 reasons. 1) It's a bummer 2) I won't know what the problem was / is.
I did do a factory reset after backing up data via my recovery. It seemed to be ok but I had nothing on SD at that point. I loaded a couple of apps and moved them to sd and it still didn't happen. The I restored the data and it was back to the same problem.
I may have to go with your suggestion but I'm going to lose some data as I can't back up selectively (so it seems).
Is there a logger I can use that starts at reboot. If I could find out exactly what it's doing when it decides to reboot I might nail the app?
louiscar said:
Yeah hoped to avoid that for 2 reasons. 1) It's a bummer 2) I won't know what the problem was / is.
I did do a factory reset after backing up data via my recovery. It seemed to be ok but I had nothing on SD at that point. I loaded a couple of apps and moved them to sd and it still didn't happen. The I restored the data and it was back to the same problem.
I may have to go with your suggestion but I'm going to lose some data as I can't back up selectively (so it seems).
Is there a logger I can use that starts at reboot. If I could find out exactly what it's doing when it decides to reboot I might nail the app?
Click to expand...
Click to collapse
hi
greetings
to find the problematic app might go tough you will have to install each and every app and check after that
try installing all the trustworthy apps before eg. file manager,fb,twitter,gmail etc then check once again ,after that install single app at a time
Hello there, I have a huge issue with my Motorola Xoom.
I ran the #156 TeamEOS 4.2 Nightly Rom for my European 3G Xoom when all of a sudden my tablet started acting really weird.
Apps were crashing, Google Play wasn't working, Browser as well, and so on.
I decided to do a hard reset, formatting cache, Dalvik Cache, Hard Reset...but nothing was cancelled. As soon as i rebooted my device, everything was back the way it was with the same issues. I noticed my tablet was costantly updating the same apps and even if I updated them the following reboot they were back re-updating themselves.
I have no idea what to do, I tried everything, including RSD Lite. Nothing.
Can somebody help me figuring out what to do and how to at least format my Xoom completely so that I can re-install my rom and then re-install the apps?
Thanks.
I would boot into recovery and do a full wipe the reflash the rom a gapps. you should be good to go.
No can do, sorry. What's weird is that even when I go to change the performance settings on the rom, to overclock it more or less, the changes are not recorded. I can set whatever I want but it doesn't change it. It's like the tablet is in a loop, always stuck doing the same things, charging the same rom, the same settings. I really don't know what to do, I don't want to throw it away but I don't know how to solve it.
Which xoom do you have? We can always flash the stock img with fastboot to restore it. It will be back to complete stock.
Can you get into recovery at all by powering off then press the power button wait till 3 sec's after the logo appears and press volume down. You will see android recovery at the top press vol up to select. If you can and you have a backup restore it. If you use an external sd card you can load a rom on to it and flash it in recovery.
"I decided to do a hard reset, formatting cache, Dalvik Cache, Hard Reset...but nothing was cancelled. As soon as i rebooted my device, everything was back the way it was with the same issues. I noticed my tablet was costantly updating the same apps and even if I updated them the following reboot they were back re-updating themselves."
this is the same exact problem i'm having. I cannot get my xoom to reset. It always goes back to where it was before.
danman1835 said:
"I decided to do a hard reset, formatting cache, Dalvik Cache, Hard Reset...but nothing was cancelled. As soon as i rebooted my device, everything was back the way it was with the same issues. I noticed my tablet was costantly updating the same apps and even if I updated them the following reboot they were back re-updating themselves."
this is the same exact problem i'm having. I cannot get my xoom to reset. It always goes back to where it was before.
Click to expand...
Click to collapse
Sounds like your data has gotten corrupted somehow. You can take the boot.img out of whatever Custom ROM ur using, and via terminal -
fastboot flash boot boot.img
fastboot reboot
I'm not using any custom roms. I'm using factory settings for almost everything.... also i don't know how to use terminal
Mjamocha said:
Sounds like your data has gotten corrupted somehow. You can take the boot.img out of whatever Custom ROM ur using, and via terminal -
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
I have the same problem.
The Xoom is a european with android 3.1 kernel version 2.6.36 and build H.6.3-25-9 <- this i dont understand but i think that is no correct.
I try flash the H.6.1-38-1_Retail_Europe version, all the process finish ok, but when i restart the tablet everything continues as before.
I not know what else to do, Heeeelp.
I'm trying to remove apps that's on this phone (GT-S7500) because some of the apps always force close and not working. Firstly, I tried uninstall the apps one by one, all went good until I rebooted the device, all of the apps are back again. Second, went to privacy>erase everything including SD card content, device rebooted and went straight to recovery. It was weird because normally it will reboot itself straight to home screen. So I select the option factory reset/wipe data, after that wipe cache partition and reboot. Device does not reboot but turned off completely (weird again) Turned it back on, and only saw that none of the apps were removed. Even the wallpaper are still the same. Next thing I do is manually boot into recovery menu and factory reset again, still the same thing, (device turned off without rebooting itself, turned it back on and everything was still the same) after few tries again, I finally decided to flash a stock rom with ODIN. Flashing was successful ODIN shows PASS, waiting device reboot but it shut off completely again. turned it back on, but nothing changes. wallpaper are still the same and every single downloaded apps were still there. Went to settings> about device only to found that it wasn't the same rom that I've flashed earlier using ODIN.(flashed 2-3 times again, results still the same) Very confused right now, suspected that the internal SD card was corrupted/damaged. Does anyone experiencing such thing on your galaxy ace plus? searched on xda forums and found that this issue was also happening on few other devices. This is not my phone, just helping a customer. Thank You.
After flashing stock rom
Go to recovery (stock of course)
Wipe data/factory reset
Wipe cache
Reboot
Sent from my Gt-S7500
Everything was going so well. I received my perfect phone a couple days ago...unlocked it, installed cwm 6.0.4.4, and rooted it. Kept it stock and only flashed franco and Drummerjed's volume boost. Life was swell.
I decided I wanted to try the Dalvik optimization mod and in preparation booted into recovery to make a nandroid. I always wipe the cache/dalvik cache before making nandroids because they're made faster when I do this. Never had an issue. This time, however, after clicking to wipe the cache partition the system seemed to freeze, which was weird because on my N4 it clears the cache in a matter of seconds. I held the power button down to reboot the phone and immediately knew something was wrong when I was greeted by 3 warning signs in the notification bar. I then discovered that I have no cell service. I am also unable to access internal storage.
I imagine that I'm going to have to flash the factory image and start over, but I'm wondering if there's any way to avoid that? I'm also wondering why this happened so I can avoid reproducing this in the future. Does cache wiping take considerably longer on the N5, and did I interrupt the process by rebooting the phone?
Thanks so much for your help.
I think you did interupt the process by rebooting the phone. Wiping dalvik/cache does seem to take a lot longer on this phone than on other devices (the only other device I have to compare to is the Nexus 7 though). I would say to just let it sit while it does it's thing next time.
I did have a problem with not having cell service once after wiping dalvik/cache though. I just rebooting into recover and wiped again and my cell service was back. Give that a shot and see what happens.
ramdyc said:
I think you did interupt the process by rebooting the phone. Wiping dalvik/cache does seem to take a lot longer on this phone than on other devices (the only other device I have to compare to is the Nexus 7 though). I would say to just let it sit while it does it's thing next time.
I did have a problem with not having cell service once after wiping dalvik/cache though. I just rebooting into recover and wiped again and my cell service was back. Give that a shot and see what happens.
Click to expand...
Click to collapse
Thanks, ramdyc, wiping again worked. After rebooting, everything was back to normal (seemingly). Cache wipe on my N5 takes waaayyy longer compared to what I'm used to on N4...just gotta be patient with it!
If you are using TWRP, go into the settings and enable rm -rf and it will wipe instantly. (or something like that - forgot teh exact setting name)
If anyone reads this and wiping it again DOESN'T work, you can flash the stock cache.img via fastboot and you'll be good to go.
Synyster06Gates said:
If you are using TWRP, go into the settings and enable rm -rf and it will wipe instantly. (or something like that - forgot teh exact setting name)
If anyone reads this and wiping it again DOESN'T work, you can flash the stock cache.img via fastboot and you'll be good to go.
Click to expand...
Click to collapse
I'm using cwm. I actually just flashed the recently released touch version of it and wiping cache with it took mere seconds like it does on my N4. Thanks for your help, guys!