When I press Fn+f3 ,the recovering stoped,and the system went blue screen error.
I have a usb-cdrom ,so I want to make the HD clean for 40GB.I am going to use the ubuntu cd to boot the system and use the cmd "dd ..."
What is the correct command for delete the rescovery partition bin
http://forum.xda-developers.com/showthread.php?t=393070
I would also like to know how can i delete the recovery partition from the Shift.
The recovery windows kit is in italian and i don't really know the language. That's why i'd like to get the full 40GB and install WM7.
Please help
Nobody ?
6 GB hidden, can't find sollution to delete recovery partition
I remember reading somewhere that the user 'pof' had a way to do it, but I cant find where I read it.
Try these links...
http://forum.xda-developers.com/showthread.php?t=390003
http://forum.xda-developers.com/showthread.php?t=378890
One solution I can think of is to:
1) Take the Shift HDD out and put it into a desktop PC
2) Open the disk managment program on the desktop PC and delete the partition there.
Obviously this will delete all data from the hdd. I dont even know if this is at all possible, but its something I would try!
have a new system with kubuntu linux 10, bootcd only.
where and how is root.zip saved since nothing is installed and linux runs from cd ?
what program is used on a bootcd system to open it? since nothing is installed, how is the file saved?
as trying to follow steps in http://forum.xda-developers.com/showthread.php?t=714250
A live cd runs as if it were a fully installed operating system, the only difference is that it runs from the cd. As for the files you need they can be downloaded from the the two posts. "How to root the Aria" and the " Liberated Aria" thread.
Sent from my HTC Liberty using XDA App
I Know the files, I do NOT know how they are opened on a bootcd system with no drives
where is root,zip saved? how is root.zip opened?
Most modern LiveCDs allow you to read files from a USB drive. So, you could put the files on the key in windows and then have access to them after booting from a LiveCD.
MANY THANKS TO REV FOR RE-WRITING THIS FOR ME!
(Post was updated on 3/23/2011)
=======================================
This post is to provide a template for using NVFlash to restore/recover your G-Tablet after suffering some kind of malfunction. Specifically, this document tries to provide ALL the information you need to use the NVFlash tool to recover the bekit 1105 software version, which has been found to be safe as a starting point for rebuilding your tablet after having a problem. This post does not include other methods of setting up NVFlash (such as installing the SDK, etc.) because this method is proven and can be easily supported.
I use Ubuntu Linux and know that the Linux instructions below are correct. Others have written Windows instructions and those too have been checked carefully and have been used before successfully.
A WARNING IN ADVANCE: NVFlash makes changes to the partition structure of your device. You should tread carefully and understand the risks. (MOD EDIT Note: It also has been noted a bunch of times that even NVFlashing your G-Tablet will not completely overwrite everything on it.)
The NVFlash setup process begins with a visit to:
http://db.tt/Wm25t7U
(Note: Sometime this DropBox is cranky. If you have trouble with it, check back later.)
Linux users: You want to get "nvflash_linux_2010110500.tar.gz" and "nvflash_gtablet_2010110500.zip "
Windows users: You want to get "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Note: The above "nvflash_gtablet_2010110500" is commonly referred to as bekit version 1105 in many posts relating to nvflashing (especially my posts).
-------------------------------------------
Installation
First, create a folder named "NVFlash" on your PC to put the needed files into and to work from. (Note: You can call it something else if you want to; we're just using "NVFlash" to keep all of us on the same page.)
Next, extract the files you downloaded from the DropBox above into the "NVFlash" directory. The files with linux and windows in the middle of then are the files for setting up NVFlash. (The are taken from the SDK and do not install the whole SDK -- just a simple, operable NVFlash for us to use here.) The files with gTablet in the middle contains the .img files with the software to go on your G-Tablet.
Third, for Windows users, you'll need to have an APX-specific USB driver for the next steps. (The Windows package bekit supplied has an .inf file in it, but the actual drivers are not there). For Linux users, you don't need an extra driver.
One source for the Windows drivers is at
http://www.myadventvega.co.uk/
Find the "Downloads" tab in the middle of the page and click on "USB System Driver" to get the files. Extract them and go down two levels to the "USB" folder -- and move that into your "NVFlash" directory. The USB folder has the .inf file for installation in it along with two other directories with drivers for the various operating systems. (Note: These drivers, which are the same as the drivers in the SDK, are proven to work with Win 7 64-bit and have the setup include to load into other versions of Windows.) Follow this narrative for actual installation of the drivers.
CHECKPOINT: At this point, you should have the nvflash files, .img files, and USB directory (and files) in you "NVFlash" directory and are ready to begin the recovery process.
Now, you will need to boot into G-Tablet APX mode: hold down the power and volume - button simultaneousl until your G-Tab comes up and the goes back to a black screen. The black screen means it is in APX mode and it is waiting to display the flashing process. In Linux, type "lsusb" in a terminal and you should see this "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
Connect your G-Tablet to your PC using your miniUSB to USB cable that came with your tablet.
Linux users: At this point, open up a command window to the folder you created, and run this script:
./nvflash_gtablet.sh
This will wipe the device back to bekit's original TnT stock image, except for user data which is retained. Should take about a minute to run and the device will reboot itself automatically. If the script does not work, make sure that the shell script and nvflash binary are set as executables.
Windows users: When you connect to the PC, the PC immediately tries to load a driver -- but since it doesn't know where the USB driver files are it will fail. Click through Start/Control Panel/Device Manager and find "APX" listed in the devices with a yellow "!" (exclamation point) on the icon. Select the APX item and find the "Update Driver" button and click it. When it asks where to search, choose the local computer manual selection choice and tell it to Browse.
Point the Browse (and the USB install) at the "USB" directory under the "NVFlash" folder. When pointed at the "USB" directory, the driver installed and I was ready to nvflash. If you go back to Device Manager after the Windows install has completed, it will show the nVidia USB drivers near the top of the USB device list.
Again, for Windows: Run this script which is in the "NVFlash" folder:
nvflash_gtablet.bat
This will wipe the device back to bekit's original TnT stock image except for user data, which is retained. Should take about a minute to run and the device will reboot itself automatically all the way to the main screen.
POST NVFlash:
When your G-Tablet has booted back to the main screen, you will have to check and make sure everything is set up. Particularly, get the wifi on and connected to the Internet. Almost immediately, you should get a notice about an OTA (over the air) update. This is the OTA Update to software version 3588. If it does, go ahead and have it do the update. From there, you can begin using your "stock 3588" G-Tablet.
If you don't get an automatic OTA notification, you can go the to manual "Update" icon on your tablet and have it check for updates -- and hopefully it will find OTA 3588.
Or, if neither of the above happen, you can download 3588 at the following link and install it manually:
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip
Note: Following is a STICKY from General Forum on the stock recovery process:
http://forum.xda-developers.com/showthread.php?t=892090
NOTICE: There are many threads out there with tell how to do this process. Others tell individuals' problem solving experiences. A few of them may not be right! The above process is not the only way to do this -- but it is fairly straightforward and it is proven. It is recommended for anyone who does not have experience with nvflashing.
***************************************************
Further references (since I'm not a Windows user): http://forum.xda-developers.com/show...0&postcount=28
and http://forum.tegratab.com/viewtopic....bbde76184e550a and http://wiki.tegratab.com/index.php/Nvflash_FAQ
An additional suggestion if you also want to tack on bekit's clockworkmod recovery versus standard recovery: http://forum.xda-developers.com/show...3&postcount=17
Hope this helps!
03/2011 update -- I've been told that this tool has been useful to erase ALL partitions, including user data. I believe you need to re-flash with the bekit 1105 above, AFTER you use this: http://forum.xda-developers.com/showthread.php?t=974422
04/22/2011 update -- I've built out both 1.1-3588-based and 1.2-4349-based versions that have effectively replaced bekit's 1105 image ("nvflash_gtablet_2010110500.zip"), at least on my own device - I'm also addding a clockworkmod recovery option. It is being hosted in the same location as my 1.2-based mods - I will be making updates there, from this point on (as I might update them from time to time).
(you'd still need bekit's Windows or Linux tools, keep in mind) I've been able to bring back my device back from a soft-brick several times, so I feel they are usable.
05/09/2011 update -- A reminder that these images are not being updated, here. I have a newer nvflash post over in the same site where I have my 1.2-based mods. The 1105 bekit image mentioned here is still relevant for 1.1-based ROM users, or you can use my 3588 ot 4349 solution at the other site.
05/10/2011 update -- I have PM'd the moderator to either unsticky this post and / or assign it to someone else, as I do not plan on updating it, here. I believe that there is a 3588 image in the TegraTab IRC that someone created, for example.
Looks good Roebeet. I wrote a little how to a while back on tegratab. I know you are aware but for the benefit of others I wanted to add the following.
One little thing is sometimes when you are done you will get a boot loop. I think it only may happen once as I never saw it again. The fix is to go into Clockwork and partition the internal sd card again. The old settings said 512 for memory, and 256 swap. Bekit updated Clockwork and now you can format all the way to 4gb if you like, and swap should be 0 as it is not used.
Edit: New wisdom says not to partition the internal sdcard to anything but 2048. Folks have had issues with memory errors in the market with anything bigger. 0 for a swap is also the recommendation as Android apparently does not make use of the swap.
roebeet said:
Wanted to expand on what was already here, since there seems to be a lot of questions that pop up. I use Ubuntu so I know that the Linux instructions are correct.
A warning in advance: nvflash makes changes to the partition structure of your device. You should tread carefully and understand the risks.
Pre-req: http://db.tt/Wm25t7U
Linux users: You want to get "nvflash_linux_2010110500.tar.gz" and "nvflash_gtablet_2010110500.zip "
Windows users: You want to get "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Other references (since I'm not a Windows user): http://forum.xda-developers.com/showpost.php?p=9564270&postcount=28
and http://forum.tegratab.com/viewtopic.php?f=6&t=8&sid=4e6bd75cda9e24e04fbbde76184e550a
http://wiki.tegratab.com/index.php/Nvflash_FAQ
-------------------------------------------
Installation
Create a folder on your PC which you use as your restore base, and then extract the platform-specific ZIP into that location.
Then, download the "nvflash_gtablet_2010110500.zip" package and unzip the /nvflash_gtablet/ folder inside into the same folder as where you dropped nvflash.
For Windows users, you'll need to have an APX-specific USB driver for the next steps (I believe that the Windows package bekit supplied has that .inf file, but again I don't know for sure). For Linux users, you don't need an extra driver.
Once ready, boot the device into APX mode (power up and volume down, at the same time - you'll see the boot screen pop up, and then go blank.). In Linux, type "lsusb" in a terminal and you should see this "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
Linux users: At this point, open up a command window to the folder you created, and run this script:
nvflash_gtablet.sh
This will wipe the device back to bekit's original TnT stock image, except for user data which is retained. Should take about a minute to run and the device will reboot itself automatically.
Windows users: (again, I did not test this myself). Run this script, in the folder you created:
nvflash_gtablet.bat
Hope this helps!
Click to expand...
Click to collapse
I need help. I finally got Windows 7 to recognize the device in APX mode but how do I flash from this point. It only shows up in my Device list with all the subfolders in it.
What is this for? Restoring to factory Rom?
Thanks,
Scott
cscotty said:
What is this for? Restoring to factory Rom?
Thanks,
Scott
Click to expand...
Click to collapse
Yes, you can use it for exactly that. I believe bekit added Launcher Pro and superuser, but other than that it's a way to completely wipe the device. Moreso than a standard recovery would do.
The pre-req link doesnt work. Can you update the link?
Thanks
roebeet said:
Wanted to expand on what was already here, since there seems to be a lot of questions that pop up. I use Ubuntu so I know that the Linux instructions are correct.
A warning in advance: nvflash makes changes to the partition structure of your device. You should tread carefully and understand the risks.
Pre-req: http://db.tt/Wm25t7U
Linux users: You want to get "nvflash_linux_2010110500.tar.gz" and "nvflash_gtablet_2010110500.zip "
Windows users: You want to get "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Other references (since I'm not a Windows user): http://forum.xda-developers.com/showpost.php?p=9564270&postcount=28
and http://forum.tegratab.com/viewtopic.php?f=6&t=8&sid=4e6bd75cda9e24e04fbbde76184e550a
http://wiki.tegratab.com/index.php/Nvflash_FAQ
-------------------------------------------
Installation
Create a folder on your PC which you use as your restore base, and then extract the platform-specific ZIP into that location.
Then, download the "nvflash_gtablet_2010110500.zip" package and unzip the /nvflash_gtablet/ folder inside into the same folder as where you dropped nvflash.
For Windows users, you'll need to have an APX-specific USB driver for the next steps (I believe that the Windows package bekit supplied has that .inf file, but again I don't know for sure). For Linux users, you don't need an extra driver.
Once ready, boot the device into APX mode (power up and volume down, at the same time - you'll see the boot screen pop up, and then go blank.). In Linux, type "lsusb" in a terminal and you should see this "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
Linux users: At this point, open up a command window to the folder you created, and run this script:
nvflash_gtablet.sh
This will wipe the device back to bekit's original TnT stock image, except for user data which is retained. Should take about a minute to run and the device will reboot itself automatically.
Windows users: (again, I did not test this myself). Run this script, in the folder you created:
nvflash_gtablet.bat
Hope this helps!
Click to expand...
Click to collapse
stanglx said:
The pre-req link doesnt work. Can you update the link?
Thanks
Click to expand...
Click to collapse
It seems to go up and down (it's bekit's dropbox). Try this:
https://www.dropbox.com/s/wrcd87u1iy31u4e
roebeet said:
Wanted to expand on what was already here, since there seems to be a lot of questions that pop up. I use Ubuntu so I know that the Linux instructions are correct.
A warning in advance: nvflash makes changes to the partition structure of your device. You should tread carefully and understand the risks.
Pre-req: http://db.tt/Wm25t7U
Linux users: You want to get "nvflash_linux_2010110500.tar.gz" and "nvflash_gtablet_2010110500.zip "
Windows users: You want to get "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Other references (since I'm not a Windows user): http://forum.xda-developers.com/showpost.php?p=9564270&postcount=28
and http://forum.tegratab.com/viewtopic.php?f=6&t=8&sid=4e6bd75cda9e24e04fbbde76184e550a
http://wiki.tegratab.com/index.php/Nvflash_FAQ
-------------------------------------------
Installation
Create a folder on your PC which you use as your restore base, and then extract the platform-specific ZIP into that location.
Then, download the "nvflash_gtablet_2010110500.zip" package and unzip the /nvflash_gtablet/ folder inside into the same folder as where you dropped nvflash.
For Windows users, you'll need to have an APX-specific USB driver for the next steps (I believe that the Windows package bekit supplied has that .inf file, but again I don't know for sure). For Linux users, you don't need an extra driver.
Once ready, boot the device into APX mode (power up and volume down, at the same time - you'll see the boot screen pop up, and then go blank.). In Linux, type "lsusb" in a terminal and you should see this "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
Linux users: At this point, open up a command window to the folder you created, and run this script:
nvflash_gtablet.sh
This will wipe the device back to bekit's original TnT stock image, except for user data which is retained. Should take about a minute to run and the device will reboot itself automatically.
Windows users: (again, I did not test this myself). Run this script, in the folder you created:
nvflash_gtablet.bat
Hope this helps!
Click to expand...
Click to collapse
Roebeet sorry but I just noticed for noobs that the linux command needs to be
. nvflash_gtablet.sh
Also if you unzip those files into a premade directory such as "gtablet" when you unzip them each have their own directories and if you ls you can see that the bash script isn't executable from there. So you need to copy either the gtablet files into the platform folders or copy all the files inside both into your "gtablet" folder. Then you can run the ". nvflash_gtablet.sh" command and voila. Sorry I am on Ubuntu and don't know if it is different, but that is the way I run them.
No worries - all replies are welcome! the more info we have, the better.
This should be stickied. Nvflash has saved my gtab many times and I think its the reason why my gtab doesn't really encounter too many Force closes. Its the perfect method to ensure your gtab is clean.
I tried this tonight to try to get my gTablet back to stock so that I could show people how to install CWM on a video but I could get neither of my Windows 7 64-bit computers to recognize the APX .inf that was included in the pack.
I have a linux machine around here somewhere I may have to use...
ehunyadi said:
I tried this tonight to try to get my gTablet back to stock so that I could show people how to install CWM on a video but I could get neither of my Windows 7 64-bit computers to recognize the APX .inf that was included in the pack.
I have a linux machine around here somewhere I may have to use...
Click to expand...
Click to collapse
My limited experience with 64-bit Win7 -- the drivers have to be signed, or else they won't work. There's a way to disable that on boot, but you can't permanently disable it. I'm wondering if the APX USB driver is signed?
Open a command prompt as an admin and type
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
This is the only way.. dont worry if the test watermark shows up.. it wont affect anything.
Also... They have a x64 driver - read this
http://tegradeveloper.nvidia.com/tegra/forum/adb-usb-driver
Hi there,
I exchanged for a new Gtab yesterday from sears (as it had some power issues).
Today, I tried TnT 2.2 on my rooted tab (Z4 for rooting). Also have ClockworkMod .8.
I partitioned my internal SDCard. But after vanilla restore, I could find my tab space reduced to 4 gigs. What should I do to restore to full 16 gigs(14+ gigs actually).
============================================================================================================================
2. I followed your instrction and partitioned again in clockworkMod and did 4 gigs and 0 in the second one. Now it shows 11 gigs for data and 4 gigs for system.
Now I inserted an external micro SD card (16 gigs) but my storage is not seeing it. What should i do? Ignore my first part please.
Your gonna have problems later if you don't repartition to 2048 and 0
satishraman said:
Hi there,
I exchanged for a new Gtab yesterday from sears (as it had some power issues).
Today, I tried TnT 2.2 on my rooted tab (Z4 for rooting). Also have ClockworkMod .8.
I partitioned my internal SDCard. But after vanilla restore, I could find my tab space reduced to 4 gigs. What should I do to restore to full 16 gigs(14+ gigs actually).
============================================================================================================================
2. I followed your instrction and partitioned again in clockworkMod and did 4 gigs and 0 in the second one. Now it shows 11 gigs for data and 4 gigs for system.
Now I inserted an external micro SD card (16 gigs) but my storage is not seeing it. What should i do? Ignore my first part please.
Click to expand...
Click to collapse
You only have 16gb to start. Partitioning you internal to 4gb uses part of that. I would go back and only use 2gb, and 0 for swap. There are things, like the new market that break with anything but 2gb.
If you mean the settings menu is not showing your external sd card that's normal. Look in a file explorer program in the / directory. Look for SDcard2. That is your external. Same deal, look for usbdisk if you plug in a usb drive.
Roebeet
also this could be helpful to Ubuntu/linux users.
in the same directory where your flash script is there is a file that is called "gtablet.cfg" if you download the clockwork.img recovery and put it in this directory you can open up the "gtablet.cfg" with a text editor
scroll down to where you see "filename=part9.img" and replace "part9" with "clockwork" and it should now read "filename=clockwork.img" this will flash clockwork and save you a step. To change it back so you flash complete stock just edit the file again and reverse it.
romanrish said:
Roebeet
also this could be helpful to Ubuntu/linux users.
in the same directory where your flash script is there is a file that is called "gtablet.cfg" if you download the clockwork.img recovery and put it in this directory you can open up the "gtablet.cfg" with a text editor
scroll down to where you see "filename=part9.img" and replace "part9" with "clockwork" and it should now read "filename=clockwork.img" this will flash clockwork and save you a step. To change it back so you flash complete stock just edit the file again and reverse it.
Click to expand...
Click to collapse
You don't even have to do that - you can just rename part9.img to something else, and clockworkmod.img to "part9.img". That's actually what I do.
roebeet said:
You don't even have to do that - you can just rename part9.img to something else, and clockworkmod.img to "part9.img". That's actually what I do.
Click to expand...
Click to collapse
Yeah I thought about that, but figured some people might get confused and forget which one was which. Either way works as well just as long as you keep both files. You should edit your original post and add that in as an option to do at the end. It will keep some from having to look through and creating a new post cause they can't find it, and keep our forums clean.
This should definitely be stickied. Mods please?
P.S. I cannot believe how awesome this forum is(Viewsonic G Tablet). I have gone to other forums and the other devs and users are not as friendly and awesome as the ones we have here. Almost brings a tear to my eye. Great job Roebeet, this should help us noobs out a lot. LOL!
Mac OS X Yosemite – Dual boot Ubuntu 14.10 from an external USB Drive
*I am making this guide on my late 2013 MacBook Pro 13” Retina:
Code:
Model Name: MacBook Pro
Model Identifier: MacBookPro11,1
Processor Name: Intel Core i5
Processor Speed: 2.4 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache (per Core): 256 KB
L3 Cache: 3 MB
Memory: 8 GB
Boot ROM Version: MBP111.0138.B11
SMC Version (system): 2.16f68
This guide assumes that you DO NOT already have rEFInd installed and that you ARE familiar with installing Linux.. I currently have 2 Operating systems on my internal 256GB SSD (Windows 8 and OS X Yosemite) and I have an external USB 3.0 enclosure with a 256GB SSD installed. That’s where I want to install and boot Ubuntu 14.10 from. Let’s get started…
Make a complete backup of your Macbook Pro!!
Make sure that you’re booted into OS X.
Install rEFInd
Download the zip version 0.8.4 or later of reFind: http://www.rodsbooks.com/refind/getting.html and unzip it.
Open a terminal and change to the extracted folder directory.
Run this command:
Code:
sudo ./install.sh
Enter your password to confirm. You should now have reFind installed and if you reboot to verify, you should see its boot menu. If you have 2 Mac OS X entries, one of them will be for your normal OS X partion and the second contains recovery in the description. Boot back up your normal OS X installation.
Download Ubuntu 14.10 Desktop 64 bit: http://www.ubuntu.com/download/alternative-downloads
In the terminal convert the iso to an img:
Code:
hdiutil convert -format UDRW -o ubuntu14.10.img ubuntu-14.10-desktop-amd64.iso
OS X will add a .dmg extension to the .img file but that doesn’t matter.
Plug in your USB flash drive (I used a 4GB) and use diskutil to find out the drive number:
Code:
diskutil list
My USB drive showed as /dev/disk1
Unmount the flash drive:
Code:
diskutil unmountDisk /dev/disk1
Write the Ubuntu image to the flash drive (*Note: If you get an error about 1M, change it to 1m)
Code:
sudo dd if=ubuntu14.10.img.dmg of=/dev/rdisk1 bs=1M
*Note: I used /dev/rdisk1 instead of /dev/disk1
Eject the flash drive:
Code:
diskutil eject /dev/disk1
Connect your external USB target disk and partition it as 1 partition, in Disk Utility. Make sure to hit options and verify that the partition scheme is GUID prior to hitting apply.
Now we are ready for the fun part; installing Ubuntu 14.10.
Power off your Macbook and connect the USB flash drive with the Ubuntu installer as well as your USB target disk (In my case it’s my external enclosure with a 256GB SSD).
When you get to the rEFInd menu, choose the option that says boot Legacy OS from FAT and press enter.
When the Ubuntu installer loads, choose the “Install Ubuntu” option.
When you get to the screen that reads something like “Erase everything”, choose the “Something else” option and click continue.
It will bring up a list of your current partitions. Find the USB target disk, which should be obvious by it’s size. You should see 2 partitions on your target disk: EFI boot partition and a HFS+ partition.
DO NOT DELETE the EFI partition! Delete the other partition and then create a partition for your root mount point “/” and a swap partition. I created a 8GB swap partition and my Mac has 8GB of RAM.
BE SURE to choose the USB target disk as where to install Grub in the dropdown at the bottom of the screen. In my case it was /dev/sdb (notice no partition number).
Select your drive in the list, click install and complete the installation.
When the installation completes, hit the reboot button and if it doesn’t complete the reboot, hold down power for 5 seconds to power off. If it does complete, when you get to the rEFInd menu, choose power off.
Remove your USB installer flash drive.
Power on and if you don’t see linux in the list of operating systems in the rEFInd menu, hit “ESC” to refresh. You should see it and be able to boot to it.
Everything pretty much worked for me out of the box on Ubuntu 14.10. I did immediately change the resolution to make it easier to see.
23) I fixed the brightness buttons by:
Code:
sudo gedit /usr/share/X11/xorg.conf.d/20-intel.conf
Add the following lines to this file:
Code:
Section "Device"
Identifier "card0"
Driver "intel"
Option "Backlight" "intel_backlight"
BusID "PCI:0:2:0" EndSection
Logout and the buttons should work to adjust the brightness.
There are more online guides if you run into other hardware compatibility problems. I will update this with problems / fixes that I run across. You're now ready to look at the building Android from source guides and run them on your Ubuntu installation.
Enjoy!
If you have tried to install Windows 7 on a Surface Pro, or a UEFI-only device., you may have noticed it hangs on "Starting Windows" or gives error 0xc000000d, or you might have seen the following message:
The Surface Pro is a class 3 UEFI device, which means it has no Compatibility Support Module (CSM), which emulates the old BIOS environment. Windows 7 is not compatible with UEFI, which means without CSM, it wouldn't be able to function.
If you had to run Windows 7 on a Surface Pro, the only way would be to enable the Hyper-V feature of Windows 8 and run Windows 7 inside a virtual machine (VM). However, this would limit the resources available and the capabilities such as some of the touch/pen features.
Click to expand...
Click to collapse
However, this article proves that it isn't impossible to achieve this. This tutorial shows you how to install Windows 7 on a Surface Pro. This tutorial is meant for the Surface Pro 1, but could work on any other UEFI-only device, which it should, but not guaranteed.
ISO file link: https://archive.org/details/windows-7-surface-pro-1
INSTRUCTIONS:
1. Boot the USB. This ISO uses a Windows 10 PE, but has a Windows 7 install.wim.
2. Open command prompt by pressing "Shift+F10"
3. Type in setup.exe /noreboot
4. Go through setup normally.
5. On the command prompt, type in "diskpart"
6. Type in the following commands:
sel dis 0
lis par
sel par 1 (where your boot partition is)
assign letter w
exit
7. Open up Notepad, and click "Open" or "Save As". Enable all files to be viewed. Go to W:\EFI\Microsoft\Boot and copy the BCD file and paste it onto the Windows 7 partition.
8. Go back to diskpart by typing "diskpart" in
9. Type in the following commands:
sel dis 0
sel vol w
form quick fs=fat32
exit
10. Go back to Notepad, and click "Open" or "Save As". Enable all files to be viewed. Go to the USB drive, then go to the FlashBootPro folder, then copy the "EFI" folder.
11.Go to W:\ and paste the EFI folder.
12. Go to the Windows 7 partition and cut "BCD".
13. Go to W:\EFI\Microsoft\Boot and paste "BCD" on the folder.
14. Reboot. Setup should continue normally.
NOTE: For some reason, Windows will NOT boot if any USB devices are connected. Any time you boot into 7, you MUST disconnect them, boot into 7, then connect them again. Wifi is integrated but doesn't work. You will need to purchase a separate USB wireless adapter.
MSFN REPOST: https://msfn.org/board/topic/184267...-surface-pro-1-or-any-other-uefi-only-device/
Proof of Windows 7 installed on Surface Pro 1:
bro i can not understand most of it, is there any more specified tutorial somewhere? or can you help me?
Should i use the iso link you gave?
Hi, I follow the guide and everything went good until i got the message:
Could not install shim for VGA BIOS: Unsupported hardware
Can someone help me?
helpinghand200 said:
bro i can not understand most of it, is there any more specified tutorial somewhere? or can you help me?
Click to expand...
Click to collapse
At the last steps, you must replace the files at the hard drive where you installed Windows 7. You can do this by booting another OS, or making a live OS and then replace them on that hard drive from that OS.
HDD = Hard Disk Drive