Database Users

Allways the same Android_ID

I dont know if this problem is known here,
all (in my opinion froyo builds) have the same android_id
In every build the id is: 9774d56d682e549c
this cause problems with some apps of the market because they use this id to identify the device. for example imobsters ;-)
see this post
forum.xda-developers.com/showpost.php?p=7251507&postcount=1110
sorry for my bad english

I think this causes a problem too with pMessenger, but I'm not sure if the Android ID or the MAC address is being used by pMessenger. However, both of them are identical on all our devices for now.
I think it should be trivial for the devs to fix it, but they are concentrating on fixing more major things now.

i am not sure, but maybe there is a way to change that id:
NOT ugly market fix
No more emulators!
Push this over to your phone, and you'll be able to get a working android ID without any sort of silly fooling around.
To repeat and clarify: You will get a fresh working Android ID, from Google, just like a phone.
From early testing it still appears SOME paid apps may be missing, but this is definitely a better solution than an ID from the 1.6 emulator as I continue to look into the issue. (I think this is actually less an Android ID issue than it is an issue with PDN being a configuration that some apps refuse to support, be it resolution, version 2.0 or whatever)
(I've also found that using your phone's ID on your PDN may "taint" what you can see in the market on your phone. Personally, I'll be moving away from sharing an ID with my phone)
Instructions
1) You'll need to remount system as R/W regardless. so let's start with that:
"adb remount"
2) If you want to start over clean, I'd recommend clearing market cache and killing your existing android ID.
adb shell sqlite3 /data/data/com.google.android.googleapps/databases/gls.db "update meta set intvalue='0' where name='androidId'";
To clear market cache: Settings->Manage Applications->press menu button->choose "Filter"->choose "All"->Scroll down to Market and select it->choose "Clear Cache"
3) Apply this hack
"adb push framework.jar /system/framework/"
4) Since we replaced a main framework, clear dalvik cache just to be safe, and reboot. Yes, the first reboot will take longer since we just cleared the cache.
"adb shell rm -r /data/dalv*"
"adb shell reboot"
5) Go ahead and log into Google Talk and use the Market to ensure all is working.
Feedback welcome!
File:
framework.jar
Click to expand...
Click to collapse
From here
I dont know if that works because its not for the hd2, but someone could try it.
I Mirrored the file in case it gets deleted:
Multimirror (Rapidshare, zshare etc.)
edit: I dont think that could work, i just tried to change to /data/data/com.google.android.googleapps/databases/ and it didnt exist at all ...

News
strazzere.com/blog/?p=217
but where can i find these "/data/data/com.android.providers.settings/databases/settings.db"

is there somebody out there who can say me how can i change my android_id on my HD2?

[Dev] Call for test, ril wrapper for pppd, 18/11/2010: test kernel 2K and wrapper 0.7

Dear All,
I modified libhtc_ril_wrapper to possibly fix the pppd disconnection problem.
As I don't have 3G at home, I'd appreciate some feedback to help me diagnose potential issues with it.
WARNING, there are reports of crash at boot, do a backup of your whole android directory before trying this!
Don't run this if don't have adb and know how to use it.
See post #2 for history and more information
To keep the thread clean, please only report problems and try to avoid unnecessary talking about it.
Don't report problem without logs, it won't help.
This is highly experimental, don't use it if you don't know what you're doing.
To install, just rename your previous wrapper and copy the attached libhtc_ril_wrapper.so to the same location.
Here are the logs I need:
Code:
logcat -d -v time -b radio > /sdcard/pppd_radiolog.txt
logcat -d -v time -s pppd:v > /sdcard/pppd_mainlog.txt
dmesg > /sdcard/pppd_dmesg.txt
/bin/ifconfig > /sdcard/pppd_if.txt
ps > /sdcard/pppd_ps.txt
Please review pppd_radiolog.txt before posting, it could show some personal stuff like phone numbers, feel free to remove these lines or refrain to post them
Wait 20 seconds to let the wrapper relaunch pppd and check connection again. If it doesn't work, please send the logs.
Grab the three files from sdcard root and post them back here.
I'm also experimenting some kernel tuning that can be activated with this:
Code:
echo 8 8 > /proc/sys/vm/lowmem_reserve_ratio
echo 8192 > /proc/sys/vm/min_free_kbytes
Nothing conclusive yet, but it seems to help.
Thanks to Hastarin, I also attached his root package that includes wrapper with ppp options and tweaks.
Thanks,
LeTama

History
2010/11/24 Hastarin root package (ppp_tweaks_root.zip) added, it includes wrapper, ppp options and kernel tweaks.
2010/11/18 new kernel and wrapper v0.7
new test kernel with smd_tty trimmed to 2K.
wrapper fake data call list has now active=1
v0.6 - 2010/11/17
same as 0.5 without the stupid bug that trashed the code.
2010/11/16
Test kernel to diagnose the "tty_prepare_flip_string fail" error with high cpu usage, please check post here for detail
v0.5: delay changed for deactivate and fake data call list added.
v 0.4 - 2010/11/14
Changed tag to RIL_WRAP to improve log reading
Improved log messages
Signal tracking to try to find who kills wrapper monitor
Lower delay between AT commands
Sleep delays and sequence reworked
Tentative improvement to re-establish ppp
Tentative fix for wrapper monitor death with extra debug messages
Memory leak on deactivate fixed
v 0.3 - 2010/11/02
added network state detection to avoid doing ATD too early resulting in getting stuck.
changed nand handling, proper initialization for nand is now done by adding "nand_init" to wrapper command line in init.rc.
(Ex: service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0 nand_init)
added a wrapper command line switch "rmnet_mode" for rmnet, "active" file in /etc/ppp is no longer used nor required for ppp.
v 0.2 - 2010/10/31, first release
restarts pppd when it dies
Troubleshooting
How to verify if wrapper is running:
In radio log (logcat -b radio -d), my wrapper write this at startup (do it quickly after boot, it disappears quite quickly over time):
Code:
----------- HTC Ril Wrapper v0.7 starting ------------
and you should have debug messages there starting with RIL_WRAP, not RILW.
Crash on boot (v0.2):
Check if your kernel command line in startup.txt has "nand_boot=0". If it still doesn't boot, try to remove any other option and only keep "nand_boot=0"
Troubleshooting crash on boot
Even if it crashes very early, it should be possible to grab early logs. To do that, start adb *before* starting android with this command:
adb logcat -b radio -v time
adb should say *waiting for device*, you can then start Android. Adb will show some logs before the device crashes. Please send me the logs if you are able to do so.
If you see [email protected]=0 in the log, it means that the wrapper thinks you are on nand, and that's why you device crashes.
pppd-fix
I saw in some logs that some are using Cass pppd-fix script with the wrapper. Cass script and wrapper are doing the same thing and are conflicting. So, if you have installed the pppd-fix, please remove it, it won't play nice with the wrapper.
Known issues
2010/11/14: pppd first launch fails after boot. wrapper catch it, however it would be nice to have it working the first time. It adds few seconds to re-establish data, so be patient!
2010/11/14: high cpu consumption. The issue comes from memory management in kernel, we still have to figure out what's happening.
2010/11/04: pppd monitor process seems to die from time to time. I don't know why yet, looking at the code it doesn't seem possible. I'll look into it and maybe release a new version with more debug traces. You can see it in terminal by doing a 'ps', it will show one of the rild as zombie ( Z instead of S just before process name). The easiest way to restart it is to do a data off/on.

Hi letama,
Currently i'm using ppp-fix. Can I contribute here? or I have to remove the script from init.rc then I reboot the device so I can contribute?

nice
try now

Hi LeTama,
thank you for your work.
It seems that your fix work. I don't notice any dropouts.
But that could be a reason of the issue that the phone does not start android.
It boots WM then haret and then it freezes on the black screen with the green HTC logo...
I use [UPD][BUILD][30.10.10] MDJ FroYo Revolution v.1.1 [kernel: hastarin R8] and after copying your file with ES explorer I've rebooted the phone and now it hangs on the htc screen after running haret...
But the good news are, the dropouts are gone
Sorry but I can't post logcat messages without booting android complete
Which build do you recommend?

funky81 said:
Hi letama,
Currently i'm using ppp-fix. Can I contribute here? or I have to remove the script from init.rc then I reboot the device so I can contribute?
Click to expand...
Click to collapse
Hi Funky81,
Well, it's better to remove ppp-fix as I do the same thing in the wrapper now. The way it's done in the wrapper is cleaner and should have the same effect.
You can just comment it in your init.rc if you want to keep it, but keeping it active could have side effects.

Crusoe86 said:
Hi LeTama,
thank you for your work.
It seems that your fix work. I don't notice any dropouts.
But that could be a reason of the issue that the phone does not start android.
It boots WM then haret and then it freezes on the black screen with the green HTC logo...
I use [UPD][BUILD][30.10.10] MDJ FroYo Revolution v.1.1 [kernel: hastarin R8] and after copying your file with ES explorer I've rebooted the phone and now it hangs on the htc screen after running haret...
But the good news are, the dropouts are gone
Sorry but I can't post logcat messages without booting android complete
Which build do you recommend?
Click to expand...
Click to collapse
You have adb on you pc ? You should be able to run adb even if android is not fully started.
With it, you can get logcat and even rename back the old wrapper to see if it starts booting again.

So far it's working very nice, I will be out and about today and will try to crash your masterpiece...
I just wanted to publicly say a big "THANKS" for helping everyone out with the PPP issues, you have always listened when I've popped in on the IRC and asked questions and relayed info from XDA. Thanks for your time and expertise. Your DEV work has not gone unnoticed!
Now get ready to fix the wrapper after we all crash it. Or read all the post on how your wrapper has made their microwave burn their popcorn and how their wifi can now communicate with the satellites....bla....bla.......

noellenchris said:
So far it's working very nice, I will be out and about today and will try to crash your masterpiece...
I just wanted to publicly say a big "THANKS" for helping everyone out with the PPP issues, you have always listened when I've popped in on the IRC and asked questions and relayed info from XDA. Thanks for your time and expertise. Your DEV work has not gone unnoticed!
Now get ready to fix the wrapper after we all crash it. Or read all the post on how your wrapper has made their microwave burn their popcorn and how their wifi can now communicate with the satellites....bla....bla.......
Click to expand...
Click to collapse
Hehe...that may not happen. At least for my copy. I am giving mine a thorough flogging with Speed Test and can't make the data freeze. And I'm seeing over 3000Kb/s HSDPA speeds...with the common, single APN settings. By the way, I'd like to thank both of you for your hard efforts.

testing...
testing now... thanks!

letama said:
You have adb on you pc ? You should be able to run adb even if android is not fully started.
With it, you can get logcat and even rename back the old wrapper to see if it starts booting again.
Click to expand...
Click to collapse
Sadly I got the same problem and it's the initial logo screen it's hanging at, not the boot animation, so no adb shell is possible. I did get you a dmesg via andlog though (attached).
Time to restore a copy of system.ext2 that I backed up before... Oh wait, I didn't. Oh well, time to restore the copy from the original build.
To anyone trying this I suggest first taking a copy of the system.ext2 from your Android folder, just in case. At least if you'd tweaked anything in it already (build.prop for example) like I had.
On the plus side I did setup a gscript with the commands you noted and test it before I rebooted the phone. From that I noticed I had some errors in my logs already. I've attached them in case they help. NOTE: This is on my kernel and it almost seems like your patch to hi/lo-mem and my patch to move ppp compression to hi-mem have countered each other. It's getting late here so I'll have to continue experiments tomorrow after work.

Hope this helps
Here you go. I had a disconnect and sync fail (Exchange Server).

And Another
Same as before

Dr Nicky said:
Here you go. I had a disconnect and sync fail (Exchange Server).
Click to expand...
Click to collapse
Dr Nicky said:
Same as before
Click to expand...
Click to collapse
crashes when your on exchange? were you doing anything else. Hmm, sounds like the same used to happen to me sometimes. But it's working ok now with this wrapper. Did you try to repush the wrapper on reboot?

hastarin said:
Time to restore a copy of system.ext2 that I backed up before... Oh wait, I didn't. Oh well, time to restore the copy from the original build.
Click to expand...
Click to collapse
Hastarin, you can mount the ext2 on your pc and replace the file ?
Your log show a modem crash, weird.

letama said:
Hastarin, you can mount the ext2 on your pc and replace the file ?
Your log show a modem crash, weird.
Click to expand...
Click to collapse
Yeah, mdeejay even sent me a whole build he had working with the wrapper and I got the same crash.
I'm back up and running now. Restored the original system.ext2 from the build and reapplied my few tweaks.
FYI I'm going to try the following in my init.rc
Code:
# Tweak inode caches
write /proc/sys/vm/vfs_cache_pressure 200
Based on this:
http://www.cyberciti.biz/faq/linux-page-allocation-failure-erro/
But now it's approaching 4am here and I really must sleep.
PS Giving up on testing your wrapper for now. It just really doesn't like me.

noellenchris said:
crashes when your on exchange? were you doing anything else. Hmm, sounds like the same used to happen to me sometimes. But it's working ok now with this wrapper. Did you try to repush the wrapper on reboot?
Click to expand...
Click to collapse
They were both forced repush. The only way I could get the radio back on line was to do a Hot Reboot.

Dr Nicky said:
Same as before
Click to expand...
Click to collapse
Thanks for the logs! Unfortunately, they are showing that the wrapper restarts pppd and it doesn't seem to go bad. Could you give me the dmesg also ?
Could you also show me /bin/ifconfig result ?
LeTama

I'm having the same issue as Hastarin - well, I've been using his latest kernel. Doesn't even boot.
Instead of restoring system.ext2, I just pushed an older lib and went back to the old method of restarting pppd.

My own logs for a dropout that just occurred (3G/H icon vanished while loading a web page). For me, the wrapper didn't work with Hastarin r8, but does with r7.7.
Thanks for looking into this!

Market won't stop force closing! - PLEASE HELP!

Hi all,
Last night, out of the blue, every time I tried to download an app from the Marketplace I got the error "process com.android.vending has stopped unexpectedly" and a force close. I have no idea what would have caused this as everything was working fine up until last night, I can't think of any strange updates or anything.
Anyway, after some Googling I cleared the market cache and data as recommended but now I can't even open the Market app at all - well it opens, but force closes straight off the bat (I see the Android TOS in the background). I now get the process com.android.vending has stopped unexpectedly error on boot and whenever launching the market.
I've attempted to install a newer market.apk (current one is 1.82) but Android won't allow me.
The only other recommendations people have given on here to those experiencing this issue on dedicated Droid handsets is to either do a full format/install or to flash something via recovery (doesn't look like I can do this on my SD build)
A couple of months ago I was getting force closes on the calender app and someone sent me a droid.zip file which had a fsck.exe inside it which allowed me to repair my data.img which in turn fixed the problem. I've formatted my PC since than and lost the files and can't find them via Google, at least not one that'll run under Windows command prompt with "fsck.exe data.img" after placing the data.img in the same directory. Can anyone point me in the right direction? Or better still provide an alternative method for fixing this issue?
Using Darkstone's SuperRAM 1.5 Froyo build.
Many thanks!!

maybe you should try an other android rom ?

The best and quickest way to fix this is to use market.app from same build what u got.
So its mean u need to extract this particular app from the ROM and copy it to the /system/app
Or if u dont know how to extract it just ask in your ROM thread so someone whos know how to extract it and than can post it for download.
SMS92 said:
Hi all,
Last night, out of the blue, every time I tried to download an app from the Marketplace I got the error "process com.android.vending has stopped unexpectedly" and a force close. I have no idea what would have caused this as everything was working fine up until last night, I can't think of any strange updates or anything.
Anyway, after some Googling I cleared the market cache and data as recommended but now I can't even open the Market app at all - well it opens, but force closes straight off the bat (I see the Android TOS in the background). I now get the process com.android.vending has stopped unexpectedly error on boot and whenever launching the market.
I've attempted to install a newer market.apk (current one is 1.82) but Android won't allow me.
The only other recommendations people have given on here to those experiencing this issue on dedicated Droid handsets is to either do a full format/install or to flash something via recovery (doesn't look like I can do this on my SD build)
A couple of months ago I was getting force closes on the calender app and someone sent me a droid.zip file which had a fsck.exe inside it which allowed me to repair my data.img which in turn fixed the problem. I've formatted my PC since than and lost the files and can't find them via Google, at least not one that'll run under Windows command prompt with "fsck.exe data.img" after placing the data.img in the same directory. Can anyone point me in the right direction? Or better still provide an alternative method for fixing this issue?
Using Darkstone's SuperRAM 1.5 Froyo build.
Many thanks!!
Click to expand...
Click to collapse

yz.hd said:
maybe you should try an other android rom ?
Click to expand...
Click to collapse
Not really an option - The build I use is the most stable and one of the most widely used here on XDA (outside the Nand forum) and has been nigh-on perfect up until now (in daily use since before Christmas). I can't replicate how and why this happened so there's just as much chance of it happening on another ROM. Google suggests it's a common problem with the fix (for non rooted/savvy) people to factory reset their devices.
There's got to be a better way and I'm sure the crew here will find it!
The best and quickest way to fix this is to use market.app from same build what u got.
So its mean u need to extract this particular app from the ROM and copy it to the /system/app
Or if u dont know how to extract it just ask in your ROM thread so someone whos know how to extract it and than can post it for download.
Click to expand...
Click to collapse
Thanks - I'll look into doing it now. I've had no luck installing various Market apks though (with the default market disabled / cleared, etc.) so I'm unsure of the results!

SMS92 said:
Not really an option - The build I use is the most stable and one of the most widely used here on XDA (outside the Nand forum) and has been nigh-on perfect up until now (in daily use since before Christmas). I can't replicate how and why this happened so there's just as much chance of it happening on another ROM. Google suggests it's a common problem with the fix (for non rooted/savvy) people to factory reset their devices.
There's got to be a better way and I'm sure the crew here will find it!
Thanks - I'll look into doing it now. I've had no luck installing various Market apks though (with the default market disabled / cleared, etc.) so I'm unsure of the results!
Click to expand...
Click to collapse
This should help cos if u do it this way u actually not installing/reinstalling the app. u actually repleace the sys market.app for the original one from the ROM. So there is no way it will not work again if it was working before after u flashed the ROM.
I'm pretty sure it will do the trick, but also I may be wrong .
I had some issue on my ROM with cam.app and this proced. helped me.

Hey,
you can try this (very simple):
1. Open terminal emulator
2. type "su" (without quotes) and hit enter
3. type "fix_permissions" (without quotes) and hit enter
4. wait until process is done and exit terminal
5. maybe reboot, but should be fine without reboot
This is a common way to fix force closes, so maybe this helps in oyur case too.
Greetz Dom

FIXED! [Edit: not]
Here's what I did.
Downloaded THIS
Extract it to C:\Droid
Boot into Win Mobile and move your data.img in \Android\ into the \Droid\ folder on your PC.
Start > Run > CMD
type "cd c:\droid" (without quotes) to get into the directory you've created.
Type "e2fsck -f data.img" (without quotes) and say 'y' (yes) to all the errors you encounter. There will be dozens. When done you'll be notified the modified data.img has been saved.
Copy the newly modified data.img from \Droid\ to \Android\ on your device.
Boot into Android - things might be a bit slower/laggy at first.
All should be well!
Edit: This fix seems to have really slowed my phone down. It takes at least 2x as long to run stable on boot (i.e. stop lagging, load all background apps etc). I've imported my previous data.img over and will be trying the fix by Dom (above).
Edit2: And I'm now getting com.android.media force closes with the modded data.img! Music app won't work. Jesus!

ricola7 said:
Hey,
you can try this (very simple):
1. Open terminal emulator
2. type "su" (without quotes) and hit enter
3. type "fix_permissions" (without quotes) and hit enter
4. wait until process is done and exit terminal
5. maybe reboot, but should be fine without reboot
This is a common way to fix force closes, so maybe this helps in oyur case too.
Greetz Dom
Click to expand...
Click to collapse
Thanks for that Dom, I'll keep that in mind for next time! Great tip!

ricola7 said:
Hey,
you can try this (very simple):
1. Open terminal emulator
2. type "su" (without quotes) and hit enter
3. type "fix_permissions" (without quotes) and hit enter
4. wait until process is done and exit terminal
5. maybe reboot, but should be fine without reboot
This is a common way to fix force closes, so maybe this helps in oyur case too.
Greetz Dom
Click to expand...
Click to collapse
Hey Dom, terminal tells me "fix_permissions: not found" when I run fix_permissions. Am I missing something? (I've su'd before hand) Guess Darkstone hasn't included this script in his rom?

Same here ...?
SMS92 said:
Hey Dom, terminal tells me "fix_permissions: not found" when I run fix_permissions. Am I missing something? (I've su'd before hand) Guess Darkstone hasn't included this script in his rom?
Click to expand...
Click to collapse
Sent from my HD2 Jaws-MIUI

Did fix_permissions via the app ROM Manager and the Market force close still remains

How about getting a fresh copy of the ROM, and just keeping your data.img. It may not work, but it's surely worth a go.

SMS92 said:
Hey Dom, terminal tells me "fix_permissions: not found" when I run fix_permissions. Am I missing something? (I've su'd before hand) Guess Darkstone hasn't included this script in his rom?
Click to expand...
Click to collapse
rikardo1979 said:
Same here ...?
Sent from my HD2 Jaws-MIUI
Click to expand...
Click to collapse
Hmm, it seems that this script isn't inluded in your roms. But for you SMS92 it seems that it is another problem anyway.
If you wanna try sth. else see this:
http://all-google-android.com/google-android-forums/t-mobile-g1-modders/fix-permissions/
This is an "improved" fix permission tutorial which goes further than the command I posted above...quote from the link above: "fix_permissions is only intended for correcting ownership issues. It does not modify permissions, as is being requested."
In this post is a downloadlink for the advanced script so it doesnt matter if its already included in the rom...
@ricardo: see here if you still wanna try it: http://modmymobile.com/forums/567-motorola-backflip-general/556261-fix_permissions-script.html
Greetz Dom

johncmolyneux said:
How about getting a fresh copy of the ROM, and just keeping your data.img. It may not work, but it's surely worth a go.
Click to expand...
Click to collapse
It's a no-go I'm afraid.
So far the only thing that's worked is running the repairs on my 2gb data.img using e2fsck on my PC, but this in turn created a load more problems (com.process.media started force closing and the rom seemed to be much slower)
Will try some more suggestions tonight.

if your running gingerbread make sure the app is installed on the phone not the sd

I'm also suffering from this issue it started for me when an automatic update downloaded (which I didn't install) I will see if any of the above fixes work for me & if not I will start with a fresh copy of the ROM. Have to admit I have barely used winmo since I started using this build!

I have the same problem using froyo 2.2

I've had the same problem, just did a totally fresh install, ok now
Sent from my HTC Desire using XDA Premium App

robdee102 said:
I've had the same problem, just did a totally fresh install, ok now
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
Any chance you could walk me through the steps you took for a fresh install? I am at my wits end with the FCs and a mount/partition error. Here is my setup:
HTC Hd2 Leo
HTC Desire
Android 2.2.1
Mod darkstone SuperRAM FroYo v1.5
Build FRG8
I am up for a new ROM or whatever to get my phone back in order. Thanks so much!

BOYPPC-SHIFTPDA v.37 Market Force Closes
BOYPPC-SHIFTPDA v.37 Market Force Closes
Please Help my Market is constantly force closing on me the error is:
Sorry!
The application Market
(process com.android.vending)
has stopped unexpectedly.
Please try again.
then it has a force close button.
I would really like to install some apps with the market but
every time I try and use the market I get this error,
I am running the BOYPPC-SHIFTPDA v.37 ROM
Please Help Me

Build.prop of newest update?

If someone has been able to properly update can you please pull the build.prop and post it up here? I'm using enomthers ROM and want to get rid of the annoying update message.

If your getting the message, download the file and give us the location / filename and i'll be happy to give you the current buildprop

Ok even though I've been a nexus one owner for over a year now and have flashed various roms, and know how to use adb, I have not a clue how to do that. Tell me step by step and I'll do it.

ksc6000 said:
Ok even though I've been a nexus one owner for over a year now and have flashed various roms, and know how to use adb, I have not a clue how to do that. Tell me step by step and I'll do it.
Click to expand...
Click to collapse
Install alogcat or a logcat logger from the market and then do a checkin (call *#*#2432546#*#*) then filter the logcat (Menu - Filter from within alogcat) and search for http or .zip

Hollow.Droid said:
Install alogcat or a logcat logger from the market and then do a checkin (call *#*#2432546#*#*) then filter the logcat (Menu - Filter from within alogcat) and search for http or .zip
Click to expand...
Click to collapse
I don't think it worked. I installed alogcat, opened it, then went to my dialer and typed that in...and then now my notification bar no longer shows the update, but shows "Checkin succeeded"..so went back to alogcat, hit filter and typed in http and none of these look like the right links. it's the link that goes along the lines of //android.clients.google.com/checkin (1 requests sent).
filtering by zip comes up with nothing.
also as i said above now my update message is not in my notification bar.
Okay. got the update thing back. went into settings>about phone>system updates and now it's showing there again.

Connect the phone with your computer.
Run adb logcat and make sure your phone's logs
Download the Update
Send us the complete output of adb logcat after downloading has started

georgemv said:
Connect the phone with your computer.
Run adb logcat and make sure your phone's logs
Download the Update
Send us the complete output of adb logcat after downloading has started
Click to expand...
Click to collapse
Just to be clear once again, I don't WANT the update..so by trying to install it, it should fail as I have a custom recovery and ROM right? I don't want to screw up my setup.
EDIT: F$ck. Sorry guys I think I might have screwed it up. I ran adb logcat, and instead of going into settings>about>system updates and hitting download I hit install now from the notification bar thing. The phone rebooted and then the installation cancelled. And looking through the logcat I didn't see any links so I decided to try it again, but now when I go to settings>about>system update it says my phone is up to date. I've heard that people who don't want the update try that and let it fail so that it doesn't bother them again, but also heard that it doesn't work as the message comes back after a little while. Hopefully it's the latter for me so I can get it right this time. If and when it does come back, am I correct in assuming that what I should do is go to settings>about>system update and try to download it there rather than hitting the install now option from the notification bar?

It should fail with a custom recovery, but do take a backup just in case.

Flash FOTAKill and don't bother yourself with build.prop and such.

Would you mind then sending me a PM with your IMEI and SN so I can fake them to Google and get the download link?

I guess he does mind...

Makes sense. It's a hard decision

[Q] Stuck on splash screen

Good evening everyone.
To start with, yes I've read all the similar topics and none of them helped me
To my problem now. My phone has been flashed with a custom ROM for 1-2 months now (I don't remember exactly) and this morning I woke up to find my phone turned off. While trying to turn it on, no matter how much time has passed, it's stuck on the splash screen refusing to load the home screen
Is there any suggestion that does not involve me losing all my data because I have no backup of them?
Waiting for any suggestions.

See if you can connect with usb, and adb can communicate with device.
If yes, you can save the /data/data folder(in which are all configurations) + /data/app folder(in which are all apps except these on sdcard if any).
You can also run adb logcat from command prompt and see if you can find what app causes the error and the bootloop, and if maybe you can uninstall/reinstall this app, or delete the folder of that app on /data/data folder, to hopefully solve the error.
Try to install a program like QtADB, droid explorer or Android manager to avoid use command line and simplify some of above operations as copy/delete folders or install/uninstall apps.
If you need more help, PM me to speak in greek(it' s better)

I've just installed QtADB and connected the phone while being inside ClockwordMod v4.0.0.5.
The truth is that from here I don't get almost any useful information (don't know why). One positive aspect is that I can copy data from/to the phone.
While stuck in the splash screen I can't connect through adb though.

You mean not at all? Usually when appears IDEOS screen you can connect via adb, after some time and when the error start maybe the device freezes and then adb probably disconects, but until then you can take some useful logcat info for the error.
You can also have some more functions with QtADB on recovery mode if you mount the partitions first.
Maybe and the app manager work then(I haven't tested though).

Managed to get logcat information while turning on the phone. I'm attaching the log file with the error lines.
Trying to read them right now to find a solution. Any help appreciated.

gkaran said:
Managed to get logcat information while turning on the phone. I'm attaching the log file with the error lines.
Trying to read them right now to find a solution. Any help appreciated.
Click to expand...
Click to collapse
By reading your log i think the problem is permissions. Try to fix permissions with recovery tool.