Database Users

MyTouch 4G goes into recovery when charging

Rooted MyTouch 4G goes into recovery when I put it on charger from wall plug. The recovery # is 2.5.1.2. It goes into recovery when the phone is shut off and plugged in to charge battery. When it is turned on and charging it operates normal. Could this be from some app I downloaded?
HELP PLEASE

vinnyjr said:
Rooted MyTouch 4G goes into recovery when I put it on charger from wall plug. The recovery # is 2.5.1.2. It goes into recovery when the phone is shut off and plugged in to charge battery. When it is turned on and charging it operates normal. Could this be from some app I downloaded?
HELP PLEASE
Click to expand...
Click to collapse
this is a known issue with clockwork recovery. no need to fret. it is not caused by any app you downloaded

vinnyjr said:
Rooted MyTouch 4G goes into recovery when I put it on charger from wall plug. The recovery # is 2.5.1.2. It goes into recovery when the phone is shut off and plugged in to charge battery. When it is turned on and charging it operates normal. Could this be from some app I downloaded?
HELP PLEASE
Click to expand...
Click to collapse
yeah, that app being rom manager. This is a KNOWN bug in clockwork recovery, and as of yet, there is not a fix to it.

Thanks for the quick response. I was just about to start deleting all kinds of apps.
Thanks again,
best website
Vinny

jmwils3 said:
yeah, that app being rom manager. This is a KNOWN bug in clockwork recovery, and as of yet, there is not a fix to it.
Click to expand...
Click to collapse
I was just going over this in another thread and someone said that enabling fastboot keeps it from going into recovery when turning off while charging...haven't tried it yet though but makes sense I guess.
fingers crossed..
i also read on another post where someone reinstalled clockwork in rom manager and got it to stop booting into recovery like that. one poster said it took him multiple times of reinstalling it before it finally stopped....i'm going to try this also if the fastboot solution doesn't work.
i'll post back if I confirm any of these work.

ckisgen said:
I was just going over this in another thread and someone said that enabling fastboot keeps it from going into recovery when turning off while charging...haven't tried it yet though but makes sense I guess.
fingers crossed..
i also read on another post where someone reinstalled clockwork in rom manager and got it to stop booting into recovery like that. one poster said it took him multiple times of reinstalling it before it finally stopped....i'm going to try this also if the fastboot solution doesn't work.
i'll post back if I confirm any of these work.
Click to expand...
Click to collapse
thanks. Im hoping for the latter solution, as CM7 doesnt have fastboot.

jmwils3 said:
thanks. Im hoping for the latter solution, as CM7 doesnt have fastboot.
Click to expand...
Click to collapse
how can you be on cm7 with clockwork 2.x.x? you have to be on clockwork 3 to flash cm7..
Sent from my HTC Glacier using XDA App

ckisgen said:
how can you be on cm7 with clockwork 2.x.x? you have to be on clockwork 3 to flash cm7..
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I'm not. Cwm3 does the same thing
Sent from my HTC Glacier using XDA App

jmwils3 said:
I'm not. Cwm3 does the same thing
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
oh, I was told this was only a bug in 2.x.x
Sent from my HTC Glacier using XDA App

ok so haven't determined which setting exactly worked. it may have been a combination but I reflashed clockwork recovery in ROM manager , enabled fast boot, and turned on USB debugging and my phone did NOT boot into recovery after I turned it off while plugged in. charged all night off.
Sent from my HTC Glacier using XDA App

Same thing with my phone... I tried reflashing CWM3 and it didn't solve the problem. Turning on fast boot did however.
Just sucks because I don't want fast boot on, but I prefer charging my phone with the power off... so I guess I'll deal with it until the problem is fixed =\

rayne127 said:
Same thing with my phone... I tried reflashing CWM3 and it didn't solve the problem. Turning on fast boot did however.
Just sucks because I don't want fast boot on, but I prefer charging my phone with the power off... so I guess I'll deal with it until the problem is fixed =\
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=944681&page=9
thats the link for the fix to this problem

Thanks! I've been searching all day for a fix and this was the only thread I could find so I figured it was still an issue
=)

Bricked my epic. Need help restoring it

Hi guys,
I know it's supposed to be virtually impossible to brick the epic but I don't know how to fix mine using the threads in this forum.
I originally rooted my phone, installed Clockworkmod and had the genocide Kernel installed.
This morning I tried to flash the Bonsai rom. Everything seemed fine and I got the message that the flash was successful. Upon reboot the phone just stays stuck at the Samsung screen.
I've tried to use Odin to reset my phone but Odin doesn't detect my phone and anything I try to do within the recovery screen gives me the message that says
E:Can't open /cache/recovery/log
Can anyone help me get my working again? And what do you think went wrong in my attempt to flash Bonsai? Could it have been that I already had Genocide kernel on there?

If Odin isn't detecting your phone, try rebooting PC and use a different USB port and cable, if possible.
Sent from my SPH-D700 using XDA Premium App

Are you in download mode when you are using Odin? If not... open keyboard while phone is off and hold down 1 and the power button. If that's not the problem try another cable.
Sent from my SPH-D700 using XDA App

I am in download mode. I will try to reboot my laptop and change the USB port. Hopefully that works. If not it won't be until tomorrow when I have access to different cables. Will let you know how it goes.

Have you successfully used Odin with this particular laptop and cable?
Sent from my SPH-D700 using XDA Premium App

As long as you can get to Download mode, you Epic shouldn't be bricked
Instead of using Odin, try the SWUPdate version of the EB13 update with the phone in download mode

xxmastermindxx said:
Have you successfully used Odin with this particular laptop and cable?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
When I used odin to flash to Froyo I was using my desktop. This was my first time using the laptop. Looks like it was a bad idea!
I rebooted the laptop and changed USB ports and still no cigar. When I plug the phone in Windows goes into it's plug n play routine trying to install drivers for the devices which unsuccessfully install. I've previously installed the Samsung drivers on the laptop in order to mount the SD card so I'm not sure why doesn't recognize the phone. Any idea on why this happens? Is it normal when the phone bricks?
It won't be until late tonight Pacific time or tomorrow that I will be home and able to try things out on my desktop where I previously used Odin successfully.

U should use your desktop for this since its worked for u in the past
Sent from my SPH-D700 using XDA Premium App

I think a PC reads the phone differently depending on what mode its in, someone correct me if I'm wrong. Mine has come up as a disk drive, an adb interface, a modem, and just plain phone. Not sure of the exact reason.
But yes, use the PC that's worked for you before. I'm sure your Epic just needs a little love
Sent from my SPH-D700 using XDA Premium App

Thanks guys, I'll try it on my PC as soon as I can and hopefully it'll all work out.

I had a similar situation where my netbook would not recognize my phone, but everything works normally on my desktop.

I had the same problem. I think to fix it I had to run the one click root for ext4 and then flash the rom. Hope this helps.

I had a similar problem but was able (eventually) to get cwm to boot and restored from nandroid
Swyped from my Epic on Bonsai

Thanks for the suggestions guys! It was as simple and unintuitive as using my desktop and the cable that came with the phone to get Odin to detect the phone. I'm now flashing back to stock before rooting and putting on a custom ROM

Glad to hear it went well
Sent from my SPH-D700 using XDA Premium App

issue mounting sd

i seem to have a problem with mounting the internal storage on the phone, it doesnt ask me to mount when i plug the phone in like it normally would so i tried mounting through recovery but still cant do it through there, tried 3 different roms and all the same issue, are there any kernels with this issue? im running newest nscollab with the kernel it comes with...not sure what to do

are you running the latest recovery? can you use the storage space with apps on the phone?

I have been having the exact same problems. Nothing seems to work. Can't mount through CW and I have the most recent version. Randomly it started to work again by turning the phone off. Plugging phone into computer. Turning phone back on. It would recognize it until now. Now that doesn't work....
I am using Mac and Linux and neither one need drivers so that has nothing to do with it.
I'm screwed if I have to take the phone in for warranty work because I am rooted.
Anyone come up with something to fix this?
Or is there a way to "force it to mount?"
Its really f'in annoying
Sent from my Nexus S 4G using XDA App

xcolt45 said:
I have been having the exact same problems. Nothing seems to work. Can't mount through CW and I have the most recent version. Randomly it started to work again by turning the phone off. Plugging phone into computer. Turning phone back on. It would recognize it until now. Now that doesn't work....
I am using Mac and Linux and neither one need drivers so that has nothing to do with it.
I'm screwed if I have to take the phone in for warranty work because I am rooted.
Anyone come up with something to fix this?
Or is there a way to "force it to mount?"
Its really f'in annoying
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
So it's showing the storage on the phone and not on the computer, correct?
Can you select to mount the USB when you plug it in?
Does the device show up in the System Profiler app in Mac OS X?

derekwilkinson said:
So it's showing the storage on the phone and not on the computer, correct?
Can you select to mount the USB when you plug it in?
Does the device show up in the System Profiler app in Mac OS X?
Click to expand...
Click to collapse
That is incorrect. It does not show up on the phone. When it shows up on the phone it mounts to the computer. It is not even recognizing it on the phone now. For awhile it was working and now its not again. Haven't done anything else to the phone.
When it doesn't show up on my phone it is not recognized by the system profiler.
Never had a problem with any other android device except on my epic 4g when I tried running the miui beta for it. But it would still mount in clockwork.
It is not the cable because I have four different cables. One of which works flawlessly on my epic. Which had a lot of problems when using the stock cable.
Is this hardware related or is it because of the rooting process?
What r some possible fixes if any?
I really would not mind going back to stock and starting over. But the only way to get back to stock is by USB. And nothing recognizes it. Adb. Fastboot. Odin (heimdall in Mac terms) nothing recognized it
Sent from my Nexus S 4G using XDA App

xcolt45 said:
That is incorrect. It does not show up on the phone. When it shows up on the phone it mounts to the computer. It is not even recognizing it on the phone now. For awhile it was working and now its not again. Haven't done anything else to the phone.
When it doesn't show up on my phone it is not recognized by the system profiler.
Never had a problem with any other android device except on my epic 4g when I tried running the miui beta for it. But it would still mount in clockwork.
It is not the cable because I have four different cables. One of which works flawlessly on my epic. Which had a lot of problems when using the stock cable.
Is this hardware related or is it because of the rooting process?
What r some possible fixes if any?
I really would not mind going back to stock and starting over. But the only way to get back to stock is by USB. And nothing recognizes it. Adb. Fastboot. Odin (heimdall in Mac terms) nothing recognized it
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
okay, I had this issue when the nexus s 4g was first released and the first roms/recoveries came out. I would just start over. backup using titanium backup and flash the stock files in fastboot, then unlock again, flash the recoveries, etc.

How exactly would I revert to stock if commands from my computer in fastboot do not recognize the device?
Sent from my Nexus S 4G using XDA App

Try es file explorer and give root access ... this was u can atleast access files from your phone...

PROBLEM SOLVED... at least for me
Found out when flashing to a stock rom (currently running MIUI) that my usb port on my phone is loose. Just have to be careful with it. Makes sense that it was randomly happening.
With MIUI it wouldn't show right away because I had it set to auto-mount. But when i flashed the stock rom. The pop-up to mount-sd would show up and go away show up and go away....
Darn.

phone will only boot when connect to computer?

so, im really confused right now. ive been having issues, and i thought i had it worked out, then i tried rebooting my phone, and it kept looping the white htc evo screen, so i plugged it into the computer to do some adb/fastboot stuff, and it booted. ive done this multiple times to confirm. any ideas why or how to fix it?

What happens if you boot it connected to the computer and then unplug it? Does it run properly? How about booting plugged into the wall, not a computer. Does that yield the same results?
Sent from my PC36100 using xda premium

After I see the boot animation start, I can unplug it and use it normally. Except my phone fcs, and I can't get USB mass storage to work, but that could be totally unrelated. I can boot while plugged into the wall. I'm even more confused haha
Sent from my PC36100 using XDA App

Might be an issue with your battery not providing enough juice. You aren't undervolted, are you? Sounds like the phone just doesn't have enough juice to run right. If you are undervolted, try adjusting back. If not, try a new battery, I have a feeling you may see some cgange.
Sent from my PC36100 using xda premium

I agree with Aaron. You may also have a bad flash of a rom,, try reflashing the rom to see if it corrects the issue

Sounds like a good wiping and a nice clean flash will fix this issue.

Had the same problem awhile back after flashing CM 7 RC. After a reflash it went away and everything worked fine.
Sent from my PC36100 using xda premium

I got it working, flashing didn't due anything to help, but the problem would appear to be when everything messed up it was with boot manager and my recovery, and I had revolutionary cwm and couldn't find a dl for it anywhere, so using among ra or normal cwm wouldn't really work. So I pulled the recovery.img from an old nand and that did the trick.
Sent from my PC36100 using XDA App

Wi-Fi not working

Have been enjoying epinter's ROM, but recently been having some issues.
Last week, everything suddenly started misbehaving, and then it rebooted and went into a boot loop. I restored to an older NANDROID backup and it worked fine. But since that event, it has been rebooting quite regularly at random times. Sometimes, it goes into a bootloop. Have realised that if I take out the battery and leave it to cool down for a few mins, it starts working fine. I suppose this is to do with overheating.
I deleted FastDormancy.apk as suggested by epinter. Doesn't seem to have made a difference.
Since day before, it isn't detecting any Wi-Fi networks. I flashed the 20120922 version of epinter's ROM too, but still have the same problem. Tried the WiFi settings, but that didn't help.
Today I cleared data and cache, and reinstalled 20120922 version of the ROM, but still got the problem.
I also upgraded radios to 37p. Didn't help.
Any suggestions on how to diagnose it? Is it possible that Wi-Fi (hardware) is bust?
Sent from my MB860 using xda app-developers app

No suggestions?

Maybe hardware!
Sent from my MB860 using xda premium

Might suggest a full -w in fastoot. Load a different recovery via fastboot then a stable rom just to test with like Joker CM9 or Fruitcake.
If that don't work start checking antenna connections and ribbon cables for damage.
Sent from my MB860 using xda premium

Cab121 said:
Might suggest a full -w in fastoot. Load a different recovery via fastboot then a stable rom just to test with like Joker CM9 or Fruitcake.
If that don't work start checking antenna connections and ribbon cables for damage.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
What do you mean by 'Load a different recovery via fastboot'? I have used fastboot to wipe fully, but could you point me to the 'recovery' to be used?
Thanks

My phone is repeatedly rebooting now. It's not in a boot loop. It actually boots into ICS and then reboots after some time.
Really would appreciate any insights on this.

You can use fast boot to flash recovery files to the phone. You need to while recovery then use "fastboot flash recovery filename.img" for example. Assuming your file is in the same directory on your PC.
I only suggest out of practice. I typically find if any part of the hardware fails to boot or load with the rest of the phone I start with a clean cwm ,rom, and so on. Start at 0 essentially. If the problem goes away then its most certainly soft wear and you can trouble shoot from thwre
Sent from my MB860 using xda premium

Does Bluetooth work ?
Sent from my MB860 using Tapatalk 2

I've been using the 20120825 version of epinter's rom, and everything has been incredibly stable for me except wifi and bluetooth. Neither will turn on, and under advanced wifi settings my wifi chip is giving the mac address as not available.
I flashed CM7 a few weeks ago to see if that would fix it and CM7 gives an error when I try and turn wifi on, also showing not available for the wifi mac address.
I've seen around here a little bit that this might be a hardware issue that happens irrespective of what rom you use or if still on stock.
Has anyone found a fix for it?
EDIT: also using the 37P radio.
I also found this thread... http://forum.xda-developers.com/showthread.php?p=26163360