• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Cannot see SD Card / ADB can't see phone

farva

Member
Hi all -

My third time rooting an EVO unfortunately went a bit south and now I'm experiencing issues with the EVO recognizing the SD card and with ADB recognizing my phone.

The bootloader can see and read from the SD card as I am able to flash PC36IMG files, but once the phone is booted up it cannot read from the card and will not charge via USB. The RUU utility also cannot find the phone. I have found a thread on XDA that appears to resolve this issue ([ How-To ] Fix SD card not being detected & USB port not working - xda-developers) but it requires ADB commands run in the bootloader.

When I am in the bootloader and select FASTBOOT, the header changes to "FASTBOOT USB", the Windows driver appears to pick it up but ADB keeps giving me a "error: device not found" when I run the "adb shell" command.

Here is my bootloader info:

SUPERSONIC EVT3 SHIP S-ON
HBOOT 2.10.0001
MICROP-041f
TOUCH PANEL-AMTEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010,12:07:00

I do not have a custom recovery loaded, if I select Recovery from the bootloader menu it will give me the EVO/red exclamation point message - I can then hit volume up + Power and it will take me to the default recovery so I can wipe data/cache.

Is anyone familiar with how I can regain SD card/charging capability or ADB connectivity so I can use the fix from that XDA thread? Ideally I'd like to just run the RUU so I can return to stock and retry the rooting process but I'm in a bit of no-man's land right now. Thanks in advance, and let me know if I can provide any additional info.

EDIT: I was able to get the RUU to connect to the phone when it was in FASTBOOT USB mode and sucessfully flashed the 3.70.651.1 but I still have the exact same issues with the SD card and ADB. When I boot into the ROM, Windows displays the "Qualcomm CDMA Technologies MSM" device message, cannot find a diver (I have the HTC drivers installed) and then the EVO eventually reboots ... like a veeeerrrry slow bootloop. When FASTBOOT USB is enabled, Device Manager shows an "Android USB Device", with "My HTC" underneath.
 
Hi all -

My third time rooting an EVO unfortunately went a bit south and now I'm experiencing issues with the EVO recognizing the SD card and with ADB recognizing my phone.

The bootloader can see and read from the SD card as I am able to flash PC36IMG files, but once the phone is booted up it cannot read from the card and will not charge via USB. The RUU utility also cannot find the phone. I have found a thread on XDA that appears to resolve this issue ([ How-To ] Fix SD card not being detected & USB port not working - xda-developers) but it requires ADB commands run in the bootloader.

When I am in the bootloader and select FASTBOOT, the header changes to "FASTBOOT USB", the Windows driver appears to pick it up but ADB keeps giving me a "error: device not found" when I run the "adb shell" command.

Here is my bootloader info:

SUPERSONIC EVT3 SHIP S-ON
HBOOT ...........

Not sure about this one buddy, but if youre familiar with the forum, someone with the technical knowledge should happen along eventually, orrrrrrr if i were you i'd pm akazabam.... that dood is like yoda around the EVO water cooler, if he cant help ya, i bet he knows someone who can. Best of luck homey :)
 
I believe I was able to resolve the SD card issues by using a slightly modified version of the procedure in the XDA thread I linked in my original post, fingers crossed on that one.

I still have bootloops once my phone gets up and running - I had it going long enough to verify the software versions and I have the 3.70.651.1 OTA but only the 1.34_003 PRI and 60662 PRL. I know the PRI has caused issues before when paired with an incorrect OTA, does anyone know if I can flash the 1.90_003 PRI in this link from HBOOT or the non-custom recovery I can access (there is an option for flash update.zip):

[ Radios ][ 12-17 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions - xda-developers
 
right on:) yeah, man..... im of absolutely no help here. only thing i can say is that theres a list of folks that scour these forums who can usually get this type of thing figured out pretty quick, and im actually kinda shocked that i havent seen mr.ed, akazabam, evomattnc, oceanbrz etc etc in here offering up some advice. but if youre familiar with this place, im sure thay wouldnt be put off if you asked them directly. theyve all been very helpful to me in the past, and courteous ta boot :)
 
right on:) yeah, man..... im of absolutely no help here. only thing i can say is that theres a list of folks that scour these forums who can usually get this type of thing figured out pretty quick, and im actually kinda shocked that i havent seen mr.ed, akazabam, evomattnc, oceanbrz etc etc in here offering up some advice. but if youre familiar with this place, im sure thay wouldnt be put off if you asked them directly. theyve all been very helpful to me in the past, and courteous ta boot :)
Akazabam was helping me the last couple of days with the exact same problem, but we havent found a solution yet.
 
Akazabam has been very helpful to me in the past as well (when I restored an AOSP Titanium Backup in a Sense ROM and had all kinds of weird shit happen :) ) ... at this point I'm pretty confident I can get it working again, but it's a couple of those problems where most of the threads on various boards lead to dead ends so it will take some poking around and trial&error.

Ivansandroid, if you're still having SD card issues I believe I have resolved that ... let me know if I can help in anyway.
 
Akazabam has been very helpful to me in the past as well (when I restored an AOSP Titanium Backup in a Sense ROM and had all kinds of weird shit happen :) ) ... at this point I'm pretty confident I can get it working again, but it's a couple of those problems where most of the threads on various boards lead to dead ends so it will take some poking around and trial&error.

Ivansandroid, if you're still having SD card issues I believe I have resolved that ... let me know if I can help in anyway.
Yeah I would love some help if you can
 
This is the thread that finally seems to have fixed my SD card:

[ How-To ] Fix SD card not being detected & USB port not working - xda-developers

You will need a card reader or some other way to load the contents of the two ZIP files attached to that post onto your SD card (not the actual ZIPs themselves). Once they are on your SD card boot into the bootloader (press Power while holding volume down) and select "FASTBOOT" - my phone then automatically switched into "FASTBOOT USB" and I was able to verify that I had "Android USB Device" listed in my Device Manager.

Once you have "FASTBOOT USB" status, you can use the fastboot.exe command that is part of the Android SDK (which you will need to download and install if you haven't already). Open a DOS prompt and change the directory to the "tools" folder in the SDK install - mine was c:\Program Files\android\android-sdk\tools. Once there, type the following commands, pressing enter after each:

fastboot oem enableqxdm 0
fastboot reboot

Each should give you a little confirmation message, and that's it - next time you boot into your ROM you should see the "Preparing SD card" message. I was able to go into the "SD card" menu in Settings and verified that the system could read it.

As for your radios, PRI, etc., you can download the file in this thread (the ZIP in the first two links, not the full RUU .exe), rename it "update.zip" and put it in the root of your SD card. Then you can boot into Recovery from the bootloader and flash that update.zip. If you get the "EVO with a red exclamation point" screen when loading Recovery, hold volume UP and Power - you may have to do this key combo a couple times but the Recovery menu should pop up.

OTA_supersonic_3.70 + full RUU - xda-developers
 
Now if I can just resolve these reboots I'll be in business :) ... I even just reflashed the 3.70.651.1 RUU after upgrading to the 1.90 PRI and still no dice.
 
Holy taco batman it worked. I had all of the sdk tools and stuff from when I rooted with unrevoked (before they had plug and play). It was hard to remember how to do the whole adb thing but I figured it out, HA HA got evo back.
 
I found z4root to give me temporary root to run the second part of the fix the usb, but when I type in the command prompts through emulator it keeps saying image not found on sd card when I know its there. Any ideas
 
Okay, now that I'm actually reading this, I will say that I was partially wrong when I told you it wouldn't work in a different thread (obviously) as you were able to do the first part. That was my bad for not actually reading it thoroughly. As for the second part, though, that is the first part of a very old root method, and I'm not confident that it's a good idea to actually try to make that work. You have a newer, updated phone, and there's a chance that it could cause bigger problems if you actually made it "work". You might want to give me or someone else some time to look into this one before trying that again.
 
Does anyone have an idea of what could be causing consistent reboots? Everytime the phone loads the stock ROM it will freeze up within 60 seconds and reboot. I've run the RUU, flashed an update.zip with the correct OTA in the stock recovery ... nothing seems to get me past these reboots.
 
What is the update.zip that you flashed? Have you verified that you have the latest radios and hboot (just because you flashed it doesn't mean it worked)? You might want to try flashing PC36IMG.zip of the latest OTA update, but verify the above information, first.
 
Sorry Farva have no idea.
Azakabam the error I recieved was the image wasn't found.
But after reading your warning I'll wait. Also I noticed my bluetooth is inoperable. Thx
 
What is the update.zip that you flashed? Have you verified that you have the latest radios and hboot (just because you flashed it doesn't mean it worked)? You might want to try flashing PC36IMG.zip of the latest OTA update, but verify the above information, first.

I have the 2.10.0001 HBOOT and the 2.15.00.11.19 radio, both according to my bootloader screen.

The phone stays booted long enough to get to the Settings > Phone Info menu and the Software section confirms the radio and also the following info:

Kernel: 2.6.32.17-gee557fd
Build Number: 3.70.651.1 CL294884
Software: 3.70.651.1
PRI: 1.90_003
PRL: 60677

I can't see any obvious conflicts here but I'm sure there could be something. I flashed the ZIP file in this thread as an update.zip, I have also flashed the 3.70.651.1 OTA as a PC36IMG, which I believe is the latest version.

http://forum.xda-developers.com/showthread.php?t=874091
 
Is there anything the RUU does not touch when it is successfully loaded onto a phone? I really don't understand how I can still be getting reboots at the exact same point every time the stock ROMs loads (about 30 seconds after) even after running the RUU.
 
Any updates to this? i have the same issues i have restored access to the sd card but i still have the constant reboot, it did stop once and a sprint icon was at the top looked like an update for a sprint application i didnt look to hard but i used it for about 10 min but when i re-booted i got the loop again.
 
Back
Top Bottom