Database Info

[Completed] KULALA brand chinese tablet need help

i have posted earlier about my problem @ http://forum.xda-developers.com/showpost.php?p=53643114&postcount=747 and @ http://forum.xda-developers.com/showthread.php?t=2795429 and the XDA assist thread was closed so i am having to post here with more info.
i did search for "MT6572" on xda forums for any possible recoveries that might work, but now the only way i can use this tablet is via fastboot.
it doesnt have any recovery or a stock ROM.
further info about the brand and tablet:
their website www.kulala.hk ,
i have submitted query on their also and tried to contact the office in Dubai, UAE where i am located but non are operational no more. so this forum is only place i can get any help with this tablet.
i just want to get this tablet working again any rom will do
thanks.

I've found these threads for your model:
Android Development and Hacking > Android General > [TUT] MTK Root and CWM Guide (Really Easy)
Android Development and Hacking > Miscellaneous Android Development > [PORT] [TOOL] Carliv Touch Recovery for MediaTek devices
Hope it's a solution for you

philos64 said:
I've found these threads for your model:
Android Development and Hacking > Android General > [TUT] MTK Root and CWM Guide (Really Easy)
Android Development and Hacking > Miscellaneous Android Development > [PORT] [TOOL] Carliv Touch Recovery for MediaTek devices
Hope it's a solution for you
Click to expand...
Click to collapse
i dont have adb access no more only way is fastboot i downloaded the CTR but it needed adb access i am not able to use that.

We are not a support forum, but I can tell you that if you can use fastboot, you can use ADB
Go here and follow my guide which is for Nexus 7, but you can use it for all devices
FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND and FILES
and this => [GUIDE][30/10/2013]New To Adb And Fastboot Guide

philos64 said:
We are not a support forum, but I can tell you that if you can use fastboot, you can use ADB
Go here and follow my guide which is for Nexus 7, but you can use it for all devices
FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND and FILES
and this => [GUIDE][30/10/2013]New To Adb And Fastboot Guide
Click to expand...
Click to collapse
i do have those tools/folders (platform tools), but it wont work with adb, here i have taken screenshot to show.
when i was able to boot into stock rom i could turn debugging on and get adb working but now without a rom and just fastboot access only i am stuck.

I can suggest you this links => [Guide] Use your tablet/phone as PC for Fastboot and ADB

Update:
I located the distributor for KULALA brand here and visited their office and they reflashed with stock rom and its working normal now.
I will try to up the system dump or if anyone can guide how i should make a copy of that stock rom so it could help anyone else to use as well. Last time did copy of a stock rom was via adb using MTKDroid Tools and chose the backup option and it made a folder in mtkdroid tools folder of it. If thats how its done ill make a copy and post here.
Thanks for the help.

Ok and good luck
Thread closed

[Completed] ADB to find my device

I have a Senap/ Sainia Pu A35 it's an MTK6589 I tried installing MTK drivers used universal installer Pdanet etc...no use but I did manage to find an install that showed android composite adb interface in my device manager using Xiaomi drivers but my device is not showing up in adb devices. I tried using another phone and install drivers and it workered showed up in adb and mtk droid tools. Switched back my mtk phone no luck tried installing mtk preloaded... Uninstall reinstall drivers... usdeview to uninstall all preloaders USB connections. I have enabled usb debugging and tried different ways to connect usb mass storage, mtp, ptp, etc... But nothing's working. I also tried different cable.

Hi there,
I see you already posted your question in this thread but you also post your question in one of this 2 forums if you don't get an answer there:
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
or
> General discussion > Questions and Answers
Good luck

Thread closed, thank you.

[Completed] Can you help me save my device (Tablet) ?

Hi.
I have done something stupid
Some website claimed that rom manager from clockworkmod would not work unless twrp was installed. (I guess they meant "for getting the CWM Recovery Boot Menu to work").
I had already rooted my device (Denver Tablet TAQ-80053 ARMv7 with Android 4.1.1) but I thought why not flash to TWRP with the file: "CWM-based-Recovery-v6.0.3.3-signed.zip" ?? BAD idea
Now "Recovery Mode" is only the "TeamWin Logo" then BLACK SCREEN and nothingness ??
Everything else is somewhat normal:
1) I can boot normally into the start screen of Android 4.1.1 and run applets etc.
2) I can connect to Windows 7 (x64) and get file access to everything.
But: Any flashing tool for windows cannot "see" my device, and I very much doubt that it could be a driver problem since I get full access to drives and files on the tablet (USB-connected to Windows 7 x64).
Do you have any thoughts about that ? Because to me it seems logical that a working windows-driver would also work with ADB or ... ?
I also tried the ADB installation with SDK etc. Everything installs fluently with no errors but when I do the "adb devices" command no devices are listed at all ?? The command "ADB Shell" returns an error.
Since I know about the settings needed on the tablet I have: set USB Debug Mode to ON and everytime I plug it in I select "Mass Storage Mode" to get file access from Windows; and it works fine.
As stated above, everything works except "boot into recovery mode" and ADB being able to "see" my device. Not even CWM Rom Manager can boot into recovery mode ??
I want to be able to flash a new OS but recovery mode seems to be the only way apart from the USB to Windows. I cannott accept the notion that the device is "almost bricked" just from installing the wrong
recovery image and now I cannot go back .....
I have spent too much time already and I have discovered that I am not the only one with this problem but I cannot find any solution (that actually works) anywhere. So writing to you guys must be my last
hope. The alternative is getting an axe and chop it to pieces just to be shure that it's completely dead and my $150 lost forever; gone out the window :\
Can anyone please advise me what to do ??
/Pete
PS: OMG captcha is unreadable 30 times or more . . . and then the session ran out. Great

Hi there,
I'm sorry but I can't find anything related to your question/device.
Please post that in the forum bellow for more answers from the experts but first you must register an account on XDA forum:
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck

[Completed] [Q] Android APP Emulator - My ASUS doesn't support intel HAXM

My computer doesn't support intel HAXM or virtualization at all. I am learning how to code right now and downloading all the necessary software that I need for the class but I can't seem to understand eclipse and/or what I can use for an emulator?
Any assistance is appreciated.

Hi there,
Reboot your computer into bios (by pressing f2/del .. at boot). There you'll find an option "Intel virtualization" or similar. Enable it, save your settings and reboot.
Then install haxm as admin (installer can be found in Android sdk folder).
For other questions ask directly here:
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck

[Completed] Bricked firephone

. I opened in regular CMD. I opened file directory of adb with desired Rom inside and typed adb sideload (update.bin) (was supposed to be stock firephone Rom )
Loading......
Bla.....
Pressed reboot.
Oy, now fone won't turn on and when I plug it into the computer the computer shows several disks each with a message that they need to be formatted in order to be used. but when I try to it fails and says the disk is read only. Only disk I had some stuff on it
Any hope or is my phone GONE?

Hi,
Thanks for writing to us at XDA Assist.
You can post your question in your device forum help section to get further help:
Fire Phone Q&A, Help & Troubleshooting
Good luck!