Database Users

HTC HD2 fails to wake up after restore using sprite backup

Hello there guys. This is my first post on this forum, so please bear with me. I have problem on my device. Basically my htc hd2 was running fine, i had all my programs installed etc. I have created various backups of the phone using sprite backup.
I decided to do a hard reset because the phone never used to go into standby (screen off) when charging, only the backlight used to dim. I checked all the settings and i set the device to dim after 1 min and switch off after 2 mins when connected to external power. It still never switched off, this was turning out to be a nuisence specially when getting missed calls at night and screen staying on.
Therefore i done a hard reset and used sprite backup to restore various backup's as i had a few, but they wernt making the device function correctly. So once the backup file's were restored everything would be fine on the phone untill it went into standby, it then would fail to respond, sometimes the hardware button light up, sometimes nothing. The screen would remain off. I would really like to use the backup files as restoring the phone manually would be teadous. Any clues in what could be causing this, cant be the case off a bad backup as i have created a few.
P.S When hd2 is returned to stock it functions normally. Programs installed battlog, clear temp, bsb tweakes opera 10, opnmarket, skype, spb wireless monitor, coreplayer, srs wowhd 1.5.1.0 v2.1, coreplayer 1.3.6, myplayer, 1NETCFv35.wm.armv4i, 2NETCFv35.Messages.EN.wm, resco explorer + reg editor, cht cookie hometab.
Really appreciate it if you pros can shed any light on this? cheers

do you have s2u2 installed?
if so goto settjng power and switch power of in setting to off.
i had a similar problem, this seemed to cure it
hth
nev

Hi nev, thans for your reply, no i do not have s2u2 installed, also i would like to add that when the device was left overnight on charge, it fails to wake up,the screen stays blank only the hardware buttons light up and shows the orange charging light. Please guys help me out here, thanks

I'm a little stuck for another solution. I'd always thought that this was an issues with sprite and s2u2, seems no now.
Would you be willing to test? worse case you could un-install S2U2 or disable it.
It would be interesting to see if installing S2U2 and disabling the power option would fix the problem.
Which lock screen do you currently use?
All of the problems you are describing are exactly the same issues I was having.

Hi Nev, so you reckon sprite backup software could be the problem? I have never had S2U2 installed.
I have restored the phone to factory it works as it should. Nev are you suggesting that i install S2U2 after restoring the sprite backup file, then disable the power option?
oh i am using the winmo default lockscreen with device password.
How did you manage to fix your device then? Were you having the same issues when restoring using sprite back up files? If so could you please give me a brief rundown on what i should do?
Seems like this is not a common issue on here judging on lack of replies. Thanks for your help nev.

I'd give it a go. You have nothing to lose.
S2U2 is an excellent piece of software, amongst other things, it has password protection, and allows you the option of reviewing txt, mail, reminders, etc all from the lockscreen. Additionally, you can set it to allow quick switching between vibrate and sound profiles. ("sales" pitch over)
If your not going down this route I suspect that another hard reset and re-installing you apps from scratch is in order.... I did this about three times before I realised that there was a conflict when restoring from Sprite.
good luck

explicitsoundz1984 said:
everything would be fine on the phone untill it went into standby, it then would fail to respond, sometimes the hardware button light up, sometimes nothing. The screen would remain off.
Click to expand...
Click to collapse
your symptoms seem kinda similar to "Leo Screen freeze crash Issue"

Thanks guys for your help, i think i am going to leave it stock for a while and see if the screen plays up. I dont fancy doing all the sofware installs, incase the device is faulty. Thank you that link p107r0

good luck with yours, btw I used to have the described 'syndrom', hard reset helped, since than I keep most of the old backup copies, assuming that if anything similar happens some of those should work properly

Same problem here - SOLVED
Guys,
I very recently faced the same problem that it was virtually impossible to wake up my HD2 from standby after I had to do a restore with Sprite Backup (same problem as reported by explicitsoundz1984).
Since I actually found two solutions to fix the problem permanently, I like to share them with you:
Solution 1) After I removed all non-stock program links from the autostart folder, the problem was still exisiting. Therefore, I checked the list of installed apps from explicitsoundz1984 with mime and found a potential suspect: "srs wowhd" which obviously is buried deeper in the OS. After de-installing "srs wowhd", the standby of death problem was permanently gone!
Solution 2) I read in another threat that the standard restore options of Sprite Backup do not replace the current registry with the backup registry, but tries to "merge" them - this obiously leads to the situation that a full restore from a stable backup set can result in an unstable configuration.
After changing the restore setting for "system settings" to "replace" instead of "merge", the resulting restore was again a stable one.
Cheers,
Jan

Yes
with Sprite you must use erase and restore. You have to reset these parameters each time you are going to do a restore. It merges by default. If you are going to restore directly from the backup file on the SD then just double click on the file and restore. Then go into Sprite and change the parameters to restore and erase and restore again. The first one directly from the file execute will merge A pain but it works.

Phone crash after battery died!!

my battery was running low, (and coz poor battery issues with JPY), i didnt notice when it switched of. normally i use the power button to turn the screen on to unlock, but instead i realised the phone had been off as it was now booting up...it booted up fine went into the homescreen and then vibrated once and powered down.......now it was powering down for a long time and occasionally there were vibrations and the lights on the home keys were constantly on. the screen was black. i got home and tried to charge it but the progress bar showed no progress on charging, i tried to switch it on but it would go to startup screen vibrate cupla times and power down. so eventually had to do a hard reset in recovery mode. tried every option but in the end had todo it by wiping data.
now the thing is, is this supposed to happen? if ur battery suddenly losses power ur whole fone will screw up?
for future ref if ur battery dies dont try to switch ur fone on until u got some charge in it and use the home key to put screen on..

Sounds like it could have been faulty firmware .
JPY does not have a significant battery drain problem per se .
jje

Black screen, vibrations and no boot after restart
Hello! I had almost the same experience (Black screen after reboot and occasional vibrations) only mine refused to boot even after memory wipe and after flashing new roms.
Was your phone rooted? Because I think rooting a 2.2.1 rom (XWJS3) was the beginning of my nightmare. keep in mind that the phone was working like charm for two months. This was the second time I had a problem. The first time the phone started after performing a factory reset by itself!
In case this happens to you next time and for every non experienced galaxy player (like me) reading this:
Don't panic! Blank screen, vibrations and no boot doesn't necessarily mean a hardware problem. Finally I managed to fix it flashing eclair and repartitioning with pit512. Now I'm a happy XWJS8 user
And a question for the experts: Any clue why this happened? Is it really a rooting issue? Can a cheap Chinese battery from ebay cause this?

everything was stock on mine, no root.......maybe thats why i could recover it??!!

Maybe! and I hope the reason is faulty firmware as JJEgan says. If this is true, your phone will be fixed by the next update.

I was very urge... the same happened again. It's been a month of smooth functioning and now after a simple restart, the device doesn't boot for absolutely no reason (Stuck on black screen constantly vibrating). Since my phone wasn't rooted, and I haven't seen many people talking about a problem like this I suspect:
1. Faulty hardware (for a few devices including yours and mine)
2. A Bad app.

Contacts Vanished
Hey Everyone
Im having similar problems, i updated my sgs to the js7 version of froyo, then rooted it with oneclick method. this was as i got the phone a month ago. Its been smooth sailing since then. But last night the phone powered down and wen it loaded up it had no contacts, my sms where still there but all the apps had a force close issue none worked. so cleared the cache in recovery. Still nothing so i did a factory reset and once loaded up. i formatted the sd and internal within the settings option. So the phone was now clean. I then connected to pc luckily had backups so installed titanium restored all my apps n settings. Using kies restored my contacts n thanks to an app called sms backup i restored those.
So all was well and worked again. I didnt restore the apps i had installed within the last week to make sure it was not a faulty app. I was happy, but now tonight it did it again. No contacts again.
Pls help
Any suggestions

That's exactly how it started for me. One month after rooting froyo 2.2.1 Suddenly everything force closes and the device hard resets by itself. I reinstall all the apps and then after one month and performing a simple restart, it refuses to boot. Stays in a black screen and vibrates every some seconds. I flash a new rom but does the same. Problem solved after repartitiong and flashing original eclair with pit 512. Reflashed a 2.2.1 rom and everything works perfect (the phone now is unrooted and with a nice clear stock rom). But then after one month again (!) I realise that some videos refuse to play. Trying to restart and craaash. black screen, vibrations and no boot. Did the same again (repartitioning and flashing) and now I wait for another month to pass and lose an hour of my life to do the same again. No idea why this is happening. Is it possible that rooting messes with something that stays faulty after restoring the file system? is there an app that we all installed and caused this mess? please this is the most serious problem I've red in this forum and still a mystery. I believe this thread should be sticky and we all share similar experiences because this looks completely random!

I believe this thread should be sticky and we all share similar experiences because this looks completely random![/QUOTE]
+ 1

[Q] Odd loop, & like to think im better than this

First off, thank you to all. Normally i can search and lil reading and be well on my way. But this Droid X has driven me nuts. Its now 2am and i bow to the guru's. So i'll start from the beginning, I got Droid x from a second hand person today, i took home and formatted to stock via normal menu. I then activated phone as it makes you. then proceeded to root with pete 1 click. which worked instantly. So then i added koush installer, which gives two options. Top option tells you success right after you click it. Well then in my wisdom used titanium backup to restore my fiancee's apps to this phone. Her old one was a original droid. Didn't think i added any of the system data but i must have, cause after a reboot a while later. the phone was in a no service state. Couldn't check about phone or really any menu after the initial settings menu at home page. So then after a lot of bad words, =) end up doing a factory reset again. Which is what got me to new problem.... The phone isn't rooted & when trying to root it fails on restarts because after RED Logo appears screen faintly is lit & hangs forever. But if pull battery and turn on, seems to be just fine. Also seems to do it only when plugged in usb to pc. Which can't reroot without the connection right? or does zroot work? So my thinking is that the person before put a bootloader on here, and i didn't know. So perhaps there is now two partial installs of loaders. that a factory reset/wipe won't fix. & having never had to do anything crazy on my Droid 3 or the other 2 original droids im really frustrated at myself. cause im sure im missing a very simple item in this process. Thank you for reading this jumbled problem as i typed it, & appreciate any and all responses.

[Q] Frequent, Random Crash-Reboot

In the last few days my S5 has started just locking up briefly and then rebooting. It doesn't do it from a particular app, only when using the camera, or any other specific symptom I can find. It will even lock up and reboot during a reboot sometimes. It's happened running various unrelated apps that don't have anything (apparent) in common, when running no apps, when closing apps, and when sitting all by its lonesome next to me while I'm doing something else entirely.
When it started I was running Safestrap with AllianceROM 1.1 installed on the boot partition. I wiped and installed AllianceROM 2.0 and it still does it. The only change I can think of that happened anywhere around the time the problem developed is I replaced a broken charging port cover (can't imagine how that would have messed anything up.)
One common symptom that may or may not be helpful: during the short unresponsive time during the crash before it reboots, one or two lines of "static" a few pixels tall running horizontally across the display will often (but not always) appear. It's happened when using the phone, when not using the phone, and during reboot from a previous crash. It's crashed while rebooting prior to the Safestrap screen displaying. It crashes and reboots with and without the SD card installed.
At this point I'm thinking the phone is just plain broken (still under warranty) and a replacement is in order. So my questions are:
1. Anyone seen this before and know a fix?
2. Is there anything I'm overlooking and should test before pursing warranty replacement?
3. Is there any reason to avoid a replacement unit (ie. would a new phone resist root/safestrap/etc)?
Thanks.

Sounds like you've covered everything but one.
Try returning the phone to stock and see if the problem persist. If it does then phone is ready to be exchanged.
If not, you'll know it is something other than a hardware issue.

c4manceph said:
Sounds like you've covered everything but one.
Try returning the phone to stock and see if the problem persist. If it does then phone is ready to be exchanged.
If not, you'll know it is something other than a hardware issue.
Click to expand...
Click to collapse
Yeah, I suppose I ought to do that just to be sure. But to be absolutely certain that would require Odin'ing back to stock to get rid of the root, Safestrap, and all the trimmings, right?
So I need a nandroid backup of my current image so I can resurrect that if it doesn't work so I have a phone that only annoys me intermittently while I wait for the replacement. While if that does solve the problem I need my Titanium Backup files so I can gradually restore my apps/settings after redoing all the root, Safestrap, and custom ROM work.
Am I missing anything?

This is the method I would use to return to stock:
http://forum.xda-developers.com/showthread.php?t=2784880
Sounds like you've got it covered.

Thanks. That link mentions repartitioning as being optional... under what conditions would it be advantageous? Is it just one of those "if you wanna be absolutely sure" things or are there cases where the partitioning has been changed and needs to be reset?

New symptom: twice now the phone has rebooted into Odin mode with the message "Could not do normal boot, mmc_read failed".
Doesn't look good... at least I've been able to reboot the phone to the OS each time. Once it even did it itself.

Sounds like internal memory failure. Do your best to ODIN back to 100% stock & do a warranty return.

I've been back to stock for a day without any spontaneous reboots.
I figure the next step is to root, install Safestrap, and then flash the AllianceROM and not restore my Titanium backups except those that are absolutely necessary (and taking a nandroid backup before doing any of those). Let it run for a day or two like that, see if the reboots stay gone and then slowly restore the backups a few at a time to see if one of them causes the problem to return.

Thanks for the update, I wondered if you were having any luck.

I'll keep this updated just in case anyone else has the same problem, so they can have a better idea how to resolve it.
Currently I've been running AllianceROM 2 for about 10 straight hours with no misbehavior. From stock I installed towelroot, Safestrap, then flashed the ROM according to instructions. Once that was loaded and the Play store done downloading everything I shut down, backed up via nandroid, and then used Titanium Backup to restore some key apps and data. Actually I restored more than a few, but not close to all. With the backup if the problem returns I have a clean restore point to use for a more conservative approach.
My plan going forward is that if nothing else goes wrong, I'll restore a few more backups as I need the related app, and after a week or so if things don't fall apart I'll go through and delete the entire contents of the Titanium Backup folder and re-backup the apps as they are in a stable state. Whatever was causing the problem seems to have died in the repartition/odin-to-stock/root-and-return-to-custom, or it's lurking in one of the unrestored backups.
Fingers crossed.

Aaaaand just had a spontaneous reboot. Second time it's done it while scrolling the newsfeed in Facebook. (First time was pre-wipe to stock.) It's possible I just didn't have the restored stock version running long enough since this took over a day to happen.
So I'm restoring the backup and not restoring any of the Titanium Backup stuff. If it still reboots on its own after this, I'm considering it hardware and pursuing a replacement.

There's been another spontaneous reboot. At this point I'm pretty comfortable calling it a hardware failure. I believe the absence of reboots while the phone was Odin'd back to stock was a fluke and, had I given it enough time, I'd have seen a spontaneous reboot there as well. I'm going to forego testing this theory to expedite a resolution to the problem.
So my next step is to call Verizon and start the ball rolling on a warranty replacement. I'll Odin the phone back to stock just before turning it in, until then I'll let it run (as much as it does) the way it is.

The warranty replacement was easy. Went over the steps I'd taken (leaving out all the bits about root, custom Roms, and so on since it's none of their business) after spending about a half hour on hold between the initial customer support person and the actual phone tech guy. He kept saying, as I was telling him what I'd done, "yeah, that's what I was going to recommend next". Set me up for a replacement, next day air, and that's what I'm running now.
Wiped the old phone back to stock via Odin, set up the new one and restored every backup I wanted from Titanium backup. So far, no problems.
It's kinda neat how they send the replacement phones. No back cover, no battery, nada. You take all the stuff out/off of your old phone, use it to finish up the new one, and you're done. Put the old one back in the package, slap the return label over the previous label, and send it on its way. (Be sure to go to a FedEx store or something where you can get a receipt and so on to PROVE you sent it in case it gets lost, or you're paying for a new phone.)
It's clearly not a new new phone, it's a refurb, but aside from some minor scratches on the screen that a screen protector would make invisible, it's essentially new.

Still no sign of a spontaneous reboot, looks like this is fixed.

Many different problems. REALLY need help

First off, Sprint S4, I had LiquidSmooth until it suddenly broke (apps gone, settings went wonky, lots of sudden glitches) so I've been trying to fix that. When I cleaned flash, it worked for a while, than it kept turning off and not getting out of the boot screen. I've tried with many roms and the stock one and it just wont cooperate with me. Also I'm having troubles charging the phone. It keeps malfunctioning when I plug it in but it charges, the original wall charger won't work for it when the cable is fine but it worked with a different cable and outlet. Something is VERY messed up and I'm not sure what to do anymore. I keep doing the three wipes and flash but it's now stuck. Is this a hardware issue? Radio issue? I don't know but I really need help.

It's really hard to explain. It acts out whenever it's charging and i made one rom boot up thought it didnt have wifi so I'll experiement getting liquid smooth on it again. I dont know why suddently the it's giving me usb problems and why roms just suddenly break

Liquidsmooth booted and now Im getting a "unfortunatly, contextprovider has stopped"

yup, did it again, at the boot screen the message wont go away and behind it is something requesting root
fought through it and just giving me problems. Going to instead of flashing "L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar" with ODIN ill flash "L720VPUFNG2_L720SPTFNG2_L720VPUFNG2_HOME.tar"

It booted and reflashing to liquidsmooth is stuck at boot

Ok, I "think" i got it. The clock stopped once and that made my heart skip a beat. As long as it doesnt take a **** again and shut itself off and refuse to propertly boot, it should be ok.
Also please excuse the typos, I've been at this for 2 days straight.
Would an APN flash do this?
WTF I saw a duplicate dialer, one went away, two clocks, one crashes, and home button doesnt work
Ok, one is native and one is GAPP and now titaniumbackup cant restore the proper ID,

Ok 2nd times the charm, home works but Titaniumbakup ID won't restore
Nvm. Home still doesnt work but it does in key test in custom recovery

Ok, im PRAYING this NANDroid backup holds