Yeah, sometimes you have to do what your woman tells you to do.
So, we made this:
And now, we bring on stage the other decorations (made entirely by herself)!
Sunday, December 6, 2015Posted by catacc at 7:00 PM
Yeah, sometimes you have to do what your woman tells you to do.
And now, we bring on stage the other decorations (made entirely by herself)!
Sunday, January 4, 2015Posted by catacc at 5:46 PM
Hello there and Happy New Year!
Extract the "RK29xxImageTools_v2.1.zip" file in the same folder, so all the files contained in the archive will be in the same folder as firmware .img file of the device (not a folder inside another folder).
Rename the image file of the firmware to "wendal.img".
Run the file "Runme.bat" (if your operating system is Windows 7 or 8 or 10, you should run this with administrative privileges - run as administrator) and follow instructions.
Press "1" on your keyboard and then press "enter" key to extract the "wendal.img" file you have in a temporary folder "Temp". During procedure, other .img files will be created, do not alter or open them in any way.
Don't close the batch file (cmd application) yet after the extraction messages. If you do close it, you can run it again but don't press "1" again, you should move to the "2" step of the file by pressing it after all the below steps are followed (locating and modifying parameter file).
Navigate to the "Temp" folder and locate the "parameter" file (does not contain an extension).
Open the "parameter" file with Notepad2 or Notepad++ (not default Notepad from Windows) - search for them on google
Locate the line named "CMDLINE". Here, we will make adjustments regarding the partitions. All names and sizes specified there will have to remain in the same order, do not switch places or arrange them alphabetically or anything.
Because we will modify the size of the "userdata" partition, all other following partitions will have to be moved (by writing the modified position from where they start) with the same amount of the size that we are putting for userdata partition.
If we want that userdata partition to have 2GB instead of 1GB, all other following partitions will have to be moved by 1GB (2GB-1GB).
If we want that userdata partition to have 3GB (this is the size I recommend) instead of 2GB or 1GB, we need to move the other following partitions by 2GB or by 1GB if we had initially a 2GB userdata partition or we have [prepared] previously another firmware with 2GB but we decided that is not enough.
So, locate on the CMDLINE the part with userdata (example: 0x00200000@0x00168000(userdata)). The first parameter (before @) is the size of the partition, the second parameter (after @) is the position from where the partition is starting. We modify the first parameter for "userdata" partition (the size) but for all the following ones, we modify the second parameter (from where to start each of them).
Pay attention that we want to resize the userdata partition (written as "userdata" in the parameter file), not the user partition (written as "user" in parameter file). The user partition (written last in the parameter file) is the partition not where the applications will be installed, but where the user is able to create/move/delete freely folders and files, where all downloads are stored, where all pictures and music files are located after we download them from internet or put with a file manager from our computer.
Modify the size from 0x00200000 (1GB) to 0x00400000 for 2GB or 0x00600000 for 3GB (again, talking about "userdata").
All following partitions will have added the difference we put on the userdata. Each 1GB is 0x00200000, so for userdata to have 2GB, we move by 1GB (0x002 becomes 0x004 - just the 3rd number after 0x is modified). For userdata to have 3GB, we move the other partitions by 2GB (0x006)
It should look like this (example):
For 2GB of userdata
For 3GB of userdata
The numbers from above may differ on your firmware image file, that's why I said that you need to modify only the 3rd character after the "0x".
If you do have other numbers there, you add "0x002" for each extra 1GB you want.
After all numbers are modified, save the parameter file and close it.
Return to "runme.bat" file which is still running or if you closed it, run the file again.
Press "2" on your keyboard and then "enter" key.
The tools are now running again to compile the modification and making a file which will be loaded after that.
Wait for tools to finish and another file will appear "wendal_new.img". Again, do not mess with other .img files that were created by the tools.
After the tools have been finished their tasks and a file "wendal_new.img" has been created, this file is the one that you will load on the device, with all modifications that you've made.
You can rename this file as you like or you can keep its name.
Extract the "RKBatchTool1.5En.zip" file (or the version which applies to your chipset or you can try with this 1.5 version to load a RK30 chipset) and it should create another folder.
Navigate inside this folder and run the file "RKBatchTool.exe".
For best results, this file should be run on a Windows XP computer or a 32bit Windows 7 computer because correct android drivers are a little hard to be found for 64 bit Windows 7 or above operating systems.
If the device (phone or tablet) is not powered down, do it now. If you forgot to make an Android backup (called nandroid) from recovery menu, you can do it also now and after that you should restart the device and connect to a computer and copy the files from internal or SD card storage onto that computer (because all internal storage will be erased when we load the new firmware file).
The correct procedure to access the recovery menu and to perform a nandroid backup is available on the internet for your specific device model.
Connect the USB cable to the computer, but not yet to the device.
With the device powered off, try accessing loader state of the device. The correct procedure for your specific device model can be found on internet (I think), but usually, try one of the following and while pressing the keys connect the USB cable to the device:
a) press volume + and keep it pressed while connecting the cable;
b) press volume + and keeping it pressed, simultaneously press also the power button of the device while connecting the cable
c) press volume - instead of volume + and keeping it pressed, connect the cable
d) press volume - and power button of the device and keep them pressed while connecting the USB cable
e) if the device has a physical button for Menu, press this button and keep it pressed while connecting the cable
f) press volume + and Menu buttons simultaneously and while keeping them pressed, connect the cable
g) press volume - and Menu buttons and connect USB cable
Again, the specific key combination for your device model can be found on internet if none of the above is working.
You could try these combinations with USB debugging turned ON (from Developer menu after unlocking it by pressing several times on build number from Settings-About section of your device).
When one of the above steps is working, a message pops up on the computer saying that a new device was discovered and needs drivers to be loaded. When this message is displayed, release all buttons of the device.
If your device was never connected to the computer in this manner (not the usual way to connect the device to the computer while the device is powered on), the computer will not find any drivers to be loaded. It will display an error message that no drivers could be found for your device.
Don't worry, just open the device manager and update that device drivers (with the exclamation mark or question mark - Android device), pointing to search automatically or manually to the folder where "RKBatchTool" is extracted. In that folder will be available another folder called "Driver". Point to the correct folder inside that also, for 32 or 64 bits operating system of your computer and wait for drivers to be correctly installed.
During this procedure, do not disconnect the device from computer and do not press any of its buttons.
When all above steps to connect the device to the computer are correctly followed, the "RKBatchTool" will display a green rectangle where the device was discovered and connected. Usually, this green rectangle is on number "1" because you are connecting only one device at the time in loader state.
In "RKBatchTool" application on the computer, press the browse button (those 3 dots from upper right) and navigate and select the image file you have prepared ("wendal_new.img" file or the one you have renamed).
The file properties will be read and it will wait for your instructions.
Although it's said there that the firmware file was loaded, it's not yet loaded onto the device, but it's loaded in the application.
Warning again: doing the following will erase your device. You will lose all files from internal storage of the device.
Extract the SDCard from the slot if you have an external one, just in case anything goes wrong and you have important files on that storage device.
When the green number is displayed and you have selected the new file to be loaded on the device, press "RESTORE" button from "RKBatchTool" application. This will load the new file, erasing at first all data from the device.
If you didn't select the correct loader state of the device when connecting it to the computer, the number of the device may be pink or magenta instead of green. You can press the "SWITCH" button from "RKBatchTool" to put the device in the correct loader state and after that, when the number is green press "RESTORE" button.
DO NOT PRESS "Upgrade" or "Clear" buttons.
After you have pressed the "RESTORE" button, wait for the application to finish the tasks.
First, it will format the device, then it will load the new firmware and after that it will verify the loaded firmware.
DO NOT PRESS ANY BUTTONS of the application and DO NOT DISCONNECT THE DEVICE and DO NOT RESTART OR POWER OFF THE COMPUTER (pay attention with desktop computers, use an UPS device or a laptop).
Failing to do so, it will brick (damage) your device. It may or it may not be recovered if this happens, so be careful.
After the verifying step of the firmware has finished, the device will restart. At this point, you can close the "RKBatchTool" window and disconnect the device from computer.
Depending on the firmware image file, the device should enter in the recovery menu by itself and erase (format) the partitions (also without the user interaction). If it doesn't, it may hang at boot loader screen (animation).
If this happens, or if you want to be sure that everything is prepared correctly, try to access the recovery menu of the device and perform an erase or format of the "cache" and "dalvik" partitions and after that, select "restore factory settings" from that menu also and wait to finish all tasks.
Then select "restart" or "reboot system" from recovery menu and wait for device to power up correctly.
If the procedure is successful, your device should power up and enter android configuration wizard where you select language, wifi, google account and so on.
If the device don't do that, try to access the recovery menu and format cache and dalvik partitions, then select to restore factory settings.
If this is unsuccessful, try to load again the firmware file by connecting the device in the loader state and performing the procedure with the "RKBatchTool" application.
If this is unsuccessful also, re-trace the steps for the whole procedure to modify the file, correct the mistakes and load the new file.
If this is also unsuccessful, connect the device in loader state and load the original firmware file of the device (the one that you used it to be decompiled, it's the file renamed "wendal.img") to restore a functioning device (all settings and files will be lost for the moment, but you will have a device on which you can install Titanium Backup application and extract apps and settings from the nandroid backup you may have performed earlier and restore the one you want.
If this procedure didn't have any success and you are not able to restore a functioning firmware file and your device cannot boot anymore, well, you had bad luck.
I did warned you several times, though.
Try to pray more at your cat goddess or spaghetti monster or whatever you worship or you can try to search more on the internet how to restore a bricked device (soft brick - meaning only the software is damaged, the hardware of the device was not affected if you didn't dropped on the floor or no hammers were applied due to frustration :D )
Ok, so let's say your device has booted correctly. If you go to the Settings menu of the device, Storage area, the amount of storage space for the application should be displayed around the value you have prepared. It will not be exactly the same, due to the fact that some internal applications of the android operating system will have reserved some space from that total amount.
So, if you have selected 3GB for applications storage size, it should be around 2.8 - 2.88GB available.
The rest of the partitions will be resized accordingly. If you have 8GB of total amount of internal storage, it should be 3GB for applications, 0.5-1GB for other internal storage space (may be hidden) and the rest of 4-4.5GB available for user to download files and whatever.
Now, start to install any applications you want from google play store or aptoide or wherever until the first 1GB space is used. If it's successful and you can install more than 1GB of applications on a 2 or 3GB userdata partition (or even more if you dare and have the internal storage space), then you will enjoy using your device.
Otherwise, the manufacturer or producer of the device put some limits in the firmware (hard coded limits) and even that the storage space is displayed larger than 1GB, the android operating system will not let you install more than that.
It will display errors after reaching the 1GB limit or it will let you install apps but when you are trying to access the app, that application will start and run with errors or even it will not start at all. Maybe some other user files will be deleted or even corrupted on the external SD Card if you access them from the application which seems to be "installed" after the hard coded storage limit.
If you are happy with the modifications, I am glad that I was able to help you.
If you bricked your device, I have warned you about this possibility and you should try to find where is the error.
If you don't want to do it, you should have not tried in the first place to perform such modifications and you should go back to your apple device. :P
Requirements: 8GB or more internal storage, 50% or more battery capacity, the correct image firmware for the device, the correct application for computer, the correct drivers and operating system.
Goal: making a cheap device to last longer on the moral (technical) obsolescence.
Satisfaction: getting a little nerdy experience and learning a useful trick for many devices.
This procedure can be applied for any Rockchip device, for any userdata limits if you have the storage space. You have to adjust accordingly the size and starting point of the partitions.
Sunday, June 15, 2014Posted by catacc at 3:41 PM Posted by catacc at 3:38 PM Posted by catacc at 3:13 PM
Ghid construit PC
Garantia monitoarelor LCD/TFT
Test viteza internet
Fun / Miscelaneous
From the best games sites
Inspirat de telefoanele SonyEricsson
The Secret Of Monkey Island - Special Edition
Tales Of Monkey Island - Episodic Series
Alan Wake - Remedy (XboX)
BulletStorm - EpiC (XboX, PS, PC)
Gears of War 3 - EPiC(XboX)
Insanely Twisted Shadow Planet
Links removed. I will try to display here only mild thoughts.
about : blog
Minimal resolution: 1280x1024px.
Tweaked for Firefox and also compatible with Internet Exploder v6 and up (some restrictions apply).
If something is not OK on Chrome/Opera/Safari, please let me know.
Locatie: Bucuresti, Romania
Varsta: 32 de primaveri
Interese: nu prea multe, deloc materiale - in general tehnice
Acest blog foloseste codul Blogger, modulele vechi si noi Blogspot (majoritatea HTML), un pic de cod gasit pe site-uri tutoriale si multa inovatie in adaptarea tuturor (babeste, dar merge).