Database Users

Phone will not turn on [UPDATE]

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!

[Q] Nexus S 1st day and its froze, cant unlock

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??????

Dexter Mod 1.3 Update

I updated my new A7 with the Dexter 1.3 Mod (no additional patches). The update went fairly smoothly, but the tablet went into a loop and kept showing the ELocity Boot Up Screen for about five minutes. I was afraid that I had "bricked" it, but I eventually I tired of seeing it loop over and over again and started pressing the recessed reset on the back of the device. Fortunately, it booted perfectly and has been running very well for several days. Bluetooth is unavailable, but that is inconsequential to me.
One problem was that when attempting to read gmail or Google Docs the screen would not let you page. I discovered that if your turned the device from horizontal to vertical it paged without a problem. If you then turn the tablet back to horizontal it will still page perfectly. The problem seems to be with the Rom Update Software recognizing the orientation of the device (horizontal or vertical) when you first reach Gmail. I believe there is a physical device inside the tablet that notifies the software once the tablet has been flipped.
This is not a big deal. The Dexter Mod is excellent. I just thought people might be interested in knowing that they can get gmail and Google Docs to work perfectly once they change the orientation of the device.
Maybe someone can pass this along to Dexter.
Thank you.

There is a Bluetooth Fix that will resolve the issue. Put it on the sd using the exact same process as you did with Dex Mod v1.3, however do not do a wipe beforehand. What this will do is update the v1.3 rom with only the additional bt fix. It resolves the issue nicely.
As for Google Docs, I haven't tried it yet, but could it be that it is not optimized for a tablet? Might also want to check for an update on the market, just to make sure.

Link to BT Fix is right under the v1.3 download link on this post:
http://forum.xda-developers.com/showthread.php?t=890042

Thank you. I did see the Bluetooth fix, but I saw some later posts that said the patches caused additional freezing of the UI.
Additionally, I was not clear about how to apply the patch. Should it be after I do the initial Dexter 1.3 update? Also, it does not appear possible to get into recovery mode anymore on my tablet. Holding the power button for 2 seconds, then 5 seconds does nothing.
I assume that attempting to run the update from a running A7 would result in disaster? Or am I wrong.
I would be grateful for any assistance that you might be able to provide.
Thanks again.

desolom said:
Thank you. I did see the Bluetooth fix, but I saw some later posts that said the patches caused additional freezing of the UI.
Additionally, I was not clear about how to apply the patch. Should it be after I do the initial Dexter 1.3 update? Also, it does not appear possible to get into recovery mode anymore on my tablet. Holding the power button for 2 seconds, then 5 seconds does nothing.
I assume that attempting to run the update from a running A7 would result in disaster? Or am I wrong.
I would be grateful for any assistance that you might be able to provide.
Thanks again.
Click to expand...
Click to collapse
That's strange that recovery won't boot......I believe you can just perform an update from within the settings screen. Just remember to change the name of the bluetooth fix to update.zip.
Just in case: are you shutting the tablet down all the way?
Then just press the power button until the light on the power button turns on then immediately press the power button and hold until you see the booting into recovery message. When you see that message let go of the power button.

tetsuo_shima said:
That's strange that recovery won't boot......I believe you can just perform an update from within the settings screen. Just remember to change the name of the bluetooth fix to update.zip.
Just in case: are you shutting the tablet down all the way?
Then just press the power button until the light on the power button turns on then immediately press the power button and hold until you see the booting into recovery message. When you see that message let go of the power button.
Click to expand...
Click to collapse
Thanks to all of you who answered my post. I solved the problem, but not in the way I expected.
I always managed to get the device into the proper mode to update it, but I never got the menu that I did when I originally updated the device with the latest Stream TV (Elocity Now) firmware update. When I did the update from Elocity I got a full GUI interface to the update.
After the Dexter Mod I only got to an update script by hitting the back (hardware button) and then the home button). Eventually, with some trepidation, I realized that I could install the Dexter Patch in that fashion. Maybe that is the way it is supposed to work. However, I did not realize it at first and I had a great fear of bricking a new $350.00 device.
It is my first tablet device.
With the Dexter Mod it is really a good device. Everything (including Bluetooth) is now working properly.
I bought this device to teach myself how to develop database Apps with SQLite and that remains my intention.
Thanks to all those that replied to my email.

After reading all the threads I could find I decided to give it a go figuring the worst that could happen was that I would need to return the tablet.
Here is what happened.
I to got the looping elocity boot screen but was unable to correct it by use of the hard reset button. So I decided to take another tact. I held the power button down forever until it turned off. I removed the SD card. I then got into the reboot screen again and erased all user data and cleared the cache. I then rebooted and it worked.
I may not have needed to clear the cache but what the heck. Anyway it appears that there may be some conflict when the card with the update is left in the tablet for the initial reboot.
One thing that I did due before installing the update was to buy a new SD card. I realize I could of formated an existing card but hey for $10 it was just easier.
I also made sure that after I downloaded the mod that I renamed it Update though I couldn't find anything on the elocity site that specifically indicated the need for a capital "U".
Hope this helps someone.

Major software issues with stock Nexus 7 FLO and how to deal with them

It seems that there are some major issues with the new Nexus. This is unrooted, with locked bootloader.
People are reporting not being able to turn theirs on, or having random reboots.
My first boot never got past the Nexus X, and I had to hold the power button to restart.
Then I have had several times where the screen wouldn't come back on after sleep. Again, holding the power button down to restart worked fine.
Then I had gcore and gapps quit unexpectedly, followed by a reboot. I had just rebooted, and only opened one app: Evernote.
So I used the factory wipe option in the settings. Within seconds of completing and booting up the same processes quit unexpectedly.
I tried to reboot into recovery (by holding volume down and power) and got "no command". I tried 'adb reboot recovery' and got the same.
As far as I can tell, the factory ROM is not available for download at https://developers.google.com/android/nexus/images yet.
I obviously don't want to risk unlocking or installing anything custom if there's something wrong with the device.
I will probably have to return it to Amazon.
I haven't found much in the way of information out there, just a few complaints. If there are any well developed threads about how to deal with these issues, please let me know.

I've had a few apps quit on me and one time at the very first boot after the ROM update I had to force restart BUT I hardly consider these as "Major Issues".

There are always bad ones. Shipping, heat, cold, lightning, the chupacabra, darth vader, moisture, the blob, gremlins, or the Jaberwoky could have caused these "major" issues you have,
You're thread is bunk. Return it....

In stock recovery (when it says no command) have you tried pressing Vol+ to get the recovery menu.

I had the launcher force close on my Nexus 4 a few times shortly after I updated but after a few restarts it went away. Other than that I haven't had any issues with my Nexus 7.
Sent from my Nexus 7 using xda app-developers app

idheitmann said:
It seems that there are some major issues with the new Nexus. This is unrooted, with locked bootloader.
People are reporting not being able to turn theirs on, or having random reboots.
My first boot never got past the Nexus X, and I had to hold the power button to restart.
Then I have had several times where the screen wouldn't come back on after sleep. Again, holding the power button down to restart worked fine.
Then I had gcore and gapps quit unexpectedly, followed by a reboot. I had just rebooted, and only opened one app: Evernote.
So I used the factory wipe option in the settings. Within seconds of completing and booting up the same processes quit unexpectedly.
I tried to reboot into recovery (by holding volume down and power) and got "no command". I tried 'adb reboot recovery' and got the same.
As far as I can tell, the factory ROM is not available for download at https://developers.google.com/android/nexus/images yet.
I obviously don't want to risk unlocking or installing anything custom if there's something wrong with the device.
I will probably have to return it to Amazon.
I haven't found much in the way of information out there, just a few complaints. If there are any well developed threads about how to deal with these issues, please let me know.
Click to expand...
Click to collapse
Had I had these issues off the bat I would have returned the device for exchange or refund (if non where available for exchange). Definitely would not have rooted if I was experiencing issues, right back to the store I would of been.
Mine works very well and I LOVE it!

Thanks for all the encouraging words guys
I'm pretty sure the problem originated when the first boot failed and I forced reboot. The OS update must not have installed cleanly.
Anyway I just installed CleanROM and everything is peachy now. I guess whether shipping improperly flashed devices is a major issue or not is a matter of opinion, but I would expect better quality control from Google. I hope it's not too wide spread, and that anyone suffering this issue has the know how and confidence to install a stable ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta

Here's a major issue. Do NOT install widget locker, and then turn on talkback! You can no longer unlock the tablet!
I thought it was a goner, and that I was going to have to return it, but I googled and found out about safe mode, and then once I got that running, found another link on how to turn off talkback.
My God, is that the most annoying feature you could ever think of!
I was reading the google library information, and it said you had to turn an assessibility feature on in order for google books to readbooks out loud.
I'm back to square one with that now... anyone know how to accomplish this?

No issues here. I absolutely love the device!!
Sent from my Nexus 7 using Tapatalk 2

I have had the launcher die a few times, but that's the only issue I've noticed on mine (and since it comes back, it isn't that big a deal).

Freeze at wake up, system UI not responding

Dear forum users,
I'm the proud owner of a 6t, but it is starting to become a nightmare.
This started on June, with Android 9. I had the phone freezing at wake up (screen stays black, even when I get my op6t in hand, not responding to power button). After some time ranging from 1s to 30s, the phone will wake up and execute every action I may have done (multiple power button press etc).
I tried to do a wipe cache and data with no success.
Did a factory reset followed by a Google account restore (apps and all) that let me with a day fine, but it came back.
Then I did a factory reset with manual restoration, app by app. Everything fine till now (writing this the phone hanged till home button press (yeah I use the evil navbar)).
I did the same procedure, but for unknown reason, I only got a day off. I'm trying right now safe mode.
This time it happened right after a strange popup poping in a baby care app, asking me to select customized Gads to continue using the app.
I've posted on their support site too, but I'm willing to know what would you think about this.
Usually the freeze happens on wake up.
Screen will stay entirely black. No heating, no battery drain.
As the phone is a year from the buy order, I might ask for a refund or exchange, but it seems to me that the issue is with my Google account. Cause if I reinstall slowly app by app, I'm pretty sure this would go **** someone else phone, as for the first time.
I'm running oos 10.3.0 OTA
Thanks for reading to this line.

Found out this comes from end of trial week with no ads (accepting ads) from baby daycare app from drilly apps.

ldFxl said:
Found out this comes from end of trial week with no ads (accepting ads) from baby daycare app from drilly apps.
Click to expand...
Click to collapse
I was going to say that it sounds like you are getting pop ups from an app.
Glad you figured it out :good:

Scott said:
I was going to say that it sounds like you are getting pop ups from an app.
Glad you figured it out :good:
Click to expand...
Click to collapse
I was unaware of the secure mode, which is so fine to test if non system app is a source of problem without any factory reset or uninstall.
For those who also aren't just long press power off popup button.