yashsingh1/xdaforums huggingface dataset:
[HTC Wildfire S] heatherelane:
I haven't tried re-downloading it, I will do that right now. 9:23PM redownloaded and flashed another copy...still hangs at "opening update package..."

I used the Goldcard method from this thread: (google: 452087-tutorials-roms-team-marvelusc-everything-you-need it won't let me post a link because i'm new to the forum)

and you're welcome! :) I appreciate the time that experienced users take to help out people like me and want to make it as quick & painless as possible!

EDIT: i attached a zip of the recovery.log from CWM from one of the first times I tried to flash the ROM...don't know if it helps.[/COLOR]
[HTC Wildfire S] kalaker:
Thank you for that link. And if you would, just post back on how the re-download goes. Personally, I didn't see anything in the recovery.log, but maybe a more experienced user would.
[HTC Wildfire S] heatherelane:
still hangs at "Opening update package..."
[HTC Wildfire S] kalaker:
Are you downloading from your computer then putting it on your SD then flashing or are you using ROM Manager?

Have you tried any other ROMs? Try flashing CM7 (make a backup in Recovery first).

CM7 Link
[HTC Wildfire S] kalaker:
This build is pretty good. It has some MMS and WiFi issues, but until Sense 3.5, this was the only ROM I'd use. In fact, I'm using it right now. You'll need to flash the gapps package from Recovery if you do CM7 (which I'm sure you know, since you had CM7 before.)
[HTC Wildfire S] heatherelane:
awesome, I might just stick with this. I don't use MMS anyway...what wifi issues are there? I barely get any service in my apartment so I am usually on wifi here.
[HTC Wildfire S] kalaker:
I actually haven't had many Wi-Fi issues, but they've been reported. The thread can be found here. Usually I'll lose WiFi if the phone has been locked for awhile. A quick fix I'll do is Settings>Wireless & Networks>WiFi. Then I'll toggle it off then on and it'll work fine.

Did it flash or have you tried yet?
[HTC Wildfire S] heatherelane:
just downloaded, flashing now. it's currently on "Installing update..."

latest gapps is still 20110828?
[HTC Wildfire S] kalaker:
Hopefully it works! And yes, 20110828 is still the latest. If you need the download link:

http://goo.im/gapps/gapps-gb-20110828-signed.zip
[HTC Wildfire S] heatherelane:
it restarts in the middle of installing :( should I try a newer version of CWM? I'm on 5.0.2.8.
[HTC Wildfire S] kalaker:
What happens if you just reboot the phone? Is it the previous ROM or does it fail to boot?

5.0.2.8 is the latest official version for the Marvelc. I am using a not-so-stable touch recovery koush made before realizing Marvelc is mdpi.
[HTC Wildfire S] heatherelane:
It fails to boot :(. tried again and now it's hanging at "Opening update package..."
[HTC Wildfire S] kalaker:
Alright, let's try redownloading the recovery (http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvelc.zip). Then re-flashing the recovery.

Download that file.

Power off phone.

Reboot to HBOOT (Power + Vol. Down)

Choose Fastboot

Open Terminal/Command Prompt

fastboot flash recovery <path-to-file>

Where, of course, <path-to-file> is the actual path and don't actually put the angle brackets.
[HTC Wildfire S] heatherelane:
>< sorry...can you back up a few steps...I think I need to install your scripts first from your signature?
[HTC Wildfire S] kalaker:
If you do not have ADB and Fastboot installed on your computer, then yes, you will need to run those scripts.

Simply open Terminal (they're Mac- and Linux-only) and drag and drop the "ADB Install Mac.sh" into the window. Then hit enter.

Edit: Do the following ONLY if you get a permssion error.

If it says something about permission denied, type

chmod 755 <path-to-directory>/*
chmod 755 <path-to-directory>/*.*

Note, do not do the file, but the directory their in. For example, if they're on your desktop, do "chmod 755 ~/Desktop/Android/*".
[HTC Wildfire S] junxracr:
I had problems with koush recovery. So I've stuck with alquez unofficial recovery. No problems at all and I do a ton of flashing. It's better imho ;)
[HTC Wildfire S] heatherelane:
ok it installed no problem, no permissions error. but now I get this error...

hlane$ fastboot flash recovery /Users/hlane/Downloads/recovery-clockwork-5.0.2.8-marvelc.zip

sending 'recovery' (2014 KB)...

FAILED (status malformed (1 bytes))

finished. total time: 0.000s
[HTC Wildfire S] heatherelane:
urgh sorry pasted the wrong error. was in HBOOT before and wasn't paying attention. ran again in FASTBOOT USB

hlane$ fastboot flash recovery /Users/hlane/Downloads/recovery-clockwork-5.0.2.8-marvelc.zip

sending 'recovery' (2014 KB)...

OKAY [ 0.966s]

writing 'recovery'...

FAILED (remote: not allowed)

finished. total time: 0.967s
[HTC Wildfire S] kalaker:
Edit: I didn't see your most recent post. Just a second.

The "FAILED (remote:not allowed) is a problem. I had that issue when I was Ship S-OFF. Part of the problem is that HBOOT 1.06.0000 does not support a lot of fastboot commands.

The best thing to do would be to go with junxracr's advice and install Alquez's Unofficial Recovery. This a PG76IMG.zip. Put it on the root of your SD card and go to HBOOT. HBOOT will parse it and then you can install it (I don't remember the exact steps).

This should flash the recovery and not be an issue. If it gives you a "Security Flag" or "Secu Flag" error, you may upgrade your HBOOT.
[HTC Wildfire S] heatherelane:
never been so happy to see this little guy :D. i flashed Alquez's recovery and then installed CM7 & gapps.
[HTC Wildfire S] kalaker:
Awesome! That rocks! If you don't like CM7, there are several other ROMs out there as well as de-bloated stock ROMs and maybe Sense 3.5 will flash using Alquez's.
[HTC Wildfire S] heatherelane:
no, I love CM7 and I think I'll stick with what I know! I was having issues with internal memory on sense, even though I formatted cache (followed simon's directions) and got a2sd sdcachereset to work once in terminal emulator. what do I need to use in CM7?
[HTC Wildfire S] junxracr:
Congrats. Sense 3.5 is my rom of choice lately :)

You can move your dalvik to sdcard with a2sd. Plenty of room. Running Einstein's dust kernel at 825mhz. Ext 4.

I'm hoping for camara fix for cm7. I need to take those pics of my newborn baby :)
[HTC Wildfire S] heatherelane:
I liked using sense, just too much of a headache for me to get it to work...I think sometimes technology likes to test how much patience I actually have haha...
[HTC Wildfire S] kalaker:
A2SD is available, but you'll need to flash it. I used: http://xdaforums.com/showthread.php?t=715940 as this ROM doesn't have it baked in. Just flash it in recovery; it should work fine.

Oh! And I almost forgot, though. For CM7, you'll need to run HTC SuperTool v3 to root as this CM7 build is not pre-rooted. The tool can be found here:

http://goo.im/apps/frigid/htcsupertoolv3.rar

It is Windows-Only and requires the HTC Drivers (just install HTC Sync)
[HTC Wildfire S] heatherelane:
ok great thanks! will try these both now. I have HTC Sync installed from the first go around so hopefully this won't be too painful. ><
[HTC Wildfire S] kalaker:
Awesome! HTC SuperTool is pretty straight forward. It should be pretty problem-free.
[HTC Wildfire S] heatherelane:
ok I think I'm good? (time will tell...)

might be a n00b question...but can I restore apps from Titanium Backup from a different ROM? Or is it best to redownload? thanks :)
[HTC Wildfire S] kalaker:
I think redownloading would be the best thing to do.
[HTC Wildfire S] heatherelane:
ok thanks, that's what I've done in the past.

It seems like it takes a few times to boot, it'll loop from the white HTC screen to CM7 logo and eventually it will load. Do you know what might be causing this?
[HTC Wildfire S] kalaker:
No, I don't. Can you explain it a different way?

Is it a:

1.) HTC->CM7->HTC->CM7->Boot

2.) CM7->Wait for a long time->Boot

3.) CM7->CM7->CM7->Boot
[HTC Wildfire S] heatherelane:
I just realized that the camera doesn't work :( :( I use it frequently so I think I'm going to have to try flashing another ROM :(
[HTC Wildfire S] kalaker:
Oh! That's right! I forgot that.

The stock VM ROM by Team BlueRidge is pretty good, as well as the BlueRidge sense (if it'll flash). I've been testing most the Marvelc ROMs recently, so I'll report back with what I find once I test more of them.
[HTC Wildfire S] heatherelane:
it's a shame, because I'd love to test it out but I use my camera on a daily basis for my labwork, etc. I'm hopeful that BlueRidge sense will flash, I'm going to try it now and see what happens! I'll let you know.
[HTC Wildfire S] kalaker:
It is slightly disappointing. Simon said at one point an update may come later this summer, but I don't know if that still holds. BlueRidge should flash with Alquez, so best of luck!
[HTC Wildfire S] heatherelane:
got a bad download on deodex blueridge sense and now neither odex or deodex files are up. both say file not found :(
[HTC Wildfire S] kalaker:
You may give Sense 3.5 another shot (I can't find 2.1, either.)

http://goo.im/devs/simonsimons34/marvelc/simonsense3.5v2.zip
[HTC Wildfire S] heatherelane:
Got 3.5 to work with alquez's recovery. Sorry i didn't get reply sooner, been busy at lab.
[HTC Wildfire S] codegeek:
I installed all the apps I wanted before using App2sd to move my apps/data to cache, and it started me out with 117 MB of free space. I'm on simonsense3.5v1 by the way.

Also was going to suggest back tracking to 5.0.2.6 of recovery, but I see someone else already pointed you in the right direction on that one.

I'd be curious to know how 3.5v2 works for you and whether or not I should risk updating. I'm pretty happy with v.1.
[HTC Wildfire S] junxracr:
Restored backup of v1. Nuff said.
[HTC Wildfire S] gotts101:
Did you end up finding a fix to the "Opening update package" hanging problem?

I am having the same problem...

thanks
[HTC Wildfire S] heatherelane:
I flashed alquez's recovery and that worked.
[HTC Wildfire S] xVesica:
I never got this sense 3.5 to boot... D:
[HTC Wildfire S] HTC_Vince:
Not sure

Not sure if you have resolved this problem yet, but try downgrading your recovery. I had a similar problem and used alquez unoffical recovery. the file is below for it.
[Samsung Galaxy Gio GT-S5660] ze_p3dr0:
Hi, ive returned from a unofficial cm7.2 rom from here, to the stock one via odin. Now i cant connect my phone to any computer (tried on 4, all with kies, and the samsung usb drivers for mobile phones) and it always says unrecognized device. Even on downloading mode to reflash via odin the problem occurs.

Is it a issue related to the ext4formatter.zip file i flashed when doing the cm7.2 procedure?

Any ideas?
[HTC Vivid, Raider, Velocity] meatwad0222:
Just bought the plantronics backbeat go today and after 4 hours is am very impressed I had been looking for a decent pair of earbuds that where Bluetooth for a while and though the price was a oil steep (100 in att and online at the plantronics site ) for those looking for the same its well worth it....no cumbersome receiver attached
[Motorola Droid Bionic] cordripper:
So I just found a leaked screen shot of Verizon's upgrade schedule to ICS!

http://www.ubergizmo.com/2012/04/verizon-ic-update-schedule-leaked/

So the HTC Rezound should get the OTA next week on May 9th. The RAZR and RAZR MAXX will be getting the OTA in three weeks. But no mention of the Bionic... Oh yea, they decided to give us the .904 update while they finalized ICS for the newer phones. We just got shafted again.

Then again, its tough to know what is actually going on because they have to keep everything confidential. I doubt this would be case but if VZW and MOTO were having issues with ICS on the Bionic, I would have no problem giving them more time to make it right. But from what we've seen, it doesn't appear to be that innocent.
[Motorola Droid Bionic] silversonic1:
You do realize that we are a low priority because the phone isn't selling well, right? RAZR's the front-runner, making it a priority. We'll get ours by July, if we're lucky.

And yes, I am being a little pessimistic, but Motorola and Verizon need to step up their game already. Moto's making too many devices and Verizon's forcing bloat too much. That's what is slowing us down.
[Motorola Droid Bionic] saintsdx:
re

I don't understand what is really taking that long. Development will continue on the latest and greatest but that doesn't mean we should get the shaft. I picked the bionic over the thunderbolt because I like the slightly thinner phone and longer screen even though it cost more.didn't think I would be buying a dead phone in terms of development. I should have just got the razr

I have Rooted 904 update Safestrap dual boot eclipse 2.2
[Motorola Droid Bionic] ronaldheld:
My view is the Bionic is a phone they would prefer to forget. The Razrs are the hot phones so they get the priority. Maybe I woukd complain much more without ICS ROMs available.
[Motorola Droid Bionic] wickedgoat:
It's interesting that on Moto's site the RAZR's are all listed as ICS upgradeable but the Bionic is not.??
[Motorola Droid Bionic] cordripper:
There are ICS ROMs available for the Bionic. I've held off on flashing one because its my understanding that they are unstable and have missing features. Please correct me if i'm wrong.
[Motorola Droid Bionic] cordripper:
Yes it is:

http://www.motorola.com/Consumers/U...and-Services/Mobile-Phones/DROID-BIONIC-US-EN
[Motorola Droid Bionic] pyroemaniac:
"ANDROID 4.0 (ICS) UPGRADEABLE: WE ALL SCREAM!

Ice cream is cool. Ice Cream Sandwich is HOT. Needless to say, DROID RAZR is Ice Cream Sandwich (Android 4.0) upgradeable. You can find all the latest software upgrade news in our Motorola Support Forums. "

That is on the top of the bionics feature page.
[Motorola Droid Bionic] psychosilva:
it would be nice if they would just let us have it.
[Motorola Droid Bionic] silversonic1:
That's a pretty big oversight, mentioning the RAZR on the Bionic page like that... Now is that the mobile site only, or is it on the full site too?
[Motorola Droid Bionic] wickedgoat:
That's the full site. It says RAZR. Read the spec's on all the phones and Bionic does not have 'ICS Upgradeable'. I think we're getting swept under the rug.
[Motorola Droid Bionic] ROB281:
****ing awesome
[Motorola Droid Bionic] jmath679:
If we get swept under the rug I will demand a new phone. Part of the reason I bought this phone is because it was going to be updated with ics. I believe them reniging (sp?) on their word is sufficient reason for a phone replacement on vzw.
[Motorola Droid Bionic] cordripper:
Agreed
[Motorola Droid Bionic] HorsexD:
Went to Moto website and under specs for Bionic it says android 2.3 upgradeable to 4.0 so maybe u miss read :x

Edit: Heres Link http://www.motorola.com/Consumers/U...obile-Phones/ci.DROID-BIONIC-US-EN.alt#anchor
[Motorola Droid Bionic] lhkjohn:
Saw the same thing. Dunno where people are getting that we're not getting ICS from. If the thunderbolt and INC2 are getting it, that would be a travesty for the Bionic not to.
[Motorola Droid Bionic] pyroemaniac:
look under the features section of the bionic, it says Droid razor. I'm think we'll be lucky to get ICS by late summer/ early fall.
[Motorola Droid Bionic] HorsexD:
if you click on the motorola support forums link where it says that it takes u to a page explaining which devices are getting ics and the bionic among others is on that list but yeah :/ it will prolly be a while. maybe we can get lucky with cheesecake.
[Motorola Droid Bionic] arnshrty:
Guys why is this even a topic. It's been confirmed we are getting official ICS by several sources along with moto. The ICS source code was released a little over a month ago, that helped out the devs. We have a solid device for the price and we have devs good enough to keep us happy and get us through until mid to late summer when we get the real thing.
[Motorola Droid Bionic] brandogg:
ICS source was released 6 months ago. That doesn't help matters since we don't have an official release, an unlocked bootloader, or a real ICS kernel, however.
[Motorola Droid Bionic] smokedkill:
I agree. Also, name a moto phone that hasn't gotten at least one real upgrade. We will get ics. Don't panic. Just have to be patient.
[Android General] sensboston:
Good news for C# programmers (i.e. WP7 developers): Android ported on C#!

Some test results:

Read more at http://blog.xamarin.com/2012/05/01/android-in-c-sharp/
[Android General] rbrunner7:
Either brilliant or crazy

Like one of the commenters over at the original article said, this is either brilliant or downright crazy: Running Android through a Java-to-C# translator and benchmarking the results...

Their ports of the .NET framework to iOS and Android are a little closer to home and should in theory allow sharing of large chunks of code between WP7, iOS and Android apps.

However, watching this scene for already quite a while, I didn't notice this making real waves, with high-profile applications built in this way.

I personally think the risk-reward ratio isn't worth it: One the one hand, 3 apps for 3 OS for maybe 1.5 or 2 times the effort of 1 app. On the other hand, dependence on a product from a small company and a framework that had a near-death experience already when Novell cancelled their support for the project.
[Android General] sensboston:
In my opinion, that project has one HUGE cons: the product price. $999 is too much for individual developers and small companies (but they should be a primary targeted customers!) Bigger companies will prefer to hire Objective-C programmer(s) for iOS project and Java/Android guys for Android project(s).

Other stuff: Objective-C by default is faster than any CIL language, Android programmers have a better (and free) alternative to use industry-standard C++ via NDK. Also, Java codebase is significantly larger than C#; I saw too many C# projects ported from Java but no Java ported from C# :) Java is industry standard and I don't think Oracle vs Google fight will change something for regular developers.

P.S. And I agree: this project this is either brilliant or downright crazy :D
[HTC One X] vans88:
Hey got a noob question here...

I read this review (http://www.engadget.com/2012/05/01/htc-one-x-for-att-review/) on Engadget and i took me by surprise a bit. In terms of performance i dont understand how tegra 3 is beaten by a dual core? Is there a reason why?

Sorry if this has been asked before, tried to look but couldn't find anything.
[HTC One X] DANOFDANGER:
I wondered the same thing, i presume is a software issue with unefficient coding limiting the full power of the tegra 3.
[HTC One X] thegregulator:
The dual core in the AT&T One X is a Snapdragon S4, which more similar to the A15 chip architecture. As I understand it, the A15 chip architecture is superior than the A9. Realistically, I think it would be very difficult to tell the difference between the two in real world usage. This is one of those choices where you simply can't go wrong!

As far as dev support goes, I think the Tegra 3 version will have more widespread development, which was the main reason I chose this over the One XL. Well, that and the 32gb of built in storage, especially with the absence of a micro sd card slot.
[HTC One X] hello00:
you can't really tell the difference between them two..the tegra has a growing library of optimized apps and games putting the extra features to good use..the average user isn't going to notice a difference between an S4 and tegra 3 device in real world non gaming situations and in gaming situations the tegra 3 will steal the show..
[HTC One X] vans88:
Is it also due to tegra 3 not as well optimized on android as snapdragon ?
[HTC One S] cannondale0815:
EDIT: I solved my own problem. Scroll down to post #8 for the solution.

My problem was that my phone (T-Mobile USA HTC One S) would not boot into ICS anymore, but I was still able to get into recovery (CWM), yet I had no access to the sdcard ("unable to mount /sdcard").

Post #8 below tells you how you can restore access to the sdcard in CWM so that you can push a ROM zip file to the sdcard via adb.

-J
[HTC One S] archie53:
Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
[HTC One S] cannondale0815:
Unfortunately I didn't have the foresight to make a nandroid backup. My previous phone was a Samsung Galaxy S 4G, which, like most Android phones, has a removable SD-Card that stuff can be copied onto (and then flashed). Not so here obviously.

Is it even possible to push files to the sdcard using the method I tried when in CWM?
[HTC One S] joshnichols189:
When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?
[HTC One S] cannondale0815:
It just got worse. I got the idea to format all partitions (data, system, cache, sdcard) through CWM, and now CWM can't even mount /sdcard/ anymore...
[HTC One S] zylith:
I had to do the same thing:

adb push "NameOfFile.zip /sdcard

then go to install from zip.

Look on sd card and it will be there.

I always rename the zip files to there can be less errors.

you can also do

adb shell pull "nameOfFile.zip /sdcard

make sure the zip file is where your adb and fastboot is
[HTC One S] LuckyMethod:
My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?
[HTC One S] cannondale0815:
Yes, I just fixed my problem yesterday after some serious trial-and-error.

1) Use the All-in-One-Kit and flash your recovery back to stock

2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.

3) Go back to the all-in-one-kit and flash a CWM recovery version again.

4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.

5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:

adb push utb.zip /sdcard

6) While still in CWM, flash the zip.

The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.

Good luck!

-J
[HTC One S] shootind5nukes:
If that doesn't work an easy fix is boot into bootloader, goto fastboot and use "fastboot flash boot boot.img" and so fouth. In the dev section I seen a stock tmobile naindroid. Download it and you'll have your data.img and boot.img. You should be able to flash them without needing to push to /sdcard. letme know how it works

I know you fixed this already just thought this still might help
[HTC One S] LuckyMethod:
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.
[HTC One S] cannondale0815:
Happy it worked for you. Took me several days to figure this out :)
[HTC One S] j3.cole:
I too formatted my sd card :( but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
[HTC One S] cannondale0815:
Thank you. I changed the title and original post to make it easier for people to find this thread.
[HTC One S] mrmoretti:
I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...
[HTC One S] mrmoretti:
IT WORKED! This thread should be made sticky! I'm sure a lot of users who have HTC One S with built-in SD will have the same issue when mucking about with their phone. Thank you!
[HTC One S] cannondale0815:
Bump, as too many people are having this problem.
[HTC One S] mrroey:
THANK YOU SO MUCH! THIS WORKED PERFECTLY!

This should definitely be included in a stickied guide for people like me who have managed to corrupt their recoveries.
[HTC One S] AttachedSilver:
Got it after several tries
[HTC One S] yasir_jan87:
hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.
[HTC One S] cannondale0815:
Try to shorten the filename, i.e. "rom.zip".

And try this slightly modified command instead:

adb push rom.zip /sdcard/rom.zip