Related
All,
I got a notification of update this morning (June 29, 2011) on my HTC EVO 4G (rooted/with netarchy toast mod) but when I tried to apply the update I get:
assert failed: apply_patch_check ("/system/lib/modules/bcm4329.ko". "78fE:unknown command [c535f323ef3a5c8304b32f514c23ea458132b".]
E:unknown command [9"0]
E: Error in /cache/OTA-Supersonic_4.24.651.1-3.70.651.1_release404yzkft23eop520.zip (Status 7)
Installation aborted.
Android system recover is open and the prompts are:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Mounts
- Other
- Power off
What do I do next? How do I get this update? Thanks!
guidecca said:
All,
I got a notification of update this morning (June 29, 2011) on my HTC EVO 4G (rooted/with netarchy toast mod) but when I tried to apply the update I get:
assert failed: apply_patch_check ("/system/lib/modules/bcm4329.ko". "78fE:unknown command [c535f323ef3a5c8304b32f514c23ea458132b".]
E:unknown command [9"0]
E: Error in /cache/OTA-Supersonic_4.24.651.1-3.70.651.1_release404yzkft23eop520.zip (Status 7)
Installation aborted.
Android system recover is open and the prompts are:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Mounts
- Other
- Power off
What do I do next? How do I get this update? Thanks!
Click to expand...
Click to collapse
Anyone, anyone? Don't everyone rush down. There's room for everyone.
Is your recovery old (ie not Clockworkmod 3)
Have you tried to backup your apps with titanium and just starting all over with a new updated full rom?
Have you edited the filesystem to cause the update to say this? If you edit any of the filesystem, the update fails.
You need to download a new rom and just start all over it seems.
How are we to figure things out if you dont give any background?
Try unrooting and put a stock rom and then do an update. Hope that helps
Sent from my HTC EVO phone, shouldn't we all have one?
If you want to keep root, then you never take the update. Otherwise you will most likely lose root, and will have to wait until a Dev finds an exploit to reroot. If you want to just update the radio(s) then there are flashable updates in the Dev section that you can flash.
I Think I Did/Didn't
mattrb said:
Is your recovery old (ie not Clockworkmod 3)
Have you tried to backup your apps with titanium and just starting all over with a new updated full rom?
Have you edited the filesystem to cause the update to say this? If you edit any of the filesystem, the update fails.
You need to download a new rom and just start all over it seems.
How are we to figure things out if you dont give any background?
Click to expand...
Click to collapse
Not sure what clockworkmod I have. I could backup app with titanium and which "full rom" would you recommend? I have netarchy-toastmod-4.3.4-cfs-havs-less-nosbc-uni installed and in zip format. I rooted the phone and applied the toastmod so I modified the stock HTC EVO 4G file system. The next comment suggests unrooting the phone and starting over. Why so much work for a "smart" phone? Any specifics would be appreciated on how to proceed.
kf2m said:
If you want to keep root, then you never take the update. Otherwise you will most likely lose root, and will have to wait until a Dev finds an exploit to reroot. If you want to just update the radio(s) then there are flashable updates in the Dev section that you can flash.
Click to expand...
Click to collapse
Seems to be a rule never to take an update of the original after modifying any gadget. Maybe my rooted phone is better off/more advanced without the update but I haven't found anyone that has said it yet. Since the update failed I think I have root but I will check it. My wife's unrooted phone took the update easily.
guidecca said:
Seems to be a rule never to take an update of the original after modifying any gadget. Maybe my rooted phone is better off/more advanced without the update but I haven't found anyone that has said it yet. Since the update failed I think I have root but I will check it.
Click to expand...
Click to collapse
That is why you should read, read, read a little more and when you feel comfortable with doing something to your phone, stop and keep reading. This is posted over and over and over again in this forum. Never, ever take the OTA update. As soon as the update was available, Haux had the rooted version ready to be flashed within hours.
If you would like to keep the stock rom but update to the newest release you can download Rom Manager from the market and flash the newest stock rom. Quite easy and only takes a few clicks. Next time you see an update from sprint, just wait until Rom Manager gets a rooted rom of that release and go nuts. If you don't feel like dealing with Rom Manager you can manually flash the roms you find in this forum. Hope this helps.
This has worked rather well for me for the past few updates, including the most recent one:
forum.androidcentral.com/htc-evo-4g-rooting-roms-hacks/90582-guide-updating-rooted-gingerbread-without-flashing-new-rom-wiping-your-phone.html
Also, the error you see is likely due to you changing the Broadcom file in that location to enable Wifi-N speeds on your EVO. Is that something you remember doing? When installing updates, it needs the original unchanged version of "\system" files to be there to verify against, including this one.
I just went through the process, and got the same error before I remembered to change bcm4329.ko back to the original. Also, don't forget to unfreeze any bloatware if it is frozen, or it won't proceed past the verification process (as it changes "\system" files. Additionally, clearing the Davlik cache is always a good idea when updating.
I forgot to mention- If I remember correctly, the instructions are elaborated on in post #44 of that page.
tgruendler said:
That is why you should read, read, read a little more and when you feel comfortable with doing something to your phone, stop and keep reading. This is posted over and over and over again in this forum. Never, ever take the OTA update. As soon as the update was available, Haux had the rooted version ready to be flashed within hours.
Click to expand...
Click to collapse
You say a rooted version was ready to be flashed within hours.
This is what I read on Android Forums:
There is no exploit yet to allow unrevoked to root the new hboot(2.16). They will find it but how long is unknown.
You can apply the update by flashing the rooted rom and the updated radios found here: [ROM][STOCK] 4.24.651.1 - Odexed & De-Odexed - xda-developers and here: [ Radios ][ 6-3 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions - xda-developers
The only thing that would not happen by flashing those it that your hboot would not be upgraded which you don't want anyway so that you can retain root.
If Haux has an exploit would it work on netachy toastmod rooted EVO 4G?
guidecca said:
You say a rooted version was ready to be flashed within hours.
This is what I read on Android Forums:
There is no exploit yet to allow unrevoked to root the new hboot(2.16). They will find it but how long is unknown.
You can apply the update by flashing the rooted rom and the updated radios found here: [ROM][STOCK] 4.24.651.1 - Odexed & De-Odexed - xda-developers and here: [ Radios ][ 6-3 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions - xda-developers
The only thing that would not happen by flashing those it that your hboot would not be upgraded which you don't want anyway so that you can retain root.
If Haux has an exploit would it work on netachy toastmod rooted EVO 4G?
Click to expand...
Click to collapse
To be technical because I am a jerk, Hehe, you don't root the hboot. You unlock it via making it s off. You root the Rom by applying super user privileges from within. Hboot s off means you can easily flash different recovety images, radios, and any ruu considering you have supported radios. Tomatoes tomahtoes.
Sent from my PC36100 using XDA Premium App
Thanks
That is why you should read, read, read a little more and when you feel comfortable with doing something to your phone, stop and keep reading. This is posted over and over and over again in this forum. Never, ever take the OTA update. As soon as the update was available, Haux had the rooted version ready to be flashed within hours.
I just thought that maybe there was an exploit for gingerbread 2.3 (OTA) that someone had found within hours of Google's release. I wanted to definitely make sure there was or wasn't a way to update my phone. Thanks for your clarification on hboot, etc. Mattlock over on Android Forums has a good guide for rooting and he is good at step-by-step 'how to do it' and some explanation why for us newbies. My rooted phone works fine but my wife's stock phone with the update seems to get a lot of network failures. She has a lot apps and a stock SD card - she refuses to let me root her phone - superstitious kind.
There still seem to be a few people with problems so I thought I'd try to collect the steps and add a bit more info:
Notes
- So far this is only confirmed to work on full stock 2.2. For the leaked 2.3.3 you'll need to downgrade first; see this thread: http://forum.xda-developers.com/showthread.php?t=1180733&highlight=temp+root+downgrade
- The only confirmed root so far requires s-off BEFORE you follow this guide: http://forum.xda-developers.com/showthread.php?t=1206930
- I have had no reports of anyone doing this with anything other than 100% stock recovery, hboot, etc. Please let me know if you do try and what happens; I'll update this post.
- Following this procedure will not wipe your apps or your data.
Steps
1. Download http://android.clients.google.com/p...MOUS_2.15.531.3-1.22.531.8_release_197463.zip and rename to update.zip. Turn off 'Hide extensions for known file types' and make sure it's not update.zip.zip!
2. To verify your download didn't get corrupted, check its md5sum. It should match 3c7b0c2253f72f86b06d2c85b2c8c294 (you can get a dos tool to do this here: http://etree.org/md5com.html. Run cmd.exe and type md5sum.exe update.zip from a folder that contains both files) If your result doesn't match, download again.
3. Place update.zip on the root of your SD card, not in any folders.
4. Power down your phone.
5. Press and hold both VOLUME DOWN and POWER until you get a menu
6. You may not be able to navigate the menu yet. Wait for 10-15 seconds until it says it's checking some files, then automatically returns to the menu. Now you can use VOLUME UP/DOWN to choose menu options.
7. Choose Recovery from the menu by highlighting with VOLUME UP/DOWN and pressing POWER.
8. Wait until you get a picture of a phone with a red triangle and !
9. Press & hold VOLUME UP, wait one second, then also press POWER. You should get a menu with blue text.
10. You will see "E:Can't open /cache/recovery/command" at the bottom of the screen. This is OK!
11. Again with VOLUME UP/DOWN and POWER, select "Apply sdcard:update.zip"
12. From this point, just wait until it tells you to reboot and choose that menu option. If you get any errors here, consult the troubleshooting below.
13. There are several more automatic reboots and wait screens to go. Be patient!
Troubleshooting
- "E:failed to open /sdcard/update.zip (no such filler or directory)" - your file isn't named update.zip! Reboot your phone and use Astro or another file manager to make sure you've got the name right.
- "E:failed to seek in /sdcard/update.zip (Invalid argument)" - your download probably got corrupted! Check the md5sum again, redownload, and try again!
- "assertfailed: file_getprop("/system/build.prop", "ro.build.fingerprint") == tmobile/htc_vision/vision/vision:2.2/FRF91/277427:user/release-keys"" - you probably don't have the latest 2.2 that this update is designed to replace. You might be on 2.3.3 or possibly the original pre-wifi-calling 2.2. To fix this, downgrade from 2.3.3 or wait for the OTA to get the newer 2.2.
Has anyone noticed any bugs in the new OTA? Waiting for bug reports before I flash.
Will this work with clockworkmod recovery?
Sent from my T-Mobile G2 using XDA App
leech1980 said:
Will this work with clockworkmod recovery?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Well I would wait until someone makes a rooted version of this, I don't think you want to loose root over an update that is kind of outdated compared to Cyanogenmod.
Thank you for the link I'm updating my wife's phone tonight
Sent from my LG-P999 using Tapatalk
Cimer said:
Well I would wait until someone makes a rooted version of this, I don't think you want to loose root over an update that is kind of outdated compared to Cyanogenmod.
Click to expand...
Click to collapse
I don't mind losing root. I'm running stock 2.2 with s-off and clockworkmod. I just want the update to work.
The instructions above don't work for me. When I attempt an update in clockworkmod I get an error "(Status 7) installation aborted", something like that.
That's because it's not meant for clockworkmod yet. You can follow his instructions, loose root and be updated, or just wait a little until someone makes a rooted version and just flash it via clockworkmod.
Cimer said:
That's because it's not meant for clockworkmod yet. You can follow his instructions, loose root and be updated, or just wait a little until someone makes a rooted version and just flash it via clockworkmod.
Click to expand...
Click to collapse
Following his instructions, I get to clockworkmod recovery after step 7. I then choose update from .zip and get an error message.
attempted this with Indian HTC Desire Z and official htc update from another user with Canadian HTC Desire Z.
Getting the error: "Invalid Operation"
Why do I have an Indian HTC Desire Z ? Amazon told me it was American. I didn't know better.
How did I get the Canadian update ? A friend kept a copy of the file when he was updating his.
Ideas ?
I get the following output:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Copying fotaBoot to /data/system for customize reload...
Verifying current system...
assert failed:apply_patch_check("/system/bin/dnsmasq", "0ca7c8c9c5d267665622497df4c67dec65166adb", "1d717ab5c2bfc75d16bf6a9ec7936158cdc65aef")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Received the following error:
assertfailed: file_getprop("/system/build.prop", "ro.build.fingerprint") == tmobile/htc_vision/vision/vision:2.2/FRF91/277427:user/release-keys"
and a bunch of other gobbletygook...ending with
E: Error in /sdcard/update.zip
(status 7)
Installation aborted
OP needs to add "Status 7" error to OP.
You cant use clockworkmod recovery to update using the official OTA update.zip.
no - i don't have clockwork or any mods at all.. I think I screwed up the downgrade slightly, anyhow, what happened was shortly after posting this i got an OTA update that updated my system - but it didn't update it to 2.3.4 just to a newer 2.2 evidently. THEN I was able to use the update file and force it so now I have 2.3.4! (albeit still without my apps..)
wireless hot spot
can anyone tell me if wireless hotspot still works with this update?
All i know is some devs need to rip this stuff apart and get to cooking up some CM type features into it and it's my new daily driver
leech1980 said:
Will this work with clockworkmod recovery?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
It looks like you can't use a custom recovery to apply this update. It likely tries to verify the recovery image. You could open the update up and remove the file version verification, and various other things to prevent it from taking away your S-Off and SuperCID. You would then HAVE to apply it with a custom recovery with signature verification off.
A quick look in the firmware.zip portion of the update and you find this in an info file:
modelid: PC1010000
cidnum: T-MOB010
mainver: 2.15.531.3
hbootpreupdate:12
As well as hboot_7230_Vision_GEP_0.82.0008_110413.nb0
I don't know if that info file actually does anything, but I would still start with changing cidnum to 11111111.
The real meat of what is going on is in the Meta-inf folder, that is what handles copy files and performing updates. You can simply remove things you don't want updated. If modified correctly, you could then apply a superuser su.zip before rebooting and keep root with your update.
Unfortunately, I don't know enough to trust my own handywork. Maybe some people more familiar with the innards of Anroid could help out the Vision/G2 community?
The more I look at it, the more it seems like you could just delete the recovery.img (or replace it with clockworkrecovery) from the firmware.zip and delete the assert(apply_patch_check crap from the updater-script in META-INF\com\google\android and apply the modified update.zip with clockworkrecovery (signature verification off).
You could then apply an su.zip before rebooting and you should come back up with custom recovery at least, if not root also.
No one do this just yet. Surely someone from the N1 community can guide us as to how to chop up the update.zip
Installed successfully on my stock 2.2 G2. Thanks! Was getting tired of constantly checking my phone to see if I had gotten the OTA update yet!
Well just ran this on my roomie's stock phone. Fingers crossed.........
As soon as I posted this the phone booted up. So far so good. Thanks, I was beginning to think this phone was never going to get GB.
Drthunderer said:
can anyone tell me if wireless hotspot still works with this update?
Click to expand...
Click to collapse
WiFi hotspot is working fine for me after updating.
Ok... I have also used Z4root. I got the update, it failed. I unrooted with Z4root. Re-downloaded the update, it failed. I tried to reinstall the kindle and blockbuster app. Re-downloaded the update, it failed. I reset to factory. Re-downloaded the update, it failed. Downloaded root checker, ran root checker, it said that I am not rooted. Re-downloaded the update, it failed.
This is the Detailed Results I got from the Advanced Root Checker:
Root Access is not properly configured or was not granted.
Superuser.apk - is NOT installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your DROID2 device by Root Checker version 3.7 from joeykrim in the Android Market -
___________________________________________
Have I done something wrong??? I don`t understand why I can not get the update. Please help.
This process should un root and put you back on stock Froyo. This is a complete factory wipe, so if you're wanting to back anything up, do it before any of these following steps. Once complete, go to Settings > About Phone > Check for Updates and report back.
WARNING: Only run the first set of instructions, do not flash the Gingerbread leak, you can get the official after running RSDlite.
To get back to stock: http://www.mydroidworld.com/forums/...id-2-gingerbread-2-3-3-release-prerooted.html
1. Grab the SBF File
You must start the process with your phone running the official 2.3.20. If you have already upgraded to gingerbread grab this 2.3.20 sbf file .... Download
2. Grab RSDlite
You must use RSDLite to use the sbf file from step 1 .... RSDLite
3. Grab the Drivers Drivers ....Download now
4. Run RSDLite and sbf your phone back to 2.3.20
Didn't work
I was unable to get the OTA to work. I was rooted using OneClickRoot and unable to update like everyone else (FAILED). I tried to sideload from a post on another page, but that didn't work either (not even sure that was the correct file). So I followed the direction as mentioned above, SBFing to a stock 2.3.20, but only after I did a complete wipe of the phone. Now that I have SBFed I don't have any phone signal and cant get it to work with anything I have tried. I don't want to go crazy trying stuff and brick my phone. So at this point, how do I get my phone working again. Screw GB for now, I just need my phone to work. HELP!
It's pretty hard to brick a D2 unless you happen to flush it down the toilet. SBF again to 2.2, do NOT root. Go to the about phone menu and run the OTA update to GB. After that run the one click root for Droid 3.
working
I don't know why, but after re-installing (SBF) 2.3.20 the phone decided to stop working. I thought it could have been a bad SBF file, and it could have been. The step that seemed to work was wiping the phone after the install. Once I did this step, of course you have to set the phon up again, but it prompted me to "Activate" the phone. So I hit activate and the phone called Verzon and run a programming function. Once that completed the phone worked fine. I am currently downloading the OTA, so here's hoping!
I did actually get the sideload (update.zip) file to work before going back to 2.3.20 as mentioned above, but I still didn't have phone. At this point I was going to do a wipe but could not get the phone to enter recovery, I'm thinking there must be some other method that's different to get it there. If anyone know, that would be good info to have.
Still downloading.....
I believe if you dial *228 it will activate for you.
I am also unable to get the OTA GB update to work. It gets all the way to re-boot and about 1/3 of progress bar after accepting to install the 4.5.601.A955. Just like mentioned in one of these other posts. I have tried everything - uninstalling and reinstalling z4 root, deleting SU, Bootstrap recovery, root explorer etc. All of which were not done properly or in the right order. I have been working on this the last 2 days. Yesterday, I even called tech support at Verizon, they helped me do a factory reset, and when it failed again, offered to send me a new D2 because my phone is still under warranty and won't accept the update, so I took their offer.
But then I got nervous because my clockwork mod was still showing up on power up, so I finally figured out how to remove that. I have SBF'd at least a couple of times since I got clockwork removed and update still fails.
My memory is not to good, but I think I first rooted in late Dec 2010. It seems like the 2.3.2 OTA update came out in Jan or Feb 2011. I don't believe I had to unroot to get that update. My current System Version is 2.3.20 A955 - Android version 2.2, and that is what it goes to after doing the factory reset on the phone. The Verizon tech didn't act like it should have gone back to an earlier version.
I have only one other issue - a week ago the phone took a bath when I fell in the water. Dried it off quickly and the only thing wrong other than barely-noticeble water damage to the display, is that the power button now requires exactly 3 pushes every time to boot the display to the unlock screen.
Sorry for the long post. Here are my questions: I no longer have clockwork at power up, it boots like a normal out of the box D2, am I missing something? Will Verizon be able to tell that I had rooted my phone? Could the water and resulting power button issue be the cause of it not accepting the update? TIA
Im having a similar problem. I can get the ota update just fine, but it will install aboutt 1/3 of it and just stop and reboot. All i did was root. I unrooted and same thing happpens. Downloaded this thing like 6 times already and same thing each time. Although a long time ago i did uninstall nfs, blockbuster, and i think kindle but i cant remember...
Are you doing a full factory wipe back to 2.3.2 when you do this or are you just "wipe data/factory reset" in recovery? Because if you only do that in recovery you're just wiping data. There's another thread here with a .zip you can run in stock recovery, not clockwork. Rename to update.zip, put it on the main directory of SD, boot holding X and power, then press the volume buttons. Hit install update.zip.
On the D2 - I am doing Settings<Privacy<Factory Data Reset<Reset Phone< Confirm.
How do you get into stock recovery? Do I need to be rooted again?
I would imagine but I don't know. Boot up holding the X key and power, should bring you to a droid guy with a !. Hit the volume buttons, if you get a blue and red recovery menu, you're in. It's not going to ask you for superuser so it's worth a shot at least.
Thanks for your help idefiler6. I got into stock recovery, but when I did the update it also failed - some logwrapper error. I am now having difficulty getting back in to stock recovery.
I had deleted system/bin/hijack and renamed system/bin/logwrapper.zip to system/bin/logwrapper to remove or stop the clockwork mod from booting up, which did make clockwork go away using Root Explorer. I found a post here to do this droidxforums.com/forum/droid-x-help/22080-im-begging-help-please-help-3.html
Anyway, my new phone is supposed to get here Wed. So I guess I'll just take my chances of whether Verizon cares or figures out I had rooted my phone. Regardless, the power button failing to work properly, should qualify for warranty coverage.
Crossing my fingers for you.
im getting mine replaced under warranty due to it cannot install the update no matter, how many times we have wiped it with tech support.
I also was very lucky since I got my 2nd warranty phone right before the one year mark so it extened the phone i have now another 90 days.
Problems all around
I too am having the OTA update problem. Downloads fine and gets about 1/3 of the way before rebooting and giving me an update failed message.
Current Device info:
D2G
System Version: 2.4.330.A956
Android Version: 2.2
Unrooted using Z4Root
Current logwrapper from November 12, 2010. No hijack or recovery .bin files in place.
I have tried RSDlite 4.8 and 4.9 using two separate downloads of the 2.3.20.A955 SBF from the link provided in this thread. Motorola Drivers are up to date and no errors are showing up in my Device Manager on my W7 PC.
The error I get when flashing in RSD is;
critical error febe 0047
Any thoughts? I'd like to try Gingerbread but haven't had any luck no matter what I try.
When in Doubt Go Linux!
Here's how I fixed the problem. I'm not a big Windows guy and the issues I was having were frustrating me because I had to update drivers, download new versions, blah, blah, blah.
I found a solution that allowed me to use my Fedora OS and it took me 10 minutes, no hassles, no errors. The incredible thing is, it kept ALL of my data, apps and settings on the phone! I had to upgrade from 2.29 (the flash from below) to 2.30 OTA and then to Gingerbread OTA Awesome stuff.
Here are the steps provided by hwertz from modmymobile.
"Download sbf_flash (just goggle it)
Download DROID2WE_X6_2.4.29_FULL.sbf.zip" (google this too)
(You would download these with firefox, make sure Firefox saves in the directory "Download".)
Open a terminal (Applications->Terminal)
Plug in your phone via USB, turn it off. Flip open the keyboard and turn it on WHILE holding down the up arrow. You'll see this screen with blocky white text, like right away -- it doesn't even get to the Motorola logo."
-----
OK, so in the terminal, you will
type "cd Download"
(If you saved somewhere else, cd to there. For instance if you saved to "Desktop" you would "cd Desktop" instead.)
Type "gunzip sbf_flash.gz"
If this gives an error, it's ok, it means you already had "sbf_flash" instead of "sbf_flash.gz"
type in "chmod +x sbf_flash"
Type in "unzip DROID2WE_X6_2.4.29_FULL.sbf.zip"
Then type in "sudo ./sbf_flash DROID2WE_X6_2.4.29_FULL.sbf"
If you are running a "real" copy of Ubuntu this'll ask for your password. The LiveCD has no password so it won't.
That's it! It'll appear to do nothing for a few seconds while it loads the flash, then it'll start flashing your phone which takes 5 or 10 minutes.
Good luck!
Thank you hwertz and thank you Linux!
cbotd said:
I too am having the OTA update problem. Downloads fine and gets about 1/3 of the way before rebooting and giving me an update failed message.
Current Device info:
D2G
System Version: 2.4.330.A956
Android Version: 2.2
Unrooted using Z4Root
Current logwrapper from November 12, 2010. No hijack or recovery .bin files in place.
I have tried RSDlite 4.8 and 4.9 using two separate downloads of the 2.3.20.A955 SBF from the link provided in this thread. Motorola Drivers are up to date and no errors are showing up in my Device Manager on my W7 PC.
The error I get when flashing in RSD is;
critical error febe 0047
Any thoughts? I'd like to try Gingerbread but haven't had any luck no matter what I try.
Click to expand...
Click to collapse
I don't particularly know how much of a difference this is, but the D2G and the D2 are two different phones, everything I have posted is for the OG D2. Might want to check the threads in the D2G forum because the files you need to SBF must differ in some way. I could be wrong...
that would explain it
idefiler6 said:
I don't particularly know how much of a difference this is, but the D2G and the D2 are two different phones, everything I have posted is for the OG D2. Might want to check the threads in the D2G forum because the files you need to SBF must differ in some way. I could be wrong...
Click to expand...
Click to collapse
That makes sense. Either way, I'm happy as can be and in love with my phone all over again. GB is fast and smooth on my D2G and after gaining root access again last night all my SU apps are back in working order.
Droid 2 updated
I had to revert back to stock 2.3.20 using the RSDLite flashing method, I let it do its thing, then performed a factory reset.
Powered the phone on, activated it, then just downloaded the OTA update over wi-fi to make it faster, installed like a charm, then ran the rooting utility.
Phone is rooted, deBloated, and rockin steady already.
Gotta say, I love my D2 again.
A955 & A957 Gingerbread sbf
On September 15th an official Gingerbread sbf was released from Motorola for the Droid 2 (not the Global). Here are the exact file names in case anyone has access:
A955:
1FF-p2a_droid2_r2d2_cdma_droid2_r2d2-user-2.3.3-4.5.1_57_DR2-32-110726-release-keyssigned-Verizon-US.sbf.gz
A957 (R2D2):
1FF-p2a_droid2_cdma_droid2-user-2.3.3-4.5.1_57_DR2-31-110719-release-keyssigned-Verizon-US.sbf.gz
I just recently performed an "Over the air" update on my Motorola Atrix in hopes of upgrading to 2.3.
The 200mb file downloaded so I selected "install".
I walked away and then came back to the following error screen:
www [DOT] hardreset.eu/images/nexus_one_android_hard_reset_3 [DOT] jpg
Upon resetting the handset it appears that not only did I experience an error during the update, but now I also will have to re-download the entire file.
Can anyone please advise if there is anyway to manually install 2.3? Surely it's still on the phone somewhere.
**Update:**
I tried downloading the file again but this time backed it up just incase.
It failed a second time so I tried renaming it and doing a manual update.
I received the following errors:
Verifying current system...
assert failed: apply_patch_check("/system/app/MagicSmokeWallpapers.apk", "9870b02dba63f6f0047e4d104329cf4c1d0a48a5", "9870b02dba63f6f0047e4d104329cf4c1d0a48a5", "94389fda652df9e0eaaddf25bbbac0b0dececa1c")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted...
Click to expand...
Click to collapse
I hope someone can shed some light on this!
humanix said:
**Update:**
I tried downloading the file again but this time backed it up just incase.
It failed a second time so I tried renaming it and doing a manual update.
I received the following errors:
I hope someone can shed some light on this!
Click to expand...
Click to collapse
Is the the Telstra over the air update? (as I just did mine yesterday)
It basically means that the update is doing a check to make sure certain files are still in place - in other words somehow or someone has deleted that .apk (is your phone rooted?!) and since the update cannot find it it aborts the process.
I ended up just re-flashing with RSDLite back to stock as I had exactly the same drama (I had removed helpcentre.apk), downloaded the update yet again (third time lucky...) and it worked perfectly.
I also did a full factory reset as well as formatted my internal SD card prior to updating.
Hope this helps
the key question is, have you done any modding to your phone? webtop hack, rooting, anything that would change system files?
geekygrl said:
Is the the Telstra over the air update? (as I just did mine yesterday)
It basically means that the update is doing a check to make sure certain files are still in place - in other words somehow or someone has deleted that .apk (is your phone rooted?!) and since the update cannot find it it aborts the process.
I ended up just re-flashing with RSDLite back to stock as I had exactly the same drama (I had removed helpcentre.apk), downloaded the update yet again (third time lucky...) and it worked perfectly.
I also did a full factory reset as well as formatted my internal SD card prior to updating.
Hope this helps
Click to expand...
Click to collapse
Yes, it's a rooted Telstra Atrix.
I did a re-flash using RSDlite and it did the trick. Thanks!
I Have a tf101 with first the ics upgrade. I recently got notice of the ota update. I ran OTA Rootkeeper and then ran the update. It bombed after reboot with the downed robot. After that would only boot into cwm, unless i cold boot. Even then the update is not applied. How do ii fix this without starting from scratch with a new or factory rom? If i have to restore factory, where/how do i do it Assn how do i then get my phone back to its current state?
Thanks all
Sent from rmy SAMSUNG-SGH-I717 using XDA
Go here. http://forum.xda-developers.com/showthread.php?t=1530337
ssl123 said:
Go here. http://forum.xda-developers.com/showthread.php?t=1530337
Click to expand...
Click to collapse
Thanks for the link, but it's not really helping me.
Firstly, it says nothing about the OTA update and how to address installing it on a rooted system.
Second, that thread has 23 pages and there seem to be a LOT of questions about the integrity of the process they have there.
I would figure that MANY people are in my situation and that there would be a more straightforward answer.
Why are you trying to get update with CWM.?
At this point, this thing is so messed up I want to toss it out the window! I have tried so many fixes! Nothing is working like it should. What is the best way to restore it back to factory...even if it means going pre-ICS and going through the upgrades? I just want the hours of time i'm spending on this to end.
Wait. You had root + CWM with stock 9.2.1.11 and you installed OTA update?
What version of CWM do you have?
Try this thread, I did it and it worked no bother, had to go back to Roach2010 CWM 3.2.0.1 first though --- http://forum.xda-developers.com/showthread.php?t=1545965
Get an Assert Failed error: apply_patch_check (long string of numbers)
E:Error in /sdcard/patch-edited.zip
(status 7)
Installation aborted