Dear Users,
I am experiencing an issue which has been raised once before and no clear,
simple solution was found.
My current problem is that, after updating my G1 from 'cupcake' to 1.6, all
the calls I make and all the calls I receive are labelled as 'unknown',
despite the fact that these numbers are in my contacts. Here is the link to
the similar issue which was officially declined by Google:
http://code.google.com/p/android/issues/detail?id=2949
In the discussion thread amoung the users, there seem to be two possible
solutions (although this was not confirmed by Google, since the issue was
declined):
1. Complete factory reset.
2. STEPS:
1) Get to a shell prompt. If you're using ADB, it's "adb shell". If
you're using a
terminal/console app, just launch it.
2) Type "rm /data/misc/rild_ril.clip"
3) Reboot the phone.
My phone is currently not rooted and I have no intentions to root it in the
near future. Also, I do not favour the idea of a factory reset, since I
shall have to re-install all my applications, which will take time. The
second method to solve the problem seems the most probable in my case,
however the only problem is that, since I am not very good on the technical
stuff (i.e. 'shell prompt', 'console app', 'ADB'), I cannot figure out how
to perform what that method requests.
I would be very grateful to a person who would explain how to sort the
problem out in clear, step-by-step, user-friendly language.
Related
Hello all I'm very Nervous that I'm a Victim on Shell Shock on My Rooted Android HTC one M8. I need some help. I understand the problem is with Bash.
Here is history
Im Rooted with Stock Image of Verizon. I understand Shell Shock can affect if you if rooted.
However what happened is one day I notice my Wifi trying to connect to a weird server.
Also I notice my Gmail was hacked as a code was redeemed that google gave me so I changed password.
I did some Reading about Shell Shock and found this is problem
I used Cheetah Mobile Security app to enable Shell Shock Protection.
That helped and it directed back to correct Wifi
However something is increasing my ram higher than usual I think something is still running from this problem as my device is lagging.
I will be honest I have No Idea how to access Bash or Patch it. This is where I neeed some help if anyone can please help me!!
I'm hoping someone is this community could point me in right direction.
Awful people like this exist.
Read this
http://www.xda-developers.com/android/bash-patched-shellshock-vulnerability/
Xploited? More analysis needed
Hi Whiskey,
I see 2 seperate questions here:
1) is your device vulnerable?
If you have any unpatched version of bash installed, it will be vulnerable.
2) Was shellshock exploited to break into your device?
What are the symptoms you see?
You mention something about WIFI connections, and a laggy feel of the UI.
At this point I can not determine whether your device has been compromised.
If it was, the usual procedure for any device that has been compromised
is to clear all data and programs and re-install them from a trusted source.
So we need to analyze this further:
- Do you have a bash shell installed ( look in /system/bin for a file sh )
-Please describe the symptoms you see.
- Which programs or services consume a lot of ram?
- What exactly does not work?
- What exactly was the unusual wifi connection you noticed?
-Your phone might just have connected to an open WIFI in your vicinity if you configured WIFI to do so.
Best regards,
Euphoric
You test this?
https://play.google.com/store/apps/details?id=com.cleanmaster.security
Hello,
I have "Pandigital Novel Black / Model R70E200 / which supposedly runs Android 1.5" which went through SD card update which did not finished correctly.
My knowledge is limited at this moment about android internals but I am coming from PC Linux world which could help in resolution of following situation.
Yesterday I decided to read some documentation on the e-Reader but found that touch screen did not respond (buttons and orientation worked fine). I did attempted to restart the e-Reader a few times but without any success -- touch screen did not respond (the e-Reader was not used for prolonged period of time).
And it seems that by accident I "hit" a combination of buttons which supposedly initiated some unknown process at boot time. After this incident I had no option as to attempt to re-flash firmware.
For some inexplicable reason the flash process did not went as I would expect. Now it does not matter what I do process verification of firmware never ends.
I've attempted to get into "hard reset" but no success so far -- I always end up in re-flash situation.
To get at least some information for debugging of the situation I installed "adb" and was able to retrieve a log message which states following
link_image[1714]: 1760 could not load needed library 'libm.so' for '/system/bin
/sh' (link_image[1703]: 1760 missing essential tables)CANNOT LINK EXECUTABLE
and similar message about libstdc++
These two messages could explain why re-flash never ends -- I am not sure what happened but some libraries or damaged or missing and I am not able to get "sh" run.
I was able to pull "sh" binary on my computer but in Linux "ldd" could not "decipher" location of missing libraries so that I could attempt to push them in proper location in the e-Reader.
I would be happy to hear any suggestions how the situation can be corrected.
I still keep some hope that the situation can be corrected as "RDU" is still running and e-Reader still "has some breath in it".
RDU Version 2.8.9a (current boot count: 0)
Firmware version S6410_PPP2_BBB_2010_11_18
At normal boot the e-Reader has following behavior:
1. Please be patient while system starts
2. On the screen "Pandigital novel image with Contains Reader(R) Mobile Technology by Adobe System Incorporated" strangely shifted about 1/5 of the screen toward right side
It is quite difficult to establish a connection between adb and e-Reader.
Thank you,
Andromeda
andromeda_2010 said:
Hello,
I have "Pandigital Novel Black / Model R70E200 / which supposedly runs Android 1.5" which went through SD card update which did not finished correctly.
My knowledge is limited at this moment about android internals but I am coming from PC Linux world which could help in resolution of following situation.
Yesterday I decided to read some documentation on the e-Reader but found that touch screen did not respond (buttons and orientation worked fine). I did attempted to restart the e-Reader a few times but without any success -- touch screen did not respond (the e-Reader was not used for prolonged period of time).
And it seems that by accident I "hit" a combination of buttons which supposedly initiated some unknown process at boot time. After this incident I had no option as to attempt to re-flash firmware.
For some inexplicable reason the flash process did not went as I would expect. Now it does not matter what I do process verification of firmware never ends.
I've attempted to get into "hard reset" but no success so far -- I always end up in re-flash situation.
To get at least some information for debugging of the situation I installed "adb" and was able to retrieve a log message which states following
link_image[1714]: 1760 could not load needed library 'libm.so' for '/system/bin
/sh' (link_image[1703]: 1760 missing essential tables)CANNOT LINK EXECUTABLE
and similar message about libstdc++
These two messages could explain why re-flash never ends -- I am not sure what happened but some libraries or damaged or missing and I am not able to get "sh" run.
I was able to pull "sh" binary on my computer but in Linux "ldd" could not "decipher" location of missing libraries so that I could attempt to push them in proper location in the e-Reader.
I would be happy to hear any suggestions how the situation can be corrected.
I still keep some hope that the situation can be corrected as "RDU" is still running and e-Reader still "has some breath in it".
RDU Version 2.8.9a (current boot count: 0)
Firmware version S6410_PPP2_BBB_2010_11_18
At normal boot the e-Reader has following behavior:
1. Please be patient while system starts
2. On the screen "Pandigital novel image with Contains Reader(R) Mobile Technology by Adobe System Incorporated" strangely shifted about 1/5 of the screen toward right side
It is quite difficult to establish a connection between adb and e-Reader.
Thank you,
Andromeda
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
There's no dedicated forum for your device here in XDA.You can post your query in Android Q&A,Help and Troubleshooting.Experts there may be able to help you
___
v7
XDA Assist
Where to begin? Logic would dictate, the beginning.
I'll do my best to be brief with the backstory.
Months ago I ordered a Jide Ultratablet to use as my portable workhorse. At first things were peachy until a rather monumental lag began to manifest every 15-45 seconds. It made the device impossible to utilize in any productive fashion, so I contacted Jide and opened up a support ticket. After months (in no way an exaggeration) of barely responsive correspondence, during which I sent them a video to demonstrate the problem, they finally came back to me with an email containing a link to a compressed folder containing the Remix 2.0 images, and also a link to a rather vague and complicated tutorial on how to flash Remix 1.5 manually to a device. (In fact, I tried to include a link to the tutorial, but I am unable to since I haven't posted to the forum enough. I am happy to PM it or email it to anyone who might like to help) I can only assume I am meant to apply the same logic to the Remix 2.0 files they sent me. Seemed a bit dicey at first glance, but while I'm by no means an expert, I'm no slouch in this arena and I'm a very quick study.
Now, on to the proverbial meat and potatoes:
If you were able to contact me for a link to the tutorial in question, you will have undoubtedly seen that they indicate one should use ADB-Fastboot as a means to flash the recovery image. No real surprises there. I have ADB and Fastboot installed on my PC (Windows 10). I also have the ADB drivers installed and have confirmed the addition to my PATH. (eg: ;C:\ADB) I can also confirm that it is working fine since I am able to pull up a terminal and issue the ADB command and it gives me the usual wall of commands. The problem is that my device (Ultratablet) is not being seen by ADB. I have checked my USB drivers and they are all up to date and installed properly. My PC sees the device no problem and there is no indication of any sort of connection error. I've also tried different cables and ports. Yet, I can't access it via ADB and thus am unable to issue commands to my device such as "adb reboot bootloader" or "fastboot reboot-bootloader".
My next logical approach was to attempt forcing the device into fastboot mode using the hardware button combination, which is not listed specifically for the Ultratablet anywhere, I might add. (Power key + Volume up) It brings me to a boot options menu with the selections "Continue/Fastboot Protocol/Recovery Kernel/Reboot/Poweroff/Forced Recovery". Ateempting to select Fastboot Protocol causes the display to shut off for a moment, the device to vibrate once, and then the display to turn back on back at the same menu full of selections.
So, in summary, I am expected to flash the device using fastboot and yet I can't even get the device into fastboot mode, let alone issue commands from my PC terminal. As I highlighted near the beginning, teh Jide support team is incredibly unresponsive and not overly helpful. I have notified them of this same set of issues, but I don't expect to hear back in any expedient fashion and I thought one of the mighty members here on XDA might be able to help me come up with a next step in the meantime. I'd cerainly love to be able to use my shiny new tablet.
In any case, thank you for your time.
Kind regards.
Shaiden
XDA Visitor said:
Where to begin? Logic would dictate, the beginning.
I'll do my best to be brief with the backstory.
Months ago I ordered a Jide Ultratablet to use as my portable workhorse. At first things were peachy until a rather monumental lag began to manifest every 15-45 seconds. It made the device impossible to utilize in any productive fashion, so I contacted Jide and opened up a support ticket. After months (in no way an exaggeration) of barely responsive correspondence, during which I sent them a video to demonstrate the problem, they finally came back to me with an email containing a link to a compressed folder containing the Remix 2.0 images, and also a link to a rather vague and complicated tutorial on how to flash Remix 1.5 manually to a device. (In fact, I tried to include a link to the tutorial, but I am unable to since I haven't posted to the forum enough. I am happy to PM it or email it to anyone who might like to help) I can only assume I am meant to apply the same logic to the Remix 2.0 files they sent me. Seemed a bit dicey at first glance, but while I'm by no means an expert, I'm no slouch in this arena and I'm a very quick study.
Now, on to the proverbial meat and potatoes:
If you were able to contact me for a link to the tutorial in question, you will have undoubtedly seen that they indicate one should use ADB-Fastboot as a means to flash the recovery image. No real surprises there. I have ADB and Fastboot installed on my PC (Windows 10). I also have the ADB drivers installed and have confirmed the addition to my PATH. (eg: ;C:\ADB) I can also confirm that it is working fine since I am able to pull up a terminal and issue the ADB command and it gives me the usual wall of commands. The problem is that my device (Ultratablet) is not being seen by ADB. I have checked my USB drivers and they are all up to date and installed properly. My PC sees the device no problem and there is no indication of any sort of connection error. I've also tried different cables and ports. Yet, I can't access it via ADB and thus am unable to issue commands to my device such as "adb reboot bootloader" or "fastboot reboot-bootloader".
My next logical approach was to attempt forcing the device into fastboot mode using the hardware button combination, which is not listed specifically for the Ultratablet anywhere, I might add. (Power key + Volume up) It brings me to a boot options menu with the selections "Continue/Fastboot Protocol/Recovery Kernel/Reboot/Poweroff/Forced Recovery". Ateempting to select Fastboot Protocol causes the display to shut off for a moment, the device to vibrate once, and then the display to turn back on back at the same menu full of selections.
So, in summary, I am expected to flash the device using fastboot and yet I can't even get the device into fastboot mode, let alone issue commands from my PC terminal. As I highlighted near the beginning, teh Jide support team is incredibly unresponsive and not overly helpful. I have notified them of this same set of issues, but I don't expect to hear back in any expedient fashion and I thought one of the mighty members here on XDA might be able to help me come up with a next step in the meantime. I'd cerainly love to be able to use my shiny new tablet.
In any case, thank you for your time.
Kind regards.
Shaiden
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist.
First, you'll need to create an account so you can post in the other sections.
After you have done that, you can post your questions and ask the experts here:
http://forum.xda-developers.com/android/help
You're sure to receive quality answers there.
Good luck and welcome to XDA!
Over the past few days, I've noticed my phone rebooting on it's own. Now, that doesn't mean it hasn't been rebooting without me noticing. Like every other user on the planet, I'd normally use the uptime from the Status screen to see how long the phone has been up. Unfortunately, it states the phone has been up for hours, or days even, when it clearly just rebooted. The only reference to the actual reboot time is when the storage initializes; the storage folder timestamp is updated.
Some users have posted (here and elsewhere) that they are seeing similar issues with rebooting, but they are only being provided workarounds (uninstall apps, remove covers, factory reset, etc.). As a developer, I'd like to start seeing some posts that explain what's going on first. Then, maybe, we can provide some understanding before providing solutions.
To that end, does anyone have any information on the right tools to use to troubleshoot Android devices (Logging, monitoring, etc.)?
Thanks, in advance.
Cheers
Shield Tablet Bug Fix "missing home button, recent tabs, notification centre" Nougat
Hello Everybody. I have a Shield Tablet running Nougat. I have been experiencing the bug described in the Title a few times, and I finally found a way to solve such bug, at least in my specific scenario. It might not work for everybody but, as I have seen a lot of Users experiencing such bug and being forced to deal with it through a factory reset, I thought posting an easy guide might be helfpful to some. It is not rocket science, but for me it does the trick well. Should you feel there is an easier way to solve the same issue, please, do not hesitate to add it to this post.
I already posted this guide on the official Shield Tablet forum, but I cannot add the link because I am a new User (c'mon dudes, I am not spamming.. just trying to help ). Therefore, I am just gonna copy paste the guide. I apologise if the formatting is not ideal.
Hello Everybody, I know that there is an Android bug that has been creating issues for many years, also on shield tablets. When the bug starts, the home button disappears, it is impossible to open the "recent app" tab, the notification centre cannot be pulled down, and there are many other side effects. Since I started having this issue, I did quite a lot of research. Apparently, all I could find were information regarding how to solve the bug on Lollipop and Marshmallow, but nothing regarding Nougat. The way this bug is usually fixed is by starting the Setup Wizard on the device. Unfortunately though, I was not able to open it due to permission restrictions. Some guides mentioned installing Nova from the appstore, and setting up an action Widget in order to start the Setup Wizard. This did not work for me as well. What I was able to do, instead, was creating and setting up a new User profile, which then fixed the bug on my main User.
I am sure people more experienced and talented than me probably would have been able to find a neater way to make this happen. However, as I am quite a noob with these kind of things, I thought that writing a basic guide might be helpful for others as well.
Before going on, you should know that in my case, the only way to fix the problem is to have "debug settings" enabled on your device BEFORE the bug starts. When I first got the bug, I had not unlocked "debug settings" and I could not do it afterward, as tapping 7 times on the build number did nothing. You also need to have Android Debug Bridge (adb) installed on your computer and configured with the tablet.
Also, the process I will describing now creates a new User and switches to it by using terminal commands and Adb. I am aware that there would be an easier way to achieve the same result by going on "settings>Users" on the tablet. However, if you experience the same bug I was having, you will find out that clicking on the "Users" tab does nothing.
Here is a step by step guide of what I did:
1
Normally boot your tablet and connect it to the computer via usb cable
2
Run a command prompt windows on the computer and run Adb. Even if, due to the bug, you won’t be able to transfer files to the tablet via USB, adb should be able to interact with the shield anyway. To double check this, type the command: adb devices . You should be able to see your device listed.
3
It is now time to create a new User through the command prompt. You can do that by typing the command:
adb shell pm create-user User_Name
Once the new user has been created, the prompt will show you the respective User_ID. You will need to type such number in order to switch to that user, by typing the command:
adb shell am switch-user User_ID
eg. adb shell pm create-user Charlie
Success: created user id 11
adb shell am switch-user 11
4
Your shield should have now switched to the new user just created. At this stage, finish the new user configuration stage on the tablet. Skip all the google services related options, as you do not need them. When the configuration process is finished, the home button, the notification centre, the recent app, etc. should be back. Now that the bug is fixed, it should be possible to go back to your main User profile by simply switching User from the settings menu on the shield: settings>Users. At this stage, if everything went well, you should be logged with your main User, and the bug should have been fixed. It is now possible to go again on settings>Users and delete the new User created on step 3.
This is it. It works well for me and, even if I do not exclude that the bug will present itself again at some point, this is a 5 minutes solution to fix it. I apologise for any english mistake, as English is not by main language. Also, somebody might know of an easier way to solve the issue on Nougat, although I was not able to find any online, and that is why I wrote this short guide. I hope it will be able to help some of you!
Have a nice day!
Alberto