The closest problem I could find to what I was experiencing was that my phone was usb bricked. I had a GB Evo that I rooted using the Revolutionary method. After I had the phone rooted I installed Titanium Backup and updated the version of superuser through TB. The next time I rebooted the phone it would boot to the lock screen, freeze and then reboot. When I boot into recovery I am randomly able to access either the sdcard or the phone through the usb cable. I have performed a few of the fixes for usb bricked phones through fastboot (fastboot oem enableqxdm 0) these seem to be only a temporary fix as soon as I reboot the phone goes back to not being able to recognize the sdcard. If anyone could offer any suggestions I would greatly appreciate it.
Related
I ****ed up my phone somehow and I don't know how to fix it. I was going to install a new Rom, was wiping data and went to partition my SD card to try A2SD. I couldn't do it in clockwork recovery so I thought I'll connect the phone to my PC and run Paul's recovery from r5 rooting method. The problem was that somehow both recovery's were running and I'm not sure what I pressed but now my phone can't recognize the SD card, nor can the PC recognize the phone when I connect it. The Rom can boot up, but somehow it's not working properly, I can't make/receive calls but for example WiFi works. I guess its not bricked since Android launches but I have no idea how to fix what I messed up. Somebody please help me
Your device is usb bricked, search for usb brick in the development, this can be easily fixed.
Thanks, I found it, but I'm stuck at step 1: "Enable the SD Card functionality. Boot your phone in FASTBOOT mode (back + power), and enter this command: 'fastboot oem enableqxdm 0' . This will re-enable your SD card."
Where should I enter that command ? Thanks.
EDIT: I fixed it ! Thank you so much. I knew it will be easy to fix just I couldn't think clearly and forgot about the USB bricking issue
OK. Im new to XDA and i have read alot of articles trying to fix my screwup. Hopefully someone can help. I was once rooted and i had redemption rom on and i tried to install cm30 nightly and got stuck somewhere and started to try to do wipe and clean amopngst other things and almost bricked it totally.The main thing that happens is when i press power i get 5 vibrate beeps and a blinking green light. i can go to hboot by pressing power and down but i cant go into recovery. Among other things i can plug usb and shows hboot usb but computer only shows android boot loader under device manager.
Now here's where it gets even weirder. I tried to install the pb113img.zip. when i did everything said ok while installing and when i got the choice to reboot it went to a green recycle looking thing then it went to a blank screen and 3 beeps with green blinking light.
I went into fastboot and hit reboot and it did boot into the stock 2.2 rom but if i disconnect a usb cord or when plugged into the wall the phone dies and goes to the blank screen with 5 beeps and blinking lights.
while in hboot the recovery choice is not working and neither is factory reset.
I hit fastboot the choice for bootloader takes me back to hboot.
Now while the usb plug is in the hboot says hboot usb but when i did get it to boot and plugged the usb in it doesnt show on my computer it does however show android bootloader interface on my device manager. Also the sdcard will not read on the phone but the sd card will read in a sdcard adpater where i can transfer files.
I have 2 sdcards and a sd adapter and htc usb cable and htc outlet charger and 2 batterys.
Here are my stats:
S-On
H-boot 0.92
touch panel-ATMEL224_16
radio- 2.15.00.07.28
Please somebody help me i been trying different methods but running into circles here.
If your S is on and it looks like it is and your running the stock 2.2 bring it in to the store and they will warranty it for you.
I did think about that because stock rom looks to be on and s-on as well just wondering if they could be able to tell through h-boot
Unfortunately this is a hardware error code, and you'll probably have to get it replaced.. My Inc came out of the box doing this (had it shipped to me), and the only option I had was to take it right back to the store.
I was able to boot mine normally if it was plugged into the computer at the time, so you might want to try that and see if you can at least verify the installed firmware. Otherwise, a warranty exchange is your only choice.
My incredible started doing the same, it all hapened when i mounted sd in recovery mode and then i was playing with diag mode to flash it. Since then its doing the vibrate and green light thing. Also I rooted it and my s is on. Also I can use the phone if i plug in the usb while turning on and then quickly take it out. Only problem is the phone doesn't detects the internal or external storage. I even got phone to be detected by unrevoked, but it is stuck as pushing recovery since phone doesn't detects the storage. BTW I already tried the Official PB31IMG zip.
Please any help is greatly appreciated.
Same issue flashing CM7 RC2. Could not fix it, Verizon is replacing it.
Here's a few threads to follow:
http://forum.cyanogenmod.com/topic/18381-bricked-my-incredible-installing-cm7-rc2/
http://forum.xda-developers.com/showthread.php?t=808294
It is probably a USB brick
I had the same problem with my HTC Legend a few days ago, it turns out to be a USB brick, which means something had corrupted the misc partition. The fix is simple, just flash a good misc image back to that partition and everything is back to normal, there are tons of USB unbrik TUTs out there.
Hope this could help.
I installed this rom yesterday:
[ROM]-[RLS2-7/21/11]-KInGdOm ReWiND 3D-[2.3.3]-[Sense 3.0]
I had not noticed any big issues, until I woke up this morning. My phone was off even when I had left plugged in all night.
I powered it back on and it was power cycling. Each time it would start up for maybe a minute and work fine then it would vibrate 5 times and shut down. I decided to attempt to flash back to an old rom and noticed clockwork was no longer installed. Then I noticed that my S-off, was now showing an S-ON. After noticing this I figured I would simply root the phone again and flash back to my old rom. It was then I noticed that neither the SD card nor the USB disk options were working. No USB = No root. I figured a hard reset would do the trick if I simply got back stock rom (2.2), but that did not fix the USB issue or the SD card issue.
It turns out this is a known issue that happens for whatever reason, I was able to fix the SD card from what I read here.
[ How-To ] Fix SD card not being detected & USB port not working
http://forum.xda-developers.com/showthread.php?t=695243
However, I can not seem to get the USB to work. I tried using Android Terminal and type in the commands from the Fix SD car/USB instruction, but since I cannot perform the su (super user?) command because I am not rooted, I cannot complete the fix for USB.
So guys, if I could please get help with this it would be great. I am currently on stock froyo 2.2, with SD functioning but no root or usb to gain root. Any ideas? I have tried using PC36img.zip on boot to fix this but still no cigar.
Thanks!
PS: I can't post on developer post where I saw first fix since I do not have 10+ posts.
I've been running Cyanogenmod 9 for a couple of months, but decided to restore to stock so I can try out ICS and the new version of sense. I tried this a while ago but got stuck when when phone wasn't recognised via USB when connected to my laptop. Fastboot would change to Fastboot USB when plugged in, but the phone wasn't picked up. However, on this occasion I was able to restore Cyanogenmod without problems.
I tried this again yesterday with the same result regarding the USB connection, but when I restored Cyanogenmod it now just hangs on the boot screen and won't go further. Prior to this, when I ran the restore function in Clockworkmod, the phone would hang on the HTC splash screen with the beats audio logo on it. I did manage to get the phone to boot into recovery, but rather than the usual menu option I had a message something like "checking SD card..." and then nothing.
I am not sure where to go from here. The only thing I am wondering is if I tried to do this with the battery being too low, and the installation has failed because of this. I do want to go back to the stock OS, but not sure how to go about resolving the USB issue.
UPDATE
Partially solved the problem, in that I've managed to reinstall the cyanogenmod. Still stuck with lack of USB connectivity though.
Wrong section.....
Do you have the Fastboot files all in the same folder and do you have the HTC Sync drivers installed? You need that set up correctly to get a fastboot USB connection.
My suggestion is to simply "fastboot oem lock"
Then flash corresponding RUU to your current HBOOT. You can find out which RUU you need by typing "fastboot getvar version-main"
I have an unrooted and locked Galaxy Nexus which seems to have got stuck in a bootloop and won't start. I had some important data on the sdcard which I want to recover. Any suggestions on how I can do so? Here are more details about the problem -
I tried to upgrade it Jelly Bean a few days back and it didn't happen successfully. However after that the phone was still working properly and one day when I switched on my Bluetooth, the device restarted suddenly and it got stuck at the initial animation after showing the Google logo. So effectively the device doesn't boot and I am assuming the boot partition either got erased or corrupted.
I also tried connecting the device to my computer but it doesn't recognize the device. I tried it in Windows, it didn't work and I assumed it to be a driver problem. So I also tried it in Ubuntu but still no luck. However the phone does get recognized in fastboot mode using "fastboot devices" but I cannot get the device to mount nor get "adb devices" to work.
I bought the device into fastboot and tried to start the recovery mode but even that doesn't start and gets stuck at the Google logo. This was strange since I haven't touched the recovery partition at all and in fact the device hasn't even been unlocked.