Database Info

Recovery console

Hey guys, here is the deal. I did toasts instructions but forgot to wipe the cache/data so it was just looping along the 4g screen. So I reboot using volume down key and reflash the original PC36IMG.zip, then I do "adb reboot recover" and restore my nandroid backup. Now I can't connect to my phone with my computer in any way. I can reboot using volume down and go to recovery, but when I try to run the script (I'm on a mac, so I'm running recovery-mac.sh) it just says "error: device not found". Furthermore, if I boot back in to android and try to send the "adb reboot recover" command from my macbook I get the same error. Any ideas?

For the record I have installed the SDK.
Also, I've just noticed that it won't even charge when plugged in to my macbook or my girlfriends win7 machine.

sambow said:
For the record I have installed the SDK.
Also, I've just noticed that it won't even charge when plugged in to my macbook or my girlfriends win7 machine.
Click to expand...
Click to collapse
ive only briefly played with the phone. i noticed settings to tell it what action to take when connected via USB. perhaps review these settings, also make sure ADB is turned on in the applications, usb debugging section.
this should at least get you a USB connection in normal android mode.
if you flash the userdebug RUU PC36IMG.zip and reboot into recovery, adb connection should work, otherwise something is wrong and i dont think its the software on the EVO because it seems to work fine for everybody else. perhaps try plugging/unplugging USB, switching USB ports, etc, the usual troubleshooting steps.
let us know how it works out!

No luck, I even tried the exe to reflash to stock (ran while HTC logo was up) and that was a no go.
Any more ideas?

Try a different USB cable. I had a cable suddenly go out on me, and wouldn't charge or act anything like a USB cable should. This was 'not' a cable that came with an EVO... but, worth a shot.

unbricking my 3.1 1.4.4 Kernel

Hi
Went to bed, surfed the web a bit, I had USB OTG Cable connected. Woke up this morning, went to turn it on and nothing. Thought the USB OTG had burned the battery so I charged it up, still nothing.
Connected to PC, tried the command: adb devices
Nothing.
Black screen of deadness on my Xoom. There is a method for restoring I believe, no? All rooting was initially completed using ADB but since 1.4.2 I have just used BRD's downloads and used Clockwork Mod recovery to install in recovery mode from zip on SD card.
The last thing I was trying to get working was NTFS partitions on memory sticks yesterday but didn't have any luck.
Would anyone mind telling me what I need to do?

yanic123 said:
Hi
Went to bed, surfed the web a bit, I had USB OTG Cable connected. Woke up this morning, went to turn it on and nothing. Thought the USB OTG had burned the battery so I charged it up, still nothing.
Connected to PC, tried the command: adb devices
Nothing.
Black screen of deadness on my Xoom. There is a method for restoring I believe, no? All rooting was initially completed using ADB but since 1.4.2 I have just used BRD's downloads and used Clockwork Mod recovery to install in recovery mode from zip on SD card.
The last thing I was trying to get working was NTFS partitions on memory sticks yesterday but didn't have any luck.
Would anyone mind telling me what I need to do?
Click to expand...
Click to collapse
Can you boot into fastboot mode using vol down + power?

Heart attack averted. Thanks for that rschenck!
Didn't know about this button combination.
Iain
Closed

[Q] Can not enter APX mode. Bricked?

I posted this in general as well, but figured I'd post it in Q&A.
I was going to install the Revolution rom and downloaded the super wipe. I ran it through Clockwork-mod (mistake) and didn't realize that I can't mount my external SD card in CWM. After running super wipe the tablet only boots into recovery. I can not get my tablet to boot into APX mode. On my PC it does not even show that the tablet is connected. My /data is missing completely. Is there a way to fix this? Any help would be appreciated.
Edit: Running CWM Touch 5.8.0.2

ultmontra08 said:
I posted this in general as well, but figured I'd post it in Q&A.
I was going to install the Revolution rom and downloaded the super wipe. I ran it through Clockwork-mod (mistake) and didn't realize that I can't mount my external SD card in CWM. After running super wipe the tablet only boots into recovery. I can not get my tablet to boot into APX mode. On my PC it does not even show that the tablet is connected. My /data is missing completely. Is there a way to fix this? Any help would be appreciated.
Click to expand...
Click to collapse
Get a microsd card reader and copy the rom to the microsd card through the reader
Sent from my EPAD using xda app-developers app

zachf714 said:
Get a microsd card reader and copy the rom to the microsd card through the reader
Sent from my EPAD using xda app-developers app
Click to expand...
Click to collapse
CWM doesn't recognize the external MicroSD.

ultmontra08 said:
CWM doesn't recognize the external MicroSD.
Click to expand...
Click to collapse
go into cwm and use adb to push the rom to the internel storage
Sent from my EPAD using xda app-developers app

zachf714 said:
go into cwm and use adb to push the rom to the internel storage
Sent from my EPAD using xda app-developers app
Click to expand...
Click to collapse
Tried that as well, it is not recognized on my PC as any type of device.

Hold volume up while its on in cwm and keep it down with the power and u should end up in apx
Sent from my ADR6300 using xda app-developers app

ultmontra08 said:
Tried that as well, it is not recognized on my PC as any type of device.
Click to expand...
Click to collapse
if the PC isn't seeing anything at all when you plug it in while it's in recovery, then it's a connection issue. Try another PC, and if it's still not seen, it's probably your cable, which is why you can't see the tablet in APX mode as well

fohdeesha said:
if the PC isn't seeing anything at all when you plug it in while it's in recovery, then it's a connection issue. Try another PC, and if it's still not seen, it's probably your cable, which is why you can't see the tablet in APX mode as well
Click to expand...
Click to collapse
It's not the cable. It was working fine prior to trying to do what I stated in the first post.

ADB could see it ... try.. if it can you can adb push or install twrp
Sent from my EPAD using xda app-developers app

ultmontra08 said:
It's not the cable. It was working fine prior to trying to do what I stated in the first post.
Click to expand...
Click to collapse
Then it's a timing/driver issue of getting into APX mode and getting it recognized. You can't wipe or remove or brick APX mode, without seriously trying. It would involve booting the tablet using some very hacked script to use the primary partition table instead of the use accessible secondary table, as APX is stored in a partition that is more or less untouchable
Just plug it into your computer, and hold down power and volume up. Hold it down for like a solid 45 seconds, even if it keeps rebooting, If after you hold power and volume up, the screen eventually goes black, then you're in APX. Open up device manager on your pc and look for any new or unrecognized devices, if nothing then try a different usb port. But a superwipe script definitely did not alter your apx mode, I can promise you that
And if that still doesn't work, try a different PC. If that still doesn't work, then I'm still betting it's the cable. When's the last time you used it for data transfer, and not charging? They do go bad. If recovery is mounted and successfully booting, then its ADB server is running. Which, if you make a working connection to a PC, will be seen

Hi ultmontra08,
Are you sure it isn't the cable?
I ran into this issue as well, I was stuck in recovery mode http://forum.xda-developers.com/showthread.php?t=1913905
If the cable is charging the tablet, it doesn't mean that it can't be defective still.
The computer should detect the device in recovery mode and apx mode. In my issue it didn't detect my device in recovery mode at all.
Until I got a new cable, I was able to see my device show up in Device Manager while it was in recovery mode.
I was able to narrow it down to being the cable because it would not show up on 3 different computers.

fohdeesha said:
Then it's a timing/driver issue of getting into APX mode and getting it recognized. You can't wipe or remove or brick APX mode, without seriously trying. It would involve booting the tablet using some very hacked script to use the primary partition table instead of the use accessible secondary table, as APX is stored in a partition that is more or less untouchable
Just plug it into your computer, and hold down power and volume up. Hold it down for like a solid 45 seconds, even if it keeps rebooting, If after you hold power and volume up, the screen eventually goes black, then you're in APX. Open up device manager on your pc and look for any new or unrecognized devices, if nothing then try a different usb port. But a superwipe script definitely did not alter your apx mode, I can promise you that
And if that still doesn't work, try a different PC. If that still doesn't work, then I'm still betting it's the cable. When's the last time you used it for data transfer, and not charging? They do go bad. If recovery is mounted and successfully booting, then its ADB server is running. Which, if you make a working connection to a PC, will be seen
Click to expand...
Click to collapse
I caved and purchased a new sync cable from amazon and it fixed the issue of not being seen by the PC! I've seen other posts about cables going bad, but I didn't think it would do any good. I just restored the newest stock image and I'm going to keep it there until I get a Google Nexus tablet in the future. It's interesting that these cables go bad. I've had the same iPod usb cable for six years and have never had a problem with it.

Unable to install ClockworkMod on TF101

I'm trying to install CWM and I rooted my Asus TF101. I installed RecoveryInstaller.apk, but when I click "Click to flash Recovery" the large button highlights blue for a few seconds, then goes back to black and nothing happens, no reboot, no CMW installed. When I try to boot into recovery I get the Android guy laying on his back with a Warning symbol in his belly...any ideas? I wiped my TF completely and still does the same thing. When I tried running Razorclaw I get the message saying I'm already rooted. Originally I used Debugfs Root Generic v2.3 to root my TF101. The firmware version I am on is US_epad-9.2.1.27-20120615. I wiped my data this morning in an attempt to resolve this issue, but before the wipe I DID have the superuser app. Now after the wipe, there is no superuser app.
Any ideas? I'm also having an extremely hard time getting my TF101 to connect to ANY PC. Its really weird because sometimes it will work after hours of it not working...most of the time it just comes up as "Unknown Device" with an error.

If you are rooted, install GooManager, grant root and then tap the 3 buttons in the top right and Install OpenRecovery Script.
This installs TWRP which is much better than CWM in my opinion.
Also, check the Dev section for my guide to Root and ROM the TF101, including APX drivers to install recovery with EasyFlasher.
I suspect young not be rooted because AFAIK you need a custom recovery to root on the latest firmware.

frederuco said:
If you are rooted, install GooManager, grant root and then tap the 3 buttons in the top right and Install OpenRecovery Script.
This installs TWRP which is much better than CWM in my opinion.
Also, check the Dev section for my guide to Root and ROM the TF101, including APX drivers to install recovery with EasyFlasher.
I suspect young not be rooted because AFAIK you need a custom recovery to root on the latest firmware.
Click to expand...
Click to collapse
So I was able to install GooManager as suggested but when I tried to install OpenRecovery it would download successfully (and I can browse to the file) but it would not install the recovery. Any suggestions? Thanks in advance.
Sent from my MB865 using Tapatalk 2

polishfly said:
So I was able to install GooManager as suggested but when I tried to install OpenRecovery it would download successfully (and I can browse to the file) but it would not install the recovery. Any suggestions? Thanks in advance.
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Are you really rooted?
I suspect you are NOT rooted, which is why these are not working.
When you opened GooManager, did it prompt you for Root Permissions from SuperUser or SuperSU?
If not, then you need to root again.
Check out PERI or EasyFlasher to root.

polishfly said:
I'm trying to install CWM and I rooted my Asus TF101. I installed RecoveryInstaller.apk, but when I click "Click to flash Recovery" the large button highlights blue for a few seconds, then goes back to black and nothing happens, no reboot, no CMW installed. When I try to boot into recovery I get the Android guy laying on his back with a Warning symbol in his belly...any ideas? I wiped my TF completely and still does the same thing. When I tried running Razorclaw I get the message saying I'm already rooted. Originally I used Debugfs Root Generic v2.3 to root my TF101. The firmware version I am on is US_epad-9.2.1.27-20120615. I wiped my data this morning in an attempt to resolve this issue, but before the wipe I DID have the superuser app. Now after the wipe, there is no superuser app.
Click to expand...
Click to collapse
Razorclaw doesn't work on that firmware. Do as frederuco suggested.

I think it may be my TF
I can't get it to connect to my PC properly. It comes up as "unknown device" and sometimes the sync app opens on the tablet but I still can't see the tablet on the PC with Asus sync or even windows explorer. I have looked everywhere online for a solution to this and tried every set of drivers I could find and I still have the same results...tried on 3 different PCs..2 win7 x64 and 1 win xp. Its out of warranty and I'm not sure what else to do. I may be stuck with the stock ROM. Any thoughts ideas or suggestions?
Sent from my MB865 using Tapatalk 2

polishfly said:
I think it may be my TF
I can't get it to connect to my PC properly. It comes up as "unknown device" and sometimes the sync app opens on the tablet but I still can't see the tablet on the PC with Asus sync or even windows explorer. I have looked everywhere online for a solution to this and tried every set of drivers I could find and I still have the same results...tried on 3 different PCs..2 win x64 and 1 win xp. Its out of warranty and I'm not sure what else to do. I may be stuck with the stock ROM. Any thoughts ideas or suggestions?
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
I used the Naked Drivers v0.72 on mine and it worked great (both ADB and APX). Did you try those?
There is also a chance it is your charging cable (it may still charge, but may not work for USB connections).

Where can I get the Naked drivers? I feel like I've already tried this and when I try to install them windows says they are not for my hardware. I will buy a new cable.
Sent from my MB865 using Tapatalk 2

polishfly said:
Where can I get the Naked drivers? I feel like I've already tried this and when I try to install them windows says they are not for my hardware. I will buy a new cable.
Click to expand...
Click to collapse
[ADB/FB/APX Driver] Universal Naked Driver 0.72

frederuco said:
[ADB/FB/APX Driver] Universal Naked Driver 0.72
Click to expand...
Click to collapse
Turns out I already tried these drivers. When I plug my TF in it shows up as 1 "unknown device" so I tried to install both the apx and win drivers which both showed the following error:
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."

polishfly said:
Turns out I already tried these drivers. When I plug my TF in it shows up as 1 "unknown device" so I tried to install both the apx and win drivers which both showed the following error:
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Click to expand...
Click to collapse
Strange, because I used those exact drivers here on a Win7 x64 system with no issues: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html

frederuco said:
Strange, because I used those exact drivers here on a Win7 x64 system with no issues: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
Click to expand...
Click to collapse
That's a bad ass guide you got there! Here is where I am getting stuck:
"Now that we have the Naked Drivers boot to APX mode. Attach your USB to your tablet (not the dock) and Hold VOL UP and POWER for 15-20 seconds. You should hear the new hardware found sound. It will probably fail the driver installation. "
Nothing happens when I hold the VOL UP and POWER for 15, 20, 30 seconds...it doens't boot up or anything...it only responds when I hold the power button alone or the power button and vol down. Any thoughts?

New USB cable on its way...but from what I have read, there has not been 1 instance where a new USB cord had fixed the exact issues I am experiencing.

Not sure, some users had issues where their power button may not work for APX mode. Keep in mind, the screen will be black when in APX mode.
You could try holding VOL UP and the plug in the USB cable to your PC (continuing to hold VOL UP) and this will trigger the tablet to turn on and enter APX mode.

polishfly said:
That's a bad ass guide you got there! Here is where I am getting stuck:
"Now that we have the Naked Drivers boot to APX mode. Attach your USB to your tablet (not the dock) and Hold VOL UP and POWER for 15-20 seconds. You should hear the new hardware found sound. It will probably fail the driver installation. "
Nothing happens when I hold the VOL UP and POWER for 15, 20, 30 seconds...it doens't boot up or anything...it only responds when I hold the power button alone or the power button and vol down. Any thoughts?
Click to expand...
Click to collapse
Nothing happens on the tablet, that is normal, screen stays black in apx mode.
The computer should see the a usb device though. Vendor ID is 0955 (nvidia). On linux 'lspci' shows it. On windows you should see it in the device manager, maybe even tagged with a yellow exclamation mark due to drivers not being installed. If you see it there try installing the drivers using device manager.

frederuco said:
Not sure, some users had issues where their power button may not work for APX mode. Keep in mind, the screen will be black when in APX mode.
You could try holding VOL UP and the plug in the USB cable to your PC (continuing to hold VOL UP) and this will trigger the tablet to turn on and enter APX mode.
Click to expand...
Click to collapse
I tried what you suggested, but I still get no APX device to show up in Device Manager. It shows up as "unknown device" and when I try to install the APX and/or Win drivers, I get the error stating that I do not have the hardware for the drivers.

I dunno, I used the naked drivers on mine with a Win7 x64 system and x86 with no issues.

frederuco said:
I dunno, I used the naked drivers on mine with a Win7 x64 system and x86 with no issues.
Click to expand...
Click to collapse
At this point I think it could be one of 2 things...a faulty USB cable (ordered) or a TF hardware issue (its out of warranty so I'm SOL if that's the case)...worst case scenario, I'm stuck with stock since I can still boot and charge. I would love to run CyanogenMod though =(

Try a linux CD and use ADB to install TWRP to the TF.
I would use an Ubuntu Live CD and install ADB on the live session (don't reboot or you will have to start over)
Then you should be able to follow the directions from the link below...
http://www.teamw.in/project/twrp2/109
The reason I say to use a Linux live CD is because you won't have to worry about drivers or be in APX mode. You just have to make sure you have the checkbox for android debugging mode enabled in settings on your TF.

bfmetcalf said:
Try a linux CD and use ADB to install TWRP to the TF.
I would use an Ubuntu Live CD and install ADB on the live session (don't reboot or you will have to start over)
Then you should be able to follow the directions from the link below...
http://www.teamw.in/project/twrp2/109
The reason I say to use a Linux live CD is because you won't have to worry about drivers or be in APX mode. You just have to make sure you have the checkbox for android debugging mode enabled in settings on your TF.
Click to expand...
Click to collapse
This, if that doesnt work id go for hardware issue(although even that is highly unlikly due to it being dectect at all) ive had various issues relating to these drivers, you really need to install the naked drivers before trying to install asus sync software as i think asus software causes issues. Best option would be to install windows in a virtual machine and install the naked drivers and try again.

Help pls!!!! 20$ in it!!!

New that would get attention. Is there anyone out there that is dedicated to helping for a lil cabbage? I have this tf101 transformer that i cant seem to get rooted. Why is it so gosh dern hard to root one? I have followed all methods and tryed diff methods. The emulator runs but root is still not acheived. I have not bricked it. Its running ics. Ive rooted phones and tablets since the evo 4g..... this garbage a$$ tablet is without a doubt one of the worst i have ever had the displeasure of owning. Nexus 7,,,samsung note 1,,,note 2,,,,,,note 10.1,,,,,htc first,,,,evo 4g,,,,blackberry tour....AND NONE HAVE EVER BEEN THIS HARD TO ROOT. I wont buy another asus anything.
So,if som1 could explain what im doing wrong thatwould be great...also 20 buck in the paypal acct.....if you can think of it. Ive done it. Next is taking it apart to see what makes it tick

First thing - Does your tablet get seen by your PC in either APX or ADB mode? And did you update the driver using the Naked Drivers?
Last time I rooted I used Wolf's Method 3. Here is what I did:
Plugged in my tablet to my PC via USB (win 7 PC).
After the device was detected, I went to Settings - Developer Options - Debugging (tick the box).
It should install new hardware and show 2 devices, an MTP and an ADB device.
Update the driver in the Device Manager on the windows machine to the Naked Drivers
Once that is updated, I downloaded ADB from the Android SDK. You really only need three files, available here: http://forum.xda-developers.com/showthread.php?t=1998650
Unzip these files to a folder called c:\adb
Open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
It should show a device connected. It may error out when restarting the daemon, but keep trying and see if it can find your tablet.
If you cannot get the ADB driver installed or updated, my guess is that you have a bad USB cable. Yes, it IS possible to have a bad cable for data transfer that STILL charges your tablet. I have even had that happen to me.
If you got this far, then here is what to do next:
Download your favorite recovery. I strongly recommend TWRP. The latest official release is here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Save this at c:\adb\TWRP.blob. You can use a different recovery method if you have the blob file (such as CWM) but TWRP is far superior unless you are looking to install Android Revolution HD.
Next, run the following commands (from Wolf's Exploit, Method 3)
Code:
adb push TWRP.blob /sdcard/
adb shell
mv /data/local/tmp /data/local/tmp.bak
ln -s /dev/block/mmcblk0p4 /data/local/tmp
adb reboot
exit
It will reboot. Once you see the ASUS loading screen, you can continue:
Code:
adb shell
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
Wait until you see it succesfully transfer data.
Then:
Code:
adb reboot
exit
Once it reboots, you should see a progress bar at the ASUS screen. Once this completes you will have TWRP (or some other custom recovery installed)
Now you can install your favorite SuperUser app.
Download a zip flashable SuperUser
ChainsDD SuperUser: http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
ClockWorkMod SuperUser: http://download.clockworkmod.com/superuser/superuser.zip
Chainfire SuperSU: http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip
I like the CWM SuperUser at the moment, but all three will work.
Put these where you can see them from the recovery you flashed. If using TWRP, it needs to be in the /sdcard/ directory or on the microSD card.
Next, reboot to recovery. Hold VOL DOWN and POWER for 12-15 seconds until you see some white text in the upper left of the screen. Release both buttons and tap VOL UP to enter RCK (Recovery).
Once in recovery, tap Install and choose the SuperUser.zip file to install. Once installed, you are rooted.
Another time I rooted, I used EasyFlasher and here is the thread on my rooting guide for that if you are interested: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
Once again, if you cannot get your tablet detected by ADB or APX, chances are it is a bad USB cable.

harley1rocker said:
-snip-
Click to expand...
Click to collapse
If you've 'tried everything', then it's likely Bad drivers or a bad USB cable, I'll assume you've tried my tool, the idcrisis tool, Easyflasher and wolf's method (Described by Fred) above.
If you'd like me to remote desktop you with Teamviewer to make sure your drivers are good I can do that, but if you've really tried everything then it's likely a bad cable.
ToD

To test the cable, simply transfer a file through USB with a known md5 signature, then verify it again after it's been transferred. You can use something like AFV to check the md5 once on the device. The bigger the file the better; the more chances it has to fail.

I GOT IT! holy crap! Ive gotta windows 7 comp. It turns out, it was the computer!. I completely wiped my laptop and started over. Still failed to flash recovery. I borrowed a friends computer and wah lah. Went into apx mode, got the new device found notification and installed the naked driver from device maneger. They finally took! This tablet is pretty old so I figure SBK1, nope, command wudnt run. No harm done. Went back and did SBK2 and FINALLY! Anyway, the first thing I do on any rooted device ready for a custom rom is do a nand back up. I kept gettin the "error path not known" or sumthin. This was on rogue. No offense to them, I never liked the lay out from the epic 4g touch days. So I loaded twrp. And now im able to do a back up.
And if I could not of gotten it, yes I would have let u remotely access my comp. It was the computer though. I trashed it and got me another this morning.
HUGE FREAKIN THANX TO ALL WHO RESPONDED. I still say this tablet is the toughest ive encountered by far. THANX FELLAS

harley1rocker said:
I GOT IT! holy crap! Ive gotta windows 7 comp. It turns out, it was the computer!. I completely wiped my laptop and started over. Still failed to flash recovery. I borrowed a friends computer and wah lah. Went into apx mode, got the new device found notification and installed the naked driver from device maneger. They finally took! This tablet is pretty old so I figure SBK1, nope, command wudnt run. No harm done. Went back and did SBK2 and FINALLY! Anyway, the first thing I do on any rooted device ready for a custom rom is do a nand back up. I kept gettin the "error path not known" or sumthin. This was on rogue. No offense to them, I never liked the lay out from the epic 4g touch days. So I loaded twrp. And now im able to do a back up.
And if I could not of gotten it, yes I would have let u remotely access my comp. It was the computer though. I trashed it and got me another this morning.
HUGE FREAKIN THANX TO ALL WHO RESPONDED. I still say this tablet is the toughest ive encountered by far. THANX FELLAS
Click to expand...
Click to collapse
Glad you got it sorted.

who got the 20 dollars
Sent from my Transformer TF101 using xda premium

stesteste said:
who got the 20 dollars
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Wasn't me. But I did not respond for the $20, I am just a good guy.

No one....yet. right after i posted that i got another comp. Installed naked drivers and wah lah. APX mode was recognized . But,if any1....fredreco. thanx for the info u posted.

harley1rocker said:
No one....yet. right after i posted that i got another comp. Installed naked drivers and wah lah. APX mode was recognized . But,if any1....fredreco. thanx for the info u posted.
Click to expand...
Click to collapse
We're all here to help, it really isn't about $, for me really it's just seeing that someone cares to donate that makes my day.. It's all about the passion of android though As fred will probably tell you.