So, I got my hands on a semi-bricked Incredible the other day. I'm not sure what was done to it previously, but I can still access recovery menu and all that.
HBOOT - 0.92.0000
Baseband - 2.15.00.07.28
CMW Recovery - 2.5.1.2
I've tried installing both of these:
http://forum.xda-developers.com/showthread.php?t=2141642
http://forum.xda-developers.com/showthread.php?t=1737398
But I get this error whenever I try:
E:Error in /sdcard/*name of rom*.zip
(Status 7)
Installation Aborted.
Any help with this would be appreciated.
EDIT - I tried installing CM 6.1 just now, but it's stuck on the boot screen.
So, I got my hands on a semi-bricked Incredible the other day. I'm not sure what was done to it previously, but I can still access recovery menu and all that.
HBOOT - 0.92.0000
Baseband - 2.15.00.07.28
CMW Recovery - 2.5.1.2
I've tried installing both of these:
http://forum.xda-developers.com/showthread.php?t=2141642
http://forum.xda-developers.com/showthread.php?t=1737398
But I get this error whenever I try:
E:Error in /sdcard/*name of rom*.zip
(Status 7)
Installation Aborted.
Any help with this would be appreciated.
EDIT - I tried installing CM 6.1 just now, but it's stuck on the boot screen.
EDIT 2 - After doing a full wipe, I tried again with the newest CM 7.2. I was able to boot properly this time. I updated CWM to 5.0.2 and tried installing one of the ROMs again (the first, to be exact). It installed fine through CWM, but it won't boot. It stays on the HTC Incredible logo screen.
bumpity bump bump
Your recovery is probably too old. (Oops, saw your edit. Still, there is a newer recovery you might want to try.)
Are you S-ON or S-OFF? And I'd update your HBOOT to 1.02.
http://www.htcdev.com/bootloader/
pswinslow said:
Your recovery is probably too old. (Oops, saw your edit. Still, there is a newer recovery you might want to try.)
Click to expand...
Click to collapse
According to the CWM website, 5.0.2 is the newest one available for the Incredible.
PonsAsinorem said:
Are you S-ON or S-OFF? And I'd update your HBOOT to 1.02.
http://www.htcdev.com/bootloader/
Click to expand...
Click to collapse
I'm pretty sure it's S-OFF since the CM ROM I installed wasn't signed. I'll update the bootloader when I get home though.
nVidius said:
According to the CWM website, 5.0.2 is the newest one available for the Incredible.
Click to expand...
Click to collapse
I use TWRP 2.5.0.0: http://forum.xda-developers.com/showthread.php?t=1404464
There is also an unofficial CWM 6.0.3.2 here: http://forum.xda-developers.com/showthread.php?t=2210009&page=2
CWM 5.0.2.0 should be fine. TWRP 2.5 has a severe backup and restore issue. I don't recommend that version of TWRP if you rely on backups but TWRP 2.4.4.0 should be ok.
Sent from my HTC One using Tapatalk 2
Related
I used the method described here: http://forum.xda-developers.com/showthread.php?t=1025336#12712582 to root my slide from its stock 2.2.1 firmware, then installed CyanogenMod7 (which is sweet by the way!). Unfortunately, I can't get the Google Apps to install. I have tried:
1) Downloading the universal and also the mdpi zips and sticking them on the sd card root and flashing them from recovery.
2) Downloading the universal and also the mdpi room from the ROM Manager application.
In both cases I get:
Code:
...
Verifying update package...
E:signature verification failed
Installation aborted
Any ideas? Both methods should have worked for me, but neither did. I have made sure the zip hashes match with the ones posted.
Having exactly the same problem. First time I tried it went into bootloop after installing gapps... later I tried to reinstall them again...shows the same error in the recovery...
coolbrain said:
Having exactly the same problem. First time I tried it went into bootloop after installing gapps... later I tried to reinstall them again...shows the same error in the recovery...
Click to expand...
Click to collapse
Out of curiousity, does your HBOOT show that you have S-ON or S-OFF? I have a theory that S-ON is the cause of our troubles.
powerofpi said:
Out of curiousity, does your HBOOT show that you have S-ON or S-OFF? I have a theory that S-ON is the cause of our troubles.
Click to expand...
Click to collapse
Its S-OFF....
try this... after installing cm7, in the recovery try to install gapps via recovery once...if it doesnt work then try to toggle signature verification..it should be disabled...then try installing gapps..you shouldnt have any problem this time...
coolbrain said:
try this... after installing cm7, in the recovery try to install gapps via recovery once...if it doesnt work then try to toggle signature verification..it should be disabled...then try installing gapps..you shouldnt have any problem this time...
Click to expand...
Click to collapse
I would do that, but unfortunately the stock 2.2.1 firmware from HTC seems to have installed a version of HBOOT that permanently enforces S-ON. I have tried both the AlphaRev and Unrevoked utilities- neither worked to get rid of this. If you have other ideas, let me know.
Very strange. Just installed Cyanogenmod and Google Apps with no problems (after rooting/downgrading the new OTA).
Followed the tutorial and installed both update-whatever-slide.zip and gapps-whatever.zip from ClockworkMod Recovery. Have S-ON in HBOOT.
Hello
Everytime I try to flash the OxygeN ROM or any ROM for that matter I get an error:
assert failed: write_raw_image ("/tmp/boot.img", "boot") Error in /sdcard/update.zip (Status 7)
What am I doing wrong? Can anyone help please??
Thanks
thecf said:
Hello
Everytime I try to flash the OxygeN ROM or any ROM for that matter I get an error:
assert failed: write_raw_image ("/tmp/boot.img", "boot") Error in /sdcard/update.zip (Status 7)
What am I doing wrong? Can anyone help please??
Thanks
Click to expand...
Click to collapse
Are You using a Gold Card? Are you rooted?
To make a Gold Card;
http://www.droid-den.com/android-guides/android-guide-how-to-create-a-gold-card
The gold card, allows you to install unsigned ROMs in the beginning, a must for Desire owners. After that;
Then root your phone;
Then flash a custom ROM.
Seriously, were past the stage of 50 billion processes.
http://android.modaco.com/content/software/308798/pc-application-goldcardtool/
Sent from CM7
Hello sirs,
I have the same exact problem.
I'm using a Goldacard (via GoldcardTool) and my Desire is rooted (i have Super User on my Apps list) with Clockworkmod recovery.
My HBOOT is 0.93 and I'm on 2.2 official ROM.
Appreciate all the help for this noob.
Thank you very much
nonofficialcover said:
Hello sirs,
I have the same exact problem.
I'm using a Goldacard (via GoldcardTool) and my Desire is rooted (i have Super User on my Apps list) with Clockworkmod recovery.
My HBOOT is 0.93 and I'm on 2.2 official ROM.
Appreciate all the help for this noob.
Thank you very much
Click to expand...
Click to collapse
I think, remove goldcard, insert blank sd, download latest oxygen to root of this sd, wipe everything in cwm, flash rom.
Hope that works, its the process I followed!
stringer7 said:
I think, remove goldcard, insert blank sd, download latest oxygen to root of this sd, wipe everything in cwm, flash rom.
Hope that works, its the process I followed!
Click to expand...
Click to collapse
Will try out that one one sir, thank you!
Flashed ROM on a non-goldcard sd and i still have the same problem.
Already tried on Oxygen, Leedroid, SupeRomHD and RCMixS. With or without goldcard. Hboot 0.93 on Stock 2.2 ROM with S-ON.
Please help
nonofficialcover said:
Already tried on Oxygen, Leedroid, SupeRomHD and RCMixS. With or without goldcard. Hboot 0.93 on Stock 2.2 ROM with S-ON.
Please help
Click to expand...
Click to collapse
You're desire isn't PVT4 by any chance is it?
If so I know there are problems using clockwork, and I wonder if that's contributing?
stringer7 said:
You're desire isn't PVT4 by any chance is it?
If so I know there are problems using clockwork, and I wonder if that's contributing?
Click to expand...
Click to collapse
Sir,
It is a PVT4. I was able to solve it by doing S-OFF
After which all my previous problems were solved - nandroid backup, modify my phone partitions and flash custom ROM.
Nevertheless it's really recommend to use amonra recovey instead of clockworkmod if you have a pvt4 desire (to avoid strange issues):
http://dl.dropbox.com/u/20471345/SUroot/Tools/Android/Recovery/recovery-RA_2.0.1.img
Another Status 7 error here.
I have a Desire with Oxygen 2.1.4 and when trying to update to 2.1.5, I got this error.
Reading through your posts and watching videos on YouTube, tried 2 methods of flashing Amon Ra over ClockworkMod to fix the Status 7 error:
1. With ClockworkMod Rom manager app, which grayed out the alternate recovery field in the app and did not allow, and
2. With the android emulator app which did not found the flash_image command
Is there an another SAFE way to flash Amon Ra Recovery 2.0.0 over ClockworkMod recovery?
Awaiting your much appreciated answer.
Unrevoked 3.21 and select custom recover img
Nothing. Flashed the Amon Ra recovery, cleared all cache, still nothing.
Back to ClockworkMod again.
Status 7 error on me like a nightmare
Have other suggestions?
Try this command...
fastboot oem eraseconfig
Need to update my recovery for successful flash of baadnewz desire S
port. Ive got the image, cant find the option in bootloader to install it
though. I am s-off. Searched everywhere but cant find a direct answer.
Any help is appreciated.
Use the fastboot commands to flash it, or the flasher app in ROM Development
EddyOS said:
Use the fastboot commands to flash it, or the flasher app in ROM Development
Click to expand...
Click to collapse
Thanks for the quick answer. Im going to try that now. Another question if i may, sorry if its
noobish just not up to date on this stuff, will say Leedroid or sense roms still work if i have
CM7 hboot?
Edit : Anyone in the same boat go here :
[UTILITY] Android Flasher(Recovery,splash1,Radio,HBOOT,bootanim)[V1.6.1](15/01/11)
Now i really need help. My phone is hanging in fasboot mode while i was
flashing hboot with the flasher. what to do next?
esk02k said:
Now i really need help. My phone is hanging in fasboot mode while i was
flashing hboot with the flasher. what to do next?
Click to expand...
Click to collapse
Can you get into recovery? If so, you could try restoring nandroid and checking that the hboot file downloaded OK - if it came with an MD5 it's worth checking that - before giving it another go.
I've never used the flasher, just adb commands. Never had a problem flashing hboot tables.
00droid said:
Can you get into recovery? If so, you could try restoring nandroid and checking that the hboot file downloaded OK - if it came with an MD5 it's worth checking that - before giving it another go.
I've never used the flasher, just adb commands. Never had a problem flashing hboot tables.
Click to expand...
Click to collapse
Yea my own stupidity i guess. well im gonna pull the battery. lets see what
happens then.
edit : its ok regained control after unpluging usb. how do i know if it installed.
i am familiar with adb. how do i flash the cm7 hboot via that?
I also had problem with the flasher when I started in windows, then the phone just couldnt start or flash a new rom, but when I started the phone with backbottom ipressed and then started Android flasher all worked perfect.
esk02k said:
Yea my own stupidity i guess. well im gonna pull the battery. lets see what
happens then.
edit : its ok regained control after unpluging usb. how do i know if it installed.
i am familiar with adb. how do i flash the cm7 hboot via that?
Click to expand...
Click to collapse
Good news! To check your recovery you can either just boot into recovery and see what version you have, or remain booted and look in /sdcard/clockworkmod.settings (open as text file) to see the version number.
To flash hboots - check the instructions on the Alpharev site: www.alpharev.nl
EDIT: I found this post helpful as the instructions at alpharev are a little minimal at first sight. Obviously you are using the CM7 table not the Oxygen one!
http://forum.xda-developers.com/showthread.php?t=882758
Hi guys, I'm a little stuck/confused. When I boot my phone in Recovery Mode it says I'm running Clockwork Mod v2.5.0.1.
I installed a new version of ROM Manager (v3.0.1.0) flashed ClckworkMod Recovery and that says I have v 2.5.0.7 - so:
1. How do I ensure that the recovery mode is v 2.5.0.7
2. Do I need to unistall ROM Manager or,
3. Just leave it be?
System details:
Rooted HTC Desire
Android version 2.2.1
Baseband version 32.54.00.32U_5.14.05.17
Kernel 2.6.32.36_rcmix_11032
Build number
RCMix HD v3.6.1 D2Ext Rotate
The numbers above don't mean much to me - I'm not a dev.
Thanks in advance.
*EDIT*
I've since downladed and installed the .zip found here: http://forum.xda-developers.com/showthread.php?t=839640
It worked but ROM Manager still says the current recovery is version 2.5.0.7 although when I rebooted the writing was orange. I hope that makes sense to someone...
djkaija said:
It worked but ROM Manager still says the current recovery is version 2.5.0.7 although when I rebooted the writing was orange. I hope that makes sense to someone...
Click to expand...
Click to collapse
This is perfectly normal as 3.0.0.5 isn't an 'official'/final release yet.
During the summer I rooted my phone and i have Clockworkmod v2.5.0.7 installed.
I am trying to upgrade to the latest version and it never seems to stick.
Using Rom manager. It says that im flashed to v5.0.2.0 yet when i boot to recovery from rom manager it loads to v2.5.0.7. Does the same thing if i choose to flash a rom though ROM MANAGER. each time v2XXX loads
So i fire up recover and try loading the zip. Bingo it works. The screen turns from green to blue and V5.0.2.0 is now there for me to use. But if i reboot and later return to recovery its back to the old V2xxxx..
Any ideas why this is happening? Is it really necessary to move on to the V5xxxx versions? I was going to try out some new roms and they failed to load yesterday through v2.5.0.7 yet the rom i had been using loaded fine.
Thanks in advance..
When you use Rom Manager to flash a rom or reboot into recovery from Rom Manager, it boots the recovery from a downloaded recovery file. It's known as fake flash or in other words, it's temporary. If you want a permanent recovery, you would need to flash a recovery.img through fastboot.
Meaple said:
When you use Rom Manager to flash a rom or reboot into recovery from Rom Manager, it boots the recovery from a downloaded recovery file. It's known as fake flash or in other words, it's temporary. If you want a permanent recovery, you would need to flash a recovery.img through fastboot.
Click to expand...
Click to collapse
if your Desire is s-off, then ROM Manager flashes recovery normally.
Sent from my HTC Desire using XDA App
rom manager now works only if u have s-off..no fake flash anymore is possible
revolutionary.io will upgrade cwm if you want
I think this thread answers one of my own questions but will ask it anyway to confirm; when I rooted my Desire (via Unrevoked) a few months back, the ROM Manager app that continues to be updated via the market offers the option to upgrade the version of CWM... is it OK to proceed with this?
I've been wary of upgrading from the version installed via the rooting process, just in case, but seeing this thread has made me think there isn't actually an issue with whatever version of recovery you have installed?
TKG26 said:
I was going to try out some new roms and they failed to load yesterday through v2.5.0.7 yet the rom i had been using loaded fine.
Click to expand...
Click to collapse
Out of curiosity - what roms you tried to load? As far as I know 2.5.0.7 was the last cwm supporting both amend and edify scripting and it never failed for me personally.
To upgrade recovery (or hboots) I always use Fastboot Commander and it's very easy to use and never let me down.
erklat said:
Out of curiosity - what roms you tried to load? As far as I know 2.5.0.7 was the last cwm supporting both amend and edify scripting and it never failed for me personally.
Click to expand...
Click to collapse
I agree. Unless you need to maintain an ext 4 partition (as 2.5.0.7 converts it to lower apparently when backing up) I see no reason to change from 2.5.0.7.
I use it even today. Best recovery IMHO.
Hey there,
My HTC One m7 vzw HBOOT 1.56. cannot use its storage after flashing teaMSeven kernel.
I use cyanogenmod 11 last stable release and TWRP 2.8.4.0.
My device is rooted, s-on and it is "TAMPERED UNLOCKED"
When the device is in the recovery, the problem does not appear.
I tried to flash a different ROM and it says "error executing updater binary in zip sdcard...
or " unable to mount /system". I can flash CM 11 and boot into it but i cant save or download anything on the Phone.
I also tried to flash a different kernel (tinykernel-m7-cm11) -nothing changed
pls help me !
ps. yes I know my english is bad, its because i'm German
maxizocker said:
Hey there,
My HTC One m7 vzw HBOOT 1.56. cannot use its storage after flashing teaMSeven kernel.
I use cyanogenmod 11 last stable release and TWRP 2.8.4.0.
My device is rooted, s-on and it is "TAMPERED UNLOCKED"
When the device is in the recovery, the problem does not appear.
I tried to flash a different ROM and it says "error executing updater binary in zip sdcard...
or " unable to mount /system". I can flash CM 11 and boot into it but i cant save or download anything on the Phone.
I also tried to flash a different kernel (tinykernel-m7-cm11) -nothing changed
pls help me !
ps. yes I know my english is bad, its because i'm German
Click to expand...
Click to collapse
Hi, You'll need to run this RUU here. It repairs mount/partition/system problems:
http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442
After running, do a factory reset, then it is 100% stock and everything will be working.