Hey, I'm helping my friend install a new rom on his Droid X because the GB update messed his phone up. The Recovery version is 2.xxxx. I have Team Liquid's rom which won't install and it says
"E: failed to verify whole-file signature"
"E: signature verification failed"
"Installation aborted."
I thought maybe the download was bad so I downloaded OMGB and the same thing happens.
I can install roms without a problem on my Thunderbolt but I know nothing about this phone. It took me a bit just to figure out how to get into Recovery. No longer can I get into Recovery with Rom Manager or Quick Boot. If I tried to use those apps it just ends up rebooting the phone.
Any ideas why this is happening? Should I install the latest version of Recovery (CWM)? I downgraded the Recovery because I thought the new version was preventing Rom Manager and Quick Boot from booting into Recovery mode. Thanks in advance!!
Edit: I downloaded the Droid 2 Bootstrap app and now I managed to get into Recovery but installation failed again. It says
"Installing update..."
"assert failed: run_program("/tmp/check_kernel")"
"==0"
"E: Error in /sdcard/update.zip"
"(Status 7)"
"Installation aborted."
Any ideas?
Sbf and try from there
Sent from my DROIDX using XDA App
Sbf to. 602 and root using petes root tools, goolge will help since I can't post links
Sent from my DROIDX using XDA App
I'm a lil confused as what you mean when you say the GB update messed his phone up. If it was a OTA update that messed the phone up, then i would simply suggest getting rid of root and going back to Verizon because it could be an issue with that phone in itself.
Now if the GB update was caused by you guys trying to do certain things than follow directions of above poster StayFrosty777 (Cool name btw dude lol).
Also make sure that you download a custom rom that is on the build. I'm unsure of whether he actually has GB or if still on Froyo. If he is still on Froyo you will need to flash a Froyo rom, flashing a rom such as Liquid 3.0 which is based on GB, will not work on Froyo.
Related
Hey guys,
I really need some help here, I have a liquid s100 from fido. i rooted perfectly fine, download the rom manager and got the clockwork recovery on it downloaded the modaco froyo fido version of rom and flashed it all fine but its stuck on the boot screen since then, so i tried manual r/s and went into recovery and ive been trying all sorts of roms but its says cant verify the signature, im so frustrated please help. What am i doing wrong here, or how can i just return to the stock fido rom, please help.
This is the error:
Finding update package..
opening update package..
verifying update package..
E: signature verification failed.
installation aborted.
And this is the same error for pretty much every rom ive tried..
Please help anyone.
Sent from my GT-I9000M using XDA App
anyone??
pls.
How hard can "flash without signature check" be?
Koki1337 said:
How hard can "flash without signature check" be?
Click to expand...
Click to collapse
Please help man im just stuck dont know what to do. Pls.
Sent from my GT-I9000M using XDA App
Just put Liquid in Restore mode -> Volume UP + Camera + Power button and with Acer Tools flash it again with some BIN file. Its ease.
If you need more help- say
Never used Clockwork Recovery.
Install MalezRecovery and flash the ROM you want to flash without signature check.
Or flash a ROM which is signed like LCR-F- http://lcr-team.org/v1/index.php
Or just flash a new bin:
Here is a how to guide- http://android.modaco.com/content/a...rial-how-to-flash-bin-files-on-acer-liquid-e/
Here is a link full of bins- http://android.modaco.com/content/a...uid-liquid-e-all-roms-bin-extract-collection/
Here is my problem. I've been running Sonofskywalker3's 4.01 DL30 rom for a couple of days (loving it). I installed an app that broke my "back" button. I booted into recovery (the stock one) and did a full wipe reinstall. Then I was stuck in a boot loop.
I used Odin to flash a DL09 tar from here. Then I rooted using this method.
Every time I tried flashing a ROM I got an error about not having signed files. I installed ClockworkMod from here using the Red install listed near the bottom.
Now I can boot into ClockworkMod 2.5.0.4 (green) from ROM Manager and at one point I was able to manually boot into the RED ClockworkMod by manually holding down both volume buttons at boot up, applying the sdcard:update.zip in the stock recovery (2e).
I tried to flash the DL30 ROM again from ROM Manager (Sonofskywalker's ROM). I just get errors saying "Can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1) (Device or resource busy).
I thought it might be the SD Card so I tried a different SD Card and exact same error. I even got the same error with the RED ClockworkMod
Is there a way I can flash something with Odin and get it to work? Right now I'm in the phone (not bricked) but I don't have vibrate (really weird). Any help would be greatly appreciated. Thank you.
Current Phone Specs:
Hardware version: i500.04
Model Number: SCH-I500
Firmware version: 2.1-update1
Baseband Version: S:i500.04 V.DL09
Kernel version: 2.6.29
Build Number: SCH-I500.DL09
ROM Manager v3.0.0.7
Current Recovery: ClockworkMod 2.5.0.4
Odin (complete dl01) may be looking for you
Sent from my SCH-I500 using XDA App
Grimis said:
Odin (complete dl01) may be looking for you
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
+1 this is the fix for all soft bricks. so just keep that file on your desktop like i do.
Same here
I am having the same issue. I have flashed DL01 and still cannot flash CWMrecovery that worked before. My issue will never push out the update.zip. I remember my CWM was 2.5.1.0 (green) before 2.2. Anyone else have this issue? I think I'm doing something wrong since this is happening to two different Fascinates or 2.2 leak changes something deeper that our odin cannot correct.
*** I resolved my issue: my root did not take. After I rooted, I was able to flash from Rom Manager ***
Where do I get the DL01 file? Can someone post a link? I'll be home soon and I can try it out.
Sent from my SCH-I500 using XDA App
phantom27-ck said:
Where do I get the DL01 file? Can someone post a link? I'll be home soon and I can try it out.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=867648
Check out this thread for DI01
namoh21 said:
http://forum.xda-developers.com/showthread.php?t=867648
Check out this thread for DI01
Click to expand...
Click to collapse
Thank you. I had actually just found it and came back here to post it and found that you had beat me to it. I actually just flashed DJ05 and then had to re-root. I'm about to try rom manager again but I think it might have just been that I wasn't completely rooted (crossing fingers).
Now I'm getting this error:
E: failed to verify whole-files signature
E:signature verification failed
Installation aborted
I guess it's on to DI01...
Try flashing CWM through Odin now. When I got the same error I flashed the tar file via Odin and then it worked perfect
Sent from my SCH-I500 using XDA App
OK... Trying that now. I'm trying the RED one. Is that right?
Ok... It looks like it's working... (fingers crossed)
Well... It worked... mostly...
When I am in ROM Manager and it reboots it gets messed up and ends up at the stock recovery. Then I run sdcard update.zip and it goes to clockworkmod and starts flashing the new ROM. It starts off with an error saying that there are some missing bitmaps or something, but then it works.
Not perfect but close enough (I guess.)
That's pretty much the way it is working for all of us I think. I know JT addressed the missing bitmap error in one of the new CWM threads. Glad it worked!
Sent from my SCH-I500 using XDA App
im trying to manually install gingerbread on my x and this is what i get
when trying to install from recovery ,does anybody know what might be the problem ? is it a problem in my system/bin? or something with logwrapper idk--Install from sdcard...
Finding update package...
.Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("MTD:boot:41943
04:5d04862f4a45755349f29c1420019f30de0867f3:4194
304:da9dd717fdcb55a978608c15f18256c3c1734d")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
rooted? or were u rooted?
sent from the DX
If you are trying to install gb manually, it will not be labeled update.zip. you need to actually choose the zip from your SD card
I'm rooted but with no custom rom, I did install koushs bootstrap but then removed it using root explorer,, and after it says apply patch it says "system/bin/logwrapper with a bunch of numbers do you think there's an error there QUOTE=taterDX;12917845]rooted? or were u rooted?
sent from the DX[/QUOTE]
I don't get what you mean, there's no other option in recovery that lets you choose it just says install update. Zip QUOTE=Jmoney47;12923123]If you are trying to install gb manually, it will not be labeled update.zip. you need to actually choose the zip from your SD card[/QUOTE]
make sure u r rooted and installed rom manager, and boostrap from market. click reboot recovery in bootstrap, then go to rom manager and click flash cwm then reboot recovery. choose install zip then find the zip to install. that should do the trick. always make sure u backup first... no im not responsible for u destroying ur pbone or causing a catastrophic global event ;p hope this helps.
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
I'm trying to install the new one for stock users not the leaked version QUOTE=akaruna;12928708]make sure u r rooted and installed rom manager, and boostrap from market. click reboot recovery in bootstrap, then go to rom manager and click flash cwm then reboot recovery. choose install zip then find the zip to install. that should do the trick. always make sure u backup first... no im not responsible for u destroying ur pbone or causing a catastrophic global event ;p hope this helps.
Sent from my DROIDX using the XDA mobile application powered by Tapatalk[/QUOTE]
You are going to need to go back to full stock. 2.3.340. Logwrapper is part of bootstrap.
You will have to sbf back to stock then go into stock recovery and run update.zip.
Sent from my DROIDX using XDA App
sbf, root, and to pick a zip off the sd card, you need bootstrapper. no way around it (unless you rename)
If you are going to the ota gingerbread and not the one from tbh then you just need stock recovery. If you are using the tbh rooted gb then you will need to root and have droid 2 bootstrap not droid x bootstrap.
Sent from my DROIDX using XDA App
http://www.androidcentral.com/new-android-233-gingerbread-build-droid-x-reportedly-pushing-over-air
if ur using this method u need 2 b fully stocked thats how I did it
sent from the DX
I am in stock appreciate it anyways im just going to wait for the ota update. and if it doesn't work ill sbf
I am looking help from someone who knows TWRP. My phone accidentally did an update and now it just boots into TWRP v2.6.3.2. I am new to this stuff but through learnings I have pushed the stock firmware found on this site (I am in Canada and with Telus) using adb push through command prompt. However when i go to install, it fails. I have also tried Rogers and Bell. Nothing works. I don't understand what is wrong?
What I see is:
E: storage partition '//TWRP/BACKUPS/018bf7ce0f4c6fa0' not found
Installing '/sdcard/TelusD803T10B_00.zip
Checking for MD5 file ...
Skipping MD5 check: no MD5 file found.
Verifying zip signature ...
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/TelusD803T10B_00.zip
Can anyone please tell me what is going on here and what is wrong? I would really appreciate it. The phone is new and useless to me right now as is .... thank you
Did you did an OTA update while on custom ROM? have you tried other recovery? I had trouble flashing with TWRP too. Im using Philz Touch atm and it works great for me.
super114 said:
Did you did an OTA update while on custom ROM? have you tried other recovery? I had trouble flashing with TWRP too. Im using Philz Touch atm and it works great for me.
Click to expand...
Click to collapse
All I did was accept an update when prompted but didn't pay attention and when the phone rebooted it went into twrp. I had no idea what twrp was. through learning about it i got the stock roms off this website and pushed it on to the phone and tried to install but it just fails for some reason. i don't know what more i can do.
Follow the"back to stock threads" you cant accept ota's when rooted
Sent from my LG-D800 using Tapatalk
I would follow the above comment and follow the step by step guide how to get back to stock when you accidentally got OTA when rooted. Just follow the steps carefully and you'll be fine.Good luck
Have you tried this?
Just untick Zip File Signature when prompting to flash zip.That might work
New Update incoming!
See screenshot, just got it this minute.
https://www.dropbox.com/s/uc58qz137uwxu1l/Screenshot_2014-04-04_12-19-44.png
e: Does not install with cwm.
e2: flashing stock recovery did not help. installing starts, but quits with an error.
e3: error is: "system/framework/core.odex has unexpected contents"
e4: same error in cwm
Any ideas on how 2 fix?
cars10k said:
New Update incoming!
See screenshot, just got it this minute.
https://www.dropbox.com/s/uc58qz137uwxu1l/Screenshot_2014-04-04_12-19-44.png
e: Does not install with cwm.
e2: flashing stock recovery did not help. installing starts, but quits with an error.
e3: error is: "system/framework/core.odex has unexpected contents"
e4: same error in cwm
Any ideas on how 2 fix?
Click to expand...
Click to collapse
My guess is you'll need a stock rom to do this (do you have a deodexed one running atm ?), the error looks quiet obvious i think.
I didn't root this device yet and OTA 2.1 wasn't a problem.
mouhii said:
My guess is you'll need a stock rom to do this (do you have a deodexed one running atm ?), the error looks quiet obvious i think.
I didn't root this device yet and OTA 2.1 wasn't a problem.
Click to expand...
Click to collapse
Well i use stock rom, only thing i did was rooting but i don't think thats the cause. will try to revert anyway and see if the update works, thanks for the hint.
e: nope, not working.
Maybe try to flash the system.img from stock 4.4 and then proceed with OTA 2.1.
If you need I have the Advent VEGA stock 4.4 OTA file.
would be nice if you could provide a link
e: already got it, and it worked. thanks.