I just got a replacement evo. As soon as i got home I rooted it. I just did a restore of the rom I backed up before I took the phone in, my question is since I got a brand new battery should I do a battery wipe? Because if I restore my rom and everything else wont the battery stats be for the old battery? They said my battery was bad so it had me thinking after the restore...any inputs?
The obvious answer is don't restore anything. Get fully charged, flash the ROM and start from scratch, using TB or MY Backup Pro to restore your user apps/data
I just did a restore of the rom I backed up before I took the phone in
Click to expand...
Click to collapse
Umm, you should NEVER restore backups from phone to phone. You probably fried your wimax keys, meaning you will never get 4g on this new phone.
As for the battery stats question, every time you flash a new rom, whether it be a new rom or a rom backup, you should always wipe battery stats.
yea so I've been reading that I f'd up. but luckily for me we don't have 4g in my area. Thank you though for the responses.
Related
I flashed DC 3.5 yesterday on top of my 3.2.3, and it was working flawlessly. However, I realized that some of my apps didn't like the upgrade, so I was planning on restoring my nandroid of my 3.2.3 installation, backing them up with TB and then restoring. I began the restore process and it has been running for over 1.5 hours so far. This seems excessive but I don't want to just pull the battery out if this could be normal.
I haven't changed from the default SD card that came with my EVO, so I know that it isn't the fastest card. Some advice would be appreciated.
Edit: I gave up waiting, pulled the battery, and restored my froyo backup. This restored in about 3-4 minutes, so that tells me there was something wrong with my 3.2.3 backup. That's obnoxious
Try restoring one more time...if it doesn't work then restore froyo again
I have similar problem, I am trying to do a nandroid restore. It's been going for two 1.5 hours.
I was on CM6 RC1 with Snap V7.b kernel.
Trying to nandroid restore fresh 3.1.0.1.
The restore process has completely filled my screen with the dots it's been going for SOOOOOOOOO long. What should I do?
If I pull the battery will it toast the phone? phone is unresponsive to button pushes but the dots are still going. PLEASE HELP
TF1984 said:
I have similar problem, I am trying to do a nandroid restore. It's been going for two 1.5 hours.
I was on CM6 RC1 with Snap V7.b kernel.
Trying to nandroid restore fresh 3.1.0.1.
The restore process has completely filled my screen with the dots it's been going for SOOOOOOOOO long. What should I do?
If I pull the battery will it toast the phone? phone is unresponsive to button pushes but the dots are still going. PLEASE HELP
Click to expand...
Click to collapse
You should be fine pulling the battery. If you've been running this for 1.5 hours as you say, I'm sure you wasted a significant amount of juice. just leave the phone off and charge it for an hour and then boot up into recovery and try again.
If it happens once more, either select a different nandroid or flash a new rom again.
Can someone please tell me how long a nandroid restore can take as a maximum?
I am running a nandroid restore as I type.
From CM6 RC1 with snap kernel
To Nandroid back up of Fresh 3.1.0.1.
It's been going for 2+ hours, the dots are still progressing but this seems like its taking longer than it should.
Question: Is this amount of time a sign that something is severely wrong?
How can I correct the issue? What will a battery pull do to my device?
Update: Battery pull did the job and my phone isn't bricked.
Shouldn't take that long.. I've done dozens of restores and most it took was 10 minutes or so.
Pull the battery and try again.. might be a r/w issue with the card.. You should still be able to get to recovery.
did you do the backup with clockwork, and trying to restore with RA, or the other way around? I heard that can cause issues.
yep, 10 minutes is the longest I've ever had one go. Also, fwiw, it always seems to finish somewhere around the fifth line of dots..
fachadick said:
did you do the backup with clockwork, and trying to restore with RA, or the other way around? I heard that can cause issues.
Click to expand...
Click to collapse
Nope, all done with Amon. Still not sure what the issue was. Resolved, I just flashed the rom again instead.
Hello everyone!
I'm running I believe the latest Fresh ROM. All I was doing was switching out a nearly dead battery, next thing I know my phone isn't getting past the boot screen. I've got into recovery, not really sure what to do there but I did do a cache & dalvik wipe. Now doing a nandroid backup. What can be causing this, and what do I need to do?
It could be any number of things. did you do anything before you took the battery out? did you power the phone down before removing the battery? did you wipe cache's before your fresh rom install? have you installed any new software recently?
Good job having a nandroid backup! the first time i got caught in a boot-loop i was SOL on that front. nice work
No I didn't power the phone down. I did the last Fresh upgrade a month ago or so but believe I did a wipe. I haven't installed anything new this week I believe. And I just did a nandroid backup, will that do me any good now?
No takers?! Your help would be much appreciated! This phone is my lifeline for biz and personal life so I need to get it back up & running quick fast and a hurry. LOL
have u tried a factory wipe at least twice I do out three times to be sure and what recovery r ur running I heard that cw is not really working well
Okay, so I researched my issue and didn't really find an answer. I'm not sure it is even the same issue, let me explain.
I rooted my phone using unrevoked, the latest one. I haven't flashed any roms or anything. I just deleted some bloatware and use wireless tether and shootme...etc....
The other while I was surfing the net on my laptop, I lost the signal. I went to my room and saw my phone rebooting. I didn't think too much of it until I realized it kept repeating after the 4g screen. I instinctively removed the battery and let it cool down. I replaced the battery and the same thing still happened. I wouldn't boot past the 4g screen.
I made a nandroid backup about a month ago and decided to just backup once again. I backed it up and restored the backup from a month ago. It worked fine. Now I tried to restore the most recent one and it wouldn't work at all. The same repetition of the boot screen, I believe it is called boot loop. I don't know.
My question is how would I be able to restore that most recent back up and why isn't it working? What could've possibly occurred to cause this malfunction?
I also read somewhere that battstatpro could be the culprit?
Cliffnotes:
Rooted phone a month ago
Did a nandroid backup & titanium backup (same day)
Phone stopped working while using wireless tether
Stuck in bootloop?
How do I fix it?
Thank you
wutitizshorty said:
Okay, so I researched my issue and didn't really find an answer. I'm not sure it is even the same issue, let me explain.
I rooted my phone using unrevoked, the latest one. I haven't flashed any roms or anything. I just deleted some bloatware and use wireless tether and shootme...etc....
The other while I was surfing the net on my laptop, I lost the signal. I went to my room and saw my phone rebooting. I didn't think too much of it until I realized it kept repeating after the 4g screen. I instinctively removed the battery and let it cool down. I replaced the battery and the same thing still happened. I wouldn't boot past the 4g screen.
I made a nandroid backup about a month ago and decided to just backup once again. I backed it up and restored the backup from a month ago. It worked fine. Now I tried to restore the most recent one and it wouldn't work at all. The same repetition of the boot screen, I believe it is called boot loop. I don't know.
My question is how would I be able to restore that most recent back up and why isn't it working? What could've possibly occurred to cause this malfunction?
I also read somewhere that battstatpro could be the culprit?
Cliffnotes:
Rooted phone a month ago
Did a nandroid backup & titanium backup (same day)
Phone stopped working while using wireless tether
Stuck in bootloop?
How do I fix it?
Thank you
Click to expand...
Click to collapse
Well I can't say for sure what caused the phone to initially wack out and go into a bootloop, but I'll tell you why the nandroid backup didn't work. The reason you can restore you're original backup, from a month ago when you rooted, is because you created that backup when your device was operating correctly. Since this most recent backup was created when you're phone wouldn't even boot to begin with, it will not work. The backup takes an exact copy of your entire system the way that it is when you make that backup. Since your phone was inoperable at the time of the backup, whatever it is that is broken was also copied to that backup, thus the reason it wont work. A nandroid restore will only be as good as your phone was when you created that backup.
Thank you. Is there anyway where I would be able to pull any information off that backup or fix that backup or at least get it to boot?
wutitizshorty said:
Thank you. Is there anyway where I would be able to pull any information off that backup or fix that backup or at least get it to boot?
Click to expand...
Click to collapse
Your welcome. I've never tried accessing any info or data from nandroid backup before, but I found this thread on how to do it. I've never tried it, so can't confirm nor deny if it works, but it looks like you're answer may be in this thread here: http://forum.xda-developers.com/showthread.php?t=890508
Thanks...I'll check it out
first things first. I just bought some batteries from someone on here, and when i tried to put one in to verify it worked, my phone bootlooped. So i wiped data and reflashed everything after making a back up, and everything was going smooth. then my battery died so i went to switch to a new one, and everything was fine. That battery died so i went to a third, and then my phone started bootlooping again.
When I tried to make a nandroid backup when that happened, my backups come out as not todays date, but by a lot of zeros followed by a 2 digit number (i think ten and 17 from the ones i've tried). when I tried to restore data from one i bootlooped.
any advice/whatever, I'm on franco.kernel and aokp b28. I'm thinking maybe a new kernel as this one may have battery issues?
Have you messed with the voltages at any point? It sounds like that could be an issue. Reflash whatever rom your on without wiping data. This should revert the kernel back. See if this solves the issue.
Am I also right in thinking that this battery is not an official samsung battery?
Sent from my Galaxy Nexus using Tapatalk
RTContent said:
Have you messed with the voltages at any point? It sounds like that could be an issue. Reflash whatever rom your on without wiping data. This should revert the kernel back. See if this solves the issue.
Am I also right in thinking that this battery is not an official samsung battery?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I leave my voltages stock at all times so no that can't be an issue.
Correct, it's not samsung oem but the oem battery still causes a bootloop after i've put one of the others in
edit: flashing my rom did not help to cure the bootloop issue, it looks like i'll have to wipe data again without a nandroid backup working.