Related
hi all,
I'm from singapore and recently have bought a htc hero. I wanted to load modaco's rom but failed. this is what i have experienced.i tried the guide on adb commands but it gave me the error "remote: failed". subsequently i try the flashrec guide but the flashrec gave me invalid error.
Can someone help?
There are my phone details:
Firmware:1.5
build number: 2.73.707.9.146733 CL#62020 release-keys
software version: 1.0.0.A6288
tianci86 said:
hi all,
I'm from singapore and recently have bought a htc hero. I wanted to load modaco's rom but failed. this is what i have experienced.i tried the guide on adb commands but it gave me the error "remote: failed". subsequently i try the flashrec guide but the flashrec gave me invalid error.
Can someone help?
There are my phone details:
Firmware:1.5
build number: 2.73.707.9.146733 CL#62020 release-keys
software version: 1.0.0.A6288
Click to expand...
Click to collapse
one assumes that you have already rooted your HTC Hero ?
If not then follow this
http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click/
once that is done then follow this
http://theunlockr.com/2009/08/27/how-to-load-a-custom-rom-on-your-htc-hero/
This worked like a charm for me so I assume that it should work for you as well
Hope this helps
Devchef1
Devchef1 said:
one assumes that you have already rooted your HTC Hero ?
If not then follow this
http://theunlockr.com/2009/08/27/how-to-root-your-htc-hero-in-one-click/
once that is done then follow this
http://theunlockr.com/2009/08/27/how-to-load-a-custom-rom-on-your-htc-hero/
This worked like a charm for me so I assume that it should work for you as well
Hope this helps
Devchef1
Click to expand...
Click to collapse
hi, i havent root my hero. i followed the guide and could not load Amon Ra’s Hero Recovery Image into my phone. there's error
Since you are in Asia you likely have the 2.73.707.9 ROM you can check this under Settings/About Phone. Please see this thread:
http://forum.xda-developers.com/showthread.php?t=563256
there is no way to gain root and flash ROMs onto this release at this time
duplicate post
Whats a G3?
here everyone calls the Hero the G3
csasek said:
duplicate post
Click to expand...
Click to collapse
u also stuck with this version too?
csasek said:
here everyone calls the Hero the G3
Click to expand...
Click to collapse
Where, China? I've heard it called the G2 by virtue of T-Mobile branding it the G2 Touch, but never the G3!
Regards,
Dave
I have this model also, just wondering when we are able to root the hero and install different roms will it enable different android market? I'm in the US and am lacking apps that should be present e.g Pandora, ebuddy etc.
I was wondering if this way of force updating would work?
download the official rom version 1.76.405.x firmware (not rooted),
boot up the unit using home+power (to boot into recovery);
extract the official rom's rom.zip and rename into update.zip
put that update.zip into sdcard's root
on the device, apply the update in the recovery.
?
kazuni said:
I was wondering if this way of force updating would work?
download the official rom version 1.76.405.x firmware (not rooted),
boot up the unit using home+power (to boot into recovery);
extract the official rom's rom.zip and rename into update.zip
put that update.zip into sdcard's root
on the device, apply the update in the recovery.
?
Click to expand...
Click to collapse
try it, but i doubt it will work because it will check the CID in the rom.zip(or renamed to update.zip) file and that ROM does not contain CID's needed for most phones.
see here
http://forum.xda-developers.com/showthread.php?t=569730
Log:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(bad)
Installation aborted.
I guess that's their meaning of non-CID'd rom reply?
kazuni said:
Log:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(bad)
Installation aborted.
I guess that's their meaning of non-CID'd rom reply?
Click to expand...
Click to collapse
uhm, could be, or it doesn't like the rom.zip (altough renamed to update.zip) zip file, which makes sence as we can create update.zip files and sign them ourselfs (stuff that for example paul (modaco) does) i need more playing time myself, but you can try and creating a new zip with the contents of the rom.zip and sign it, then look if that works....but i'm doubtful
funny thing is, i've downloaded the signed rom from modaco, (they are signed, as far as i can be told by the file name), and tried to flash it again using the same method:
log:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Veryfiying update package...
E:No signature (740 files)
E:Verification failed
Installation aborted.
still no go.
does renaming a file affect the signature?
kazuni said:
funny thing is, i've downloaded the signed rom from modaco, (they are signed, as far as i can be told by the file name), and tried to flash it again using the same method:
log:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Veryfiying update package...
E:No signature (740 files)
E:Verification failed
Installation aborted.
still no go.
does renaming a file affect the signature?
Click to expand...
Click to collapse
no, but the type of signing is the problem, the update.zip (with cert/sign files inside the zip) is a different kind then doing an edit on the physical zip file and changing (signing) and thats whats being checked and we currently can't duplicate (or re-sign a changed rom.zip)
I found a solution after being told it was not possible.
The Brown Hero I purchased was also an Asian version and had no Market.
I was so scared and frustrated at first because everyone said there was no solution.
But I found one!
*1. Download Linda file manager from here and install since you don't have the market! (I had a copy already on my sdcard) goto Settings, Applications, and make sure Unknown source is checked ON.
*2. On your phone, goto Settings, SD card and phone storage, and click Unmount SD card.
*3. Then click Format SD card (it should automatically remount after this)
*4. Plug the phone into the compuer via USB, then pull down the notification bar and click on the SD card notification. Then click mount.
*5 Download the Flashrec apk from this link: http://zenthought.org/system/files/asset/2/flashrec-1.1.2-20090909.apk and install using Linda File manager.
*6. Download Amon_RA_Herov1.2.2 Recovery image and place on root of sdcard
*7. Open the FlashRec program and click on Backup Recovery Image and wait for it to finish.
*8. Once done, click on the empty text box in the FlashRec program and type
/sdcard/Recovery-RA-HERO-v1.2.2.img
Then click on the Flash Custom RecoveryImage button and wait for it to finish.
*9. Turn off the phone and turn it on into Recovery mode by holding down Home and Power to turn it on (keep holding until the recovery screen comes up has a bunch of text on a black background). So long as that screen comes up, you have done it correctly and now you can load this rom which is HTC Generic 2.73.405.5
It's also referred to as Modaco version 2.2, it's what I'm currently using.
*10. Place that rom on the root of you're sdcard and use option Apply sdcard: choose zip option and flash! Once done reboot and you're all set and will have The Android Market and all the goodness that rooting provides!
Hope this helps!
You had the same ROM version as mentioned in the original post? ^^
plbe said:
You had the same ROM version as mentioned in the original post? ^^
Click to expand...
Click to collapse
My version was a little different but it was an Asian version and did not come with the Android Market installed and had SlideMe market instead.
Here is a screen shot:
i have tried the method u suggested but to no avail. ya, your version of hero is slightly different from mine.
ok i downloaded the update for 2.2 but i can not get it to load.
i have put it on the sd card and then tried to update from that. but its a no go.
then i renamed the file to update.zip and tried another time and still no go.
so if some one could let me know how to get this thing updated.
are you getting this?
ttp://img507.imageshack.us/img507/5466/img00414201007302042.jpg
add h to the front of the link.
im getting this am im clueless.
I downloaded it using the link directly from HTC, you need to be on a stock 1.47 (I did a reinstall of 1.47 from the HTC ruu, so it was a clean install), copy the update to your sd card and name it update.zip, power off, turn on by pressing power and vol up, select bootloader, then select recovery, once you are at the htc phone with red exclamation mark screen press power and vol up, select apply sdcard: update.zip, it will start scanning the file, then it will prompt to reboot, it will reboot to a green circle with an arrow and begin the installation. Those are the steps I followed and mine updated to 2.2 successfully.
no i downloaded it from Engadget on my phone and then copied it to the computer for safe keeping. but then cleared all storage as well and then added it back on there. on the sd and it will not load.
it just keeps saying that not the right file.
i followed all the instructions to the T.
FYI im unrevoked. Shouldnt matter.
Ok and what were those another time bc i did not see any other then the download.
hey thanks i for got i was on 1.32 still but with up date 1 so i guess that is the issue then. will check it out and see. thanks
Android police has a mirror for the update. HTC has delete the link form their site. I am just letting you guys know how I did it. My phone was not rooted. All stock, from original release to 1.47 update and now this 3.26 update (froyo 2.2).
Anyone else think i gotta get rid of unrevoked off my evo, go to the previous RUU and then update?
Daft Punk said:
Anyone else think i gotta get rid of unrevoked off my evo, go to the previous RUU and then update?
Click to expand...
Click to collapse
Probably so if you want to try 2.2. Also, engadget has a statement from HTC regarding this update:
Update: HTC just shot us a message to clarify that this is not the final ROM version and that the company is strongly recommending not to install this. Additionally, a request has been put in to remove the file from the server, so if you still want to try at your own risk, better download now while it's still available.
Update 2: ... and now it's gone. We're sure crafty internet users can still find the file lingering elsewhere, but you won't be getting it from HTC's servers this weekend. You know the old saying, ye who snoozes, something something, tough luck.
Its running fine for me, so I we will have to see on 8/1 what the ota version will be.
ok i just updated to the 1.47 and now its telling me that the it can not open the sd card. and or failed to open directory
OK PEOPLE DONT COME IN HERE TELLING US HOW TO DOIT OR WHAT THIS OR THAT SITE SAYS. WE KNOW!!
Now back on topic.
so i get now signature verification failed
this is what is says in full.
--Install from sdcard...
finding updated package....
opening update package....
verifying update package...
E:failed to open/sdcard/update.zip (no such file or directory)
E:signature verifcaiton failed
install aborted
so what am i doing wrong. i have checked to files and they should all be there. so if some one has a link to the file that i might need to redownload the update and try all over.
fsuwade said:
so i get now signature verification failed
this is what is says in full.
--Install from sdcard...
finding updated package....
opening update package....
verifying update package...
E:failed to open/sdcard/update.zip (no such file or directory)
E:signature verifcaiton failed
install aborted
so what am i doing wrong. i have checked to files and they should all be there. so if some one has a link to the file that i might need to redownload the update and try all over.
Click to expand...
Click to collapse
Did you name the file update.zip on your sd card?
Daft Punk said:
OK PEOPLE DONT COME IN HERE TELLING US HOW TO DOIT OR WHAT THIS OR THAT SITE SAYS. WE KNOW!!
Now back on topic.
Click to expand...
Click to collapse
You for real? Caps? What are u a child, nobody was off topic till you opened your mouth!
Happy Friday everyone!
fsuwade said:
ok i just updated to the 1.47 and now its telling me that the it can not open the sd card. and or failed to open directory
Click to expand...
Click to collapse
I had issues with my sd since I purchased the phone (wouldn't show up as a drive on a mac, etc), I formatted the sd card earlier this week, and now all my problems are gone.
Daft Punk said:
OK PEOPLE DONT COME IN HERE TELLING US HOW TO DOIT OR WHAT THIS OR THAT SITE SAYS. WE KNOW!!
Now back on topic.
Click to expand...
Click to collapse
I wasn't saying not to do it, in fact I am trying to help, I did mine successfully. I was just posting HTC's response as to why they removed the file from their servers. They say it isn't the final Froyo 2.2 update.
that i did. and i even tried just leaving it the way was downloaded. and still it does the same. that is the reason maybe i need to redownload it. any links to a download.
I don't have rights to post links, sorry
Edit: guess I do, lol
http://www.androidpolice.com/2010/07/30/breaking-htc-releases-android-2-2-froyo-ota-for-evo4g-download/
Also, even though HTC is saying this isn't the final update, it has the build number sprint posted, 3.26.651.3, so not sure what else is missing.
Are you worrying about your warranty voided Galaxy Y? (by rooting it in some earlier day!)
Dont Worry! So here's trick to kick "Super user" and take your phone into Unrooted Condition back again.
1. Just Download this File
2. Save it in the root of SDCard.
3. Restart into Recovery mode [Shutdown and Hold (Volume Up + Power Button + Home Button) at once for few Seconds]
4. Choose "Update using a Zip file"
5. jz point this Unroor.zip and Proceed.
Voila! It should work!
Good luck!
-harshadura
Just hit the LIKE button if this POST helpful for you too. Thanks
matching root / unroot
one should point out that there are many rooting UPDATE.ZIPs around. most require a special unrooter to unroot perfectly. some unrooters do not properly work with certain rooting-techniques. here is a matching pair of root / unroot:
mai77 said:
one should point out that there are many rooting UPDATE.ZIPs around. most require a special unrooter to unroot perfectly. some unrooters do not properly work with certain rooting-techniques.
Click to expand...
Click to collapse
As most rooting techniques just install Superuser.apk and the su binary, this unrooter should work. It simply uninstalls those two files and even uninstalls busybox, just in case your rooting technique installed it.
Nice edify!
above files tested OK on SGY
-- Installing: /sdcard/UPD_unroot.zip
Finding update package...
I:Update location: /sdcard/UPD_unroot.zip
Opening update package...
Installing update...
un-rooting
script result was [1]
Install from sdcard complete.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
-- Installing: /sdcard/UPD_root.zip
Finding update package...
I:Update location: /sdcard/UPD_root.zip
Opening update package...
Installing update...
rootingminzip: Extracted file "/system/app/Superuser.apk"
minzip: Extracted file "/system/bin/su"
script result was []
Install from sdcard complete.
find rooting script below with "proper" name UPDATE.ZIP
Dead Link
media fire, please re-up
j0rdz02 said:
media fire, please re-up
Click to expand...
Click to collapse
You can download the attached files directly from xda servers if mediafire isn't working.
Also reporting to get it moved to general section.
A Hero Can Be Anyone. GENERAL HELP THREAD
Deleted
Chronique said:
wow
very nice thread
Click to expand...
Click to collapse
Stop spamming. I've already reported it for moving. Hope mods sees your post also.
A Hero Can Be Anyone. GENERAL HELP THREAD
Hi all,
I'm trying to replace the font on bubor's CM11 ROM by means of flashing one on of the ZIPs available at http://forum.xda-developers.com/goo...-fontster-betas-flashable-font-packs-t2513985
I am using bubor's TWRP v2.7.1.
The problem I first encountered when trying to flash a font was the error message "Error executing updater binary" and thus the flashing "Failed". Based on the advice at http://forum.xda-developers.com/showthread.php?t=2290009 , I figured it would probably be a good idea to replace the update-binary with the one found in my ROM's ZIP, so I did that.
However, the ZIP still doesn't flash. Although I no longer get the "Error executing updater binary" message, now TWRP simply tells me "Error flashing zip" without offering me any explanation.
Please can you help with this, and apologies for the noob question. I have tried installing the ZIP from both internal and external SD. My SD's are swapped - could that have something to do with it?
- downlaoded http://www.mediafire.com/download/40x5qm44a24p0dg/CantarellFontPack.zip
- downlaoded http://dualhoki.vim.hu/bubor/dev/keyboard-light.zip
- replace update-binary ( copy from keyboard-light.zip)
- install
no error.
Would you be more detailed what did you use with what, please.
bubor said:
- downlaoded /CantarellFontPack.zip
- downlaoded keyboard-light.zip
- replace update-binary ( copy from keyboard-light.zip)
- install
no error.
Would you be more detailed what did you use with what, please.
Click to expand...
Click to collapse
I'm sorry for not being detailed enough.
I tried following your steps but unfortunately the flashing still failed. I eventually got it to work after a combination of actions, but I think the most crucial one was changing the write permissions of the \system\fonts folder from "drwxr-xr-x" to "drwxrwxrwx".
Thanks for your efforts in any case, I really appreciate all the work you're doing.
Hi
I have some weird questions some problems that Im trying to figure out, hoping someone can help or point me in right direction.
Im not new to 'Android' but this are beyond my scope.
Ok, so, the WFS. Got it unlocked, S-Off, rooted etc thats all fine.
Now, the basis of my troubles come with the zips and updater-binary. It seems that every zip I have can be flashed on any device Ive tried (from N4 to a OUYA to a HUDL to a Nook Simple Touch etc) all except the ruddy WFS.
I either get a status error or a binary fail.
I used to have to grab a updater-binary from a current ROM zip and replace it in every zip I wanted to flash which just got annoying. Even then it will only be certain recoveries that will flash them.
I only use my WFS as a remote for XBMC and not as a 'phone' but like to keep all my devices as current as technically possible.
Im trying to find out what is the cause of this and how to make it so that all my zips work with all my devices off the bat.
Maybe not your usual questions but either way I could do with extending my knowledge a little and getting this sorted
{ffs posted in General by mistake, apologies}
Dude360 said:
Hi
I have some weird questions some problems that Im trying to figure out, hoping someone can help or point me in right direction.
Im not new to 'Android' but this are beyond my scope.
Ok, so, the WFS. Got it unlocked, S-Off, rooted etc thats all fine.
Now, the basis of my troubles come with the zips and updater-binary. It seems that every zip I have can be flashed on any device Ive tried (from N4 to a OUYA to a HUDL to a Nook Simple Touch etc) all except the ruddy WFS.
I either get a status error or a binary fail.
I used to have to grab a updater-binary from a current ROM zip and replace it in every zip I wanted to flash which just got annoying. Even then it will only be certain recoveries that will flash them.
I only use my WFS as a remote for XBMC and not as a 'phone' but like to keep all my devices as current as technically possible.
Im trying to find out what is the cause of this and how to make it so that all my zips work with all my devices off the bat.
Maybe not your usual questions but either way I could do with extending my knowledge a little and getting this sorted
{ffs posted in General by mistake, apologies}
Click to expand...
Click to collapse
What is it you are flashing exactly? And which recovery are you using? Could be a problem with the recovery you use
I have many zips which do many things but they all use the same binary..
eg,
I have a zip which i use to remove .ogg from the /system/media/audio folder and extracts my own set of sounds. Or
I have a zip which has a game apk and its relevant obb files which extract to save me downloading them again.
etc
These have all been flashed on a large variety of devices without a hitch.
They will work on WFS using an update-binary from a WFS ROM zip but not with the one I use for the rest.
I have tried these on every recovery from CWM 5x to the very latest TWRP compiled recently by Oliver for the CM11 builds.
I suspect that it is something to do with the recovery as I also cant get other things to work.
eg.
For ROMCleaner we use a custom busybox binary which does some work in /tmp and our romcleaner binary which does the brunt of the work.
busybox will error (but for life of me cant remember what it says), while the RC binary will 'exit status 4'
Ive been playing with the WFS version of ROMCleaner for a long time now and am determined to get it working properly.
This is where my knowledge ends really, it could be something to do with the binary, with ARM6, the kernal used in the recovery or an evil gremlin determined to make me rake down and cry.
Just looking for big shove in the right direction.
Dude360 said:
I have many zips which do many things but they all use the same binary..
eg,
I have a zip which i use to remove .ogg from the /system/media/audio folder and extracts my own set of sounds. Or
I have a zip which has a game apk and its relevant obb files which extract to save me downloading them again.
etc
These have all been flashed on a large variety of devices without a hitch.
They will work on WFS using an update-binary from a WFS ROM zip but not with the one I use for the rest.
I have tried these on every recovery from CWM 5x to the very latest TWRP compiled recently by Oliver for the CM11 builds.
I suspect that it is something to do with the recovery as I also cant get other things to work.
eg.
For ROMCleaner we use a custom busybox binary which does some work in /tmp and our romcleaner binary which does the brunt of the work.
busybox will error (but for life of me cant remember what it says), while the RC binary will 'exit status 4'
Ive been playing with the WFS version of ROMCleaner for a long time now and am determined to get it working properly.
This is where my knowledge ends really, it could be something to do with the binary, with ARM6, the kernal used in the recovery or an evil gremlin determined to make me rake down and cry.
Just looking for big shove in the right direction.
Click to expand...
Click to collapse
TWRP will not work with older update-binary. Could you upload an example zip which does not flash ?
This is a test zip im playing with, all it does is extract busybox to /tmp, mount the three partition, make a folder on each partition then unmount.
Doesnt even get that far. Heres the part from recovery log, used CWM 6.0.5.3 from Oliver for this one.
Code:
-- Installing: /storage/sdcard0/test.zip
I:Cannot load volume /misc.
Finding update package...
I:Update location: /storage/sdcard0/test.zip
Opening update package...
Installing update...
[B]I:Using legacy property environment for update-binary...
I:Legacy property environment initialized.
I:Legacy property environment disabled.[/B]
E:Error in /storage/sdcard0/test.zip
(Status 0)
Installation aborted.
I:Cannot load volume /misc.
I:Can't partition non-vfat: /storage/sdcard0 (vfat)
Assuming the bold part you meant about older binaries, just wondering why its only the WFS that cant do it and how to get round it.
Appreciate the time guys!
Dude360 said:
This is a test zip im playing with, all it does is extract busybox to /tmp, mount the three partition, make a folder on each partition then unmount.
Doesnt even get that far. Heres the part from recovery log, used CWM 6.0.5.3 from Oliver for this one.
Code:
-- Installing: /storage/sdcard0/test.zip
I:Cannot load volume /misc.
Finding update package...
I:Update location: /storage/sdcard0/test.zip
Opening update package...
Installing update...
[B]I:Using legacy property environment for update-binary...
I:Legacy property environment initialized.
I:Legacy property environment disabled.[/B]
E:Error in /storage/sdcard0/test.zip
(Status 0)
Installation aborted.
I:Cannot load volume /misc.
I:Can't partition non-vfat: /storage/sdcard0 (vfat)
Assuming the bold part you meant about older binaries, just wondering why its only the WFS that cant do it and how to get round it.
Appreciate the time guys!
Click to expand...
Click to collapse
A status 0 would refer to a update-binary or updater-script failure. CWM now falls back to a legacy mode when an older binary is encountered. So I would recommend to use a newer binary. Or you could try an older CWM. TWRP does not at all works with the older binaries since 2.3. What recovery are you using in your other phones?
BTW what rom are you using ? Because at least in CM there is no /storage/sdcard , its just /sdcard . I don't know about stock though.
aWFSuser said:
A status 0 would refer to a update-binary or updater-script failure. CWM now falls back to a legacy mode when an older binary is encountered. So I would recommend to use a newer binary. Or you could try an older CWM. TWRP does not at all works with the older binaries since 2.3. What recovery are you using in your other phones?
Click to expand...
Click to collapse
That error would make sense then, reverting to an older binary.
From memory, Ive used these binaries myself on:
Desire
CWM 5x, 6x
EXT4 Recovery All versions
Desire HD:
CWM 5x, 6x
EXT4 Recovery All versions
Nexus 4:
CWM 5x (I think it was)
TWRP 2.x to latest
Nexus 7:
TWRP 2.x to latest
Samsung S2
Aman Ra I think its called
Transformer 101
CWM 5x (I think)
Nook Simple Touch:
CWM 5x
OUYA:
CWM 5x
Tesco HUDL
CWM 5x
Several Cheap Chinese Tabs with CWM 5x
And as far as I know they've been used on the rest of the ROMCleaner devices as well, but have no idea about the recoveries as I was on hiatus for some of them.
Sensation
Incredible S
One X
One S
EVO 4G LTE
HTC One (m7)
HTC One (m8)
GNex
TF201
Galaxy S3
Galaxy Note II
Galaxy S4
I remember we did a LOT of testing with updater binaries to find one that was compatible with as many devices as possible but at the time none of us had access to a WFS hence why we were never able to check with them.
We we quite surprised that this one worked with everything we tested and tbh I cant even remember where it came from and Its still running on everything we throw at it!
aWFSuser said:
BTW what rom are you using ? Because at least in CM there is no /storage/sdcard , its just /sdcard . I don't know about stock though.
Click to expand...
Click to collapse
I was using PA at the time, same error with CM11 though.
At the end of the day, the binary can be worked around. The romcleaner binary not working is (child status 4 error) cant!
Im beginning to think its definitely a recovery incompatibility, maybe the way it has to be compiled to run on ARM6 or maybe just particular to the WFS.
The romcleaner binary hasnt changed either and is running on the above devices as well.