Related
I have a new Evo and it came with the latest radio installed. Because of that I did the unrevoked3 root process. While trying to get Fresh Evo in place I have really knackered this phone.
After it has booted it no longer sees the SD card. It also doesn't charge over USB unless I have it plugged into a wall socket. The PC doesn't detect the phone at all.
I've tried other SD cards and it doesn't fix the problem. I have also tried other Android phones and cables and it is only this phone that no longer works.
Any suggestions on how to recover? Any recovery that requires that I go into recovery will not work. (Did I mention that I can boot into hboot, etc, but not recovery?) Anything that might try to use USB won't work either. I can put a PC36IMG type file in place and fastboot will scan it. However the few I've tried haven't got me anywhere.
Try this: http://forum.xda-developers.com/showthread.php?t=695243
I lost my SD and USB after I rooted, but that got me back on track
Success! Or at least in part.
Thanks mistersquirrle.
The USB still doesn't work but I'll try it again and see if that fixes things. These things often take a few tries...
vanstrien said:
Success! Or at least in part.
Thanks mistersquirrle.
The USB still doesn't work but I'll try it again and see if that fixes things. These things often take a few tries...
Click to expand...
Click to collapse
I think that my USB took more than one try, not sure. Glad I could help though, I keep that link on my bookmarks, just incase
BTW, edit the post if you can and put [FIXED] if you get it all good, so it's not misleading
I did it a couple more times and it finally took. Thanks!
Hello,
I have tried attempted to root and flash a new ROM on my phone and now I seem to have lost SD and USB support. it does not recognize any of the SD cards i put it (doesn't realize theres an SD card inside) and does not recognize any USB plugged in.
I have HBOOT .80 and i THINK i got the root correct (lotsa problems along the way so i'm not sure), but i was able to flash a ROM (NexTSENSE) so i think it worked. now, i saw a thread about fixing USB support but that required SD support. and reading that made me feel like i was royally screwed. in any case, any suggestions? I think USB support is still kinda there since I can get it to recognize it in the boot menu. but when i try to do it in recovery and use the flash rom .bat, it says device not found.
it would seem that the main concern right now is that i can't get it to see my SD cards. any of them, even after reformats and whatnot.
i can't connect to HTC Sync or anything of the of the sort. usually when i charge the phone, you get the charging notification but i don't even get that now. sounds like a driver problem but i can't see what is wrong. my computer doesn't even recognize the phone as a device every now and then
Hope i provided sufficient information. New to android scene so don't be too hard on me please =O but yea, any suggestions are welcome. thanks in advance
edit: usb support... ever so slightly back. aka, it charges now. probably was drivers on my lappy getting funny after moving between bootloader and recovery and all that fun stuff
You have the usb brick issue. Check out the thread on that. Also once you are up and running again, root using unrevoked or the fake flash method. All information is available in the dev forum.
ok, i've done some reading and this is what i've found so far. my phone is stuck in USB debug hence no USB support and somewhere along the way, SD support was disabled. from what i see, the fix is to
first:
reload the step1 of root to get back to 1.15 and basic root access.
second:
from there, i can re-enable SD support using the command:
fastboot oem enableqxdm 0
third:
apply USB-Brick fix found in post 1 of thread
and then i should be able to reload ROMs as usual. is this correct?
and where exactly do i put in the command to re-enable SD support? this is what has be confused right now. along with the commands for the USB fix
i am using the tinycore method so i just have the step1.sh. and then in the same console, can i enter that command? should i do it after a reboot? or load back into bootloader to do it. (bootloader or fastloader)
OOOOK. sorry about the continuous posts. putting new info up so it isn't exactly a bump right?
in any case, i used the androidSDK tools and ran the fastboot from there and i think i re-enabled my SD correctly. i was then able to run the USB-brick fix found on modaco forums. all done and done. nowww, since i just went through half the root process (step1.sh with tinycore), do i need to finish it? or since i had already rooted before, is it all done now?
I'm not 100% sure about that as I haven't had to fix the usb brick for ages now!
Download and install titanium backup from the market. If it works fine, then you are rooted. If not, root woth unrEVOked or fakeflash.
All the older root methods that require usb during the root process leave you open to the usb brick again.
Hi fatpandas..
Is your phone ok now? Actually my phone also have a problem like yours last week..until now,i can't fix it..if now your phone ok,can u share with me..thnks in advance..
@csyrix
sorry to hear about your situation. after just being there, i can tell how horrible it is. good news is, if you really have the same problem, then it is definitely fixable.
now, i don't know what method you used to flash yours the first time but from what i've seen, they're mostly the same. what you wanna do first is do that step1 thing where you have a temporary ROM installed. (1.15?) same process as usual.
then you'll need to run 'fastboot oem enableqxdm 0' with phone plugged in while in FASTBOOT (back button + power button thing)
in case you don't know where to put that in, you wanna run that in your command prompt (computer) while operating in the tools folder of the android SDK. (thank god for my limited computer knowledge cuz all the instructions i found just say, "run this command" and like hell if most know how/where)
in any case, the end result will be you having completed step1 and having re-enabled SD support. then turn off phone.
then get the fix from this thread
move that to your SD card (micro SD adapter) and turn back on your phone into bootloader. go to the recovery menu and hold volume up + power to bring up menu and hit the apply: update.zip.
then all should be well. i then moved on to step2 to make sure i had rooted properly. may not be necessary but i remember reading that rooting a rooted device isn't a problem so i just felt the need to do it to be safe.
that should be it. the link provided actually has all the instructions anyways (i hope mine are a bit more clear), but if not, that link should be able to fill in the holes. g'luck sir
I tried to root it a few weeks ago, but it didn't quite work, so i did a hard reset.
Everything works, except the phone won't boot with the SD card in it (it just keeps looping at the "MyTouch 3g Slide" screen. And the phone will not recognize any SD card. i've tried three. the original samsung 8gb, a kingston 2gb, and a 16gb one. all the cards work perfectly on my computer, one is used to run android on my HD2. so i KNOW it works. I've tried reformatting it also, and that didn't work (FAT32).
how can i fix this?
HotEspresso said:
I tried to root it a few weeks ago, but it didn't quite work, so i did a hard reset.
Everything works, except the phone won't boot with the SD card in it (it just keeps looping at the "MyTouch 3g Slide" screen. And the phone will not recognize any SD card. i've tried three. the original samsung 8gb, a kingston 2gb, and a 16gb one. all the cards work perfectly on my computer, one is used to run android on my HD2. so i KNOW it works. I've tried reformatting it also, and that didn't work (FAT32).
how can i fix this?
Click to expand...
Click to collapse
Can you get to the bootloader and recovery with the SD card in it? If you don't know how hold down the vol down button and power button, then use the volume rocker to go down to recovery and pres power again to select it. If you can't access the bootloader with an sd card in it I would suspect a hardware issue but I'm not sure. If you can get into recovery and flash clockworkmod recovery, then re-download and flash a ROM, such as cyanogenmod 6.1.0 or CR_mod or something. Just to rule out a ROM error.
Might want to try a full wipe again using recovery if you can get into it.
MusicMan374 said:
Can you get to the bootloader and recovery with the SD card in it? If you don't know how hold down the vol down button and power button, then use the volume rocker to go down to recovery and pres power again to select it. If you can't access the bootloader with an sd card in it I would suspect a hardware issue but I'm not sure. If you can get into recovery and flash clockworkmod recovery, then re-download and flash a ROM, such as cyanogenmod 6.1.0 or CR_mod or something. Just to rule out a ROM error.
Click to expand...
Click to collapse
in order to flash CM or clockworkmod recovery, i need to have my phone rooted, correct? what's the easiest way?
HotEspresso said:
in order to flash CM or clockworkmod recovery, i need to have my phone rooted, correct? what's the easiest way?
Click to expand...
Click to collapse
In the Dev section for our phone THIS method.
Also, check the slide rom bible for some other stuff you might need, like the stock rom.
Oh, I assumed you were rooted. When you power on with Vol Down, the first screen is hboot... isn't there a full wipe option there, therefore not requiring the OP to go into recovery?
Yeah, there is a wipe option in Hboot.
fermunky said:
Oh, I assumed you were rooted. When you power on with Vol Down, the first screen is hboot... isn't there a full wipe option there, therefore not requiring the OP to go into recovery?
Click to expand...
Click to collapse
nope. not yet, at least. i'm working on it now, but i keep running into problems. the latest one, is when i run the "adb push exploid /sqlite_stmt_journals" command in step 4, it just says "error: device not found". i'm pretty sure i've done everything right.
is there anyone willing to help walk me through this with an instant messenger or something? i can probably figure it out eventually, but help would be much appreciated.
also, when i plug the phone into the computer, the phone charges, but doesn't recognize the phone. windows (7) says it can't identify it. and when i unplug the phone, it resets.
HotEspresso said:
nope. not yet, at least. i'm working on it now, but i keep running into problems. the latest one, is when i run the "adb push exploid /sqlite_stmt_journals" command in step 4, it just says "error: device not found". i'm pretty sure i've done everything right.
is there anyone willing to help walk me through this with an instant messenger or something? i can probably figure it out eventually, but help would be much appreciated.
also, when i plug the phone into the computer, the phone charges, but doesn't recognize the phone. windows (7) says it can't identify it. and when i unplug the phone, it resets.
Click to expand...
Click to collapse
Yeah you have to download the drivers for the phone. Here's the link: http://www.htc.com/us/support/t-mobile-mytouch-3g-slide/downloads/
Download the sync update, it'll install the drivers necessary for adb to work
MusicMan374 said:
Yeah you have to download the drivers for the phone. Here's the link: http://www.htc.com/us/support/t-mobile-mytouch-3g-slide/downloads/
Download the sync update, it'll install the drivers necessary for adb to work
Click to expand...
Click to collapse
still doesn't work. nothing shows up when i run "adb devices", and it says "error: device not found" when i run the adb push... command.
any ideas?
HotEspresso said:
still doesn't work. nothing shows up when i run "adb devices", and it says "error: device not found" when i run the adb push... command.
any ideas?
Click to expand...
Click to collapse
Do you have USB debugging enabled on your phone?
Sent from my T-Mobile myTouch 3G Slide
MusicMan374 said:
Do you have USB debugging enabled on your phone?
Sent from my T-Mobile myTouch 3G Slide
Click to expand...
Click to collapse
yes i do. i've done everything right.
if it helps, hboot does see my SD card. so i know it's not a hardware issue.
is there any way i can load the original stock firmware? i loaded ESPRIMG.zip and it worked, but didn't do anything.
It must be an issue on the computer side with your computer not recognizing your phone. I'm on my phone at the moment, with an almost dead battery (bad cm6.1 battery life) but when I get to a computer I'll look it up, there's something else you might have to install. Are you on xp vista or 7?
Sent from my T-Mobile myTouch 3G Slide
thanks. i've got windows 7. i can try using another computer. i'll post when i try that.
i called HTC and i'm still under warranty. but will they be able to see my root attempt and not repair it? i don't wanna be charged the $40 "triage fee"
HotEspresso said:
thanks. i've got windows 7. i can try using another computer. i'll post when i try that.
i called HTC and i'm still under warranty. but will they be able to see my root attempt and not repair it? i don't wanna be charged the $40 "triage fee"
Click to expand...
Click to collapse
Yes, they will see your root attempt and say you voided your warranty, but it's easy to unroot. Although I don't think your phone is the issue here, since you can still see your microsd card when you plug into your computer, right? Like if you mount USB storage, it works?
Also, try following the instructions in the link I'm about to paste, I used it and it worked fine for me: http://androidforums.com/t-mobile-mytouch-slide/90832-adb-drivers.html
MusicMan374 said:
Yes, they will see your root attempt and say you voided your warranty, but it's easy to unroot. Although I don't think your phone is the issue here, since you can still see your microsd card when you plug into your computer, right? Like if you mount USB storage, it works?
Also, try following the instructions in the link I'm about to paste, I used it and it worked fine for me: http://androidforums.com/t-mobile-mytouch-slide/90832-adb-drivers.html
Click to expand...
Click to collapse
not from the phone. but i can take the SD card out and put it into my computer.
i'll try the link now.
nope. i already had that driver. but i installed it again anyway. no luck. how can i restore to good enough condition so HTC will fix it?
HotEspresso said:
nope. i already had that driver. but i installed it again anyway. no luck. how can i restore to good enough condition so HTC will fix it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=746577 Flash that, it will flash the pure stock w/OTA update, without root or wifi tether, it's just pure stock. They don't think twice about it.
And if you cant mount usb storage on your phone and see it on your computer, then I think your phone does have an issue with the usb port. Either that or it's a rom issue? Could be something corrupted.
MusicMan374 said:
http://forum.xda-developers.com/showthread.php?t=746577 Flash that, it will flash the pure stock w/OTA update, without root or wifi tether, it's just pure stock. They don't think twice about it.
And if you cant mount usb storage on your phone and see it on your computer, then I think your phone does have an issue with the usb port. Either that or it's a rom issue? Could be something corrupted.
Click to expand...
Click to collapse
it MIGHT be a usb issue, but i doubt it. it can't be a rom issue, because i haven't rooted the phone.
when i hit apply update.zip in recovery, it just says "can't find /sdcard/update.zip". it's definitely there, in the root of the SD card.
any ideas?
EDIT: i just used hboot to load ESPRIMG.zip. i THINK that worked. but it still says firmware 2.1-update 1. will that be enough to clear it for HTC?
Hi chaps, I've done a lot of searching but unlike many who managed to fix theirs I fear that my Desire is dead. Did a nandroid backup and during reboot for one reason or another (likely the cheap Ebay battery) the phone rebooted a couple of times and I suspect it's corrupted the ext4 that was holding data. Phone was running Starburst 1.5 Classic with data2sd. It's also s-off.
Ok, I've read threads where people have plugged it in and using adb have managed to issue a command to have the phone re-enable the sd card. The issue I have is that adb doesn't even recognise that the phone is actually connected. I've tried this on both my PC and laptop with no joy.
I can still get into recovery and also fastboot and there must be some life as the phone recognises the USB connection when plugged into the PC but 'adb devices' gives me nothing so I therefore can't issue commands.
I have also tried putting the original firmware back on via PB99IMG.zip but since the phone's not reading the card at all that too is a dead end. It still boots to recovery and I get the 'Why so serious' logo if I try starting the phone up but I just can't get any further with it.
Anyone any ideas?
You can wipe and flash partitions and files from fastboot
http://android-dls.com/wiki/index.php?title=Fastboot
Once you get it working, restore your nandroid to see if it's working and not corrupted by the reboot. If it's not working, you can rebuild in fastboot!
Ok, I'm doing some more reading and learning, driving me nuts this thing. Cheers.
Edit: That won't work as I cannot gain access to the phone from the PC. adb devices show nothing connected even when it clearly is.
Edit 2: C:\Android\android-sdk\platform-tools>fastboot
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Perhaps I'm missing something???
Sorted I think, was me being a n00b. Will post back if I manage to get it all running again.
Did you get fastboot to work and recognise your device?
Take a look at the thread I posted earlier, the command to check it is
Code:
fastboot devices
So just as the title says, but here's a little back story (might help).
I'm trying to help out a friend with his Bell Mobility i747M. He wanted to try out Lollipop, so I looked into it and said I could do it. Last I even touched his phone was quite a while ago when he wanted me to flash CM11, back when KK was still pretty new. So it's been over a year. I flashed CWM back then, got the ROM installed, and everything has been good ever since. Fast forward to now, and he wants to try Lollipop. I figured the first thing I should do is update the bootloader/radio, which went perfectly fine (after some researching, I chose 4.3/MK5 for his i747M). I tested them by booting back to the ROM and checking About Phone - everything was good. So I booted back to the old version of CWM, and thought it would be a good idea to get a more modern recovery. CWM or TWRP didn't matter, just as long as it was more up to date (I thought it might help with Lollipop compatibility). So I decided on TWRP, and I got the latest version (2.8.4.0 as of now) and flashed it. Successfully flashed, then rebooted recovery. TWRP is there and working. Great. Next step... I had the Lollipop ROM and Gapps already downloaded and ready to go, so in TWRP, I proceeded to wipe everything (system, data, cache, internal sd).
Uh oh... Half way through wiping, the phone reboots itself! Now there's no ROM, so naturally it has nothing to boot to. Try going back to TWRP, and I see the splash screen again. OK, false alarm... Well, not really... Because now it just reboots itself after the splash screen, every time. Can't get into TWRP no matter what! I can access download mode, but Odin doesn't recognize the phone. Yes, I have the drivers. In fact, the device isn't detected by Windows at all.
So here we are. Download mode boots, but Odin doesn't work because there's no communication through USB at all. There's no ROM on the phone because it was wiped. And TWRP won't boot beyond the splash screen.... Now what?? I tried the 80MB MK5 debricking .img on a 64GB microSD. It does nothing - besides, USB isn't reading anyway, so it's not like I can proceed with Odin.
I'm at a stalemate here... Any suggestions?
My friend's gonna kill me if I killed his phone I'm pretty experienced with several devices, but not much with Samsung. I've never seen anything like this happen before...
When connecting to the computer, have you tried different USB 2.0 ports and USB cables? Have you tried different computers? Different operating systems?
Is the phone recognized using adb or fastboot commands?
audit13 said:
When connecting to the computer, have you tried different USB 2.0 ports and USB cables? Have you tried different computers? Different operating systems?
Is the phone recognized using adb or fastboot commands?
Click to expand...
Click to collapse
Yeah, I figured that would be the case. Just about done downloading Ubuntu which I'll boot from USB. I'll post back with results once that's ready. I should have it booted within 10 minutes. Once I get there and verify the phone connects, what would be my next step? Should I try flashing stock 4.3 first?
I would confirm the bootloader that is on the phone before flashing anything from sammobile.com.
You may be able to use fastboot commands to get the information by typing fastboot getvar all.
OK, in Linux now. ADB/fastboot won't connect. Tried different USB ports and cables, ones that I know work. No luck...
The only thing I can boot to in the phone is Download mode, so that's where I'm trying from.
For the record, ADB picks up my Nexus 5, so I know it's all set up right.
I'm gonna retry the debrick img, using dd to write it this time.
Bloodflame said:
OK, in Linux now. ADB/fastboot won't connect. Tried different USB ports and cables, ones that I know work. No luck...
The only thing I can boot to in the phone is Download mode, so that's where I'm trying from.
For the record, ADB picks up my Nexus 5, so I know it's all set up right.
I'm gonna retry the debrick img, using dd to write it this time.
Click to expand...
Click to collapse
No luck. wrote to the SD successfully, and it just boots to download mode. Nothing else.
ADB and fastboot still do nothing
Maybe the phone's USB port is flaky?
Have you tried Kies to see if it recognizes the phone?
audit13 said:
Maybe the phone's USB port is flaky?
Have you tried Kies to see if it recognizes the phone?
Click to expand...
Click to collapse
I don't have Kies, but I'm doubting that would work anyway. There's absolutely no communication between the computer and phone. Nothing happens when I plug it in. No sound, no indication anything was even plugged in. Running lsusb in a terminal doesn't show the phone either.
Edit: Downloading Heimdall (Linux-compatible Odin)...
Bloodflame said:
I don't have Kies, but I'm doubting that would work anyway. There's absolutely no communication between the computer and phone. Nothing happens when I plug it in. No sound, no indication anything was even plugged in. Running lsusb in a terminal doesn't show the phone either.
Click to expand...
Click to collapse
Okay, forget kies. Sounds like a USB port issue. Does the phone start charging when connected to a power source?
audit13 said:
Okay, forget kies. Sounds like a USB port issue. Does the phone start charging when connected to a power source?
Click to expand...
Click to collapse
Plugging into the wall makes the phone vibrate every couple of seconds, but nothing shows up on screen, and there's no indicator light.
The vibrations lead me to believe it's detecting something, but no indicator light worries me (unless that's just because there's no kernel)
The red light does come on if I plug it in without the battery.
Heimdall fails to detect the device as well (no surprise there)
If the phone was bricked, it would usually be recognized as a some sort of device under Windows' device manager which leads me to conclude that it is a USB port issue.
audit13 said:
If the phone was bricked, it would usually be recognized as a some sort of device under Windows' device manager which leads me to conclude that it is a USB port issue.
Click to expand...
Click to collapse
I agree that it is weird, because it's not coming up as a device at all, in either Windows or Linux, yet it does receive power.
I'm guessing here but it appears to me that the only left to try is a debrick image. Is it possible the battery is drained and needs to be charged?
audit13 said:
I'm guessing here but it appears to me that the only left to try is a debrick image. Is it possible the battery is drained and needs to be charged?
Click to expand...
Click to collapse
The debrick image is what I've been trying. It's on a 64GB microSD. And I made a new one from Linux a few minutes ago (booted back to Windows now).
The battery was about 80% before all this started, and the phone powers on without being plugged in, so I doubt it's the battery.
Maybe you need a different SD card? Based on posts I have seen, it seems that certain brand/size combinations work while others don't.
audit13 said:
Maybe you need a different SD card? Based on posts I have seen, it seems that certain brand/size combinations work while others don't.
Click to expand...
Click to collapse
I only have one card over 16gb...
Either way, I still have the USB problem. I'll need USB to flash with Odin. The debrick card only seems useful when Download mode isn't working, but that part works fine on the phone, even without the debrick card. My problem is with recovery. If I could run that from the SD, I think I would be fine - just flash a ROM. But I'm not finding anything for that (not surprised).
I thought it could potentially be a corrupt driver, so I tried using USBDeview to uninstall all disconnected devices. I tested it with a portable hard drive, which indeed had to reinstall after. So the program works as intended. However, the phone still isn't detected when I plug it in. No sound, no notification saying it's installing or install failed - absolutely nothing. Power goes to the phone through USB, with multiple cables and USB ports. Just no data connection.
I'm starting to think there's just nothing I can do...
The phone may need a USB port replacement. I know of no way to push recovery to the phone from as SD card without USB capabilities.
audit13 said:
The phone may need a USB port replacement. I know of no way to push recovery to the phone from as SD card without USB capabilities.
Click to expand...
Click to collapse
Yeah, that's what I'm thinking. Found this, and it's cheap enough... But that shipping!
You'd be better off getting it from China with free shipping. The problem is the amount of time required to get the part.
Maybe contact a cell repair shop to see how much it would cost to have them replace it. Soldering is not my strongest skill
audit13 said:
You'd be better off getting it from China with free shipping. The problem is the amount of time required to get the part.
Maybe contact a cell repair shop to see how much it would cost to have them replace it. Soldering is not my strongest skill
Click to expand...
Click to collapse
Yeah, doesn't look easy. I already tore down to here, and visibily, it looks OK. I'm not so sure about soldering either :silly:
I appreciate your assistance.