Hello, earlier today I dropped my LGOG and shattered the glass rendering the touch scren absolutely useless, I'm taking it to get repaired but would like to do an adb backup for my apps as it will be a while before I can afford it though I have a slightly older temp android device.
My problem is this: plugging it into my computer displays mtp mode but I cannot see the device using "adb devices". I've read that sometimes usb eebugging and mtp dont get along well, any ideas on what I could do?
phazingazrael said:
Hello, earlier today I dropped my LGOG and shattered the glass rendering the touch scren absolutely useless, I'm taking it to get repaired but would like to do an adb backup for my apps as it will be a while before I can afford it though I have a slightly older temp android device.
My problem is this: plugging it into my computer displays mtp mode but I cannot see the device using "adb devices". I've read that sometimes usb eebugging and mtp dont get along well, any ideas on what I could do?
Click to expand...
Click to collapse
I would think you could get your files through fastboot. Also, clockworkmod has a USB mount mode, however for some reason i don't think twrp has that feature (idk y).
Sent from my LG-LS970 using Tapatalk
JESUSARIUS REX said:
I would think you could get your files through fastboot. Also, clockworkmod has a USB mount mode, however for some reason i don't think twrp has that feature (idk y).
Sent from my LG-LS970 using Tapatalk
Click to expand...
Click to collapse
Well, theres still the problem of switching from twrp to cwm I havent figured that bit out without a computer
phazingazrael said:
Well, theres still the problem of switching from twrp to cwm I havent figured that bit out without a computer
Click to expand...
Click to collapse
Tbh, I I haven't pushed a recovery with adb in a long time, so I can't tell you how to do it. However, I do recall it was relatively simple. I would go on the irc http://forum.xda-developers.com/showthread.php?t=1984620 and ask if someone can give you a link to the commands or guide you through it.
Sent from my LG-LS970 using Tapatalk
Theres still the issue of getting adb to accept the device
Related
So I recently decided to root my phone but I can't get past the actuall root process. I have the bootloader unlocked and everything but when I try to actually root it my computer can't seem to find the phone. I've attached two photos of what I'm looking at, if anyone needs more information I'll try to respond as fast as I can. I'm really confused by this. Thanks in advance
Forgive me if you did, but it's worth asking, did you wait the whole 160 seconds?
Sent from my Galaxy Nexus using Tapatalk
RTContent said:
Forgive me if you did, but it's worth asking, did you wait the whole 160 seconds?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Yes I did lol, I gave it about 5 minutes then I unplugged everything and tried again, I actually got a little farther and it said <Waiting for usb debugging to be enabled>.
But now it's not even being detected when I first open the root kit. At the top it lists no devices
Edit: Uploaded a screenshot of what i have now.. It's showing two devices and another pic showing where I'm stuck with the usb debugging.
Kosuda14 said:
Yes I did lol, I gave it about 5 minutes then I unplugged everything and tried again, I actually got a little farther and it said <Waiting for usb debugging to be enabled>.
But now it's not even being detected when I first open the root kit. At the top it lists no devices
Edit: Uploaded a screenshot of what i have now.. It's showing two devices and another pic showing where I'm stuck with the usb debugging.
Click to expand...
Click to collapse
So you do have USB debugging enabled right? Lol. You also have the GNex drivers installed, right?
anton2009 said:
So you do have USB debugging enabled right? Lol. You also have the GNex drivers installed, right?
Click to expand...
Click to collapse
USB Debugging is enabled and I do think I have the correct drivers, they're the ones that come with the root kit, I've also chceked in Device Manager and it looks correct from what I've seen. I've attached a picture of what my Device Manager looks like, I know its not much but maybe it's something. I'm just completely frustrated with this, it's been weeks and I can't figure it out
Kosuda14 said:
USB Debugging is enabled and I do think I have the correct drivers, they're the ones that come with the root kit, I've also chceked in Device Manager and it looks correct from what I've seen. I've attached a picture of what my Device Manager looks like, I know its not much but maybe it's something. I'm just completely frustrated with this, it's been weeks and I can't figure it out
Click to expand...
Click to collapse
when you connect the phone to the computer does your computer recognize it?
mailman64 said:
when you connect the phone to the computer does your computer recognize it?
Click to expand...
Click to collapse
The first thing to pop up is the Auto play thing, It says Galaxy Nexus so I'm guessing it does. Also in the earlier screen shots it shows my phone is connected to my computer. It will connect in fast boot and ADB.
Kosuda14 said:
USB Debugging is enabled and I do think I have the correct drivers, they're the ones that come with the root kit, I've also chceked in Device Manager and it looks correct from what I've seen. I've attached a picture of what my Device Manager looks like, I know its not much but maybe it's something. I'm just completely frustrated with this, it's been weeks and I can't figure it out
Click to expand...
Click to collapse
Well... if the toolkit isn't working out for you I'd recommend you do it manually. If you have any questions, just ask.
Kosuda14 said:
The first thing to pop up is the Auto play thing, It says Galaxy Nexus so I'm guessing it does. Also in the earlier screen shots it shows my phone is connected to my computer. It will connect in fast boot and ADB.
Click to expand...
Click to collapse
Ok if the computer is recognizing your phone then the drivers are correct. Are you sure that Settings>Developer Options>USB Debugging is checked? If so, are you following the toolkit instructions for rooting exactly? I'm just trying to make sure that you haven't missed something like I do so very often.
anton2009 said:
Well... if the toolkit isn't working out for you I'd recommend you do it manually. If you have any questions, just ask.
Click to expand...
Click to collapse
I've tried this in the past, I get stuck at the same exact thing. I can never get it to recognize it. It's weird I know, Like it will show up connected to my computer and everything but when I try <adb reboot bootloader> it says something like device not found.
mailman64 said:
Ok if the computer is recognizing your phone then the drivers are correct. Are you sure that Settings>Developer Options>USB Debugging is checked? If so, are you following the toolkit instructions for rooting exactly? I'm just trying to make sure that you haven't missed something like I do so very often.
Click to expand...
Click to collapse
I've watched videos of people doing this just to make sure I'm seeing what I'm suppose to see and for some reason mine just stops at the same point everytime
Kosuda14 said:
I've tried this in the past, I get stuck at the same exact thing. I can never get it to recognize it. It's weird I know, Like it will show up connected to my computer and everything but when I try <adb reboot bootloader> it says something like device not found.
I've watched videos of people doing this just to make sure I'm seeing what I'm suppose to see and for some reason mine just stops at the same point everytime
Click to expand...
Click to collapse
Have you been able to flash cwm recovery? also have you tried superboot instead of the toolkit?
mailman64 said:
Have you been able to flash cwm recovery? also have you tried superboot instead of the toolkit?
Click to expand...
Click to collapse
I'm trying superboot now, I'll post with updates. CWM hangs on downloading boot.img I think it is.
Ok Superboot worked. You're awesome I never heard of superboot before lol
Glad it worked! Sorry I didn't think about it sooner.
Hey all,
My power button stopped working and I, thinking it was a software issue, pulled the battery and found out I could not restart. I need to get into recovery or at least turn on the phone to unroot and relock it before heading to verizon.
So far I have had no luck turning the phone back on. I'm sure there is a way to do this... any help is greatly appreciated.
You can use a jig to go into the download mode
And flash a rom
Sent from my GT-N7000 using xda premium
Is the jig the only option? I don't currently have a jig so if that's the only thing I can do I will need to order one ASAP so I can get this thing working.
danteoo7 said:
You can use a jig to go into the download mode
And flash a rom
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
evahnyird said:
Hey all,
My power button stopped working and I, thinking it was a software issue, pulled the battery and found out I could not restart. I need to get into recovery or at least turn on the phone to unroot and relock it before heading to verizon.
So far I have had no luck turning the phone back on. I'm sure there is a way to do this... any help is greatly appreciated.
Click to expand...
Click to collapse
you might want to check this out..
http://www.ifixit.com/Answers/View/84579/Power+Button+stopped+responding.+Phone+will+not+turn+on.
Try to start it via adb, usb connect it, then type in adb devices, and then just adb reboot bootloader
Sent from my Sensation using xda premium
DesperadoX93 said:
Try to start it via adb, usb connect it, then type in adb devices, and then just adb reboot bootloader
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
Are you talking about in command prompt? I tried
Code:
adb-windows.exe devices
which returns " list of devices attached" with none listed.
If you can't get it to turn on they won't be able to either it will probably be fine.
Sent from my Galaxy Nexus using xda premium
Beamer9408 said:
If you can't get it to turn on they won't be able to either it will probably be fine.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The issue is that the phone is in no way broken other than the power button. I'll have to take it in and hope for the best if I can't figure something out, but I'd really like the peace of mind knowing that all of my files and data aren't stuck on it (I'd also like to get my lastest nandroid or do another one).
I saw a timing trick on http://forum.xda-developers.com/showthread.php?t=1731128 that is supposed to allow the device to boot, but I haven't gotten it to work yet.
Google wugfresh nexus root toolkit
It has a simple one click fix for flashing stock and unrooting when the device can't boot up
Or you can use something like glados cp to relock the boot loader as your rooted then delete the superuser apk in system app
Sent from my Galaxy Nexus using xda premium
I've gotten the phone into download mode using a jig, but it still doesn't seem to be recognized by the computer. Is this an issue of re-installing the Samsung drivers/adb or a limitation of download mode? Do I need to use odin?
evahnyird said:
I've gotten the phone into download mode using a jig, but it still doesn't seem to be recognized by the computer. Is this an issue of re-installing the Samsung drivers/adb or a limitation of download mode? Do I need to use odin?
Click to expand...
Click to collapse
Are you sure you have ADB configured properly for the device to be picked up via command line? USB debugging would have to of been turned on for ADB commands..
I'm almost positive USB debugging is on, especially since I think it's a default option in kang. I can get into download mode but not anything else. At this point I think I'm going to have to use ODIN and lose my data. Stupid power button...
Try removing the battery then tapping the metal battery pins against the phone pins repeatedly.
A friend of mine used to have to do this to get his nexus one to boot.. it can be a bit temperamental but does work.
evahnyird said:
I've gotten the phone into download mode using a jig, but it still doesn't seem to be recognized by the computer. Is this an issue of re-installing the Samsung drivers/adb or a limitation of download mode? Do I need to use odin?
Click to expand...
Click to collapse
Make sure you have the correct drivers installed. From download mode you will have to use Odin.
Note: since the device won't actually boot into Android, you don't have to worry about USB Debugging.
Note x2: the only driver that would let my device be recognized was the PDA Net driver, you may want to give it a try.
Sent from my Galaxy Nexus using Tapatalk 2
Well guys, thanks for all the suggestions. In the end I could get nothing to work other than Download mode with a jig and Odin to restore to stock. I lost everything on the phone, including my nandroid backups (should have copied them over more recently ...), but was able to re-lock the bootloader with nexus root toolkit after using Odin to flash the stock rom. ]
Moral of the story, if you lose your power button, you are screwed.
DesperadoX93 said:
Try to start it via adb, usb connect it, then type in adb devices, and then just adb reboot bootloader
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
Unfortunately you can't use adb to turn on a powered off device; not saying that wouldn't be awesome.
My Galaxy Nexus won’t boot into Paranoid Android after flashing a mod. It is not in a real bootloop (I don’t see a reboot including the Google splash screen) but keeps loading/booting the rom (Paranoid Android Logo). Reflash through recovery you would think.
Problem: my volumekeys are broken (cable broken when replacing USB-port)
So I can’t enter recovery with volume buttons. Therefor I wanted to use ADB commands but I only get ‘device not found’ when I type ADB devices or ADB reboot recovery.
ADB has always worked on this laptop so the drivers are installed correctly. Just to be sure I reinstalled the ADB drivers but with no success.
When I connect my Galaxy Nexus while in bootloop I see the Windows device manager showing: Galaxy Nexus (and after reinstall of ADB drivers it says Samsung Galaxy Nexus ADB Interface)
TLDR: Galaxy Nexus wont respond to ADB commands.
How to enter bootloader/recovery/push working rom or solve my problem any other way?
Try the galaxy nexus toolkit. It has an option for recovery even when ADB seems to be unavailable. Worked for me as my device was bricked.
wictor1992 said:
Try the galaxy nexus toolkit. It has an option for recovery even when ADB seems to be unavailable. Worked for me as my device was bricked.
Click to expand...
Click to collapse
Thank you for your reply. Could you tell me which option? Im in the toolkit now but can't seem to find the exact option you mentioned.
Is USB debugging on?
Sent from my i9250
bk201doesntexist said:
Is USB debugging on?
Sent from my i9250
Click to expand...
Click to collapse
To be honest I don't know. Since I just flashed Paranoid Android and booted my GN to see if it worked (which did) I immediately rebooted to flash the Mod. So it depends on the standard setting for this specific ROM.
Say it is not on, is there any way I could activate it without ADB and volume keys for recovery?
Im starting to think the only chance would be to buy new volume buttons strip and replace it myself.
I just don't get is why Windows recognises a Samsung Galaxy Nexus ADB Interface when i connect my phone while in bootloop and still the ADB drivers do not work.
bk201doesntexist said:
Is USB debugging on?
Sent from my i9250
Click to expand...
Click to collapse
this.. most likely debugging if not on
k786 said:
this.. most likely debugging if not on
Click to expand...
Click to collapse
I guess that is a problem, however i read some topics where people say that ADB should still work without USB Debugging on so I'm not really sure if that is the problem or not. Honestly I would think USB debugging would be on by default on a custom ROM to enable ADB in case of a bootloop.
Anyway, what are my options besides hardware repair volume button or buy new phone?
I'm having almost the exact same problem. Would appreciate it if you could PM me if you find a solution. Thanks.
Sent from my MB860 using xda app-developers app
mitchell.23 said:
I'm having almost the exact same problem. Would appreciate it if you could PM me if you find a solution. Thanks.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Unless someone knows a way to force ADB connection i think it will be a hardware repair for the volume button. If you find a solution let me know as well
there has to be a way
victor00100 said:
there has to be a way
Click to expand...
Click to collapse
Real helpful....
Anyway..if you can get to the bootanimation you're not bricked...even with the volume buttons not working. How badly are your volume buttons broken?
It should be possible if you know a bit of electrical stuff...if you find a way to close the circuit between the volume buttons then press the press the power button. It is possible...I just took apart my phone and if that isn't a problem for you, then it is possible to manually close the circuit.
Ok, I'm praying that someone can help me with a solution to this problem.
I have a T-Mobile Galaxy S2 that has a fantastically cracked LCD & Digitizer. It's so bad that the screen doesn't even turn on anymore. Maybe the ribbon cable is disconnected when I slammed the phone down on the counter thus cracking the screen. Who knows but I don't really want to tear it apart to find out.
Anyway the phone was rooted and running:
Juggernaut_50_0218
Blaze_4G_LB7
Sadly there is a pattern lock and I can't see the dumb screen to unlock it or do anything period. I know the phone works because I put the battery in and turn on the phone and I see all the touch buttons at the bottom light up.
Now, Kies doesn't even recognize the rooted device and I need to get my stuff off. Yes I know, I should've backed everything up but let's just say it was a hard learned lesson.
I know someone must've been able to get their files off their device that was in a similar situation. :crying:
Xyberz said:
Ok, I'm praying that someone can help me with a solution to this problem.
I have a T-Mobile Galaxy S2 that has a fantastically cracked LCD & Digitizer. It's so bad that the screen doesn't even turn on anymore. Maybe the ribbon cable is disconnected when I slammed the phone down on the counter thus cracking the screen. Who knows but I don't really want to tear it apart to find out.
Anyway the phone was rooted and running:
Juggernaut_50_0218
Blaze_4G_LB7
Sadly there is a pattern lock and I can't see the dumb screen to unlock it or do anything period. I know the phone works because I put the battery in and turn on the phone and I see all the touch buttons at the bottom light up.
Now, Kies doesn't even recognize the rooted device and I need to get my stuff off. Yes I know, I should've backed everything up but let's just say it was a hard learned lesson.
I know someone must've been able to get their files off their device that was in a similar situation. :crying:
Click to expand...
Click to collapse
Try booting into recovery and copy whatever possible, I'm not sure about installed files though :/
Maybe you could use adb or something
I can't see the screen to be able to even know which screen it's at. How would I do that?
Hopefully you had debigging enabled. If you did, boot it up normal. Then use the adb pull command from your computer. HTH
Sent from my SGH-T989 using Tapatalk 2
ackliph said:
Hopefully you had debigging enabled. If you did, boot it up normal. Then use the adb pull command from your computer. HTH
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I'm not sure but I'm assuming it was since the phone was rooted with a custom rom. It's been a little while since I've seen this phone on.
Don't know how to use ADB pull command and what software to do it with.
Xyberz said:
I'm not sure but I'm assuming it was since the phone was rooted with a custom rom. It's been a little while since I've seen this phone on.
Don't know how to use ADB pull command and what software to do it with.
Click to expand...
Click to collapse
I'm not by my computer now, but I'll try to steer you in the right direction. Adb.exe should be on your computer somewhere. If not, do a google search. Usually you can find adb.exe and fastboot.exe packaged together. You'll then want to use adb to pull your files. Open up a command prompt. Change to the directory that has adb.exe. then type "adb pull /data \data" you can also try "adb pull /sdcard \sdcard"
You can also try the adb pull command after you boot into recovery mode. Play with it. I bet you can do it.
Sent from my SGH-T989 using Tapatalk 2
---------- Post added 27th February 2013 at 12:02 AM ---------- Previous post was 26th February 2013 at 11:59 PM ----------
Here is adb in the download section on the first post.
http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1
Sent from my SGH-T989 using Tapatalk 2
ackliph said:
I'm not by my computer now, but I'll try to steer you in the right direction. Adb.exe should be on your computer somewhere. If not, do a google search. Usually you can find adb.exe and fastboot.exe packaged together. You'll then want to use adb to pull your files. Open up a command prompt. Change to the directory that has adb.exe. then type "adb pull /data \data" you can also try "adb pull /sdcard \sdcard"
You can also try the adb pull command after you boot into recovery mode. Play with it. I bet you can do it.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
Ok, I will try this later on when I get home from work. I'm praying it works but hate using command prompts lol. GUI is always easier but I can't complain if it works!
Phone is going full retard now
I have been using CyanogenMod 10.1 nightly 'till now.
I fell down one day and since then it's stuck on the CyanogenMod boot logo. forever.
Recovery is accessible, and I've tried flashing the rom again but I can't get past the point when I should type in adb "fastboot flash boot boot.img"
It's just "<waiting for device>"
and nothing's happening.
even though the device appears on the adb devices list.
I also can't mount storage through recovery.
What the **** is happening to my phone and what can I do to fix it?
Does it appear on the fastboot devices list? Is your phone in fastboot mode, not hboot?
Did you try flashing an RUU?
Sent from my Desire HD using Tapatalk 4 Beta
bananagranola said:
Does it appear on the fastboot devices list? Is your phone in fastboot mode, not hboot?
Click to expand...
Click to collapse
Uhm, it depends. usually it appears on the devices list on adb when I do things right.
It only appeared when I was in clockworkmod recovery though.
The usb completly disconnects whenever I'm in hboot/white background thing.
humzaahmed155 said:
Did you try flashing an RUU?
Sent from my Desire HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
Which RUU though? there are thousands. I didn't try
You helped me that other time to root my phone, if you remember.
well I'm now really scared of flashing RUUs and doing factory resets, as I'm scared the phone will unroot.
YagFrazier said:
Uhm, it depends. usually it appears on the devices list on adb when I do things right.
It only appeared when I was in clockworkmod recovery though.
The usb completly disconnects whenever I'm in hboot/white background thing.
Which RUU though? there are thousands. I didn't try
You helped me that other time to root my phone, if you remember.
well I'm now really scared of flashing RUUs and doing factory resets, as I'm scared the phone will unroot.
Click to expand...
Click to collapse
Hmm, so it looks like your computer isn't detecting your phone in fastboot right, go into device manager and check what the phone has been installed as, Windows sometimes likes to mess around with drivers when it comes to Android phones and debugging
Sent from my Desire HD using Tapatalk 4
Wait, adb and fastboot are not them same...
humzaahmed155 said:
Hmm, so it looks like your computer isn't detecting your phone in fastboot right, go into device manager and check what the phone has been installed as, Windows sometimes likes to mess around with drivers when it comes to Android phones and debugging
Sent from my Desire HD using Tapatalk 4
Click to expand...
Click to collapse
By the way did you select Fastboot when in hboot?
Sent from my Desire HD using Tapatalk 4
YagFrazier said:
Uhm, it depends. usually it appears on the devices list on adb when I do things right.
It only appeared when I was in clockworkmod recovery though.
The usb completly disconnects whenever I'm in hboot/white background thing.
Which RUU though? there are thousands. I didn't try
You helped me that other time to root my phone, if you remember.
well I'm now really scared of flashing RUUs and doing factory resets, as I'm scared the phone will unroot.
Click to expand...
Click to collapse
Have you tried re installing the drivers with the phone unplugged? if you are using windows OS. Try using a different USB port, plugged directly to the motherboard. Do not use a usb hub
humzaahmed155 said:
Hmm, so it looks like your computer isn't detecting your phone in fastboot right, go into device manager and check what the phone has been installed as, Windows sometimes likes to mess around with drivers when it comes to Android phones and debugging
Sent from my Desire HD using Tapatalk 4
Click to expand...
Click to collapse
Yup, my USB also got broken last time I tried to root and this time I used my dad's Kindle USB. looks like it didn't fit that well with the device or something, he got me a normal USB thing and now I can even mount USB storage through ClockworkMod recovery. great since I needed to backup photos.
humzaahmed155 said:
By the way did you select Fastboot when in hboot?
Sent from my Desire HD using Tapatalk 4
Click to expand...
Click to collapse
Nope, looks like that was the problem. stupid me.
It works, it boots. everything seems alright.
The thing is, now there's no wifi. it doesn't want to go on at all.
I've been trying to switch it on for an hour now, it just "turns wifi on" and goes off again. the off button is gray.
Edit: I switched between CyanogenMod 10.1 Nightlies and CodefireXperiment ROM and with nova launcher it's the same, just better now. so happy to have my phone now
YagFrazier said:
Yup, my USB also got broken last time I tried to root and this time I used my dad's Kindle USB. looks like it didn't fit that well with the device or something, he got me a normal USB thing and now I can even mount USB storage through ClockworkMod recovery. great since I needed to backup photos.
Nope, looks like that was the problem. stupid me.
It works, it boots. everything seems alright.
The thing is, now there's no wifi. it doesn't want to go on at all.
I've been trying to switch it on for an hour now, it just "turns wifi on" and goes off again. the off button is gray.
Edit: I switched between CyanogenMod 10.1 Nightlies and CodefireXperiment ROM and with nova launcher it's the same, just better now. so happy to have my phone now
Click to expand...
Click to collapse
Hmm that wifi issue seems interesting, glad i could help
YagFrazier said:
The thing is, now there's no wifi. it doesn't want to go on at all.
I've been trying to switch it on for an hour now, it just "turns wifi on" and goes off again. the off button is gray.
Edit: I switched between CyanogenMod 10.1 Nightlies and CodefireXperiment ROM and with nova launcher it's the same, just better now. so happy to have my phone now
Click to expand...
Click to collapse
Had the same problem with cyanogen10.1, no wifi. I think some DHD's won't work with all cyanogen's. With the XPERIA rom i had wifi, but no GPS In another rom (don't know, which it was) phone said no pictures (but there were 15 to see with ghostcommander...)
Now i installed Android Revolution 7.0 (its a 2.3.5, but its very stable, all works fine...).
It seems, that some DHD's dont't like Android 4 and above... :crying:
ammo12 said:
Had the same problem with cyanogen10.1, no wifi. I think some DHD's won't work with all cyanogen's. With the XPERIA rom i had wifi, but no GPS In another rom (don't know, which it was) phone said no pictures (but there were 15 to see with ghostcommander...)
Now i installed Android Revolution 7.0 (its a 2.3.5, but its very stable, all works fine...).
It seems, that some DHD's dont't like Android 4 and above... :crying:
Click to expand...
Click to collapse
Get yourself a CodefireXperiment rom. Together with Nova launcher it's the same as CyanogenMod and even better.
Wifi's good.
I usually stay away from Android Revolution, I developed sincere hate for Sense 3.6 and below.