(Samsung) setup wizard has stopped - Android

This often happens when one tries to enable multiple users. Asuming that you have root, ADB, etc. try this:

Disable Samsung Setup Wizard:
pm disable com.sec.android.app.SecSetupWizard


Disable Google Setup Wizard:
pm disable com.google.android.setupwizard

Trick: you can try to install and run Titanium Backup to run it on the Android interface. 

See also StackExchange here for other method: via File Manager, etc., this one with pictures.

Android Speakerphone always on when calling

Is your Android phone is always loud (in the Speakerphone) when calling or being called? 

You may try these sensible steps first, and if that fails (as it has not resolved the speakerphone prob for me), toggle the Car Mode in Rooted phones, ON and then OFF, with this Car Mode Toggle app.

"Process system not responding" in Android - freeze plus reboot loop

After changing the SIM card or playing with WiFi settings in your Android device (stock or otherwise), you may see "Process system not responding" with a forced reboot.

This is what worked for me. Take your pick from the easiest to the hardest one: 

• Remove the battery. Let the power drain for 10 seconds and reinsert it. (Yes, only that.)
• Clear Dalvik Cache in the Recovery Mode.
• Change the boot animation to a shorter one. Try this one.
• Remove the Google Backup service. See here.

Android, Google: "Can't establish a reliable connection to the server"

Draft, ver. 1.0

127.201.26.224 android.clients.google.com mtalk.google.com

If you cannot add another Google account, getting errors:
Can't establish a reliable connection to the server
, or if synchronization of the existing Google services fails with:
Sync is currently experiencing problems
then your /etc/hosts file may be playing up.

Quite often this hosts file is created by an ad-blocking application, e.g. AdFree.

Despite this recommendation, it is not only this entry:
(see above)
that is playing up. In fact, I could not find it in my hosts file. I did not waste time experimenting which of these URLs is the right (wrong) one, so I just deleted the whole hosts file.

Here's how:
1. Run ES Explorer
2. Go to the root folder (/) and mount the system as Read/Write (now available in the Tools section, Root Explorer: ON)
3. Rename the /etc/hosts file to /etc/hosts.bak
4. Reboot (important).
5. Check if the hosts file is realy gone.
6. Try creating a new Google account again.

If that fails too, try toggling the connection between WiFi and Cellular. If all fails, try to restore the system from your restore point.

Recovering rooted and bricked Tolino Shine reader via ADB

[Draft]

Having rooted your Tolino Shine (a post to be written), you have been using it for a while. As the days passed by and the Internal Storage was bursting at its seams from the installed apps, you may have noticed that your new ereader has become sluggish.
What is worse, some autostart system applications (Button Savior, Floating Toolbar) fail to start on their own. Have you remembered about  checking the external and internal drives for errors and defragging them? No? Give them a try.

Despite these measures, one day Tolino may just die on you. There will be not even the creeping boxes boot animation - only the initial Tolino leaf will show. Of course you won't have a nandroid backup to speak of, either.

What did not work for me:

• fastboot
• flashing recovery.img with tools or manually
• toying with init.rc or /system files

That is what helped me instead:

• Make sure you have the right ADB driver files (e.g. Xiaomi), see How I rooted my Tolino post (to be written). 
• Check if you can see Tolino in the Device Manager as Google ADB, not Tolino
• Find the newest ADB.EXE package or download it off the Net.
• Connect a hung Tolino via a good micro USB cable. Try different USB ports.
• Check if Tolino has been discovered by the desktop computer. In the Windows command line run 

ADB devices

• If you see the identification number of the connected Tolino device (e.g. "00096e7549872f  device"), run

ADB logcat

to see the booting process. Most probably you will see a boot loop: a service refuses to start and the panic daemon keeps restarting it. Run

ADB shell

• If you are lucky, you should see #, which means you are running it as a root. Run

ps

• to list the processes. Try to find the PID of the service monitor, to kill it, e.g.:

Kill 2683

- that way, the booting loop should stop and you will have more processor power. You will need it, trust me.

• Run the QtADB front end and see if you can browse the root file system.
• Remount /system  as read and write:

busybox mount -o remount,rw /system

• Run

busybox mount /dev/block/mmcblk0p1 /sdcard

• to mount the SD card. (You may experiment with mounting the other images, e.g. busybox mount /dev/block/mmcblk0p4  /mnt/obb/, just to try)
• Copy one of the original Tolino update.zip files, select any from this forum, to the root directory of the internal sdcard (yes)
• Find and analyze the /system/bin/upgrade_check.sh script on your Tolino, the bolded part, see also Naberius' post. We will use a trick from there.
• On your computer, create a file named just command with the following content:

--update_package=/sdcard/update.zip

• Copy this command file to the /cache/recovery directory with QtADB, so that you get /cache/recovery/command
• You may need to change its permissions: chmod 777 command, just in case.
• Run this command, taken from the script:

am start -n com.ntx.msg/.MsgUpgradeActivity

• Run:

Reboot

in the shell, or press and hold the Power button to do it manually. 

If you are lucky, you will see the Recovery/Update screen. If you are very lucky, the update process will accept the update.zip file and you will have your /system and init files fixed.  Proceed to root your Tolino. See my "Root your Tolino" post (in the making) with more details.

"Insufficient storage available" Android error

Have you been bothered with the "Insufficient (internal) storrage available" error?

I have, for years now. Even upgrading to the ICS has not helped. I tried moving the apps to the external storage with Link2SD etc, but to little avail.

Exasperated, I analyzed the internal storage and finally found the culprit. The solution seems simple, maybe too simple. Here are the steps. Well, the step:

1. Delete the \data\logs folder.


That's it. Of course, you need to be rooted, and have the proper (simple) tools, listed below.

Here are the screenshosts

Before:

After:

Tools:

• Storage Analyser 

• ES File Manager  

How to solve Kies crashes: 6.1.7601.17651 bug

 Do you have an Android device? If so, do you use Samsung Kies to sync or update the content between your PC and Android?

You may have been faced with the infamous "Kies crash in 6.1.7601.17651" bug then.

It has been driving me nuts too. When using some pre-October 2012 Kies versions, I found that running Kies in Vista compatibility mode was a temporary workaround. No such luck with later post-Oct 2012 Kies updates: it crashed mercilessly on me each time, with the 6.1.7601.17651 error number as the only clue.

After troubleshooting, I discovered it is due to buggy calls to the Net 4.0 framework.

To solve it, you have to force Kies to use Net 2.0. Sounds scary? Needs not be.


1. Search for all *.config files in the Kies installation folder:


C:\Program Files\Samsung\Kies

2. Open each one. (Did I say: each?)

3. Delete the line:
    <supportedRuntime version="v4.*" />
(where the * part of the number, the build version, may vary depending on your configuration)
leaving the line:
    <supportedRuntime version="v2.0.50727" />
4. Reboot for good measure. Restart Kies.

This modification will force Kies to use the older, Net framework, version 2.0.

Your mileage may vary. It worked for me. 

Android backups: MD5 checksum and other CWM Recovery errors

• MD5 checksum error
• Data corrupted
• No directory XYZ

Such error notices remind you of the fragility of existence: if digital data rots that quick, even more so do your analogue body, heart and soul. Yet let not all hope be lost.

•  The MD5 checksum error

Cause: The MD5 checksum file for the backup was generated under a different Android OS or configuration.
1. Remove the SD card and browse its content on another computer.
2. Delete the content of the *.MD5 file, to get an empty file. Just open it (e.g. in Notepad) and delete all. (Do not delete the file itself, though.)
3. Rename the CWM Recovery backup folders, removing the spaces in the folder names.
(Some CWM Recovery versions do not like spaces for some reason.)

•  System restore errors

Cause: The restore process modified the CMW application itself. 
1. Reboot your phone
2. Enter the CWM Recovery menu again.
(Yes, as simple as that)

Android ICS "TwLauncher has stopped"

Every now and then, especially after moving some applications to the SD card or using the Today Calendar widget, the TwLauncher home screen freezes upon a reboot, with the error:
Unfortunately, Twlauncher has stopped



It is a common occurrence in Ice Cream Sandwich (ICS, Android 4.0), and seems to be gone in the Jelly Bean Android system version (+4.1).

A quick fix :
1. Click OK in the error message box.
2. Quickly slide the home page to the second page (or the previous one), that is: left or right.

Now, Option A, which hopefully will work

3. Pinch the screen in so that all the pages, including the home page, are seen.

4. Delete the page the widget that crashes your phone. (Most likely than not, it will be the Calendar Today widget, not necessarily on the home page.)

Alternative B:
3. If you can, go to Settings, Applications, All
4. Select the TwLauncher entry
5. Select Clear Data.
You will thus delete the folders, widgets, etc. on the home screen and in the Applications group.
Don't worry: your messages, pictures, contacts and other files, etc. will be left intact.
6. Possibly, restore the TwLauncher application data from your previous backup, e.g. via Titanium Backup.

Alternative C:
(Sine qua non: your Android phone should be connected to the Internet while the screen locking bug is on.)
3. Go to Google Android Play (aka: Market) from any other computer.
4. Log in using the credentials used in the locked Android phone.
5. Install an alternative Home launcher, e.g. Go Launcher Ex, or the best of the ones I tested, 360 Launcher.


See here for more details.