Related
***Root method for .621 update***
THIS IS FOR USERS WITH THE .621 UPDATE ONLY. IF YOU HAVE NOT UPDATED DO NOT USE THIS METHOD.
*****DO NOT USE WINDOWS*****DO NOT USE RSDLITE*****
Instructs are made by Skelente
1.) Download the latest Ubuntu iso for your system. Most processors these days are 64 bit, but if you're running on an older computer or do not know if you have a 32 or 64 bit processor I'd recommend doing 32 bit just to be safe (64 bit processors can run both 32 and 64 bit distributions, but 32 bit systems cannot run 64 bit distributions.) Side note: you can download other distributions, but if you do you will not be able to create the persistent drive using the USB method. It should also be noted that some older systems cannot boot from USB, most newer systems (post 2000/2001 IIRC) can boot from USB, however you should consult Google to verify for your system.
2.) Burn the iso:
2.a If you have a cd burner and blank disc, this is the easiest method but, again, you will not have a persistent drive you will just have a Live CD. Use an iso burner to burn to cd, then skip to step 3a.
2.b If you do not have a burner, a blank disc (or don't feel like wasting a DVD disc) but have a free USB drive (with at least 2 GB of memory, bit overkill but it has to be big enough to hold the iso + changes + the persistent "drive") then I recommend downloading either unetbootin or universal USB installer. Go to either web site and follow their instructions. If you use Ubuntu, you'll have the option of creating a persistent drive, which is basically a fake-partition that allows you to save files to when you reboot Linux after running this Live USB. I would recommend using a persistent size of at least 200 mb so we can save the SBF file and sbf_flash. If you created a persistent drive go to step 4. If you opted out of this, skip to step 4.
3.a So you have a Live CD now. If you have a spare flash drive, load up the 604 SBF and sbf_flash. Either way, you'll need to proceed to booting into linux, go to step 4.
3.b Once the respective application has finished, copy the SBF and sbf_flash file to the persistent drive listed in windows.
4. Now we need to boot from your Live image. Restart your computer. When your computer is booting up it should give you two options, "Enter BIOS" and "Select Boot Order" or similar. For my Lenovo Laptop, I can hit F12 to change the boot order, and from there I can select my USB port and it'll boot from there. If you do not see a boot order option, you will need to go into your bios and change the boot order manually. Again, you will need consult Google for this as the menu selections vary by system. It really isn't that hard to figure out if you go through the menus, but I strongly, strongly, strongly recommend and encourage you to google your motherboard's manual to verify what you need to change if you don't know what you are doing. You are responsible for any changes you make on your system. Your BIOS is crucial for your system to function properly. Once you have found where to change your boot order, select the respective drive (USB, or your CD/DVD drive). These will be listed by the manufacture name (so SamsungXXXX for a Samsung drive or PNYXXXX if you're using a PNY usb stick.)
5. When Ubuntu boots up, it'll give you an option to run "Live" from the CD/USB. Select this option. Installing to your hard drive could mess up your current OS install, and I'm not going to get into partitioning here. Once you've gotten into Ubuntu, select "Dash Home" in the upper left hand corner, and then type terminal in the search box. Click terminal, then open it up.
6. Now you'll need to get to where ever you have the SBF and sbf_flash stored through the terminal. If you chose to use the boot cd, and did not have an available flash drive, you will need to download the SBF from here, as well as sbf_flash and then extract them to the same folder. The default is "Downloads" and I recommend just extracting them to that directory for simplicity.
6.a If you had to download the SBF/sbf_flash, getting there through terminal is rather easy. All you'll need to do is type these commands into the terminal:
cd Downloads
chmod +x sbf_flash
./sbf_flash mb809-2.3.5.sbf
And then let the program do it's work. When it's done, go to step 7.
6.b If you already copied the required files to a USB drive, we need to get there through terminal. Type these commands:
cd /
cd /media/
ls (This command will list all the drives connected to your system, cdrom, usb, etc. If you used the Universal USB installer it will list the USB drive as "PENDRIVE", I'm not sure what the default is for Unetbootin but you should be able to figure it out and if you just used a spare device it could be completely random.)
cd drivename (obvioiusly this will vary based on the USB method, for me its "cd PENDRIVE"
If your files were just on the main drive, you don't need to do anything else but the following commands. If you put them in another folder, you will need to do "cd foldername" without the quotes obviously. When you're in the directory with both the SBF and sbf_flash you will need to do these commands (again, ignoring the '-'):
chmod +x sbf_flash
./sbf_flash mb809-2.3.5.sbf
And then let the program do it's work. When it's done, go to step 7.
7.) After sbf_flash is done, you'll need to restart your computer. Its recommended you remove your boot media (cd or usb drive) so that Windows can boot normally. If you changed the boot order in bios you will need to change it back to what it was before, otherwise whenever you have a CD/USB stick plugged in your computer will automatically try to boot from it, and get pissy if it can't boot from the media.
8.) Once you're back in windows you'll need to run the zergrushv4 root method. From there you can do whatever you want. You still cannot SBF to previous versions (602 or 605) and you cannot run Froyo roms.
Downloads:
sbf_flash
SBF File & root tools
*HELP*
If you flashed with RSD Lite and have no data here is your options...
Flash stock .621 sbf and...
Switch devices on your account to reactivate the data
or
Call verizon to have them reporvision your data...
Once you are on the milestone system you can flash a custom rom.
You must SBF in Linux using sbf_flash, otherwise .604's radio will flash over .621's and your phone will no longer be able to take or place phone calls.
Edit: It may just be data, instead of phone capabilities. But still, flashing in Linux is much easier than having to spend time with Verizon's incompetent phone operators.
Sent from my Transformer TF101 using Tapatalk
If you SBF'd using RSD Lite, you flashed the 605 baseband over the 621. I didn't think this would mess up texts/phone calls but just your data connection, but correct me if I'm wrong I'm just going from memory (I had a dx2, just been watching the threads.) This was a big problem for the people over at rootz and they had a few different tactics on how to solve it. Some were able to call VZW and ask the tech support to "re-provision their data" although that was with mixed results (it depended who ya got on the phone, some people had no luck and other people had their data start back up no problems.) You would need to sbf back to 621 and call from a separate phone, however. Another user (skreelink) theorized that it was merely the AUTH code that was being messed up, and suggested that (for those with a secondary smart phone) you just go onto VZW.com, switch out phones for your number, wait 15 minutes, then go back to the website and switch back to your DX. I'm not sure if anyone has had any success with the latter but I know the former worked for a handful of people (with others getting tech support who had no idea what they were talking about.) If you call and don't get someone knowledgeable, I'd just cross your fingers and call back another time and hope you get someone different.
link not working
anyone have updated link that works to download this?
yea i learned about the radio the hard way, but i found a quick fix... maybe...
If you flashed with windows and now cant get data if you have a old smartphone that is compatible with you plan just go online and switch devices and then switch them back. Saves from having to call verizon But some people may not have a extra
I am probably one of those people who will also need to use this alternative root method but I have a question -
I have been recently acquainted to this dilemma on my "new" Droid X. I mistakenly started downloading the .621 update on my Droid X . I quickly realized what was happening and pulled the battery before the download was complete. (data disabled on phone) . I turned off my router. I reinstalled the battery and turned off all of the data on the phone. I tried clearing the cache but get a message the triangle that it will try to download it again. I pulled the battery and do not plan on powering up the phone with any data connection until I can get some clarification on what to do . The phone has little value to me if it can't be rooted . Is there anyway to stop the train at this point and go back to .605 ( i believe that was the previous one) . - Thanks
bamx2 said:
I am probably one of those people who will also need to use this alternative root method but I have question -
I have been recently acquainted to this dilemma on my "new" Droid X. I mistakenly started the downloading the .621 update on my Droid X . I quickly realized what was happening and pulled the battery before the download was complete. (data disabled on phone) . I turned of my router. I reinstalled the battery and turned off all of the data on the phone. I tried clearing the cache but get a message the triangle that it will try to download it again. I pulled the battery and do not plan on powering up the phone with any data connection until I can get some clarification on what to do . The phone has little value to me if it can't be rooted . Is there anyway to stop the train at this point and go back to .605 ( i believe that was the previous one) . - Thanks
Click to expand...
Click to collapse
If you disabled the download you are still on .605.
Turn your phone on, quickly root it with Pete's Motorola Root Tools, install Titanium Backup and freeze the "2.3.3 Updater" application.
Afterwards, reboot your phone and you should be golden.
Sent from my DROIDX using Tapatalk
nfazzdar - Thanks for the reply . I did a factory reset and that got rid of the yellow triangle. I then rooted as you suggested and installed TiBu . I really is too bad that M and V are pullin this cr#p .
I am going to update the post and host the files. There is also some extra stuff i will put up for download.
For people who don't want to pay for Titanium Backup to have the freeze feature, use a free app called gemini app manager.
Good to know. I think that I will also install OTA Rootkeeper as well.
deboyz1014 said:
For people who don't want to pay for Titanium Backup to have the freeze feature, use a free app called gemini app manager.
Click to expand...
Click to collapse
using linux mint and have a ?
I've followed everything, I believe, but when I run the commands in linux everything runs then it says "reboot into bootloader" and just sits there. I've tried doing it in bootloader and get a message 'waiting on phone:failed Are you root? Can someone steer me in the right direction I gotta get this phone on another ROM. Thanks in advance.
BRANDENDEUCE said:
I've followed everything, I believe, but when I run the commands in linux everything runs then it says "reboot into bootloader" and just sits there. I've tried doing it in bootloader and get a message 'waiting on phone:failed Are you root? Can someone steer me in the right direction I gotta get this phone on another ROM. Thanks in advance.
Click to expand...
Click to collapse
Exactly the same problem here too.
Sent from my HTC Flyer P510e using XDA
landonotis said:
Exactly the same problem here too.
Sent from my HTC Flyer P510e using XDA
Click to expand...
Click to collapse
You need to either:
Code:
sudo su
./sbf_flash
or
Code:
sudo ./sbf_flash
Note: if using
Code:
sudo su
be sure that the terminal shows a "#" instead of a "$" after you input the command. This shows that you are root.
Sent from my DROIDX using Tapatalk
infazzdar said:
You need to either:
Code:
sudo su
./sbf_flash
or
Code:
sudo ./sbf_flash
Note: if using
Code:
sudo su
be sure that the terminal shows a "#" instead of a "$" after you input the command. This shows that you are root.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
When exactly do we need to input the code? I am assuming this is in terminal on linux?
BRANDENDEUCE said:
When exactly do we need to input the code? I am assuming this is in terminal on linux?
Click to expand...
Click to collapse
Sorry for not specifying, but you assume correctly.
Sent from my Transformer TF101 using Tapatalk
What roms can we use now?
Now that we have root and su on the droid x/milestone what roms are we able to flash? I know they can't be froyo based but do they now have to be related to the milestone roms, droid x, or both? I've tried a few and it's always an abort so I'm just needing some direction here...
BRANDENDEUCE said:
Now that we have root and su on the droid x/milestone what roms are we able to flash? I know they can't be froyo based but do they now have to be related to the milestone roms, droid x, or both? I've tried a few and it's always an abort so I'm just needing some direction here...
Click to expand...
Click to collapse
I believe this thread will be of help to you. =D
http://rootzwiki.com/index.php?/topic/21337-[ROMS]-Multi-ROM-Thread---Blur-Based-ROMs-for-those-on-.621/.604!
Sent from my DROIDX using Tapatalk 2 Beta-5
This worked great.
Any cwm kernels are we able to use?
Just wondering if we can flash custom kernels since we can do roms? If so any help would be appreciated.
Hi everyone,
I see more people than usual having issues with Rooting their Nexus 7 because of problems with booting into CWM recovery post flash - thought I would do a nice plain and easy to follow guide including instructions for booting into CWM recovery from a command point (thanks to Wugfresh for his Toolkit which is used in the guide).
http://www.androidnz.net/2012/07/how-to-root-your-nexus-7.html
Porting the full guide here, first the text because that is a simple cut n paste job, images to follow soon:
Before we get down into the nitty-gritty of the guide itself you should familiarise yourself with our usual disclaimers at the beginning of this post. I say this not because we don't care if you have problems, it's just that our capacity to trouble shoot is limited, and you shouldn't have embarked on an adventure to Root your device unless you did your due diligence first and had some understanding of what you were up to. One final disclaimer weasel-word at the off: the CWM recovery ports for the N7 are still a little iffy at this stage and even when taking appropriate steps to make it permanent you may only be able to boot into it via a command prompt window. Expect updates once fixes are available.
Disclaimers out of the way, here are the things you will need:
A Nexus 7, fully charged
A windows PC (the guide may work on macs via Windows virtual environments, but that isn't confirmed by us and is outside the scope of this guide)
The appropriate Nexus 7 USB drivers, there are several ways to get these:
Preferred method - Go to this thread at XDA-Developers and download and install the Root Toolkit there, which has an automated drivers installation included (this is preferred because it is what the guide that follows is based on because the Toolkit is probably going to be the most straightforward for the majority to use, and even if it fails and they have to resort to using command prompts that is more easily done from the Toolkit). Many many thanks to WugFresh at XDA for producing such a noob-friendly Rooting application - please consider making a donation to him here.
Install the Android SDK from here. Please note if you are already an SDK user that the Google USB drivers in the SDK have updated with the release of the Nexus 7 and Jelly Bean and you should update your drivers from within the SDK itself
Install the universal drivers from this post at XDA-Developers, but please make note of how you will need to adjust fastboot commands if you are using these drivers
Go to this post at XDA-Developers and install the USB drivers from there if you have no luck whatsover with any of the other methods
OK, now that you've got the Root Toolkit let's proceed (if you plan to do this with the SDK and command prompts then you should be advanced enough to follow the guide here, I did the first time and if you've done this stuff before the process is trivial).
Open the Root Toolkit, at the prompt to select your device scroll down to the bottom and select the Nexus 7 and the version number that corresponds to the firmware installed on your Nexus 7 (you can find this out in Settings --> About tablet --> Android version)
You'll be greeted with a screen that looks like this:
Click on Initial Setup and use the automatic driver installation facility from here to install USB drivers, it will check that ADB and Fastboot commands are working before dropping you back to the install window.
Turn on USB Debugging in the Nexus 7 by navigating to Settings --> Developer options. Turn on Developer options using the toggle in the top right hand corner, and then turn on USB debugging
Connect your Nexus 7 to your computer with the micro USB cable that came in the box. At this point it is vital that your computer recognises the Nexus 7 as a connected device, you will know if it has because a Nexus 7 "AutoPlay" window should pop up and ask you what action you want to take. If it doesn't show up, pull down the notification tray and press on the notification that says "Connected as a media device". A new menu will open and select the "Camera (PTP)" option. You should now get the AutoPlay window.
Head back to the Toolkit, and select "Unlock" from here, be aware that this will wipe your device (you might want to take a backup if you've already installed a lot of stuff on the device, that's just a button click away also in the Toolkit)
This will boot the device up to a screen giving you the option to unlock the bootloader, with "Yes" selected hit the power button. You'll see some text in the top left corner telling you it is unlocking the device, and then you will see the red "Locked" text toward the bottom of the screen change to "Unlocked". Moments later the device will reboot, and because it will have been wiped you will need to either set it up again or just skip past set-up and get back to the homescreen.
Once you're back onto the home screen, connect as you did before and take the same steps to turn on USB debugging and get the AutoPlay prompt to appear. Then go back to the Toolkit and select the Root option with permanent CWM recovery. All things going well the process will be fully automated from here, it will check that ADB and Fastboot are working, push the SU and CWM files to the device, boot the Nexus 7 into it's bootloader, flash CWM recovery to the device, and then reboot with Root privileges and a fresh new recovery permanently installed.
...or so the theory goes. Using this method I get Root, but CWM recovery is only accessible via command prompt, and I see others having the same problem. So...
Accessing CWM recovery:
In the Root toolkit go to Advanced Utilities by launching it here:
On the next screen select Launch CMD Prompt:
Once the command prompt appears type: ADB reboot recovery - the phone will boot into CWM recovery for you, so you can do things like make Nandroid backups, install zip files and so forth
Installing the 4.1.1 update post-Root and installation of CWM recovery:
Install OTA Rootkeeper by Supercurio from the Play Store here
Open the app once installed and grant it SuperUser privileges
In the app select "Protect Root", and then "temp unroot" the device
Download a zip of the 4.1.1 update here.
Copy it to the internal SD of the Nexus 7
Access CWM recovery as per the instructions above. In this version of CWM recovery you will navigate the options with the volume keys and press the power button to select an option - do that to navigate to "Install zip from SD card" and press the home button
On the next screen go to down "Toggle signature verification" and toggle it until it says "disabled" at the bottom of the screen (it should be set to default to disabled, but you lose like 5s making sure)
Go up to install zip, navigate to the zip file you downloaded in step one and install it
When the device reboots go to OTA Rootkeeper and restore Root, viola! You're done!
So, after all is said and done you should have a Rooted Nexus 7, running the 4.1.1 update, and with a custom recovery that can only be accessed via command prompt. Don't forget to shout WugFresh, the Toolkits developer, a coffee - make a donation here.
Would be nice if you posted that guide on this forum too.
Thanks for the guide.
Oooohh pictures
Caliyork said:
Oooohh pictures
Click to expand...
Click to collapse
You know, for the totally acopic
Will this work on the new Build number JRO03D? Or should I wait until he updates the toolkit?
Dillon610 said:
Will this work on the new Build number JRO03D? Or should I wait until he updates the toolkit?
Click to expand...
Click to collapse
No idea. You can simply downgrade to an older stock image using his Toolkit though and then follow the same process used in the guide to update to the latest build.
"Meh" at requirement #2:
A windows PC
Click to expand...
Click to collapse
I haven't ran Windows for years. I hope there's a way to do this with Linux (assuming a computer is even needed?)
I remember rooting my Optimus T with Z4 root... one click, bingo bango, done.
JaSauders said:
"Meh" at requirement #2:
I haven't ran Windows for years. I hope there's a way to do this with Linux (assuming a computer is even needed?)
I remember rooting my Optimus T with Z4 root... one click, bingo bango, done.
Click to expand...
Click to collapse
"Windblows"
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
mario24601 said:
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
Click to expand...
Click to collapse
There's a wiki on cyanogenmod.com that explains root.
mario24601 said:
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
Click to expand...
Click to collapse
Should be doable on mac in a windows virtual environment, which seems to be how most mac users are doing things here at XDA.
Actually looking for someone to write "for mac" guides, if anyone is up for that!
Hello guys as a developer when we make a rom, we have alot of requests from people which is fine and good. However, it comes to a point where we have so many requests for things, which we do not have time for in our free time. You have to remember we develop in our free time, and it is not a full time job, it is something we enjoy to do. Developers do expect requests, but not constantly, i will try to add features when people request it, but as explained above some of us, physically do not have the time, but some members annoy you by sending the same messages over and over again so the aim of this thread is:
If the Developers cannot do it, for whatever reason you should try it your self, and not just annoy them about it!
Now before we start there are things I want you to consider, before starting:
Code:
#include
*
* Your warranty is now void.
*By you using my Mods, Roms etc...
* I am not responsible for bricked devices, or dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Do not Start a thread with upcoming, or WIP because it is a waste of space, only post it when it is ready.
If you don't plan on continuing development, do not post it!
Do not steal other peoples work, ask them first, if they say no, build your own from a RUU or from source.
You can ask for help from other Developers, but do not annoy them over the issue they will help in their own time
Now the main things are out of the way, just one more thing if you are using lets say my ReVoluTioN RoM as a base if you just place a theme over it, and say it is your work it ISN'T! If you are just going to do that make a new theme thread instead, that way you will be credited, however, if you are adding extra code and your OWN custom HTC apps, or whatever that is maybe then yes it is worth making a new rom thread,ONLY IF IT IS YOUR WORK at implementing such code or new features.
ALSO if you are using a Existing rom as a base, give the developer credit for that and a link to their profile, to make sure you appreciate their work!
Now Onto the Tutorial:
In this guide, or new RoM builders it is a good idea to use an android rom kitchen called dsixda's Android Kitchen it is Compatible with Windows, Linux and Mac OS X.
Just a note about this kitchen:
The kitchen will not automatically turn you into a developer. A developer is someone who writes code or builds something from the ground up and understands exactly what goes on behind the scenes. The kitchen hides all that and puts a user-friendly interface above it. However, this may be the push that gets you into development in the future.
A little bit of prior UNIX command-line knowledge would be useful to get started with the kitchen, but the help guides should be enough for a newbie. Knowledge of command lines is always important if you ever want to get involved in Android or development.
However, just as a reference this is what the user interface looks like:
Main Menu:
1. Set up working folder from ROM
2. Add root permissions
3. Add BusyBox
4. Disable boot screen sounds
5. Add wireless tethering
6. Zipalign all *.apk files to optimize RAM usage
7. Change wipe status of ROM
8. Change name of ROM
9. Check update-script for errors
10. Show working folder information
Advanced Options
11 - Deodex files in your ROM
12 - Add task killer tweak for speed (stock ROM only)
13 - Add /data/app functionality
14 - Add Nano text editor + sysro/sysrw
15 - Add Bash (command shell)
16 - Add Apps2SD
17 - Add /etc/init.d scripts support (busybox run-parts)
18 - Add custom boot animation functionality
19 - Porting tools (experimental)
20 - Tools for boot image (unpack/re-pack/etc.)
21 - Unpack data.img
22 - Sign APK or ZIP file(s)
23 - Convert update-script or updater-script
24 - Miscellaneous optins / Plugin scripts
99. Build ROM from working folder
00. About/Update kitchen
0. Exit
Click to expand...
Click to collapse
In order to make the kitchen work you will need to be running one of the following operating systems:
Windows, this can be from Windows XP all the Way up to Windows 8
Linux/Unix, based system I use ubuntu 11.04 but 12.10 is good too
Mac/OSX, however it is recommended 10.4 or above.
First of all you need to download the kitchen from here: LINK
Once you have downloaded it follow the operating system guide of your choice below:
Windows, XP, 7 and 8:
There are currently three choices for windows users these include:
Cygwin, this is a UNIX command line environment for windows
Virtual Machine, this is a good choice but you need a powerful system, with a fast CPU and lots of RAM!
Use the Ubuntu WUBI installer, this basically creates a installation of ubuntu inside windows, and can be easily uninstalled.
WINDOWS OPTION 1: CYGWIN:
I currently use this option for my Rom compiling, but this is due to the fact I have a 2nd Gen Core i3, and 8GB of RAM if your CPU is not very fast I recommend the third option!
Lets get started then...
Fist of all download the Java JRE for windows, it is recommended you use this link.
Secondly, download the cygwin binaries from here.
Below you will find the additional steps required to get it working properly on your windows based system
Russell664's guide to getting cywin working for HTC Desire C
First of all run the downloaded Cygwin" setup.exe" you downloaded in the last step, but be sure to select the default installation paths, which are:
Install from the internet, to download required packages
install to C:\cygwin, to make it easy to access
Once that is done you will be greeted with the "select packages" screen, from there go to the search box and look for the following packages:
gcc, this is found under the "devel" section to select it click the + icon on the section it is found in. After this find this single package "IT HAS TO HAVE THE EXACT NAME OF gcc NOTHING ELSE! once you have found it click it and press "Skip" after to select more packages.
Once the above is done you will need to search for these packages:
perl, this is found under the section of "Interpreters"
cpio, this is found under the section of "Utils"
util-linux, this is found under the section of "Utils"
ncurses, this is found under the section of "Utils"
zip, this is found under the section of "Archive"
unzip, this is found uder the section of "Archive"
wget, this is found under the section of "Web"
Once this is done click next to begin downloading the required packages, this may take some time to do this.
When everything is downloaded, and installation had completed, there will be a new cygwin desktop icon, once this is clicked a linux terminal will be displayed.
Once this terminal is displayed, we need to next configure "java" do do this follow these simple steps:
First of all type "java" (do it without the quotes) if the terminal says "command not found" go on the the next step. However if it dooes not say that skip these following steps for setting up java
To fix the no command found follow these steps:
First, make a backup of your .bash_profile file in case you make a mistake later in this procedure.
Enter the following in the terminal:
cp .bash_profile .bash_profile.backup
Next, find out where your java.exe file is and run the appropriate command to add it to your Cygwin path.
For example, my java.exe is found under C:\Program Files\Java\jre7\bin, so I had to type:
echo "PATH=/cygdrive/c/Program\ Files/Java/jre7/bin:\${PATH}" >> .bash_profile
Modify the command above so that it matches the actual path to your installed Java.
Remember to add a "\" character before any spaces in your path, as shown above.
Type the following so that the file gets loaded (you only need to do this once):
source .bash_profile
There should not be any errors displayed if successful.
(Otherwise, if you made an error in the .bash_profile file, restore your backup by typing: cp .bash_profile.backup .bash_profile, and then try the procedure again)
If done correctly, then when you type 'java' it should display some help information.
Once this is finished you are now setup to use the kitchen on your Windows based computer!
Click to expand...
Click to collapse
WINDOWS OPTION 2: VIRTUAL MACHINE:
Before considering this option for building Roms in this environment reads the Pros and cons first.
Advantages of using virtual box:
The size of the installation doesn't have to be predetermined. It can be a dynamically resized virtual hard drive.
You do not need to reboot in order to switch between Ubuntu and Windows.
The virtual machine will use your Windows internet connection, so you don't have to worry about Ubuntu not detecting your wireless card, if you have one.
The virtual machine will set up its own video configuration, so you don't have to worry about installing proprietary graphics drivers to get a reasonable screen resolution.
You always have Windows to fall back on in case there are any problems. All you have to do is press the right Control key instead of rebooting your entire computer.
For troubleshooting purposes, you can easily take screenshots of any part of Ubuntu (including the boot menu or the login screen).
It's low commitment. If you later decide you don't like Ubuntu, all you have to do is delete the virtual hard drive and uninstall VirtualBox.
Disadvantages of using virtual box:
In order to get any kind of decent performance, you need at least 512 MB of RAM, because you are running an entire operating system (Ubuntu) inside another entire operating system (Windows). The more memory, the better. I would recommend at least 1 GB of RAM.
Even though the low commitment factor can seem like an advantage at first, if you later decide you want to switch to Ubuntu and ditch Windows completely, you cannot simply delete your Windows partition. You would have to find some way to migrate out your settings from the virtual machine and then install Ubuntu over Windows outside the virtual machine.
Every time you want to use Ubuntu, you have to wait for two boot times (the time it takes to boot Windows, and then the time it takes to boot Ubuntu within Windows).
If you still wish to use the virtual box route follow these steps to get it installed:
Installation of virtual box
The first thing you have to do is obtain VirtualBox. First of all visit the VirtualBox website's download page and install it the same way you would any normal Windows program.
Once Virtualbox is installed, launch it from the windows start menu, after this click New to create a new virtual machine. Once the wizard comes up press the next button as seen below:
{
"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"
}
You can call the machine whatever you want. If you're installing Ubuntu, it makes sense to call it Ubuntu, I guess. You should also specify that the operating system is Linux.
VirtualBox will try to guess how much of your memory (RAM) to use for the virtual machine. If you have 1 GB or less of RAM, I would advise you stick with the recommendation. If, however, you have over 1 GB, about a quarter your RAM or less should be fine. For example, if you have 2 GB of RAM, 512 MB is fine to allocate. If you have 4 GB of RAM, 1 GB is fine to allocate. If you have no idea what RAM is or how much of it you have, just press next.
If this is your first time using VirtualBox (which it probably is if you need a tutorial on how to use it), then you do want to Create new hard disk and then click Next.
Click next at this section, don't change anything!
A dynamically expanding virtual hard drive is the best option, because it'll take up only what you actually use. I have come upon weird situations, though, when installing new software in a virtualized Ubuntu, in which the virtual hard drive just fills up instead of expanding. So I would actually recommend picking a Fixed-size storage.
Ubuntu's default installation is less than 3 GB. If you plan on adding software or downloading large files in your virtualized Ubuntu, you should tack on some buffer.
Click Create and wait for the virtual hard drive to be created. This is actually just a very large file that lives inside of your Windows installation.
Then this will show up:
The next thing to do to make the (currently blank) virtual hard drive useful is to add the downloaded Ubuntu disk image (.iso) boot on your virtual machine. Click on Settings and Storage. Then, under CD/DVD Device, next to Empty, you'll see a little folder icon. Click that.
Select the Ubuntu .iso you downloaded earlier.
Once the image is selected, click ok.
You may get a bunch of random warnings/instructions about how to operate the guest operating system within VirtualBox. Read those, and then you may also want to mark not to see those again.
Wait for Ubuntu to boot up.
Once it's started up, just follow the regular installation procedure as if you were installing Ubuntu on a real hard drive (instead of a virtual one).
Afterwards, in order to use your virtualized installation (instead of continually booting the live CD), double-check that the CD/DVD Device entry is Empty again.
Now you have ubuntu installed on virtualbox! Now on the the next part, making the kitchen work.
WINDOWS OPTION 3: WUBI INSTALLER:
Before you start this download the ubuntu iso image from the website, and burn it to a cd!
You may want Linux but think Virtual Box is too much effort to install, or it runs too slow for you, then you can try the 'Wubi' installer from Windows. This method will install Ubuntu Linux inside a file in your Windows operating system and will boot from it.
Use this method only as a last resort, as it will modify your PC's boot loader and may also require some hunting for video drivers if you're not lucky. The benefit to this method is that it runs the kitchen super fast. The downside is that setting it up may require some technical expertise and Linux experience! If it's not working out for you, just go back to Windows and run the Wubi installer again to uninstall.
You can find lots more info about Wubi in YouTube and Google search. In the meantime, here is a summary of the required instructions:
First, download and install the Wubi installer. A good size to allocate for Ubuntu would be 20 GB (this is for all your roms and updates)
When it finishes installing, the PC will reboot.
Select Ubuntu from the boot selection menu.
Notes:
NOTE: If the screen remains blank afterwards and never shows the login screen, then you have a video driver issue. You will need to reboot, and then at the Ubuntu boot options, press 'e' to edit the command line. To force the generic video drivers you will need to add something like this: nomodeset (Just Google it)
When you arrive at the desktop, configure your Wi-Fi connection by clicking on the seashell-shaped icon at the top right section of the screen.
Follow the instructions in the next section of this FAQ ("Ubuntu Linux") for installing Java. That should be all you need to do. I really hope this helped you out.
NOTE: If you had to do the video workaround earlier on, then you'll need to edit /etc/default/grub and change the appropriate lines so that it always boots up in this mode and so you won't need to edit it every time in the boot menu. i.e. Open up an xterm and then type sudo vi /etc/default/grub, modify the file, then type sudo update-grub. Again, Google is your friend.
Ubuntu 11.04 to 12.10:
UBUNTU NATIVE INSTALL:
Before you follow any of these step mentioned in this ubuntu section, you NEED to have it installed either on a physical drive (Partition) or inside a virtual machine. If you do not meet the requirements you need to first install ubuntu, which will be mentioned above this post.
Okay these next steps of setting up the running requirements for the kitchen on linux are very easy compared to the windows setup, the required steps are:
First open up the terminal windows, the buttons to quickly do this are:
Code:
CTRL + ALT + T
If you are using the 64-bit version of ubuntu, type the following into your terminal:
Code:
sudo apt-get install ia32-libs
Now if you go onto the ubuntu market place, a shortcut is found on the sidebar.
Once you are in to market, in the search bar type "Java"
There will be many choices which come up, but you need to install the package name of:
Code:
OpenJDK Java Runtime
This option is usually displayed at the top of the search result.
Once the Java has installed, type "java -version" If installed correctly it will bring back some information into the terminal.
Code:
java -version
If you are using Ubuntu in a virtual machine, you NEED to follow these extra steps to complete installation.
This thread will be updated as soon as possible, i need to get other stuff done so hang tight.
Configuring DSiXDA's kitchen
Just to note the HTC Desire C is not compatible with kitchen, there is a work around that works perfectly so follow the steps further down the thread, these are the officially supported devices for a reference:
Remember this is a reference, and is extracted from DSiXDAs thread itself.
Code:
Acer Liquid
Dell Streak 7
HTC Amaze 4G
HTC Aria / Liberty
HTC Desire
HTC Desire HD / Inspire 4G
HTC Desire S
HTC Desire Z / Vision / T-Mobile G2
HTC Dream / G1
HTC Droid DNA
HTC Droid Eris
HTC Evo 3D
HTC Evo 4G
HTC Evo 4G LTE
HTC Evo View 4G (untested)
HTC Evo Shift 4G
HTC Flyer (untested)
HTC HD2
- Use NAND ROM method (Please follow this thread for details)
HTC Hero / G2 Touch
HTC Incredible
HTC Incredible 2
HTC Incredible S
HTC Legend
HTC Magic / myTouch 3G
HTC myTouch 3G Slide
HTC myTouch 4G / Glacier
HTC Nexus One
HTC One S
HTC One X
HTC One X+ (AT&T and International versions)
HTC One XL
HTC One V (including CDMA version)
HTC Rezound
HTC Sensation
HTC Tattoo / Click
HTC Thunderbolt
HTC Wildfire / Buzz
HTC Wildfire S
Huawei Ideos X6
- Please follow this thread for details
Huawei U8100/U8110/U8120/U8150/U8160/U8180/U8650
Huawei U8220 / T-Mobile Pulse
LG Ally
LG GT540 Optimus
LG Nexus 4 (mako)
LG Optimus 2X (P990)
LG Optimus Black
- Please follow this thread for details
LG Optimus G2X (P999)
LG P500
- Please follow this thread for details
LG Shine Plus
LG Vortex
Micromax A60
Motorola Atrix (unconfirmed)
Motorola CLIQ / CLIQ XT
Motorola Droid
Motorola Droid Bionic
- Please follow this thread for details
Motorola Milestone (unconfirmed)
- You may need to remove the boot.img before building
Samsung Galaxy Ace 2 - GT-I8160(L/P)
Samsung Galaxy Mini
Samsung Galaxy Nexus (untested, 'maguro' and 'toro' versions only)
Samsung Galaxy Note
- GT-N7000 - please follow this thread for details
- SGH-I717 - Please follow this thread for details
Samsung Galaxy Note 2
- Supported for:
-- Sprint variants - SPH-L900 - Please follow this guide
-- T-Mobile variants - SGH-T889(V) - Please follow this guide
-- Verizon variants - SCH-I605
(unconfirmed - see this equivalent guide)
-- International variants - GT-N7100/N7105(T)/N7108
(unconfirmed - see this equivalent guide)
-- AT&T/Rogers/Bell/Telus variants - SGH-I317(M)
(unconfirmed - see this equivalent guide)
-- US Cellular variants - SCH-R950
(unconfirmed - see this equivalent guide)
Samsung Galaxy R GT-I9103
Samsung Galaxy S (GT-I9000 and most variants)
- Please follow this thread for details
Samsung Galaxy S Plus (GT-I9001)
- Please follow this thread for details
Samsung Galaxy S2
- Supported for:
-- GT-I9100 and Exynos CPU variants - Please follow this thread for details
-- Qualcomm/LTE variants
(AT&T Skyrocket, Rogers, Telus, T-Mobile, Bell HD LTE SGH-I757M,
Telstra GT-I9210T)
- Please follow this thread for details
Samsung Galaxy S3
- Supported for:
-- T-Mobile/Mobilicity/Wind variants: SGH-T999(V) - Click here for a guide
-- AT&T/Rogers/Bell/Telus variants: SGH-I747(M) - Click here for a guide
-- Verizon variants: SCH-I535, SCH-R530U - Click here for a guide
-- Sprint variants: SPH-L710, SCH-L710 - Click here for a guide
-- International variants: GT-I9300(T) - Click here for a guide
-- International LTE variants: GT-I9305(T) - Click here for a guide
-- Korean variants: SHV-E210K/L/S and SHW-M440S (unconfirmed)
Samsung Galaxy W (GT-I8150)
- Please follow this thread for details
Samsung Nexus S / Nexus S 4G
Sony Ericsson Xperia 2010 devices (X10 / X10 Mini / X10 Mini Pro)
- Can only build ROM without boot.img (please follow this thread for details)
Sony Xperia 2011-12 devices, specifically:
- TX, P, U, Sola
- Active, Arc, Arc S, Mini, Mini Pro, Neo, Neo V, Neo L,
Play, Ray (follow steps below):
- Can only build ROM without boot.img
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
- OR If using Nandroid backups: Rename system.yaffs2.img to system.img
- Use this system.img in kitchen's original_update folder
- WARNING - If using a ROM made from system.sin (not Nandroid), it
is recommended to flash from the temporary (fastboot) Clockwork
Recovery, rather than the regular Clockwork Recovery, otherwise
device may not boot (possibly because custom recovery files in
system folder are not added to ROM? e.g. recovery.tar).
ZTE Blade / Orange San Francisco
Now for the compatibility fix details
There are one of two ways you can do this, these being:
Do the file editing manually, I will explain it step by step for you.
Or be lazy and use my provided file at the bottom if this post.
If you choose to learn a little bit more from this tutorial, you may want to go the manual route. That is all well and good, however, follow these instructions precisely, or you could cause a lot of problems with your phone. If you don't feel safe doing it manually, use my file below to make sure that does not happen.
Here we go...
Option 1:
By this step your kitchen should be downloaded, and confirmed that it does in fact start up, if it does your set to go and follow these remaining steps.
In your kitchen directory, you will find a tools folder you want to Click that and then the Edify_defs folder after that, the file structure should look like this:
Code:
C:\cygwin\home\yourusername\Kitchen\tools\edify_defs
This is on a Windows based system.
Code:
\home\yourusername\Kitchen\tools\edify_defs
This would be on a linux based system, it will be very similar.
Once you are in this folder save a file called "Golfu". (You can do this by saving the file as a blank text document, but save it as *file insted of .txt)
Get a recovery.img (Yes the one used for flashing your recovery, or a stock one) And save it in the "Original_update" folder, the file structure should look like so:
Code:
C:\cygwin\home\yourusername\Kitchen\Original_update
This is on a Windows based system.
Code:
\home\yourusername\Kitchen\Orginal_update
This would be on a linux based system, it will be very similar.
Once you have done that follow these menus through the kitchen:
Code:
Advanced --> Tools for boot image --> Extract from boot.img/recovery.img in any folder.
Once this is done, once again go to the Orginal_update folder and you will find the extracted recovery.img, open it's ramdisk folder and Follow this file structure:
Code:
/system/etc/recovery.fstab or /etc/recovery.fstab
After you have found this file open it with a text editor. (Due to this being code, you will want it in a neat fashion, this is why I recommend NOTEPAD++ for windows user, linux user you are fine with the standard one included)
When looking at the code you are looking for these lines:
Code:
sys_mnt=\/dev\/block\/[B]mmcblk0p25[/B]
cache_mnt=???
data_mnt=???
sdcard_mnt=???
However you are only really looking for the system block number, you can add data etc later on manually though updater scripts it is much easier. Remember you are looking for this line highlighted in bold, you can just copy that number down, it is the same for every HTC Desire C.
The last step is too add these lines you have found, to the "golfu" file you created, basically you want it to look exactly ike the code below, copy and paste it if you wish:
Code:
change_mnt=yes
param1=ext4
param2=EMMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p25
cache_mnt=???
data_mnt=???
sdcard_mnt=???
Now the configuration is now done of the kitchen, now you can move onto how to build your Rom from a RUU, or from an exsting rom such as Revolution, or nameless.
Option 2:
As said in option 1 you need to make sure you Rom kitchen starts up and shows the menu, this means it is working. If it does not do that you have done something wrong.
Basically you need to download this attached file, unzip it and place it in the following directories. (Make sure you read to notes at the end of the directory code, so you know what operating system it is aimed at)
Move the file here:
Code:
C:\cygwin\home\yourusername\Kitchen\tools\edify_defs\thefileyoudownloaded
This is on a Windows based system.
Code:
\home\yourusername\Kitchen\tools\edify_defs\thefileyoudownloaded
This would be on a linux based system, it will be very similar.
That is basically it, now you need to read below, on how to actually build your roms.
Reserved for FAQ
Great Russell! I'm glad to see a guide of this nature within our forum, it will certainly help to promote further development on our device. There are a lot of guides available concerning this topic, however none that have anything specific to the Desire C, I look forward to seeing the completed guide!
First post updated, nearly finished, the windows section is finished, the ubuntu section needs a little bit of work. However this guide is ready to use for people who plan on using windows.
Good luck guys.
russell664 said:
First post updated, nearly finished, the windows section is finished, the ubuntu section needs a little bit of work. However this guide is ready to use for people who plan on using windows.
Good luck guys.
Click to expand...
Click to collapse
Thankyou russell I plan on following this ...once I get the time . I'm out of thanks again this morning which is weird as I havn't used any today . I will spam you later :good:
Thanks Rich
The thread should be complete tomorrow, with the ubuntu section.
Sent from my HTC Desire C using xda premium
I can't get Ubuntu installed, the installation freezes at about 75%. Tried using Wubi and real installation on a partition.
I suggest you to use Ubuntu on dual boot. Boot Ubuntu from stick.
I know but that is just a demo
Sent from my HTC Desire C using xda app-developers app
You can install it from the demo, let it load to the desktop. There is a icon saying install ubuntu on the desktop, click it and install ubuntu. You can do this from a USB stick or cd
Good luck.
Sent from my HTC Desire C using xda premium
That's what I did, installation doesn't complete but freezes after about 75 per cent
Sent from my HTC Desire C using xda app-developers app
Could you take a picture of the screen?
Are you installing on a VM, and if so how much RAM have you allocated to you VM, and how much does your system have?
Sent from my HTC Desire C using xda premium
Strange, okay if you are using a VM my recommendation is to use 2Gb of ram, if you have 4GB in your computer. However installing linux is still your best option. Now if ubuntu does not work for you, you can try linux mint. This already has java installed, and can run the kitchen out of the box, all you need to do is make it comparable with our phone.
The main thing what I think could be happening is lack of ram or possible corrupt image of ubuntu, try the linux mint approach and update us with your results mate.
Best of luck.
Sent from my HTC Desire C using xda premium
Not using a vm my computer wouldn't be able to run smoothly it's pretty crap
I'll re download the iso and try again, if that doesn't work ill try Linux mint
Sent from my HTC Desire C using xda app-developers app
update: still didn't work, downloading linux mint right now...
does anybody know a way to install that awesome looking unity interface on mint?
Use the version of ubuntu from this link http://forum.xda-developers.com/showthread.php?t=2152398
It already has most of the packages required for building a rom preinstalled
Unity awesome? never KDE is much better im my opinion.
Yes you can install it with the command:
Sudo apt-get update
Sudo apt-get ubuntu-desktop
That will install unity for you.
nikhil16242 said:
Use the version of ubuntu from this link http://forum.xda-developers.com/showthread.php?t=2152398
It already has most of the packages required for building a rom preinstalled
Click to expand...
Click to collapse
Staahp!!! xD
So many choices... my linux mint download only just completed and you posted that xD
will look at it later
Hi all,
First of all I would like to say how awesome this site has been. I knew nothing about my first venture into rooting a phone so this has been a learning experience.
Right - now for those who have a HTC Incredible S and are looking to breathe some new life into this device (like I have purely for giving to my son to watch YouTube - so no calling, texting, etc) this is what I did (all information sourced from various threads on XDA and some external links as well):
1. Read through the following guide: {[GUIDE]} HTC Incredible S Unlock Bootloader, flash recovery, Root, S-OFF. Note: It appears that it is no longer possible to get S-OFF due to the Revolutionary site no longer existing. So you will have to stop at the end of Step 5.
2. Assuming you are using Windows 10 I had to do the following in order to successfully connect to the HTC Incredible S using fastboot/adb:
1. Install HTC Sync.
2. Once you have done this go to Control Panel -> Programs and Features then uninstall the HTC Sync program (the one with the sync icon) but leave the drivers etc installed.
3. Then download and install the Android SDK and update it as per the instructions https://www.andreszsogon.com/using-android-8-and-9-emulators-without-android-studio/
4. You then want to create a folder called C:\Android.
5. Now browse to the C:\Users\<username>\AppData\Local\Android\android-sdk\platform-tools folder and copy the adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll files to C:\Android.
6. Now make the changes to the registry. Put this in a *.reg file (with your texteditor and rename the file to e.g. import.reg
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\0BB40FF00100]
"SkipBOSDescriptorQuery"=hex:01,00,00,00
Then import that import.reg via regeditor (as admin) into your registry. Then reboot your computer.
7. Restart your PC.
8. If you are unlocking the bootloader for your HTC device - put the "fastboot.exe" file from the HTC Dev webpage (https://www.htcdev.com/bootloader/) here as well. Also put any recovery mods, roms, etc here as well.
9. Make sure - if you can that - that you boot your phone normally and go into the settings and turn USB Debugging "ON" and Fastboot "Off" (the second one is you can get to the bootloader on your phone using the appropriate key combinations). You may also want to turn on the option to install apps from unknown sources. Power off your phone.
10. Now turn on your phone into Fastboot mode then connect it to the PC it should change to Fastboot USB.
11. Open a command prompt as administrator and browse to C:\Android. You should now be able to use the Fastboot command.
Click to expand...
Click to collapse
3. You should now be able to complete steps 2 - 5 from the guide.
4. For my HTC Incredible S I went with the following:
Clockwork Mod Recovery 5.0.2.0 (download it here: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-vivo.img)
Root obtained using SuperUser 3.1.3 (filename is Superuser-3.1.3-arm-signed.zip from here https://forum.xda-developers.com/showthread.php?p=39959468#post39959468)
Installed Unofficial CyanogenMod 10.1 for vivo (download it here: https://forum.xda-developers.com/showthread.php?t=2127020) [EDIT: You may or may not need to also install this patch for it as well https://forum.xda-developers.com/showpost.php?p=38765296&postcount=493]
Installed Google Apps (Gapps) (download it here: https://www.teamandroid.com/gapps/ Just scroll down until you get to Gapps CyanogenMod 10.1)
Thanks all!
Hey bud, try https://web.archive.org/web/20150601030338/http://revolutionary.io/
Nonverbose said:
Hey bud, try https://web.archive.org/web/20150601030338/http://revolutionary.io/
Click to expand...
Click to collapse
Hi. Yeah, tried that.
While you can download the required zip file it doesn't let you generate the beta key required.
How about the solution posted here?
https://forum.xda-developers.com/showpost.php?p=63060287&postcount=11
Was wondering if it's easy to root or unlock the bootloader on the new chromecast with google tv
Sent from my A0001 using Tapatalk
We should wait for a custom recovery first. But you might loose all the DRM keys when the recovery partition is flashed. So choose wisely.
The 4gb storage is putting me off from buying it, if it was possible to root it to use apps2sd (or link2sd) to install entire apps on external storage, it would be a good upgrade to my fire tv stick 4k (vulkan support for emulators, slightly more powerful processor and better gpu drivers, as well as gapps installed from the start)
dictorclef said:
The 4gb storage is putting me off from buying it, if it was possible to root it to use apps2sd (or link2sd) to install entire apps on external storage, it would be a good upgrade to my fire tv stick 4k (vulkan support for emulators, slightly more powerful processor and better gpu drivers, as well as gapps installed from the start)
Click to expand...
Click to collapse
Isn't installing on external media a built in option? And forcing it for all apps in in the developer options.
xnamkcor said:
Isn't installing on external media a built in option? And forcing it for all apps in in the developer options.
Click to expand...
Click to collapse
Yeah you are right! This works without Problems.. you only need an USB C Hub with SD support.. look here: https://forum.xda-developers.com/android-tv/chromecast/chromecast-google-tv-ethernet-usb-hub-t4176725
I use an USB C Hub with Gigabit Ethernet and 128GB SD Card. It works nice!
airwolf1544 said:
Yeah you are right! This works without Problems.. you only need an USB C Hub with SD support.. look here: https://forum.xda-developers.com/an...hromecast-google-tv-ethernet-usb-hub-t4176725
I use an USB C Hub with Gigabit Ethernet and 128GB SD Card. It works nice!
Click to expand...
Click to collapse
How did you get the SD card working? I put in a 64GB in mine, but wasn't working until I discovered that the CCwGTV only supports FAT32 which has a max volume size of 32GB. I even tried creating two volumes of 32, but in the end the only thing that worked was just using 32GB of the 64GB as a single FAT32 volume.
EsotericCleric said:
How did you get the SD card working? I put in a 64GB in mine, but wasn't working until I discovered that the CCwGTV only supports FAT32 which has a max volume size of 32GB. I even tried creating two volumes of 32, but in the end the only thing that worked was just using 32GB of the 64GB as a single FAT32 volume.
Click to expand...
Click to collapse
I've succeeded to format large USB sticks (64GB) on FAT32 with Rufus portable (free software). SD card is working only in an USB stick adapter on my hub.
Hi,
Did anyone succeed to write files on a second USB stick?
I have the first USB stick formatted to extend the storage, and a second one as an external USB storage.
The second stick can be read or write on a PC, can also be (only) read on Chromecast with Google TV, but cannot write on it on chromecast. It's a write permission restriction there.
There is an ADB solution or similar?
Thanks,
Any sign of being able to root the Chromecast with Google TV yet?
@Twotoneeddy It sounds like we have to wait for TWRP to be ported to support Android11, once that is done then you can have full Recovery functionality and Root (unless someone wants to port fastbootd like what we did in OP8T). Atm A10 just got support recently from the TWRP Team (https://twrp.me/site/update/2020/12/31/twrp-3.5.0-released.html).
**Edit**
Didn't realize device was A10, figured due to release time frame that it would have been released w/A11.
But the basics still stand, there is much more work to be done to get root (we can argue chicken or egg all we want but it doesn't change the end answer just the how you got to the answer).
card13 said:
@Twotoneeddy It sounds like we have to wait for TWRP to be ported to support Android11, once that is done then you can have full Recovery functionality and Root (unless someone wants to port fastbootd like what we did in OP8T). Atm A10 just got support recently from the TWRP Team (https://twrp.me/site/update/2020/12/31/twrp-3.5.0-released.html).
Click to expand...
Click to collapse
Dude, you're putting the cart before the horse. If you don't have root or equivalent*, you can't boot a twrp, assuming you even wanted to.
Technically, you need the ability to boot an unsigned boot/recovery image, which includes the ability to feed that unsigned image into the device. If you can do that, then take the original boot image, install magisk on it, feed it in, and tell it to boot it. There's your root, no twrp required.
EDIT:
card13 said:
**Edit**
Didn't realize device was A10, figured due to release time frame that it would have been released w/A11.
But the basics still stand, there is much more work to be done to get root (we can argue chicken or egg all we want but it doesn't change the end answer just the how you got to the answer).
Click to expand...
Click to collapse
This isn't a chicken and egg problem AT ALL. twrp is just a custom recovery image. Without already having root or equivalent, there is NO WAY TO RUN IT.
Let me give you a simple example of the process as it works on a pixel phone;
1) Developer options --> OEM unlocking
2) adb reboot-bootloader
3) fastboot flashing unlock
4) fastboot [boot|flash boot] boot-magisk.img
* where boot-magisk.img is the boot.img found in the factory package, after being modified by magisk.
Steps 1-3 are the barrier for this device. twrp won't help you with them because you need to COMPLETE STEP 3 before you can install or boot twrp, and by the time you've completed STEP 3, you've already achieved the goal.
There are 2 ways to get there;
1) figure out how to accomplish steps 1-3.
2) figure out a privilege escalation exploit, either through Android, or through recovery, or whatever else you can come up with.
Here is a very simple question that could help start this process off; IS THERE ANY WAY TO BOOT INTO FASTBOOT?
Delete
has anyone tried to boot off sd card? possibly running emuelec?
The real reason to root this thing has to be to bring support for HD audio passthrough.
Apparently the Amlogic S905D3G used to have HD audio passthrough on older firmware. If someone could figure out how to reenable it it would be the perfect streamer.
You can find twrp builds for the S905 but they are for older versions of android
blaze2051 said:
has anyone tried to boot off sd card?
Click to expand...
Click to collapse
wanna know if you found the answer.
What's the answer
Stricted and I just wrote a bootloader unlock exploit - for those of you with compatible units, enjoy: https://www.xda-developers.com/chromecast-with-google-tv-bootloader-unlock-exploit/
npjohnson said:
Stricted and I just wrote a bootloader unlock exploit - for those of you with compatible units, enjoy: https://www.xda-developers.com/chromecast-with-google-tv-bootloader-unlock-exploit/
Click to expand...
Click to collapse
Not to necromorph an old thread, but I was curious to know by chance if it would be possible to apply your root method onto a Chromecast with Google TV that has been automatically updated to Android 12 even though it was manufacture 12/2020? After the update, some functionality I was used to that was present before the update occurred has been neutered and the OS sound effects are ruined and there's noticeable crackling/pop. Now I'm actively searching for a way to root my device so I can downgrade to either Android 11 or Android 10.
urbanman2004 said:
Not to necromorph an old thread, but I was curious to know by chance if it would be possible to apply your root method onto a Chromecast with Google TV that has been automatically updated to Android 12 even though it was manufacture 12/2020? After the update, some functionality I was used to that was present before the update occurred has been neutered and the OS sound effects are ruined and there's noticeable crackling/pop. Now I'm actively searching for a way to root my device so I can downgrade to either Android 11 or Android 10.
Click to expand...
Click to collapse
Nope. Locked up tight.