[Q] Revived Droid Incredible - Re-update help - Android Software/Hacking General [Developers Only]

I tried to follow the instructions here: http://solo.dc3.com/dinc/ to apply the November update for my phone which is rooted.
I need some help, since it starts the update (00cb7fa66e35.OTA_IncredibleC_Verizon_WWE_3.26.605.1_3.21.605.1_release_sign renamed to update.zip) but then:
Code:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
I Had originally rooted my device running stock with unrevoked, then updated to Froyo. I now have the nag for the second 17.7mb Update, but I forgot how I installed and got past this; I do recall going through several instructions before finding ones that worked, so I guess I'm facing that once again.
Here are some device stats:
su v2.3-ef (2.3.2.1)
ClockWorkMod 3.0.0.8
-- ROM Manager 4.3.2.4
Android 2.2
Kernel 2.6.32.15-gb7b01d1
Baseband version 2.15.00.07.28
Build Number 3.21.605.1 CL231334 release-keys
PRI 1.28_002
PRL 52169
ERI 5
I'm back in this condition because I attempted to install wifi calling, but then my phone stopped booting.
Essentially my device is stock, except for having root enabled so I can use wifi tether, and of course some other dilly dallying that I do but I'm still trying to keep the device pretty close to root/stock as possible.
Any help would be appreciated in pointing me back to the right guides/files.
If you need more info please let me know, I had to restore to a very old backup (my bad for not making a recent one). Very much appreciate the help getting back to current updates.

Related

OTA Update failed

Hi,
I've got a magic from TIM but i'm leaving in belgium. I'm running MyHero 2.0.5
By two times, my handset requested me to reboot my phone for a 'system update'. Both attempt failed.
The phone reboots then an icon representing a package update then a a failure sign. The only way to get back the phone was to remove the battery.
My question:
Where can i find the package that android tries to install....is there a log somewhere where the failure is reported ?
Thanks
Ced
If you're running a custom rom and trying to install an OTA it isn't going to work. The OTA is only compatible with the stock OS. If you have root and manage to get an OTA to install then you will lose it. I'd say to just ignore the updates. If your phone is working the way you want it then I would leave it as is. If you want anything different then you'll need to flash something!

downgrade from ice cream sandwich??

is that possible to downgrade from ice cream sandwich?
i updated yesterday, and it is not really useful as before with many bugs.
i wanna change back to 2.3.X ..
what do you mean you upgraded?
tszkin622 said:
is that possible to downgrade from ice cream sandwich?
i upgraded yesterday, and it is not really useful as before with many bugs.
Click to expand...
Click to collapse
Upgrade as in flash a rom created by beezys?
Just go into recovery and do a restore
-Google
problem solved...
i downgraded it to 2.3.4 and get back to 2.3.6....
tszkin622 said:
problem solved...
i downgraded it to 2.3.4 and get back to 2.3.6....
Click to expand...
Click to collapse
=\ u took a long route there.. unless u didn't back up your 2.3.6 then I guess u did good
-Google
@iGoogleNexus i just updated ice cream sandwich. Not via the guy called beezys btw
however i want to downgrade! As i searched trough internet i couldnt find any answers besides your advice (which did not work for me). If you could help me i will be really appreciated. Please help me and my hopeless situation
Unroot your phone, then you'll be able to flash anything you want, even 2.3.3 no matter what rom you're currently using.
Good luck!
Great! Thank you so much however I don't know how to flash it :/ (n00b)! It would be perfect I'd you could explain it to me too! Thank much you sooooo much again!!!
I'm going to follow this thread closely.
Noob here too.
I have the bone stock NS, I9020T (not rooted) and got the OTA update of ICS 4.0.3. Like the OS but there are too many apps that are either buggy or simply don't work on ICS.
I downloaded the "Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader" rom from here on XDA, renamed it to "update.zip" and copied it to the phone. When into the bootloader, selected Recovery and then selected "apply update from /sdcard" and selected "update.zip"
When trying to install the "old" rom, I get this error:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: !less_than_int(1316544229. getprop("ro.build.date.utc"))
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I have looked all over the XDA site, Android Central and searched Google in general and can't find some simple step-by-step instructions to go back to Gingerbread.
I am SO looking forward to someone to tell me (us) what we're doing wrong and what I (we) need to do to get back to Gingerbread.
Thanks in advance from a Moderator from another (motorcycle) message board.
UPDATE: Installed fastboot and my bootloader is unlocked. Tried again to go back to GB using the steps above and I still get the same error.
good topic ... bump to top for expert advice
As a matter of fact it is not that easy my friend i also tried that method however it did not worked for me too, it gave me the same error. So as rafael said we gotta unroot our phones and we can flash it from there (but how? ) it would ve awesome if someone could help
Thanks
BRICKED!!!
OK i think i bricked my phone after unrooting it i finally got back to gingerbread but a gingerbread that is only capable of mounting and unmounting the storage after unrooting suprisingly clockworkmod recovery was gone! most of the tasks end unexpectedly such as acore, setupwizard and calendar. in android system recovery i have only 4 options: reboot the system, apply update from /sdcard and wipe various data. Besides my mac doesnt see the nexus s via ADB. I am wrecked what should i do?? Any pro tips??
First off, I want to reassure you that your phone is not "bricked". If it was bricked, it would be completely unusable, wouldn't turn on, show anything on the screen etc.
It sounds like you didn't wipe your data before installing the new ROM. This can lead to force closes and issues like what you are experiencing - I have done the same before.
It will be possible to recover your phone. You say in the Android recovery you have access to "Apply Update from SD Card" - simply use this option to flash another ROM, but this time make sure that you wipe the data beforehand. Bare in mind this will remove all personal data from your phone such as apps, contacts etc. However, this should be synced with your Google account and will re-download to your new ROM.
It would be good for another forum member to confirm this before you do anything - I don't have a Nexus S yet (getting it tomorrow ) but I am a developer for other Android handsets.
OK problem solved. After i unrooted somehow magically gingerbread 2.3.6 installed itself (or i did somehow i dont know) after the gingerbread installation i installed the clockwork mod recovery. I found the correct software (Ice Cream Sandwich for Nexus S) and installed it and the system is running silk smooth for now
Thank you everybody who helped me working this out really appriciate it
Here is what I did...
http://kishanrathod.blogspot.com/2011/12/downgrade-nexus-s-from-403-to-236.html
Downgrade no-root OTA
BartmanJax said:
I'm going to follow this thread closely.
Noob here too.
I have the bone stock NS, I9020T (not rooted) and got the OTA update of ICS 4.0.3. Like the OS but there are too many apps that are either buggy or simply don't work on ICS.
I downloaded the "Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader" rom from here on XDA, renamed it to "update.zip" and copied it to the phone. When into the bootloader, selected Recovery and then selected "apply update from /sdcard" and selected "update.zip"
When trying to install the "old" rom, I get this error:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: !less_than_int(1316544229. getprop("ro.build.date.utc"))
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I have looked all over the XDA site, Android Central and searched Google in general and can't find some simple step-by-step instructions to go back to Gingerbread.
I am SO looking forward to someone to tell me (us) what we're doing wrong and what I (we) need to do to get back to Gingerbread.
Thanks in advance from a Moderator from another (motorcycle) message board.
UPDATE: Installed fastboot and my bootloader is unlocked. Tried again to go back to GB using the steps above and I still get the same error.
Click to expand...
Click to collapse
I have the same problem, how to downgrade from ICS to GINGERBREAD using only non rooted system and OTA update?
I have ICS 4.0.3 if I would like to downgrade Nexus S to 2.3.6 how to i can without root ?
The message is the same
...
assert failed: !less_than_int(1316544229. getprop("ro.build.date.utc"))
E:Error in /tmp/sideload/package.zip
...
I think that is impossible (without rooting the phone) because probably this assertion
1316544229 < getprop("ro.build.date.utc")
is every time false with condition !(date build of gingerbrade < date build of ICS)

Unable to get 4.0.4 OTA Update

I have a Telus Nexus S running the following;
Baseband Version: i9020AUCKF1
Kernel Version: 2.6.35.7-gf5f63ef [email protected]#1
Build Number: GRK39F
I tried to do the OTA update, and it says there are no updates.
I followed this to try to force it to find an update;
Settings --> Applications -> ALL -> Google services Framework --> clear data
2) and do the check in code in the dialer - dial (no spaces) * # * # 2 4 3 2 5 4 6 # * # *
Doesn't seem to work.
Is there any way to install the update to 4.0.4 by flashing it on the phone?
if you know how to use fastboot then you can use these images corresponding to your phone model http://code.google.com/android/nexus/images.html#soju
and here is a guide to use fastboot to flash these images http://forum.xda-developers.com/showthread.php?t=1572307
or
you could use this http://forum.xda-developers.com/showpost.php?p=24379505&postcount=87
So I got it updated, following the instructions I found on another site! The package contained an update.zip which was the ICS build IMM76D
This package is for the AT&T/Telus/Roger/Fido/Bell versions of the Samsung (Google) Nexus S running Android 2.3.6 Gingerbread build GRK39F. It will update to Android 4.0.4 build IMM76D. If you have any other version of the phone or Android - IT WILL NOT WORK! Please stop now.
Also, proceed at your own risk.
1. Place the update.zip in the root directory of your MicroSD card.
2. With your Nexus S off press and hold the volume up button and power button until your phone turns on. It will enter a recovery screen.
3. Scroll down using the volume down button and select Recovery by pressing the power button.
4. In a couple of seconds you will see a yellow triangle on your screen, now press the power + volume up button to get to the file selection screen.
5. Choose to install update from SD card using the volume up/down to move the selection and press power to select.
6. It will take about 5 minutes to patch required files and reboot. Upon reboot, it will patch more files during first launch of Android 4.0.4.
It's all working, nice and smooth, love it!
I'm helping a friend with her phone and its not working and this thread helps a lot, but stuck on one part. She is on Android Version 2.3.4, Kernel Version 2.6.35.7-ge382d80. How do I get her phone updated to version 2.3.6 so i can then perform the 4.0.4 update for her?
mizzery85 said:
I'm helping a friend with her phone and its not working and this thread helps a lot, but stuck on one part. She is on Android Version 2.3.4, Kernel Version 2.6.35.7-ge382d80. How do I get her phone updated to version 2.3.6 so i can then perform the 4.0.4 update for her?
Click to expand...
Click to collapse
I followed this;
http://benheide.com/archives/229
Read the comments section, he talks about first upgrading to 2.3.6, then flashing the ICS update. Really straight forward, just make sure your phone is one of the above.
The above should work for AT&T/Telus/Roger/Fido/Bell Nexus S phones which are on 2.3.6 or follow the instructions to get to 2.3.6, then update to ICS 4.0.4.
I just tried to on my friends phone but it failed on the 2.4.6 update (the 17mb one).
Here is the output/error
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
<it gets about 30% and says the following>
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
mizzery85 said:
I just tried to on my friends phone but it failed on the 2.4.6 update (the 17mb one).
Here is the output/error
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
<it gets about 30% and says the following>
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
Have you tried to OTA update the phone to 2.3.6? Also the phone is I9020A?
The only OTA is the 4.0.4 and it fails every time it tries to update.
The phone is GT-I9020T.
mizzery85 said:
The only OTA is the 4.0.4 and it fails every time it tries to update.
The phone is GT-I9020T.
Click to expand...
Click to collapse
Yeah those instructions to update it will work for i9020A only
Download this ~17mb update;
http://android.clients.google.com/p...c0.signed-soju-GRK39F-from-GRJ22.7d114042.zip
Run that the same way you did earlier, it's the update for:
Model: Nexus i9020t/i9023
GRJ22 (2.3.4) TO GRK39F (2.3.6)
After you're done, then try the OTA once it's confirmed updated to 2.3.6.
She had to leave, but will be trying it tomorrow. Thanks for the help! Where are you finding these links? Ill be playing with my samsung galaxy s2 soon.
Hey there.
I tired that last package and it still failed. It gets farther, but fails after "verifying current system..."
I'm attaching a picture of it.
mizzery85 said:
Hey there.
I tired that last package and it still failed. It gets farther, but fails after "verifying current system..."
I'm attaching a picture of it.
Click to expand...
Click to collapse
I have the same problem. Does anyone has a solution?
xhellblazer said:
I have the same problem. Does anyone has a solution?
Click to expand...
Click to collapse
Root your phone and flash the update or preferably, something better than stock
Sent from my Nexus S using xda premium

[Q] Updates fail from 4.1.1 to 4.1.2

Hi,
A while back I rooted and unlocked using clockwork recovery and installed bigxie_magurTA_JRO03C-signed.zip
All was good for a while until the last month where I continually receive notification to update to 4.1.2
when I choose install, it attempts to reboot and on the recovery mode, I attempt to run the /sdcard/update.zip and it fails due to signature verification failure.
When I disable the signature verification, it states it cannot open the update file as if it is corrupt or not there,
I then tried to put on cyanogen mod, and when that loaded, I could not enter in my gmail profile info.
I then installed gapps on the next attempt to install cyanogen mod 10 and although more apps (google play app) was listed, still could not enter my gmail info anywhere
i have gone back to the 4.1.1 install I mentioned earlier, and it is running fine, but I am still prompted to update, which fails every single time.
Any suggestions on how to update this, I would be happy to go with cyanogen mod, but no idea really where to start.
I searched for the same error messages I was getting, and found a few posts but not solutions or recommendations,
Also, is this going to happen for every single update from this point on since rooting and unlocking the phone? i would prefer to give up more app control if going back to stock builds means not having to give up this much time for every update.
Thanks to anyone that can help.

[Q] Gingerbread or ICS?

Being my first smartphone, of course I wanted to fiddle with it, so the first thing I did want upgrade to ICS (Android 4.0.4, got the link from Samsung's site). All that rooting stuff kinda made me gun-shy, at first...but, after getting up the nerve, I got Odin, the pit and tar files, and fired for effect. However...during the process, I got some sort of device driver error from my laptop ("not successfully installed" or some such, which was rectified since), and after rooting attempt, my phone wouldn't get past the welcome screen. Did the unroot (many thanks to k0nane), and was back to stock...or so I thought. Baseband still shows T769UVMB1, which I was told by T-Mobile tech support was the latest update; "About Phone" shows Android 2.3.6, Kernel v.2.6.35.11, Gingerbread UVLB7. "Software Updates" show none available. I recall the Menu being different when I had 4.0.4, though, much better than what I have now. I tried the root process again, was successful, and DLed Superuser and Titanium Backup to get rid of a lot of clutter. Phone runs like a champ, and I love it, but there's always room for improvement. Oh, and the link that *was* on Samsung's site for the upgrade is now "Page Not Found".
So...am I running the latest software/OS/updates? If not, how can I get 4.0.4 back?
ElGorditoMagnifico said:
Being my first smartphone, of course I wanted to fiddle with it, so the first thing I did want upgrade to ICS (Android 4.0.4, got the link from Samsung's site). All that rooting stuff kinda made me gun-shy, at first...but, after getting up the nerve, I got Odin, the pit and tar files, and fired for effect. However...during the process, I got some sort of device driver error from my laptop ("not successfully installed" or some such, which was rectified since), and after rooting attempt, my phone wouldn't get past the welcome screen. Did the unroot (many thanks to k0nane), and was back to stock...or so I thought. Baseband still shows T769UVMB1, which I was told by T-Mobile tech support was the latest update; "About Phone" shows Android 2.3.6, Kernel v.2.6.35.11, Gingerbread UVLB7. "Software Updates" show none available. I recall the Menu being different when I had 4.0.4, though, much better than what I have now. I tried the root process again, was successful, and DLed Superuser and Titanium Backup to get rid of a lot of clutter. Phone runs like a champ, and I love it, but there's always room for improvement. Oh, and the link that *was* on Samsung's site for the upgrade is now "Page Not Found".
So...am I running the latest software/OS/updates? If not, how can I get 4.0.4 back?
Click to expand...
Click to collapse
Baseband T769UVMB1 is a radio, not the rom. Android 2.3.6 is Gingerbread, so no, it does not look like you are on ICS. Looks like you have Root. Do you have (if not you should get) Clockword Mod Recovery - once you have a recovery, you can do a complete Nandroid backup of your currently running rom; then you are free to try any of the custom roms and if there is a problem you can flash backwards to your old rom. So get a recovery and nandroid first, then flash away!
LBN1 said:
Baseband T769UVMB1 is a radio, not the rom. Android 2.3.6 is Gingerbread, so no, it does not look like you are on ICS. Looks like you have Root. Do you have (if not you should get) Clockword Mod Recovery - once you have a recovery, you can do a complete Nandroid backup of your currently running rom; then you are free to try any of the custom roms and if there is a problem you can flash backwards to your old rom. So get a recovery and nandroid first, then flash away!
Click to expand...
Click to collapse
Thanks, I'll bone up more on this stuff & see what happens.
Update: I installed Odin 3.07 and did a flash with *SGH-T769_TMB_T769UVLH5_T769TMBLH5_Original.zip*, but it failed to root. Did a reflash, the updates, and I'm back in business again. It's late; I'm going to bed...I'll work on rooting this later...
CWM Recovery weirded out
Well, I tried the 4.0.4 root (as per Beastmode's guide)...and when I downloaded the ClockWorkMod Recovery file, it showed up in WinZip as recovery.img & tried to open in Paint Shop Pro. PSP did *not* like it, and told me so, refusing to open, 'cuz it wasn't an image file. Weird.

Categories

Resources