hey guys,
I was uninstalling some apps via Titanium Backup when the phone started acting weird (I must have uninstalled sth I should not). so I tried 'Factory Reset'. after the phone restarted, a black screen came up (no wallpaper), with the title 'set-up' at top and nothing else I could do with the phone. it recognizes the sim and has got reception.
I even tried 'wipe data' and 'wipe cache', still the same.
what should I do?
The thing is you deleted files from the system partition. A wipe will not restore these files.
I did the same thing. Had to flash a stock 2.51 sbf (the version i came from) then start again from scratch.
Flashd the JRDNEM_U3_2.59.0 (same as begining) w/rsd and it is up and running like the day first
thnx XDA & ephumuris
I think the problem we both encountered was we deleted some Moto/Blur setup file. So the system could go no further. I'm much more careful about what i remove now :lol:
yeah, you're right. i think it was BlurEmailEngine
Related
This is as little long, but I wanted to be as thorough as possible. I have loaded custom ROMs successfully in the past and I beileve I followed all the directions in the FAQs. Nevertheless, I could have missed something.. so here you go.
I installed the cyanogen7 RC2 release today. I installed it on a freshly wiped phone. I updated the incredible to the latest official update from verizon, rooted it with Unrevoked3 and then did a nandroid backup.
I rebooted, opened recovery and wiped the cache and then the phone. I installed the rom update-cm-7.0.0-RC2-Inc-signed via SD card. It said it was successful. After I restarted, the phone worked.
Next, I went into the rom manager and downloaded gapps. it asked me to reboot I said yet but declined to backup prior (as I already had the fresh verizon backup). It said it installed successfully.
Upon rebooting I hit the cyanogen load screen which cycles ~4 times.. After that the "welcome to adr6300" screen pops up where it tells you to click the droid in the middle of the screen. The screen is almost unresponsive. If I can get it to click, i advance to the next screen where it becomes completely unresponsive. Regardless of where I get on the setup page, after ~3 seconds it takes me back to the cyanogen load screen and this continues in an endless loop.
I tried clearing the cache and wiping the drive in recovery and reinstalling the rom but I still get that screen (which leads me to believe its an issue with gapps??). So I went ahead and cleared the cache, dalvik cache, wipe, and then restored my original official vwz rom.
I downloaded gapps-hdpi-20101114-signed from the CM6 stick this time and put in on my sd card (root). I got the phone back into recovery mode, and cleared both cache's (realized I missed this the first time) as well as wiped the phone. The CM7RC2 rom installed successfully and once again I was able to get into the rom.
I restarted after that success, booted into recovery, and flashed the gapps-hdpi-20101114-signed.zip file. It said it was successful and I rebooted. However... the phone still will not get past the CM7RC2 screen...
Do you know what I'm missing? I've tried to be as thorough as possible. When I first boot up the CM7RC2 rom, do I need to do something else prior to installing GAPPS? Do i need to install GAPPS immediately after CM7RC2 prior to booting the phone up at all?
edit: With the fresh vwz rom install, I did install a few apps (about 10) prior to backup as well as remove about 15 bloatware apps so I wouldn't have to re download or delete them if I flash back to the regular rom (re installed beautiful widgets, astro, titanium backup, etc. Removed vm, vzwnav, etc). I didn't open or input preferences in any of them.. but could this be causing the conflict? Should I hard reset the phone, get the OTAs all over again, root etc w zero apps?
Just realized I had the wrong version of gapps and not to get the ones from the sticky under the Dinc rom section.
I got the latest (and correct one) here:
at goo-inside.me/google-apps/
Not sure how I missed this before but I now have the correct one and its working.
Thanks anyway!
I'm using regular Clockworkmod 5.0.2.6 (not touch, which I've never tried).
I made a bunch of Nandroid backups of my phone. In the past I've restored to some of them and they worked. However, now, whenever I try restoring any of them from CWM, including the ones that worked before, it restores for a while and then it fails stating:
"Error while restoring /data!"
I searched on Google, and the only references I've found to this problem are from Galaxy Nexus owners. For them, just reflashing stock over Fastboot fixes it, so I reflashed stock 2.3.5 over Odin, but the problem remains.
I've also tried doing wipe data/factory reset from inside CWM and that didn't help.
Has anyone seen this before or have any ideas on how to fix this?!
I've discovered the log function under Advanced of CWM. This is what the log is ending with:
tar: can't remove old file data/system/packages.xml: Operation not permitted
#92997temp.dumpefs1.binefs2.binefs3.binS30edt_perms.logzipalign.log.cid.info.psm.info.mac.infoentropy.datbatterystats.binuiderrors.txtusage-20120304usage-20120305usage-20120229usage-20120301usage-20120302usage-20120303packages.xmlError while restoring /data!
Click to expand...
Click to collapse
I Googled around, and came up with this:
http://forum.xda-developers.com/showthread.php?t=1461658
Again, the Galaxy Nexus, with the same problem being this data/system/packages.xml file, and the same solution being Fastboot.
What the heck is going on? Is it possible for us to use Fastboot on our T989's?
manekineko said:
I'm using regular Clockworkmod 5.0.2.6 (not touch, which I've never tried).
I made a bunch of Nandroid backups of my phone. In the past I've restored to some of them and they worked. However, now, whenever I try restoring any of them from CWM, including the ones that worked before, it restores for a while and then it fails stating:
"Error while restoring /data!"
I searched on Google, and the only references I've found to this problem are from Galaxy Nexus owners. For them, just reflashing stock over Fastboot fixes it, so I reflashed stock 2.3.5 over Odin, but the problem remains.
I've also tried doing wipe data/factory reset from inside CWM and that didn't help.
Has anyone seen this before or have any ideas on how to fix this?!
Click to expand...
Click to collapse
You're not alone my friend and I know how to fix it, albiet temporarily, although I haven't actually had the issue in quite some time.
Do a full wipe and clean install of your favourite rom. Once it boots and you let it settle for a few minutes reboot recovery and restore your backup. I have done this method about 12-15 times. The error restoring was accompanied by the inability to reboot my phone at all without having a complete meltdown of every app force closing. It was after the first "bad reboot" I had that I got the error while trying to restore a backup. Hopefully you don't have o go through that. It sucked big time to say the least. Hope this helps
»»DARKSIDE««
raycaster3 said:
You're not alone my friend and I know how to fix it, albiet temporarily, although I haven't actually had the issue in quite some time.
Do a full wipe and clean install of your favourite rom. Once it boots and you let it settle for a few minutes reboot recovery and restore your backup. I have done this method about 12-15 times. The error restoring was accompanied by the inability to reboot my phone at all without having a complete meltdown of every app force closing. It was after the first "bad reboot" I had that I got the error while trying to restore a backup. Hopefully you don't have o go through that. It sucked big time to say the least. Hope this helps
»»DARKSIDE««
Click to expand...
Click to collapse
Fixed it, just as you were typing up your response. (Thanks for the tip nonetheless!)
I just ran Darkside Super Wipe on my phone, and after that my restore proceeded perfectly.
I wonder if that's really the key. I don't suppose your favorite ROM is Darkside Digital Warfare, which has Darkside Super Wipe built-in?
manekineko said:
Fixed it, just as you were typing up your response. (Thanks for the tip nonetheless!)
I just ran Darkside Super Wipe on my phone, and after that my restore proceeded perfectly.
I wonder if that's really the key. I don't suppose your favorite ROM is Darkside Digital Warfare, which has Darkside Super Wipe built-in?
Click to expand...
Click to collapse
Of course it is lol.
»»DARKSIDE««
Thanks for the fix, same thing happened to me. I had the Optimus T before this so I whent flash happy 12 hours after I unboxed this beautiful phone. I've only had this phone a week, you saved my life lol.
this is just now happening to me, this threat is old but very help full lol
Hey all,
not trying to rehash a "solved" thread but Im having this issue and then some.
First, I tried Darksides wipe script and tried to restore the boot and install a new rom, then install the backup, all to no avail. I tried everything. When you get this error, it seems (at least from my experience) that your only hope is to restore from the stock 4.02 google image and then restore from the nandroid. This first happened to me when my phone dropped and off the couch and the battery came out. It seemed to have corrupted the sdcard, or, at least that was my guess.
However, upon redoing everything to stock and restoring the nandroid (even upgrading to the latest ver of clockworkmod recovery), the problem comes back. Im worried about permeneant damage, possibly, but it makes no sense that I would be able to revert to stock and have it working fine. When I reverted and restored from my nandroid, everything worked flawlessly. Then, today, I turned off my phone (which is a rarity, if ever) and it wouldnt boot back up a few minutes later. Bootlooop and the dreaded "error while restoring data!" message. Im going to revert to stock again and start completely from zip, no nandroid. Its possible that the nandroid is corrupted I suppose but i dont believe it would let me restore it than. Any ideas? Could this be from me leaving my phone on practically all the time, without ever turning it off? or the battery coming out while in use? (which makes sense in theory but I've done a battery pull countless times and never had a problem like this). Would there be a way I could determine, for sure if its a hardware problem? Verizon Nexus (hardware ver 9 I believe) now running JB Sourcery 2.0 (from team sourcery...an AWESOME rom, so I dont believe it to be that.)
Cheers!
raycaster3 said:
You're not alone my friend and I know how to fix it, albiet temporarily, although I haven't actually had the issue in quite some time.
Do a full wipe and clean install of your favourite rom. Once it boots and you let it settle for a few minutes reboot recovery and restore your backup. I have done this method about 12-15 times. The error restoring was accompanied by the inability to reboot my phone at all without having a complete meltdown of every app force closing. It was after the first "bad reboot" I had that I got the error while trying to restore a backup. Hopefully you don't have o go through that. It sucked big time to say the least. Hope this helps
»»DARKSIDE««
Click to expand...
Click to collapse
Wow thanks so much for this! Just happened to me on my note 2 and after doing some googling I came across this post and it worked perfectly, first try. thanks again!
i had this problem now.. my hearth stopped to work.. but this guide helped me ! thanx ! so it is working in year 2014 too
raycaster3 said:
You're not alone my friend and I know how to fix it, albiet temporarily, although I haven't actually had the issue in quite some time.
Do a full wipe and clean install of your favourite rom. Once it boots and you let it settle for a few minutes reboot recovery and restore your backup. I have done this method about 12-15 times. The error restoring was accompanied by the inability to reboot my phone at all without having a complete meltdown of every app force closing. It was after the first "bad reboot" I had that I got the error while trying to restore a backup. Hopefully you don't have o go through that. It sucked big time to say the least. Hope this helps
»»DARKSIDE««
Click to expand...
Click to collapse
plz help me :crying: i am new to this here is my situation i hav a galaxy s4 i9500 i rooted my device 2 days ago and i backed up during the back up it showed no .android_secure found. skipping backup of applications on external storage andalso root error fix . i google it and found its not a big deal so i factory formatted it but when it restored it and restored it all the applications started showing error msg so i formatted sd card and replaced backup folder and tried to back up it showed md5 mismatch so i editted nanroid.md5 with notepad++ and tried to reboot again now its showing recovery data error . what to do?
So on Wednesday, I woke up to find all blank screens on my droid incredible. No apps, no widgets, etc. Thought this was odd. Rebooted, and they all came back. Then, came the error/force close messages. For everything. My contacts would randomly disappear, everything would just crash etc.
Went to clockwork (most recent version, whatever it is) to try to wipe the dalvik cache, regular cache, and fix permissions. Dalvik and permission fix went fine. When I tried to format the cache I got an "error formatting cache" message.
Over the last couple days, I noticed other strange problems. App updates wouldn't install properly, Every time I would reboot my phone, all my text messages from tuesday on would disappear (including any I have sent since a reboot). Apps I tried to uninstall would magically reappear on reboots. It seems that every time I rebooted my phone, it would revert back to this state prior to whatever went wrong with it.
This morning, I got a strange "UID Inconsistencies" message and telling me to wipe the phone data. My Only choice was to select a button that said "I'm Feeling Lucky"
I said screw it, I'll just backup what I need and wipe it.
Tried to do a data wipe via CW and.......when I rebooted it was like I never did. All the apps I had uninstalled were present, same issues (though slightly less prevelent), it was like I never did a factory reset at all.
I am really confused by this. I installed NO new apps prior to this, was not doing anything fancy on my phone. I rooted my phone last fall sometime, and have Touch of Blue 2.0 Rom installed. My only purpose for rooting and flashing this rom was to get rid of the dreaded "memory low" errors that plague the Incredible. I didn't experiment with anything so I am unclear how this problem arose or how to fix it. My phone basically works, but it's like the state of the phone continually reverts back to sometime between Monday and Wednesday of this week every time I reboot, no matter what I do to it, along with a slew of crazy errors that makes it extremely frustrating.
Hoping for some help. Thank you.
w0j07 said:
So on Wednesday, I woke up to find all blank screens on my droid incredible. No apps, no widgets, etc. Thought this was odd. Rebooted, and they all came back. Then, came the error/force close messages. For everything. My contacts would randomly disappear, everything would just crash etc.
Went to clockwork (most recent version, whatever it is) to try to wipe the dalvik cache, regular cache, and fix permissions. Dalvik and permission fix went fine. When I tried to format the cache I got an "error formatting cache" message.
Over the last couple days, I noticed other strange problems. App updates wouldn't install properly, Every time I would reboot my phone, all my text messages from tuesday on would disappear (including any I have sent since a reboot). Apps I tried to uninstall would magically reappear on reboots. It seems that every time I rebooted my phone, it would revert back to this state prior to whatever went wrong with it.
This morning, I got a strange "UID Inconsistencies" message and telling me to wipe the phone data. My Only choice was to select a button that said "I'm Feeling Lucky"
I said screw it, I'll just backup what I need and wipe it.
Tried to do a data wipe via CW and.......when I rebooted it was like I never did. All the apps I had uninstalled were present, same issues (though slightly less prevelent), it was like I never did a factory reset at all.
I am really confused by this. I installed NO new apps prior to this, was not doing anything fancy on my phone. I rooted my phone last fall sometime, and have Touch of Blue 2.0 Rom installed. My only purpose for rooting and flashing this rom was to get rid of the dreaded "memory low" errors that plague the Incredible. I didn't experiment with anything so I am unclear how this problem arose or how to fix it. My phone basically works, but it's like the state of the phone continually reverts back to sometime between Monday and Wednesday of this week every time I reboot, no matter what I do to it, along with a slew of crazy errors that makes it extremely frustrating.
Hoping for some help. Thank you.
Click to expand...
Click to collapse
Are you s-off, bootloader unkocked, or both? Have you tried reflashing recovery?
cmlusco said:
Are you s-off, bootloader unkocked, or both? Have you tried reflashing recovery?
Click to expand...
Click to collapse
s is on, because it seemed like too much effort to downgrade/turn it off than it was worth since my reasons for rooting didn't require it. I'm not sure what you mean by the bootloader being unlocked so probably not, and no I have not tried reflashing recovery. Will try that now.
w0j07 said:
s is on, because it seemed like too much effort to downgrade/turn it off than it was worth since my reasons for rooting didn't require it. I'm not sure what you mean by the bootloader being unlocked so probably not, and no I have not tried reflashing recovery. Will try that now.
Click to expand...
Click to collapse
Well if you have a custom recovery and have flashed a rom, then you have to be unlocked. Use fastboot and type without quotes "fastboot erase recovery " and then " fastboot flash recovery recovery.img ".
I'm in need of help guys and girls.
The other night I decided to "increase my battery life" by "disabling" a few (probably system) apps, through the "Apps Manager / All Apps" tab in Settings.
Everything was ok for another 10mins, went to bed.
Woke up to the "Samsung" logo stuck on the screen.
I tried rebooting and rebooting after removing the battery (15-20 times),
this gave me the same result; self rebooting non-stop after freezing on the "Samsung" screen.
I cleared the Dalvik Cache.
This got me past the "Samsung" screen and went to "Updating Apps".
It initially completed the 192/192 (Number of apps on my phone),
but then rebooted, and continued to reboot every time it got to the "Android is updating apps" screen.
Will 'flashing' a (most likely stock, but suggestions are very much welcome) Kernel fix this problem?
I was stupid in not backing anything up on Titanium Back Up, and not setting up a regular backing up schedule, (since everything was running smoothly for 1 year)
I really have no back up of the data on the phone.
Please.
Please, some one out there, help me just get back into my phone with out losing all my data, and I promise I won't play around with system files any more.
Extra info.
I remember rooting the phone the day I got it, but can't remember what I did exactly. Probably a pre-rooted ROM.
It was a fire and forget thing, and I haven't played with Android software much since then. So now processes need to be explained to me like I'm 5. :good:
>TLDR; Think I disabled system apps. Can't get past "Samsung" / "Android is updating apps" screen. Constant self rebooting at these screens. No back up of any phone data. Will 'flashing' (stock?) Kernel fix this? (and not delete all my data) Please help, ****ting bricks here.
Reflashing the Stock ROM should fix this, yes.
Clear the cache again once you've flashed it.
Mate,
For what you are saying, you have a recovery (Phil'z, Clockwork or TWRP). If so, try and Format data and cache. Doing that wont erase your internal memory, dont worry. I guess it should be enough to get your phone working again.
After that, BACK UP!
Leogp said:
Mate,
For what you are saying, you have a recovery (Phil'z, Clockwork or TWRP). If so, try and Format data and cache. Doing that wont erase your internal memory, dont worry. I guess it should be enough to get your phone working again.
After that, BACK UP!
Click to expand...
Click to collapse
I'm at a recovery(?) screen. "CWM-based Recovery v6.0.1.4"
You mean to "wipe data/factory reset" AND "wipe cache partition" ?
Will I lose contacts, sms messages, S notes, emails, installed apps, photos, videos, the lot?
I'm still in semi panic mode and am afraid to do anything that might delete any of the above. :silly:
Through this "CWM-based Recovery v6.0.1.4", I have made a ".dup" back up to my external SD.
Is this enough before I do anything else?
I have other users saying I should, "Then flash a stock rooted rom and restore your data backup."
If so, should I flash JUST the stock ROM (which I don't even know where to get),
or should I flash the newer 4.3 Jelly Bean ROM since I'll be "flashing a ROM" anyways?
Greetings,
I would have liked to post this questions, where it belongs to, but I'm new to this forum, so I put it here.
Last September I've updated my DHD following the instructions given in the thread mentioned in the headline and everything was fine. Yesterday in the evening, I got the notification to restart using the recovery mode, because something in the context of the superuser should be updated or modified. Because it was not the first time, I just did it. But this time, after rebooting, the device stopped with the HTC bootscreen (green HTC on white background).
After 10 minutes I took out the battery and restarted again. Again I was able to choose recovery mode, but while starting the DHD got stuck with the bootscreen. I decided to wait and just put it aside showing the boot screen, but the result this morning was that the battery is empty and nothing changed.
Does someone know about that issue and what do I need to do to get the device to work again? Why was this update needed in the first place?
Thanks a lot in advance...
im not sure why
but have you tried re-flashing the ROM?
PHOENIX-9 said:
im not sure why
but have you tried re-flashing the ROM?
Click to expand...
Click to collapse
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
If you don't wipe your data partition (dirty flash) and you flash the exact same ROM, you shouldn't lose data.
KKrittel said:
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
Click to expand...
Click to collapse
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
PHOENIX-9 said:
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
Click to expand...
Click to collapse
Tried to make a backup, but it recovering did not work. Doesn't matter. I just flashed the same image again, downloaded 'my' apps and restored the status from before the crash.
Nevertheless the same notification showed up, saying that the superuser kernel needs to be updated and I should use 'recovery mode' again. With a bad feeling, I did it again, but this time it works.
So to sum it up: device was useless for some days, restored it with some effort and now it works again. But I need to get prepared for the next time and to think of an app to backup all apps including app-data.
...but as always, this is a task for laaaaater
Thx,
Karl