So I was about to install the Louder mod for the nexus 4, but when I tried to go to recovery, it'd just be a gray screen. I tried going from the power menu, same gray screen. I tried going from when the phone is shut off, and it's still gray. Anyone know what I can do to get my CWM back?
mrjoeltan said:
So I was about to install the Louder mod for the nexus 4, but when I tried to go to recovery, it'd just be a gray screen. I tried going from the power menu, same gray screen. I tried going from when the phone is shut off, and it's still gray. Anyone know what I can do to get my CWM back?
Click to expand...
Click to collapse
I'd try deleting everything in /data/media/clockworkmod (after backing it up), or just rename it to clockworkmod.bak. There are a couple settings files in there that could be screwing it up. Or maybe a corrupted backup that exposes a bug in CWM. And some silly things to try: try clearing the cache, or reflashing CWM and clearing the cache.
fenstre said:
I'd try deleting everything in /data/media/clockworkmod (after backing it up), or just rename it to clockworkmod.bak. There are a couple settings files in there that could be screwing it up. Or maybe a corrupted backup that exposes a bug in CWM. And some silly things to try: try clearing the cache, or reflashing CWM and clearing the cache.
Click to expand...
Click to collapse
So nothing would happen to my phone if I just go in and delete CWM? and then I just can reflash it in?
EDIT: Nevermind, I just went into adb and reflashed the .img! Thanks for helping!
Related
I'm trying to flash to DamageControl. I've tried both 1.0 and 1.1v5 Beta. The same thing happens in both.
Basically, when I flash the update.zip my phone loads up then gets 2 force closes that cycle over each other. Rosie/sense never loads and I never see the desktop. I can hold the power button and shut down, though. Here are the 2 apps that keep FC'ing.
com.android
com.htc.launcher
I tried the UID fix in recovery and reformated my SD, deleted Ext, and tried the EXT fix in Recovery. I also deleted the cache via Fresh Kitchen. Still getting the same problem.
I'm flashing from a clean Hero. Basically, I made a nandroid back up of my hero before I touched anything on it. The only thing different from stock spring is that it was rooted.
Am I doing something wrong? Do I need to update from a different ROM?
Thanks in advance.
Did you wipe data and you may have to wipe your davilk cache as well
bcnice20 said:
Did you wipe data and you may have to wipe your davilk cache as well
Click to expand...
Click to collapse
I wiped the cache. Is there a tool to wipe data?
second option from the top in recovery mode...1.wipe data 2. wipe dalvik then reflash and you should be good to go
fatkitty420 said:
I wiped the cache. Is there a tool to wipe data?
Click to expand...
Click to collapse
LOL You obviously didnt wipe cache, otherwise you'd see data/factory reset in the same section.
obannvi said:
LOL You obviously didnt wipe cache, otherwise you'd see data/factory reset in the same section.
Click to expand...
Click to collapse
If you read my post I said I used Fresh's Kitchen Tools to clear the cache.
Edit: Prick.
yea man well instead of being cocky just channel that energy into the search bar cause you got alotta work to do if you cant flash a rom properly
Maybe you just got a bad download. Try redownloading the rom. Also, boot into recovery by turning your phone off, then hold home key + power til you get a black screen with green writing. Scroll down to wipe and then wipe each option in the next screen and try flashing again.
kbizzle said:
Maybe you just got a bad download. Try redownloading the rom. Also, boot into recovery by turning your phone off, then hold home key + power til you get a black screen with green writing. Scroll down to wipe and then wipe each option in the next screen and try flashing again.
Click to expand...
Click to collapse
Working on that now. Going back to my nandroid stock image first, then wiping everything, then flashing again.
kbizzle said:
Maybe you just got a bad download. Try redownloading the rom. Also, boot into recovery by turning your phone off, then hold home key + power til you get a black screen with green writing. Scroll down to wipe and then wipe each option in the next screen and try flashing again.
Click to expand...
Click to collapse
I tried both downloads but I'll re-download. Maybe my luck is that bad.
First question: I notice that a fair % of the time when I try to do a restore from CWM, it tells me there's a MD5 mismatch. Is this just a symptom of a bad SD card -- that the backup did not save properly to the card?
Since it's no good to find out the backup is bad when I actually need it, I came up with a work-around, which was to try and immediately restore from the backup immediately after making it. If it gives me an MD5 error, then I make a new backup. Eventually I don't get an MD5 error and the restore works, and in theory it should be restoring the phone to the state it was in just a few minutes earlier -- i.e. nothing is changed.
However, after a successful restore and reboot, I tend to get a slew of FC's at startup from background apps. I'm wondering what I'm doing wrong -- is there some extra step I need to do after a restore using CWM?
Sounds like when you backd up you had some data issues that are being restored too your phone each time you restore. Bite the bullett reflash your rom don't restore. But before you do that try fixing permissions in cwm.
I would clear cache and dalvik before doing the backup...
Sent from my SPH-D700 using XDA App
If you're using SRF, just reflash srf 1.1.1 right over it. It will repair your framework but save your personal data.
MD5 bmismatch is a result of renaming backups incorrectly or using ROM manager or Quick Boot to get into recovery. ONLY use 3 finger method.
Did not know that. You get a thanks.
I tried clearing cache and davik cache before backup. When I restored, it gave me a FC on Google framework or whatever that's called. I rebooted and did another restore from the same backup, then cleared cache and dalvik cache before rebooting, and that time it booted with no FC's.
kennyglass123 said:
MD5 bmismatch is a result of renaming backups incorrectly or using ROM manager or Quick Boot to get into recovery. ONLY use 3 finger method.
Click to expand...
Click to collapse
Is "quick boot" when you don't power-down and then power-up with 3-fingers, but just do the 4-finger reboot? That would make sense that it would be causing the MD5 problem... good to know. Is that also what's causing the FC's when I restore?
Nerva said:
I tried clearing cache and davik cache before backup. When I restored, it gave me a FC on Google framework or whatever that's called. I rebooted and did another restore from the same backup, then cleared cache and dalvik cache before rebooting, and that time it booted with no FC's.
Is "quick boot" when you don't power-down and then power-up with 3-fingers, but just do the 4-finger reboot? That would make sense that it would be causing the MD5 problem... good to know. Is that also what's causing the FC's when I restore?
Click to expand...
Click to collapse
if you arent properly shutting down you will almost always get FCs on reboot if you have a no journal rom...
Wow, I had no idea that was an issue (I'm quite new to Android and was thinking of the phone as being more like a digital watch than a personal computer). Will pulling the battery cause the same problems?
How do I fix the FC problems when that happens?
ummmm
Nerva said:
Wow, I had no idea that was an issue (I'm quite new to Android and was thinking of the phone as being more like a digital watch than a personal computer). Will pulling the battery cause the same problems?
How do I fix the FC problems when that happens?
Click to expand...
Click to collapse
that would be not shutting down properly like pulling the power cable out of your comp and turn it back on not goood to do alot wil be ok in light doses
Corrupt data is 100% the cause. The only problem now is trying to determine where the problem came from. It can be from many things, but to be safe, i'd reformat the SD card (backup all ur data first on a computer). And recreate a backup from the rom previously. I use "my backup root" from the market and it works like a charm when switching from rom to rom.
Sent from my SPH-D700 using XDA Premium App
yep
i use the very same thing........... i read that somewhere lol
Nerva said:
I tried clearing cache and davik cache before backup. When I restored, it gave me a FC on Google framework or whatever that's called. I rebooted and did another restore from the same backup, then cleared cache and dalvik cache before rebooting, and that time it booted with no FC's.
Is "quick boot" when you don't power-down and then power-up with 3-fingers, but just do the 4-finger reboot? That would make sense that it would be causing the MD5 problem... good to know. Is that also what's causing the FC's when I restore?
Click to expand...
Click to collapse
The 4 finger will cause corruption on ROMs without journaling, so yes. There is also a Quick Boot app that boots into recovery, same thing can happen. So for backups and restores, always power down then 3 finger into CWM.
I used Titanium Backup to uninstall certain packages (not before backing them up, of course) and it seems that I uninstalled too much... Whenever I start certain applications, the phone immediately blanks - and locks.
I have to press the power button 1-2 times before the screen unlock allows me to seep my finger. And it doesn't always succeed in retaining the screen: too often, it will immediately blank and lock again.
Example of applications that make the phone lock: Titanium Backup.
Example of applications that don't blank the phone: Dialer.
I started restoring some of the packages I uninstalled yesterday with the hope that this will fix the problem. So far I tried restoring:
- hiddenmenus
- sns
- Dialer 2.2.2
-setup wizard
- syncMLsvc
But without much success yet.
Any idea which service or package are responsible for correct behavior of the phone?
UPDATE 2: I gave up and decided to flash the EC07-Nuckin-1 ROM. I repeated the entire procedure detailed here and the phone boots fine, but the problem persists - in addition to the fact that the soft menu buttons now disappeared (replaced by faint color dots - LED-like).
How could this happen? Is it possible that my phone contracted an Android virus? (it appears that the problem started immediately after installing Stay Awake from the Android Market.
OK, this is becoming insane: I did a factory reset, re-installed ec07-clean, and not only the problem persists, the settings, home, back and search buttons no longer work!
Not to mention that my account details (and everything else) are still there, even after the factory reset...
And Market won't even start.
How is this possible?
What do I do to simply start from scratch, wiping out everything and all history (except for the SD card)?
verizonless said:
OK, this is becoming insane: I did a factory reset, re-installed ec07-clean, and not only the problem persists, the settings, home, back and search buttons no longer work!
Not to mention that my account details (and everything else) are still there, even after the factory reset...
How is this possible?
What do I do to simply start from scratch, wiping out everything and all history (except for the SD card)?
Click to expand...
Click to collapse
those softkey mod (led dots) are in the rom, look at what ur downloading/flashing first.
did u clear caches/dalvik??? clear them before u flash ec07clean and after and see buddy.
ciscogee said:
did u clear caches/dalvik??? clear them before u flash ec07clean
Click to expand...
Click to collapse
Of course I did.
ciscogee said:
and after
Click to expand...
Click to collapse
After, too? I didn't know that.
ciscogee said:
and see buddy.
Click to expand...
Click to collapse
Who is buddy?
ciscogee said:
those softkey mod (led dots) are in the rom, look at what ur downloading/flashing first.
Click to expand...
Click to collapse
OK, but they don't respond. Even with your ec07-clean.
Is there a way to do a real factory reset? Start all over again? This problem is driving me nuts.
Thank you ciscogee, you life saver.
Ur buddy lol.
I'm out and about right now. In joshkoss rom thread there is a dl17 stock rom. If u flollow that second post I believe u will achieve 2. 1 stock as in out the box and flash up from there
Sent from my SCH-I400 using xda premium
ciscogee said:
I'm out and about right now. In joshkoss rom thread there is a dl17 stock rom. If u flollow that second post I believe u will achieve 2. 1 stock as in out the box and flash up from there
Click to expand...
Click to collapse
I'm not really interested in 2.1. I just don't understand why a total re-install of ec07clean.zip + ec07.tar + update.zip won't restore everything to "brand new condition". Surely there is a way to tell the phone to "forget all history". But what is it?
In the meanwhile, I managed to make the Settings (leftmost) button work, by manually restoring SDM from Titanium Backup.
Android Market now starts. But the SCREEN OFF problem persists. I am now beginning to believe that Stay Awake actually caused a permanent damage.
verizonless said:
I'm not really interested in 2.1. I just don't understand why a total re-install of ec07clean.zip + ec07.tar + update.zip won't restore everything to "brand new condition". Surely there is a way to tell the phone to "forget all history". But what is it?
In the meanwhile, I managed to make the Settings (leftmost) button work, by manually restoring SDM from Titanium Backup.
Android Market now starts. But the SCREEN OFF problem persists. I am now beginning to believe that Stay Awake actually caused a permanent damage.
Click to expand...
Click to collapse
i understand, but see dl17 is the latest official samsung/verizon release, so what ever you erased will be brought back. the roms that are released here are leaks/hacked so they wouldnt be 100% until tweaked
ciscogee said:
i understand, but see dl17 is the latest official samsung/verizon release, so what ever you erased will be brought back. the roms that are released here are leaks/hacked so they wouldnt be 100% until tweaked
Click to expand...
Click to collapse
I understand that they aren't 100% and I am OK with that. All I want is bring the phone to that pristine state it was right after I upgraded it from DL17 to ec07clean.zip.
Is this possible at all?
I even tried the built in stock recovery 2e to do "factory restore". Didn't help.
Why doesn't it even delete my account information? This is weird.
Wipe all your data. Cache. Dalvik etc.
Sent from my SCH-I400 using xda premium
ciscogee said:
Wipe all your data. Cache. Dalvik etc.
Click to expand...
Click to collapse
I tried this at least 4 times. It doesn't get rid of anything. That's really puzzling.
In the meanwhile, I managed to restore my phone to a usable state (i.e. get rid of the original screen-off problem). Here is how I did it:
Settings > Display Settings > Power saving mode: UNCHECK (was checked)
Settings > Display Settings > Screen timeout: 1 minute (non was selected!)
I bet this was some remanent of that Stay Awake app.
Now, I lost quite a few productivity hours due to this. But at least now I know that this phone will always be mine, because in this particular phone, "Factory data reset" simply doesn't work.
Have you thought about using a different version of clockwork for flashing and wiping? That usually helps or perhaps stock recovery even
Sent from my DROIDX using xda premium
verizonless said:
I tried this at least 4 times. It doesn't get rid of anything. That's really puzzling.
...
But at least now I know that this phone will always be mine, because in this particular phone, "Factory data reset" simply doesn't work.
Click to expand...
Click to collapse
Mystery solved!
It turns out that it is the cyan wipe that doesn't work. The red wipe works.
Here is what I did:
Settings > Privacy > Factory data reset (Erases all data on phone) > Reset phone > Erase everything attempt:
Progressed as expected, then rebooted -- right into Android System recover <2e> (blue!):
Code:
Samsung Recovery Utils
- for BML -
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
___________________________________________
-- Wiping data...
Formatting FOTA:...
FOTA wipe failed.
Formatting DATA:...
Data wipe failed.
Formatting CACHE:...
Cache wipe failed.
Formatting DBDATA:...
Db data wipe failed.
E: Can't mount /dev/block/mmcblk0p3
(No such file or directy)
E: install_application_for_customer:Can't mount HIDDENSDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
copy application failed.
As you can see, there were clear error messages, so now I selected "apply sdcard:update.zip" ==> which brought me you into CwM Voodo Lagfix Recovery v2.5.1.x:
Code:
wipe data/factory reset
-- Wiping data...
Formatting DATA:...
Formatting DATADATA:...
Formatting CACHE:...
Formatting SDEXT:...
Formatting SDCARD:/:.android_secure...
Data wipe complete.
wipe cache partition
-- Wiping cache...
Formatting CACHE:...
Cache wipe complete.
Advanced > Wipe Dalvik Cache
Dalvik Cache wiped
Reboot system now
Phone looks now brand new.
Oh wait! I just examined the SD card and it contains all the old stuff. Nothing wiped, nothing formatted. And the Home button doesn't work. And the ticker-feed button reboots the phone... What's going on???
Edit: Looking into what you said
I have an encrypted n4 that I upgraded to lollipop.
Eveything went well but i cant get past the boot screen.
The dots just keep spinning.
I dont want to do factory reset. Have too much data that I dont want to lose.
Has anyone had any luck with resolving this issue other than doing a factory reset?
The first boot could take up to 6-8 minutes... else try to clear the cache
I've let it run for 8 hours and still stuck on boot screen.
Even rebooted and still the same.
How do I clear cache?
On boot press and hold the volume rocker to get into the bootloader. Then use the volume rocker and power button to select recovery, and wipe the cache with the stock recovery using the volume rocker and power button also. There should be video tutorials on YouTube also
NotBillable said:
I have an encrypted n4 that I upgraded to lollipop.
Eveything went well but i cant get past the boot screen.
The dots just keep spinning.
I dont want to do factory reset. Have too much data that I dont want to lose.
Has anyone had any luck with resolving this issue other than doing a factory reset?
Click to expand...
Click to collapse
NotBillable, were you able to solve this issue? I'm having the exact same problem, stuck on the spinning dots after upgrading to lollipop. I cleared the cache, it's been a few hours Anyone else have any other ideas (besides a factory reset)?
gouhst said:
NotBillable, were you able to solve this issue? I'm having the exact same problem, stuck on the spinning dots after upgrading to lollipop. I cleared the cache, it's been a few hours Anyone else have any other ideas (besides a factory reset)?
Click to expand...
Click to collapse
It should only take 10 minutes or so. You wiped /cache and it still did not work? A Factory Reset will probably fix your issue. Hope you made a Nandroid
I'm having the same problem but when I fastboot and try for recovery, I get a downed Android. Thoughts?
cnatalie said:
I'm having the same problem but when I fastboot and try for recovery, I get a downed Android. Thoughts?
Click to expand...
Click to collapse
I tried everything and nothing works except Android 4.4.4... I relocked bootloader, formatted everything, even erased all partitions, flashed via Factory Image, via OTA zip, via flashable zip... It used to work the first time I flashed Lollipop but the second time I ended up with the spinning dots for hours...
Maybe we should make a sticky thread for everyone having the same problem.
Flying f...... dosts
Hello guys,
I have the same problem. After I updated my Nexus 4 my system cannot load. It stucks only on boot screen with flying dots. I dont want to do wipe/erase data. What is wrong please? I tried wipe cashe, but nothing happend with this bug. I have so a lot of dirty words on this s....
ariesgodofwar said:
It should only take 10 minutes or so. You wiped /cache and it still did not work? A Factory Reset will probably fix your issue. Hope you made a Nandroid
Click to expand...
Click to collapse
yep, did wipe cache and it did not work. Had to factory reset. Didn't lose anything too important (e.g. photos and contacts backed up in the cloud), lesson learned though: back stuff up, esp. before before touching and upgrading the OS. Also used this as a chance to flash cyanogenmod
Solved it without a format! I had the same issue with my Nexus 5. I manually sideloaded the OTA zip via adb in Recovery mode and it rebooted ok. Hopefully that helps you guys too.
francobanman said:
Solved it without a format! I had the same issue with my Nexus 5. I manually sideloaded the OTA zip via adb in Recovery mode and it rebooted ok. Hopefully that helps you guys too.
Click to expand...
Click to collapse
Nice! Did you already have debug mode enabled to be able to use adb? Or am I missing something here (I'm a noob )
gouhst said:
Nice! Did you already have debug mode enabled to be able to use adb? Or am I missing something here (I'm a noob )
Click to expand...
Click to collapse
No, all you need to do is connect the phone to the computer, get into Recovery at startup, select to install a zip file. At this pount you need to run adb sideload from command and it should take care of itself. You have to rename the file to update.zip. For this to work you do need the right drivers. Let me know if you need further help.
Stucked on boot screen
If anyone helps.
I tried to install directly the 5.01 update from 4.4.2 on my Nexus 7 and was stucked on boot screen.
After several attempts I installed lollypop 5.0 and worked fine.
I'll try to install now the update from 5.0 and will tell you later if that works.
Cheers
Upgraded to 5 on my 2012 n7 and after getting it all set up i decided to wipe caches and fix permissions out of habit and now it just sits at the spinning circles. Left for a while. Tried rebooting.
Is this normal or justbad luck?
Thanks
tevil said:
Upgraded to 5 on my 2012 n7 and after getting it all set up i decided to wipe caches and fix permissions out of habit and now it just sits at the spinning circles. Left for a while. Tried rebooting.
Is this normal or justbad luck?
Thanks
Click to expand...
Click to collapse
no one?
Im reflashing, I let the thing sit there on the boot screen for an hour last night with no luck.
Are we not able to clear caches and fix permissions anymore?
I'm gonna go with just bad luck, although I'm not sure what you mean by fix permissions.
I cleared the cache from stock recovery right after sideloading the OTA, without even booting into Android, and had no such issues.
try flashing just lollipop boot.img, then if no luck flash system.img, and try booting up before you do these fixing permissions that you speak of.
Edit: Curiosity had me looking up fixing permissions. Seems like an outdated procedure that had been deemed more of a placebo and therefore unnecessary. From the ClockworkMod website:
fix permissions --
resets system
permissions back to
their default values
[this feature was
removed beginning
with version 6.0.3.5
due to its placebo
effect as a cure-all]
Click to expand...
Click to collapse