Database Users

Location of apps after app2sd?

With root explorer, i see that my apps are saved to something like '/system/sd/app,' but when I mount my G1, I can't find that folder. I can't even find the "system" folder. Anyone have any ideas?
Also, I pressed the "R/W" button on that folder in Root Explorer, but now I can't switch it back to R/O. It gives me an error saying, "Remount Failed: Device or resource busy."

what is it you want to do with the apps?

My gmail app is force closing, and I haven't found a way to reinstall it through market. I was going to try to replace the .apk.

I don't believe the gmail app is on the SD, it should be under /system/app/Gmail.apk
For the most part, the system apps install on the phone, the rest are on SD.

That still leads me to my first question, lol. I can't find the "system" folder after mounting my G1.

??
I don't know. I use the rooted file browser SUFBS and have never had a problem seeing the system folder.
Might have been associated with other changes you made to the system.
For me, if all else fails, I re-partition, wipe & re-flash.
Hopefully someone else can offer some better info.

I find it fine on my G1 via Root Explorer. It's just that I can't seem to locate it on my computer (i.e something like h:\system\app), after plugging my G1 in.
Sorry for any confusion.

You must be on a windows machine. You can not nativly see an ext partition under windows.
Look at the guides that tell you how to set up adb and adb push the application to the folder you want.

adobrakic said:
I find it fine on my G1 via Root Explorer. It's just that I can't seem to locate it on my computer (i.e something like h:\system\app), after plugging my G1 in.
Sorry for any confusion.
Click to expand...
Click to collapse
You can do these things right from recovery console, and probably terminal, I like recovery better though. place the file you want to use on the root of the SDcard. Since it is the Gmail.apk you want to replace you would go about it like this:
mount system
mount sdcard
cp /sdcard/Gmail.apk /system/app/Gmail.apk
reboot
thats pretty much it.

Cant flash another recovery image!!!

It used to work along time ago, this is my new refurb that i rooted a few days ago, im on the 1.5.2 recovery image and im trying to flash the new 1.6 but i dont what the crap im doing wrong. i keep getting error messages i used to be able to do this in 10 seconds. i already have the image on the root of my card can anyone help.
Plus those bastards sent me a refurb that has dead pixels that are white in the blk screen wtf sprint, thats pure whack customer service.
EDIT: problem solved, i was trying this whole time to flash another recovery inside recovery, i actually left the phone on and pushed the recovery lol no more ghanja.

see the # symbol when you enter teh shell? that means you have root already and su isn't necessary. Also try unplugging then plugging back in, the phone from the usb. The file not found error probably means that the sd card is mounted. do an ls from /sdcard to make sure

Also try "adb mount" over "mount -a".

DISABLE usb debugging.
i know, its the little things we overlook. i just did this last night and forgot to disable it.

i did and its still not working.........i dont understand, let me upload another pic. and i already tried adb mount and fastboot still no luck

i kept getting these errors what i did and found easiest with no errors is save the recovery in the sd card. download terminal emulator then in terminal emulator su then enter
then type flash_image recovery /sdcard/nameofimage.img
someone please make sure my prompts are right as i hadn't done it in awhile.

I am trying to do the exact same thing and getting the exact same errors. The file is definitely on the sd card, I am typing the name correct, and USB debugging is off.
Anyone have any other ideas or ways to update to the newest recovery image?

Maitiu said:
I am trying to do the exact same thing and getting the exact same errors. The file is definitely on the sd card, I am typing the name correct, and USB debugging is off.
Anyone have any other ideas or ways to update to the newest recovery image?
Click to expand...
Click to collapse
hahaha dude it used to work perfectly, i been trying and trying for the past couple of hours. (scratching head)

Demoyo23 said:
hahaha dude it used to work perfectly, i been trying and trying for the past couple of hours. (scratching head)
Click to expand...
Click to collapse
you try using the terminal emulator method directly on the phone? only way i can get to work and works everytime.

I'm working on that now, but I tried that a few days ago and got different errors, I'll post what the specific error was when I get there in a few minutes. For some reason Superuser Permissions is force closing right now.
Yeah even from the terminal emulator, I get a "not found" error.

I just updated today from RA1.5.2 to RA1.6.2. I used the Recovery Flasher to update to the newer version as that is what I had originally used to get 1.5.2 installed.
These were original instructions from theunlockr .com:
7. Save both the Recovery-RA-HEROC-v1.5.2.img and the FlashRec.apk to your computer, then copy them both to your SD card (do NOT put them inside any folders on the SD card, just put them on the SD card itself).
8. Unplug the phone from the computer once they are downloaded to the SD card.
8. Goto the Market and download Linda File Manager or any file manager program if you do not already have one.
9. Open the file manager and goto SDCard and then find the FlashRec apk file and click it. If asked tell it to use Package Installer to open it. It should automatically install the apk.
10. Open the FlashRec program and click on Backup Recovery Image and wait for it to finish.
11. Once done, click on the empty text box in the FlashRec program and type (again remember we have replaced the recovery image from the one in the video so type what is written here, NOT what is written in the video!):
/sdcard/recovery-RA-heroc-v1.5.2.img
Then click on the Flash Custom RecoveryImage button and wait for it to finish.

Just barely.

That's still not working flashrec won't back up it keeps saying failed. And it won't flash a custom img. This refurb is cursed I had no problem doing it all on my original.
-------------------------------------
Sent via the XDA Tapatalk App

Demoyo23 said:
It used to work along time ago, this is my new refurb that i rooted a few days ago, im on the 1.5.2 recovery image and im trying to flash the new 1.6 but i dont what the crap im doing wrong. i keep getting error messages i used to be able to do this in 10 seconds. i already have the image on the root of my card can anyone help.
Plus those bastards sent me a refurb that has dead pixels that are white in the blk screen wtf sprint, thats pure whack customer service..
Click to expand...
Click to collapse
Type 'adb devices' in... Whenever I see the '/' before the '#' it means that it isn't recognizing my phone.

Just do it through adb. I did mine through adb the 1st, 2nd and 3rd time. After looking at the dirwctiona, I think it might be easier and should work.
-------------------------------------
Sent via the XDA Tapatalk App

Make sure the phone is connected as charge only, once it is type
ls /sdcard
AND PASTE THE RESULTS HERE
It sounds like you don't have the sdcard mounted or if you do you may be typing the file wrong compared to what is on the sdcard.
Don't panic, this had nothing to do worth the phone being refurbished, it is only a simple file not found error that once you fun that command can easily be solved.

liquidtenmillion said:
Make sure the phone is connected as charge only, once it is type
ls /sdcard
AND PASTE THE RESULTS HERE
It sounds like you don't have the sdcard mounted or if you do you may be typing the file wrong compared to what is on the sdcard.
Don't panic, this had nothing to do worth the phone being refurbished, it is only a simple file not found error that once you fun that command can easily be solved.
Click to expand...
Click to collapse
it keeps telling me permission denied lol

Type in
"adb shell" then
"ls /sdcard"
Without the quotes exactly as I typed them one at a time and paste the results.

dirkydirk23 said:
i did and its still not working.........i dont understand, let me upload another pic. and i already tried adb mount and fastboot still no luck
Click to expand...
Click to collapse
did you try fastboot boot recovery [dir on your computer]

Do a search for adb shell recovery. It should tell you how to do it. You are going to have to mount the system before doing anything else...and also change the recovery image to something Like recovery.ing as it is easier to type and less likely to be mis-typed
-------------------------------------
Sent via the XDA Tapatalk App

Rooting through a noob's eyes

I'm not sure how this will be taken by the people here. Everyone seems really helpful when other people ask questions or need help so I may be surprised, but after rooting my Incredible last night and then trying to look into boot animations, removing bloatware and other things I was left with some feelings that took the joy out of being rooted and I wanted to share them.
Laugh if you will, insult if you feel it's necessary. I'm old enough to be able to handle it but beyond all of that I just wanted to say that the "rooting community" are a brilliant bunch of people. The things that you guys do boggles my mind. Since I only just registered I'm forbidden to post links, but if you're so inclined to go read it here it is.
ishootpixels.tumblr.com/
EDIT: I'd also like to add that my wife's netbook is running XP and not Vista. I forgot that we downgraded it (or upgraded however you want to look at it). I've gone back and changed my blog post.

If you would like some help getting where you want to be, PM me and I would be glad to help. I am far from an expert, but after scouring these forums endlessly, I am quite familiar with the process.

@mtag1029 Thanks. I guess my first problem is that whenever I type in "adb" anything, I get that "adb is not recognized as an internal or external command, operable program or batch file."
I've used this method to connect the phone to the netbook...
1. Boot into Clockworkmod recovery by powering off the phone and pressing and holding the volume down and power button until the screen lights up.
2. At the menu press volume down to select Recovery, then press power.
3. At the Clockworkmod main menu select partitions menu, then select mount /system
4. On the computer click Start > Run, and type CMD to open a command prompt.
5. In the command prompt type cd\sdk\tools
6. At the command prompt type adb shell. Now you’re in the phone’s OS.
and I get as far as step 6 before I can't go any further which is where I get that message. Right now I'm trying to install a boot animation and sound but I'll also need to be able to get beyond this in order to remove the bloatware. What am I doing wrong?
And THANK YOU again for the help. I'm almost to the point of returning it to stock so I'll at least be able to get Froyo whenever it's released OTA, but I've come so far at this point I'd hate to throw it all away and go back to stock.

IShootPixels said:
5. In the command prompt type cd\sdk\tools
6. At the command prompt type adb shell. Now you’re in the phone’s OS.
Click to expand...
Click to collapse
Assuming your sdk folder is in the root of the C drive (i.e. C:\sdk\), the command in step 5 is wrong -- it's supposed to be:
Code:
cd \sdk\tools
with a space. That should get you into the C:\sdk\tools directory, where adb is.
Not sure if the lack of spacing was just a typo, but if not, there ya go Let me know how it works
edit: Just tried cd\sdk\tools, actually works, I thought there had to be a space, but maybe not. I guess the next step would be to make sure there's an adb.exe in your tools folder?

I created a file folder under Local Disk C called "sdk" and inside that I created another folder "tools". I couldn't find folders that were already named this so I created them myself. That may be wrong so it wouldn't surprise me if that's my first mistake.
Beyond that, when I get into running command lines I have gotten to where it looks like this...
C:\sdk\tools>
No spaces. I'm taking a pic and trying to attach it if my noob status on the forums will allow me.

I don't have the exe file. I didn't need it to root the phone. I don't know where to even get it.

IShootPixels said:
I created a file folder under Local Disk C called "sdk" and inside that I created another folder "tools". I couldn't find folders that were already named this so I created them myself. That may be wrong so it wouldn't surprise me if that's my first mistake.
Click to expand...
Click to collapse
If you just made the folders, there's nothing in them -- if you go to the tools directory and type "dir", there probably won't be any files unless you extracted some in there.
From the how 2 adb thread by dreamersipaq:
1) Setting up ADB
ADB stands for Android Development Bridge. It is used by Android developers for programming. For us, it is used to hack into our phones . For our purposes, just know that it is like the cmd (command prompt) that allows us to send commands to our phone. This is extremely useful when we're in the custom recovery
Download the Android SDK from Google: http://developer.android.com/sdk/index.html
Unzip to your desktop
Take the "android-sdk-_**-windows" folder and move it to the root of your hard drive (C:\)
** will change, it is revision of SDK, like "r6"
****The below is not necessary, but is useful sometimes if you just want to run "adb shell" from anywhere without going into the sdk directory****
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-_**-windows\tools
****End of the "This is not necessary thing****
Click to expand...
Click to collapse
edit: the rest of that thread is located http://forum.xda-developers.com/showthread.php?t=709220 there, if you're interested

gmonox is absolutely correct. You cannot just create the folders. They have to come from the sdk.
Another thing. You mentioned in your blog post that you would like to have froyo. Froyo should be flashed before removing any apps becauseeverything that you have removed will be put back in with froyo.

Wow, that was a pretty necessary step that I never knew about. Okay, so I DL'd, unzipped, and copied the folder to the root of C. Question, do I have to rename the "android-sdk-windows" folder to simply "sdk" when following the directions I listed earlier or do I leave it and at the command line type...
cd\android-sdk-windows\tools
I also didn't do the "advanced" part of the post simply because it's my wife's PC and I'm really not in the mood to screw up anything else today.
EDIT: And about Froyo, right now I just want to see if I can get a little boot animation working before I even THINK about tackling ROMs, Kernals or anything else. Although I know that most ROMs have the kernals that are optimized for that particular ROM if I've read things right. I realize Froyo is not a mod so it won't have an overclocked kernal but I read that others might. I've read that Froyo packs in VZ Nav (like I didn't have enough of that crap with my old Blackberry) amongst other things. If nothing else, I'm really good at reading about all of the things that I wish I could do.

IShootPixels said:
Wow, that was a pretty necessary step that I never knew about. Okay, so I DL'd, unzipped, and copied the folder to the root of C. Question, do I have to rename the "android-sdk-windows" folder to simply "sdk" when following the directions I listed earlier or do I leave it and at the command line type...
cd\android-sdk-windows\tools
I also didn't do the "advanced" part of the post simply because it's my wife's PC and I'm really not in the mood to screw up anything else today.
EDIT: And about Froyo, right now I just want to see if I can get a little boot animation working before I even THINK about tackling ROMs, Kernals or anything else. Although I know that most ROMs have the kernals that are optimized for that particular ROM if I've read things right. I realize Froyo is not a mod so it won't have an overclocked kernal but I read that others might. I've read that Froyo packs in VZ Nav (like I didn't have enough of that crap with my old Blackberry) amongst other things. If nothing else, I'm really good at reading about all of the things that I wish I could do.
Click to expand...
Click to collapse
Either way works. I renamed mine sdk because I'm too lazy to type android-sdk-windows every time I want to go into adb shell. But it's up to you

Ok, I'm guessing that my question will be answered after I run the setup. I didn't see the link at first to the thread. Apparently my wife's netbook doesn't even have the right java ver. to run the setup.
This is making my brain hurt.

I should have asked this earlier, have you made a nandroid backup?

LOL. Actually as soon as I finished rooting the phone I DL'd Titanium from Marketplace and installed it and BusyBox and made a backup that way. Then I remembered Nandroid and went in and backed up that way too. Probably overkill but the whole process has scared the crap outta me. I wouldn't know how to apply these backups, but at least I have them.
At the moment I'm installing the Documentation for Android SDK, API 8, revision 1
EDIT: This is going to take awhile I'm guessing. Installing SDK Platform Android 2.2, API 8, revision 2

Okay. The nandroid is the most important. It will save your butt if something goes wrong.

IShootPixels said:
LOL. Actually as soon as I finished rooting the phone I DL'd Titanium from Marketplace and installed it and BusyBox and made a backup that way. Then I remembered Nandroid and went in and backed up that way too. Probably overkill but the whole process has scared the crap outta me. I wouldn't know how to apply these backups, but at least I have them.
At the moment I'm installing the Documentation for Android SDK, API 8, revision 1
Click to expand...
Click to collapse
Both types of backups are easy to restore, for nandroid you just go into recovery, same place as you backed it up but click Restore and just wait for it. For titanium, go into backup/restore, batch, and there's an option to restore apps, apps+data, and apps+system data I think. If you have the paid version, the apps will all install on their own, but if not I don't think they will.
Are you still on a netbook or can you use a pc? Might be easier if your java's out of date and whatnot to just use a pc, I'm no expert on netbooks but I'd imagine they're stripped down a lot

gmonox said:
Both types of backups are easy to restore
Click to expand...
Click to collapse
Just keep in mind that you need a functioning phone in order to use Titanium. If you mess something up while in adb and the phone will not boot, Titanium is useless. A nandroid however will restore you back exactly how you were before messing around in adb even if the os will not boot.

Well then I'm glad I did the Nandroid BU! Bsically then I guess that because I backed up with Ti first and then with Nandroid, the Nandroid created a back up of my Ti backup. If so I think I just set a record for redundancy.
As for using a netbook, I don't have a choice. I run everything off of my Macbook, or did until now. The only Windows based item in the house aside from my Xboxes is my wife's netbook. I've updated the Java and begun the setup process. I had to do as the thread said and force the http and then go into the available packages and I'm DLing and installing them all because I was afriad that if I didn't I'd find that I needed one I hadn't installed. I'm guessing that since I'm already rooted (and I'm hoping) that once I'm done installing all of these packages that that should be it except for step #4 and #5.
1. Run SDK Setup.exe
2. If it gives you any error go to settings and click on "Force http//....."
3. Select usb driver package, let it download and install
4. Some say the below step is not needed, but I did this so I'm posting it
Go to tools folder, and edit "android_winusb.inf" (you can do this by opening it via wordpad). Add the following at the end of the [Google.NTx86] and [Google.NTamd64] blocks:
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
Save the file and exit.
5). Plug your phone into PC, when windows asks to install drivers for new found hardware, point the New Hardware Found wizaed to android_winusb.inf that you just edited.

I'd also like to add that this is the YouTube video that started this mess. I followed his tutorial on rooting the phone and although the sound was low it was pretty spot on minus one or two things he failed to mention.
However, after watching this video I thought it would be just as easy to install the boot animation as it was to root the phone. Seems the bigger task would be rooting rather than a boot animation. In the hours that you guys have helped me I've learn that this boot video lacks a TRUCK LOAD of information and assumes that the person watching it isn't a noob. Dont' most people that watch tutorial videos watch them because they have no idea what they're doing? I realize now that there's a ton o' stuff missing from it. I still want the animation and sound though.
http://www.youtube.com/watch?v=-Ju9lpH7_4g&feature=channel

Titanium stores backups on your SD card. Nandroid does not backup your SD card, but you are in good shape. Keep us posted.

I'm not sure if step 4 is required, I'm on win7 64bit and I don't recall doing it, but I guess it couldn't hurt. Also, I don't think nandroid backs up your titanium backup -- Ti backup is stored on your SD card

Can't write on internal SD card after root

After having rooted (with nexus 10 toolkit v1.3.0) my nexus 10 and flashed AOPK Nexus 10 (WIP) Task650 & Ktoonsez (1-4) rom, I'm unable to upload to, change or move any files or folders on my internal SD card. I installed Root Explorer and changed from Mount R/O to Mounted as r/w. Access is granted by Super SU. I also tried to change permission settings, unfortunatedly without any success. There appeared the following message:
"Warning
Permissions change was not successful. Please note that some file systems (e.g. SD card) do not allow permission changes."
Is there a possibility to change these permissions in order to be able to create and move files and folders on my SD card?
Thanks for taking your time to help me with my issue!
Anzirothu

1. Clear cache
2. Clear dalvik
3. Fix Permissions
forgot something ?

Thank you for your reply, Patrik!
1. done.
2. done.
3. Fix Permissions - How? With cwm? I did fix permissions with cwm recovery, but the problem persists...

Just so we are clear, when you say "upload to, change, or move" are you meaning you cannot copy a file from your computer to your Nexus 10? Or just that you cant arrange stuff through root explorer from within the tablet itself?

Neither copying from PC to Nexus nor arranging stuff through root exlorer from within the tablet itself. I can't even download an email attachment and put it to the SD card. The card seems to be locked.

I had that problem once but I dont remember what caused it or what exactly I did to fix. I think I just did a complete wipe by locking and unlocking the bootloader and then installing a new ROM again.

I think I did this too (unroot, lock bootloader, then root and unlock bootloader) and then installed the same rom again. I will try it this time with another rom.
Isn't there really no other solution to get access to my SD card again??
Thx for your help!

Are you using a toolkit to unlock and root? If so them maybe it is not doing something right and it messing up a permissions somewhere. It could also be a driver problem on your PC with being unable to copy a file to the tablet.

Thank you for your help!
I am using the nexus 10 toolkit V1.3.0. Right now I'm trying to intall twrp recovery with a fully wiped sd card. No easy task fot me being a noob...

In ClockWorkMod, make sure that /data is mounted
Then download the Android SDK: http://developer.android.com/sdk/index.html
I usually put all the files just in C:/android-sdk-windows
Once you have it all there open up the SDK Manager and download all the additional files needed. You probably only need to download "Android SDK Tools" and "Android SDK Platform-tools", but I always download the other files for whatever version of Android I am running, in our case Android 4.2. That way I have them if I need to do something else.
Once downloaded, open the Android-sdk-windows/platform-tools directory. copy:
adb.exe
adbWinApi.dll
adbWinUsbApi.dll
fastboot.exe
to your base C:/Android-SDK-Windows directory.
Now open command prompt from Start -> run
type: cd C:/Android-SDK-Windows
type: "adb devices" and it should list your tablet. It will actually say something with your devices serial number and then "Recovery" after it, showing your tablet is in recovery. If you dont see this then you either dont have your tablet mounted right from in the Recovery, ClockWorkMod is stupid, or you dont have working adb drivers.
Now copy the ROM you want to flash to C:/Android-SDK-Windows
Then type: "adb push blahblahblah.zip /data/media/0"
That should push the ROM to the root of your SD card. Give it time, it takes a while to push a ROM file. Once it is done, flash the ROM.
That *should* put it in the right spot where it looks like it is on your "internal storage" (what you see when navigating files within the ROM). If you dont see the ROM in clockworkMod then keep navigating back to the root of your internal storage and then open up "data", then "media", then "0" and you should see it. If you still cant find the ROM, push it again but just use "/data/media" as the location.
I just did all these steps myself to verify I remembered it all correct and I was able to successfully copy a ROM and find it on my tablet to flash by doing everything I just listed above. SO you should be good to go if you follow all those steps properly. I know it looks like a lot of work, but it really isnt and will go quite fast. Most of it is just the setup for getting ADB and Fastboot ready to use.
For a ROM to install, I would recommend to someone new like you either of these:
http://forum.xda-developers.com/showthread.php?t=2071082
^^^^^ That one is pretty close to the stock ROM with a few fixes and a couple extra features
or: http://forum.xda-developers.com/showthread.php?t=2071082
^^^^^ This one is pretty much CyanogenMod 10.1, but built by a different guy and not pulling every new thing from CM, just the "cherry picks" of features. It tends to be a bit more stable and less buggy than the real CM10.1 nightly's
And for a kernel you can flash and forget you will want to try this one:
http://forum.xda-developers.com/showthread.php?t=2098157
^^^^^ To flash that you will want to do a similar thing as how you pushed the ROM to your device. Only this time you will copy the kernels' "boot-r4.img" file into your android-adk-windows directory and use the command: "fastboot flash boot boot-r4.img"
While I enjoy the KTManta kernel more, it does require a bit of tweaking to get running perfect. Which is one of the things I like about it because of all the options to tweak. But for someone just learning this stuff that would be a bad thing, so Franco's kernel is much better than stock and doesnt require you to adjust anything once it is flashed to your tablet.

<<Q>>cracked screen. ADB and/or OTG what are my options?

first... its been a while since i have messed with a nexus. so im not on the nexus boards that much. my buddy and i both bought nexus phones during the first day of second round of sales back in 2012. back then there was no otg support. and rooting was done via adb etc. i sold mine shortly thereafter and have not been on the nexus boards since. so please catch me up to speed with my questions and maybe help me to get his files switched from his old nexus with a cracked screen to the new one he just got yesterday.
is there now otg support for this phone?
i found a post to adb past the lockscreen. can i also use adb to pull the backup file (i booted into recovery and did a backup yesterday) on the old and use it on the new? new phone is not rooted yet, but can be.
is there a way to pull specifics from the backup. or pull specific apps with adb? as in he has company passwords and such in a note app that he really needs with a passion.
is there an easier way to get to the files than what i am thinking i have to do? i still need to relearn how to use adb and such, but if i can otg through this and use airdroid that would be wonderful. if adb is the only way to get this done.... would you mind giving me the commands i need to get to and pull the files i need. i can get the paths from his new phone to figure out where they are. i just dont know the commands to do the deed.
thanks a ton for anyone willing to help. <-- seriously.
-patrick

You can get USB Host working BUT it has to be externally powered.
Sent from my Nexus 4 using Tapatalk 4

I hope I'm understanding your exact situation; feel free to let me know where I misunderstood you.
Ok, your friend bought a Nexus 4 a while back, has somehow broken the screen, bought a new Nexus 4, and wants to grab a nandroid backup and a document from a notepad-esque application from it?
If so, this is what I'd do. I'd grab the Nandroid backup from the old device, and restore it onto the new device (again, assuming both old and new devices are the same model i.e. Nexus 4)(also after backing up the new device, in case you ever need or want to revert to a fresh image) and grab the text file. What recovery are you using on the broken phone? I don't know the path for backups for TWRP, but if you're using CWM, the path is /mnt/shell/emulated/clockworkmod/backup/. Ok, let me make this easier by making a step-by-step. Some of it you probably already know how to do but I want to be as clear as possible.
1. Make a nandroid backup on new device in case something goes wrong, or you want to go back in the future
2. Hook up broken device to computer, open a cmd window in the platform-tools folder, containing adb.exe (shift right-click in an Explorer window and hit "Open command window here" is the fastest way)
3. Use this command: adb pull /mnt/shell/emulated/clockworkmod/backup/NameOfBackup/ NameOfBackup
4. That will pull the backup and put it in a folder called NameOfBackup (whatever you called it) in the platform-tools folder containing adb.exe
5. Flash CWM recovery onto new device
6. Hook up new phone to computer and run this command: adb push NameOfBackup /mnt/shell/emulated/clockworkmod/backup/NameOfBackup/
7. Boot into recovery and flash that backup
8. Reboot. It should look exactly like your old phone. Grab the file you want with all the passwords in it and back it up on your computer something. Now you can restore the other backup you made of this device or keep with your backup of the broken phone. Your call.
EDIT:
I just reread my post to make sure I included everything. You might have to move step 5 way up before step 1. You'll need a custom recovery to make a nandroid, so flash a custom recovery first.

Johmama said:
I hope I'm understanding your exact situation; feel free to let me know where I misunderstood you.
Ok, your friend bought a Nexus 4 a while back, has somehow broken the screen, bought a new Nexus 4, and wants to grab a nandroid backup and a document from a notepad-esque application from it?
If so, this is what I'd do. I'd grab the Nandroid backup from the old device, and restore it onto the new device (again, assuming both old and new devices are the same model i.e. Nexus 4)(also after backing up the new device, in case you ever need or want to revert to a fresh image) and grab the text file. What recovery are you using on the broken phone? I don't know the path for backups for TWRP, but if you're using CWM, the path is /mnt/shell/emulated/clockworkmod/backup/. Ok, let me make this easier by making a step-by-step. Some of it you probably already know how to do but I want to be as clear as possible.
1. Make a nandroid backup on new device in case something goes wrong, or you want to go back in the future
2. Hook up broken device to computer, open a cmd window in the platform-tools folder, containing adb.exe (shift right-click in an Explorer window and hit "Open command window here" is the fastest way)
3. Use this command: adb pull /mnt/shell/emulated/clockworkmod/backup/NameOfBackup/ NameOfBackup
4. That will pull the backup and put it in a folder called NameOfBackup (whatever you called it) in the platform-tools folder containing adb.exe
5. Flash CWM recovery onto new device
6. Hook up new phone to computer and run this command: adb push NameOfBackup /mnt/shell/emulated/clockworkmod/backup/NameOfBackup/
7. Boot into recovery and flash that backup
8. Reboot. It should look exactly like your old phone. Grab the file you want with all the passwords in it and back it up on your computer something. Now you can restore the other backup you made of this device or keep with your backup of the broken phone. Your call.
EDIT:
I just reread my post to make sure I included everything. You might have to move step 5 way up before step 1. You'll need a custom recovery to make a nandroid, so flash a custom recovery first.
Click to expand...
Click to collapse
you are awesome. thanks a ton. thats what i needed. just wasnt sure if the imei needed to match or whatnot. cwm is what i am using on the old phone. and ill make sure thats what goes on the new one once i root it. will come back and let you know how it goes. i still need to meet up with him and get his new phone to make things work.
once again. thank you.

ok so he thought he had debugging turned on. but he apparently does not. i keep getting device not recognized by adb. he has an icon of a jellybean with horns or antennas coming out of it. i thought that was the notif icon for debuggin. but after an image search i see that debugging is different.
anywho... it doesnt look like i can rig up an otg cable either because i need to be able to install a zip script before it will work. it looks like i am out of options. i guess i need to tell him to buy another screen. let me fix. and then he can sell it on craigslist and try to get his money back.
if there is anything i am missing... let me know. but for now i seem to have hit the end of the road.

Boot to recovery and use adb.
Either straight up pull the backup (might be more sane to make a tarball and pull that) or push the otg mod and use cwm to flash that.
If you have cwm touch, you can use adb or fastboot to flash the regular cwm.

ziddey said:
Boot to recovery and use adb.
Either straight up pull the backup (might be more sane to make a tarball and pull that) or push the otg mod and use cwm to flash that.
If you have cwm touch, you can use adb or fastboot to flash the regular cwm.
Click to expand...
Click to collapse
cool beans. did not know i could adb in recovery. ill give it a try after work, bout to head to bed. ill search tarball to find out what you are talking about also. i will need to push your .zip to it anyways for the pics and such. i guess i will go ahead and jump on amazon to get the cables and hub.
edit: i used ill and i wll several times. but too tired to go back and re-word. pardon the near impossible to follow post.

How much free space is on the phone? Tarballs are archives similar to zips (although without compression in base form). If you have the space for it, just make a big tarball and adb pull it. Only real reason to go OTG is if you want to be able to use the phone still-- hook up a usb hub, keyboard, mouse, usb stick.