Hey, So i was trying to root my motorola droid maybe 2 weeks ago but it didnt work, and i didnt really care enough to try again (i have a mac and it was a pain to find a windows computer). I thought everything would be fine, but for some reason when i tried to update my phone to 2.2 (i found the update.zip on androidcentral) it said that it failed, and for some reason when i restart holding down the X, it says:
Android system recover <2e>
Patched by SirPsychoS (0.00.3b)
is there a way to change that back to the regular one? or am i screwed hahaha
Also when i hit "allow update.zip installation' and then 'install /sdcard/update.zip (deprecated) i get this:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Installation aborded.
What do you guys think i should do? finish rooting it (can i have directions please ) or is there a way to get it back to how i got it? I think i alreayd tried to factory reset it
Thanks
Assuming you can boot into recovery, find your original ROM on the net, if available and re-flash with that to be un-rooted and back at square-one.
Could be the ROM you flashing now is not for your network provider, or you haven't successfully rooted.
I'm HTC myself so would use a goldcard (google it) to use a generic rom with my vodafone phone. Don't know if goldcards work with motorola.
hmm i cant seem to find it, could i just stick with what i have now and receive the 2.2 froyo update when it comes through OTA?
Depends how you rooted (or tried to root) if you flashed a rooted Rom in the root process it probably won't be updating from the official Motorola servers.
Sent from my HTC Desire using XDA App
I don't think i even flashed a rom, i tried that screenshot program (i cant remember the name of it, but you need root to use it) and it wouldnt work so i dont actually have root. I think that i tried to flash it with a rooted 2.1 rom but it failed. what do you guys suggest i do?
ok so i figured out that it was because my mac unzipped the file, but when i try to install it i get this:
Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("MTD:boot:25047
04:0b5ee101da4118aa026a32848f609fa4b05403e:2875
392:d104d2ev84a2d06600e786c0fb8174bfacb4079db6")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Ive tried like 4 different downloads and its just not working :S
Related
Okay here's my problem. My phone has been asking to update for a while so I restored to a recovery with the stock kernal and unrooted it. I go to install the update and I am getting an error. I click instal, my phone turns off like its suppose to, recovery mode then appears says there's been an error update failed.
Anyone know what I did/what I can do to fix this?
edit: heres exactly that it says:
ClockwordMod Recovery v3.0.0.5
Finding update package...
E:unknown volume for path [SDCARD:download/OTA_Vision_BellMobility_WWE_1_84_666_2-1_34_666_5_release_172473wagbpno61mgwg4k0.zip]
E:Can't mount SDCARD:download/OTA_Vision_BellMobility_WWE_1_84_666_2-1_34_666_5_release_172473wagbpno61mgwg4k0.zip
Also When I try to install zip from sdcard is says:
Installing: /sdcard/download/OTA_Vision_BellMobility_WWE_1_84_d666_2-1_34_666_5_release_172473wagbpno61mgwg4k0.zip]
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Hey I have this same problem! Where can I get a copy of the OTA update or something else? I also tried updating to cyanogenmod 7 and can't get it to work either
i had this problem with my sgs2 for there update, i unrooted went back to the stock like the phone was brand new , did you do the same?
No, I am not sure I want to go back to unrooted, the bacckup options just aren't as good. I guess I want the best of both worlds, to have htcsense and to be able to back it up completely. (It's really my dad's phone, I'm not so tied to htc sense)
First time trying to install a ROM other than the default on my AT&T Nexus S. Unlocked the boot loader. Installed Clockwork. Downloaded the NexusBeam4.01 and named the file update.zip. Copied it to the SD card, rebooted, told it to update from the zip file. I get the following:
-- Install /sdcard --
Finding update package....
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
e:signature verification failed
Installation aborted.
Being new, I was hoping someone could tell me where I went wrong. Nexus S, AT&T.
Thank you.
Mike.
Got it figured out. I had unlocked the bootloader, but not rooted. All better now. Sorry for the newbie intrusion.
Mike.
I keep getting an OTA notification, but when I try to install it, the update always fails. My Android version is currently 4.0.4. My phone is rooted and have the custom recovery installed. When I try to install the update, the phone reboots into recovery and always fails with the following details:
CWM-based recovery v5.5.0.4
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
What is this update? Should I just keep trying? Do I need to do something to make it work? Or should I just install the new leaked JB ROM?
MrGibbage said:
I keep getting an OTA notification, but when I try to install it, the update always fails. My Android version is currently 4.0.4. My phone is rooted and have the custom recovery installed. When I try to install the update, the phone reboots into recovery and always
Click to expand...
Click to collapse
I believe you can't be on a custom recovery and successfully install an OTA update on its own.
- ooofest
MrGibbage said:
I keep getting an OTA notification, but when I try to install it, the update always fails. My Android version is currently 4.0.4. My phone is rooted and have the custom recovery installed. When I try to install the update, the phone reboots into recovery and always fails with the following details:
CWM-based recovery v5.5.0.4
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
What is this update? Should I just keep trying? Do I need to do something to make it work? Or should I just install the new leaked JB ROM?
Click to expand...
Click to collapse
Any OTA update, you need to go back to pure stock rom, meaning no root, no custom rom, no cwm. Sooner or later you need to move on to Jelly Bean, so yeah, prepare yourself, do a full backup of your apps (not system apps), go back to stock then take the OTA. Second option, disabled the OTA notification for now and wait for JB custom rom build for official Jelly Been.
That all makes sense. Thanks, guys!
So I unrooted my Shield Tablet a while back without changing the stock recovery, and found out that whenever I try to install an OTA update it shows an error during instalation, rendering me unable to aquire the 2.2 and 2.2.1 updates. Already tried unrooting it, locking back the bootloader and so on. I can still sideload updates to the tablet but would like to gain back the convenience of OTA updates. Has anyone encountered similar issues? Could anyone help me fix this issue?
Saw the probable solution on another post.
mdecaminop said:
So I unrooted my Shield Tablet a while back without changing the stock recovery, and found out that whenever I try to install an OTA update it shows an error during instalation, rendering me unable to aquire the 2.2 and 2.2.1 updates. Already tried unrooting it, locking back the bootloader and so on. I can still sideload updates to the tablet but would like to gain back the convenience of OTA updates. Has anyone encountered similar issues? Could anyone help me fix this issue?
Click to expand...
Click to collapse
In these forums somewhere I read that the unroot was done using Super su's full unroot option. However it apparently left behind a few files that caused the OTA to fail. So what he did was to uninstall Supersu, reinstall Supersu and update the binary. Then use full unroot function... Maybe it will work for you if you have unrooted using SUpersu...
Unrooting, locking the bootloader, and flashing the stock recovery doesn't allow you to take OTA's.
There is THIS thread, providing OTA files that can be flashed in TWRP or CWM. And are official files from Nvidia.
You have to flash these every time there's an OTA, or just flash a full stock image through fastboot, and never root or flash a recovery.
I'm having similar issues. I was rooted with CMW recovery but unable to install OTA update. I unrooted, and did a factory reset of the OS.
I tried to install stock recovery 2.2.1 (found on another thread here) with adb sideload command with the following result:
"cannot read "update.zip" (I tried the original filename and changed it to update.zip. Neither worked.) To test adb, I installed Supersu via the same method.
Trying to install the OTA update I receive the following:
Invalid command argument
Finding update package...
E: unknown volume for path [@/cache/recovery/block.map]
E: Can't mount @/cache/recovery/block.map
Installation aborted
I do apologize if I've missed something. Some of the other threads I've been using to learn are many pages long. Any help is appreciated.
mycologik said:
I'm having similar issues. I was rooted with CMW recovery but unable to install OTA update. I unrooted, and did a factory reset of the OS.
I tried to install stock recovery 2.2.1 (found on another thread here) with adb sideload command with the following result:
"cannot read "update.zip" (I tried the original filename and changed it to update.zip. Neither worked.) To test adb, I installed Supersu via the same method.
Trying to install the OTA update I receive the following:
Invalid command argument
Finding update package...
E: unknown volume for path [@/cache/recovery/block.map]
E: Can't mount @/cache/recovery/block.map
Installation aborted
I do apologize if I've missed something. Some of the other threads I've been using to learn are many pages long. Any help is appreciated.
Click to expand...
Click to collapse
Well it seems my second hand tablet has been rooted as well ... I've got the exact same problem that yours ...
Is there a way to go back as out of the box ?
I downloaded the OTA update and whenever I install it, it gives me this..
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
/dev/block/platform/msm_sdcc.1/by-name/system has been remonted R/W; reflash device to reenable OTA updates
E:Failed to install /sideload/package.zip
E: Please take note of all the above lines for reports
Installation aborted​
I searched on google but I could only find solutions which include downloading the whole rom, is there another way to fix this? I'm scared that flashing the rom might wipe my data. I already tried downloading the update thru the internet but still gave me the same thing. I'm rooted, and have the stock recovery. Thank you
You can either flash the full ROM zip with the stock recovery, or flash the stock images with fastboot. Neither will wipe your data (unless you flash the userdata image).