Related
Just a quick note to everyone who is constantly switching between ROM's with their 'daily driver' phone.
Make sure all of your apps are backed up using Astro or AppControl. They will be backed up to /sdcard/backups/apps.
Once your new ROM is installed, and your phone has been wiped, mount your SD card on your PC.
Open a command prompt and navigate to the \backups\apps folder on your SD card.
(this assumes that your adb.exe is in your PATH)
In the command prompt, type in:
for %%f in (*.apk) do adb install %%f
Watch all of your apps install! This really saves a lot of time over using Astro or AppControl to re-install all of your apps.
Absolutely brilliant!
I've done this dozens of times over the last couple weeks. I felt so dumb finding this little snippet of code after manually installing 100+ apps every time I wanted to try a new ROM.
Huh, how about a script to back up via adb? Or backup/restore app data?
Actually, the latter is far more important =P.
I think easy backup restore is with astro file manager...
SpaceBoy2000 said:
Huh, how about a script to back up via adb? Or backup/restore app data?
Actually, the latter is far more important =P.
Click to expand...
Click to collapse
That's more difficult since the data is stored in a DB inside Android (for most apps, anyway). I noticed there is a sqlite3.exe inside the Android SDK so I assume you can query the DB using that and extract certain data, for example SMS and call history, just need to invest a bit of time reading up I think!
hello. i managed to get ubuntu running on my tablet, and i thought i'd share how i did it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
note that this does not change your android setup, ubuntu will run on top of android. you will not lose any data if everything goes well.
all credit goes to user houzuoguo for his guide and the people he cites for their work. this post is based on this one.
my setup
zpad clean 3.0 with pershoots latest kernel. i don't know if it will work with other combinations, so if you try and succeed with a different system please tell me. also, if it doesn't work try using pershoot's kernel on your current rom and trying again.
when reporting success or failure, make sure to note whether you are using any of the new data2loop, data2ext, or other weird fs hacks.
what you'll need
the main ubuntu package. download with a torrent client (much preferred to save the devs bandwidth) here. if you don't know how to use torrent clients or can't for some reason, you can direct download from here.
android vnc viewer. it's on the market.
better terminal emulator, also on the market.
the attached zip file.
maybe adb, depending on your storage situation (more later.)
NO APPS ON YOUR SD CARD. just move them all to your internal storage with the built in application manager. the guide i linked above has instructions for trying to do it with apps on your sd, but i'm not even gonna bother. do it at your own risk and all that.
get to it
1. extract the attached zip. you should have a folder called "ubuntu" with three scripts (one letter filenames) inside.
2. open the ubuntu package you downloaded, go into the "linux" directory, and extract JUST "rootfs.ext2" to the "ubuntu" folder you just made.
3. rename "rootfs.ext2" to "ubuntu.img"
4. okay, decision time. you want at least 2gb free on the partition you're putting ubuntu. if you have the room on your sd card, you can just put it there with android's built in mass storage mode. if you need more room and it has to go on your internal storage, you can put it there.
if you decide to put ubuntu on external storage (i did) you need to make one small change to the "b" script in your ubuntu folder. open "b" with notepad or your favorite text editor, and change line 15 (losetup /dev/block...) to say "sdcard2" instead of "sdcard". again, this is for zpad clean. i don't know if other roms mount storage in the same way. (EDIT: looks like TNT stock and TNT Lite do, at least)
also if you decide to use external storage, the built in mass storage mode won't work to mount it. instead you can use an ftp server or adb to get your files on internal storage. i use the swiftp android app from the market and coreftp for windows to transfer files. this is very slow, so you can use "adb push file\path /sdcard2/file/path" to transfer over usb if you'd like. also, i guess, you could just pull the sdcard and throw it in a reader.
btw, if you do have adb running you can use it to do most everything below, it's handy. i'd recommend hooking a keyboard up to your tablet if not, there's a lot of typing. hint: control + d twice in adb will send it to the shell
5. ok, so now you have a directory called "ubuntu" with 4 files (u, e, b, ubuntu.img) inside. it's either on your internal flash, or on your sd card with the modified "b" file. if that sounds like you, move on.
6. because we don't have a trackball, and we need a special key for some of the stuff we're doing, you need "better terminal emulator" from the market. open the preferences and change your "Control Key" to volume down. also check "start as root" while you're in there.
7. in the terminal, type "cd /sdcard2/ubuntu" (or sdcard/ubuntu, depending on where you got it. i'm not going to differentiate again, you can figure it out)
8. now "sh u" (ignore rm -r -f errors)
9. when it tells you to, type "b" and hit enter.
10. if you see “[email protected]:/#” then you've successfully booted into a ubuntu shell. you can be done now, if you want, but most people want to see the gui, so keep going.
NOTE: always use "exit" to leave the ubuntu shell. don't just quit stuff willy-nilly. if you do quit stuff willy-nilly, open your terminal again and type "e" to clean up. you can do this a couple of times as an OCD check.
11. while in the ubuntu shell (and while connected to wifi) type "apt-get update", wait for it to finish and return a new line, then type "apt-get install tightvncserver". wait for that to finish.
12. type "cd /bin". this is where it get's really fun. now type "cat > x". this will not return a new command line, just a blank one. now type the following, hitting enter after each line, even the last one, and another one at the bottom.
Code:
rm -r -f /tmp
mkdir /tmp
chmod 777 /tmp
export USER=root
export XKL_XMODMAP_DISABLE=1
vncserver -geometry 1024x600
now press and hold volume down, and hit d. this should take you back to a new command line.
13. one more. this time do "cat > s" and enter:
Code:
export USER=root
vncserver -kill :1
vncserver -kill :2
sudo reboot
sudo halt
do volume down + d again.
14. to make those scripts executable, type "chmod 777 x" and then "chmod 777 s"
15. you're about ready. type "x" and hit enter. it will ask you for a password, which you should make, and then verify. answer "n" to the view-only password. it will only do this password stuff once, each subsequent time you run it will just do it.
16. leave the terminal app and open android-vnc-viewer. give the new connection a nickname, enter the password you just made in the terminal, choose port 5901 and use 24-bit color. hit connect.
17. in a minute you'll see ubuntu! be patient. play around when it's up, wee!
there's no sound yet, and you need to use ftp to connect to your gtab's internal storage (see bottom of post), but you get firefox! no flash.
keyboards and mice (including bluetooth HIDs) will work in ubuntu if they work in android.
some programs won't run, it's because android has stricter memory management policies than ubuntu. i'd like to get a list going of successfully run apps in ubuntu so post if you get something working.
NOTE: for some weird reason, ubuntu is using the keyboard key "d" by itself as a shortcut key, so whenever you use it it just minimizes everything. to fix this, go to the top and click (system -> preferences -> keyboard shortcuts) and look for one using "d". i think it was the very bottom one. just click the shortcut and use backspace to clear the shortcuts' function. you may have to restart your ubuntu shell for it to take.
18. to exit, hit menu -> disconnect, then in your terminal app again type "s" to stop vnc, and "exit" to leave ubuntu.
from houzuoguo in the original guide
If you have GUI running, you * MUST * type “s” (enter) to stop VNC server before you exit from Ubuntu terminal!
In case that your Android kills your Android Terminal application and you still have VNC server running, do the following steps:
a. Start Android Terminal
b. type “b” (enter) to bring back Ubuntu terminal
c. type “s” (enter) to stop VNC server
d. type “exit” (enter) to exit from Ubuntu terminal
Fail to do so you will have problem with VNC connection next time you use it.
Click to expand...
Click to collapse
from houzuoguo in the original guide
A little trick to access SD card from your Ubuntu:
1. Install “SwiFTP” from Market (freeware)
2. Set up FTP server using SwiFTP
3. In Ubuntu, “Places → Connect to Server” then:
Service type: FTP (with login)
Server: localhost
Port: (port number specified in SwiFTP, default is 2121)
Folder: /
User Name: (user name specified in SwiFTP)
Then press “Connect” and enter your password specified in SwiFTP. Now feel free to access your phone's file system!
Click to expand...
Click to collapse
19. i suspect that i'm going to have to revise this guide a lot if anyone ends up being interested, so let me know if you think i should change something.
cheers!
Ha, Good Work!
But I am expecting an full Boot to Ubuntu instead of using VNC
heeae said:
Ha, Good Work!
But I am expecting an full Boot to Ubuntu instead of using VNC
Click to expand...
Click to collapse
doesn't this thread acomplish that,
http://forum.xda-developers.com/showthread.php?t=894960
Might be a silly question but... is this a dual boot kinda thing? I've none experience with Ubuntu, but would like to.
Hi,
I have the same question as jpmi above.
Also, is this apparoach similar to this thread:
http://forum.xda-developers.com/showthread.php?t=908502
If it is, it's great that you got it working!
Having said that, I have a couple of questions, because I'd really like to do this with my Gtab:
- I know you said that you're running Zpad firmware. I'm still on stock TNT 3452, and I'd really like to get this working on stock. FYI, with stock:
/sdcard == internal SDCARD
/sdcard2 == external microSD card
Can you tell me (us) what changes in the b/e/u files need to be changed for stock?
- FYI, I had started to look into what was in that thread I linked above, and ended up borking my Gtab. However, one of the things that I noted when I was reviewing the scripts from that other implementation was that it expected to use an ext2fs for the .img, and TNT stock doesn't have the ext2fs module. I noticed that your scripts use yaff, which I think the stock TNT also uses, i.e., the big .img file is an ext2fs, and that gets mounted using a loop mount. Is that correct.
- Again, I have the same question as jpmi above. I'd really like to be able to put this ubuntu stuff JUST on the external microSD, not affecting the stock TNT stuff on the internal SDCARD (/sdcard), and be able to boot into stock TNT, start a term, and then run a (or some) command lines to bring the Gtab up in Ubuntu. Does what you describe in this thread do that?
Thanks for this, and sorry for all the questions!!
Jim
hey jim
that approach looks very similar, although it's for the nook color and wouldn't work on your gtab.
you're right, i'm going to update the OP, /sdcard points to internal and /sdcard2 to external on my ROM as well. got 'em switched. you would want to change your "b" script to use /sdcard2 and make sure that the ubuntu folder is on the external storage.
also, i'm not sure about ext2fs on TNT stock, but you can download and flash pershoots gtab kernel which will work with TNT but give you the correct support. this won't change your rom, you probably won't notice any difference at all.
the "e" and "u" scripts are all good. you don't need to mess with them.
yes, you're correct in assuming that the .img file gets mounted as a loop device. (losetup). you're also correct in saying that you will be able to boot into TNT and run ubuntu from the terminal without derailing TNT. in fact, because the ubuntu shell happens in better terminal and the gui happens in android-vnc, you can use the home button to get back into your android launcher at any time, and back into ubuntu without interrupting anything. it's pretty cool.
i hope i got you on the right track. keep in mind that this isn't my work, just adapted a teeny bit for the gtab from a guide in the nexus one forums.
good luck!
iammuze said:
hey jim
that approach looks very similar, although it's for the nook color and wouldn't work on your gtab.
you're right, i'm going to update the OP, /sdcard points to internal and /sdcard2 to external on my ROM as well. got 'em switched. you would want to change your "b" script to use /sdcard2 and make sure that the ubuntu folder is on the external storage.
also, i'm not sure about ext2fs on TNT stock, but you can download and flash pershoots gtab kernel which will work with TNT but give you the correct support. this won't change your rom, you probably won't notice any difference at all.
the "e" and "u" scripts are all good. you don't need to mess with them.
yes, you're correct in assuming that the .img file gets mounted as a loop device. (losetup). you're also correct in saying that you will be able to boot into TNT and run ubuntu from the terminal without derailing TNT. in fact, because the ubuntu shell happens in better terminal and the gui happens in android-vnc, you can use the home button to get back into your android launcher at any time, and back into ubuntu without interrupting anything. it's pretty cool.
i hope i got you on the right track. keep in mind that this isn't my work, just adapted a teeny bit for the gtab from a guide in the nexus one forums.
good luck!
Click to expand...
Click to collapse
Hi,
Thanks for the info.
The ext2fs thing is a stopper for me, as I don't want to (permanently) switch off of stock TNT yet, so the kernel thing is a kind of no-go.
At one point, I thought that it was possible to add filetype support using modules, e.g. using modprobe and the appropriate .so, but haven't figured that one one.
Another way: I think you did this with Zpad? So, I'm assuming that comes with ext2fs support? Is that via modprobe, or is it built into the Zpad kernel?
Again, thanks for the info.
Jim
Running with vnc, meaning where
Got it running, but when I type a 'd' the current app minimizes, rather useless like that
I followed your instructions to the letter but after i run "sh u" and then hit b to boot I get the following error. What did I do wrong, or is it a simple mistake?
Edit: should probably mention I am using data2loop. Might be the cause of my problems...
Type 'b' to boot Ubuntu
# b
b
SET VARIABLES
SET UP LOOP DEVICE
losetup: /dev/block/loop1
MOUNT
mount: Device or resource busy
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
SET UP NETWORK
net.ipv4.ip_forward = 1
b: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexistent
b: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexistent
b: cannot create /data/local/ubuntu/etc/hosts: directory nonexistent
ENTER UBUNTU
chroot: can't execute '/bin/bash': No such file or directory
UMOUNTING
umount <path>
umount <path>
umount <path>
umount <path>
losetup: /dev/block/loop1: Device or resource busy
Click to expand...
Click to collapse
jimcpl said:
Hi,
Thanks for the info.
The ext2fs thing is a stopper for me, as I don't want to (permanently) switch off of stock TNT yet, so the kernel thing is a kind of no-go.
At one point, I thought that it was possible to add filetype support using modules, e.g. using modprobe and the appropriate .so, but haven't figured that one one.
Another way: I think you did this with Zpad? So, I'm assuming that comes with ext2fs support? Is that via modprobe, or is it built into the Zpad kernel?
Again, thanks for the info.
Jim
Click to expand...
Click to collapse
you could technically use insmod to push the correct kernel module, but in all honesty it's probably not worth it. you'd have to do it at every boot. do you have clockworkmod recovery installed? installing a new kernel is as simple as flashing it like a rom, and going back to stock is just as easy. there's nothing permanent about any changes you make, especially because the gtab comes with root access already.
and no, i have a viewsonic gtablet, i'm just using the zpad clean rom with pershoot's kernel, which comes with the ext2fs pieces built in.
bigideasmb said:
Running with vnc, meaning where
Click to expand...
Click to collapse
i suppose with a local vnc viewer (or a forwarded port) you could run ubuntu and android simultaneously with another computer. i can't imagine why, except just to do it.
Xerion said:
Got it running, but when I type a 'd' the current app minimizes, rather useless like that
Click to expand...
Click to collapse
i had this stupid-ass problem too. it turns out that ubuntu is using "d" as a keyboard shortcut, for some reason. while in the ubuntu gui, go to (system -> preferences -> keyboard shortcuts) i think it's the very bottom one. just click it and hit backspace to clear the key, and you may have to restart your ubuntu shell to see the change, it'll stick. thanks for bringing this up, i'll throw it in the OP.
dekkon said:
I followed your instructions to the letter but after i run "sh u" and then hit b to boot I get the following error. What did I do wrong, or is it a simple mistake?
Edit: should probably mention I am using data2loop. Might be the cause of my problems...
Click to expand...
Click to collapse
like i said, i haven't tried or heard of anyone trying with data2loop, so that could be your problem. also make sure that there are no apps installed to your sd card (see "what you'll need" in the OP) and try again if there are.
i said, i haven't tried or heard of anyone trying with data2loop, so that could be your problem. also make sure that there are no apps installed to your sd card (see "what you'll need" in the OP) and try again if there are.
Click to expand...
Click to collapse
I borked something and needed to do a factory reset (no big deal) which I think should have cleared out data2loop after I reinstalled my rom (TnT Lite 4.1.0 w/pershoot's 1/12 kernel). I am however trying to run this from the internal sdcard (/sdcard/ubuntu) instead of the external /sdcard2. I still get the same error.
iammuze said:
i had this stupid-ass problem too. it turns out that ubuntu is using "d" as a keyboard shortcut, for some reason. while in the ubuntu gui, go to (system -> preferences -> keyboard shortcuts) i think it's the very bottom one. just click it and hit backspace to clear the key, and you may have to restart your ubuntu shell to see the change, it'll stick. thanks for bringing this up, i'll throw it in the OP.
Click to expand...
Click to collapse
Haha, I looked everywhere except in Ubuntu itself Thanks, now I can at least play with it a bit
I ran into an issue when trying to execute the code after step 15 (the typing "x" part) in the terminal emulator. It gives me an error saying the user variable is not defined, any ideas what's going bonkers?
Unrelated to this I had to do a data/cache wipe and after that I had no issues booting up ubuntu
my setup:
zpad 3.0
pershoot's kernel
no other hacks or updates yet
This worked very well for me so far. Thanks!!!
Hi,
I'm new to the business and I spent some time to learn the environment trying different applications and different approaches for almos every action I took. Today, I have not much bigger knowledge, but I finally decided to take few things in my own hands because existing software is not fulfilling my wishes.
I started with this simple script which eases the pain of reinstalling all applications after ROM upgrade. There are few such tools already, but I found those quite bloated with unnecessary thing for my own approach.
With this script I assume:
1. There is/was SSHDroid installed (or any tool with busybox and you can access shell command line) both in old and new ROMs and your ROM have bash installed in /system/bin/.
2. Backup/restore operation includes only INTERNALLY installed applications, it completely ignores SYSTEM and SDCARD installed ones.
3. This is TEMPORARY backup so it should be as fast as possible not caring about occupied space (!). Althought I added -zip parameter to enable compression if you are running out of space on your sd.
4. Installed ROM is clean with no additional apps installed (excluding those needed by the script)
5. You have basic knowledge about bash scripting, because I take NO RESPONSIBILITY of the script behavior or data loss it can do.
So, basically it is simple. It runs like this:
1. On old ROM type: sbackup -backup
2. Flash your ROM
3. On new rom type: sbackup -restore
Just like that. The applications data is tar'ed in one file per application so if you want to get rid of any, just delete it from backup directory. The directory name is same as script name on sdcard but you can change it adding a parameter without a '-' sign at runtime (first non-option parameter is treated as backup directory path). The file is zipped because this forum disallows files without an extension so... it is zipped ;D
It was tested on my fresh LeeDroid 3.3.3 GB AFTER i installed some apps. I backed them up and then restored. All seems to be perfect right now, but I will test it more thoroghly very soon because I'm planninig to have CM7 based ROM too just to choose that I need Sense or not (two nandroids for fast switch weekly ;P).
With this script and MyBackup functionality of backing up contacts, sms, history and similar it should be quite complete approach to restore all the data needed on the fresh ROM. In the future maybe I will look at the MyBackup part too. Maybe.
Feel free to comment, use, suggest or anything you like, and have fun ;P.
How do I run this script? Do i run it from sdcard or from system /bin? When i do it from system bin it says cannot create directory. When i run it from sdcard/sbackup it says permissions denied?
Sent from my ADR6400L using Tapatalk
jgrimberg1979 said:
How do I run this script? Do i run it from sdcard or from system /bin? When i do it from system bin it says cannot create directory. When i run it from sdcard/sbackup it says permissions denied?
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
And thats why I mentioned in topic about not being a newbie (and I meant not forum newbie but more a linux newbie). The thing is, it's a simple script - without any user-proof capabilities, comments inside or something BUT...
But ok, I will try to help you run it. First of all, you have to set permissions to the script. It has to have executable permission to be run by the system (and I mean filesystem permission). This can be done by chmod instruction of busybox. Most of the times it's done like this:
chmod 755 filename
This is a reason of not running form sdcard if your sdcard is NOT ext filesystem (it is usually windows fat filesystem not to generate problems with reading it under windows).
Second thing to run is to have /system/bin/bash because first line of the script (a comment like this: #!/system/bin/bash) instructs busybox to execute script using bash. This can be simply changed by modifying this line, but you have to remember that changing the shell executing script have consequences. Differens shells have sometimes different syntax, althoght i wrote this script simply so it should run on most of them, especially sh.
Third thing is to have write permissions to the directory in which the backup will be created. In original version of the script it is /sdcard, because backup is made in /sdcard/sbackup. So, you have to check it (second error - problems with creating directory).
And a last tip - it can be run from ANYWHERE. Even if your partition does not alolow executing, you can do it like this:
bash-3.2# /sdcard/test
bash: /sdcard/test: /system/bin/bash: bad interpreter: Permission denied
bash-3.2# . /sdcard/test
OK
bash-3.2#
First try does not succeded, but second did. The trick is a dot which means to execute file with a shell not caring about why or permissions.
And thats most simple introduction I could write. It applies to ANY script you want to run.
Please anyone - if you want me to help, paste your results here because without a precise error message it can be very hard to deduce what caused for example permission denial or anything usual.
For now, I won't add any more error handling, but if there will be more users caring about, I will add it.
Installing Mods on a Defy MB525:
A Guide for the Laymen MacOS User
Read In Rich Text:
https://docs.google.com/document/d/15XYKWyjvfHr4pAV5Wtxlt_4KsM-ykmQ4pvLhOt_mzlM/edit
This began as a personal list/guide for myself since much of the info was scattered across the XDA forum and some other websites. I'm still tweaking the guide on my laptop but if anyone thinks this is useful I'd be more than willing to update it here.
I just have some questions listed below as well as a general wonder if anything I'm doing isn't that efficient. Cheers.
I. Questions:
I.A. What Apps should I use on an unrooted Defy for backup?
I.B. Which SBF do I have? (Out-of-the-box)
http://sbf.droid-developers.org/umts_jordan/list.php
I.C. Is there a way to batch restore APKs on Mac like the Windows APK Batch Installer?
http://forum.xda-developers.com/showthread.php?p=23291051
http://www.droidsector.com/blog/2010/06/23/easy-way-to-install-apk-files-using-android-sdk-for-mac/
I.D. Is it necessary to know what color the lens is? Is knowing the camera module enough?
In the Beginning…
II. Rootin'
II.A. Prepping for Unrooted Flashin'
II.A.1. Copy down your SBF info (See I.A.)
II.A.2. Find out which Defy you have:CatLog
II.A.3. Android Development Bridge (ADB is found in the Android SDK)
Download Android SDK http://developer.android.com/sdk/index.html
Drag her into a location such as Applications/Android (The location is of your choice) & unzip. Open the newly unzipped folder "android-sdk-macos" then open "tools."
In Terminal drag and drop "android" located in tools so the command looks like:
$YOURPATH/android-sdk-macosx/tools/
We will write a shortcut so that ADB can be accessed anywhere. In terminal enter:
$ open ~/.bash_profile
.bash_profile should have been opened in a Text editor. At the bottom enter the following(Remember to replace "$PATHto/xxxx" with a drag and drop of the directory):
export PATH=$PATHto/platform-tools:$PATHto/platform:$PATHto/tools=$PATH
i.e.
export PATH=/Users/BobDole/Android/android-sdk-macosx/platform-tools:/Users/BobDole/Android/android-sdk-macosx/platform:/Users/BobDole/Android/android-sdk-macosx/tools=$PATH
Save the file and jump back into Terminal. Reload the sucker:
$ source ~/.bash_profile
In Terminal open up the SDK by typing:
$ android
Press enter. this will launch the SDK Android Manager. Find the folder named, "Tools;" tick it and click the install button.
Sources: http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
II.A.4. Create a folder on your Mac to organize all your Android files. i.e.
/Users/BobDole/Documents/MotoDefy/
II.A.5. If you have been using your Defy, you will probably want to save your text messages, phone calls, photos etc. Make , non-root Apps and do a manual backup:
SMS Backup
Call Logs Backup & Restore
Source: http://wiki.cyanogenmod.com/wiki/Mo...efore_you_do_anything_.E2.80.94_Make_a_backup
II.A.6. Getroot (Contains):
busybox, copy_rootfile.sh, getroot.sh, rage.bin, su, SuperUser.apk
II.A.7. Your MOD (and any extra files)
II.B. Backup (Unrooted)
II.B.1. Optional: Preform SMS Backup & Call Logs Backup
II.B.2. Duplicate entire SDcard via mounting on a Mac.
i. Plug Defy into a Mac
ii. Defy will now have a new notification at the top, open it and select Memory Card Access.
iii. Right click (or option + mouse-click) and select duplicate.
iv. Relabel as you like and put her into you android folder for safe keeping.
Source: https://motorola-global-en-uk.custh.../defy---transfer-files-from-phone-to-computer
II.C. Rooting
II.C.1. Mount SDcard (if not already mounted) See II.B.2.i.
II.C.2. Extract Getroot.zip and drag unzipped contents onto SDcard. Once done, Eject SDcard.
II.C.3. Change Defy's USB connection to "None."
II.C.4. Go to settings - Apps - Development - USB debugging. Turn this on.
II.C.5. In terminal launch adb:
$ adb shell
Launch getroot.sh by typing:
$ sh $SDcardNAME/Getroot/getroot.sh
Re-enter ADB:
$ adb shell
"$" should now be "#." Time to copy some files including the recovery tool (up next):
# sh #SDcardNAME/Getroot/copy_rootfile.sh
Reboot!
# reboot
This should have Clockwork Recovery load on reboot. Continue to II.B. Flashing to add ROMs and Mods like CM7.
Flash Some Color
III. Flashing
III. A. Prepping for Rooted Flashin
All You Need:
Titanium Backup https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup
Your ROMs & MODs
Place them on your SDcard in an easy to find place. (Refer to II.B.2. i - ii for Mounting SDcard instructions) I'd suggest placing them at the root unless you plan on keeping them, in which case I'd place them in a folder designated for ROMs and Mods, i.e.
/SDcard/mods
The Mods and ROMs can be removed after flashing them but you may wish to keep them in a folder for quick flashing between ROMs.
III. B. Backup (Rooted)
III. B. 1. Titanium Backup
Open 'er and in the upper right corner select Batch Backup/Restore - All button, the paper with a check mark onto. (See Image 1.)
Under Backup, find Backup all user apps + system data and press RUN. (See Image 2.)
"Pause active apps" should be ticked.
Press Select all.
Press the green check in the upper right corner to begin backup.
III. B. 2. "Nandroid" Backup - via Clockwork Recovery
Reboot your Defy
Upon reboot when the phone flashes the Blue LED, press Volume Down to load the Bootmenu.
Using the volume buttons to navigate; press the power button to select Recovery > Backup and restore > Backup (All). This will take a few minutes (depending on how much is on the phone and SDcard.
Reboot after backup unless you're installing ROMs/mods.
Sources: http://wiki.cyanogenmod.com/wiki/Motorola_Defy:_bootmenu
III. B. Flash! Installing ROMs & Mods
III.B.1.
Go to Bootmenu
Recovery > Backup and restore
Wipe data/factory reset
When done, Wipe cache partition
When done, Instal zip from SDcard >Choose Zip from sdcard>Your ROM/mod .zip
When finished with all the installs select Go Back and reboot the phone.
Source: http://wiki.cyanogenmod.com/wiki/Motorola_Defy:_Full_Update_Guide#Flashing_CyanogenMod
|||. Reverting to Stock SBF
All You Need:
Windows PC **(Most Likely needed as Mac OS & Defy don't seem to get along via USB during sbf_flash's execution.)
Your Defy's Stock SBF (refer to the notes you took for it in II.A.1):
http://sbf.droid-developers.org/umts_jordan/list.php
IV. Apps of Interest
As of 2012-10
Here's the few essential and near-perfect apps:
AdAway
Blocks a great number of ads in and out of Apps. You can also customize which URLs to allow or not (white listed).
SwiftKey
I don't use too many of the type-saving features (which really are great) but the amount of slight adjustments like key height in Landscape gives the text half an inch of space! That and it's seamless (so far).
Apex Launcher
It's hard to find a smooth Launcher. Apex isn't perfect but it's the closest I've come to finding one with the most space-saving, shortcut-creating, quick-loading, customizing-featured launcher.
Turntable FM
Want continuos music… with no ads? Interested in discovering new artists or songs every time you jump on? Turntable FM has "rooms" which are entirely dj'd by it's users. If there's an open spot feel free to jump on and upload your own tunes! Just make sure you stick with the style or else you'll get "booed" off. It's a great lil' music app I've run on my laptop's browser for a good year now. It can be tempting to take part in the community but even just being a listener and grad a song here and there makes this app so great.
Tasks
Need a quick and easy To-Do list? Hook this batboy up to your Google account and have them sync back and forth. It'll only take 15seconds to add a new "task," and if you put the widget on the desktop, it only take one second to mark completed. This also allows for different lists, notes, due dates and reminders (reminders are only on the app, not on Google's.)
Solid Explorer
The only file browser you'll need. can be very simple but offers so much for such a clean app? I'll take two! Oh and you can swipe between two "windows" and drag and drop!
Honorable Mention:
Photoshop Express
Manually adjust the exposure, saturation, tint, "Black & White," contrast and brightness. Crop, straighten, rotate and flip. The basic adjustments to make your image pop. If you want auto settings like InstantHipster, I mean Instagram, try Streamzoo. Lot's of great auto settings but also offer some manual adjustments. This is the closest app I have found to manipulate photos the way I do… which isn't as close as I'd like but the closest yet.
Currents
I haven't spent much time finding a good RSS reader but Currents works just fine for me so I haven't done too much searching. Plus she's pretty minimal and to the point.
V. Notes & Terms
Terminal Commands
($ represents the username you see, merely a place holder for each line of commands you will type into Terminal. Wait for $ or # to appear before entering new commands.)
Device Identification
SOC or BAYER Camera Module?
a. Install CatLog
b. Open & your camera app.
c. Open Catlog and "Search Logs for SOC, BAYER or Camera
d. If nothing is found try reopening the camera app and repeat these steps.
Model Number MB525 or MB526?
a. Open settings > About Phone > Model No.
b. MB525 is a Defy. MB526 is Defy+.
Manufacturing date: Late January or Later are Red?
a. Look at your battery.
b. There's a Thread about what each letter/number means.
SBF info?
Rooting
Android Rooting is the process of devices running the Android mobile operating system to attain privileged control (known as "root access") within Android's subsystem. http://en.wikipedia.org/wiki/Rooting_(Android_OS)
Post One: Unlocking and Rooting
Post Two: Installing Roms / Kernels / Tweaks
Post Three: Panic Section / FAQ / Miscellaneous
Unlocking The Bootloader And Obtaining Root
*This part of the tutorial is geared towards Windows users. The MAC instructions are very similar, from what I understand. Install the package the same way. All ADB/Fastboot commands may need to start with "adb-mac" (no quotes) rather than "adb" (no quotes). Due to the vast amount of Linux distros available; instructions will vary for your device. Once ADB/Fastboot are set up all command will begin with "./adb" (no quotes) rather than "adb" (no quotes). Once ADB/Fastboot are set up; this guide is relevant to everyone.*
Time required:
20-40 minutes.
Setting up ADB for our device:
Download the AndroidSDK onto your computer.
Note: Google changes their mind every other week as to if this will be distributed as a .zip or an .exe. If you get an .zip file, simply extract the contents to your C:\ drive. For an .exe install it like you would any other program, but set the path directly to the C:\ drive when the installer asks.
Or...you can use this page to download the "ADB for Dummies AIO App."
This will automatically install ADB for you to your C:\ directory. It's very very simple this way.
If your platform-tools folder doesn't have a fastboot.exe, place this fastboot.exe file in your C:\android-sdk-windows\platform-tools (or possibly simply called tools, if you set up ADB ages ago) folder.
Now you have ADB installed! Congratulations.
Unlocking the Bootloader:
***NOTE***
This will perform a factory reset on your device. You will lose all applications. Even the data on your SD Card! I'd recommend making a Backup to your computer BEFORE performing this. There is a method for backing your data up, detailed HERE.
For the time being, there is a method available that will allow you to unlock your device (and root it) without losing your data.
For instructions, click HERE. Please note: this is a hack and isn't the "conventional" and "accepted" way of unlocking your bootloader on a nexus device. The wipe requirement is there for your safety, really, and I'm certain this will be patched in the upcoming releases.
Get the drivers:
Uninstall any previously attempted drivers if they don't work and move to the next.
Option One:
Navigate to the "Device Manager" (Control Panel > Device Manager) in Windows and Select the android device. Open the properties and select the "Install Driver" option. Pick the driver with "Install from disk." Ignore any warnings about the driver not being signed properly.
PDAnet's drivers may work if the above options don't. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
While that is downloading, on your Nexus 4: turn USB debugging on.
To do so; you must first go to Settings>About>Build Number and click seven times.
The actual setting can then be found in Settings>Developer Options>USB Debugging
Once the drivers are installed, navigate to the C:\android-sdk-windows\platform-tools folder on your computer.
Hold shift and right click. Select "Open Command Window Here."
Plug your phone into the computer. Now in this command window type:
Code:
adb reboot bootloader
(Hit Enter)
Your phone should now boot into a screen with a green android with his chest exposed.
Type this:
Code:
fastboot oem unlock
(Hit Enter)
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Driver with the newest date and install it. Now retry the code above.
Your phone will ask if you want to unlock it. Select "Yes" by using the volume keys and use power to select it.
Now, navigate to "Recovery Mode" with the volume keys. Use power to select.
A screen with another Android will pop up. Press Volume Up and Power at the same time.
Select Factory Reset. This process may take a few minutes. Be patient and let it work.
Once finished, select "Reboot."
Your phone is now unlocked!
Obtaining Root Access and Custom Recovery:
Turn on USB Debugging.
To do so; you must first go to Settings>About>Build Number and click seven times.
The actual setting can then be found in Settings>Developer Options>USB Debugging
Download the following:
SuperSU (CWM .zip)
CWM (Pick the version for your device)
Place the recovery-clockwork-VERSIONNUMBER-mako.img file into your C:\android-sdk-windows\platform-tools folder.
Put the SuperSU.zip on your phone.
Open another Command Prompt if it isn't still open. (Navigate to C:\android-sdk-windows\platform-tools and shift + right click. Select "Open Command Window Here.")
With your phone plugged in type:
Code:
adb reboot bootloader
(Hit Enter)
And wait for your phone to boot into the android again.
Now type:
Code:
fastboot flash recovery IMAGENAME.img
(Change the file name to the correct file name and Hit Enter)
Once that is finished: select the "Recovery Mode" option again on your phone.
You should get a new recovery menu here. Select "install zip from sd card" and "choose zip from sd card."
Find the SuperSU.zip that you transferred earlier and select "Yes" to installing.
Navigate back to "Reboot" and reboot your phone.
You're now rooted!
However, ClockworkMod Recovery won't continue to load after this.
To fix this, find "Rom Manager" from the market. (The free version is fine.) Use the "Flash ClockworkMod Recovery" option.
If your recovery still doesn't stick around after a reboot, you have another couple options. Find a file explorer that allows root access, such as Root Explorer. Use this program to rename /system/etc/install-recovery.sh to /system/etc/install-recovery.bak. You'll need to mount the system as r/w to do this. Root Explorer provides a button at the top to do so.
Or, you can do this completely manually by firing up ADB again and running a few commands:
Code:
adb shell
(Hit Enter)
Code:
su
(Hit Enter)
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
(Hit Enter)
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
(Hit Enter)
Congratulations!
Your phone is now unlocked, rooted, and has a custom recovery!
Continue reading the next posts for info on getting custom roms, kernels, tweaks, and more!
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***
Thanks:
Google, for making Android a reality.
VanillaTbone, for the ADB AIO app.
Efrant, for posting about a bootloader locking utility without USB.
ClockworkMod team, for being a part of making our phones as awesome as they are.
The assorted developers, who continue to push out amazing material for us to use.
The awesome community, for endlessly supporting both Android itself and its users.
Installing Custom Roms Kernels and Tweaks
All of the instructions below require your bootloader to be unlocked. Please follow the guide above and return here when you're done.
Backing Your Files Up:
Time required:
15-25 minutes.
Making a Nandroid
The first thing you're going to want to do is back up your phone's entire system. This is done by making a "nandroid."
To do this, boot into ClockworkMod Recovery. To accomplish this: Turn your phone off. Once it is completely off: hold both volume buttons and the power button until the Android with his chest exposed is displayed. Navigate to the "Recovery Mode" option and select "backup."
This will take some time. Be patient and let it finish. This process is important! You should always have a recent nandroid available on your device.
Backing Your Data Up
Install Titanium Backup from the market.
Open Titanium Backup. A Superuser request should pop up. Allow it. Note: if Titanium Backup then says it failed to obtain root access; press the menu button and select more>reload application.
Press menu>batch. Select "Backup all User Apps." Select all and "Run the Batch Operation."
Let the process complete. This may take quite some time: depending on how many applications you have installed.
You can now backup your Text Messages, Bookmarks, and WiFi addresses with Titanium Backup as well.
Press Menu>Backup Data To XML to do so.
Backing Your Contacts Up
Note: This process may or not be useful to you. The Google servers should automatically import any contacts you have stored back whenever you install a new rom. Also note that Facebook/Google+/etc contacts will need to be synced again through their respective applications.
Open the Contacts application.
Press the Menu button.
Select import/export.
Export to storage.
Installing A Rom (Or Kernel/Radios/Tweaks/Themes/etc.)
Time Required:
5-10 minutes.
Note:
Follow the guide above about backing your phone up before attempting!
This guide will also work for flashing kernels/radios/themes/tweaks/etc. Simply ignore the part about wiping data and wipe whatever the thread says you should. You only need to restore data after a rom install.
Find a Rom You'd Like To Try:
Nexus 4 Original Development
Nexus 4 Development
Download the rom you'd like to try on your device.
Most roms also require you to install "gapps" as well.
You can find the correct ones for the rom you're using in the rom thread.
Make sure the Rom and Gapps are on your SD card.
Now, open Google Wallet (if you have it installed) and press Options>Settings>Reset Google Wallet. This will prevent the "Secure Element" errors some users have experienced.
Boot into ClockworkMod Recovery by turning your device completely off. Hold volume up, volume down, and power until the green Android with the open chest is displayed. Navigate to "Recovery Mode" with the volume buttons and select using the power button.
Remember to have a recent nandroid before continuing!
Navigate to "wipe data/factory reset" and select it. Select "yes."
Wait for the process to complete. This may take some time. Be patient!
Once complete: Navigate to "Install Zip from SD card" and "Choose zip from SD card."
Find the rom's .zip and install it. Once that completes install any applicable gapps' .zip.
Select the "Reboot" option.
Congratulations! Your phone should now boot into the custom rom!
Follow the prompts to re-activate your phone.
Restoring Your Applications / Contacts / Nandroid
Time Required:
5-15 minutes.
Restoring Your Applicaions
Install Titanium Backup. Note: you may want the pro key. If you have it, you won't have to manually click "install" on each application. The process is completely automated. Open Titanium Backup (grant root access. If titanium says it failed to obtain root access, press menu>more>reload application). Press menu>batch>restore missing apps with data. Now, here you have a choice to make. Do you want a completely clean install? Select "app only" and run the batch operation (Deselect Google Wallet first. We don't want to risk restoring wallet in any way. Install it manually through the Play Store.). Do you want all of your application data (saved games/settings/etc)? Select "app+data" and run the batch operation (Deselect Google Wallet first. We don't want to risk restoring wallet in any way. Install it manually through the Play Store.). This MAY cause you problems or it may not. Personally, I often restore application data and seldom run into any trouble. If you do find that restoring data caused problems, follow the guide above to re-install your rom and restore without data. This process will take some time. Be patient (I'd suggest turning your screen off so the screen doesn't burn, but that's just me.) It will vibrate upon completion.
You can now restore your Text Messages, Bookmarks, and WiFi addresses if you backed them up by pressing Menu>Restore Data From XML.
Note:
Overclocking/CPU tweaking applications should never be restored with data. Simply deselect it from the list.
Facebook/Haxsync/Google+ may have problems restoring your contacts when installed through Titanium Backup. Simply uninstall and reinstall through the market (and be sure to log in and select to sync your contacts again).
Also, if you have NFC Task Launcher successfully launching Tasker tasks with your stickers: they may not immediately work.
Through my testing, it's as simple to fix as uninstalling NFC Task Launcher and Tasker. Restore Tasker first. Then restore NFC task launcher.
Restoring Your Contacts
If google fails to restore your contacts (not facebook/haxsync/google+/etc) you may import them manually if you backed them up.
Open the contacts application and press menu>import/export>import from storage.
Restoring A Nandroid
If your phone is acting funny or won't boot...restore a nandroid from a previous rom or working set-up.
You may also use a Nandroid to switch back to a previous rom if you decide you don't like the one you're on.
Do this by booting into ClockworkMod Recovery (hold volume up, volume down, and power while your phone is off and navigate to "Recovery Mode").
Simply select "restore" and find the most recent (or relevant) backup.
This process will take some time. Be patient and let it complete! Once done, select "Reboot."
Note:
Nandroids are stored in the "clockworkmod" folder on your SD card. They take up quite a bit of space. ALWAYS have at least one recent one on your SD card. However, since these are huge files: you may like to delete old ones to save space. You must delete backups by booting into CWM and navigating to Backup and Restore>Delete.
Important Notes About Restoration
I outline the method of using Titanium Backup above for a reason. Restoring system applications and data is the most common cause of problems on custom roms. For this reason, always ONLY restore "missing applications" from "user applications" that were backed up when restoring onto a new rom. Every time you restore system data or applications a narwhal sodomizes your favorite childhood cartoon. This is FACT.
Installing Alternate Custom Recoveries
If you find a custom recovery (such as the touch-recovery options) that came as a .img file:
Use these instructions to flash. Plug your phone into the computer. Open up ADB. Move the .img to the C:\android-sdk-windows\platform-tools folder.
Type the following:
Code:
adb reboot bootloader
(Hit Enter)
You can also manually boot to the bootloader by powering off and holding volume down, volume up, power buttons until the green Android with his chest exposed is displayed.
Then type:
Code:
fastboot flash recovery FILENAME.img
(Replace the file name with whatever the .img is called and Hit Enter).
Wait for the process to complete and reboot.
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***
Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu). Navigate to recovery and select it with the power button.
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.
Code:
adb push NAMEOFZIP.zip /sdcard/NAMEOFZIP.zip
(Hit enter)
You may have to reboot recovery to get the file to show up. Now follow the guide above for flashing a rom to get you booting again.
Did you install a tweak that modified only a file or two on your phone? (Find this out by opening the .zip and looking in the folders (ignore META-INF). Good news! We MAY be able to recover you completely. If this doesn't work...you'll have to follow another method.
Get your phone into fastboot (the boot-menu that allows you to select recovery/reboot/etc). Navigate to Recovery. Start up ADB. Pull the files that were modified out of the stock rom's .zip (using whatever tweak you were installing as reference to find what was changed) that you're on into the C:\android-sdk-windows\platform-tools folder. Now we're going to push these files onto your phone...replacing the tweaked ones and hopefully getting you booted again. Use this code, but change the values of the file name and where it should reside. This is only an example!
Code:
adb shell
(Hit Enter)
Code:
su
(Hit Enter)
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
(Hit Enter)
This will mount your system so you can write to it.
Code:
exit
(Hit Enter)
This should exit shell and allow the use of adb commands again. You may need to type it a couple of times (until the #_ changes back to the platform_tools> prompt).
Code:
adb push framework-res.apk /system/framework/framework-res.apk
(Press enter after each file that you need to replace).
Note: This last option probably won't work. I'd just skip over it unless you're absolutely adamant about restoring your current setup and want to try everything possible.
Q: I want my SDcard files from my phone...but I'm in a situation where I need to flash stock images! This will erase my SD content. What can I do to save it?
A: Do you have a custom recovery installed? If not, download a custom recovery from post one in this guide and flash it using those instructions. You'll need to be in a custom recovery in order to obtain ADB access without booting your phone. Boot into recovery (With phone turned off: hold Power and Volume+ and Volume- until the bootloader pops up and navigate to "Recovery"). Run the command:
Code:
adb pull /sdcard/ /SDCARD/
(Hit Enter)
This will put all of your files into a folder called "SDCARD" in your C:\ drive. Keep in mind that this will take a LONG time. Maybe a couple of hours.
To restore once you're booting again:
Move the "SDCARD" folder you created from your C:\ drive to the platform-tools folder. *Then input:
Code:
adb push SDCARD /sdcard/
(Hit Enter)
Q: How do I make an "ADB Backup?"
A: An ADB Backup will backup your phones data (applications and their settings). Follow the guide HERE about ADB Backups.
Q: My phone gets really sluggish and often turns off or reboots on its own.
A: Without knowing anything about your situation...I'd say you either have severely bad data somewhere or some bad kernel tweaks. Use the rom install guide above, paying close attention to the part about backing up and restoring if you haven't already. In the case of a kernel problem, you're likely undervolting too low. Restore the stock kernel values and see if your problems subside.
Q: My phone screen won't turn on! This requires a battery pull to fix.
A: This is called a "Black Screen of Death" or BSOD. This is generally due to using a hotplug governor (one that turns cores off with the screen off) or possibly undervolting your device too low. Change governors or up your slots a bit.
Q: My phone is doing really weird things. Regardless of kernel/rom and even if I don't restore any data at all! Either that or I simply cannot boot up! My phone is possessed no matter what I do!
Download the stock IMAGES for your device and extract the files using 7-zip. Move all of the extracted files to your platform-tools folder. Open the flash-all.sh file with a text editor. Copy and paste the commands (one by one) and wait for each process to complete for continuing.
FAQ
Roms/Kernels
Q: What is the best rom?
A: The "best" rom is a matter of opinion. Do you like a certain customization and can't live without it? Use a rom that has that option.
Q: What is the best rom for battery life?
A: Roms themselves really shouldn't impact your battery all that much. They can have an impact, but if you're really looking for better battery I'd suggest swapping kernels or tweaking yours.
Q: What is the best rom for stability?
A: All of the roms out are "stable." They may have options that don't work correctly, but generally: this is user error. If you follow my advice on installing a rom, you'll end up with MUCH fewer bugs.
Q: What is the best kernel?
A: The best kernel is a matter of opinion. Some users may love one, while others swear by another. Find one you like and tweak it accordingly.
Q: How do I tweak a kernel for better battery?
A: Generally, you'll want to either change your governor and or undervolt and or underclock your kernel. This is done either by using SetCPU or similar apps, or with an option in your rom (usually labeled "performance" or something similar). Take note: extremely high/low voltages may cause instability. Never "set at boot" until you've thoroughly tested the options you've set. Testing includes low strain (like turning your screen off for an hour) and high strain (like playing a game for an hour) scenarios. To be extra safe: run the values for a couple days before setting them at boot. Follow the users ideas in the kernel's threads for some guidelines. However, remember that not all values will play nicely with all phones.
Miscellaneous
Q: Why isn't Google Wallet working at [store]?
A: I'm not sure if it's a Google Wallet problem, or a problem with the terminal. But I personally struggle to find a terminal that consistently works in my area. Something that has generally worked for me is to open wallet and go to Options>Reset Google Wallet. You must then re-add any cards you had.
Q: Does my ass look good in these shorts?
A: Yes.
Neat Ideas / How to Show Off the Nexus 4
-Get some NFC stickers. Tagstand has them available.
You can use these to make your phone perform certain tasks when you touch the sticker. Use NFC Task Launcher to define the tasks. These are capable of doing simple things like muting your volume to the more complex like turning on Tasker tasks that do things like auto-reply to text messages while you're at work.
-Do you have any suggestions? Submit them below!
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***
ADB Backups:
SDcard backup:
Code:
adb pull /sdcard/ /sdcard/
(This will pull all of your sdcard contents to an "sdcard" folder in your C:\ directory)
Applications and their data:
Take note, that you'll need to be using CyanogenMod's method for setting up ADB to do this. The ADB AIO application installs an older SDK without this functionality. First, get your drivers installed (detailed in post one). Once you get ADB installed (post one), navigate to the C:\android-sdk-windows\platform-tools folder on your computer. Hold shift and right click. Select "Open Command Window Here."
Input this while your phone is turned on and USB Debugging is Enabled:
To do so; you must first go to Settings>About>Build Number and click seven times.
The actual setting can then be found in Settings>Developer Options>USB Debugging
Type this:
Code:
adb backup -apk -noshared -all -nosystem
(Hit Enter)
Your phone will ask for a password. Input one and remember it.
Once the process completes: continue with unlocking and rooting your phone.
Restoration:
Upon unlocking and rooting your phone: open up ADB again.
Enter this code:
Code:
adb restore backup.ab
(Hit Enter)
Input the password you saved to this file earlier, and wait for the restore to complete.
To restore your SDcard backup, first move the "sdcard" folder that was made in the backup process to your platform-tools folder.
Then run:
Code:
adb push sdcard /sdcard/
Do you have to install "ADB" ?
As far as like...clicking it and letting the windows installer install...no.
The exe file will read the commands in cmd without "installation."
Nice Work!
I've just added this guide to the Nexus 4 Complete Index
Sent from my GT-I9100 using xda premium
Great work!!! nice and clean reading!
Can this guide include information on how to re-lock bootloader and unroot the device? Does this informaiton exist?
I need to RMA my phone due to dead pixels and I want to make sure I dont have any issues with the warranty.
jayluke said:
Can this guide include information on how to re-lock bootloader and unroot the device? Does this informaiton exist?
I need to RMA my phone due to dead pixels and I want to make sure I dont have any issues with the warranty.
Click to expand...
Click to collapse
Post 3.
fastboot oem lock
Locks the device.
How long is the first boot, after unlocking the bootloader, supposed to take? Mine's sitting there for quite a while already. (I had a lot of stuff installed, but still, this is really long.)
EDIT: When rebooting the custom recovery, you have to say "yes" to the message it gives you, something about keeping some recovery. I had originally said no because I didn't flash it, I just booted it once.
I just got my nexus yesterday, and this isnt the first phone that I have rooted.... however... my settings on the thing are extremely basic..
How do I enable usb debugging if I dont have the option in the settings?
Thanks
Chris
---------- Post added at 03:19 PM ---------- Previous post was at 03:14 PM ----------
I just got my nexus yesterday, and this isnt the first phone that I have rooted.... however... my settings on the thing are extremely basic..
How do I enable usb debugging if I dont have the option in the settings?
Thanks
Chris
Edit: Got an app to enable it... still not in the menu though.
wizshaw said:
I just got my nexus yesterday, and this isnt the first phone that I have rooted.... however... my settings on the thing are extremely basic..
How do I enable usb debugging if I dont have the option in the settings?
Thanks
Chris
---------- Post added at 03:19 PM ---------- Previous post was at 03:14 PM ----------
I just got my nexus yesterday, and this isnt the first phone that I have rooted.... however... my settings on the thing are extremely basic..
How do I enable usb debugging if I dont have the option in the settings?
Thanks
Chris
Edit: Got an app to enable it... still not in the menu though.
Click to expand...
Click to collapse
Oh geeze!
I forgot.
Settings>about>version number I think...
Click 7 times to enable developer options.
Will update op soon.
Quick question: is there a reason the first post links to SuperSU version 0.98, when version 0.99 is the most recent? If version 0.99 has known issues with the Nexus 4, I don't want to use it on my device.
The 0.99 version came out after this guide was posted. I was offered to upgrade to the new version of supersu from 0.98 and so far no problem at all.
Does this work on the latest version of JB (4.2.1)?
When installing a new ROM it says to perform a factory reset through CWM, which will remove all apps and data but should keep all your pictures, videos, songs etc.
It doesn't mention to wipe the System partition as well. Is this not necessary when flashing ROMs on a Nexus?
Prior to owning the N4 I had the Galaxy S 2 and it was always stated in the OP instructions to wipe data/factory reset, wipe system, clear cache, clear dalvik and then flash ROM and Gapps.
However, I don't notice in any guides or instructions for N4 ROMS to wipe the system partition, just the data partition. Is there a reason for this or is it not necessary to wipe the system partition? Thanks. Great guide by the way.
Peace
thank u for ur effort
Chochiwpg said:
When installing a new ROM it says to perform a factory reset through CWM, which will remove all apps and data but should keep all your pictures, videos, songs etc.
It doesn't mention to wipe the System partition as well. Is this not necessary when flashing ROMs on a Nexus?
Prior to owning the N4 I had the Galaxy S 2 and it was always stated in the OP instructions to wipe data/factory reset, wipe system, clear cache, clear dalvik and then flash ROM and Gapps.
However, I don't notice in any guides or instructions for N4 ROMS to wipe the system partition, just the data partition. Is there a reason for this or is it not necessary to wipe the system partition? Thanks. Great guide by the way.
Peace
Click to expand...
Click to collapse
I actually have a question along these lines.
I just came from a LG G2X so things were different for me whenever I flashed ROM's/kernels. For one thing, I had an external sd card so whenever CWM made it's backups, they went to that automatically and I didn't have to worry about wiping since everything was on the external. This phone doesn't have an external so where do the backups go? From the looks of the new CWM 6.0.2.0, the backups (and blobs now apparently) go to /data/media/clockworkmod. Well I guess my question here is if you have to wipe /data for installing new ROM's, how would I restore a backup because they would have been deleted off the /data partition. I tried adb pulling /data/media/clockworkmod to my computer but it won't go. Don't know if it's because that partition is mounted while the phone is in use or what. I tried the mount/umount command that OP listed but it won't work for me. Don't want to flash ANYTHING on this phone until I know for a fact I can get to the backups that I'm creating.