Today, my Qtek 9090 main and backup battery ran out and my machine
when back to the factory settings. Whe I got into the office, the first
thing that I did was perform a restore from yesterday's backup. All
proceeded well, but it got to the end and told me that a number of files
were
open on the device and if I closed them, I could try again.
I went on to the device and went throug the memory settings and closed all
the "Running Programs" except the ActiveSync program. This still did not
close any of the open file, so I skipped them and rebooted the device.
Enclosed a screenshot of error. I could not enclose it since the server did
not accept it. Anybody interested I can send the screenshot via email.
Why does the restore application not automatically close the require files
when it need to?
How can I force the open files closed on the device so that the restore will
work fine?
Last post was mine, Sorry, logged in as guest.
I managed to upload a screenshot of error. Sorry fo multiple posts.
I suspect that it's the phone application. The only problem is that you cannot shut it down! Even without putting in the pin number or putting it on flight mode I get the same errors. Anybody know how to force shut down the phone application?
Related
just as you get one thing working correctly...something else f***s up!!
just went to check some mails and now my GPRS settings don't work.
I've not changed anything, or messed with connections...it's just stopped working.
followed the instructions on the t-mobile website...but still no GPRS connection. Just nothing happens..doesn't even try to conect and tell that I have a username or password incorrect..just does nothing but tell me that the current connection cannot be used for your request.
wtf??
Can anyone let me know where I can find step by step instructions to get this set up?
many thanks
even worse...if I try to access anything while connected by wifi....the same message!!
the current connection cannot be used for your request!!...
URGENT HELP PLEASE
Just about had enough and thought about a hard rset....better back yo first though right?....and now active snyc wont recognise my device....could it get any worse???
Hmm is this a HTC Artemis or T-Mobile MDA Compact III? if its the later the hardware is not fitted for WiFi so that option won't work.
When my device is playing up in this way (which it does at least once a week) I simply soft reste the device by poking the stylus in the reset hole. Being a soft reset it doesn't wipe any data or settings - I wold start with a soft reset and see what happens next - Mike
You could try deleting your connections and the installing a tmob connection cab which shoudn't be too hard to find on this site.
This is one particular bug I,ve not yet had the pleasure of, but I can appreciate what a pain it is.
Do you have a backup that works?
well...I'm having a nightmare!!!!!!!
hard reset the phone (nothing seemed to be going my way)
someone on here told me that I could save a copy of pim.vol and then replace this back onto my machine and I would have all my contacts back....sadly not..if you try to copy this file back you just get a sharing violation!! I'll be making a comment about this in the post where it was suggested!!
so, might have to spnd the next few hours adding my contacts back in.
NEXT....to try to fix the sync problem I upgraded to 4.5 (as suggested by the MS website) ....that screwed my PC up well and proper!!...everytime I tried to connect my PC usage went to 100% and nothing worked!!
so had to search for my original CD and go back to 4.2 which seems to be ok now.
I do have a back up that I made a few days ago...just a little concerned that it will put back all the issues I had in the first place, as I'm not sure when I lost my connection stuff.
what a complete nightmare tody!!
try to restore, at least you will get you contacts back which I am sure though I can't point you at it, there are other ways of backing up.
Just finished restoring my backup from a few days ago.
Got my contacts back which was one of the main things.
then had to set up a new connection with active sync (now called PC2, how do I delete PC1???)
anyway..everything is back to normal..including my GPRS and wifi working...
happy man now...
Cool.
Just open AS on your PC, click file and you will see an option to delete a partnership.
I have hit the reboot on the back of my dell x50v and for the last couple times it says that "tbstart.exe failed to start, may need to reinstall".
I have no idea what this is and tried a search and found nothing on the internet.
Anyone have any idea what this is? I also posted another problem about my device now not recognizing my home network and says the ssid is hidden, are these two items related? I have wm5 ao2.
Any ideas?
I'd say that if everything is working the way it should on your phone, then go to the windows startup folder and remove the link to it. Don't delet it just yet, cut it and paste it somewhere that you'll remember where it is, like the My Documents folder, just in case you find out that you did need it for some program. More than likely, the reason it failed to start is because you removed the program and it forgot to delete the startup link. Don't worry that removing the link will cause your phone not to boot or something like that either because your phone is already rebooting without the program anyway.
OK im not sure if this post is in the right location but here's my dilemma:
I have a rooted motorola cliq and adb on my computer but recently i was trying to "unprotect" my market by editing the build.prop file in my phone's system.
CMD prompt was giving some weird "cross device link" error whenever i tried to copy the new edited build.prop from my sd card and replace the old system file so i decided to use an app instead, root explorer. the app worked perfectly, the problem is that i made an error in the edited file...
I deleted the line that starts with "ro.build.fingerprint=" like i was suppose to but i made a copy n paste error from the website i was using
(heres a link: androidforums. com/spica-all-things-root/98024-protected-app-market-fix-tutorial-build-prop. html
and i replaced that line with
"ro.build.fingerprint=verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/rel (rest of lines)"
instead of
"ro.build.fingerprint=verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/release-keys (rest of lines)"
(Ill attach the bad build.prop and the original so you can see what i mean)
Ok here come the main issue:
I didnt catch my mistake and i reset my phone to factory settings like the next step says to (i backed my apps up using mybackup which saves to the sd)
but when my phone turned back on, it repeadadly says that
"Sorry!
The process "(EVERY SINGLE PROCESS)" has shut down unexpectedly. Please try again"
I can see the motoblur screen in the back and in between pop ups i can click next and get the phone to the main menu which is completely blank
even the process "HOME" wont open. Luckily, in between fighting the pop ups of "this process has shut down" i can manage to get the phone to turn on usb mode. I COULD EASILY FIX MY PROBLEM BY EDITING THE build.prop but i need a way to get into my system folders, not sd card. On my computer, if i type adb devices in cmd is doesnt list any devices so cmd wont help me here...
SOMEONE PLEASE LET ME KNOW HOW TO GET INTO THE SYSTEM FILES W/O ADB but with USB DRIVE
THANKS IF YOU READ THIS FAR and wish me luck!!!
P.S please recommend me to some other android help forums or anywhere i can get help is appreciated. this doesnt seem like it should be that hard a problem to fix...
Good morning all.
So I installed the 8.1 preview through the store when it first came out a few months ago with no problems. Last night I went to try to move over to the official 8.1 release by going to the store then opening the browser then clicking on the link to take me back to the store to retrieve the official update through the store. The store update "application" never showed up(even after a few restarts and repeating the process). I thought it was strange so I said "screw it, i have nothing important on here" and decided to do a full/clean restore.
I plugged the charger in, let it go about its business and walked away. I came back 2 hours later and the screen was black(no "restoring windows" progress"). Let it sit for another hour in case it was doing something I just wasnt seeing. Came back and decided to hit the power button. Screen turned on with the "Surface" start up logo and then I got this error message.
http://i.imgur.com/Q37Af1a.jpg
Now I am stuck in a boot loop where if i hit "ok" it just restarts and brings me back here.
Of course I never made a 8.1 recovery USB. I have the touch keyboard and access to a USB keyboard too.
Any ideas/direction/thoughts AT ALL are greatly appreciated.
EDIT: I was considering using my colleagues RT to create a recovery image to attempt to get this guy booting but it seems as though this is a bad idea due to his SN being copied over to my RT and causing issues. Am I correct in assuming so?
The CD key ought to come from flash ROM, but it depends on how the recovery image works, which I don't know >.<
If you can use his recovery image to boot to command prompt, you can mount your SSD's registry hive and dump the product key data, then decode it on a Windows PC. Then after recovering with the image, even if the product key ended up copying your colleague's Surface's key, you could just go to System and click "Change product key" and type your own key. (In this situation, the desktop will likely be black, a sign that Windows was unable to activate. Changing the key to yours will fix that, of course.)
I'm not saying that this is easy or anything, but this ought to work, with my understanding of Windows NT.
Note that you don't need to bother decoding the registry data if you notice after recovering that your product ID in System is different than your colleague's, and it also says that Windows is activated. This would mean that the recovery image grabbed your CD key out of flash ROM.
EDIT: I guess what I meant to say is that when you boot to command prompt, run regedit. In regedit, go to HKEY_LOCAL_MACHINE then File/Load Hive. Find your system hive on your SSD, which may be on a different drive letter than usual, in somewhere like Z:\Windows\System32\config\SYSTEM. Give it some name like "meow". Find the subkey meow\SOFTWARE\Microsoft\Windows NT\CurrentVersion. Go to File/Export and export that to a .reg file on your USB stick. If there is an option to do so non-recursively (I forget, and I'm on my iPad), use it because that key is big. Once you've backed it up, you're safe to recover, because now you have everything needed to find out your old key if required.
If in fact you do need to use that .reg file to determine your old key, let me know so I can help you out. Some tricks will be required to proceed.
Melissa
munsterrr said:
Good morning all.
So I installed the 8.1 preview through the store when it first came out a few months ago with no problems. Last night I went to try to move over to the official 8.1 release by going to the store then opening the browser then clicking on the link to take me back to the store to retrieve the official update through the store. The store update "application" never showed up(even after a few restarts and repeating the process). I thought it was strange so I said "screw it, i have nothing important on here" and decided to do a full/clean restore.
I plugged the charger in, let it go about its business and walked away. I came back 2 hours later and the screen was black(no "restoring windows" progress"). Let it sit for another hour in case it was doing something I just wasnt seeing. Came back and decided to hit the power button. Screen turned on with the "Surface" start up logo and then I got this error message.
http://i.imgur.com/Q37Af1a.jpg
Now I am stuck in a boot loop where if i hit "ok" it just restarts and brings me back here.
Of course I never made a 8.1 recovery USB. I have the touch keyboard and access to a USB keyboard too.
Any ideas/direction/thoughts AT ALL are greatly appreciated.
EDIT: I was considering using my colleagues RT to create a recovery image to attempt to get this guy booting but it seems as though this is a bad idea due to his SN being copied over to my RT and causing issues. Am I correct in assuming so?
Click to expand...
Click to collapse
If you recover using an 8.1 recovery image form somebody else it won't mess with the keys. Worst case is that you may have to activate and you do not have a key. If you look at this post by Osprey you will see how to get the key from a 8.0 installation. That won't help you of course unless you have access to the registry and hive as Melissa suggested.
I actually recommend you use an 8.0 image to recover your RT and then upgrade. The only thing you have to do is get the image and "burn" it to a thumb drive. There are no steps required to obtain your key. Make a bootable thumb drive with an image you can download from here and start from scratch. Your system will automatically activate going this route. I've done this several times to switch between Preview 8.1 and 8.0. Follow the instructions above from Osprey's post to obtain your key just in case you do need it sometime in the future. Then you upgrade to 8.1 (nothing necessary in terms of activating this way).
Here is a post with a link on how to recover with a USB recovery image. One important point when you put the image onto the thumb drive is that it has to be bootable. Use UltraIso or Rufus to put the image onto the thumb drive (FAT32 formatted).
munsterrr said:
Any ideas/direction/thoughts AT ALL are greatly appreciated.
Click to expand...
Click to collapse
Apparently this is a widespread problem, and one of the reasons I haven't upgraded to 8.1. Heres the solution: http://kickthatcomputer.wordpress.com/2013/10/19/windows-rt-8-1-upgrade-fails-with-boot-configuration-error/
Thanks for the replies everyone. My colleague was able to upgrade to 8.1 on his RT with no problems. We were able to copy the image(minus recovery partition) over to a thumb drive and I was able to boot from that and eventually upgrade myself.
ETA: I don't see a way to delete this topic so I'm just updating it. I didn't want to risk waiting another day to not have an answer since I'd already posted other places over the weekend with no response and we need it working for tomorrow morning, so I just went ahead and flashed the factory image from here:
https://developers.google.com/android/images
Everything is in order now! Tips for anyone else doing this, don't skip the step of adding the platform tools to the path environment variables. I did the first time and the flash script wasn't able to find some files because of it and aborted. Everything pushed to the tablet and installed fine after I added the tools folder to system variables.
**********************************************************
This is the only place where I see detailed answers so I registered to ask this.
Status locked/not rooted, just however I bought it when it released plus whatever OTA updates before I stopped using it. Dead in a drawer for maybe two years, I got it powering on again by disconnecting/reconnecting the battery then charging on my PC overnight via USB, but it kept booting to a black screen, no logo, no splash.
I went into recovery mode and did the wipe data/factory reset. I can now get to the welcome setup screen but there are two problems:
1) Errors immediately pop up blocking the screen, making it hard to choose anything because as soon as I hit ok to make an error go away, another pops up. It bounces between "android.process.acore/gapps/media has stopped" with "calendar has stopped/email has stopped" sometimes appearing too but it's mainly the first ones.
2) If I'm fast enough after dismissing an error, I can click next from the language screen to the wifi connection screen. SKIP is greyed out. I can select my wifi but when the password prompt comes up, no keyboard appears after clicking the field to enter one. It's just the blinking cursor.
Keep in mind the errors are still popping up too so I don't know if they're blocking things. I sometimes used a bluetooth keyboard with it, so I grabbed that and tried typing with it just in case and no luck.
Attempts​
I found a fix to try sideloading a factory image via the apply update via adb option in recovery mode, but the google site said it's safer to try sideloading a whole image OTA, so I tried that instead using the zip file there for Nexus 7 2013 wifi (I have 1st Gen but don't see that anywhere so this may be the issue too). After it hit 100% it was aborted for some reason I can't remember now.
But I do remember when I looked up whatever it said, most responses were that sideloading a whole image OTA won't work on devices that haven't been "unlocked" or something.
I found another response to someone with my problem, not having a keyboard after resetting, which said to sideload a keyboard app through adb. I found some gboard apk listed as the version for the Nexus 7 but when I did the adb thing, it aborted because of something to do with e-signature not being verified.
Question​
I can figure out trying to copy over a factory image but since I suspect the main issue now is the Nexus not having wifi access to complete setup then update/install what it needs to stop those errors, I consider that a last resort. So my question for now is for further help on getting a keyboard app or another way so I can type. If I still can't get things working after that, then I'll ask about the factory image.
Thanks!