Database Users

Help!! messed up updating cyanogenmod! Bricked??

I really need some help please! I think I may have done something very bad. I have a tmobile mytouch 3g. I was trying to update from cyanogenmod 4.2.1.9. I was using a darkstar theme from ringer nation.
Here’s where I think i screwed myself. I am fairly new to all this stuff so I was trying to find a guide on how to update the mod and instead of doing it properly by adding the files to the sd card, doing a wipe, and then installing everything. I instead messed up and did an install of sapping.nbh and basically followed all the directions to originally root the phone. Including formatting the sd card and everything. When I realized that i was doing this all wrong I was still able to load my os and everything seemed ok. I was getting a sd card error that said that the card was blank or had an unsupported file system, but I was able to mount it so, I erased everything off the card and then put the cyanogen update and the drc83_base file and attempted to load into recovery and do the update.
I loaded into and did a wipe. I attempted to follow the instructions on upgrading from the cyogen page. (God I wish I had found that page first) But after I did the wipe and I attempt to Apply any from SD I get “error: sd card is not mounted”
When I attempt to reboot the phone it goes to the tmobile mytouch logo, THEN it goes to my them logo from Ringer Nation, then it just goes to a black screen I let it sit there for like 5 minutes to see what would happen, but nothing. So I took out the battery and sim. I can get into recovery though so I hope that someone can help me figure out where to go from there.I thought that since I had done a wipe that the theme would have been deleted as well? This is weird.
I did do a nandroid backup before. Hopefully that will prove to be helpful. Sorry for the long post, but I wanted to dump as much useful information about this problem so that hopefully someone will be able to help! BTW I'm using a mac with the latest snow leopard software.
As I am desperate for help, please reach out to me via aim – icolinirie or via email
Thank you in advance for everything. This is a great community, and all of Cyanogen’s work is greatly appreciated!!
EDIT: I really need some help! Here's some more information. I have a Magic 32B. Its running Cyanogenmod v1.4 + JF Recovery.
From what I have gathered I need to adp into my phone in order to get it to mount. Anyone know how to do this on a mac. I am trying, but I don't fully understand. I have created the .bash_profile from terminal and typed the following "export PATH=${PATH}:/Users/itunes/Documents/android-sdk-mac_86/tools" which is the path to the tools file in the sdk. I am just stuck at this point. I don't know what to do from here.

Hi I quote.
Install SDK utilities you need to connect your PC to your phone
You can download the full SDK from the Android Developer website for your platform
http://developer.android.com/sdk/index.html
You'll need to download the SDK appropriate for your platform and extract it into a directory somewhere. I'm going to assume you're using Windows here and suggest you extract it into a folder called
C:\AndroidSDK\
on your hard disk. You can put it anywhere you like really, but if you do you'll need to substitute it for the folder above.
Add the tools directory to your system path for easy access
In Windows it's easy to add the Android SDK Tools directory to your system path. Doing this lets you use the Android SDK tools anywhere and makes it easier for you.
On Windows XP: Go to Control Panel->System, Choose the 'Advanced' tab and then click 'Environment Variables' To do this on Vista/Windows7: Simply go to Control Panel->System and choose 'Advanced System Settings' and then 'Environment Variables'
Now that you've got here locate Path under System Variables and click Edit, then add the following to the end of the string displayed:
;C:\AndroidSDK\tools\
Then click OK until you get out of the menus.
Now that you've done this you should be able to bring up a command shell and type 'adb' and it should run straight away without needing to change path.
Please note that you can skip this step completely if you find it too complicated - however you will need to CD to the ?AndroidSDK\tools every time you open up a command prompt so it's worthwhile doing. I'm going to assume you have made the change above in all further examples as it gets too complicated really. If you're not confident in a DOS shell, I'd suggest you do a little bit of reading up on basic navigation in DOS first.
Enable Debugging mode on the phone before connecting to PC and installing the ADB driver
Menu > Settings > Applications > Developement > USB Debugging
Install the USB drivers correctly - check using "adb devices".
If you have already connected your phone to your computer before then the USB drivers are probably already loaded. If you're lucky then typing 'adb devices' in a command prompt will produce something like:
C:\AndroidSDK>adb devices
List of devices attached
XXXXXXXXXXXX device
Where XXXXXXXXXXXX is the serial number of your phone. If it doesn't produce that line, then you need to check Device Manager and ensure the device drivers for your phone were installed correctly.
If you are having issues installing the ADB driver, you need to connect your phone then go into Device Manager and check the ADB device properties. Check the following property and it'll look something like:
Device Instance Id: USB\VID_0BB4&PID_0C02&MI_01\7&293A7D0D&0&0001
To fix the driver installation problem, you need to edit the driver's .ini file and change all the references of 0C03 to 0C02, or 0C02 to 0C03 if your device property states your Device Id is 0C03.
Note: After flashing a new ROM, your Device Id may change again to either 0C03 or remain as 0C02. So you need to update the .ini file again as above to refelect the change and re-install the driver. Another known way to fix the above issue is to download and install HTC Sync - this seems to install the correct drivers.
How to use ADB
ADB stands for Android Debugging Bridge - it's a useful way of talking to your handset while it's running. ADB provides commands for copying files to and from your phone, installing packages and debugging your Android applications.
Useful commands include:
adb devices - lists which devices are currently attached to your computer
adb install <packagename.apk> - lets you install an Android application on your phone
adb remount - Remounts your system in write mode - this lets you alter system files on your phone using ADB
adb push <localfile> <location on your phone> - lets you upload files to your phones filesystem
adb pull <location on your phone> <localfile> - lets you download files off your phones filesystem
adb logcat - starts dumping debugging information from your handset to the console - useful for debugging your apps
adb shell <command> - drops you into a basic linux command shell on your phone with no parameters, or lets you run commands directly
How to use Fastboot
Fastboot is another boot method and is used to drop the phone into a safe mode to load/flash alternate roms. You need USB debugging turned on before you can use Fastboot mode - so I'd recommend you do this first (under Settings->Applications->Development->USB Debugging). You will also need to power off your phone first (hold down Power and select Power Off) and then hold down the Back+Power Buttons to start the phone in Fastboot mode. You will need your USB cable connected to be able to issue any commands and assuming your drivers are correct you should be able to issue:
C:\AndroidSDK>fastboot devices
List of devices attached
XXXXXXXXXXXX fastboot
Other commands in this mode include - we'll cover these below in subsequent sections.
fastboot boot <filename> - boots a rom stored on your pc specified by the filename
fastboot flash <partition> <filename> - flashes a rom stored on your pc, partition can be one of {boot, recovery, system, userdata}
fastboot binaries for mac and linux can be found here.
3. Learn how to use fastboot and boot a recovery rom
Download a recovery rom for your device
There are several different recovery roms available for the HTC Magic devices.
Amon_RA has created several nice recovery roms available from http://forum.xda-developers.com/showthread.php?t=530492 and get the Recovery Rom appropriate for your device - these recovery roms have Nandroid Backup and Nandroid Restore and are perfect for the average user.
You can also use Cyanogen's 1.3.1 Recovery ROM available for: PVT32A devices and PVT32B devices - this rom has some additional options for partitioning your SD card for ?Apps2SD/Swapper/etc.
Fastboot the recovery rom
Fastbooting a rom doesn't write anything to your device - it just loads it directly from your PC - so it's a completely safe way of fixing/recovering/backing up your existing rom. To fastboot a rom you need to first drop your phone into Fastboot mode and check that it's working. Now drop into a command shell and make sure the recovery image you're wanting to load is in the same directory that you're running this in. If it's called something other than recovery-rom.img then substitute that instead.
C:\AndroidSDK> fastboot boot recovery-rom.img
If you are having problems changing the directory in the command prompt, just make a copy of the command prompt .exe itself, and place it in the folder that contains the recovery rom, then run the above command.
And once again, if you have a perfected SPL which does not allow remote fastboot, you will have to fix it first.
Use the Recovery Rom to Backup your current ROM with Nandroid
Once you've booted to a recovery rom - you can use the Nandroid Backup option. If you get a 'cannot mount /dev/mkblkxxx error' when you do this then check your microSD card is inserted correctly and if so, wait a few seconds for it to register to the recovery rom correctly. If at first you don't succeed, try, try again (sdcard can take a few seconds to mount!)
You do not need to be a rocket scientist to do this.
you can use the ADB to put in recovery again by fast boot
http://forum.xda-developers.com/showthread.php?t=530492

Hey! First off Thanks for the reply! I really appreciate someone chiming in to throw some advice my way! But while reading your thread you described the instructions for windows. In this case I have a macbook pro running snow leopard.
I did download the android sdk to my documents folder and I understand that I need to execute some scripts from the terminal on my mac to get things running. But I really dont know what those scripts are or what exactly to do.
I can get into the recovery mode on the MyTouch by holding power and home when powering on. So do I open the console from the recovery screen on the mytouch and then run the scripts on the terminal from my macbook? And which scripts should I run to get the sd card mounted onto my desktop (that is what I'm trying to do). Im not too sure what to do from there either. I want to get the phone back to stock android 1.5 os so that I can root again. My sd card has to be corrupted because it keeps giving me an error saying that it wont mount when I try to do a fix file systems or try anything from that menu. What to do??

What!
can you get in the recovery?

Yeah I can get into cyanogen v1.4 recovery. I'm just stuck from there.

Ok ok If I understand this correctly then you are not briced. you do not have any imag on your phone.
if you do not have anything nadroid recovery on sdcard you must enter a new ROM on the sdcard and flash it
remember full wipe.!

Yes this is what I believe I must do. But I need to either find a way to mount my SD card from the phone while it is in recovery mode (cyanogen v1.4). That's my problem.. I wish there was an easier way to get it mounted onto my mac from the recovery screen. I think I'm just going to go to best buy tomorrow and get a micro sd card reader and maybe another sd card just in case.
Once I have done that though. What files should I put onto the sd card in order to flash it back to original factory android 1.5.
What do you think?

Good idea
I have never used cyanogen v1.4 recovery
I use the recovery-RA-sapphire-v1.5.2H.img and ther you can use USB togle in recovery mode, You must go to the store to buy the adapter that fits on your Mac, I have two adapters for your Mac, you can borrow

Yeah that's the plan for tomorrow. Thanks for the offer man. But I'm in Los Angeles, Ca LOL!! Where are you?

icolinirie said:
Yeah that's the plan for tomorrow. Thanks for the offer man. But I'm in Los Angeles, Ca LOL!! Where are you?
Click to expand...
Click to collapse
Bergen . norway.
http://maps.google.no/maps?f=s&utm_...o-google-gm&utm_medium=ha&utm_term=google map

OMG! WOW! Looks like a beautiful place! LA is a concrete jungle but beautiful in its own respects. Bergen looks like a very comfortable place! I enjoy finding out about these things. Maybe someday I'll visit. I'd definitely love to!

icolinirie said:
OMG! WOW! Looks like a beautiful place! LA is a concrete jungle but beautiful in its own respects. Bergen looks like a very comfortable place! I enjoy finding out about these things. Maybe someday I'll visit. I'd definitely love to!
Click to expand...
Click to collapse
it is sick cold. I'll take one picture out the window

Ubuntu LiveCD with ADB and Unrevoked Recovery installer(Guide).

I have been helping out with rooting HTC Aria's over in IRC in the #liberatedAria channel for a while now. A lot of people have problems with drivers on Windows. The easiest solution for them to do this has been to download an Ubuntu LiveCD and use it to root their phone, however many people know nothing about Linux at all and feel daunted by this.
I have created a customized Ubuntu LiveCD that has a script that downloads the Unrevoked Teams reflash, untars it, and runs it as root to root HTC's phones that are supported by the tool (HTC Evo, Hero, Aria, Desire, and Incredible). It also has the Android SDK included and added to the path so it is accessible from a terminal. Everything can be done without a single change to the computer you are doing it on.
Download the iso image here:
MD5: 9a34c343e8f610e66674af9384334bf6
ubuntu-10.04-desktop-i386-HTCROOT.iso Primary
ubuntu-10.04-desktop-i386-HTCROOT.iso FileFactory.com
Burn the iso to a cd (This can be done with any cd burning software, imgburn found here is free)
[Optional]
If you do not have a CD drive, you can create a bootable flash drive by using the tool found here:Pendrive Linux
Put the CD into your computer cd/dvd drive and reboot your computer.
You must make your computer boot from CD, there are many different ways to do this depending on what computer you have, most recent computers have this enabled by default. Here is a guide that may help if you can't get this to work:Enable Boot from CD
Once it boots from the cd it will show a small picture of a keyboard and a person, do not press anything here and it will come to a window that will allow you to select your language.
Select your language and click "Try Ubuntu 10.04 LTS". This will boot up to a standard Ubuntu livecd desktop.
On your phone click menu, settings, applications, development, usb debugging
On the computer click "Places" on the top menubar and click "Home Folder". This will open a file explorer window, in that window is a script called "reflash.sh".
Double click reflash.sh. A window will pop up asking you what to do with this file, click "Run in Terminal". This will go get from the internet the current version of Unrevoked recovery installer from unrevoked.com/recovery, unzip/tar it, and run it as root.
Once it is complete you will be looking at the unrevoked3 screen and you should follow the prompts on screen.
You will then follow the prompts on the screen to plug in your phone, from the notification pane in android select charge only.
unrevoked3 will reboot your phone twice and leave you in ClockworkMod Recovery. On the computer at the bottom of the window it will say "Done".
Close the window, if you do not need to do anything further you can shut down the machine and be back in windows with nothing changed on your windows system.
Congratulations, your phone is now rooted and has ClockworkMod recovery installed.
There are other guides to setup of sideloading for the aria as well as how to load roms. You can do these using this live cd as well, this is a full ubuntu 10.04 livecd with only games and open office removed, and the unrevoked3 installer and the android sdk installed, it is already in the path and you can use adb commands from the terminal without having to switch directories(however it can be found in /opt/android-sdk-linux_86).
I would like to thank The Unrevoked team for making such a nice tool, and website that made this possible. I would like to that the guys in IRC on Freenode.net channels #liberatedAria and #koush for everything I've learned recently as well as all the great work they have done. Thanks also to Attn1 for making some nice roms for the HTC Aria and gave me the idea to create this. Thanks to Downer3d for the torrent mirror. Thanks to Neolobster for the new faster mirror.
Allowing Non-Market Apps using this cd on the stock ARIA rom:
Click Applications in the upper left corner.
Go to Accessories, click Terminal. This will put in you a terminal in the default users home folder. Because ADB(and android sdk) are in the path you do not need to change any directories. Start the phone in CLockworkmod with data mounted from the partitions menu and plug the phone into the computer.
Code:
sudo su
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo "update secure set value = 1 where name = 'install_non_market_apps';"|sqlite3 ./settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb reboot
What this does:
Switch user to root.
ADB pulls the file that contains the setting to allow non market apps down to the machine from the phone.
The next line runs a sql update of the field install_non_market_apps in table 'secure' and sets the value to 1 (on).
ADB then pushes the file back to the phone in its original location.
You then use ADB to reboot the phone to enable it.

Thats awesome!! If I didnt already go through all the trouble of doing it on my Windows box I would definitely try your live CD. I already have 10.04 installed on my laptop and I never really thought of trying it on there. I wonder if it would have been easier....oh well. Thanks again. Im sure there are plenty of people out there that will find this very useful.

Much easier. And yes, this IS awesome. Great job, Shad0wf0x. This kicks ass.

This is a fantastic idea, I had a ton of trouble rooting my Aria on Win7 x64 and downloading and using Ubuntu 10.04 eventually proved to be much easier. If your iso works as advertised I can see this possibly being the most pain-free solution for annoyed Windows rooters.
Sent from my HTC Liberty using XDA App

This works wonderfully for rooting and sideloading apps (the only issue there was figuring out I needed the root account and permissions). As painless as a dentist trip.
If I was to install Ubuntu from that LiveCD, would it still have the Android SDK on it or would I need to reinstall it? I like not having to cd to it.

the android sdk is installed on the livecd and in the path, you'll have it every time you boot up, the part the script downloads will be gone on a second boot(unrevoked.com's recovery installer)

Great job!
Do u think that u could add some other HTC devices, in the future?

Awesome, thanks!

matteios said:
Great job!
Do u think that u could add some other HTC devices, in the future?
Click to expand...
Click to collapse
The devices supported are the devices supported by the unrevoked3 tool, I am not part of their team, just trying to help out some windows users who have driver problems.

Virtual image?
Has anyone created a virtual image of s full Android dev system? That would sure be handy!

jmdearras said:
Has anyone created a virtual image of s full Android dev system? That would sure be handy!
Click to expand...
Click to collapse
not sure if this is what you're looking for, but it'll help.
http://forum.xda-developers.com/showthread.php?t=701816

Problem with reflash.sh tool
I followed all the steps, till the final step, and it said failed to flash recovery image and my phone only booted up once. Am I doing something wrong?
I am currently running.
Version 2.2 updated OTA last week Aug 3rd
Kernel version - 2.6.32.15
build #: 3.26.651.6
software: 3.26.651.6
PRI version: 1.40_003

jbwfg said:
I followed all the steps, till the final step, and it said failed to flash recovery image and my phone only booted up once. Am I doing something wrong?
I am currently running.
Version 2.2 updated OTA last week Aug 3rd
Kernel version - 2.6.32.15
build #: 3.26.651.6
software: 3.26.651.6
PRI version: 1.40_003
Click to expand...
Click to collapse
it says in your signature you have 2.2 updated OTA, that must mean you have an evo, and those aren't supported by the unrevoked tool when running 2.2.

awesome shortcut for rooting phones, however I followed the steps and it is saying that the hero is not supported at this time? Did i do something wrong, I'm running 2.27.651.5

I've burned the the iso file to a cd but I'm not able to get the boot-up to work correctly..or to come up at all, when re-booting windows.

@lcw
When you boot, you will need to hit your bios and select your CD drive as a boot device. Then enjoy the ride - easy as falling off a bike.

I cannot get my dell d600 or d630 to boot. The CD spins but I get the message "No bootable device".
I verified that the ubunto_*HTCROOT.iso file 641,942 kb is the only file on the CD.
Can someone please help.

pinkpanther2000 said:
I cannot get my dell d600 or d630 to boot. The CD spins but I get the message "No bootable device".
I verified that the ubunto_*HTCROOT.iso file 641,942 kb is the only file on the CD.
Can someone please help.
Click to expand...
Click to collapse
You're not supposed to burn the ISO file onto a disc as a file. You're supposed to burn the contents of the ISO to a disc.
Sent from my HTC Liberty using XDA App

I attempted to boot from the CD, I get the person/keyboard screen then i get the Ubuntu screen, then my computer goes black, any solutions?

This is the BEST way to root your Aria. Big props to everyone that helped create it. You guys are the best.

Gain root access to hardware locked vibrant

We now know that the new vibrant phones have the hardware key disabled to enter recovery mode. But these phones are not defective. The hardware key has been purposefully disabled as part of a misplaced strategy to secure a phone that has basically no security built into it.
Therefore it is really easy to gain root access to these phones. However the process requires the use of the adb program that is part of the google android sdk. This program likes to run on a 32-bit linux distribution. Since it will not run on a 64 bit system, here is how I managed to gain root access to my phone:
1. Download the sdk from google.
2. Boot into linux on a 32 bit machine. (I used ubuntu live cd on an old Toshiba laptop with an available linux partition to mount on the hd. Your mileage may vary.)
3. If you are not using ubuntu make sure that your c library is compatible.
4. Install the google android sdk on the hd linux partition, e.g. /home/android.
5. Plug your Samsung vibrant into the usb port on the linux machine.
The following steps are specific to ubuntu. The important thing to remember is that the adb program must run its server as root to gain the access we desire.
6. Start the terminal app: Applications > Accessories > Terminal
7. Mount the partition and change to the sdk directory:
sudo mount /dev/sda2 /media
cd /media/*/home/android/tools
7. Start the adb server:
sudo ./adb start-server
8. Make sure your device is recognized:
./adb devices
If you do not see your device connected you have some troubleshooting to do.
9. Reboot your phone into recovery mode:
./adb reboot recovery
Congratulations! You just gained root access to your hardware locked vibrant.
This message has been posted by my old g4 laptop while tethered through t-mobile 3g using wireless tether on my brand new Samsung vibrant.

M_T_M said:
Hmmmm..good enough to stick!
Click to expand...
Click to collapse
Yeah it's good, but you should move this thread to Samsung Vibrant forum.

This works on any android phone.
Although the method was inspired by the desire to use my vibrant as a g3 modem, the adb program is a general android maintenance tool that runs on linux. So it really doesn't matter what kind of phone you have. Once you have started the adb-server as root the reboot command will boot any android phone plugged into the linux box.

Spiaatie said:
Yeah it's good, but you should move this thread to Samsung Vibrant forum.
Click to expand...
Click to collapse
I know, I know mate .....I'll do it later...

r2d4 said:
Although the method was inspired by the desire to use my vibrant as a g3 modem, the adb program is a general android maintenance tool that runs on linux. So it really doesn't matter what kind of phone you have. Once you have started the adb-server as root the reboot command will boot any android phone plugged into the linux box.
Click to expand...
Click to collapse
Would this also work for the new T-mobile G2 4G ?

I'm sure we will be seeing more locked phones besides the vibrant and g2. This fix should work for them all. The adb-server gives you root access to your phone provided that you have root access to the machine upon which it runs.

r2d4 said:
I'm sure we will be seeing more locked phones besides the vibrant and g2. This fix should work for them all. The adb-server gives you root access to your phone provided that you have root access to the machine upon which it runs.
Click to expand...
Click to collapse
Keep in mind that no matter what you do on the G2, it'll be wiped on reboot. You can gain root temporarily, but when you reboot, it's gone

Installing the root update
tjhart85 said:
Keep in mind that no matter what you do on the G2, it'll be wiped on reboot. You can gain root temporarily, but when you reboot, it's gone
Click to expand...
Click to collapse
If you want to keep root after your next reboot, you need to update your filesystem. The first step is to install the programs busybox and su.
Before you boot into recovery mode, make sure you have the update.zip file downloaded onto your phone's internal memory card. Whatever is on this card will be left alone even upon a factory reset. But the phone's internal memory will be wiped. The update.zip file merely installs those two programs to the internal memory and doesn't wipe anything.
1. Download the root update for your phone. Rename the file update.zip and place it on the root directory of your device's internal flash memory.
2. Once you are in recovery mode, use the volume keys to scroll and the power key to select "reinstall packages". (This works on the vibrant. The g2 may be slightly different.)
3. Your phone will reboot and you will find the Superuser app has been installed. This app lets you grant root access to applications that need it.
Now you can download powerful apps from the market to gain even more control over your phone.
I hope this helps.

Does boot with a live CD of 32 bit ubuntu on my AMD64 work?? or do i need to boot on a computer with a 32bit processor as well?

Nextbook Flexx 11 Tutorials

Nextbook Flexx 11
A 200-250$ 2-in-1 laptop.
CPU: 1.83 GHz Intel Atom Z3735F Quad-Core
RAM: 2 GBs
SSD: 64GBs
Screen: 11.6" Touchscreen
Ports: 1 x MicroHDMI, 1 x MicroUSB 2.0, 2 x USB 2.0
Micro SD Card slot

Installing every linux based OS(Android, RemixOS, Linux Distros)
Prerequisites:
A bootia32.efi file (Found in attachments)
A copy of your favorite linux distro
Rufus, UNetbootin, or a USB disk image write of your choice.
A flash you can wipe, and boot from
A little bit of time
Step 1: Setting up
First thing you'll need to do is use your image writer to write the iso to your USB.
MAKE SURE YOU SELECTED THE RIGHT USB DRIVE!
I cannot stress this enough, if you don't want to lose everything on another flash drive, or your hard drive, check and make sure you are using the right drive letter.
Do not restart now. We need to add some files to it.
Extract bootia32.efi and copy it to /boot/efi on your flash drive.
So this was some instructions I made for booting it, but this is much more complicated than it should be. You can totally disregard this spoiler.
Step 2: Booting
Plug your USB into your nextbook (if you haven't already) and turn it on/reboot it.
As its powering on, hold ESC to get into the boot options.
Click "Boot Manager" and select your USB drive.
IF IT DOESN'T SHOW UP, FORMAT YOUR USB DRIVE TO FAT32 AND GO BACK TO STEP 1.
Now, 2 things may happen, it may boot up perfectly, and from there, just follow the steps to install.
If it doesn't boot properly, we'll need to type a few commands.
Step 2.1: Grub Command Line.
So if it doesn't boot up properly, which chances are it wont, you'll be dropped into a command line.
This is grub, if you didn't know, and to boot we need to locate the drive its on.
First press FN+Ins to turn off NumLk, then type,
Code:
linux (hd
now if you press tab, it should list everything you have attached, for example:
Code:
hd0, hd1, hd2, hd3
The usb will most likely be hd0. So now you should have
Code:
linux (hd0,
If you press tab again, it will list off all of your partitions, or autofill one in.
Now you should have either:
Code:
1. linux (hd0,msdos1)
2. linux (hd0,gpt1)
Now, if you have this, type this(replace hd0,gpt1 with what you got):
Code:
set root=(hd0,gpt1)
then type
(new)Step 2: Creating a boot file.
So, now that you have the files copied over, you need to name the drive.
Right click your drive, and click Rename... (Remember the drive name, its important)
After you renamed your drive, create a folder at DriveLetter:/boot/grub
In that directory, create a file named grub.cfg
Now depending on your linux version, you'll have either syslinux, or grub already.
If grub: The file should already be there, so you can move on to step 3.
If syslinux: Find the isolinux.cfg or syslinux.cfg (probably in /syslinux or in /isolinux)
It will look something like:
Code:
label LinuxVersion
kernel /kernelFile
append initrd=/initrdFile (more options)
We're going to use these options to create our grub.cfg file.
Use this as a template.
Code:
menuentry 'LinuxVersion' {
search --set=root --label THIS_IS_WHERE_THE_LABEL_YOU_SET_EARLIER_GOES
linux /kernelFile (more options)
initrd /initrdFile
}
Step 3: Boot into your new OS.
Reboot your PC. When it turns back on, hold ESC.
You should be brought back to the BIOS area.
Press "Boot Manager" (you will need a mouse for this), and select your USB drive.
If you did everything correctly, it should boot.
Step 4: Go wild!
You should be booted, GO CRAZY!
There are a few problems with most distros, including:
No Wifi
No Bluetooth
No Gyroscope
No Audio
There are drivers online for these, but you need to be able to patch a kernel, and build/install a driver.
Wifi
Is the guide not working?
Go ahead and ask some questions, don't be afraid of help.

Useful resources:
Ubuntu with Wifi (Source)
Thats all the links for now. I will add more as I find them (hopefully to fix audio, power button, and rotation)
Huge thanks to Ian Morrison for the Ubuntu iso.

TAG

Any chance you're going to do the linux?
Reserved
I'm guessing that is where the linux how to, is going.

Dude.. You gonna finish this?
set code=(hd0,msdos1)
Then type
Type what? Need a complete tutorial here...

I'm so sorry
Chaosmstr said:
Dude.. You gonna finish this?
set code=(hd0,msdos1)
Then type
Type what? Need a complete tutorial here...
Click to expand...
Click to collapse
I apologize for the delay, busy with school and all.

You can't leave us hanging like this!

I'm not sure about OP here, but I have the smaller model of this device being the Flexx 10. Now I haven't tried to boot Android on it, but I have successfully booted Linux Mint with it.
First I would recommend using a USB OTG capable flash drive (they are available at office stores, walmart, and so on and so forth,) or an OTG adaptor instead of using a full sized usb. The reason for this is stability of the booted system as the connection of the keyboard dock does not appear to be extremely reliable. This may vary by model or device but I would still recommend it as you may need the full sized USB ports later.
Now instead of using Unetbootin, I used Rufus. I used the settings of GTP for efi and bios to write the image to the drive. I didn't mess with any other settings there. After that I had to get a file called bootia32.efi and then add it to the /efi/BOOT/ before the system would even try to recognize it. From there it was just waiting patiently while it booted. (use the instructions in the earlier post to get to the boot options of the UEFI) It took it a while to boot as I suspect the USB speed was rather slow.
As I didn't really have time to really mess with it and get to the point of install, I will list the issues I came across.
1: Automatic rotation of the screen did not work.
2: wifi (RTL8723BS SDIO)
3: bluetooth
4: sound
everything else seemed to work just fine though, even the volume rocker, windows button and power button on the tablet section reacted and did things. not entirely useful, but they did work.
Edit: forgot to mention that if you go through with the install, you will have to finish the install by doing some grub modifications to make it boot without a live disk. just a heads up.

Hmfan said:
I'm not sure about OP here, but I have the smaller model of this device being the Flexx 10. Now I haven't tried to boot Android on it, but I have successfully booted Linux Mint with it.
First I would recommend using a USB OTG capable flash drive (they are available at office stores, walmart, and so on and so forth,) or an OTG adaptor instead of using a full sized usb. The reason for this is stability of the booted system as the connection of the keyboard dock does not appear to be extremely reliable. This may vary by model or device but I would still recommend it as you may need the full sized USB ports later.
Now instead of using Unetbootin, I used Rufus. I used the settings of GTP for efi and bios to write the image to the drive. I didn't mess with any other settings there. After that I had to get a file called bootia32.efi and then add it to the /efi/BOOT/ before the system would even try to recognize it. From there it was just waiting patiently while it booted. (use the instructions in the earlier post to get to the boot options of the UEFI) It took it a while to boot as I suspect the USB speed was rather slow.
As I didn't really have time to really mess with it and get to the point of install, I will list the issues I came across.
1: Automatic rotation of the screen did not work.
2: wifi (RTL8723BS SDIO)
3: bluetooth
4: sound
everything else seemed to work just fine though, even the volume rocker, windows button and power button on the tablet section reacted and did things. not entirely useful, but they did work.
Edit: forgot to mention that if you go through with the install, you will have to finish the install by doing some grub modifications to make it boot without a live disk. just a heads up.
Click to expand...
Click to collapse
Sorry I'm coming back so late, I've been busy with life.
The Wifi issue can be fixed by building the driver (https://github.com/hadess/rtl8723bs)
The bluetooth wont work on most OS' because it relies on some windows drivers to work.
I might be able to find a driver for screen rotation/audio.
Another issue is the power doesn't get registered, and the touch screen is VERY flaky.

Kitsumi said:
Sorry I'm coming back so late, I've been busy with life.
The Wifi issue can be fixed by building the driver (URL removed per post restrictions.)
The bluetooth wont work on most OS' because it relies on some windows drivers to work.
I might be able to find a driver for screen rotation/audio.
Another issue is the power doesn't get registered, and the touch screen is VERY flaky.
Click to expand...
Click to collapse
I didn't really notice that power one as I did not use it long, but I think that is just an atom thing. My old n270 based aspire one does that too.
Really though, the way I would use it, I wouldn't miss screen rotation or the bluetooth, but the touch screen is the nuisance. What I noticed with it is that when the screen is forced into proper orientation (by use of screen rotation in the settings, you know without using the command line) is that the touch screen doesn't follow the new orientation correctly. It appears to have the portrait resolution set to the top left of the screen in landscape. That said, it works fine in portait. Or at least managably.

Hmfan said:
I didn't really notice that power one as I did not use it long, but I think that is just an atom thing. My old n270 based aspire one does that too.
Really though, the way I would use it, I wouldn't miss screen rotation or the bluetooth, but the touch screen is the nuisance. What I noticed with it is that when the screen is forced into proper orientation (by use of screen rotation in the settings, you know without using the command line) is that the touch screen doesn't follow the new orientation correctly. It appears to have the portrait resolution set to the top left of the screen in landscape. That said, it works fine in portait. Or at least managably.
Click to expand...
Click to collapse
Well, I decied to try and boot remixOS, and it works VERY well, so does android-x86 5.0
That being said, audio is a glaring issue.

When you tried Remix OS and say it worked very well. What do you mean? What actually worked? Obviously audio is what doesn't since you mentioned it. But am I to assume that screen rotation works as expected then?
I'm not willing to use REMIX OS personally as the whole android bit is a limiting factor to me. Unless it rooted of ccourse. but even then some of my prefered uses for Linux is lost.
Also hows the hardware acceleration?

How do I install the x64 version of Windows? I downloaded the ISO with the Media Creation Tool and it won't boot from the USB drive. I enabled USB booting and made sure secure boot was off, but it's not working. It keeps saying there's no USB device available.

Unfortunately due to the way that Windows works, the 64 bit version is not usable due to the bootloader difference. Even though the hardware of the device is capable of 64 bit code execution, the 32 bit UEFI Bootloader will only allow a 32 bit version of Windows or a 64 bit version of Linux with some EFI fiddling. And as far as I know there is not a way to fiddle with the EFI related workings of a Windows ISO so 64 bit Windows is not possible on these Nexbook devices or others with similar hardware (Asus t100 is a good example of similar device)

Hmfan said:
Unfortunately due to the way that Windows works, the 64 bit version is not usable due to the bootloader difference. Even though the hardware of the device is capable of 64 bit code execution, the 32 bit UEFI Bootloader will only allow a 32 bit version of Windows or a 64 bit version of Linux with some EFI fiddling. And as far as I know there is not a way to fiddle with the EFI related workings of a Windows ISO so 64 bit Windows is not possible on these Nexbook devices or others with similar hardware (Asus t100 is a good example of similar device)
Click to expand...
Click to collapse
That's really dumb. Most Windows devices are 64-bit nowadays. Why would they put in a 64-bit processor but not allow x64 operating systems?

You're guess is as good as mine on that one. Ask Microsoft on that one. They used the 32 bit version because Microsoft will only give the "Windows XX (originally 8.1) with bing 32bit for free. Which keeps the device cost down. Kinda hard to to sell a cheapskate device when it ends up costing as much as a better speced laptop.

Where can I find recovery images for this? I messed up and now I don't have audio or touchscreen drivers.

You can try this web site from Efun themselves
http://nextbookusa.com/recovery/index.html That is their official recovery download site.
(apparently I can post links...)

Hmfan said:
You can try this web site from Efun themselves
http://nextbookusa.com/recovery/index.html That is their official recovery download site.
(apparently I can post links...)
Click to expand...
Click to collapse
I tried that. It says there's no recovery option for this model....
Do you have this tablet? Do you think you could do a driver backup and upload it here? Or create a recovery image and share it?

Install Android 7.0 Nougat in PC Hard-Drive | Dual-Boot with Windows OS

1. Download Android Nougat 7.0 ISO file[Developed by Android x86].
2. Download Rufus win App to Create Bootable/Live USB.
3. Insert USB with Minimum 4GB and select Downloaded ISO file and finally start.
4. After Finishing, Create New/ Separate Partition in PC for Android to be Installed with Minimum of 16GB Disk Size and Format it as FAT32.
5. After formatting, Reboot PC.
6. Boot PC from USB.
7. Select Install android x86 to HDD.
8. Now In bluescreen Select the Separate Fat32 formatted Partition to Install.
9. Do not Format.( I didn't formatted and it works fine).
10. Install Boot Loader GRUB.( It will replaces default Windows Bootloader).
12. Next it shows up that your are having Windows Partition and asked to create boot item for windows. Select Yes for that else you won't be able to boot into Windows next time.
13. Next Select Skip for EFI GRUB2.(I Skipped and worked for me, I think because I'm having Legacy PC).
14. Then Select Yes to Create Read/Write enabled system directory.
15. Now To create data.img, select yes and then Enter the Size you need for System Memory in MBs (1GB-1024MB).
16. Now Accept Reboot and then Boot Android from GRUB Menu.
17. Thats all . You have Successfully installed Android 7.0 nougat in your PC HDD.
Also I Made Video Tutorial in YouTube for Better Understanding. You can Checkout if you don't understand or if any error pops.
https://www.youtube.com/watch?v=o90aPj4zT-M(TechGeekShan).
Follow Me
http://facebook.com/techgeekshan
http://twitter.com/techgeekshan
https://www.reddit.com/r/TechGeekShan/
http://instagram.com/techgeekshan/
http://www.techgeekshan.in/

Wow thanx mate, will give it a try and will give a feed back.
Sent from my SM-G935F using XDA-Developers mobile app

silverrum said:
Wow thanx mate, will give it a try and will give a feed back.
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah.. You are welcome and we must Appreciate the Developer who developed Android Nougat x86..

Don't work for me((( Laptop wan't boot after installation...

gmikes said:
Don't work for me((( Laptop wan't boot after installation...
Click to expand...
Click to collapse
Its because of EFI/UEFI Computers

Why not work
Shanmukarajan said:
Its because of EFI/UEFI Computers
Click to expand...
Click to collapse
Why not Work ?

If I install it on my PC, do I access google play store like normal?

successfully installed on Z3735F Bay Trail-T windows 10 tablet. I don't need windows 10 OS anymore, so made one partition and install Android 7. It books OK, WIFI works fine. BUT!!!!! All the physical buttons don't work. Power button doesn't work, so there is no way to turn off the system. Volume Up and Down button also doesn''t work. But touch screen works fine. How to solve this problem? any idea? My tablet is Unbranded Tablet 10.1 from Best Buy

hey,
i got it up & running on my uefi windows 10 lenovo yoga (after some struggle i also have dual-boot). my question - how do i get gapps and supersu? it's not like you could simply flash some zips, as there is no recovery

No Playstore!! Browser does not download files!!!
So after wasting 400mb of data and roughly 30 minutes of my time, I discover that there is no preinstalled PlayStore, the preinstalled browser will not download APKs and trying to install apps from the online MarketPlace only discovers devises that the email used to Sign In with is associated to, not the device this is installed on.
These things SHOULD by all ethical means be stated in the description to prevent others from wasting both their time as well as their data.
I want to see a solution to these problems Shanmukarajan. Should you decide to neglect this issue, I won't hesitate to have this post reported to the moderators.
Thank you in advance for your prompt support on the matter.
Stevo | True.Tech.Tabs
+1 360 **** ***

there is just one issue.
you can not create a data.img file that is larger than 4GB on a fat32 partition...
how do we fix that?

It’s installs fine but when restarts windows is just starting every time and it’s not coming up with step 12 asking me about windows partition and creating boot item

I performed the installation process about 10 times with different settings but none of them seem to install Android on my HDD. The live version works and there are no errors whatsoever, but even after installation there is never an option to boot the installed Android. Only live, debug or again option to install the OS. Does anyone know the solution?
Sent from my Xperia X Compact using XDA Labs

Godecki said:
I performed the installation process about 10 times with different settings but none of them seem to install Android on my HDD. The live version works and there are no errors whatsoever, but even after installation there is never an option to boot the installed Android. Only live, debug or again option to install the OS. Does anyone know the solution?
Sent from my Xperia X Compact using XDA Labs
Click to expand...
Click to collapse
Have you tried selecting yes to GRUB 2 during installation? It's been a little while since I went through the process, but I believe that was what I had to do to get it up and running.

Godecki said:
I performed the installation process about 10 times with different settings but none of them seem to install Android on my HDD. The live version works and there are no errors whatsoever, but even after installation there is never an option to boot the installed Android. Only live, debug or again option to install the OS. Does anyone know the solution?
Click to expand...
Click to collapse
Yeah I have the same issue with my Sony VAIO Duo 11. To start from power off I have to hit the special Duo Assist button, then F11 to boot from usb, then go thru the (re) install every time, so boot takes a couple of minutes, but it always bring me back to the same great working Android with all apps and setting unchanged. I don't understand, but I just happened onto it. Be sure to not format or install any grub (not really sure about grub or grub2), but yes to make it writeable. Then you get an awesomely fast Android.
I don't even want Windows on that machine, but I'm afraid to kill all the partitions and start from scratch as the Duo has some weird builtin Windows boot stuff hard wired. I'm not sure if Android could boot without the Windows partitions.

When I am creating a new partition with 16 GB of space does it mean that Android is going to use just this partition and 16 GB or is it just for the installation files and Android will see my whole HDD as the internal storage?

Could you please let me know how you got it up and running? I am on a UEFI yoga as well, but after the installation,
grub doesn't show up and my computer boots automatically into Windows
Thanks in advance
bombaglad said:
hey,
i got it up & running on my uefi windows 10 lenovo yoga (after some struggle i also have dual-boot). my question - how do i get gapps and supersu? it's not like you could simply flash some zips, as there is no recovery
Click to expand...
Click to collapse

ZOOMA7997 said:
Could you please let me know how you got it up and running? I am on a UEFI yoga as well, but after the installation,
grub doesn't show up and my computer boots automatically into Windows
Thanks in advance
Click to expand...
Click to collapse
Did you change the boot sequence in bios? Select android to boot 1st, then Grub should ask you which os you want to launch. I installed grub 2. I also went with the triple boot. My laptop is an Asus x401a with windows 7. Along with ubuntu and android. x86 Nougat.

A little help here mates,
I installed it alongside a windows 7 ultimate.
Gave it an 80gb Partition (fat32)
So I'm planning a dual boot here.
Here's my Steps:
used rufus to create bootable from android-x86-8.1-r1.iso
booted to Flash drive
installed android to 80gb partition (with grub/windows boot entry/ and data image of 2048MB)
after installation, Reboot to test boot options
grub didn't show up, booted directly to win7
Did some researches, and from those researches I should disable SECURE BOOT, but bios don't have that option.
Also tried EasyUEFI Tool which didn't even work in windows 7
Also, no settings for UEFI or Legacy.
Boot Order doesn't show Windows bootmanager or grub too, only HDD....
I installed android in ASUS Eee Notebook Laptop 1201b
I think the only problem here is grub cant load, but I run out of solutions, so here I am asking for help.

every android on work fine in my tablet(z3735f) but there is a bug in every os no sound in headphone any one tell me how to fix it