Database Info

[GUIDE] :: SuperPad/FlyTouch2/WWE10 Android 2.2 V2.5 #4325 Froyo USB Flashing ::

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This guide is for:
SuperPad / Flytouch2 / WWE10 Tablets
Make sure you've got the right device.
- Infotmic 10.2" Flytouch2 SuperPAD
- It has 256MB RAM
- It has 2GB Internal Storage
- Android OS 2.1
- Have 2 MicroSD Card Slots
- 1024x600 Screen Resolution
- Infotmic X210 Processor
This ROM is NOT for you if your device is SuperPad 2 / Flytouch 3
- Infotmic 10.2" Flytouch2 SuperPAD
- It has 512MB RAM
- It has 4GB Internal Storage
- Android OS 2.2
- Have 1 MicroSD Card Slots
- 1024x600 Screen Resolution
- Infotmic X220 Processor
-------------------------------------------
Warning: Follow these steps. All of them. If you do, it will work. If you misread or miss a step or skip a step because you are hurrying through the process, it WILL brick your tablet. Flashing is a relatively simple process but it requires patience. If you don't have the time to read all of the directions and follow them, YOU DO NOT HAVE TIME TO FLASH, and stick with your old firmware.
I AM NOT RESPONSIBLE FOR ANY DAMAGE THAT THIS ROM HAS CAUSED. FLASH AT YOUR OWN RISK! SINCE THERE ARE SO MANY CLONES OF THIS TABLET, DON'T EXPECT IT WILL WORK PERFECTLY.
-------------------------------------------
Note: I'm not so good in English and grammar, so bear with me. The images is not so clear co'z im using webcam for fast capture and focusing.
If I made mistakes, corrections are welcome.
:: Super Improvement ::
- Much Faster response, you will notice playing Angry Birds is smoother.
- New Default Application updates
- New Icons
- New 3D Gallery
- Supports Flash on browser.
- GPS is now working, GPS app required to test the satellite lock.
- Youtube on browser working fine if you have fast connection.
:: Known Issues ::
- "Some" RJ45 (Ethernet) Port sometimes not working
- "Some" WiFi unstable
- "Some" 3G Device not working
- Market is still free, no paid apps.
- Save path not on MicroSD but inside your Tablet (fixed)
- When it sleeps, it sleep to power off.
- Youtube App is not working, you need to download another compatible version.
:: Thanks to the Donors ::
- Austin Pc Fixed .Com
- frank rugolo
- pastorb1
:: Credits ::
- stragulus
- dgcruzing
- isergio
- _barsuk_
- Aries on an Android (android tablet forum)
- rgocal (android tablet forum)
- and others who I forgot to mention
This guide is for Windows XP, I'm windows7 user before but I downgrade because I want to use my other old softwares for flashing. If you get the idea you can do this also on windows7.
------------------------------
NOTE:
- For windows7 user Run As Administrator the IUW application.
- 64bit Operating System may not work with IUW application.
------------------------------
NOTE: If your tablet showing version 6.1.5 (559[or higher]) or 0.6.1.2(587) Then you can skip some part of the guide. Scroll down directly to the "Alternative Solution" using MicroSD burning. You still need to download the Android 2.2 Froyo Main Firmware.
------------------------------
:: Preparing the Male to Male USB Cable :: (if you have one skip this)
Ok let's start, what you need is a male to male USB cable, if you don't have one you can make your own male to male cable.
Tools
- 2 USB Cable
- Scissor or Cutter
- Electrical Tape or anything to cover the exposed wire
- Solder Lead (Optional)
- Soldering Iron (Optional)
1. Cut each USB to the nearest tip of the female, to make your USB cable longer.
2. Cut each end of the USB to expose the wires and copper wires.
3. Now you can connect each end of the USB, and twist each wires, you can solder it if you like.
4. Now you can tape each wires, and tape all the wires.
This is the finish product.
:: Preparation for Files and Flashing Procedures ::
*Note: Please PM me if there are missing links.
Download IUW 1.1 Flashing Tool
Download Firmware V2852
Download Uboot - V 0.6.1.2(587) working camera
Download Main Android 2.2 Froyo ROM with Flash 10.1
Download New Ramdisk image to change the path of save files to SDCard1
Download Extra Tools Apps
Updated ROM: 25.11.2011
Download Firmware Froyo 2.2 v2.5 #4325
------------------------------------------------------------
:: Clean up the tablet files ::
- Wipe cache partition
- Wipe data/factory reset
- then reboot.
Remove all microSD so that it will not start burning if you have firmware on your microSD.
Visit this link how to clean the data for your tablet.
------------------------------------------------------------
:: Let's Start ::
1. Make a Folder on your desktop for fast track of your files, I named it Froyo 2.2 and save all your downloaded files here.
2. Download IUW Flashing tool, and save it inside the folder of your desktop.
3. After download, unpack it inside the folder.
NOTE: Your tablet should be full charged, and connect the charger while flashing, just to make sure it will not drain much power on your tablet. Don't forget also to remove all your MicroSD cards from the tablet.
4. Since your done making your USB Cable, your tablet should be off and plug the other end USB to the PC and plug the other end on your tablet USB Port between the headphone jack and SDCard Slot 1.
5. Open the IUW application, select Link USB on the left side. And on the Link information the DV (driver) is greyed, because it's not detecting the tablet with driver.
6. Power up the tablet with this combination Power + Menu button for few seconds until you see the message on your tablet "Communicating with PC..."
7. A New Hardware notification will pop up on your PC Screen.
(you have 2 minutes to setup this or the tablet will boot normally)
Select Advance, Next.
Browse the driver from your desktop inside the folder "otg_driver"
Then it will install the driver.
The flasher will turn to green.
:: FLASHING V2852 ::
This rom will only run on tablets which display a version number in the bottom-right "Infotmic" screen when first turned on.. If yours doesn't display a number there, you will need to flash firmware v2852 first.
8. 'Choose a wrapped image' press the "..." button Select the IUS file "WWE10B_Android_393477-v9full.ius"
9. Click 'burn' to flash the tablet.
This picture is flashing the tablet.
10. After burning finishes, plug out the USB cable and press Reset, then restart the device.
:: Flashing UBOOT ::
11. Open UIW application, and connect your tablet USB to PC.
12. Select "Link USB" on "USB Mode:" select "Expert Mode" Uncheck all except "UO".
13. Browse the "u-boot-nand.bin" the one with working camera.
14. After flashing this is the result.
15. Your screen with start to flicker, it will start to initialize.
16. I will take time to load up, until you are in display calibration.
:: Flashing IMAGES ::
17. Power off your tablet, and prepare again the UIW to flash the main android 2.2 firmware.
18. Click Link USB, and select Expert burn.
NOTE: Use the other Ramdisk.img fix you download, not from the flash10.1-android2.2 folder.
19. Power up the tablet with this combination Power + Menu button for few seconds until you see the message on your tablet "Communicating with PC...", if the Dv is green your ready and click the burn button.
20. I will take time to load up, until you are in display calibration and your Done!
:: Alternative Solution ::
If you cant burn the main android image using USB method. You can try the MicroSD card method, but this is only applicable if your tablet will display the version under the InfoTMIC start up logo.
Lets make a bootable MicroSD, to convert the file size to 700~705MB, you need a MicroSD at least 1GB.
Download WinHex with MicroSD Clone Image.
1. Open your WinHex
2. Click Tools->Disk Tools->Clone Disk->
3. On Source Raw Image: click the file button.
locate the "aben.start sector" file, click open.
4. On Destination Medium: click the drive button.
locate the Physical Media of your card reader/MicroSD, ok.
5. Fill in the Start Sector with 0 (zero).
6. Click OK, and WinHex pop up will appear, click OK and it will start cloning the image file to your MicroSD.
7. A notepad will pop up that you are done cloning the image, close and press OK on the pop up message.
8. Close WinHex, and safely remove the card reader/MicroSD.
9. Plug the card reader/MicroSD again, and do a quick format.
10. If you successfully formated the MicroSD to 700~705MB then create an "android" folder, and copy all the main image files on the folder. And your Done! :: If you fail there are some other reason, some card reader is not working properly, try to find another card reader, if your phone has MicroSD Slot and able to communicate and serve as card reader, you can use this also.
- ramdisk (use the other ramdisk you download)
- system
- uImage
- userdata
some optional or skipped file.
- u-boot-nand (android v2.2)
- zSYS (Flytouch Official Image 3245)
This is what's inside the MicroSD on android folder.
12. After copying the files plug the MicroSD at the top most/Slot 1 between the 2 USB port.
13. And Power On your Tablet, and it will start Flashing just like here on the video. http://www.youtube.com/watch?v=47kf4-Vbba8#t=3
You can also use this MicroSD to downgrade back to 3245 firmware.
Thank you.
Don't forget to click the Thank You button
joshgabel said:
SmaRkieS whats your Paypal email address? i owe you $ worked like a charm!
Click to expand...
Click to collapse
Confirmed that the 3G USB modem Huawei E1752 is working perfectly. Just create an APN and reboot while the Huawei E1752 is in the USB port.. After startup it makes a connection and works fast!
manually created an APN in settings/connections/mobile providers and configured for your local provider. Also enabled data connection, otherwise I won't start searching. After that reboot and it started working. No specials actions required.
:: Google Sync ::
If you want to sync the calendar (basic) and contacts go to:
Contacts-> Menu-> Accounts-> Add Account-> Corporate-> enter data for a google account -> choose the default setting -> set the sync options-> Enter the name
:: z4root USB Debug solution ::
1. Download Launcher Pro.
2. Install Launcher Pro.
3. Tap the Home Button at the upper left, it will let you choose different type of launchers.
4. Select Launcher Pro.
5. Tap Menu Button = or at press the menu button at the top of your tablet.
6. Tap the + add
7. Tap Shortcuts
8. Scroll Down, and Tap the Activities.
9. Wait it will load, scroll down to Settings.
10. Scroll down and look for Development.
11. Press OK without changing the name.
12. On Desktop/Home Tap Development.
13. Check the USB Debugging.
14. Restart if necessary.
15. And your done ready to root.
:: Enabling Live Wallpapers ::
1. After rooting your device, your good to go.
2. Install Busybox Installer.
3. Open Busybox Installer, OK, SuperUser request Allow.
4. If BusyBox is not found, tap Install.
5. Press Back Button on your tablet.
6. Install Terminal Emulator.
7. Open Terminal Emulator.
8. Type this commands.
Code:
su
mount -o remount,rw,codepage=utf8,vfat,xattr,check=no /dev/stl5 /system
cat /sdcard/LiveWallpapersPicker.apk > /system/app/LiveWallpapersPicker.apk
cat /sdcard/libRS.so > /system/lib/libRS.so
cat /sdcard/librs_jni.so > /system/lib/librs_jni.so
sample pic of my terminal emulator, I made a mistake in line 5 but it's ok just retype it.
9. Reboot your tablet.
10. Install your live wallpaper apps.
11. On your home screen, tap the menu button. (near the volume next to back)
11. Tap Wallpaper
12. Tap Live wallpapers
13. Select your live wallpapers, and your done.
sample screen shot.
:: GPS Configuration and Setup ::
Download GPS Test Tool
1. Install that app in your tablet.
2. Go to Settings
3. Go to Location & Security
4. Check Use wireless networks
5. Check GPS Satellites
6. Plug your GPS Antenna.
7. Take your antenna outdoor, if the wire is still long try to place the antenna higher.
8. Connect to your WiFi.
9. Run the GPS Status application.
10. Wait for 5~20 mins for satellite discovering and locking.
11. Wait for 5 satellite lock on and you are done.
12. Run your Google Maps, and your locked to your location.
This is the picture number of satellites and number of locked satellites.
The GPS is very accurate.
:: Dismantle/Dissemble of Superpad/Flytouch2 ::
http://www.androidtablets.net/forum/gome-flytouch-ii/14255-inside-my-superpad.html
===========================================================
This is my screen now.
with new virtual keyboard.
I also try swapper2, they say it can improve the performance. This is my Terminal Emulator.
Other Useful Guides here.
http://forum.xda-developers.com/showthread.php?t=1067746
http://forum.xda-developers.com/showthread.php?t=1048776
http://forum.xda-developers.com/showthread.php?t=831178
-------------------------------------

Good work
25-12-2012 -updated links
Download IUW 1.1 Flashing Tool iuw1.1-english.rar - 291.98 KB
Download Firmware Froyo 2.2 v2.5 #4325 - 4325.zip - 212.16 MB
Download Uboot - V 0.6.1.2(587) working camera u-boot-nand.zip v0.6.1.2(587).zip - 130.13 KB
Download New Ramdisk image to change the path of save files to SDCard1 Ramdisk_SmaRkieS.zip - 166.06 KB
Barsik recovery for superpad flytouch - recovery_rd.zip - 1.32 MB

Thank you, cause this people are lazy enough to open the pdf/docx file instructions hehehehe.
I made some mistakes on my post, please post some corrections and suggestions are welcome also.

Thank u for your instructions. Its the first time I manually try to flash my pad so I had to flash to 2852 rom first and it does but when i restart and check my version build it is still on build 1561 (flashing with usb cable).
Tried couple of times can u help me out?

kolk11 said:
Thank u for your instructions. Its the first time I manually try to flash my pad so I had to flash to 2852 rom first and it does but when i restart and check my version build it is still on build 1561 (flashing with usb cable).
Tried couple of times can u help me out?
Click to expand...
Click to collapse
Can you see the version under the InfoTMIC start up logo?
If you can see it then you are ready to update using MicroSD method.

@smarkies
no there is no version number
first time I connected to pc it said found new hardware but no driver. There I selected the otg driver in the package.
Burntool does connect and goes up from 0 to 100 procent (very quick about 7 secs.) when i burn but when i check im still on my previous build.
After that I tried to update to other firmware using update.zip on winhexed sd card. This did work so now I am on 1623 build.
after that I tried again using burntool but still didnt work out.
In the folder containing the 2852 rom there are also two folders
0.6.1.2_1.4.587_OV2655 and
0.6.1.5_1.4.587_GT2005
both contain uboot and uboot nand files is there something I have to do with them before I can flash?
Any advice?
Other thing I noticed: in recovery menu there is a line saying:
e:can't open / cache / recovery / command
It didnt stop me from update with update zip but could it be the reason burntool isnt working for me?

kolk11 said:
@smarkies
no there is no version number
first time I connected to pc it said found new hardware but no driver. There I selected the otg driver in the package.
Burntool does connect and goes up from 0 to 100 procent (very quick about 7 secs.) when i burn but when i check im still on my previous build.
After that I tried to update to other firmware using update.zip on winhexed sd card. This did work so now I am on 1623 build.
after that I tried again using burntool but still didnt work out.
In the folder containing the 2852 rom there are also two folders
0.6.1.2_1.4.587_OV2655 and
0.6.1.5_1.4.587_GT2005
both contain uboot and uboot nand files is there something I have to do with them before I can flash?
Any advice?
Other thing I noticed: in recovery menu there is a line saying:
e:can't open / cache / recovery / command
It didnt stop me from update with update zip but could it be the reason burntool isnt working for me?
Click to expand...
Click to collapse
dont touch any file inside the folder of 0.6.1.2_1.4.587_OV2655 and 0.6.1.5_1.4.587_GT2005.
Try to burn the UO first, u-boot-nand.bin the one with working camera, if not try this another u-boot-nand.
Then burn the Main Image Android Rom.

Thanks for the quick repy to be sure I wont Brick my Pad
for the uo file I use Uboot - V 0.6.1.2(587) or uboot - 0.6.1.5 (587)
and for the ROM files I only use files from the 20110416-v1001 folder?
If so I will burn right away

kolk11 said:
Thanks for the quick repy to be sure I wont Brick my Pad
for the uo file I use Uboot - V 0.6.1.2(587) or uboot - 0.6.1.5 (587)
and for the ROM files I only use files from the 20110416-v1001 folder?
If so I will burn right away
Click to expand...
Click to collapse
I abused my pad flashing many times, and still it is alive, It will brick if your USB cable is poorly made, or overpowered that will fry the motherboard of your tablet, just like what happen to other people.
the safest way to flash is microSD, but it is tricky with this froyo update that's why I risk on flashing using USB.
V 0.6.1.2(587) this one has working camera. But you can try both uboot to display the version under the InfoTMIC logo. But I use V 0.6.1.2(587) coz I want the camera to work fine.
Yes the files inside the 20110416-v1001 folder except for the u-boot-nand inside.
If the USB flashing doesnt work you can try the alternative, using the microSD.

Thank u very very much worked like a chime.
camera and wifi are working I used uo V 0.6.1.2(587)
will play with it tonight to see what else it can do now
Greetz

kolk11 said:
Thank u very very much worked like a chime.
camera and wifi are working I used uo V 0.6.1.2(587)
will play with it tonight to see what else it can do now
Greetz
Click to expand...
Click to collapse
Glad you made it! Check out the speed and the Gallery is now 3D
So you did the UO burn first then Main Image?
Confirm this and I will revise my post.
Co'z I burn my tablet the other way. Main Image then UO.

Yep U0 first than main Rom
Only thing is market has only free apps
but doesnt matter can get apps all over the internet

kolk11 said:
Yep U0 first than main Rom
Only thing is market has only free apps
but doesnt matter can get apps all over the internet
Click to expand...
Click to collapse
Thank you for the confirmation.
Confirm this again.
First: WWE10B_Android_393477-v9full.ius burn
Second: UO burn
Third: Main Image burn
Check my post, applanet can help you with that hehehehe.
This is my screen now.
with new virtual keyboard.
I also try swapper2, they say it can improve the performance. This is my Terminal Emulator.

IUW does not work with 64 bit
Please add in the OP that some on other forum sites have confirmed that IUW does NOT work with any 64 bit operating system.
I will link to reference if I come across it again...
For Development USB debugging options for Z4Root, you may also want to link to my post HERE.

quick tip for windows 7 users, picture 6 will not happen, at least it didn't for me, you need to navigate to devices and printers, find the unknown device, and manually install the otg driver

Works as advertised.
I bricked my tab first, but got it up and running again with your step by step guide. Many thanks!

I followed your instruction for SD card and it worked perfectly. I now have the 3925 version on my Superpad and it seems to be working well. Definite improvement on Angry Birds(which I play way too much) and Home Run Battle 3D. WiFI works fine, don't know about GPS or camera as I don't really use them, but I will check just for curiosity sake Seems to be faster and I have had no random lockups that I had with the v5 I had on previously. I will report back as I use it. Thanks for all the great work!

Jiggity Janx said:
Please add in the OP that some on other forum sites have confirmed that IUW does NOT work with any 64 bit operating system.
I will link to reference if I come across it again...
For Development USB debugging options for Z4Root, you may also want to link to my post HERE.
Click to expand...
Click to collapse
Yes, that's why I made it with Windows XP, and we are aware that 64bit OS is so choosy in terms of software compatibility.
About the USB Debugging, I already made a guide after the Flashing/Burning guide.
caravanman said:
quick tip for windows 7 users, picture 6 will not happen, at least it didn't for me, you need to navigate to devices and printers, find the unknown device, and manually install the otg driver
Click to expand...
Click to collapse
Yes, It is self understanding, there is a note above I use windows XP, but the idea is still there.
If you like to contribute for a guide in windows 7 is welcomed.
nullandvoid said:
I bricked my tab first, but got it up and running again with your step by step guide. Many thanks!
Click to expand...
Click to collapse
You are welcome, enjoy your new faster tablet.
woodeman said:
I followed your instruction for SD card and it worked perfectly. I now have the 3925 version on my Superpad and it seems to be working well. Definite improvement on Angry Birds(which I play way too much) and Home Run Battle 3D. WiFI works fine, don't know about GPS or camera as I don't really use them, but I will check just for curiosity sake Seems to be faster and I have had no random lockups that I had with the v5 I had on previously. I will report back as I use it. Thanks for all the great work!
Click to expand...
Click to collapse
Thank you so much, but I would like to suggest to remove the long quote of my post, just to make the thread clean.

SmaRkieS said:
Thank you for the confirmation.
Confirm this again.
First: WWE10B_Android_393477-v9full.ius burn
Second: UO burn
Third: Main Image burn
Check my post, applanet can help you with that hehehehe.
FOr your confirmation I directly made the UO burn and than burned the main image burn never touched WWE10B_Android_393477-v9full.ius
Where can I find your post on applanet to get market running?
Thanks in advance
Click to expand...
Click to collapse

kolk11 said:
SmaRkieS said:
Thank you for the confirmation.
Confirm this again.
First: WWE10B_Android_393477-v9full.ius burn
Second: UO burn
Third: Main Image burn
Check my post, applanet can help you with that hehehehe.
FOr your confirmation I directly made the UO burn and than burned the main image burn never touched WWE10B_Android_393477-v9full.ius
Where can I find your post on applanet to get market running?
Thanks in advance
Click to expand...
Click to collapse
pmed you.
Click to expand...
Click to collapse

BlueBerry NetCat M-12 FirmWare Development

Dear open developers community I managet to fully root BlueBerry NetCat M-12 Tablet PC (a.k.a rebranded Cube H30GT) using "remount" exploit, here is my contribute:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
REQUIREMENTS:
* Android SDK with ADB (guess you have this, if not, main files are included in permaroot.zip attached below)
* RockChip RK3066 USB Driver (see attachments below)
* Root/UnRoot script (thanks to Bin4ry from this thread, see attachments below)
* Micro USB Cable to connect Tablet and Windows Desktop PC (Linux is unsupported for now due to manufacturer limited driver distribution)
WARNINGS
1. Using this tutorial will make firmware/software changes on your device(s) but I am not responsible for any damage it could cause.
2. Following steps below will probably VOID YOUR WARRANTY. Read carefully your reseller warranty terms and conditions, and make your decision. It is all up to you.
3. I am not obligated to respond to future questions and/or support, it is my time and good will. If you must, ask here in this thread, there is no need to send me private messages to me because i wont read them at all.
4. You will spot that i dont recommend making any nand backups in this howto - is because I am not aware of any working method for backup M-12. I onlu can imagine dumping whole partition images to your EXTERNAL_SD and flashing back through bootloader but I did not tested that for now.
#GET ROOT
STEP-BY-STEP HOWTO
1. On your tablet PC go Settings -> Developer Options -> Turn on USB Debugging
2. Now You need to manage your Android Debug Bridge recognize your Tablet PC. You can check if it already works by typing this command in command prompt (in ADB folder, or wherever if you extracted adb into windows/system32)
Code:
adb devices
It should give you list of attached devices (something like this: 0123456789ABCDEF device) you should recognize your device if is connected. From my experiences it wont work the way manufacturer described, therefore you need to install patched RK3066 SoC driver you downloaded (this post below). To do so you must right click on My Computer -> Manage -> Device Manager, find your Unknown Device and install driver manually by selecting search folder manually, where you extracted RK3066_ADB_PATCHED.rar content respectively to your OS version (use correct 32-bit or 64-bit driver). Reboot your PC, go to device manager to check if Android Debug Bridge is there:
And You can repeat "adb devices" once again in adb to verify:
3. Now is time to obtain temporary root. To do so, simply navigate command prompt to wherever You extracted adb.exe and type following command:
Code:
adb remount
It uses common JB exploit, which exists in BlueBerry NetCat M-12, alowing you to get temporary root access via ADB shell until next reboot. You can stop at this point and push any system file You want (ie /system/etc/hosts) and set permissions. But if you want permanently rooted device, you need to push SuperSU.apk, su, busybox,... manually via adb before next reboot. Lucky for you, there is a script (permaroot.zip thanks to Bin4ry) which can do it all automatic with just few clicks. Download it from attachment below, extract somewhere on your hard drive run permaroot.bat and have fun.
Comming soon...
++ Flashing through Bootloader (via RockChip Batch Tools) HowTo ++
++ Illustrated Hardware disassembly guide ++
++ There is one custom ROM ported for another device and tested by me, which works in M-12 like a charm. It is purified JB ROM, rooted and without bloatware. I will post it ASAP ++
++ If i be able to obtain original Blueberry firmware dump, i will make CWM Touch based recovery image. Any interested owner of original BlueBerry NetCat should supply me with F/W dump, so if you are one, PM me please ++
++ If I be able to make Cube CWM Touch recovery work I will share (I managed to extract and install it from supersport900 ROM but it wont mount partitions for some reason) ++

BlueBerry NetCat M-12 Disassembly Guide
+++ BlueBerry NetCat M-12 HardWare Assembly +++
Tools needed:
1 x 1mm Torx Screwdriver (pictured below)
2 x sharp plastic departer for simultaneous two-side gently disassembling plastic parts (any Credit Card or guitar pick will do)
Step-by-Step Guide for servicing (H/W repairs, forced bootloader, etc) your BlueBerry NetCat M-12:
* Torx screws are located along port side, noted the difference on Torx and Cross screw types between some devices - Picture 5
* Some BlueBerry NetCats M-12 dont have left speaker - Pictures 20, 25 and 26
* BlueBerry NetCat M-12 has different stamp (OEM Logo) on backside - Picture 14
** Note LED and short circuit testpoint locations for forced bootloader mode which will be described later in more details - Pictures 25-32
Picture 1:
Picture 2:
Picture 3:
Picture 4:
Picture 5:
Picture 6:
Picture 7:
Picture 8:
Picture 9:
Picture 10:
Picture 11:
Picture 12:
Picture 13:
Picture 14:
Picture 15:
Picture 16:
Picture 17:
Picture 18:
Picture 19:
Picture 20:
Picture 21:
Picture 22:
Picture 23:
Picture 24:
Picture 25:
Picture 26:
Picture 27:
Picture 28:
Picture 29:
Picture 30:
Picture 31:
Picture 32:
Picture 33:
There is a PDF with all images in attached archive.

+++ClockWorkMod based recovery image for BlueBerry NetCat M-12+++
CWM Touch 6.0.2.7 (Thanks to Typhoon.X)
CWM Touch is Direct-Touch-Input CWM Recovery image: you can use touch gestures to navigate through menus, but I still prefer old-fashioned way of navigating through menus by using Volume +/- for <UP> and <DOWN>, and Power button as <CONFIRM> which is also available on our devices.
WARNINGS
1. Using this tutorial will make firmware/software changes on your device(s) but I am not responsible for any damage it could cause.
2. Following steps below will probably VOID YOUR WARRANTY. Read carefully your reseller warranty terms and conditions, and make your decision. It is all up to you.
3. I am not obligated to respond to future questions and/or support, it is my time and good will. If you must, ask here in this thread, there is no need to send me private messages to me because i wont read them at all.
4. You are welcome to make backup(s) before make any change to your device; You can export partition(s) dump or make nandroid backup via CWM based recovery image if you have it allrady installed.
Install:
1. Make sure you have installed RK3066 drivers;
2. Download ClockWorkMod.zip, extract, run RKAndroidTool.exe.
3. Reboot your BlueBerry NetCat M-12 in Flash Mode (turn on device by holding Volume- and Power Button or push "Reboot to Flash Mode" button in RKTool)
4. Push "Flash ROM" button like on image below (all settings are stored in config.cfg so You dont need to change anything):
After procedure is finished (cca 15 seconds), device will be automatically rebooted into CWM Recovery, so it's highly recommended making first nandroid backup.
Usage:
If your device is rooted, you can reboot your device into CWM recovery by typing following commands in terminal emulator:
Code:
su
reboot recovery
Or by using any 3rd party rebooting widget/app, which allows rebooting into recovery.
However, if your device is not-rooted, you can reboot into CWM recovery by typing following commands which exploit temporary root access via Android Debug Bridge (adb.exe on your PC, drivers must be installed):
Code:
adb.exe reboot recovery
or
Code:
adb remount
adb shell
su
reboot recovery
Download CWM Touch based recovery image from Google Drive: ClockWorkMod or attachment below.
Be aware that bootsplash will be changed as you need to replace misc.img, so dont panic if you see Cube logo instead of NetCat.

Hey, CyberianIce, thank you for your contribution for this device, since it's really hard to find anything verified out there, and xda is alwas the safest choice.
I wanted to ask you if you could share the info, or link maybe, to that ported ROM you tested on Blueberry, since I don't wont to brick my device by trying an untested ROM.
Thanks in advance!

I can re-upload from my HDD because I forgot original URL, when I got day off my work.
/CyberianIce via TapaTalk HD

That would be amazing, thank you! And if you could write something about the ROM (when you have free time, of course) just so that I know what I'm installing..

Hi, i wonder how to make a hard reset on this devices, i have tried the normal way, volume(-)(+) + power but nothing is working. Can someone help me? Thanks!!

Hi, CyberianIce, I was wondering if you'll have time soon to upload the ROM, if it's not too much trouble. Thank you!

So far I found this Firmware image working best on NetCat M-12: http://www.rockchipfirmware.com/sites/default/files/cube_u30gt-h_V1.11_TNT_R1.zip
For Flashing use this tool: http://www.rockchipfirmware.com/sites/default/files/RKBatchTool1.5en.zip
(Credits: http://www.rockchipfirmware.com/)
It is great because you can flash it vie Rockchip Batch Tool which means its very useful for debricking. It is 4.1.1 from Cube U30GT-H with all this tweaks:
Brief Description:
-Rooted
-Based on stock rom (2012.12.28)
-App partition is Larger
-Build.prop mod based on SGS II SGH-i777 for improved market
-Added Permission Files for improved market
-Removed Chinese Apps
-framework.jar mod for better gameloft compatibility (Asphalt 7 should now work)
-Added SuperSu, gallery with picasa support, ESfile Explorer, english dictionary fix
-Simplified and pretty boot animation
-Changed Annoying Keyboard Key-press sounds... now they are less annoying (based off Cyanogen sounds)
-Default Background should be changed
-Changed "browser" start page to our Google paid search. Use it (free to use for you) to search the web and you will be helping to support us as we release more free firmware. Can easily change this if you want.
Click to expand...
Click to collapse
Afterwards one can flash CWM based recovery image following tutorial from this post

[ROM][RK3066][U30GT-H]BlueBerry NetCat M12
Based on latest original Cube U30GT-H ROM debranded from BlueBerry NetCat M12
Tested on many CUBE U30GT-H devices
Debloated
Removed China
Custom tuned Kernel for optimum performance and stability (up to 15k points in AnTuTu Benchmark)
Increased /data partition size to 2GB instead of 1GB (reduced internal sdcard partition to 12.5GB instead of 13.5GB)
NetCat BootSplash
Custom android bootanimation.zip
Fully working CWM Recovery 6.0.2.7
HOWTO:
1. Shut down your tablet and start it by holding down Volume + button and insert USB Cable with PC. RK Device will apear, if you have no drivers you can find them in archive.
2. Navigate to RKDevelopTool_v1.35 folder and run RKAndroidTool.exe
3. Click Erase IDB and wait for finish
4. Click Run and wait for finish
5. After procedure is complete, if your tablet don't start automatically in CWM, remove USB and shut down tablet by holding POWER button for 8 seconds (you will hear silent *click* sound from tablet as signal it's off). Now download CWM Base from this XDA post put tablet in download mode (VOL+ and USB CABLE) and flash this recovery (run RKAndroidTool.exe, push Flash ROM button). It is very same recovery from this ROM, but after this flashing is finished, tablet will boot into CWM automatically on it's own.
6. Now install ZIP files from after_install folder via CWM recovery. Format NAND is required if you first time using 2GB Data mod, and int2ext is required for some devices which reported switch between internal and external SD card. You must use an external SD Card for flashing ZIPs and search for files in both internal and external sd card in CWM as you still dont know how CMW see your SD card.
7. Reboot System. All done!
DOWNLOAD
Note: If you are used increase /data to 2GB MOD before, you can just install this firmware via RKAndroidTool. If your /data partition was 1GB before, you may need to install patches from folder after_install via CWM recovery.

All About Cherry Mobile Fuze (Q390)

Fuze (Q390) is an Android-powered smart phone sold by Cherry Mobile, a local brand in the Philippines. Fuze is powered by Mediatek MT6582 Quad-Core SoC (@1.3GHz), partnered with a 1GB RAM and is equipped with a 5.0in TN screen/display panel. Its SRP is 5,499 in Philippine Peso (or approximately US$125.00). Physically, it looks the same as the Micromax A96, but they differ internally (at least in the amount of RAM).
For more info, I recommend that you take a look at this in-depth, detailed review of this device (courtesy of [email protected])
Basic Specifications
CPU: Mediatek MT6582 (@1.3GHz) SoC
GPU: Mali 400MP
RAM: 1.0GB
Storage: 4GB (eMMC)
Display: 5.0" (TN panel, DragonTrail surface) @854 x 480 resolution
Camera: 8MP main / 1.3mp secondary
GPS: Yes
Bluetooth: Yes
WiFi: Yes
Sensors: Accelerometer, Proximity, Ambient Light
USB-OTG: Yes
SIM: Dual Standby
Battery: 4000mah

CMFuze Recovery Installer
CMFuze Recovery Installer
This app can be used to install TWRP for Fuze, CWM for Fuze or Fuze Stock Recovery. There's no need to download a separate recovery file. Its all in this app.
NOTES
Your phone needs to be rooted.
INSTRUCTIONS
Download the APK file
Install in your Fuze
Once installed, launch the app "CMFuze Recovery Installer"
Tap the recovery of your choice from the set of buttons
Confirm to Install
Reboot to recovery to test
DOWNLOADS (Kindly not mirror these files somewhere else without my knowledge/permission)
from mediafire
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THANKS TO
our Creator
TeamWin
ClockWorkMod
Android Open Source Comunity

[ROM] Genesis 1.0
This is simply a debloated stock ROM of CM Fuze
Features
init.d support enabled
zram (compcache) enabled (see compcache/zram at wikipedia)
zipalign on the fly (for newly installed apps)
Seeder (2.0)
Rooted (no SuperSU apk. just get it from PlayStore)
busybox with symlinks
debloated (only essential apps remained)
deodexed
zipaligned
Google boot animation
JB keyboard with swipe
There are no performance tweaks done, as its intention is to become the baseline for ROM porting.
Debloated - removed apps that are optional
removed CM apps and bundled apps
removed CM wallpapers
removed CM tones
removed Google apps that can be downloaded from PlayStore (Map, G+, Calendar, GMail, Notes, Voice Search, etc.)
remained are essential apps, enough to properly run Fuze.
removed faceunlock
removed voice unlock
removed day dreams
removed engineer mode
DOWNLOADS (Kindly not mirror these files somewhere else without my knowledge/permission)
ng0tkul4.CMFuze_GenesisV1.0.zip
INSTALLATION (requires custom recovery: CWM/TWRP)
Backup, backup, backup
Download the zip and flash via custom recovery
(Optional) Factory reset / Data, cache wipe
NOTE: Factory reset is optional, but it may cause bootloop if you didn't do factory reset.
THANKS TO
our Creator
Android Open Source Community
xda-devs

LewaOS v5 for Cherry Mobile Fuze
Flashable via TWRP/CWMR
Ported from official LeWaOSv5 for JIAYU G2F
Should work in all version of Fuze (v4, v5)
Rooted (Lewa is rooted)
Google Playstore included (just download other Google apps from PlayStore if you need them)
No tweaks
No voice unlock/face unlock (removed)
No engineering mode apps (get if from your stock ROM if you need it)
HOW TO INSTALL
Download the flashable zip file (and Google Apps - if you need it)
Install ROM (flash via TWRP/CWMR)
Do factory wipe (cache and data wipe)
DOWNLOADS (Kindly not mirror these files somewhere else without my knowledge/permission)
ng0tkul4.CMFuze_LeWaOS5.1_14.03.28.zip
BUGS
(you tell me...)
TO ENABLE ROOT
- Security Center -> Details -> Permission management -> Perm -> ROOT
THANKS TO
our Creator
Lewa OS5 team/devs (www.lewaos.com)
xda-devs

MIUIV5 for CM Fuze
MIUI V5 for Cherry Mobile Fuze
Flashable via TWRP/CWMR
Ported from Lenovo JIAYU J2F
Should work in all version of Fuze (v4, v5)
Rooted (MIUI is rooted -> Enable in Security App)
Google Playstore included (just download other Google apps from PlayStore if you need them)
No tweaks
No voice unlock/face unlock (removed)
NOTES
MIUI Torch/Flashlight does not work. Just download one from PlayStore like 'Simple Torch'
HOW TO INSTALL
Download the flashable zip file (and Google Apps - if you need it)
Install ROM (flash via TWRP/CWMR)
Do factory wipe (cache and data wipe)
DOWNLOADS (Kindly not mirror these files somewhere else without my knowledge/permission)
ng0tkul4.Fuze.MIUIv5_4.3.21.zip
BUGS
Torch/Flashlight
(you tell me...)
TO ENABLE ROOT
- Security App -> Permission -> Root Permission
THANKS TO
our Creator
MIUI devs (@miui.com)
[email protected] (for his MIUI port for G'Five A800)
[email protected] (for his miui porting guide)
xda-devs

<reserved 5>

thanks sir nice rom can you make not 3 or s4 rom

Nice job sir ... We are waiting for color OS...

colorOS
addictz10 said:
Nice job sir ... We are waiting for color OS...
Click to expand...
Click to collapse
ColorOS --- i'm hesitant to upload because it has few yet ignorable problems. it uses the GB/ICS's /sdcard0/external_sd approach to fetch and enum files... the effect is Oppo Music and Filemanager is failing to get the files (we can use different music player and filemanager). Also OTG storage mounts ok, but there's no easy way to properly unmount it (i.e. unmount via terminal) ... unlike LewaOS that there's an item in its "Storage" settings that can be used to properly/safely unmount the storage.
I will try again after two weeks...

ng0tkul4 said:
ColorOS --- i'm hesitant to upload because it has few yet ignorable problems. it uses the GB/ICS's /sdcard0/external_sd approach to fetch and enum files... the effect is Oppo Music and Filemanager is failing to get the files (we can use different music player and filemanager). Also OTG storage mounts ok, but there's no easy way to properly unmount it (i.e. unmount via terminal) ... unlike LewaOS that there's an item in its "Storage" settings that can be used to properly/safely unmount the storage.
I will try again after two weeks...
Click to expand...
Click to collapse
ok sir... Im still waiting for my fuze...

Just bought a Fuze, and wondering if my unit is defective or it really has issues with the edges of the touch screen. Whenever I use Touchpal X, I have trouble pressing the "a" key. I need to press slightly between "a" and "s" to get it to register.
I have the same issue with some games, when tapping on the very edge of the screen wont register. I have show touches enabled, and it shows the white circle, but the game won't respond at all. Any ideas? I'm running rooted stock rom with gravity box. The only other module i'm using is root cloak for avabel online.
Anyone have similar problems?
EDIT: Found the cause. I had Pie Controls set to 15px so it was eating a lot of screen space for activation. I disabled Pie and it works fine now

How to do screenshot..
Thanks in advance

Elucidator21 said:
How to do screenshot..
Thanks in advance
Click to expand...
Click to collapse
press volume down and power button at the same time..

I need help
I formatted my PC (due to virus) then my Backup for Cherry Mobile Fuze Q390 is lost.
Now my Q390 phone got corrupted and after formatting the phone Baseband is Unknown and IMEI is NULL. I need help by any chance any user with backup that I can use? I cannot write my IMEI because the phone its self has nothing to write on to. Phone is working can boot and etc except the baseband is gone and evidently no IMEI.

phaw16 said:
I formatted my PC (due to virus) then my Backup for Cherry Mobile Fuze Q390 is lost.
Now my Q390 phone got corrupted and after formatting the phone Baseband is Unknown and IMEI is NULL. I need help by any chance any user with backup that I can use? I cannot write my IMEI because the phone its self has nothing to write on to. Phone is working can boot and etc except the baseband is gone and evidently no IMEI.
Click to expand...
Click to collapse
if you can get hold of a NVRAM partition from others phone (not necessarily Q390 - at least same SoC: MT6582), then you can flash it to your phone.
BUT, your phone will have the same IMEI as the source phone. So if you and source phone would use the same SP (Service Provider or network), and IF this SP is strict about cloned IMEIs, they could block this IMEI. Leaving both phones unusable to this network. So if you can get hold of NVRAM partition from somebody living abroad (i.e. foreigner), the better.
if you are rooted, and terminal (adb shell) savvy, you can write it it via dd, i.e.:
$ dd if=/path/of/nvram of=/dev/nvram
or you can flash it via SPFT memory write ("Window" menu -> "Write Memory").
1) Select "Write Memory" tab (after it is shown)
2) Select "EMMC" for the memory setting
3) Select/browse ("Open Raw Data") the NVRAM image for the "File Path"
4) "Begin Address (Hex)" = 0x1800000
5) "Container Length (Hex)" = 0x500000
6) Click "Write Memory"
7) Connect your phone to PC (must be turned off as you may already know)
The NVRAM image could be named as nvram.bin or something else. But it must be a raw image of NVRAM partition (/dev/nvram) from other phone. TWRP can do a backup of this partition by selecting it when you are about to perform TWRP backup.
If you want to temporarily restore your IMEI, you can try MTKDroidTools or Mobile Uncle Tools (apk)

LeWaOSV5.1 for CMFuze
- apps that show as 0.00kb in "All" and "Downloaded" are now shown ok
- added engineering mode to settings
- corrected some misspeling in english translation
- etc.

ng0tkul4 said:
if you can get hold of a NVRAM partition from others phone (not necessarily Q390 - at least same SoC: MT6582), then you can flash it to your phone.
BUT, your phone will have the same IMEI as the source phone. So if you and source phone would use the same SP (Service Provider or network), and IF this SP is strict about cloned IMEIs, they could block this IMEI. Leaving both phones unusable to this network. So if you can get hold of NVRAM partition from somebody living abroad (i.e. foreigner), the better.
if you are rooted, and terminal (adb shell) savvy, you can write it it via dd, i.e.:
$ dd if=/path/of/nvram of=/dev/nvram
or you can flash it via SPFT memory write ("Window" menu -> "Write Memory").
1) Select "Write Memory" tab (after it is shown)
2) Select "EMMC" for the memory setting
3) Select/browse ("Open Raw Data") the NVRAM image for the "File Path"
4) "Begin Address (Hex)" = 0x1800000
5) "Container Length (Hex)" = 0x500000
6) Click "Write Memory"
7) Connect your phone to PC (must be turned off as you may already know)
The NVRAM image could be named as nvram.bin or something else. But it must be a raw image of NVRAM partition (/dev/nvram) from other phone. TWRP can do a backup of this partition by selecting it when you are about to perform TWRP backup.
If you want to temporarily restore your IMEI, you can try MTKDroidTools or Mobile Uncle Tools (apk)
Click to expand...
Click to collapse
under NVRAM folder. It has nothing. Literally nothing inside the nvram folder.

phaw16 said:
under NVRAM folder. It has nothing. Literally nothing inside the nvram folder.
Click to expand...
Click to collapse
correct.
there's shouldn't be anything there...as it is not supposed to be a folder. for one, dd will not work in folder, so i really expect /dev/nvram to be not a folder, rather than a device file pointing to NVRAM partition (offset 0x1800000) of your Fuze's EMMC.
if you see /dev/nvram as a folder/directory (rather than a device file), then something's gone really wrong in your EMMC partitions.

Grawrz said:
Just bought a Fuze, and wondering if my unit is defective or it really has issues with the edges of the touch screen. Whenever I use Touchpal X, I have trouble pressing the "a" key. I need to press slightly between "a" and "s" to get it to register.
I have the same issue with some games, when tapping on the very edge of the screen wont register. I have show touches enabled, and it shows the white circle, but the game won't respond at all. Any ideas? I'm running rooted stock rom with gravity box. The only other module i'm using is root cloak for avabel online.
Anyone have similar problems?
EDIT: Found the cause. I had Pie Controls set to 15px so it was eating a lot of screen space for activation. I disabled Pie and it works fine now
Click to expand...
Click to collapse
Sir the multi touch for Fuze works well your device is not defective. You can't do multi touch if you press already on the left part for me it doesnt really makes sense why'd do that. Example you press arrow up button then you want to press A should you still use your right thumb well in fact the left thumb is already near it furthermore it doesnt affect when your playing games. Its just whenever your using the keyboard.
ng0tkul4 said:
correct.
there's shouldn't be anything there...as it is not supposed to be a folder. for one, dd will not work in folder, so i really expect /dev/nvram to be not a folder, rather than a device file pointing to NVRAM partition (offset 0x1800000) of your Fuze's EMMC.
if you see /dev/nvram as a folder/directory (rather than a device file), then something's gone really wrong in your EMMC partitions.
Click to expand...
Click to collapse
As I mentioned on my post. I factory formatted the partition. Well I sent back the device to Cherry Mobile so that they can repair it.I just have to wait for 1 month.

Sir, how can i install xposed installer properly? I'm getting bootlooped both in MIUI and LEWA rom. I really need this for greenify. Thank you in advance.
Sent from my Q390 using Tapatalk

[GUIDE]How to setup Dual Boot on legacy PC? (BlissOS and Windows 7/8.1/10)

NOTE: This guide is for MBR disks and legacy bios. If you want install on UEFI, this method can not help you.
1- Preparing the installation
a. Download BlissOS Official Roms ISO image.
b. Extract .ISO files into the *\BlissOS\ folder and create a custom size data.img (4gb for fat32 disk - Recomended 16 GB or 32 GB for NTFS disk)
* = Must be disk part. (you can select C:\ , D:\ or another diskparts)
Tips: You can create data.img file with Android PC Toolbox . Create and copy data.img into the BlissOS folder.
2- Setup grup for dual boot
a. Download EasyBCD and install it.
b. Run EasyBCD.exe > Add new entry > NeoGrub > İnstall
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-Click Configure and delete all text. (editing menu.lst)
-Copy and paste that text there..
default 0
timeout 1
title BlissOS
root (hd0,1)
find --set-root ls /BlissOS/kernel
kernel /BlissOS/kernel quiet root=/dev/ram0 androidboot.selinux=permissive SRC=/BlissOS vga=788
initrd /BlissOS/initrd.img
boot
Click to expand...
Click to collapse
Important Note for root settings: You will change these numbers according to where you installed it.
root (hd0,1)
hd0 is your hdd number..
1 is your hdd disk volume number..
-Download Bootice for see disk numbers..
-Run Bootice.exe > Physical disk > Parts Manage - You will see disk parts.. No = hdd disk Volume number
-Rename your boot entry
-Select Count down (you can change timing "10")
-For Windows 10 / windows 8.1 os, check the "use metro bootloader" option.
-Click Save settings.
3-Setup completed. Restart your pc and have fun.

Error 15 file not found

Edit : Changed menu.lst entries. Now,It is set to be the root kernel.

WoltreX said:
Edit : Changed menu.lst entries. Now,It is set to be the root kernel.
Click to expand...
Click to collapse
I hope this works fine, I used the easy installer provided by bliss but it shows error "not all requirement are met" and it opens but I cant click anything.

jhetrosky said:
I hope this works fine, I used the easy installer provided by bliss but it shows error "not all requirement are met" and it opens but I cant click anything.
Click to expand...
Click to collapse
the installer provided by bliss is only compatible with UEFI systems. Is not compatible with legacy. And it will tell you in the output window(top right corner of the installer) which conditions are not met. Just have to look:good:

ElfinJNoty said:
the installer provided by bliss is only compatible with UEFI systems. Is not compatible with legacy. And it will tell you in the output window(top right corner of the installer) which conditions are not met. Just have to look:good:
Click to expand...
Click to collapse
Does it creates a swap partition or use ramdisk. If ramdisk, then compatibility will also depend on the RAM.

TeamPrimeOS said:
Does it creates a swap partition or use ramdisk. If ramdisk, then compatibility will also depend on the RAM.
Click to expand...
Click to collapse
There is no swap created by Bliss
There is a ramdisk

ElfinJNoty said:
There is no swap created by Bliss
There is a ramdisk
Click to expand...
Click to collapse
Thanks for the info, what is the minimum ram required then?

TeamPrimeOS said:
Thanks for the info, what is the minimum ram required then?
Click to expand...
Click to collapse
We've not had an issue with a minimum requirement.
This is an OS booting directly. Compare it to an older phone that can run Android: 1gb? 2gb?safe to assume more ram the better...
Most modern systems have at least 2gb which should be sufficient for any Blisss OS build.
As usual, why not test and find out?
#StasyBlissful

ElfinJNoty said:
We've not had an issue with a minimum requirement.
This is an OS booting directly. Compare it to an older phone that can run Android: 1gb? 2gb?safe to assume more ram the better...
Most modern systems have at least 2gb which should be sufficient for any Blisss OS build.
As usual, why not test and find out?
#StasyBlissful
Click to expand...
Click to collapse
Thanks for the info.
---------- Post added at 07:25 AM ---------- Previous post was at 07:23 AM ----------
jhetrosky said:
I hope this works fine, I used the easy installer provided by bliss but it shows error "not all requirement are met" and it opens but I cant click anything.
Click to expand...
Click to collapse
Can you list the mentioned incompatibilities.

TeamPrimeOS said:
Thanks for the info.
---------- Post added at 07:25 AM ---------- Previous post was at 07:23 AM ----------
Can you list the mentioned incompatibilities.
Click to expand...
Click to collapse
His issue was not due to incompatibility
The installer has some basic minimum requirements which is explained in the OP and Post 2. It also produces a log which would have explained his exact problem. There is also a YouTube video demonstrating the process successfully from start to finish.
*I didn't want their to be any confusion of there being something incompatible or broken about the UEFI Windows installer.exe*

Why the link for BlissOS/Android PC Toolbox has been deleted? I need it for installing Bliss OS on my not uefi pc
EDIT: Anyway I created an USB Bliss image (BlissOS 7.2 stable) and installed successfully on my hd (on a new partition formatted as ext4), I created then the entry with EasyBCD as suggested, changing the hd number, but when I choose the Bliss entry in the boot menu i got the "Error 13, invalid or unsupported executable format” message. Can anybody help me?

nerub config file for a android 9 Pie Bliss
when you click on easy BCD and install a neogrub and open neogrub install file
you i have seen someone has made a code like this >
defaul 0
timeout 10
root (hd0,X)
title 1. Normal Mode - Start Android OS in normal mode.
find --set-root /Android/kernel
kernel /Android/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet SRC=Android/ DATA= CREATE_DATA_IMG=1
initrd /Android/initrd.img
boot
root (hd0,X)
title 2. Recovery Mode - Start Android OS in recovery mode.
find --set-root /Android/kernel
kernel /Android/kernel root=/dev/ram0 SERIAL=random logo.showlogo=1 androidboot.selinux=permissive quiet SRC=Android/ DATA= CREATE_DATA_IMG=1 SAVE_LO
initrd /Android/initrd.img root=/dev/ram0 androidboot.selinux=permissive vmalloc=192M buildvariant=eng nomodeset RECOVERY=1 RAMDISK=recovery.img SRC
boot
--------------------------------------------------------------------------------------
then instead of X you find your partition and like everything but
my ask for help is a code is incomplete as you see a second part a recovery more
start android in recovery mode is incomplete ? does anyone knows the ending of a code ? thank you ....its for making a better boot android neogrub menu and dual boot with windows 10 .......

@WoltreX hey, i just followed your guide for my laptop but after booting it just keeps showing a yellow animation forever any idea what's wrong ?

works on windows 10 surface tablet? without touch or bluetooth bugs?

Any suggestions on what to use if EasyBCD doesn't work states cannot run on (U)EFI.

Detecting android x86 found at Dev/sda6
Stuck at this screen plz help plz.....

Stuck at (blinkin) _
After I press the BlissOS boot option
The last phrase on the text is Android-x86. . . found at /dev/sda4
then around 20 seconds
black screen appear with blinking _ at the top corner

wtf is up with the shady as hell link for the toolbox? Russian website says I have to install Multy App to download it.
This is some bull**** right here, not touching that with goddam 10 foot pole

Do you know if this is possible in Linux Ubuntu?

Mercury Pro - RCA Tablet BootLoop + No way to acess ADB to hard reset

Hi. I bought the Mercury Pro 7" prosumer tablet back in 2014. I installed a google account on it, forgot the password, beat the 10 opportunities, account (and RCA tablet) locked.
Soon after that, I tried to "hard reset" and "factory reset" this tablet, with all the things I found at the moment through forums, but everytime it came to restart, it will lock itself because I forgot my password and it will not allow me to enter nor my gmail account or any other password at all (no text dialogue).
A friend took it to some "expert android shop", but they never got to fix the small tablet (needless to say).
I remember the tablet came with Marshmallow (Android 6?).
It's 2021, and I thought to find the original ROM Image for this device. But tough luck, I haven't found one (from all the forums I've read, you either need to short-circuit or download a similar clone image for the processor and cross fingers so the wifi modem picks up the .img drivers).
In all and all, if anyone of you would be so kind to help me out with this 7+ year plead: I'd like to fix this tablet in 2021, please. Help me out.
The tablet can be switched on, but Loops itself in the "Mercury Pro" logo, after the dogs logo.
The tablet runs out of battery. I charge it up so that it can be turned "on" just 1 time and 1 time only, to access the Bootload menu by power + volume up.
The times I do this procedure, I wipe clean the dalvik cache, user cache, system cache, set the device to factory reset, and reboot after that.
Again, the 2 dog logo appears, but the tablet stops at the Mercury Pro logo in a loop.
Reset pinhole helps to enter the tablet's "hard reset" (power+volume up) boot menu. It reads:
Android Recovery v1.2
RCT6673W-V1MKC-Android6.0-v08-v1.15.0
- Reboot system now
- Reboot to bootloader
- Apply Update from ADB
- Apply update from SD card
- Wipe data/factory reset
- Wipe Cache partition
- Backup user data
- Restore user data
- Root integrity check
- Mount / System
- view recovery logs
- Power off
(Supported API: 3)
In the remote case the so-called "android repair" shop installed a bad rom on this hardware, what are my chances to Factory reset - re-flash the original stock rom for this device?
The Screen works normally, this tablet doesn't have a hardware fail of any kind, it just loops-boot after the 2 dogs logo into "Mercury pro".
I've checked the tablet internally, there are no burnt connections or anything out of the ordinary. Hardware is intact.
Please help me.
Thanks.

Obviously I went for the VIEW RECOVERY LOGS:
--bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
--bionic_open_tzdata: couldn't find any tzdata when looking for GTM!
--bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery (pid 133) on Fri Jan 1 00:00:12: 2010
ro.build.product=RCT6673W23M
ro.build.version.sdk=23
ro.build.version.bases=
ro.build.version.release=6.0
ro.build.version.codename=REL
ro.build.version.incremental
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.ota.host=tablet15.gyrodock.com:2300
ro.product.name=RCT6673W23M
ro.product.board=
ro.product.brand=RCA
ro.product.model=RTC6673W23M
ro.product.device=RTC6673W23M
ro.product.locale=en-US
ro.product.version=1.15.0
ro.mediatek.version.dsk=4
ro.mediatek.version.branch=alps-mp-m0.mp8
ro.mediaversion.release=alps-mp-m0.mp8-v1.51_spyked8127.e_P16
ro.mediatek.chip_ver=S01
ro.mediatek.platform=MT8127
ro.openles.version=131072
ro.revision=0
ro.serialno=
ro.setupwizard.mode=OPTIONAL
ro.setupwizard.suppress_d2d=true
ro.mtk_is_tablet=0
ro.mtk_bt_support=1
ro.mtk_wfd_support=1
ro.have_aee_feature_=1
///
Every time I left a space, there were a lot more lines, but I only copied these.

Is this device also known as mercury tab 7?

@viktorrios
In the linguistic world of Android users, they often use the term "hard reset" for "factory reset", which means that the device is reset to the state it was in when it was launched. In official serious usage, there is no "hard reset" for Android devices.
Your issue is that phone is stucking at boot logo. That can't get fixed doing a "Factory Reset" or even by means of ADB and/or Fastboot. IMO you've to re-flash phone's Stock ROM what can be achieved if phone is accessible by means of ADB - what requires USB debugging got enabled on phone.

Tab E said:
Is this device also known as mercury tab 7?
Click to expand...
Click to collapse
No.
Mercury Pro. 7" inch screen RCA TABLET.

jwoegerbauer said:
@viktorrios
In the linguistic world of Android users, they often use the term "hard reset" for "factory reset", which means that the device is reset to the state it was in when it was launched. In official serious usage, there is no "hard reset" for Android devices.
Your issue is that phone is stucking at boot logo. That can't get fixed doing a "Factory Reset" or even by means of ADB and/or Fastboot. IMO you've to re-flash phone's Stock ROM what can be achieved if phone is accessible by means of ADB - what requires USB debugging got enabled on phone.
Click to expand...
Click to collapse
ok. this is one step forward.
Thank you for your reply.
I found this site, but it doesn't have the stock rom:
ROMs | RCA

Be careful download your stock rom from unverified/ unofficial websites. May contain malware

What makes me wonder is; I can access the fastboot menu, I can CLEARLY read the entire log, but the OS is not reached during boot (logo loop). What makes it possible that I have a corrupted library?
Also: If I could find the stock rom and flash it from an SD card: How possible is it from the fastboot menu?

For anyone else who is reading this thread, here's another site with ROMs:
RCA Download Latest Firmware | Flash File | CFirmware - Mobile Phone Flashing, Unlocking and, Latest Firmwares Available.
www.cfirmware.com

Fastboot hasn't a menu ( GUI ) it's a CLI.
Look inside here:
How to Flash Stock Firmware via Fastboot Commands
In this comprehensive post, we will show you how to flash stock firmware of any Android device via Fastboot Commands.Sample Fastboot Command sheet included!
www.droidwin.com

I found an explanation of one of the errors:
I: no boot messages
I: Open /cache/recovery/comand fail error= no such file or directory locale is [(null)]
stage is []
fb0 reports (possibly inaccurate)
The Unable to open DRM node: No such file or directory issue seems to indicate that there is no DRM driver running on your device (or that it failed to initialize). DRM support is a prerequisite for using this tool, as you can see. Most platforms supported by cedrus should also have DRM support, so you probably need to enable it in your kernel config and/or in the board's device-tree file.
Closing since this is not an issue of the tool but a setup issue instead.
I think I need to upload the entire message Log, maybe someone could help. So far I already know the "driver" is not booting and there is no mount of the OS. Everything else is there, and ready to receive an image. It seems the tablet was so wiped off that it doesn't even have an OS.

jwoegerbauer said:
Fastboot hasn't a menu ( GUI ) it's a CLI.
Look inside here:
How to Flash Stock Firmware via Fastboot Commands
In this comprehensive post, we will show you how to flash stock firmware of any Android device via Fastboot Commands.Sample Fastboot Command sheet included!
www.droidwin.com
Click to expand...
Click to collapse
There is another log report that says: error/system/framework/arm/boot.oat check fail
E:Error:/system/framework/oat/arm/wifi-service.odex has been modified md5on Thu Jan 19 01:38:12 2017
System check: FAIL!!
I: Open /cache/recovery/command fail errno = No such file or directory
local is [(null)]
cannot find/open a drm device: No such file or directory
ro.board.platform=mt8127
ro.build.id=MRA58K
....
....
ro.build.type=user
ro.build.user=builder
ro.build.product=RCT6673W23M
ro.build.flavor=RCT6673W23M-user

This site has an RTC 668xxxx image. Will it work?
Download RCA Stock Firmware For All Models | Root My Device
Download RCA Stock Firmware and flash it in your Android device using a Flash tool to get back the native Android experience again.
rootmydevice.com

For anyone else reading, I remember I got this RCA tablet from Amazon years ago. They were out of stock. Recently they are selling the item again: https://www.amazon.com/RCA-Keyboard-Marshmallow-Charcoal-RCT6873W42KC/dp/B01M7TSY16
And guess what?
All along the ROM version my tablet had (from the so -called-experts in Android store in my story) put the wrong ROM version.
So Amazon indicated it is: RCT6873W42KC the rom.
Googling, I found: https://naijarom.com/rca-rct6873w42m
And the site looks legit. The scatter file is there and everything matches 1 to 1 to the STOCK image.
This site also has links: https://androidmtk.com/download-rca-stock-rom-for-all-models
My question now:
Whenever I plug the USB cable in my computer, (even after installing the ADB drivers), it says that windows 10 cannot recognize the USB device.
I am ready to flash using the SP Flash tool and the ROM file, but I can't -for the love of me- make contact from the PC to the tablet.
Could anyone help me with some work around suggestions, please?
Also: Why can't I just drag-drop all scatter ROM image to the microSD and Boot from recovery using "Apply update from SDCard"?

Ok so far everything was going full sail until I hit this brick road: Apparently I need a better USB cable. I've tried 3 different USB cables, but the device becomes unstable on win10 (switches on and off, and the "connected USB" sound dingles every 10 seconds.
Please help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

viktorrios said:
Ok so far everything was going full sail until I hit this brick road: Apparently I need a better USB cable. I've tried 3 different USB cables, but the device becomes unstable on win10 (switches on and off, and the "connected USB" sound dingles every 10 seconds.
Please help.
View attachment 5265921
Click to expand...
Click to collapse
Is the stock rom for your device?
And the reason you can't just apply update from SD card is that the scatter rom doesn't have Meta inf and updater script. So the recovery can't install that

Yes, I checked this is the CORRECT Stock Rom for the RCA 7" Tablet Mercury Pro
I've also installed the "legacy hardware drivers":

viktorrios said:
Yes, I checked this is the CORRECT Stock Rom for the RCA 7" Tablet Mercury Pro
I've also installed the "legacy hardware drivers":
View attachment 5265979
Click to expand...
Click to collapse
After you installed the drivers did you restart you Computer?

No, I didn't restart the computer. Let me do that.
I also tried the "newest" micro USB to USB cable I have...
I hope this works.

This is a driver problem. https://tehnotone.com/windows-10-mtk-vcom-usb-drivers-for-32-64-bit-drivers-installation-tutorial/ check this guide out. Don't use the drivers from the above site, just use the driver you instslled