Related
I have a couple problems that I've been having since rooting my phone and installing cyanogen. I'm currently using cyanogenmod 4.2.2 with recovery 1.4 on my t-mobile g1. Also, I have the CM updater.
1. When I am using my stock headset, the phone restarts automatically at random intervals. Also, when the headphones are plugged in when the phone initially starts, the phone will definitely restart shortly after the home screen finishes loading.
2. When I am listening to music through the stock headset (either through the base music app or pandora) and I receive a call or text message, I lose all sound functionality (including in-call sounds) When this happens I have to unplug my phone and restart it again to regain sound functionality.
Are these bugs with the following that others are experiencing that can't be avoided:
1. cyanogenmod or
2. root or
3. cyanogen recovery 1.4?
Am I the only one that has had these problems? Is there another ROM that anyone would recommend that would most likely rectify this?
Help!!!!
I have the same problem.
No idea how to fix it?
G1
CyanogenMod 4.2.2
I think I fixed my own problem
I flashed this new radio:
http://sapphire-port-dream.googlecode.com/files/ota-radio-2_22_19_26I.zip
Then I backed up my sd card, formatted it, and partitioned it into a main fat32 partition and a 500mb ex2 partition.
Then I wiped and re-flashed cyanogen 4.2.2 and it works!!!
Also, it took me a while to figure out how to partition my sd card. It seems there is no easy way to do this with windows vista. I had to use Ubuntu's partition manager called "gparted". Apparently this can be done without actually installing Ubuntu if you just boot from the CD, but my computer wouldn't read the sd card through Ubuntu until I installed ubuntu and downloaded the updates. Then when I was done I tried to delete the Ubuntu partition (VERY BAD IDEA). Now my computer won't boot at all and I have to find a way to re-write my master boot record (MBR) which I don't know how to do. CRAP!!!
anoyment
ajchandler said:
Also, it took me a while to figure out how to partition my sd card. It seems there is no easy way to do this with windows vista. I had to use Ubuntu's partition manager called "gparted". Apparently this can be done without actually installing Ubuntu if you just boot from the CD, but my computer wouldn't read the sd card through Ubuntu until I installed ubuntu and downloaded the updates. Then when I was done I tried to delete the Ubuntu partition (VERY BAD IDEA). Now my computer won't boot at all and I have to find a way to re-write my master boot record (MBR) which I don't know how to do. CRAP!!!
Click to expand...
Click to collapse
Dude, take your HDD out of the computer, put it inside a USB enclosure and save your data, then just delete all partitions and install Windows again. Next time, you can just install Ubuntu from INSIDE Windows with "wubi.exe".
As for the sporadic resets, I am having the same problem. Only thing is: I had just flashed the 4.2.2 rom in the phone, wiped, and just then, being in the WC, I get a call, take the phone out of my pocket, it slips from my hand and drops right inside the can (yes, it had just been cleaned, Thank God), took it out fast enough, battery out. Couldn't find the screwdriver for it so I shook as much water as I could off, and let it dry in front of a full throttle fan for about 12 hrs.
It reset itself some times after that, but I don't know if the problem is the Rom, hope it is, (sorry). Next thing I know is, there's an update to ver. 4.2.5, so I updated, hasn't done it again yet, it's been 36hrs.
Hope I could help and anoy you some guys...
I have the same problem with my G1 (cyanogenMod-4.2.5 kernel 2.6.29.6-cm42 baseband 62.505.20.17H_2.22.19.26I), had to change from cyanogenMod-3.6.6 hoping it will fix the reboot problem, but it doesn't change
I reformat SD card (1 Gb) and repartitioned it, doesn't fix the problem. The difference is that is reboots now less frequently (with cyanogenMod-3.6.6 it started reboot suddenly and did it every 20min - 3 hrs, now 1-3 times a day).
Seems that it somehow related to WiFi connection, and may be email receiving process (may be free space problem? But as far as i can check there is free space available on the SD card).
If with cyanogenMod-3.6.6 i could assume that some new installed application caused it, then with 4.2.5 i didn't install anything, and it starts rebooting again recently.
Is there a way to write a log or something to see which app caused reboot? It's linux anyway, so should be smth to see the reason, right?
Updated to CM-4.2.7.1 and added a 4GB Class 6 TF
luk1 said:
I have the same problem with my G1 (cyanogenMod-4.2.5 kernel 2.6.29.6-cm42 baseband 62.505.20.17H_2.22.19.26I), had to change from cyanogenMod-3.6.6 hoping it will fix the reboot problem, but it doesn't change
I reformat SD card (1 Gb) and repartitioned it, doesn't fix the problem. The difference is that is reboots now less frequently (with cyanogenMod-3.6.6 it started reboot suddenly and did it every 20min - 3 hrs, now 1-3 times a day).
Seems that it somehow related to WiFi connection, and may be email receiving process (may be free space problem? But as far as i can check there is free space available on the SD card).
If with cyanogenMod-3.6.6 i could assume that some new installed application caused it, then with 4.2.5 i didn't install anything, and it starts rebooting again recently.
Is there a way to write a log or something to see which app caused reboot? It's linux anyway, so should be smth to see the reason, right?
Click to expand...
Click to collapse
LUKE, I AM YOUR FATHER, NOT...
Just kidding, just couldn't let a chance like this pass me by, sorry .
2 days ago I changed the 2GB TF (which was a class 1) with a 4GB TF, now a class 6. Wiped the phone and added an ext3 1GB partition.
Yesterday I updated the CYanogen Mod to ver 4.2.7.1. Haven't seen another reset since, but it could be that I haven't used the phone much other than for phone calls since the update. But altogether it seems pretty stable.
I just used the cm-updater and everything was done automatically.
If you don't already have it, download it from the market, check for new roms and download the one I said. Please let us know if it makes any difference for you.
ajchandler said:
Then when I was done I tried to delete the Ubuntu partition (VERY BAD IDEA). Now my computer won't boot at all and I have to find a way to re-write my master boot record (MBR) which I don't know how to do. CRAP!!!
Click to expand...
Click to collapse
To reinstall the Vista MBR:
http://support.microsoft.com/kb/927392/en-us
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.
Hi folks!
Sorry I'm posting this here, as I only found out after registration that for the first 10 posts I'm not allowed to post to the original Encryption Unsuccessful thread.
So here is my story about my SGS, Gingerbread, ICS, the Encryption Unsuccessful message and Jelly Bean – maybe this is of some help.
First of all my conclusion (for those who want to know more – read the story after conclusion). Note that this refers to SGS – I don’t know about other devices. The Encryption Unsuccessful message appears on ICS when the /data partition fails (can’t be mounted / accessed anymore – hardware issue). Other partitions may be failing, too. The failure may happen both after cold start of the device and suddenly while running. In the latter case, you may also get this message on Jelly Bean. BUT: If vital partitions fail at cold start of the device, Jelly Bean would not start booting until Encryption Unsuccessful message. Instead, it starts recovery mode. From there it may help to select restart of device – at least for me, after a few attempts, Jelly Bean starts normally (because finally the partition(s) could be mounted). If mounting of partitions fails on Gingerbread at cold start, Gingerbread keeps restarting the device (instead of entering recovery mode) until the partitions could be mounted successfully – and then Gingerbread starts normally. However, if partition(s) fail while Gingerbread is already running, system may hang or slow down (can’t say because it never happened to me).
Solutions I can think of:
1) Patch ICS to also enter recovery mode instead of booting if vital partitions could not be mounted. This way it behaves like Jelly Bean and at least doesn’t throw the Encryption Unsuccessful message after cold start (which – at least for me – is the only situation in which I get that message). Maybe one could even patch ICS / Jelly Bean to enter a boot loop like Gingerbread until the partition(s) could be mounted. This is – of course – not a real solution, because sooner or later the internal memory may fail completely. Especially because of the risk of data loss, solution 2) is to be preferred (but more difficult).
2) Somehow manage not to use the internal memory (at least not the failing parts of it). That means everything – apart from the /boot partition, which doesn’t seem to be affected – should be located on an external micro SD card. The problem: It’s not enough to swap mounting of internal and external SD card by changing the vold.fstab file. At least for me, during installation of Jelly Bean, vital partitions were still created on the internal memory. But maybe I did something wrong? It looks like if the internal memory is *completely* failing (so unlike my case), this may however work – see youtube -> watch?v=zdMhYYdMB08
If anyone knows how to make Android boot from external micro SD card – please let us know.
The story:
About half a year ago, my SGS (Gingerbread) suddenly went into a boot loop when I switched it on. After several attempts (reinsert battery etc.), it worked again. By time this and that wasn’t working properly anymore – settings gone, apps crashing, lags… As restarts didn’t help, I decided to flash ICS. This has worked until a few weeks ago. The battery went down and after the device switched itself off automatically, I inserted another battery, tried to start – and: Encryption Unsuccessful message. I thought maybe it didn’t properly switch itself off so that the internal memory didn’t get enough power and, consequently, data got corrupted. So I flashed ICS again. 3 days later, after I had turned the SGS off for about 2 hours, I got Encryption Unsuccessful message again. As I read that maybe only one person so far experienced that message on Jelly Bean, I flashed that one. Worked fine the first few hours, but then after device was switched off again for some time, it went to recovery mode at startup. Only after some restarts it finally booted Jelly Bean (which was then running without problems). At this point I was convinced that it’s a hardware issue (failure of internal memory). As warranty was still valid, I decided to flash stock ROM (Gingerbread) and updated it to 2.3.6 via Samsung Kies (as earlier, it went into a boot loop after cold start) and sent it to Samsung service (a company called w-support was supposed to repair the device). They only replaced the LCD (for whatever reason) and applied a software update. When I got it back, as expected, symptoms had not changed. The thought of sending it in again without a replacement of internal memory or mainboard really frustrated me. So I tried to make Jelly Bean use an external micro SD card instead of the internal by changing vold.fstab. It worked with respect to swapping USB memory and external memory. But it didn’t make Jelly Bean install on the external micro SD card. And that’s where I am now. I would love to get all the vital partitions installed on the external card – but that doesn’t happen. Anyone has any advice? I tried to do it the way described in the youtube video (see above), except that I didn’t want to install Linux just for repartitioning the micro SD card. So I used SD Formatter and MiniTool Partition Wizard Home Edition. I would have preferred to partition the external SD card using CWM, but V3.0.0.5 seems to be somehow buggy – it got that option, and within a second it says “done”, but nothing has happened to the external SD card.
Has anyone managed to install ICS or Jelly Bean on an external SD card?
Thanks a lot in advance!
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
This all happened a long time ago, but I have these 2 lexar 128gb micro sd cards that are read only, everything I have thrown at them, windows, mac, android, it says read only, I'm about to throw them out but just wanted one last question about them specific to Android.
The chain of events I believe was, I put them in an ulefone paris (2015) chinese phone, before I rooted, it had some tweaks/malware garbage on the os, I tried to format as internal, it did something I didn't like, or it didn't work, but for whatever reason I took out, now they are unusable, read only. Later I rooted and put in regular android.
Can't format or do anything with them, tried windows, mac, official sd formatter, command line, all the usual tips but they give read only error and won't budge but they infuriatingly mount fine and show a bunch of android junk files (stuff that was on my phone Ig uess) everytime I plug in to my mac, but if I delete they come right back (makes sense because they're read only), I tried putting them back in the phone but since it's been rooted to normal marshmallow (I think I don't use it much), it too gave errors.
There is no adapter switch lock or anything, I plug them in through the usb device that came with them, although I have tried adapters set to unlock, and it didn't work.
Could the phone really have destroyed them both, they were brand new (way too old for any refund), I'm going to throw out but just wanted confirmation the phone wrecked them.
Try formatting the card with a different fille format like , ex4 or other, then rewert back to stock threw twrp of some windows formatting tool (freeware)
Goodluck
Sent from my HYPER using Tapatalk
2ISAB said:
Try formatting the card with a different fille format like , ex4 or other, then rewert back to stock threw twrp of some windows formatting tool (freeware)
Goodluck
Sent from my HYPER using Tapatalk
Click to expand...
Click to collapse
I only have a mac right now, but I'll try format to ext4, didn't try that.