I am trying to flash my HTC One M7. I bought this device from T-Mobile.
I am using ClockworkMod Recovery v6.0.4.8 (recovery-clockwork-6.0.4.8-m7.img). However, whenever I try to flash anything, it give me an error. I am using Cyanogenmod snapshot build (cm-11-20141112-SNAPSHOT-M12-m7.zip). Aso tried latest nightly build.
Steps I am following:
Wipe data/factory reset -> Yes - wipe all user data
install zip -> install from sdcard -> select the zip file
Log:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I get same error whenever I try to flash anything. Either it being UPDATE-SuperSU-v2.zip or GAAPPS. I have also tried TWRP (twrp-2.8.6.0-m7.img) still same error. Right now, except recovery, hboot and fastboot nothing else is working. When I try to boot the devices, it shows the initial HTC boot screen and gets stuck there.
I am following the instructions from here: wiki.cyanogenmod.org/w/Install_CM_for_m7
What's might be reason for it or where am I going wrong?
Use a different rom. Or a more updated one.
zelendel said:
Use a different rom. Or a more updated one.
Click to expand...
Click to collapse
Found the issue. It was due to safari auto-unzip file after download. I was making a zip of the file again.
I used chrome to download the file and voila it worked perfectly.
Related
hi there!
i just flashed the official rom to my htc hero to get the latest radio.
T-Mobile DE
RUU_Hero_T-Mobile_DE_2.73.111.26_release_signed_NoDriver.exe
from here: showthread.php?t=559622
now im trying to flash the latest villian rom 12.
if i boot the phone via home-and-power into recovery mode i just get the orange/white warning triangle. if i hold home-and-power again i have three options: reboot the system, apply the update, and wipe data/factory reset. if i try to flash the rom i just get
e: cant't open /cache/recovery/command
-- install from sd card
...
e: no signature (785 files)
e: verification failed
installation aborted.
im trying to flash via the bootloader (back-and-power) and access the phone via fastboot my device will be recognized but i can load any recovery rom.
i entered:
"fastboot-windows boot recovery-RA-heroc-v1.5.2.img"
i also tried the latest recovery rom from here: showthread.php?t=561124... and others, that i found on different sites and threads.
this is the message i get:
"downloading boot.img ... FAILED (remote: not allow)
i also tried to flashing the recovery rom via flashrec.
these are the versions i used:
flashrec-1.1.2-20090909
flashrec-1.1.3-20091107-2
flashrec-20090815
but i cant backup and therefore flash a recovery-rom.
so are all my hopes to flash a custom rom to my phone gone because i flashed the official update or is there any way to maybe downgrade again?
im new to the rom scene, any help would be much appreciated.
cheers.
For now you are essentially up the creek without a paddle.
I'm not aware of a way to reverse this issue
Goes to show you should never flash anything that comes from HTC...
http://villainrom.co.uk/viewtopic.php?f=43&t=28 explains why this shouldn't be done. Not much help though
Mod. edit: not dev related, moved to q&a
gl though
Hi guys,
I have unlocked my bootloader a few days ago, and also installed the CWM recovery, which I used to install the ATT 2.3.4 ROM (I own an International Atrix), and it was working flawlessly. Being annoyed by that bunch of bloatware, I decided to install the Alien-ROM, so I wiped data with fastboot -w, and entered CWM to erase the cache partition/dalvik cache and install Alien. The problem is, when I tried to install the .zip package, CWM threw at me "Installation Aborted", with no error message whatsoever, just before "Beginning Installation". At first I thought my .zip was corrupted, so I re-downloaded it and tried again, but got the same error.
Being unable to install the AlienROM, I fastbooted the ORFR ROM (surely a lot cleaner than ATT's) and installed the ROM manager app, and through it, updated my CWM to the latest version. And then there I was trying to install the .zip again, with no success. As a last effort, I uninstalled manually the install-recovery.sh file and the recovery partition, reinstalled Tenfar's CWM, but fell into the same error: "Installation Aborted".
Does someone have a clue of that is happening??
Thanks in advance.
Rom manager recovery does not work always.what I suggest is use tenfar recovery and then put alien zip on your ext.SD card and use tenfar recovery --- choose zip from SD card--- browse and select alien.zip and flash through it.
Hope this helps.
Well, I tried to install Tenfar's CWM, as I said at the end of my first post. I recently installed a new CWM-based recovery, and it also failed to install any .zip. Could it be because I'm using ORFR ROM? I've noticed the misbehaving os CWM when I uninstalled ATTs ROM...
Install rom racer's recovery.
I voided my warranty.
Use this link: romracer's custom CWM
Let us know if this helps
pedrohz said:
Hi guys,
I have unlocked my bootloader a few days ago, and also installed the CWM recovery, which I used to install the ATT 2.3.4 ROM (I own an International Atrix), and it was working flawlessly. Being annoyed by that bunch of bloatware, I decided to install the Alien-ROM, so I wiped data with fastboot -w, and entered CWM to erase the cache partition/dalvik cache and install Alien. The problem is, when I tried to install the .zip package, CWM threw at me "Installation Aborted", with no error message whatsoever, just before "Beginning Installation". At first I thought my .zip was corrupted, so I re-downloaded it and tried again, but got the same error.
Being unable to install the AlienROM, I fastbooted the ORFR ROM (surely a lot cleaner than ATT's) and installed the ROM manager app, and through it, updated my CWM to the latest version. And then there I was trying to install the .zip again, with no success. As a last effort, I uninstalled manually the install-recovery.sh file and the recovery partition, reinstalled Tenfar's CWM, but fell into the same error: "Installation Aborted".
Does someone have a clue of that is happening??
Thanks in advance.
Click to expand...
Click to collapse
May be you want to try installing the CWM from here... http://forum.xda-developers.com/showthread.php?t=1204500
This should most likely help you fixing the issue you are facing.
Good Luck.
Cheers!!!
Just tried the recovery mentioned above by you all... and nothing, I keep getting the same error -> "Installation aborted", right after "Beggining installation" (or something like that)
Any clues?
pedrohz said:
Just tried the recovery mentioned above by you all... and nothing, I keep getting the same error -> "Installation aborted", right after "Beggining installation" (or something like that)
Any clues?
Click to expand...
Click to collapse
How are you installing RomRacer's CWM? Flashing the .zip or via fastboot?
Sent from my MB860 using XDA Premium App
I've installed it through fastboot, as it's the only way I can do it... my problem resides solely on the fact that I can't install any .zip through it, I keep getting "Installation aborted", no matter what I try to install (Kernels/ROMs/etc)
Pedrohz... Are you using a Mac? If so do you have it set to unzip after downloading? Then are you re-zipping the file before you try to install? If so turn off the unzip feature. Just a thought... Hope it helps
Similar Issue, can't boot into anything :/ if you can help, read below :S
Ok, so I backed up using Oringinal CWM, and it said all OK. After this, I restored the backup, just to check all was working. I got the error error formatting /system. Rebooting, I found that my phone wouldn't boot. Thinking the only way out was to flash a new ROM, I flashed the new boot.img from evals Orange France 2.3.4 firmware, so that I would have the ram fix. After this, I wiped all the caches and the user data, and tried to install the ROM.
SAME FRIGGEN ERROR. no error code, just installation aborted.
Finally, I tried AGAIN with romracers cwm, but same error. Restoring from backup now gives the error - "Unable to flash new boot.img" or something along those lines.
If anyone cares, heres what my phones running
Firmware = Orange UK 4.4.20 (Android 2.2.2)
SBF= Bell_ihop (the international bootloader unlock sbf)
State= Won't boot past the big red M in the centre of the screen.
Hey guys, I rooted my device with the CF-KG2 kernal and am trying to use Rom Manager with Clockwork Mod 4.0.1.5. to install Cyanogen mod.
I can't get into CWM recovery for anything after installing without getting:
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
I can't find a solution to this on google or anywhere on this forum.
I also tried manually wiping my data/cache and installing the cyanogen nightly 26 with the CWM 4.0 included with CF kernal. It installs fine but won't boot past the samsung logo, so I had to restore.
Any help is appreciated!
Do a fresh download of a cm7 nightly.
Put it into your internal sd card.
Boot into cwm recovery
Wipe data/cache/dalvik
Flash cm7 zip
If you get stuck at the screen flash the zip again from recovery and it should boot.
Also, don't flash it via flash update, do it via flash zip.
Sent from my GT-I9100 using XDA Premium App
Thanks a ton. Believe it or not just installing the zip twice actually installed cyanogen perfectly. Amazing.
Canadianreaper said:
Thanks a ton. Believe it or not just installing the zip twice actually installed cyanogen perfectly. Amazing.
Click to expand...
Click to collapse
It's weird, seems to be due to custom versions of cwm recovery in most kernels, the other way todo it is to flash codeworx's cwm kernel then cm7, which seems to make it work with one flash of cm, but glad to hear you got it going.
Sent from my GT-I9100 using XDA Premium App
Same Here
Canadianreaper said:
Hey guys, I rooted my device with the CF-KG2 kernal and am trying to use Rom Manager with Clockwork Mod 4.0.1.5. to install Cyanogen mod.
I can't get into CWM recovery for anything after installing without getting:
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
I can't find a solution to this on google or anywhere on this forum.
I also tried manually wiping my data/cache and installing the cyanogen nightly 26 with the CWM 4.0 included with CF kernal. It installs fine but won't boot past the samsung logo, so I had to restore.
Any help is appreciated!
Click to expand...
Click to collapse
I also have the same problem, errors when trying to boot CWM recovery. Did not allow me to back up anything. and now my phone is stuck on the Galaxy S 2 boot screen and keeps on looping. I think I was using lightning ROM previously. What is the next thing I should do to make the phone work again.
Once the phone works, how do I get CM7 on it? Thanks so much. I am a new user and am not really familiar with the process.
gtizon said:
I also have the same problem, errors when trying to boot CWM recovery. Did not allow me to back up anything. and now my phone is stuck on the Galaxy S 2 boot screen and keeps on looping. I think I was using lightning ROM previously. What is the next thing I should do to make the phone work again.
Once the phone works, how do I get CM7 on it? Thanks so much. I am a new user and am not really familiar with the process.
Click to expand...
Click to collapse
Pull the battery and boot to cwm again. Wipe data/factory reset, wipe cache and flash cm7 (provided u put it on ur sd card).
If not, flash a stock rom, let boot and place latest cm7 .zip on ur ad card. Flash a kernel with cwm and flash cm7 .
I also have this problem. Also I can't back up my current rom, because it gives the same message as in First post. And I want to flash MIUI -rom. What to do?
Any solutions to this? I rooted using Zedomax's Method. all went smoothly. When I went into Rom Manager to backup, it said I had to flash CWM, I said ok. Now I get the same error as the OG. Don't know if the recovery worked prior to going into ROM Manager. I'm thinking of running the Zedomax's Method again to see if it reinstalls a workable CWM.
Hi everybody,
I've got an error when trying to flash my legend, or even enter to the recovery.
Here you got my specifications, in order to give you an idea:
S-off
HBOOT-1.00.0000
RADIO 7.13.35.05
I have an OTA 2.2 update, from Vodafone
I've rooted the device with "unlock root" some weeks ago.
ROM MAnager 5.0.0.6 with successfully flashed ClockworkMod Recovery: 5.0.2.0
The problems:
When I try to boot into recovery (for example, when in ROM MAnager I try to backup my ROM, or install a ROM from SD card), I get this message:
" E:can't open cache/recovery/command "
Then appear 4 options (blue colour): reboot / apply sdcard: update.zip / wipe data factory reset / wipe cachee partition. The 2 wipes work OK, the reboot also, but when I select "apply sdcard: update.zip" I get next message:
" Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted. "
When I try to open bootloader, I get this message (it appears but disappears 1 second later):
" SD checking
Loading legediag.zip
No image
Loading legediag.nbh
No image or wrong image
SD checking
Loading legediag.zip
No image
Loading legediag.nbh
No image or wrong image "
I get also an error message in ROM Manager when I do "Fixing Permissions". First I got a Superuser window "SuperManager has been granted Superuser permissions" but then a ROM MAnager window "An error occured while attemting to run privileged commans!".
I've tryed uninstalling and reinstalling ROM Manager, Factory reset, everything, except Wipe Dalvic (not sure about what it does).
I'm not sure what's not working. Is it the recovery or ClockworkMod ?? Is the HBOOT-1.00.0000 the problem ? Is a disfunction of the SD Card (i've not tryed another card...).
Not sure if it could be associated to the same problem but now when I plug the phone to the PC the phone don't ask me if I want only charging mode or USB drive, even if I fix the behaviour (ask always or USB drive default). Not sure if it's related or not.
So, I'm a bit lost. Anyone has any idea ??
Hi, I only having s-on, I can't flash custom recovery, so have never seen how it really works, but what your describing is your stock recovery hasn't hasn't been replaced with custom recovery (clockwork mod recovery) and is still looking for update.zip in the root folder of your SD card.
Maybe look for an update.zip in the xda forums and put it in the root folder and see if that helps.
Found this for you
http://forum.xda-developers.com/showthread.php?t=1290841
Sent from my HTC Legend using XDA App
escombralls said:
I've rooted the device with "unlock root" some weeks ago.
Click to expand...
Click to collapse
Hi escombralls,
i think, you are the first who used the "unlock root"-tool wihtout boot-problems after that.
Maybe, this tool nevertheless did not work correct. All other legend users had no success with this tool.
You should use a guide from this forum for rooting ...
if you are in the system recovery and the top part say...
Android system recovery <3e>
you cant use the fake flash...
you can find guides where everyone uses with no problem to properly root your legend from the forum.
than you'll notice after the process (downgrade to 2.1 step) when you go to recovery you'll notice the top part of this bunch of blue words say...
Android system recovery <2e>
than you can use the fake flash...
head here
http://forum.xda-developers.com/showthread.php?t=969076
for the fake flash and follow Blay0's simple rename copy instrutions...
with this fake flash (CWM) you can start flashing other rom and also partition your card (remember to backup important stuff before you do anything)...
good luck
OK, thanks for your inputs.
First of all I will try with another update.zip file.
If the problem persists, I will follow one of the guides for rooting...
I will keep you informed.
Okay, so this is what happened:
1) I received the OTA update and everything went fine with upgrading the my T-mobile Springboard tab to ICS 4.0.3
2) I then got brave and went ahead with rooting and installing SU using the technique described in "Root Stock T-Mobile Springboard" by xdajunkman. That worked fine and I was able to get CWM recovery installed.
3) I then tried to install the [ROM][ICS] [Unofficial] Root-ready Huawei/Springboard International ROM and downloaded the dload folder to my SDCard, etc. I tried using the dload folder with the ulmt.cfg file in it and that failed with a "Installation aborted" message. I then removed that file and tried to go into CWM and tried "Install from zip" approach. Same thing...installation aborted message.
4) So, then I did the next stupid thing...in CWM, I formatted my /system, /data, and /cache. That was a big mistake! I now have officially bricked by tab.
5) I tried to get rid of CWM recovery by extracting the recovery.img file from the stock rom zip file. I fastboot flashed that to the recovery and recovery2 partitions. I then thought, let me try extracting the update.zip from the stock rom zip and put that on the root of my sdcard and tried to install that. No go...it just says, update failed with a big red "FAIL" message in the center.
6) I then tried to install CM10, to see if that would work. I downloaded the TWRP recovery and also the CM10 ROM .zip file, along with the google apps zip. I flashed the TWRP recovery using fastboot. That worked fine. I was also able to install the CM10 Rom, or at least it reported back "Successful". Same with the google apps zip. But then when I reboot, it only gets to the T-mobile Splash screen and stays there forever.
Please help! I tried to install the Stock Rom using the TWRP recovery, but again, it reports "Installation aborted." So, what am I doing wrong or what can I do to fix this?
Thanks.
[UPDATE] -
Okay, so I actually tried installing CM10 again using the TWRP recovery since it said that it was "Successful." And sure enough, it was successful, it seems. Once I installed it, rebooted the tablet and waited on the T-mobile Springboard screen for about 10 minutes, it launched CyanogenMod. I then set up the tablet with CM10. I had received the unlock code from T-mobile and so my tablet was sim unlocked. I put a AT&T sim card and sure enough it got signal and I was able to surf the web and make phone calls. I downloaded the speed test app from the Play Store and noticed that I was getting about 1.5Mbps download and about 600kbps upload. Not bad. The problem I noticed is that I can't receive calls. I can call out, but when someone tries to call me, the tablet doesn't acknowledge an incoming call. The caller just goes straight to voicemail. I do get a voicemail alert.
So, I don't know whether that is an issue with the CM10 build or a problem in my network / APN settings.
I would like to get the rooted T-mobile International stock ROM on there so that I can try it with that. I'll keep you all posted.
Thanks!
9 times out of 10, I get installation aborted errors because of a botched download. Try downloading the file again, and if available, verify that the MD5 sum of your downloaded file matches the one provided by the developer.
And if I'm not mistaken, TWRP recovery and CWM recovery aren't capable of flashing the T-Mobile stock recovery. If you have TWRP working properly, I would continue trying to flash one of the unlocked ROMs available. I highly recommend HWMOD's ICS (available here)
Best bet would be to fastboot flash the recovery img from the hauwei site update.zip. Then do the standard pop the stock hauwei update.zip on the sd card and do the normal upgrade method. That should full wipe the phone and then you can start tinkering with it again. Also huawei posted the offical root on their site.
nightanole said:
Best bet would be to fastboot flash the recovery img from the hauwei site update.zip. Then do the standard pop the stock hauwei update.zip on the sd card and do the normal upgrade method. That should full wipe the phone and then you can start tinkering with it again. Also huawei posted the offical root on their site.
Click to expand...
Click to collapse
I don't want to mix up the T-mobile images with the Huawei images. Even though I've screwed things up already. But, if you read my previous post, I've got CM10 working, but no incoming calls.