Related
{
"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
Micromax Funbook Infinity - P275Development & Hacking
HOT NEWS : CyanogenMod 10 or CM10 (Jellybean) is available for Funbook Infinity P275 and you can install from HERE
This thread is dedicated to Micromax Funbook Infinity P275 as there is no specific forum for it. This deals with Root, CWM, Roms, Mods, etc. You may also share if you found something new about this device...
INDEX
|
|------- About Device
|------- Parts Of The Device
|------- Specifications (HW)
|------- Rooting/Unrooting
|------- CWM Recovery
|------- Installing ADB Drivers
|------- Mods & Apps
|------- LiveSuit Guide
|------- Roms
{
"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"
}
Micromax Funbook Infinity P275 is a Android Full touch bar, based on the ARM Cortex-A8 architecture,collocation Android4.0.3 operating system.P275 provides MP3/MP4 player, camera, camcorder, voice memo. Built-in WiFi function, supports Web surfing and email, bring you perfect Internet, social, email and shopping experience. P275 supports connectivity as WIFI, T-flash card, UART and USB2.0 OTG
Specifications:
HardWare :
Design :
Dimension : 26x209x11.2 mm
Weight : 460g ( Including Battery )
Form Factor : Android Full Touch Bar
Antenna : FPC Antenna
LCD :
Display : 7”,800 x 480,TFT LCD, 16.7M Color
Panel type : Capacitive 5 Multi Touch
Camera :
Image Sensor : CMOS
Resolution : Front 0.3MP / Rear 0.3 MP
Focus : Front FF / Rear FF
Digital Zoom : x4
Optical Zoom : Non
Motion JPEG : Yes
Camcorder : Yes
Flash : No
Video :
Sound Format : Support up to HD 2160P; Support AVI, MPG, MKV, RM, RMVB, MP4, MOV, VOB, DAT, FLV, TS, 3GP, WEBM(VP8), etc. 1080p decoder
Video Steaming : RTSP/SDP over TCP; RTP/RTCP over UDP
Video output : Non
(HDMI)
Audio :
Sound Format - Encoding : Yes
Sound format - Decoding : MP1、MP2、MP3、WMA、WAV、OGG、OGA、APE、FLAC、AAC、M4A、3GP
Ringtones : Yes (64poly MIDI, MP3)
MP3 playback : Yes (up to VBR)
Voice Memo : Yes
External Audio Jack : 3.5mm
Audio amplifier - AWINIC : Yes
Memory :
DDR RAM : 512MB DDR3
Nand Flash : 4GB
MicroSD : Upto 32 GB
(T-flash)
Battery :
Standard 4,000mAh Li-ion
Extended Non
Connectivity :
RS232C : Non
USB 1 Mini : USB OTG,
IrDA : Non
IrRC : Non
Bluetooth : Non
Wi-fi 802.11: b/g/n
Other Options :
Travel charger Adapter : Yes
USB Data Cable : Yes
USB adapter : Yes
Ear – Microphone : No
Motion Sensor : Yes (3-axis supportable)
z
Rooting Funbook Infinity P275
Rooting & Unrooting Funbook Infinity P275
Android rooting is the process of allowing users of smartphones, tablets and other devices running android to attain privileged control (known as "root access") within Android's subsystem.
There are two methods for rooting our Funbook Infinity :
1) Root Many Android! by Bin4ry
2) Super One Click by CLShortFuse
Both are very easy methods, but I prefer using Universal Rooting Script by Bin4ry. However, I will post how to root in both methods!
Preparing Funbook Infinity For Rooting :
1) On your infinity tablet, go to Settings- -> Developers options and tap on USB debugging to check (tick) the USB debugging on.
2) Connect the Funbook Infinity with your Windows Computer via USB cable.
3) If it is the first time that you have connected your tablet to your computer, then allow windows to Automatically Install the Drivers for you.
4) Change the Connectivity Option from MTP to Mass Storage in Settings --> Storage --> Options --> USB computer connection
If the drivers are not installed automatically then you nedd to install them manually. Go to 3rd post for the guide on installing ADB drivers manually.
Note : Remove your SD Card from your Tab.
METHOD 1 :
Root Many Android! BY BIN4RY
1) Download Root_With_Restore_by_Bin4ry_v31 : HERE or HERE [OP LINK]
2) Extract & Double-Click RunMe.bat
3) Follow the instructions
4) Connect your tablet to the computer.
5) Then, the program will ask you to go to the tablet and
tap Restore My Data. Do it.
6) Wait till it finishes. Your tablet will restart once.
7) Once the program is done, press Enter.
8) Your Funbook Infinity will be rooted.
METHOD 2 :
Super One Click by CLShortFuse
Note : The program requires Microsoft .NET Framework 2.0+ or Mono v1.2.6+
1) Download SuperOneClick Root v2.3 : HERE [ORI LINK]
2) Open SuperOneClick.exe
3) Click the Root button and wait for a few minutes.
4) You can select Yes, if you would like to test it.
5) Your Funbook Infinity will be rooted.
Unroot Your Funbook Infinity:
i) Use Root_with_Restore_v31
Select the Unroot Option from the list.
ii) Use SuperOneClick
Click on Unroot on the SuperOneClick.exe window.
z
CWM Recovery 6 For Funbook Infinity P275
ClockWorkMod Recovery
Screenshots in updated CWM recovery:
Prerequisite :
Your Funbook Infinity Must Be Rooted In Order To Install CWM.
Credits to dolorespark for posting this.
1) Downlad CWM_6028_P275.zipfrom HERE [Dev-Host]
and Novo_Tools.apk from HERE
2) Put both Novo_Tools_1_0.apk and recovery.img in /sdcard of your Funbook Infinity.
3) Install Novo_Tools_1_0.apk as a normal app.
4) Open NovoTools and grant SU (SuperUser) permissions.
5) Click Flash Recovery in NovoTools and wait for few seconds.
6) Next Click Enter Recovery in NovoTools and You will go to CWM Recovery 6.0.2.8.
Note :
i) If You Want to Go To Recovery :
ii) Switch Off the Tab.
iii) Press and Hold Home And Power Keys at the same time.
or
Use Novo_Tools.(Enter Reocvery option)
Note : This updated CWM reocvery contains the *** Go Back *** option which favours devices like P275 which doesn't sport back or volume rocker button.
Installing P275 ADB Drivers :
If your tab is not rooted, even after trying both Methods, then the problem must be the ADB drivers. Here is a guide for installing them.
1) First, download the P275-Drivers.rar from HERE [Dev-Host] and Extract it anywhere in your PC.
2) Go to Settings > Developer Options > (and tick) USB Debugging ON
3) Connect your tablet to your PC via USB Cable.
4) Open Device Manager (Seach in Start)
5) Under Other Devices, you will see Android with a caution symbol.
Note : If you do not see the Android with a caution symbol, then ADB drivers are already installed in your PC and you don't need to continue...
6) Right-Click on Android and select Update Drivers and a dialog box will appear. Select Browse my Computer for Driver Software
7) Browse for the folder that you extracted earlier and click OK.
8) A warning will appear. Click Install the driver software anyway.The ADB drivers will be installed.
9) The caution symbol will disappear and you will see Android Composite ADB Interface.
Guide by luvk1412 : Post #104
z
Roms & Mods For Funbook Infinity P275
MoDs & AppS
1) Remove Bloatwares
Download Link : http://www.mediafire.com/?oapdvt5n7hw47e4
About :
Type : Flashable Zip
Instructions : Flash In CWM
This will remove all the unwanted or bloatware apps from your Funbook Infinity.
List Of Apps : (will be removed)
-Apps.apk
-E-learning.apk
-Entertainment.apk
-Games.apk
-Livetv.apk
-Movies.apk
-mStore_P275_230812.apk
-Need For Speed The Run.apk
-Weather Widget Tab.apk
-Exchange.apk
-PlusOne.apk
-Tetris.apk
-LiveWallpapers.apk
2) Swap Internal & External SD Card
Thanks to luvk1412
Download Link : http://www.mediafire.com/?2gazncf5z2zx85y
Original Thread : http://forum.xda-developers.com/showthread.php?t=2066307
About :
Type : Flashable Zip
Instructions : Flash In CWM
This mod will swap your internal & external sdcards making your External SD card Internal and Internal SD card External. You can even have a mighty 32 GB internal memory with this mod...
3) Undo Swap Internal & External SD Card
Download Link : http://www.mediafire.com/?qt8ossi4iiyk2l3
About :
Type : Flashable Zip
Instructions : Flash In CWM
This mod will undo what you did in the above mod. This will reset if you swapped your SD cards.
LiveSuit Guide
Guide by EMOBlazeXD : http://forum.xda-developers.com/showthread.php?t=2326368
z
Thread Changelog :
Added advanced specs
Added two root methods
Added CWM recovery
Added Mods
Updated CWM recovery
Added guide for instaling drivers
Things to expect :
Livesuit guide
More CooL Mods
Mod to deodex custom rom
Detailed guide with pictures for installing drivers
CM10 rom (under development)
will the above mod work on p275?
Ganesh A said:
last one
Click to expand...
Click to collapse
will the above mod work on p275?
arunanson said:
will the above mod work on p275?
Click to expand...
Click to collapse
Yes, I tested and only posted here...
Ganesh A said:
Yes, I tested and only posted here...
Click to expand...
Click to collapse
Found Original ROM!
LiveSuit flashable
Some good-guy-greg was generous enough to post a link to Micromax FTP servers, intended for Service Technicians.
And voila! There was livesuit Image for every single micromax tabs.
I am currently downloading it (78%@ 150k).
FTP
Username/Pswd:https://docs.google.com/file
:good:
You guys download it too, as a security.... Who knows when micromax bar this user..
:angel:
Thnks I will add it to my thread...
Sent from my GT-S5360 using Tapatalk 2
Prashnts said:
Found Original ROM!
LiveSuit flashable
Some good-guy-greg was generous enough to post a link to Micromax FTP servers, intended for Service Technicians.
And voila! There was livesuit Image for every single micromax tabs.
I am currently downloading it (78%@ 150k).
FTP
Username/Pswd:https://docs.google.com/file
:good:
You guys download it too, as a security.... Who knows when micromax bar this user..
:angel:
Click to expand...
Click to collapse
somehow i am not able to enter the server...its saying "530 User cannot log in."
Edit : Missed the "m" XD ..now able to log in! =)
Ok, guys...
Thread will be updated with some advanced specs and livesuit flashing guide...
FEEL FREE TO COMMENT!!!
Eagerly waiting for your custom rom
Ganesh A said:
Ok, guys...
Thread will be updated with some advanced specs and livesuit flashing guide...
FEEL FREE TO COMMENT!!!
Click to expand...
Click to collapse
Gr8 Efforts..
Keep up the good work...
Regards,
Amardeep Banga
pratap6789 said:
somehow i am not able to enter the server...its saying "530 User cannot log in."
Edit : Missed the "m" XD ..now able to log in! =)
Click to expand...
Click to collapse
I'd recommend to download early version, as the latest image is 600 MB+ and has some crap preinstalled..:good:
Prashnts said:
I'd recommend to download early version, as the latest image is 600 MB+ and has some crap preinstalled..:good:
Click to expand...
Click to collapse
Yeah, the V2 contains the Virint folder which will be copied to our sdcard...
But, the V2 is compatible with both the variants of Infinity..
Added Advanced Specs
Advanced Specifications Added Guys...
Check it Out...
Question
Ganesh A said:
Advanced Specifications Added Guys...
Check it Out...
Click to expand...
Click to collapse
I want know how to go back to the default Recovery, If I have to?
I am new to this, so please don't mind if its a stupid question.
Waiting for your reply.
Thanks,
amarbanga123 said:
I want know how to go back to the default Recovery, If I have to?
I am new to this, so please don't mind if its a stupid question.
Waiting for your reply.
Thanks,
Click to expand...
Click to collapse
In Stock Recovery, You can't do anything cause you cannot scroll...You can only reboot in stock recovery...
A person who never made a mistake never tried anything new.
- Albert Einstein
Thanks for a quick response
Ganesh A said:
In Stock Recovery, You can't do anything cause you cannot scroll...You can only reboot in stock recovery...
A person who never made a mistake never tried anything new.
- Albert Einstein
Click to expand...
Click to collapse
Thank you for a quick response.
But I want to know how to go back to stock recovery after installing CMW?
The only reason I think I will go back to stock is in situation where in I have to take the tab to the service centre.
Thanks,
amarbanga123 said:
Thank you for a quick response.
But I want to know how to go back to stock recovery after installing CMW?
The only reason I think I will go back to stock is in situation where in I have to take the tab to the service centre.
Thanks,
Click to expand...
Click to collapse
maybe ...just maybe ...flashing the image through livesuit might install the stock recovery...
(i am also new to this... do dont mind me )
amarbanga123 said:
Thank you for a quick response.
But I want to know how to go back to stock recovery after installing CMW?
The only reason I think I will go back to stock is in situation where in I have to take the tab to the service centre.
Thanks,
Click to expand...
Click to collapse
Just flash the live suit image to ur tab...
And it will be as u brought from the shop!
For livesuit instructions...
I will add it to this thread...
A person who never made a mistake never tried anything new.
- Albert Einstein
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.
Intel Android Devices Root / Temp Recovery Session
social-design-concepts said:
Disclaimer:
Before you proceed to the rooting instructions below, please read this disclaimer:
XDA-DEVELOPERS.COM and I are not responsible for what you are doing to your device. You understand and agree that you are doing this at your own risk.
as for warranty the rule of thumb is if you root you should always consider your warranty voided : i will make no claim otherwise on the subject.
i am just a simple hobbyist from Cinti. OH USA i have no intention to buy devices or users getting mad that they were under some impression this wouldn't void the warranty.
if you root you should always consider your warranty voided
Click to expand...
Click to collapse
Tethered Temporary CWM / TWRP Recovery Session :
Note : This is a Temporary CWM / TWRP Recovery Session for some Intel Devices with locked bootloaders.
This recovery is not installed to the devices and has to be launched from a computer ( tethered ) each time you need to access the CWM / TWRP Recovery. . .
WARNING : This Temporary CWM / TWRP Recovery Session is for some Intel Devices with locked boot loaders.
It is not intended for installing custom roms as if the devices has a locked bootloader the device will fail to boot the unsigned images
Intel Fastboot Tethered Temporary Recovery Session Launcher download :
Current Version : IntelAndroid-FBRL-07-24-2015.7z
Generic Instructions for use better instructions coming later just wanted to get the thread up :
notes :
make sure you have downloaded and installed the adb / fastboot drivers for your device . . .
make sure you have enabled developer options / adb debugging under settings on your device . . .
make sure you have download the latest : UPDATE-SuperSU-vX.Xx.zip and place it on your internal or external_sd
1 : download and extract IntelAndroid-FBRL-07-24-2015.7z some where on your computer.
2 : double click the launcher.bat file to start , type " ACCEPT " case sensitive without quotes to continue
check that the tool is reporting as either :
DEVICE STATUS: ADB-ONLINE
DEVICE STATUS: FASTBOOT-ONLINE
If " DEVICE STATUS: UNKNOWN " please check your cable connection and driver installation under Windows Device Manager
If " DEVICE STATUS: UNAUTHORIZED " please check if your devices is displaying an authorization prompt be sure to check Always allow from this computer and then press ok
3 : select the trigger to launch the Temporary CWM Recovery Session support fastboot oem triggers are :
T1 oem startftm ( very few devices support this command , but its the original used so )
devices supported : coming soon
T2 oem backup_factory ( limited devices support this command )
devices supported : coming soon
T3 oem stop_partitioning ( should work on alot of kitkat builds )
devices supported : coming soon
T4 oem stop_partitioning ( probably works on all devices that are supported (Jellybean , KitKat , Lollipop) )
devices supported : coming soon
4 : after selecting the trigger your device should reboot in to fastboot and begin to copy files to your device
note : if your device hangs at the waiting-for-device screen and you see droidboot CMD Waiting on your devices double check that the fastboot driver installed correctly.
note : if you see unknown oem command the trigger isn't supported by your device.
5 : The temporary cwm recovery session should be started at this point select install zip from the recovery menu using vol up / vol down to navigate and power to select
6 : select install zip from sdcard / external_sd depending on where you placed the file and select the UPDATE-SuperSU-vX.Xx.zip you downloaded earlier
7 : confirm the installation
8 : after install completes reboot your device
note :
some devices have limited space under /system and the supersu app wont install
if you don't see the supersu app on your device attempt to install it from the playstore
more than likely the su binary installed correctly but there want enough room on the device for the app.
This recovery uses the CWM Recovery @vampirefo built for the Dell Venue 8 3830 NoModem original thread : Dell Venue 8, CWM, unsecure boot/recovery
You know it's annoying to find this on so many other forums. with other people taking credit for it. sad face : (
APPRECIATE MY WORK, I DON'T DRINK, SO CLICK HERE DONATE NOW AND BUY ME COFFEE
XDA:DevDB Information
Intel Android FBRL, Tool/Utility for the Android General
Contributors
social-design-concepts
Version Information
Status: Stable
Created 2015-07-28
Last Updated 2015-07-28
Supported Devices List / Trigger
Supported Devices List / Trigger
Acer :
B1-730 T2
B1-730HD T2
A1-830
A1-840FHD T3
A1-840 (HD) T3
Asus :
ME170C T2 & T3
ME176C T2 & T3
Dell :
Venue 7 3730 / Venue 8 3830 All Triggers Should Work
Venue 7 3740 / Venue 8 3840 T3
Venue 7 3741 / T3
Venue 8 7840 T3
Iview :
i700 T2 & T3
Kurio :
Xtreme 7 Only had a chance to test trigger T3
Odys :
intellitab 7
Nabi:
Dreamtab model IN08A trigger T3 reported working
Prestigio :
MultiPad Thunder 7.0i
Tesla :
L7 Tablet T3
Tesco :
Op3n Dott 8 T2 & T3
Toshibia :
Excite 7 T3
Links to devices specific threads / forums
Links to devices specific threads / forums
If you have created a devices specific thread / forum for your devices please PM the link so that i can post a link to it here to make it easier to help new users . . . . Please put Intel Device Specific Thread in the supject . Thank You .
The Concept / Source Code
The Concept / Source Code
Collected Device Dumps / Captured OTA Updates
Collected Device Dumps / Captured OTA Updates
Generic / Tips for Unbricking
Generic / Tips for Unbricking
Ahh!
Just my luck lol. Had a feeling I would end up bricked for some reason, maybe I jinxed myself.
Anyways... everything was going ok, I selected trigger 3 to try first, reboots to droidboot (with "waiting for fastboot command") then I select recovery and get android dude laying down with a red exclamation point coming out his belly and it just said "no command" now I am soft bricked, only getting the USB symbal with the white line under it. Please help!
GeeKerGurL said:
Just my luck lol. Had a feeling I wouls end up beicked for some reason, maybe I jinxed myself.
Try to manually boot to droidboot
Anyways... everything was going ok, I selected trigger 3 to try first, reboots to droidboot (with "waiting for fastboot command") then I select recovery and get android dude laying down with a red exclamation point coming out his belly and it just said "no command" now I am soft bricked, only getting the USB symbal with the white line under it. Please help!
Click to expand...
Click to collapse
We can remote around 1130pm est and I'll get you running v8 correct?
Sent from my XT907 using XDA Free mobile app
social-design-concepts said:
We can remote around 1130pm est and I'll get you running v8 correct?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah 3830. Thanks a bunch. Now what do I have to do to remote? I am on a win7 PC with 1gig that is so slow I wanna scream. Also I am in another timezone so how long would that be from now?
GeeKerGurL said:
Yeah 3830. Thanks a bunch. Now what do I have to do to remote? I am on a win7 PC with 1gig that is so slow I wanna scream. Also I am in another timezone so how long would that be from now?
Click to expand...
Click to collapse
1 hour 30 minutes
Sent from my XT907 using XDA Free mobile app
social-design-concepts said:
1 hour 30 minutes
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Okie dokie. Ill be here.
social-design-concepts said:
We can remote around 1130pm est and I'll get you running v8 correct?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Woot!!!YA! no need, I got it back all by myself just had to boot with vol down and go back through the process and everything copied fine and worked this time! :good: thanks a ton for offering to help me though buddy!
BTW trigger 3 works for the 3830 V8 no modem
WOOOHOOOOHOOOOWOOOO! root check cleared, I am SOO happy to finally have root on this thing. Besides my minor hiccup for whatever reason this method was pie too! YAHOO. I went from about to cry to jumping around happy like a crazy person haha.
recovery fstab
What needs to be change for jb 4.2.2?
I am able to open and edit the file.
b.g.
whgarner said:
What needs to be change for jb 4.2.2?
I am able to open and edit the file.
b.g.
Click to expand...
Click to collapse
recovery.fstab may or may not need to be edited for some devices especially if the device doesn't use by label partitioning. What device do you have?
Sent from my XT907 using XDA Free mobile app
asus aa3-600
I have an asus aa3-600-ur10
android 4.2.2
Intel Celeron J1850 Quad-core 2 GHz
21.5" Full HD (1920 x 1080) 16:9
Intel HD Graphics with Shared Memory
2 GB, DDR3 SDRAM
500 GB HDD
The problem I'm having is no usb debugging, only debugging via lan. I can get adb to work but not working with fastboot in the bootloader(droidboot). I have a post about it in this section, search for "aa3-600"
b.g.
Hi, SDC
I know this has been ask before, I searched and couldn't find the answer though, I would like to get the source code for the launchers , I use the Linux version of this method, cause I don't have windows, and would like to convert the recovery.launcher triggers and so forth into a shell script rather that use binary file.
If you have a shell script already can you post it if not, can you post or give me a link to your binary files source code?
tomtom1265 said:
Hi, SDC
I know this has been ask before, I searched and couldn't find the answer though, I would like to get the source code for the launchers , I use the Linux version of this method, cause I don't have windows, and would like to convert the recovery.launcher triggers and so forth into a shell script rather that use binary file.
If you have a shell script already can you post it if not, can you post or give me a link to your binary files source code?
Click to expand...
Click to collapse
I'm going to post the source after I finish getting the thread put together I just wanted to get it up yesterday.
As for doing it through shell scripts the reason its binary is because if /system is mounted or any prebuilt binary has a dependency on a shared library it makes it extremely difficult some times impossible to stop services and unmount /system and such.
But I hope to have everything finish by the end of the day.
Sent from my XT907 using XDA Free mobile app
whgarner said:
I have an asus aa3-600-ur10
android 4.2.2
Intel Celeron J1850 Quad-core 2 GHz
21.5" Full HD (1920 x 1080) 16:9
Intel HD Graphics with Shared Memory
2 GB, DDR3 SDRAM
500 GB HDD
The problem I'm having is no usb debugging, only debugging via lan. I can get adb to work but not working with fastboot in the bootloader(droidboot). I have a post about it in this section, search for "aa3-600"
b.g.
Click to expand...
Click to collapse
You use Linux or windows? If Linux, you may need to use my fastboot binary, anyway if using Linux while in fastboot mode use terminal type lsusb.
Do you see your device listed?
Sent from my T1 using XDA Free mobile app
Root!
Thank you for this!
I successfully rooted my V8 3830 KK4.4 V1.33 no modem with T3 - in about 4 mins. tops.
FYI:
I connected and launched the launcher from the IntellAndroid-FBRL folder. Typed ACCEPT and got the green screen. Chose T3. The tablet rebooted into fastboot and files where loaded, But then fastboot turned red and said "device unauthorized" when CWM popped onto my tablet. (maybe it's suppose to do that, DK) and yes, US debugging was on, I flashed the SU zip, rebooted, all is well. SU updated and working fine. I was able to remove all the crapwear. :laugh:
thank you SDC!
Quick question - Do any of the intel devices have unlocked bootloader?? Thought I read somewhere somebody was able to install a factory 4.3 or 4.2 on a Dell venue and the bootloader unlocked?
NOTE: This tutorial REQUIRES root access for it to work. If you do not have root access you need to get it for this
tutorial to work ( If you are confused on what root is and/or how to install it, you can run a simple Google search )
WARNING: If you have already rooted your device, your warranty is already void. If you have not rooted your device, keep
in mind that rooting and installing custom recoveries, roms, kernels, etc will void your warranty, no way around it. Unless
you do not want to void your warranty, then do not continue with this tutorial.
DISCLAIMER:I WILL NOT be responsible for any possible damage that may/may not occur to your device by following this
tutorial, you decided to go through with it, therefore it is YOUR FAULT if YOU damage YOUR device. If you point the finger
at me for any damage caused to your device by following this tutorial, myself and the community will laugh at you.
You'll need a few things before we get started:
1) A Windows Computer
2) Your device & your respective device's USB charging cable
3) 7Zip / Winrar installed on your computer
4) CHECK TO MAKE SURE YOUR DEVICE HAS ROOT ACCESS
5) A Web Browser, and, preferably, a video editing software that can render image sequences (Preferably Sony Vegas)
6) Also check to make sure your devices rom supports custom boot animations, if it doesn't, feel free to install a custom
rom that does support custom boot animations.
Lets Get Started!
You'll need to 'generate' an idea in your head of what you want the animation to look like on your device, thinking doesn't
take much effort now does it?
Go to your web browser and download all images, videos, gifs, etc you need for your animation. But keep in mind that the boot
animation is consisted of many individual .png / .jpeg / .jpg images, and a DESC.TXT file (which we'll get to later). The
boot animation cannot be consisted of a .gif or any video of any kind (.MP4, .AVC, .AVI, etc) otherwise the animation will not
play.
Next, take some time to construct your animation in the video editor you should've downloaded ( if you do not have the time,
money, or HDD space to download a video editor needed make a boot animation, you can send it to me and I will happily make it
for you, just know i cannot make 20 animations at the same time. Gather the files needed to construct your animation, compile
them in a simple .ZIP file and upload it to Google Drive or File Dropper, then send me the link to it and once done, i will
send you your new boot animation, free of charge of course )
Once done, render the video you've made as an image sequence ( this setting is different/non-existent on some video editors,
hense why i prefer Sony Vegas ) to a simple and easy place to remember and make sure you render them with a name sequence
similar to the example below.
Example:
BOOT_00001.jpeg
BOOT_00002.jpeg
BOOT_00003.jpeg
BOOT_00004.jpeg
BOOT_00005.jpeg
BOOT_00006.jpeg
CONTINUE DOWN BELOW!
DESC.TXT file:
The DESC.TXT file can be the most complicated part for some users, it involves code that basically outlines how the animation plays,
the amount of images to play, image size, frame rate, etc. It can get pretty confusing. However once you do it once or atleast twice,
it becomes pretty easy. I will now show you how to make your DESC.TXT file.
Here's an example from my Samsung Galaxy S4:
1080 1920 30
p 1 0 part0
p 0 0 part1
To newbies, it can look really complicated at first glance. But it's what these values mean that make the DESC.TXT file the easiest
part of the whole tutorial. Here's the most basic explanation I can give of what these values mean ( All values below are ripped from
the example stated above, values may differ depending on device ):
1080 = Animation Width ( Your devices screen width )
1920 = Animation Height ( Your devices screen height )
30 = Frame rate / FPS ( Frames Per Second ) ( For most boot animations, 30-35 is the best FPS to have )
p = First animation part
1 = How many times this animation part loops ( in this case, only once )
0 = An amount of pauses after the part is finished playing ( in this case, none ) ( Note that the number of pauses can only range from 0-10 )
part0 = Name of the folder where the images for the first part are stored ( Preferably, keep the name of the folder part# )
p = Second animation part
0 = Defines that it loops until Android starts
0 = Defines a pause
part1 = Name of the folder where the images for the second part are stored ( Preferably, keep the name of the folder part# )
In a nutshell, that's how you make the DESC.TXT file for your boot animation.
TYPES OF BOOT ANIMATIONS:
If you are making a one part boot animation, continue down below.
If you are making a multi part boot animation, continue down to 'Multi Part Boot Animations'
One Part Boot Animations:
For one part boot animations, you will only need one folder named 'part0', place all your images into that folder. After that, scroll up
a bit for instructions on how to make the DESC.TXT file.
Here's an example from an older boot animation on my Samsung Galaxy Tab S:
2560 1600 35
p 5 0 part0
Again, these values may differ depending on your device, but for one part boot animations, that is typically what the DESC.TXT file will look
like. This screenshot is what your one part boot animation should look like.
Multi File Boot Animations:
For multi part boot animations, it requires more than one animation part ( part1 or even a part2 ), for this tutorial, I will not go passed
2 animation parts, if your animation is more than 2 parts, pls leave a comment down below. It also requires more code in your DESC.TXT file.
Continuing to use the example from my Samsung Galaxy S4's DESC.TXT file:
1080 1920 30
p 1 0 part0
p 0 0 part1
If you are having troubles at the DESC.TXT file, please refer to the 'How to make DESC.TXT file' section above. In this case, we only have 2
animation parts, so this is what your boot animation file should look like on your pc.
Depending on how you wrote your DESC.TXT file, you may have to do some thinking on your own to determine how to finalize your respective devices boot animation. But for me, part1 loops until Android finishes booting, so i had to go down to the end of the folder i rendered my animation in and select the images that i felt should go into part1 ( again, DESC.TXT files and the amount of images in a part can vary depending on device ). At the end, the boot animation turned out exactly how i intended. For the part1 folder, you may have to do some thinking on your own to get all the images set in their correct directories.
So after all that, you might be asking yourself, "How do we install the boot animation?" Your gonna find out right now.
Installing / Packaging your boot animation:
Once you have your animation set and ready to go, follow the screenshots below, afterwards, you're file will be ready to install.
{
"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"
}
Now that you've done that, copy it to your devices internal storage or a Micro SD card ( if your device has Micro SD card slots on it )
preferably for transfering to internal storage, copy it into your 'Download' folder.
Next, download the boot-animations.apk and install it onto your device ( you should know how to do that, if not, run a Google search ). After
installing it, click on the small '+' icon in the bottom right hand corner of the frame, click 'Install from local storage', and browse your
phones internal storage/sd card for your bootanimation.zip file. Once the application has pulled the animation up, it is recommended to make sure you did everything right by clicking on the play button on the top, it will give you a preview of your boot animation. After confirming you've done everything correctly, you can click the '+' icon below to the right of the preview box, un-check 'Create A Backup Before Installing', then click install. Wait for the installation to complete.
After completion, you should get a 'Success' message in the notification bar.
Before rebooting, click on the small '+' icon, then click 'Manage Current Bootanimation' then click 'Apply' 3 times and let it process. This
is because on some devices, the animation wont play without performing this step.
After all that, reboot your device and enjoy your new boot animation!
If you had ANY troubles at all while following this tutorial, post a comment down below and I will be happy to help you!
Downloads:
S4 Boot Animation: filedropper.com/bootanimation
Boot-Animations.apk: filedropper.com/boot-animationsapk
7Zip: 7-zip.org/download.html
KingOfTheNet said:
NOTE: This tutorial REQUIRES root access for it to work. If you do not have root access you need to get it for this
tutorial to work ( If you are confused on what root is and/or how to install it, you can run a simple Google search )
WARNING: If you have already rooted your device, your warranty is already void. If you have not rooted your device, keep
in mind that rooting and installing custom recoveries, roms, kernels, etc will void your warranty, no way around it. Unless
you do not want to void your warranty, then do not continue with this tutorial.
DISCLAIMER:I WILL NOT be responsible for any possible damage that may/may not occur to your device by following this
tutorial, you decided to go through with it, therefore it is YOUR FAULT if YOU damage YOUR device. If you point the finger
at me for any damage caused to your device by following this tutorial, myself and the community will laugh at you.
You'll need a few things before we get started:
1) A Windows Computer
2) Your device & your respective device's USB charging cable
3) 7Zip / Winrar installed on your computer
4) CHECK TO MAKE SURE YOUR DEVICE HAS ROOT ACCESS
5) A Web Browser, and, preferably, a video editing software that can render image sequences (Preferably Sony Vegas)
6) Also check to make sure your devices rom supports custom boot animations, if it doesn't, feel free to install a custom
rom that does support custom boot animations.
Lets Get Started!
You'll need to 'generate' an idea in your head of what you want the animation to look like on your device, thinking doesn't
take much effort now does it?
Go to your web browser and download all images, videos, gifs, etc you need for your animation. But keep in mind that the boot
animation is consisted of many individual .png / .jpeg / .jpg images, and a DESC.TXT file (which we'll get to later). The
boot animation cannot be consisted of a .gif or any video of any kind (.MP4, .AVC, .AVI, etc) otherwise the animation will not
play.
Next, take some time to construct your animation in the video editor you should've downloaded ( if you do not have the time,
money, or HDD space to download a video editor needed make a boot animation, you can send it to me and I will happily make it
for you, just know i cannot make 20 animations at the same time. Gather the files needed to construct your animation, compile
them in a simple .ZIP file and upload it to Google Drive or File Dropper, then send me the link to it and once done, i will
send you your new boot animation, free of charge of course )
Once done, render the video you've made as an image sequence ( this setting is different/non-existent on some video editors,
hense why i prefer Sony Vegas ) to a simple and easy place to remember and make sure you render them with a name sequence
similar to the example below.
Example:
BOOT_00001.jpeg
BOOT_00002.jpeg
BOOT_00003.jpeg
BOOT_00004.jpeg
BOOT_00005.jpeg
BOOT_00006.jpeg
CONTINUE DOWN BELOW!
DESC.TXT file:
The DESC.TXT file can be the most complicated part for some users, it involves code that basically outlines how the animation plays,
the amount of images to play, image size, frame rate, etc. It can get pretty confusing. However once you do it once or atleast twice,
it becomes pretty easy. I will now show you how to make your DESC.TXT file.
Here's an example from my Samsung Galaxy S4:
1080 1920 30
p 1 0 part0
p 0 0 part1
To newbies, it can look really complicated at first glance. But it's what these values mean that make the DESC.TXT file the easiest
part of the whole tutorial. Here's the most basic explanation I can give of what these values mean ( All values below are ripped from
the example stated above, values may differ depending on device ):
1080 = Animation Width ( Your devices screen width )
1920 = Animation Height ( Your devices screen height )
30 = Frame rate / FPS ( Frames Per Second ) ( For most boot animations, 30-35 is the best FPS to have )
p = First animation part
1 = How many times this animation part loops ( in this case, only once )
0 = An amount of pauses after the part is finished playing ( in this case, none ) ( Note that the number of pauses can only range from 0-10 )
part0 = Name of the folder where the images for the first part are stored ( Preferably, keep the name of the folder part# )
p = Second animation part
0 = Defines that it loops until Android starts
0 = Defines a pause
part1 = Name of the folder where the images for the second part are stored ( Preferably, keep the name of the folder part# )
In a nutshell, that's how you make the DESC.TXT file for your boot animation.
TYPES OF BOOT ANIMATIONS:
If you are making a one part boot animation, continue down below.
If you are making a multi part boot animation, continue down to 'Multi Part Boot Animations'
One Part Boot Animations:
For one part boot animations, you will only need one folder named 'part0', place all your images into that folder. After that, scroll up
a bit for instructions on how to make the DESC.TXT file.
Here's an example from an older boot animation on my Samsung Galaxy Tab S:
2560 1600 35
p 5 0 part0
Again, these values may differ depending on your device, but for one part boot animations, that is typically what the DESC.TXT file will look
like. This screenshot is what your one part boot animation should look like.
Multi File Boot Animations:
For multi part boot animations, it requires more than one animation part ( part1 or even a part2 ), for this tutorial, I will not go passed
2 animation parts, if your animation is more than 2 parts, pls leave a comment down below. It also requires more code in your DESC.TXT file.
Continuing to use the example from my Samsung Galaxy S4's DESC.TXT file:
1080 1920 30
p 1 0 part0
p 0 0 part1
If you are having troubles at the DESC.TXT file, please refer to the 'How to make DESC.TXT file' section above. In this case, we only have 2
animation parts, so this is what your boot animation file should look like on your pc.
Depending on how you wrote your DESC.TXT file, you may have to do some thinking on your own to determine how to finalize your respective devices boot animation. But for me, part1 loops until Android finishes booting, so i had to go down to the end of the folder i rendered my animation in and select the images that i felt should go into part1 ( again, DESC.TXT files and the amount of images in a part can vary depending on device ). At the end, the boot animation turned out exactly how i intended. For the part1 folder, you may have to do some thinking on your own to get all the images set in their correct directories.
So after all that, you might be asking yourself, "How do we install the boot animation?" Your gonna find out right now.
Installing / Packaging your boot animation:
Once you have your animation set and ready to go, follow the screenshots below, afterwards, you're file will be ready to install.
Now that you've done that, copy it to your devices internal storage or a Micro SD card ( if your device has Micro SD card slots on it )
preferably for transfering to internal storage, copy it into your 'Download' folder.
Next, download the boot-animations.apk and install it onto your device ( you should know how to do that, if not, run a Google search ). After
installing it, click on the small '+' icon in the bottom right hand corner of the frame, click 'Install from local storage', and browse your
phones internal storage/sd card for your bootanimation.zip file. Once the application has pulled the animation up, it is recommended to make sure you did everything right by clicking on the play button on the top, it will give you a preview of your boot animation. After confirming you've done everything correctly, you can click the '+' icon below to the right of the preview box, un-check 'Create A Backup Before Installing', then click install. Wait for the installation to complete.
After completion, you should get a 'Success' message in the notification bar.
Before rebooting, click on the small '+' icon, then click 'Manage Current Bootanimation' then click 'Apply' 3 times and let it process. This
is because on some devices, the animation wont play without performing this step.
After all that, reboot your device and enjoy your new boot animation!
If you had ANY troubles at all while following this tutorial, post a comment down below and I will be happy to help you!
Downloads:
S4 Boot Animation: filedropper.com/bootanimation
Boot-Animations.apk: filedropper.com/boot-animationsapk
7Zip: 7-zip.org/download.html
Click to expand...
Click to collapse
Hello,
This forum is for newbies finding their way around XDA Developers, it isn't a development section.
Please post your tutorial here Miscellaneous Android Development Forum, the users looking for the same could use your help.
Thread closed!
Regards
Vatsal,
Forum Moderator.