Related
This little gem of a phone is a tough little thing to custom install apps on, but that didn't stop the Coburn from being able to get busybox installed.
Therefore, introducing Busybox for your HTC Click/Tattoo!
FOLLOW THIS TUTORIAL CAREFULLY. This guide may brick or NOT brick your Tattoo (most likely the latter), however I cannot assure you that it's 100% fail proof. I have installed it successfully. IN OTHER WORDS: THIS IS NOT FOR THE FAINT HEARTED! IF YOU DO NOT KNOW WHAT 'FLASH','ADB' OR 'HACK' MEANS, PLEASE DO NOT CONTINUE.
Requirements:
1 HTC Tattoo (The Victim)
1 MS Windows Powered Computer (I used Win7 64Bit)
1 HTC Tattoo -> USB Cable (Included with phone... Well, it was in the box).
Download the package attached to this post. Extract all files to a directory like C:\BUSYCLICK . (Actually, please extract them there).
Installation
Connect your Tattoo to your phone, make sure USB Debugging is enabled (Settings -> Applications -> Development) and sit back. Windows should say "New Hardware! OMG!" and ask "What is this piece of tech?" (aka New Hardware Install Wizard). On XP, allow to search Windows Update. On Vista/7, I'm going to have to get back to you on that. The installed driver will be like "HTC Dream blah blah blah ADB Interface" or something. Odd why it says it's a HTC Dream...
Anyway, go to the folder where you extracted the files, and run the Installation.bat file. It's the one that says "Installation" With the cogs icon.
You'll get a DOS Prompt and some text, PAY ATTENTION! My installer will hold your hand and explain what's happening. Should any errors occur, you may be out of space on your Tattoo's internal memory or something. If you do get errors, please post them here! I'll try to fix them for you guys and girls.
Post-install tasks
When complete, run the TestBusybox.bat script in the same folder where you extracted the BusyBox files, and you should get some output. If not, busybox failed to install... Let me know what the error is and I'll try to fix it.
Notes:
You can use the busybox commands in /data/local/bin from "adb shell" or a terminal emulator on the phone itself... /data/local/bin/sh DOES NOT work from adb shell, I don't know why. It will work using a terminal emulator. Try "/data/local/bin/free" and such for some memory read outs, etc, etc.
Feel free to love/like/hate/kill/shoot my work, you can expect to see ROMs and the like in the near future as I love hacking devices.
Cheers,
Coburn64
Ok busybox installed normally...
Do i have root acces with busybox now? I dont see su...
C:\Busybox>adb shell /data/local/busybox ls /data
ls: can't open '/data': Permission denied
I do see /data/local and under tho... including ../bin and ../rights but dont see any use of it...
Coburn Hi, this is a step closer to being root
can be root in busybox?
chmod command does?
thx
Code:
benno.id.au/blog/2007/11/14/android-busybox
chmod command is useless without su...If only su worked
Installed and worked fine, can run busybox but:
it runs with shell privileges
setting setuid bit doesn't solve, because I can chown to root
Do I miss something?
Thanks Really appreciate your work!
Do you have to install the new RUU Click HTC WWE 1.63.405.1 WWE test signed NoDriver first?
coolbits said:
Code:
benno.id.au/blog/2007/11/14/android-busybox
chmod command is useless without su...If only su worked
Click to expand...
Click to collapse
I know friend!
I asked the chmod without adb, or if they could use the chmod as root from the busibox console
leon1984 said:
I know friend!
I asked the chmod without adb, or if they could use the chmod as root from the busibox console
Click to expand...
Click to collapse
All this does is allows you to run more commands from the shell in Android, whereas the standard shell doesn't have many commands built-in. Could be used in conjuction with a root hack.
One step more, but nothing to do with root
I'm starting to believe that Click will never have a root method working because its underused compared with other android devices
MiSSigNNo said:
One step more, but nothing to do with root
I'm starting to believe that Click will never have a root method working because its underused compared with other android devices
Click to expand...
Click to collapse
The next Linux kernel root vulnerability (which works on the Tattoo) should bring us root, as well as other Android devices such as the Eris.
coolbho3000 said:
The next Linux kernel root vulnerability (which works on the Tattoo) should bring us root, as well as other Android devices such as the Eris.
Click to expand...
Click to collapse
What's the new root vulnerability? Is it something that was just discovered?
coolbho3000 said:
The next Linux kernel root vulnerability (which works on the Tattoo) should bring us root, as well as other Android devices such as the Eris.
Click to expand...
Click to collapse
Ok, where to find more info about this? :S
coolbho3000 said:
The next Linux kernel root vulnerability (which works on the Tattoo) should bring us root, as well as other Android devices such as the Eris.
Click to expand...
Click to collapse
I was able to install Busybox on my phone successfully. But the problem is I don't know what it's for. Would anyone be kind enough to post a link or a tutorial for this? Thanks.
sheik_yerbouti said:
I was able to install Busybox on my phone successfully. But the problem is I don't know what it's for. Would anyone be kind enough to post a link or a tutorial for this? Thanks.
Click to expand...
Click to collapse
Busybox just allows you to use more features at the adb shell command line. So, yeah. Heh.
You lost me at 'adb shell command line'. Is that some command line provided by the Android SDK?
sheik_yerbouti said:
You lost me at 'adb shell command line'. Is that some command line provided by the Android SDK?
Click to expand...
Click to collapse
Sorry if I lost you. Let me sum it up: It's a 'feature pack' for Android Developers, which could be used in conjunction with rooting tools.
Coburn64 said:
What's the new root vulnerability? Is it something that was just discovered?
Click to expand...
Click to collapse
zenthought.org/content/file/android-root-2009-08-16-source
This is linked in the other thread...
ivendor said:
zenthought.org/content/file/android-root-2009-08-16-source
This is linked in the other thread...
Click to expand...
Click to collapse
That code is old, and apparently won't work. It won't compile either, Paul from Modaco tried it and it just spat the dummy and gave a make error.
Coburn64 said:
That code is old, and apparently won't work. It won't compile either, Paul from Modaco tried it and it just spat the dummy and gave a make error.
Click to expand...
Click to collapse
That's the code for the old asroot exploit (used in the Hero IIRC). It's been patched in August/09 so it won't affect the kernel in stock Tattoos.
Yeah, that's what I was getting at - the exploit is too old.
We need to either:
1) Get a S-OFF bootloader
2) Find another working root exploit
3) Dig around in the test ROM and extract the SU binary out of that sucker and put it in /data/local on the working ROM.
I think I can do the latter.
After you root the Nook Color, how do you set or change the root password? Is it similar to how it is done in linux with the passwd command? What is the default root login and password?
thanks
I think you're confused on what rooting is. There is no root password.
tunwear said:
I think you're confused on what rooting is. There is no root password.
Click to expand...
Click to collapse
Actually, there is on Linux but I believe android lacks the feature. Just type su in terminal to get root access if you are rooted.
Sent from my SPH-D700 using XDA App
phfaty said:
After you root the Nook Color, how do you set or change the root password? Is it similar to how it is done in linux with the passwd command? What is the default root login and password?
thanks
Click to expand...
Click to collapse
This sounds like something you had to do after jailbreaking an iDevice maybe you're mixing them up
I think he's comming from the apple world where you have to change the ssh password from alpine to something else.
There is no password to change because there is no ssh or telnet service running in the background. Hense no one can access the device remotely. If you install a remote access server and run it as a service (deamon, running all the time) then yes you need a password for that service. Most of these services in android are apps and only run when you turn them on. The one I use asks you to create a password before it even runs. Wireless adb doesn't ask for a password but then you are only using it for a short time and I seriously doubt hackers would be scanning for open adb ports since it is such a small number of devices using it.
But...
Hello, I have a question about this: what about other apps can access system files by accessing with root priveleges to install software that collect our information ?
Thanks
MikiBroki said:
Hello, I have a question about this: what about other apps can access system files by accessing with root priveleges to install software that collect our information ?
Thanks
Click to expand...
Click to collapse
Only if you click 'allow' for that app.
I am looking for a SU binary that has password protection. Does it exist? Can someone compile that into the SU binary?
Just a simple text file like /data/system/passwd ?
If not set it will not ask (like now)
I you want to set it use /system/xbin/su --setpwd ***** where ***** is the password stored in /data/system/passwd (rw-rw---- root.root)
Only factory reset will clear it.
Then if password is set then /system/xbin/su will ask for a password in the shell.
Just my 2 cents.
Thx.
tweakradje said:
I am looking for a SU binary that has password protection. Does it exist? Can someone compile that into the SU binary?
Click to expand...
Click to collapse
I personally have one, actually, but I'm not about to publish it (I'm not confident enough in my setuid-program-writing skills to promise anyone else security, and the code I have actually requires compiling the password hash into the binary). That said, you don't actually want my personal su, because it breaks pretty much every root-using Android app out there by prompting for a password via standard input.
It's certainly possible to do this "correctly" -- you'd need to move the password prompt into the Android UI (the Superuser app or equivalent). That would further complicate code that's already far too busy for comfort, though (seriously, who links SQLite into a setuid root binary??!?).
Thanks for your feedback. Nice to know there is a need for this. I only want security when adb is on.
You can detect if su request is from the shell? Then only ask for password if request is from the shell.
Else SuperUser.apk is not compatible? Or devs like Chainfire needs to change that too.
Cheers
gedster314 said:
I think he's comming from the apple world where you have to change the ssh password from alpine to something else.
There is no password to change because there is no ssh or telnet service running in the background. Hense no one can access the device remotely. If you install a remote access server and run it as a service (deamon, running all the time) then yes you need a password for that service. Most of these services in android are apps and only run when you turn them on. The one I use asks you to create a password before it even runs. Wireless adb doesn't ask for a password but then you are only using it for a short time and I seriously doubt hackers would be scanning for open adb ports since it is such a small number of devices using it.
Click to expand...
Click to collapse
I just installed cm10.1 and saw their is built in ssh.... I configured it without authentication and allowed root login and its asking me for my android root password -.-
Using any ssh of the market works. But this thing comes with ssh.. Whats the password its asking for lol
leathan said:
I just installed cm10.1 and saw their is built in ssh.... I configured it without authentication and allowed root login and its asking me for my android root password -.-
Using any ssh of the market works. But this thing comes with ssh.. Whats the password its asking for lol
Click to expand...
Click to collapse
Type "su" and then after it asks for root type "passwd" in terminal emulator without the quotes. It will ask you to enter a new password as one has not yet been set up.
Changing root passwd android 2.3.3
tunwear said:
I think you're confused on what rooting is. There is no root password.
Click to expand...
Click to collapse
I beg to differ there is a way to do it however i found this on someone elese thread and figured id share.....i got as far as making a new user however i still can but cant change the root passwd.
mount -o remount,rw /dev/block/mtdblock3 /system
now type:
cd /system/bin
ls
Do you see su or your username listed?
If so type:
chmod 4755 (type su or your username here, without parantheses)
now open terminal emulator on your phone and try your superuser command again.
If you did not see su or your username in the output of ls type the following to get a setuid shell:
cat sh > (username or su whichever you want)
chmod 4755 (username or su whichever you want)
now open terminal emulator on your phone and try your superuser command again.
That should get you going.
First of all, Linux and OS X come with sqlite3 by default. Windows users will need to download the executable. With that said, here is how you can enable sideloading the old-fashioned way.
Code:
[[email protected] ~]$ adb shell
$ su
# busybox cp /data/data/com.android.providers.settings/databases/settings.db /data/data/com.android.providers.settings/databases/settings.db.bak
# chown system.system /data/data/com.android.providers.settings/databases/settings.db
# ls -l /data/data/com.android.providers.settings/databases/settings.db*
# busybox cp /data/data/com.android.providers.settings/databases/settings.db /sdcard
# exit
$ exit
[[email protected] ~]$ adb pull /sdcard/settings.db
sqlite3 settings.db
sqlite> SELECT * FROM secure WHERE name="install_non_market_apps";
3|install_non_market_apps|0
sqlite> UPDATE secure SET value=1 WHERE name="install_non_market_apps";
sqlite> SELECT * FROM secure WHERE name="install_non_market_apps";
3|install_non_market_apps|1
sqlite> .quit
[[email protected] ~]$ adb push settings.db /sdcard/
[[email protected] ~]$ adb shell
$ su
# busybox cp /sdcard/settings.db /data/data/com.android.providers.settings/databases/settings.db
# chown system.system /data/data/com.android.providers.settings/databases/settings.db
# ls -l /data/data/com.android.providers.settings/databases/settings.db*
# exit
$ exit
[[email protected] ~]$ adb reboot
You should be all set.
thank god for super one click
Script?
Sent from my MB860 using XDA Premium App
lsxrx7 said:
thank god for super one click
Click to expand...
Click to collapse
1) Great if you use Wind'oh!s which I refuse to do.
2) I like to know how things work.
I think this work on only rooted devices. If that case we have one already which will root it and also side load apps.
You got the phone gdanko?! Cool
I'll do it this way for kicks when I get my phone lol
gdanko said:
1) Great if you use Wind'oh!s which I refuse to do.
2) I like to know how things work.
Click to expand...
Click to collapse
Yes, it's always great to know how things work.
But it looks like SuperOneClick is not just confined to Windows.
It is compatible with:
Windows Vista
Windows 7
Ubuntu Hardy (8.04 LTS)
Ubuntu Jaunty (9.04)
Ubuntu Karmic (9.10)
Ubuntu Lucid (10.04 LTS)
Ubuntu Maverick (10.10)
Debian Lenny (5.0)
Debian Squeeze (testing)
Debian Sid (unstable)
Debian Experimental
SuperOneClick uses Mono on Linux platforms, so most any of the modern ones should work. I used it on my openSUSE box and it worked just fine for allowing non-market installs.
Can anyone do this a little more nood friendly? And/or does this require root?
phro321 said:
Can anyone do this a little more nood friendly? And/or does this require root?
Click to expand...
Click to collapse
Yeah, you basically want to get out of this thread and head here:
http://forum.xda-developers.com/showthread.php?t=960336
Follow briefmobile's tutorial. And yes, it requires root.
If I am not mistaken gdanko doesnt use any of those operating systems. He uses a mac...
Maybe his old school ways will help uncover some mysterious portal into the Atrix that will allow cracking the bootloader...
I just finished running superoneclick. I wanted to double check that my phone is now allowing unknown sources, but i dont see the checkbox where it should be. Is this normal? Thanks!
__redfox__ said:
I just finished running superoneclick. I wanted to double check that my phone is now allowing unknown sources, but i dont see the checkbox where it should be. Is this normal? Thanks!
Click to expand...
Click to collapse
I guess the check box is not added, but superoneclick did do its job. The phone is communicating with the laptop as expected.
__redfox__ said:
I guess the check box is not added, but superoneclick did do its job. The phone is communicating with the laptop as expected.
Click to expand...
Click to collapse
Follow this to add the check box: http://forum.xda-developers.com/showthread.php?t=972760
agentdr8 said:
SuperOneClick uses Mono on Linux platforms, so most any of the modern ones should work. I used it on my openSUSE box and it worked just fine for allowing non-market installs.
Click to expand...
Click to collapse
Fails on Ubuntu 64. And installing mono and a host of other things for something so trivial is pointless.
Thank you, I needed this sideloading hack since I've already updated/rooted my phone and couldn't use Gladatrix or aRoot without having to reflash 1.26
------------
edit: Actually it got my phone stuck in bootloader with my configuration (1.57 update and rooted). SBF flashing now..
marlasinger said:
Thank you, I needed this sideloading hack since I've already updated/rooted my phone and couldn't use Gladatrix or aRoot without having to reflash 1.26
------------
edit: Actually it got my phone stuck in bootloader with my configuration (1.57 update and rooted). SBF flashing now..
Click to expand...
Click to collapse
Hey How did you root your 1.57?
Spoofy said:
Hey How did you root your 1.57?
Click to expand...
Click to collapse
Go to the GladRoot thread linked in my signature below. Please use the search function in the future.
Ririal said:
Go to the GladRoot thread linked in my signature below. Please use the search function in the future.
Click to expand...
Click to collapse
Lose the attitude buddy.
Don't tell me to search, as I have been googling and searching this forum for over a week and found nothing but SuperOneClick which also required me to downgrade.
I probably missed it due to "Last edited by Ririal; 23rd April 2011 at 01:40 AM. Reason: Updates"
Unfortunately this is still not what I am looking for as I am on 1.57 and am still required to downgrade.
Please have some respect.
EDIT: I'ts also not in the sticky thread
EDIT #2: I just found [HOWTO] Easy Root 1.5.7 using GingerBreak which popped up on the 23rd. WOHOOO, no need to downgrade and risk Wifi issues.
Spoofy said:
Lose the attitude buddy.
Don't tell me to search, as I have been googling and searching this forum for over a week and found nothing but SuperOneClick which also required me to downgrade.
I probably missed it due to "Last edited by Ririal; 23rd April 2011 at 01:40 AM. Reason: Updates"
Unfortunately this is still not what I am looking for as I am on 1.57 and am still required to downgrade.
Please have some respect.
EDIT: I'ts also not in the sticky thread
Click to expand...
Click to collapse
It has nothing to do with respect, and I don't have an attitude. Relax, guy.
All the information is readily available, all you need to do is look for it. There's several threads on the first page of the development forum (which you found as you're posting in it) that contain the information you need. One of the threads is even clearly labeled: "[HOWTO] Easy Root 1.5.7 using GingerBreak"
So sorry, I get a little short with people who ask questions that are already answered. Don't take it personally. Here's the breakdown:
There's currently 2 methods of root, one is GladRoot, which requires you to downgrade first. The other is GingerBreak, which formats your phone data. Pick your poison.
Head over here and root your phone normally, no webtop open, undocked.
Make sure ADB is Enabled (settings > applications > development, check usb debugging)
dock your phone on the laptop dock
open a cmd prompt on your pc
adb shell
su (accept on phone interface)
passwd (choose a password and confirm it)
sulogin (enter the password you created above)
There ya have it, root access on the webtop! you should see "[email protected]"
Sorry for my ignorance but will this allow me to mirror the screen on a monitor or tv using the hdmi cable?
Sent from my MB860 using XDA App
That's cool, just wondering what we can do with this!
yokozuna82 said:
Sorry for my ignorance but will this allow me to mirror the screen on a monitor or tv using the hdmi cable?
Click to expand...
Click to collapse
Not yet, altough progress on it is being made.
Doubbbbleee Root! Combooo breaker!
I love this forum. Don't even have my Atrix yet, but the excitement is killing me.
I would really not recommend changing the root password just in case moto has scripts or processes that have the password built in. A easier way to achieve [email protected] is
su
/osh/bin/bash
"root" on the webtop
From my understanding the webtop and android are running the same kernel and have access to the same shells (i.e. I can run the webtop bash from within the android terminal), users and other data. Where the webtop differs from android is the use of an actual X11 server, but the server is actually running in android. Try running ps | grep X while the webtop is running but in a android shell, you will see /usr/bin/X as a running process, now run /osh/bin/bash and ps aux | grep X, you will see the same process number associated with /usr/bin/X. We can see that X is running with hdmi out.
wealeat said:
I love this forum. Don't even have my Atrix yet, but the excitement is killing me.
Click to expand...
Click to collapse
Same! Get mine on my birthday, March 19th. Can't wait to see what's possible then!
kjbreil said:
I would really not recommend changing the root password just in case moto has scripts or processes that have the password built in. A easier way to achieve [email protected] is
su
/osh/bin/bash
"root" on the webtop
From my understanding the webtop and android are running the same kernel and have access to the same shells (i.e. I can run the webtop bash from within the android terminal), users and other data. Where the webtop differs from android is the use of an actual X11 server, but the server is actually running in android. Try running ps | grep X while the webtop is running but in a android shell, you will see /usr/bin/X as a running process, now run /osh/bin/bash and ps aux | grep X, you will see the same process number associated with /usr/bin/X. We can see that X is running with hdmi out.
Click to expand...
Click to collapse
Thats not full root access to the ubuntu side tho, that is just root over the android side(ubuntu side is inside the android side). Now we can properly access root inside the ubuntu environment.
So far nothing has failed to run from changing that. Start up, use, shutdown, there are no errors related to sulogin.
designgears said:
Thats not full root access to the ubuntu side tho, that is just root over the android side(ubuntu side is inside the android side). Now we can properly access root inside the ubuntu environment.
Click to expand...
Click to collapse
That doesn't really make sense, you are either uid 0 or you are not.
Sent from my MB860 using XDA App
designgears said:
Thats not full root access to the ubuntu side tho, that is just root over the android side(ubuntu side is inside the android side). Now we can properly access root inside the ubuntu environment.
So far nothing has failed to run from changing that. Start up, use, shutdown, there are no errors related to sulogin.
Click to expand...
Click to collapse
It would usually be bad practice to presume a known root password when coding something like this. Scripts needing root should get suid set on them, and thus no plain text password would be involved.
So I don't really envisage any issues with a changed root pw
So with root everywhere, can we add an option that shows up when docked,
ie. if i just dock my atrix and i can HD entertainment and listen to music show photos, etc.
if i dock with hdmi, i get the webtop experience in ubuntu, which i love, But being the g33k i am, if i had an addition option that let me load fedora, i would smile very g33ky, and say Look what i can do!...
i guess this is a dev request.
i am using the atrix as my daily driver, but do have a backup phone, so if a dev wants me to test something out with my setup, i would be glad to do anything to better the dev of this device.
regards,
Killster
forgive my ignorance here, but if I am docked into the laptop dock, my microusb port is being used in the laptop dock. How exactly will i be able to sync to my pc (with USB debugging enabled) to run adb? are running some kind of splitter cable?
tchan012 said:
forgive my ignorance here, but if I am docked into the laptop dock, my microusb port is being used in the laptop dock. How exactly will i be able to sync to my pc (with USB debugging enabled) to run adb? are running some kind of splitter cable?
Click to expand...
Click to collapse
adb wireless i think
What does this get me?
So what does root access on Webtop grant me that I wouldn't have access to before?
If you have root on your phone you have root on webtop, you are uid 0, so it doesn't gain you anything that you don't already have.
Sent from my MB860 using XDA App
Okay..I Know this is simple but its not somthing to do at 5am I frogot what I entered as the password..
Pulled a
Su
Passwd
********
Sulogin
********
Passwd not found:
Tried every old pass I had on it nothing, any way to spare the phone reset and redo the root password?
Update: Ive tried reseting the phone, re flashing the retail sbf and I am still having problems with this its bugging the hell outta me used the OP preps:
su
# passwd *****
passwd ******
passwd: not found
# sulogin
sulogin
Give root password for maintenance
(or type Control-D to continue): ******
Login incorrect.
Give root password for maintenance
(or type Control-D to continue):
Any ideas?
kennethpenn said:
Doubbbbleee Root! Combooo breaker!
Click to expand...
Click to collapse
LOL Nice!
kennethpenn said:
Doubbbbleee Root! Combooo breaker!
Click to expand...
Click to collapse
LOL that made my morning. And the original post of course.
Is this working still?
anyone know a way to force the update over ssh or telnet?
I know several people who can't upgrade.
Here is how I did it via ssh or telnet.
Code:
curl http://pdl.team-eureka.com/ota/19084.001.zip -o /cache/eureka_image.zip
the correct md5 is 2414b9f0fb603ec809cad2b6fec6909f for 19084.001.zip
http://pdl.team-eureka.com/ota/19084.001.zip.md5 is the url for the server md5.
run this command to get the md5.
Code:
busybox md5sum /cache/eureka_image.zip
Code:
rm -r /cache/flashcast-data/
Code:
touch /cache/ota.zip
Code:
curl -H "Content-Type: application/json" http://localhost:8008/setup/reboot -d '{"params":"ota"}' -X POST
I was just following along in.
https://github.com/team-eureka/ChromeCast-OTA/blob/master/chromecast-ota
Was wondering do you have to be on a particular ROM version to do this? I only ask because I rooted my Chromecast back when the exploit first came out but I no longer have the equipment to use Flashcast to update it and as of right now my Chromecast is useless. How do you know which version ROM your are using. My Chromecast is still running the 13300 firmware and I know I have the "Pwned" boot screen but apparently it was before the OTA updates were included in the ROM. Will this method work or do I have to go buy a new Chromecast?
I don't think it will work but I don't really know.
I only know what the update script does. I just wanted to avoid using a usb drive and otg cable.
I also had to update some that are at a remote location. I couldn't physically be there.
klbjr said:
Was wondering do you have to be on a particular ROM version to do this? I only ask because I rooted my Chromecast back when the exploit first came out but I no longer have the equipment to use Flashcast to update it and as of right now my Chromecast is useless. How do you know which version ROM your are using. My Chromecast is still running the 13300 firmware and I know I have the "Pwned" boot screen but apparently it was before the OTA updates were included in the ROM. Will this method work or do I have to go buy a new Chromecast?
Click to expand...
Click to collapse
If you have access to ssh this should work, I think. Wait for someone else to confirm this. But be aware that you should check md5 after downloading the file.
busybox md5sum /cache/eureka_image.zip
BlueCop said:
Since no one will help with this.
Here is how I did it via ssh or telnet.
Code:
curl http://pdl.team-eureka.com/ota/19084.001.zip -o /cache/eureka_image.zip
Code:
rm -r /cache/flashcast-data/
Code:
touch /cache/ota.zip
Code:
curl -H "Content-Type: application/json" http://localhost:8008/setup/reboot -d '{"params":"ota"}' -X POST
I was just following along in.
https://github.com/team-eureka/ChromeCast-OTA/blob/master/chromecast-ota
Click to expand...
Click to collapse
You forgot the check of md5sum step. Without this step you can turn a chromecast in paperweight if it doesn't download the file successfully.
I figured the zip crc would fail if it was a corrupted download. One can still manually verify the md5.
I am looking at the Eureka Sources to add a force upgrade option.
I would love to see a private key signing of the firmwares so people couldn't easily mitm them to pwn your chromecast.
BlueCop said:
I figured the zip crc would fail if it was a corrupted download. One can still manually verify the md5.
I am looking at the Eureka Sources to add a force upgrade option.
I would love to see a private key signing of the firmwares so people couldn't easily mitm them to pwn your chromecast.
Click to expand...
Click to collapse
once we get curl working with the ssl libraries, we plan on moving to https for everything we do.
So I'm out of luck? Well is there anyway to return this to stock because right now I can't use it for anything and would rather get some use out of it vs losing root.
ddggttff3: awesome!
klbjr: why are you out of luck? im confused.
the correct md5 is 2414b9f0fb603ec809cad2b6fec6909f for 19084.001.zip
Code:
busybox md5sum /cache/eureka_image.zip
So BlueCop your saying I can still update this way? I thought you said I couldn't
klbjr said:
So BlueCop your saying I can still update this way? I thought you said I couldn't
Click to expand...
Click to collapse
As your on a ROM before We had the auto-OTA system, this method will not work for you. You will have to manually flash Eureka-ROM using flashcast.
So is there anyway for me to return it to stock because it won't work now with the current ROM and I dont have the tools that I used to originally root it and hate to waste money on another Chromecast. Granted its only $35 but there is nothing wrong with this one.
Sent from my GT-P3100 using XDA Premium HD app
klbjr said:
So is there anyway for me to return it to stock because it won't work now with the current ROM and I dont have the tools that I used to originally root it and hate to waste money on another Chromecast. Granted its only $35 but there is nothing wrong with this one.
Sent from my GT-P3100 using XDA Premium HD app
Click to expand...
Click to collapse
if you can, get on the IRC (#team-eureka on freenode) and I can help you get onto the latest OTA on your device, or stock, (your pick) doing some dirty tricks (hope you don't mind using SSH).
ddggttff3 said:
if you can, get on the IRC (#team-eureka on freenode) and I can help you get onto the latest OTA on your device, or stock, (your pick) doing some dirty tricks (hope you don't mind using SSH).
Click to expand...
Click to collapse
Sure will. Just let me know what time is good for you and I'll have to brush up on SSH.
klbjr said:
Sure will. Just let me know what time is good for you and I'll have to brush up on SSH.
Click to expand...
Click to collapse
Just get on whenever you feel, and even if I am away I will make sure directions are thrown your way.
ddggttff3 said:
Just get on whenever you feel, and even if I am away I will make sure directions are thrown your way.
Click to expand...
Click to collapse
Thank you. I'm hopping on now.
ddggttff3 said:
Just get on whenever you feel, and even if I am away I will make sure directions are thrown your way.
Click to expand...
Click to collapse
Just want to point out to others that you CAN'T BUY support like this! LOL
klbjr said:
Thank you. I'm hopping on now.
Click to expand...
Click to collapse
Sounds good, and its #teameureka not #team-eureka, my bad.
Asphyx said:
Just want to point out to others that you CAN'T BUY support like this! LOL
Click to expand...
Click to collapse
I agree!!! You can't! ddggttff3 found me on IRC, walked me through every step very patiently and made sure I got everything working! Another testament to the goodness and greatness of the devs we have here!