I've FXZ'd back to .902, successfully updated to. 905 via official OTA twice, but eveytime I boot into stocl recovery and try to update to the ICS leak via Apply Update from SD Card, it always fails to verify the signature or something like that. Of course I'm completely stock and unrooted.
I've been searching through all the ICS threads, but theres just to many different threads with pages and pages of replies. If someone could offer some insight it'd be greatly appreciated.
Thanks in advance.
I had the same issue
I found this on XDA:
Indeed there should be an option for that (turning off signature verification), but I WOULDN’T go there unless you’re absolutely, 100%, certain that the file you’re trying to flash is not corrupted (via downloading or something). Signature is intended to prevent exactly this kind of problems.
I did the same thing as you and was having the same issues. I downloaded a different file for ics and it is loading fine as I type.
Anyway you could give me the link you downloaded the ICS file from?? I've tried two different ones and same thing keeps happening /:
I had a issue when it tried to verify /system ended up being i had traces of CWM Recovery left over i had to delete before i could flash .2233
Sent from my DROID BIONIC using xda app-developers app
Related
I'm inviting all you guys shoot me down for the noob i am.
I've search and i have found, I've read but only partially understood.
the background:
-Nexus one on vodafone epf30
-Downgraded to erd79 using fastboot (via Terminal in Mac-osx).
-Rotted and installed Amon recovery with sucess.
-At this stage i tried to install a variety of different pre rooted roms
- upgraded to frf91 OTA after giving up on trying to root froyo
I basically just would Froyo 2.2 rooted on nexus one.
I've found a variety of different methods and techs but haven't had any success i can downgrade again and again but each attempt i reach the update.zip stage and simply get a varification failed message.it's likley ive missed something here?!
I'm on mac and I'm sure I'm not having the update.zip.zip issue. ive checked and double checked, (that same issue caught me out before on symbian).
Does anyone dhave a simple deffinitive soloution or can point me in the right direction/
im aware this post will cause a shower of "search you noob SCUM!" style posts.
cheers in advance
http://forum.xda-developers.com/showthread.php?t=712983
Read from:
"By Popular Demand (Credit to lox):
Update.zip to flash with custom recovery"
Download, update using AmonRa's recovery, reboot to bootloader, flash new radio from any Froyo ROM thread in Development, reboot, enjoy.
hi, thanks for your reply. I'm pretty sure i have tried this method. if i down grade to erd79 can i apply this from there or should i go up to ere27 ? and does this require amons recovery or can it be done from a standard recovery?
Sorry im a symbian migrant :-( this is all new and exciting
ok so i down graded again to erd79 then rooted and installed AMONs recovery
installation of update.zip fails with the verification failed, is there something about AMONs custom recovery that im missing should what could be the cause for the verification to fail. im pretty sad now.
maybe there is a way to flash pre rooted Froyo directly using super boot?
maybe i need to be up
You've already installed a custom recovery. Basically you are done the whole rooting process.
No more need to downgrade or anything of the sort. Now you just go into recovery and flash what you want, no other steps.
Now you should be able to flash any custom rom meant for unlocked users.
You may be trying to flash the official 2.2 rom, try looking for a 2.2 for root users. Or try flashing CyanogenMod 6.
Are you sure you have Amon's Recovery because my buddy though he had it and he didnt which is why he couldnt install a rooted froyo ROM. Try http://forum.xda-developers.com/showthread.php?t=702191
ok ill give that rom a shot though i think my main issue could be the fact im using mac os x the downloader in safari automatically unzips .zip files so maybe recompressing the zip is causing the varification to fail.
ill have a go when im home and at a faster net connection work is like 0.2 up and down makes me feel ill!
Oh ok. I have a MAC aswell but I use google chrome for my browser.
OMG! mods lock this down! no need for anything more to be added!
MAC = FAIL
Windows+win
all you have to do is download using anyother browser DONT USE SAFARI!
and success will be yours! rebooting now to pre rooted custom frf91 WOOP!
Hey OP,
Actually you can still use Safari as it does unzip the file automatically but it also downloads the zip file so you end up with both. At least my MAC does this. MAC's are great, Safari on the other hand is junk so don't blame the whole computer for the browsers fault.
A few weeks ago I rooted my X and ran the manual deodex method posted on the site. Phone ran great, I installed clockwork recovery and made a few backups. after installing a rom and not being able to get back into the recovery, I had to flash the phone with the 2.2 full SBF. This leads to my questions
1. After I SBF'd I was able to recover my applications and my data was all on the SD card. however I have a few applications that when run will close and give me an error message stating that the "application unexpectedly quit" I can duplicate the issue most when attempting to search the a forum through the XDA application. I am sure I failed to wipe data and cache before I recovered the stock OS, could this be the cause, any ideas?
2. I have re-rooted my phone but I have a question about deodexing again. I understand that motorola is in the early stages of working on an update to fix reported issues with 2.2, I also believe that they will use this opportunity to update the bootloader version. is there a way to disable the OTA updates? I am concerned about bricking my phone if an update is release and I am deodexed, what is the worst that could happen?
Sorry for the post, I am technically inclined but am still learning the android OS, any help is very much appreciated.
If you run a rom either aosp or blur you can avoid the ota that's end only way I know to avoid it
Sent from my DROIDX using XDA App
thanks for the response, I read a few places that clockwork recovery blocks OTA updates from installing, but I am having a hard time nailing down a definitive answer.
From what I understand Droid X SBF files do not wipe data like other phones. I recently had to SBF but kept getting stuck looping at the droid eye. I booted into recovery and did a factory reset and all worked out just fine. I know it's not your exact problem but it still might be worth it to try.
As for not getting OTA updates other than doing a custom ROM I can't help you there, sorry.
Just a quick background, I purchased my DS7 at staples and rooted it and installed CWM using the info found on the forums so I could connect to my ad-hoc tether. Last week I attempted to install the HC upgrade and got the mis-match message. I booted into CWM and started looping. In an effort to correct this I mistakenly wiped the memory (big mistake!). I found the instructions on flashing the stock ROM (turned out that it was TMO) and got the unit running again. I called Dell (I have posted in another thread on this) and they are to send a pickup. In the meantime I have found instructions on flashing the OEM stock wfi ROM and have done so. I, like many others, noticed that the service tag was wrong and edited PG23/line220 to reflect my correct tag ( note to posters of ROMs and those who would flash: before doing so write down all the information about your unit so you can make changes later if needed). I now have most everything back to pre-upgrade status, but Gingerbreak v1.2 will not root. When I attempt it the program runs but I get a message “Not sure what happened her. Either the exploit failed or the reboot failed. Please reboot manually and see if you have Superuser!” I reboot and nothing, no Superuser and no root access. Also, before I attempt the “unroot’ option is greyed out so I take it that the unit is not rooted nor can I see root files in file manager One thing I have not tried is the CWM un-install that was included in the stock ROM flash thread. Since I don’t see it and I boot into fastboot I am guessing that it is gone. Any suggestions or has anyone had this issue as well?
Another note, I too have the 338 version and no auto update yet. I am not real sure I want to update now. To those that have updated, can you connect to ad-hoc networks with out changing the WPA?
Big wall of text, if you're on 2.2.x reflash CWM 3.0 and flash Superuser.zip as a update.zip though it.
If you're on HC, flash CWM 4.0 and flash Superuser7.zip on it.
Superuser.zip will always work on 2.x roms.
Superuser7.zip will always work on 3.x roms.
If you try and run the wrong one it will just 'run' and give no error, it will simply not do anything, but it wont damage anything.
Thanks, you think cwm is still lurking and giving problems? So I need to reinstall cwm and use it to install the zip? Won't CWM interfere with the HC update?
alchrisr01 said:
Thanks, you think cwm is still lurking and giving problems? So I need to reinstall cwm and use it to install the zip? Won't CWM interfere with the HC update?
Click to expand...
Click to collapse
If you have CWM installed you won't get the update automatically no matter if you have a matching ROM or not... you must be FULLY stock... but I see no sense in waiting, TheManii has already posted the releases that are coming out... why not just flash the zip
Hello! I have been researching this for a friend and figured I would try good old XDA. Here is the problem, after a forum search only one post had this problem but with no solution.
It is a bone stock 7 inch galaxy tab. It is running froyo and is prompted to download the gingerbread update. After the download, it will boot and start to flash, approx 1/3 of the way, the patching stops, an exclamation point appears then the tab reboots back to Froyo as the update has failed.
Any idea what is causing this? I have booted it into recovery and wiped data/cache and even SD card for good measure. It always does the same thing.
I am savvy with working on Motorola droids, but samsung is new to me. I did reading and found out about Heimdal and Odin. I believe this must be something like RSDlite that I use but am uncertain.
Anyways, how can i get this update to go through? can I retrieve the file after it downloads, change it to "update.zip" and flash it in recovery? The only thing I can think of is having him download the 2.3.5 Stock + root file from this thread. and flashing this in Heimdal.
What seems to be the best possible action here. Thanks
in99flames said:
Hello! I have been researching this for a friend and figured I would try good old XDA. Here is the problem, after a forum search only one post had this problem but with no solution.
It is a bone stock 7 inch galaxy tab. It is running froyo and is prompted to download the gingerbread update. After the download, it will boot and start to flash, approx 1/3 of the way, the patching stops, an exclamation point appears then the tab reboots back to Froyo as the update has failed.
Any idea what is causing this? I have booted it into recovery and wiped data/cache and even SD card for good measure. It always does the same thing.
I am savvy with working on Motorola droids, but samsung is new to me. I did reading and found out about Heimdal and Odin. I believe this must be something like RSDlite that I use but am uncertain.
Anyways, how can i get this update to go through? can I retrieve the file after it downloads, change it to "update.zip" and flash it in recovery? The only thing I can think of is having him download the 2.3.5 Stock + root file from this thread. and flashing this in Heimdal.
What seems to be the best possible action here. Thanks
Click to expand...
Click to collapse
which model of the tab do you have?
It's been awhile since I did anything much with my phone and so I am a bit out of date on what is available these days, especially with the Bionic, I could use a little advice and some recommendations. I used to be into phone modding big "back in the day" with my DX but not so much anymore.
Firstly, I am not a nub and I spent a few hour's online reading before deciding to post anything so I am not trying to be spoon fed here, but I am a bit stuck here and I am not sure what to do. Anyway, I got the phone with 886 and rooted it, installed my stuff and have been using it since. Been having some issues with the phone (still do) so I decided to update it. I made backups via clockworkmod and did the forever root (where you edit with SQL editor) and ran the official update. The OTA said I would be getting 902 however after it installed I was on 893, so I assume I needed to be on 893 before I could go to 902, however when I try to go to 902 I get failed update.
I have tried two ways of updating.
1a. Updating to 902 from phone
2a. Updating from stock recovery using the 902 update file, named Blur_Version.5.5.893.XT875.Verizon.en.US.zip
1b. When updating from phone it downloads, "installs", phone reboots to "update failed".
2b. When installing update from stock recovery I get "package verification failed bla bla myverizon.apk".
So, I figured it was apps and such I either removed, froze, etc. I unfroze and restored any stock apps and still myverizon.apk failed. I read online about putting myverizon.apk in /system/apps however that did not work.
My goal is to keep my phone as is, I cannot really afford to reset it at this time. I feel what I need is the proper myverizon.apk file and someone with more knowledge than myself to tell me exactly what to do.
Any help is greatly appreciated and thank you in advance.
Go here and use Timmy10shoes files if needed...http://androidforums.com/bionic-all-things-root/480176-how-flash-5-5-893-5-9-902-rsdlite.html
Thank you but this does a full wipe, I am just trying to update to 902.
This will get you to 902 and Timmy10shoes file will prevent a wipe of the sd card.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A