• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Help the Hacking Community!

M

mazz0310

Android Enthusiast
Help the hacking community - snag the update.zip...instructions - Droid Forum - Verizon Droid & the Motorola Droid Forum

Help the hacking community - snag the update.zip...instructions


So the update will be rolling out today. If you get it, please help everyone by getting the update.zip from your sd card before it installs. There are two ways of doing this and it in no way hurts your phone and you are at no risk of brick unlike what some of us have tried(Miami lol).

Method 1: When you get notification, download the update. When the phone turns off to restart and apply the update pull the battery. Pull out the sd card and mount it in your pc or even another microsd compatible phone you can mount. Then you should have an update.zip on the card.

Method 2: Download a logcat from the market. When you get notification of the update, open logcat. Let it start to download then just go into logcat and copy the download link from the log.

Then, post on here, or the irc room or PM someone and lets get this out so we can see if it helps at all with rooting. Thanks!
 
This isn't even for the hacking community, this is so that once someone does this, everyone else that is anxiously waiting can manually update.
 
mazz0310 said:
This isn't even for the hacking community, this is so that once someone does this, everyone else that is anxiously waiting can manually update.
Click to expand...

Actually, it could be possible that cracking open these update files may assist the dev community in hacking the bootloader to allow for custom roms.
 
TxAggieMichael said:
Actually, it could be possible that cracking open these update files may assist the dev community in hacking the bootloader to allow for custom roms.
Click to expand...

I know that, but I'm saying in addition to being for the hacking community there is also another purpose behind it (for those not interested in hacking)
 
this is said out of complete ignorance but couldn't the update.zip also be dissected to find what ever signing method Motorola uses so that custom roms could appear to be signed Motorola roms?
 
dB Zac said:
this is said out of complete ignorance but couldn't the update.zip also be dissected to find what ever signing method Motorola uses so that custom roms could appear to be signed Motorola roms?
Click to expand...

Hopefully, that's why it's important to get our hands on it. :)
 
Jw but could they do the same thing with the froyo update possibly to see about how its signed to sign future updates? Im not big into rooting was just curious though
 
ckochinsky125 said:
Jw but could they do the same thing with the froyo update possibly to see about how its signed to sign future updates? Im not big into rooting was just curious though
Click to expand...

Yeah but they won't see anything more in the Froyo update than they would see in this update.
 
Anyone have an idea about what I'm looking for in the logcat output or where on my phone the update is...I can pull it off and save it, but I gotta know where to find it...lol :D
 
scary alien said:
Anyone have an idea about what I'm looking for in the logcat output or where on my phone the update is...I can pull it off and save it, but I gotta know where to find it...lol :D
Click to expand...


It would have to be somewhere in the internal storage as it is not on the sdcard. As far as I know there is no way to access the internal storage to pull it off. :(

This is all that I can find. Perhaps someone can read it better than I can but it doesn't appear to have the file location included anywhere. Gobbly gook follows:

I appear to have read the entire file 19391229/0
I/cUs ( 1326): CusFile.verify: signature verification start
D/dalvikvm( 1326): GC freed 17651 objects / 1168216 bytes in 83ms
I/UpdateVerifier( 1326): Exempt: META-INF/MANIFEST.MF
I/UpdateVerifier( 1326): Exempt: META-INF/CERT.SF
I/UpdateVerifier( 1326): Exempt: META-INF/CERT.RSA
I/UpdateVerifier( 1326): Verified: META-INF/com/google/android/update-binary
I/UpdateVerifier( 1326): Verified: META-INF/com/google/android/updater-script
I/UpdateVerifier( 1326): Verified: bp.img
I/NotificationService( 1227): enqueueToast pkg=org.jtb.alogcat callback=android.app.ITransientNotification$Stub$Proxy@46397aa8 duration=1
D/dalvikvm(16670): GC freed 2986 objects / 1004864 bytes in 102ms
D/dalvikvm(16670): GC freed 2455 objects / 500192 bytes in 73ms
I/global (16670): Default buffer size used in BufferedWriter constructor. It would be better to be explicit if an 8k-char buffer is required.
W/InputManagerService( 1227): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@463c0748
D/dalvikvm(16670): GC freed 47 objects / 405648 bytes in 68ms
I/UpdateVerifier( 1326): Verified: cdrom.bin
V/VSuite ( 1347): [J-VST-DEBUG 119704747]onSignalStrengthChanged, msignalStrenth = SignalStrength: 99 -1 -90 -80 -7 -1 6 cdma
I/UpdateVerifier( 1326): Verified: device_tree.bin
I/UpdateVerifier( 1326): Verified: mbm.bin
I/UpdateVerifier( 1326):
 
krichek said:
It would have to be somewhere in the internal storage as it is not on the sdcard. As far as I know there is no way to access the internal storage to pull it off. :(

About the only line I could find in the log that even looks like the update is:

com.motorola.blur.service.blur.Actions.UPGRADE_DOWNLOAD_STATUS
V/cUs
Click to expand...

same here...lol

still looking through the logs...
 
It got two logcat files that I sent to gmail. The first shows looking for the update, but doesn't show the start of the download. The second is already well in to the download, so I might have missed capturing the URL... Should I battery pull and retry the update/download?
 
scary alien said:
It got two logcat files that I sent to gmail. The first shows looking for the update, but doesn't show the start of the download. The second is already well in to the download, so I might have missed capturing the URL... Should I battery pull and retry the update/download?
Click to expand...

My phone is sitting here with the battery pulled already.. Pretty sure the problem is once I restart it the update will install, unless anyone knows how to enter recovery so I can do a system wipe before it boots back up.
 
Someone needs to download the update & after it is finished they need to say update later when given the prompt, that way you have the file. Then use Astro (or some other file management app) to search in the internal storage to find it, then try to copy it out of there. You are looking for an 18.5 MB file with the likely name update.zip. Check /tmp first...
 
SiXiam said:
Someone needs to download the update & after it is finished they need to say update later when given the prompt, that way you have the file. Then use Astro (or some other file management app) to search in the internal storage to find it, then try to copy it out of there. You are looking for an 18.5 MB file with the likely name update.zip. Check /tmp first...
Click to expand...

Well, I found a reference in the logcat (apparently after the download) that looks like the size of the file:

D/WSBase ( 1304): doRequest(): upgrade/2/download_upgrade resp length: 19415120

Sure looks like 18.5MB to me...

But, I still can't find the file...
 
krichek said:
I had a suspicion they would download it to the internal memory. Makes sense I guess since I don't think it is easily accessible by us for now. :(
Click to expand...

You can copy files out of the internal memory on to the SD card. I just copied a ringtone out of internal on to my sd, but I'm not sure if you can do this with all files. Linux file permissions are extensive.
 
You must log in or register to reply here.
Back
Top Bottom