So, just a few hours ago I decided to install ADWLauncher, then I noticed my phone was acting VERY sluggish no matter what I did;uninstall ADW, restart, wipe cache, dalvik, and now my very last attempt is nand restore...but I'm getting the error "Error: run 'nandroid-mobile.sh restore' via adb" I'm not familiar with adb, so bear with me.
If it's any help, I'm on Virus ROM with Carbon theme.
I've had no prior problems like this or at all.
I know how to use a computer and do commands, but I'll need some guidance with adb, etc.
--------- I tried posting in Q&A but no replies thus far and I'm freakin' out because I really need my phone.
Try charging your battery for awhile...
apristel said:
Try charging your battery for awhile...
Click to expand...
Click to collapse
I was hoping that would be the solution, but I popped in my fully charged battery and keep getting boot loops too, and still won't restore my backups...
We wipe the system and instead of restoring the NAND backup just load up a new ROM. You can restore after you get it working.
Try that.
mrmomoman said:
We wipe the system and instead of restoring the NAND backup just load up a new ROM. You can restore after you get it working.
Try that.
Click to expand...
Click to collapse
Wiping the system as in wiping data/factory reset, wiping cache, wiping dalvik?
Sweet Jesus, I fixed it! I did what you suggested although I tried that earlier and it didn't work. Thanks a lot guys.
Related
I posted this on DamageLess' page in hopes that he could help me, but I haven't gotten a reply yet. I figure someone on this forum can help me.. Just read the paragraph and you'll know my problem...
Hey man, I really need your help
I tried using your new DCUpdater (which is a fantastic idea btw) and i'm having a major issue. My phone won't boot. At first I was having problems with SuperUser, but I fixed that by enabling USB debugging, then unplugging the phone, then using the Updater. That worked. But when I tried to reboot the phone, it wouldn't boot. I wiped, restored to my most recent backup, and it still won't boot. I wiped, manually installed your new ROM, and tried to reboot again, and that's where I am right now. It had the Quietly brilliant screen, flashed the sprint logo screen, and now it's back to the Quietly brilliant screen. I think it's in an endless boot, because as I was typing this, the screen flashed grey for a second, then it flashed the sprint logo, and now it's back to quietly brilliant. Please please PLEASE get back to me asap, because I don't know what to do.
dereklane said:
I posted this on DamageLess' page in hopes that he could help me, but I haven't gotten a reply yet. I figure someone on this forum can help me.. Just read the paragraph and you'll know my problem...
Hey man, I really need your help
I tried using your new DCUpdater (which is a fantastic idea btw) and i'm having a major issue. My phone won't boot. At first I was having problems with SuperUser, but I fixed that by enabling USB debugging, then unplugging the phone, then using the Updater. That worked. But when I tried to reboot the phone, it wouldn't boot. I wiped, restored to my most recent backup, and it still won't boot. I wiped, manually installed your new ROM, and tried to reboot again, and that's where I am right now. It had the Quietly brilliant screen, flashed the sprint logo screen, and now it's back to the Quietly brilliant screen. I think it's in an endless boot, because as I was typing this, the screen flashed grey for a second, then it flashed the sprint logo, and now it's back to quietly brilliant. Please please PLEASE get back to me asap, because I don't know what to do.
Click to expand...
Click to collapse
do a wipe/ factory restore and then restart phone. dont flash any other rom or anything. samething happened to me the other night when i flashed the rom. it was an endless boot loop. i tried a wipe and reflash. wipe nandroid, nothing worked until i said screw it ill wipe and go back to factory and then try after phone boots up. to my surprise when phone started back up it was the 2.1 rom that i tried to flash. dont ask me why but it worked
Try wiping the ext partition.
-------------------------------------
Sent via the XDA Tapatalk App
david279 said:
Try wiping the ext partition.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Do I re-flash the ROM after I wipe, or do I try to do a restore????
dereklane said:
Do I re-flash the ROM after I wipe, or do I try to do a restore????
Click to expand...
Click to collapse
id say do not flash a rom. do a factory wipe then restart. read my comment under ur original post
You can do what the 2nd guy said..
Wipe everything.. Then dont flash or nandroid restore.. JUST reboot your phone.
Or save all your files to your computer that are on your sdcard... Repartition your sdcard. Then reflash the rom and move your stuff back.
cbarlan said:
id say do not flash a rom. do a factory wipe then restart. read my comment under ur original post
Click to expand...
Click to collapse
So you're saying wipe everything and then just reboot the phone?
Jus10o said:
You can do what the 2nd guy said..
Wipe everything.. Then dont flash or nandroid restore.. JUST reboot your phone.
Or save all your files to your computer that are on your sdcard... Repartition your sdcard. Then reflash the rom and move your stuff back.
Click to expand...
Click to collapse
I just did a factory reset, wiped my Dalvik cache, and wiped my sc card option thingy. I went straight from there to rebooting my phone. I'll say something if it boots now
i'd say wipe settings, wipe ext, wipe dalvik, flash rom, boot. if that doesn't work, wipe again and again then boot.
Jus10o said:
You can do what the 2nd guy said..
Wipe everything.. Then dont flash or nandroid restore.. JUST reboot your phone.
Or save all your files to your computer that are on your sdcard... Repartition your sdcard. Then reflash the rom and move your stuff back.
Click to expand...
Click to collapse
can i flash a new rom now?
Thread Moved as it isn't development.
Hello guys.
I would really appreciate an answer to a question I have.
I installed leedroid 3.0.2 and I have the same apps and settings as before.
I think I haven't done a good wipe..
I rebooted to recovery from cwm and used the wipe before I installed the new Rom. (i was using the revolution 3.5 before)
After I installed the new Rom, when I booted on, all apps and settings were there.
Shouldn't the wipe thing clean everything and leave the phone "empty"?
Or, (most obvious) did I do something wrong and should do it again? Cause there is a little thing with the market that closes the process when I click on new released apps.
Thank you in advance guys.
Cheers !!!
Sent from my LeeDroid 3.0.2 Enhanced Desire HD
GeorgeKps said:
Hello guys.
I would really appreciate an answer to a question I have.
I installed leedroid 3.0.2 and I have the same apps and settings as before.
I think I haven't done a good wipe..
I rebooted to recovery from cwm and used the wipe before I installed the new Rom. (i was using the revolution 3.5 before)
After I installed the new Rom, when I booted on, all apps and settings were there.
Shouldn't the wipe thing clean everything and leave the phone "empty"?
Or, (most obvious) did I do something wrong and should do it again? Cause there is a little thing with the market that closes the process when I click on new released apps.
Thank you in advance guys.
Cheers !!!
Sent from my LeeDroid 3.0.2 Enhanced Desire HD
Click to expand...
Click to collapse
Are you wiping data and cache in recovery?
"wipe data/factory reset"
It will then say:
Code:
-- Wiping data...
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
Then:
"wipe cache partition"
It will say:
Code:
-- Wiping cache...
Formatting /cache...
Cache wipe complete
(second option is overkill)
Have you still got the setting to backup to Google servers ticked? Or any other app that you have backed things up with?
Whilst the last option wouldn't be instant (they would download again and take a good 5 minutes to appear).
And yes, you will probably experience issues if this is due to a missed wipe.
So, I will need to do a factory reset first, then do a cache wipe and then install the Rom?
(i don't remember doing all these for the revo Rom..)
Do I need to do these without rebooting the phone until everything is done?
Cheers !!!
Sent from my LeeDroid 3.0.2 Enhanced Desire HD
GeorgeKps said:
So, I will need to do a factory reset first, then do a cache wipe and then install the Rom?
(i don't remember doing all these for the revo Rom..)
Do I need to do these without rebooting the phone until everything is done?
Click to expand...
Click to collapse
Yes, you should always do the "wipe data/factory reset" before installing any new ROMs or if the dev has advised it, also between major update revisions.
You don't need to reboot. If using recovery to install the ROM just do the wipes then flash the ROM using menu.
Awesome. Thanks for the help.
Will try it now and I hope everything goes well. Hope I won't get stuck since am not in front of my pc.
Cheers !!!
Sent from my LeeDroid 3.0.2 Enhanced Desire HD
Well, I did it again. Everything wiped out, started as new.
But still, new apps in market and battery history in spare parts give me a process termination...
Oh well, I guess that Lee will release an update.
Oh, something else I would like to ask. There is a new kernel for the Rom. Do I flash it the same way I flash everything? Through recovery?
Thanks again guys
Cheers !!!
Sent from my LeeDroid 3.0.2 Enhanced Desire HD
I use Leedroid and don't have this problem. Today I have installed from scratch and gone back and forth between ROM's. i turned off all the processes that backup and restore apps and I get a blank fresh install.
I have to ask, the last time you installed Leedroid, did you use the downloaded one or a copy from your sdcard? is it possible you are restoring a copy rather than flashing a fresh copy?
And you don't have any apps that have backed up your apps such as Titanium? And you have turned off Google Backup and restore feature?
The thing is, it is handy not to lose data but we need to make sure your wipe is being done. Did you see the same messages in Recovery as I showed above?
gosh, it is sooooooooooooo weird...
i did it all again. factory reset, delete cache, installed the 3.0.3 version (which was released today).
everything seemed to go smooth. still, i went to market and clicking on the newly released apps list i get an error which is "com.android.vewnding" has been shut blah blah blah. and the same happens to spare parts. when i click battery history ""com.android.spare_parts" shuts down.
do you guys think it has to do with the kernel? should i flash lee's kernel (i couldn't find how to. i mean, shall i do it from the cwm recovery?)
i guess that the radio has nothing to do with all these, does it?...
thank you guys once again for your help
Cheers !!!
GeorgeKps said:
gosh, it is sooooooooooooo weird...
i did it all again. factory reset, delete cache, installed the 3.0.3 version (which was released today).
everything seemed to go smooth. still, i went to market and clicking on the newly released apps list i get an error which is "com.android.vewnding" has been shut blah blah blah. and the same happens to spare parts. when i click battery history ""com.android.spare_parts" shuts down.
do you guys think it has to do with the kernel? should i flash lee's kernel (i couldn't find how to. i mean, shall i do it from the cwm recovery?)
i guess that the radio has nothing to do with all these, does it?...
thank you guys once again for your help
Cheers !!!
Click to expand...
Click to collapse
You have tried fix permissions in ROM Manager, yes?
eeeeeeeeeerm.... you got me. that is something i totally forgot to do :-(((
gosh.. i flashed the radio, sweet. tried to flash a kernel using jkoljo's tool and it stayed on the white screen (and of course cold sweat was all over the place )
but i flashed the rom again after clearing cache and the likes and (thank god) i'm in.
but the most weird thing is that, after all these, the kernel is flashed :-S
i checked in the phone info and the kernel is there..
anyway, am gonna do the fix permissions thingy and reflash once more. if it stays the same way, i'll have to live with it. it's late here in greece.
thanks again for your help guys, i really appreciate it )))
Cheers !!!
i did it all again but nothing happened.
did the permissions, rebooted to recovery, factory reset, cache wipe, install new rom and nothing.
i have to tell you guys though.. the problem with the market started when i was on the revolution rom. and it started just like that. one day everything was fine, next, bam. it didn't budge.
do you think there might be something wrong with the phone itself? (probably not and i'm paranoid)
other than that, everything works nice.
oh, and some other thing. there is this "full wipe 1.3" zip i had put in my SD card but never really used it.
should i use it this time?
this app should clean everything in the cache but not my files, right?
Cheers !!!
YouTube clip of how to manually full wipe everything.
http://www.youtube.com/watch?v=fCwr6Ru0yko
When using this method I've never had a problem.
Sent from my HTC Desire HD using XDA App
I did the wipe as shown in the video. The problem remains the same. New market apps list gives an error followed by a restart of it and spare parts battery history does the same (without the restart though)
I don't know, I'm thinking of trying a different Rom even though I like the one Lee released.
(could all this mean that I have a problem with the phone?.......)
Anyway, thank you guys for spending time helping me.
Cheers !!!
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.
So I used the Auto CF root and all went well. Next, I went back into recovery and installed the TWRP Recovery though odin. It installed fine. After that I noticed I no longer had root and I can't figure out how to get it back. Supersu was still installed, it just wouldn't work.
At this point, i've tried redoing the root process a couple of times and it says that it worked fine, but doesn't do the job. Anyone got any ideas on what to do?
If anyone's curious, I started on totally stock OTA MF9.
Thanks
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
ifly4vamerica said:
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
Click to expand...
Click to collapse
Thanks for the tip. Downloading the odexed version of this. Slow download so almost 2 hrs left.
[ROM][ZIP]Stock Rooted Deodexed/Odexed MF9 with SuperSU/Busybox 1.20.2
Hopefully it works. I tried wiping cache and dlvik cache and now when i turn the phone on it just keeps giving errors that this and that app can't open so the phone is essentially unusable. Didn't think wiping cache would do that.
Yeah sometimes things just go screwy. Have you tried fixing permissions? While you wait for a download you can wipe cache davlik and fix permissions its in the advanced menu of twrp. The odexed with no data wipe should fix you up I would recommend wiping cache davlik and system before you flash it. If it still gives errors you may have to wipe the data also and start fresh. You can also try TWRP version 5.0.2 if you aren't on it there is a flashable in the dev forum also. Some people have reported issues with the newer version. I think you will be fine flashing that stock odexed ROM though.
SGS4 Sent
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
iivisionii said:
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
Click to expand...
Click to collapse
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preload before flashing to avoid issues. All the custom ROMs have root built into them so you should be good to go.
SGS4 Sent
ifly4vamerica said:
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preloaded.
SGS4 Sent
Click to expand...
Click to collapse
Thanks. I'll have an update soon. Either that or a panic attack and a question in roughly 30-45 minutes.
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
daniel4653 said:
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
iivisionii said:
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
Click to expand...
Click to collapse
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
iivisionii said:
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
Click to expand...
Click to collapse
Have you tried the battery pull trick once frozen?
ObrienDave said:
Have you tried the battery pull trick once frozen?
Click to expand...
Click to collapse
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
iivisionii said:
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
Click to expand...
Click to collapse
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
ObrienDave said:
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
Click to expand...
Click to collapse
Ah ok. Good tip to know. I had tried that and it didn't work. Seems to be working ok now. I'm gonna be careful not to screw it up cuz its already 1 am, hehe. Thanks for everyone's tips.
Hey everyone.
So, as every Android I've ever had.. Sometime the device needs a reboot... The battery goes out faster then it should, stuff runs a bit slower and i reboot gives me a clean start.
Here, a reboot does not do that, everything is still open on recent apps as if i didn't reboot at all .. What is the solution for this?
One thing you can do, if you have a custom recovery installed is first, close all open apps, reboot into recovery and delete Cache and Dalvik Cache... then reboot, let it do it's thing... you're as refreshed as you can get without wiping entirely and starting over.
CJ-Wylde said:
One thing you can do, if you have a custom recovery installed is first, close all open apps, reboot into recovery and delete Cache and Dalvik Cache... then reboot, let it do it's thing... you're as refreshed as you can get without wiping entirely and starting over.
Click to expand...
Click to collapse
First of all, Thank you!
is no one else bothered by this? sigh
Caniv said:
First of all, Thank you!
is no one else bothered by this? sigh
Click to expand...
Click to collapse
I've done this method a few times... I usually once I do a full fresh new rom setup will go through and setup everything, tweak it all up nice, remove things I don't want, etc... and when I'm 100% operational... I'll go to recovery, wipe the cache and dalvik, make a nandroid backup and boot back up. I run into less problems it feels like this way.
I just swipe them all away then reboot, its a pain but since I want to use android pay its something i have to live with.