Database Develop

No USB Notifications..

Hello,
My G1 stopped receiving usb notifications. each time i connect it to a computer,the battery charges but i get no notifications about the usb.which means, i cannot mount it to a computer.
I run Cyanogen mod 5.0.7 test2, but i dont think its related since its started a couple of days after i installed the new rom.
i also tried it on different computers/usb cables, seems like its device related.
Anyone has any idea?
TIA,
Roy

use fix permissions option in recovery
it works for me
or
simply restart your phone while connected to the pc

It is device related, if you have a recovery that supports usb mounting from it, I suggest go there and mount your phone if you need to get something onto your device asap. If you have time, a full wipe fixed the problem for me.

Just tried the fix_permissions with no success.
the weird thing is that even in recovery mode, when i enable usb mass storage i still dont get anything!!
i'm trying to avoid a full wipe ,and starting to feel like it's a rom issue, anyone thinks the same?

Same Problem
I too have the same issue. Incase you have any solution let us know. I did some search in google but could not find any thing.

Nandroid, wipe, reflash, and retry. Retry with a different ROM and a fresh wipe maybe. You always need to wipe and reflash when you run into errors like this. Like it or not.
However, if that doesn't work, try a few different USB cords. Maybe something happened to yours, or the one you're using doesn't support a G1. Some companies rig theirs to work with just their product.
Edit: Just noticed you tried different cables and computers... How many different cables? Have you just tried your original one and then another one? Or about 3 - 5 maybe? These are quite common cables, and anyone you know should have at least one or two.

this happened to me a few times after i flashed cyans 5.07 test2 rom and all i did was restart and the notification came back. hope that helps.

Happens to me too with T1-T3. I can just reboot with the cable installed and it will mount once the phone is up.

pkrattu said:
this happened to me a few times after i flashed cyans 5.07 test2 rom and all i did was restart and the notification came back. hope that helps.
Click to expand...
Click to collapse
Same thing. This actually happened to me today and a restart brought it back.

I have the same issue
and everyday I have to reboot the phone while connected to the usb cord
to have the phone recognized.

alternative: try using dual mount sd widget out on the market. It lets you mount your SD card and still use the apps on the phone.

[Q] Won't start unless plugged

It won't start unless plugged it shows empty battery. sometimes when i unplug it stays connected. In usb settings if choose mass storage it seems to get in a loop of connect-disconnect. I have tried flashing different roms but it didn't fix. Any idea of what is happening? Could it be hardware problem?

I've got the same problem, I've tried every kind of wipe, flash with repartition, clearing stats and so on. I'm starting to suspect it's a hardware issue. The Phone seems to always think it's plugged into USB no matter what, it keeps rebooting to the battery icon over and over until I plug it onto a power source and then it boots fine.
After that I can get it back to normalish by rebooting with the power disconnected using the extended power menu in Darkys Rom.
Can anyone help? When I get back from my trip I'll likely flash it back to stock and send it in for repair, or just ***** at bell and get another new phone.

I'm having the same issue, I've searched all over internet and I found other posts with the same problem.. and no one has found a solution for this.
I think is a hardware problem. after having this I've bought a chinese compatible battery, and when I put that battery in, the phone boots up without even pressing the power on button, so weeeird!
With the original one.. there is no way to boot up without plug the phone. I've had the phone working well for more than 5 months
if someone finds a solution please tell!
thanks in advanced!

I had the some problem and more. I did something and this one has gone. I think i replaced a new update.zip in the phone and that solve it but i am not 100% sure. My phone starts normal but when its off sometimes the battery still flashes. In a week or so i will send it to waranty i think.

grofudaniel said:
I had the some problem and more. I did something and this one has gone. I think i replaced a new update.zip in the phone and that solve it but i am not 100% sure. My phone starts normal but when its off sometimes the battery still flashes. In a week or so i will send it to waranty i think.
Click to expand...
Click to collapse
what did you did? so do you think it's a software problem?
I tried to use a non-original battery and when I put in this new battery, the phone boots up without even press any button. so something it's really wrong. if I try the same with the original battery.. nothing happens, the screen is black unless I plug the phone to the charger.
well, at least I can boot my phone without plugging it this way.
I look forward to know more details about this issue.
thanks!

I look forward to know more details about this issue.
Search loads of posts on this topic . Dont know if problem solved or not .
jje

JJEgan said:
I look forward to know more details about this issue.
Search loads of posts on this topic . Dont know if problem solved or not .
jje
Click to expand...
Click to collapse
unfortunately I've done the search in this forum and I haven't found any solution for this, I can't believe it!
regards!

This problem is back again. I can`t start the phone unless it is plugged. I am with the nervs down at this moment.

what makes me crazy is to not know if it's a software or hardware failure!
in my case seems to be a hardware problem unless the phone recognize the non original battery and that makes a software change that makes the phone to boot.
I'll wait until the gingerbread update, and if after update it doesn't work, I will bring the phone to samsung repair point.
I see that I'm not alone with this problem.

Maby if i could connect the phone on usb to pc i would do something but that dosent work either for me so god have mercy.

I had that problem for a few weeks. Went away with a firmware change. Flashed back to stock and then docs rom. No idea what it was. Just went away.

Are you sure the battery is charged? I had the exact same problem on cm7, turned out my battery ran flat overnight
Sent from my GT-I9000 using XDA Premium App

Try this:
Format all your mounts in recovery mode with Clockworkmod. You can do this by going to 'mounts and storage' and formatting boot, system, data, cache. I did sdcard and sd-ext to be sure).
When you have done that install a 2.2.1 stock rom and the problem should be fixed. From here you can install custom rom's again.
Also try disabling any lagfixes (also via CMW)

KeesKaas said:
Try this:
Format all your mounts in recovery mode with Clockworkmod. You can do this by going to 'mounts and storage' and formatting boot, system, data, cache. I did sdcard and sd-ext to be sure).
When you have done that install a 2.2.1 stock rom and the problem should be fixed. From here you can install custom rom's again.
Also try disabling any lagfixes (also via CMW)
Click to expand...
Click to collapse
OK, I'll do that thanks for the suggestion.
I only have one more doubt left, If I do that, after formating everything in clockworkmod.. What does it happens to the phone? is it going to be able to boot after formating all of this? I'm asking this because I don't know how to download the official rom without using kies and the phone booted up and connected via usb cable.
thanks so much!

I've got the same problem.
I thought it was me trying to flash JVK, but after flashing and reflashing 2.2.1 and 2.3.3 and back with bootloaders the problem stayed. I'll try the format "everything" from CWM, hope this will work.
Still abit strange
(BTW I recently was in sub 15 degrees temperatures, surely this isn't the case??)

I had a problem like this where I was getting USB connected coming up again and again and my phone not starting when it wasn't plugged in.
This sounds dumb and I may just have been lucky but I turned USB debugging off and it stopped, left it off for a day or so, a couple restarts later I thought I'd see if it was still playing up so re-enabled it and nope everything's ok again. That was a couple weeks ago and so far so good, I hadn't seen any reports of anyone else with this.
Might be worth a try
Oh I'm using Darkys 9.5 by the way

My problem got worst! My phone would not charge at all until i reflashed. It now charge and boot normaly without to have it plugged, but my pc don't recognize it, not even in download mode with odin. I quess it has something to do with the hardwhare because both times the problem started when i charged it in the same plug.

i had the same problem,I just cleaned the usb port,plugged in the cable without connecting it to the pc or power source,and it started now it's ok

Me too
Another victim of this issue.
I was running a Darky Rom when I first noticed it... I think I was on Ficeto's 2.3.5 JVT. s
I have tried several steps to rid myself of this issue, with no success:
1. Reflashed ROM CWM
2. Reflashed Kernal CWM
3. Factory Reset, format internal SD, & ODIN flash Stock ROM.
4. Wipe & Flash Juwe ROM.
5. Each time, I also wiped the Dalvik Cache and battery stats.
I have tried leaving the battery out for a lengthy period, I have tried draining the battery all the way down, charging all the way up.
At least with the Launcher I am using now, it has the "Reboot" option instead of just turn off. However, I have to make sure I have a USB cable close by and charger in the car all the time now, just in case it runs out of juice or locks up for some reason and needs a battery pull.
Frustrating... Of course, the warranty expired the end of October.
If anyone has successfully completed the recommendation of formatting boot, system, data and cache and flashing stock Froyo? If you have done it, PLEASE post your detailed steps and the result so we don't waste time repeating something that won't work.
I was eyeing the SGS 2, but with all of the issues the market went through with the SGS, I am thinking maybe I should get away from Samsung...
MM

ROM Manager no boot loader

Hi,
Full version as a note. Droid 1
Flashed clockworkmod recovery (2.5.0.1), went fine. Made a backup of stock rooted ROM, worked fine. Next flashed bugless beast .6, while clearing data & cache, no problem.
Now i want to flash to cm - trying out different ROMs - trying to reboot into recovery or flash another ROM both fail to get me to a bootloader. Instead i see the motorola boot logo for 30-45 seconds, followed by what looks like a regular boot (motorola M, then Droid eye, & booted.). I have also tried fixing permissions.
If anyone has any idea why this is happening or can direct me to a forum link it would be greatly appreciated. Sorry if this is in the wrong section, and yea I've tried looking through the forums for a while.
Thanks

just a little baby sized pump...

This happened to me too after working perfectly for several months. All of the sudden I just couldn't get to clockwork. I am running CM7 Nightlies. After not being able to fix the issue for several days I decided that a full wipe via the .sbf method was in order. I've got everything up and running again but it was an annoying process. Can anyone out there help us to understand why this happened so we don't have to deal with this again?

Do you have a link for the method you described about? That would be really helpful!

An ever so slightly larger bump
I really am not trying to be lazy, but all the .sbf methods I've read so far seem require you getting to a boot loader. If I could get to a boot loader this wouldn't be a problem, as I made a back up of my stock ROM. I have a functioning bugless beast ROM, just no recovery / boot loader, and no way to flash back to my recovery.

And possibly solved..
One: Please pardon my ignorance, doing these things on my Eris was far easier, or at least what I got used to.
Two: Please also ignore the word boot loader in my previous posts, as it was the recovery console that I could not get to load. Sorry Again.
Three: Its magically working. My methods were unscientific to say the least, but the Droid is now in "ClockworkMod's Recovery v2.5.0.1".
Things I finally did:
NOTE - I DO NOT BELIEVE ANY OF THIS TO BE THE PROPER ORDER OF THINGS. PLEASE VERIFY WITH SOMEONE FAR MORE INTELLIGENT THAN ME. THE FOLLOWING REFLECTS THE PROCESS I DID, AND SHOULD PROBABLY NOT BE FOLLOWED UNLESS A MOD ACTUALLY SAYS THIS WAS CORRECT
1. Pulled Battery, hold power button down for a few seconds, and then put back in
2. Hold Up on D-pad while holding the Power Button
3. You see the following
Code:
bootloader 2c.7c
battery ok
ok to program
connect usb
data cable
4. Connect USB data cable to PC running RSD Lite. You will also want a .sbf recovery file from a trusted source.
5. Select the .sbf in RSD Lite. Tell it to start. I used the clockwork recovery only .sbf
*** Where things got officially weird for me ***
6. The .sbf file I told it to load seemed to work, as the progress bar moved. The phone almost instantly rebooted, back to the ROM I was running minutes earlier. Clockwork had not been working previously trying to reboot into recovery, but almost instantly upon trying this time, I was in recovery mode.
NOTE - The USB cable was still plugged in as well. I don't know which combination of things actually got this to work, but it did.
Hope this helps someone else out.

Phone suddenly acting up need some help

I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.

whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery

Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....

send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too

The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....

whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.

[Q] USB/Blackrose Bad Combo Help

Hiya!
Been on the forums for years modding my Nexus One and would like to thank everyone for their humongous contribution! 3 years of constant upgrading and improving of what turned out to be the best phone ever!
Now, I've come to an end where my self-confidence took over caution and preparation and i think i've made a boo-boo.
Long story short, i have a unlocked Nexus One that has been running a CM10 ROM with Blackrose for a good 6 months. Most of the functions were working fine, except for a few glitches, but last night i decided to go back to the roots, and install a stock Gingerbread ROM. I found a unrooted GB ROM, and went straight on to renaming it to PASSIMG, throwing it on card and rebooting. Now that's where the funny things started:
First, all goes well, click Volume Up, get it started, and than a screen with all OKs except for [7] BOOTLOADER - Fail-PU and a message saying 'Only Blackrose can be flashed'
Next, I get 7 OKs, except for BOOTLOADER, and the following: Partition update fail! Update fail! Do you want to reboot? Y/N
Figuring i forgot to uninstall Blackrose and need to do so, i let it restart, it comes up with a clean un-rooted GB ROM, and here's where my troubles start.
1. USB Connection: Plug it in, laptop doesn't recognize it at all. Classifies it as 'Unknown Device' and that's it. Tried fresh drivers, Universal Naked Drivers, SDK drivers, ASUS tablet drivers, nothing. Tried 3 cables, the HTC one, a Blackberry one and a Samsung one. Nothing. Uninstalled all USB hubs/devices, restarted the laptop multiple times. Debugging ON/OFF, no difference. I'm at a loss here, no clue what else to try!
2. Fine, i thought, let's flash a rooted rom! PASSIMG on the card, phone finds it, gets to the line 'Parsing... Passimg.zip' and goes back to the neutral screen. Tried it multiple times, different ROMs, nothing.
3. At this point, figured maybe an earlier ROM will cause an OTA update and fix things up. FROYO PASSIMG on the card, flashed 'succesfully', just like in #1, reboot to clean un-rooted FROYO. Checked USB connection, same again. OTA Update - constantly failed.
Been reading through Wikis and Q&A's here all day today, everything seems to be so easy to fix as long as you get a live ADB connection, and i know i could fix it, but i just can't get the laptop to recognize the bloody phone! Do not have access to another computer just now, so can't check whether it's just my Vaio.
So now, the questions:
1. Any other ideas on the USB issue? The phone does not display the usual 'choose your option/mass storage...' when connected, and nowhere in the menu is there an option for that.
2. When booting into recovery, i get the green droid with the white triangle and the !, and then get into the 3e recovery that has an 'update.zip' option. can i install a custom recovery without the phone being rooted? just of the sdcard? is there an update.zip that can re-stock my HBOOT?
any other ideas will be greatly appreciated, as of right now i am stuck with a FROYO handset that is perfectly capable of running JB, and it's really frustrating!
thanks in advance for all your help, cheers!