[Q] ROM for SMDKV210 - Android Software/Hacking General [Developers Only]

Hi ppl,
I have a tablet with Android 2.2. I think that it´s a Sinor M8 but I´m not sure (How can I see it?). The problem is that the OS doesn´t work well, for example, Google tells me that it´s an unknow device. My question is how can I reinstall Android 2.2 or higher (I prefer Honeycomb). Is there any ROM for this device or an tutorial of how can I compile the Android source code for this device. The device has an ARMv7 Processor rev2 (v7l) and 512 MB. Is it a good decision to compile it?
Thanks,
Gabriel

I saw that my device has SEC-SMDKV210 8in Android 2.2 CortexTM-A8 512MB 1Ghz HDMI. Is there any ROM for this hardware. I saw that many devices have SMDKV210.

ROMS for your device
Hi gabvalentin,
You can find ROMS for your device at www.slatedroid.com
It the best site for tablets based on android OS.
Let me know if you find a good one
Cheers
Ashhem

Related

[Solved] [Q] Build Android for phone on Qualcomm MSM7227 (Motorola Quench XT3)

Hello everybody!
I need an advice on where to get drivers (or what kernel options to use) for my phone (Motorola Quench XT3) build on Qualcomm MSM7227 chpset.
It would be cool to be able to compile new version of Android from source, like gentoo or LFS; we wouldn't depend on Motorola's software updates. The only thing that seems missing is drivers and kernel configuration. (May be I am wrong - correct me)
So how do I find out what drivers/kernel options to use for my hardware?
Any help is appreciated. I would make an understandable guide for compiling Android for Motorola Quench XT3 if I succeed.
Upd:: Motorola Quench XT3 is a "Boston Orange" phone. Look for mods on cyanogenmod forum, in the z71 variants section.
Therein lies the problem.
Linux drivers for phone chipsets (mostly Qualcomm) are often provided as binary lumps for a specific kernel version. When kernel sources are made available for a specific phone then we can generally compile a full AOSP build by making sure that the kernel we build is compatible with the binary blobs, this get more difficult as the framework gets upgraded and depends on features of newer kernels.
So the things to look for are:
What version of Andriod does it run, what do you want to run?
Have Moto released kernel sources yet?
What are the GPU/Radio/BT/Wifi/Audio chipsets
Do we have binder-friendly driver source available for any of the above.
This is all _hard_ stuff and generally if you've never compiled a Linux kernel before this is not the place to start.
Linux drivers for phone chipsets (mostly Qualcomm) are often provided as binary lumps for a specific kernel version.
Click to expand...
Click to collapse
This is OK as long as binary drivers are available for new kernels, I guess.
What version of Andriod does it run, what do you want to run?
Click to expand...
Click to collapse
It has Android 1.6, and my goal is 2.2.
Have Moto released kernel sources yet?
Click to expand...
Click to collapse
yes, they have sources available for download. I downloaded, but couldn't figure out what ".config" they use, in the bundled script "Android.mk" that depends on external variable KERNEL_DEFCONFIG.
What are the GPU/Radio/BT/Wifi/Audio chipsets
Click to expand...
Click to collapse
Ok, I am trying to find that out. Couldn't find specs in the net (including Motorola website), they only give processor (Qualcomm MSM7227) Is there a command like lspci on Android?
if you've never compiled a Linux kernel before this is not the place to start
Click to expand...
Click to collapse
What is the place to start then? Actually I've configured and compiled kernels for several desktops/laptops, they are fine. I am not any kind of expert, but may be it isn't too difficult to build a working 2.2 Android. There's almost no hope to get it from Motorola. Also I don't care about Motorola-specific software.
Overall, thank you for a good & quick response. I will try to figure out exactly what hardware it uses, and post it here.
P.S.: what else people do to upgrade their phones when it isn't supported by manufacturer?
It's MSM7227 !!!
Hello people!
After a lot of reading I start to understand concepts. Turns out, my phone has a good and popular chipset Qualcomm MSM7227. The same chipset is used in, say, HTC Aria and HTC Legend, which are well supported by cyanogen mod. And looks like chipset determines all major drivers I need! (probably except minor things like flash light)
So, I need help of somebody who knows these things better than me in the following questions:
What could be a difference in firmware between (say) HTC Legend and Motorola Quench XT3, which share the same chipset?
Is there a "generic" build for MSM7227?
Any input is greatly appreciated.
Unfortunately that is rarely the whole of it. Slight differences in implementation can make all the difference. E.G. the radio itself has a firmware that may fundamentally change the interface presented to the CPU. Sound/Display/3D are also up in the air.
Short version, if you can find out the chipset driving each of the above (not just the CPU/Radio SOC) and you can either find:
1. 2.2 binary blobs from another phone
2. Open source drivers that can be compiled for the 2.2 kernel
Then you may be ok.
The reason I said that this may not be the place to start is that what you are trying to do here is get binary blob drivers running for a kernel they were not intended to run with, debugging that is some heavy magic on a desktop, even more so on an embedded device.
I also have the same phone and i was looking for a froyo mod.
I would be willing to test it out (i have the same phone ).
I should warn you though i have no mobile phone hacking experience!
SilentMobius, thank you much for good explanations!!
I googled more, and I have strong suspicion that Motorola Quench XT3 is the same as "Orange Boston" phone. That piece of hardware has been manufactured by many companies under many names (GigaByte G1305 Codfish, Apanda A60, WellcoM A88, Vibo A688, Cincinnati Bell Blaze f800, Commtiva Z71, Muchtel A1, Chinavision Excalibur, Motorola Greco, Nexian A890).
Though I am not sure that orange boston hacks would apply to Quench XT3. Is there a way to check their compatability (in hardware, radio firmware, etc) ?
Cyanogenmod
Turns out we are lucky - Quench XT3 is a part of "Boston Orange", and it runs cyanogenmod. This is very nice, and there is no need to make rom from scratch. Moreover, everything I was thinking of is already done for this phone.
Look on cyanogenmod forums in z71 variants section for mods and other information.
Thanks a lot
Uh, could anyone help me?
I rooted the phone with Universal AndRoot but when i click on z41 on rom manager it gets an error.
Help?
qwerty156 said:
Uh, could anyone help me?
I rooted the phone with Universal AndRoot but when i click on z41 on rom manager it gets an error.
Help?
Click to expand...
Click to collapse
In ROM Manager the phone is known as an Commitiva A71. You are selecting the wrong phone.

Compiling Android for a Device without sources (Zenithink Tablet)

Hey, so last year I bought a China-Tablet called Zenithink C91, it seemed like a good choice back then.
However, the software on it is rubbish. The manufacturer didn't even bother to change anything from the reference software for the hardware platform, did no optimization whatsoever. For example the build.prop is a complete mess with dozens of duplicate lines and references to the reference platform from AMlogic. All the stock firmwares have phone functionality enabled, even though there is no gsm module, showing an empty signal indicator all the time. Or the shipped ICS with gingerbread gapps and so on. The Tablet is just not usable in this state because the software sucks so much, and they do not answer any questions or take advice. Therefore, no sources.
However, I think the Tablet could be much more useful, because it has a decent cortex a9 processor which runs at 1ghz, and a mali 300 gpu.
So much for the situation.
So for a long time I thought about trying to compile a new rom for it, to make it actually work like it should, but I cant find any advice which would help me, because all tutorials that I find require me to use devtrees for devices that already exist. But how would I go to create Android for a device which has none?. I could probably extract most drivers from the latest ICS build. How compatible are they with JB?
On a side note, I wanted trying to Port CWM recovery, does anyone have a pointer where to start?
Thanks and I hope I did not post in the wrong section.
I actually think that there is a source available for your tablet. Check out Slatedroid, as it's a forum dedicated to chinese tablets.
The problem atm is the new version of the amlogic's platform for which they haven't released sources yet.
Oh, and tutorial for Clockwork recovery:
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Thanks for your reply, especially for the link concerning cwm.
I am aware of the slatedroid forum, and a user there, too. Zenithink did not publish any sources, I am very sure sadly.
ArRaY92 said:
Thanks for your reply, especially for the link concerning cwm.
I am aware of the slatedroid forum, and a user there, too. Zenithink did not publish any sources, I am very sure sadly.
Click to expand...
Click to collapse
Zenithink maybe didn't, but you can find amlogic sources (the chip/platform manufacturer) here:
http://openlinux.amlogic.com/wiki/index.php/Arm/Android/2.Getting_the_Source_Code
edit: that is if they are using that as a platform ofc, if they're not well from what I see on slate you're limited to modifying stock roms, same as we on elf/aurora ii devices
Yeah, the stock sources are there, but ZT modified them and does not release the changes. No chance then, I guess? Anybody know if there is a chance for JB based on the ICS rom?

[Q] Help needed on building custom Android for a new Tablet

Hi,
Right now, I am looking into building custom Android OS. Here is my constraints,
-- It is a custom build for a new Android tablet
-- It should launch our own app when the OS boots. This app will be main entry to the tablet. Need to lock down/remove all the other apps and launcher screens
-- Device drivers are need to be changed while building according to the hardware
-- There is no constraint on which version of Android need to be used
Hardware details of the tablet:
1.2Ghz Cortex A9 processor,
a 7” display of 1024x600 resolution
comes with Android 4.2
Do I need to look for building a custom ROM or with a new design of Android launcher app I can enable these? For installing new device driver I hope I need root access. I have searched a lot of tutorials on all the topics. Can anyone suggest me where should I start with according to my needs?
Let me know if I need to provide any more details.
Thanks!

[Research] Supported MTK Custom Roms?

Hi All,
I'm looking for active MTK Custom roms.
I've been browsing all over, but have been unlucky in my search for the moment.
I recently bought an android smartphone on aliexpress and it's a budget phone with moderate specs.
But I'm unsatisfied with the current factory performance of current OS, so I'm searching to replace it with something I might optionally tweak over time as well, but any active custom rom will do.
I'm specifially using the MTK6899 cpu on this phone.
I had to aswell already factory reset to fix storage capacity issue, so not a good sign to begin with either.
I'm really looking for any answer to clarify my quest/research in understanding the possibilities to port this phone to a different rom.
AFAIK Mediatek's source code for their chipsets isn't open source, hence developing Custom ROMs suitable to a specific Mediatek chipset is impossible.
jwoegerbauer said:
AFAIK Mediatek's source code for their chipsets isn't open source, hence developing Custom ROMs suitable to a specific Mediatek chipset is impossible.
Click to expand...
Click to collapse
Hmm that's a bummer, if only I knew this before acquiring this phone, right?
So should I aim at finding one for another mediatek chipset?
Or will there be too many issues caused by incompatibility?
bossc2 said:
So should I aim at finding one for another mediatek chipset?
Or will there be too many issues caused by incompatibility?
Click to expand...
Click to collapse
As I can see you didn't get it.
A Custom ROM basically doesn't depends on Android device's chipset, it only matters with regards to being a 32-bit or 64-bit chipset.
Developers of a Custom ROMs claim their Android ROM is oftentimes faster, more efficient, and use less memory because
they ripped out useless garbage, such as OEM/ carrier installed apps ( AKA bloatware ) or
they optimized the kernel. For example, an undervolted kernel can provide a much better battery life than the stock one.
That's all.
jwoegerbauer said:
it only matters with regards to being a 32-bit or 64-bit chipset
Click to expand...
Click to collapse
(noob here) regarding a tablet
What device info do I need, other than 32/64bits, in order to find a ROM that works?
and I mean basic functions, browser, wifi, touch screen etc... (No need any GSM/celular/mobile etc..)
gsi roms works also on mtk devices
wetito said:
gsi roms works also on mtk devices
Click to expand...
Click to collapse
hey i am looking for a gsi for my Moto G 5G 2022 (Austin) I am a noob i dont know where to find any that will actually work... the device is a mt6833 MediaTek Dimensity 700 and is on android 12... i'd like maybe an android 13 gsi like pixel experience but have no idea where to start.
gr3uh said:
hey i am looking for a gsi for my Moto G 5G 2022 (Austin) I am a noob i dont know where to find any that will actually work... the device is a mt6833 MediaTek Dimensity 700 and is on android 12... i'd like maybe an android 13 gsi like pixel experience but have no idea where to start.
Click to expand...
Click to collapse
Same here, if you're able to get a GSI please share, I'm running Android 11 and I want Android 12 stock ROM

Samsung A13 (sm-a135m) 64bit kernel building

Hi Everyone!
I'm very new to this topic, this is my very first time trying to build a kernel from source code. As setup i've a samsung a13 SM-A135M (which is the 4g version of a13 series), this phone by default is forced to work 32bit on a processor and hardware that has the capability to go full 64bit.
The question is:
I've inquiried the correct version and baseband that corresponds to my device, on https://opensource.samsung.com/, and they uploaded the source code of it (the baseband is A135MUBU1AVB5), so with this source code should i be able to build a 64bit version of both kernel and android OS , or this source code only works for 32 bit installations?
Thanks and Regards!
Hi, I just asked a very similar question here: https://androidforums.com/threads/i...this-problem-a13-samsung.1347411/unread?new=1
And someone's reply brought me to your thread. I don't exactly know much about coding but an experienced user said he did some searching, his answer is on my thread. As of now there is no way that he could find to get a 64bit software on the a13, hopefully this changes.
Hi!! thats right, the problem that you have is what has driven this question, although i've the source code for building the OS i'm waiting for someone more experienced to tell me if this source is able to build a 64 bit version of the OS and Kernel for the A13 phone. Hope we find this experienced person
arieleoar said:
Hi!! thats right, the problem that you have is what has driven this question, although i've the source code for building the OS i'm waiting for someone more experienced to tell me if this source is able to build a 64 bit version of the OS and Kernel for the A13 phone. Hope we find this experienced person
Click to expand...
Click to collapse
That would be great I think the a13 is great value for the price now we just need to get around the software limitations

Categories

Resources