I rooted the first day and also did lag fix. Worked fine until this afternoon I haven't installed anything today and the only root app on the phone was (besides SU, BusyBox, etc) Root Explorer. Suddenly today while trying to update Twitter and Facebook via the Samsung Feeds widget I get a "network communication error". So I pull the battery and turn the phone back on and I get a very long Verizon splash screen and then it goes black. The capacative keys will light up and blink when you touch them but no other phone action besides that.
Any idea for a fix before I have to go get a replacement? Tried to run the unlagfix batch file and of course I get permissions denied since I can't SU from the phone.
Guess I got a little excited before trying the basics, here's what I did to fix it in case anyone else has the same problem...
1. Wait for the boot animation to stop and get to the black screen
2. Connect USB to PC
3. Run cmd.exe
4. cd to your Android SDK tools directory
5. Run "adb reboot recovery"
6. Once the recovery menu comes up volume button down to "restore factory settings" and hit the home button
7. Volume down to "clear cache" and hit the home button
8. Reboot phone
Something similar happened to me on a BB and also on my original Droid.
What worked: Put it on the charger. Walk away, watch a ball game, or a movie and a half, get some food, think about something else for about four hours.
Come back and try again.
It's a weird thing with these devices. As near as I can figure, they can actually run the battery down faster than the OS/firmware realizes, and then they need a good bit of charge to get running again. In all of my own cases, running off of AC didn't help, either, which really freaked me out.
If it's still not working by morning, start thinking about taking it in.
Good luck!
Updated, got it working.
kvaughan said:
Updated, got it working.
Click to expand...
Click to collapse
Awww Right!
Next time, what you may be able to do is run adb logcat to view the realtime log from the phone to get an idea of what's going on.
It's also good to remember that the rage*.bin file that you put into /data/local/tmp is an exploit that should get you root access back temporarily.
Of course, the steps you outlined above are also very helpful. Thanks!
Related
WARNING This is a long post describing various events of my G1 and things I was going through, so Im basically doing a dump of my thoughts and possible reasonings to put everything I can report, case it is a ROM, Hardware, or Software flaw somewhere or just user error. But since this forum is about feedback for devs or rom providers =)
Ok I dont know where to begin with this post. Last night my G1 needed a wipe. Why? Cause all it did was reboot over and over not getting past 1st home screen, then finally android screen. What happened before this? All I have of the things going on during that time frame was this:
(Now before the below stuff, earlier that day, Quest Live glitched on me, and when I was at the home screen, I tried to scroll left and right and it got stuck half way, which WORRIED me since I thought the touch screen was messed up. To my luck after a reboot and iso alcohol rub down on screen, it was fixed. Tho only after I unplugged it from the car charger (Which seems to really make the G1 % battery jump in record speed.. glicth?) Or Power Manager issues? Tho this wasnt the updated one, so the new one may have fixed the issues the dev said power manager was causing.
I plugged in the usb to a ubuntu running PC. To charge it, thus triggering Power Manager. Same time, I was trying to install SnapPhoto, which it downloaded, but didnt install, I was also noticing abit of lag, So I ran task manager to turn off some apps running in background, Camera, Gallery, Gaming Buzz Widget, Weather app Widget, Calender. (Then as I rem.. I tried to update AdFree when the new version came out.. it didnt install but same time when I tried to load it, it just came up black.. sign of a bigger issue maybe?)
After that of course couple of them came back. Then I tried to change the volume using the side button, It didnt respond, The on screen worked fine tho. So I decided ok, time to reboot fresh on the phone. Rebooted, Then it loaded to home screen before radio signal, then rebooted. After getting tired of not booting, (I had unplugged it from the USB btw which at 1st kept the charging light on before I rebooted it. ) I pulled the battery out. Which MAYBE I pulled it out at the wrong time during the android screen. Cause after that and I put it back in, all it did was goto the G1, then Android cycling screen, but no longer went to the home screen to try to load. Then was too late for this trick, but the Safe mode attempt. Which MAY have worked when it made it to the home screen, but once it was on Android only, safe mode didnt load at all. Just endless stuck on Android. So I had to wipe 1st then I reapplied the JF 1.51 update.zip to fix it and get the G1 to turn on again and boot.
Advice tip: If you can still boot to the home screen "somewhat" next time it cycles, try holding "Menu" in to have the G1 bypass any apps and load into safe mode, which may allow you to uninstall or fix whatever the issue is.
To my surprise. The Apps when the G1 started installing again went to the SD card. (I do not use apps2sd, Only Lucids orig) Now thats when I noticed more hell.. I went to the market to look at "My Downloads" and WHAM, the 10 apps it auto downloaded (Which I guess was a sync) are the only ones in the My Download section.. nothing from my past downloads.. Which is 110 more apps.
Advice tip: Use Atrackdog to "Export" your database to a text file and keep that on your PC. This way if ANYTHING happens, you least know which apps to look for.
Advice Tip: Upon reflection I probably should have made a nandroid backup after 1.51 was smooth. So if you havent, Id suggest looking at it) I know I will once Im set back up.
So now I am left with a interesting ponder. I msged Lucid to see if his scripts would allow me to use my 2GB which had my 1.51 data on it and somehow relink it to the G1 and have everything restored, then recopy to the 4GB which is my current one. But chances are I need to 1 by 1 install again. (Anyone know how you get apps back that arent on the market anymore? Extract from the SD card maybe?)
Anyways now I am wondering, If you install too much to the G1, will it in the end cause a problem? Im not a dev so I dont know how that all works with the ROM builds. But that wouldnt be good news if you have 129 apps, things could start messing up. (Tho not sure if that was a cause for any of the above)
Another thing I learned, if you have a GOOD screen protector on the G1 (Not the one it came with) and it smears up, or gets smudgy it seems it may interfere with the response of the touch screen. Ive notice if the screen thinks its being pressed in, a app could hang, lock up or choke the G1 to where it fixes itself by doing a reboot. Now that sounds odd that the G1 is sensitive to smudges or oil from your hands (If you had a humid hot day). Anyways fixed that with iso rubbing alcohol and a soft wipe cloth. Then rebooted.
Now my next task is to 1: Find out if my Cache since the wipe is running on the SD still, or if its on Internal. The app "Move Cache" I hear could do that, but I heard it messes up market, maps etc.. so not what I wanna do atm. Then I just gotta see if I can restore apps from SD using a app or terminal, which I am studying now, but just wanna end this post for now.
Will post more as I get around to it. Maybe I can restore the market cache manually.
do you still experiencing the touch screen error problem after all the steps you have taken? because i have the same problem. sometimes when i use touch screen to switch screens, the screen get stuck in the middle and shaking. i also cannot select anything correctly by touching. and i've read from various forums that this has something to do with the charger / charging process. i think that my problem occured because i charged using usb cable to my computer. because i never done that before (i usually charge my phone using a wall charger) and when i did, the problem happened.
How I fixed it? I turned off the G1, used rubbing alcohol with a tissue to gently wipe the screen off and clean it. Then turned back on and it was fine.
Hi guys, having a problem with the nexus s that i have just got today.
Installed an app for getting wallpapers, something like FLickir HD wallpapers or something.
Set a wall paper, then browsed on through others.
Phone soft rebooted, and now the screen and bottom buttons are totally unresponsive. No idea why, and no matter how many times i battery pull etc i cant get it sorted.
Any help would be a great help.
Can you get into recovery mode?
Pull battery. Wait 30 seconds. Put battery back in.
Press and hold volume up button, then press hold power on button.
Phone should enter Fastboot mode.
Use volume keys to highlight the recovery option.
Use power button to select it.
Once the phone starts to reboot you'll quickly see a little box pouring an arrow into an android figure, hold the power button, then press hold the volume up key. Timing (on my phone) is important, you need to be holding the power key first, then get the volume up key while the box and arrow are still there.
If you get to the Android and triangle, you might still be able to do the two buttons to get into recovery, but it doesn't work on my phone; some reports on various blogs say it does, though.
Once in Recovery, you should be able to pick the option to factory wipe/reset the phone. This will wipe the ROM space and reset the phone, but it won't touch the sdcard stuff. You'll have to set up the phone again, but that's not too difficult.
Just trying it now. Didnt realise about the 2nd stage of the power button and volume up. Just rebooting now after the reset.
Seems to have worked with the phone setup.
Will all my apps be gone?
kiteboarderni said:
Just trying it now. Didnt realise about the 2nd stage of the power button and volume up. Just rebooting now after the reset.
Seems to have worked with the phone setup.
Will all my apps be gone?
Click to expand...
Click to collapse
Yes, all apps from the Market will be gone.
So will your wifi settings, user accounts, EVERYTHING, except the sdcard contents.
You're basically putting the non-sdcard part of the phone back into the same state it was in when you took the phone new out of the box.
I'd recommend appbrain.com for your phone to have an easy way to reinstall apps if something like this has to be done in the future.
distortedloop said:
Yes, all apps from the Market will be gone.
So will your wifi settings, user accounts, EVERYTHING, except the sdcard contents.
You're basically putting the non-sdcard part of the phone back into the same state it was in when you took the phone new out of the box.
I'd recommend appbrain.com for your phone to have an easy way to reinstall apps if something like this has to be done in the future.
Click to expand...
Click to collapse
last i remembered Backup is on by default meaning all his apps will be re downloaded automagically and the WiFi settings will also be synced
slowz3r said:
last i remembered Backup is on by default meaning all his apps will be re downloaded automagically and the WiFi settings will also be synced
Click to expand...
Click to collapse
Ah, so much the better! It should just sync up after logging in with his account.
I thought I had to acknowledge I want that feature when I first set up the phone.
Either way, Appbrain still a neat combo of website discovery and phone installation, I find it very useful.
Ive been using app brain and the apps are being re installd.
However some of them that are in my list on the webpage, are not showing up in the app on my device. Any ideas why?
kiteboarderni said:
Ive been using app brain and the apps are being re installd.
However some of them that are in my list on the webpage, are not showing up in the app on my device. Any ideas why?
Click to expand...
Click to collapse
No, not sure, but if they're on your webpage, just click onto their links for the full app description page, then and cancel install if it's there as an option, and then install again.
this happend to me with two phones
Last night after my phone froze after downloading a wallpaper, after an initial pull of the battery the phone booted but the screen was unresponsive to touch, after I tried a hard reboot, with no success, I took it to best buy today and got a replacement. (Phone 1)
I Did system updated asked by the OS after i turned the phone on. (Downloaded update via wifi, and no sym card was in the phone) After Boot it was unresponsive to touch just like the last one. (Phone 2)
I went to Best Buy again and got a 3rd Nexus S. Have not done the system update and the phone is working well....for now
Any thoughts??????
My Kindle Fire, running CM7 and GoEx Launcher, froze today while browsing the internet. It is stuck on the last page I visited, no screen or power button response at all, and when I try to reboot using adb, it just tells me the divice is not found. Any ideas? I've tried remounting, rebooting, even just asking for log information and adb refuses to recognize my device. I'm not too savvy with adb, but I have used it to reboot the device before when I got it stuck in a boot loop, so I know basic commands and I know adb works. I'm not sure what else to do though. Any suggestions or ideas would be much appreciated. Thanks.
nogloww said:
My Kindle Fire, running CM7 and GoEx Launcher, froze today while browsing the internet. It is stuck on the last page I visited, no screen or power button response at all, and when I try to reboot using adb, it just tells me the divice is not found. Any ideas? I've tried remounting, rebooting, even just asking for log information and adb refuses to recognize my device. I'm not too savvy with adb, but I have used it to reboot the device before when I got it stuck in a boot loop, so I know basic commands and I know adb works. I'm not sure what else to do though. Any suggestions or ideas would be much appreciated. Thanks.
Click to expand...
Click to collapse
Hold down the power button on the Kindle Fire for about 20 seconds to shut it off and then turn it back on.
Thanks!
kinfauns said:
Hold down the power button on the Kindle Fire for about 20 seconds to shut it off and then turn it back on.
Click to expand...
Click to collapse
Well bloody hell I fell dumb. I guess I just wasn't holding the power button long enough. I though it wasn't responding. When I slowed myself down and counted one mississippi, ect. it worked haha! Any idea why that happened and why adb wouldn't recognize the device? No other screen controls or the power button were responding. Usually if I get stuck somehow, I can just type "adb reboot" into the terminal and it fixes it.
On a separate note, my device sometimes reboots spontaneously for no apparent reason. I haven't been able to see a pattern anyways. Any idea if these incidents are related?
nogloww said:
Well bloody hell I fell dumb. I guess I just wasn't holding the power button long enough. I though it wasn't responding. When I slowed myself down and counted one mississippi, ect. it worked haha! Any idea why that happened and why adb wouldn't recognize the device? No other screen controls or the power button were responding. Usually if I get stuck somehow, I can just type "adb reboot" into the terminal and it fixes it.
On a separate note, my device sometimes reboots spontaneously for no apparent reason. I haven't been able to see a pattern anyways. Any idea if these incidents are related?
Click to expand...
Click to collapse
If it's not a frequent occurrence, I wouldn't give it a whole lot of thought. It's just one of those things where several non-obvious things line up and the device gets the hiccups. Every few days, my KF with CM7 won't turn the display back on after sleeping, but it wakes up if I give it a jolt of power with the USB cable. Solar flares? Cosmic rays? I dunno.
If it really bothers you or it happens a lot, try wiping the caches or even reflashing the ROM.
kinfauns said:
If it's not a frequent occurrence, I wouldn't give it a whole lot of thought. It's just one of those things where several non-obvious things line up and the device gets the hiccups. Every few days, my KF with CM7 won't turn the display back on after sleeping, but it wakes up if I give it a jolt of power with the USB cable. Solar flares? Cosmic rays? I dunno.
If it really bothers you or it happens a lot, try wiping the caches or even reflashing the ROM.
Click to expand...
Click to collapse
Yeah, I guess it's not a big deal. Thanks for your help though.
I was playing NFS Underground on my Nexus 7 (Running Paul O'Briens MCR) and I have started having a weird problem with it.
I was playing away (at work) and someone came in the door, so I switched the screen off, after that it wouldn't respond to me pressing the power button to turn it back on. (I was using Gesture Control to hide the Nav Bar also)
So I held the Power Button to Hard Reset it, and it still wouldn't come back to life, so I thought I should plug it into the wall to give it a charge, then try again! When I picked it up 10 minutes later there was a weird vertical static on the screen (a bunch of white dots on black background), and again it wouldn't respond to any input.
From there I have tried to Wipe Dalvik & Cache and reboot (same happens), I tried to backup my ROM and flash a fresh one, the same thing happens in the middle of a backup.
I have managed to start it a few times (and it has now managed to process all the apps after the Dalvik wipe), but as soon as it boots, it just re-starts?
Anyone have any ideas how I can get it up and running again?
Also one thing I have noticed (this may be related to an updated Bootloader) whenever I plug my Tablet into the Wall, it turns on automatically! It definitely never used to do that!!
This is driving me mad!!!
Cheers
Stewart
EDIT - I seem to be able to put it in bootloader mode without it turning itself off!
Going to try flashing back to stock!
Quick question, can I pull a file from my SDCARD partition using my Mac while in bootloader?
Moral of the story, don't play games at work :/
But on a helpful note to you, yes you can pull a file.
If it doesn't boot, I'd get TWRP and the mount it whilst in recovery mode.
From there you can push/pull files
Hey all! It looks like dev forums are really the main places this is being discussed, so I thought I'd drop in and see if any of y'all had noticed this or figured out a fix for it:
I'm running Linux on Dex from my Note 9. Goal has been to set up Eclipse for code purposes, but also to see how useful it might be as a pentest box. At least 10 times now I've set the thing up, installed everything I want, followed what Samsung indicated were 'proper' shutdown procedures, and like clockwork when I plug it in again the next time the whole image is glitched out. The last time I did this was last night, and after I plugged it back in the screen was white with an invisible terminal window, where the green text only showed up when I moused over it. That's the first time it's done that, but it regularly either turns black, or elements render on top of each other, menu bars don't work, etc.
As far as I understand, we should be able to hover at the top of the screen, hit the 'back' arrow, accept the option to shutdown the container, then exit out of LoD, and then unplug the phone in order to close things 'gracefully'. When I have absolutely nothing installed, it seems to work, but the second I start installing tools from the Kali distro, it loses its mind and glitches everywhere. Granted I'm using Katoolin for those installs, but I would have imagined if they install properly and it's shut down properly, it ought to work, right?
Any of y'all have any experience with yours doing anything like this?