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
Related
Hello! Yesterday I was putting a custom recovery on my LG p500, and as I am a noob in phones and everything else I fcked up something, and now i have the ''fastboot mode started'' screen. Now, on this http://www.androidpure.com/unbrick-lg-p500-stuck-at-fastboot-mode-due-to-bad-recovery-flash/ page, i have downloaded all the things listed there.
Now, my computer recognizes the phone, it doesn't open the ''removable disk F'' as it has always, but it says it is recognized.
WHen i downloaded Android SDK, on the page they say I should have a directory on disk C, but I DONT KNOW HOW TO INSTALL ANDROID SDK!! When i click on SDK manager it just opens a window similiar to cmd prompt, and then the window close after some seconds.. Please help me!!
Also, on that link there is the cmd program open and he says what to write to unbrick it, but I don't understand anything about it!! Please someone help me I am mad!!!
Instead of messing with the entire Android SDK, which isn't needed BTW, why not use Android Flash Recovery to install another recovery? Link for Android Flash Recovery ( AFR ) is in my signature. It's just a simple UI for the fastboot executable from the Android SDK. No command windows to deal with and nothing to type. Point and click...
As per you problem with the SDK, Android can't find your Java installation. Did you install Java 6 or 7 SDK as well?
shinobisoft said:
Instead of messing with the entire Android SDK, which isn't needed BTW, why not use Android Flash Recovery to install another recovery? Link for Android Flash Recovery ( AFR ) is in my signature. It's just a simple UI for the fastboot executable from the Android SDK. No command windows to deal with and nothing to type. Point and click...
As per you problem with the SDK, Android can't find your Java installation. Did you install Java 6 or 7 SDK as well?
Click to expand...
Click to collapse
I got rid of the problem, but if the problem gets back i will use your link! thanks!
Kk connect USB goto sdk and find fastboot binary use cmd. And do fastboot flash recovery /path to SD/
Sent from my LG-P500 using xda app-developers app
TABLET: Fusion5 Premium+ (Re-branded yuandao N90 II dual core RK3066)
ISSUE: The tablet is now stuck in recovery mode (red triangle black exclamation) Stock 3e recovery after a failed firmware upgrade which I think was due to me selecting 'upgrade' and not 'restore'.
Details:
Before this failure rkbatch tool could see my device.
I have now tried rkbatch tool on 4 different PC's with different OS'es (Win8 x64, Win7 x32, Win XP x32, Linux x32) and at least 5 different USB cables using the latest driver_assist and batch tools or Linux equivalents.
Can not get rktools to see device in flash mode on any of them.
All the PC's can see it in ADB though.
“adb devices” reports device in recovery mode.
There's no fastboot and no shell which reports *“exec*'/system/bin/sh' failed:*No*such file or directory” but sideload appears to work.
“adb ls” of /sys /system /data etc show they are all empty.
I have the found the following firmwares specifically for this device
:LINK withdrawn
:LINK withdrawn
PM for the links
Unfortunately both of these updates are *.img files which as I can't connect using rkbatch
tool, I can't flash.
I have tried zipping them and flashing from sideload or from SDCARD both both fail, from sdcard the error is “no update found”. In sideload mode it reports “installation aborted” after the verifying the update stage. I'm quite sure there is more to creating a working update.zip but unsure of the details.
My question is does anybody no of a way to convert these supplied .img files into a format, prbably update.zip, that I can either install via sideload OR from sdcard?
Thanks
Hi,
XDA has no section for your device, therefore this would be the best place to ask for help....
>*Android Development and Hacking*>*Android Q&A, Help Troubleshooting
Good luck!
Hopefully you'll find help there. It's in the right section. This is not where to get help, only direction. ?
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
Hello,
I'm actually working with miowork's tablettes but they are not recognized by adb on unix system, I'm actually working on mac.
The manufacturer provided me a driver for windows which is working but it said to me that there is actually no way to make it work on mac or linux.
Devices are MioWork A330 and L130, the first one is not recognized by the system as an android device but as a usb key while the second one is recognized by the system as android device but impossible to see it with the command "adb devices".
Both devices have the developer mode enabled and usb debugging is activated.
How can i do to make them recognized by adb on Unix system ?
Links to devices :
http://miowork.mio.com/product_L13X_enGBR.asp
http://miowork.mio.com/product_A330_enGBR.asp
Thanks for your help.
Hi there,
I'm sorry but I can't find anything related to your question/devices.
Please post that in the forum bellow for more answers from the experts:
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
Good luck
I am using Bacon Root Tool Kit to unlock my oneplus one device. I am following the inbuilt driver installation guide. As per the guide I need to configure ADB after installing the google drivers. In update software's list of devices Android device is not displaying.
chaitut715 said:
I am using Bacon Root Tool Kit to unlock my oneplus one device. I am following the inbuilt driver installation guide. As per the guide I need to configure ADB after installing the google drivers. In update software's list of devices Android device is not displaying.
Click to expand...
Click to collapse
see [FAQ] OnePlus One Frequently Asked Questions
[GUIDE] How-To Guide For Beginners Thread.
This thread will be moved to ONE Q&A, Help & Troubleshooting