Related
can someone help me figure this out? i turn my g2 off, but right after its off it automatically boots into clockwork-mod recovery!! has anyone else had this issue?
rapidfire224 said:
can someone help me figure this out? i turn my g2 off, but right after its off it automatically boots into clockwork-mod recovery!! has anyone else had this issue?
Click to expand...
Click to collapse
Im having the same issue..weird!
Well known issue with CWR. Koush said its not high on his priorities. You could download the source and try to figure it out though.
hmmm, ok. im not an expert with doing things from source. somone else maybe, with more skills?
It's an issue when the charger is plugged in. It should shut down fine if you haven't got the charger connected.
there is nothing wrong with being in recovery while charging -- uses very very very little power and when your ready to turn on the phone, you just hit reboot and your done. Or maybe you want to clear cache before you boot? or maybe you want to backup before you boot or maybe you wanted to fix permissions before you boot? i mean -- its actually a blessing in disguise. I would be more annoyed if this was an issue with the G1 because it was so easy to get to recovery as it was (power and back button) whereas with the g2 if you wanted to get to recovery you'd have to either use adb or its PC counterparts, a reboot app in the rom, or by booting into fastboot and then 3 more steps after that to get to recovery.
its like living next door to the convenience store, bank, grocery store, and the massage parlor. one stop shoppin -- no hard trudging around to get places.
it is a benefit... yes its a bug...(a bug with benefits heh) but frankly i've put in a request that if koush updates recovery i want to be able to "keep" this bug.
androidcues said:
there is nothing wrong with being in recovery while charging -- uses very very very little power and when your ready to turn on the phone, you just hit reboot and your done. Or maybe you want to clear cache before you boot? or maybe you want to backup before you boot or maybe you wanted to fix permissions before you boot? i mean -- its actually a blessing in disguise. I would be more annoyed if this was an issue with the G1 because it was so easy to get to recovery as it was (power and back button) whereas with the g2 if you wanted to get to recovery you'd have to either use adb or its PC counterparts, a reboot app in the rom, or by booting into fastboot and then 3 more steps after that to get to recovery.
its like living next door to the convenience store, bank, grocery store, and the massage parlor. one stop shoppin -- no hard trudging around to get places.
it is a benefit... yes its a bug...(a bug with benefits heh) but frankly i've put in a request that if koush updates recovery i want to be able to "keep" this bug.
Click to expand...
Click to collapse
A convenience store that keeps its blinding storefront lights on all night even though the whole damn place is closed except for a soda machine outside.
Sent from my HTC Vision using XDA App
helloelan said:
A convenience store that keeps its blinding storefront lights on all night even though the whole damn place is closed except for a soda machine outside.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Talking about the screen?
Hold the back button. On my Pulse it turns the screen off. Or totally black, I can't remember.
Better yet, turn it upside down.
Or, leave it switched on.
DanWilson said:
Talking about the screen?
Hold the back button. On my Pulse it turns the screen off. Or totally black, I can't remember.
Better yet, turn it upside down.
Or, leave it switched on.
Click to expand...
Click to collapse
First time I discovered this bug I was about 9 hours late. I grabbed my hot ass phone n unplugged. I put it infront of the ac vent so it could cool down. After about ten minutes I powered up n the setcpu widget told me the phone was at 120 something degrees.
Needless to say my first g2 never ran right after words. Too many random reboots n odd graphical glitches.
I unrooted and cried bad hinges so tmobile would replace it.
Damn shame its not on his priorities list...
I've seen a lot of these threads on random android forums, never with much resolution, which is frustrating.
My power button has stopped working entirely. I took it into the Sprint shop, they spent an hour with it, came back out and said they could find no reason it shouldn't be working. It's an obnoxious fix, but I downloaded "No Lock" from the marketplace and set the screen to shut off after 15 seconds. Now I press a volume key to turn on my screen...
Now, when it gets annoying is when I went to install Cyanogenmod 7 tonight. The power button obviously doesn't work. Widgetsoid's reboot button is ignored entirely if I do Shut Down, Reboot, Bootloader, or Recovery. It's A-OK with Hot Reboot. So the only way I've gotten into the bootloader to wipe/install CM7 is to pop out the battery, hold VolDown, and put the battery in. Peachy. But once I'm into the bootloader, now not only does power (which is now my "enter" button) now work, but the volume buttons are unresponsive as well. So no scrolling.
I'd love to call up HTC or Spring and see what I can do about a replacement (which might not even happen, I don't have a warranty), but I can't un-root the device to send it in.
Any insight you guys have would be greatly appreciated...
Is there an SDK or something that would allow me to remote control the phone using my computer via USB? I'm completely at a loss here.
END_OF_FLESH said:
Is there an SDK or something that would allow me to remote control the phone using my computer via USB? I'm completely at a loss here.
Click to expand...
Click to collapse
I believe you are referring to adb?
and you can unroot via adb, just search around, I'm sure you'll find something on it.
btw, does Sprint know you rooted your phone? if they didn't find out, then you still have a warranty
Samzebian said:
I believe you are referring to adb?
and you can unroot via adb, just search around, I'm sure you'll find something on it.
btw, does Sprint know you rooted your phone? if they didn't find out, then you still have a warranty
Click to expand...
Click to collapse
Yeah, I'm just not as familiar with ADB as I'd like to be.
Not so much looking to unroot, as reload HTC Sense so they don't think to look haha. And yeah, when I brought the phone in today it was very obviously modded. They restarted it and the Cyanogenmod 6 flash screen came up. The guy looked a little confused. He was more than willing to help out, but I'm not so sure it would be the same if I sent it in. They definitely wouldn't replace it.
Alright, so I have ADB up and running with no issue. Got it to give me my device's serial #. At this point, how do I hijack the phone's bootloader and force it to wipe and install the ZIP of CM7 that's on the SD card?
hey guys, my girlfriend just bought a new evo that has the gingerbread ota already installed. i want to root it and install a gingerbread rom (synergy to be specific). i understand that i need to revert back to froyo first, and then i plan on using the auto root from here--> http://forum.xda-developers.com/showthread.php?t=838448. my question is whats the best way to revert to an older ruu? i did it on my thunderbolt by just flashing in cwm but i was already rooted. ive read something about using fastboot but ive never done anything with that on my thunderbolt, so could someone point me in the right direction?
edit: did some more research, turns out the new hboot wont allow you to downgrade an ruu, and there's currently no way to install an older hboot. looks like im stuck waiting( well actually she is, i can still enjoy my root )
turn off phone completely (pull battery) press power button and volume down at same time. Thats brings you to Hboot. if there is S-on at the top of the screen somewhere just reboot and wait until someone comes up with a definate method of rooting the 2.3.3 otherwise you might look like a fool by breaking ur gf new phone.
Michaud85 said:
turn off phone completely (pull battery) press power button and volume down at same time. Thats brings you to Hboot. if there is S-on at the top of the screen somewhere just reboot and wait until someone comes up with a definate method of rooting the 2.3.3 otherwise you might look like a fool by breaking ur gf new phone.
Click to expand...
Click to collapse
haha my thoughts exactly. and unless sprint ships there phones pre-rooted im gonna assume its still s-on since i havent touched it yet lol
haha yeah i just got my phone today and its so stupid how they force their OS on you. You cant even shut the phone off without pulling the battery (the power off in the menu just puts it to sleep so it boots up quickly when u power on). Hopefully someone can save us from this non rooted nightmare soon.
Michaud85 said:
wait until someone comes up with a definate method of rooting the 2.3.3 otherwise you might look like a fool by breaking ur gf new phone.
Click to expand...
Click to collapse
I haven't laughed this hard in a long time, thanks!
Another way to get s-off is to put the phone on the stage at a strip club. Them exotics dancers can help you get it off...lmao
Michaud85 said:
haha yeah i just got my phone today and its so stupid how they force their OS on you. You cant even shut the phone off without pulling the battery (the power off in the menu just puts it to sleep so it boots up quickly when u power on). Hopefully someone can save us from this non rooted nightmare soon.
Click to expand...
Click to collapse
It sounds like you still have fast boot on. Just go into settings and applications the unchecked fastboot. Then it'll turn all the way off.
firket2000 said:
It sounds like you still have fast boot on. Just go into settings and applications the unchecked fastboot. Then it'll turn all the way off.
Click to expand...
Click to collapse
That will be settings/power settings. buddy
evolishesh said:
That will be settings/power settings. buddy
Click to expand...
Click to collapse
Nope just checked its applications at least on so keep nonrooted evo
firket2000 said:
Nope just checked its applications at least on so keep nonrooted evo
Click to expand...
Click to collapse
yup on mine to
Sent from my PC36100 using XDA Premium App
Can this be done?
Can you explain a bit more? The screen remains off until you turn it on.
I noticed this too. Unplug your phone and the screen turns on. Never happened on my previous android phones.
RogerPodacter said:
I noticed this too. Unplug your phone and the screen turns on. Never happened on my previous android phones.
Click to expand...
Click to collapse
Yep, this is what I'm talking about.
I did the Touchstone mod, and while at work I always grab my phone and go right into my pocket. I'd like to keep the screen off so I don't hit anything on the screen.
RogerPodacter said:
I noticed this too. Unplug your phone and the screen turns on. Never happened on my previous android phones.
Click to expand...
Click to collapse
Hmmm, this happens on EVERY phone or tablet I've used... Even my iOS devices do this. Same when plugging in... The screen will turn on.
I've wondered this myself. I'll attempt to make a tasker profile that shuts off the screen after a delay of a second or so after it detects being unplugged from the charger. I'll post if I have any luck with it.
I had a D2G and it would turn the screen on when plugged in, but not when unplugged.
I've created some tasker profiles that will turn the screen off after a three-second delay when plugged into (or unplugged from) USB or AC power. These rules are ignored when the phone has been unlocked and is currently in use.
I haven't tested them extensively so there could certainly be some bugs, but they've worked for me the past hour or so.
Just need a dev to do it.
<!-- If this is true, the screen will come on when you unplug usb/power/whatever. -->
<bool name="config_unplugTurnsOnScreen">false</bool>
frameworks/base/core/res/res/values/config.xml
adrynalyne said:
Just need a dev to do it.
<!-- If this is true, the screen will come on when you unplug usb/power/whatever. -->
<bool name="config_unplugTurnsOnScreen">false</bool>
frameworks/base/core/res/res/values/config.xml
Click to expand...
Click to collapse
This interests me more than a Tasker profile....
adrynalyne said:
Just need a dev to do it.
<!-- If this is true, the screen will come on when you unplug usb/power/whatever. -->
<bool name="config_unplugTurnsOnScreen">false</bool>
frameworks/base/core/res/res/values/config.xml
Click to expand...
Click to collapse
Could we just do the edit ourselves using something like Root Explorer?
No. It is compiled into resource.asrc.
All someone has to do is change that line and recompile that individual package. Easy for anyone already setup to compile and is synced to the repo.
Btw ard is on top of things for posting that so quick. He prob has every line of code memorized!
I've compiled AOKP with
<!-- If this is true, the screen will come on when you unplug usb/power/whatever. -->
<bool name="config_unplugTurnsOnScreen">false</bool>
I can upload it if anyone is interested
Sorry for waking up this thread from the dead, but I have 2 questions:
1) Could someone explain why if the current CM10 build I have on my GS3 (10-20121124-NIGHTLY-i9300) apparently has the value for config_unplugTurnsOnScreen set to false (according to the current github file: https://github.com/CyanogenMod/android_frameworks_base/blob/jellybean/core/res/res/values/config.xml), but still the screen turns on when unplugging from charge?
2) I actually also want this to happen when starting to charge (so that the screen keeps off when put to charge instead of turning on...), yet I didn't find a config_plugTurnsOnScreen configuration... Does anyone know where else (and if) this option could be found and tinkered with?
As a side note, I have modded my gs3 with the touchstone wireless charging trick and I put it on and off the touchstone charging base quite oftenly and would like to prevent it from turning on the screen each time I put it to charge or remove it from charging... maybe there's a general android option that handles wireless charging options so that the screen is not affected on those events? (something like these WebOS options intended for the original use of the touchstone on WebOS: http://www.webosnation.com/keep-screen-while-touchstone)
Thanks!
rgonzruiz said:
Sorry for waking up this thread from the dead, but I have 2 questions:
1) Could someone explain why if the current CM10 build I have on my GS3 (10-20121124-NIGHTLY-i9300) apparently has the value for config_unplugTurnsOnScreen set to false (according to the current github file: https://github.com/CyanogenMod/android_frameworks_base/blob/jellybean/core/res/res/values/config.xml), but still the screen turns on when unplugging from charge?
2) I actually also want this to happen when starting to charge (so that the screen keeps off when put to charge instead of turning on...), yet I didn't find a config_plugTurnsOnScreen configuration... Does anyone know where else (and if) this option could be found and tinkered with?
As a side note, I have modded my gs3 with the touchstone wireless charging trick and I put it on and off the touchstone charging base quite oftenly and would like to prevent it from turning on the screen each time I put it to charge or remove it from charging... maybe there's a general android option that handles wireless charging options so that the screen is not affected on those events? (something like these WebOS options intended for the original use of the touchstone on WebOS: http://www.webosnation.com/keep-screen-while-touchstone)
Thanks!
Click to expand...
Click to collapse
You might have better luck over in the galaxy s3 forum
http://forum.xda-developers.com/forumdisplay.php?f=1563
Darunion said:
You might have better luck over in the galaxy s3 forum
http://forum.xda-developers.com/forumdisplay.php?f=1563
Click to expand...
Click to collapse
Thanks... I thought the questions were generic-android enough to be answered right here....
adrynalyne said:
No. It is compiled into resource.asrc.
Click to expand...
Click to collapse
Ah, so we can decompile the framework-res.apk, change that value, then recompile it?:laugh::good:
EP2008 said:
Hmmm, this happens on EVERY phone or tablet I've used... Even my iOS devices do this. Same when plugging in... The screen will turn on.
Click to expand...
Click to collapse
FYI, it didn't happen on the N1. It did at first, but it was fixed after one of the updates. I hoped that was a sign that someone figured out how dumb it is to automatically turn on the screen right before I put it in my pocket, but apparently it was just an accident
[My device is a Sprint Galaxy S III, unrooted on STOCK 4.1 (with multi-view)]
So the previous night I plugged my phone into the charger as normal and went to bed. Strangely, when I woke up, my phone was turned off. Curious, I went to turn it back on and waited for it to boot back up, only to have it freeze up in the middle of opening an app. I wasn't worried at this point, but after a battery reseating and restart, it happened again. This time, it froze up on the 'Galaxy S III' boot logo. I tried multiple times to restart, swapping batteries, waiting, and managed somehow to get it to recovery mode. There, I managed to wipe cache and attempt to restart the phone once more. Nothing--it was still frozen on the boot logo. After waiting a while, I tried to get it back into recovery mode, popping out the battery whenever it froze. To my horror, this time, pressing and holding the power button did not get a response from the device.
Mind you in my (roughly) year's worth of time with this phone, I had never dropped it or subjected it to any form of shock or damage. Seriously--the phone looks out-of-the-box-brand-new.
Now the device is bricked(?) I'm thinking it's some sort of hardware defect, but I'm confused because it happened out of nowhere--simply overnight. Nothing I do seems to elicit a response from it and I even tried swapping in a freshly charged battery.
I really don't care about most of the data on the internal storage (cloud sync ftw!) but there are a ton of photos inside that I would give anything to save. Is there any way I could save them? I'd appreciate any input!
TL;DR: Out of nowhere, my 1yr old GSIII suddenly started acting strange and after some troubleshooting bricked itself. Need photos on internal storage.
Can you get Into download mode? If so you can just Odin it back to stock, but it will wipe everything on internal storage.
BEFORE YOU DO THAT, I know @CNexus knows some commands in adb that can probably save your photos on the internal storage. Let me see if I can find them real quick or he might see this thread first..
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Whiplashh said:
Can you get Into download mode? If so you can just Odin it back to stock, but it will wipe everything on internal storage.
BEFORE YOU DO THAT, I know @CNexus knows some commands in adb that can probably save your photos on the internal storage. Let me see if I can find them real quick or he might see this thread first..
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Click to expand...
Click to collapse
You haxor, why you mention my name, I had no choice but to show up...
@cytark
The following commands will pull all the pictures from your internal storage (connect phone to computer and make sure you are in the same directory as the adb.exe folder)
Code:
adb pull /sdcard/DCIM camera <press Enter and then wait..>
adb pull /sdcard/Pictures pictures <press Enter and then wait...>
Also, was your phone rooted? Because if the above doesn't work, then we can still get your stuff for you if you can get into recovery
Note: The phone is only truly bricked if it shows "QHSUSB_DLOAD" when you connect it to the computer.
CNexus said:
The following commands will pull all the pictures from your internal storage (connect phone to computer and make sure you are in the same directory as the adb.exe folder)
Code:
adb pull /sdcard/DCIM camera <press Enter and then wait..>
adb pull /sdcard/Pictures pictures <press Enter and then wait...>
Also, was your phone rooted? Because if the above doesn't work, then we can still get your stuff for you if you can get into recovery
Note: The phone is only truly bricked if it shows "QHSUSB_DLOAD" when you connect it to the computer.
Click to expand...
Click to collapse
My phone actually won't even go into download mode. It stays off no matter what I press. Will the adb commands still work?
Additionally, my phone is not rooted.
EDIT: Actually, upon plugging my phone into my PC, it says exactly that. QQ
Well yes it is a general term, but people tend to use it loosely with meaning that the phone won't go into the OS for whatever reason. When you overwrite the bootloader, that's when you have a brick. Either that or the kernel is so messed up that it fries your EMMC. On these phones when the bootloader is overwritten it will show as QHSUSB_DLOAD when connected to a computer.
Can you try connecting it to your computer and seeing what pops up? If it shows up at all, it may still be possible to recover it.
CNexus said:
Well yes it is a general term, but people tend to use it loosely with meaning that the phone won't go into the OS for whatever reason. When you overwrite the bootloader, that's when you have a brick. Either that or the kernel is so messed up that it fries your EMMC. On these phones when the bootloader is overwritten it will show as QHSUSB_DLOAD when connected to a computer.
Can you try connecting it to your computer and seeing what pops up? If it shows up at all, it may still be possible to recover it.
Click to expand...
Click to collapse
I see.
"QHSUSB_DLOAD - No driver found" comes up as a driver installation failure message.
cytark said:
I see.
"QHSUSB_DLOAD - No driver found" comes up as a driver installation failure message.
Click to expand...
Click to collapse
No bueno. Here this can get you fixed up. http://forum.xda-developers.com/showthread.php?p=43724690
Sent from the future via Tapatalk 4
CNexus said:
You haxor, why you mention my name, I had no choice but to show up...
I don't know what that means... I hope I didn't bother you. Sorry...
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Click to expand...
Click to collapse
Whiplashh said:
CNexus said:
You haxor, why you mention my name, I had no choice but to show up...
Click to expand...
Click to collapse
I don't know what that means... I hope I didn't bother you. Sorry...
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Click to expand...
Click to collapse
Dude c'mon, I'm just teasing
CNexus said:
Dude c'mon, I'm just teasing
Click to expand...
Click to collapse
Oh alright. Lol. I figured you knew more about this.
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Similar issues
I had a similar issue with my phone today. I'm mostly posting to show that this isn't an isolated incident, since I have insurance and can get my phone replaced, but any suggestions for fixing it would be very welcome.
My phone is a year old Sprint SGS3 running CM10.0 or so, stock battery with plenty of juice, haven't flashed anything or even booted into recovery in quite a while, no new apps for a week or so, no recent battery pulls, no usage out of the ordinary.
The phone died in my pocket, and upon trying to boot it would display the SAMSUNG screen for ~0.5 seconds, then display the "Samsung Galaxy S III" screen for ~0.2 seconds before dying. It did not bootloop, but remained off. Similar behavior was exhibited when trying to boot into recovery and download mode:
When booting into recovery, the SAMSUNG screen with the recovery overlay would display for ~0.5 seconds, then the "Samsung Galaxy S III" screen would come up for ~0.2 seconds before it died.
When booting into download mode, the SAMSUNG screen came up for ~0.5 seconds, then the warning about running custom ROMs came up. If I was quick, I could press volume up to start going into download mode, but it would still die almost immediately either way.
When plugged into a USB cable attached to a laptop or power, the battery icon would come up with the loading circle for ~0.5 s, then it would die. If plugged in with the battery removed, the right indicator light would come on and it would vibrate, but the screen would not turn on.
After booting over and over for some time, it will no longer respond in any fashion, except when plugged in with the battery removed as described directly above. I suspect the battery has died, and cannot be charged because the phone crashes before charging begins.
Any thoughts on how to fix it, or ways to revert back to stock when the phone won't stay on for more than 2 seconds?
That is The Sudden death Syndrome. Your power button has failed. It is messed up internally. This is a known issue with the S3. You can try blowing some air in the power button area and jiggling it around to get a temporarily working. But they do replace it for this condition.
Sent from the future via Tapatalk 4
That sounds very plausible. I noticed some irregularities with the power button as well, but didn't think they were worth mentioning. When you say "they", do you mean Samsung? Or someone else?
CogDancer said:
That sounds very plausible. I noticed some irregularities with the power button as well, but didn't think they were worth mentioning. When you say "they", do you mean Samsung? Or someone else?
Click to expand...
Click to collapse
Sorry when I referred to as they i meant Sprint.
Sent from the future via Tapatalk 4
Do you know if they will replace the phone past the standard warranty? I'm out of warranty by only a few days. I figured I had a problem with my battery so I bought a new one to test before I found the power button to have failed. I'm going to be heading back over in a few minutes to return the battery kit, and hopefully they will replace my phone without making me go through insurance.
CNexus said:
You haxor, why you mention my name, I had no choice but to show up...
@cytark
The following commands will pull all the pictures from your internal storage (connect phone to computer and make sure you are in the same directory as the adb.exe folder)
Code:
adb pull /sdcard/DCIM camera <press Enter and then wait..>
adb pull /sdcard/Pictures pictures <press Enter and then wait...>
Also, was your phone rooted? Because if the above doesn't work, then we can still get your stuff for you if you can get into recovery
Note: The phone is only truly bricked if it shows "QHSUSB_DLOAD" when you connect it to the computer.
Click to expand...
Click to collapse
I haven't ever replied to these threads but I need help so I hope im doing this right. I have a galaxy note 2 that did pretty much the same thing as the original thread poster. I can get to the recovery screen but I cannot connect to a computer. I really want my pictures and possibly to fix my phone. I appreciate any help you can provide. thanks