Database Users

ugh... disaster! (lol for me...)

So, I took my microSD card out of my phone, put it into my digital camera, and my digital camera formatted the card. So, I lost all my pics I had taken with my phone. One of the pics, I have saved as the screen lock on my phone. Id love to get this pic off my phone, and onto my computer. can anyone suggest the best way to do this? Any responses are greatly appreciated! Thanks!

plug your phone into your computer via the usb cable and mount the sdcard via your phone

You could try this free deleted recovery software called Recuva. It works with removable media. I've attached it to this message for you.

where on the phone is the pic that is my current lock screensaver at? that pic is the pic I want, and I was unable to get it off the SD card (although other things I could get off there, thanks so much for that!). just curious, I would love to salvage this one pic.

/data/misc/lockscreen/

flipzmode said:
/data/misc/lockscreen/
Click to expand...
Click to collapse
alright, so... just to prove my noob status with android... how would I go about getting that off my phone from there?

jtmercutio said:
alright, so... just to prove my noob status with android... how would I go about getting that off my phone from there?
Click to expand...
Click to collapse
*makes mental note to add "pull any file" to my kitchen. heh*
Do you have the sdk / adb installed on your comp? Or are you a totally nubile noob? heh
If you do, from a command prompt it would be:
Code:
adb pull /data/misc/lockscreen c:\temp\
and make sure that c:\temp\ exists before you do it. If you don't have adb installed then download my kitchen (link is in my signature). Open a command prompt (on your computer) and then do this instead:
Code:
cd c:\folder-where-you-extracted-kitchen\adb\
adb-windows pull /data/misc/lockscreen c:\temp\
If you have any problems or errors then copy/paste them to me.

whew, got it. thank you guys sooo sooo much!

Hero flashing option screen not coming plz help

hi i have just installed the ROM manager software from the market and after deleting this my hero flashing option screen not coming its shows like that i have attached the pictures please help me i have hard reset the phone its start working but the flashing options still gone & i m unable to install any other ROM ,suggestions from the Experts are needed thanks

sunshine4u said:
hi i have just installed the ROM manager software from the market and after deleting this my hero flashing option screen not coming its shows like that i have attached the pictures please help me i have hard reset the phone its start working but the flashing options still gone & i m unable to install any other ROM ,suggestions from the Experts are needed thanks
Click to expand...
Click to collapse
Just try pushing recovery via adb .. if you know how to use it

Do you mean fastboot isnt working? (3 skating andoids) it wont boot? or recovery doesnt work?
in the clockwork rom manager it has an option for broken recovery...
other than that put the recovery.img on the sdcard (the root of it) then connect the phone and type adb shell flash_image /sdcard/recovery.img

i have tried it with ADB its gives message
usage : Flash_image partition file.img
but it doesn't boot in recovery mod what to do now ?

sunshine4u said:
i have tried it with ADB its gives message
usage : Flash_image partition file.img
but it doesn't boot in recovery mod what to do now ?
Click to expand...
Click to collapse
I know this mite seem a dumb question but you are holding " home " & " Power " right ?
Have to tested using flashrac and amon ra ?

Steven_belfast said:
I know this mite seem a dumb question but you are holding " home " & " Power " right ?
Have to tested using flashrac and amon ra ?
Click to expand...
Click to collapse
whats these thing i dnt knw about them please provide the link for that

Greetings sunshine4u,
There use to be a how to on the unlockr but its no longer there,
How ever here you go man,
Flashrac
http://zenthought.org/content/project/flashrec
Amon_ra
http://forum.xda-developers.com/showthread.php?t=561124
Code:
1. On your phone, goto Settings, Applications, and make sure Unknown source is checked ON.
2. On your phone, goto Settings, SD card and phone storage, and click Unmount SD card.
3. Then click Format SD card (it should automatically remount after this).
4. Plug the phone into the compuer via USB, then pull down the notification bar and click on the SD card notification. Then click mount.
5. Download this APK and recovery image and save it to your computer:
6. Save both the recovery-RA-heroc-v1.5.2 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).
7. 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-hero-v1.7.0.1.img
Then click on the Flash Custom Recovery Image button (this button might say something else in different versions of Flashrec, but similar to this) and wait for it to finish.
12. Turn off the phone and turn it on into Recovery mode by holding down Home and Power to turn it on (keep holding until the recovery screen comes up has a bunch of text on a black background). So long as that screen comes up, you have done it correctly
Now this mite not work with your rom but it will not damage it in any way,
If point 10 fails then you will not be able to do it this way.
I know my self i had to downgrade my orange rom before doing it,
But before that point 10 just kept saying failed,
Downgrade and it worked a treat.
Hope that helps.

how to downgrade ???

Greetings,
I guess it did not work then,
As for the downgrade this depends on your provider,
I was able to get the orange rru thats a .exe and just run this,
But if you give have a look on the internet for your provider i am sure you will be able to find some thing,
If not get back to me with the name of your provider and the software you are on at this point and i will have a look for you.

my hero has no logo on it and its unlocked to all networks and i m using it in pakistan i m using warid as service provider and they dnt know anything about this issuee

i have Flashed the RA-hero-v1.7.01. now can any body tell me which backup is required to take nand or nand+ext what both of these doo and which 1 i should take before changing roms??

sunshine4u said:
i have Flashed the RA-hero-v1.7.01. now can any body tell me which backup is required to take nand or nand+ext what both of these doo and which 1 i should take before changing roms??
Click to expand...
Click to collapse
Just nand,
Any time i do a nand+ext it all ways fails when i restore.
Hey as least you are getting there now.

Steven_belfast said:
Just nand,
Any time i do a nand+ext it all ways fails when i restore.
Hey as least you are getting there now.
Click to expand...
Click to collapse
i never had problems while doing Nandroid + Ext Back up/restore ..

i have taken it with +EXT after partiton the SD card no error will come on Nandroid + Ext Back up

Steven_belfast said:
Greetings,
I guess it did not work then,
As for the downgrade this depends on your provider,
I was able to get the orange rru thats a .exe and just run this,
But if you give have a look on the internet for your provider i am sure you will be able to find some thing,
If not get back to me with the name of your provider and the software you are on at this point and i will have a look for you.
Click to expand...
Click to collapse
Hi i have the same problem as threadstarter. It did not work for me. May i know how do i downgrade my version?

[Q] Stuck on splash screen

Good evening everyone.
To start with, yes I've read all the similar topics and none of them helped me
To my problem now. My phone has been flashed with a custom ROM for 1-2 months now (I don't remember exactly) and this morning I woke up to find my phone turned off. While trying to turn it on, no matter how much time has passed, it's stuck on the splash screen refusing to load the home screen
Is there any suggestion that does not involve me losing all my data because I have no backup of them?
Waiting for any suggestions.

See if you can connect with usb, and adb can communicate with device.
If yes, you can save the /data/data folder(in which are all configurations) + /data/app folder(in which are all apps except these on sdcard if any).
You can also run adb logcat from command prompt and see if you can find what app causes the error and the bootloop, and if maybe you can uninstall/reinstall this app, or delete the folder of that app on /data/data folder, to hopefully solve the error.
Try to install a program like QtADB, droid explorer or Android manager to avoid use command line and simplify some of above operations as copy/delete folders or install/uninstall apps.
If you need more help, PM me to speak in greek(it' s better)

I've just installed QtADB and connected the phone while being inside ClockwordMod v4.0.0.5.
The truth is that from here I don't get almost any useful information (don't know why). One positive aspect is that I can copy data from/to the phone.
While stuck in the splash screen I can't connect through adb though.

You mean not at all? Usually when appears IDEOS screen you can connect via adb, after some time and when the error start maybe the device freezes and then adb probably disconects, but until then you can take some useful logcat info for the error.
You can also have some more functions with QtADB on recovery mode if you mount the partitions first.
Maybe and the app manager work then(I haven't tested though).

Managed to get logcat information while turning on the phone. I'm attaching the log file with the error lines.
Trying to read them right now to find a solution. Any help appreciated.

gkaran said:
Managed to get logcat information while turning on the phone. I'm attaching the log file with the error lines.
Trying to read them right now to find a solution. Any help appreciated.
Click to expand...
Click to collapse
By reading your log i think the problem is permissions. Try to fix permissions with recovery tool.

[Q] Backup from TWRP with USB

I've managed to softbrick my nexus 10 by trying to disable extra services (was getting about 1.5 hours battery life with media services running the processor 100% all the time). It worked wonderfully (no negative side effects, went back to 10+ hours with the screen on, or days on standby) until I reboot it and now it won't load past the moving colors (Android 4.4.3, unlocked and all that).
I have TWRP, I was hoping to backup everything possible via usb, but it seems it's incapable of doing so. ADB backup can't be done using TWRP since there's no unlock function (reaaal useful there, recovery mode that doesn't support backups) and adb pull fails if I try to pull everything since there are files and folders with invalid file names (who puts ":" in folder names? they should be shot), and I don't know specifically what to pull, I was just going to get everything put back what I found was missing that I needed. There's no room to do a backup onto the device, and since the N10 has to sd/microsd, well... Useless options are useless.
Is there anyway to just do a proper backup with TWRP over USB? Or is the "recovery" mode as useless as I think it is when it comes to backups? (I'm aware I can get the tablet back to working order if I disregard the data on it, this is a question about backing things up before doing so)
Edit: Also, I have a pro version of SkipSoft ToolKit, but unless you can actually load into the OS the toolkit can't do anything at all.
Just really frustrated with the lack of doing something as basic as copying files from one place to another. Been messing with this all morning.

Diet6 said:
I've managed to softbrick my nexus 10 by trying to disable extra services (was getting about 1.5 hours battery life with media services running the processor 100% all the time). It worked wonderfully (no negative side effects, went back to 10+ hours with the screen on, or days on standby) until I reboot it and now it won't load past the moving colors (Android 4.4.3, unlocked and all that).
I have TWRP, I was hoping to backup everything possible via usb, but it seems it's incapable of doing so. ADB backup can't be done using TWRP since there's no unlock function (reaaal useful there, recovery mode that doesn't support backups) and adb pull fails if I try to pull everything since there are files and folders with invalid file names (who puts ":" in folder names? they should be shot), and I don't know specifically what to pull, I was just going to get everything put back what I found was missing that I needed. There's no room to do a backup onto the device, and since the N10 has to sd/microsd, well... Useless options are useless.
Is there anyway to just do a proper backup with TWRP over USB? Or is the "recovery" mode as useless as I think it is when it comes to backups? (I'm aware I can get the tablet back to working order if I disregard the data on it, this is a question about backing things up before doing so)
Edit: Also, I have a pro version of SkipSoft ToolKit, but unless you can actually load into the OS the toolkit can't do anything at all.
Just really frustrated with the lack of doing something as basic as copying files from one place to another. Been messing with this all morning.
Click to expand...
Click to collapse
Do you still need help? What about mtp mounting? You can pull * for a whole folder
Why not adb sideload a new rom?

I don't think I can MTP mount a Nexus 10, at least not in recovery mode. What I ended up doing was buying a OTG usb drive and making a backup to that. Problem was it split the tar over 4 files, which corrupted them (or at least made them not work with 7zip or tartool) fortunately I was able to get them to work with cygwin enough to get the files I wanted. I didn't want to sideload a new rom until I had backed up certain application data just in case it removed it.
All in all, had to buy a OTG usb drive (I would have just bought a cable but all the stores around here had was this "Dane 16gb OTG drive". So 20 bucks later I had the files I needed. Still annoyed that you can't do a ADB backup from fastboot or recovery mode, it seems like those would be the best places because no system files are in use, but who knows maybe the developers know something I don't.
In summary:
TWRP recovery cannot confirm a ADB backup over USB. ADB backups can only be done from the operating system.
TWRP recovery mode can only backup to OTG (if your device supports it, Nexus 10 does), but if the backup is larger than 2gb it will split the file and you will need some form of linux to extract it.
ADB cannot copy every file in recovery mode over USB due to certain file names being invalid for NTFS (this is probably not a problem on other file system types), this is problematic since the "pull" command has no skip option, it just fails when it hits one of these files.

Well you can easily flash latest rwrp that does well on my Linux mount internal storage but another solution is just flashing a rom with abd sideload and the'the back up from pc the content
---------- Post added at 04:24 AM ---------- Previous post was at 04:23 AM ----------
Or that will just un brick your tablet

Diet6 said:
Still annoyed that you can't do a ADB backup from fastboot or recovery mode
Click to expand...
Click to collapse
adb doesn't work in fastboot mode, only recovery or Android itself.
Diet6 said:
In summary:
TWRP recovery cannot confirm a ADB backup over USB. ADB backups can only be done from the operating system.
Click to expand...
Click to collapse
Maybe because /data (not talking about /data/media) wasn't mounted?
Diet6 said:
TWRP recovery mode can only backup to OTG
Click to expand...
Click to collapse
Huh?
Diet6 said:
ADB cannot copy every file in recovery mode over USB due to certain file names being invalid for NTFS (this is probably not a problem on other file system types), this is problematic since the "pull" command has no skip option, it just fails when it hits one of these files.
Click to expand...
Click to collapse
That's NTFS' problem, not TWRP's.

beekay201 said:
1. adb doesn't work in fastboot mode, only recovery or Android itself.
2. Maybe because /data (not talking about /data/media) wasn't mounted?
3. Huh?
4. That's NTFS' problem, not TWRP's.
Click to expand...
Click to collapse
1. I was just covering that you can't actually do a ADB backup unless you have access to android OS, in case anyone else came across this. (I didn't know when I started, and it took awhile to find it said concretely anywhere)
2. I made sure everything was mounted, the issue is when you send a backup command over ADB it says the "Now unlock your device and confirm the backup operation" message in terminal which you can't do from recovery mode on the device, thus you cannot do a ADB backup command over TWRP (or other recovery modes I'd imagine).
3. I should have been more specific. TWRP can do a backup to the device itself (built in storage), SD card (if your device has one and you mount it), or a OTG (on the go) device via usb directly to media like a flash drive. It cannot issue a backup over USB to a computer.
4. Completely agree it's a NTFS issue, but it could be mostly avoided by allowing files that error to be skipped or renamed rather than terminating the process. (I understand that's on the android devs since pull is made by them, and I doubt they would care to improve the command for a file system I doubt they use). Again I mostly included that so if anyone else is trying to figure it out they can stop looking for "a way" and just accept it can't be done.
Ultimately Khaon is right in that sideloading a rom would have unbricked it and I could have done the ADB backup then, I just wasn't sure how that might affect the app data storage so I was looking for a way to back it up before doing that.

Diet6 said:
1. I was just covering that you can't actually do a ADB backup unless you have access to android OS, in case anyone else came across this. (I didn't know when I started, and it took awhile to find it said concretely anywhere)
2. I made sure everything was mounted, the issue is when you send a backup command over ADB it says the "Now unlock your device and confirm the backup operation" message in terminal which you can't do from recovery mode on the device, thus you cannot do a ADB backup command over TWRP (or other recovery modes I'd imagine).
3. I should have been more specific. TWRP can do a backup to the device itself (built in storage), SD card (if your device has one and you mount it), or a OTG (on the go) device via usb directly to media like a flash drive. It cannot issue a backup over USB to a computer.
4. Completely agree it's a NTFS issue, but it could be mostly avoided by allowing files that error to be skipped or renamed rather than terminating the process. (I understand that's on the android devs since pull is made by them, and I doubt they would care to improve the command for a file system I doubt they use). Again I mostly included that so if anyone else is trying to figure it out they can stop looking for "a way" and just accept it can't be done.
Ultimately Khaon is right in that sideloading a rom would have unbricked it and I could have done the ADB backup then, I just wasn't sure how that might affect the app data storage so I was looking for a way to back it up before doing that.
Click to expand...
Click to collapse
I'd just 'tar' what I wanted on the device and then pull that with adb.

Yeah, I just had no idea what I wanted. I'm not 100% familiar with how the system stores application data, I figured if I copy everything than anything I "miss" after I formated it I'll be able to just research where it was and dig in the backup and pull it out.

Yeah adb sideload a rom will only affect system partition thus your data would not have been modified in any way. So you are done with your issue?
Sent from my Xiaomi MI2s

Khaon said:
Yeah adb sideload a rom will only affect system partition thus your data would not have been modified in any way. So you are done with your issue?
Sent from my Xiaomi MI2s
Click to expand...
Click to collapse
Yes, sorry for the slow reply. I've completed my update, just wanted to follow up on everything I did incase the information is useful for anyone else new to this like I am.

Internal SD Card Paths

Hey guys,
Quick newbie question for you. I followed the procedure in this thread ([ROM][5.1.1][LMY47V] 21 May- Stock Flashable Rom/Factory Image) to a T and have 5.1.1 on the Nexus 4 but for some reason my internal SD card paths are all messed up. I couldn't use my camera to take a photo - it wouldn't save anywhere.
I used Terminal to run the restorecon -FR command for /data/media/0/* and then I restarted the phone and I could use my camera, so that was a good step.
Now I'm in WhatsApp and I can't see any media that people are sending me. The photos stay blurry. Is WhatsApp pointing to a directory that doesn't exist? How can I solve that? Or is my internal SD card ****ed?
I am using TWRP so if you have any solutions I can fully utilize that to fix the path errors or re-flash system img or whatever you think will work! My brother is trying to send me photos through WhatsApp and I can't see 'em!
Any help is appreciated!
--Mike

Did usie the script included with the stock ROMs to flash back to stock?

audit13 said:
Did usie the script included with the stock ROMs to flash back to stock?
Click to expand...
Click to collapse
You mean the flash_all.bat? Nah - I manually flashed as per the forum thread I linked to. I installed through TWRP, not fastboot. My Nexus 4 only connects as an AC source so I can't even get it communicating with my PC to unroot and flash stock.

So the phone is not recognized in OS X, window, or Linux? Tried different USB cables and USB ports?

audit13 said:
So the phone is not recognized in OS X, window, or Linux? Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Yeah I've pretty much tried everything to get it communicating with the computer again. I think it's a hardware issue - I had my screen replaced and I think some part of the battery assembly wasn't re-installed properly and thus communication ceased. I thought flashing to 5.1.1 would fix what could have been a 4.4.4 issue, as I had USB fast charge enabled with various kernels, but alas this was not to be.
Any ideas about the internal paths?

A screen replacement does involve moving the USB charging port to the new screen and it is possible that this part was damaged and vertical seems to be the case. I assume you don't have access to another phone to test the port.

audit13 said:
A screen replacement does involve moving the USB charging port to the new screen and it is possible that this part was damaged and vertical seems to be the case. I assume you don't have access to another phone to test the port.
Click to expand...
Click to collapse
Yeah no other phone to test the port. I just got an X Play and am using the same cable I was using with my Nexus 4 and communication is flawless - adb, fastboot, all the goodies. I thnk I'll need to take the Nexus to a shop or open it up myself.
Thanks for paying attention to this thread, audit.

Try opening the phone yourself as it is pretty easy but that choice is yours. Good luck!.

Hi Mike, just a hint... did you check the partition status on your device ? To check if it's a logical or hardware issue, here's a reference: http://forum.xda-developers.com/moto-x-play/general/partition-layout-t3196367
You can analyze yours with something like: https://play.google.com/store/apps/details?id=com.cls.partition
and eventually mount manually the missing mounts.

dev>null;5160773 said:
Hi Mike, just a hint... did you check the partition status on your device ? To check if it's a logical or hardware issue, here's a reference: http://forum.xda-developers.com/moto-x-play/general/partition-layout-t3196367
You can analyze yours with something like: https://play.google.com/store/apps/details?id=com.cls.partition
and eventually mount manually the missing mounts.
Click to expand...
Click to collapse
Great idea, dev. How do I go about manually mounting? Do I need to use Terminal or something similar?
Thanks for your reply.

mounts & partitions
@XxMikeMasterxX Yes! In terminal emulator.
Code:
su
cat /proc/mounts
- or -
mount
- or -
df
- or -
cat /proc/partitions
to list all partitions/devices/... a bit messy output
The mount command is also what you'll need after you find the problem.
It can mount a partition, remount read-write...in case it's a permission problem, or bind a folder to another, in case it's looking for a specific folder, but your system named it in a different way.
Not sure if this applies to your case...just an idea Did your partitions check return any anomaly ?

dev>null;5160773 said:
@XxMikeMasterxX Yes! In terminal emulator.
to list all partitions/devices/... a bit messy output
The mount command is also what you'll need after you find the problem.
It can mount a partition, remount read-write...in case it's a permission problem, or bind a folder to another, in case it's looking for a specific folder, but your system named it in a different way.
Not sure if this applies to your case...just an idea Did your partitions check return any anomaly ?
Click to expand...
Click to collapse
Not that I can see. I'm a bit of a noob with Terminal so I'll even have difficulty identifying the erroneous file paths. It's too bad my adb and fastboot don't work. Or else I'd just revert to stock and re-flash everything.

@XxMikeMasterxX If you don't want to mess with terminal, try using the app linked in my first message then (or others that show mount points and partition details), and please use this as a reference. I posted the MXP one by mistake !!!

dev>null;5160773 said:
@XxMikeMasterxX If you don't want to mess with terminal, try using the app linked in my first message then (or others that show mount points and partition details), and please use this as a reference. I posted the MXP one by mistake !!!
Click to expand...
Click to collapse
@dev>null Eeeek! Scared! I'll try the app and see what I can see. I guess from there it's a simple remount.
So hypothetically let's say that sdcard is mounted somewhere else by mistake and some app folders end up on the wrong partition/location, do I use a remount to remount that particular folder/location to the proper sdcard path?
Whoa I think I just got it.

@XxMikeMasterxX Exactly! There used to be a bug in CM with wrong sdcard mount point. Take a look at this, I'm sure it will address you to the right direction
And also give you examples for command syntax...

dev>null;5160773 said:
@XxMikeMasterxX Exactly! There used to be a bug in CM with wrong sdcard mount point. Take a look at this, I'm sure it will address you to the right direction
And also give you examples for command syntax...
Click to expand...
Click to collapse
You're the man. I'll try it soon. My brother has the phone now so it could be a bit.

XxMikeMasterxX said:
You're the man. I'll try it soon. My brother has the phone now so it could be a bit.
Click to expand...
Click to collapse
@dev>null
My brother tried the Terminal commands but after he entered su and tried the other 4 commands Term returned "nothing found" each time. What does that mean?
Also, it appears that he needs to remlunt his entire SD card somewhere. What's the folder? Root/sfcard

@XxMikeMasterxX Nexus 4 does not have a physical sdcard, so I guess it's just a missing symbolic link.
Try:
Code:
su
mount -o bind /data/media /sdcard
and see if Whatsapp can save the images now.

Also you may want to check this guide: http://forum.xda-developers.com/google-nexus-5/general/howto-repairing-corrupted-data-partition-t2577447

dev>null;5160773 said:
Also you may want to check this guide: http://forum.xda-developers.com/google-nexus-5/general/howto-repairing-corrupted-data-partition-t2577447
Click to expand...
Click to collapse
@dev>null
Thanks for your recommendations. Yet again, though, the command you provided didn't work. I tried to get him to bind different locations to sdcard but that didn't help either.
A funny thing he told me is that under Settings>Storage he can't open the Internal storage section. He said it just doesn't open.
It's almost like Android installed to a really weird location and isn't recognizing anything. I am really baffled.
I checked out the guide - the o ly problem.is that the phone doesn't connect as a USB device (broken link...battery maybe?) and as such he can't run the adb commands.
I wish it did connect USB though - I'd just have him return to stock and then this would all be erased. Any other ideas, dev? I really don't know what to do next... Thanks for your ideas so far - you've been a great help.