I recently installed Office 2007 onto my Vaio. It said it was successful and needed a reboot, so I rebooted. Upon reboot, it simply won't let me get to the lock screen (where I enter my pass/PIN). I have control of the keyboard (I think) because I can still adjust the brightness. The trackpad won't register my click to get into the lockscreen.
I'm not sure what options I have. I tried to get into safe mode, which I've read is done by holding Shift and pressing F8 repeatedly at bootup. No go on safe mode.
Is there some alternative way to get into safe mode or somehow get into the lock screen?
Pressing any key should do it; you don't have to use the mouse. If that doesn't work either, though, there's a deeper problem. I'm not sure why you'd install a 6-year-old Office suite on Win8, but it should either work or not work; it should have no impact on the login process.
A usually workable but generally terrible way to get to the boot menu is to crash the system during bootup (force reboot, remove the power, or similar). There's a small risk of data corruption doing this, even using NTFS, though it shouldn't be a problem.
Or you can use an installation disk and try repairing Windows?
You cannot go into safe mode because when Fast startup is enabled. If you can somehow manage to restart your pc (like booting from an installation disk and quit after step 1) you will be able to get the boot menu using F8
GoodDayToDie said:
Pressing any key should do it; you don't have to use the mouse. If that doesn't work either, though, there's a deeper problem. I'm not sure why you'd install a 6-year-old Office suite on Win8, but it should either work or not work; it should have no impact on the login process.
A usually workable but generally terrible way to get to the boot menu is to crash the system during bootup (force reboot, remove the power, or similar). There's a small risk of data corruption doing this, even using NTFS, though it shouldn't be a problem.
Click to expand...
Click to collapse
The PC is for an aunt, whom did not want to adopt any new changes for fear of unfamiliarity. I actually still run Office 2007 on my own W8 machine.
So in order to crash the system, I'd have to remove the battery when the laptop is booting up? What should I expect having successfully crashing the system...? That just sounds so wrong
marvelprash said:
Or you can use an installation disk and try repairing Windows?
You cannot go into safe mode because when Fast startup is enabled. If you can somehow manage to restart your pc (like booting from an installation disk and quit after step 1) you will be able to get the boot menu using F8
Click to expand...
Click to collapse
It's an ultrabook with no DVD-ROM drive
"Crash" just meaning cause the startup to fail unexpectedly. The idea is that by causing the bootup to fail, the system may offer (when you next boot up) to boot into Safe mode and so forth. It worked in older versions.
GoodDayToDie said:
"Crash" just meaning cause the startup to fail unexpectedly. The idea is that by causing the bootup to fail, the system may offer (when you next boot up) to boot into Safe mode and so forth. It worked in older versions.
Click to expand...
Click to collapse
Thank you for the advice. I'll give it a try tonight.
Related
So, dumb self made a pattern that I don't remember. So my Vibrant is at the Too Many Pattern Attempts screen. I've tried to wipe the phone using vol up and down plus power but that doesn't remove the too many attempts screen at all. The only gmail account that I hooked up to my phone keeps telling me that something is incorrect yet I can log in to my gmail fine from my computer... What can I do? I tried to do Odin, but vol down plus power does nothing on my phone. It just continuously power cycles... When I boot into the recovery screen I can use Odin but it just hangs at checking files... Any suggestions?
Do you have coverage? Maybe the Google verification can't connect. It always worked on my myTouch and once on the Vibrant.
Sent from my Samsung Vibrant using the XDA app
Tmobile Galaxy S pattern locked out, can't root
I just bought my first Android device, the Samsung Galaxy S from Tmobile from the US (I live in China) last week. I have only used it a few days and my girlfriend thought the pattern lock would be a fun game to play. Result - locked out. I have the same problems as in the below thread:
http://code.google.com/p/android/issues/detail?id=4784
I tried the receive a phone call then hammer the home key; emergency call and go to search and many of these type fixes; however none have gotten me through. It seems they fixed the security problem here but didn't fix the username password problem as I'm sure the credentials I entered are correct and I have data service.
After giving up on these methods I tried doing a hard reset. BTW, on this model you must hold down volume up AND down buttons at the same time, then press the power button to get the reset screen.
I have cleared user data etc, but when I try to reset the phone I get the error message "setup.zip not found".
I understand that I now need to root the phone, so I tried the method explained here but without having access to the phone I need to load this setup.zip file on the SD (not the one with Avatar).
http://samsungvibranthacks.com/samsung-vibrant-hacks/how-to-root-samsung-vibrant-galaxy-s/
I already installed Kies (has Outlook sync functionality!) on my desktop so that I can access the internal memory as an external drive. However the phone's USB mode must be set to (it will prompt whenever I connect) to Kies mode. However since I am locked out of the phone I can't tell the phone to get into Kies mode, therefore cannot access the internal memory, therefore cannot load setup.zip, therefore cannot root, therefore cannot get past the pattern lock screen = useless phone.
I need to root the phone anyway so I can load a few Asian IME's that didn't come with the phone so don't mind playing with this, but since I'm new to Android it may be a while before I can get through since most root instructions either require access to the internal memory via my computer or access to the phone (past the pattern lock).
If I offer to make a paypal donation could I summon the help of one of the more experienced Android gods that frequent this forum that can help me get through this?
To use odin you need to get into download mode not recovery mode (Volume Down+ Power) but since for some reason that wont work for you, you will have to do something involving the android sdk do you know how to use it?
Genesis1791 said:
To use odin you need to get into download mode not recovery mode (Volume Down+ Power) but since for some reason that wont work for you, you will have to do something involving the android sdk do you know how to use it?
Click to expand...
Click to collapse
On one or two tries, when the device was attached to my laptop I got a yellow on black downloading screen but had no idea what it meant. How does this help me root it? In general the volume down+plus power button didn't do anything but reboot it.
I just downloaded the SDK last night for the last time and haven't succeeded in installing it so have still got a bit of learning to go before I can make it useful.
I have the phone back in my hand now so adding some details:
Holding volume up and down and the same time, then pressing powere gets me to the "Android system recover <2e>" screen with four options:
Reboot system now
reinstall packagages
delete all user data
delete cache data
I've tried all and none will get me out of the username/password screen after reboot. If I select "reinstall packages" it says:
E:can't open /sdcard/update.zip
(No such file or directory)
Installation aborted
Hey,
Yesterday I upgraded my gf's GT540 to 2.1 (v20B) (fooled around a bit with the no-logos-showing-at-boot error but got rid of that bug eventually by KDZ software upgrade) and later I tried fixing the "can't establish a reliable data connection to the server" bug by deleting the file located at /data/data/com.android.providers.settings/databases/settings.db. After a reboot, I got stuck in an infinite boot loop of the Android logo. No matter what update I reflashed, I was stuck with the infinite Android logo. I kind of fixed that problem by adb-ing inside the phone while the loop was going on and I tried to recursively delete everything in /data/data/.
Now, no matter what update I KDZ, every boot gives me constant "The process _________ has stopped unexpectedly...". I think the files are missing but I don't quite understand why, the updates should totally wipe everything from the device and then create a new file system bla bla bla... It's like no matter how I apply any update, or do a bunch of hard resets, it doesn't do anything to the phone.
BTW I haven't tried fastboot stuff (simply because holding the camera + power doesn't take me to fastboot for unknown reasons), and I don't know about the windows enabler or where to find it.
I spent like 10 hours trying to unbrick this phone and searched everything everywhere now and I am getting really annoyed and confused with what's going on so please somebody throw me some tips before I nail this device on the wall...
Damn, everything is so much easier with HTC devices...
Thanks for every chunk of info,
Jay
You can try to do a hard-reset - http://www.hard-reset.com/lg-optimus-gt540-hard-reset.html
PS. To turn on fastboot mode you should press Power (and hold it until the phone vibrates) and then press and hold Home button. Fastboot mode is just a black screen (there won't be any text displayed).
hash87 said:
You can try to do a hard-reset - http://www.hard-reset.com/lg-optimus-gt540-hard-reset.html
PS. To turn on fastboot mode you should press Power (and hold it until the phone vibrates) and then press and hold Home button. Fastboot mode is just a black screen (there won't be any text displayed).
Click to expand...
Click to collapse
I did at least 10 hard resets.
Holding the home button doesn't give me fastboot mode, it boots Android into safe mode...
PS: Somehow I have lost the ability to use ADB, which is quite annoying.
I forgot to mention - fastboot mode works only if you've ROM with fastboot - http://forum.xda-developers.com/showthread.php?t=828003
hash87 said:
I forgot to mention - fastboot mode works only if you've ROM with fastboot - http://forum.xda-developers.com/showthread.php?t=828003
Click to expand...
Click to collapse
Thank you I have managed to get to the blue FASTBOOT screen! Now I have a device named Android in the Device Manager, but I do not have drivers for it so fastboot console application is still stuck at < waiting for device >...
The drivers for fastboot installed for me just fine using windows update. You can also try drivers from this link: http://www.speedyshare.com/files/24707580/android_usb_windows.zip or http://pdanet.co/bin/PdaNetA245.exe
hash87 said:
The drivers for fastboot installed for me just fine using windows update. You can also try drivers from this link: http://www.speedyshare.com/files/24707580/android_usb_windows.zip or http://pdanet.co/bin/PdaNetA245.exe
Click to expand...
Click to collapse
Thank you, you are the hero of the day! Now I have succeeded in flashing back the v20a firmware!!
[Q] Download mode "do not unplug the device until the process is complete..."
i boot on this for axident and i cant exit, some one know how to exit this download mode ??
and try various combinations of keys and nothing
javier.aguilar said:
i boot on this for axident and i cant exit, some one know how to exit this download mode ??
and try various combinations of keys and nothing
Click to expand...
Click to collapse
long press the power button(10-20 seconds), this will force reboot the phone.
What exactly is this download mode? I just had it and it looked unofficial like spyware or something?
cable_guy said:
What exactly is this download mode? I just had it and it looked unofficial like spyware or something?
Click to expand...
Click to collapse
its *almost* same as Samsung phones, its a mode that allows *almost* full reflash of your phone, from partition table to bootloader,system etc.
in the n4 we use lgnpst instead of odin for Samsung phones. its not spyware or something like that, its from the backup bootloader(abootb), can be automatcly triggered if aboot fails to start, or if the user press a combination of buttons.
also if you get in that situation, you may find qpnst mode, its a even more emergencial mode(in this case, even abootb is failing to start, screen dosent turn on, and its recognized as QHUSB_DLOAD on pc), but at moment we can´t do much on this mode,we use qpnst (from QUALCOMM instead of lg) to re-program the full nand(the program pulls imei data, then the nand turns full writable, all blocks are writable, then the program re-programs it, sends new partition table, etc....). you may find more on the "How to unbrick your N4 using LGNPST" thread and the "Unbrick N4 using QPNST" thread.
opssemnik said:
its *almost* same as Samsung phones, its a mode that allows *almost* full reflash of your phone, from partition table to bootloader,system etc.
in the n4 we use lgnpst instead of odin for Samsung phones. its not spyware or something like that, its from the backup bootloader(abootb), can be automatcly triggered if aboot fails to start, or if the user press a combination of buttons.
also if you get in that situation, you may find qpnst mode, its a even more emergencial mode(in this case, even abootb is failing to start, screen dosent turn on, and its recognized as QHUSB_DLOAD on pc), but at moment we can´t do much on this mode,we use qpnst (from QUALCOMM instead of lg) to re-program the full nand(the program pulls imei data, then the nand turns full writable, all blocks are writable, then the program re-programs it, sends new partition table, etc....). you may find more on the "How to unbrick your N4 using LGNPST" thread and the "Unbrick N4 using QPNST" thread.
Click to expand...
Click to collapse
thanks very much for the informative response!!! I wonder if it rebooted in the night and couldn't boot back up properly. It's stock by the way!! Thanks again though for taking the time.
cable_guy said:
thanks very much for the informative response!!! I wonder if it rebooted in the night and couldn't boot back up properly. It's stock by the way!! Thanks again though for taking the time.
Click to expand...
Click to collapse
probably some wakelock crashed, then system rebooted but battery couldn't handle it(low voltage) so it gone there? idk, if it happened one time, then its nothing to worry
Hello, about a weekago I've installed dorimanx kernel for my D802 and today I realized that it made my 3g connection unstable
I decided to flash back to the stock kernel which I backed up before flashing dorimanx, but something went wrong. I really don't know what.
The phone won't turn on, it keeps showing LG logo and showing Secure booting error. Cause: boot certification verify. (1001)
I tried pretty much everything in the past 6 hours and i'm losing my mind.
LG PC suite or any LG pc software won't recognize the phone when plugged with USB, and everytime I plug in the phone to my PC windows opens 15 boxes of "new hard drive detected, format needed to use" (here's a picture)
Also tried following this post: http://forum.xda-developers.com/showthread.php?t=2582142, but no luck. It seems like my dev folder is missing alot of sub-folders for some reason.
Anyway I'm really lost. Can you guys please help me to solve this? I would really appreciate it.
Thanks.
To be sure, have you already tried to get into TWRP through the factory reset key combination?
I tried almost every combination possible. the phone simply resets itself to the same situation, screen is on but black and nothing else happens
After holding power+down buttons the LG logo comes up and disappears in a snap, like something is wrong.
Nightbeat said:
I tried almost every combination possible. the phone simply resets itself to the same situation, screen is on but black and nothing else happens
After holding power+down buttons the LG logo comes up and disappears in a snap, like something is wrong.
Click to expand...
Click to collapse
Your device is unplugged while you do this right? It has to be completely turned off before doing the combination, and while plugged in, it just doesn't turn off completely.
Yes, it is unplugged while I do it
You'll need to hold the volume down + power key as you turn the phone on, then re-press them when the LG logo shows up to get to the factory reset page. Just verifying the simplest solution before I go in depth with this.
If your phone still won't get into TWRP, try this: plug the phone in to your computer, and open device manager (right click computer > manage) and under portable devices, locate your phone. Once you find it, right click it, click uninstall, and once that's done, unplug your G2 and reboot the PC. Once it boots up, plug your G2 back in and let it reinstall the drivers and try to do the guide again. Best of luck!
EDIT: I just realized the guide you are looking at requires Ubuntu. Are you aware of this?
double edit: http://forum.xda-developers.com/showthread.php?t=2432476
Let me know if you've tried this guide yet.
I believe you're using vistual machine for ubuntu.
Well, if you keep getting 15 messages about formating drives (in windows) when you plug your phone to ubuntu you will not get your patitions in ubuntu.
So you should close the messages asking you to format drives, then open vmware in full screen mode, then plug your phone to computer and follow the guide http://forum.xda-developers.com/showthread.php?t=2582142. I'm sure in this case you will get your phone partitions showing is dev/sdb.
Even if you don't get those partitions keep trying several times untill you succeed.
Good luck.
Thank you!
Apparently I was using the key combination wrong.
And yes I was using ubuntu on a VM.
Nightbeat said:
Thank you!
Apparently I was using the key combination wrong.
And yes I was using ubuntu on a VM.
Click to expand...
Click to collapse
Had a feeling! Glad you fixed it!
Two days ago my wifes 1st generation Nexus 7 refurb started giving the "Unfortunately, NFC service has stopped" error. You click OK and the error instantly pops up again. There is a moment to click on something if you're fast and I've been able to click on settings but when settings opens it's nothing but a black screen with no options. This means that I can not enable usb debugging. I have tried quite a few different processes, ADB sideload, going through the bootloader, but they all seem to require usb debugging and the tablet is never recognized. The tablet is stock but I have no way of knowing what version of android it is currently running with the blank settings window (unless you can give me a tip on that). Have done two wipe/factory restores on it and the error comes up right at the first boot screen. I am willing to pursue any option to get this tablet in working order. Rooting, flashing, whatever but I am a novice in the world of android rooting. It was purchased off groupon (won't make that mistake again) and the 14 days are past so If I have to send it in, it's cash money out of our pockets.
Do I have any options? Thank you for your time!
Most frustrating of all is that everything else about the tablet seems to be functioning normally. I can install apps from google play. I can't really run many of them though.
notnorm said:
Most frustrating of all is that everything else about the tablet seems to be functioning normally. I can install apps from google play. I can't really run many of them though.
Click to expand...
Click to collapse
If the tablet has never been rooted, and the factory reset procedure seemed to complete successfully, then your symptoms suggest that something is wrong with the /system filesystem - which, for stock devices is never modified (always mounted read-only).
So that in turn suggests *perhaps* flaky hardware - probably the flash memory chip - that has gone awry and is the root cause of the problem.
It is conceivable that you could go through the process of unlocking the bootloader and re-flash a Google-provided "factory image", and that the problem will go away. But if the root cause is really a flaky flash memory chip, it will very likely return with a vengeance, and your efforts will be for naught.
There is something missing in your narrative, however - if the appearance of the "NFC Service has stopped" dialog on-screen prevents you from interacting with your (intended) foreground apps, how were you able to perform a factory reset and then follow that up with a tablet configuration? (e.g. to get Google credentials on the tablet so you could push apps to it by using a PC Web browser from the Google Play market).
If you are unfamiliar with rooting but still want to proceed with reloading the factory images, you will have to follow the Stock Recovery tutorial threads. Many users - especially those with Windows machines - seem to get stuck at this step, although truth be told that has nothing to do with Android, and everything to do with Windows Driver Installation Hell.
Note - specific to your situation.. You do not need to enable USB debugging to re-flash factory stock images. You only need to communicate with the device (booted into bootloader mode) with the "fastboot" program. For this you only need working USB hardware - not "adb".
good luck
BTW, note that you can perform a factory reset in the stock recovery without launching it from the O/S. The sequence is:
1) Turn the tablet off (not screen off, but powered completely off)
2) Boot into bootloader mode by holding Power+Vol-Down together (hold them down until android lying on its' back shows up - about 4 seconds)
3) Using the vol-up/vol-down button, select "Recovery Mode" on screen and press the power button
At this point the screen will go black. Wait about 10-13 seconds. The screen will remain black even though the stock recovery is now running. To get the screen to show the (stock) recovery menu,
4) press and release the Power & Vol-Up keys simultaneously.
The stock recovery menu should show now up. If it doesn't, try again. (After 60 seconds if you have done nothing, the tablet will reboot to the "normal" OS).
5) Use the on-screen menu to perform a factory reset (follow the directions on-screen for key usage).
Thank you so much for your response! The unanswered question is that I managed to put in the network info and what not during setup by hitting OK on the error and tapping the letter in the moment before the error popped up again. Not a fun task!
I've been trying to flash and after installing the google usb drivers it's still doing the <waiting for device> for infinity. I think I will have to bite the bullet and send it in. You saying that it might be a flash chip is kind of comforting because I think I might have bashed my skull against this issue forever before giving up!
Chris
flashed the wifi fix for the TMObile us version (from the X Note rom page)and was able to get out of the loop.