Database Info

Problem with my rooted Inspire running Android Revolution HD not syncing correctly.

I got my Inspire and used it normally for about a month. Then I rooted it and tested out about 5 different ROMs and came to like Android Revolution for it's Gingerbread and Sense 2.0 that could have parts of it individually upgraded. (That's besides the point)
Anyway, as it only comes with an 8 GB microSD I looked on ebay for a 16 GB microSD and found one for about $20 or something, class 4. Anyway, I basically hooked up my phone with the old SD card in it, copied the entirety of its contents and then ejected the SD card and put in the new one. Pasted the contents from the old onto the new. Worked fine for a time. Now my phone will occasionally get stuck in a loop of boot animation, starting and working for 1 minute, then going back to the boot animation. I also noticed that any app installed to my SD through ZDBox becomes unusable. I then have to go back to the market and reinstall the apps as trying to restore from my Titanium Backup doesn't work.
I also have noticed that my photos and music can't be accessed. I even looked with root explorer and on my computer and can't find my music or photos at all. I've tried syncing using DoubleTwist and by copying and pasting the folders from the old SD to the new SD in the same directories.
Finally, just a bunch of force-close issues with everything on the phone. Using Rom Manager to Fix Permissions fixes things for a while but then it restarts.
I know it's a lot to read, but I don't know what is causing this and how to fix this. I even tried restoring a backup I had made, but it only resumed about 3 hours later. Any ideas or suggestions are welcome. Thanks in advance!

Things I would do:
If AR requires EXT4 sd card (it will say on the front page, and I believe it does)
-Format your sd card.
-Follow the steps for converting it to EXT 4 ( should be found on the front page)
-Create a back up with recovery or rom manager.(it doesn't matter which)
-Retain the 8gig back up.
-Wipe your phone through recovery (not through rom manager.)
-Redownload the rom.
-Re flash the rom.

Thanks, I'll be sure to try this later tonight.

Hate to reopen this topic, but when I tried to reflash the ROM, I was greeted with a an error saying I cannot open "(insert filename here).zip (bad)".
I've looked, and tried a couple of solutions other people have had, but so far they haven't worked. What can someone suggest?
I'm assuming it has something to do with the fact that the md5 checksums are different and don't match. I've downloaded AR HD about 5 times and moved to the phone. I get a different md5 checksum everytime.

Ssssschwartz said:
Hate to reopen this topic, but when I tried to reflash the ROM, I was greeted with a an error saying I cannot open "(insert filename here).zip (bad)".
I've looked, and tried a couple of solutions other people have had, but so far they haven't worked. What can someone suggest?
I'm assuming it has something to do with the fact that the md5 checksums are different and don't match. I've downloaded AR HD about 5 times and moved to the phone. I get a different md5 checksum everytime.
Click to expand...
Click to collapse
Make sure all anti virus is shut off when you dl the rom

zelendel said:
Make sure all anti virus is shut off when you dl the rom
Click to expand...
Click to collapse
Thanks for the advice. The checksum for the downloaded ROM matched, then I pasted it onto the SD and it matched when I checked it on the computer. Then I went into recovery and tried to load it and it's still giving me a the file bad error. I checked the checksum through recovery and it was a completely different checksum.
I'm really confused as to why I'm having these issues.....

make sure you disconnect the phone/sd card properly - sometimes the OS will report the file has fully written but the cache is still writing the file. If you can, use a service like dropbox or another file sharing (via web) and download the rom directly to the sd card - might get better results.

No need to bring back a very old thread. Thread closed

[Q] "E: Can't open /sdcard/tiamat-xoom-rom-2.2.1.moray.zip (bad)"!!

MZ601 Xoom on 3.1HC wifi + 3G rooted using Universal Xoom Root. Now wish to be able to use USB Host mode. Have followed the instructions in [ROM] Team Tiamat Xoom Rom 2.2.1 - Moray [18/9/11] including performing a factory reset (Wipe data/factory reset) from within recovery, and then selected "Install zip from sdcard" and selected the Tiamat zip file. The system reports that it is opening the file but then immediately aborts with the above message.
Assuming that the download was not successful I then downloaded again, went through the whole procedure again but came up with the same error. Hmmm this is a bit of a mystery.
So, is 2.2.0 a prerequisite of 2.2.1 and should I have tried to flash that first? Or could there be something else that this old fart is missing? I guess it must be the latter judging by all the success stories on here. Can somebody please help?
Irobbie.

irobbie said:
MZ601 Xoom on 3.1HC wifi + 3G rooted using Universal Xoom Root. Now wish to be able to use USB Host mode. Have followed the instructions in [ROM] Team Tiamat Xoom Rom 2.2.1 - Moray [18/9/11] including performing a factory reset (Wipe data/factory reset) from within recovery, and then selected "Install zip from sdcard" and selected the Tiamat zip file. The system reports that it is opening the file but then immediately aborts with the above message.
Assuming that the download was not successful I then downloaded again, went through the whole procedure again but came up with the same error. Hmmm this is a bit of a mystery.
So, is 2.2.0 a prerequisite of 2.2.1 and should I have tried to flash that first? Or could there be something else that this old fart is missing? I guess it must be the latter judging by all the success stories on here. Can somebody please help?
Irobbie.
Click to expand...
Click to collapse
So, just to clarify, you are rooted and attempting ti install the Moray Rom, and your Xoom is giving you an error that it can't access the sdcard to flash the Moray file.
My first question is, what version of CWM recovery are you using and is your Moray file on your external micro sdcard which is inserted in your Xoom?
It sounds like you are trying to flash from the Xoom's internal "sdcard" which doesn't work (unless you have the Rogue recovery installed).

Thanks for your reply.
Regarding the recovery mode version, in recovery mode my Xoom tells me "Clockwork Recovery V3.2.0.0 (solarnz-R4c-100611-1150).
Using "My Files", I have confirmed that the Zip file doesn't exist on the "Internal" storage, but does exist on the external SD card. This is where the Universal Xoom Root zip file sits and where it was installed from. The root zip file installed smoothly, and as far as I know I followed the exact same steps in trying to install the new rom. So I remain confused.
Once again thanks for your reply and any further help will be appreciated.
Irobbie

irobbie said:
Thanks for your reply.
Regarding the recovery mode version, in recovery mode my Xoom tells me "Clockwork Recovery V3.2.0.0 (solarnz-R4c-100611-1150).
Using "My Files", I have confirmed that the Zip file doesn't exist on the "Internal" storage, but does exist on the external SD card. This is where the Universal Xoom Root zip file sits and where it was installed from. The root zip file installed smoothly, and as far as I know I followed the exact same steps in trying to install the new rom. So I remain confused.
Once again thanks for your reply and any further help will be appreciated.
Irobbie
Click to expand...
Click to collapse
Ok, Sounds like you should be set regarding recovery. I'm pretty sure that you should be able to go right to Moray 2.2.1.
First, confirm that your sdcard is good and working properly by inserting it into a phone or a card reader. It could be as simple as a bad card. Also, you could redownload the file, but I think it's most likely your sdcard.

Thanks for getting back to me.
I replaced the SD card with another from my mp3 player and checked it out by loading up a song and playing it. No problems. So then I moved the zip file for the rom (which I had previously re-downloaded) over to the root of the sd card from my PC and proceeded through the steps again. Failed again. The message sequence reads:
--Installing: /sdcard/Tiamat-Xoom-rom-2.2.1-Moray.zip
Finding update package... (So its gone looking)
Opening update package... (And it is found?)
E:Can't open /sdcard/Tiamat-Xoom-Rom-2.2.1.Moray.zip
(bad)
Installation aborted
Hmmm. Just to check that the sd card is still viable, after reboot went back to "files", sdcard, music and selected a song and it played as normal. Also checked that the Tiamat rom zip file is on the card and yep, it is. So tomorrow morning I will download the zip file once again and retry. If you can think of anything else it will be much appreciated.
Irobbie.

If you can check to make sure the downloaded file is the right size that will be great. also make sure that you don't add another.zip file extension on the end, somehow. Some pcs are set up to hide file extensions and that's been a problem a few have encountered.

The mystery deepens! Well, for me at least.
Re: zip file extra extension, have show extensions switched on, and there is no extra extension.
So on to file size, it looks the same to me on each download so I went a bit further. I noticed the link to the file has a MD5sum check noted. So I downloaded an open source file "Sigma Informatics Checksum calculator", pointed it to the rom zip file and ran the check, and then cut and pasted the original number from the thread and got the calculator to do a check. Bingo - exactly the same!
So then copied the file from the Xoom back to the PC, ran the same checks and got different answer!
OK, I deleted the rom zip file from the Xoom, copied another over from the PC, then recopied it back to the PC to a different location, ran the check sum, got the correct answer, so now I knew I had a correct file on the Xoom.
Next, reran the installation of the Rom - failed again with the same results and messages as before.
Then copied the Rom zip file back to the PC to another location, ran the checksum and different answer popped out again. Well, could it be that the zip file is being corrupted during the install and that is why it fails? I've never heard of that sort of thing happening before but I suppose it is possible.
Your continued support is much appreciated.

It seems like I have heard of this happening, but why? What would cause that? Can you use a different method to copy the Rom file to the sd card? Using an adapter, and inserting the card directly into the sd slot of the pc? Download right onto the card?

Thanks for the reply and suggestions again.
To make absolutely sure I eliminated everything possible; I went out and bought a new micro sd card, and card reader with a micro sd card slot. Plugged it altogether into the pc and copied over a copy of the rom zip file.
Then did a checksum check on the file on the sd card and it was fine.
So, holding breath, puff, puff, puff, started the procedure all over again.
SUCCESS! It all went as smooth as silk! Thanks for your help and suggestions. But now I am left with a concern about where the problem really was - was it in the copying of the file onto the card through the Xoom, or was it, in fact, a bad card? I don't want to discard the card because it seems to be o.k. in every other respect so I think a little play around is in order. I think in all probability you are right in questioning the process I was using before, and recommending that the file be copied directly to the sd card.
But in the meantime I'm off to explore the new rom and in particular USB hosting.

Yes! I love success!
Enjoy.

o3d goes into recovery mode every time it boots

Hi guys, i'm in desperate need of your help. i think my precious o3d might have been screwed.
first let me tell you what i did. as you know the internal sd card of o3d is 5gb or so and it fills up very quickly. this internal sd card is mounted as /sdcard. i have a class 10 16gb micro sd card and when i insert it, its automatically mounted as /sdcard/_ExternalSD. The applications or games, especially the ones that have external data folders which are like 1gb in size insists to be installed on /sdcard. You can't move those data folders to _ExternalSD, because then the apps doesn't work.
Then i came across this topic:
http://forum.xda-developers.com/showthread.php?t=1189701
As you can see that was exactly what i needed. I had CWM 5.0.2.0 installed so i downloaded the first .zip then copied all of the files and folders excluding the _ExternalSD folder to the external sd card then rebooted into recovery. From there i flashed the zip and rebooted again. phone booted up and all was ok and it worked. now the phone sees the external sd card as the internal one and the internal sd card was mounted as /sdcard/_ExternalSD. I then formatted the internal sd card from the settings menu because i already copied all of the stuff there to the external card. It worked fine and the internal card is formatted. After that i decided to get a nandroid backup so i opened the rom toolbox program. From the menus i selected the backup option, gave it a name, clicked ok. the phone rebooted into cwm recovery screen but nothing happened. then i noticed something was not right because there was some error lines under the cwm menus saying "E:can't mount CACHE:recovery/command" etc. Then i selected the reboot phone option but the phone rebooted right back into the CWM recovery again!! At that point i knew that i was @#?^ed.
Anyways i researched a lot and came across this thread:
http://forum.xda-developers.com/showthread.php?t=1156549
i did exactly what he said and it worked, i mean it flashed nicely. then i rebooted the phone but it booted into the recovery again!!! But this time the CWM recovery was gone and i believe this is the stock recovery screen. I can browse the menu of it and make selections but the phone boots into the recovery every time it reboots.
The recovery screen looks like this:
http://farm8.staticflickr.com/7010/6654644033_b616bc0635_z.jpg
Then i flashed the phone to the latest official firmware V21A_00, it flashed nicely but it still boots right into the recovery everytime.
Then i installed the Android SDK and tried to push the original vold.fstab file to the system using the adb command line tool but it doesn't see the phone. I think adb works only when the system boots up normally, not in the recovery mode.
I don't know if there's a way to install the CWM from the stock recovery somehow. If you know how, please tell. The CWM has more options.
I don't know what else i can do. It started to look ridiculous. If there are any experts cool enough to help please do so. I'll be waiting. Thank you...
Edit:
I also tried this:
http://forum.xda-developers.com/show....php?t=1244490
I starts just fine but get's stuck on the "RESET" command, after a while it gives "DOWNLOAD FAIL!" error. I think the phone is supposed to restart automatically but it doesn't. Manually resetting the phone doesn't work either.
I'm about to pull my hair out...
Edit 2:
I also posted on the official LG Mobile forum here:
http://www.lgforum.com/forum/boards...d-goes-into-recovery-mode-every-time-it-boots
Fingers crossed

Quite a post!
From all your post there is no mention that you formated and did a factory reset after 21a flash.
Can you please try that if you haven't?
Sent from my LG-P920 using xda premium

thank you for the reply!
i tried all 4 wipe options on the recovery screen then rebooted. it's the same, i'm back at the good old recovery again

Did you try with the external sd card out?
This is strange, usually a kdz flash coupled with a format fixes the problem.
Some how it still can't find the internal SD card.
I don't have further recommendations. Sorry
Sent from my LG-P920 using xda premium

yes i tried with the external sd card out. it didn't work..

vpamir said:
yes i tried with the external sd card out. it didn't work..
Click to expand...
Click to collapse
Hopefully someone else on this forum can suggest a way for you to unbrick.
your problem is although you have reset your phone, somehow it can't find a partition to boot from.
or
somehow the KDZ flashing is not totally successful.
good luck

If only there could be a way to be able to use the adb command from the Android SDK then i might be able to restore the vold.fstab file to its original, if the problem is that at all. Maybe then it'll work. To be able to flash the CWM Recovery again somehow might be a good thing too because it has more options like flashing .zip format roms but i have no idea how. Does anyone know if the stock recovery can flash some specifically named file to the system, does it have that kind of functionality? I'm desperate, please share your thoughts.

.............anyone?

I am sorry to say that but there is no solution for this problem yet. I have done the exact thing that you do and tried every single solution with no luck. The only way is to send it to lg repair service. My solution was to replace the mainboard.
Dostum gecmis olsun malesef tek cozum yolu anakarti degistirmek. Uzaman sayilirim android konusunda bosuna ugrasmayasin diye soyluyorum. LG servisi bile anca anakarti degistirerek cozum sunabildi. Temel problem internal karti formatlamis olman. Partititon table'i bozuyor bu islem malesef ve bu yuzden hicbir yontem ise yaramiyor.
Gecmis olsun tekrar...

so you say that the main problem was to format the internal sd card? well if formatting the internal sd card bricks the phone then why the hell is there an option to format it in the settings menu?

well if you didn't apply the swap fix, it wouldn't be a problem to format. When you swap the sd cards and format, it is the problem.

crime_of_heart said:
well if you didn't apply the swap fix, it wouldn't be a problem to format. When you swap the sd cards and format, it is the problem.
Click to expand...
Click to collapse
so you did exactly the same thing as me right? i mean you applied the swap fix then formatted the internal sd?
replacing the motherboard to fix this seems to be a bit nonsense to me to be honest. what does the partition table have anything to do with the motherboard?
if only there would be a .kdz format custom rom which factory resets the internal sd card during the flash process and maybe fixes the bootloader somehow, that might be the solution.

yes i did the same and the only solution was to replace the motherboard. we need a sowftware that can reach to the emmc in low-level. like omap flasher. but we also need the correct drivers which doesn't exist yet.

crime_of_heart said:
yes i did the same and the only solution was to replace the motherboard. we need a software that can reach to the emmc in low-level. like omap flasher. but we also need the correct drivers which doesn't exist yet.
Click to expand...
Click to collapse
i don't know what the emmc is, i need to do research on that. but i still think that replacing the motherboard won't solve this issue because it seems non relevant to me. i messed up with the vold.fstab file. but after that it worked fine. i mean the internal and external cards swapped just fine. only after i decided to make a nandroid backup using rom toolbox all hell broke loose. i plan to wait a couple of days before turning the phone to LG service. i believe someone will come up with an idea.
yardım etmeye çalıştığın için teşekkür ederim bu arada

Well, there´s a new recovery for the O3D, v5.0.2.7 (I got it with ROM Manager).
It fixes 2 bugs of the previous (5.0.2.0) version: now the USB mass storage option in the mounts menu works (mount external SDCARD), and we can use ADB while in recovery. That way we can fix stuff in the phone filesystem while in recovery: we can now use ADB shell, or ADB push to replace files.
The problem is that I don´t know how to flash it to the phone while in the stock recovery. If someone can guide me on creating a signed ZIP containing this new recovery, flashable in the stock recovery, I would be glad to do that and post it here. I think these phones of you guys can be fixed using this method!

Marcovecchio said:
Well, there´s a new recovery for the O3D, v5.0.2.7 (I got it with ROM Manager).
It fixes 2 bugs of the previous (5.0.2.0) version: now the USB mass storage option in the mounts menu works (mount external SDCARD), and we can use ADB while in recovery. That way we can fix stuff in the phone filesystem while in recovery: we can now use ADB shell, or ADB push to replace files.
The problem is that I don´t know how to flash it to the phone while in the stock recovery. If someone can guide me on creating a signed ZIP containing this new recovery, flashable in the stock recovery, I would be glad to do that and post it here. I think these phones of you guys can be fixed using this method!
Click to expand...
Click to collapse
Great news! But now i need to find a way to install the new CWM. Just as you said i believe what i need is to find or make a .kdz update which includes this new CWM.
What do you think?

I know this is possible, at least for the Galaxy Ace: I have a ZIP file for this device with a custom recovery image, flashable in stock recovery!
To make one for the Optimus 3D, I need to know the following:
- How can I obtain the .IMG of the new recovery? I have found some temp files in clockworkmod folder in my sdcard. The creation date of one of them matches the exact moment I upgraded my recovery, and the file size also matches a recovery image: 5.54MB. Is it the recovery image? Can I just rename it to recovery.img? How can I extract it to ensure it´s ok?
- After I get the recovery image, I can use the Galaxy Ace ZIP as the base to build the O3D zip file. Any help on what do I have to change to make it work correctly?

I also tried this:
http://forum.xda-developers.com/showthread.php?t=1244490
I starts just fine but get's stuck on the "RESET" command, after a while it gives "DOWNLOAD FAIL!" error. I think the phone is supposed to restart automatically but it doesn't. Manually resetting the phone doesn't work either.
I'm about to pull my hair out...
Edit: I'm 99% sure that this isn't a hardware related problem. And LG's software not being able to turn the phone to stock is totally [email protected]#$%!

On some "unbrick your optimus 3d" threads i came across this image:
http://attachments.xda-developers.com/attachment.php?attachmentid=667470&d=1311752328
i tried all methods around here but not once i came across a screen like it. weird...

well i give up guys. so much technical [email protected] going on and no one seems to understand this device enough. i'll turn it to the LG Repair Service today. Thank you everyone for your help...

[Q] No way out of Bootloop + 'can't open /sdcard/update.zip (bad)' error

Ok..so I've been using HTC explorer for 2-3 months and everything was going fine but the low internal memory kept bugging me so I rooted the phone (i delayed rooting because it voids warranty..)..I deleted the pre installed apps and all other unnecessary crap..but the internal memory was still low so I went for factory reset..:|..and thats how you get into bootloop but searching for solutions..i found that my problem can be solved by flashing new rom..so I downloaded 1 and flashed it (yes i followed all the steps like creating ext4 partition and wiping cache etc).. but suddenly 'can't open /sdcard/*rom*.zip (bad)' popped up..so I went through the forums but didn't found any approved solution but suggestions like re downloading the rom..or checking if signature verification is off or flashing any other rom..i tried all of them..i retried re downloading the rom..I tried flashing cm 9..explode^1..Jaggyrom..even the stock rom but nothing positive happened..I am clueless..Please Help...

What recovery did you flashed, another thing, try with another sd card, or repartiotion this one through recovery after that get some rom on it. If you have a card reader, check if the card is ok.
And don't rename zip's live them with their original names.

shortyoko said:
What recovery did you flashed, another thing, try with another sd card, or repartiotion this one through recovery after that get some rom on it. If you have a card reader, check if the card is ok.
And don't rename zip's live them with their original names.
Click to expand...
Click to collapse
i flashed with A310e recovery...and the card is fine..I read somewhere to format the card with sdformatter and flash the rom from there and create the partition after the rom has booted..so i am trying that..I'll update you..thnx for reply btw.. :highfive:

Try installing CM10 Beta 2 on a clean, unformatted sd.
If that doesn't work, change your recovery.

Working fine
everything's alrite now..the thing that was causing the problem was the partitioned sd card...I removed partition and then flashed it and everything went well...:laugh:

[Q] External MicroSD card problems

I just found I have an issue copying files from my PC to my SGS3. The error I get is " Device stopped responding or is disconnected" (on my pc). It worked days ago, and it worked on the current ROM I'm using. I can't think of anything else I could have done to mess it up. This happens when trying to copy anything to the Ext card or internal storage. Here's the kicker: now I can copy small files, but big zip files are a no go. Before I couldn't copy anything. All I did was reboot phone and PC, and looked into phone with Root Explorer, no changes.
I can copy files FROM the phone to PC but not to the phone from PC. How could this change literally overnight?? I did find a way to add Google Wallet to the phone. Could that have possibly been it?? Flashing a new ROM right now, gonna see if it helps.
New ROM didn't help. Still same issue.
*Update* Next day, I tried once again just for fun. And now it works fine! I did nothing to correct it. I did however reflash the ROM that the problem first arose. But I still don't get how that's even related to the ext sdcard. And how did it fix itself??? Would still like to know why it happened!

Real_JESRadio said:
I just found I have an issue copying files from my PC to my SGS3. The error I get is " Device stopped responding or is disconnected" (on my pc). It worked days ago, and it worked on the current ROM I'm using. I can't think of anything else I could have done to mess it up. This happens when trying to copy anything to the Ext card or internal storage. Here's the kicker: now I can copy small files, but big zip files are a no go. Before I couldn't copy anything. All I did was reboot phone and PC, and looked into phone with Root Explorer, no changes.
I can copy files FROM the phone to PC but not to the phone from PC. How could this change literally overnight?? I did find a way to add Google Wallet to the phone. Could that have possibly been it?? Flashing a new ROM right now, gonna see if it helps.
Click to expand...
Click to collapse
I had this EXACT same problem a few weeks ago. I'm not saying this is the case for you, but I found out that when I tried to batch transfer certain files, one of the files was corrupt. I eliminated whatever the culprit file was and was able to transfer. The strange thing is, it only happened when I tried transferring from internal to external as well, as if something in the transfer corrupted one of my files. So I started transferring files one by one, and the problem seems to be temporarily eliminated. Check to see if the zip file became corrupted in some way. Hope this helps.

MindArchr said:
I had this EXACT same problem a few weeks ago. I'm not saying this is the case for you, but I found out that when I tried to batch transfer certain files, one of the files was corrupt. I eliminated whatever the culprit file was and was able to transfer. The strange thing is, it only happened when I tried transferring from internal to external as well, as if something in the transfer corrupted one of my files. So I started transferring files one by one, and the problem seems to be temporarily eliminated. Check to see if the zip file became corrupted in some way. Hope this helps.
Click to expand...
Click to collapse
I can transfer from ext to internal. I just can't transfer anything larger than a few MB. The zip files I'm trying are ROM zips so they are very large. Can't find anyone with this exact issue. I just flashed a new ROM, before that I formatted my sdcard. No idea what's wrong. Thanks for the reply though!

Real_JESRadio said:
I can transfer from ext to internal. I just can't transfer anything larger than a few MB. The zip files I'm trying are ROM zips so they are very large. Can't find anyone with this exact issue. I just flashed a new ROM, before that I formatted my sdcard. No idea what's wrong. Thanks for the reply though!
Click to expand...
Click to collapse
No problem at all. Do you think it's possible that the format you formatted the sdcard in may possibly be causing the issue? I've heard cases that incorrect formatting can block file transfers if over so many MBs, GBs, etc.

Real_JESRadio said:
I just found I have an issue copying files from my PC to my SGS3. The error I get is " Device stopped responding or is disconnected" (on my pc). It worked days ago, and it worked on the current ROM I'm using. I can't think of anything else I could have done to mess it up. This happens when trying to copy anything to the Ext card or internal storage. Here's the kicker: now I can copy small files, but big zip files are a no go. Before I couldn't copy anything. All I did was reboot phone and PC, and looked into phone with Root Explorer, no changes.
I can copy files FROM the phone to PC but not to the phone from PC. How could this change literally overnight?? I did find a way to add Google Wallet to the phone. Could that have possibly been it?? Flashing a new ROM right now, gonna see if it helps.
New ROM didn't help. Still same issue.
Click to expand...
Click to collapse
I had this exact problem as well. After a lot of trial and error, I gave up on the native MTP file transfer method, and went with ADB instead.
I use a very nicely done GUI on top of ADB to do all my file transferring called QtADB. Just install the Android SDK first, and then the GUI.
QtADB Android Manager Website
XDA QtADB Forum Link

MindArchr said:
No problem at all. Do you think it's possible that the format you formatted the sdcard in may possibly be causing the issue? I've heard cases that incorrect formatting can block file transfers if over so many MBs, GBs, etc.
Click to expand...
Click to collapse
I'm going to try and find the adapter that came with the micro card. I've read where some people having this issue have to use the adapter to plug into the PC directly to copy files. What I don't get is how it just happened all of a sudden. It was working just a few days ago, I loaded a bunch of music no problem as well as ROMs to flash. Very weird. It has to be a setting somewhere lol.

MindArchr said:
No problem at all. Do you think it's possible that the format you formatted the sdcard in may possibly be causing the issue? I've heard cases that incorrect formatting can block file transfers if over so many MBs, GBs, etc.
Click to expand...
Click to collapse
Just for grins, I hooked my phone up again to see by chance if it would work. Guess what? It works WTF?????? That's the craziest thing. I am back on the original ROM I had installed when the problem arose. But I just don't see how that's possible. UGGGGHHH

Real_JESRadio said:
Just for grins, I hooked my phone up again to see by chance if it would work. Guess what? It works WTF?????? That's the craziest thing. I am back on the original ROM I had installed when the problem arose. But I just don't see how that's possible. UGGGGHHH
Click to expand...
Click to collapse
now that's crazy, lol. glad to hear it's working