Related
If anyone can post a link to a detailed Ubuntu guide for newbies to root the Hero and remove stock apps, I would appreciate it. The guide posted doesn't go into too much detail in Ubuntu since the OP said that he could not get it to work in Ubuntu. Thanks.
killabee44 said:
If anyone can post a link to a detailed Ubuntu guide for newbies to root the Hero and remove stock apps, I would appreciate it. The guide posted doesn't go into too much detail in Ubuntu since the OP said that he could not get it to work in Ubuntu. Thanks.
Click to expand...
Click to collapse
Wouldnt the Mac version work since they are both *nix?
I was able to root my Sprint HTC hero just fine running Jaunty. I followed the instructions in the guide you mentioned, for Ubuntu. One thing I noticed is before adb recognized my phone, I had to start "HTC Sync" from the phone's notifications. Just ignore the error about it not finding HTC Sync on your PC. Obviously it never will since HTC Sync is a Windows app
Here's the step by step that worked for me: http://romeosidvicious.com/2009/11/09/rooting-the-htc-hero-with-ubuntu-karmic/
I typed it so I could find it easily if necessary and figured why not share it....
romeosidvicious,
Thanks for all your hard work. I and others really appreciate it.
Stevious said:
I was able to root my Sprint HTC hero just fine running Jaunty. I followed the instructions in the guide you mentioned, for Ubuntu. One thing I noticed is before adb recognized my phone, I had to start "HTC Sync" from the phone's notifications. Just ignore the error about it not finding HTC Sync on your PC. Obviously it never will since HTC Sync is a Windows app
Click to expand...
Click to collapse
Yep, that is something I had to do in windows XP as well. It will help many others as well. Thanks.
Stevious said:
I was able to root my Sprint HTC hero just fine running Jaunty. I followed the instructions in the guide you mentioned, for Ubuntu. One thing I noticed is before adb recognized my phone, I had to start "HTC Sync" from the phone's notifications. Just ignore the error about it not finding HTC Sync on your PC. Obviously it never will since HTC Sync is a Windows app
Click to expand...
Click to collapse
Great, now my Ubuntu Jaunty machine won't detect the phone. I did the above but it still won't work. Im gonna reboot and retry...
Edit:
Nope, no love for my Ubuntu. It's not seeing the Hero. I will have to research this one.. If anyone has suggestions, please chime in.
Ok, found a solution:
http://forum.xda-developers.com/showthread.php?t=537508
----------------------------------------------------------------
Here is the part that solved it for me:
Setting up UDEV to recognize HTC Device -
1. Type the following into a terminal (Applications > Accessories > Terminal):
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
2. Now add the following line to the blank file:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
3. Click save and close.
4. To restart udev, open up a terminal and enter:
Code:
sudo /etc/init.d/udev restart
---------------------------------------------------------------------
Thanks to Wddglr for all the useful info. It looks like I will be using other things he posted about. Hopefully that info will help someone else.
Just curious, which version of Ubuntu are you running? I didn't have to make any UDEV changes in Jaunty.
romeosidvicious said:
Here's the step by step that worked for me: http://romeosidvicious.com/2009/11/09/rooting-the-htc-hero-with-ubuntu-karmic/
I typed it so I could find it easily if necessary and figured why not share it....
Click to expand...
Click to collapse
I want to follow through with this...
I was following this
http://www.youtube.com/watch?v=ArMO5IHS2eI
until the step came to plug it in and then he suggested typing "adb devices" which told me this.
"~/android-sdk-linux/tools$ adb devices
bash: adb: command not found"
So I came here and I want to follow the links tutorial.. two questions
Is it safe to proceed even though i've been told adb: Command not found
will i be able to proceed although ive been told this command is not found?
Onompoly2 said:
"~/android-sdk-linux/tools$ adb devices
bash: adb: command not found"
So I came here and I want to follow the links tutorial.. two questions
Is it safe to proceed even though i've been told adb: Command not found
will i be able to proceed although ive been told this command is not found?
Click to expand...
Click to collapse
Try:
sudo ./adb devices
From the same directory. Or, you can specify the full path:
sudo ~/android-sdk-linux/tools/adb devices
To answer your other questions, it won't work if it says the command is not found.
Okay
It worked but I must have turned into an idiot when i decided my operating system was good enough.
This isn't working, and I am not even upgraded to the operating system the tutorial is written for...
194 updates due... running 8.04 with a bunch of double half installed broken applications.. maybe I should reformat.
I'll let you guys know how things go which ever way it goes.
back again. fresh 9.10 install fully updated.
Following this
http://romeosidvicious.com/2009/11/09/rooting-the-htc-hero-with-ubuntu-karmic/
I get this far
[email protected]:~# sudo su
[email protected]:~# cd ~/android-sdk-linux/tools
[email protected]:~/android-sdk-linux/tools#
[email protected]:~/android-sdk-linux/tools#
[email protected]:~/android-sdk-linux/tools# ./adb push ../asroot2 /data/local/
711 KB/s (74512 bytes in 0.102s)
[email protected]:~/android-sdk-linux/tools# ./adb shell chmod 0755 /data/local/asroot2
[email protected]:~/android-sdk-linux/tools# /data/local/asroot2 /system/bin/sh
bash: /data/local/asroot2: No such file or directory
[email protected]:~/android-sdk-linux/tools# ./adb shell /data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/559/fd/3
SUCCESS: Enjoy the shell.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
reboot
Click to expand...
Click to collapse
It seems as though after it says "SUCCESS" that my terminal just stops responding to code...
Tried reading the link to where he made the tutorial from, but its a mixture of ubuntu and windows with 30 pages of posts.
Any thoughts/help?
Thanks
[Continuing]
So just pretending that everything is going as planned I reboot the phone and it actually turns my computer off as well..
So I continue with the steps.
[email protected]:~# cd ~/android-sdk-linux/tools
[email protected]:~/android-sdk-linux/tools# ./adb push ../recovery-RA-heroc-v1.2.3.img /sdcard/
* daemon not running. starting it now *
* daemon started successfully *
1199 KB/s (3352576 bytes in 2.730s)
[email protected]:~/android-sdk-linux/tools# ./adb shell
$ su
su: permission denied
Click to expand...
Click to collapse
But Get permission denied.
I'm going to go ahead and start over but skip the first line that i input that said SUCCESS and stopped the terminal.
(really don't know what i'm doing but I think I need to get these two lines in
cat sh > su
chmod 4755 su)
EDIT: on second thought perhaps this has something to do with me being logged in as root on my computer from the get go, i'll try that.
A dummy and his cell phone perhaps soon part.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
reboot
Click to expand...
Click to collapse
It looks like you copy/pasted this whole section as a block. I think you need to execute the commands one at a time, and wait for a new "#" prompt between each one. The reason the terminal stops responding is that as one long string, it's not a meaningful command.
buck2202 said:
It looks like you copy/pasted this whole section as a block. I think you need to execute the commands one at a time, and wait for a new "#" prompt between each one. The reason the terminal stops responding is that as one long string, it's not a meaningful command.
Click to expand...
Click to collapse
I didn't, although i did try that as well
after I would do the mount commands i would no longer get a $ or a # sign, it was just a bunch of nothingness...
I ended up booting up my girlfriends vista and then spent quite a while figuring out how to get the driver for adb, I had to follow two different windows guides for rooting for some reason as well... so if that says anything.. just imagine how long it took me to realize how to get the driver hahah
buck2202 said:
It looks like you copy/pasted this whole section as a block. I think you need to execute the commands one at a time, and wait for a new "#" prompt between each one. The reason the terminal stops responding is that as one long string, it's not a meaningful command.
Click to expand...
Click to collapse
no, I'm having the same problem. After the "mount" command it gives me nothing.
Edit: doing this in karmic
Odd. I've had no problems following the generic procedure from theunlockr on ubuntu. My only suggestion would be to turn
Code:
./adb shell /data/local/asroot2 /system/bin/sh
into
Code:
./adb shell
/data/local/asroot2 /system/bin/sh
I'm not sure why it should make a difference, but on my computer "./adb shell <command>" exits the shell when it finishes. From what you've pasted, it doesn't look like that's happening to you, but that's my only guess right now.
If you run "./adb devices" do you see your serial number?
And out of curiosity, why are you running as root on your computer? (sudo su) Have you tried just starting the adb server as root, and running the rest of the commands normally? Does this work?
Code:
./adb kill-server
sudo ./adb start-server
./adb devices
I'm trying to start busybox's httpd at boot w/o success. However, I can start it manually post-boot w/o problems. Can I enable a syslog facility so I can see what happens when the bootup script calls it?
Code:
httpd -p 80 -u 80 -h /sdcard/www -c /etc/httpd.conf
I've tried running the process as -u 80 and as -u 0, both work post-boot, not before.
It's Linux - if there is an rc.local you should be able to drop a string in there to make it start.
KaiserLinux said:
It's Linux - if there is an rc.local you should be able to drop a string in there to make it start.
Click to expand...
Click to collapse
Not that simple
There is no rc.local, but I inserted
Code:
/sbin/syslogd -O /data/log/syslog
into the beginning of init.rc, but it logs nothing.
Go into applications and turn on debugging mode. Plug your phone into your computer and run 'adb logcat' or something to that effect. You can play around with your phone and watch the log scroll by.
Your gonna need the whole ADB setup. Go to the samsung epic 4G wiki and check the article about getting root and flashing a new kernel. This will have the instructions for getting ADB on your system as well.
KaiserLinux said:
Go into applications and turn on debugging mode. Plug your phone into your computer and run 'adb logcat' or something to that effect. You can play around with your phone and watch the log scroll by.
Your gonna need the whole ADB setup. Go to the samsung epic 4G wiki and check the article about getting root and flashing a new kernel. This will have the instructions for getting ADB on your system as well.
Click to expand...
Click to collapse
I've compiled my own rooted kernel and a new busybox with syslogd to see if I can diagnose why bb's httpd isn't starting at boot. As I mentioned, it starts manually w/o a problem. adb logcat isn't very useful in this particular situation. Thanks for the reply though.
jocala said:
There is no rc.local, but I inserted
Code:
/sbin/syslogd -O /data/log/syslog
into the beginning of init.rc, but it logs nothing.
Click to expand...
Click to collapse
I'm kind of a noob myself, but I recall reading that init.rc isn't really a shell script. It has a special syntax that is parsed by Android init, I'm not sure just throwing shell commands in there is going to work. I'd post a link to the doc but I can't post links yet
coldguy said:
I'm kind of a noob myself, but I recall reading that init.rc isn't really a shell script. It has a special syntax that is parsed by Android init, I'm not sure just throwing shell commands in there is going to work. I'd post a link to the doc but I can't post links yet
Click to expand...
Click to collapse
Weird, the first 500 lines of init.rc are nothing BUT shell commands.
i.e. chmod 0666 /dev/input/event0
Anyway, further along in init.rc the daemon processes are started up. syntax looks like:
Code:
service playlogo /system/bin/playlogo
user root
oneshot
I've tried setting up my programs (httpd,syslogd) as services, no joy.
jocala said:
Not that simple
There is no rc.local, but I inserted
Code:
/sbin/syslogd -O /data/log/syslog
into the beginning of init.rc, but it logs nothing.
Click to expand...
Click to collapse
sorry to hijack your post.
but i want to know how do you modify the /init.rc,
because when i reboot, the /init.rc will automatic recovery the old verison.
did you check the /init.rc, is it modified, after your phone reboot?
Does logcat not give you the info you want?
You can go here to find out how to redirect stdout and stderr to the logcat as well.
init.rc is part of the root fs, which is compiled into the kernel. So, a custom kernel is required. Search for custom kernel for details.
After 2 days of testing i think i have a clean solution to fix the mobile data drain by setting the preferred network mode to 1 (GSM only). No need to delete or rename anything. Just update the db that is already there .
You need a rooted device for this.
Extract the sqlite3.zip and push to your device with the following commands:
Code:
adb shell mount -o rw,remount /dev/block/mmcblk0p3 /system
adb push sqlite3 /system/bin
adb shell chmod 6755 /system/bin/sqlite3
adb shell
su (to gain root permissions)
sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
reboot
I'll give this a try. Thanks
Edit: Is it possible I can do this on the device without adb? Adb doesn't want to detect my tablet with debugging enabled.
agentdax5 said:
I'll give this a try. Thanks
Edit: Is it possible I can do this on the device without adb? Adb doesn't want to detect my tablet with debugging enabled.
Click to expand...
Click to collapse
Sure, as long as you have some sort of terminal emulator installed.
agentdax5 said:
I'll give this a try. Thanks
Edit: Is it possible I can do this on the device without adb? Adb doesn't want to detect my tablet with debugging enabled.
Click to expand...
Click to collapse
with root explorer and a terminal app (eg connectbot) you can do it.
What exactly does this do? Is it the same result as renaming the phone and telephone apks?
Sent from my SPH-D700 using XDA App
Thanks! Mine is done. I'll report back later after I charge and give it a go.
mrkrabs said:
What exactly does this do? Is it the same result as renaming the phone and telephone apks?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
This updates the database configuration setting that causes the phone to not to look for 3G networks only 2G (GSM which includes GPRS and EDGE). I'll let the OP elaborate more, but this config change must reduce the battery usage by causing the phone and telephony services to chill out out a bit when in standy mode.
_motley said:
This updates the database configuration setting that causes the phone to not to look for 3G networks only 2G (GSM which includes GPRS and EDGE). I'll let the OP elaborate more, but this config change must reduce the battery usage by causing the phone and telephony services to chill out out a bit when in standy mode.
Click to expand...
Click to collapse
couldn't describe it better
2g = only poll cell if request is made that needs cell, 3g = poll all the time, which means that if you change to only 2g then it should not check for cell if you are in wifi range.
I am sure thats how the tech works if i remember my time at nokia right LOL
is there a post around here to explain how to get ADB working on this thing? i can ADB shell in but i get "operation not permitted" when i try to mount /system as r/w
(yes i'm rooted)
thanks guys
edit: i got permission to mount the /system as r/w but when i try to push the sqlite3 i get "Device not found"
i suppose i can give a little more info
i'm running windows 7 ultimate 64 bit with an administrator command prompt and the newest iconia a500 usb drivers from acer's support site and i have my SDK up to date
I did this and it doesn't seem to have a big effect. 2 hours on battery mostly in sleep, Display 33%, Cell 31%, Idle 18%, etc.
Richard:
Just out of curiosity (Yes, I fully acknowledge I should have done something like "select * from secure where name='preferred_network_mode'" beforehand! ) what is the default value of "preferred_network_mode" before this modification sets it to "1"?
-----
Doc Kinne
Somerville, MA
kinnerc said:
Richard:
Just out of curiosity (Yes, I fully acknowledge I should have done something like "select * from secure where name='preferred_network_mode'" beforehand! ) what is the default value of "preferred_network_mode" before this modification sets it to "1"?
-----
Doc Kinne
Somerville, MA
Click to expand...
Click to collapse
Default value is 0 (zero).
agentdax5 said:
I did this and it doesn't seem to have a big effect. 2 hours on battery mostly in sleep, Display 33%, Cell 31%, Idle 18%, etc.
Click to expand...
Click to collapse
It's not about what your stats say, but what your mA drain is. i loose only a couple of % in a night (sleep).
edgemaster191 said:
is there a post around here to explain how to get ADB working on this thing? i can ADB shell in but i get "operation not permitted" when i try to mount /system as r/w
(yes i'm rooted)
thanks guys
edit: i got permission to mount the /system as r/w but when i try to push the sqlite3 i get "Device not found"
i suppose i can give a little more info
i'm running windows 7 ultimate 64 bit with an administrator command prompt and the newest iconia a500 usb drivers from acer's support site and i have my SDK up to date
Click to expand...
Click to collapse
@edgemaster191
I am getting the same error; I also am rooted, running ADB from Windows 7 (and Mac OS X - tried both, same error). I also have latest drivers, and latest ADB.
I get "operation not permited error." Did you have any luck on getting further?
try this instead as a work around:
adb push sqlite3 /sdcard/sqlite3
adb shell
$ su
# mount -o remount,rw /system
# cp /sdcard/sqlite3 /system/bin/sqlite3
# chmod 6755 /system/bin/sqlite3
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
# reboot
I've never been able to use root level adb cmnds with this device from outside the adb shell env, I think you need to update the default.prop, but this gets overwritten on reboot, I'm sure there is a way to fix this, and has proabably been discussed in another thread I've been too lazy to go find lol.
nycbjr said:
try this instead as a work around:
adb push sqlite3 /sdcard/sqlite3
adb shell
$ su
# mount -o remount,rw /system
# cp /sdcard/sqlite3 /system/bin/sqlite3
# chmod 6755 /system/bin/sqlite3
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
# reboot
I've never been able to use root level adb cmnds with this device from outside the adb shell env, I think you need to update the default.prop, but this gets overwritten on reboot, I'm sure there is a way to fix this, and has proabably been discussed in another thread I've been too lazy to go find lol.
Click to expand...
Click to collapse
FTFY. 10char.
I am going to have to run some logs....just not seeing any drain that would justify doing this ....will definitely keep an eye out for it though
nycbjr said:
try this instead as a work around:
adb push sqlite3 /sdcard/sqlite3
adb shell
$ su
# mount -o remount,rw /system
# cp /sdcard/sqlite3 /system/sqlite3
# chmod 6755 /system/bin/sqlite3
# sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'update secure set value="1" where name="preferred_network_mode"'
# reboot
I've never been able to use root level adb cmnds with this device from outside the adb shell env, I think you need to update the default.prop, but this gets overwritten on reboot, I'm sure there is a way to fix this, and has proabably been discussed in another thread I've been too lazy to go find lol.
Click to expand...
Click to collapse
such things will be able with kernels that overwrite the default.prop
matguard said:
@edgemaster191
I am getting the same error; I also am rooted, running ADB from Windows 7 (and Mac OS X - tried both, same error). I also have latest drivers, and latest ADB.
I get "operation not permited error." Did you have any luck on getting further?
Click to expand...
Click to collapse
i was able to finally get it, i copied the splite3 to /system/bin using root explorer, ran chmod through terminal emulator then ran the final command from adb shell.
not ideal but it worked
Hi all,
I rooted my Nook Simple Touch via TouchNooter 2.1.31. No hitches aside from the Market giving me a Server Error just after installing, which cleared up the next day. Since now I have my email (and in the future other sensitive apps/info) on the Nook I would like to be able to lock the screen like a full Android phone or tablet. Is this possible? I don't necessarily mean having the exact same way of locking (i.e., press the power button and the screen locks) but at least an app for doing that would be great. Any ideas?
Thanks!
Set a PIN lock on your Nook.
In an ADB shell:
Code:
am start -n com.android.settings/.ChooseLockPin
Thanks! Now if I could only get adb to work... doing adb shell gives me "error: device not found", and turning on AdbWireless and trying to connect with adb connect just hangs.
Renate NST said:
Set a PIN lock on your Nook.
In an ADB shell:
Code:
am start -n com.android.settings/.ChooseLockPin
Click to expand...
Click to collapse
Ah... SUFBS to the rescue! Did it from the terminal. Works perfectly! Thanks!
mcamou said:
Thanks! Now if I could only get adb to work... doing adb shell gives me "error: device not found", and turning on AdbWireless and trying to connect with adb connect just hangs.
Click to expand...
Click to collapse
Renate NST said:
Set a PIN lock on your Nook.
In an ADB shell:
Code:
am start -n com.android.settings/.ChooseLockPin
Click to expand...
Click to collapse
How to remove the lock?
I don't know if there is an easy user way to do this, but:
Code:
sqlite3 settings.db
delete from system where name like 'lock%';
.q
Either do this on the Nook in /data/data/com.android.providers.settings/databases/
Or else adb pull it, sqlite3 it, adb push it.
Renate NST said:
Set a PIN lock on your Nook.
In an ADB shell:
Code:
am start -n com.android.settings/.ChooseLockPin
Click to expand...
Click to collapse
Hi, I'm very new to rooting and have managed to get tinynoot to root my UK Simple Touch Glowlight. I can use the adb install in my command prompt but when I copied your script into the command prompt I just got a list of commands. I have looked at the adb command instructions here http://developer.android.com/tools/help/adb.html#commandsummary but still can't work out what to do. Would you mind giving me some slightly more detailed instructions for adding the lockscreen from a windows command prompt?
Thanks
EDIT 1: Just brought myself up to speed on shell stuff. Thank you, thank you, thank you Renate NST!!!!
Hi, I know this thread is a bit old but I am having a problem and I am bit of a blind baboon in a maze with all this.
I followed the directions as best I could: connected rooted Nook, started adb shell then:
Code:
# am start -n com.android.settings/.ChooseLockPin 1111
am start -n com.android.settings/.ChooseLockPin 1111
Starting: Intent { act=android.intent.action.VIEW dat=1111 }
Error: Activity not started, unable to resolve Intent { act=android.intent.actio
n.VIEW dat=1111 flg=0x10000000 }
Tried other things too but I can't code for toffees so..
Can you help?
icouldntfindit said:
Hi, I know this thread is a bit old but I am having a problem and I am bit of a blind baboon in a maze with all this.
I followed the directions as best I could: connected rooted Nook, started adb shell then:
Code:
# am start -n com.android.settings/.ChooseLockPin 1111
am start -n com.android.settings/.ChooseLockPin 1111
Starting: Intent { act=android.intent.action.VIEW dat=1111 }
Error: Activity not started, unable to resolve Intent { act=android.intent.actio
n.VIEW dat=1111 flg=0x10000000 }
Tried other things too but I can't code for toffees so..
Can you help?
Click to expand...
Click to collapse
Presumably that's your desired PIN (i.e. 1111?)
You don't put it on the command line, am start -n com.android.settings/.ChooseLockPin starts the PIN chooser activity on your Nook and you enter it there, twice, to set it.
cowbutt said:
Presumably that's your desired PIN (i.e. 1111?)
You don't put it on the command line, am start -n com.android.settings/.ChooseLockPin starts the PIN chooser activity on your Nook and you enter it there, twice, to set it.
Click to expand...
Click to collapse
Lmao there's something I didn't try. Thank you for replying so fast!
cowbutt said:
Presumably that's your desired PIN (i.e. 1111?)
You don't put it on the command line, am start -n com.android.settings/.ChooseLockPin starts the PIN chooser activity on your Nook and you enter it there, twice, to set it.
Click to expand...
Click to collapse
I have to say thank you, first, for providing this information! It was exactly what I wanted.
Now, though, I've been locked out of my device. I think pressure from inside my bookbag created a bunch of readings that the nook took as attempts to access the system, and I'm locked out after 'too many pattern attempts.' It says: "to unlock, sign in with your Google account." But I do that, with no response. (This is without active wi-fi, which I can't activate anyway!)
I was hoping I could use ADB to reset the PIN again, but ADB doesn't appear to recognize the system; maybe it's not opening up the device to USB until it gets unlocked.
I'm currently on the road so I can't go back to my home wi-fi...
Any suggestions?
jasonmehmel said:
Any suggestions?
Click to expand...
Click to collapse
Well, on my Nook, I'd open up the Nook, hook into the console connector and do the SQLite solution to delete the lock and reboot.
You probably never got around to soldering a console connector to your Nook.
If you had access to ADB you could do the same.
Apparently you have ADB over WiFi and the WiFi is off.
I could also boot up on Clockwork Mod Recovery and use ADB over USB.
(I already have CWM as my recovery internally.)
You could put CWM on an SD card and boot that.
Renate NST said:
...
I could also boot up on Clockwork Mod Recovery and use ADB over USB.
(I already have CWM as my recovery internally.)
You could put CWM on an SD card and boot that.
Click to expand...
Click to collapse
I basically did that. Not CWM specifically, but factory resetting it and then re-rooting it. I'm getting a lot of practice at rooting the little son of a gun...
jasonmehmel said:
... factory resetting ...
Click to expand...
Click to collapse
I didn't say anything about factory resetting.
The only way to fix things is to know what's going on.
Why don't you get a console somehow going to your device and fix the settings database?
Hello,
I have just rooted my nook ST glowlight using Nook manager, and it is my first android device so I am not very familiar with this world. I have installed android SDK on my laptop and started an adb console. I can see my device connected when I list the devices but when I run
am start -n com.android.settings/.ChooseLockPin
it says that 'am' is not recongnized as a command.
Could you please help here?
Many thanks
MRXIII said:
it says that 'am' is not recognized as a command
Click to expand...
Click to collapse
Interesting. Try
Code:
ls -l /system/bin/am
ls -l /system/bin/pm
Did you accidentally delete something?
This is the NG1 (old black Nook Glow)?
Renate NST said:
Interesting. Try
Code:
ls -l /system/bin/am
ls -l /system/bin/pm
Did you accidentally delete something?
This is the NG1 (old black Nook Glow)?
Click to expand...
Click to collapse
Hi Renate
Thank you for your reply. I am using windows, is ls supposed to work with adb ? I have tried but it says the same :/
'ls' is not recognized...
I did not delete anything as far as I know. It is the nook Simple touch glowlight (black)
thanks
Ha, ha, the joke's on me.
That "am" command is supposed to be executed in a Linux shell running over ADB.
Code:
C:\>adb shell
# am start -n com.android.settings/.ChooseLockPin
# ^C
C:\>
Renate NST said:
Ha, ha, the joke's on me.
That "am" command is supposed to be executed in a Linux shell running over ADB.
Code:
C:\>adb shell
# am start -n com.android.settings/.ChooseLockPin
# ^C
C:\>
Click to expand...
Click to collapse
Hi Renate
Happy new year.!
Is there a way to achieve lock screen using a windows shell ?
Thank you
MRXIII said:
Is there a way to achieve lock screen using a windows shell?
Click to expand...
Click to collapse
Do you mean:
Code:
C:\>adb shell am start -n com.android.settings/.ChooseLockPin
In the car this morning on my way to work, listening to music (default music player), Waze running in the background. Pretty much as I do every morning.
All of a sudden the S5 rebooted itself. Just like that, out of the blue. No messages that I could see.
Is there a way I can see what has happened? A log file perhaps?
(the S5 is rooted)
yud said:
All of a sudden the S5 rebooted itself. Just like that, out of the blue. No messages that I could see.
Is there a way I can see what has happened? A log file perhaps?
(the S5 is rooted)
Click to expand...
Click to collapse
I wouldn't worry about it too much if it was a one time event. But yes, you can use the logcat command to dump the system log. From the command line, type:
Code:
$ su
# logcat > /sdcard/logcat.txt
.
fffft said:
I wouldn't worry about it too much if it was a one time event. But yes, you can use the logcat command to dump the system log. From the command line, type:
Code:
$ su
# logcat > /sdcard/logcat.txt
.
Click to expand...
Click to collapse
Thank you!