I attempted to update the BIOS on my HP iPAQ hw6940 mobile messenger by downloading and installing the update from hp.com. I discovered during the process that the USB cable I was using was not properly powered and the update failed. The device remains in a serial connection mode and cannot be reset or restarted. The screen is dimmed and displays “serial v.g.39”. Even after solving the USB power issue, the BIOS updater was unable to connect to the device. Syncing through MSDC also fails. Is there a way I can restore connectivity to the device so that I can complete the BIOS update?
jaydee08 said:
I attempted to update the BIOS on my HP iPAQ hw6940 mobile messenger by downloading and installing the update from hp.com. I discovered during the process that the USB cable I was using was not properly powered and the update failed. The device remains in a serial connection mode and cannot be reset or restarted. The screen is dimmed and displays “serial v.g.39”. Even after solving the USB power issue, the BIOS updater was unable to connect to the device. Syncing through MSDC also fails. Is there a way I can restore connectivity to the device so that I can complete the BIOS update?
Click to expand...
Click to collapse
Hi, i used to have the same problem........ keep following full restall step again. Restart comp, reconnect Ipaq, 4 buttons your ipaq, make sure all connectons is secure before trying the installaton again. Hp hw6900 series have a "fail safe" rom unlike newer models that why you get the the display Hp logo, V G 0.39, etc. ALL you have to do is reinstall the rom......... if it does not work again, take a 6-24 hrs rest, drain the battery, take out the battery from the ipaq. after 24hrs, place everything back to normal and retry. keep trying till you get the loading........... Happy if you see the loading, dont touch anything til its complete this time.....
enjoy cracking your ipaq... be patience with this ipaq, it has a weak heart
Thanks.
I managed to successfully restore the BIOS via USB by downloading and installing the update from HP.com on my Vista machine. It didn't work from an XP machine, which is what others including HP told me I needed.
Interesting that the 24 hr break and battery drain actually seemed to have had an effect. A weak heart indeed, but not a bad little device. I'm happy to have it back.
Thanks again.
If you want to offer help PLEASE read through the thread, or at least the initial post. It seems like I'm repeatedly answering the same questions that were already answered.
I've tried to boot in APX and all I get is the black screen, yet neither Windows 7 64bit/Linux Mint 64 on one PC and Windows XP on another don't detect it at all. I know the cable works because when I had CWM installed I could see it attached via ADB. I'm a b30
Edit: I managed to get the stock ROM back on it, but it still doesn't want to boot into the bootloader/APX mode. I know it's not necessary but I would like to have it as a failsafe for the future.
brando56894 said:
This all started with me wanting to go back from AOKP to stock, I flashed a rooted version of 9.2.1.17 and it kept telling me to update, but when I did it failed because CWM was installed. It also wiped my system. I found 9.2.1.24 but couldn't flash it because TWRP wouldn't stick. I tried to install the stock recovery, which worked in a sense that it removed CWM but left me with just the Android and the exclamation point (I can't seem to get past that no matter what I do [vol +, Vol -, power or any combination of those] ) I decided to use NVflash to get back to complete stock and start over.... The only problem is that Windows 7 doesn't even detect the TF when its in APX mode, hence it doesn't ask me to install the drivers, nor will they install manually.
So my TF is soft bricked and nothing works. I'm going to reboot into Linux now to see if I can get nvflash working. Any other suggestions?
Edit: Linux Mint didn't detect it either I know it's not the cable since I was able to see the TF via ADB when I had CWM installed. Also the major thing that is worrying me is will the TF be recoverable if the battery dies? I have no way of knowing if it is actually off or just in APX mode, I obviously can't do a battery pull and I can't power it down from the recovery or the OS. IIRC it also won't charge when it is in recovery and I'm assuming the same is true for boot-up and APX mode.
Click to expand...
Click to collapse
Same to me-- win7 does not recognize my tf 101- apx is installed-works with another transformer well- if i do vol down and then vol up i see the laying android with exclamation mark.
no solution till now- hope you had more luck-
By the way- try to load it normal - in my case it works.
kind regards
gandalf
I just tried connecting it to an older Dell with a P4 in it and it doesn't detect it either, it just seems like the TF doesn't want to boot into APX mode. I'm doing Vol + and Power from both the recovery and from the initial splash screen, then it reboots to a black screen which I'm assuming is APX mode. From the black screen I've tried Vol + and Power for as long as 30 seconds and still nothing. There were also times when it would sit at the initial splashscreen and then go to a black screen, then I'd try to enter APX mode from there but it would be the same thing.
I've been contemplating getting a Nexus 7, partially because I lightly stepped on the screen of my TF one night and damaged it enough to cause the LCD crystals to break (there about two or three grayish "lines" where I stepped on it) but not hard enough to crack the glass. The screen will also flicker some times on that side and will also randomly shut the screen off. Maybe this is a sign telling me to get a N7?
Do you have debug mode enabled?
Where did you get the win 7 APX mode software. Some links in this site are to defective software. Go to the SDK kit site and download the software there. http://developer.android.com/sdk/index.html
Rumbleweed said:
Do you have debug mode enabled?
Where did you get the win 7 APX mode software. Some links in this site are to defective software. Go to the SDK kit site and download the software there. http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
Debug mode is for ADB, not APX. Debug mode is set in Android and with APX no Android is loaded.
I have used the live cd of Ubuntu 11.10 without installing any driver by myself. It recognized the TF with APX in my case.
There is no debug mode considering that the OS isn't installed. AFAIK debug mode is only necessary to use ADB while booted into Android. APX is something that is built in to the device. I downloaded the drivers from android.mobi which has an "unroot/unbrick" package, that doesn't matter though because Windows never asks me to install the driver so the drivers don't seem to be the problem, considering Linux (which doesn't require any drivers) doesn't see the device either.
I had the same, downloaded the drivers, but couldn't install.
After I made sure I had the correct drivers, I clicked in hardware settings on the thingy with the exclamation point, I choose manual search and had Windows search the entire c:\ drive, after a while it installed
Sent from my Transformer TF101 using xda premium
That's my problem guys. APX mode/unknown device doesn't show up in device manager
oi, than I cant help you, sorry
I think it's F'ed because I took it apart to make sure it was turned off by disconnecting the battery and then did the power and Vol+ combo but the PC still doesn't detect it.
1. your battary is empty, charge it
2. your battary is done.
3. your power key or vol-up key do not work.
4. you did not press two keys in the same time long enough
5. cable doesn't work
6. usb port doesn't work, try another one.
7. you did not pay attention on the sound of device connected nor the device list.
8. your windows broke. try another pc.
---------- Post added at 11:39 PM ---------- Previous post was at 11:33 PM ----------
get a micro sd and copy rom to it and flash, since you said cwm works ok
vista1984 said:
1. your battary is empty, charge it
2. your battary is done.
3. your power key or vol-up key do not work.
4. you did not press two keys in the same time long enough
5. cable doesn't work
6. usb port doesn't work, try another one.
7. you did not pay attention on the sound of device connected nor the device list.
8. your windows broke. try another pc.
---------- Post added at 11:39 PM ---------- Previous post was at 11:33 PM ----------
get a micro sd and copy rom to it and flash, since you said cwm works ok
Click to expand...
Click to collapse
1 & 2 It boots up to the initial splash screen and to the android recovery so the battery is ok
3. The Vol + does work unless it suddenly died because I was using it moments before I bricked it
4. I would say 30+ seconds is long enough
5. The cable does work because it charges the unit and when I had CWM installed I could see it via ADB
6. Tried another port, nothing
7. The sound is definitely noticeable and it's kind of obvious if it's not in the device manager list
8. I tired two different computers, and three different operating systems. Including Linux.
I know you are trying to be helpful but ALL of these were answered in previous posts, if not the OP.
I'm having the same issue with my pad not booting into APX, might I ask how you got the stock ROM back on it without APX?
Luckily I had the stock recovery installed and I was able to place the OTA on A MicroSD card and named it so that it would flash automatically once I booted into the recovery.
Sent from my Transformer TF101 using Tapatalk 2
Edit: here's how to do it
baseballfanz said:
Download the latest official firmware from Asus.
Extract the zip from within and rename it to "EP101_SDUPDATE.zip" (without the"" )
Put it on the root of your sdcard
Boot into stock recovery and it should flash it
Click to expand...
Click to collapse
I have to go with #5. My Transformer would charge when using my cord and so I thought it was good. Plugged it into the computer and nothing. Switch to my wife's cord and the computer saw it instantly. It was then able to see APX mode.
Yea it was actually the cord being stupid, when I got back to my house I tried my other cord and it connected just fine. I actually just sold my TF yesterday to a friend for $250 so that I can get a Nexus 7
Sent from my ADR6425LVW using Tapatalk 2
So this is making me thing that my cord is the issue, but I tried 3 different cords and none of them recognized. Is it possible the device itself has a faulty connection?
It's entirely possible, have you tried a different computer/different USB ports first though?
Tried every port on two machines as well as in linux. My HTC G2 connects just fine to everything.
You may be screwed Do you have the dock? Does it connect and charge fine with that?
Just wanted to share how i unbricked my A500 .
I bought an A500 that was stuck on android boothoping i could fix it .
Vol+/Power gave me an " unrecoverable bootloader error (0x19000008)"
Vol-/Power tried to boot from recovery but after a few seconds got the dead android with red triangle
tried various flash mode with device recognised as "acer picasso boot recovery device" to no avail ,
with A500 connected to pc in boot loop windows(7 x64) was looking for "MTP" driver which it could never find , DESPITE me having installed AND reinstalled usb drivers numerous times AND trying to manually force which driver windows used .
i even tried putting various stock roms on an sd card to try and force an update . No joy .
i had also left device in bootloop overnight hoping something would kick in , again to no avail . the only thing that did appear to help was blackthund3r's " ICS Root 7.1.1. " which got rid of my "unrecoverable bootloader error (0x19000008)" though i still could not flash an update from sdcard
So i decided to see what would happen if i booted up my other (working but never previously connected to pc)A500 , which the pc immediately recognised as "Acer Iconia Tab A500 "
and installed drivers .
THIS IS THE WEIRD BIT
as soon as i disconected the WORKING A500 from usb and connected the A500 which was still doing its boot loop , Windows suddenly recognise it as "Acer Iconia Tab A500 " and the Tab's screen almost immediately lit up with the Android welcome/setup screen !
i have no idea the number of other "fixes " i had tried (from here and other sites but it worked for me)
Yes i was lucky to have another A500 handy but if someone else is having boot problems , and has never connected their A500 to pc before they had problems this may work for them if they know someone else with a working one .
Nice, I have an A500 that is stuck in a bootloop, I will try to do some of these things to bring her back around, Thanks.
brysie said:
i decided to see what would happen if i booted up my other (working but never previously connected to pc)A500 , which the pc immediately recognised as "Acer Iconia Tab A500 "
and installed drivers .
THIS IS THE WEIRD BIT
as soon as i disconected the WORKING A500 from usb and connected the A500 which was still doing its boot loop , Windows suddenly recognise it as "Acer Iconia Tab A500 " and the Tab's screen almost immediately lit up with the Android welcome/setup screen !
i have no idea the number of other "fixes " i had tried (from here and other sites but it worked for me)
Yes i was lucky to have another A500 handy but if someone else is having boot problems , and has never connected their A500 to pc before they had problems this may work for them if they know someone else with a working one .
Click to expand...
Click to collapse
So you can only get PC to install drivers if you have a working tablet? Not available to download anywhere? So given this situation, do you know any method that could help someone with only one, broken, a500.
I have a stock, unrooted tablet that gets stuck on boot on the acer logo. It started happening after the battery died and I charged and tried to boot.
Hey guys,
my brand new nexus 7 32gb (hsdpa+) isn't booting anymore.
I shutted down my device correctly and was holding all buttons to start the device.
I searched on XDA and found out that this combination activate fastboot.
Is my device in fastbootmodus? The screen is black and it isn't booting at all
My PC has Nexus 7 drivers installed but if i connect my device its just showing me "USB device isn't recognized"
What can i do?
Thanks in advanced.
jogibush said:
Hey guys,
my brand new nexus 7 32gb (hsdpa+) isn't booting anymore.
I shutted down my device correctly and was holding all buttons to start the device.
I searched on XDA and found out that this combination activate fastboot.
Is my device in fastbootmodus? The screen is black and it isn't booting at all
My PC has Nexus 7 drivers installed but if i connect my device its just showing me "USB device isn't recognized"
What can i do?
Thanks in advanced.
Click to expand...
Click to collapse
Got it.
Reinstalled the drivers five times. After every install i connect the device and hold the power button a long time.
now it is back to life again...but i donno why this happened at all...
Hi, I've bought a nexus 7 three months ago and it working nice until I've installed CM10. One months after an update, my tablet turned off and never turn-on again.
I've already tried with all buttons combinations, I've already bring it to support but they can't repair it.
When i connect them to PC show "Unknown device" or "APX", with adb or fastboot i can't list device. How I can repair it?
jajaya said:
Hi, I've bought a nexus 7 three months ago and it working nice until I've installed CM10. One months after an update, my tablet turned off and never turn-on again.
I've already tried with all buttons combinations, I've already bring it to support but they can't repair it.
When i connect them to PC show "Unknown device" or "APX", with adb or fastboot i can't list device. How I can repair it?
Click to expand...
Click to collapse
Was it Asus who couldn't repair it? Kinda find that hard to believe...but...okay.
Have you tried charging the tablet, then holding the Power button for like 30 seconds to a minute? Sounds like it's in APX Mode, which is why fastboot and adb won't recognize it.
jajaya said:
Hi, I've bought a nexus 7 three months ago and it working nice until I've installed CM10. One months after an update, my tablet turned off and never turn-on again.
I've already tried with all buttons combinations, I've already bring it to support but they can't repair it.
When i connect them to PC show "Unknown device" or "APX", with adb or fastboot i can't list device. How I can repair it?
Click to expand...
Click to collapse
Indeed, it's really strange that the support didn't want to repair your tablet.
Have you try the solution from @RMarkwald
Which version of win, have you ?
Install this drivers => USB DRIVERS r_06 for Windows 7 & 8
After this install, connect your tablet and try to go to your bootloader.
Send a feedback after this try
We will see after