Related
Since Monday morning, I have not been able to sync my phone (was dcd v3.0.4 when it stopped working). I have done much research and have tried many different things in an unsuccessful attempt to solve the issue.
When I plug it in, it begins charging but nothing else happens. No windows new device sound or system tray notification, no driver prompt, no windows activesync activity, nor any activesync activity on the phone (that little arrow icon on the top bar).
I have gotten this problem extremely intermittently previously but have always been able to resolve it with either a soft reset and/or a computer reboot. When that solution attempt failed, I tried moving the usb cable to a different port. I tried four or so different ports with no different results. I tried a different cable. I tried disabling advanced networking, deleting my partnerships (lost my contacts and have not yet been able to re-sync them :/), uninstalling activesync, and cleaning all the activesync files and drivers. I even launched device manager with hidden/non-present devices shown to remove the windows mobile devices (which were oddly not present, although this was after my first activesync uninstall/clean).
After not being able to get anything to respond, I thought it may be something not working properly on my workstation, so I tried similar processes of troubleshooting on my laptop with the same results.
At this point, I figured I had isolated the problem to the device, hopefully being just a software issue and not a hardware issue. At the time, I was still running rom dcd v3.0.4 with radio 3.35. I decided to flash to the newest versions in a hopeful attempt to restore my device's functionality. After flashing radio 3.39 and cooking and flashing a dcd v3.1.2 rom, I tried again with no different results.
Finally, I decided to connect it in bootloader mode, just to see what would happen (what is normal behavior for this anyway? does it get detected and drivers installed correctly?). It was detected as a usb device by my workstation but could not install drivers for it.
Needless to say, I have become rather frustrated with my device this week. I am not sure what the problem is exactly, nor what I could possibly do to fix it. I am on the verge of flashing a stock rom and *gasp* going to the Sprint store for support. Perhaps I finally dropped or shocked it one too many times this past weekend, and it does indeed have a physical issue...
Does anyone have any suggestions/ideas/thoughts? I would be very greatful for any input.
Thank you!
See this thread and see if anything in there fixes your problem.
http://forum.xda-developers.com/showthread.php?t=393918
I have been following that thread in hopes that something may prove helpful and have tried everything suggested, including attempting to clean the port (what would be best for this? anything more than just blowing into it?), trying the two Y adapters I have (emu -> emu / mini-usb & emu -> mini-usb / 2.5" stereo), running that batch script and working with the device manager (those devices were not present), and disabling advanced network functionality, all with no results.
VerusMaya said:
running that batch script and working with the device manager (those devices were not present),
Click to expand...
Click to collapse
If you've sync'd in the past then when you display hidden devices those devices should be present (at least faded). It'll be very strange if you don't see them. If not then uninstall the Mobile Device 6.1 upgrade, restart the PC and reinstall it. Then open up the device manager and watch what changes when you plug in your WinMo device.
Keystone said:
If you've sync'd in the past then when you display hidden devices those devices should be present (at least faded). It'll be very strange if you don't see them. If not then uninstall the Mobile Device 6.1 upgrade, restart the PC and reinstall it. Then open up the device manager and watch what changes when you plug in your WinMo device.
Click to expand...
Click to collapse
I also thought it quite strange that I did not see those devices at all at when I displayed hidden/non-present devices in the device manager. I definitely have sync'd on this machine many times, I typically leave it plugged in throughout the day here at work. My machine is part of a corporate domain but I do not see how anything pertaining to that would affect my devices. On my laptop (used to sync here), the devices were present in the device manager, but even after uninstalling them the phone would not be detected when I plugged it in.
When you say uninstall the mobile device 6.1 upgrade, are you talking about the vista mobile device manager? I am on XP with activesync 4.5.
Also, nothing happens when I plug the device in, not even the standard device connected notification sound. Nothing changes in the device manager, nothing is found when I rescan hardware, I even uninstalled all the usb root hub devices and rescanned for them, hoping a complete usb subsystem driver reinstall may help detect something.
I even downloaded and ran two usb tools, one free usbdeview (http://www.nirsoft.net/utils/usb_devices_view.html) which displayed and monitored all usb devices (present and non-) and drivers and a trial of a usbtrace (http://www.sysnucleus.com/) which was a usb protocol traffic capture and analysis program. I experimented with (un)plugging the phone multiple times in multiple ports with two different cables while running these programs, attempting to find something useful. Absolutely nothing at all happened in either program, which makes me believe it is something either on the phone software or hardware.
I have a feeling I may require a device swap :/
VerusMaya said:
When you say uninstall the mobile device 6.1 upgrade, are you talking about the vista mobile device manager? I am on XP with activesync 4.5.
Click to expand...
Click to collapse
Yeah, activesync then... I dunno, I'm at a loss.
Yeah me too, looks like I am going to have to flash the latest stock Sprint rom and take it in hopefully they can do something for me.
Went to sprint, it was a bad port after all, they gave me a brand new device.
VerusMaya said:
Went to sprint, it was a bad port after all, they gave me a brand new device.
Click to expand...
Click to collapse
Are you sure they gave you the brand new device? coz same thing happened to me a week ago and i went to sprint. They gave me the refurbished phone back. Physical condition of the phone is very good tho.
SptMogul said:
Are you sure they gave you the brand new device? coz same thing happened to me a week ago and i went to sprint. They gave me the refurbished phone back. Physical condition of the phone is very good tho.
Click to expand...
Click to collapse
Well I suppose I am not sure it was brand new, but it had the screen protector and the plastic stickers still on it (next to keyboard when you slide it out). I also received an additional 512MB SD card that comes with it.
Did you flash back to a sprint rom via sd card?
arcanecho said:
Did you flash back to a sprint rom via sd card?
Click to expand...
Click to collapse
Yes, I extracted the two NBH files from the latest (3.35 I believe) stock Sprint rom installer and first flashed the smaller image (bootloader/radio I think it was), and then the larger image (os) before I took it in.
The rep I dealt with at first was somewhat of a technical idiot and only served to confuse/delay matters but after I returned, I spoke to someone else and gave them permission to hard-reset, as well as mentioned I had done this multiple times as well as tried multiple computers and multiple cables, just to help them narrow down the possible source of the problem (as well as to block possible common excuses). After waiting around for half an hour or so in-store, a technician brought me a new phone and told me the port was physically bad.
All-in-all, I was quite pleased with Sprint's service and my free swap for an issueless and scratchless new device. I was afraid it was not going to be quite so easy, requiring more time and/or an insurance replacement fee. Not to mention the free 512mb sd card.
I had a similar problem, I was un able to connect to active sync but was able to charge. Everytime I would try to connect to active sync I got the "device is not recognized" error. Then someone on here suggested perhaps my USB port was messed up, sure enough I looked in the port and noticed one of the gold pins was flipped up slightly higher then the rest. My friend took a needle and adjusted the pin and it was good as new. Somehow I had lifted one of the pins.
Anyways IMHO it's good to look in there and just check if your having problems connecting, it saved me a trip to a technician and having to wait or go through reprogramming everything.
So I have a bad feeling here. I was fixing my ad hoc problem and accidentally renamed my /system/bin folder to "bin - Copy" not sure how I did it, a finger swype n boom it was that way. Could not change it back. Rebooted and now I can't get passed the Eee Pad boot screen. Any one know how to fix this?
I've got a similar problem.
There should be a sollution where you start up, holding the powerbutton and volume up. You feel a vibrate and the screen stays black.
with this way you can connect your transformer, and access it. But I don't know how.
Windows reconiges the device as and APX (under linux as an Nvidia device) But I can't connect to it, don't have the drivers and so.
So is anyone knows how to access the prime trough this method, our problem could be solved using adb pulling and pushing these folders.
Greets
If you connect it to your computer can adb access it??
Nope. Going to try a couple more things this evening.
Sent from my PC36100 using XDA App
Well, I tried a bunch of different things: microsd recovery, wipe data, recovery, "up volume/pwr button", broke down n called Asus. So here's what happened in case anyone else comes across this thread: microsd method to flash firmware=nothing, anytime I entered recovery Andy laid down and opened his chest cavity and red triangle !, wipe data done. signature match=freeze up at that screen, no reboot. hard reset with paper clip=nada just reset to frozen eee pad screen. I have linux 11.10 and 10.04BT on another hdd so I booted to both b/c I read a post somewhere about booting the prime by holding up volume/pwr and its supposed to be some kind of nvidia diagnostic mode. Interestingly in windows it changed from an unknown MTP usb to APX device doing this, in Linux it never even came up either way. I don't know enough about this, so I tried searching and reading=nothing fruitful. I'm a Linux and ADB noob so I read and read and read some more, but after trying a few walk throughs, my Prime just seems to be dead. So I called Asus and played dumb, said it froze after trying to update to ICS. He walked me through these other steps I mentioned to no avail. Then he gave me an RMA# so I went ahead and mentioned the excessive light bleed and non-functioning GPS. He noted those issues and now I'm sending it in apparently. I was REALLY hoping to avoid this b/c this was my fault, but my experience with the Prime has prompted me to ad my 2 cents/rant in the general thread.
I wish this had a better outcome, but with the bootloader locked I and many others have been unnecessarily doomed to RMA.
Well that sucks big time... hope you get another soon
hoping to hear about an update to this other than sending it in. unfortunatley i have just done the exact same thing.
There are APX drivers in the dev section. My Prime changed from APX device to Asus Transformer prime APX mode when I installed them. After that I don't know what to do; I think we need an nvflash for the Prime or something.
Mine went into APX mode after the last OTA update failed and won't leave APX mode for anything, so I was looking for a way to connect to it to flash an update or something, but no luck so far. Maybe Asus will release a tool for us to fix a failed OTA update, would be a lot better than sending my tablet away for a month so they can do it.
I searched and searched for this too. Couldn't get anything to work.
As for an update, as of about a couple hours ago, looks like they are sending me a new tablet. Has a different serial number listed as "ready to ship" and states "original serial number: C1O....." which is the s/n of the tab I sent in.
So we'll see if this one comes with no light bleed and working gps. Don't think I'll be screwing this one up! Gonna be extra careful...
I was in the same situation, stuck. I tried everything you did as well and nothing. "Doktaphex" gave me this link http://forum.xda-developers.com/showpost.php?p=22743057&postcount=119 in my post and it worked perfectly. I was sooo damn happy to see Andy actually working instead of laying down when I entered RCK
Oops...shoulda read through. Hehe sorry bout that :/
That would've been just one more thing to try on top of all the other things I tried. If it actually works, then ALL the other ppl that say to use this microsd recovery method need to read your link and actually know what they are talking about. I read method after method and tried them all to no avail.
I did this and that worked for me : http://forum.xda-developers.com/showpost.php?p=22857274&postcount=21
Got my replacement Prime today. Putting it through the paces now. GPS isn't noted on the box, but I don't remember if it was on my first one. Still a C1O serial. Went ahead and updated first, bc I don't care about HC.
GPS: Can see 4 but signal stays under 35, no locks. will try again tom from Dallas
BT/Wifi issue: None, Does not degrade
Wifi range: Not bad, little better than my phone
Light bleed: Better than last, but still 5 spots along bottom and right side
Side Note: put a 64gb microsd in the tab and a 64gb microsd w adapter in dock. Both work fine, now up to 192gb.
I'm very happy Asus replaced this so quick (week and 1 day). I'm not a picky person so I am fine w the lesser light bleed, I will never use gps but it would be nice to have as an option. I bricked my first tab and would gladly have paid for them to reflash it, heck if they called me even now and said, "hey, we found that you bricked your own tab, here's a bill to reflash" I'd gladly pay it. So far I have to agree w everybody's sides to every issue, which is crazy to think, but everyone has legitimate points. Except ppl that expect Asus to still warrant after unlocking n flashing roms, that's ridiculous.
Hello guys!
For about 2 or 3 weeks now I have the problem that the speaker on my TF201 does not work anymore. Headphones are working fine.
It also does not recognize any USB Sticks anymore. The Dock is not dead, it works fine and also has current on the USB Port (the USB stick LED is activated but does not blink for accessing it). Also the SD Card slot does not work anymore. The MicroSD slot on the tablet itself works fine...
And the next thing: My PC does not recognize the tablet anymore when I connect it. It does load when I connect it to the adapter but I can't transfer files anymore via PC. Cable is not broken but to minimize this risk I already offered a new one just in case.
Do you guys have any idea what this maybe is caused from? Maybe broken hardware? Or maybe a not properly connected cable in the tablet? But if so why is USB and stuff not working?
Please help me, I don't wanna lose such an awesome tablet
And I may can't even RMA it cause I've unlocked and flashed a new ROM on it...
EDIT 12.06.2013: When the tablet is fully turned off and USB is plugged in (PC, not charger) it suddenly powers up. I still can't use USB ports...
EpicLPer said:
Hello guys!
For about 2 or 3 weeks now I have the problem that the speaker on my TF201 does not work anymore. Headphones are working fine.
It also does not recognize any USB Sticks anymore. The Dock is not dead, it works fine and also has current on the USB Port (the USB stick LED is activated but does not blink for accessing it). Also the SD Card slot does not work anymore. The MicroSD slot on the tablet itself works fine...
And the next thing: My PC does not recognize the tablet anymore when I connect it. It does load when I connect it to the adapter but I can't transfer files anymore via PC. Cable is not broken but to minimize this risk I already offered a new one just in case.
Do you guys have any idea what this maybe is caused from? Maybe broken hardware? Or maybe a not properly connected cable in the tablet? But if so why is USB and stuff not working?
Please help me, I don't wanna lose such an awesome tablet
And I may can't even RMA it cause I've unlocked and flashed a new ROM on it...
Click to expand...
Click to collapse
Do you have one of the Prime to USb connectors? I wonder if the issue is in the dock or the tablet connector.
poofyhairguy said:
Do you have one of the Prime to USb connectors? I wonder if the issue is in the dock or the tablet connector.
Click to expand...
Click to collapse
Sadly no. I never ever would have used that cause I have the dock. And Dock can't be broken, the problem appeared since the speaker is not working too.
I tested MicroHDMI output now. Works fine, audio is there too. Hm... Strange...
Hidden "Camera Version" function?
Sorry, wrong thread ^-^" Please delete this entry!
My first guess is that something may have gotten disconnected inside the Prime. It's unlikely, but worth a check. Have you ever opened your prime?
When you have a dock, you have two options of connecting it to your PC. You can put the Prime into the dock then connect the two to your PC or you can just set the dock aside and connect the Prime directly. Have you tried both ways?
Jgrimoldy said:
My first guess is that something may have gotten disconnected inside the Prime. It's unlikely, but worth a check. Have you ever opened your prime?
When you have a dock, you have two options of connecting it to your PC. You can put the Prime into the dock then connect the two to your PC or you can just set the dock aside and connect the Prime directly. Have you tried both ways?
Click to expand...
Click to collapse
Jup I tried both ways.
And no I never opened it up. May I should look for a tutorial. Does iFixIt have an tutorial for it?
I don't think that iFixIt has one. At least they didn't about 6 months ago when I needed to replace my glass. There should be links to tutorials buried in these forums. Also, a little Googling should find you something too.
Regarding the HDMI audio working: Not too much of a surprise. Remember that the micro-hdmi port is sending a data stream with the audio embedded/encoded as 1s and 0s. It seems like something may have (hopefully) come disconnected related to the built-in speaker.
Jgrimoldy said:
I don't think that iFixIt has one. At least they didn't about 6 months ago when I needed to replace my glass. There should be links to tutorials buried in these forums. Also, a little Googling should find you something too.
Regarding the HDMI audio working: Not too much of a surprise. Remember that the micro-hdmi port is sending a data stream with the audio embedded/encoded as 1s and 0s. It seems like something may have (hopefully) come disconnected related to the built-in speaker.
Click to expand...
Click to collapse
I opened it up but I saw no unconnected or partly connected cable. I only lifted up the touchscreen, about the other parts I was too afraid to ruin something... Didn't unscrew so I wasn't able to see the under connectors.
Anyway, I don't think it's an unconnected cable. But if it's a software fault why are suddenly without flashing anything like Kernel or Bootloader so many things not working? That's just... What the hell o-O
Also I don't want to RMA it again. It's flashed and unlocked so I may have to pay 100€ for it... I could easily spend that money on a Galaxy Tab or something. But would still be awesome to have that one as "backup tablet" then just in case so I don't want to just throw it away.
Good on ya for taking a look. If you disconnect the robbon cables that connect the digitizer and LCD to the mainboard, you can set the top part (the screen and glass) aside and take a much better look. I completly understand your reluctance for fear of damaging. I felt the same way when I took mine apart the first time to replace the digitizer glass.
In devices like this, the headphones and the built-in speaker have separate amplifiers. They're not like very old transistor radios where the headphone jack is connected to the speaker wires with an interlock. I found this out when my Viewsonic 4.5" video player had digitally garbled sound in the headphones but not in the built-in speakers. Weirdest thing that I wouldn't expect being old-school...
The upshot is that you simply may have failed components, which is a real bummer since these are (imho) still pretty sweeet tablets.
You *could* always contact ASUS support and describe the problem and see if they can share any familiarity or knowledge with you. Sadly, I've found ASUS support to be bag-of-hammers dumb and patently useless, despite having a decent product.
Jgrimoldy said:
Good on ya for taking a look. If you disconnect the robbon cables that connect the digitizer and LCD to the mainboard, you can set the top part (the screen and glass) aside and take a much better look. I completly understand your reluctance for fear of damaging. I felt the same way when I took mine apart the first time to replace the digitizer glass.
In devices like this, the headphones and the built-in speaker have separate amplifiers. They're not like very old transistor radios where the headphone jack is connected to the speaker wires with an interlock. I found this out when my Viewsonic 4.5" video player had digitally garbled sound in the headphones but not in the built-in speakers. Weirdest thing that I wouldn't expect being old-school...
The upshot is that you simply may have failed components, which is a real bummer since these are (imho) still pretty sweeet tablets.
You *could* always contact ASUS support and describe the problem and see if they can share any familiarity or knowledge with you. Sadly, I've found ASUS support to be bag-of-hammers dumb and patently useless, despite having a decent product.
Click to expand...
Click to collapse
Opened up again, tried to push a few connectors in a bit but nothing... Looks like I really have a hardware failure...
But what now? When I send it to ASUS (or the shop where I bought it) they might say "Nope, you opened that thing". Also flashing back Stock ROM is... Yeah... Many work... I already was on the 4.1.2 Bootloader, upgraded to 4.2.1 now. I don't know how seriously they take that whole hacking/flashing thing, maybe they even repair a flashed tablet.
I dont know if it helps anyone further pin-point the problem because i havent been able to but i have the same issues and for me the sound comes back once i have the screen separated from the tablet. i can restart the tablet many times and audio still works as long as the screen is not fully in its place. If i clip the screen back in its place audio still works until i turn off or restart the tablet.
Sent from my Transformer Prime TF201 using xda app-developers app
Hello i've got the same problem and i'm praying someone can help.
Since updating from Androwook Hairy Bean V2.11 to V2.2 RC1;
there is no sound from the external speaker; playing media, notifications, alarms etc
dock doesnt recognise usb stick
pc doesnt recognize the tablet
on V2.2 RC1 i got the update pad firmware message and i accepted it, not sure if this is the cause because others have done the sam and reported everything working fine.
Also starting getting a notification on startup "unable to detect driver for loudspeaker" on V2.2 RC1. So i downgraded to Hairy Bean V2.11 thinking it would solve the issue but it hasn't, nothings changed.
I've tried a factory reset, cold boot, downloaded dsp manager and not been successful.
Has anyone come across this problem and found a solution?
Please help me
Thanks
zillar5 said:
Hello i've got the same problem and i'm praying someone can help.
Since updating from Androwook Hairy Bean V2.11 to V2.2 RC1;
there is no sound from the external speaker; playing media, notifications, alarms etc
dock doesnt recognise usb stick
pc doesnt recognize the tablet
on V2.2 RC1 i got the update pad firmware message and i accepted it, not sure if this is the cause because others have done the sam and reported everything working fine.
Also starting getting a notification on startup "unable to detect driver for loudspeaker" on V2.2 RC1. So i downgraded to Hairy Bean V2.11 thinking it would solve the issue but it hasn't, nothings changed.
I've tried a factory reset, cold boot, downloaded dsp manager and not been successful.
Has anyone come across this problem and found a solution?
Please help me
Thanks
Click to expand...
Click to collapse
That is very strange mate.
The firmware update was just for the pad and if it had already installed on 2.11 and was working fine then that was done. The only person who ever had a problem with it happened as he was installing it and we fixed that.
Upgrading to 2.2 changed nothing from 2.11 except a slightly newer base and some newer kernels. Even if the kernels were not supporting your hardware when you downgraded back to 2.11 you would have been back on the old kernels and back to how you had it working before.
This does confuse me.. As a test because I cannot think of anything else except hardware failure at the moment can you try getting the downgrade zip from the hairybean thread that takes you back to 4.1.1 bootloader and compatible twrp and then try flashing hairybean 1.51 instead.
Read the instructions thoroughly under the downgrading section.
flumpster said:
That is very strange mate.
The firmware update was just for the pad and if it had already installed on 2.11 and was working fine then that was done. The only person who ever had a problem with it happened as he was installing it and we fixed that.
Upgrading to 2.2 changed nothing from 2.11 except a slightly newer base and some newer kernels. Even if the kernels were not supporting your hardware when you downgraded back to 2.11 you would have been back on the old kernels and back to how you had it working before.
This does confuse me.. As a test because I cannot think of anything else except hardware failure at the moment can you try getting the downgrade zip from the hairybean thread that takes you back to 4.1.1 bootloader and compatible twrp and then try flashing hairybean 1.51 instead.
Read the instructions thoroughly under the downgrading section.
Click to expand...
Click to collapse
Thanks for the assistance Flumpster and I've been following your thread, you've done some damn amazing work!
Just for the record 2.11 + that kernel had my prime running the best it ever has! after doing all the wipes, formats I flashed v2.2 and got the update pad firmware then and missing speaker driver notification? I dismantled my prime and checked for a loose connection on the speaker but it looks ok.
I'll try the downgrade tomorrow (going to bed now) and if that doesn't work, i still have audio through the headphone jack.
Thanks again
zillar5 said:
Thanks for the assistance Flumpster and I've been following your thread, you've done some damn amazing work!
Just for the record 2.11 + that kernel had my prime running the best it ever has! after doing all the wipes, formats I flashed v2.2 and got the update pad firmware then and missing speaker driver notification? I dismantled my prime and checked for a loose connection on the speaker but it looks ok.
I'll try the downgrade tomorrow (going to bed now) and if that doesn't work, i still have audio through the headphone jack.
Thanks again
Click to expand...
Click to collapse
Just to make sure... Are you saying this happened straight after the firmware update on the next reboot or are you saying it happened when updating the rom ?
flumpster said:
Just to make sure... Are you sayig this happened straight after the firmware update on the next reboot or are you saying it happened when updating the rom ?
Click to expand...
Click to collapse
Honestly I don't know because afer I flashed 2.2 the homescreen loaded and the update firmware message appeared straight away. I dont think the notificatipns were sounding as the apps were restoring? Sorry i'm not 100% sure it happened pretty quickly
zillar5 said:
Honestly I don't know because afer I flashed 2.2 the homescreen loaded and the update firmware message appeared straight away. I dont think the notificatipns were sounding as the apps were restoring? Sorry i'm not 100% sure it happened pretty quickly
Click to expand...
Click to collapse
Ok mate.. Well try the downgrade option first and if that doesn't work then first of all I want you to drain your battery completely and leave for an hour. After that charge it up a little and try ( I know this sounds crazy and I thought the same when I first read it in another thread but it fixed our one guy who had problems with the firmware upgrade )
If this still does not work then upgrade back to 2.2 and once you are in the OS I will try to talk you into downgrading that firmware update to see if that helps.
If that still doesn't work after downgrading the firmware update then it is hardware sorry.
flumpster said:
Ok mate.. Well try the downgrade option first and if that doesn't work then first of all I want you to drain your battery completely and leave for an hour. After that charge it up a little and try ( I know this sounds crazy and I thought the same when I first read it in another thread but it fixed our one guy who had problems with the firmware upgrade )
If this still does not work then upgrade back to 2.2 and once you are in the OS I will try to talk you into downgrading that firmware update to see if that helps.
If that still doesn't work after downgrading the firmware update then it is hardware sorry.
Click to expand...
Click to collapse
i did what the 1st page of the ROM says and rebooted into recovery, tried installing 4.1.1 bootloader and recovery zip from my external sd card and failed - unable to open zip? strange...
zillar5 said:
i did what the 1st page of the ROM says and rebooted into recovery, tried installing 4.1.1 bootloader and recovery zip from my external sd card and failed - unable to open zip? strange...
Click to expand...
Click to collapse
ok micro sd card was coming up write protected, so formated and downloaded new files and managed to downgrade to 4.1.1 bootloader and v1.51 - still no sound from external speaker, also sd slot and usb still not working on dock. Tried running the battery flat and leaving it for over an hour then charged a little and powered on still no change.
I'm leaving work now and have limited internet access tonight so i download the v2.2 zip tomorrow and see if that works, otherwise could be hardware hey.
A little while ago, I'm not really sure when but my Wifi stopped working. If I tried to enable it, it would just grey out and look like it was enabling but eventually just returned to not on. I've tried flashing new kernals, new roms, new modems, and currently sitting on stock 2.3.4. I've factory reset, (without wiping sdcard data) on stock. Tried to see if there was an update (saw a post that had said if you update to 2.3.6 over the air it will fix wifi, however no such update exists) I've searched and searched and searched and I cannot seem to find any information regarding whats wrong or how to fix this.
Any input would be greatly appreciated, thank you.
It may be hardware failure. The normal test for hardware/firmware issues is to flash back to stock. You have tried everything that I would suggest for such an issue, except perhaps flashing the latest stock. However, wifi works on all stock versions, so... your troubleshooting steps point to likely hardware failure.
Actually, there is one more step I can suggest. Install a custom kernel, and re-format everything, including USB memory (internal sd card- be sure to back up anything you don't want to lose) and remove any external card. Mr-cook has some scripts that can make the process easier. This is a little more thorough than just erasing the data from the partitions. Then install the stock firmware, preferably the latest stock UCMD8.
creepyncrawly said:
It may be hardware failure. The normal test for hardware/firmware issues is to flash back to stock. You have tried everything that I would suggest for such an issue, except perhaps flashing the latest stock. However, wifi works on all stock versions, so... your troubleshooting steps point to likely hardware failure.
Actually, there is one more step I can suggest. Install a custom kernel, and re-format everything, including USB memory (internal sd card- be sure to back up anything you don't want to lose) and remove any external card. Mr-cook has some scripts that can make the process easier. This is a little more thorough than just erasing the data from the partitions. Then install the stock firmware, preferably the latest stock UCMD8.
Click to expand...
Click to collapse
Which of those scripts do you suggest using?
killerxtreme said:
Which of those scripts do you suggest using?
Click to expand...
Click to collapse
Hopefully, you have a basic understanding of memory partitioning. It is best to understand what you are doing, and not just follow someone else's recipe. That being said, you can use the first one, cook's rom wipe, which will format the system, preload, data, and cache partitions. If you also want to format the USB memory, you will need to do that from within recovery of the custom kernel: from the "mounts and storage" option, select "format /sdcard".
For installing the stock firmware, Odin3 v1.85 is recommended. Download the file from the Download Repository, extract the .tar.md5 file, and put that in the pda slot.
I actually have narrowed it down to a hardware issue, apparently I have the battery leaking issue. I've removed the corroded battery, and cleaned up the area which was effected. The phone still operates, however I still do not have Wifi. Is there something I can do to further fix the issue? I am missing a few tiny resistors in that area could they missing be the issue? I heard they just filtered the signal or something along those lines. What can I check or do before finally just needing a new mainboard.
killerxtreme said:
I actually have narrowed it down to a hardware issue, apparently I have the battery leaking issue. I've removed the corroded battery, and cleaned up the area which was effected. The phone still operates, however I still do not have Wifi. Is there something I can do to further fix the issue? I am missing a few tiny resistors in that area could they missing be the issue? I heard they just filtered the signal or something along those lines. What can I check or do before finally just needing a new mainboard.
Click to expand...
Click to collapse
I bought a phone cheap from the Swappa boneyard with a good screen but with the wifi not working to go with another phone I acquired which had a cracked screen but fully working main board. I combined the two into a fully working phone, and a phone with cracked screen and no wifi. The second phone sat in a box for a long time. Not too long ago, I read about the battery leaking issue, so I pulled that second phone apart and looked at the main board. Sure enough, the battery and the area around it was corroded. The phone was fully functioning except for the wifi.
I didn't play with it too much, but it looked to me like the battery was soldered onto the main board. Did you have to de-solder it to get it off? I believe that the battery is necessary for the wifi to work. I build electronics, but not on the miniature scale of a phone pcb. I have a professional soldering station, but I wouldn't attempt to work on a board like that myself. Unless you have the right equipment, and the experience to go with it...
I think you would need to replace the main board. You could try buying a phone with a broken screen that is otherwise working. It might be fairly cheap. But the I777 is getting old enough that it will be experiencing various kinds of failure, so it is a crap shoot.
I gave my original I777 to my wife, and bought one for myself on swappa over a year ago. The one I bought just went dark one day a few months ago. I don't know what part failed, but it was completely non-responsive, a true brick. My son had an I777 also, and he had cracked the screen, so I bought him an S4 for Christmas. I got his i777 and combined the main board with the good screen from my dead phone, to make a fully functioning phone. After setting that phone up and using it for a couple of weeks, one day the power switch failed. I'm still using that phone as my main phone, with gravity screen to overcome the failed power button, since I don't want to spend another $40 on it to get the power button replaced. The point of relating this is just to show how likely failures are.
Actually I just pulled it off, and cleaned the area. I've been reading that its suppose to keep the date and time, and I've also read that people don't actually know what its for. However I do know that since i pulled it my phone seems to heat up less. (It was getting rather hot) However wifi still does not work.
I have a Chinese netbook with Android 4.2.1 on it, and I've managed to root it. I've been interested in installing something like CyanogenMod or even Linux on it. The problem is that everything seems to be centered around very specific device information like manufacturers and model number in the ARM/Android world. But unfortunately, the most specific numbers associated with my device tie it back to a chipset manufacturer called WonderMedia, WM8880 GA-1311F. And I can't find anything at all about that device except that there's supposedly a 7-inch tablet or two with the same chipset, but their manufacturers are fairly unknown as well. When I do Google searches for the serial number, I mostly find my own old threads
I keep hitting dead ends trying to figure out how to boot something else on this device, because they expect me to know a specific recovery procedure or have a device specific ROM to apply.
Am I basically stuck with what I've got? I mean, I've been doing searches for days, I've searched for specific strings found under build info, and found nothing. I keep hunting for clues about the nature of the device in the kernel logs, and I keep coming up empty. The closest thing I can find is information about an older WM8650 netbook, and I saw a dead thread somewhere that implied there was an architectural similarity between WM8880 and that one, but I wasn't able to find anything about my device specifically.
I really don't want to waste anymore time with this if I don't have any chance of getting anywhere with it. Just tell me the truth... am I stuck with the pre-installed version of Android on this device?
I was hoping I'd be able to hack the device and do whatever I wanted with it, sort of like a Raspberry Pi in laptop form, but I'm starting to think I made a mistake because this device seems hopelessly locked into running Android 4.2.
Well, I found out that my device actually has something called U-boot built in. It wasn't easy to find because I had to dump a region of flash memory, hunt around in a hex editor, cut off part of the file, and then gunzip it to see it. Apparently my device can be booted from an SD card through a file called "FirmwareInstall/autorun.1.wmt". I also saw an odd reference to a USB disk and "FirmwareInstall/autorun.u.wmt", which may suggest it can also be booted from USB.
At first I tried to have it print a Hello World message, but it didn't work. However, I did notice that when I put the file in place, the machine refused to power down with the SD card inserted, which was abnormal. Clearly, it was changing something, but the console isn't visible. So I tried the "poweroff" command instead, and sure enough the netbook started cycling its power until I removed the SD card.
Apparently there IS a way to get stuff working on here, but I would have to know TONS of low-level memory addresses for loading stuff like the kernel, they recommend installing stuff over the network for some weird reason, and it seems like you have to use a specific device tree to get it up and running. Half the ARM Linux installation documentation was just an apology saying that devices vary and there's no consistent implementation of anything.
So it seems like it's POSSIBLE to get something else working on here, but I would literally have to reverse engineer every little aspect of the machine and study every single subsystem carefully in order to do so. What's frustrating is that there is a person who is doing work on very similar devices like the 8505, 8650, and 8850, but they're not supporting mine because, get this, the developer's 8880 tablet was damaged from messing with those ridiculous analogue console pins, and they can't be bothered to buy another one. So anyone that has my chipset is stuck without any kind of support for anything, and I would be lucky to get a console framebuffer with keyboard support running on this stupid thing.
Overall, everything I read was just more and more bad news... stuff like the default console for the installer often being a serial terminal that you have to break open the computer to use. Everything about ARM devices is painful, and you apparently have to fight tooth and nail to get them to run anything besides their stock version of Android, and all because there's no standardization and no BIOS.
hi do you still have the netbook i need the rom for it