Related
Hey guys I need your help
I've been using cm7 for a couple of weeks now. I havnt had problems until today.
I flashed build 32 over and for some reason it wasn't booting up. It was on the splash screen for a while (it usually does that and when I take battery out and restart it boots) so then I took the battery out. Next thing I know is that my phone is stuck on the mytouch screen... I went to recovery and when it booted into cwm 3. I got a error saying it couldn't open system/recovery/log or something like that... it still went to cwm and I checked the mounts and it said /system and /data wasn't mounted. I clicked it to mount and it gave me an error saying it couldn't ... therefore it wouldn't let me install cm7 or do a wipe... is there anything I can do to fix this? It seems to be that the nand. Is corrupted or something...
I think, based on your description, that pulling the battery at the particular instant caused the secondary problem.
A "factory reset" reformats /data and /cache. But not /system. You can do that manually from the mounts and storage menu, then either restore a nandroid backup or install cm7 and gapps.
HTC Glacier running CM7 #33
Hmm I font think its just two directories... I think my whole internal storage is messed up. I tried using the reformat option from cwm but no luck
Time to discover what you might be able to accomplish with Fastboot and a USB cable.
HTC Glacier running CM7 #33
I think a lot of people are having problems with clockwork 3 in the nexus forums, and more specifically with it screwing up partitions. I was luck just to lose my ext position on my sd...
Reformat and reflash seems to be the easiest fix...
Sent from my Nexus One using XDA App
i dont know how to repartition the phone storage :/
i tried doing it off cwm and it wouldn't let me... is there anyway to do this through adb? i think adb is working...
Reformat the whole card, and then try to repartition. This will write your data, so back up first...
Sent from my Nexus One using XDA App
how do i do that? o_o through cwm? i tried formating everything including system data cache... and i dont know how to repartition through cwm. cwm is the only thing i can get to right now :/
Sorry, looks like the only option in clockwork is to partition. Can you not do it from your pc?
Sent from my Nexus One using XDA App
yeah it gives me error when i try to do :
fastboot erase system -w :/ is there anything else?
guys... ((((( am i totally effed up? i couldn't find anything i could do.. no matter what i did, the /system and /data would NOT mount... so i cant format it
I have never tried this, but you might consider it.
In this thread is a method to return your phone to stock -- it uses the bootloader's ability to repartition and reformat everything somewhat automatically, using a file called PD15IMG.ZIP from the SD card's root folder.
http://forum.xda-developers.com/showthread.php?p=11011692&highlight=pd15img.zip#post11011692
There's a link in the thread to the .zip file -- look to post signatures. Put the file on an SD card (with another phone, or camera, or Micro-SD to SD adapter, etc.) and boot into the bootloader with that file on the SD card.
I do not know if you can rename the .zip it to update.zip and force it to flash with Fastboot's update command, because the PD15IMG.ZIP is a specific thing this phone's bootloader looks for. As stated, I have never tried this, and do not recommend this. It might work, or, it might cause more damage. Putting the file on an SD card without Fastboot will be safer.
You could try to boot your phone into fastboot,
and then type
fastboot erase -w system
Your phone wont boot after that, but you should be able to flash a new rom from clockwork.
ive tried both the pd15img.zip method. it says "partition update fail"
and i also tried the "fastboot erase system -w" and it did not work.. it says that it can't be done. i also tried to format /system through adb and cwm, and both says it can't because it must be mounted before
From your description, it seems to me that the internal flash memory has a damaged partition table -- easy enough to repair if this were a hard drive you could remove and take to a linux system somewhere. But it's a phone, and a bit of flash memory that can't be removed.
Flashboot has an "erase <partition>" command. I don't know what it does, since it's not well documented. Does it reformat an existing partition? Or does it remove the partition from the partition table? There is no commensurate "create <partition>" command, so perhaps it recreates an empty partition. But I tend to doubt it.
I would think such work might be done from an engineering bootloader or engineering recovery system -- one available to HTC service technicians, for example.
Since you're not getting a great deal of help in the MT4G subforum, you might post your question in the top level Questions and Answers forum.
Sorry I'm not much help with this.
One last thought. The bootloader itself has a Factory Reset. That might do it. Might not. But like chicken soup, it probably couldn't hurt. Boot into the bootloader (volume down while powering up), select BOOTLOADER with the volume control and then the power button, then select FACTORY RESET. Perhaps it will do something positive.
eh.. i couldnt do anything. i tried all options. its like impossible to reformat or repartition the drive..
i actually called up insurance and they'll be sending me a new mytouch 4g..
we have just told them that it doesnt go past the mytouch screen.. would they figure out that it is rooted? i mean.. choosing recovery from the bootloader menu takes it right into cwm lol
Just flash the stock recovery back via fastboot...
Sent from my Nexus One using XDA App
ive tried
dumbkkid said:
ive tried
Click to expand...
Click to collapse
you are sending the fastboot commands while in the bootloader right? I would imagine you are but I just want to make sure.
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...
I am asking this again here, as my previous thread seemed to be hijacked by someone elses question!
I recently decided to root my inspire as i am no longer using it as a phone, so i thought that it would be interesting to do and fun to play around with all of the options available (i recently did the same thing on my Nook Tablet, and that was the single best decision i have made a while!). I started out researching the manual techniques to do it, but i didn't really like the high risk factor there (i really dont want to brick my phone) so i tried Ace Hack Kit. Of course, it has to download the phone from 2.3.5 to be able to work. During this process, it has me hold volume up and power twice, and every time i do that, it flashes up really quick something about holding volume up and volume down and power, but then it skips past that. Anyway, here is where my problem comes in: It says that it should reboot in to hboot, which it does, but that hboot should run a test, then prompt me to continue by pressing volume up, and then should reboot, flashing twice, and that should be the end of it. THe problem is, it does boot in to hboot, but it is just a standard hboot screen asking to recover, load bootloader, etc. When i reboot from there it just boots in to the phone as normal. I have tried 3 different SD cards, all of which work and are recognized by my PC, my other phone and my Nook tablet. I have also inserted a working sim card, just to be sure that wasnt the issue, and i still cant make it work. Does anyone have any experience with his issue, or any idea what i might be doing wrong?
Opening multiple threads on the same issue is frowned upon. Even if someone supposedly hijacked your thread. I read it and only 7 posts ,I'd call that far from hijacked.
Now at the issue on hand. As mentioned in the other thread. Its the SD card. Also their is a hack kit irc go there. Plus pasting the output would help aswell
marsdta said:
Opening multiple threads on the same issue is frowned upon. Even if someone supposedly hijacked your thread. I read it and only 7 posts ,I'd call that far from hijacked.
Now at the issue on hand. As mentioned in the other thread. Its the SD card. Also their is a hack kit irc go there. Plus pasting the output would help aswell
Click to expand...
Click to collapse
OK, as i have stated, i have tried a new SD card (2, actually, with the same results.) as far as an output screen, there is none. Ace Hack Kit goes through the whole downgrade process, my phone gets in to hboot, but it is just a standard hboot screen, and it doesn't downgrade. When my phone restarts, it restarts like i just did a factory reset.
There is an output,copy what ever it says. There probably is something you missed
As too the SD card ,try adifferent one again. Your SD cards are corrupt and you need to find one that works with the kit
Also since your on a sense 3.0 did you do the changing of the boot img before running the kit?
marsdta said:
There is an output,copy what ever it says. There probably is something you missed
As too the SD card ,try adifferent one again. Your SD cards are corrupt and you need to find one that works with the kit
Also since your on a sense 3.0 did you do the changing of the boot img before running the kit?
Click to expand...
Click to collapse
by changing the of the boot img do you mean downgrading it? That is what i am trying to do. The kit is supposed to do it automatically. If that is not what you mean, please explain!
As to the output, copy thing, no, there is none of that. I have followed the instructions about 20 times. After starting the downgrade process, the phone restarts and comes up with a red triangle. At that point i am supposed to hold volume up and power, and it goes and reboots and i do the same thing again. At this point, i am told that the phone will boot into hboot and check the boot image. When it is done, i am supposed to hit volume up to confirm, and then the phone will reboot, this time in to the down graded image. That is where my problem comes in. Instead of checking the boot image, it just goes to a standard hboot screen. There are no error messages or warnings, and i have followed the instructions to the letter.
As far as the cards are concerned, the maker of the kit suggested a 2 or 4gb Sandisk series 4 or 6 SDHC card, so i bought 2 of the series 6 4gb, along with the 2 others that i already have. I also have 2 series 4 4gb and 2 series 4 2gb Sandisk cards, as well as an 8gb and 2 4gb PNY cards. All of the cards recognize in my phone and PC, and the older cards also recognize in my Nook (and were used to root and load custom roms on several other devices), i have not loaded the new cards in to any other devices besides my laptop and the phone for fear of corrupting it. So i find it difficult to believe that the cards could be the problem.
I know what the kit says. What I'm saying is In the command prompt it spits out a lot of info. For example it will say stuff about zergrush and or taco root. THATS the important stuff, this is what is used to allow the downgrade to be possible. If their a failure in the process it would state it there. That's why I keep asking for it. Don't understand your reluctance to do a simple copy and paste
The changing of the boot img is something that is different and you should read about it on attn1 site. Version 3.20 has a slightly different method
marsdta said:
I know what the kit says. What I'm saying is In the command prompt it spits out a lot of info. For example it will say stuff about zergrush and or taco root. THATS the important stuff, this is what is used to allow the downgrade to be possible. If their a failure in the process it would state it there. That's why I keep asking for it. Don't understand your reluctance to do a simple copy and paste
The changing of the boot img is something that is different and you should read about it on attn1 site. Version 3.20 has a slightly different method
Click to expand...
Click to collapse
I appreciate the attempt to help (the reason why i didn't post a direct copy paste was simply as i was in no position at the time to take one, not any reluctance to ultimately do so...) In my recent attempt to provide you with a full copy paste of the process, i was able to figure out what i was doing wrong. For anyone who may have the same or similar issue: format the SD card while it is in the phone from your PC right before starting the process. Thats all it took. Even for a card that was brand new and untouched, or formatted before putting it in the phone, i couldn't get it to work, but it worked doing it that way, and i am now happily rooted and ready to install CM9!
Glad you got it figured out. Formatting the SD card in the phone is a must, since the phone puts important files on the card after formatting.
pazzo02 said:
Glad you got it figured out. Formatting the SD card in the phone is a must, since the phone puts important files on the card after formatting.
Click to expand...
Click to collapse
Wrong. There's no need to format the sdcard to run the Hack Kit, unless your sdcard is not in fat32 system file format. The only requirement is that your sdcard must not be corrupted to work as a goldcard. Corruption of the boot partition of the sdcard can not be solved by formatting and is produced by improper dismount of it.
glevitan said:
Wrong. There's no need to format the sdcard to run the Hack Kit, unless your sdcard is not in fat32 system file format. The only requirement is that your sdcard must not be corrupted to work as a goldcard. Corruption of the boot partition of the sdcard can not be solved by formatting and is produced by improper dismount of it.
Click to expand...
Click to collapse
I'm just speaking from experience. Every SD card I've put in my phone I had to format in the phone because it was giving me problems. After, no problems. Maybe it's just my phone. or the cards weren't FAT32.
You're last sentence is probably where most people screw it up. You can't just yank an SD card out of whatever device it's in, which I think a lot of people do. But I have fixed cards that were removed without unmounting by formatting. Maybe other parts were corrupt but not the boot partition?
pazzo02 said:
I'm just speaking from experience. Every SD card I've put in my phone I had to format in the phone because it was giving me problems. After, no problems. Maybe it's just my phone. or the cards weren't FAT32.
You're last sentence is probably where most people screw it up. You can't just yank an SD card out of whatever device it's in, which I think a lot of people do. But I have fixed cards that were removed without unmounting by formatting. Maybe other parts were corrupt but not the boot partition?
Click to expand...
Click to collapse
As far as I am concerned the boot partition can not be restored by formatting. SDCARD should always be dismounted properly.
Hello everydody, I am experiencing some difficulties with my Samsung, model GT-I9003-phone which "dropped off a lorry" somewhere next to my relatives somewhere in Asia. When I goth the device, it was in a non-working condition, except a boot-loop and the download-mode. Back then, I had the package of the phone where the exact version ( I don't know if this is what is called "Baseband" or at least is called baseband at my wife's GT-I5003) was specified. So, back then, I was able to find the exact ROM for the device. Unfortunately, the box with the version number now is - somewhere.
After flashing a stock-rom, I managed to enter recovery-mode where I read something about the internal memory being corrupt. As far as I can recall, I then mounted the external SD-Card and somehow managed to reboot the system back to almost normal operation. Even reboots appeared to work normal, besides the fact I had no memory access, neither to internal nor to external sd. In addition, GPS malfunctioned, too.
Unfortunately, even this state didn't last for long time. After several weeks of now-and-then-use, the system just broke down again into a boot-loop. After some time of flashing a variety of stock roms, I managed to flash clockworkmod recovery which works perfectly well. Unfortunately, I didn't manage to root the phone before it "collapsed" again. Besides the possibility, I'd guess this could be a resaon for CWM being unable to flash a custom rom? Otherwise, I'd just test my way through the varieties of versions .
Basically, I do have two questions: 1. is there a possibility to find out if internal memory has failed - and if yes: How?
2. Is it possible to install any version of CM on that phone in the condition it is in?
Thanks a lot in advance for any answers
Hello everybody, I finally found the box . It reads GT-I9003MKDTHL. Is my assumption right that there are no such things as basebands in the GT-I9003 any more and I should be able to flash pretty much any firmware? Furthermore, today I tried to format what is specified as "sd-card ext" in CWM fir GT-I9003 and it gives me an error-message. When I flash "sd-card", my external sd-card gets formatted. So, I'd presume the internal sd is just fried. I read about a workaround for GT-I 9000, where someone installed Androd on a partitioned external SD. Is there somebody who knows someboy having heard about somthing similar working with the GT-I9903?
One step forward...
Hello everybody, I finally managed to get some light into my issues as I once again figured out how to get a software installed and running . It's this one:
http://forum.xda-developers.com/showthread.php?t=2329200
Thanks a lot to the guy who just posted it somewhere where id could do good...
By the way, I figured out that this software actually includes the Baseband.
As in this version, the original recovery system is running and giving me an error message when I start it without external SD-card, I am now quite sure that the internal memory has just failed as this error message was specified in another posting of someone who had a similar issue with a GT-I9000.
The biiiig "Outch" is, that I am unable to install any CWM Recovery System with that Baseband..This results in me not being able to upgrade the software to ICS, where - as far as I read some troubleshoot-information - will enable me to mount an additional partition on my SD-Card as Data-Partition which isn't possible yet (i.e.: I can't access my SD for storing data or whatever - it's just specified as "not there").
I tried to install the XXKPE-Baseband to be able to go for KPQ which would enable me to install CWM Recovery. I also installed Bagarias CWM-normalboot-image via Heimdall - but I was unable both to boot the OS and to find any trace of a zip-file on the SD-card.
Edit: I managed to install the right CWM - it's mentioned in the post where I've got the firmware from... now, I only have to figure out how to deal with the fact that "officially" there is no SD-card inserted - or, better, that this SD-card is now flagged as "internal SD" - and how that machine can find the zip-file on it
Thanks for every bit of help with that issue
Try Aroma File Manager with Terminal
For SDCard issue you could probably switch them in vold.fstab in /system/etc
Good Luck !!!
try this- http://forum.xda-developers.com/showthread.php?t=2329200
Just wanted to check peoples thoughts on this. Had a 32GB Sandisk card corrupt (i think) on me the other day. Woke the phone and seen the SD card icon in the task bar as if it had just mounted the SD but it had unmounted it and said that there wasn't one inserted. Have yet to try it in a PC to see what (if any) files I can recover.
The previous night I had made a nandroid backup (Philz touch), there was something not quite right with the file sizes not showing on screen but it seemed to work the second time around. Can't recall if the card was formatted as FAT32 or exFAT, but if FAT32 could one of the nandroid files caused issues if it was over 4GB? Anyway going to see what I can possibly recover and if it can be reformatted again before possibly purchasing a 16GB Samsung card here: (http://www.7dayshop.com/samsung-plus-microsdhc-uhs-1-16gb-memory-card-class-10). Dont mind the smaller size if its more reliable.
gsmyth said:
Just wanted to check peoples thoughts on this. Had a 32GB Sandisk card corrupt (i think) on me the other day. Woke the phone and seen the SD card icon in the task bar as if it had just mounted the SD but it had unmounted it and said that there wasn't one inserted. Have yet to try it in a PC to see what (if any) files I can recover.
The previous night I had made a nandroid backup (Philz touch), there was something not quite right with the file sizes not showing on screen but it seemed to work the second time around. Can't recall if the card was formatted as FAT32 or exFAT, but if FAT32 could one of the nandroid files caused issues if it was over 4GB? Anyway going to see what I can possibly recover and if it can be reformatted again before possibly purchasing a 16GB Samsung card here: (http://www.7dayshop.com/samsung-plus-microsdhc-uhs-1-16gb-memory-card-class-10). Dont mind the smaller size if its more reliable.
Click to expand...
Click to collapse
I quite highly doubt a Samsung SD card will be more reliable. Don't know what's the fuss about SanDisk corrupted but I myself or anyone in my friend/colleague circle have yet to face a problem with SanDisk!
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
jujuburi said:
I quite highly doubt a Samsung SD card will be more reliable. Don't know what's the fuss about SanDisk corrupted but I myself or anyone in my friend/colleague circle have yet to face a problem with SanDisk!
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
Click to expand...
Click to collapse
This is the first problem I've had with it to be honest, had it or over a year and was using it in my HTC Sensation previously. I'm trying to remember if it was exFAT or FAT32, I remember a ROM (Google Edition S4 ROM) not being compatible with exFAT and checking mine out of curiosity, but just can't recall what it was and never flashed the ROM. I didn't reformat it coming from my Sensation so it hadn't changed in anyway.
Luckily all my photos were backed up to dropbox so nothing lost of too much importance. Need to get a microSD card reader to see if its completely borked or if files can be retrieved.
Someone will correct me if I'm wrong but I'm pretty sure that Nandriod breaks the files down smaller than 4GB if you're running on Fat32 so I doubt that'll be your problem. Mostly because the FAT32 architecture just won't accept a file that big unless the Linux kernel of Android ignores the limitations. I would HIGHLY recommend NOT restoring a nandroid backup if you think the sizes are off or if you're attempting to recover the data without and MD5 checksum. That's all sorts of bad juju.
As for Sandisk vs Samsung, I have both, I've never had a problem with either. My sammy card is in my TF201 and my Sandisk is in my I337 as it's a faster card from my benchmarks. But like I said, no problems with either.
As for data recovery, go check out Recuva, it's supposed to be pretty good especially for being free. Since I'm IT I have professional grade software for data recovery and don't have tons experience with Recuva. A couple tips about data recovery. Once you determine you want to recover data, DO NOT WRITE TO OR FORMAT THE CARD, that'll prove to make the entire process more difficult. it's going to take a good long time, at least an hour for the initial scan. Do all the work on the card from a computer and not through a connection to your phone. Anyway if you have any questions or possibly want some help shoot me a PM, I'm happy to impart my knowledge.
Theoriginalgiga said:
Someone will correct me if I'm wrong but I'm pretty sure that Nandriod breaks the files down smaller than 4GB if you're running on Fat32 so I doubt that'll be your problem. Mostly because the FAT32 architecture just won't accept a file that big unless the Linux kernel of Android ignores the limitations. I would HIGHLY recommend NOT restoring a nandroid backup if you think the sizes are off or if you're attempting to recover the data without and MD5 checksum. That's all sorts of bad juju.
As for Sandisk vs Samsung, I have both, I've never had a problem with either. My sammy card is in my TF201 and my Sandisk is in my I337 as it's a faster card from my benchmarks. But like I said, no problems with either.
As for data recovery, go check out Recuva, it's supposed to be pretty good especially for being free. Since I'm IT I have professional grade software for data recovery and don't have tons experience with Recuva. A couple tips about data recovery. Once you determine you want to recover data, DO NOT WRITE TO OR FORMAT THE CARD, that'll prove to make the entire process more difficult. it's going to take a good long time, at least an hour for the initial scan. Do all the work on the card from a computer and not through a connection to your phone. Anyway if you have any questions or possibly want some help shoot me a PM, I'm happy to impart my knowledge.
Click to expand...
Click to collapse
I thought it should break them down, it was just the /data partition that includes the apps and app cache, if it could be over 4GB stored as a .tar file would that still be broken down as such? Won't be attempting to restore the nandroid (if its even still recoverable) as I have flashed a pre-rooted stock odin firmware and its actually really smooth (maybe thats due to the sd card not being inserted). Although I seem to be having an issue flashing a custom ROM, as even after flashing the firmware via odin then trying to flash a ROM via Philz touch its still bootlooping (even with a wipe/factory reset and clean install format). Haven't attempted a different custom ROM but just havent had the time to test that out. Thinking I would have to download the original firmware files and start from scratch with rooting and adding a recovery to see if that solves it, but think I'm going to sit tight for the moment.
Thanks for the recommendation and the support, much appreciated.
gsmyth said:
I thought it should break them down, it was just the /data partition that includes the apps and app cache, if it could be over 4GB stored as a .tar file would that still be broken down as such? Won't be attempting to restore the nandroid (if its even still recoverable) as I have flashed a pre-rooted stock odin firmware and its actually really smooth (maybe thats due to the sd card not being inserted). Although I seem to be having an issue flashing a custom ROM, as even after flashing the firmware via odin then trying to flash a ROM via Philz touch its still bootlooping (even with a wipe/factory reset and clean install format). Haven't attempted a different custom ROM but just havent had the time to test that out. Thinking I would have to download the original firmware files and start from scratch with rooting and adding a recovery to see if that solves it, but think I'm going to sit tight for the moment.
Thanks for the recommendation and the support, much appreciated.
Click to expand...
Click to collapse
Well in general in windows when a FAT32 structure is asked to write a file larger than 4GB it'll flat out deny it (usually saying something like disk is full). If you're writing to a FAT32 structure using something that increments the file as it writes it, when it hits the 4GB file size limit, it'll usually say again disk is full and the file will go corrupt (which can lead to the file being undetectable). I do believe that Nandriod is smart enough to realize when it gets to that 4GB limit it'll break the tar into multiple files or else the linux OS would probably kick back an error. As for your ROM bootloops and things like that, I'd see about another ROM, maaaaybe it could just be that the ROM you flashed doesn't like your phone (I have an i717 that does that with a ROM). If that still doesn't solve it, like you said. Start at the beginning completely clean and just work through the entire process.
Theoriginalgiga said:
Well in general in windows when a FAT32 structure is asked to write a file larger than 4GB it'll flat out deny it (usually saying something like disk is full). If you're writing to a FAT32 structure using something that increments the file as it writes it, when it hits the 4GB file size limit, it'll usually say again disk is full and the file will go corrupt (which can lead to the file being undetectable). I do believe that Nandriod is smart enough to realize when it gets to that 4GB limit it'll break the tar into multiple files or else the linux OS would probably kick back an error. As for your ROM bootloops and things like that, I'd see about another ROM, maaaaybe it could just be that the ROM you flashed doesn't like your phone (I have an i717 that does that with a ROM). If that still doesn't solve it, like you said. Start at the beginning completely clean and just work through the entire process.
Click to expand...
Click to collapse
Cheers, I had re-downloaded the previous version of the ROM which I was on before hand and made sure to check the md5s but it still wouldn't boot which was annoying, but a full install from scratch may be the way to go. Never had bootloops before and was just worried after I had wiped and started a fresh and it still happened. I think the real lesson is to make sure to backup ANYTHING that is of value to you!
Luckily I had just happened to use the auto backup for photos to dropbox so got off lightly this time!
I have had the EXACT same issue 2 weeks ago.
I bought 2 x 32gig microSD cards (Sandisk)
1 for my phone and 1 for my digital camera.
Recently the 32gig one in my phone just DIED for no reason at all. Lost all my files, music, everything.
I contacted Sandisk, had it repalced. In the meanwhile i purchased a 64gig Samsung one.
I am yet to have an issue with the Samsung 64gig, but only time will tell.
On a plus note, Sandisk sent me a replacement 32gig card very quickly (infact too quick, i purchased the 64gig Samsung one on the idea that the Sandisk replacement was going to take months... in fact it only took 6 days...)
Cheers
How did you contact Sandisk, did you need to give a serial number or provide proof of purchase?
Sent from my Nexus 7 using xda app-developers app
jujuburi said:
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
Click to expand...
Click to collapse
I always use Fat32 on SD-cards. Why? It works on every Rom, with every kernel, every recovery, on every device, every camera, every computer, all the time.
When not in need of files greater than 4GB Fat32 simply is the way to go, compatibilty-wise.
gsmyth said:
How did you contact Sandisk, did you need to give a serial number or provide proof of purchase?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Tried the card in a reader connected to my laptop but nothing. I've emailed Sandisk support so will see what they say.
Sent from my GT-I9505 using xda app-developers app