I trying to extract the LiveWallpapers.apk from ctso's snackpack rom, and install it onto cyanogen's latest rom. I tried following the directions laid out by another member, but just can't get it to work. can anyone help me out with this. I'm just trying to learn what I can about flashing, cooking, and general tweaking of the android OS. there's a lot of great help here, but I'm having some trouble when it comes to breaking down the inner workings. any help is greatly appreciated. If you don't feel like typing a novel out, even a push in the right direction, for getting more into the inner working of This phone and android would be great.
EDIT: intstruction in fourth post.
nevermind, I should have kept trying stuff. figured it out.
Feel free to delete post.
hurrycaine3000 said:
nevermind
Click to expand...
Click to collapse
Instead of "nevermind" how about posting the method here to benefit others?
AndyBurns said:
Instead of "nevermind" how about posting the method here to benefit others?
Click to expand...
Click to collapse
good point, I guess if we all did that, it wouldn't have been as hard for me to figure out. Here we go then, I wanted to install the Nexus live wallpaper from ctso's Snackpack ROM, which by the way is now avaliable as a free download on the market. here's what I did
You need to have Root
Download Snackpack ROM from xda
Extract files (in this case LiveWallpapers.apk
Placed folder in Android Sdk-tools folder
open command window (Shift-right click in tools folder window)
plug in phone
Enter Recovery ( turn on phone while holding vol. down, navigate to recovery )
This is a good point to do a nandroid backup
turn on usb within recovery
in command window type
adb devices (press enter)
adb shell (press enter)
mount /system (press enter)
exit (press enter)
adb remount (press enter)
adb push LiveWallpapers.apk /system/app (press enter)
adb shell reboot (press enter)
once phone boots up you should be all set.
This process works for pushing any file to phone, from what I understand.
If I am wrong on any part of this please correct me, as I am still pretty new to the android back end. If you have any questions, let me know and I'll try to help. That's what it's about.
hurrycaine3000 said:
good point, I guess if we all did that, it wouldn't have been as hard for me to figure out. Here we go then, I wanted to install the Nexus live wallpaper from ctso's Snackpack ROM, which by the way is now avaliable as a free download on the market. here's what I did
You need to have Root
Download Snackpack ROM from xda
Extract files (in this case LiveWallpapers.apk
Placed folder in Android Sdk-tools folder
open command window (Shift-right click in tools folder window)
plug in phone
Enter Recovery ( turn on phone while holding vol. down, navigate to recovery )
This is a good point to do a nandroid backup
turn on usb within recovery
in command window type
adb devices (press enter)
adb shell (press enter)
mount /system (press enter)
exit (press enter)
adb remount (press enter)
adb push LiveWallpapers.apk /system/app (press enter)
adb shell reboot (press enter)
once phone boots up you should be all set.
This process works for pushing any file to phone, from what I understand.
If I am wrong on any part of this please correct me, as I am still pretty new to the android back end. If you have any questions, let me know and I'll try to help. That's what it's about.
Click to expand...
Click to collapse
Is there a Terminal Emulator with virtual keyboard support yet? If so, it's even easier that way... It takes three or four commands and done.
uansari1 said:
Is there a Terminal Emulator with virtual keyboard support yet? If so, it's even easier that way... It takes three or four commands and done.
Click to expand...
Click to collapse
There is one built into Cyanogen's ROM. What are the different steps? I was not 100% on how to use this.
hurrycaine3000 said:
There is one built into Cyanogen's ROM. What are the different steps? I was not 100% on how to use this.
Click to expand...
Click to collapse
Command lines should look as follows assuming you have the apk on the root of your SD card... make sure you figure out the correct command to mount /system first, as I can't remember it off the top of my mind:
su
mount XXXXXXXXXXXXXXX
cp /sdcard/xxxx.apk /system/app/
That's it.. That last command copies the file to /system/app and overwrites any file with the same name. All you need to do is reboot and you're done.
Related
ok... i am a little confused to what "adb" is and how to get "su" (superuser) via a Terminal app that i downloaded for my phone.
I type "su" and and I get "su: not found" same with "adb"
what am i not understanding?
trying to follow http://forum.xda-developers.com/showthread.php?t=797397 but the commands are not working..
i am a little new to my captivate here, so help me out. I install 2.2 and i would like to root it..
thanks in advance, and forgive my ignorance.
ADB is the Android Debug Bridge. You can read what it is here Android Debug Bridge
To use this you must first install the Android Software Development Kit found here Download the Android SDK
Read up a bit on those and search the forums to find more help. Good luck.
I was / am in the same boat.
I spent 4 hours last night getting it figured out, I sure wish I could find an Android for dummies book.
Anyway, here is what cha do....
once you dowload the adb package unzip it to the root of your c drive, you may want to rename it to some thing shorter, I just called it android.
next download the root package from the root thread here and unzip the files and copy or cut them into the tools folder of the ADB folder you placed on the root of C:
navigate to the tools folder and copy adb.exe and adbwinapi.dll to the system32 directory in windows, you will need to reboot. This will allow you to use the windows cmd line.
now I am on window 7 64 so I ran the commond line as administrator to be safe. to do this click start all prograns accessorires right click cmd and select run as admin.
change directory to the tools folder, for me "cd c:\android\tools"
Connect phone be sure usb debugging is on in the phone, (settings, application, development. it will install drivers. (I manually installed the samsung 64 bit drivers I had downloaded from samsung)
from the command promt type adb devices and hope fully it will see your phone and return with the serial number and them you are good to go with following the instructions to root from there.
I hope this helps...
Cappy
the information on how to use this is really not in one place, I spent 4 hours last night searching all over to figure it out, just so I would not ask and be belittled because there is NOT good information.
I have even been searching for any books I can find on Android so I can understand how this system works, but have found no good ones yet.
I need a nice Android for dummies type thing.
I spent an hour just to figure out it still won't run right unless you change directory to the tools folder where everything is at. ( it's been like 15 years since I messed with dos).
Some where in the wiki or bibles or all the other how toos being posted we really need better information on how to use the tools and what they are.
Cheers
Jeff
http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=android+for+dummies
WOOT looks like they have one now...
Quick Tip: Once you get the Android SDK installed, you can add the location of the Tools directory to the Windows path variable and be able to call the programs from anywhere on your computer.
Masacrk said:
Cappy
the information on how to use this is really not in one place, I spent 4 hours last night searching all over to figure it out, just so I would not ask and be belittled because there is NOT good information.
Click to expand...
Click to collapse
Sorry you feel I was trying to belittle you. I was trying to be helpful by pointing you to the proper information. You know the old saying, "You'll never learn by letting others do it for you."
Sent from my SAMSUNG-SGH-I897 using XDA App
it's all good man I did not mean you.
I was taught along time ago that there are no dumb questions but it don't seem to hold true around here I have noticed.
Quess the new generation are not as patient or willing to help as mine was.
Ha ha ha. Guess I should have picked a better screen name.
Sent from my SAMSUNG-SGH-I897 using XDA App
ugg.. I dont get it.. I finaly got it to connect to the phone, but even in windows when i type in SU I get invalid command..
uggg..
i dont get it.. please help!
go to this thread
http://forum.xda-developers.com/showthread.php?t=797397
at the bottom of the first post you will see a link to Captivate2.2rootpack.zip.
http://forum.xda-developers.com/attachment.php?attachmentid=411708&d=1285997559
download , unzip, copy contents to the tools folder of the sdk package.
Also this thread was a help,
http://forum.xda-developers.com/showthread.php?t=502010
Cheers
Jeff
Masacrk said:
go to this thread
http://forum.xda-developers.com/showthread.php?t=797397
at the bottom of the first post you will see a link to Captivate2.2rootpack.zip.
http://forum.xda-developers.com/attachment.php?attachmentid=411708&d=1285997559
download , unzip, copy contents to the tools folder of the sdk package.
Also this thread was a help,
http://forum.xda-developers.com/showthread.php?t=502010
Cheers
Jeff
Click to expand...
Click to collapse
thanks.. i think i got that far,.. I copied the files into the tools folder and I still get
Code:
$ su,busybox,sqlite3
su,busybox,sqlite3
su,busybox,sqlite3: not found
$
i even copied the files to the android, and ran it from that folder.. still no luck
what am i doing wrong?!? gosh.. i never felt soo dumb about things like this before
eatonjb said:
thanks.. i think i got that far,.. I copied the files into the tools folder and I still get
Code:
$ su,busybox,sqlite3
su,busybox,sqlite3
su,busybox,sqlite3: not found
$
i even copied the files to the android, and ran it from that folder.. still no luck
what am i doing wrong?!? gosh.. i never felt soo dumb about things like this before
Click to expand...
Click to collapse
OK. took me a little while to figure this out, too. Not sure of your level of knowledge of the terminal. If I over-simplified please forgive me.
"Extract RootPack zip file" Did you do this? I think you did from you post. Make sure you've copied the files to your "tools" subfolder in the android sdk folder.
Click the start button, click run, type "cmd", press enter.
When that window opens type "cd.." and press Enter. Keep typing "cd.." and pressing Enter until the only thing you see at the prompt is "c:\"
Now navigate to the Tools folder where ever it is you put the android sdk.
I put mine at "c:\android_sdk" so I would type "cd c:\android_sdk\tools"
Plug your phone into your computer.
Go to home screen>menu>settings>applications>development and select "USB debugging".
At the command prompt type "adb devices" and your phone should return a value (the serial number).
If that works you should be able to follow the directions below.
It's been mention that you should be able to copy the commands from the web page and right click the terminal window and select "Paste". Makes everything faster, easier and more accurate. One other thing to mention: after you perform these steps and you want to do something else through adb where you're instructed to type "su" you'll need to open the SuperUser application on your phone and press "approve" after typing "su".
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell
cd /data/local/tmp
chmod 0755 rageagainstthecage-arm5.bin
./rageagainstthecage-arm5.bin
(wait for you to get kicked from adb)
adb shell
mount -o rw,remount /dev/block/stl9 /system
exit
adb push su /system/bin/su
adb push busybox /system/bin/busybox
adb push sqlite3 /system/bin/sqlite3
adb push superuser.apk /system/app/superuser.apk
adb shell
cd /system/bin
chmod 4755 su
chmod 4755 busybox
chmod 4755 sqlite3
reboot
eatonjb said:
thanks.. i think i got that far,.. I copied the files into the tools folder and I still get
Code:
$ su,busybox,sqlite3
su,busybox,sqlite3
su,busybox,sqlite3: not found
$
i even copied the files to the android, and ran it from that folder.. still no luck
what am i doing wrong?!? gosh.. i never felt soo dumb about things like this before
Click to expand...
Click to collapse
those arent even commands. just random words you put into the terminal....
follow the instructions exactly like PersonOfKnownOrigin has posted. it works
I too was having trouble, turns out the files were extracted and were in a sub folder in the Tools folder so I copied and pasted them directly into the tools folder one by one, that worked great for me. Also, I find it easier to open command shell and use the Android Tools by holding the shift key and right clicking on the Tools folder and choose open command window here. I hope this helps.
I have a stupid path becaue my laptop messed up when I first got it and I haven't been able to fix it because DOS is difficult to me. It works fine but I am too lazy to type such a long path and if you are off at all it dosen't work.
just copy and paste the commands so you don't get them wrong, worked for me. The command is su then hit enter then enter the next command line and hit enter, works like a charm.
ok, I got it.. I misinturpted that the first line (the 3 commands in one line) was a command that I was supposed to run..
it was not..
dohh.. thanks guys for all the help... i felt kinda dumb, but now I think I am kinda smrt. I mean Smart!! (Simpsons Humor)
thanks again for the paitence.
Eaton
I have been trying to make this whole adb think work for about twenty hours strait and I still have not gotten very far. I own a mac and no pc and updated to froyo with my buddies pc. I have followed all the directions to a T over and over using terminal on the mac and I can get to the ADB commands and even to where I can see my phone by clicking devices but I must be missing something important. ANY HELP WOULD BE REALLY APPRECIATED I AM ABOUT TO PULL MY FREAKING HAIR OUT!!!
Ok, so if you can see your phone through adb, then you are definitely on the right track. Unfortunately, I'm not really familiar with OS X anymore so I'm not quite sure how to do it. Just sit tight for now until someone who does use a Mac, or has more of a clue then I do can help you out.
But seriously, don't pull your hair out. It won't stay on your head forever ya know...
Edit: oops, just saw this is JI6 (Froyo) not JF6, so I can't help you, but here is a general overview:
from terminal inside Android sdk main directory:
tools/adb devices -> list all devices connected that ADB can see
tools/adb shell -> gets a normal user shell on your phone
tools/adb reboot recovery -> reboots into recovery mode, suitable for update.zip root method
--------------------------------
Place the root update.zip on internal sdcard.
from terminal inside Android sdk directory:
tools/adb reboot recovery
Select the update software option, and you will be done.
laxwillsch said:
I have been trying to make this whole adb think work for about twenty hours strait and I still have not gotten very far. I own a mac and no pc and updated to froyo with my buddies pc. I have followed all the directions to a T over and over using terminal on the mac and I can get to the ADB commands and even to where I can see my phone by clicking devices but I must be missing something important. ANY HELP WOULD BE REALLY APPRECIATED I AM ABOUT TO PULL MY FREAKING HAIR OUT!!!
Click to expand...
Click to collapse
Start simple:
If you open a terminal on the mac, and go to your android SDK tools folder; what happens when you type ADB shell?
Or if you type any of the ADB push commands?
You need to give more detail around what you are seeing for us to help you.
Ok so if I am in terminal and i type in my /android-sdk-mac_x86/tools nothing happens and it just says /android-sdk-mac_x86/tools is a directory. But if I type the same but with /tools/abd it opens the abd command lines, like how to write code. Then when I try to "adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin"
it says "-bash: adb: command not found"
however when I type laxwillsch$ /android-sdk-mac_x86/tools/adb shell
it does give me the drop down $
but when I then try to write the next line of code "chmod 0755 rageagainstthecage-arm5.bin"
it says "chmod: rageagainstthecage-arm5.bin: No such file or directory"
I am stumped I am beginning to think i need to buy a pc as I am very interested in android development and want to learn more, but it seems all the tutorials are run assuming you are on a PC
EDIT** I have downloaded the android SDK started pack, and the 2.2 root pack and they are all in my /android-sdk-mac_x86/tools folder that is directly on my Macintosh HD for simplicity
Do you know how to change directories (cd command)?
The problem is that you are trying to work in one directory, but all your tools are in another.
So change directories to the tools directory:
cd /android-sdk-mac_x86/tools/
now run your adb commands - you may have to type ./adb to tell your mac to look in the current directory for the adb command (that is what ./ means "start here")
Also, try to understand what is happening so you can more easily troubleshoot: chmod is a command to change permissions, and you are running it on the phone. If you can't push the file to the phone, then you can change it's permisssions. I guess you never got rageagainstthecage on the phone, so there is no way to chmod it.
If you can't do this on a mac, a PC is not easier. I use both, and like both, but you need to learn basic commands first - they apply to the mac terminal and the windows cmd prompt.
Getting root means moving in and out of the phone - adb shell - puts you in a terminal on the phone. So you really need to understand cd (change directory); pwd (present working directory - shows you where you are); cp (copy); and know your current path - what the ./ does.
I hope this helps, not trying to sound condescending - maybe practice a linux terminal tutorial would help
Thanks so much, I am at school right now and cant test out all that but you are really helping me understand all this! I will post tonight and let you know how it goes. again thank you
ok so i dont have my usb cable with me but I was playing around with the commands that you suggested and ureka! i finally got to a point where it says "h70-33-65-19:tools laxwillsch$" thats a first! and when i type pwd it shows "/android-sdk-mac_x86/tools" so that means I am working out of the right directory right? and from here I enable usb debugging connect my phone then just copy and paste the codes from the thread correct?
yes, it sounds like you are on the right track. But take it nice and slow when you follow the steps. It is very important that the commands are entered exactly as you see them.
Also, one step tells you to wait for something to run and kick you out of ADB - wait just like it says - takes about 45 seconds but feels like forever.
If you are in the tools directory - just by typing "adb" no quotes will give you whole page of adb commands - if you get a "command not found", then you need to add the ./ and make it ./adb
Hope this helps and again, read the commands step by step a couple times first so you understand what is happening.
In a nutsell, you push the rage file;
change its permissions, run it;
get kicked out of ADB and then open a new ADB shell;
you are now root;
remount the system partition to give you write access when it reboots;
reboot;
push over some files;
change permissions on files you pushed;
reboot;
Some things to know - SU is a command for gaining root access; when you use SU your prompt changes (in adb shell) from $ to #
If you are succesful you should see the SuperUser app listed in your apps.
Done and Done just rooted successfully couldnt have done it without you! thanks so much
I have wiped and restored more times tonight than I can count....HELP!!!! I have a very lean rom. So lean it that it has no file explorer and I don't want to install gapps. All I want to do is install Titanium Backup (the .apk file is on the root of my SD card) with the terminal emulator and I'll be all set. I have had all different error messages, and I'm more confused now then when I started this adventure, 6+ hours ago. Any help would be great.
hockeyfamily737 said:
I have wiped and restored more times tonight than I can count....HELP!!!! I have a very lean rom. So lean it that it has no file explorer and I don't want to install gapps. All I want to do is install Titanium Backup (the .apk file is on the root of my SD card) with the terminal emulator and I'll be all set. I have had all different error messages, and I'm more confused now then when I started this adventure, 6+ hours ago. Any help would be great.
Click to expand...
Click to collapse
Just download a file manager, (es fileexplorer, or root explorer) and install it that way. or if you have adb and all the drivers you need for it.
Put the .apk in the tools folder in the SDK
and go to it in a command prompt and type adb install titaniumbackup.apk..
Or whatever you apk is named.
if you need help, dont quote this, just send me a pm for help =]
(Posting this again for others reference all this is pulled from my previous post which you can find in my signature - "Terminal/adb shell commands")
Adb commands are completely different than terminal commands.
First enter "su" to get substitute user (the # sign)
Then enter "mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system" to make the root r/w
to copy files use "cp" command
to move files use "mv" command
to remove files use "rm" command
to change file/dir permissions use "chmod"
to change directories use "cd" - "cd .." will bring you back one directory - "cd //" brings you back to root
to list files in the dir use "ls"
to read/mod/combine a file use "cat"
to edit a value use "echo"
to see running processes use "top"
to kill a process use "kill -9 PID#HERE"
ex) cp /sdcard/download/myapplication.apk /data/app/myapplication.apk
If you know any linux commands then you should know your way around terminal emulator. If you want i can give you more examples just let me know. Hope this helped
To answer your question OP, just follow my example. Except in your case it'd be something like this:
Code:
su
cp /sdcard/TitaniumBackup.apk /data/app/TitaniumBackup.apk
replace "titaniumbackup.apk" with the actual file name of your apk file.
Sent from my Android using Tapatalk
kyouko said:
(Posting this again for others reference all this is pulled from my previous post which you can find in my signature - "Terminal/adb shell commands")
Adb commands are completely different than terminal commands.
First enter "su" to get substitute user (the # sign)
Then enter "mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system" to make the root r/w
to copy files use "cp" command
to move files use "mv" command
to remove files use "rm" command
to change file/dir permissions use "chmod"
to change directories use "cd" - "cd .." will bring you back one directory - "cd //" brings you back to root
to list files in the dir use "ls"
to read/mod/combine a file use "cat"
to edit a value use "echo"
to see running processes use "top"
to kill a process use "kill -9 PID#HERE"
ex) cp /sdcard/download/myapplication.apk /data/app/myapplication.apk
If you know any linux commands then you should know your way around terminal emulator. If you want i can give you more examples just let me know. Hope this helped
To answer your question OP, just follow my example. Except in your case it'd be something like this:
Code:
su
cp /sdcard/TitaniumBackup.apk /data/app/TitaniumBackup.apk
replace "titaniumbackup.apk" with the actual file name of your apk file.
Sent from my Android using Tapatalk
Click to expand...
Click to collapse
i know theyre different,i was getting a point across, in which if he cant get it too work, try adb. Even though errors with TE usually means youre not entering something correct
davidevan said:
i know theyre different,i was getting a point across, in which if he cant get it too work, try adb. Even though errors with TE usually means youre not entering something correct
Click to expand...
Click to collapse
Yea they are. Besides, personally I'd do it the way you mentioned; either first using a filemanager (easiest imo) or via adb install
Only reason I replied was in case there was a specific reason he'd only want to use terminal emulator and not adb or a FileMan
Edit: Oh I see what I think you're referring to, the line:
Adb commands are completely different than terminal commands.
Click to expand...
Click to collapse
That was just directly copied from a post I made before something about wanting to "adb push" with TE, it had nothing to do with your response
Sent from my Android using Tapatalk
Thank you everyone. I need to use Terminal Emulator, because I'm not allowed to install the ADB drivers on my work computer, the ROM I want to use did not have a file manager packed in it and I don't want to install gapps to download one from the market. I simply want to install Titanium, so I can add a file manager and a couple of other select apps so as not to clutter up the system. As soon as I flash back to that rom, I'll try it the above mentioned way.
hockeyfamily737 said:
Thank you everyone. I need to use Terminal Emulator, because I'm not allowed to install the ADB drivers on my work computer, the ROM I want to use did not have a file manager packed in it and I don't want to install gapps to download one from the market. I simply want to install Titanium, so I can add a file manager and a couple of other select apps so as not to clutter up the system. As soon as I flash back to that rom, I'll try it the above mentioned way.
Click to expand...
Click to collapse
Ah thats sucks bro, it come in handy now and then, Listen to this guy up here since he knows more about TE than I. Also a simple google "terminal emulator" command and it might add on to your comprehension.
And judt to get this outta of the way, in TE if you do type su <enter> you get #? if you dont #,you get acces denied; denied meaning youre not rooted. Meaning it cant find an su in the bin or xbin, rendering TE pointless. So make sure youre root
hockeyfamily737 said:
Thank you everyone. I need to use Terminal Emulator, because I'm not allowed to install the ADB drivers on my work computer, the ROM I want to use did not have a file manager packed in it and I don't want to install gapps to download one from the market. I simply want to install Titanium, so I can add a file manager and a couple of other select apps so as not to clutter up the system. As soon as I flash back to that rom, I'll try it the above mentioned way.
Click to expand...
Click to collapse
btw click my thanks meter ;]
its the ony thing i have left lmao! :'(
davidevan said:
Ah thats sucks bro, it come in handy now and then, Listen to this guy up here since he knows more about TE than I. Also a simple google "terminal emulator" command and it might add on to your comprehension.
And judt to get this outta of the way, in TE if you do type su <enter> you get #? if you dont #,you get acces denied; denied meaning youre not rooted. Meaning it cant find an su in the bin or xbin, rendering TE pointless. So make sure youre root
Click to expand...
Click to collapse
and how is your computer not compatible with SDK. You dont have Windows, linux or Macc?
davidevan said:
and how is your computer not compatible with SDK. You dont have Windows, linux or Macc?
Click to expand...
Click to collapse
It's not an issue of compatibilty..... It's an issue of the IT people at work having our computers locked up so we can't install / uninstall anything from them. All I can do is transfer files from the pc to my sd. I don't have authorization to install the necessary drivers for my phone.
hockeyfamily737 said:
It's not an issue of compatibilty..... It's an issue of the IT people at work having our computers locked up so we can't install / uninstall anything from them. All I can do is transfer files from the pc to my sd. I don't have authorization to install the necessary drivers for my phone.
Click to expand...
Click to collapse
If you can transfer files from a computer to a device, then you should be able to take files from a USB drive and put them on the C drive of your computer.
waffle_ said:
If you can transfer files from a computer to a device, then you should be able to take files from a USB drive and put them on the C drive of your computer.
Click to expand...
Click to collapse
To clarify.... Yes I can access my sd card from my computer. Yes I can transfer files between my sd card and my hard drive. However, when I try to install the ADB drivers to access the rom in my phone I get a little message that I'm not authorized to add / remove hardware or software from the computer....to please contact my IT administrator. Maybe it's something I'm doing wrong, maybe it's not. If I can learn to use this emulator though, it doesn't really matter. I have ADB on my computer at home if I really need it, I'm just not inclined to turn the computer at home on very often. Thanks again to everyone for the help.
"
hockeyfamily737 said:
To clarify.... Yes I can access my sd card from my computer. Yes I can transfer files between my sd card and my hard drive. However, when I try to install the ADB drivers to access the rom in my phone I get a little message that I'm not authorized to add / remove hardware or software from the computer....to please contact my IT administrator. Maybe it's something I'm doing wrong, maybe it's not. If I can learn to use this emulator though, it doesn't really matter. I have ADB on my computer at home if I really need it, I'm just not inclined to turn the computer at home on very often. Thanks again to everyone for the help.
Click to expand...
Click to collapse
Search the dev thread for my guide on how to install adb. Might do the job for your work computer. Or just hit my avatar and find the thread that way. If you do try it let me know if it works.
#Root/Hack_Mod-Always®
laie1472 said:
"
Search the dev thread for my guide on how to install adb. Might do the job for your work computer. Or just hit my avatar and find the thread that way. If you do try it let me know if it works.
#Root/Hack_Mod-Always®
Click to expand...
Click to collapse
Sitll no good installing ADB at work, but I did get a good ADB workout at home this weekend rooting my son's Optimus......Wholy crap!!! Revert to old software, lose the lcd display, root with rage against the cage, push recovery to the phone, revert back to current version of software, lose root, and then re-root on current software with recovery already installed, what a process that was!!!! BTW.... Terminal Emulator commands worked perfect. Mistake I was making was trying to "push" from my SD card instead of "copy".
Ok now that we got Root on Arc thanks to our devs (Bin4ry...) it's time to move to the next step...recovery!
All the devs who want to discuss, brainstorm, work on and edit recovery for Arc are all invited here.
I don't consider myself a dev so I will let you begin...
Can you check which
/dev/input/eventX [X is a number]
is the Keys under the display?
On X10 it's
/dev/input/event2
f.e.:
You can try it with:
cat /dev/input/event2
now press the keys, do you see some output? If not just try the next one. Until you find the right one for the keys.
Regards
On mine (unbranded, unlocked, UK version) it's /dev/input/event1
Okay,
Flashtool is already prepared for this case!
So we can try it directly. Download latest!!!!! Flashtool (version 2.9.1) and download the chargemon.zip from my attachment.
Flashtool link:
http://forum.xda-developers.com/showthread.php?t=920746
Unzip the file and copy it into flashtool folder:
Flashtool/custom/xRecvery/
overwrite the original chargemon file!
Now open flashtool and and click "Ask Root Permissions", if that had worked you will see that the "xRecovery" Button on the right side gets activated.
Push it now!
When flashtool says -> Recovery installed.
You can reboot the device -> Now push the back button on the device during the booting process. If all works you will be in Recovery
Regards
Flashed the recovery, but it doesn't appear to be loading (tried rebooting while holding the back button, and 'adb reboot recovery')
adb reboot recovery won't work!
try opening flashtool ->Advanced -> Recovery -> Reboot in recovery.
Does this work?
Regards
Nope, didn't work!
ok, thanks for testing.
Can you check if the files are there correctly ?
use adb shell and type:
cat /system/bin/chargemon
do you get a readable text or some weird signs?
Regards
Strange symbols
As an update - I copied the correct version onto the phone (the script) and it still does the same thing
Okay thanks,
maybe this will help.Problem is that we cannot run anything from /data/.....
So Flashtool fails to install it :/
Just run the RunMe.bat
Regards
Bin4ry said:
Okay thanks,
maybe this will help.Problem is that we cannot run anything from /data/.....
So Flashtool fails to install it :/
Just run the RunMe.bat
Regards
Click to expand...
Click to collapse
File seems to be missing 'sh'. Also, getting permission denied when attempting to copy into /system/bin. (/system/bin permissions are root:shell, 755).
you're missing a file ("sh") and the adb push commands failed - I modified your batch file slightly, but it doesn't work, possibly due to the missing "sh" file
Code:
adb shell su -c "mount -o remount,rw /dev/block/mtdblock0 /system"
adb shell mkdir /system/recovery
adb push files\recoveryLT15.tar.bz2 /sdcard/arcrecovery/recovery/recovery.tar.bz2
adb push files\sh /sdcard/arcrecovery/recovery/sh
adb push files\chargerLT15 /sdcard/arcrecovery/bin/charger
adb push files\model /sdcard/arcrecovery/recovery/model
adb push files\chargemon /sdcard/arcrecovery/bin/chargemon
adb shell su -c "cp -rf sdcard/arcrecovery/* /system"
adb shell su -c "chmod 04755 /system/bin/chargemon"
adb shell su -c "chmod 04755 /system/bin/charger"
adb shell su -c "chmod 04755 /system/recovery/sh"
adb shell su -c "chmod 444 /system/recovery/recovery.tar.bz2"
Ups
Sorry i said before long day today!
Here is one with SH included.
Hope it works for you, if not i have to put it into system.img directly or you have to do all that on your own via shell directly!
Regards
Doesn't appear to be at the moment stuck on the Sony Ericsson screen when I choose reboot into recovery but it boots normally when I adb reboot it.
Powered off, then booted with back button held town, just bootloops
well this is quite good!
It seems the phone tries to start the recovery but for some reason it won't start!
It's designed the way that on next reboot it have to reboot normal, so no need to worry about this behaviour, it should be stick on the logo aswell if you push the key during boot now!
Let me think about this tomorrow, i have to think if the problem is the compiled file or the script! If it's the file we will have to wait for Z, he has the sources on the recovery and i'm just too lazy to reconstruct them for the ARC
But you can check if all files are in right place with right permissions and IF they are really the files ?
Regards
originlabs said:
Powered off, then booted with back button held town, just bootloops
Click to expand...
Click to collapse
But if you DONT press a button it boots okay or not ?
Regards
Bin4ry said:
But if you DONT press a button it boots okay or not ?
Regards
Click to expand...
Click to collapse
Yes, booting with no keys is fine.
Does the recovery mount and filesystems, and if so, does it write a log file?
Just look in the chargemon and extract the tar.bz2 to see how it works.
I think that the init from recovery (the recovery itself) is not working because of incompatible compilation.
So it cannot write anything into logs!
But it's good that the script itself is still working, we can create a working recovery now from this base
I go and get some sleep now! cu
Regards
Im following the guide on the unlocker.com. I can root the watch, flash the custom recovery with odin and copy the file over null.zip file.
The trouble i encounter is when trying to enter twrp by selecting recovery.
The android sign comes up with installing update? and then it boots back into the operating system and i have to repair it with my note 3 again? am i doing something wrong or is it just sods law?
Thanks for the help in advance
I had the same problem with mine. You have to enter the following commands after rooting to make the new recovery stick (note, don't put the $ and # symbols in the command) -
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
Full Throttle1 said:
I had the same problem with mine. You have to enter the following commands after rooting to make the new recovery stick (note, don't put the $ and # symbols in the command) -
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
Click to expand...
Click to collapse
Hi is this with the windows command? the rooting method im following is using an impactor.exe to supersu onto the system and then installing supersu on the watch with wondershare mobilego? is this the same as you?
dav08094194 said:
Hi is this with the windows command? the rooting method im following is using an impactor.exe to supersu onto the system and then installing supersu on the watch with wondershare mobilego? is this the same as you?
Click to expand...
Click to collapse
Correct. You do it through the Windows command (after rooting), the same way you flash the new recovery (TWRP) through ADB. So before flashing, type those commands and it'll allow the new recovery to stick without reverting back to the factory Samsung software every time you enter the recovery mode.
Full Throttle1 said:
Correct. You do it through the Windows command (after rooting), the same way you flash the new recovery (TWRP) through ADB. So before flashing, type those commands and it'll allow the new recovery to stick without reverting back to the factory Samsung software every time you enter the recovery mode.
Click to expand...
Click to collapse
Hi jumping in here as appears I am having the same issue. Question the recovery is added through Odin and then the ROM is added through Wondershare directly to the SD card on Gear. Where and how are the commands you typed to be added? Thinking original poster and I are in the same boat. I go to flash recovery and get complete reboot.
ptfd139 said:
Hi jumping in here as appears I am having the same issue. Question the recovery is added through Odin and then the ROM is added through Wondershare directly to the SD card on Gear. Where and how are the commands you typed to be added? Thinking original poster and I are in the same boat. I go to flash recovery and get complete reboot.
Click to expand...
Click to collapse
The correct way of installing null_ would be:
1. Root your Gear
2. Enable ADB in your Gear (Search how to enable)
3. Conenct to PC and install Gear adb drivers
4. Download ADB to your PC, unpack, in explorer go to the adb folder, Hold shift and right click the mouse, choose "Start command prompt here"
5. Run the commands listed in this thread.
6. install TWRP using odin.
7. Move your null_ zip file to Gear storage using wondershare
8. Reboot Gear into Recovery and install your null_ zip.
That should be about it... There is great guides on this forum that explains every step more detailed.
st-tps said:
The correct way of installing null_ would be:
4. Download ADB to your PC, unpack, in explorer go to the adb folder, Hold shift and right click the mouse, choose "Start command prompt here"
5. Run the commands listed in this thread.
That should be about it... There is great guides on this forum that explains every step more detailed.
Click to expand...
Click to collapse
Thats step apepars I am having issue with... is ther detailed explanation how to do? I have ADB on puter but lost once I get to "prompt" part as I've never used this method in any of my previous roots/roms.
ptfd139 said:
Thats step apepars I am having issue with... is ther detailed explanation how to do? I have ADB on puter but lost once I get to "prompt" part as I've never used this method in any of my previous roots/roms.
Click to expand...
Click to collapse
Try the thing I explained:
Hold shift on keyboard and the rightclick anywhere in the folder window. You will get a new alternativ saying something like "Start command prompt here", choose that and a command window shows.
Now copy and paste row one and press enter, row two and so on... You should notice if things go good or bad.