Hi guys!
As some of you might have seen it already: Microsoft has released an Insider Preview to the Raspberry PI 2.
Here are the instructions on how put the image on an SD card:
Source: http://ms-iot.github.io/content/win10/SetupRPI.htm
We have provided a utility to provision your SD card with the Windows 10 IoT Core Insider Preview. The following steps can only be executed on a system running Windows 10 (build 10069 or higher).
Follow these instructions to configure your SD card:
NOTE: you will need to follow these instructions on a physical Windows machine (and not a VM) because you need access to the SD card reader.
Please download the package "Windows 10 IoT Core Insider Preview Image for Raspberry Pi 2" from the Microsoft Connect here. If you see a blank page or no downloads listed, please make sure you are signed into Microsoft Connect by looking at your login information at top right part of the screen. If you did not sign up for the Microsoft Connect program, please refer to the instructions in the "What you need" section above.
Make a local copy of the flash.ffu contained in the downloaded package "Windows 10 IoT Core Insider Preview Image for Raspberry Pi 2".
Insert an SD card into your SD card reader.
Open an administrator command prompt and navigate to the folder containing your local flash.ffu.
Find the disk number that your SD card is on your computer. This will be used when the image is applied in the next step. To do this, you can use the diskpart utility. Run the following commands:
Code:
diskpart
Code:
list disk
Code:
exit
Using the administrator command prompt, apply the image to your SD card by running the following command (be sure to replace PhysicalDriveN with the value you found in the previous step, for example, if your SD card is disk number 3, use
Code:
/ApplyDrive:\\.\PhysicalDrive3
below):
Code:
dism.exe /Apply-Image /ImageFile:flash.ffu /ApplyDrive:\\.\PhysicalDriveN /SkipPlatformCheck
Click on the "Safely Remove Hardware" icon in your task tray and select your USB SD card reader to safely remove it from the system. Failing to do this can cause corruption of the image.
Click to expand...
Click to collapse
This is all good and fine, but most of us don't have a physical computer running Windows 10, so as the site mentions VMs don't have access to physical drives or the card reader, so you can't format and partition a physical disk (you can virtualize it and install it onto the virtual drive, create similar partitions on the physical drive and copy the contents of the virtual drive onto it, and copy the BCD of the virtual hard drive, but that's not 7what we want to do). To be able to flash the Windows Core image onto the SD card we need the latest version of a tool called dism.exe. The latest version of this tool is included with Windows 10 (that's why this manual says that you need Win 10 to do it), but it's also available as part of the Windows Assessment and Deployment Kit and luckliy enough Microsoft has made it available for everyone, so we don't need to scrap it with its dependant DLLs from Win 10.
To be able to flash the image from a computer that's running Windows 7 or higher (I haven't tried from anything below it) we need to first download and install Windows Assessment and Deployment Kit (ADK) RC for Windows 10.
Download page: https://msdn.microsoft.com/en-gb/windows/hardware/dn913721.aspx
Direct download: http://go.microsoft.com/fwlink/p/?LinkId=526740
When installing just install it normally, on the step "Select the features you want to change" tick only the box that says "Deployment Tools" and click Install
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After the install open a CMD window as an Administrator (you have to type cmd to the start menu search and right click on the cmd.exe and click on run as administrator)
In CMD navigate to:
Code:
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM
And follow the same steps as in the instructions on the MS website. (get the disk number, and flash it with dism.exe).
Code:
dism.exe /Apply-Image /ImageFile:"C:\Image\File\Location\flash.ffu" /ApplyDrive:\\.\PhysicalDriveN /SkipPlatformCheck
(Don't forget to change C:\Image\File\Location to the location where you extracted the file from the downloaded ZIP file, also change the number of the physical drive)
On the MS site it also doesn't mentions that the smallest SD card that you can use is 4 GB, anything under that will generate a CRC error when trying to flash the image onto the SD card.
If you want to write your own apps for it (I assume that's why you have downloaded the preview, you'll need Visual Studio 2015)
Mostly a proof of concept that it runs on an ARM device, good thing most basic services are already running.
Have you seen any startup app around for testing?
There are a bunch of samples available on the MS-IOT Github:
https://github.com/ms-iot/samples
I Just bought the Raspberry PI 2 today and been messing on with it, coding seems fairly simple through visual studio, not too distant from Arduino. (im not much of a code expert though).
Im going to eventually use my Rpi to control my partially built Arduino Drone.
So, I know the Raspberry Pi 2 can run Windows 10, but anyone know if the UDOO can run it?
I haven't tried this yet, but you should be able to use USB passthrough to get access to card reader from a Windows 10 VM (at least in Virtualbox)
Seems like a fair bit of hassle (ADK is huge), when one could easily install Windows 10 to a separate partition or VHD(x) for the same amount of work. I guess if you had some wonky legacy BIOS setup that can't handle chainloading, this would be the only way to go.
For those with recent BIOS and UEFI devices, (and running W7 or later), this will allow you to play with W10 safely
Become a Microsoft Insider
Download the most recent ISO
Mount the ISO (8/8.1 can handle this natively) or burn it to a disk/thumb drive
Open Disk Management as Administrator
Create your VHD or VHDX, and mount it.
Grab the http://www.rmprepusb.com/tutorials/getwaiktools/GetWaikTools.7z?attredirects=0&d=1
Select the appropriate imagex file for your OS, and drop it into C:\
Run in an admin command prompt "imagex /apply E:\sources\install.wim V:" NOTE: Replace E:\ with your mounted ISO's drive letter, and V:\ with your VHD or VHDX's
Run "bcdboot V:\Windows" again, replace V:\ as neccessary.
For just a bit more effort, you can have full access to Windows 10 on your desktop, DirectX12, Cortana, and W10's faster boot speeds, with no overhead from a VM, or risk damaging a partition. Get tired of it? Delete the VHD. That's it.
I tried to follow your directions exactly but imagex doesn't seem to work, it just shows me all of the parameters. Could you offer any suggestions?
---------- Post added at 05:54 PM ---------- Previous post was at 05:46 PM ----------
Snaipersky;60701419
[* said:
Run in an admin command prompt "imagex /apply E:\sources\install.wim V:" NOTE: Replace E:\ with your mounted ISO's drive letter, and V:\ with your VHD or VHDX's
[/LIST]
.
Click to expand...
Click to collapse
I added the number 1 after install.wim and it started working. Is that correct? I will report later if it works.
Snaipersky said:
Seems like a fair bit of hassle (ADK is huge), when one could easily install Windows 10 to a separate partition or VHD(x) for the same amount of work. I guess if you had some wonky legacy BIOS setup that can't handle chainloading, this would be the only way to go.
For those with recent BIOS and UEFI devices, (and running W7 or later), this will allow you to play with W10 safely
Become a Microsoft Insider
Download the most recent ISO
Mount the ISO (8/8.1 can handle this natively) or burn it to a disk/thumb drive
Open Disk Management as Administrator
Create your VHD or VHDX, and mount it.
Grab the http://www.rmprepusb.com/tutorials/getwaiktools/GetWaikTools.7z?attredirects=0&d=1
Select the appropriate imagex file for your OS, and drop it into C:\
Run in an admin command prompt "imagex /apply E:\sources\install.wim V:" NOTE: Replace E:\ with your mounted ISO's drive letter, and V:\ with your VHD or VHDX's
Run "bcdboot V:\Windows" again, replace V:\ as neccessary.
For just a bit more effort, you can have full access to Windows 10 on your desktop, DirectX12, Cortana, and W10's faster boot speeds, with no overhead from a VM, or risk damaging a partition. Get tired of it? Delete the VHD. That's it.
Click to expand...
Click to collapse
Following these directions, can one still flash windows 10 for use on the rpi2?
Nice Idea..
Will Try this
Snaipersky said:
Seems like a fair bit of hassle (ADK is huge), when one could easily install Windows 10 to a separate partition or VHD(x) for the same amount of work. I guess if you had some wonky legacy BIOS setup that can't handle chainloading, this would be the only way to go.
For those with recent BIOS and UEFI devices, (and running W7 or later), this will allow you to play with W10 safely
Become a Microsoft Insider
Download the most recent ISO
Mount the ISO (8/8.1 can handle this natively) or burn it to a disk/thumb drive
Open Disk Management as Administrator
Create your VHD or VHDX, and mount it.
Grab the
Select the appropriate imagex file for your OS, and drop it into C:\
Run in an admin command prompt "imagex /apply E:\sources\install.wim V:" NOTE: Replace E:\ with your mounted ISO's drive letter, and V:\ with your VHD or VHDX's
Run "bcdboot V:\Windows" again, replace V:\ as neccessary.
For just a bit more effort, you can have full access to Windows 10 on your desktop, DirectX12, Cortana, and W10's faster boot speeds, with no overhead from a VM, or risk damaging a partition. Get tired of it? Delete the VHD. That's it.
Click to expand...
Click to collapse
You can choose which parts to install when installing ADK (in this case Deployement Tools which is only ~50 MB), so it will only download a minimal amount of data. I chose to do it this way as I run my Win 10 VM on ESXi and all the USB ports are disabled for security reasons.
Are those of us with a B+, I think it was called left out? I have one collecting dust that I would like to do something like this with.
help ASAP
viktorgino said:
Hi guys!
As some of you might have seen it already: Microsoft has released an Insider Preview to the Raspberry PI 2.
Here are the instructions on how put the image on an SD card:
Source: http://ms-iot.github.io/content/win10/SetupRPI.htm
This is all good and fine, but most of us don't have a physical computer running Windows 10, so as the site mentions VMs don't have access to physical drives or the card reader, so you can't format and partition a physical disk (you can virtualize it and install it onto the virtual drive, create similar partitions on the physical drive and copy the contents of the virtual drive onto it, and copy the BCD of the virtual hard drive, but that's not 7what we want to do). To be able to flash the Windows Core image onto the SD card we need the latest version of a tool called dism.exe. The latest version of this tool is included with Windows 10 (that's why this manual says that you need Win 10 to do it), but it's also available as part of the Windows Assessment and Deployment Kit and luckliy enough Microsoft has made it available for everyone, so we don't need to scrap it with its dependant DLLs from Win 10.
To be able to flash the image from a computer that's running Windows 7 or higher (I haven't tried from anything below it) we need to first download and install Windows Assessment and Deployment Kit (ADK) RC for Windows 10.
Download page: https://msdn.microsoft.com/en-gb/windows/hardware/dn913721.aspx
Direct download: http://go.microsoft.com/fwlink/p/?LinkId=526740
When installing just install it normally, on the step "Select the features you want to change" tick only the box that says "Deployment Tools" and click Install
After the install open a CMD window as an Administrator (you have to type cmd to the start menu search and right click on the cmd.exe and click on run as administrator)
In CMD navigate to:
Code:
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\x86\DISM
And follow the same steps as in the instructions on the MS website. (get the disk number, and flash it with dism.exe).
Code:
dism.exe /Apply-Image /ImageFile:"C:\Image\File\Location\flash.ffu" /ApplyDrive:\\.\PhysicalDriveN /SkipPlatformCheck
(Don't forget to change C:\Image\File\Location to the location where you extracted the file from the downloaded ZIP file, also change the number of the physical drive)
On the MS site it also doesn't mentions that the smallest SD card that you can use is 4 GB, anything under that will generate a CRC error when trying to flash the image onto the SD card.
If you want to write your own apps for it (I assume that's why you have downloaded the preview, you'll need Visual Studio 2015)
Click to expand...
Click to collapse
was following the method no. 1 and this was happening
"C:\Users\adi\Desktop>/ApplyDrive:\\.\PhysicalDrive1
The filename, directory name, or volume label syntax is incorrect."
what to dousing windows 10 ( still updating )
I will this as soon as possible
girron said:
Following these directions, can one still flash windows 10 for use on the rpi2?
Click to expand...
Click to collapse
No clue, haven't bothered with IOT. I'd recommend a sandboxed install of VS2015CE and building an image that way.
viktorgino said:
You can choose which parts to install when installing ADK (in this case Deployement Tools which is only ~50 MB), so it will only download a minimal amount of data. I chose to do it this way as I run my Win 10 VM on ESXi and all the USB ports are disabled for security reasons.
Click to expand...
Click to collapse
My problem is the ADK .iso is about as big as the W10 .iso. For those with poor connections, that could take quite a while. Why do both, when the imagex method is faster?
Snaipersky said:
My problem is the ADK .iso is about as big as the W10 .iso. For those with poor connections, that could take quite a while. Why do both, when the imagex method is faster?
Click to expand...
Click to collapse
For me ADK insalled from the Internet, the insall file that I downloaded was a 1.5 MB file.
I completely agree with @viktorgino
Related
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!
HOW to install a distribution of GNU/Linux and configure the necessary tools for the development of ROMs
Autores: TugaPower aka danieldmm e porfirio
Firstly, it is important to say that GNU/Linux is open source software / free, robust, reliable, free and easy installation for any user, even if you have few computer skills.
There are dozens of distributions of GNU/Linux, all available free at: http://distrowatch.com/, so choose that of your choice and according to the hardware capabilities of the machine will be installed where the distribution chosen by you.
The choice of authors this "HOWTO" is based on the distribution of GNU/Linux, Ubuntu 11.10, with the XFCE desktop environment and also the GNOME desktop environment. This is abolished by default the manager's main Gnome desktop environment and in its place put XFCE, to perform the daily tasks of work, which is very lightweight and fast. Or if they want to be more direct, Xubuntu and will soon install from scratch, which will get the same results. Personally, I'm a fan of this graphical environment (XFCE), attending to its lightness, speed, customization, etc..
What will be explained in this HOWTO:
1. Install Ubuntu or any other distribution, such as: Xubuntu, manager native XFCE desktop environment, Kubuntu, manager native KDE graphical environment; Lubuntu, manager native LXDE graphical environment, which uses less hardware resources on the machine all present in this work. Basically, we are always talking about Ubuntu, what changes is only the GUI (Graphic User Interface), where the user goes to work.
2. The process of installation and basic configuration for any of these variants, it is always the same.
3. Do not expect to find in this work, the whole process complete installation and configuration. Only the main roads and where possible, with visual aids. However there are situations so redundant, that does not need that same help. Not the purposes of this HOWTO, other possible configurations, eg setup SAMBA, APACHE, a home FTP server, desktop, etc..
4. Let's begin as follows:
4.1 Installing Ubuntu on dual boot with WIndows 7 via USB Universal Installer;
4.2 From the field 16 is a normal installation via live DVD of Ubuntu (Xubuntu, Kubuntu, Edubuntu, Lubuntu).
4.3 Installing and configuring the basic tools for the development of ROMs for the Android operating system (smartphones) on GNU/Linux.
4.4 Some illustrative examples of these tools in place to obtain "cooked," ready to use for users.
GETTING STARTED
1. Installing Ubuntu on dual boot with WIndows 7 via USB Universal Installer.
1.1 To start this process, you must be made to download an image of the Ubuntu operating system for the machine architecture, or x86 (for CPU 36 bit) or x64 (for 64-bit CPUs).
1.1.1 However, this day, there is some controversy on this subject. Some say that if the machine has 4GB of RAM or more, we always use the 64 bit version, even if the CPU is x86 and also say that if the machine has less than 4GB of RAM, we use the 32 bit version regardless of the CPU is x36 or x64.
NOTE: Rarely, modern computers, whether desktops, laptops, at least have at least 4GB of RAM standard. However, do not relinquish that each CPU (x86 or x64), must have the OS corresponding to your architecture. Therefore it is up to each one choose the best option.
2. ISO Images
2.1 Ubuntu 02.01 11.10 (32bit)
2.2 Ubuntu 02.02 11.10 (64bit)
3.Universal USB Installer
3.1 Now we do download the appropriate version of the distribution, we will have to download the USB Installer: www.pendrivelinux.com/downloads/Universal-USB-Installer/
But what is the purpose of this installation process?
3.2 Firstly, we can be a machine, you have not installed a drive read / write CD / DVD.
3.3 Secondly, avoid using a CD or DVD drive for installation.
4. Run the USB Installer, as Administrator of the OS and this not to happen errors during the copy of the OS to the thumb drive. This procedure is performed as follows:
- Click on the icon of the program with the button on the right mouse button and select Run as Administrator option.
5. After installing the USB Installer, run the program and click on I Agree.
{
"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"
}
6. Now we set the distribution of GNU/Linux, we will be using. I choose Ubuntu 11.10.
7. Now calm down! I hope you remember where it was saved the iso image of Ubuntu! Only then will the USB Installer will be able to recognize and perform the installation on the pen drive. Will normally be in downloads.
8. Insert the flash drive and expect it to be recognized by Windows. In this case explanation, their location is in F.
9. At this point, we select the Format F: Drive to FAT32.
NOTE: If you wish, can create a little more memory to the pen, in case it is likely to change. This is an optional. If your interest, as it is put in the picture.
Now we have everything configured properly, we will click Creat.
10. At this point you will get a WARNING message. All contents of pen drive will be erased. Click YES and continue.
11. Now it is time for a coffee, etc., etc. and wait for the installation process to complete. After this step, we will be ready for installation on the computer distribution.
11.1 While the above task does not end, we can and must perform other actions, such as creating a partition for the Ubuntu operating system.
11.2 Let's Start Menu;
11.3 Clicking the right-click Computer and then Manage;
11.4 Now on the left menu, click Disk Manager;
Arrived here, the C partition, let's click and select Shrink Volume.
12. Let us wait quietly, and very soon we will be faced with the option to reduce the partition chosen. For a minimal installation of Ubuntu, will require approximately 10 GB. However, if we want to later install the updates, music, videos, etc. ... recommend 25 GB. To be closer to the 25GB, 26GB put!
13. The next step is to reduce and click new partition will be marked in black. We will then activate this partition:
13.1 Click on the partition, with the right mouse button and select New Simple Volume.
13.2 Click Next> Next> and choose a letter to the new drive (eg U).
13.3 Now let's change the Volume Label. Put Ubuntu.
13.4 Next Run. We have created the partition and active.
NOTE: Wait now that Universal USB Installer program in the following screen appears indicating that the installation was completed and then click Close.
14. Restart the computer.
15. Immediately press F12 and select USB stick and then press ENTER.
15.1 will appear something like this:
Calm ..... very quiet .... Choose the option Install Ubuntu on a Hard Disk.
16. Now it is like to install via DVD, which I dispense to comment on "How to install Ubuntu 11.10 per DVD." See 4.2 The field from the field 16 is a normal installation of Ubuntu live via DVD.
16.1 After appearing Choose Setup Language, Portuguese choose and click Next. (You pick the language that you anderstand)
Preferably, you must have a fast Internet connection, so that the OS be upgraded soon. In the situation of not being currently available internet connection, do not put the "seen". No problem your installation will proceed smoothly. You can do it later.
17. Then will click on: One more thing, in order to choose the partition for installation.
18. CAUTION ... CAUTION!
18.1 In this field, we have all the possible CARE! The Windows partition can die!
18.2 Should be selected before the partition created in Windows (which is named Ubuntu), and then click Modify. After selecting the partition that was created on Windows (Ubuntu). In the new partition size, and put 21,000 Mount Point select /. After running OK.
The aspect should be this:
19. Now let us take the remaining space in the example 1490MB. Click Modify, and followed by the option Use as we choose and swap area and click OK.
It should be something like this:
20. Next, click Install Now and wait ......
21. Choose the location of the user:
22. Now the installation of the default keyboard ....
23. Enter personal information and click Continue.
24. Installation completed. Reboot the PC.
25. And Behold .....
Choose from the boot menu option Ubuntu .... There is also the option Windows ... Choose!
26. I chose .... Ubuntu with the Gnome GUI!
7. There is a method, also very reliable, to expedite this process, but directed to Mint distribution, which can be obtained here: community.linuxmint.com/tutorial/view/744
NOTE: TugaPower friend and colleague, will use the Mint 12 in the process of compiling ROMs. (In this case S2 i9100 ROM 4.0.3 ICS)
Version used: Linux Mint x64 12 vKDE
Download Links: http://blog.linuxmint.com/?p=1927
4.3 Installing and configuring the basic tools for the development of ROMs for the Android operating system (smartphones) on GNU / Linux.
4.3.1 Installing the JAVA
Open the Synaptic package manager and install the openjdk-7-jdk and mark their dependencies:
Approval for the changes made:
Download the required files:
Installation of the necessary files and OpenJDK 7:
Now we have to install JAVA on the machine fully realized, we will proceed to their inspection.
To do so open the command line terminal to write the following command: java-version
4.3.2 Check if the package is installed 7zip more specifically p7zip-full, if not select for installation:
Once this is done we can then proceed with the installation of the Kitchen.
4.4 Installing the Kitchen
4.4.1 Initial Procedures
All information to carry out this section were collected on: forum.xda-developers.com/showthread.php?p=5626292#post5626292
Therefore, our choice falls on dsixda Android's Kitchen (Support Several devices)
(The Custom ROM made in this Guide its based to the Galaxy S2 i9100)
Download link of Kitchen: http://github.com/dsixda/Android-Kitchen/archives/master
Informational Page on Kitchen: http://forum.xda-developers.com/showthread.php?p=5626292#post5626292
After these preliminary procedures have been performed, we proceed to next steps.
By default, you will be allocated in the Downloads folder files.
4.4.2 Click on the file up with the right button of mouse and perform the extraction of the file to the Downloads folder:
4.4.3 Change the file name for kitchen (it's easier to work).
4.4.3.1 Move or Copy to folder or Personal Home:
They should stick with a structure like this:
4.5 Perform download the ROM Stock
NOTE: I personally recommend two sites:
http://forum.xda-developers.com/showthread.php?t=1075278
http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-I9100&r=1#regional
Download the ROM to be used in Kitchen, in this case we use the XDA, specifically the XWLP7:
NOTE: The screenshot references XWLP4 because at that time had not XWLP7
4.5.1 Download the kernel corresponding CF-root (This way remains CWM Recovery Busybox and SuperUser GB, if ICS SuperSU depends the kernel used to cook the ROM.
4.5.2 Download the kernels on CF-root: http://forum.xda-developers.com/showthread.php?t=1103399
NOTE: This case will be used the latest available to ICS, the CF-root-SGS2_XX_OXA_LPS-v5.4-CWM5.zip
NOTE: It is already available in the XDA KERNEL CF ROOT XWLP7.
4.5.3 Copy the file from the ROM inside the Kitchen to the folder original_update
4.5.3.1 If the file is in the form *******. Tar.md5 have to remove the. Md5 so that it only ********. Tar
After these steps have been made in all its fullness, then we have all the necessary files to start our cooked
4.5.4 Some illustrative examples of these tools in place to obtain "cooked," ready to use for users.
4.5.4.1 In order to run our furnace we have run the Kitchen in a command line also known as terminal or console, for it will open a command prompt within the folder Kitchen:
In order to execute the Kitchen just run the following command as root sudo. / Menu in the terminal:
6. First thing to do is point 1 or set a folder where we work. In this process the Kitchen will get to select and give the stock ROM original_update previously placed in the folder, simply enter the next screen and then select the ROM list:
Therefore, we select the first option because we only have a ROM in the kitchen, so just to enter a default because it's one
6.1 In the kitchen will then ask if we want to keep the name.
This name stock is organized as follows: WORKING_DATA_HORA, this can be changed to whatever you want, the only thing required is to keep the WORKING_
In this case I press the button to change the name ye WORKING_XWLP7_TugaPower:
To continue then just press Enter.
7. The kitchen will start the process of extracting the file from the ROM to the folder with the name we gave earlier WORKING_ ********
In this process we have to decide if we want to use the CSC (NET configuration and applications) that are included with the Stock ROM or NO.
By default this is set to YES ...
Thus, we can, because the Kitchen gives the following list of apks existing CSC and if we add the folder WORKING_ *****
Remember that in most cases, there is no problem in using the CSC Stock ROM, just advise not to use the apks the CSC because they are essentially propaganda NETWORK, which can be set to follow in the next menu to the Kitchen already well default to not add the apks:
Ready to the next step?
8. After the CSC will appear in the information regarding the boot.img, here we select the letter n because for the effect of Custom ROM do not need!
9. Then will come the question if we want to see information about the ROM.
This option is your choice will; default is Y. I personally put n. Now let's return back to the first screen which means that the necessary files are all ready ....
10. In this field, you may want to check whether there is a need to use option 2 and 3.
10.1 In the case of using the KERNEL Stock are advised to do option 2 and 3.
If the kernel you are going to use is for example the CF ROOT or any other that already have root then there is necessary to make the option 1 and 2.
10.2 In this case I will use the CF KERNEL, we will open the zip file of CF ROOT Kernel, find a file ****.tar, opening the file we find the zImage (KERNEL), selecting the zImage we proceed to the extraction process to the working folder of the Kitchen, in this case to the folder: Working_XWLP7_TugaPower
A new window will appear saying that the file already exists, just select and replace the existing ...
11. We will now switch to the Kitchen 7. Kitchen is a default to NO WIPE ROM, option 7 serves to change this ...
12. In this case I do WIPE version, you just will access option 7 in the next field and put y:
12.1 This procedure will eventually lead back to the main menu of the Kitchen. Now we have to think whether we want a ROM or deodexed ODEXED Stock ...
12.2 If we use a version ODEXED we can switch to the option 99 which will be explained below, because I'll use this version deodexed and before passing the option will be option 0 99: ADVANCED OPTIONS
IMG]http://i.imgur.com/XtfZp.png[/IMG]
13. Here I select option 11 to deodexed ROM:
13.1 Now we need one more aspect to consider: what kind of ROM, if GB or ICS.
In this case as I am using a ROM ICS will change the level of API's Kitchen and they default to GB, so I'll use the v
14. Then I confirm that I change the level of the API key y.
In this case I set the API level to 15 which corresponds ROM will be concerned that I'm using ICS 4.0.3:
14.1. Now set the API, I will proceed to the DEODEX ROM for option b, which is advised, because this way, will deodexed the system / app and system / framework.
15. Will be asked if you want a log deodex, this is your charge, if you put y, a file will be created in the root folder of the Kitchen with Deodex process, this log can be used to screen for possible errors that occur in deodexed; I always use the log file because the design is not great and always give way if there are problems in deodexed.
16. After this step made the Kitchen will carry out the relevant technical Deodexed ROM:
17. Now just wait, if you can go for a coffee or a cigarette because it still takes a bit if they do not get any errors and the process goes well deodexed will be presented the following screen:
18. Pressing the Enter, go to the submenu of Kitchen Advanced Menu.
We will then press 0 to return to the main Kitchen; next step we change the name of the build of the ROM (this information that appears in the menu on the About the Phone.
18.1 For this press the key 8 from the Main Menu of the Kitchen, in which case I will change to XWLP7 Stock by TugaPower:
http://i.imgur.com/I6ZXw.png[IMG]
19. Press Enter, then we will change back to the Main Menu Kitchen, now is the time better, create CWM zip file for flashing the ROM :)
19.1 For this we will then press the Option 99:
[IMG]http://i.imgur.com/eYhj4.png
NOTE: Because you are beginning to learn how to make Custom ROMs recommend the first option which is already the default and that the Kitchen, then just do enter in the respective options that appear to the end:
Until we reach the end of file creation can change the name of it, this is the last question that makes the kitchen:
Done this you can find the ROM inside the OUTPUT folder in the Kitchen ...
You only need to copy to the memory of the phone and make the flash.
Have a good cooked and good flash
ROM that was created in TUTU --->
XWLP7 Stock By TugaPower
a hell lot of screenshots, foolproof guide, really great one for beginner
Thanks.. Must have !!
Thanks fool proof, full of screens and has each and every detail.
:thumbup:
randommmm said:
a hell lot of screenshots, foolproof guide, really great one for beginner
Click to expand...
Click to collapse
aditya_7298 said:
Thanks fool proof, full of screens and has each and every detail.
:thumbup:
Click to expand...
Click to collapse
Thanks guys...
Cheers
wow really Great Guide.....................
[SIZE="+1"]-- Android SDK/ADB tool Tutorial --[/SIZE]
I decided to create this Beginner Friendly tutorial on how to install SDK tool mainly because recent phones such as the i.e. HTC One X / One X+ are requiring many basic usage of adb command line, and lots of members are having difficulities to have basics adb command to work because their SDK tool is not correctly installed. I won't show you how to make usage of it, there is plenty of How-to's for that purpose all around xda and on the Web.
This is all safe to install on your Windows based computer, and if you can not achieve success with this installation, well obviously, you shouldn't play the hacking game with your device. From now on, I or anyone else on the Internet can not be held responsible if something really bad is happening to you because you didn't read and followed any given instructions letters by letters and you ended with a screwed, pricey and valuable paperweight device. That being said, let's get started.
Let's GO!
____________________________________________
[SIZE="+1"]-- Enabling USB debugging mode --[/SIZE]
On your phone simply follow this path : Settings -> Developer options -> Turn the option ON -> under Debugging -> tick USB debugging option Debug mode when USB is connected
That's it, done!
____________________________________________
[SIZE="+1"]-- Java Installation --[/SIZE]
This is a prerequisite to have a flawlessly working SDK tool installation.
Click on the following link to download it on Java's website : Free Java Download
On the next page, do not click on Agree and Start Download, instead click on See all Java downloads.
Which should you choose? If you have a 64-bit Windows OS you MUST install the two versions (both 32-bit and 64-bit), otherwise the 32-bit is sufficient for a 32-bit Windows OS.
Before installing the latest version of Java, it is recommended to uninstall all previous Java's installation. (How to -> Remove Older Versions)
Complete the required installation depending of the type of Windows installation.
You are all done for Java.
-- Screenshots for the visual ones --
{
"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"
}
____________________________________________
[SIZE="+1"]-- SDK Tools Installation --[/SIZE]
First step is to download the SDK Manager, to do so click on this link -> Download the SDK
Next locate on the bottom of your screen the USE AN EXISTING IDE, click on it.
On the Get the Android SDK page, tick the I have read and agree with the above terms and conditions box and click on the Download the SDK Tools for Windows button.
Navigate to your Download folder, and locate a file named like this: installer_r21.1-windows.exe (N.B. The r21.1 version was available when I did this how to, your version could be different.)
Double click on the installer_r21.1-windows.exe file to start the installation. Take good note where the file will be installed, generally the default SDK path is : C:\Users\your_session's_name\AppData\Local\Android\android-sdk.
Now, navigate to the path of the SDK installation folder.
Select all (CTRL + A) in this folder and Copy (CTRL +C) them for the next step.
Now you need to create a new folder at the root of your C:\ drive named : AndroidSDK
Open up the newly created folder and Paste (CTRL + V) the previously copied files.
Stay in this folder and double click on the SDK Manager icon.
The SDK Manager will open a new window, click on Deselect All, then tick the following line in Tools : AndroidSDK Platform-tools
Click on Install 1 Package..., accept the license agreement and click on Install let the manager do it's thing.
Click on Done and close the manager's window.
Congrats! You have created successfully your SDK tool!
Wait! Let's clean your computer a bit....
Go back to the previous folder, the one located in this path : C:\Users\your_session's_name\AppData\Local\Android\android-sdk
Click on the Uninstaller, we don't need this one anymore. Don't worry the other AndroidSDK folder won't be deleted.
Voilà! You are done with this part.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Creating of script file for a fast access --[/SIZE]
Locate the Platform-tools sub-folder in the AndroidSDK folder.
Right click in a empty space of the folder and select in the contextual menu New -> Text Document
Open this new Text Document and Copy/Paste this : c:\windows\system32\cmd.exe
Save this file as : Start SDK.bat
Acknowledge the : If you change file extension... warning.
Right click your new created Start SDK and send a shortcut on your Desktop.
Done! If you try to double click on your Start SDK shortcut, a command window should open with something like these lines :
Code:
C:\AndroidSDK\platform-tools>c:\windows\system32\cmd.exe
Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\AndroidSDK\platform-tools>
Success!
____________________________________________
[SIZE="+1"]-- Installing HTC's Drivers --[/SIZE]
This one is very easy, simply download and run the installer and let Windows do the rest. Drivers compatbile 32-bit or 64-bit
Download the Self-install HTCDriver_4.0.1.001.exe/
Make sure your phone is not plugged on your computer via the USB cable.
Simply run the installer of the driver you've just downloaded.
Once the installation is completed, simply plug your phone via your USB cable and Windows "wizard manager" will now detect your phone.
If it doesn't work, unplug your phone and reboot your computer. Then plug back your phone once rebooted.
Done!
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Let's try all this! --[/SIZE]
With your phone plugged on your USB cable...
From your Desktop, double click on your Start SDK shortcut.
In the command window, at the command line : C:\AndroidSDK\platform-tools> type this -> adb devices (Enter)
The serial number of your phone should appear in the command window. If it is the case, then try this again : C:\AndroidSDK\platform-tools> type this -> adb reboot (Enter)
Your phone will now Reboot
If all this worked, you have a successful SDK Tools installation!
-- Screenshots for the visual ones --
This is it, I hope this tutorial was helpful, if you have some sort of problems let me know, I will try to help you at the best of my knowledge. Have fun hacking your Android!!
Nice guide
Very concise
Lucky Thirteen said:
[SIZE="+1"]-- Android SDK/ADB tool Tutorial --[/SIZE]
I decided to create this Beginner Friendly tutorial on how to install SDK tool mainly because recent phones such as the i.e. HTC One X / One X+ are requiring many basic usage of adb command line, and lots of members are having difficulities to have basics adb command to work because their SDK tool is not correctly installed. I won't show you how to make usage of it, there is plenty of How-to's for that purpose all around xda and on the Web.
This is all safe to install on your Windows based computer, and if you can not achieve success with this installation, well obviously, you shouldn't play the hacking game with your device. From now on, I or anyone else on the Internet can not be held responsible if something really bad is happening to you because you didn't read and followed any given instructions letters by letters and you ended with a screwed, pricey and valuable paperweight device. That being said, let's get started.
Let's GO!
____________________________________________
[SIZE="+1"]-- Enabling USB debugging mode --[/SIZE]
On your phone simply follow this path : Settings -> Developer options -> Turn the option ON -> under Debugging -> tick USB debugging option Debug mode when USB is connected
That's it, done!
____________________________________________
[SIZE="+1"]-- Java Installation --[/SIZE]
This is a prerequisite to have a flawlessly working SDK tool installation.
Click on the following link to download it on Java's website : Free Java Download
On the next page, do not click on Agree and Start Download, instead click on See all Java downloads.
Which should you choose? If you have a 64-bit Windows OS you MUST install the two versions (both 32-bit and 64-bit), otherwise the 32-bit is sufficient for a 32-bit Windows OS.
Before installing the latest version of Java, it is recommended to uninstall all previous Java's installation. (How to -> Remove Older Versions)
Complete the required installation depending of the type of Windows installation.
You are all done for Java.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- SDK Tools Installation --[/SIZE]
First step is to download the SDK Manager, to do so click on this link -> Download the SDK
Next locate on the bottom of your screen the USE AN EXISTING IDE, click on it.
On the Get the Android SDK page, tick the I have read and agree with the above terms and conditions box and click on the Download the SDK Tools for Windows button.
Navigate to your Download folder, and locate a file named like this: installer_r21.1-windows.exe (N.B. The r21.1 version was available when I did this how to, your version could be different.)
Double click on the installer_r21.1-windows.exe file to start the installation. Take good note where the file will be installed, generally the default SDK path is : C:\Users\your_session's_name\AppData\Local\Android\android-sdk.
Now, navigate to the path of the SDK installation folder.
Select all (CTRL + A) in this folder and Copy (CTRL +C) them for the next step.
Now you need to create a new folder at the root of your C:\ drive named : AndroidSDK
Open up the newly created folder and Paste (CTRL + V) the previously copied files.
Stay in this folder and double click on the SDK Manager icon.
The SDK Manager will open a new window, click on Deselect All, then tick the following line in Tools : AndroidSDK Platform-tools
Click on Install 1 Package..., accept the license agreement and click on Install let the manager do it's thing.
Click on Done and close the manager's window.
Congrats! You have created successfully your SDK tool!
Wait! Let's clean your computer a bit....
Go back to the previous folder, the one located in this path : C:\Users\your_session's_name\AppData\Local\Android\android-sdk
Click on the Uninstaller, we don't need this one anymore. Don't worry the other AndroidSDK folder won't be deleted.
Voilà! You are done with this part.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Creating of script file for a fast access --[/SIZE]
Locate the Platform-tools sub-folder in the AndroidSDK folder.
Right click in a empty space of the folder and select in the contextual menu New -> Text Document
Open this new Text Document and Copy/Paste this : c:\windows\system32\cmd.exe
Save this file as : Start SDK.bat
Acknowledge the : If you change file extension... warning.
Right click your new created Start SDK and send a shortcut on your Desktop.
Done! If you try to double click on your Start SDK shortcut, a command window should open with something like these lines :
Code:
C:\AndroidSDK\platform-tools>c:\windows\system32\cmd.exe
Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\AndroidSDK\platform-tools>
Success!
____________________________________________
[SIZE="+1"]-- Installing HTC's Drivers --[/SIZE]
This one is very easy, simply download and run the installer and let Windows do the rest. Drivers compatbile 32-bit or 64-bit
Download the Self-install HTCDriver_4.0.1.001.exe/
Make sure your phone is not plugged on your computer via the USB cable.
Simply run the installer of the driver you've just downloaded.
Once the installation is completed, simply plug your phone via your USB cable and Windows "wizard manager" will now detect your phone.
If it doesn't work, unplug your phone and reboot your computer. Then plug back your phone once rebooted.
Done!
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Let's try all this! --[/SIZE]
With your phone plugged on your USB cable...
From your Desktop, double click on your Start SDK shortcut.
In the command window, at the command line : C:\AndroidSDK\platform-tools> type this -> adb devices (Enter)
The serial number of your phone should appear in the command window. If it is the case, then try this again : C:\AndroidSDK\platform-tools> type this -> adb reboot (Enter)
Your phone will now Reboot
If all this worked, you have a successful SDK Tools installation!
-- Screenshots for the visual ones --
This is it, I hope this tutorial was helpful, if you have some sort of problems let me know, I will try to help you at the best of my knowledge. Have fun hacking your Android!!
Click to expand...
Click to collapse
This works fine on windows 8 I needed that for my HTC Desire C and I managed to do with this! Thank you!
I didn't know about that shortcut. Very nice.
:good:
Why isn't that driver link in a stickied thread?? Solved my connectivity issues.
Rooting My Htc Desire C
I need to know How to root my HTC DESIRE C ,like this beginner friendly method.Many websites are showing different ways to do it and some ways didn't work for some people iam afraid my phone becoms a brick.so please help xda developers.
And this helped a lot....Thank You So Much
I have the HTC One for AT&T, I have the drivers installed and everything works fine when the phone is powered on I can transfer stuff back and forth easily. Although as soon as I boot my into the bootloader and select the fastboot and fastboot usb and when I run my adb devices in the CMD it comes up blank under the devices connected with several cables in all 4 usb ports. What is wrong? Help please
this helped me thanks. I followed everything to the tee. I only had a problem with changing the .txt to.bat extension however in notepad choosing save as and adding ".bat" in quotation marks allowed me to change the file extension
What an awesome tutorial! Thank you very much flawless!!! :good:
can you delete the android-sdk folder once everything is finished?
please ppl can u upload sdk for me ? i can not do it , iran is banned from google . just one developer man
here is my requested thread
http://forum.xda-developers.com/and...k-23-0-5-android-l-api-21-api-20-api-t2915318
{
"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"
}
In addition to GNU/[email protected] topic, this one is a separate for Ubuntu users. Read below if you want to have native Ubuntu 13.10 wih Gnome/LDXE/XFCE at your Galaxy Note 10.1 device (2012 models only).
Screenshots:
Please be aware, that stuff I share with you is experimental, it does not work 100% correctly and there are some lags and bugs.
Some technical details:
The approach is based on using custom recovery (e.g. custom kernel and initrd image) which boots into Linux. All Linux files are stored at data partition (it is mmcblk0p12 when using standard firmware, which also is internal sdcard) in a separate folder. Initrd script mounts data partition and looks for the special file /media/rootdev - this file contains the path to the Linux root folder. Script sets the Linux root device to be this folder specified and invokes /sbin/init. You see Linux booting - Ubuntu in our case.
However I've also prepared the second folder with native recovery files. E.g. if you change rootdev content to point to recovery files folder, you will boot into recovery. Generally, you can boot any other recovery or Linux distro using this approach. And hosting it at sdcard in a folder much easier than re-partitioning tablet or using loop-device in a file. Free space for your Linux depends only of free space you have at data partition.
Prerequisites:
Rooted GT-N80xx device
Busybox tools installed
Desktop computer with ADB tools
Custom recovery image (with or without menu), native recovery, Ubuntu image files downloaded (see downloads section)
Understanding of what are you doing
Downloads:
Custom recovery image which boots to Linux (no menu) - recovery_nomenu.img
Custom recovery image which boots to Linux (with menu) - recovery_menu.img
Native recovery files archive - recovery.tar.gz
Ubuntu 13.10 files archive - ubuntu.tar.gz
Steps:
Connect your device to the desktop computer with USB cable. Make sure your device is visible when you run "adb devices"
Rename downloaded recovery image to "recovery.img"
Upload downloaded files to the internal memory:
Code:
adb push recovery.img /sdcard/
adb push recovery.tar.gz /sdcard/
adb push ubuntu.tar.gz /sdcard/
Now you need to get into device, so run "adb shell", then type the next commands (the lines beginning from # are the comments, you don't need to type it ):
Code:
# 4. become root user
su -
# 5. go to the internal sdcard real path, where you uploaded files
cd /data/media
# 6. write custom recovery to the special partition, by default it is mmcblk0p6
dd if=./recovery.img of=/dev/block/mmcblk0p6
# 7. unpack native recovery files, the "recovery" folder will be created
gunzip -c ./recovery.tar.gz | tar -x
# 8. unpack Ubuntu files, the "ubuntu" folder will be created
gunzip -c ./ubuntu.tar.gz | tar -x
# 9.1. Now, if you downloaded custom recovery without menu - set what to
# boot, in our case it is Ubuntu, and go to step #10
echo "/media/ubuntu" > ./rootdev
# 9.2. OR, if you downloaded custom recovery with menu - add menu entries
echo "Ubuntu=/media/ubuntu" > ./rootdev
echo "Recovery=/media/recovery" >> ./rootdev
echo "Reboot=reboot" >> ./rootdev
# 10. remove files that we don't need anymore and quit
rm ./recovery.img ./recovery.tar.gz ./ubuntu.tar.gz
exit
exit
Now you should reboot your device to recovery mode. If you did all correctly (and I did not miss anything in steps) you should see Linux booting (and menu if you are using custom recovery with menu).
Please use your S-Pen as mouse, button on the pen works as "right-click".
The password for root user and android user is "q" (small q-letter without quotes).
Notes:
The Ubuntu image I shared with you is v13.10 and Gnome-based (Unity does not work due to Compiz issues).
Regular Gnome session works at most, but have some bugs, due to 3D acceleration support issues. For example, window dragging does not work and the session hangs (sorry, I have not found why, please fix if you can and share your workaround with us).
Gnome Fallback works better, but might not start properly from the first time. E.g. you should boot to regular Gnome session, then log out and login to Fallback (also have no idea why it works like this, please help if have experience).
Due to the issues with Gnome, I've also installed LXDE and XFCE, so you could try login to it. However I would recommend booting to regular Gnome session at least to configure your Wi-Fi connection.
Internal and external sdcards are mounted to /mnt/intSdCard and /mnt/extSdCard paths.
Important notes:
The Ubuntu image has ADB installed. E.g. if something goes wrong at the screen and you are not able to manage your device, connect it to the desktop with USB cable, run "adb shell", then "sudo su -" and you become root user. To restart graphical session you need to invoke "service gdm restart" command.
If you are using custom recovery without menu and want to boot native recovery instead of Ubuntu, edit "rootdev" file at internal sdcard to contain "/media/recovery" path (without quotes). You can do that via ADB shell, using any Android text editor, or directly from Linux.
The last thing to know:
Not all is working from Ubuntu. Currently there is no 3G support and some other things. All of them are discussed in the parent thread
Please let me know if I have missed something and my steps do not work for you. Any other feedback will also be appreciated
downloading right now... just one question! can i do all this with terminal emulator on android?
edit: forget about that last question, tried from terminal emulator and it worked.
X-Stranger said:
In addition to GNU/[email protected] topic, this one is a separate for Ubuntu users. Read below if you want to have native Ubuntu 13.10 wih Gnome/LDXE/XFCE at your Galaxy Note 10.1 device (2012 models only).
Screenshots:
View attachment 2432486 View attachment 2432487 View attachment 2432488
Please be aware, that stuff I share with you is experimental, it does not work 100% correctly and there are some lags and bugs.
Some technical details:
The approach is based on using custom recovery (e.g. custom kernel and initrd image) which boots into Linux. All Linux files are stored at data partition (it is mmcblk0p12 when using standard firmware, which also is internal sdcard) in a separate folder. Initrd script mounts data partition and looks for the special file /media/rootdev - this file contains the path to the Linux root folder. Script sets the Linux root device to be this folder specified and invokes /sbin/init. You see Linux booting - Ubuntu in our case.
However I've also prepared the second folder with native recovery files. E.g. if you change rootdev content to point to recovery files folder, you will boot into recovery. Generally, you can boot any other recovery or Linux distro using this approach. And hosting it at sdcard in a folder much easier than re-partitioning tablet or using loop-device in a file. Free space for your Linux depends only of free space you have at data partition.
Prerequisites:
Rooted GT-N80xx device
Busybox tools installed
Desktop computer with ADB tools
3 files downloaded (see downloads section)
Understanding of what are you doing
Downloads:
Custom recovery image which boots to Linux - recovery.img
Native recovery files archive - recovery.tar.gz
Ubuntu 13.10 files archive - ubuntu.tar.gz
Steps:
Connect your device to the desktop computer with USB cable. Make sure your device is visible when you run "adb devices"
Upload downloaded files to the internal memory:
Code:
adb push recovery.img /sdcard/
adb push recovery.tar.gz /sdcard/
adb push ubuntu.tar.gz /sdcard/
Now you need to get into device, so run "adb shell", then type the next commands (the lines beginning from # are the comments, you don't need to type it ):
Code:
# 4. become root user
su -
# 5. go to the internal sdcard real path, where you uploaded files
cd /data/media
# 6. write custom recovery to the special partition, by default it is mmcblk0p6
dd if=./recovery.img of=/dev/block/mmcblk0p6
# 7. unpack native recovery files, the "recovery" folder will be created
gunzip -c ./recovery.tar.gz | tar -x
# 8. unpack Ubuntu files, the "ubuntu" folder will be created
gunzip -c ./ubuntu.tar.gz | tar -x
# 9. set what to boot, we want Ubuntu
echo "/media/ubuntu" > ./rootdev
# 10. remove files that we don't need anymore and quit
rm ./recovery.img ./recovery.tar.gz ./ubuntu.tar.gz
exit
exit
Now you should reboot your device to recovery mode. If you did all correctly (and I did not miss anything in steps) you should see Linux booting.
Please use your S-Pen as mouse, button on the pen works as "right-click".
The password for root user and android user is "q" (small q-letter without quotes).
Notes:
The Ubuntu image I shared with you is v13.10 and Gnome-based (Unity does not work due to Compiz issues).
Regular Gnome session works at most, but have some bugs, due to 3D acceleration support issues. For example, window dragging does not work and the session hangs (sorry, I have not found why, please fix if you can and share your workaround with us).
Gnome Fallback works better, but might not start properly from the first time. E.g. you should boot to regular Gnome session, then log out and login to Fallback (also have no idea why it works like this, please help if have experience).
Due to the issues with Gnome, I've also installed LXDE and XFCE, so you could try login to it. However I would recommend booting to regular Gnome session at least to configure your Wi-Fi connection.
Internal and external sdcards are mounted to /mnt/intSdCard and /mnt/extSdCard paths.
Important notes:
The Ubuntu image has ADB installed. E.g. if something goes wrong at the screen and you are not able to manage your device, connect it to the desktop with USB cable, run "adb shell", then "sudo su -" and you become root user. To restart graphical session you need to invoke "service gdm restart" command.
If you want to boot native recovery instead of Ubuntu, edit "rootdev" file at internal sdcard to contain "/media/recovery" path (without quotes). You can do that via ADB shell, using any Android text editor, or directly from Linux.
The last thing to know:
Not all is working from Ubuntu. Currently there is no 3G support and some other things. All of them are discussed in the parent thread
Please let me know if I have missed something and my steps do not work for you. Any other feedback will also be appreciated
Click to expand...
Click to collapse
Hi! What about the Source Code for your custom recovery and stuff?
Simon94 said:
Hi! What about the Source Code for your custom recovery
Click to expand...
Click to collapse
In ubuntu or debian:
Code:
apt-get install abootimg
abootimg -x recovery-1.img
After this you will have a folder with all the contents of the img. Some of which you can edit the scripts. You can extract the initrd and kernel even further with abootimg-unpack-initrd
i must say this is pretty awesome very few bugs, and xfce works perfect
Can't risk ruining my tablet until after the semester ends but as soon as it does I'll be trying this! Sounds awesome...
THANK YOU, and THANK YOU for returning! Note 10.1 is currently in hands of Samsung for repairs. Hopefully I can have some fun with this once it is back.
Please check drivers here: http://forum.xda-developers.com/showthread.php?p=45340017#post45340017
I think the driver for Mali acceleration may be possible (you are using Hardkernel from ODROID, correct?).
Simon94 said:
Hi! What about the Source Code for your custom recovery and stuff?
Click to expand...
Click to collapse
My latest kernel sources (arch branch) and toolchain (in the toolchain branch): https://github.com/X-Stranger/N8000
Kernel sources, patched video driver and other stuff: https://code.google.com/p/opensgn/
Recovery can be unpacked/fixed/repacked using abootimg tools as mentioned
dwegiel said:
THANK YOU, and THANK YOU for returning!
Click to expand...
Click to collapse
Don't forget to press "thanks" button (or even "donate to me" )
dwegiel said:
Note 10.1 is currently in hands of Samsung for repairs. Hopefully I can have some fun with this once it is back.
Please check drivers here: http://forum.xda-developers.com/showthread.php?p=45340017#post45340017
I think the driver for Mali acceleration may be possible (you are using Hardkernel from ODROID, correct?).
Click to expand...
Click to collapse
Yes, I'm using Mali acceleration in my Ubuntu image. It is still not 100% working though, that is what I'm talking about, when describe Gnome issues. If you can fix that - please do and share your experience, I'll update the image then.
I would also like someone to help with migration to the latest kernel, which has support for our Exynos board. Exception13 was going to do that, but looks like he is very busy person (and I can understand that).
Have composed a small menu program and added it to custom initrd. Now it is possible to select what to boot (see screenshot), e.g. don't need to edit rootdev file every time, only when adding new menu entry.
Updated first post of this topic with instructions how to get this.
X-Stranger said:
Have composed a small menu program and added it to custom initrd. Now it is possible to select what to boot (see screenshot), e.g. don't need to edit rootdev file every time, only when adding new menu entry.
View attachment 2436305
Updated first post of this topic with instructions how to get this.
Click to expand...
Click to collapse
This is fantastic news for Note 10 owners out-there. I never read about another tablet with a bootmenu to native linux and recovery, so Y'all are lucky to have X-Stranger on the case =] because also now the Ubuntu flavor is on the go.
For all you Note 8 owners out-there I am trying to port the images over with as few changes as possible but my skill level at this type of task is 1/10 that of X-Stranger, so bare with me! (Or you can try and get a package together faster than me =] ).
My process so far is to use the initrd from X-Stranger's recovery_menu.img, and use a zImage from CWM, TWRP, and stock. All that they do is loop back to the note's defalt splash screen. I used X-Stranger's entire recovery_menu.img too and it boots to just a black screen on the Note 8. So my WIP conclusion thus far is that I or someone (volunteer required) has to compile a kernel with some patches just like X-Stranger did on page 3 of the previous thread.
Enjoy Ubuntu all the Note 10 owners....
at the first boot it says "failed to mount extsdcard, press S to skip ....." of course there's nothing to press anything on. I guess it's because my 64gb microsd is ntfs formated. Should I convert it to exfat from windows, should I attach a usb keyboard with OTG and press s?
Sent from my GT-N8013 using Tapatalk
Anyone tried this on the n8020?
I cant get it to work.
Nothing happens
Edit: Wrong recovery partition...for me it is mmcblk0p9
I'm having the same the same issue as panoz, error mounting /mnt/extSdCard. Also tried removing it before boot, but it complains that there's nothing to mount. I only have a Bluetooth keyboard, no otg, so is my only option to format the card?
Btw thanks X-Stranger and all the devs involved for all your work!!
panoz said:
at the first boot it says "failed to mount extsdcard, press S to skip ....." of course there's nothing to press anything on. I guess it's because my 64gb microsd is ntfs formated. Should I convert it to exfat from windows, should I attach a usb keyboard with OTG and press s?
Sent from my GT-N8013 using Tapatalk
Click to expand...
Click to collapse
Yes, it is expecting FAT to be mounted. As a workaround you can disable ext sdcard mounting. Just go to ubuntu image directory, etc folder, find fstab file and comment out the line related to external sdcard (put # symbol in the beginning).
emptynick said:
Anyone tried this on the n8020?
I cant get it to work.
Nothing happens
Edit: Wrong recovery partition...for me it is mmcblk0p9
Click to expand...
Click to collapse
Didn't know n8020 has recovery partition different. Is data partition the same? Or also differs? Did you finally get it working or still need help?
X-Stranger said:
Didn't know n8020 has recovery partition different. Is data partition the same? Or also differs? Did you finally get it working or still need help?
Click to expand...
Click to collapse
Userdata is mmcblk0p16.
It starts to boot but tells me that the path "new_root/linux" and "new_root/ubuntu" couldn't be found.
I read about it recently, but dont know where anymore
What im mostly curious about right now are the bugs you talked about. Are they comparable to the archlinux ones? Worse? Better?
Does it have mali hardware accel?
Does the entire thing crash after a while?
Does the img itself get corrupted every few boots?
Wifi works fine?
Sorry for the barrage, but these are important for me to know before i make the switch
Sent from my Nexus 4 using xda app-developers app
emptynick said:
Userdata is mmcblk0p16.
It starts to boot but tells me that the path "new_root/linux" and "new_root/ubuntu" couldn't be found.
I read about it recently, but dont know where anymore
Click to expand...
Click to collapse
Okay, in your case I need to fix recovery partition to look for mmcblk0p16 instead of mmcblk0p12 in my case. Please send me your email, I'll generate and send special version for you to try fixing that.
younix258 said:
What im mostly curious about right now are the bugs you talked about. Are they comparable to the archlinux ones? Worse? Better?
Click to expand...
Click to collapse
This really depends. I would say that it is the same. The bugs I'm talking about: the graphics may hang it you try to move window in Gnome for example, but works perfectly in Gnome Fallback. You should give it a try.
younix258 said:
Does it have mali hardware accel?
Click to expand...
Click to collapse
Yes, it has the same accel that ArchLinux has. But after summer upgrades Gnome did not want to work in ArchLinux and I was not able to fix that. That is why there is no new ArchLinux images.
younix258 said:
Does the entire thing crash after a while?
Click to expand...
Click to collapse
Have not faced this yet.
younix258 said:
Does the img itself get corrupted every few boots?
Click to expand...
Click to collapse
Nope. There I use new approach without img. All the files are stored and the data partition and it is fsck-ing every boot. Even more - it is easier to have Ubuntu and ArchLinux together. I just need to to prepare the Arch files folder for you when have free time. Or you can do it by yourself.
younix258 said:
Wifi works fine?
Click to expand...
Click to collapse
WiFi works the same. The only thing is better - it does not require to off/on to start seeing hotspots.
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