Development [HOWTO] Enable USD Debugging, and gain root with Debug password

I don't have a copy of the update, is there a link to it?

Someone with gtalk hit me up at admin@soblow.me, so we can sort this out. I will most likely just release an app that patches the device this time.

someone run these commmands

adb shell busybox whoami

then

adb shell su -c busybox whoami

Looks like password still works from the bytecode i was looking at. Can anyone verify if adb still runs?

Good morning (UK time). (I have rooted using the universal root apk)

adb shell busybox whoami

gave me whoami: unknown uid 2000

and doing the su version gave "persmission denied"

am going to try on device debugging today (when I get the time - am at work now).

andy.

I don't understand why Entourage Systems is making life so difficult for people who want to write apps for the eDGe. maybe they don't want any apps in thier store. I for one won't be putting any more in.

Originally Posted by mrspaceman

I don't understand why Entourage Systems is making life so difficult for people who want to write apps for the eDGe. maybe they don't want any apps in thier store. I for one won't be putting any more in.

Hey guys, this change is to SUPPORT developers. We want to eventually support paid apps as well as the free ones, but there would be very high resistance for a developer to put his paid app on our store if our device ships rooted. It would be too easy to steal.

Also - we DID NOT change the debug password, we just un-rooted the shell you get. We knew you guys would crack right back in, it's not like we're sitting here thinking that we locked you out for good.

So we're now doing what every single phone does when they ship!

AND - We were curious how long it would take you fellas to break back in... I think I won; someone owes me a quarter.

Rooting isn't the point. I don't Want to root my eDGe, I just want to develop apps for it.

Originally Posted by PonMan

So we're now doing what every single phone does when they ship!

Nope you are not doing what phones do.

Phones ship with a "enable adb debugging" checkbox, you don't.

which is why I will switch back to developing for my phone (HTC hero running Android 2.2).

p.s. if you were really interested in stopping people stealing apps, then you would disable the "allow untrusted apps" and not the "allow debugging" checkboxes. untrusted apps is how you install pirated apps (as well as any other app not in an app store - I know). the only people you annoy by disabling on device debugging is developers who want to target your device.

I use universal root 2.02 and my EE is rooted.
I turn debug on with previous password, it is OK. My EE is debug on

connected EE to MacBookPr, Run terminal program
issue
adb shell su -c busybox whoami
BusyBox v1.15.2 (2010-08-31 03:36:26 EDT) multi-call binary
Copyright (C) 1998-2008 Erik Andersen, Rob Landley, Denys Vlasenko
and others. Licensed under GPLv2.
See source distribution for full notice.

Usage: busybox [function] [arguments]...
or: function [arguments]...

BusyBox is a multi-call binary that combines many common Unix
utilities into a single executable. Most people will create a
link to busybox for each function they wish to use and BusyBox
will act like whatever it was invoked as!

Currently defined functions:
[, [[, addgroup, adduser, adjtimex, ar, arp, arping, ash, awk,
basename, beep, blkid, brctl, bunzip2, bzcat, bzip2, cal, cat, catv,
chat, chattr, chgrp, chmod, chown, chpasswd, chpst, chroot, chrt, chvt,
cksum, clear, cmp, comm, cp, cpio, crond, crontab, cryptpw, cttyhack,
cut, date, dc, dd, deallocvt, delgroup, deluser, devmem, df, dhcprelay,
diff, dirname, dmesg, dnsd, dnsdomainname, dos2unix, du, dumpkmap,
dumpleases, echo, ed, egrep, eject, env, envdir, envuidgid, ether-wake,
expand, expr, fakeidentd, false, fbset, fbsplash, fdflush, fdformat,
fdisk, fgrep, find, findfs, fold, free, freeramdisk, fsck, fsck.minix,
fsync, ftpd, ftpget, ftpput, fuser, getopt, getty, grep, gunzip, gzip,
halt, hd, hdparm, head, hexdump, hostid, hostname, httpd, hush,
hwclock, id, ifconfig, ifdown, ifenslave, ifplugd, ifup, inetd, init,
insmod, install, ionice, ip, ipaddr, ipcalc, ipcrm, ipcs, iplink,
iproute, iprule, iptunnel, kbd_mode, kill, killall, killall5, klogd,
last, length, less, linux32, linux64, linuxrc, ln, loadfont, loadkmap,
logger, login, logname, logread, losetup, lpd, lpq, lpr, ls, lsattr,
lsmod, lzmacat, lzop, lzopcat, makedevs, makemime, man, md5sum, mdev,
mesg, microcom, mkdir, mkdosfs, mkfifo, mkfs.minix, mkfs.vfat, mknod,
mkpasswd, mkswap, mktemp, modprobe, more, mount, mountpoint, msh, mt,
mv, nameif, nc, netstat, nice, nmeter, nohup, nslookup, od, openvt,
passwd, patch, pgrep, pidof, ping, ping6, pipe_progress, pivot_root,
pkill, popmaildir, poweroff, printenv, printf, ps, pscan, pwd,
raidautorun, rdate, rdev, readahead, readlink, readprofile, realpath,
reboot, reformime, renice, reset, resize, rm, rmdir, rmmod, route,
rtcwake, run-parts, runlevel, runsv, runsvdir, rx, script,
scriptreplay, sed, sendmail, seq, setarch, setconsole, setfont,
setkeycodes, setlogcons, setsid, setuidgid, sh, sha1sum, sha256sum,
sha512sum, showkey, slattach, sleep, softlimit, sort, split,
start-stop-daemon, stat, strings, stty, su, sulogin, sum, sv, svlogd,
swapoff, swapon, switch_root, sync, sysctl, syslogd, tac, tail, tar,
tcpsvd, tee, telnet, telnetd, test, tftp, tftpd, time, timeout, top,
touch, tr, traceroute, true, tty, ttysize, tunctl, udhcpc, udhcpd,
udpsvd, umount, uname, uncompress, unexpand, uniq, unix2dos, unlzma,
unlzop, unzip, uptime, usleep, uudecode, uuencode, vconfig, vi, vlock,
volname, watch, watchdog, wc, wget, which, who, whoami, xargs, yes,
zcat, zcip

Originally Posted by PonMan

Hey guys, this change is to SUPPORT developers. We want to eventually support paid apps as well as the free ones, but there would be very high resistance for a developer to put his paid app on our store if our device ships rooted. It would be too easy to steal.

Also - we DID NOT change the debug password, we just un-rooted the shell you get. We knew you guys would crack right back in, it's not like we're sitting here thinking that we locked you out for good.

So we're now doing what every single phone does when they ship!

AND - We were curious how long it would take you fellas to break back in... I think I won; someone owes me a quarter.

No phone ships with a password for adb. As a developer who makes a livable income off apps, I don't give a rat's butt if a device ships rooted or not. Since your device lacks the market apis, the only option for copy protection is either forward locking (which we know is a complete failure, and google has depreciated it and no longer recommends it) or another method like a secondary license server (which I know can work) which would work rooted or not.

I can provide some payment option recommendations if your interested, and willing to open your app "store" to them. I am coding up some stuff with the paypal API, waiting for my tablets to arrive.

PonMan, LOL. Sorry, but it's so lamish....

Originally Posted by PonMan

We want to eventually support paid apps as well as the free ones, but ...

Didn't You thought that _at first_, you need at least to make an option to SELL apps on Your market?

Originally Posted by PonMan

but there would be very high resistance for a developer to put his paid app on our store if our device ships rooted.

Tell me this developer's name ) At first, try to find developers who really interested in creating serious apps for EE (which still sold less than 100.000 devices? correct me if I wrong ), and (or at least) give them SDK envirement or debugging control. Be real. EE has so small market share that there's no interest to create exclusive apps... You lucky that you use android, and lucky that android is an uniform platform which allow you to run apps designed for other devices on EE. As for me (as an example)... I haven't commercial interesting in market (standalone site or devices) unless it sale more than 10.000 paid apps per day (or if there's some special interest or underground agreements).

Originally Posted by PonMan

if our device ships rooted.

You need to learn difference between rooted and rootable devices.

Originally Posted by PonMan

It would be too easy to steal.

LOL, it takes 5 minute to:
a) download apk, from your site WITHOUT using EE.
b) or to copy paid apk from devices
c) or to copy installed apps.
and it takes another 2 minutes to:
a) patch odx/apk,
b) or to patch firmware.
c) to install in private envirement
And all those steps doesn't requre root.

Originally Posted by PonMan

So we're now doing what every single phone does when they ship

LOL, So EE is the PHONE??? Why there's no google market then?
Phone ships blocked for simple reason: to not allow users to use phone as mobile hotspot (internet sharing). And to protect phone from dumb users. In first case they also patch some internal code to block tethering bu default. In second case they leave some options to enable adb for advanced users (voiding warranty by enabling it).

P.S. yip, it's not problem to root device. But it's takes time. Not much time, but it makes me upset, as time mean money. So when you steel time from developers, developers pushing you, which lead again to some problems, when you need to spend your time on us like in the case with GPL code (by the way, where's new revision?)...

So what the point? It all makes me think that there's some people in EE CEO which just do not understand how things done
Time to fire someone
p.s. To EE CEO: nothing personal, just business

p.s. sorry, I forgot (or You didn't want to mention it) another reason why EE, want to make device unrootable...
it's to force people buy books from EE's shop (To make a little harder proccess of viewing or purchasing books from other stories, or to protect books from DRM removing)...
But again it's useless...
1. all DRM protected keys on EE is unencrypted (hashed but it's not a problem for anyone). So another security hole in EE.
2. again there's no problem to download books without EE, or copy them from EE without root.
3. DRM by itself is suck, and removing protection (no matter if DRM or PASS based) takes almost no time.
4. There's no problem to download any book that you're selling (or will sell) on torrents or book sharing sites.

robot,

Hit me up on GTalk, I have a Tesla card here (240 1.3ghz processors, does wonders for hashes). Could be fun.

Originally Posted by robot

another reason why EE, want to make device unrootable...
it's to force people buy books from EE's shop (To make a little harder proccess of viewing or purchasing books from other stories, or to protect books from DRM removing)...

I haven't had a single problem with opening book from other vendors. Don't you think they would've come up with a better idea if they had wanted to limit our access to third party books. Btw, rules related to copyrights (DRM) in the US are far more strict then in Russia, so it's not the company's decision, it is their duty.

emen, don't take my words exactly. I just mean that some e-book companies made some dirty tricks to improove their own sales.
As for copyrights:
I know that removing DRM is federal crimes in some countries (even if you had hardcopy, and DRM is expired not supported by software\platform e.t.c.)...
I know that you can be sued even if your children download an mp3 or avi file (even if you allready own an licensed disc with the same content)...
I know that you must pay for every copy of an song for every device you have... (o.k. some companies allow to use one song on up to 3 devices... what a wonderfull option )
I know that you can be sued for listening (broadcasting) of an song in public (even if it was your mobile's ringtone)...
I know that you can be charging for citing an book (or article)...
e.t.c.
so...
I know that some companies will use any trick to made some money (to not start flaming... I'm not talking about EE, but about industry in general) and that's the reason why they protect their devices from "improper" use, or used spyware software to control users.