Hi,
CPU of my android device is MT6592 (8xARM Cortex –[email protected] MHz) with instruction set 32-bit ARMv7. Board and product is ht1_107a_iball_mjk. Apart from this, Codename is REL, Internal Memory is 16GB and RAM is 2GB. And I searched many times on https://download.cyanogenmod.org/ for compatible CM 13 but I didn’t find.
If no CM 13 is exists for my device, it’s unacceptable for me. Like system requirements for Windows 7, Windows 8.1, Windows 10, etc, I would like to know the hardware requirements for android 6 and android 7.
Also I noticed, all builds on https://download.cyanogenmod.org/ are for Snapdragon Processors only. Is it right?
Please let me know about the compatible CM 13 from https://download.cyanogenmod.org/.
Regards
GNS
u forgot the most important part xD , what's ur device model ?
Modal Number is iBall Brace-X1. It really more unfortunate for me that there is no release from my device manufacturer related to boot-loader, Custom Recovery, Custom ROM or anything related to this. Also I do not find any helpful developer release for my device. As I do not get helpful tools, release, Custom Recovery and Official Custom ROM for my device, however I am ready to try for unlocking boot-loader, flashing Custom Recovery and Custom ROM multiple times but while doing all these procedures sometimes I get scared of any faults in terms of hardware.
Related
I was going through the xdadevelopers forums when I saw that the process of installing ROMs seems of be device dependent. Can someone please explain me why it is so?
More specifically, shouldn't the process of installing a pure Android ROM (AOSP) be the same on every device since all of them are based on the ARM architecture.
I haven't installed an android ROM before, but I am trying to understand why the process isn't similar to installing a Linux based OS on my computer.
I recently bought an Android tablet (HCL ME X1) to experiment with ROMs but later realized that there aren't ROMs for this device. Can someone let me if I can use the ROMs of any other device for this?
Because all different models have different hardware so the rom has to be specific to that device.
Sent from my GT-I9100 using Tapatalk
Thanks for the reply stylez.
So I guess if I want to develop a custom ROM (say an AOSP ROM) I will need the device drivers which my vendor wrote.
Is there any way of identifying the vendor specific drivers of my device? I am using an HCL ME X1.
Hi
Welcome to what im hoping will become a popular project amongst owners of Rockchip devices. Over at rkDroid we are aiming to create the first custom rom for the rk3026.
We really are starting at the bottom with this one as there is so little info available about these devices. The aim will be a 2 stage project :
Stage 1 : Cooked stock rom
Stage 2 : KitKat
We want to get as many people involved as we can. This means addressing ALL levels of skill. This is why there are 2 stages.
Stage 1 :The 'cooked rom' - This will be for beginners to contribute to. It could be themes, app suggestions, tweaks, etc. They all go into a custom rom and no one is better than another. Anyone can get involved, even if they dont have a Rockchip device. Icons, Themes, etc. They ALL count.
Stage 2 :'KitKat' - I have the source for the kernel and Android build for KK on the 3026. This means we can (in theory) build KK for it. Rockchip released a press release a few months ago saying the 3188 & 3026 WILL get KK. So far the 3026 has been lacking in this. rkDroid aims to bridge that gap and get a KK build out there for these devices. Im no pro when it comes to building Android or kernels. Ive done a few but im in no way a 'guru'. Im also not stupid. This stage of the project WILL require people with some knowledge of building Android, etc.
Overall, the aim of rkDroid is to bring Rockchip device users together to share info, solve problems, build roms, etc. Our site aims to be a popular resource for Rockchip tablets (No TV sticks or Mini PCs yet, sorry guys).
We dont only support the rk3026, We also have info/roms/etc for the other Rockchip devices like the rk3066, rk3188, etc. We will be aiming to create roms for these too once we get more support.
The bottom line is that if you own a Rockchip device and want to be involved in creating a custom rom for it then get involved with us. Whatever level you are at you can have an input in this project and we welcome everyone. n00b or bo$$, its all the same to us, There is a place for everyone at rkDroid.
Let us know if your interested in this project and lets see if we can beat Rockchip by getting our own KK build out before them
did this rom can change size storage sytem
in fact on rk3026 MD706B tablet 8GO/1Go
we have
1 Go for system
1Go for internal sotage
and 5.6 for internat SD : nand flash
can we use 1 giga from those 5.6 to add them to internal storage like on samsung 16g tablket hey have 3G for internal storage
Rk3026
Is this thread still active?
[Solved] WiFi doesn't turn on
Cass1977 said:
Hi
Welcome to what im hoping will become a popular project amongst owners of Rockchip devices. Over at rkDroid we are aiming to create the first custom rom for the rk3026.
We really are starting at the bottom with this one as there is so little info available about these devices. The aim will be a 2 stage project :
Stage 1 : Cooked stock rom
Stage 2 : KitKat
We want to get as many people involved as we can. This means addressing ALL levels of skill. This is why there are 2 stages.
Stage 1 :The 'cooked rom' - This will be for beginners to contribute to. It could be themes, app suggestions, tweaks, etc. They all go into a custom rom and no one is better than another. Anyone can get involved, even if they dont have a Rockchip device. Icons, Themes, etc. They ALL count.
Stage 2 :'KitKat' - I have the source for the kernel and Android build for KK on the 3026. This means we can (in theory) build KK for it. Rockchip released a press release a few months ago saying the 3188 & 3026 WILL get KK. So far the 3026 has been lacking in this. rkDroid aims to bridge that gap and get a KK build out there for these devices. Im no pro when it comes to building Android or kernels. Ive done a few but im in no way a 'guru'. Im also not stupid. This stage of the project WILL require people with some knowledge of building Android, etc.
Overall, the aim of rkDroid is to bring Rockchip device users together to share info, solve problems, build roms, etc. Our site aims to be a popular resource for Rockchip tablets (No TV sticks or Mini PCs yet, sorry guys).
We dont only support the rk3026, We also have info/roms/etc for the other Rockchip devices like the rk3066, rk3188, etc. We will be aiming to create roms for these too once we get more support.
The bottom line is that if you own a Rockchip device and want to be involved in creating a custom rom for it then get involved with us. Whatever level you are at you can have an input in this project and we welcome everyone. n00b or bo$$, its all the same to us, There is a place for everyone at rkDroid.
Let us know if your interested in this project and lets see if we can beat Rockchip by getting our own KK build out before them
Click to expand...
Click to collapse
I flashed your ROM from rkdroid here with 3.0.36+([email protected]) #69 kernel. Rom is really fast but only problem is that wifi doesn't work. If I try to turn wifi bar on it will automatic slide to off position. It says that "turning wifi on" but nothing happens. I can't flash my stock rom back because my TWRP backup is corrupted (system part is missing).
Can you help me?
Solution: Turns out that that my wifi is actually Atheros AR9271 so all I need to do was flash Oma Cube U25GT2-H JB v1.0 rom with my genuine kernel. Everything is working now!
please help me...... i have supertab r10 rockchib rk3026 i flashed him then it become working whithout screen...... do you have any soluation?????!!!!!!
You should flash original firmware if your tab is bricked. Which firmware did you flash? Seems to be kernel related.. Did you make a backup before it got bricked?
i tried every flash at "wwwrockchipfirmware.com ..... and still the same problem ...... whait screen ore black screen ...... i did not make a backup ...... do you have an original firmware ore any solution for this problem
Hi all anyone can help me please? i have an INTENSO TAB 734 "7" inchs ARM, Processor Cortex-A9 with Rockchip RK 3026 Risolution 1024 x 600 Pixels, RAM type DDR3-SDRAM ,ram memory 1 gb......................
I have need the firmware for this Tab because is completly bricked.please im desperate anyone can help me? THANKS ADVANCED
rk3026 Rom
I greet the whole community of forum.xda-developers.com and ask for pleasure if someone can help me
in finding the right firmware for my tablet
template: 759
rk3026
yudongsheng @ ubuntu # 435
I state that I was able to install twrp and I also have the possibility of installing a ROM
Hello, I am not-exactly-proud owner of PAP5400DUO, it has only 512 MB RAM and Quad-core CPU, so it is sometimes unresponsive and since there is no hope of it getting an update to KitKat. I searched for a custom roms, but I haven't found any (which is little troubling), yet the device can be rooted and MIUI recovery flashed (version unknown, I didn't root my phone yet). On my way when searching what do I need to build AOSP ROM I found out that I need a "device tree" which if I understood right is some specific information about my device (drivers etc) needed to compile a rom properly.
Which is quite an obstacle, because it is nowhere to be found, yet I stumbled upon a post that said that device tree can be created from scratch (yet probably by trial-error method).
All I need is to know if it is really worthy the time and struggle, I used to own HTC Wildfire S and have limited knowledge about ROMs, yet I am willing to study by myself, there are the main questions:
Is it everything possible?
Is the said recovery sufficient to flash KK? (hard to tell, i don't know the version, I know)
Would AOSP KK ROM improve the performance? (I hope so, but still its 512 MB RAM only)
Is it worth it? isn't there another way? (the kernel doesn't support SWAP, so maybe kernel update?)
As far as I know, flashing a ROM cannot brick the device (unless it harasses with Radio, which I really don't intend), so I can Always revert to backup and phone stays functional right?
Can i possibly know why devices owning the 6795 like the rn3 won't upgrade to CM13 ? What do the devs require so much that they can't port CM13 to the mediatek version ? I'm afraid i'm not aware of this version so much, but does it properly need android M in order to run ?
Mediatek phones are generally far more difficult to develop for because they don't like to release kernel sources and they are built for generic phones so they don't work as well
Mediatek development most currently are porting roms that is the same base as the original. If it came out with 5.0.2 then the max version for a custom rom is probably 5.1.1 and its harder to port higher android OS without any sources.
Oh, i see.. So mostly is because of the phone devs that won't release certain codes and whatever you need in order to develop the rom, right ?
Yeah blame the chipset manufacturer.
I'm no developer, but what about this info?
https://github.com/rmtew/MediaTek-HelioX10-Kernel
Hi everyone,
After a few hiccups, I successfully rooted my Leagoo T5c, thanks to the excellent tutorial posted here. The phone works fine, thank you, but now, I'd like to know how to proceed to, say, upgrade the phone from its current Android version (7.0) to a more recent version.
Where to start?
Since this phone has a Spreadtrum/Unisoc SC9853i SoC (Intel-based), I suppose the custom ROMs and upgrade possibilities are few and far between, but I'd like to give it a shot.
I'm open to ideas, tips, tricks, voodoo moves and Santeria incantations, but I'm still a noob when it comes to Android, so please, be patient, and methodical... :good:
@UglyStuff
If you can unlock phone's boot-loader then you should be able to flash any Custom Recovery and/or Custom ROM that's suitable to 100% to phone's CPU-architecture. Who is the supplier of phone's SoC isn't of any interest at all.
Hi,
Thing is, as I said, I'm a noob when it comes to Android, so I don't want to brick my phone by trying to make it ingest a ROM that's not suitable for it.
If my phone came with a MediaTek or Qualcomm SoC, I wouldn't worry, because there are plenty of ROMs out there, custom or not, to play with, but this Spreadtrum/Unisoc SoC is a thing of its own.
It's based on Intel's Airmont architecture, and few phones or tablets use it, at least this specific version (SC9853i). Maybe I just don't understand too well how a ROM is built.
UglyStuff said:
Hi,
Thing is, as I said, I'm a noob when it comes to Android, so I don't want to brick my phone by trying to make it ingest a ROM that's not suitable for it.
If my phone came with a MediaTek or Qualcomm SoC, I wouldn't worry, because there are plenty of ROMs out there, custom or not, to play with, but this Spreadtrum/Unisoc SoC is a thing of its own.
It's based on Intel's Airmont architecture, and few phones or tablets use it, at least this specific version (SC9853i). Maybe I just don't understand too well how a ROM is built.
Click to expand...
Click to collapse
For example, I found this article where they explain how to flash LineageOS 17 (based on Android 10) on a Panasonic Eluga Ray 800 that uses the same SoC as my Leagoo T5c.
The thing is, I don't know if this is transposable to my device, though the two share the same SoC. As I said earlier, I don't want to permanently brick my phone...
@UglyStuff
The mentioned Intel Airmount SoC's instruction set architecture is x86_64 , the also mentioned Intel Spreadtrum SC9853i SoC's instruction set architecture is x86_64, too. Hence in order to upgrade yor phone's Android you need a Custom ROM compiled for x86_64 architecture. GIYF ...
OK, but since this Panasonic and my Leagoo share the same SoC, they also share the same x64 instruction set, so do I get it right if I say that the custom ROM built for the Panasonic would fit on my Leagoo, or am I missing something?
In theory it should.
OK, I guess I'll have to chance it, and use recovery in case things so south. My phone isn't compatible with Treble, according to this app. Does it mean anything in terms of installing one of the generic system images found here or not?