I AM POSTING THIS BECAUSE I HAD A VERY HARD TIME ROOTING MY BACKFLIP BECAUSE OF SO MANY DIFFERENT POSTS AND DOWNLOADS THAT EITHER DONT WORK OR JUST WRONG TRYING TO USE WAYS FROM OTHER ANDROIDS SO AS I WENT THROUGH WITH FINDING THINGS THAT WORKED I PUT IN A LOG SO I ALWAYS HAD IT AND NOW IM SHARING IT NOTE I HAVE 2.1 ON MY BACKFLIP AND THATS IT WHAT THIS TUTORIAL IS FOR! IF YOU DONT KNOW WHAT THAT IS YOU PROBABLY SHOULDNT BE TRYING THIS! <~YOUR FAIR WARNING~ BUT CLICK THE BOTTOM LEFT BUTTON ON THE TOUCHPAD (windows looking button) THEN SETTINGS / ABOUT PHONE AND YOU SHOULD SHE FIRMWARE VERSION. IT SHOULD SAY 2.1-update1....... GOT ALL THAT? GOOD! LETS DO THIS!
1st
We'll start with some downloading!(from PC) I assume you have the drivers to connect your phone to the computer. If not no worries you can get them from several hosts FREE including motorola's website. I have XP and the phone installed them automatically.. i tried on vista.. not so much they needed to be downloaded.
Anyway what i have done is compiled EVERYTHING YOU NEED TO ROOT in one zip file includes MY OWN PERSONAL SDK which in the tools folder are su.apk , superuser.apk , rageinthecage_arm5.bin , and install_root.sh (ALSO some apps Including the premium ROM Manager! but well get into that later!) HERE~>http://forum.xda-developers.com/showthread.php?p=9753200#post9753200 MUST ROOT 1ST!!
SO.. the drivers and this one zip file and the drivers are the only thing you need to download on your PC (UNLESS YOU DONT HAVE WINZIP OR SOMETHING OF SORT!)
zip file is here ~~> http://www.uploading.com/files/31fa2c2f/android.zipx/ ( just copy and paste to your preferred browser! as a new user to this forum i cant post outside links!) (if you use another SDK than one i have provided this tutorial you will not have everything you need... there will be 4 files and the command prompt missing in the tools folder!)
2nd
Now with the folder unzipped and the drivers installed open the folder that says Android SDK or somthing like that! inside you will see a folder that says tools. OPEN IT!
There will be a icon that is black and says CMD open it and run it. (it's system32 but its already directed to your sdk tools to save you the hassle (your welcome )
Meanwhile connect your phone to PC via USB and before doing anything go to settings/applications/development/ and check usb debugging and make sure its is on. (you should see the triangle with ! inside it on your notifications bar)
(THIS IS VERY IMPORTANT!)
Now in your notifications bar select USB connected and select CHARGE ONLY! (also VERY important)
Back to the System32 on your PC.
type in the command "adb devices" (NO QUOTES DUH!)
it will probably say daemon not running starting daemon then a serial # should show up under connected devices. Weather it says all that or not the serial number MUST be listed or you are not connected to the adb
If you have had no problems with this so far then this should all flow together very nicely from here out!
3rd
Now that we are connected via adb you will need to rum some commands listed here IN THIS ORDER!!! (just copy them from here one at a time, right click the cmd box and select paste, and press enter... ctrl v does not work in system32!(atleast not mine!) you should get very little feedback with each command! should just repeat what you typed.... if you got 2 pages of feedback thats an error! but if u copy and paste like suggested im sure this will be as smooth as butter!
commands =
adb push Superuser.apk /sdcard/Superuser.apk
adb push su /sdcard/su
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb push install-root.sh /data/local/tmp/install-root.sh
now with proper feedback move to these commands (in order)
adb shell <~ this should change your command prompt from the tools location to a money sign "$"
cd /data/local/tmp
chmod 0755 rageagainstthecage-arm5.bin
chmod 0755 install-root.sh
NOW AS LONG AS YOU HAVE NOT GOT ANY DENIALS OR ERRORS IN THIS PROCESS WERE GOOD TO GO!!
4th BACK TO THE PHONE!
What we need to do now is go to android market and search for /download connectbot. ITS FREE!!
Once installed on phone open it and and where it asks for host click where you see SSH and change it to Local. put what ever host name your heart desires (i used my 1st name "Josh", IT DOESNT MATTER!) now hit enter!
This should've taken you to a cmd prompt similar to system32
5th AND FINAL STEP!
more commands YAY!!! now OBVIOUSLY we can't copy from PC and Paste to ConnectBot (WHAT A SHAME!) you must type these correctly or it WILL NOT WORK!! SOOOO LETS MAKE SURE WE PAY ATTENTION AND GET OUR SPACES, FORWARD, AND BACK SLASHES CORRECT!!!! THIS IS WHAT GAVE ME THE MOST TROUBLE AND NOW THAT I HAVE MADE THIS CLEAR I DONT EXPECT ANY HATE MAIL OR ANY ONE KNOCKING MY SKILLS BECAUSE YOU, YOU, AND YOU, OH AND DID I MENTION YOU!!! TYPED IT WRONG
READY?? OK! LETS DO THIS!
cd /data/local/tmp
./rageagainstthecage-arm5.bin
your phone will go into a prompt and you MUST wait until you see
"forked **** childs" (this could take a moment) the **** will be a number once this happens close the terminal
Now reopen the terminal and it should force close the 1st time and boot just fine the 2nd! now type
/data/local/tmp/install-root.sh
and if no errors occur, like magic! YOU ROOTED! now power off the phone and back on return to connectbot and type
su the $ should become a # and it along with other apps that require root will ask for superuser permissions. just grant permission and GO!
I HOPE THIS WAS HELPFUL TO YOU AND ENJOY YOUR NEW ROOTED PHONE!
help
I cannot get this line load:
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
cannot stat 'rageagainstthecage-arm5.bin' : No such file or directory
well heres a few things i can think of...
if you are manually typing the codes maybe you missed the space before the first backslash,if copy and pasting try typing manually, if this does not work, double check that the rageagainstthecage-arm5.bin is showing in your tools directory and is also showing that its 6kb in size if its not there maybe re download the sdk or just search for the BIN file elsewhere MEANWHILE i will download the sdk i provided and make sure its not something i did and if so ill correct it. Please let me know if this helps or not
yea i just redownloaded it myself and it worked just fine, i honestly think its a typo. (no offense. i did it bout 1000 times myself on the SAME file and was ready to throw my phone computer and everything in a lake lol) just try alternate ways of typing it, some also dont know that you cant use ctrl-v to paste in system32, just right click and select paste. if no dice im very sorry... just try to redownload the sdk or locate rageagainstthecage-arm5.bin elsewhere and just copy and paste it to your sdk's tools directory replacing the old or abscent, the successful pushes however will remain where they were pushed to, no need to do that again.
I have 2.1 update 1. I rooted it no problem with z4root... Not sure why you have to go through all that trouble with yours.
xdunlapx said:
I have 2.1 update 1. I rooted it no problem with z4root... Not sure why you have to go through all that trouble with yours.
Click to expand...
Click to collapse
i personally knew nothing about rooting phones just got the idea from a friend who mentioned jailbreaking his iphone and i searched for hacks and all i found was a few tutorials like this which were all somewhat different and i tryed super1click and it failed so i just bounced back n forth until i put them together and got root successfully... never heard of or seen z4root in my searches but ill look into that next time i root. Thanx!
file is missing
How can I root my motorola backflip 1.5 to 2.1 on my iMac. I've been looking around but can't see to find a tutorial and when I do ask somewhere no one answers. Please Help thanks.
install windows on it and follow the instructions :3
So I everything went smooth until install-root.sh at the very end and I get a string of errors super long most ending with read only file system. I went through the tutorial twice to check for typos (still could of messed up but Im pretty sure I didnt). Also at the beginning for some reason install-root.sh was missing from your zip so I downloaded it else where. Could that of effected this process?
wait. My phone is apparently up to date but is only at firmware version 1.5. How do I go about that upgrade?
did the upgrade to 2.1 and still get read only errors at the very end.
same problem
nkemm2 said:
So I everything went smooth until install-root.sh at the very end and I get a string of errors super long most ending with read only file system. I went through the tutorial twice to check for typos (still could of messed up but Im pretty sure I didnt). Also at the beginning for some reason install-root.sh was missing from your zip so I downloaded it else where. Could that of effected this process?
Click to expand...
Click to collapse
I'm having the same problem.
Unable to locate su
Hello, I need some guidance as to what to do next. I'm at the step where I have to type in 'su' and receiving error: reloc_library[1244]: 707 cannot locate '_ZNK7android6Parcel15setDataPositionEj'...CANNOT LINK EXECUTABLE
I have going through the steps of rooting twice and unable to add su rights. Thank you in advance for any assistance.
sithlorddevious said:
Hello, I need some guidance as to what to do next. I'm at the step where I have to type in 'su' and receiving error: reloc_library[1244]: 707 cannot locate '_ZNK7android6Parcel15setDataPositionEj'...CANNOT LINK EXECUTABLE
I have going through the steps of rooting twice and unable to add su rights. Thank you in advance for any assistance.
Click to expand...
Click to collapse
Also having this same issue, has someone resolved this yet?
Problem
i don't know if the package was damaged when i downloaded it or if it is my computer but the folder with the files that you gave us to use for the rooting doesn't work,it marks a lot of errors when you extract the files and the only thing that it extracts are the folders only,non of the files are extracted. i was hoping to know if you have an undated link for the download or if you can give me a trick to extract it correctly.
I'm sorry I haven't been on for quite some time. At this point superoneclick should do it. I no longer have a backflip or the computer with the files I was using. I honestly believe the cheapo free up/download site I used may have corrupted the file. But at one time I completely deleted my adb and downloaded the one I posted and did a friends backflip in no time at all. I'm not sure why some are having problems and others aren't. I will see what I can find and maybe just find the original links to the files needed in the adb.
Sent from my LG-P925 using XDA App
I used 7 zip to extract. No clue if it makes a difference. And as far as downloading the missing files elsewhere as Long as they are the correct files for your operating system it should make no difference and I would suggest looking through xda and other forums as well for anything that's missing in my adb. Or anything missing from the tutorial
Sent from my LG-P925 using XDA App
cant get root
Ok I tried this method and the one on thetechguy.com and on both everything goes fine until the part were you have to type on the phones terminal cd /data/local/tmp ./rageagainstthecage-arm5.bin
Then I get an error message " can't cd /data/local/tmp ./rageagainstthecage-arm5.bin "
Only got to
I was only able to get to the rageagainstthecage-arm5.bin step. My computer will not let me download this and i have no idea how to let it slip through my security. All in all, I was getting to where I needed to be so I can update to gingerbread and I've come to a standstill again. Any other ways around this little snag? Please and Thank-you!
---------- Post added at 07:17 AM ---------- Previous post was at 07:12 AM ----------
nkemm2 said:
wait. My phone is apparently up to date but is only at firmware version 1.5. How do I go about that upgrade?
Click to expand...
Click to collapse
Manually. You can find it at the motorola site. I did it last year and now i'm trying to root mine so I can update to Gingerbread.
Related
Always perform a nandroid backup before attempting any mods.
This is a tutorial on how to change the music widget to the one of your liking. It doesn't matter if you have the Dude build and want the G build widget or have the G build and want the 1.5Hr1 widget. This will work for any cupcake (Android 1.5) user who is not happy with their current music widget. I use a windows PC and I am not a Linux guru so I'm not going to attempt to tweak my tutorial for Linux users. Hopefully it's not to hard for them to figure it out from this. (I think it's just file path differences, maybe?)
First step is to have ADB commands working on your computer. Follow this link if you don't know how to do this.
http://forum.xda-developers.com/showthread.php?t=502010
Now that you have ADB, you have to download the appropriate music player/widget that you prefer.
This one is for installing the dark blue music widget with the off-center play/pause button and the transparent record and needle logo. My personal favorite for looks, but has a play/pause with a easy to miss touch area.
http://rapidshare.com/files/227653807/Music_fancy_widget_G_build.apk
This one is for installing the plain white and pale blue music widget with rectangular shape and the large play/pause button with it's large touch area.
http://rapidshare.com/files/227653907/Music_standard_build.apk
This third option is for future development. You can "harvest" a third music widget/player from a third source that doesn't yet exist using the ADB pull command. Lets say your using build X, but build Y has a theme available and you love the themed music widget on themed build Y. What you do is perform a nandroid backup of your current build so you can return to it later and install build Y and then theme it. (Don't waist your time setting up your settings because you won't be on this build for long. Just make sure USB debugging is enabled in settings > Applications > Development so you can use ADB.) You can skip this step if you have access to a friends phone who's already running the music player/widget you want. Connect the USB cable to the phone and go into where you run your ADB commands in Command Prompt on your PC. Type in this command.
adb pull system/app/Music.apk c:\your_path_here
Click to expand...
Click to collapse
The "system/app/Music.apk" part of the command is case sensitive. This will create the Music.apk with the widget you want at the path you specify. Next you can use Fastboot to restore your nandroid backup of build X. (Nandroid saves everything. It's as if you never left.)
Next step is to rename the downloaded file "Music.apk". It's case sensitive and take note of the folder path it's in.
Next, enter the following ADB commands from the appropriate place in Command Prompt. (Start > Run > type "cmd")
adb remount
adb shell rm -r system/app/Music.apk
adb push c:\your_path_here\Music.apk system/app
Click to expand...
Click to collapse
"system/app/Music.apk" and "system/app" parts are both case sensitive.
saying no such directory, would apps to sd card cause that, and ifso what would i instead need to put in?
i never knew there was a difference between the music widgets...
whats different about them?
the gui??
pgiuoco said:
saying no such directory, would apps to sd card cause that, and ifso what would i instead need to put in?
Click to expand...
Click to collapse
On the last step, adb push, dont just put your directory, put in the file name also, Music.apk. For example, i put the file on my C directory to make it easy, so I typed "adb push c:\Music.apk system/app" without the "".
FYI - I have Apps2SD and I used the above command. Guess that doesn't make a difference, assuming because the symlinks say so? I'm such a Linux noob!!!!
bigballa said:
i never knew there was a difference between the music widgets...
whats different about them?
the gui??
Click to expand...
Click to collapse
Yes, different looking gui, the Dark Blue is very nice!
P.S. Nice write up!
setzer715 said:
On the last step, adb push, dont just put your directory, put in the file name also, Music.apk. For example, i put the file on my C directory to make it easy, so I typed "adb push c:\Music.apk system/app" without the "".
Click to expand...
Click to collapse
Wow, that was a BIG OOPS! Thanks for catching that. I fixed the original post.
Has anyone found a way to do this via Terminal Emulator? I'm at work so I wanna do this now instead of waiting till I get home.
djdeviance said:
Has anyone found a way to do this via Terminal Emulator? I'm at work so I wanna do this now instead of waiting till I get home.
Click to expand...
Click to collapse
I'm not a frequent Linux user, but I know a couple of commands. You could download the apk file to your sdcard and try this. This method is not recommended!
su
rm -r system/app/Music.apk
Click to expand...
Click to collapse
This will delete your old music player. Next, you can just install the new music player apk through Apps Installer or whatever you use in it's place. This will allow you to use the new music player as if it was any other 3rd party app. However, I recommend uninstalling it and doing it through the ADB push when you get home.
yeah the app installer method didn't work for me
pgiuoco said:
yeah the app installer method didn't work for me
Click to expand...
Click to collapse
Did you delete the original Music.apk first? Do you have cupcake, or are you using JF RC33 like it says in your sig? This music player has a widget embedded and needs cupcake. If neither of these is the problem, then just use the adb push commands in the first post. I don't recommend using apk installer. I just posted that to help out someone who was too impatient to get home to his pc.
testing567 said:
Did you delete the original Music.apk first? Do you have cupcake, or are you using JF RC33 like it says in your sig? This music player has a widget embedded and needs cupcake. If neither of these is the problem, then just use the adb push commands in the first post. I don't recommend using apk installer. I just posted that to help out someone who was too impatient to get home to his pc.
Click to expand...
Click to collapse
Haha ended up doing it at home anyways. =D Yeah i was kinda doing nothing at work. So as usual I started fidgeting with my phone.
the steps given in the first post work perfectly...!!!
i am on ADP1.5H A2SD...Gud Work...THNX..!!
If someone could post screenshots of the different UIs, that'd be great.
For some reason, when I pushed the Music.apk it worked fine, but when I tried to do the same thing with the CalendarProvider.apk, it didn't....
This method works for me as well. How do you take screenshots with the new builds?
CalendarProvider.apk... Just do a normal .apk installation.
Does this only work for Rooted phones as when I try it I get permission denied
Code:
C:\android\tools>adb shell rm -r system/app/Music.apk
rm failed for system/app/Music.apk, Read-only file system
C:\android\tools>adb shell
$ su
su
su: permission denied
$
jayaustn said:
If someone could post screenshots of the different UIs, that'd be great.
Click to expand...
Click to collapse
i second this idea
moosefist said:
i second this idea
Click to expand...
Click to collapse
I third it
music.apk
can someone post some different download links for the two different music.apk builds? rapidshare has always hated me and will still not let me download either of them saying that my ip address is already downloading something. thanks.
Can someone post pics of all the music widgets in order to compare them?
I'd been trying to figure out how to set up a few simple things in my rooted, post-MR, but otherwise stock CDMA Hero. Namely, ADB Remount permissions (/default.prop file), set up Superuser to properly manage permissions for apps that require root, and install Busybox. Ideally, I wanted to set these up manually. Turns out it's not as simple as one might hope. ADB Remount, for example, requires that you modify and repackage the boot.img/recovery.img.
So, what I've got here is a minimal update.zip file you can apply to your phone via the recovery console. Nothing crazy, it's just MoDaCo's ROM 1.1, but with everything taken out except for the aforementioned items. Once you patch your phone, just these items will be configured and your phone will still look, run, etc. the same as before. Also, a2sd will be copied to your /system/bin directory, but it's something that had to stay in the file for some reason, otherwise the phone wouldn't boot. Probably a setting Paul built into the boot.img.
In any case, here it is. It's working well for me. Hope it helps some of you out too.
****
Thanks goes to Paul of course (MoDaCo) camalot (Droid Explorer) and dagnasty for telling me about the auto-sign plugin that's available in Droid Explorer.
Instructions for manually installing Busybox over here:
http://forum.xda-developers.com/showthread.php?t=591303
****
I responded on ppcgeeks:
mercado79 said:
IAlso, a2sd will be copied to your /system/bin directory, but it's something that had to stay in the file for some reason, otherwise the phone wouldn't boot. Probably a setting Paul built into the boot.img.
Click to expand...
Click to collapse
Yup. It's a script that was added to the boot.img-ramdisk that copies all of your apps to your sd when apps2sd's requirements are met.
So if the sdcard is not partitioned correctly then ap2sd will not run, yes?
Smacky55 said:
So if the sdcard is not partitioned correctly then ap2sd will not run, yes?
Click to expand...
Click to collapse
"Correctly" is relative. If there is no EXT partition on the sdcard, then the ROM won't try to move your applications to it. But the script runs regardless.
Sorry, meant if sdcard isn't partitioned at all. Thanks for the answer.
flipzmode told me in another thread that even though this script is included, that doesn't mean that the update.zip i posted will enable apps2sd for anyone. there's more required in order to get it to work (i stripped most everything out).
A few simple questions. re -stock 1.56... rom
1) in the zip system folder, its refers to /xbin ; does that require that /system/xbin be pre-existent, or will it create it ?
2) busybox is in /system/bin on mine. Do I need to remove it?
a) if so then due to the "busybox --install -s /system/bin"
command , how do i remove the current symbolic busybox entry points?
b)have $PATH changes been applied to overwrite the current export
3) empty init.sh file?
4) google meta references?
I think I may understand the need to get bootstrap-"root" permissions established, is there another way as well?
Thanks for dealing with these noobie questions.
Thanks for this. worked out great.
willy900wonka said:
A few simple questions. re -stock 1.56... rom
1) in the zip system folder, its refers to /xbin ; does that require that /system/xbin be pre-existent, or will it create it ?
2) busybox is in /system/bin on mine. Do I need to remove it?
a) if so then due to the "busybox --install -s /system/bin"
command , how do i remove the current symbolic busybox entry points?
b)have $PATH changes been applied to overwrite the current export
3) empty init.sh file?
4) google meta references?
I think I may understand the need to get bootstrap-"root" permissions established, is there another way as well?
Thanks for dealing with these noobie questions.
Click to expand...
Click to collapse
sorry willy man. not sure what i can tell you. i'm pretty close to being a newbie myself. i never fully understood what the script was doing. i simply took the original modaco update and compared it to another script paul had posted on his forums last fall.
if you unzip the file, you should be able to see everything that's going on. the file structure is super simple, so modify it to suit your needs and give it a try. worst case, you'll need to revert to a nandroid backup. oh, and don't forget you'll need to sign the file and zip it back up in order to flash it onto the phone.
come to think of it, i guess maybe i should update the script using the latest modaco rom, though i'm not sure how helpful it'd be for everyone. to be honest, i've since bitten the bullet and moved on to flipz's rom and the gumbo kernel. runs beautifully!
Ok, so I formated the card, put the .zip file on the sdcard and tried to press home+power to enter the recovery council. When I hold home and press power I am taking to a screen that has an exclamation point and an image of the phone.
Can anyone help?
partylatino420 said:
Ok, so I formated the card, put the .zip file on the sdcard and tried to press home+power to enter the recovery council. When I hold home and press power I am taking to a screen that has an exclamation point and an image of the phone.
Can anyone help?
Click to expand...
Click to collapse
Boot the phone by holding home only. And...I'm assuming you have the recovery console installed and are rooted.
I think the problem is that a recovery boot image was not previously installed. A green screen with a set of options should've appeared.
http://forum.xda-developers.com/showthread.php?t=596879
I prefer 1.2.3
mercado79 said:
Boot the phone by holding home only. And...I'm assuming you have the recovery console installed and are rooted.
Click to expand...
Click to collapse
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
partylatino420 said:
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=596879 explanation
code from : http://forum.xda-developers.com/showthread.php?t=583291
13:
Code:
adb push recovery-RA-heroc-v1.5.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
14:
Code:
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
http://tinyurl.com/yc96j2z
partylatino420 said:
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
Click to expand...
Click to collapse
Your google search didn't turn anything up on "recovery council" because the operative use would have actually been "recovery console"..
that did it!! Thanks guys!!!
um, what???
mercado79 said:
So, what I've got here is a minimal update.zip file you can apply to your phone via the recovery console.
Click to expand...
Click to collapse
Apply via the recovery console? Sorry, still very new to this. Thanks!
Recovery Console
Go to the recovery console by holding down home when you power your Android. In that menu, you should see something that says 'flash update from SD card'... or something like that... then you choose the .zip that he has so kindly provided us.
Oh, and you have to put the .zip file that he provided on the SD card if that isn't already obvious :/
I also renamed it update.zip once I copied it to my SD card. Hope this clears it up a little. I just rooted my Hero yesterday.. so I am on the same NOOB level.
Do I need to wipe before flashing this / will this wipe my phone if I flash it?
fallonjp said:
Do I need to wipe before flashing this / will this wipe my phone if I flash it?
Click to expand...
Click to collapse
You shouldn't need to wipe your phone; however I really don't think it's a good idea to use this. I put this together last year when we were still running Android 1.5 so it's WAY out of date. Just go with Nfinite's ROMs. He keeps them almost completely stock (depending on which you choose) and they can serve as great back-up / go-to ROMs.
I had a mod done to my widgetlocker apk , but i cant adb push it. Can someone please sign it for me so i can install using root explorer? Im not sure how difficult it is , so if its insanely hard or something im sorry for asking haha . Thanks .
Get apkmanager and it will sign it for you. Plus apk manager will let you decompile and recompile then sign so you can mod anything and it's a whole lot easier.
Sent from my Incognito Droid using Tapatalk
1. Add your JDK Directory to the Path variable (Right click on My Computer, Properties, Advanced, Environment Variables)
2. At the command prompt, navigate to the containing folder
3. keytool -genkeypair
4. jarsigner -verbose APPNAME.apk mykey
5. Push the signed app
sorry guys but im not real sure what a JDK directory is or anything. I didnt do the mod myself. i made a donation and had it done by someone on here. Once they returned it to me via email they told me to adb push it.. but i do not have any exp doing that and was hoping someone could help me out... there would be a nicely themed widgetlocker.apk in it for you haha
Different problem, same answer.
I have been trying to install a custom framework res for a while now. I am on a Mac. I simply have been changing ext to zip, unzipping, making changes, rezipping, using mv command in terminal to change to apk, and pushing to phone. It hasn't even kind of worked. Could someone please help? Are there any steps I'm missing? Do I need to sign the framework res apk?
Please help
lucas.scott said:
I had a mod done to my widgetlocker apk , but i cant adb push it. Can someone please sign it for me so i can install using root explorer? Im not sure how difficult it is , so if its insanely hard or something im sorry for asking haha . Thanks .
Click to expand...
Click to collapse
Post it or post a link to it and I'll sign it.
That said, if you modify one apk it is highly unlikely you will not modify others (which is a good thing). Therefore, I would highly recommend getting acquainted with the proper tools.
First you will need to install the Android SDK on your computer. Here is the link:
http://developer.android.com/sdk/index.html Bear in mind that to use it you will also need to install the JDK (Java Developers Kit) on your computer but the links are in the instructions so it is very easy.
In addition to the SDK download 7zip if you do not already have it. It is a free archive utility that enables opening and editing the contents of archives without extracting them.
Lastly, if you just plan on editing images download Stericson's autosign tool so that once you finish changing images you can resign the apk which is necessary to install. However, if you want to delve a little deeper into apps I highly recommend Apk Manager. Not only does it include a signing tool but can also decompile apks so that you can do deeper editing.
dkdude36 said:
I have been trying to install a custom framework res for a while now. I am on a Mac. I simply have been changing ext to zip, unzipping, making changes, rezipping, using mv command in terminal to change to apk, and pushing to phone. It hasn't even kind of worked. Could someone please help? Are there any steps I'm missing? Do I need to sign the framework res apk?
Please help
Click to expand...
Click to collapse
The framework-res.apk does not need to be resigned. In fact, there are few, if any, reasons why any system app would need to be resigned. Therefore, that should not be your issue.
That said, in the steps you listed above I see several areas which could problems so, it would be beneficial if you provided more information. Here are my initial comments:
1)When you are rezipping the apk are you recompressing the folder created when you unzipped the apk OR, are you selecting the contents of the folder (e.g. AndroidManifest.xml, res folder, etc. ) and compressing them? It is important to do it the second way I described.
2)No need to bother with the mv command as you are using it. Once you've rezipped the apk (it will likely be named Archive.zip) you will need to rename it "framework-res.apk" at which point you should only need to push the apk back to the phone. The process would go like this:
a)put modified framework-res.apk into the tools folder (located in the SDK folder)
b)open up terminal.app
c)type "cd " (without the quotes) and drag the tools folder located in the sdk folder into the terminal terminal window, and press Enter
d)type "./adb remount" (without the quotes) and press Enter
e)type "./adb push framework-res.apk /system/framework/" (without the quotes) and press Enter
f)type "./adb reboot" (without the quotes) and press Enter. (The phone will reboot which is necessary to see your changes)
g)Marvel at your accomplishment
Obviously, you should make a nandroid backup of your phone first so that in case you mess anything up you can restore it as if nothing happened.
If you have any more questions simply post them and I'd be happy to answer them. I bought and rooted my EVO the day it first came out which was before there were any Mac tutorials and have since become fluent in adb due to lots of trial and error.
could you possibly help me with my widgetlocker apk? i have adb pushed ( finally learned how to do that on mac) and it still wont install . have contacted ultralynx (he did the mod) but im not getting a response...thank you .
lucas.scott said:
could you possibly help me with my widgetlocker apk? i have adb pushed ( finally learned how to do that on mac) and it still wont install . have contacted ultralynx (he did the mod) but im not getting a response...thank you .
Click to expand...
Click to collapse
Hmmm... If ultralynx did the mod for you it is probably already signed. I've seen some of his threads and he clearly knows what he is doing. And, signing is apk-modding-101.
Where did you ./adb push the widget locker to? /system/app/ or /data/app/? Adb push does not install the apk if you push to /data/app/
My recommendation would be to do the following:
1)Using root explorer, find and delete the widgetlocker.apk from wherever you adb pushed it on your phone. Exit out of Root Explorer.
2)Reboot phone
3)Confirm that you don't have any previously installed versions of WIdget Locker on your phone. From your home screen press the menu button and navigate to Settings-->Applications-->Manage Applications-->All and look for Widget Locker. If you find it select and uninstall it.
4)Assuming the modified widget locker.apk was signed you should not need to mess with adb. You certainly can but it is not necessary and I'd hate to confuse you with the commands. So... Instead, connect the EVO to your computer and mount as disk drive. Put the widget locker.apk you want to install on your sdcard. Personally, I would recommend creating a folder named Apps and putting it in there.
5)Unmount phone as disk drive and unplug phone from computer
6) Using any file manager (Root explorer is fine) navigate to the apk on your sdcard and select install.
If that doesn't work let me know
Found problem, need answer
okolowicz said:
The framework-res.apk does not need to be resigned. In fact, there are few, if any, reasons why any system app would need to be resigned. Therefore, that should not be your issue.
That said, in the steps you listed above I see several areas which could problems so, it would be beneficial if you provided more information. Here are my initial comments:
1)When you are rezipping the apk are you recompressing the folder created when you unzipped the apk OR, are you selecting the contents of the folder (e.g. AndroidManifest.xml, res folder, etc. ) and compressing them? It is important to do it the second way I described.
2)No need to bother with the mv command as you are using it. Once you've rezipped the apk (it will likely be named Archive.zip) you will need to rename it "framework-res.apk" at which point you should only need to push the apk back to the phone. The process would go like this:
a)put modified framework-res.apk into the tools folder (located in the SDK folder)
b)open up terminal.app
c)type "cd " (without the quotes) and drag the tools folder located in the sdk folder into the terminal terminal window, and press Enter
d)type "./adb remount" (without the quotes) and press Enter
e)type "./adb push framework-res.apk /system/framework/" (without the quotes) and press Enter
f)type "./adb reboot" (without the quotes) and press Enter. (The phone will reboot which is necessary to see your changes)
g)Marvel at your accomplishment
Obviously, you should make a nandroid backup of your phone first so that in case you mess anything up you can restore it as if nothing happened.
If you have any more questions simply post them and I'd be happy to answer them. I bought and rooted my EVO the day it first came out which was before there were any Mac tutorials and have since become fluent in adb due to lots of trial and error.
Click to expand...
Click to collapse
Thanks for the help okolwoiz. I am fluent in adb and have been hacking for a while. I think I know the problem. The mod I was trying to theme (drop down notifications bar) is a .9.png, which means it is automatically resized to fit the phone. These are different than normal .png files. I know i need to use a draw9 something file in the sdk, but I don't know how. Any help would be great. Thanks
Dk
yeah i have tried all of that . It always just says "Application not installed" . No matter how i get it on the phone . ore than happy to send it to you to see if its the file or my phone .
Thanks this thread has helped me and I was just wondering through aimlessly.. And stumbled upon tis thread.
Sent from my netarchy_toast, froyo beast of a machine evo!
glad it helped someone haha
***MUNKY-TOOL***
IS AN ONBOARD ANDROID UTILITY
FEATURES
[*]Copy system.img
[*]Copy boot.img
[*]Backup efs
[*]Logcat
[*]Backup and Restore Contacts
[*]Out For A Rip
Munky-tool will locate and copy most partitions without you having to track down paths. This is convenient if you use a ROM kitchen, or just want to make a backup of your system without using custom recovery. Some devices do have weird partition names, and munky-tool will not find them. If this happens to you, run the following command in terminal emulator
Code:
ls /dev/block/platform/*/by-name
Paste the output and your device name in the comments, and I will work your device in if possible.
INSTRUCTIONS
Download zip or clone git
Place extracted munky-tool folder in system partition (must be able to set permissions)
Set permissions of munky-tool script (not the directory) to at least 775 (rwx rwx rw)
Open terminal emulator and key in 'su' for root permissions
cd to the munky-tool directory
Type ./munky-tool to execute the script and start the utility
DOWNLOAD
github
Dude once again you're creativity and hard work is paying off. Great job man
Style point for the rip bud!
Sounds very helpfull and as markbencze already replyed I gues it's working on the O+O too. Have to try it in the next days.
thx markbencze for sharing.
SaschaKH said:
Sounds very helpfull and as markbencze already replyed I gues it's working on the O+O too. Have to try it in the next days.
thx markbencze for sharing.
Click to expand...
Click to collapse
Yes. I tested it on my OPO. It went out for a rip. It will run on any device, and it will find the partitions on most.
Where's the download link dude, i'm not find download link from github ?
itsnie said:
Where's the download link dude, i'm not find download link from github ?
Click to expand...
Click to collapse
On the right side of page near the clone url, there should be a button that says download as zip.
Just realized you have to be in desktop view to see the download as zip button. I will post an additional link a little later.
Just added backup and restore contacts.
N-i-c-e!
Thank you.
I've been working on the same sort of thing, and trying to figure out how to get adb connected to the phone with debugging off, for those people (I won't use the word I'm thinking of) who don't make backups, then break the screen, or bootloop the phone. Your script makes finding the data partition trivial, but I'm still working on the "force debugging on from outside" part.
But munky is going to be part of my phone from now on.
Rukbat said:
N-i-c-e!
Thank you.
I've been working on the same sort of thing, and trying to figure out how to get adb connected to the phone with debugging off, for those people (I won't use the word I'm thinking of) who don't make backups, then break the screen, or bootloop the phone. Your script makes finding the data partition trivial, but I'm still working on the "force debugging on from outside" part.
But munky is going to be part of my phone from now on.
Click to expand...
Click to collapse
Thanks, man. Glad to hear you like it.
mike the inkman said:
***MUNKY-TOOL***
IS AN ONBOARD ANDROID UTILITY
FEATURES
[*]Copy system.img
[*]Copy boot.img
[*]Backup efs
[*]Logcat
[*]Backup and Restore Contacts
[*]Out For A Rip
Munky-tool will locate and copy most partitions without you having to track down paths. This is convenient if you use a ROM kitchen, or just want to make a backup of your system without using custom recovery. Some devices do have weird partition names, and munky-tool will not find them. If this happens to you, run the following command in terminal emulator
Code:
ls /dev/block/platform/*/by-name
Paste the output and your device name in the comments, and I will work your device in if possible.
INSTRUCTIONS
Download zip or clone git
Place extracted munky-tool folder in system partition (must be able to set permissions)
Set permissions of munky-tool script (not the directory) to at least 775 (rwx rwx rw)
Open terminal emulator and key in 'su' for root permissions
cd to the munky-tool directory
Type ./munky-tool to execute the script and start the utility
DOWNLOAD
github
Click to expand...
Click to collapse
Good Tool, do you already plan to support restore EFS? which make a full loop of running time change the EFS setting without a PC,
this can help to me to control the modem band preset selections for network testing purpose.
Azlun said:
Good Tool, do you already plan to support restore EFS? which make a full loop of running time change the EFS setting without a PC,
this can help to me to control the modem band preset selections for network testing purpose.
Click to expand...
Click to collapse
It is usually done in bootloader, but I am pretty sure I can make it work. Just need to test it before I release it. I am also going to release this as an apk soon. (Don't know how soon, but I probably won't have time for a few weeks)
An app that we can point new users to that will back up their userdata partition? Fantastic!
Rukbat said:
An app that we can point new users to that will back up their userdata partition? Fantastic!
Click to expand...
Click to collapse
Yeah, I think it will fill a need. I am going to do an APK to do the things from this script, and a corresponding GUI Linux package for APK modding, and maybe do something for Windows as I get time. In the process of moving somewhat unexpectedly, so it is taking longer than I would have liked.
Hi,
So my screen broke yesterday and I needed to check my phone for missed important calls. I know there is lots of solutions out there, but I needed a way access your screen without the installation of any software on your phone. I was lucky because my digitizer still works so I can still use the touch feature and figure out on my screen where to press . I figured i would post it, might save someone someday....
Note: Works on Android 4.0 +
You need to have have developper options enabled so this can work. So first of all, I need to enable ADB from recovery. There is lots of post on the forum and google, so I will not cover this part.
Once I had ADB enabled, I wrote a small batch file that would take a screenshot from my phone, then pull it to my pc, wait 1 sec, then restart. After I used chrome and a auto-refresh extension to refresh the image every second. I will assume that you have ADB installed and all drivers for adb working. Here it goes
1. You will need to create a batch file. Open notepad and paste this into it.
Code:
:start
adb shell screencap -p /sdcard/screen.png
adb pull /sdcard/screen.png
timeout 1
goto start
Save it as ss.txt, or whatever you like. Then go to desktop and rename ss.bat or "whatever you like.bat"
This may vary a bit if you do not have an SDcard, or if your directory is not named the same way, So change SDcard to the name of your storage folder.
Copy it to your adb directory.
2. Open a Command Prompt as Admin change directories to ADB folder. Once you are there, just type ss and the batch should start.
3. Open chrome and install an auto-refresh extension. I used this one:
HTML:
https://chrome.google.com/webstore/detail/easy-auto-refresh/aabcgdmkeabbnleenpncegpcngjpnjkc?hl=en
4.Then open your c:\ drive in chrome (type in the address bar file:///C: ). Navigate to your adb folder and open screen.png.
5. Start auto refresh on screen.png opened in chrome and set to 1 second.
Now you will have a screenshot of your phone being refreshed every second! I agree its slow, but its an easy way to get on your phone and configure other applications such as vnc or other stuff or just to get the phone number of that hot date you had last night.
Other thoughts: I your digitizer is broken, you can always just get a USB on the go adapter and plug-in a mouse and use ADB over wifi.
I guess you can also use an usb micro to hdmi adapter and plug it in to a monitor, they have them at bestbuy for 20$ if you dont want to make your life complicated.
Have Fun!
Need busybox do you not? screencap is not in my /system/xbin nor /system/bin folder
kirito9 said:
Need busybox do you not? screencap is not in my /system/xbin nor /system/bin folder
Click to expand...
Click to collapse
What phone and what rom are you using? What I read is that some vendors do not include screencap in their stock rom. ..
Steph_D said:
What phone and what rom are you using? What I read is that some vendors do not include screencap in their stock rom. ..
Click to expand...
Click to collapse
Using Blu Dash Jr D140a, stock ROM ( Gingerbread 2.3.6)
kirito9 said:
Using Blu Dash Jr D140a, stock ROM ( Gingerbread 2.3.6)
Click to expand...
Click to collapse
Should of mentionned, dosen't work with gingerbread, you need 4.0+ if i recall correctly. Maybe, if your lucky, the manufacturer may have included their version instead of screencap since it did not exist back, i would take a look in the bin folder to try to find an equivalent if not you are out of luck with this method.
Steph_D said:
Should of mentionned, dosen't work with gingerbread, you need 4.0+ if i recall correctly. Maybe, if your lucky, the manufacturer may have included their version instead of screencap since it did not exist back, i would take a look in the bin folder to try to find an equivalent if not you are out of luck with this method.
Click to expand...
Click to collapse
OP should be updated then and here's my bin folder.
kirito9 said:
OP should be updated then and here's my bin folder.
Click to expand...
Click to collapse
Ya, I don't believe it will be possible for you using this method. :/ Sorry Will update original post...
Steph_D said:
Ya, I don't believe it will be possible for you using this method. :/ Sorry Will update original post...
Click to expand...
Click to collapse
No problem, I will try on my 4.2.2 device.
EDIT: It works bro. Nice little guide of doing it manually