[Themeing] Stuck, adb push not working - myTouch 3G, Magic General

Hey folks,
Working on my first theme and I ran into a roadblock.
Steps up until road block:
1. Generated new colored bars for an existing theme for my rom listed in my sig.
2. Used draw9 to have the edited files in the appropriate formats.
3. zipped, renamed the attached file to the .apk format and signed it.
4. Went to cmd prompt > tools.
5. adb remount (Success)
6. adb push framework-res.apk /system/app (Success)
7. adb shell reboot
Phone reboots - No theme changes applied.
Could it possibly be I'm applying the edited files over the theme I already applied?
Any pointers would be much appreciated. I think if I nail down this process with a couple of .9 files I should be out of everyones hair until I come up with a rom/theme to share.

Related

Replacing HTC apps with ANDROID ones

Hi,
After reading this thread and learning that you CAN replace HTC's apps with stock Android ones, I have started messing around to see what other apps I can / should change. I'll use this thread as kind of a log, so if I mess things up I can come back and see where I went wrong. Fellow noobs can surely use it too!
I am using SDK in Ubuntu, but the procedure should be pretty similar in Windows.
First, follow the Unlockr's method to root your phone.
Download a stock Android rom and extract its /system/apps folder inside /sdk/tools. I named the folder "Apps-stock
Check if Ubuntu recognises your phone:
Code:
./fastboot devices
Load the recovery image and mount the system:
Code:
./fastboot boot cm-hero-recovery.img
./adb shell mount /system
Replacing HTC's calendar:
Code:
./adb shell rm /system/app/Calendar.apk
./adb shell rm /system/app/Calendar.odex
./adb push Apps-stock/Calendar.apk /system/app/
I'll edit the thread, add details as I go on
Nice one!
Please keep us informed!
Thanks for this thread.
Post moved to a more appropriate topic :
http://forum.xda-developers.com/showthread.php?p=4477971#post4477971
Thanks for setting this thread up!
Firstly, you should probably say in the first post that everyone should do a Nandroid backup first - it's saved my bacon. Might be an idea to link to the files, too?
Second, I've got a problem trying to run this method. I removed the original calendar.apk and .odex without any problems, and copied the new one over, but on rebooting, it wasn't in the list of applications anywhere. I browsed there in Astro and opened the file, which gave me an option to install it - which then gave an error of "Calendar could not be installed on this device".
I'm running the MoDaCo 2.1 custom ROM and using the calendar.apk from this thread.
Thanks for your time!
fastboot
can you tell me where this fastboot command is located? I am using Ubuntu too, but can not find fastboot. What is it for by the way?
dragonflyFZX said:
can you tell me where this fastboot command is located? I am using Ubuntu too, but can not find fastboot. What is it for by the way?
Click to expand...
Click to collapse
fastboot and adb are executables you get from the Android SDK - see here.
This thread does require your phone to be rooted, though, which would require you to have already used adb at least once....
frandavid100 said:
........
Replacing HTC's calendar:
Code:
./adb shell rm /system/app/Calendar.apk
./adb shell rm /system/app/Calendar.odex
./adb push Apps-stock/Calendar.apk /system/app/
I'll edit the thread, add details as I go on
Click to expand...
Click to collapse
how about simply replacing those files using a file explorer (like linda)? possible, or would that screw up my system?

How to push files through ADB

Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
usadevil7193 said:
hi mate...i m new to android..i own a nexus1..hav rooted without unlockin d bootloader..i am tryin to push d track ball to wake mod...evry time i type adb remount it says permission denied..any ideas to get things workin...???????
Click to expand...
Click to collapse
Welcome to XDA and Android! Are you trying to get help for your Nexus One? This forum here is specifically for the HTC Hero CDMA.
You will probably find better and more specific help in the Nexus One forums which are here: http://forum.xda-developers.com/forumdisplay.php?f=556
Great post, very easy to follow, thank you.
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
this also works for the samsung Galaxy S in recovery mode.
mikeybonez28 said:
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
Click to expand...
Click to collapse
mine shows up but then says error, device offline
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
yogi2010 said:
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
Click to expand...
Click to collapse
i had the same issue with something i was trying to push. I think you need to make sure you have exactly the same file name like caps and all. i was trying to push rootexplorer.apk and i got the same message but i then changed it to RootExplorer.apk and it work.(notice the difference in caps)
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
{LCD}Stelios said:
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
Click to expand...
Click to collapse
Make sure your have the drivers for your phone installed first of all.....Then, in your command prompt you have to change directories to the sdk (which you made harder by not installing to C:\
Try: cd Program Files\Android\android-sdk\tools
Then type: adb devices
That should return "xxxxxxdevice" connected....Then you know you have it set up.
Look in kyouko sig he has all the commands for adb
Sent from my HERO200 using XDA App
Bierce22 said:
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Click to expand...
Click to collapse
great video arse....thanks for the help donkey
Flashing fresh ROM via ADB in Linux
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
pacut said:
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
Click to expand...
Click to collapse
There is a thread somewhere on how to flash without a SD card and flashed using adb I believe, but don't take my word for it. Adb works fine with Linux, just have to set it up differently. Look in my sig and select the compile aosp on Ubuntu one and follow instructions on getting the USB set up.
Sent from Dorian's HTC Hero CDMA
Yes, I saw it. It's http://forum.xda-developers.com/showthread.php?t=911228
The fact is...still have to navigate through menu via VolumeUp/volumeDown buttons
Maybe through ROM manager, premium, I can install ROM direclty.
I am gonna trying
YES ! It works !
Hi I need help. I accidentally wipped my phone in CWM and now I'm trying to use adb push to push the update.zip into my phone sd everything seems to work but then in CMW it says there are no files..
any suggestions?
[Edit]
nevermind
I kept trying different locations
not sure which one did the trick but I'll list the one's I tried
so \update.zip /sdcard/
.... /sdcard/update.zip
(note I put "/update.zip" thinking maybe it needed to be reallocated to the same file/destination
Can i use adb push *.apk /system/app to push several files at once, and then repeat but using *.odex instead of *.apk? I keep ending up getting the same error, and i want to find out which app is messing with me...
rulermon said:
Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
Click to expand...
Click to collapse
Hey guys ...
I have also rooted my phone , everything was OK until one day i tried to write something to /system/app and i recieve this error:
in Addition , i am writing "adb shell" and it shows me $
if i am doing adb shell --> $ --> su --> it shows #
Can some1 knows what is the problem?

cant access shell...

I installed vodoo lagfix (froyo 2.2) preview6 (or what is newest as today) Before that I had replaced sh with bash, sh was link in same directory binary bash. After vodoo lagfix i encountered reboots... Then i saw that shell is inacessible and now i need to copy bash back to /system/bin (bash is zero bytes) to acess shell and fix things Looks quite simple but i simply cant do it root explorer isint working android mate either any other suggestions? Maybe i can somehow can give root permisions to some simple file explorer? Now my phone restarts as soon as i unplug it and it goes into sleep mode...
Even before that I couldnt simply copy (why there is no cp command?) i had to cat file > file
BTW voodoo really works phone is fast
I hope i posted in right thread thanks for answers.
Had a similar problem: I have JG1, and clockwork replaces my shell and it then becomes unusable.
If you still have your old shell bianry lying around somewhere, or want to "install" your bash again, you can do it by creating an update.zip file.
I've attached a template for this - copy your desired shell binary to system/bin/sh, name it update.zip, place on SD card, go into recovery mode and hit "apply: update.zip"
IMPORTANT: the attached template is untested - you can, however, use the file I actually use, and simply adjust it for your needs (replace its shell binary, and look at the update script... nevermind the "root" text in it... I simply used the rooting update.zip as a base for it...)
Here's what I need when I play around with clockwork: http://db.tt/xGDcT1y
As for the template, see the post's attachments.
I hope this helps.
Cant apply update zip, because there is no such option only reinstall apps and so on... Have 2e recovery. Looks like i will need to use heidmall or similar app.

Cannot get ADB shell working

Hi guys, so I've done tons of searching & I still can't seem to get this work.. I'm running CM7 #21 & I'm trying to install adfree using the tutorial here.. For some reason I just can't seem to get ADB shell commands working.. I can put my phone into recovery via ADB, no problem, but that's about it.. When I try running recovery-windows.bat I get "directory not found" errors, from what I can see it's looking for a "files" folder, which I don't have, & I've downloaded the SDK 3 times! Initially I didn't even have a recovery-windows.bat file, I found it somewhere & modified it.. Anyway, I've attached pics of the steps I've done, could someone tell me what I'm doing wrong, or guide me in the right direction...? thanks in advance...
Using fakeflash will get you to recovery more easily. Look in the roll up sticky for that Once in recovery the adb push syntax is thus:
adb push [file on PC] [location on phone]
For pushing a directory, c:\foo to the phone's data partition you'll want this:
adb push C:\foo /data/
Or you could use wildcards:
adb push C:\foo\* /data/foo/
The latter option is probably easier
EDIT:
I notice that this was your first post. Welcome!
Thanks for the help & welcome! What I didn't realize all this time was that I had to reboot in ClockworkMod recovery & not normal recovery, but by you directing me to the fakeflash post I figured it out.. Btw, the download link at modaco.com for the update.zip file is dead...
Rename to update.zip: http://dl.dropbox.com/u/3382637/recovery-update.zip

How to prevent update/block update

I've been reading a couple of threads on preventing OTA updates and can't seem to figure it out. I'm more interested in the sqlite & ADB method from this thread (http://forum.xda-developers.com/showthread.php?t=933291). I read this thread about 10 times over and over but can't seem to get it to work. Can someone that's knowledgeable please put instructions that an idiot like me can follow?
I have a rooted NC with firmware 1.2.
1. I've downloaded sqlite3 and nookcolor-easyADB to my PC.
2. I've extracted nookcolor-easyADB and install the install.vbs file.
3. Connected my NC to my PC via USB cable
4. My PC recognizes my NC and the microSD card as a different drive.
i followed the following steps from the thread and nothing works:
***************************************************************
Attached is a working sqlite3 binary.
Copy it to /system/bin
(I transfered it to my SD, then used rootexplorer (mount R/W) to copy into /system/bin))
you will now be able to edit sqlite databases on the nook itself.
--------------------------------------------------------------------------------
Attached Files sqlite3.7z (11.9 KB, 56 views)
--------------------------------------------------------------------------------
In your terminal:
$ adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
$ sqlite3 devicemanager.db
sqlite> update registry set value='manual' where name='com.bn.device.fota.mode';
sqlite> .q
$ adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
$ adb reboot
Congrats Your NC is now permanently blocked from any future BN OTA auto updates.
No more build.prop spoof hacks for each release (sideload only),,,,,, yada yada
***************************************************************
Questions:
should I create a directory in my PC (C:/windows/system/bin) and copy sqlite3 to the /bin folder or copy sqlite3 to my microSD card and insert it into my NC?
Please be very elementary in your answers (as you were explaining it to your 6 year old). Thanks in advance.
There is a free version of SQLite with graphic user interface that allows you to change the fota field from "auto" to "manual". Do a search of title only for "block" and you should find it.
crazyasian2 said:
I've been reading a couple of threads on preventing OTA updates and can't seem to figure it out. I'm more interested in the sqlite & ADB method from this thread (http://forum.xda-developers.com/showthread.php?t=933291). I read this thread about 10 times over and over but can't seem to get it to work. Can someone that's knowledgeable please put instructions that an idiot like me can follow?
I have a rooted NC with firmware 1.2.
1. I've downloaded sqlite3 and nookcolor-easyADB to my PC.
2. I've extracted nookcolor-easyADB and install the install.vbs file.
3. Connected my NC to my PC via USB cable
4. My PC recognizes my NC and the microSD card as a different drive.
i followed the following steps from the thread and nothing works:
***************************************************************
Attached is a working sqlite3 binary.
Copy it to /system/bin
(I transfered it to my SD, then used rootexplorer (mount R/W) to copy into /system/bin))
you will now be able to edit sqlite databases on the nook itself.
--------------------------------------------------------------------------------
Attached Files sqlite3.7z (11.9 KB, 56 views)
--------------------------------------------------------------------------------
In your terminal:
$ adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
$ sqlite3 devicemanager.db
sqlite> update registry set value='manual' where name='com.bn.device.fota.mode';
sqlite> .q
$ adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
$ adb reboot
Congrats Your NC is now permanently blocked from any future BN OTA auto updates.
No more build.prop spoof hacks for each release (sideload only),,,,,, yada yada
***************************************************************
Questions:
should I create a directory in my PC (C:/windows/system/bin) and copy sqlite3 to the /bin folder or copy sqlite3 to my microSD card and insert it into my NC?
Please be very elementary in your answers (as you were explaining it to your 6 year old). Thanks in advance.
Click to expand...
Click to collapse
1. Go here and get the sqllite browser and throw it in a directory on your pc.
2. Use adb and pull the database file from your nook to your pc (like the instructions you quoted).
3. Use the sqllite browser and make the changes and save them.
4. Use adb and push the file back to your nook.
5. Reboot your nook
6. Enjoy being free from updates.
Here's the idiot's guide that worked for me:
1. Go download the following 2 files:
nookcolor-easyADB.zip
sqlitebrowser_200_b1_win.zip
2. Extract “nookcolor-easyADB.zip
this will create a file “.android” in the following directory C:/Users/your_user_account
extract “sqlitebrowser_200_b1_win.zip” anywhere
3. Connect your NC to your PC via USB port.
4. Open the command prompt (it’s in your program, accessories directory)
You should have a prompt that looks like this – C:\Users\your_user_name>
5. Type the following command:
adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
This command will go grab the file “devicemanager.db” from your NC and place it in the following location: C:/Users/your_user_account on your PC.
6. Now go to the directory where you extracted “sqlitebrowser_200_b1_win.zip” and double click on the file “SQLite Database Browser 2.0 b1.exe”. This will run the browser that will allow you to open the file “devicemanager.db” and edit it.
7. In the browser click file/open database. It should automatically take you to where the file “devicemanager.db” is located. Select that file.
8. Click on the “Browse Data” tab.
9. Click on the “Table:” pull down menu and click on “registry’.
10. If you look at line 7, all the way to the right is the “value” column it should say “auto”.
11. Double click on “auto” and another window will pop up.
12. Change the word “auto” to “manual”.
13. Click on “Apply changes” and close the window.
14. Click on “save” button on the top left and close the browser.
15. Go back to the command prompt and type the following:
adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
This command will push the file “devicemanager.db” from your PC back to your NC with the updated file.
16. Type the following command to reboot your NC:
adb reboot
DONE!
I would think the simplest method, using materials you should be halfway familiar with from rooting, is to install ClockworkMod Recovery to your NC. I know it will stop the update from installing, but I'm not sure if the update would quit trying to install.
The simplest ways to get CWM on your NC are:
1) get the ROM Manager app and "Flash ClockworkMod Recovery"
2) if you have a CM7 sdcard, it probably already has ROM Manager, and flashing from there will also install CWM to your internal recovery.
Taosaur said:
I would think the simplest method, using materials you should be halfway familiar with from rooting, is to install ClockworkMod Recovery to your NC. I know it will stop the update from installing, but I'm not sure if the update would quit trying to install.
The simplest ways to get CWM on your NC are:
1) get the ROM Manager app and "Flash ClockworkMod Recovery"
2) if you have a CM7 sdcard, it probably already has ROM Manager, and flashing from there will also install CWM to your internal recovery.
Click to expand...
Click to collapse
This is my thinking as well. B&N tried pushing the update to me and a coworker yesterday. CWR blocked it as expected. Rebooted and all is well. As you mentioned, time will tell if B&N will continue to try to push v1.3 to me. If it becomes obnoxious, I may go this route.

Categories

Resources