So here is something interesing. I've head of phones hangning and boot loops, etc.
So, let me reverse this abit and see what everyone thinks. If my phone is turned on, but my laptop off, when I go to boot my laptop with the phone plugged in (its always in development mode never auto mount) my laptop hangs at the windows boot animation screen, at least til I unplug the phone.
I've tried this with various roms on the phone, another android phone (HTC aria), and even my nook color. Its only limited to the android phones, as it doesn't hang with the nook color.
I'm wondering why android phones would be causing windows to get stuck on the boot screen. Any idea's?
Try checking the bios settings to see if usb is first on the bootlist or at least before it boots from harddrive. If so, change them.
My computer wrong shut down correctly if my phone is plugged in, what it does is it recognizes it as hardware and tries to user it as hardware, which it can't
Your welcome
Now you say/press thanks
Teaching manners one person at a time
wow thats weird. i have my phone plugged in and it does boot in windows with no problem. what windows are you using? and maybe there is a bios update or contact the manufacturer tech support and ask them about the problem
Im using windows vista 32 bit
Your welcome
Now you say/press thanks
Teaching manners one person at a time
Related
Bad news today :
Wanted to revert to ThaiHugo's light ROM.
Booted Windows 7, executed CustomRUU. After 1 minute, before
the real transfer of files begins, Shift BSOD in Windows 7.
No sweat, I thought, just reboot Windows 7, and hope that WinMo ROM wasn't touched yet.
However, even after removing the battery, Shift won't go to Bios, nor will it boot Vista. After power on, the HDD clicks, and that's it. If I wait long enough, the Fans will start blowing air.The power indicator is on, and the HDD led never flashes....
The WinMo part can be seen to work, albeit very rarely.
So now I'm stuck with an unbootable Windows 7, as it won't even do BIOS, and without WinMo.
Anyone else suffered from this and how did you recover ?
I'm glad it's a 2 year warranty, would have gone ballistic !
lucid said:
Bad news today :
Wanted to revert to ThaiHugo's light ROM.
Booted Windows 7, executed CustomRUU. After 1 minute, before
the real transfer of files begins, Shift BSOD in Windows 7.
No sweat, I thought, just reboot Windows 7, and hope that WinMo ROM wasn't touched yet.
However, even after removing the battery, Shift won't go to Bios, nor will it boot Vista. After power on, the HDD clicks, and that's it. If I wait long enough, the Fans will start blowing air.The power indicator is on, and the HDD led never flashes....
The WinMo part can be seen to work, albeit very rarely.
So now I'm stuck with an unbootable Windows 7, as it won't even do BIOS, and without WinMo.
Anyone else suffered from this and how did you recover ?
I'm glad it's a 2 year warranty, would have gone ballistic !
Click to expand...
Click to collapse
Did you try to downgrade to Vista and try to flash the original SnapVue?
Can't even get to the BIOS
I cannot try much anymore... device just won't boot to the bios. Only the powerled is working.
So if I take out the battery, and unpug the powercord, and wait 10 minutes, my device should at least show the bootscreen and BIOS, it doesn't.
Strangely, WinMo once in a while does fully boot, regardless the fact that the other side is "dead"
A very very peculiar problem, it seems that the BSOD while flashing a ROM has locked the EC controller and my Harddrive permanently.
I've been playing with computers for 30 years now, this one is ODD, really really ODD.
Frak, now that SD and BT will be out, my shift will be in for repairs.
lucid said:
I cannot try much anymore... device just won't boot to the bios. Only the powerled is working.
So if I take out the battery, and unpug the powercord, and wait 10 minutes, my device should at least show the bootscreen and BIOS, it doesn't.
Strangely, WinMo once in a while does fully boot, regardless the fact that the other side is "dead"
A very very peculiar problem, it seems that the BSOD while flashing a ROM has locked the EC controller and my Harddrive permanently.
I've been playing with computers for 30 years now, this one is ODD, really really ODD.
Frak, now that SD and BT will be out, my shift will be in for repairs.
Click to expand...
Click to collapse
Can you do a Fn>F10 to boot from a cd drive? If so, boot your Windows 7 from the cd to do a repair....That's what I had to do.
Earlier today i was on the samsung website to download some drivers which i think was needed to speed up the boot on of my samsung nc10 netbook. This was mainly because after downloading windows 7 yesterdayi i had a lot of drivers to re-install from the samsung download centre. I noticed during the booting up my laptop that it delayed pn a black screen for a VERY long time before entering into the desktop. I spent hours trying to fix this in device manager, command prompt etc. Nothing worked. When i read on a forum that bios updates might be needed to help windows 7 run better i chose to download one. As the bios update was downloading from the samsung website, after about five mins i noticed the computer had frozen. tried moving the mouse, ctrl alt etc. but nuthing worked. I was very worried when i pressed the power button and the computer did not go off. As i proceeded to take out the battery from the bank i muttered 'nice knowing you laptop' cos i kinda sensed it was a very bad thing about to happen. Took out the battery for a few mins and put the computer back on but it would not switch on. It just showed a blue indicator light and it hasn't come on since then. I can't help but wonder if those 20 delayed seconds during boot was really that intolerable, i should have just left well alone. The poor baby is only a few weeks old and already its met the end. Does anyone know if a laptop can be recovered from an error during bios update? thanks for ur help
I have never seen a laptop that has been able to recover from a Bad BIOS flash, and unlike a Desktop PC it is a bit harder to open it up and change the BIOS ROM chip (containing the EEPROM). Some laptops and computers have the BIOS chip soldered onto the motherboard so you can't just change it (grr).
I would advise you take it back to where you bought it, but be careful with what you tell them happened. Sometimes businesses like to charge you if you were the one that played about with the BIOS, which is kind of annoying since its not exactly you that wrote the BIOS flashing software..
U're very right about not being to quick to state i'd be downloading software. I noticed there is a disclaimer on their website stating they are not liable for any issues caused by changing software. Nice to have seen that cos when i rang them up i just said the laptop won't turn on for some strange reason They agreed to book it in to their service center
you are correct!
if you search in the web of american megatrends maybe you can found a DOS app called something like low application that can helps you to restore a corrupted bios.
My jobs pc has the bios corrupted because of a worm its a vaio so... al the drivers needs to read the model ID and... the model has beendeleted! unbelievable but true the IT technician tells me that he needs time to try that app cause he never do it but he say it will makes the trick.
Try it you cant loose anything more... or take it to the seller and ask him for the service center.
If it uses Phoenix BIOs then you can use an emergency flash disk. I've successfully used it to recover my HP DX6000 after I borked a bios hack to remove a WiFi whitelist.
ok, i am hopelessly stuck. I ran the unlocker and after I click the last button to start the process, it says it cannot read a file. Anyways, I check to see if it worked by chance, and it does say security unlocked. But every time I try to flash a rom from the computer it starts and gets to the point where my phone goes to the color bar screen and says usb at the bottom, then it tells me that it cannot communicate with my phone???HELP
Edit: Really Guys??? I have posted twice here, I have been in the android forums for a long time and I can get a response to anything there in 5 min., I thought this was part of our community but I guess I was wrong.
matthewjulian said:
ok, i am hopelessly stuck. I ran the unlocker and after I click the last button to start the process, it says it cannot read a file. Anyways, I check to see if it worked by chance, and it does say security unlocked. But every time I try to flash a rom from the computer it starts and gets to the point where my phone goes to the color bar screen and says usb at the bottom, then it tells me that it cannot communicate with my phone???HELP
Edit: Really Guys??? I have posted twice here, I have been in the android forums for a long time and I can get a response to anything there in 5 min., I thought this was part of our community but I guess I was wrong.
Click to expand...
Click to collapse
I haven't had this problem, but is the driver installed for when it is in the bootloader screen?
Another way you could try is flashing it from bootloader mode. Just go into bootloader mode then plug it into your comp and run the romupdate utility.
Odd
Never personally ran into it but check your USB cable. Try a different cable. Try a different USB port. I had some issues with them being a little touchy.
I dont know if anyone cares, but I figured it out. I am using a Early 2010 Model MacBook Dual Core running Parallels instead of dual-booting Win XP.
When I am in Windows XP, OSX is running in the background, when the rom update utility turns the phone off then on into the bootloader, the phone is off for that split second and parallels cant keep up with it, and the Mac trys to grab the USB connection in that split second before Win XP says "No, thats my connection", so in that split second exchange the connection with Windows and the RUU gets droped! Kind of simple once you know whats happening. No matter, I used my brother in-laws Vista Toshiba( infected with viruses to the max), it worked fine and I am now running Moonscapes 1.6 with android as well! Thank You to the people who took the time to help!! Remember guys this is a community, it doesnt work unless people respond, without participation we may as well be talking to our dogs!
You never mentioned you were doing something crazy like trying to flash your phone from a virtual machine. That never works, because the usb passthrough driver doesn't detect the windows low-level bootloader mode. How are we supposed to help you when you don't provide details?
Lol, my bad, I got sloppy!! My son dumped a Sonic drink on my dell so all I could work with was my trusty Mac, I am going to dual boot it later today. I have to say after a day with Moonscapezx's 1.6, I like WM, dont know if I like it enough to swap it out for good, I still love my Hero(at least for another 3 months when I get an upgrade, EVO!!!). Ok, well Thank You again guys, I love XDA, you guys are great
Alrighty, folks. I've searched the far reaches of the internet, gone through hundreds of pages on this forum alone, and I think I may just have a different set of issues than most.
The symptoms: Long-time thought-to-be-bricked TouchPad with partition for WebOS and Android... Jelly Bean? I think? so long ago... ended up not being bricked, but rather in need of the factory original charging cylinder for proper power flow. When I got it back in somewhat working order, it, PROBLEM 1, got stuck on the Android loading screen (where the word "Android" gets repeatedly swept across with shininess - remember, this is OLD) and never budged from there. I've restarted it who knows how many times by holding down the power and home buttons. I can scroll through the menu with the volume keys, can load WebOS perfectly fine, can launch Android, but it just stays on the loading screen.
Obvious choice is to wipe the whole deal and start fresh. No worries. Except I wanted to get some design sketches off of it, and, PROBLEM 2, my computer was no longer recognizing it as an external drive, or anything, really. I've looked at darn near every "computer won't recognize TouchPad" thread I could find over the past 14 hours. Finally found one with the driver software that could have been my missing link, and my computer won't accept it as a driver. This is a whole other can of worms for someone who has the patience. I will admit that the one fix I haven't tried for this is using a factory original cable. That cable was awful and it broke on me a long time ago. I will try another cable tomorrow, though, as I'm traveling and only have one on me now.
I managed to get my pictures etc off of the TouchPad by booting WebOS and putting it into USB drive mode there (which my computer magically reconizes ). However, I still can't access files in the standard recovery mode to actually do any wiping/software things. I'm well aware that the solution is to go to The Three Dots and switch that developer slider so that my computer knows what's what, but sadly I can't get to the settings menu. There must be another way.
I discovered just a bit ago that I can boot into ClockworkMod; however, I'm not really sure what to do once I'm in there. I can do a factory reset, yes? Would that help?
TL;DR
TouchPad which cannot connect to computer will load everything but Android.
WHAT I'VE TRIED: booting partially through WebOS with WebOS Doctor running and then trying to pick up the connection with TPToolkit when the Dr recognizes the WebOS side of things, new drivers, sacrificing a goat and doing a ceremonial dance around it, etc.
GOALS: Get TouchPad recognized as a USB drive, using ClockworkMod, which is apparently the only thing I have going for me.
Any and all help gratefully accepted. Thank you all in advance!
Hello everyone,
Having major issues with my Idol4S. It is the unlocked version (Cricket). It was working just great until a few days ago when I plugged it into the car charger. Phone instantly shut off, and got stuck with a blinking (rapid) LED light. This happens if plugged into my PC, or my Alcatel charger (both the wall and car).
The phone has suffered no damage (had a cover, but it was never dropped or exposed to external weather damage, nor water - I took great care of it), and was working quite well. I'm unable to boot it into any sort of recovery mode (as the screen is black, so I wouldn't be able to see anything anyways). The only indication of life is the flashing LED when plugged in ..(charging loop, maybe?)
I am using my idol4S Win10 (TMO/unlocked) phone in the meantime, but the base model was working just fine before this happened. I was also mindful of checking voltage/Amps when using chargers, so I would not have exposed it to any incorrect input/output. QuickCharge worked great too (sorely missed on Win10 model).
The phone was never rooted so it has the stock ROM, and whatever the last update Alcatel had pushed out for it. I did have developer mode and USB debugging on for MSVC/NSDK.
Is there anything I can do? After awhile being plugged in, the LED shuts off. I kind of need it as I was porting my game engine to it (using the SDK), plus it was my primary. I love the Win10 version too, but the Android idol4S was my primary phone. Kind of disappointed in Alcatel - I read it doesn't have an external battery otherwise I would attempt to transplant the battery (if that is even the issue). . .
Any tips, advice, or suggestions would be greatly appreciated! <3
what you describe is what the phone does when it's plugged into the PC in download mode. Since you have the Cricket version which is also what I have, it is very easy to start from scratch and reflash everything. I have released a newer version TWRP and also have the ~CricketRom~ available if you're interested.
PizzaG said:
what you describe is what the phone does when it's plugged into the PC in download mode. Since you have the Cricket version which is also what I have, it is very easy to start from scratch and reflash everything. I have released a newer version TWRP and also have the ~CricketRom~ available if you're interested.
Click to expand...
Click to collapse
Okay, but would it work even though the phone gives no indication of being plugged in to the computer, or the chargers for it? I plugged it into the PC just now, brief flash of light and then nothing. .
Should mention again that the screen does not turn on, ever since that day, the screen has not came back on -- so I really can't do anything, even accessing 'download mode' does not show anything on-screen, nor does Windows 10 alert me of the USB device being connected.
I wouldn't mind starting from scratch at this point. I'm definitely interested in getting up and running again! It's not like I can do anything else at this point except spend money and get it repaired by TCL.
Would it be rude of me to ask for links to the TWRP/CricketROM from you? Maybe a quick-start guide, I pick up on things easy, but I've never properly flashed with TWRP =)
Also @PizzaG, THANK YOU for your help!! Definitely appreciated <3
Oh! @PizzaG, I also have an older Onetouch Idol 3 that has the _exact_ same symptoms, I wonder if that too could be recovered? ... ^__^
well I guess the first thing to do would be plug it into the PC. Hold volume+ and volume- then hold power until you feel the buzz and let go of power. Hopefully you get the red Download mode screen? I didn't realize it had no life at all, I thought it was just messed up. It's sounding like more may be wrong then just a simple reflash.
New TWRP and ~CriketRom~ Beta5: https://forum.xda-developers.com/idol-4s/development/rom-twrp-recovery-t3792659