I have a Craig 7 inch tablet. It is supposedly based off of Rockchip.
I'm only posting specs to avoid confusion.
Specs:
Model #: CMP738A
Android Version: 2.2.1
Kernel Version: 2.6.5 YT200-700-004600000000000000 #3
Build #: froyo1.00 MASTER.eng.gump.20110331.162508
------------------------------------------------------
Like I said I have this Craig 7 inch tablet and I was just wondering; Why wouldn't I simply be able to flash android 2.3.3/.4 or android 3.2 to this device via Odin?Android is Android isn't it? I have read that it can be rooted and that there are two custom roms for this device but it seems difficult. I am not new to rooting and flashing via Odin, Super One Click, and Clockwork Mod. Just wondering what it would take to flash either of these roms to this device and if not why?
Redirection
Could this be redirected to another area to where I may possibly stand a better chance for an answer?
(bump)
Sent from my PC36100 using xda app-developers app
Hy,I would like to know more about the android versions and custom roms.
1)Why some devices do not support new versions of Android?
Why is not working as a PC operating system? For example when windows7 appeared most of the PCs could install windows 7.
2) Why is possible using a custom rom like cyanogen to update to a newer version of android although this version is not released by the producer. Ex. install ics on galaxy S.
3) Using a custom ROM can update a device from the first version of Android to the latest one?
Thank you for your help.
Catalin
To answer your questions as best I can...
1. Most phones can support almost any version of android. It all has to do with their chipset.
2. When a custom ROM is created, it is based on a certain version of the OS. It is custom because it is modded by developers to be compatible with different devices.
3. Yes. This is true depending on, again, the device and the developers. For me, I have had many devices that were on froyo 2.2. And would not get an OTA update. Whereas a custom ROM could kick it up to gingerbread 2.3 or ice cream sandwich 4.0.
I hope this helps!
Sent from my HTC Vision using xda premium
1. the problem is with your carrier or manufacturer usually. some push updates through fast, others test updates before letting users update. also older phones get forgotten. a new phone will be more likely to get updated than an old one. they want you to buy a new one
2 and 3 what i337 said. i would just add that using a rom bypasses the problem in #1
Also one of the big issues are the drivers. The open source drivers work but don't use the hardware to the fullest. Also non of the OEM related apps and stuff work on AOSP roms. Then you have app compatibility issues with AOSP roms as well.
I came across this site. http://www.engadget.com/2012/02/02/htc-sensation-puts-on-a-white-ice-coat-to-match-its-ice-cream-sa/
and it seems like the sensation will have an OTA update to ICS with sense 4.0. So, does that means that we will have a custom ROM base on that ROM? That will be awesome. Discuss.
UPDATE: ok, now I have a few questions for the developer. Since there are already so many ROMs on ICS with sense 3.6, but why there are non for our desire s ? Take a look at this ROM http://forum.xda-developers.com/showthread.php?t=1419278... there are more at sensation forum. Is it because of the drivers or hardware related? I'm not quite familiar with all these developing stuffs, so maybe the experts out there would enlighten to me? Thanks.
Firstly I am no developer but I think I can say some things about what you said. Yes it is hardware related like all linux based OS android has a kernel and the kernel is mostly written for a device specific hardware. And sensation and saga in that respect is no match so no part of it could be used in ours. And also there might be a need of lot kernel tweaks and for that rom to work. The derivative of sensation , sensation xl in retrospect is whole lot similar to our device so if a leaked rom is released for that one then I am sure devs will be able to do the things you wished. On top of kernel device specific hardware driver and all that the sense version as always by htc is a very special one as i understand cause its a whole lot different than any other rom. Looking through posts you might have seen sense kernels and aosp ones are different. So in the end to port that rom it will need a kernel drivers and all plus the effort to crack the sense overlay that htc slaps on anything too...
It might be not possible my heart strongly wishes for an ICS official rom as that would ease up a lot of things.
The HTC Desire S has a different screen, so the one leaked sense 3.6 (4.0) could only be ported to devices sporting the same screen. Be patient, HTC anounced that the Desire S will get ICS with Sense l8er in 2012. I'm sure the XDAdevs will be faster though....
Hi, I have recently rooted my Desire S, with revolutionary, clockwork etc, and I currently ported this rom HTC_DESIRE_S_2.3.5-2.10.401.4.zip
Everything is working just fine, but theoretically, when I decide to port a new rom, how would I know which will work, and which won't?
Actually, I'm waiting until ICS is released for desire s, so I can find it and install it...
Are there any methods to identify which rom would be compatible?
Thank you!
kostistheo said:
Hi, I have recently rooted my Desire S, with revolutionary, clockwork etc, and I currently ported this rom HTC_DESIRE_S_2.3.5-2.10.401.4.zip
Everything is working just fine, but theoretically, when I decide to port a new rom, how would I know which will work, and which won't?
Actually, I'm waiting until ICS is released for desire s, so I can find it and install it...
Are there any methods to identify which rom would be compatible?
Thank you!
Click to expand...
Click to collapse
hey mate
your're actually talking about two different things: porting a ROM and flashing a ROM.
Porting means, you take a ROM from another device and modify it so it works on your device too.
flashing means, you take a ROM which is already optimized for your device
and install it, so you wipe the stock firmware and get a custom rom.
which of the two things is what you want to do? i think its just the flashing.
so you can take any ROM from the "development section", and if you follow the guides that you can find everywhere here im sure you will be succesfull and happy with it.
bytheway
there is no "best" ROM for your device. it all depends on what you need and want. there are alot sense 3.5 Roms, Endymion 3.4 is the one i would recommend. you can also try AOSP ROMs (android open source project, means no sense), cyanogenmod7 could be a good first choice. and you can also try ics right now, since there are at least 3 (?) ICS AOSP ROMs right now:
CM9, Virtuous Quattro RC3, IceColdSandwich
have fun!
Yes I meant "flashing" a rom
Thanks for all the information. That's the general idea I have as well, however I had this question because after I flashed another rom (official rom through htc sync - that could have been the problem) over my first flashed one , the phone was "bricked"....
kostistheo said:
Yes I meant "flashing" a rom
Thanks for all the information. That's the general idea I have as well, however I had this question because after I flashed another rom (official rom through htc sync - that could have been the problem) over my first flashed one , the phone was "bricked"....
Click to expand...
Click to collapse
i would never recommend to flash an official ROM over a custom ROM. But anyways, i think if you would have done a full wipe before flashing the official rom you wouldnt have got a "you call it brick"
a real "BRICK" is a useless phone, where there is no way to use it again.if there is still a way, its no brick.. but who cares about definitions
I recommend you to flash the ROMs only through recovery mode. AND ALWAYS DO A FULL WIPE BEFORE FLASHING A NEW ROM. very important
and dont forget to backup as always
Yes you are absolutely right. I'll have that in mind the next time I'll decide to flash a new one
Yeah the device wasn't completely useless, it hanged at boot...but I guess that was due to not following the right procedure as you previously described..
Thanks eyahl
Start flashing different roms and trying them for a day or two. First
Sens 3.0 and then sense 3.5 roms to see the difference. Only then you will know which rom is best for you.
+1 for Endymion 3.4,
+1 for Endymion
Swyped from my Desire S using XDA Premium
+1 Endymion
Sent from my HTC Desire S using xda premium
edymion, will try it
+1266592.23 for Endymion
kostistheo said:
Yes you are absolutely right. I'll have that in mind the next time I'll decide to flash a new one
Yeah the device wasn't completely useless, it hanged at boot...but I guess that was due to not following the right procedure as you previously described..
Thanks eyahl
Click to expand...
Click to collapse
Each ROM type suits different personal tastes, so there isn't an 'best' ROM for everyone. Trial and Error which ones suit you!
General opinions:
Stock
Pro: Straight from HTC, *newest kernel/drivers*, least likely to have compatibility issues.
Cons: HTC is slow to release updates, and sense interface is usually resource hungry.
Sense-like
Pro: usually keep the Sense interface, but custom kernals offer speed / various other improvements.Runnymead versions are kernals ported across from HTC Sensation (which offer some of the goodies like Beats Audio etc. that were not originally developed for Saga.
Cons: Sense interface is resource hungry...
CyanogenMod based
Pro: offer lots of customisations
Cons: not the most user friendly
AOSP
Pro: Roms from the android source, usually less resource hungry, so lighter and faster.
Cons: Obviously, no sense.
ICS Alpha/Beta
Not strictly a new category, but builds from the new Android 4.0 (ICS).
Currently some things (like camera) isn't fully working yet.
Note: new Desire S may suffer from camera/video lag bug with non-stock / non-sense ROMs, this is due to HTC putting in new hardware / driver into the new DS phones and the other kernels not reflecting this change yet.
Personally, I use SenseMOD Lite V1.2 build 2 as it is one of the few AOSP like builds that don't have the camera bug. Oxygen would have been best choice for me but unfortunately camera bug makes it unusable.
Hey guys. I don't want to drive over your feet, but I think the OP is already very satisfied with all those replies. specially the post above is really trying to help, but you spend much time to type what has already been written on the first page.
I appreciate your intend to help, bit I think the OP isn't gonna read this anymore..
Btw: endy!...
Sent by my fingers to your head
Okay, i've been out of the scene for a really long time.
I'm currently running MIUI and so far it's the best rom i've used and most importantly, other than the sh!tty camera, IT WORKS!
my question is: I just logged onto the MIUI.US site and there appears to be an update for the Sensation. Problem is, I cant determine what version of MIUI i'm currently running and whether or not the available ROM is a good update path for me or not.
There's two versions available:
HTC Sensation (AOSP based)Version: 2.6.29
HTC Sensation 4GVersion: 2.7.13
Here's what the settings in my phone say:
Android Version: 2.3.7
Kernel version: 2.6.35.13 Trinity-S4g
Build number: MIUI-20224
IIRC way back when, the MIUI.US version number I downloaded was 2.2.4 or something.
Can someone tell me where I'm at currently and whether or not the available update is worth updating to, based on stability, features and whatnot?
Thanks!