Related
Ok, first I've done some search and I've try different things...
I'd like to flash my Hero (T-Mobile) with an updated HTC ROM for the Hero, ok it should be easy, like in WM time ;-)
But I cannot run the "RUU_Hero_HTC_WWE_2.73.405.38_WWE_release_signed_NoDriver.exe" through Wine for example. So I've setup a virtual XP machine (VirtualBox rocks) But this don't work either...
So the real question: how to flash "official" ROM from microSD?
I mean I've probably to "unpack" the content of "RUU_Hero_HTC_WWE_2.73.405.38_WWE_release_signed_NoDriver.exe" in a certain way and use the update fonction from recovery mode. So if somebody has the answer it will be cool to share
PS: My Hero is rooted of course
Thanks
ok it seems my answer was here: http://android.modaco.com/content/h...-24-11-hero-roms-radios-in-update-zip-format/
hope it will be usefull for someone else
Its rather this:
http://android.modaco.com/content/h...ng-the-patched-recovery-image-on-your-device/
Once you have the patched recovery image, future updates are a breeze (just copy update.zip on the SDHC card and reboot).
Hello all,
Was thinking if there could be way to have some android live versions of the rOM images similar to the OSes having Live CD/DVD Where in you could boot up your machine with the Live CD/DVD and work on the OS from the CD/DVD.
We could have all the different ROM mods being put on the SD card, boot up the phone via SD card and test the ROMs before really flashing them on to the Phones.
I know the Gurus and geniuses here can make it happen.
Waiting for this to happen.
I am not sure if its version 1.5 or 1.6 but after one or the other Android stopped being able to boot to x86 chips. Which means you could build a live CD to do this but it would have to be a relatively old version of android. I believe google did this because if I remember correctly they were starting to support x86 architecture on chrome.
jvward said:
I am not sure if its version 1.5 or 1.6 but after one or the other Android stopped being able to boot to x86 chips. Which means you could build a live CD to do this but it would have to be a relatively old version of android. I believe google did this because if I remember correctly they were starting to support x86 architecture on chrome.
Click to expand...
Click to collapse
I am not sure If I was clear. What I am talking here is about having a mechanism for the Modified Phone ROMs to be on the SD card, boot up the phone with the ROM on the SD card and test the ROM before flashing it on the Phone.
jvward said:
I am not sure if its version 1.5 or 1.6 but after one or the other Android stopped being able to boot to x86 chips. Which means you could build a live CD to do this but it would have to be a relatively old version of android. I believe google did this because if I remember correctly they were starting to support x86 architecture on chrome.
Click to expand...
Click to collapse
I believe he want's a way to test the roms on his phone using some kind of a virtual machine type of program on his phone.
sada23 said:
I am not sure If I was clear. What I am talking here is about having a mechanism for the Modified Phone ROMs to be on the SD card, boot up the phone with the ROM on the SD card and test the ROM before flashing it on the Phone.
Click to expand...
Click to collapse
I do not know of anything like this for the phone itself, but what you can do is get the Android SDK and use the emulator to run the rom you want to run and test it out that way.
Cody,
Thanks for the hint. I do have the andoid emulator installed on my machine and will try your suggestion. I have interest in developing some apps or even compile the android ROMs . Will have to start somewhere.
I've been thinking: In order to use UrukDroid or Churli's quick-root method, we have to sacrifice using the other, as well as giving up on Angstrom (not a great loss...).
Thinking of the future, is there a way we can insert a bootmenu (something Grub-like) at the beginning of the SDE boot process that could allow us to have multiple OSs on the Archos. This way, for example, we could install Uruk on the SD while still having Angstrom available. We could then potentially install Ubuntu, Honeycomb betas, etc. in additional partitions we create.
I'm hoping to inspire someone...
strongergravity said:
I've been thinking: In order to use UrukDroid or Churli's quick-root method, we have to sacrifice using the other, as well as giving up on Angstrom (not a great loss...).
Thinking of the future, is there a way we can insert a bootmenu (something Grub-like) at the beginning of the SDE boot process that could allow us to have multiple OSs on the Archos. This way, for example, we could install Uruk on the SD while still having Angstrom available. We could then potentially install Ubuntu, Honeycomb betas, etc. in additional partitions we create.
I'm hoping to inspire someone...
Click to expand...
Click to collapse
Yes and no.
The no.
The problem is that the real boot loader (equivalent to grub on a linux box) is still not accessible. That boot loader is what does the choice between the custom, init and recovery images that are place in the /mnt/rawfs.
The Yes
It would be possible to create a zImage and an initramfs.cpio.gz with a special init script that asks what root filesystem to mount and then complete the boot.
The thing is that the kernel will be shared between all the custom boot solutions.
wdl1908 said:
It would be possible to create a zImage and an initramfs.cpio.gz with a special init script that asks what root filesystem to mount and then complete the boot.
Click to expand...
Click to collapse
That is what I was thinking about. I guess it was too early in the morning when I posted...
The thing is that the kernel will be shared between all the custom boot solutions.
Click to expand...
Click to collapse
So, did the Angstrom that came in the SDE run on the same kernal as the Android on the Archos? I assume not. If not, this would mean we could only pull this stunt for different Android builds only, right?
strongergravity said:
So, did the Angstrom that came in the SDE run on the same kernal as the Android on the Archos? I assume not. If not, this would mean we could only pull this stunt for different Android builds only, right?
Click to expand...
Click to collapse
I don't think so. Installing the SDE gives you the possibility to install a secondary kernel and to uninstall the default Android kernel.
So I can give you a No for your first question and a 'Yes, at the current state of development ans research' for your second question.
strongergravity said:
That is what I was thinking about. I guess it was too early in the morning when I posted...
So, did the Angstrom that came in the SDE run on the same kernal as the Android on the Archos? I assume not. If not, this would mean we could only pull this stunt for different Android builds only, right?
Click to expand...
Click to collapse
There can be 3 different kernels.
custom
init
recovery
The custom is the only one that can be replaced when the SDE is flashed to the device, init is the stock android and recovery is just a kernel with some scripts that give you the ability to do stuff like reformat check disk etc.... Also the recovery is the part that is used to flash the custom kernel.
What about kexec, seems to be the perfect choice for this problem.
Unmensch said:
What about kexec, seems to be the perfect choice for this problem.
Click to expand...
Click to collapse
Sounds good to me, someone should definitly do some research and testing. Unfortunately it won't be me as I already have a bunch of project going on
Until now I was testing Remix on a flash drive, most of the stuff is running great, so I think it's time to try it on the HD.
So here's the question, it's possible to install RemixOS on HD without create partition?
I want Remix to be installed in a regular folder in my HD, with an option to select it in the OS selector when PC starts, and I want it to use data.img instead of something else... Basically just like Phoenix OS.
Is this possible?
Thx..
Cheers...
Regnas said:
Until now I was testing Remix on a flash drive, most of the stuff is running great, so I think it's time to try it on the HD.
So here's the question, it's possible to install RemixOS on HD without create partition?
I want Remix to be installed in a regular folder in my HD, with an option to select it in the OS selector when PC starts, and I want it to use data.img instead of something else... Basically just like Phoenix OS.
Is this possible?
Thx..
Cheers...
Click to expand...
Click to collapse
dude, all you need to do is to look on jide's web
For Hard Disk Installation:
NOTE: Currently, installation tool only supports Windows 7, Windows 8 or Windows 10, with a minimum capacity of 8GB. Users of other operating systems, please install on USB flash drive.
1. Download the Remix OS for PC package, which contains the Remix OS for PC ROM & Installation Tool.
2. Open the Remix OS Installation Tool and follow the instructions to install Remix OS for PC on your hard disk.
3. Reboot your PC.
NOTE for UEFI boot: press special key (F12 for Dell, F9 for HP, F12 for Lenovo, Option Key for MAC) while booting to enter boot menu and ensure that Secure Boot is disabled.
4. Select Remix OS in Windows Boot Menu.
find more on http://www.jide.com/remixos-for-pc#downloadNow
Dude...just try and will know the answers [emoji4]
bombaglad said:
dude, all you need to do is to look on jide's web
For Hard Disk Installation:
NOTE: Currently, installation tool only supports Windows 7, Windows 8 or Windows 10, with a minimum capacity of 8GB. Users of other operating systems, please install on USB flash drive.
1. Download the Remix OS for PC package, which contains the Remix OS for PC ROM & Installation Tool.
2. Open the Remix OS Installation Tool and follow the instructions to install Remix OS for PC on your hard disk.
3. Reboot your PC.
NOTE for UEFI boot: press special key (F12 for Dell, F9 for HP, F12 for Lenovo, Option Key for MAC) while booting to enter boot menu and ensure that Secure Boot is disabled.
4. Select Remix OS in Windows Boot Menu.
find more on http://www.jide.com/remixos-for-pc#downloadNow
Click to expand...
Click to collapse
Thanks, I already saw this...
But in this guide it's not clear what the installation tool will do, if it will create partitions, if it will format something etc... Take the USB installation as an example, I never thought it would create 3 partitions on it...
That's why I'm asking this... Besides, I saw many people unable to boot into Windows after some sort of HD installation of Remix.
Have you tried this method of installation?
If yes, how is the structure of the directory, what files are in there, is it using data.img?
Cheers...
kretex said:
Dude...just try and will know the answers [emoji4]
Click to expand...
Click to collapse
I'm triple boot Win 10, win7 and Phoenix OS, so I'm a little afraid of mess things up.. It would be a nightmare.......
Regnas said:
Thanks, I already saw this...
But in this guide it's not clear what the installation tool will do, if it will create partitions, if it will format something etc... Take the USB installation as an example, I never thought it would create 3 partitions on it...
That's why I'm asking this... Besides, I saw many people unable to boot into Windows after some sort of HD installation of Remix.
Have you tried this method of installation?
If yes, how is the structure of the directory, what files are in there, is it using data.img?
Cheers...
Click to expand...
Click to collapse
The hard drive installation will create a folder called "RemixOS" and add a boot entry for it in the Windows boot loader. In that folder is the kernel, initrd.img, system.img, menu.lst and some other files. An 8 GB data.img will be created on first boot. Those who have problems with booting are typically using a third-party method to install it.
putr4s said:
The hard drive installation will create a folder called "RemixOS" and add a boot entry for it in the Windows boot loader. In that folder is the kernel, initrd.img, system.img, menu.lst and some other files. An 8 GB data.img will be created on first boot. Those who have problems with booting are typically using a third-party method to install it.
Click to expand...
Click to collapse
Thanks for the "encouraging" answer..
So it seems like a safe method....!?
But damn, stuff like this: https://groups.google.com/forum/m/#!topic/remix-os-for-pc/vAIwtc8QuOw are a nightmare....
Cheers....
Regnas said:
Thanks for the "encouraging" answer..
So it seems like a safe method....!?
But damn, stuff like this: https://groups.google.com/forum/m/#!topic/remix-os-for-pc/vAIwtc8QuOw are a nightmare....
Cheers....
Click to expand...
Click to collapse
It appears that for the issue mentioned in the link you posted the solution is to simply disable Secure Boot. I don't have much experience with UEFI myself, but on a BIOS system the installer worked perfectly, it didn't break either Windows or Linux Mint.
Sent from my Galaxy Tab 2 3G using Tapatalk
Regnas said:
Thanks for the "encouraging" answer..
So it seems like a safe method....!?
But damn, stuff like this: https://groups.google.com/forum/m/#!topic/remix-os-for-pc/vAIwtc8QuOw are a nightmare....
Cheers....
Click to expand...
Click to collapse
it also happened to me, i had to use lenovo's one click recovery...
now i installed remix on my d drive and it's fine, last time it went wrong, just because i tried to root it.. so just don't try to root and you'll be fine
this is what the folder looks like:
putr4s said:
It appears that for the issue mentioned in the link you posted the solution is to simply disable Secure Boot. I don't have much experience with UEFI myself, but on a BIOS system the installer worked perfectly, it didn't break either Windows or Linux Mint.
Sent from my Galaxy Tab 2 3G using Tapatalk
Click to expand...
Click to collapse
Thanks for the support.
Fortunately (I hope) I'm on BIOS as well, cause I heard somewhere that disabling secure boot prevents Windows to boot. I don't know if it's a Windows requirement on UEFI machines...
Now it's time to build courage to install it....
Cheers..
bombaglad said:
it also happened to me, i had to use lenovo's one click recovery...
now i installed remix on my d drive and it's fine, last time it went wrong, just because i tried to root it.. so just don't try to root and you'll be fine
this is what the folder looks like:
Click to expand...
Click to collapse
Thanks for the reply.
So trying to root it cause your PC to not be able to boot into Remix and Windows? Whoa, that's scary man...
In your screenshot everything seems fine, and I can see that you have a bigger data than standard 8GB, did you expanded it using third part tools?
Cheers.
Regnas said:
Thanks for the reply.
So trying to root it cause your PC to not be able to boot into Remix and Windows? Whoa, that's scary man...
In your screenshot everything seems fine, and I can see that you have a bigger data than standard 8GB, did you expanded it using third part tools?
Cheers.
Click to expand...
Click to collapse
I expanded the data.img using this tutorial (http://forum.ppcgeeks.com/android-tp2/138623-how-get-bigger-data-img.html). Don't mind the fact that it was originally made for Windows Mobile devices running Android on SD card, the concept is the same (add zeros to the end of data.img, then expand the partition table in the data.img to cover the extra space).
putr4s said:
I expanded the data.img using this tutorial (http://forum.ppcgeeks.com/android-tp2/138623-how-get-bigger-data-img.html). Don't mind the fact that it was originally made for Windows Mobile devices running Android on SD card, the concept is the same (add zeros to the end of data.img, then expand the partition table in the data.img to cover the extra space).
Click to expand...
Click to collapse
Interesting method...
Thanks for sharing..
Regnas said:
Thanks for the reply.
So trying to root it cause your PC to not be able to boot into Remix and Windows? Whoa, that's scary man...
In your screenshot everything seems fine, and I can see that you have a bigger data than standard 8GB, did you expanded it using third part tools?
Cheers.
Click to expand...
Click to collapse
no need to expand at all, you can choose between 8, 16 and 32GB
bombaglad said:
no need to expand at all, you can choose between 8, 16 and 32GB
Click to expand...
Click to collapse
Thank you Sir.
Hmm, interesting...
Where I can choose this, in the installation tool?
And does it take too long to boot? I'm asking this because I expanded the data.img of Phoenix OS, and since then it takes a lot more time to boot.
Cheers..
Regnas said:
Thank you Sir.
Hmm, interesting...
Where I can choose this, in the installation tool?
And does it take too long to boot? I'm asking this because I expanded the data.img of Phoenix OS, and since then it takes a lot more time to boot.
Cheers..
Click to expand...
Click to collapse
nope, as long as your data.img is much smaller than your actual harddisk, you will have no problems with speed.
yes, the instalation tool asks you what size you want to use, either 8, 16 or 32 GB can be chosen
bombaglad said:
nope, as long as your data.img is much smaller than your actual harddisk, you will have no problems with speed.
yes, the instalation tool asks you what size you want to use, either 8, 16 or 32 GB can be chosen
Click to expand...
Click to collapse
Thank you Sir.
Cheers.
So.....the problem solved [emoji16]
kretex said:
So.....the problem solved [emoji16]
Click to expand...
Click to collapse
We're getting there........
Finally I installed it on my Hard Drive... Everything seems to be working fine...
Thank you guys for all the info, help, support and whatnot...
Cheers..
Hey everyone!
I know that one of the biggest barriers for completely ditching my MacBook Pro for my Pixelbook was the ability to use ADB and fastboot (upgrading Android versions, flashing TWRP, factory resetting). ADB and fastboot are installed on later versions of Chrome OS; unfortunately, these versions are too old for devices like the Pixel 2 (XL) and there isn't a ton of information on how to get them updated and working properly.
As such, I created an installation script that will push the latest versions of the platform tools to the local binary directory and install a small wrapper script so you can use the commands as you normally would. The scripts should be fairly easy to read if you have a basic understanding of the command line, I have commented them so it's clear what is going on.
The installation script can be used to install the tools for the first time as well as upgrading to newer version as they come out. The changelog for each version can be found here.
Please see the README for the full instructions and let me know if you have any questions, enjoy!
On Chrome OS Canary version 69 on an ARM CPU, ADB and Fastboot are both installed by default.
zarthan said:
On Chrome OS Canary version 69 on an ARM CPU, ADB and Fastboot are both installed by default.
Click to expand...
Click to collapse
Do they actually work? They were installed on my Chromebook Plus out of the box but they are too outdated for my Pixel 2 XL.
Will this work in Acer c720p, or is it too old? If not what about Samsung Chromebook pro? Would it have to be in developer mode?
firegoblin said:
Will this work in Acer c720p, or is it too old? If not what about Samsung Chromebook pro? Would it have to be in developer mode?
Click to expand...
Click to collapse
In theory, it should work for both.
Please see the README as it answers the second question.
nathanchance said:
In theory, it should work for both.
Please see the README as it answers the second question.
Click to expand...
Click to collapse
Dear lord my c720p has a purpose now. Thank you! ChromeOS ftw
nathanchance said:
In theory, it should work for both.
Please see the README as it answers the second question.
Click to expand...
Click to collapse
Do you know if there is anyway to run a shell directly from the downloads folder in ChromeOS? I couldn't get fastboot to function properly.
firegoblin said:
Do you know if there is anyway to run a shell directly from the downloads folder in ChromeOS? I couldn't get fastboot to function properly.
Click to expand...
Click to collapse
Going to have to give me more details, like the stuff I request in the README.
Sent from my Pixel 2 XL using XDA Labs
nathanchance said:
Do they actually work? They were installed on my Chromebook Plus out of the box but they are too outdated for my Pixel 2 XL.
Click to expand...
Click to collapse
fastboot doesn't report version but adb is 1.32 which is old. I don't know how recent adb was added to Chrome OS but I am sure I have used them in the past. I have lived in Canary for the last 2 years so I have no idea whether it was a Canary thing or widely available within developer mode.
Another option since you are in developer mode is Crouton and install a fullish version of Linux. adb does work within a Crouton session. Even if I was to update the version installed in Chrome OS, I would need to reinstall it every day since Canary is updated daily and sometimes two or three times a day. Even stable can be updated mid-cycle so you could get caught with the outdated one at an inopportune time.
zarthan said:
fastboot doesn't report version but adb is 1.32 which is old. I don't know how recent adb was added to Chrome OS but I am sure I have used them in the past. I have lived in Canary for the last 2 years so I have no idea whether it was a Canary thing or widely available within developer mode.
Another option since you are in developer mode is Crouton and install a fullish version of Linux. adb does work within a Crouton session. Even if I was to update the version installed in Chrome OS, I would need to reinstall it every day since Canary is updated daily and sometimes two or three times a day. Even stable can be updated mid-cycle so you could get caught with the outdated one at an inopportune time.
Click to expand...
Click to collapse
For me personally, I bought a Chromebook for Chrome OS, not the hardware, so Crouton wasn't really an option.
You don't need to reinstall these as they are in /usr/local/bin so they're not touched during a Chrome OS upgrade.
I don't think I understand "Crouton wasn't really an option". Crouton is a simple script that installs various versions of Linux desktops that run alongside Chrome in a chroot. Probably any Chromebook made can install Crouton. The only thing required is to be in developer mode, which you are. I choose to run my sessions in a tab but it can be a separate window. Not much you can't install and run in these sessions.
zarthan said:
I don't think I understand "Crouton wasn't really an option". Crouton is a simple script that installs various versions of Linux desktops that run alongside Chrome in a chroot. Probably any Chromebook made can install Crouton. The only thing required is to be in developer mode, which you are. I choose to run my sessions in a tab but it can be a separate window. Not much you can't install and run in these sessions.
Click to expand...
Click to collapse
Would help if I actually did proper research into Crouton :silly:thanks for the clarification, I'll have to check it out soon
Crouton was developed by a Google employee. You can create a pretty complete development environment. An i7 and 16 GB RAM are becoming more and more appealing.
zarthan said:
Crouton was developed by a Google employee. You can create a pretty complete development environment. An i7 and 16 GB RAM are becoming more and more appealing.
Click to expand...
Click to collapse
Ended up trying it yesterday, I'm a big fan so far. Will continue to explore it, thanks for the tip!
nathanchance said:
Ended up trying it yesterday, I'm a big fan so far. Will continue to explore it, thanks for the tip!
Click to expand...
Click to collapse
http://skycocker.github.io/chromebrew/
If you mainly just want command line to install packages.
There is also chromebrew, almost a chromeos version of homebrew on mac.
Hello!
First off I would like to thank you very much for making this installation script! I've been waiting the whole time since I bought my Chromebook about 3 weeks ago for somebody to post a script to install ADB/fastboot since the recent added support of the 2 to ChromeOS. ADB/fastboot support is the entire reason why I bought this Chromebook, if it did not have it, I would of been stuck buying a Windows laptop. I was really excited when I read they just added support recently for ADB/fastboot! I have a couple of small problems and if anybody can help me out, it will be greatly appreciated.
1. I cannot get ADB to work yet on my Pixel 2 XL, but fastboot works no problem. When I try to use ADB, it says device is "offline". Sometimes it says "unauthorized" when I've accepted permissions and click 'always allow from this computer' etc etc. Do I have to use a root shell to run adb/fastboot or can i use a regular shell like on my old windows laptop? Do i have to use sudo before every single command as well or just 'adb devices' like I would on a windows. I know these are noob questions but it is because I am a noob and have only used ADB/fastboot on a WIndows 7 laptop before this.
2. My other question is when I powerwashed and it booted to the user sign in screen, I tried to click enable debugging features but it said not all of the features could of been enabled. Wth does that mean? How can I fix it? Does the chromebook stay in developer mode after I powerwash it if it was in dev mode before I powerwashed it? I did return it back to the dev channel after the powerwash bc I noticed it was back on stable.
Do I have to install a custom version of Chromium OS before this will work?
Thank you guys so much, and thanks again @nathanchance for making this script. Also thanks for your Pixel 2 XL kernel, I use that as well. Cheers!
My device is the Acer Chromebook R11 .. 32 GB HD / 4 GB RAM with a 64 GB sdcard in it .. 2 in 1 tablet/laptop .. x86_64
ok so how do I copy the files I downloaded to another directory? The chrome files explorer only shows drive and downloads
Nathan
Will you be building your own kernel and or system images for pixelbook?
smartymcfly said:
Nathan
Will you be building your own kernel and or system images for pixelbook?
Click to expand...
Click to collapse
No. The entire reason I got a Pixelbook is so that I could have a super stable local device and do all my heavy computing on a remote server.
nathanchance said:
Hey everyone!
I know that one of the biggest barriers for completely ditching my MacBook Pro for my Pixelbook was the ability to use ADB and fastboot (upgrading Android versions, flashing TWRP, factory resetting). ADB and fastboot are installed on later versions of Chrome OS; unfortunately, these versions are too old for devices like the Pixel 2 (XL) and there isn't a ton of information on how to get them updated and working properly.
As such, I created an installation script that will push the latest versions of the platform tools to the local binary directory and install a small wrapper script so you can use the commands as you normally would. The scripts should be fairly easy to read if you have a basic understanding of the command line, I have commented them so it's clear what is going on.
The installation script can be used to install the tools for the first time as well as upgrading to newer version as they come out. The changelog for each version can be found here.
Please see the README for the full instructions and let me know if you have any questions, enjoy!
Click to expand...
Click to collapse
Hi Nathan,
I also have a Chromebook plus which is not x86_64. Have you written a script compatible with the Chromebook plus?
Thank you for all your contributions to the community!
-Dan