Hello.
I'm using mini tablet, unknown brand, chip is rk2928.
I flashed two ROMs on the device, none of them with touch.
I guess I need driver or something, but don't really know what to do.
Any help?
Which ROMs did you flash?
You should flash ROMs specially made for your device, not for any other device.
Even flashing a ROM for a different carrier version of the same device can cause serious problems (AT&T Note 2 ROM on International Note 2 for example)
You will need to re-flash the Stock ROM for your tablet.
Mashed_Potatoes said:
Which ROMs did you flash?
You should flash ROMs specially made for your device, not for any other device.
Even flashing a ROM for a different carrier version of the same device can cause serious problems (AT&T Note 2 ROM on International Note 2 for example)
You will need to re-flash the Stock ROM for your tablet.
Click to expand...
Click to collapse
He is talking about a Tablet with a specific chip, for these chinese tablets, the brand does not matter, its the chipset can flash any roms that are for that chipset only.
Hello.
I'm using mini tablet, unknown brand, chip is rk2928.
I flashed two ROMs on the device, none of them with touch.
I guess I need driver or something, but don't really know what to do.
Any help?
Click to expand...
Click to collapse
your right you have to flash a touch driver, it sucks to try to find it so i am unable to help you though its normal that if the touch does not work you would have to find a touch driver, you have done nothing wrong its just these chinese chipsets suck to develop for.
Related
Hey guys. I tried to port CyanogenMod for my ZTE Blade III Pro ( copy/paste tutorial ) because there is no kernel source for this phone and there are no custom roms for it. It's a MSM8225 device ( 2 cores 1GHz, 512mb RAM, 4" display, 4.1.2 android .... ) I'm a big fan of AOSP and vanilla android so I tried to port cyanogenmod 10(4.1.2) from Huawei Y300. I did all the steps, repackaged the files into a zip archive, installed it with CWM and expectedly ran into bootloop. The phone won't go past the bootanimation. I did a logcat and there are several fatal errors (signal 11) I've searched and I found that this error is being caused because of the kernel (boot.img), and can be solved with flashing the kernel-only after installing the ROM through the recovery. So my question is: What will happen if I try to flash the cm10 kernel made for the phone I tried to flash the CM10 from (Ascend Y300)??? I'm not really sure what will happen, but since they have the same internals (http://www.gsmarena.com/compare.php3?idPhone1=5425&idPhone2=5386) it should work. But I bricked this phone once (different reasons) and they had to replace the main board ( chipset probably ) but luckily I didn't have to pay anything. Will I be able to flash my stock kernel if this won't help booting the ROM??? Is there a possibility that the phone will be bricked that I will have to replace the chipset??? Please help me.
1. Read the stickies
2. You should never flash a port from any device unless you know what you're doing. Even more so if you ported it yourself. You may want to just go back to stock, but since you said there are no kernel sources, I'm guessing there is no way to return to stock, ergo, you might be SOL.
Vuciz said:
1. Read the stickies
2. You should never flash a port from any device unless you know what you're doing. Even more so if you ported it yourself. You may want to just go back to stock, but since you said there are no kernel sources, I'm guessing there is no way to return to stock, ergo, you might be SOL.
Click to expand...
Click to collapse
Well, I actually know what I'm doing, and that it's very risky, and I've flashed ported ROMS like this before, and they never worked, so I know how to recovery from a soft-brick(bootloop), but I didn't know what would happen If I tried to flash kernel made for a totally different phone. But you seem to know quite a bit about Android porting, and I wanna ask you another question. Even though ZTE hasn't released kernel-source for ZTE Blade III Pro (my device), it has released sources for ZTE Blade G, which has the same internals as ZTE Blade III Pro, but features a bigger and higher resolution display!!! http://www.gsmarena.com/compare.php3?idPhone1=5425&idPhone2=5620 Can I use the kernel source to attempt to build cyanogenmod or a completely stock ROM from source??? I know how to do this because I've already been doing it but failed when I came to the step to load the sources. But, still, I'm sure that the display wouldn't work. Thanks anyways...
I've ported from the G300 to the Fusion 2, and you still need to use a modified kernel so it works on your device.
You should also note that while the first two devices have similar specs they are from different OEMs so they could be totally different. Also when porting the displays must have the same res.
Vuciz said:
I've ported from the G300 to the Fusion 2, and you still need to use a modified kernel so it works on your device.
You should also note that while the first two devices have similar specs they are from different OEMs so they could be totally different. Also when porting the displays must have the same res.
Click to expand...
Click to collapse
Thanks again!!!
Hi guys,
Need help to get what kind of phone get into my hands? How to get differences beetwen those 2? All I know its the version with MTK6589.
Also I'm trying to instal some ROM at this phone, and can't get it done. SP Flash Tool is not seeing the phone, same with Odin, when I try to instal ROM from recovery mode it always say: aborted.
Did anyone of you had this phone and manage to be done??
Thanks for advices.
Your first question: We cannot tell you which device to buy/is better. That is a decision for you to make based on your needs.
Your second question: please clearly indicate which device you're having the issue with so we can recommend your next course of action.
thank you
markbencze said:
Your first question: We cannot tell you which device to buy/is better. That is a decision for you to make based on your needs.
Your second question: please clearly indicate which device you're having the issue with so we can recommend your next course of action.
thank you
Click to expand...
Click to collapse
Thank You for the answer. Im not considering buying any of this devices, I just got it from my sister boyfriend to see what can I do with it. That's why I asked do anyone got idea how to check is it HDC or Goophone.
To Your second question: I think its HDC S5, so lets stay on it. I tried to instal ROM via SP Flash Tool and the program didn't find the devices (I was doing everything like in the instructions), same with Odin (which i guess is normal since its a chineese clone). Stock recovery at this phone is in china language so I tried to instal ROM via CWM Recovery and got only information that instalation is aborted.
ROM installed right now is:
model.. sm-g900h
device.. mtk 6589
android..4.4.2
baseband version. G900HXXU1ANCE
Ok well you'll need to ask your question here.
It's not a popular phone and has very little support so you may not find what you're looking for.
good luck
Hi, im using an Iphone 6 Clones (the brand name is HDC) which has MTK6582 chipset on it.
exciting about rom porting, i found a link of Goophone official kitkat ROM, firstly, i thought that it has very similar hardware,
I've managed to flash it using SP Flash Tools. it can boot up, however the touch screen gone mad, it seems it has different calibration. However, after felt that the ROM was unusable, I've managed to revert back to my Stock ROM, however, the touchscreen problem remains the same.
Im thinking, i was accidentally flashed my touchscreen's driver or something.
does anyone here ever faced the same problem?
PS: i've found some possible answer here, but i couldn't pull my script.bin from my device, because the script can't found any script.bin on my device
sites.google.com/site/fixedandoidtouchscreen/how-to-fix
I have a similar problem on an Alcatel device, Pop D3. I haven't found a solution but i will try yours and see. Is your phone stock ROM kitkat? It may be a problem with sp flash tools.
Hi, sir,
My stock ROM is on 4.2 but, the ROM which i've tried is 4.4.. I have managed to downgrade it to the original ones, but it remains the same..
evoluzionne said:
Hi, sir,
My stock ROM is on 4.2 but, the ROM which i've tried is 4.4.. I have managed to downgrade it to the original ones, but it remains the same..
Click to expand...
Click to collapse
The pull script.bin program doesn't work for me either. Idk what is the problem. I think this is specifically for Allwinner chipsets though since those devices frequently get this problem. Read more here
Hi, thank you for the response, however can anyone here have idea how to see detailed spec of the hardware, so that I can find the LCD driver somewhere.
or should I use the "format+download" option on the SP Flash Tools software, so that I have clean device first and then reflash it using the stock ROM.
Best Regards.
Sorry if this has been posted before. I have successfully install a custom recovery but cant seem to find a good ROM that supports this specific device? Can anyone help? I wanted to use the cm-resurrection_remix but when I installed the one i downloaded it says my device is not supported.
You shouldn't flash roms made for other tab2 variants - it would brick your tab! Happylie you flashed the right recovery and it saved your tab.
Right I didnt flash it. Can you recommend a good ROM that is available for my device. The device is so sluggish with the stock rom even after factory reset and removing a lot of AT&T apps
Android-Andi said:
You shouldn't flash roms made for other tab2 variants - it would brick your tab! Happylie you flashed the right recovery and it saved your tab.
Click to expand...
Click to collapse
ellandrydroid said:
Right I didnt flash it. Can you recommend a good ROM that is available for my device. The device is so sluggish with the stock rom even after factory reset and removing a lot of AT&T apps
Click to expand...
Click to collapse
there is no rom for your device, i think. google it. maybe you have luck.
I'm also looking for any usable rom apart from stock. I have an sph-p500 which is technically the same as sgh-i497 but found no roms at all. any help appreciated. all rom links are broken. I know the device is pretty old but I don't want to shred it.
I have an RFinder B1+(14) that works fantastic, it has the 6567 chipset. I also have an RFinder B1 Classic with a 6563 chipset that will not boot into Android 8 on the way, and the ROM has not been easy to find.
I suspect they are NOT compatible, but if I did flash the older radio with newer firmware, I'd be able to reverse the damage as long as I didn't overwrite the preloader.
If the two are, in fact, compatible, it would save me some time.
Are they compatible?
N
shadow460 said:
I have an RFinder B1+(14) that works fantastic, it has the 6567 chipset. I also have an RFinder B1 Classic with a 6563 chipset that will not boot into Android 8 on the way, and the ROM has not been easy to find.
I suspect they are NOT compatible, but if I did flash the older radio with newer firmware, I'd be able to reverse the damage as long as I didn't overwrite the preloader.
If the two are, in fact, compatible, it would save me some time.
Are they compatible?
Click to expand...
Click to collapse
Not without porting them from one to the other, "IF" the sources to do so are available(either stock firmware for the two devices or at least the stock source code for the device the ROM will be flashed on.
I have tried without success to compile software. Of course it can be done, I just haven't got the hang of it (I need to learn though).
If there are other things I can do, learn, etc from this thread, I'm all ears. If not, thank you for the info.
shadow460 said:
I have tried without success to compile software. Of course it can be done, I just haven't got the hang of it (I need to learn though).
If there are other things I can do, learn, etc from this thread, I'm all ears. If not, thank you for the info.
Click to expand...
Click to collapse
There really isn't a 100% all in one get it right the first time guide out there. There are lots of guides that give a general idea of how to port stock ROMs but it will still require trial and error to iron out the details. Do some research to see if there are any specific security features preventing the ported ROM from flashing/booting then see if there are any tricks to bypass those specific features. You may need to unlock the bootloader and dig into trying to modify the bootloader.img located in the copy of your devices currently installed stock firmware file(or the last "official" firmware that was installed on your device before you tried to modify it).