Forum switched to read-only as of 2020/06/01
|Latest product reviews|
The stock speaker volume is rather low. I followed coreo at slatedroid.com and installed Viper4Android from the Play Store. The speakers are loud now. Here are my settings:
- upon starting of Viper4Android, choose cortex A9/A15 with NEON
- under PHONE SPEAKER
- MASTER POWER: Enable checked
- EXTRA LOUD
- Enable checked
- Select Effect Strength Extreme
- Max Gain 10x
- Max Output 0 dB
I hope somebody can help me. When I press the 'VOL+ and Power' to get in Recovery, I got the green android lying down and the red triangle. In Windows 8 I got a error 10 on the Rockusb device. I tried several version of drivers, even with signing off in W8. I am desperate now, because I cannot upgrade the firmware anymore.
Does somebody know what the problem is? And how to solve it?
(at this moment I run version 1.0.9)
@pierre118: You use the Rockchip Batch Tool to flash this ROM, which is a .img file, not .zip. So don't go into Recovery. You press and hold VOL+ and plug the USB to your PC.
@pierre118: Here's my quick instruction I posted earlier:
@Jrain9: Power off your tablet. Hold down Volume Up (the volume rocker's right if you are holding the tablet with the screen facing you and the front camera is at the top of the screen) and plug in the USB cable. Once your PC (assuming running Windows) knows a device is plugged in, you can let go on the volume rocker.
If it's the first time you plug in your tablet to the PC, you have to install the driver. Go to Device Manager and look for the unknown device icon. Upgrade the driver and select the appropriate driver directory (in the Rockchip_Batch_Tool_v1.7.zip under RockusbDriver), x64 for 64 bit OS, x86 for 32 bit OS - under each directory you'll find the OS such as Windows 7.
Once the driver is installed successfully, you can start RKBatchTool.exe. In RKBatchTool, for FW Path, choose the image file you have unzipped (.img). Then hit the Restore button.
All this is actually in the Rockchip Batch Tool tutorial.
@bklm1234 Thanks for your answer!
But what is described I already did more than 1 time, but without any success. I still got the error 10 in the the Windows device manager on the Rockusb device. I even booted W8 with driver signing off, but makes no difference. It stays on code 10. I even tried it on my Surface Pro, but with the same result.
Is there another way to flash firmware on the X2, maybe from SDcard?
I hope someone can help me with this.
@pierre118: are you running 32 or 64 bit Windows 8? I'm guessing the driver installed is the wrong version.
If you run Windows 8 64-bit, you select the driver from Rockchip_Batch_Tool_v1.7\RockusbDriver\x64\win8
If you run Windows 8 32-bit, you select the driver from Rockchip_Batch_Tool_v1.7\RockusbDriver\x86\win8
so on so forth
This ROM is in .img. Recovery takes .zip. I don't know how to repackage this ROM into a .zip. Besides, the stock Recovery (I haven't booted into it to see) may not have the ability to flash a zip file. You'll then have to get CWM Recovery. There's a version of CWM out there which is supposed to work with the X2. But I had a hard time getting the flashing tool to work so I gave up. Besides again currently the customs ROMs for X2 are in .img. CWM will only be good for backing up your current ROM 'cause it doesn't flash .img. But then flashing a .img will totally erase your internal SD. So what you back up with CWM will get wiped. Unless the version of CWM out there is capable of reading/backing up to external SD, CWM is probably not that useful.
@pierre118: When I go home, I'll try to boot into Recovery and see what I get. In the meantime, see if you can get a hold of a Windows 7 pc or Windows XP pc. I have sucessfullyflashed with both Windows versions, haven't tried Windows 8.
Thanks! I will wait if you can boot in to recovery.
Guys, that is normal behavior on a Rockchip based device, when you simply boot into recovery.
A successful restore for any partition other than recovery, using the Rockchip Batchtool will actually write a "batch" of work for recovery to perform. It then reboots the device into recovery, which actually performs the queued up work.
Recovery on a Rockchip device is not like Clockwork recovery at all. It is not interactive and has no user inputs. It requires a properly queued up batch of commands and it simply runs the commands. You are seeing the android on his back, because recovery has no list of commands to do.
Assuming that your drivers are correctly installed and the batchtool is seeing your device, running the restore command using a valid firmware image should write the image to a reserved partition of the device's nand flash and create the batch file telling recovery to write the image to the devices android partition. It then reboots the device into recovery, which should flash the new image to the correct partition.
There is one notable exception to this rule.
If you restore an image to the recovery partition, the batchtool writes the image immediately. There is actually a logical reason for this, as you don't want to have the recovery partition overwrite itself as it is running.
Note that this also mean that if you overwrite your recovery partition with something else, the batchtool will be unable to image any of the other partitions, unless you restore it to stock using the batchtool.
Btw, I figure this out over the course of re-imaging my RK3066 TV stick probably 50 or more times testing Android and Picuntu linux on the device.
Hope this helps.
Most Users Ever Online: 749
Currently Browsing this Page:
Devices in use: Desktop (46), Phone (8)
Guest Posters: 43
Moderators: globula_neagra, exelletor, JochenKauz, Oma7144, cracktech