Related
Hey guys. I was thinking of Rooting/Flashing my Incredible S, but have a couple of questions first?
1. If I Root/Flash, can I go straight back to stock firmware without any Goldcard or anything?
2. What's the best Sense 3.0 Rom with good battery life?
Thanks guys
First: there is always a chance that something goes wrong. But as you read in different posts, that's rarely the case.
And second: there is no "best" Rom. Take a look at some Roms and decide for yourself. I would recommend Revolution HD But only because I haven't tried anything else yet. I assume that other ROM can be better or worse.
Sent from my HTC Incredible S using XDA App
revolution hd isn't sense 3.0 like he asked though (although I definitely agree it is the best rom on here)
tobdroid said:
First: there is always a chance that something goes wrong. But as you read in different posts, that's rarely the case.
And second: there is no "best" Rom. Take a look at some Roms and decide for yourself. I would recommend Revolution HD But only because I haven't tried anything else yet. I assume that other ROM can be better or worse.
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
Hi.
Thanks for the reply, but I wasn't asking if anything went wrong, I was just asking if I'd be able to flash an RUU Over a custom ROM, or how I could go back to stock firmware from a custom ROM
Also, is this guide the one for windows that I could use to Root/Flash? http://forum.xda-developers.com/showthread.php?t=1137008
It is possible and easy to use sense 3.0 with revolution. Anyway, I don't know any reason why it wouldn't be possible to flash back to a stock Rom.
BTW: the link you posted is the same guide that worked for me.
Sent from my HTC Incredible S using XDA App
Brilliant
One more thing, has anyone got the link to this Revolution Sense 3.0 ROM? Can't find it in the Android Development section.
http://forum.xda-developers.com/showthread.php?t=1088498
There you go. Second post.
Sent from my HTC Incredible S using XDA App
tobdroid said:
It is possible and easy to use sense 3.0 with revolution. Anyway, I don't know any reason why it wouldn't be possible to flash back to a stock Rom.
BTW: the link you posted is the same guide that worked for me.
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
?
only the lockscreen and weather, though you are still on sense2.1....
Hmm, what's the battery life like on Revolution?
I'm looking for Sense 3.0 and hopefully Improved or pretty much the same battery life I have on stock
(I'd prefer an actual Sense 3.0 ROM to get the Homescreen Transitions)
JccageX2 said:
Hmm, what's the battery life like on Revolution?
I'm looking for Sense 3.0 and hopefully Improved or pretty much the same battery life I have on stock
Click to expand...
Click to collapse
battery life is great....
it is the best rom on here imo.
like I said though it is sense2.1 (though I think sense 2.1 is better. smoother and less of a resource hog )
if it is imperative you have sense3, try virtuous unity
The battery life is at least the same. The developer says its better but I don't think so. Since you are going to root it anyway you can make use of some more tutorials on how to improve your battery. You will find them in the forum.
Sent from my HTC Incredible S using XDA App
scoobysnacks said:
battery life is great....
it is the best rom on here imo.
like I said though it is sense2.1 (though I think sense 2.1 is better. smoother and less of a resource hog )
if it is imperative you have sense3, try virtuous unity
Click to expand...
Click to collapse
Okay, thanks for the help guys
I'm still un-sure if I should Root and Flash yet, so... yeah. But thanks for the help
JccageX2 said:
Okay, thanks for the help guys
I'm still un-sure if I should Root and Flash yet, so... yeah. But thanks for the help
Click to expand...
Click to collapse
I would you really have nothing to lose
THIS IS ONLY FOR DEVELOPERS. DO NOT ATTEMPT TO FLASH THIS AT ALL. YOU HAVE BEEN SEVERELY WARNED.
Device specs: http://www.phonearena.com/phones/HTC...7037/fullspecs
Enjoy
RUU_GOLF_U_ICS_40A_HTC_Europe_1.35.401.1_Radio_10. 08.98.09H_1.05.98.08M2_release_260338_signed.exe
RUU_GOLF_U_ICS_40A_HTC_Europe_1.45.401.1_Radio_10. 08.98.09H_1.05.98.11M3_release_262024_signed.exe
thanks to jmztaylor
http://forum.xda-developers.com/show....php?t=1658056
Hello developers will be possible that our Sense HTC Wildfire may have ICS?
Porting sense 4 from the original desire C ruu: Not possible
Porting it from other ARMv6 devices: Possible.
I know the hero and WFS have both got it booting. So if you want to investigate into porting it. Go ahead.
I think that the phone name is desire c.... However our best bet is to wait for a port to an arm6 device (there is a work in progress in wildfire s forum) because desire c is arm7 and a port would be very difficult..
elia222 said:
I think that the phone name is desire c.... However our best bet is to wait for a port to an arm6 device (there is a work in progress in wildfire s forum) because desire c is arm7 and a port would be very difficult..
Click to expand...
Click to collapse
I think it was going to be called the Wildfire C, but then HTC renamed it to the Desire C. To make it seem like a premium device on a budget. (I guess). The WFS thread is a mess of flaming and trolling, and its been closed. So any updates won't be going on there. Although, someone managed to shrink the RUU down enough to fit the WFS partition sizes.
http://www.xatakandroid.com/moviles-android/htc-golf-asi-sera-el-sucesor-de-la-gama-wildfire
it is impossible, haha
tathanhlam66 said:
it is impossible, haha
Click to expand...
Click to collapse
Nothing is impossible, that's how we've got sense 2.1, sense 3.5, gingerbread and ICS on our phone. Once it gets ported to another ARMv6 device, we can work from there.
Sent from my HTC Wildfire using xda premium
somebody check it ruu?
Hi all,
The thread was locked indeed but we are now discussing the ROM on the leaked ruu thread. We have it booting to boot animation however audio/power is causing dalvik to fail, and causes a bootloop.
You could always look at our github to see what we have changed/added/improved/fixed. We will be doing this for the marvel (Wildfire S) and as soon as it boots we will inform you asap.
We are looking for a bit of help so if you see something obvious that we have missed then send us a pull request over github.
Sent from my HTC Wildfire S A510e using xda premium
how we can run this without a kernel 3?
someone should port drivers or create them
and this phone is too old,i think noone will do something like this
it s too difficult
just think this: desire s has a kernel 3 and sense 4 is working fine,but it has A LOT OF problems(crash,freeze,semi-functionl things)
i don t think our phone can support it with sense,we at least should have a fully working cm9 first
i think
benjamingwynn said:
Hi all,
The thread was locked indeed but we are now discussing the ROM on the leaked ruu thread. We have it booting to boot animation however audio/power is causing dalvik to fail, and causes a bootloop.
You could always look at our github to see what we have changed/added/improved/fixed. We will be doing this for the marvel (Wildfire S) and as soon as it boots we will inform you asap.
We are looking for a bit of help so if you see something obvious that we have missed then send us a pull request over github.
Sent from my HTC Wildfire S A510e using xda premium
Click to expand...
Click to collapse
I've been following the thread in the WFS dev section. Will replacing libs from sense 4.0 with CM9/AOSP Libs solve any issues. Or have you already tried that? Could it be a conflict between Beats Audio and the power management driver? Would you have to sacrifice beats to get it working?
Justice™ said:
I've been following the thread in the WFS dev section. Will replacing libs from sense 4.0 with CM9/AOSP Libs solve any issues. Or have you already tried that? Could it be a conflict between Beats Audio and the power management driver? Would you have to sacrifice beats to get it working?
Click to expand...
Click to collapse
Yeah we have replaced the libs, and yes we may have to sacrifice beats audio, although we could also used modified beats libs that were ported to AOSP, but i'm not sure that would integrate it with the onboard beats on/off system :/
Even if we were able to make this possible for our device, it would be unbearably laggy and slow. In my opinion its not worth doing it although its not bad trying. My opinion
rayven18 said:
Even if we were able to make this possible for our device, it would be unbearably laggy and slow. In my opinion its not worth doing it although its not bad trying. My opinion
Click to expand...
Click to collapse
It depends. While ICS can suffer from some slowdown on our device (Atleast at stock clockspeed). It is still usable and can still perform well. As we've seen with Sense 2.1 Gingerbread on the wildfire. It is very fast. And I mean, as fast as stock froyo sense. Which is nothing like CM7 is. So maybe Sense 4 will be even fast and optimized?
Sense 2.1 is not fully working
And ics need a kernel 3
And we don t have enought ram to run this
so it work or don't work?
kylon said:
Sense 2.1 is not fully working
And ics need a kernel 3
And we don t have enought ram to run this
Click to expand...
Click to collapse
You don't need a 3.x kernel to run ICS at all.
benjamingwynn said:
You don't need a 3.x kernel to run ICS at all.
Click to expand...
Click to collapse
you need it for fully working camera,wifi tether,hotspot,bluethoot and stability
anyway as i said we need more ram,wildfire c has at least 450 mb aviable
kylon said:
you need it for fully working camera,wifi tether,hotspot,bluethoot and stability
anyway as i said we need more ram,wildfire c has at least 450 mb aviable
Click to expand...
Click to collapse
Well. Clearly we don't. Because we have ICS with Camera, Bluetooth, WiFi-Tethering working on a 2.6 kernel. Besides, we can use MTD partitions if we don't have enough for the rom. Because we have 512mb of rom. So we can allocate that with MTD partitions.
kylon said:
you need it for fully working camera,wifi tether,hotspot,bluethoot and stability
anyway as i said we need more ram,wildfire c has at least 450 mb aviable
Click to expand...
Click to collapse
Agreed with Justice, the kernel is NOT the issue here, it's simply getting the correct patches to interface the software with the older chipset and HAL, or so I think?
Don't use this rom due to random bootloop .
Hi all here the latest aokp milestone rc2 based on the latest unoficial cm9 rom BY Erwin.P
It's aokp milestone 6. version 4.0.4
Enjoy the aokp rom
The defauct lanchet is nova i think is the fastest but you can always use apex lancher or other ics one.
Detail:
Ics interface.Cm9 theme chooser, aokp setting and more will come.
What need to be fix :
Aokp stock live wallaper .But it's all and all cm9 bug.
Download:
https://docs.google.com/open?id=0B-5I_FmNMNolX0JpdEVFX2NIZG8
WARNING:
Before to install you have to delete 77tweaks in System/etc /init d
Credit:
Erwin.p
Aokp developer for wildfire.
Cyanogenmod team
can't download
Hello Pator57,
First I want to express my intentions with this post: I'm VERY glad that you have started to work on these ROM ports, and I'm only willing to help ya so that you can contribute more and more for the wildfire.
For me, a ROM presenting shouldn't be done in this way. First , lets start with the thread name-you should specify what actually is in this thread, is it a port/mod/build-from-source/etc, not only 'aokp update' for example, you should specify a date/version of the specific ROM , so that the users can keep an eye on the ROM since its almost certain that it will have some bugs , that should be fixed in new versions.
Later, in the thread its good not only to explain how and what you did it, but to put screen-shots/videos. To give details about the features,the ROM base and from where did you ported it, about the performance and some glitches. Plus that don't forget to include some disclaimer, so that you are not taking any responsibility for bricked phones, earthquakes or anything else. There can always be someone to point at you and claim that you bricked his precious phone. Detailed credits are also good to write, but you have made it so its OK.
Moreover,the actual zip of the ROM. Its not cool to name it 'aokp.zip' or 'miuiv4.zip'. I again think that including date/version is good, because when you make 3-4 different zips with bug fixes for example, personally i love to store more than a one version of the ROM I use and with these names it wouldn't be practical.
Of course one can rename it himself , or try the ROM to find out whats in,but(I think) these small suggestion would make you look more professional and reliable, just the way a developer/porter should look. This will give me personally convince in you, and that the things you do wont harm my phone. I hope noone will feel offended in any way. My intention as I said is only to help you, so that we can have one more ROM "producer" here. All what I wrote are personal views on how the things are done around here, its your choice whether to follow them!
Vency77 said:
Hello Pator57,
First I want to express my intentions with this post: I'm VERY glad that you have started to work on these ROM ports, and I'm only willing to help ya so that you can contribute more and more for the wildfire.
For me, a ROM presenting shouldn't be done in this way. First , lets start with the thread name-you should specify what actually is in this thread, is it a port/mod/build-from-source/etc, not only 'aokp update' for example, you should specify a date/version of the specific ROM , so that the users can keep an eye on the ROM since its almost certain that it will have some bugs , that should be fixed in new versions.
Later, in the thread its good not only to explain how and what you did it, but to put screen-shots/videos. To give details about the features,the ROM base and from where did you ported it, about the performance and some glitches. Plus that don't forget to include some disclaimer, so that you are not taking any responsibility for bricked phones, earthquakes or anything else. There can always be someone to point at you and claim that you bricked his precious phone. Detailed credits are also good to write, but you have made it so its OK.
Moreover,the actual zip of the ROM. Its not cool to name it 'aokp.zip' or 'miuiv4.zip'. I again think that including date/version is good, because when you make 3-4 different zips with bug fixes for example, personally i love to store more than a one version of the ROM I use and with these names it wouldn't be practical.
Of course one can rename it himself , or try the ROM to find out whats in,but(I think) these small suggestion would make you look more professional and reliable, just the way a developer/porter should look. This will give me personally convince in you, and that the things you do wont harm my phone. I hope noone will feel offended in any way. My intention as I said is only to help you, so that we can have one more ROM "producer" here. All what I wrote are personal views on how the things are done around here, its your choice whether to follow them!
Click to expand...
Click to collapse
It's the same port as tamahal port but based on the latest cm9 09/20 rom.But exept that and some tweaks it's exactly the same rom.
Sent from my HTC Wildfire using xda premium
ROM dont work, enter pin code and always boot screen
Fulfen said:
ROM dont work, enter pin code and always boot screen
Click to expand...
Click to collapse
Ho too bad.Flash this fix and it should work now.
OT: dafuq, what is this updater-script for a simple build.prop replace
Vency77 said:
OT: dafuq, what is this updater-script for a simple build.prop replace
Click to expand...
Click to collapse
Yea i change it but before i have testing the rom without the build prop change and all was working well.So come back to the stock build prop of cm9.IF it still doesn't work i will try again a new port this week end
now just htc logo... so still fail
Strange it was working well for me..But do you make an factory reset, wipe data, wipe dalvik cache,wipe cache partition before flashing ?
Ok but if the rom still doesn't work i will deleted the thread.
Sent from my HTC Wildfire using xda premium
I'm going to backup my current CM9 setup and try this out? What device did you port from?
Sent from my Wildfire using Tapatalk 2
It's not an port it's an uptate of the other aokp rom by thathanmal66.
Sent from my HTC Wildfire using xda premium
im biting my tongue here lol
R.V.3 (MokeeOs)
Pator57 said:
Strange it was working well for me..But do you make an factory reset, wipe data, wipe dalvik cache,wipe cache partition before flashing ?
Ok but if the rom still doesn't work i will deleted the thread.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
yes i have wildfire for 2 years i know how to flash rom, i did all those things.
Looks like i am having some great fun here
Sent from Hell!!
Pator57 said:
It's not an port it's an uptate of the other aokp rom by thathanmal66.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
I'm sure it shouldn't be called like this,because its a whole-ROM zip , and you tell that we should wipe everything when installing it,but whatever.Since its an 'update' of tathanhlam66's ROM , why do you make a whole new thread and not just continue what tathanhlam66 started ?
EDIT: Plus that , you have not edited both threads as I suggested you, which is making them BOTH look just funny. If you are not serious , and constantly state 'This is an update...blqblq', they will continue to look funny and futile!
and i hope you got permission to post and uptate his work?
R.V.3 (MokeeOs)
slymobi said:
and i hope you got permission to post and uptate his work?
R.V.3 (MokeeOs)
Click to expand...
Click to collapse
...and to play scrabble with his name
As on the MIUI thread, is it possible to provide some more details on that? Screenshots, bug list?
It's quite tricky to flash a ROM without knowing the results..
There are no bug but if im wrong tell me like my miui port.But it report to doesn't boot so i will try to make it boot next weekend.And i don't need to ask permision aokp it's like miui it's an open software and no need screenshoot the rom it's an ics rom but only with some aokp option tweaks
Sent from my HTC Wildfire using xda premium
Hey guys can any one tell me if i can make my gpu performance better ? because when i launch some games like asphalt 7 the graphics are kind of crappy compared to other devices so i was wondering if any one can help me and tell me if i can make these graphics look better ?
Wrong section but GPU of on this device is a no go. We have been able to get better graphics in jb ROMs but not some that can be done as a user. Updated drivers gave some better results.
Sent from my Sensation XL using XDA Premium HD app
anders3408 said:
Wrong section but GPU of on this device is a no go. We have been able to get better graphics in jb ROMs but not some that can be done as a user. Updated drivers gave some better results.
Sent from my Sensation XL using XDA Premium HD app
Click to expand...
Click to collapse
great results or just maybe a slightly tiny bit better ?
and if its worth trying could you show me a list of jb roms or some thing ?
madshark2009 said:
great results or just maybe a slightly tiny bit better ?
and if its worth trying could you show me a list of jb roms or some thing ?
Click to expand...
Click to collapse
test temple run 2 on full grapichs, no lags at all when i tested it. try it yourself.
well look here in the dev section.....
[ROM][4.2.2]RunnyCM AOKP MR1
[ROM][4.2.2]RunnyCM Paranoid Android 3.+
[ROM][4.2.2]RunnyCM Evervolv 3.2.0
[ROM][4.2.2][AOKP/CM/PA] RunnyCM Vanilla RootBox
[ROM][Cyanogenmod10.1][v1.0]
[rom][cm10.1]jellybeerv4
next time when you make a thread read before postin
IS THIS A QUESTION?
x Yes, this thread is a Question
we have a specific Q & A thread in general section use that next time
anders3408 said:
test temple run 2 on full grapichs, no lags at all when i tested it. try it yourself.
well look here in the dev section.....
[ROM][4.2.2]RunnyCM AOKP MR1
[ROM][4.2.2]RunnyCM Paranoid Android 3.+
[ROM][4.2.2]RunnyCM Evervolv 3.2.0
[ROM][4.2.2][AOKP/CM/PA] RunnyCM Vanilla RootBox
[ROM][Cyanogenmod10.1][v1.0]
[rom][cm10.1]jellybeerv4
next time when you make a thread read before postin
IS THIS A QUESTION?
x Yes, this thread is a Question
we have a specific Q & A thread in general section use that next time
Click to expand...
Click to collapse
oh ok no problem didnt pay attention this time you can close the thread now if you want
madshark2009 said:
oh ok no problem didnt pay attention this time you can close the thread now if you want
Click to expand...
Click to collapse
Im not an moderator just helping
Sent from my Sensation XL using XDA Premium HD app
madshark2009 said:
oh ok no problem didnt pay attention this time you can close the thread now if you want
Click to expand...
Click to collapse
Please pay attention when posting! We dont want a mess of a forum. As requested:
Thread Closed
Is there going to be Sense 5.0 Rom for HTC incredible s? Could it be ported?
deni1996 said:
Is there going to be Sense 5.0 Rom for HTC incredible s? Could it be ported?
Click to expand...
Click to collapse
Not to sound rude but to open a new thread in the development section to ask such a question is just not right. Please post such questions in the general section.
We do not have that many devs working on incredible s as it is a relatively old device. If someone manges to develop an ion kernel and port sense 5 you will see it in the dev section.
Quite fortunate to get a few working jellybean aosp ROMs and quite a few sense 4.1 ROMs for a device that has no more support from htc so enjoy those and be happy.
@ moderator can this thread please be closed or moved to the general section?
Sent from my HTC Incredible S using xda app-developers app
deni1996 said:
Is there going to be Sense 5.0 Rom for HTC incredible s? Could it be ported?
Click to expand...
Click to collapse
No. Because kernel.
spazzy1912 said:
No. Because kernel.
Click to expand...
Click to collapse
-_- what do u mean kernel...... The kernel is still a jellybean kernel, just modified to be compatible with Sense. Although I dont know how to do it, Im sure it might be possible for someone like Szeszo to develop such a kernel. The only problem is that it requires a ton of work and I dont think Szeszo has that much time..... Not to mention resizing of the actual ROM.....
072665995 said:
-_- what do u mean kernel...... The kernel is still a jellybean kernel, just modified to be compatible with Sense. Although I dont know how to do it, Im sure it might be possible for someone like Szeszo to develop such a kernel. The only problem is that it requires a ton of work and I dont think Szeszo has that much time..... Not to mention resizing of the actual ROM.....
Click to expand...
Click to collapse
its got something to do with a thing called ION within the kernel.
apparently our phone doesnt have it by default.
it was mentioned somewhere in cyanvivo thread i believe.
spazzy1912 said:
its got something to do with a thing called ION within the kernel.
apparently our phone doesnt have it by default.
it was mentioned somewhere in cyanvivo thread i believe.
Click to expand...
Click to collapse
Yes it was and Im well aware of that. Our phone doesnt natively support Ion and as a result you have to change some camera libs, i think they were, and maybe a few other things here and there. But it is possible and the proof to that is the fact that we have Jellybean ROMs for our device.