I don't know what happened, but I no longer have a working lock screen on my Verizon (T-Mobile network) LG G3.
All of a sudden, there's just no lockscreen whatsoever. I tried disabling the lock screen and then turning it back on using swipe, patter and PIN, but there's just no lock screen at all. If I hit the power button or let the device time out and go to screen off, when I wake the phone via double tap or hitting the power button, I'm just taken to my home screen. I've disabled trusted places and on body detection. That really shouldn't matter though as I should still get the swipe screen if those are active.
Even when I initially boot, it goes right to my desktop, where before, I had to enter my PIN first.
Completely stumped here.
Any ideas? I really don't want to factory reset.
Probably related. My screen is not timing out. I have screen timeout to 15 seconds, I'm not plugged in and the screen never goes off. Smart screen is off as well.
Any ideas now?
I have no ideas that don't involve first trying wiping Cache and Dalvik/ART, and then wiping those two plus Data if the first doesn't fix it, and then flashing the 10B TOT to start fresh if neither of those fix it. Of course before wiping Data I'd do an LG Backup to backup my user apps and user data, and before flashing the TOT, I'd move everything I want to keep from the internal storage. I'd also have a TWRP backup of the EFS which includes IMEI, and remove the SIM and MicroSD card before flashing the TOT or any kind of flashing when possible, as I believe flashing has occasionally wiped one of those items. Rare for the SIM and for the MicroSD card, but it happened to me with the MicroSD card.
Any time there's ever any kind of problem, the first thing to try should always be the wipes.
roirraW "edor" ehT said:
I have no ideas that don't involve first trying wiping Cache and Dalvik/ART, and then wiping those two plus Data if the first doesn't fix it, and then flashing the 10B TOT to start fresh if neither of those fix it. Of course before wiping Data I'd do an LG Backup to backup my user apps and user data, and before flashing the TOT, I'd move everything I want to keep from the internal storage. I'd also have a TWRP backup of the EFS which includes IMEI, and remove the SIM and MicroSD card before flashing the TOT or any kind of flashing when possible, as I believe flashing has occasionally wiped one of those items. Rare for the SIM and for the MicroSD card, but it happened to me with the MicroSD card.
Click to expand...
Click to collapse
The screen on issue wasn't really an issue, that was TiBu keeping the screen on.
I already did a factotry reset that fixed it. What a pain though, I'm still not full recovered.
I did wipe cache and dalvik before wiping data. Wiping data fixed it.
I've never had any luck with LG Backup, so I didn't do that, but used TiBu to recover, which didn't go so well.
I guess it's lucky I didn't have to go the whole TOT process. I've done that before and that's not fun either.
lexluthor said:
The screen on issue wasn't really an issue, that was TiBu keeping the screen on.
I already did a factotry reset that fixed it. What a pain though, I'm still not full recovered.
I did wipe cache and dalvik before wiping data. Wiping data fixed it.
I've never had any luck with LG Backup, so I didn't do that, but used TiBu to recover, which didn't go so well.
I guess it's lucky I didn't have to go the whole TOT process. I've done that before and that's not fun either.
Click to expand...
Click to collapse
Glad you solved it. Hopefully nothing you restore re-creates the problem.
I sure wish I knew why LG Backup doesn't work for some people? When you tried it did you try saving to internal storage, or just MicroSD card? I always save to internal since it's much faster than any MicroSD card, and then move it later if need be.
I'm used to TOTing. It's no big deal to me any more.
roirraW "edor" ehT said:
Glad you solved it. Hopefully nothing you restore re-creates the problem.
I sure wish I knew why LG Backup doesn't work for some people? When you tried it did you try saving to internal storage, or just MicroSD card? I always save to internal since it's much faster than any MicroSD card, and then move it later if need be.
Click to expand...
Click to collapse
I don't recall, haven't done it in a while. It didn't get me anywhere close to back to a full restore when I've tried it. I probably did it to SD card, but don't remember for sure.
lexluthor said:
I don't recall, haven't done it in a while. It didn't get me anywhere close to back to a full restore when I've tried it. I probably did it to SD card, but don't remember for sure.
Click to expand...
Click to collapse
If you have your MicroSD card formatted FAT32 (which is common, and what Android, TWRP and probably Windows would normally format it as), then I *think* that maybe LG Backup complains because it puts everything in one huge compressed file and FAT32 can't handle files over 4 GB in size, as it was made in 1977. ExFAT (you can format as such in Windows with the card connected directly to the PC/via adapter, etc) has no restriction. NTFS doesn't either but I wouldn't use that on a MicroSD card.
Another option is to back up half your apps the first time (A-K?) and then L-Z the next time.
Warning that some Android builds/kernels might not have ExFAT support built in, but I'm very sure stock LG does.
Of course if you don't have a huge amount of apps this probably wouldn't be the trouble.
roirraW "edor" ehT said:
If you have your MicroSD card formatted FAT32 (which is common, and what Android, TWRP and probably Windows would normally format it as), then I *think* that maybe LG Backup complains because it puts everything in one huge compressed file and FAT32 can't handle files over 4 GB in size, as it was made in 1977. ExFAT (you can format as such in Windows with the card connected directly to the PC/via adapter, etc) has no restriction. NTFS doesn't either but I wouldn't use that on a MicroSD card.
Another option is to back up half your apps the first time (A-K?) and then L-Z the next time.
Warning that some Android builds/kernels might not have ExFAT support built in, but I'm very sure stock LG does.
Of course if you don't have a huge amount of apps this probably wouldn't be the trouble.
Click to expand...
Click to collapse
I have a ton of apps. I will reformat to ExFAT when I get a chance and try to run LG backup again. I won't be chancing a restore though, but at least I'll see how the backup completes.
I'm actually currently formated as exFat. I can't say if I ever tried an LG backup formatted that way, but it's possible. I'll try to run one once I've fully recovered here.
Had a lot of recovery issues with TiBu. Got parsing error even when restoring via indirect method with many apps. I had to restore from a feb TiBu backup, then update all the apps in the play store, then I'm going to restore data with the new TiBu backup. Big PITA. New apps will still show as not restored from the new TiBu backup, so I can just d/l those from the play store and then restore data on this. Good excuse to not bother restoring apps I never use and shortening my total number of apps.
Aigh! Yeah, I've been having more and more trouble with TB which is why I just use LG Backup where possible, although the specific troubles you're having with TB don't sound the same.
MicroSD card in general just isn't as reliable as internal storage. Just plain copying files that have already been written to internal storage to MicroSD card is less taxing than having software create the files on the card to begin with. I've been in the habit of doing disk intensive stuff to internal storage starting with the Galaxy S2.
Hopefully your current restore journey is ultimately successful.
FWIW, I had to wipe data again today due to another issue I was having. I did an LG backup to my external SD that was about 6GB, wiped and did the restore. It looks like it did a pretty good job of getting me back to where I was. The text database is a bit screwed up. All of the group chats are showing at the top of Yaata for some reason. I have an sms backup & restore backup from last night, so I'll wipe the messaging database and restore that. Lot of settings I'll need to clean up, but apps look to be in good shape. Not sure why LG Backup totally didn't work for me previously.
Hope the data wipe fixed this problem (SIM card keeps getting disconnected), but I bet it doesn't and that'll be the end of my G3.
Related
Hi, I used to own a G1 but have got a hero (and I am proud). I always used A2SD with G1 because of the shocking storage, however I have been getting away with the amount on this for sometime now, Until recently, though, when apps have been getting bigger (20+mb for raging thunder).
Is the Hero the same as the G1, or am I able to remove the memory card that has A2SD (while the phone is switched off, i don't mind), put a different memory card in, and view images from that memory card (i put my digital camera card into phone often to send images) obviously with none of my apps installed, and then switch the phone off, put the original memory card back in, and carry on using apps like normal?
PS this is on VillainRom 4
Thanks
Bump..Anyone?
Can anyone help withthis? A simple Yes/No would do
Thanks
Considering how Apps2SD works (basic symlinks), as long as you have an ext partition with the appropriate folders on both cards (at the same place, number-wise), you should be fine.
I would imagine the boot process probes /data/app and /data/app-private at some point - you just need to make sure those exist (even if they're empty).
If you've moved dalvik-cache as well, you will experience slowdowns when you switch cards.
tucka20 said:
Can anyone help withthis? A simple Yes/No would do
Thanks
Click to expand...
Click to collapse
#
Why don't you just try it? Seems a lot simpler way of finding out to me!
Regards,
Dave
Here's a related issue.
Obviously with the OS relying on the ext partition, you shouldn't remove the sd card while the phone is on & certainly not while it's mounted (unless you want filing system corruption), but in my naivety I thought it would be ok to power down, remove the card & power back up. So similar to the situation the OP is asking about, only with no card, rather than a new card, present on the reboot.
Clearly your apps on the card are not going to work as they're gone & you might get some complaints as /data/app now links to a non existent directory, but I assumed:
1) Most things would work.
2) More importantly, I assumed if I then powered down, replaced the card & rebooted, I'd be back to where I started with fully working apps.
1) Turns out to be true.
2) Doesn't. After replacing the card I found most (though not all) apps resident on the card would force close at some point, often sooner than later. I ended up having to reinstall them.
Can anyone explain why/how this happens? I can only guess that when the phone was run without the card present, it changed the missing apps user data or dalvik cache in a way that broke them once they are brought back. Trouble is, I can't see what mechanism would result in such behaviour.
have you tried wiping the dalvik-cache before booting up after reinserting the card?
kendong2 said:
have you tried wiping the dalvik-cache before booting up after reinserting the card?
Click to expand...
Click to collapse
If you mean me, no. This was shortly after i got my phone & I was less comfortable experimenting. Plus at the time I didn't have a nandroid backup & reinstalling twenty odd apps put me off
I'll give it a try shortly though. First as you suggest, & if that isn't enough, I'll try wiping the cache when the card is first removed too.
[Edit:] Nope, wiping Dalvik cache doesn't help at all. It seems if you attempt to run an Android install which utilises apps2sd without the sdcard present, something gets changed in the existing partitions on internal flash (other than the Dalvik cache) such that when the system is subsequently booted with the card present, app installs will have been corrupted leading to force closures & the need to remove/reinstall those apps.
Seems a shame. I'd have preferred an atomic means of relocating apps to sd, such that removal of the card means the system behaves as if the app had never been installed, with normal behaviour once the card is replaced. Ah well.
At least I used the chance to revert my ext4 partition to ext3 to avoid having to use tune2fs everytime I want to run a nandroid backup.
BTW For the record I should make clear this was all tested on a gsm Hero running MCR 3.2 with Amon Ra's RA-hero-v1.6.2 recovery.
Ha! Painful memories. Found this out the hard way as well. Wish I'd read more about how A2SD works (symlinks). In fact I wanted to swap while phone was on.
cauli said:
[Edit:] Nope, wiping Dalvik cache doesn't help at all. It seems if you attempt to run an Android install which utilises apps2sd without the sdcard present, something gets changed in the existing partitions on internal flash (other than the Dalvik cache) such that when the system is subsequently booted with the card present, app installs will have been corrupted leading to force closures & the need to remove/reinstall those apps.
Click to expand...
Click to collapse
I tried wiping Dalvik cache as well as ext repair. Nothing helped.
cauli said:
Seems a shame. I'd have preferred an atomic means of relocating apps to sd, such that removal of the card means the system behaves as if the app had never been installed, with normal behaviour once the card is replaced. Ah well.
Click to expand...
Click to collapse
Agreed, serious "flaw" in the A2SD way of things.
cauli said:
At least I used the chance to revert my ext4 partition to ext3 to avoid having to use tune2fs everytime I want to run a nandroid backup.
Click to expand...
Click to collapse
I used to employ ext4 for the /sd partition, then I read ext3/4 wear out your SD memory much quicker, because they are journaling filesystems (see http://en.wikipedia.org/wiki/Ext2), so I used the opportunity to repartition and stick with ext2.
cauli said:
BTW For the record I should make clear this was all tested on a gsm Hero running MCR 3.2 with Amon Ra's RA-hero-v1.6.2 recovery.
Click to expand...
Click to collapse
When I had this happen, I too was on MCR 3.2, with Amon RA 1.6.2 or possibly 1.5.2 or 1.5.3.1.
Hi. My phone was bootlooping this morning, I decided to wipe data (I had a backup of /data) reflash, and carry on. However, I accidently confused the factory reset option in TWRP with the one in the bootloader, and clicked the bootloader one. This wiped my internal sd card. I tried to use things like Undelete from play, but it only works on the external sd. I've been trying to follow this guide (http://forum.xda-developers.com/showthread.php?t=1994705) to regain my data, but I don't know what the name of the /data partition is (for example, for the galnex, it's mmcblk0p12). Does anyone know A. what the name of the partition is for the evo, or B. an easier/different way to recover my files? Thanks in advance for any assitance.
/data is mmcblk0p37 according to steelh over in this thread
roids87 said:
/data is mmcblk0p37 according to steelh over in this thread
Click to expand...
Click to collapse
awesome. however, is /data the same as internal sd card?
Va1ha1a said:
awesome. however, is /data the same as internal sd card?
Click to expand...
Click to collapse
I am not sure. You could try and use the Mount Point Swapper and see if undelete will work then. I'm just tossing out some ideas. I've never actually tried to recover anything.
I'm gonna necrobump that first thread you linked to and see if anyone knows. I'll also try mount point swapper.
Edit: I've tried everything. mount point swapper caused bootloops, the guide i mentioned earlier created .raw files with nothing inside, etc. The upside is that I didn't have my roms, photos, or music on the internal. I can't remember. What else does android normally store there?
Va1ha1a said:
I can't remember. What else does android normally store there?
Click to expand...
Click to collapse
Usually not much, random app data, downloads, photos, music(depending on settings). You may get a warning in Titanium Backup(if you use it) about a different android id, you can restore your old id, or keep your new one. I have yet to see any issues. I've restored old id's and kept new is's without issues.
roids87 said:
Usually not much, random app data, downloads, photos, music(depending on settings). You may get a warning in Titanium Backup(if you use it) about a different android id, you can restore your old id, or keep your new one. I have yet to see any issues. I've restored old id's and kept new is's without issues.
Click to expand...
Click to collapse
Thanks, I don't think I had anything of massive importance on there (at least not that I can remember)
Hi 2 all,
Forgot to make nandroid and unlocked bootloader on my wife's m8. And 27GB of photos gone. I think she'll kill me after she wake up in the morning. Is there any way to get data back?
Unlocking the bootloader is not supposed to do that. It will wipe user data (/data partition) but I believe the internal storage ("virtual SD") should have been untouched. So you shouldn't blame yourself too much. And a nandroid would not have helped you as not only is that partition not backed up with a nandroid, but the default location for a nandroid is the internal SD, so it would have been lost, anyway.
That said, I try to backup any important personal data (even on partitions that are not supposed to be impacted) to my computer whenever doing something major like flashing a ROM or unlocking the bootloader. Only reason I've started doing that is a similar bug on the One X (EVITA) where actions that are not supposed to wipe the internal memory, occasionally did so (which is what I suspect happened to you).
I think your only hope is to use data recovery programs (Recova is a free one). But I've had mixed results doing so (and have seen similar reports here) when trying to recovery photos and other data that were "accidentally" deleted or recovered. Its certainly worth a try, and also keep in mind that you should do so ASAP as the more you use your phone, the higher the chance that those memory sectors where the photos were saved will be overwritten by other data.
Also, is there anything left on the internal memory at all when you browse with a file manager? Sometimes, corrupted data will be saved to a folder named LOST.DIR and there have times where folks have often found many of their photos simply moved there.
Found very helpful post
http://forum.xda-developers.com/galaxy-nexus/general/guide-internal-memory-data-recovery-yes-t1994705.
For M8 it works pretty much the same. I was able to get userdata partition from the phone, but because of I converted to GPE I lost everything. So I'm 99% sure that it will work right after unlock bootloader and factory reset.
exbarboss said:
Found very helpful post
http://forum.xda-developers.com/galaxy-nexus/general/guide-internal-memory-data-recovery-yes-t1994705.
Click to expand...
Click to collapse
Ah, that's true. I hadn't thought about the fact that the memory mounts as MTP now. The times I did the data recovery was on the old bulk storage mode on my One X (before it was switched to MTP). All I had to do was connect my phone to my PC and run Recuva.
Mind you, even mounted properly, data recovery programs will not always be able to recover all data. It was pretty hit or miss for me (and from other reports I've seen). But the linked method is also clever in that it makes a copy of the corrupted partition to your computer, so you sidestep the issue that those sectors may be overwritten as the phone is being used. Give you more times to try various data recovery apps, etc.
redpoint73 said:
Ah, that's true. I hadn't thought about the fact that the memory mounts as MTP now. The times I did the data recovery was on the old bulk storage mode on my One X (before it was switched to MTP). All I had to do was connect my phone to my PC and run Recuva.
Mind you, even mounted properly, data recovery programs will not always be able to recover all data. It was pretty hit or miss for me (and from other reports I've seen). But the linked method is also clever in that it makes a copy of the corrupted partition to your computer, so you sidestep the issue that those sectors may be overwritten as the phone is being used. Give you more times to try various data recovery apps, etc.
Click to expand...
Click to collapse
Yeah I tried Recuva, WinHex, R-Studio - nothing helped. I looked at low level data with WinHex and most sectors were zeroed...
Tennor1 said:
Just try for a sd card data recovery
Click to expand...
Click to collapse
Maybe I'm missing something, but I don't understand what is being referred to here. Can you clarify or give more detail?
Hello Guys, i have been attempting to flash the phone , but it doesnt go in flashmode ( i know it's volume down when plugging to usb ), but nothing happen with flashtool, any idea ?
Maybe driver, but it looks like the phone still in fastboot, and it s reconized by flashtool with the build number and kernel . i don t know how to go to this flashboot mode.
thank you
do i need to save my rooted stock rom backup on an xternal sd card before i install a new rom like viper that wipes everything or is it safe to save on internal storage
Slightly tricky question. Flashing a ROM is not supposed to wipe internal memory. For the large part, it isn't going to happen.
That being said, I tend to back up lots of things on my computer before flashing any ROMs (alternately you can use cloud services) due to the fact that on my old phone (One X EVITA) where was some bug which randomly wiped/corrupted files on the internal storage. It didn't happen all the time, and it seemed to happen less and less as time went on (updates to TWRP?). But it happened to me at least a couple times. Enough to make me back up anything not replaceable (photos in particular), as well as "emergency" copies of nandroids and Titanium data to my computer before almost any flash.
Also, I know that some builds of TWRP even wiped the removable SD. So even that is not guaranteed to be untouched when flashing. Don't know if Philz CWM has reports of any such issues.
Moral of the story: Nandroids should be fine on the internal storage. But never a bad idea to back up to other locations (even a computer) "just in case". Same goes with any other important personal data (photos, etc.). If it will upset you to lose it, back it up.
How can I back it up to my computer or to cloud storage
Jacobz1996 said:
How can I back it up to my computer or to cloud storage
Click to expand...
Click to collapse
To backup any files on your phone to computer, simply connect the phone to your computer by USB. Navigate to the desired folder or files, and simply copy and paste to your computer.
Cloud solution, it depends on what solution you pick (Google Drive, Dropbox, Mega, too many others to even list). For instance, Dropbox will prompt you when you first start the phone app if you want to backup your photos. You can then also backup any other phone files to your Dropbox.
redpoint73 said:
Slightly tricky question. Flashing a ROM is not supposed to wipe internal memory. For the large part, it isn't going to happen.
That being said, I tend to back up lots of things on my computer before flashing any ROMs (alternately you can use cloud services) due to the fact that on my old phone (One X EVITA) where was some bug which randomly wiped/corrupted files on the internal storage. It didn't happen all the time, and it seemed to happen less and less as time went on (updates to TWRP?). But it happened to me at least a couple times. Enough to make me back up anything not replaceable (photos in particular), as well as "emergency" copies of nandroids and Titanium data to my computer before almost any flash.
Also, I know that some builds of TWRP even wiped the removable SD. So even that is not guaranteed to be untouched when flashing. Don't know if Philz CWM has reports of any such issues.
Moral of the story: Nandroids should be fine on the internal storage. But never a bad idea to back up to other locations (even a computer) "just in case". Same goes with any other important personal data (photos, etc.). If it will upset you to lose it, back it up.
Click to expand...
Click to collapse
There seems to be a fix for the SD Card beeing wiped in this thread in post #498
.
I am on a sprint LGLS990, rooted with twrp. I have just started doing backups. I did one the other day on the internal storage which worked fine. Now I'm doing a bu on the external sd and worked well until generating md5. Its said this for the last 30 minutes. It appears that it is stuck. Is there any way to stop or cancel this?? I tried pushing any of the hardware buttons in back, but power just locks it, then I swipe to unlock it. Please help!! I don't know if I can do a battery pull or not if that would stop it, but I definately dont want to ruin my ext sd card as I have sensitive info that I need.
Update - I did a battery pull and it just seemed to reboot it. Nothing wrong with my external SD card that I can see. I can successfully do a backup on internal but everytime I try on external it gets stuck on generating md5. I have searched google but can't come up with anyone that has had the same issue on the g3. It's a sprint with model LG LG 990.Any help would be greatly appreciated. Just a thought, are there any other recoveries that work on my model g3?
jreink01 said:
I am on a sprint LGLS990, rooted with twrp. I have just started doing backups. I did one the other day on the internal storage which worked fine. Now I'm doing a bu on the external sd and worked well until generating md5. Its said this for the last 30 minutes. It appears that it is stuck. Is there any way to stop or cancel this?? I tried pushing any of the hardware buttons in back, but power just locks it, then I swipe to unlock it. Please help!! I don't know if I can do a battery pull or not if that would stop it, but I definately dont want to ruin my ext sd card as I have sensitive info that I need.
Update - I did a battery pull and it just seemed to reboot it. Nothing wrong with my external SD card that I can see. I can successfully do a backup on internal but everytime I try on external it gets stuck on generating md5. I have searched google but can't come up with anyone that has had the same issue on the g3. It's a sprint with model LG LG 990.Any help would be greatly appreciated. Just a thought, are there any other recoveries that work on my model g3?
Click to expand...
Click to collapse
Is the card larger than 32GB, and formatted as exFAT? If so, that's likely the problem. Our bumped version of TWRP has a bug affected the ability to read exFAT cards. If so, you can copy all the data off to a PC (or Mac), reformat the card as FAT32, and test it out. Here's some info on how to reformat the card to FAT32:
http://forum.xda-developers.com/showpost.php?p=57286346&postcount=30
meyerweb said:
Is the card larger than 32GB, and formatted as exFAT? If so, that's likely the problem. Our bumped version of TWRP has a bug affected the ability to read exFAT cards. If so, you can copy all the data off to a PC (or Mac), reformat the card as FAT32, and test it out. Here's some info on how to reformat the card to FAT32:
http://forum.xda-developers.com/showpost.php?p=57286346&postcount=30
Click to expand...
Click to collapse
Its a 64gb card and I'm not sure if it was formatted as exfat. I will try your suggestion. Will I lose any storage space by formatting the card to fat32?
jreink01 said:
Its a 64gb card and I'm not sure if it was formatted as exfat. I will try your suggestion. Will I lose any storage space by formatting the card to fat32?
Click to expand...
Click to collapse
If it's 64GB, it was probably formatted as exFAT from the factory. And yeah, you'll probably lose some storage space by formatting it as FAT32. How much will depend on what you have stored on the card. A lot of small files will waste more space than the same number of large files.
I just copied the external card to my desktop. I tried opening it up but it wouldn't open, saying it could not open that file. I even tried to extract and it said the same thing. I don't want to erase my card unless I know for a fact that my files are safe. With some apps, I have over 2 years of sensitive data that I can't afford to lose. Maybe it might be easier to just do a backup on my internal, then just copy and paste to my external.
There's a new TWRP that I believe fixes the exFAT bug:
https://www.androidfilehost.com/?w=files&flid=22315
meyerweb said:
There's a new TWRP that I believe fixes the exFAT bug:
https://www.androidfilehost.com/?w=files&flid=22315
Click to expand...
Click to collapse
I just did a backup on external SD. It appears to be working. The only thing is that it took 30 minutes to backup.
I am rooted and have the latest twrp recovery, think it is 2.8.2. On this version, I am able to save my backup directly to ext sd. I have noticed however that when I do a backup, it takes between 30 to 40 minutes to do one. However, I just did a restore last night and it took over a hour and a half. I have only had the phone about 2 weeks. When I had my S3, doing backup would takes kess than 10 minutes, same with restores. Is this normal or is something amiss?? Thanks for the feedback.
Update-
I have also noticed that when backing up to the internal that it takes just a few minutes, now when I backup onto the ext sd it takes about 20 minutes. The issue I had above I believe is connected when I used twrp manager instead of booting directly into recovery from the power menu. But its still taking alot longer to backup on my ext vs the internal. What would be the cause of that??
It seems most have issues if you SD is more than 32g.
The recommended format seems to be Fat32 on any card. That may be your issue. TWRP shouldn't be taking any extra time.
engine95 said:
It seems most have issues if you SD is more than 32g.
The recommended format seems to be Fat32 on any card. That may be your issue. TWRP shouldn't be taking any extra time.
Click to expand...
Click to collapse
I'm just wondering when I had my S3, I had the same card and did backups with both phiz and twrp and never had any of these issues and the backup and restore times were usually under 5 minutes. Now with the G3 I am having these issues.
jreink01 said:
I'm just wondering when I had my S3, I had the same card and did backups with both phiz and twrp and never had any of these issues and the backup and restore times were usually under 5 minutes. Now with the G3 I am having these issues.
Click to expand...
Click to collapse
It probably wouldn't hurt to format it and start over. Just like in the other thread I just answered you in. Start fresh and clean since you're starting with a different phone anyway.
engine95 said:
It probably wouldn't hurt to format it and start over. Just like in the other thread I just answered you in. Start fresh and clean since you're starting with a different phone anyway.
Click to expand...
Click to collapse
I just formatted for 64gb sd card, moved all my files back onto the card, checked on my pc and it said fat32 under properties. I did a backup and halfway through the data backup it failed. I have updated twrp to 2.8.3.
Any suggestions on why I can't use the external card??
jreink01 said:
I just formatted for 64gb sd card, moved all my files back onto the card, checked on my pc and it said fat32 under properties. I did a backup and halfway through the data backup it failed. I have updated twrp to 2.8.3.
Any suggestions on why I can't use the external card??
Click to expand...
Click to collapse
Did you format it in Windows/Linux as Fat32? Then move your files to it, and put it in the phone.
You may need to format it as 2 partitions.
Other than that, I really don't know what else to say.
engine95 said:
Did you format it in Windows/Linux as Fat32? Then move your files to it, and put it in the phone.
You may need to format it as 2 partitions.
Other than that, I really don't know what else to say.
Click to expand...
Click to collapse
I formatted it in Windows 8 but I had to use a third party program as Windows only had the options ntfc and exfat. I first deleted all my files, then formatted and copied all my files back, then inserted back in phone and tried a backup. In the third party software, I don't it gave a option to split the partitions.
Am I the only one having issues with creating and restoring backups on the external SD or ate others having the same issues?
Anyone else having issues backing up and restoring to the external sd card??
I'm just wondering when I was on the stock rom (with twrp recovery), I never had a issues backing up and restoring to the external sd card. Seems like this might be rom related, don't know, just a guess.
Also, are there any other recoveries that work with the G3, since it appears that twrp still has bugs.
I'm guessing not.
Pull your SD card out, or just make it backup to internal just to rule out TWRP.
Then maybe try a smaller card to make sure it's not your phone, or the pins for the SD card.
If the smaller card works, then you know it's the 64g card. It it doesn't, then it's got to be your phone.
engine95 said:
I'm guessing not.
Pull your SD card out, or just make it backup to internal just to rule out TWRP.
Then maybe try a smaller card to make sure it's not your phone, or the pins for the SD card.
If the smaller card works, then you know it's the 64g card. It it doesn't, then it's got to be your phone.
Click to expand...
Click to collapse
I have done backups through internal and everything works fine. I think I might have a 32 gb card around somewhere, if I can find it, I will try that and let you know the results, thanks.
jreink01 said:
I have done backups through internal and everything works fine. I think I might have a 32 gb card around somewhere, if I can find it, I will try that and let you know the results, thanks.
Click to expand...
Click to collapse
I just did a backup on my 32gb sd card. This card has not been formatted, its stock. It did do a backup but it took 40 minutes to do it. It appeared to get stuck on the last 1000 files when backing up data, the last 1000 files took over 15 minutes itself. I just did another backup, this time on my internal, it took only 5 minutes. How come its taking so long backing up to exernal, and thats with the 32gb card, still doesn't work on my 64gb card. Is anyone else have issues with backing up on a 64gb card?? I would like to know if i am a isolated issue or if others are having the same issues.
Try using Partition Master to format the 64GB card as FAT32, instead of exFAT.
http://www.partition-tool.com/personal.htm