|Latest product reviews|
I bricked my mini trying to update from 1.3 firmware to 1.4, there is definately something wrong with 1.3 firmware because you can not get back into flash mode once you have a failed flash. I found the 2 outside screws were T3, my T2 screwdriver did not grip the screws very well, T3 fitted perfectly. Also, I tried a genuine Samsung cable for Samsung galaxy, the computer recognised the mini, but rkbatch would not see the device, I tried many times disconnect and re-connect but rkbatch would not see the mini, as soon as I changed to the usb cable that came with the mini, rkbatch saw it instantly, and it flashed fine.
I don't know if the early cube devices came with bad usb cable, but my cube is only 2 weeks old, it came with 1.3 firmware installed and it has a very good quality usb cable, much thicker than my samsung one and very well moulded ends. I would try original cube usb cable first if you are trying to unbrick your device, because I tried for ages with my Samsung cable and I could not understand why the computer saw the cube mini connected and in flash recovery mode, but rkbatch would not see the device. It drove my crazy.
I would also appreciate any help in getting my u30gt-H working again.
Read all the posts and tried everything but either I'm doing something wrong or its a goner!
Booting normally just gives me the white screen of death.
I can get into the Recovery menu ..
... even when i do an ADB update and it completes, it aborts the installation
Tried using the RKTool but that doesnt work anymore either (sometimes i get a blue tag but never green anymore)
Tried putting may `update.img` files onto an sdcard but the system doesnt boot off my sd card.
Guys I am really stuck and frustrated.
Any help appreciated!!
I downloaded new usb drivers called RockusbDriver. Forced windows to install drivers from the AMD64 folder.
Then my tab showed up as green in the RKBatchTool UI. The rest worked as intended.
Hope something like this will work for you man. Its frustrating as hell trying to get this stuff to work.
Thank you for answering.
The device is found and a generic device driver is installed - "Android composite ADB Interface" under "libusb-win32 devices".
On a sidenote ... i did get the RKBatchTool 1.5 to see my device and mark the block green but when trying to flash my device with RESTORE or UPGRADE options it simply fails. (I have tried many update.img files)
Yes, I read the same thing. I tried several diffrent cables myself last night and the one that worked was a samsung data cable for my galaxy s3.
Removing your old drivers couldnt hurt at this point. Maybe try to do a search for the RockusbDriver and point to the x86 folder and force install. Mine showed up as Rock306 in my devices. I right clicked on the batch tool to make sure it was running as administrator.. Then in the batch tool it showed up as Rock306 green square with 8-4 numbers under. (no clue what these numbers are)
also I used kasty-cube_u30gt_h-41-110-rooted firmware for mine. I selected upgrade not restore. Then the batchtool started spamming success messages and the green box changed to yellow flashing as it was updating. Hope this happens for you to man!
Im a relative noob to the flashing scene. But for what its worth I forgot to mention I was able to get into the recovery tool on the tablet and did wipe the cache and tried a system restore to no avail before I figured out that USB drivers may be what I needed.
Mind if i ask, when you uninstalled your drivers, what did you see in your device manager and under what heading.
Did you just uninstall the driver and plug the cable back in and try to boot again or did you plug the cable in, hold power & + for a few seconds and then boot into a black screen (if you know what i mean)
If i boot into a white screen - i get drivers called "CUBE U30GT-W Gadget USb Device"
If i boot into the black screen after pwr & + i get "Android composite ADB Interface"
I do have kasty-cube_u30gt_h-41-110-rooted firmware
I only get green if i boo the second way - i also am trying to use my s3 cable.
Feels like the answer is really close (frustratingly so)!!!
Yes, mine said Unknown device so I knew it was being recognized my comp just didnt know what it was.
I had to plug mine into the ac charger and hit power and volume + to even get mine to the dead droid screen. Thats when I wiped the cache in the tablet. After I wiped cache I got unknown device.
It wouldnt do a darn thing at my computer but give me the usb bloop (usb connected sound) then immediately the USb error sound (the sounds when you unplug your usb device)
Like i said tho, even when it did the bloop, debloop sound it showed up as unknown device.
Those rockusb drivers are the official drivers for the Rockchip inside of these tablets. Thats why I figured what the hell and tried them.
Again, thanks for trying to help.
I wonder if i could ask, just to see where your device driver sits in your device hierarchy, would it be possible for you to tell me under which header the device now sits (eg: Universal Serial Bus Controllers -> U30GT-H) or a screenshot of you device manager.
I think the driver must be the key! Just have to try to figure out how to get mine there (another difference is mine is AMD 64 but there is a driver for it under rockchip)
Rockchipusb drivers and batchtool included. This should be the download link.
Most Users Ever Online: 749
Currently Online: yogavich
Currently Browsing this Page:
Devices in use: Desktop (94), Phone (9)
Guest Posters: 43
Moderators: globula_neagra, exelletor, JochenKauz, Oma7144, cracktech