Related
Now that we have kernel source... anyone see Ubuntu in our future?
I have unbuntu on my pc and in process of partitioning he for mac os x install 3 OS why not
Well, ubuntu netbook edition 10-10 would be the perfect candidate, but it seems someone already beat us to the punch:
http://techietonic.com/an-ubuntu-netbook-os-tablet-pc-edition-2011-the-tenq-p07-specs-features/#respond
If we could find a somewhere to download that version of ubuntu netbook, all the basic tablet specific work has already been done, might just need a couple tweeks. I have personally had no luck to even find the company's website though.
TheZedo said:
Well, ubuntu netbook edition 10-10 would be the perfect candidate, but it seems someone already beat us to the punch:
http://techietonic.com/an-ubuntu-netbook-os-tablet-pc-edition-2011-the-tenq-p07-specs-features/#respond
If we could find a somewhere to download that version of ubuntu netbook, all the basic tablet specific work has already been done, might just need a couple tweeks. I have personally had no luck to even find the company's website though.
Click to expand...
Click to collapse
That does not apply, there are no hardware similarities between an android tablet and that one other than form factor.
That machine uses an Intel Atom processor, ubuntu install image on a usb drive and you're pretty much done on that one. Not so much for us.
I see now why the lack of Linux support for Tegra tablets...
http://developer.nvidia.com/tegra/forum/linux-support-becoming-unsupported
(follow the link in his post for some udated info)
Its sad, but between the Honeycomb delays, and Linux being put on the back burner, we have very limited choices at the moment. Ultimately I would like to have Linux on my A7 too, as long as its not uncomfortably slow with only 512MB DDR2 RAM. It looks like Meego might be the distribution to watch for any kind of prebuilt distributable images, at least they have some big players still on board for backing, and they support a variety of platforms.
If you have access to the Nvidia Tegra 250 Developer kit, you could try building a custom Gentoo distro. I really like Gentoo for its configurability options, but honestly, I'm afraid of bricking my A7 with one little mistake.
Android still uses a Linux kernel though, so with kernel source and ability to compile for the tegra chip progress will not grind to a halt. Things just unfortunately won't move along as quickly as most of us would like.
I think a modified version of Ubuntu NBR would run fairly quick on an a7 though.
After some more digging around on the Nvidia Developers forum, I tracked down a few "work-arounds" to install linux...however, please note that most of these posts are very dated.
http://developer.nvidia.com/tegra/forum/workaround-run-ubuntu-now
http://developer.nvidia.com/tegra/forum/fedora-12gnome-running-tegra
http://www.elinux.org/Installation_Detail
I would dare to call this post, "Instructions for the Brave".
After reading those it does sound like we could have a unbuntu os
I've bought a new phone however I do not want to waste my Nexus One. The idea came to my mind firstly was to make it a small 'server' running at home.
Technically I bet it's possible however I don't have a clear path to do that... I've googled for a while and I saw a lot tutorials about how to run Ubuntu on top of Android. However what I want is to get rid of Android and run Linux directly on the hardware.
I think that should have been done by some guys... any help thanks in advance!
zhangxiao83 said:
I've bought a new phone however I do not want to waste my Nexus One. The idea came to my mind firstly was to make it a small 'server' running at home.
Technically I bet it's possible however I don't have a clear path to do that... I've googled for a while and I saw a lot tutorials about how to run Ubuntu on top of Android. However what I want is to get rid of Android and run Linux directly on the hardware.
I think that should have been done by some guys... any help thanks in advance!
Click to expand...
Click to collapse
IIRC, Android is Linux.
If you mean the computer OS, I have no idea.
Theshawty said:
IIRC, Android is Linux.
If you mean the computer OS, I have no idea.
Click to expand...
Click to collapse
Yes I understand that - However I meant Linux such as Ubuntu or Arch distribution...
zhangxiao83 said:
Yes I understand that - However I meant Linux such as Ubuntu or Arch distribution...
Click to expand...
Click to collapse
Running Ubuntu has been deemed possible.
Yes, but why and who will make a port (isn't this simple)? And not all drivers are open source and available to public.
BTW, android is linux and you can even port some applications (a time ago sometime is talking about porting glibc to android, don't remember if this get done, but I think is useless somehow).
It will happen
Word on the street is that Android drivers are being merged back into the development branch of the Linux 3.3 kernel. It's not too surprising considering Android developers were working with the Linux kernel developers until the 2.6.33 Linux kernel.
I bet we will see Debian or Ubuntu running on our N1s eventually. The N1 has a great developer backing since it was pitched as a developer phone, so I bet one of the many talented developers out there will eventually cook up a native Linux ROM. Besides, there are native ports for other devices out there so they can't be too far off.
You can currently install Ubuntu on your N1 but honestly it's pointless. Yes There are great apps to use but compatibility isn't 100% on the phone AND the apps run too slow to actually be useful.
You'd have better chances developing an app for android to do what you want lol.
If this helped hit THANKS
http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-android/ Check this link for a how-to.
I want to know if it is possible and how to make this. Because some people add other governors to their device stock rom
Sent From My Super Modded KFHD
If im not mistaken the governors are built into the kernel, and we cant flash a modified kernel yet
Sent from my KFTT using Tapatalk HD
How To Add Governors and Schedulers To A Linux Kernel
persano said:
I want to know if it is possible and how to make this. Because some people add other governors to their device stock rom
Sent From My Super Modded KFHD
Click to expand...
Click to collapse
persano,
Yes Governors are a function of the Linux Kernel, it can not be done to the factory boot.img due to the constraints with the current Kernel. We will be launching a Ubuntu custom ROM for the Kindle in a few weeks, maybe a couple of Months, it really depends on how busy we are with the XDA topic.
Here is what you would do to build and pack a Kernel:
How To Build Kernel Step 1: Make sure you are running Linux, or else it won't work. So the current Kindle Kernel is out.
How To Build Kernel Step 2: Download the source code from either source.android.com, sonymobile.com (for a stock kernel), kernel.org or FXP github for FXP Kernel.
How To Build Kernel Step 3: unpack the source code from one of the above sources
How To Build Kernel Step 4: make changes to the source code you want to (i.e. adding in governors or io schedulers) - example here
How To Build Kernel Step 5: Build the source (note: the defconfig is probably different you'll have to check the /arch/arm/config folder to figure out which ones is the FXP one...) - Example here
How To Build Kernel Step 6: Make it into a boot img as noted here: Sony Developer Site
How To Build Kernel Step 7: Try booting, if it works, check to make sure that the changes you made sticked. If it doesn't boot, well, you can ask questions in this thread or send us a PM, we do this almost daily.
There are many "tricks of the trade" that we would love to share with you. First attempt to build and pack your own, then when you have issues let us know.:good:
Our new software will automate much of the above process, this feature is due to be added Mid march of 2013. Most of our ROM's will be Ubuntu based.
prokennexusa said:
persano,
Yes Governors are a function of the Linux Kernel, it can not be done to the factory boot.img due to the constraints with the current Kernel. We will be launching a Ubuntu custom ROM for the Kindle in a few weeks, maybe a couple of Months, it really depends on how busy we are with the XDA topic.
Here is what you would do to build and pack a Kernel:
How To Build Kernel Step 1: Make sure you are running Linux, or else it won't work. So the current Kindle Kernel is out.
How To Build Kernel Step 2: Download the source code from either source.android.com, sonymobile.com (for a stock kernel), kernel.org or FXP github for FXP Kernel.
How To Build Kernel Step 3: unpack the source code from one of the above sources
How To Build Kernel Step 4: make changes to the source code you want to (i.e. adding in governors or io schedulers) - example here
How To Build Kernel Step 5: Build the source (note: the defconfig is probably different you'll have to check the /arch/arm/config folder to figure out which ones is the FXP one...) - Example here
How To Build Kernel Step 6: Make it into a boot img as noted here: Sony Developer Site
How To Build Kernel Step 7: Try booting, if it works, check to make sure that the changes you made sticked. If it doesn't boot, well, you can ask questions in this thread or send us a PM, we do this almost daily.
There are many "tricks of the trade" that we would love to share with you. First attempt to build and pack your own, then when you have issues let us know.:good:
Our new software will automate much of the above process, this feature is due to be added Mid march of 2013. Most of our ROM's will be Ubuntu based.
Click to expand...
Click to collapse
Android rom or ubuntu rom?
Sent From My Super Modded KFHD
Custom ROM for The Kindle Fire HD 7" and 2 - Ubuntu Linux
persano said:
Android rom or ubuntu rom?
Sent From My Super Modded KFHD
Click to expand...
Click to collapse
persano,
To be exact, it will be Ubuntu for Android and Ubuntu. There are two versions, one is pure Ubuntu, the other is Ubuntu for Android - we will be building both platforms. The overall idea is to eliminate the old desktop PC. So when you are out in the Field you would take your phone or Tablet with you and when you come home you would Dock it and use it as your primary PC with external monitor, keyboard, mouse, printer and a full array of supported peripherals.
What is Ubuntu for Android?
How would you like a PC that fits in your pocket? For the lowdown on Ubuntu for Android, in terms your grandma could understand, watch this short video. And for news on Ubuntu for Android products, watch user Prokennexusa Posts .
The full PC desktop for multi-core Android phones
Now multi-core Android phones can be PCs too. Ubuntu for Android enables high-end Android handsets to run Ubuntu, the world’s favorite free PC desktop operating system. So users get the Android they know on the move, but when they connect their phone to a monitor, mouse and keyboard, it becomes a PC.
Easy to integrate to your Android phone
Ubuntu for Android drops in cleanly alongside the rest of Android, so it is easy to integrate into current production roadmaps. The hardware requirements are straightforward and, with a broad range of ARM and x86 hardware supported, it can realistically be added to phones already in development.
Of course, your phone needs the docking capability and hardware support for HDMI and USB. But that’s standard for high-end models in the current generation of devices in development.
Why add anything to Android?
Android is a mobile solution, designed for a touch interface on a handheld device. On the desktop, where users expect a pointer-driven experience, a PC operating system is essential. Several vendors have tried to bring Android-based desktops or laptops to market, with no success; Android was designed for touch only, and has its hands full winning the tablet wars.
A complete desktop solution needs a full range of desktop applications. While a mobile OS carries no deep desktop software catalog, Ubuntu offers thousands of applications, all designed for the desktop and most, like Ubuntu, free. And Ubuntu is certified by governments, industry and enterprises, widely deployed on the desktop, and supported by leading management solutions.
Another alternative would be a web-top, or web only desktop. But markets have not responded to web-only environments. The desktop is a high-productivity mode, not a media consumption mode or a browsing mode. That’s why we’ve brought the full power of a native desktop to this solution.
More to come.....
We were just added as one of Ubuntu Developers so the door has opened up! The app ecosystem is much more versatile than Android variants. You can run any Android App on Ubuntu, Windows Apps and the full array of Ubuntu Apps.
Here is a nice YouTube Video Explaining the idea: http://www.youtube.com/watch?feature=player_detailpage&v=iv1Z7bf4jXY
prokennexusa said:
persano,
To be exact, it will be Ubuntu for Android and Ubuntu. There are two versions, one is pure Ubuntu, the other is Ubuntu for Android - we will be building both platforms. The overall idea is to eliminate the old desktop PC. So when you are out in the Field you would take your phone or Tablet with you and when you come home you would Dock it and use it as your primary PC with external monitor, keyboard, mouse, printer and a full array of supported peripherals.
What is Ubuntu for Android?
How would you like a PC that fits in your pocket? For the lowdown on Ubuntu for Android, in terms your grandma could understand, watch this short video. And for news on Ubuntu for Android products, watch user Prokennexusa Posts .
The full PC desktop for multi-core Android phones
Now multi-core Android phones can be PCs too. Ubuntu for Android enables high-end Android handsets to run Ubuntu, the world’s favorite free PC desktop operating system. So users get the Android they know on the move, but when they connect their phone to a monitor, mouse and keyboard, it becomes a PC.
Easy to integrate to your Android phone
Ubuntu for Android drops in cleanly alongside the rest of Android, so it is easy to integrate into current production roadmaps. The hardware requirements are straightforward and, with a broad range of ARM and x86 hardware supported, it can realistically be added to phones already in development.
Of course, your phone needs the docking capability and hardware support for HDMI and USB. But that’s standard for high-end models in the current generation of devices in development.
Why add anything to Android?
Android is a mobile solution, designed for a touch interface on a handheld device. On the desktop, where users expect a pointer-driven experience, a PC operating system is essential. Several vendors have tried to bring Android-based desktops or laptops to market, with no success; Android was designed for touch only, and has its hands full winning the tablet wars.
A complete desktop solution needs a full range of desktop applications. While a mobile OS carries no deep desktop software catalog, Ubuntu offers thousands of applications, all designed for the desktop and most, like Ubuntu, free. And Ubuntu is certified by governments, industry and enterprises, widely deployed on the desktop, and supported by leading management solutions.
Another alternative would be a web-top, or web only desktop. But markets have not responded to web-only environments. The desktop is a high-productivity mode, not a media consumption mode or a browsing mode. That’s why we’ve brought the full power of a native desktop to this solution.
More to come.....
We were just added as one of Ubuntu Developers so the door has opened up! The app ecosystem is much more versatile than Android variants. You can run any Android App on Ubuntu, Windows Apps and the full array of Ubuntu Apps
Click to expand...
Click to collapse
This deserves multi thumbs up!!!:good::good: This sounds great! Please keep up your great work and dedication!
Kindle Fire HD and 2 - Ubuntu Linux
lacoursiere18 said:
This deserves multi thumbs up!!!:good::good: This sounds great! Please keep up your great work and dedication!
Click to expand...
Click to collapse
lacoursiere18,
We will be doing an official post when Ubuntu sends us the Ad shots and personalized goodies we can share with everyone in XDA. This has been a joint venture that we have been working hard to make reality. Finally, the idea was launched at CES, now it is time to make everything reality.
We will have an official release post in a couple of weeks.
Hi Chris,
i'm a bit excited now, because I'm looking forward to the development which is going on there ...
Are you talking about bringing "ubuntu for phones" and "ubuntu for android" with all the benefits and features as announced on ubuntu.com to the kindle fire hd soon? I heard Mark Shuttleworth saying he is expecting to see ubuntu on phones in Q4/2103-Q1/2014.
How much of that development is in that coming ubuntu? Is there any more or less official collaboration with canonical or s.th. like that?
Thanks in advanvce
f
Ubuntu for Android on Kindle Fire HD
freaksworth said:
Hi Chris,
i'm a bit excited now, because I'm looking forward to the development which is going on there ...
Are you talking about bringing "ubuntu for phones" and "ubuntu for android" with all the benefits and features as announced on ubuntu.com to the kindle fire hd soon? I heard saying he is expecting to see ubuntu on phones in Q4/2103-Q1/2014.
How much of that development is in that coming ubuntu? Is there any more or less official collaboration with canonical or s.th. like that?
Thanks in advanvce
f
Click to expand...
Click to collapse
freaksworth,
Initially we will be offering Ubuntu for Android. We are an acknowledged developer with Canonical and are developing Apps for Ubuntu for Android, although all of the Google Apps will work natively under Ubuntu for Android. You will have the several ten of thousands of Apps already available for Ubuntu on top of the Google Play options. How much development is happening with Ubuntu? A large amount, we alone spend 4 to 6 hours daily developing new apps for Ubuntu. Yes, we are working directly with Canonical on both the development aspect of Ubuntu and the promotion part of the new idea. This has been in discussion for over 2 years, as of CES it became reality. We are working to build a custom ROM for the Kindle, time-line is hard to nail down at the moment and it is not due to the Compiling part of the ROM it has to do with the constraints we are under with Canonical directly.
There are several aspects of Ubuntu that we can not even discuss at the moment, all I can say, is that we have an exciting future ahead of us and the desktop PC will disappear as we know it in the next three to four years, you can mark my words.
Yes, the release of the OEM Ubuntu Phone are really not going to happen until Q1 of 2014, Q4 of 2013 is a dream, but not very realistic. If they deploy the idea too early, the idea will fall on it's face. The idea has to be deployed in a highly methodical fashion. The first part is what we are doing, getting everyone excited - you should be excited, this is an awesome platform!
I will post an official release when Canonical approves us to do so, more to come.............
I have wanted to build for and wanted info on building environment. Like what do you use to build with a full Linux box or in virtual box on windows. Also what distro do you run. I heard years ago Ubuntu could give you errors that arch wouldn't.
Thank you in advance!
Sounds like you're new this, so I'd recommend Ubuntu.
Personally, I don't like Ubuntu's desktop environment (Unity) so I opted for Kubuntu instead (Ubuntu with KDE)
KDE often gets a bad reputation for being unstable, and while there's some truth to that, I like it. It's easy to customize and get used to. If you choose Kubuntu, I'd go with the 16.04 release though, it's more stable than 16.10.
I can't think of anything that being on Ubuntu has limited me for. For me, Unity feels kind of restricting in terms of UI, but Ubuntu has full Linux functionality.
Ubuntu is probably the most mainstream Linux distro, and therefore the most noob-friendly. You're more likely to find tutorials for Ubuntu; if you go with Arch you'll have to figure a lot of things out yourself.
Sent from my Axon 7
Hey,
I have really been wanting to root my Galaxy-S8, and the only computer I have available to me currently is a Acer Chromebook. I've been doing a little research on the subject, and it doesn't seem like there's a lot of info on the topic - is that a sign I'm wasting my time?
Really curious if this is possible...
hammer280 said:
Hey,
I have really been wanting to root my Galaxy-S8, and the only computer I have available to me currently is a Acer Chromebook. I've been doing a little research on the subject, and it doesn't seem like there's a lot of info on the topic - is that a sign I'm wasting my time?
Really curious if this is possible...
Click to expand...
Click to collapse
Root is only achievable on a nougat system Oreo and pie nope. I don't know if it's possible from a chrome book most of the rooting tools are based for windows. But jrkruse safestrap rev 5. Is the way
TheMadScientist said:
Root is only achievable on a nougat system Oreo and pie nope. I don't know if it's possible from a chrome book most of the rooting tools are based for windows. But jrkruse safestrap rev 5. Is the way
Click to expand...
Click to collapse
Uhmm...
Actually, I'm afraid that's incorrect. I understand this post was from 2019, but Chromebooks have never been able to use Windows packages and programs. Their OS is Chrome OS, which is basically android but with an enhanced chrome browsing experience. And everyone knows that Android is solely Linux based,... as android uses the linux kernel. You see, Linux is open source, right?... therefore, using the Linux kernels, the android developers were able to implement the various modifications that fit their needs.
Now, the Chromebooks, have actually brought even more Linux computing to the table. First off, they have a full fledged Linux distro in beta, that you can enable... Actually even without enabling the linux beta, Chromebooks all have access to the developer shell. As well as Chrome's very own "Crosh" terminal. Both of which are operable using linux commands. (Not windows)
And on just another note...
Google, over the past few years, actually has been working on a new Chrome browser. And by "past few years", I mean even at the time off this original post, up untill now, they've continuously been working on this thing. Lol Yes, I know... Incredible isn't it? Lol Any way, even though it is still currently being worked on Chromebook users now have access to this new brower, via enabling it through turning on a few flags in "Chrome://flags". So the main idea for this browser is actually to decouple the browser from the OS, giving the new Chrome Web browser, much more of a separation. (Which I'm definitely in favour of, and is far less confusing lol). So this new browser, has yet to actually be "officially named" (probably will just stay as "Chrome")... But for now, the developers have made it identifiable to us users, and have been referring to it as "LaCrOS". So, I just want to point out, that the name "LaCrOS" is actually derived from both the words "Linux" and "Chrome OS".
One thing, maybe is what you were thinking of, is that some Chromebooks (like my own) use the amd x86 processors, instead of Arm64, which is the same processors that you'd find in any windows computer (that is aside from, well... now Apple lol) But even though The Chromebooks that use x86 processing offer more of a powerful performance (as well as a powerful consumption of battery & memory) they still very much are Linux based machines... And are VERY VERY different than a windows computer. In order to run any Windows program or package on a Chromebook, you'd need some type of emulator allowing you to do so. Chromebooks, alike Androids, without use of an emulator, are only able to read, install, and run .apk files and not a windows .exe file.
Gorvetco said:
Uhmm...
Actually, I'm afraid that's incorrect. I understand this post was from 2019, but Chromebooks have never been able to use Windows packages and programs. Their OS is Chrome OS, which is basically android but with an enhanced chrome browsing experience. And everyone knows that Android is solely Linux based,... as android uses the linux kernel. You see, Linux is open source, right?... therefore, using the Linux kernels, the android developers were able to implement the various modifications that fit their needs.
Now, the Chromebooks, have actually brought even more Linux computing to the table. First off, they have a full fledged Linux distro in beta, that you can enable... Actually even without enabling the linux beta, Chromebooks all have access to the developer shell. As well as Chrome's very own "Crosh" terminal. Both of which are operable using linux commands. (Not windows)
And on just another note...
Google, over the past few years, actually has been working on a new Chrome browser. And by "past few years", I mean even at the time off this original post, up untill now, they've continuously been working on this thing. Lol Yes, I know... Incredible isn't it? Lol Any way, even though it is still currently being worked on Chromebook users now have access to this new brower, via enabling it through turning on a few flags in "Chrome://flags". So the main idea for this browser is actually to decouple the browser from the OS, giving the new Chrome Web browser, much more of a separation. (Which I'm definitely in favour of, and is far less confusing lol). So this new browser, has yet to actually be "officially named" (probably will just stay as "Chrome")... But for now, the developers have made it identifiable to us users, and have been referring to it as "LaCrOS". So, I just want to point out, that the name "LaCrOS" is actually derived from both the words "Linux" and "Chrome OS".
One thing, maybe is what you were thinking of, is that some Chromebooks (like my own) use the amd x86 processors, instead of Arm64, which is the same processors that you'd find in any windows computer (that is aside from, well... now Apple lol) But even though The Chromebooks that use x86 processing offer more of a powerful performance (as well as a powerful consumption of battery & memory) they still very much are Linux based machines... And are VERY VERY different than a windows computer. In order to run any Windows program or package on a Chromebook, you'd need some type of emulator allowing you to do so. Chromebooks, alike Androids, without use of an emulator, are only able to read, install, and run .apk files and not a windows .exe file.
Click to expand...
Click to collapse
Ummm. As I stated years ago. I didn't know. I didn't say yes.
We didn't need a long drawn out explanation of a chrome book. And so you know. I've had a hp windows laptop that I've swapped back and forth between windows and chrome os. For my kid.
Your post is completely irrelevant. As it is so old of a topic. Either way the methods for these devices are completely depreciated.
I am one of the people who helped out on these devices with heavy testing. Plus much much more.
By you telling me I was incorrect just shows that you are acting like a pompous know it all and trying to prove me wrong where I specifically said I didn't know. How does me saying I don't know make me incorrect?
On a side note. We here at xda don't much care to drag up old deals topics that have long since been gone and irrelevant.
Clutters the pages with old useless information
It wasn't irrelevant. I disagree.
Furthermore, the original question was regarding Chromebooks specifically, and not Chrome OS. So my apologies, but shouldn't even the oldest of threads be contemporized if the new information or tools now available have changed since then? But as I did mention, this was not the point of what I wanted to make clear.
I did not say anything regarding the effectiveness or ineffectiveness of utilizing a Chromebook to obtain root on an seperate android device. Nor did I state that you were incorrect. I'm well aware, that it would be ignorant and frankly just unfair to disparage you based on the knowledge available at the given point in time. However, it's unfortunate that you felt obligated to retaliate in such a manner, as It was very clear of what my actual intensions here were, and that it was not in any way a means to belittle you.
There is something you may just have me on though. For in the sense that I guess I am unsure of the protocol here at XDA. But I still do not feel that attacking me was the right way to go about your response. You see, I'm a member at both GitHub, and Stack exchange. So I guess I just assumed that because there is plenty of room for misinterpretation, and at times even errors, so honestly, some of the best ways to further our understanding is when we converse and can learn from one another. In any case, I had noticed that your comment could very easily be misinterpreted, and not everyone is on the same advanced level as you might be. So its best to not just assume, but actually it is encourage to give your answers as if you may be explaining to someone who isn't familiar with the subject at all, and using examples and explaining as clearly as possible are excellent way to do this, and usually can be most appreciated.
As for trying to prove you wrong, I do then appologize, as that was not my intentions. I only wished for it to be acknowledged, that a Chromebook, regardless of the year, then and now, in no way has the ability to utilise any Windows rooting tool. I did not state this to offend any one. It was only to contribute a very descriptive and detailed body of information, ensuring that the difference between windows executable files and that of Androids are to be both known and understood, to avoid anyone's time being wasted on a task or and idea that would get them nowhere.
It is necessary to do this, as for the chance an unknowingly individual may come across this thread, looking for answers similar to the question at hand. As you should know, even "old topics" should be rectified as such. Unless in the event they are to be removed, locked or relocated to a more appropriate forum.
The only thing here I believe to be irrelevant, is that you felt inclined to point out what I had already stated and took into consideration. So again, that way it is clear, I would just like to point out... that regardless of the year, whether it be 4 years ago, 4 months ago, or whether it be today. I amend the information I provided, and consider it to not only be "relevant" but I hope it proves to be useful and potential prevent or deter someone who would have been then proceeding to inquire about how to run "Windows rooting tools" on a chromebook.