Related
I got a Vibrant as a gift from my relative (he recently bought a Tab), and i can't erase the data (gallery, his gmail account).
I have done everything that i know, from factory reset to wipe data from recovery mode. Well, i even downgrade the firmware to the stock UVJFD, but no matter how hard i try, everytime i restart the phone, the data will always restored. the applications i installed are also gone it's like the phone create some restore point that resets whenever it gets rebooted.
I'm not living in US, so i guess i can't get support from T-mobile
please help.. and excuse me for my bad english ^^
settings>sd & phone storage>unmount phone storage>format will erase everything
if you want to format the microsd..its there too, but you will lose Avatar if you do..
jmcghee1973 said:
settings>sd & phone storage>unmount phone storage>format will erase everything
if you want to format the microsd..its there too, but you will lose Avatar if you do..
Click to expand...
Click to collapse
i't didn't work the pictures and gmail account is still there
there are 2 storages there ..one says sd card and the other says phone storage ...you unmounted the one under phone storage and hit format??? because there should be like 3 folders left after that..
i unmounted and formatted both the phone and sdcard storage.. to no effect.. flashing new firmware didn't help either..
hmmm.. yep.. beyond me then .. works for me every time so you might need someone with a little more knowledge.
getting hopeless
Did you try the data factory reset from privacy settings?
Sent from my SGH-T959 using XDA App
shovelhead83 said:
Did you try the data factory reset from privacy settings?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
already
Setting>Accounts and sync - if there are any of your relatives accounts under there, click on it then click remove account.
already... but to no effect..
fckndrmr said:
already... but to no effect..
Click to expand...
Click to collapse
All you have left then is to root and install a custom rom. That will fix the issue for sure or odin back to stock.
Dialing *2767*3855# will do a hard reset. That may help.
Sent from my SGH-T959 using XDA App
Monk4Life said:
All you have left then is to root and install a custom rom. That will fix the issue for sure or odin back to stock.
Click to expand...
Click to collapse
The problem is right there, I even could not do "re-install package" in the recovery mode because all data I kept in the internal sdcard will always be vanished if I reboot the phone,, I tried to mount the internal sdcard in the PC, then format the drive. It can be formatted, but after I rebooted the phone all the previous data come back. That's the problem
fckndrmr said:
The problem is right there, I even could not do "re-install package" in the recovery mode because all data I kept in the internal sdcard will always be vanished if I reboot the phone,, I tried to mount the internal sdcard in the PC, then format the drive. It can be formatted, but after I rebooted the phone all the previous data come back. That's the problem
Click to expand...
Click to collapse
Sounds like you need to get cwm recovery on there and format sdcards internal and external then reflash with Odin just to be safe
Sent from my SGH-T959 using xda app-developers app
So I flashed a new rom after backing up everything through Titanium Backup and Clockwork Recovery. I flashed the rom, but was met with a force close loop. I tried doing a factory reset through recovery mode and that got rid of the loop. But when I installed Titanium Backup, none of the backups were there. Same goes for Nandroid. What's going on?
Did u accidentally format ur sd card? Because tb is pretty reliable
Sent from my SGH-T959 using XDA Premium App
Never had this happen before, but to fix this in the future you should make a backup of the tb folder on your pc...actually you should do your entire internal and external sd anyway!
Sent from my SGH-T959 using XDA App
jl.1212 said:
So I flashed a new rom after backing up everything through Titanium Backup and Clockwork Recovery. I flashed the rom, but was met with a force close loop. I tried doing a factory reset through recovery mode and that got rid of the loop. But when I installed Titanium Backup, none of the backups were there. Same goes for Nandroid. What's going on?
Click to expand...
Click to collapse
Reboot and see if they're still there or plug your phone into a pc and try to access the sd card contents. I've had a few instances where TB didn't show me anything on the sd card until i rebooted. Weird but it's worth a shot before you do anything drastic.
movieaddict said:
Did u accidentally format ur sd card? Because tb is pretty reliable
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
Arghh I think this is what I might have done somehow. My sdcard folders did get messed up. I guess I'll have to start from scratch then...
For some reason unknown to me, CWM only see's my internal storage. Also, when I try to Wipe Dalvik Cache, it gives an error:
E: unknown volume for path [/sd-ext].
I am wondering if maybe this is maybe causing some sort of issue even though I wipe everything three times...
Yarbo said:
For some reason unknown to me, CWM only see's my internal storage. Also, when I try to Wipe Dalvik Cache, it gives an error:
E: unknown volume for path [/sd-ext].
I am wondering if maybe this is maybe causing some sort of issue even though I wipe everything three times...
Click to expand...
Click to collapse
ive had this same "issue" with it only seeing internal storage not sure what caused this all of a sudden, if anyone can clarify it would be much appreciated from the both of us.
Projectdwnshft said:
ive had this same "issue" with it only seeing internal storage not sure what caused this all of a sudden, if anyone can clarify it would be much appreciated from the both of us.
Click to expand...
Click to collapse
I am starting to think this causes some serious issues with roms that I install - cause I am betting that it is not properly wiping the internal storage....
Yarbo said:
I am starting to think this causes some serious issues with roms that I install - cause I am betting that it is not properly wiping the internal storage....
Click to expand...
Click to collapse
I wouldn't sweat it. I've had this issue as long as I can remember flashing on my note (a whole two months) and it hasn't caused any issues that I've noticed. If it's a good release, mine works the same as everyone's. Same with a buggy release, same bugs as everyone else. The sd-ext issue when formatting dalvik cache hasn't caused any (extra) bugs for me.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
I would use TWRP instead of CWM.
Did you try to fix permissions though in CWM?
I did try to fix permissions, and it said it succeeded, but still hasn't resolved the problem.
I'm not sure if it's an issue per se, based on one of the above posters. But it is annoying none-the-less, so if someone knows a way to fix this I'd be much obliged.
Also, what is TWRP?
Yarbo said:
I did try to fix permissions, and it said it succeeded, but still hasn't resolved the problem.
I'm not sure if it's an issue per se, based on one of the above posters. But it is annoying none-the-less, so if someone knows a way to fix this I'd be much obliged.
Also, what is TWRP?
Click to expand...
Click to collapse
The best way I can think of twrp is its cwm except for a lot more functionality with a more friendly user interface. You can flash it via goo manager app in play store which will overwrite your cwm as your active recovery.
As far as the card is concerned, I would start by...
Backing up w/e before starting
Plug into PC via in phone or memory card reader. All that is important is that your PC can see it.
Use the windows built in diskpart utility to clean it partition it and format it.
Let me know if you need the diskpart syntax, its from command line.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
lmike6453 said:
The best way I can think of twrp is its cwm except for a lot more functionality with a more friendly user interface. You can flash it via goo manager app in play store which will overwrite your cwm as your active recovery.
As far as the card is concerned, I would start by...
Backing up w/e before starting
Plug into PC via in phone or memory card reader. All that is important is that your PC can see it.
Use the windows built in diskpart utility to clean it partition it and format it.
Let me know if you need the diskpart syntax, its from command line.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
I can't just select the internal storage from Windows explorer, right click on it and select "Format"?
Yarbo said:
I can't just select the internal storage from Windows explorer, right click on it and select "Format"?
Click to expand...
Click to collapse
You can try, that might do the trick but if not try diskpart.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
lmike6453 said:
You can try, that might do the trick but if not try diskpart.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
I assume that doing this will leave CWM so that I can re-install CM10?
Is CWM stored on some other storage then internal storage? Some other memory chip or something?
I'm having this issue with CWM too, it's kind of driving me nuts cause it used to see both cards just fine before, and I don't like filling up my internal card with all my roms & radios. I'm kind of scared to use TWRP again though after what happened with my GSII. In short- I have reason to believe TWRP bricked my phone. I had just gotten my Note & was getting my GSII ready to sell(clearing data, formatting storage, etc). I booted into TWRP(which I'd been using for months, so it wasn't user error) & did a factory reset there too just to be safe. It seemed to work fine & gave me the "rebooting" message, and then.... nothing. Black screen. No boot, no recovery, no download mode, no signs of life whatsoever. I had to send it to Samsung to be fixed.
Now, it could have just been coincidental timing, but I'm now understandably hesitant to use TWRP again. Has this happened to anyone else? Sorry to hijack the thread.
In CWM, have you guys tried to mount sd card.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
There's an issue with the External SD listing coming up under the root emmc folder, rather than under Internal. Have y'all checked there for your External SD? This applies to CWM and TWRP.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I was about to post this issue, and I'm glad you beat me to it.
Was getting ready to Nandroid and flash a new ROM, but now got a new issue to deal with.
There's an issue with the External SD listing coming up under the root emmc folder, rather than under Internal. Have y'all checked there for your External SD? This applies to CWM and TWRP.
Click to expand...
Click to collapse
Nope, it comes up under "Internal".
I was trying to flash jellybomb rom and keep getting this error in
twrp recovery
Unable to mount '/usbstorage
Any one have a solution?
im getting the same issue with trying to bump up from m13 to m15 wont change baseband version or software version.
onemanruler said:
im getting the same issue with trying to bump up from m13 to m15 wont change baseband version or software version.
Click to expand...
Click to collapse
Same here with any rom it seems, even when doing a wipe of any kind.
Im going to try a older version of TWRP, smells like the recovery isnt right in some way, not the roms.
svghost said:
Same here with any rom it seems, even when doing a wipe of any kind.
Im going to try a older version of TWRP, smells like the recovery isnt right in some way, not the roms.
Click to expand...
Click to collapse
Found the fix for it. I followed one of the posts from chain fire who was referred to this method by someone I believe. (I apologize if I'm not giving credit to who referred)
1.Turn phone off
2. Remove sd card
3. Flash mi5 stock recovery( you can find a link in the general form in the let's figure this out guys forum on page 7 or so)
4. Keep sd card out while you boot the phone back up.
5. Update to new mj4
Hope this helps. I take no credit for this I just sumerized the genius devs of this forum who I have come to love since I found this place on my s3. Thanks devs
Sent from my SM-N900P using xda app-developers app
cocaineblunts said:
I was trying to flash jellybomb rom and keep getting this error in
twrp recovery
Unable to mount '/usbstorage
Any one have a solution?
Click to expand...
Click to collapse
Folks, this is NOT an error. It's support for OTG USB storage. Disregard unless you're using a USB OTG adapter and a USB Thumbdrive. Confirmed with the devs. (Which is where this question should have been posted)
Compusmurf said:
Folks, this is NOT an error. It's support for OTG USB storage. Disregard unless you're using a USB OTG adapter and a USB Thumbdrive. Confirmed with the devs. (Which is where this question should have been posted)
Click to expand...
Click to collapse
No this is an error.. It fails to install the rom and the only explanation at the end of the log is Unable to mount USBSTORAGE.. Whether it has anything to do with usbstorage or not that is the error we are getting. I am also getting this error. I wipe everything, go to install a rom and it fails.. I can nandroid back to my stock but that is about all I can do aside from flash some mods.
And for the record.. he's trying to get help and Troubleshoot which is the topic of this portion of the forum so I think it's perfectly placed..
xsisbest said:
No this is an error.. It fails to install the rom and the only explanation at the end of the log is Unable to mount USBSTORAGE.. Whether it has anything to do with usbstorage or not that is the error we are getting. I am also getting this error. I wipe everything, go to install a rom and it fails.. I can nandroid back to my stock but that is about all I can do aside from flash some mods.
And for the record.. he's trying to get help and Troubleshoot which is the topic of this portion of the forum so I think it's perfectly placed..
Click to expand...
Click to collapse
I had this issue, what i did to fix it was wipe everything, system, davlik, cache, data, and internal then I did a "format" data in twrp. Once that was done I restored a nandroid booted into it. Then back to recovery and flashed the rom. It was funny as before I did the format data I couldn't mount anything, including inernal storage even when in the rom.
Not sure if this will help you guys but it worked for me.
ifly4vamerica said:
I had this issue, what i did to fix it was wipe everything, system, davlik, cache, data, and internal then I did a "format" data in twrp. Once that was done I restored a nandroid booted into it. Then back to recovery and flashed the rom. It was funny as before I did the format data I couldn't mount anything, including inernal storage even when in the rom.
Not sure if this will help you guys but it worked for me.
Click to expand...
Click to collapse
The one thing I haven't done is wipe internal .. I was afraid of losing some stuff on my internal card.. I'll back anything up and give it a go. Thank you so much for your help and recommendation! I'll let you know how it goes.. I gotta download Jellybomb again as I tried moving it to my sdcard in recovery and it seems to have disappeared somehow.. . Thanks again!
xsisbest said:
The one thing I haven't done is wipe internal .. I was afraid of losing some stuff on my internal card.. I'll back anything up and give it a go. Thank you so much for your help and recommendation! I'll let you know how it goes.. I gotta download Jellybomb again as I tried moving it to my sdcard in recovery and it seems to have disappeared somehow.. . Thanks again!
Click to expand...
Click to collapse
Sure thing,if somebody that has MJ4 with passwords sticking can do a factory reset then TWRP back up their system partition and post it I may be able to make a zip that fixes this issue. Of course this is exactly what freeza did I am sure so it may not work but I could give it a try. I will pull system from the girlfriends phone but she is on a plane and gone for the weekend so it may be next week before I can get hers.
ifly4vamerica said:
Sure thing,if somebody that has MJ4 with passwords sticking can do a factory reset then TWRP back up their system partition and post it I may be able to make a zip that fixes this issue. Of course this is exactly what freeza did I am sure so it may not work but I could give it a try. I will pull system from the girlfriends phone but she is on a plane and gone for the weekend so it may be next week before I can get hers.
Click to expand...
Click to collapse
So I put the rom on my card, rebooted, wiped ONLY cache and dalvik and flashed the rom and it worked.. lol. This is what is called a dirty flash coming from the Evo LTE.. I would never have done this lol.. But if it works whatever lol. Thanks again for the recommendation. It actually installs more like a theme than a rom. Always interesting to learn the changes from phone to phone. Excited to see what's to come!
ifly4vamerica said:
I had this issue, what i did to fix it was wipe everything, system, davlik, cache, data, and internal then I did a "format" data in twrp. Once that was done I restored a nandroid booted into it. Then back to recovery and flashed the rom. It was funny as before I did the format data I couldn't mount anything, including inernal storage even when in the rom.
Not sure if this will help you guys but it worked for me.
Click to expand...
Click to collapse
thank you kind sir.
ifly4vamerica said:
I had this issue, what i did to fix it was wipe everything, system, davlik, cache, data, and internal then I did a "format" data in twrp. Once that was done I restored a nandroid booted into it. Then back to recovery and flashed the rom. It was funny as before I did the format data I couldn't mount anything, including inernal storage even when in the rom.
Not sure if this will help you guys but it worked for me.
Click to expand...
Click to collapse
Tried this, still get the error, at least on the Tmobile Note 3.
ifly4vamerica said:
I had this issue, what i did to fix it was wipe everything, system, davlik, cache, data, and internal then I did a "format" data in twrp. Once that was done I restored a nandroid booted into it. Then back to recovery and flashed the rom. It was funny as before I did the format data I couldn't mount anything, including inernal storage even when in the rom.
Not sure if this will help you guys but it worked for me.
Click to expand...
Click to collapse
Did ya have the backup on your external? If I'm reading this right, you wiped your internal storage. I've yet to successfully get a clean backup onto my external. It sounds like this could come in very handy, I just want to make sure I understand the steps in case I want to use this. Thanks, bro.
Sent from my Nexus 7 using Xparent BlueTapatalk 2
micmars said:
Did ya have the backup on your external? If I'm reading this right, you wiped your internal storage. I've yet to successfully get a clean backup onto my external. It sounds like this could come in very handy, I just want to make sure I understand the steps in case I want to use this. Thanks, bro.
Sent from my Nexus 7 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Yep had the backup on external. When this happened to me it was after taking the OTA to MJ4. Basically I had odined to full stock, factory reset and wiped internal. Then I removed external SD. Rebooted and took the MJ4 update. After this I flashed TWRP before CF auto root, this took me to an endless boot loop. I couldn't flash anything and anything I tried to run in Odin failed. So I wiped everything again, formatted system and data, tossed in the external SD and restored a nan droid. Presto I was back in business. I think having twrp flashed before cf auto root may have been the culprit. After I restored the nan droid I reran cf first then twrp. Since then no issues at all. In fact I have restored several nan droids from external and have had no problems.
Those nan droids were only of system, data and boot. I am using the latest TWRP with a scan disk 64gb external. I can't remember if it is formatted NTFS or fat32.... I will have to check that for you if you need the info. I am pretty sure it is NTFS but I did have it formatted fat32 for a while so like I said I will have to check that to be sure.
Break.....
In reply to the other post, if you have a T-Mobile version I would try the efs partition restore. I don't have the link anymore but it is in xda forum somewhere, if you search or ask around somebody is bound to know what thread it is in.
Last thing to try is wiping in recovery first then if the flash fails just reboot back to recovery with the twrp menu. Then don't wipe and try the flash again.
I have kind of jumped around a bit with the explanation and couple more things to try, hopefully it makes sense.
Note 3 or Gear Sent
ifly4vamerica said:
Yep had the backup on external. When this happened to me it was after taking the OTA to MJ4. Basically I had odined to full stock, factory reset and wiped internal. Then I removed external SD. Rebooted and took the MJ4 update. After this I flashed TWRP before CF auto root, this took me to an endless boot loop. I couldn't flash anything and anything I tried to run in Odin failed. So I wiped everything again, formatted system and data, tossed in the external SD and restored a nan droid. Presto I was back in business. I think having twrp flashed before cf auto root may have been the culprit. After I restored the nan droid I reran cf first then twrp. Since then no issues at all. In fact I have restored several nan droids from external and have had no problems.
Those nan droids were only of system, data and boot. I am using the latest TWRP with a scan disk 64gb external. I can't remember if it is formatted NTFS or fat32.... I will have to check that for you if you need the info. I am pretty sure it is NTFS but I did have it formatted fat32 for a while so like I said I will have to check that to be sure.
Break.....
In reply to the other post, if you have a T-Mobile version I would try the efs partition restore. I don't have the link anymore but it is in xda forum somewhere, if you search or ask around somebody is bound to know what thread it is in.
Last thing to try is wiping in recovery first then if the flash fails just reboot back to recovery with the twrp menu. Then don't wipe and try the flash again.
I have kind of jumped around a bit with the explanation and couple more things to try, hopefully it makes sense.
Note 3 or Gear Sent
Click to expand...
Click to collapse
I believe that the T-Mobile efs partition fix works great on this phone, if it's the miracle zip to which you are referring (small zip file labeled brick bootloop fix after restoring backup, or something to that effect).
The external SD card I'm using is only 16 GB (yeah, I know), so definitely not a problem with the way it's formatted (it's the one I had on my E4GT). It just fails on backup. I may try it again sometime, but just got tired of that red fail message.
Your explanation is clear and useful.
FWIW, I believe that boot, system and data comprise a complete backup, unless the efs gets fried. Also, I think that you may be right, that the TWRP then autoroot may have been the culprit, but back in business is way awesome (pain while in the mire, though).
In preparation for KitKat, I think a large external SD card is my next purchase, along with a complete wiping of internal, clean start and all.
Thanks for the info. Very helpful.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
I believe that the T-Mobile efs partition fix works great on this phone, if it's the miracle zip to which you are referring (small zip file labeled brick bootloop fix after restoring backup, or something to that effect).
The external SD card I'm using is only 16 GB (yeah, I know), so definitely not a problem with the way it's formatted (it's the one I had on my E4GT). It just fails on backup. I may try it again sometime, but just got tired of that red fail message.
Your explanation is clear and useful.
FWIW, I believe that boot, system and data comprise a complete backup, unless the efs gets fried. Also, I think that you may be right, that the TWRP then autoroot may have been the culprit, but back in business is way awesome (pain while in the mire, though).
In preparation for KitKat, I think a large external SD card is my next purchase, along with a complete wiping of internal, clean start and all.
Thanks for the info. Very helpful.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I'm sure the 64gb cards are much cheaper now. I think I got mine on amazon for like 50 over a year ago.
Every time I want to do a "clean" install I format the internal memory. I usually have backups of apps/data/rom on the sd card which makes using mybackup pro awesome to restore apps/data. But for whatever reason I am having trouble using mybackup with this phone..
So I've kinda been chillen on freezas rom / kernel waiting for development to increase more (it's coming along great)
Sent from my SM-N900P using Tapatalk
tt281gt said:
I'm sure the 64gb cards are much cheaper now. I think I got mine on amazon for like 50 over a year ago.
Every time I want to do a "clean" install I format the internal memory. I usually have backups of apps/data/rom on the sd card which makes using mybackup pro awesome to restore apps/data. But for whatever reason I am having trouble using mybackup with this phone..
So I've kinda been chillen on freezas rom / kernel waiting for development to increase more (it's coming along great)
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Been running that rom for quite a long time.
Yeah, I was looking at prices for 64 GB cards. Prices look quite good.
Sent from my SM-N900P using Xparent BlueTapatalk 2
I have run into this same problem. This is my first time tyring to flash on my note 3 and when I wipe or try to flash the rom I get the error that it is unable to mount usbstorage. I don't fully understand how you fixed this? Is there a stock image I need to flash?
Also a friend of my said that there is an issue with doing restores on the note 3, that it causes a bootloop. Is this true? It's the first I've heard of it
mike208 said:
I have run into this same problem. This is my first time tyring to flash on my note 3 and when I wipe or try to flash the rom I get the error that it is unable to mount usbstorage. I don't fully understand how you fixed this? Is there a stock image I need to flash?
Also a friend of my said that there is an issue with doing restores on the note 3, that it causes a bootloop. Is this true? It's the first I've heard of it
Click to expand...
Click to collapse
I have personally been switching back and forth between maximus ROM and AOSP and have had no issues with restoring backups through TWRP. As far as the unable to mount USB storage error I believe everyone gets that but it has never caused me an issue with flashing a ROM. It is looking for a mass storage device if I am correct. Sometimes after I do a factory reset I rebbot twrp back into recovery before I flash a new ROM and have not had any issues. Someone please chime in if you know better than I.
Hope this helps in some way.
Sent from my SM-N900P using Tapatalk
mhutton said:
I have personally been switching back and forth between maximus ROM and AOSP and have had no issues with restoring backups through TWRP. As far as the unable to mount USB storage error I believe everyone gets that but it has never caused me an issue with flashing a ROM. It is looking for a mass storage device if I am correct. Sometimes after I do a factory reset I rebbot twrp back into recovery before I flash a new ROM and have not had any issues. Someone please chime in if you know better than I.
Hope this helps in some way.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Not sure if it affected the wip or not, but I got that error pretty quick during the flash. I don't see how the rom could have flashed in under 10 seconds, so I do think it is affecting it from flashing and possibly wiping. Thanks for the info about the restore though
I am having trouble running a backup.
1. I have been rooted for some time no problems.
2.Bumped my phone yesterday. Used Terminal Emulator. Worked fine.
3. Booted into TWRP to Backup my phone. everthing looked good.
4.Ran a backup it started off fine backing up system files then kicks over to data files and I get a failed message.
5. I tried it on both sd cards and was unsuccessful.
Has anyone else had this problem?
lawless21 said:
I am having trouble running a backup.
1. I have been rooted for some time no problems.
2.Bumped my phone yesterday. Used Terminal Emulator. Worked fine.
3. Booted into TWRP to Backup my phone. everthing looked good.
4.Ran a backup it started off fine backing up system files then kicks over to data files and I get a failed message.
5. I tried it on both sd cards and was unsuccessful.
Has anyone else had this problem?
Click to expand...
Click to collapse
Bare with me for I haven't install bump yet, but your problem seems like something I had with my MAXX HD. My issue was after the KK update that I wasn't able to twrp to my SD card, I installed a SD Card fix https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en and It fixed... Hope this helps
Not able to backup with TWRP!
I have tried the SD Fix. Did not work.
It begins to backup system runs fine but fails when it starts to backup the data patition.
Did this with both SD cards with the same result.
Have you tried just backing up to internal memory?
Not able to backup with TWRP!
Yes . I have tried both internal and external memory.
Problem Fixed!
I did a factory reset!
Rerooted!
Rebumped!
I was able to run a full backup after.
I think it might been that I was on ART and not Dalvik. I should have tried going back to dalvik first. But it works! Let the romming begin.
I'm kinda having the same issue. TWRP sees internal but not external...
Sent from my VS985 4G using Tapatalk
sd_N said:
I'm kinda having the same issue. TWRP sees internal but not external...
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
You have to format the SD card to fat 32.
Yeah....lol...my noobness came out for a minute.. It was still exFAT from it's newness. Lol...thank u
Sent from my VS985 4G using Tapatalk