Database Users

Haykuro 1.5r3 keeps downloading official update CRB43

Hi,
I still use Haykuros 1.5r3 and since last weekend my battery went flat in like 8 hours each time after charging. There was constant GPRS traffic and I finally found out why: The system keeps downloading the official update: signed-kila-CRB43-from-PLAT-RC33.xxxxx.zip from the google site.
When the download is done, the signature check of course fails (this is actually expected as far as I know) and it is redownloaded and so on....
Anyone got an idea how I can stop this? Preferably without upgrading to a newer build! Restoring all my apps and data takes ages...
Thanks,
Dicer
Edit:
Creating an empty file or directory and only giving root rights to write does not help

I think you should really switch from this ROM to another.
It doesn't take so long to resetup...
If you relly want to not switch use "toggle data" from the market and disable your data connection when yxou don't use it.
Maybe someone here knows a better solution.

Random data usage

Hi guys,
Not sure what's happening on my Vodafone Magic...
Rooted it so i could install the HTC (htc_ime) keyboard. All that went fine all working ok. However since i've noticed my phone seems to be randomly using 5mbs of data every few hours. Can see this in netcounter. At one time i actually caught it happening, checked taskiller and closed everything that was running, yet the data still carried on transferring!!!
I've done a wipe to factory and set up again, just checked the phone before it was on 9mb, closed everything in taskiller, left for maybe an hour or two just looked and it now says 14mb.
Any ideas???

Could be the update problem I had. The phone downloads an update but fails to install (because the phone is rooted otacerts.zip does not match). If you catch it again you should be able to see the download progress in settings software update or the file being created in /cache. As soon as the download completes the update fails quietly and the cycle begins again. I'm looking for a stock ROM but for now I have copied /system/build.props from the ADB JFv1.51 ROM and is seems to have prevented the download from starting.

Roostlick said:
Hi guys,
Not sure what's happening on my Vodafone Magic...
Rooted it so i could install the HTC (htc_ime) keyboard. All that went fine all working ok. However since i've noticed my phone seems to be randomly using 5mbs of data every few hours. Can see this in netcounter. At one time i actually caught it happening, checked taskiller and closed everything that was running, yet the data still carried on transferring!!!
I've done a wipe to factory and set up again, just checked the phone before it was on 9mb, closed everything in taskiller, left for maybe an hour or two just looked and it now says 14mb.
Any ideas???
Click to expand...
Click to collapse
Turn off Data synchronization and see how it is. Maybe this is sync traffic

Downloaded JFV1.51 CRB43 ADP (10791) from the jesus freke blog.
adb pushed build.prop to system folder on phone, will leave it a few hours now and see if the data count randomly goes up or not, cheers!
Surely everyone should get this problem when they root? As i haven't put on a custom ROM or installed jesusfrekes stuff, just rooted it to install a keyboard!

Still doing it, went from 33mb to 37mb.
Could of done the build.prop wrong i guess, do you mind detailing the complete full procedure just in case?
Many thanks!

I had a very similar problem with my Magic although I don't know if it was downloading 5Mb chunks each time. It was on the stock firmware from Vodafone UK, can't remember if I had rooted at the time ... my Magic was rooted using these instructions: http://android-dls.com/wiki/index.php?title=Magic_Rooting
Just interested to see if you did the same? At one point I had noticed 200Mb of data downloaded within one week ... Voda only allows 500Mb per month in their 'fair use' policy.
I didn't ever fix this but wiped and flashed a different ROM, I've been OK since then. Unfortunately Netcounter does not tell you which apps have been doing the downloading!
I didn't have many apps installed but you know how it is, virtually every app in the market requires internet access for something or another.

Hmmm that sounds very similar to me st0kes.
Left Voda stock rom on, just rooted it to be able to install the htc keyboard and yep i used those instructions you linked to.
Think i will follow your lead and flash to a different ROM this afternoon, thanks for your reply!

How did you go flashing a different ROM Roostlick? Which ROM did you try (URL?).
I rooted my Australian Vodafone Magic the day i got it using the same instructions st0kes mentioned. I didn't replace the 'su' program since i didnt need it and seemed like an unnecessary security risk.
Data usage was fine (normal) for the first 2 weeks. Then it started downloading 4.5mb chunks every 2 hours.
Got close to my 1gig cap, so i turned off all data synchronisation. I have just received my bill today to find the cap was blown.... and that these 4.5mb downloads have continued.
Obviously looking to fix it, since i'm already 400mb through this months cap!!
edit: looked at Settings>About phone>System updates> and i can see "Android Update 1.5" waiting to be installed... no surprises its 4.2mb. I hit "download' on the update and it fails silently after downloading, giving a download prompt again.
Found some more info on the OTA updates in JF's blog here.
I'm currently testing the chmod solution:
./adb shell
chmod 000 /cache/download*

Hi rrfx,
I flashed the phone and installed the rom here:
http://forum.xda-developers.com/showthread.php?t=538633
Think it was the 3.6.8 release 4 version.
That seems to of fixed the problem

Roostlick,
You have done everything I did to solve the probelm except after I modified build props I did a factory reset and I have not hit the download button in settings->about phone->system updates since I did the factory reset. I still see the download available but it does not download any more.
Do you have the following info in settings->about phone (shows the build.props has been updated properly)?
Model No. = Android Dev Phone 1
Build = dream_dephone_.......
My phone is rooted as done here: http://android-dls.com/wiki/index.ph...=Magic_Rooting
B.

Hi guys, thanks for the information. I've fixed my phone now... for anyone else with this problem, and unwilling to use a 3rd party ROM... the path I followed from my post above.
JF's chmod 000 *.zip idea didnt work, my Vodafone Magic AU just kept downloading over the top. However using the SDK and logcat gave plenty of info
Code:
./adb logcat
I/SystemUpdateHelper( 63): Started a new update download: http://android.clients.google.com/updates/signed-vfpioneer-CRC1-from-CRB17.7fbab120.zip
D/InetAddress( 155): android.clients.google.com: 66.249.89.101 (family 2, proto 6)
D/InetAddress( 155): android.clients.google.com: 66.249.89.100 (family 2, proto 6)
D/InetAddress( 155): android.clients.google.com: 66.249.89.102 (family 2, proto 6)
E/SystemUpdateVerifierTask( 63): Verification for /cache/signed-vfpioneer-CRC1-from-CRB17.7fbab120.zip failed: java.io.FileNotFoundException: /system/etc/security/otacerts.zip
W/SystemUpdateHelper( 63): Download system update disappeared.
W/SystemUpdateHelper( 63): Download system update disappeared.
Specifically touching the exact filename in /cache and chmod'ing it 000 didn't work. Suspect the android downloader runs as root and seems to clobber the file anyway:
Code:
touch /cache/signed-vfpioneer-CRC1-from-CRB17.7fbab120.zip
chmod 000 /cache/signed-vfpioneer-CRC1-from-CRB17.7fbab120.zip
(didnt work)
I tried a bunch of other ideas, trawled through bits of the OS code etc. Tried manually downloading and forcing the OTA update.
What worked:
I tried replacing the build.prop file with JF's v1.51. If anyone needs specifics here happy to help.
Rebooted the phone etc, the build version didn't change and the downloads continued. I didn't want to do a factory reset! So left it like this for a couple of days.
This morning, checked the logs and the downloads weren't happening. Odd. Checked the build version and the "dream_devphone" seems to have been read from the build.prop file now! And in system updates "your system is currently up to date". Yay. So perhaps no need to do a factory reset.

Devs Need volunteers that are using 1.5

This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
First go here and download the RUU:
http://www.pcdphones.com/downloads/Eris%20MR1.zip
Next you need to go to verizon's website and login to your account. Click "Suspend/Resume Service" and suspend your phone. You can resume service on the phone after you are done here with no penalties or charges.
Please follow these directions, taken from the first root thread
bftb0 said:
Steps:
[Binny knows this, but if anyone else is reading, it is the same as a factory reset - you will lose all your settings and apps (but not the contents of the SD card)]
1) Unpack the 1.16.605 RUU - by running it as if you were going to actually do the RUU using the USB cable and your host PC, but stop right before you would apply the update to the phone. Pull the "rom.zip" file out of the temporary area that the RUU installer unpacks.
(Poke around under C:\Documents and Settings\<Username>\??? (I can't remember - you'll see folders with names that look like registry entries). You have to do this while the RUU installer is sitting there waiting for you - if you cancel the install, it will nuke everything it unpacked. I just made copies of the entire subtrees.
2) Cancel the RUU install.
3) Move the ROM.ZIP file to the root folder of your SD card, and rename it PB00IMG.ZIP
4) You can cancel the RUU install session on the PC, and unplug the USB cable if you want (so long as you have a well-charged battery!)
3) Power down the phone, and boot it back up holding the Call and End buttons simultaneously
4) Scroll down (or whatever it asks) to go from Fastboot mode to HBOOT mode
5) The phone will automatically discover the PB00IMG.ZIP file, and unpack it and verify it.
6) It will ask you if you want to install; when you (select and) enter Yes, the phone will reboot, and come up again - appearing as if it is repeating the same thing. This time, however, it won't stop and ask you - it will just begin the install.
7) Wait... Wait... Wait... Wait... and then wait some more. If I recall correctly, it seems to hang a little bit at the HTC splash screen after the reboot. That is normal - just WAIT and let the phone do it's thing.
That's it, except for:
8) You probably will want to dial *228 and choose option 1 to complete the programming of your phone - it will reboot after it completes.
Click to expand...
Click to collapse
After you are done, DO NOT start the OTA update that it prompts you to do.
Now we are going to install wireshark and setup the capture environment:
Download wireshark from http://www.wireshark.org/download.html for your versions of windows
Install it - make sure you also install WinPcap
At this point you should turn off any wireless encryption on your router. I know it's not necessary but it makes it easier to go through the captures.
Setup the wireless on your phone to connect to your wireless router and turn off your mobile data connection.
After you have turned off the wireless security on your router, we are going to start the wireshark capture.
Run wireshark - if you are on vista or windows 7 make sure to run it as an administrator
Click "Capture" then "Interfaces"
Click "options" next to the interface that your computer has an IP for
Make sure to check "Capture packets in promiscuous mode"
In the Capture Filter box, type "host <ip_address>" where <ip_address> is the ip address your router gave your phone
Make sure that "Automatic scrolling in live capture" is checked so you can ensure the capture is working
Click "Start"
At this point, you should browse the web with your phone. You should see lots of stuff scrolling by in the wireshark window.
If there isn't, you messed up something above and should try again.
If there is a lot of stuff scrolling by, continue:
Close the browser
In wireshark, click "Capture" then "Restart"
Reboot your phone
On your phone, go to "Settings" -> "About Phone" -> "Check for Updates" and go through with the OTA update
After the update is done and your phone is rebooted, go to wireshark and click "Capture" -> "Stop"
Then click "File" -> "Save As" and give it a name.
Upload that file to Megaupload, or Mediafire, or some other file sharing site, or any private server that I can get access to.
After you have uploaded the file please message me through the forums with a link to the file.
Thanks a ton.

e-mail me at [email protected] i got my wifes phones todo this to shes still on 1.5

NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.

Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip

FireSokar said:
NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.
Click to expand...
Click to collapse
You CANNOT downgrade from 2.1 to 1.5.

Videofolife13 said:
Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip
Click to expand...
Click to collapse
We don't need the location of the update file, we need all the extra network traffic that surrounds the OTA process.

Ah. My bad.

We need to know, exactly, how the update process works.
I'm currently working on downgrading 2.1. Will post back a tut if i get it working

Can't we create an AVD to run with a custom rom and use the Eris MR1 ROM to do it?

Scratch that. I don't think AVDs will get OTAs.

zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Sadly I tried this a while ago when messing around with AVD Skins but wasn't able to figure it out. If anyone can figure it out please let me know how you do it! -_-"

zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Wait can't you set it to wireless only mode and get the OTA through wireless? (Simulated by your network connection)

nindoja said:
This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
...
Thanks a ton.
Click to expand...
Click to collapse
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0

Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.

FYI,
When you roll back to MR1, the phone seems to have already grabbed and downloaded the OTA update... in less time than it takes to hand-configure the phone. If you want to observe the OTA process via wireless, you need to prevent the phone from having Mobile network access, since that comes up by default after a FR or MRx rom burn.
Here's a long shot. Perform the MR1 rollback inside a cell dead zone, and conduct a MIM attack by setting up a server on the wireless net so the phone downloads a different OTA zip. You control DHCP for WiFi, so you also in principle control the DNS and routing the phone sees via WiFi. In principle, it's not possible because https should prevent Man-In-the-Middle... but if that (Google) server isn't correctly configured, maybe the phone is not really being too careful about certificate problems. (Either that or the Google server is tuning its' responses based on UA strings).
bftb0

bftb0 said:
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0
Click to expand...
Click to collapse
bftb06: could you please PM me? I am going to trade my phone this week if you understand what I am getting at.

nindoja said:
Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.
Click to expand...
Click to collapse
Sorry, my bad. I didn't read carefully enough.
I could probably attempt what you are asking for - I am quite familiar with wireshark (and even hardware sniffing of WiFi, so long as you have the right nic), but the fact that the phone seems to go and look for updates immediately after a FR or MRx update means that the "check for updates" thing may not do anything useful for you if there is already an update on the phone waiting to be installed by the time you start pressing menu buttons. (Thus the idea about "do MR1 in a cell dead zone")
Beyond that, there is a possibility that the update app does not do a wildcard host bind() when it sets up the socket when it inquires about updates with the Verizon servers - for instance, MMS service works exactly that way (it will only use the mobile network interface), and precisely so because of security considerations. Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0

bftb0 said:
Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0
Click to expand...
Click to collapse
You can force updates to occur over WiFi if the mobile network is turned off. Do you think this would work:
1. on 1.17 do a factory reset but do not activate the phone.
2. Initiate the downgrade process
2a. while downgrading, turn on packet capture
3. When the phone boots back up and wants you to call a number to activate, hang up
I think if you can skip the activation the phone will not have a mobile data connection, which would allow you to turn on wifi and initiate the update process.

Im still on 1.5 PM me and ill help if needed

Do you guys still need this?

Can't find my 2.3 update

I was out of the country and used my phone on wifi. Of course as soon as I am gone, I get the notification for the 2.3 update. I downloaded it (160 megs or so) over wifi, but didn't install it since I wasn't sure if it would turn off my airplane mode and I would get slammed by tons of txt which add up $$ quick. It was always in my notification bar for the update and when I cleared all notifications it was still there under "ongoing". I landed back in the US and turned on the cell. A few minutes later I looked in the notifications and the update was gone. Anyone know where the file was saved on my phone so I can go ahead and run the update? Thanks in advance. I checked the "about" screen and I am still running 2.2 (was hoping it automatically updated without me knowing it).

DMC78 said:
I was out of the country and used my phone on wifi. Of course as soon as I am gone, I get the notification for the 2.3 update. I downloaded it (160 megs or so) over wifi, but didn't install it since I wasn't sure if it would turn off my airplane mode and I would get slammed by tons of txt which add up $$ quick. It was always in my notification bar for the update and when I cleared all notifications it was still there under "ongoing". I landed back in the US and turned on the cell. A few minutes later I looked in the notifications and the update was gone. Anyone know where the file was saved on my phone so I can go ahead and run the update? Thanks in advance. I checked the "about" screen and I am still running 2.2 (was hoping it automatically updated without me knowing it).
Click to expand...
Click to collapse
here, download THIS FILE, and rename it to "PD15IMG.zip"
place it in the root of your sdcard, reboot into hboot/bootloader by holding power +volume down buttons, then follow the onscreen instructions.
good luck

That file saranhai gave you is exactly what you need. Do as he says, and you'll get what you are wanting. Its the least dangerous flash you can make to your phone. If you walked into T-mobile and asked for the update they would pop in an sd card with that file and follow the same procedure.
BTW, its important that the name be all caps.
Sent from my HTC Glacier using XDA App

Correct me if I'm wrong, but I believe doing this manual install will wipe your device's memory. Just a heads up as a reminder to backup your data beforehand.

Yeah, it will. Sms backup & restore will save your sms messages at least.
Sent from my HTC Glacier using XDA App

Thanks for the help. Is there any way to run the update that I already downloaded ? I assume that it is stored somewhere, and wanted to see if anyone had an idea where.

Hello,
I really dont know if the file has the same name but you can try using find.
Something like that :
Code:
adb shell find / -name PD15IMG.zip
Regards

[Q] Random reboots - Is there a log I can view?

Hey all,
running CM7 (in particular this), and have always experienced these random reboots since I rooted/ROM'd etc.
I have worked out it is to do with 3G/4G data connection and/or swapping back to 2G to save battery or something along those lines. I have tried different radios, but not other ROMs (dont particularly want to change ROM).
My question is, is there a log file or some sort of diagnostic i can run to see exactly the cause so i can better find a fix/report the bug?
Cheers.

Ye, just write su than logcat > /sdcard/logcat.txt in terminal emulator this will save the logcat to the logcat.txt file, you can than copy that to your pc and see what happened before the reboot.

I'm going to try and provide a log too. Problem is, I usually only notice it after a while, when I take my phone and see that it has rebooted and waiting for PIN.

crnkoj said:
Ye, just write su than logcat > /sdcard/logcat.txt in terminal emulator this will save the logcat to the logcat.txt file, you can than copy that to your pc and see what happened before the reboot.
Click to expand...
Click to collapse
Thanks man, will do this very soon and post my log (if thats ok? and if there isnt anything personal in there)
EDIT: Holy c***. its 14,500 lines of code... what should I be looking for?

I have found there are several errors relating to GTalk (which i never/cant use). I didnt realise I hadnt Frozen this with Titanium Backup, so I have done that now.
I was also getting errors relating to sqlite and the Market, but not sure this is causing any reboots as yet, the error was as follows:
Code:
I/Database(12351): sqlite returned: error code = 0, msg = Recovered 8 frames from WAL file /data/data/com.android.providers.downloads/databases/downloads.db-wal
I will see if I get any more reboots and let everyone know, but I suggest freezing GTalk as a start if you are getting reboots.

FWIW the culprit in my case was SKYPE

wintermute000 said:
FWIW the culprit in my case was SKYPE
Click to expand...
Click to collapse
Really! Interesting. Did you uninstall or freeze?

Also, I can tell you that freezing GTalk definitely has reduced the number of reboots, but not eliminated it. I have just tried uninstalling Skype (I never use it anyway) as wintermute000 suggested, and will follow up again in a few days.

Uninstalling Skype has greatly helped. Thanks wintermute000!

No worries. I just run skype when I need and exit fully when done, no need to freeze or uninstall
Sent from my Sony Tablet S using Tapatalk

You can redirect stdio (will increase logcat events):
http://developer.android.com/guide/developing/tools/adb.html
sometimes dmesg it's useful too...