yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Tanarif:
Massive apologies if this isn't the correct section, I had a look across the board and couldn't really see where else to put it.

Essentially I have the code to a project, it loads in eclipse and I have everything installed and experience with working in eclipse. But lately the emulator just refuses to load the project. Usually I get a forced close message, or a disconnection etc. If anyone could perhaps get onto a live chat with me, or teamviewer, and help me out - I will gladly pay you $20 per hour of your time as I need this done asap.

This is what I get when I run the the project, if you wish to help out for free then that is also much appreciated.

[2012-02-08 20:46:46 - GoalManager] ------------------------------

[2012-02-08 20:46:46 - GoalManager] Android Launch!

[2012-02-08 20:46:46 - GoalManager] adb is running normally.

[2012-02-08 20:46:46 - GoalManager] Performing com.android.sample.goalmanager.LoginActivity activity launch

[2012-02-08 20:46:46 - GoalManager] Automatic Target Mode: launching new emulator with compatible AVD 'droidX2'

[2012-02-08 20:46:46 - GoalManager] Launching a new emulator with Virtual Device 'droidX2'

[2012-02-08 20:46:50 - Emulator] emulator: emulator window was out of view and was recentered

[2012-02-08 20:46:50 - Emulator]

[2012-02-08 20:46:50 - GoalManager] New emulator found: emulator-5554

[2012-02-08 20:46:50 - GoalManager] Waiting for HOME ('android.process.acore') to be launched...

[2012-02-08 20:46:51 - GoalManager] emulator-5554 disconnected! Cancelling 'com.android.sample.goalmanager.LoginActivity activity launch'!
[General Questions and Answers] nrlp:
Hi. Can someone please help as I'm new to this this and would very much like my phone to work again...

My Defy kept restarting approximately 5 seconds after starting up. Without being able to access any settings I tried a factory reset via the on button / volume down button. I'm not sure how long this should have taken but decided after a few hours of nothing more than a yellow dot moving across the screen that it wasn't working! Button presses / screen taps had no affect so I pulled the battery.

On powering it up it now either gets as far as the Moto Blur or T-Mobile logos but just hangs there. Further attempts to factory reset give the same result as the first time.

I've noticed two lines of text when accessing the reset screen which read 'E:Can't open /cache/recovery/command' and 'E:Can't open /cache/recovery/caller'. I think these were present at the first attempt but I'm not totally sure of this.

In case it's relevant the phone shipped with Eclair, I changed this to Froyo using the Motorola software upgrade some months ago, it had been working fine since apart from not saving photos (?).

Aplolgies for the essay. Can someone please help?
[General Questions and Answers] wyxpark:
I have same problem now.....but I didn't find any answer yet. I thought i could be the hardware
[General Questions and Answers] blackbuddha:
Could you try to boot into bootloader then use RSDLite to flash the original SBF to your phone from there? I used to do that in the past with my Milestone.
[XPERIA X10 Q&A, Help & Troubleshooting] elhainero:
please i need to know is posible do dualboot in xperia x10 baseband .71 and Miui rom installed?
[XPERIA X10 Q&A, Help & Troubleshooting] iridaki:
Nope, sorry! :o

iR¡D@k!* via Tapatalk
[XPERIA X10 Q&A, Help & Troubleshooting] NikitoGR:
So... Is it confirmed that there isnt any way to get the dual boot feature in x10i?:( ****! I could have ferarom and ics in the x10!
[HTC Wildfire S] Tigger31337:
Okay, silly question here:

(First of all, YES, I did a brief search through the forums for this exact question. Couldn't find an answer.)

Background: I am a ROM junkie (but a newbie, I admit). I have flashed and re-flashed

EVERY ROM on this site

(and others) on to my HTC Wildfire S (rooted, but S-ON). Soon, I will release a "report" with all of my findings, comparing each ROM against each other, etc.

With that, I am *quite comfortable* flashing ROMs and tweaking them afterwards. What I do not know is whether it's possible (after flashing a ROM) to subsequently go back an upgrade ONLY the Android version (from 2.3.3 to 2.3.5, for example).

I'm aware of the OTA updates that a "normal" user would be entitled to. But, with a customized ROM, it seems like I am exempt from those upgrades.

N.B.

If anyone replies: "Just find a modified ROM that runs the version of OS you need, and then flash that onto your phone!"... that is not an option (...unless it's the ONLY option!) :)

If you don't know, don't guess. (Sorry, but I've seen some of the "quality" answers that come back from certain users who are just trying to up their post count, I assume.)

Thanks in advance, to all those who answer.

- Anthony
[HTC Wildfire S] theq86:
It is not possible, because the system image (the OS) IS the rom. In fact, if you change anything in your system partition, you change the ROM.

there are no different memory locations for ROM and OS.
[HTC Wildfire S] intel007:
You could download an official rom that contains 2.3.5 here:http://xdaforums.com/showthread.php?t=1074445

The rom is the os mate.
[HTC Wildfire S] Tigger31337:
Thanks theq86,

So, to be clear, if I am running a custom ROM that happens to be GB 2.3.3, there is no way for me to apply a GB 2.3.5 "upgrade" (if such an animal exists)? The goal here is to leave the rest of the ROM (apk's, settings, internal data, etc.) intact.

Well... that's a tad disappointing, but thanks so much for your answer.

- Anthony
[HTC Wildfire S] Tigger31337:
Oh yeah? And do what with it?

(Go back and read my "N.B." from my original post.)

p.s. The ROM is

not

the OS. You're not the first person who's said this, though.

- Anthony
[HTC Wildfire S] nerotNS:
You can keep the apks and data(but not settings) if you don't wipe.But that can cause ptoblems on some roms.
[HTC Wildfire S] Tigger31337:
Thanks nerot, that's kinda the path I was heading down myself (install, without wipe).

The only thing is that I don't wish to install a ROM over another ROM. I was hoping to somehow sneak just a GB upgrade (into an update.zip, let's say) and then flash that through the recovery menu. That way (in theory) the only thing that gets refreshed in my current ROM are the actual Android OS files.

[Hint: Think of the way you would perform an OS upgrade in the Windows world... one does not have to flash an entire Windows image over the existing one. One could simply upgrade the OS, while keeping applications and settings intact. ]

I see no reason, in principal, why this isn't possible with Android and, quite frankly, I'm surprised some clever XDA hacker hasn't done it already.

- Anthony
[HTC Wildfire S] nerotNS:
I dont think it is possible to use a update.zip on custom roms because they are modified and even if it was possible i think it would be easier for the developer to just compile the whole rom again.
[HTC Wildfire S] b02:
nobody wants to bother, so find the updated version of the rom you wish to install, make titanium backup of your apps, and move on ..
[HTC Wildfire S] Tigger31337:
Wow, what a very clever answer. :confused:

Keep in mind I'm not asking what YOU would do; I'm merely asking if something is technically possible.

While it would be nice to find "the updated version of my ROM", it does not exist (because it's a heavily customized version of an already heavily customized version.)

It's perfectly tweaked the way I like it (and yes, I've been backing up the ROM along the way)... so now, my question is (as before): is it POSSIBLE to overwrite ONLY the Android files, thus giving me a newer version of the OS?

Don't worry about whether or not it's something YOU would do... that's missing the point. And don't worry about whether or not certain apps would break after I perform the upgrade... that's my problem. (I suspect that going from 2.3.3 --> 2.3.5, or 2.3.5 --> 2.3.7 would not cause my phone to explode.)

Simply:

is it POSSIBLE to perform an OS upgrade on an EXISTING ROM?!

I've heard one answer so far (of "No") but it seems like that was a "most people don't do this" or "it's not practical"-type of answer.

I'm looking for someone knowledgeable enough (because I'm not) to say whether or not it's technically possible. For me, I don't see why it wouldn't be. If someone can confirm it, then I'll get to work and try creating a flash package to get the job done.

Danke,

- Anthony
[HTC Wildfire S] Tera Tike:
A custom ROM (Read Only Memory) as it is so often referred to, is the OS (Operating System) packaged to be flashed into the ROM, which can include the kernel, system, boot image and or other file like data, radio etc.. This is why it is loosely called a custom built ROM.

Yes, it is possible to JUST flash the upgraded files into the OS in the ROM.

The issues most have is when updating some main system files like the systemiu.apk or framework.jar is the /data/data setting files. If those file are not compatible with the newer files you flashed you will get a boot loop issue. I know this since I am modifying my own OS this way from time to time.

Now I am not a expert or a have advance knowledge but I know I what I have done, and the manufactures also do the same with their OTA(Over The Air) updates.

-Mark
[HTC Wildfire S] theq86:
The answer IS no.

The files of the rom are the same files of the os.

you can upgade the only the os, but ...

you will not able to start the upgraded os unless you wipe caches and data partition

So you need to:

- backup your apps

- backup your pim data

- upgrade the os (or ROM, whatever term you like more)

- recover pim data

- recover apps

- do the phone settings

having os upgraded and data not wiped is an inconsistent system state.

the only way to upgrade as you like is done by a FOTA update. From 2.33 to 2.35 all the settings and data were kept.
[HTC Wildfire S] Tigger31337:
...and so we have a DIRECT contradiction:

One user says it CAN be done; one says it CAN'T. :rolleyes:

theq86, although your answer is detailed, here is why I'm having a problem accepting it:

- First, you keep equating OS to ROM. A customized flashable ROM is more than the OS. For example, a ROM can be deodexed, overclocked, embedded with system apps, themed, tweaked, yadda yadda yadda. The OS is merely one component of a ROM package. Please stop equating the two.

- Second (as you already identified) it actually IS possible to do an OS-only upgrade because we are able to receive those types of upgrades today (in the form of OTA updates).

That's my difficulty. Surely, if my phone can handle a package that's designed to upgrade ONLY the OS (say, from 2.3.3 to 2.3.5) then it's just a matter of finding out how that upgrade is packaged and delivered (zip flash, update.zip, whatever) and then re-creating that process offline so that I can apply the upgrade manually.

Here's another description, so you get the picture: Imagine you absolutely LOVE a custom ROM called TiggerROM. It's the best thing you've ever seen in your entire life (you don't get out much) and it happens to be based on GB 2.3.3. Now imagine the author of your custom ROM gets hit by a bus and dies a horrible, twitching death. (There will be no more updates to TiggerROM, sadly). A week after his funeral service, GB 2.3.5 has been released. Your other friends (who have NOT modded their phone) are freely getting the 2.3.5 upgrade OTA, and it does not affect the rest of their phone (i.e. they do not have to re-install all their apps, they did not lose their wallpaper of their pet dog, they did not have to reconfigure their WiFi and Google accounts, etc.) Now, you are saying to yourself, "I want that too! I want to keep my current ROM+settings+tweaks and all I wish to do is upgrade Android from 2.3.3 to 2.3.5" (because you're just the kind of guy who likes to have the latest OS).

...so, what would

YOU

do?

- Anthony
[HTC Wildfire S] nerotNS:
If you put it that way it is impossible to do that because you don't know what was edited in the custom rom and os compared to the stock ones it would cause instability an probably boot loop or the system not starting at all.Its almost like you want to upgrade from custom froyo to stock gingerbread using a ota.So the finnal answer is no.
[HTC Wildfire S] nerotNS:
And as for keeping all the other stuff i think that during the update it's all temporarily backuped somewhere(probably the sd card) and then restored.But i think it depends on the update itself for example there is no need to delete apps and google accounts for a Wi-Fi fix but it is necessary to do that when upgrading from froyo to gingerbread(unless my backup theory is correct)
[HTC Wildfire S] theq86:
you can not separate os and rom the way you do.

see, android is an OS that has a lot of dependencies. among these dependencies there are apks, themes and all the other stuff of the ROM.

it is sure possible to only upgrade the minimal dependencies that allow you to update your os and keep the rest (possible like: it's possible to fly)

the problem is: everything providers release are ROMs and no OS diffs. So what you want to do is very impractible.

no one does and want to struggle with those OS diffs. If you want to do, feel free. But you are the 1st one here.

so, yes it is possible, as it is possible to catch a fish with your hands. but the amount of work is much more than it it practicable.

Anyway, I got what you want. And the best thing you can do now:

- take a stock rom

- import it into a rom kitchen

- add your holy stuff

- cook your new rom and be careful not to be caught by a bus, because then the next one will arrive here crying that is favourite rom developer has died.

Try to only update the needed files would take you months of work just to find out what you can update.
[HTC Wildfire S] Tigger31337:
No, no, no.

In the examples I've been giving, I've always said that the change is minimally incremental (going from 2.3.3 --> 2.3.5, or 2.3.5 --> 2.3.7, for example). In theory, I'm sure you could go from Froyo to GB, but that's never an example I gave (nor something I'd want to do in real life). The bigger the version jump == the bigger the risk!

I am saying, (to repeat, yet again) that I would be working off a ROM that was GB 2.3.3 and then (somehow) apply a patch that would upgrade the bare minimum to get that Android up to 2.3.5. No other parts of the ROM would be touched. Whether or not **** breaks after the OS upgrade - well, that would have to be dealt with after the fact. I suspect not much would break, but that's not my question/concern right now. I'm saying can it be done TECHNICALLY. Is there a delivery method to apply an OS upgrade patch to a ROM. Don't worry about boot loops or broken apps... that's my problem, not yours.

And, if such an OS upgrade zip doesn't exist, then why not? Are they hard to make? Has anyone tried? Wouldn't such an update be HUGELY beneficial to the custom ROM community?

- Anthony
[HTC Wildfire S] Tigger31337:
Okay thanks. I think I'm getting the sense that it's just too much trouble than it's worth.

Thanks so much, everyone who replied.

I guess we are stuck in the hands of the ROM chefs (unless we take the time to learn to cook ROMs ourselves :-)

Thanks again, take care!

- Anthony
[HTC Wildfire S] Nicknoxx:
Yes, it's technically possible. BUT you'll need to get whoever made the ROM you like to provide another ROM with the Android upgrade already in it. This may not be an insignificant task.
[HTC Wildfire S] Tigger31337:
Yes, but that's just another way of saying "you'll need to flash a new ROM" which is what we're trying to avoid here (because, by flashing new ROM, you'll lose everything - embedded apps, tweaks, themes, Link2SD data, etc.)

We're trying to keep our existing ROM and just change ONLY the Android version (from 2.3.3 to 2.3.5 for example, not a major version change).
[HTC Wildfire S] b02:
tehnically it is possible since when you install any rom, and then you want lets say data2sd, you go and flash a flashable zip ... that is a sample of updating a rom(os).. in a similar way you can do update, but there are some tricks... since this is ADDING something to rom, and in some case it can be CHANGING some of the files, and there it gets tricky i guess... and thats why some of the users i guess told you that it is not possible...

and rom and os are the same... u said one can be deodexed clocked and so on ... that is the same stuff like on lets say bios, some bios is protected and it cant clock the cpu, BUT you just change it to new one that allows the same thing to be done...

rom is actually the os with added features, but you are still running it, arent you :) (well not exactly you)

so making that update depending on what you want to do is possibly impossible :D but that implies that it is also possibly possible ;)

thats why there is an app called titanium backup... it gets your work that you want to avoid, to the minimum.
[HTC Wildfire S] Tigger31337:
Yeah... I'll be honest, I couldn't make heads or tails of your reply. :)

Suffice to say, I've moved on... so we can consider this thread closed.

(If it helps, however, I was not talking about adding extra bits to the ROM after it's flashed... that's child's play. I was asking what I thought was a simple question: whether it's possible to modify ONLY the Android OS after flashing a ROM. Apparently, the question has caused more confusion and grief than anything else... so skip it and let's move on.)
[HTC Wildfire S] kagevazquez:
Like just adding a few security patches on windows? Just basically changing/adding/removing a few files?
[HTC Wildfire S] scott_doyland:
Tigger,

You ask for guys opinions and when they reply you tell them they are wrong so i assume you already know the answer in that case so why ask.

You could maybe update certain OS tye files to perform an upgrade and leave all the other files as they are and i would guess this is how a a FOTA works. But with a custom rom you would probably find the OS files have had changes made and updating with stock files would break the custom rom or remove some of its customisation.

Regards

Scott
[HTC Wildfire S] b02:
just like you dont know what i wrote, thats how we cant understand what you want .... ;)
[HTC Wildfire S] Tigger31337:
Yes, similar to that analogy.

In effect:

- you start with a stock Android 2.3.3 ROM

- you then obtain stock Android 2.3.5 ROM

- you analyze the differences between the two, to find out which files are changed/added/deleted (trivial task)

- you capture JUST THOSE DELTA CHANGES and package them all into a .ZIP file (for example) called delta.zip

- the chef cooks a ROM based on 2.3.3 OS (cooking a ROM includes all the other tweaks and crap that get to the OS)

- then you somehow apply the delta.zip file (I dunno how one would do this. Flash the .zip as you would a normal ROM? Apply it as an "update"? I dunno what the difference is. I assume one overwrites the entire ROM whereas one just applies "on top" of it.) This step is the crux of my question.

- Once it's flashed, you go back in and see what broke (hopefully, little to none) and that determines success or not.

Maybe this works, maybe it doesn't. I'm saying it's worth it to try, because that delta.zip can then be applied to MANY other custom ROMs (essentially, any ROM that uses GB 2.3.3!)

Get it?

Cool.

- Anthony
[HTC Wildfire S] nerotNS:
Well since you put it that way then from the technical side i think it may be possible but it's a lottery what would work and what wouldn't.
[HTC Wildfire S] scott_doyland:
The problem is that the custom ROM may have had changes made to "OS" files (for want of a better name).

For example in 2.3.3 and 2.3.5 stock there is file called fileA. In 2.3.3 it contains a string such as 'xxx'. In 2.3.5 stock it contains a string such as 'yyy'. So in your scenario you would find this file is different and therefore decide to overwrite the custom ROM fileA with 'yyy'.

But what if the ROM developer had already updated fileA in his custom ROM and it now contained 'aaa'.

You would then overwrite this customization with 'yyy' and be in a mess.

Windows is different, the files being upgraded wont/shouldnt have been customized, you cant access the Windows source code and build your own 'customization version'. The files being updated will be guaranteed to still be the 'official' windows files with no unathorized changes.

What you are asking to do is like taking ubuntu linux and trying to update it using linuxmint. They are similar but its not gonna work.

Scott
[HTC Wildfire S] Tigger31337:
Your logic is flawed.

It is true that I asked folks here a question (because I don't know the answer).

It is true that some of them replied with erroneous/irrelevant answers.

It is true that I made them aware of their unsatisfactory answer.

But from that, it does NOT follow that I already know the answer to my question in advance.

So, you're probably not going to like this but, "you're wrong". :-)

Listen, on my VERY FIRST post, I asked people to please not reply with a "all you need to do is apply a new ROM" answer, because that is missing the point. It shows you didn't understand the question and you're wasting everyone's time. And, like I also say in my first post: I'm embarrassed to have to make such a disclaimer but I've seen some of the "quality" responses that come back from some trigger-happy "experts" here. I just wanted to weed those folks out.

Sure enough, less than ONE HOUR later, I get a reply telling me to do just that. *doh!*

Then, I get a few replies like "No, because the ROM is the OS". Not only is that false, but I'm not sure what I'm supposed to do with that information. It's not exactly helpful. Again, it tells me that the wrong people are answering.

At this point, I don't see why I can't just say, "sorry guys, you're wrong" or "you misunderstood the task" and then proceed to give clarifications (upon clarifications). But, if you feel I did anything wrong, then quote the post # and tell me what you would have done differently.

I think, in the end, the facts speak for themselves: we have users here who still say it CAN be done and some who say it CAN'T. I'm not entirely satisfied with the answers, and I hope you can see why. I'm leaning more towards the "it can't be done", but that's only because no one has been able to provide enough evidence that it CAN be done! In any case, as mentioned several times, I am willing to let the thread die.
[HTC Wildfire S] b02:
i hope you guys will make it, since i would say now, no joking and stuff. it is possible... well how will you do it ... we will see ... i guess you will get on it ?
[HTC Wildfire S] Tigger31337:
Correct.

It's my understanding that this is EXACTLY how the FOTA updates work, which is why I used that in an example. Folks who receive a FOTA update, in effect, receive an upgrade ONLY to the OS files. I don't remember my wallpaper, apps, themes, tweaks, settings, WiFi info, and Google account all going down the tubes when I received my FOTA update taking me from GB 2.3.3 from 2.3.5. It works (somehow).

That tells me that it should, in theory, be POSSIBLE to recreate this process such that we can all enjoy an "offline" version of this OS upgrade. Perhaps one that took everyone's custom ROM from GB 2.3.5 to 2.3.7, for example. Wouldn't that be just swell?

Methinks so.

The only way the custom ROM would break (in the way you describe) is if the chefs are making changes to the actual core OS files. I'm not entirely sure they are (any experts wanna chime in here?) Overclocked kernels may be the exception.

I'll put my cards on the table right now and say that if anyone "cooks" up an OS-only update zip file in this manner, I am willing to apply it to my custom ROM to see what happens.

- Anthony