My wifi keeps turning off after every half hour or so if I'm not using the phone. Iv tried changing kernels and Roma and yet the same problem comes back after about a week after installing a new rom. I've since downloaded a radio from here and tried installing from zip via recovery but it just says error in installation. Any idea where I'm going wrong ?
Last i checked (which was a while back) you can not flash a radio via recovery, it has to be done via ADB or PD98.zip. The topic from where you got the radio should have stated this.
Also more to the point of your original problem, have you tried looking in wifi settings to see if it has a sleep policy enabled or not ?
Settings>Wifi>(Press menu and Select Advanced) and there will be a tab that says something along the lines of "Keep wifi on During Sleep" and select "always".
Ha, never knew there was an advanced option. Why would it be on sleep after 15 minutes on default ? Thanks very much, that should fix that problem. I'm still having a few problems that is not changing with switching roms or kernels, such as having to press back about four times on dolphin browser before it actually returns to previous page, and slow rotate, slow performance, weak network signal etc, etc. Really think I could benefit from using a radio that actually matches the Rom I'm using.only issue is I have no volume button as it's fallen off so if I ever need to recover should anything go wrong, I won't be able to.
Sent from my Desire HD using XDA
You will still be able to enter recovery ect and make you backups flash roms, by installing the clockwork recovery app from the play store, and boot to recovery that way, which if your volume is broke i am assuming that is how you are booting in to recovery either that or you have a rom which has that option attached to the power button, but you are right about the fact if you ever encounter a problem or boot loop.
You may want to get a replacement power rocker from ebay or that, either that if someone knows how to enter recovery with out a volume button which in a boot loop.
Related
Rooted my Incredible yesterday...with relative ease...some very helpful guides out there.
After searching a little...I can't find anything similar to my issue, and the pieces I can find don't piece together for me.
Was accessing hboot (power plus volume -) this morning and accidentally hit the power button to select "fastboot", rather than the "recovery" option i was wanting to get to to make another backup since I had added a few apps after my root.
My phone booted into froyo without any issue...and all my rooted apps worked fine (mainly wireless tether...the main reason I rooted). I shut down the phone and attempted to access hboot again...but got 5 vibrates and a green blinking led, with a blank black screen.
Pulled the battery...and let the phone boot normally (which I was hoping for since I thought I may have bricked it) and all is well...still with root applications working fine. I have tried hboot again with same result (5 vibrates and green flashing led), so I have let the phone stay with froyo for fear that if i screw around with it too much I may brick it after all.
Am I over-reacting to the lack of hboot? Suggestions for a fix are appreciated!
This is wierd, the only time ive heard this prob is when someone tries to flash a rom and then this happens. Sry man i have no idea its strange
Sent from my ADR6300 using XDA App
Download Rom Manager if you dont already have it a then install CWM recovery through it. It just sounds like it didn't install correctly the first time. That usually works for me when I get the problem of only being able to get into HBoot and Fastboot.
Hi Guys -
First time android user and attempted rooting using the odin method. I followed the instruction listed here http://forum.xda-developers.com/showthread.php?t=1311194 to the "T" before starting. I was doing alright until after flashing the recovery-cwm-hercules.tar, then it gets weird. It didn't flash to recovery but just rebooted to the main screen (where I could see the background picture with the locker pattern), then it immediately shuts off and the cycle begins again.
The weird thing is that I can't even access recovery mode (hold vol. up+down+power), because I'll see the Clockworkmod logo then it flickers and reboot itself. This happens every time I attempted recovery mode.
My attempts to fix it:
1. I flashed the recovery, http://forum.xda-developers.com/showthread.php?t=1315390, to see if it makes any difference. The same story happens with loading to main screen w/locker then it reboots itself again and again. Sometimes I'll be lucky to input the pattern but before soon it will reboot itself again. Same thing with recovery mode as described above.
2. Flashing the stock kernel provided by http://forum.xda-developers.com/showthread.php?t=1311229 to see if it does anything. Nope, same story for both recovery mode/home screen.
3. The insecure kernel, http://forum.xda-developers.com/showthread.php?t=1320946. Same story. nope, nope.
4. Tried these in all order and permutation. Nada.
5. Tried it both ways using samsung driver/kies.
6. Tried it both ways with/without SIM card.
7. Battery is fully charged when attempting any flashing.
8. All the above in my second computer to no avail.
I'm sorry if this might come across as long winded but I just want you guys to get the full picture. I would really appreciate it if you guys could offer any solutions or advice on how to correct this problem. Please be gentle with this first time android user haha, thanks in advance man.
Manually boot into recovery (vol up/down keys) and make a backup (be sure to do this). Then try wipe data/factory reset through recovery. Sounds like a ROM issue not a hardware issue
First off, thanks roman for the quick reply. That's the thing I can't get to recovery manually with the button combinations. When I do that it gives me this message:
[Picture]White dropbox/mail box with a yellow arrow pointing to the Android
"Verifying internal mmc block
Checksum confirmation check (0)
No need checksum confirmation already exceuted
#manual mode#"
It would then reboot and goes to the screen with the locker then immediately repeats that cycle. It doesn't have any wipe options/restart now/etc.
No way to power it down except with battery removal. I've attempted what you suggested many times too to no avail.
redlaws said:
First off, thanks roman for the quick reply. That's the thing I can't get to recovery manually with the button combinations. When I do that it gives me this message:
[Picture]White dropbox/mail box with a yellow arrow pointing to the Android
"Verifying internal mmc block
Checksum confirmation check (0)
No need checksum confirmation already exceuted
#manual mode#"
It would then reboot and goes to the screen with the locker then immediately repeats that cycle. It doesn't have any wipe options/restart now/etc.
No way to power it down except with battery removal. I've attempted what you suggested many times too to no avail.
Click to expand...
Click to collapse
Ok, so if it actually boots into the ROM but reboots, try rebooting to recovery from adb -- "adb reboot recovery"
think it's a no go . i tried using adb recovery method and the same thing would occur, it would restart and seems to load into recovery mode but then I would only see the logo, then it flickers and restart itself.
then the vicious cycle of loading up to the screen-locker and restarting itself begins. guess this is the smartphone version of being friend-zoned.
Have you tried taking battery out then back in and while holding volume up/down plug it back into computer? That has never failed to get me into d/l mode. Man I hope you get it working.
Yeah I tried that and getting to download mode is not the problem. just that recovery mode doesn't boot properly in that it would restarts itself. and when i boot normally to screen, i would see the locker and background picture then within 3 secs, it would restart itself.
Guess last resort is to go to t-mobile store, play dumb, and get samsung on it. only problem is that i worry about the flash rom counter # since mine is like 10 already (my attempts to address this problem). Let's hope those tmobile reps aren't that tech savvy.
Thanks for all the help fellas, great early posting experiences so far.
I'm sorry I've read your post..and i'm confuse, if you're able to go into download mode, then why could you just start Odin and flash the recovery again. If its unsuccessful then check the MD5 to see if you have a bad download. I think you should download the recoveries files again add give Odin another shot..Good luck..
Sent from my SGH-T989 using XDA App
are you able to go into CW recovery ?
if so, you can mount the USB, download a stock ROM, and then flash it using CWR
kt0ce said:
I'm sorry I've read your post..and i'm confuse, if you're able to go into download mode, then why could you just start Odin and flash the recovery again. If its unsuccessful then check the MD5 to see if you have a bad download. I think you should download the recoveries files again add give Odin another shot..Good luck..
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
I'm going to give it another try. I've been trying it with different files for a good 2 days now though.
AllGamer said:
are you able to go into CW recovery ?
if so, you can mount the USB, download a stock ROM, and then flash it using CWR
Click to expand...
Click to collapse
I understand that but that's the a big problem. If I could go to CW it would be a different story but I can't go into CW recovery. I would be able to see the logo CWR and the version number then immediately it shuts off again and reboot. Happens every time without fail.
redlaws said:
I understand that but that's the a big problem. If I could go to CW it would be a different story but I can't go into CW recovery. I would be able to see the logo CWR and the version number then immediately it shuts off again and reboot. Happens every time without fail.
Click to expand...
Click to collapse
did you let go of holding the vol+ & vol- buttons as soon as you see the blue text in CWR ?
it can easily reboot by accident when holding those buttons and hitting power, but the buttons are so responsive it selected the first option to reboot the phone by accident a couple of times on me
I'm positive that I held it properly and long enough. I never got to the blue text, just the CWR logo showing then turns off (like you shutting off a tv) and reboots itself. Trying to flash it again with Odin didn't work either and I tried the recoveries from different sources as well.
I went to the Tmobile store today and seems like they'll mail me a replacement then I'll return my current one to them. Only thing is stocking/processing fee but it's a small price to pay if it resolves everything.
glad they will give you another one..
Dude if you can get into download mode then it can most likely be fixed by flashing stock through odin. This would save you some $$. Just saying.
reocej said:
Dude if you can get into download mode then it can most likely be fixed by flashing stock through odin. This would save you some $$. Just saying.
Click to expand...
Click to collapse
Dude, I understand that it should but it's not. I've flashed the stock recovery for more than 10 times and I still can't past the home screen. It would just reboot itself in less than 3 sec. And I'm positive I flashed it properly. Believe me I don't want to spend extra money if I don't have too.
Hey guys
I'm running MrGarak's fantastic MIUI rom however I've found that the kernel is booting my phone into that white HTC diagnostic screen by default. Unfortunately my volume down button is dead and so I can't navigate the menu; the only way I can boot my phone at the moment is to boot it connected via USB as that makes it boot to Recovery and I can reboot from there.
Any ideas? I think this and another rom I tried both used LordMUE's kernel, could that be the reason the boot preferences don't default to just booting the OS?
Any help and/or pointers would be greatly appreciated
So you can access bootloader and recovery!
So just flash another kernel. What's your problem?
Put a zip on your SD (with a SD reader or ADB pull), then go in recovery, navigate with the 4 keys under the screen (or vol+ and power)... and flash.
What is strange for me is that it seems to happen sudenly... so how do ou know it's the kernel. Anyway...
I have clockwork recovery, and can navigate it using the soft keys (home menu etc). You should also he able to use the vol up key to get to the bottom of the list, (depending on the recovery you're using I suppose)
Sent from my Desire HD using Tapatalk
_david_94 said:
I have clockwork recovery, and can navigate it using the soft keys (home menu etc). You should also he able to use the vol up key to get to the bottom of the list, (depending on the recovery you're using I suppose)
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Unfortunately it boots into the white HTC area (dunno what it's called). The one where you can see if your phone is S-OFF or not.
Also, I'm not sure what is to blame... but I've only just recently noticed that my phone cold boots this way so I assumed it was a recent rom that I applied. Will test this theory later.
Sounds to me like your volume down button is stuck in.
Definitely not a ROM issue, as it has nothing to do with the bootloader.
Sent from The App that Time Forgot.
Hey, i had this issue like a month ago. You can check my previous threads. It's hardware I'm 100% sure. Basically if you're in warranty you need to flash the stock rom with S-On so you can get a new phone. You can get it to boot but it's really a pain. You have to play with the volume up when first turning on your phone. It took me about an hour. Then when it boots you'll be in a "Safe Mode" (no clue whats limited all seemed fine to me). Then do your backup if you wish.
Also note: Flashing the S-On rom is a PAIN, took me about 2-3 hours of rebooting, holding vol up, tapping vol up, to get it to boot right, but with patients you'll get it to go.
Good luck to ya.
xtremedelta said:
Hey, i had this issue like a month ago. You can check my previous threads. It's hardware I'm 100% sure. Basically if you're in warranty you need to flash the stock rom with S-On so you can get a new phone. You can get it to boot but it's really a pain. You have to play with the volume up when first turning on your phone. It took me about an hour. Then when it boots you'll be in a "Safe Mode" (no clue whats limited all seemed fine to me). Then do your backup if you wish.
Also note: Flashing the S-On rom is a PAIN, took me about 2-3 hours of rebooting, holding vol up, tapping vol up, to get it to boot right, but with patients you'll get it to go.
Good luck to ya.
Click to expand...
Click to collapse
Ah, I'm definitely beyond warranty. The thought of vol+down being stuck down makes a lot of sense!
I'll just take it to one of the dodgy Asian repair shops, if it's a hardware issue I'm sure they'll know what to do.
Cheers for your help everyone!
My Xperia Play has had a few problems out of the box, mainly that when I switch it on there is no boot animation, just a black screen. This means I can't access Recovery through the normal method of holding down on the volume or the back button etc. I've installed CWM through the CWM Xperia installer so I know it's there. I also ran the Auto-Magic Nandroid through that app, which caused my screen to go black (as it does whenever I choose to reboot through an app). When I looked on my SD card though there is now a Nandroid folder, so it's probable that the device does go into Recovery; I just can't see it.
So my question is this; is there any other way of getting my phone into Recovery so I can install some sweet, delicious custom ROMs? Maybe through ADB or similar? Or is it possible to install a ROM via another method?
Any help at all would be appreciated!!
If it wasn't working right right out of the box, I would have sent it back.
Can't you boot into recovery from the CWM-installer app?
Solar.Plexus said:
If it wasn't working right right out of the box, I would have sent it back.
Can't you boot into recovery from the CWM-installer app?
Click to expand...
Click to collapse
Sadly that wasn't an option, it was the only one they had and I wasn't about to send it back for another type of phone, I've wanted this thing for ages
I've just clicked that option in the app and it's just rebooted the phone normally.
Trism said:
Sadly that wasn't an option, it was the only one they had and I wasn't about to send it back for another type of phone, I've wanted this thing for ages
I've just clicked that option in the app and it's just rebooted the phone normally.
Click to expand...
Click to collapse
Turn on the phone, and when you see the notification light turn blue, press volume down for the locked bootloader cwm, or the back button for the one in DooMKernel.
Sent from a Galaxy far, far away
I've not yet tried installing DooMKernel, I'm worried that if I can't get into the normal recovery in won't be able to get into that one, then I'll be stuck with a boot looping phone.
Pressing down on volume on the blue led comes on doesn't seem to do much, simply stops the boot process from completing fully. I left the phone for 5 mins and got nothing. Pressing the power button again started the boot process again and it loaded up normally (minus any animations of ciurse)
It seems like stuff is happening, but I just can't see it. I doubt this is a hardware fault as the screen works perfectly all other times, so what the heck could it be!?
The recovery in DooMKernel is already built in, so it's different than using the Xperia CWM installer. By the way, the back button will get you into DooMKernel's recovery.
I'll give it a try and see what happens. Thanks for the advice guys!
I've currently attempted to root my Galaxy and everything went well until I tried to back up my applications.
I can't get clockworkmod to work, I hold vol up, power, and home and it shows my the android character laying back with a red ! in Android System Recovery.
Not really sure what to do. I've been searching for possible solutions but I can't find anything.
I followed this method, http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
The FAQ section under it talks about two files that should be deleted as it overrides CWM but file explorer isn't finding them for me.
Just use the Root66 rooting method : http://forum.xda-developers.com/showthread.php?t=1949687 .
It sounds like whatever you did, it did not work and you still have stock recovery. Just do it through Odin as described in the thread linked - it is very easy.
Any possible chance of me bricking my phone by adding additional files along with the ones I've added? CWM seems to be working through the ROM Manager app but not working through Vol Up, Home, and Power.
You press power. Wait a second or two, then hold vol up and home.
If you hold power, the phone will never turn on. If you wait too long, the phone will boot into the OS. It's a timing thing.
I've done that and that's how I get sent to Android System Recovery.
I've downloaded CWM through ROM Manager but I can only access CWM right after I download I. It worked last night but today when I tried accessing CWM it sent me to Android System Recovery. I downloaded CWM again then it worked.
For some reason it seems CWM isn't sticking onto my device.
Oh, I misunderstood. To fix that, flash CWM (version 6.0.3.0) again. And when you reboot your device, before your device boots into the OS, drop into recovery mode. It will allow you to disable the script that keeps overwriting CWM for you (you will get this option when you attempt to exit CWM).
Oh wow, I did what you said my phone rebooted. I did vol up, power, and home and got sent into CWM. I think its working now
Thank you so much bro
Sent from my SGH-T999 using xda app-developers app
Now save yourself time and hassle and flash twrp recovery cwm is.in my opinion troubled... twrp seems to be the rec of choice
With goomanager from market.
Sent from my LG-MS770 using xda app-developers app
They are crawling out of the woodwork.
There is nothing wrong with CWM. There is nothing wrong (mostly) with TWRP. They both work. Pretty well, in fact. Though, I still have issues with TWRP pretending I pressed the back button when I didn't.
Since you are on TWRP, tell me if you can reproduce this: Go into the timezone settings and start selecting different timezones as fast as you can (also works with typing filenames for nandroids, but this is quicker for reproduction). What happens on my device is I get knocked back into the settings page. It is 100% reproducible, but inconsistent with presses/time required to make it crash. I have seen other people complain about this, but not nearly as many as I would expect, given the severity and prevalence of the bug.