Related
for the t-mobile g1 with 1.6 firmware and some number stuff like drc92 and other G ones that won't cooperate..
to mod it from a stock (t-mobile nl) rom.
What u need :
1 sd-card (preferably more then 128mb)
1 pc running windows (i run win 7 ultimate)
1 usb cord
1 phone-internet connection (there is a wifi version too but since i find it not neccesary i wont link it. instead if you dont have phone internet : just download the packages on pc and put them in the G1)
1 app from market called : mybackup (you can use it for backing up contacts and stuff.. backup to sdcard and copy it to pc)
Backup
-download app MyBackup from the google marketplace and make a backup of programs and contacts (if you dont have phone-internet then get it from pc)
Preparing Gold Card:
- insert sd card into G1 and format it (whatever sd card and whatever format (there is only one on G1 hehe so go find it. also format is to be found in G1.)
- attach to pc and copy the RC7 image(DREAIMG.NBH) on the sd card in the G1 (do not detach from pc, i know you wanted to)
- goto appstore and download terminal emulator (as it says like that)
- open Terminal Emulator on G1
- type:
cat /sys/class/mmc_host/mmc1/mmc1:*/cid
- write down the code somewhere, its ur CID thingy
- push backbutton
Reverse the CID:
Begin: 1c5356555344202010051cc3b7008cf4
1c 53 56 55 53 44 20 20 10 05 1c c3 b7 00 8c f4 (yes i copied it from you thnx - normal code... add the spaces so your CID looks like this (your own CID not this one )
f4 8c 00 b7 c3 1c 05 10 20 20 44 53 55 56 53 1c - reversed one (note the couples are reversed)
00 8c 00 b7 c3 1c 05 10 20 20 44 53 55 56 53 1c - now change the first two digit to 00
so you will have something looking like this: 008c00b7c31c0510202044535556531c (this is example CID so use ur own!)
- goto revskills and get a goldcard image with the code ur having now. revskills page
- now get the mail and save the attachement in a dir
Making your Goldcard:
- right-click and open as admin Hxd editor
- in HxD editor :
- goto extra menu and open disk > choose psysical disk > ur sd card
- goto extra menu and open disk image > choose the received file from mail called : goldcard.img and press ok on the popup saying some about 512
- now go to this tab goldcard and goto topmenu and edit>choose select all and then topmenu again and copy
- now go to first tab (ur sdcard) and select 00000000 to 00000170 with mouse (mark it)
- goto top menu and select edit> write
- now goto top menu and save
- pull the G1 out of pc
- yes you can
- ok now pull the battery out (or shutdown if u have the time)
- press camera button+power so it will give this rainbow 3 color shizzle
- you see a gray screen saying some words you probably wanna read.
- now press power to confirm overwrite the rom thing
- reboot by holding the two phone buttons (hangup and answer)and press menu or home and back (im not sure but one of these work and you see something saying it updates some stuff.
(if this dont work in ur G1 (specially latest versions) you can use a sdhc usb cardreader or a windows mobile phone or anything else with direct disk acces mode , probably nokia and sony ericsson too)
on the next boot you will have the old RC7
(if you have no internet on phone you can skip the next 2 lines and download the package and copy it to the G1 (dont know where so if anyone can tell me it would be nice to help people out )
- fill in your google account stuff
- Download Android "Telnet" application from the Market.
- Download recovery.img and copy it to your SD card. rename it to recovery.img
- Download the Hard SPL and copy the zip file to the SD card. (this is for G1 drea110 htc dream only so be carefull as this stuff can ruin your phone)
- All files must be on the root of your SD card.
- turn off the phone and detach from the pc
Rooting your G1- RC7 phone:
On RC7 Rom and lower, anything you type into your keyboard is also being run in a hidden console with root permissions.
To get root access, do the following:
- Restart your phone. Wait for your phone to start up fully and show the home screen.
- Unlock it by pressing menu after you typed code for sim and it fully started ( it will auto-lock itself)
- Hit the enter key twice,(Yes, it will start up a contact search, so you can see what you type . aint it cool) type "telnetd" and press enter.
- start telnet application you downloaded before on G1 and connect to localhost. (if you dont see localhost and connect window you have wrong app or need to reboot another time). If you connect successfully, you will have a root prompt "#".
Type the following into Telnet (these commands will give you root access for now):
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
Power off your phone by pressing send/hangup&menu together when its done.
Now you have the modified recovery and root !
Now that you have root and stuff, you will want to apply "Hard SPL" to your phone. HardSPL includes engineer SPL and is what will allow you to apply any rom image from any other regions
(like UK on US phones, UK on dutch and vice versa), create full backups of your phone, install the latest build from the Android source, enable usb on recovery mode, usually resurrect your phone if it is "bricked" and give you allways root and ability to flash another rom. Allows fastboot. Fastbooting of images allows the flashing of 1:1 images of system, data, boot, cache, pretty much everything.
You have already downloaded the file to your SD card, so now you can apply it.
-Start up in recovery mode by holding home and pressing power.
-You will now enter recovery mode. You should see an exclamation.
-If you do not see a menu on screen, press Alt-L to show the menu. It is supposed to show the modified recovery menu.
-select update from zip to apply the update.zip (hardspl) from the SD card.
-After the update is complete, hold Home and press Back to restart.
ok your G1 europe 1.6 or whatever version is now unlocked.
Installing your modded rom:
now download this europe rom (or here: link ) and this cyanogen update mod
(here are more roms: android-roms make sure you READ what is needed for this roms as these all need different recovey and things which are all nicely written to you in the help and readme files that come with it.)
- copy both files to root of the sd-card
- detach G1 and shut it down
- press home and start to get into the menu
- wipe device
- wipe cache
- install from zip the europe rom and do not reboot or anything else
- install cyanogenMod
- after it finish press both talk&hangup button and tap menu
- its probably giving the recovery menu . take out the battery and put it in and start the phone normally
- wait a long while for the phone to setup and i donno what the heck it needs to do but let it.
enjoy...
THnx to this greatfull forum-members like myself, moneytoo, amon ra, cyanogen, mark_v, persiansown who do this coz few others can and they have a sort of happy feeling doing it.
hi.
this isnt working for me. i used the hex editor to copy sections 00000000 to 00000170 from goldcard.img to my sdcard, then shut down and turned on phone with HOME+POWER, it "hangs" on phone with exclamation mark image. if i press home+power again i'm presented with default android recovery. i did put DREAMIMG.NBH to the root of my sdcard.
that means no confirming anything... what am i doing wrong then?
Seriously, use 1Clickroot.
maxisma said:
Seriously, use 1Clickroot.
Click to expand...
Click to collapse
1clickroot doesn't work with 1.6, does it?
greglord said:
1clickroot doesn't work with 1.6, does it?
Click to expand...
Click to collapse
The new should work in theory.. idk..
greglord said:
hi.
this isnt working for me. i used the hex editor to copy sections 00000000 to 00000170 from goldcard.img to my sdcard, then shut down and turned on phone with HOME+POWER, it "hangs" on phone with exclamation mark image. if i press home+power again i'm presented with default android recovery. i did put DREAMIMG.NBH to the root of my sdcard.
that means no confirming anything... what am i doing wrong then?
Click to expand...
Click to collapse
thats probably coz i mixed up buttons for starting the rainbowscreen updating mechanism.. sorry for that
i dont own or have a G1 so im not used to the button layout
edit: you can in that screen press Alt-L to get the menu , once u have the recovery.img installed it will change there to the menu of the modded recovery
maxisma said:
The new should work in theory.. idk..
Click to expand...
Click to collapse
i have no idea
but it might be handy to put a link to the file you mentioned instead of shouting it without researching the fact whether it works or not in 1.6
can anyone quickly tell me what the advantages of having the hard spl are? all iv done is rooted, (via 1 click) and then flashed cyanogens latest. radio was already up-to-date. just wondered if flashing new spl changes anything? many thanks
Hard SPL enables you to install roms like Hero or others that have a large "update".zip
bbuchacher said:
Hard SPL enables you to install roms like Hero or others that have a large "update".zip
Click to expand...
Click to collapse
Actually...The Haykuro SPL allows that...
Ace42 said:
Actually...The Haykuro SPL allows that...
Click to expand...
Click to collapse
Right. HardSPL (and DangerSPL) are something that allow fastboot. Fastbooting of images allows the flashing of 1:1 images of system, data, boot, cache, pretty much everything.
You should always have HardSPL/DangerSPL installed so you can fastboot a nandroid image as a worstcase scenario.
Jesus, the amount of noobiness is this thread is astounding.
persiansown said:
Right. HardSPL (and DangerSPL) are something that allow fastboot. Fastbooting of images allows the flashing of 1:1 images of system, data, boot, cache, pretty much everything.
You should always have HardSPL/DangerSPL installed so you can fastboot a nandroid image as a worstcase scenario.
Jesus, the amount of noobiness is this thread is astounding.
Click to expand...
Click to collapse
thnx for clearing that out
as i said i dont own a G1 i modded a friends one . so i dont know anything about this G1 but getting a new rom on it hehe.
i choose the hardspl as precaution and it seemed pretty stable from what i read.
i choose the 1.5 recovery as i thought it should have the same recovery image as the rom . dont know about that. it is the 1.4 recovery with some extras which are usefull, cant deny that.
i choose the rom as it seemed to be the most stable at the moment and allows thetering . this is why i needed to rom upgrade in the first place. second place that i just like modding and unlocking so that one can do everything with the device as it is yours anyway.
APEX.7 said:
can anyone quickly tell me what the advantages of having the hard spl are? all iv done is rooted, (via 1 click) and then flashed cyanogens latest. radio was already up-to-date. just wondered if flashing new spl changes anything? many thanks
Click to expand...
Click to collapse
it is allready answered in the how to ..
I can vouch for the OP tutorial working on the Australian Optus(Singtel) HTC Dreams wtih DRD20 build. Just waiting on that final epic long load up now.
Anacche said:
I can vouch for the OP tutorial working on the Australian Optus(Singtel) HTC Dreams wtih DRD20 build. Just waiting on that final epic long load up now.
Click to expand...
Click to collapse
I'm also G1 / 1.6 / DRD20 ... it's sounds good news for me ...
Hahahhahahh.....
this post should be named "The Most Difficult Way to Root your G1". How bout this.....downgrade to 1.5, DL one click root, and you're done.
Please help!!! Pleasee!
Do help me out on this one. I really can't seem to actually make my SD card into the gold card part. Whenever i plug it in the G1 or on a USB reader it tells me it's damage and needs to format.
i have two questions, Can i flash SPL first, then do a downgrade then flash recovery?
2nd : If i can't then can i flash recovery, flash spl then do a downgrade to RC7?
if so how do i flash my recovery?
DO HELP ME OUT PLEASEE! i've been on this for days!!!
I know that this is going to cause problems and fighting but, I cannot read this thread and not say anything in good conscious.
With the amount of errors and misinformation in this thread, perhaps the OP should leave the tutorials and how-to's to the people that actually HAVE a G1, have modified ROMs on their phone, and can support the questions that are asked in the thread.
Just my two cents, but I have a feeling that my words are supported judging from the general consensus of the previous posts.
~DM
DirectMatrix said:
I know that this is going to cause problems and fighting but, I cannot read this thread and not say anything in good conscious.
With the amount of errors and misinformation in this thread, perhaps the OP should leave the tutorials and how-to's to the people that actually HAVE a G1, have modified ROMs on their phone, and can support the questions that are asked in the thread.
Just my two cents, but I have a feeling that my words are supported judging from the general consensus of the previous posts.
~DM
Click to expand...
Click to collapse
Id have to second that, while I may not have many posts here on XDA,I've rooted and rebuilt and replaced screens from 7 G1's using the how to's and wiki's here on XDA(thanks devs). My thought is if it the current guides work we should prob stick with them unless someone else figures a better faster way.(ie;one click root). By the way,just wanna say,I've never charged anyone to root their phone or fix one. The knowledge I've gained I learned here,it wasn't something I developed and I think its wrong for people to take open knowledge they didn't come up with and charge other people for it like I've seen at some of these cell phone repair shops and on craigslist. If your gonna charge for the knowledge then pay the people you gained the knowledge from. Sorry for going off topic,just had to vent.
{
"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
Android 4.0.4 Ice Cream Sandwich for PC
This tutorial is for installing Android Ice Cream Sandwich 4.0.4 on your PC, in this case create a Live USB Android to run a more portable, fully functional, fast, and handy for using. It works for x64 & x86 computers. (Tested on a computer x64 with an Intel Corei5).
:::>Requirements:
-ISO RC2 Android 4.0.4 ICS ***mod edit
-LiLi (Linux Live USB Creator) ***mod edit
-Pendrive 512mb minimum (USB1)
-Pendrive 2Gb minimum (USB2)
-PC
:::>Instructions:
1- Connect your Pendrive USB1 and apply a quick format to delete all files stored in pendrive.
2- Run LiLi (Linux Live USB Creator) and where it says 'Step 1' select your pendrive USB1.
3- Then select where it says ISO / IMG / ZIP and select the ISO Android 4.0 you downloaded.
4- Click the yellow lightning symbol is at the bottom. when you click LiLi will start the process of creating and recording of Android 4.0 on your USB1. Just wait for it to finish the process (the program will indicate this in the section of the yellow lightning).
5- Conect your pendrive USB2 and reboot your PC.
6- Upon restart, enter bios boot device selection to tell the PC you want to boot from your USB1 (for booting selection, this depends of your pc, in some case is F12, F9, F8, DEL, you will have to investigate it)
7- Boot from your USB1. A window of Android-x86 will appear, select 'Install to harddisk ".
8- Many letters and codes appear for several seconds, do not worry is normal as you start reading all the drives and partitions that are connected to the PC.
9- Then, a list of drives connected, is a list where the right is the name of the connected hardware or drive, here you will recognize the name (brand) of your USB2, example: "sdc1 DTRAVELER KINGSTON G2". When you recognize your USB2's name, select it.
10- Now it asks you, format your USB2?, select 'ntfs' or 'fat32'
11- Now it asks you, want to install the GRUB bootloader?, select 'YES'
12- Asks you if you want to create the DATA partition on Android, select 'YES'. its default value is 512MB, I recommend minimum 1024MB. Then select 'YES'.
13- Then it begins to create Android in USB2, when it ends select 'Reboot'.
14- Your PC will reboot, enter in bios selection boting device and boot from your USB2, then select 'Run Android x86', then Android ICS will start, only set it as you want. And it's everything. It is not necessary make root, it is rooted
:::>Recommendations of essential apps for this rom:
--To turn off the screen and lock:
Download 'Screen Off and Lock' ( Katecca) or 'Turn Off The Lights' (Protoport)
- -To sleep your PC, just press the power button once, and Android will be lock and turn off the screen and sleep your PC. To restore just press any key again and wake up your PC showing the lock screen of Android.
--To exit of android and reboot the PC, just press CTRL + ALT + DEL.
--To exit of android and turn off the PC, just press the power button for several seconds after turning off disconnect your USB.
:::>Screenshots:
Click here to see
Note: This screenshots are resized.
.
Sweet. I'll take a look at it. What does the screen resolution go to?
Sent from my Incredible 2 using Tapatalk 2
i think this post should be in 'Android Software and Hacking General' section
hey users!!
13. Advertising and Income Generation
Commercial advertising, advertising referral links, pay per click links and other income generating methods are forbidden. Do not use xda-developers as a means to make money
Questions:
Will I be able to use internet via my Ethernet port???And what about a webcam?
I assume the iso is from:
http://www.android-x86.org/
So just go there, you'll find more files and tutorials too.
nelsdzyre said:
13. Advertising and Income Generation
Commercial advertising, advertising referral links, pay per click links and other income generating methods are forbidden. Do not use xda-developers as a means to make money
Click to expand...
Click to collapse
sorry, I did not know about it, did not read
my only intention is to share how I did this.
no boot system found
try'd as usb1 and 2 and burned the iso on cd and installed on usb...
Anyone think it would be possible to compile b43 drivers on android?
sent from my HP Touchpad. Dual-booting Android 4.0.4 and WebOS 3.0.5
pxrave said:
no boot system found
try'd as usb1 and 2 and burned the iso on cd and installed on usb...
Click to expand...
Click to collapse
same here
Nice..been waiting for this..thanks
The only thing that sucks is no hardware acceleration, using WiFi or Ethernet drivers, or anything like that.
Sent from my HP Touchpad Dual-booting WebOS 3.0.5 and Android 4.1.2!
Sweeet, tested and it works but I wan't to use more space why is this not possible. Just 2gb memory is not enough
Galaxy Nexus Tapatalk
takeiteasyy said:
Sweeet, tested and it works but I wan't to use more space why is this not possible. Just 2gb memory is not enough
Galaxy Nexus Tapatalk
Click to expand...
Click to collapse
Use a bigger USB, and if that's not the issue then modify the boot.img to allow larger storage.
Sent from my HP Touchpad Dual-booting WebOS 3.0.5 and Android 4.1.2!
blmvxer said:
Use a bigger USB, and if that's not the issue then modify the boot.img to allow larger storage.
Sent from my HP Touchpad Dual-booting WebOS 3.0.5 and Android 4.1.2!
Click to expand...
Click to collapse
I use 16gb sandisk cruzer, any idea to modify the boot.img?
Galaxy Nexus Tapatalk
no work.. cant boot usb on boot.. any idea...
:::::> [FOR PC] Android 4.0.4 for PC & Live USB
kakho55 said:
no work.. cant boot usb on boot.. any idea...
Click to expand...
Click to collapse
use a PLOP floppy, you will find it with Googlr
****...
Is stupid and not your work, is the asus_laptop.iso from Code Google.
Anybody can download for google and create a live usb with unetbootin.
Please go somewhere else to hoodwink users...
Thanks for the links.
I didn't see any paid links????
On an Asus 1215N EEEPC
1. Installed ISO with YUMI multiboot (FRRREEEEE) no link.
2. rebooted Choose Android
3. Choose play without install
4. Watched Detecting Android x86 asus iso . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Each DOT was about 10 seconds apart = or 3 min. (+ or -)
Rebooted to W7 and redownloaded ISO and Re-installed with YUMI (FREE)
Rebooted to USB and picked USB
Chose play without install and Watched detecting Android x86 asus iso. . . . . . . . . . . . . . . . . . . . . . . . for more than 4 minutes and gave up.
Why?
Run JB 4.2.2 NATIVE (EFI bios only)
Diualboot with win8/linux/osx. - This is NOT a x86 emu - its bare metal
https://01.org/android-ia/documentation
Required materials:
•1GB or larger USB thumb drive
•A supported target device
•A laptop or PC running Linux, Windows, or Mac OS with working internet connection
Step 1: Back up your existing OS and all data on your device. The Android-IA installer will erase everything and repartition your hard drive automatically.
Step 2: Download the latest installer image for your device from the Downloads page.
Step 3: Prepare the USB thumb drive
Linux users:
•Unzip the downloaded file: `unzip your_installer_file.zip'
•Insert the USB thumb drive into your machine
•Open your terminal application and find the device name of the thumb drive. Run `dmesg' and look near the end for a name like "/dev/sdX" where X is a letter.
•Unmount any partitions that were automatically mounted: `sudo umount /dev/sdX*' (Where X is the letter from above)
•Write the live.img file from the extracted zip to the USB flash: `sudo dd if=live.img of=/dev/sdX bs=1M conv=fsync' (Where X is the letter from above)
Windows users:
•Extract the installer image from the downloaded zip file
•Download "Image Writer" application from https://launchpad.net/win32-image-writer/ and extract it to a folder of your chioce.
•Insert your USB drive into your computer.
•Find the drive letter of your USB drive by opening 'My Computer' on the desktop.
•Run Win32DiskImager.exe from Image Writer's directory.
•In Image Writer's window, select the installer.img you extracted from the downloaded zip
•In Image Writer's window, select your thumb drive's letter that you found in 'My Computer'
•Click "Write" and wait until the process is over.
Mac users:
•Extract the installer image from the downloaded zip file
•Open the Terminal (under Utilities)
•Execute `diskutil list' to get the current list of devices
•Insert your USB drive into your computer.
•Execute `diskutil list' again and determine the device node assigned to your flash media (e.g. /dev/diskN)
•Execute `diskutil unmountDisk /dev/diskN'
•Execute `sudo dd if=live.img of=/dev/diskN bs=1m'
•Execute `diskutil eject /dev/diskN' and remove your flash media when the command completes.
Step 4: Prepare device for installation:
•Set the device to boot from the USB thumb drive (device-specific instructions can be found on the devices page.
•Make sure "UEFI Boot Support" is enabled in the BIOS.
Step 5: Install the system.
• Plug in the USB thumb drive with the Android-IA installer image created in step 1
• Power on the device
• From the boot menu, choose "Install Android to hard disk"
• Wait until the installer finishes
• Unplug the USB thumb drive
• Power off the device by holding down on the power button for 10 sec., then power on the device and choose "Boot Android system" (or let the countdown timer expire)
You're done! Enjoy your Android-IA device.
Click to expand...
Click to collapse
Move post if in wrong section plz...
Sent from nexus 4 AOSP
Hello.
I installed the latest Android-IA (android-4.2.2_r1-ia1) on my Acer Iconia W700, and it works perfectly. The only downside (however, huge one) is the lack of libhoudini - without it half of android apps refuse to load on x86 processor. Which, by the way, scores ~70000 in Antutu (!)...
I searched everywhere, but there's just too little information on both libhoudini as well as Android-IA . Please, can anyone help in porting this library to Android-IA? I know it is not open source, but so are gapps, and Android-x86 already uses libhoudini. So there shouldn't be any real difficulties...
WBR, Draco.
Drakosha said:
Hello.
I installed the latest Android-IA (android-4.2.2_r1-ia1) on my Acer Iconia W700, and it works perfectly. The only downside (however, huge one) is the lack of libhoudini - without it half of android apps refuse to load on x86 processor. Which, by the way, scores ~70000 in Antutu (!)...
I searched everywhere, but there's just too little information on both libhoudini as well as Android-IA . Please, can anyone help in porting this library to Android-IA? I know it is not open source, but so are gapps, and Android-x86 already uses libhoudini. So there shouldn't be any real difficulties...
WBR, Draco.
Click to expand...
Click to collapse
Antutu score 70000!? really? You are using the i5 model?
Drakosha said:
Hello.
I installed the latest Android-IA (android-4.2.2_r1-ia1) on my Acer Iconia W700, and it works perfectly. The only downside (however, huge one) is the lack of libhoudini - without it half of android apps refuse to load on x86 processor. Which, by the way, scores ~70000 in Antutu (!)...
I searched everywhere, but there's just too little information on both libhoudini as well as Android-IA . Please, can anyone help in porting this library to Android-IA? I know it is not open source, but so are gapps, and Android-x86 already uses libhoudini. So there shouldn't be any real difficulties...
WBR, Draco.
Click to expand...
Click to collapse
I remember finding a manual install of libhoudini somewhere but it didnt work. That was with the february version of A-IA, though.
Sent from my 700T using XDA Premium HD app
Drakosha said:
Hello.
I installed the latest Android-IA (android-4.2.2_r1-ia1) on my Acer Iconia W700, and it works perfectly. The only downside (however, huge one) is the lack of libhoudini - without it half of android apps refuse to load on x86 processor. Which, by the way, scores ~70000 in Antutu (!)...
I searched everywhere, but there's just too little information on both libhoudini as well as Android-IA . Please, can anyone help in porting this library to Android-IA? I know it is not open source, but so are gapps, and Android-x86 already uses libhoudini. So there shouldn't be any real difficulties...
WBR, Draco.
Click to expand...
Click to collapse
Did you ever find a solution to this?
DJDrew said:
Did you ever find a solution to this?
Click to expand...
Click to collapse
Hi there
I'd also be glad to hear more about that...From what I could gather so far, there is no fully working ARM translator / libhoudini solutions for android IA. Hence the only solution would be to switch to android x86...
Change dpi and get bluetooth working with android and windows 8.1 at the same time
Do these changes if you are confident in your skills. I'm student and quite busy so if you ask something it can take some time for me to answer. Damages you might do to your system are your own responsibility. I have tested these instructions with Acer W700 on android-4.2.2_r1-ia3 and can confirm that they worked for me.
First changing dpi from original 213 to 160:
1. Get file manager on android like ES file Explorer
2. R/W rights to whole system on android
3. From root go to /system/etc/machine-props/
4. Open acer-w700.prop with ES Explorer and edit line "ro.sf.lcd_density = 213" and change 213 to 160
5. Reboot android and system should now be 160 dpi
Now about that bluetooth. I find it annoying that you have to pair your bluetooth mouse and keyboard again every time when you switch between android and windows 8.1. So I did research and found a way to fix this problem and here's how to do it. I can confirm that this works with Acer bluetooth/cover keyboard and MS Sculpt touch mouse.
1. Pair your bluetooth devices first with android and the with Windows
2. On Windows download PsExec
3.Then from downloaded file copy PsExec.exe in Windows to directory C:\Windows\System32 or to directory where your System32 folder is.
4. Write in the search cmd and run it as administrator
5. Then use command: psexec -s -i regedit.exe
6. Now go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Keys
7. From \Keys you can find your paired bluetooth devices. First there is the devices bluetooh mac address and 32 numbers long linkkey. Now write those linkeys and mac addresses up or copy them.
8. Now everything is set on Windows side. Next boot to android.
9. On android you need again for example ES file Explorer and R/W rights
10. With file Explorer fro root go to /data/misc/bluedroid/
11. Open file called BT_config.xml
12. From text find your devices using mac address
13. When you find you devices mac addres scroll down and you should see line with linkkey and 32 number code.
14. Now take that 32 number code you got from Windows
15 You have to change it little so the linkey works and here how it's done:
for example your Windows linkkey is "12345678qwertyuiasdfghjkpoiuytre" now set it as 8 number clusters like this
"12345678 qwertyui asdfghjk poiuytre"
Now you have to reverse those 8 number clusters
Take the set on far right "poiuytre" and mark it like this "po iu yt re"
Now reverse those pairs like this "re yt iu po"
Now "reytiupo" this is the first line in the new linkkey
Do the same for other three cluster. After it's done this example linkkey looks like this "reytiupojkghdfasuityerqw78563412"
16. When you have your modified Windows linkkey ready you can just replace the old one from the file BT_config.xml
17. Now just reboot android and your keyboard and mouse should work.
I've found that sometimes when switching from Windows to android bluetooth doesn't connect. Just reboot android and your bluetooth devices should connect.
I would have posted this on deveopers site where people visit more often but you need 10 posts and this is my first one so if you can you should link my post there so more people can enjoy these instructions.
Thank you for reading this and don't forget to like it :good:
Anyone know where to find the source code for this?
Featured on XDA-Portal
Hi all !
Welcome to the tutorial of how to install Android x86 !
I've written this extensive guide, it is as detailed as possible and it is written as easy and as understandable for new user.
This guide is, however does not put guarantee of any action you've done outside the guide itself. Anything such as partitioning, OS installing or uninstalling is not guaranteed by me or by anyone at XDA. You're doing this at your own will.
Preparations :
1. Any computer / device that supports installation via flash driver / disc (or have enough space for VM)
2. Any media that is mentioned below (either flash drive, CD / DVD, or VM)
3. Android x86 ISO
4. 2 GB of free or clean partition is recommended (you can use more than 2 GB to increase internal storage)
1. Download Android x86 ISO.
You can download it here
If your device isn't listed there, download Generic ICS build here : Click ! [You need to unzip after download]
The newest KitKat build is unified and it's also generic. It supports wider range of hardware, but it does not support LAN device (yet). You can download it here
Follow the guide with your preferred installation method.
If you're using USB stick / Flash Drive :
2. Download UNetbootin
You can download it here : Click !
On Ubuntu (11.04 and higher, or its derivatives) you can type : sudo apt-get install unetbootin
On Arch (or its derivatives) type : pacman -S unetbootin
3. Run UNetbootin, select the Android x86 ISO
4. Select USB drive (make sure you don't select your HDD partition), then click OK
5. The UNetbootin will copy and install Android x86 live image & installer to your flash drive
6. Reboot your device after the process is completed
7. Boot to Boot Device Selection (in BIOS image), after you entered it, select your flash drive
8. There will be a GRUB menu generated by UNetbootin, select Install Android x86 to hard disk
9. Wait until it loads
10. Select partition to install Android x86
11. If you're unsure, don't format the partition
12. There will be a prompt, 'Install GRUB bla-bla-bla', if you use Windows, select yes. Another prompt will appear, select yes again.
If you've installed GRUB, do not select yes.
13. Another prompt, 'make system r/w', select yes (this enables root and read write access to your system partition)
14. If you're using Android x86 4.0.3 and older, you'll be prompted to install virtual sdcard, input 2GB (maximum size)
15. Reboot your device
If you're using CD / DVD
2. Burn the Android x86 ISO
3. Reboot your device, go to Boot Device Selection menu, select the CD / DVD
4. You will see Android x86 GRUB menu, select Install Android x86 to hard disk
5. Wait until it loads
6. Select partition to install Android x86
7. If you're unsure, don't format the partition
8. There will be a prompt, 'Install GRUB bla-bla-bla', if you use Windows, select yes. Another prompt will appear, select yes again.
If you've installed GRUB select no (installing it will break your GRUB configs)
9. Another prompt, 'Make system r/w', select yes (if you like modifying your Android x86)
10. If you're using Android x86 4.0.3 and older, you'll be prompted to install virtual SDCard, input 2 GB (maximum)
11. Reboot your device
If you're using it as virtual machine :
2. Set up the VM (RAM set to min 512 MB), tweak the configuration to match your need
3. Make sure you've loaded the ISO file in the VM menu, load the VM
4. A GRUB menu generated by Android x86 will appear, select the last option (Installation - Install Android x86 to hard disk)
5. Wait until it loads
6. Create a new partition (Navigate to New, , set to maximum size, navigate to write, done, navigate to quit)
7. Install Android x86 to the new partition
8. Format the partition to ext4
9. Answer 'yes' to 'Install bootloader GRUB bla-bla-bla'
10. Answer 'yes' again to 'make system r/w' (enables root and read write access to your partition)
11. If you're asked for sdcard, then input 2GB (the maximum size is 2GB, if your partition is smaller input suitable size for your partition)
12. Reboot when the process is done
How to add Android x86 to GRUB Menu
For GRUB 1.97 - 1.99 / 2.00
1. To make it easy, install GRUB Customizer
Type these into terminal emulator :
Code:
sudo add-apt-repository ppa:danielrichter2007/grub-customizer
sudo apt-get update
sudo apt-get install grub-customizer
2. Open GRUB customizer, make a new GRUB entry.
3. Open 'Sources' tab, type these :
Code:
[B]set root='(hd0,4)'[/B]
search --no-floppy --fs-uuid --set=[B]root e1f9de05-8d18-48aa-8f08-f0377f663de3[/B]
linux [B]androidx86[/B]/kernel root=UUID=[B]e1f9de05-8d18-48aa-8f08-f0377f663de3[/B] quiet [B]androidboot.hardware=generic_x86[/B] SRC=[B]/androidx86[/B] acpi_sleep=s3_bios,s3_mode
initrd [B]androidx86[/B]/initrd.img
Pay attention for the bolded part, here's what to change :
1. set root='(hd0,4)' : Change the (hd0,4) to partiton Android x86 is installed.
The hd0 means sda, so if you install it to sdb, it'll be hd1 and so on.
The hd0,4 means the partition number, in my case, hd0,4 means sda4. So if you install it on sda6, it'll be hd0,6.
2. --set=root e1f9de05-8d18-48aa-8f08-f0377f663de3 : The random number here is the UUID of partition Android x86 is installed
You must change it to correct UUID, you can easily got UUID by creating new entry in GRUB Customizer then go to Options tab, then select the 'Linux' option in dropdown. You'll see partition dropdown, select your partition. Open the source tab, you'll see the UUID there.
3. androidx86/ : The root of Android x86
Change it into your Android x86 root. You can see what's your Android x86 root by navigating to Android x86 partition, and you'll see a folder name started with 'android', that's the root of your Android x86
4. androidboot.hardware : Your device, of course.
Note : If you're using Android 2.3 - 4.0.3, change it to androidboot_hardware
Here's the list of hardware :
Code:
- generic_x86 : If your hardware isn't listed, use this
- eeepc : EEEPC laptops
- asus_laptop : ASUS laptops (supported ASUS laptops only)
GRUB 2.0 tutorial is the same like GRUB 1.97-1.99.
-------------
FAQ
-------------
Q : Does this work on my device ?
A : Try it ! There's generic build which supports many device.
Q : Which release should I pick ?
A : Generic is recommended (if your device isn't listed in download list), if your device is supported (like EEEPCs for example), pick one for your device. Do take a note that newer builds uses unified image, which means it supports wide range of hardware.
Q : Will this overwrite my old OS ?
A : As long as you install it in different partition and you did the right setup, you are good to go !
Q : Why does my network / touchscreen / mouse / etc, doesn't work ?
A : Mostly this is a driver problem. Try to use newer / older release. If it doesn't work, try different build for other device (there's a chance this will fix your problem)
Q : Does Android x86 works on USB disk (as a Live Image / as an OS itself) ?
A : It does, I have tested it on Gingerbread and ICS release.
Q : Why deep sleep / suspend doesn't work on my device ?
A : This is one of the issue on Android x86. The developer might be working on a fix.
Q : It doesn't work on a VM setup !
A : Check your configuration and virtual disk, Android needs at least 2GB of free space.
Q : Why does games feel choppy when played ?
A : This is because the game uses ARM libs / libraries which is not optimized for Android x86 (which uses ARM to x86 translator by Intel). On newer build, like unofficial Lollipop release doesn't include ARM to x86 translator, so it can't execute any ARM libraries or binaries.
Q : Android 4.4.2 RC-1 hangs on bootscreen (the flashing Android logo / tty1 terminal) !
A : Check your hardware, if you're using x64 probably the x64 isn't supported yet. Also, try using older release.
Q : There's no Play Store !
A : Sometimes, nighlies build (as Custom ROMs user calls it) is uploaded, this type of build doesn't have GApps. Also, if you're using deprecated release (old release), they have Android Market instead of Playstore.
Q : Can you flash .zips in this ?
A : You can, but it's not recommended.
Q : Play Store only have small amount of app !
A : Because Play Store detects your device as Android with a x86 CPU. This kind of CPU isn't widely used by apps in Play Store (most CPU in Android phone is ARM)
wow awesome guide :good:
Desktop
Does this also work on a desktop?
Rami1997 said:
Does this also work on a desktop?
Click to expand...
Click to collapse
Bro, any computer. Be it a desktop, netbook, ultrabook, MacBook, Linux computer, etc
F4uzan said:
Hi All !
I'm going to post a tutorial, how to install Android x86 to your laptop & netbooks (works on Personal Computer too).
So, let's start !
Preparations :
1. A working laptop & netbooks
2. R/W CD / Bootable USB stick (flashdisk)
3. Android x86 ISO
4. Free partition :
- 2 GB for Froyo - ICS
- 8 GB for JellyBean 4.2 - JellyBean 4.3
- 10 GB for KitKat 4.4.2
1. Download Android x86 ISO.
You can download it here : Click !
If your device brand is listed there, download Generic ICS build here : Click ! [You need to unzip after download]
If you're using USB stick :
2. Download UNetbootin
You can download it here : Click !
On Ubuntu (11.04 and higher) you can type : sudo apt-get install unetbootin
3. Run Unetbootin, select the Android x86 ISO
4. Select USB drive (instead of Hard Disk), then click OK
5. The UNetbootin will install Android x86 live image & installer to your USB stick
6. Reboot your device after the installation is completed.
7. Boot to Boot Device Selection (in BIOS image), after you entered it, select USB2.0 / USB4.0 / USB Disk (or something similiar)
8. There will be a GRUB like menu generated by UNetbootin, select Install Android x86 to hard disk
9. Wait until it to load
10. Select partition to install Android x86
11. If you're unsure, don't format the partition
12. There will be a prompt, 'Install GRUB bla-bla-bla', if you use Windows, select yes. Another prompt will appear, select yes again.
If you're using Ubuntu, select no
13. Another prompt, 'Make system r/w', select yes (if you like modifying your Android x86)
14. If you're using Android x86 4.0.3 and older, you'll be prompted to install virtual SDCard, input 1800 MB / 1.8 GB
15. Reboot your device
If you're using CD R/W
2. Burn the Android x86 ISO
3. Reboot your device, go to Boot Device Selection menu, select the CD / DVD
4. You will see Android x86 GRUB menu, select Install Android x86 to hard disk
5. Wait until it to load
6. Select partition to install Android x86
7. If you're unsure, don't format the partition
8. There will be a prompt, 'Install GRUB bla-bla-bla', if you use Windows, select yes. Another prompt will appear, select yes again.
If you're using Ubuntu, select no
9. Another prompt, 'Make system r/w', select yes (if you like modifying your Android x86)
10. If you're using Android x86 4.0.3 and older, you'll be prompted to install virtual SDCard, input 1800 MB / 1.8 GB
11. Reboot your device
I'll add tutorial how to add Android x86 to Ubuntu's GRUB menu. Stay tuned !
There's no screenshot, because the result may vary with your device.
Click to expand...
Click to collapse
Sorry if this has already been asked/answered but would this work on a Surface Pro (1st gen) or a Dell Venue 8 pro?
Windows
raghav kapur said:
Bro, any computer. Be it a desktop, netbook, ultrabook, MacBook, Linux computer, etc
Click to expand...
Click to collapse
And this doesn't delete windows right?
dodgebizkit said:
Sorry if this has already been asked/answered but would this work on a Surface Pro (1st gen) or a Dell Venue 8 pro?
Click to expand...
Click to collapse
Yes, it will work on both. Not sure about the touchscreen and the keyboard covers though
---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------
Rami1997 said:
And this doesn't delete windows right?
Click to expand...
Click to collapse
If you overwrite this Android installation over the Windows, then IT WILL DELETE WINDOWS.
But, if you create separate partitions for Windows and Android, then you can dual-boot.
I suggest that you run Android in a virtual machine rather than installing this way
Cool
Sent from my Nexus 5 using Tapatalk
Sounds great, can't wait to try it on my old laptops, thanks!
If you want Ubuntu Grub entry, see here : https://groups.google.com/forum/#!topic/android-x86/GrPdnpa6XBM
Use Li's kernel from here IF YOU ARE USING 4.4 on an UEFI system (<efivar> KP): https://groups.google.com/d/msg/android-x86/GrPdnpa6XBM/dA1ChqU1vu4J
All credits goes to there owners (not to me ).
GOOD LUCK
BTW, I have Vaio S (SVS 2012) and I can get WiFi working of I boot from legacy mode BIOS from an external HD w/ the original kernel, while it doesn't work of I boot it from UEFI w/ the custom kernel (since it can't boot w/out it) and doesn't work w/ either 4.3.X or 4.2.X. Can someone help me? (using Intel Centrino Advanced N 6235)
Thanks
Interesting
Anyone try to run this as a VM using either VMWare or VirtualBox?
sent from my hsvxo out in cbciioebd
Whoop!! Featured on portal!!
Sent from my LG-E430 using XDA Premium 4 mobile app
14. If you're using Android x86 4.0.3 and older, you'll be prompted to install virtual SDCard, input 1800 MB / 1.8 GB
Could we set more for more space to install apps?
simon_lefisch said:
Anyone try to run this as a VM using either VMWare or VirtualBox?
sent from my hsvxo out in cbciioebd
Click to expand...
Click to collapse
Yep, I did... But when I tried to boot it it shows only attachment and stock on Android logo
Could someone please answer my question please, also can you try the OS before installing it on the hdd, like test it and reboot and then install it
Awesome... wud try it n post screen shots if i can :laugh::good:
i tell you sth.. i was able to make 2gb data partition only... and trying to change data.img in other programs to make it bigger but never succeded.. maybe there is some workaround to make data partition bigger... or to use swap with usb stick or sth..
i had installed android x86 kitkat on usb 8gb drive and works perfectly some apps just had problems with mouse pointer.. (i think those designed for android 2.3) just had this problem with only 2gb data partition...
Bootmgr is missing
unetbootin creates the boot image but my windows laptop doesnt detect it
jarusss said:
Yep, I did... But when I tried to boot it it shows only attachment and stock on Android logo
Click to expand...
Click to collapse
Same thing happened to me with Virtualbox. However, I shutdown the VM, unmounted the iso, and rebooted. After that, it worked. I used the 4.4 version.