I've had a Gtab for a few days and tried TNT 4.4 and now Vegan 5.1, and in both ROMs, my tab keeps freezing. It often freezes on Gallery, but it has frozen elsewhere. I've tried wiping it with clockwork, but the problem wont go away. Any ideas? Any other way of reformatting the drive or anything else?
Since you're familiar with clockworkmod, you could try to re-partition the internal sd to 2048 and 0. WARNING: this will format your device and delete everything on the user partition (what's called "sdcard" in these ROM's), back up all data externally (micro sd or usb flash or pc) or it will be gone!!!
This is a common fix for force close across platforms.
Be Sure To BACKUP Important Data to something other than the Internal Device's 16 GB flash memory.
I would also re-flash whatever ROM you want after the re-partition.
There is also a "format all" procedure from Calkulin in one of his threads in development forum.
Edit: There's a couple of format procedures in the development forum, one uses nvflash (sticky) and Calkulin's looks to be .zip. I haven't used either of these, but I would be familiar with nvflash/apx and have that set-up before attempting either.
Related
My Vibrant's internal sdcard was reporting corruption, so I put a fresh ROM (Macnut 12) on the external SD, rebooted into Clockwork, and formatted the SDcard, system & data partitions. Then went to install the ROM, but it turned out it wouldn't recognize the ext-sd card either! I get this error when i try to mount:
Code:
E:INFO is WRONGError mounting SDEXT:!
I've tried a different ext-sd, and even tried formatting that one on the computer (MBR partition scheme, FAT partition). Nothing is recognized by the phone.
Also when I try "mount USB storage" nothing shows up on my desktop either.
SO: I have an almost empty phone, and no way of putting any ROM whatsoever on there. Can anyone point me in the right direction?
note: i have a Mac, so AFAIK ODIN doesn't work for me.
I'm in "Clockwork 2.5.1.0 lagfix edition", and was previously rocking Eugene's Macnut R12 with the JFS+RFS lagfix.
thanks!
~peter in oakland
wrong section
huzzam said:
NOTE: I figured this out, don't bother replying! thanks for looking
My Vibrant's internal sdcard was reporting corruption, so I put a fresh ROM (Macnut 12) on the external SD, rebooted into Clockwork, and formatted the SDcard, system & data partitions. Then went to install the ROM, but it turned out it wouldn't recognize the ext-sd card either! I get this error when i try to mount:
Code:
E:INFO is WRONGError mounting SDEXT:!
I've tried a different ext-sd, and even tried formatting that one on the computer (MBR partition scheme, FAT partition). Nothing is recognized by the phone.
Also when I try "mount USB storage" nothing shows up on my desktop either.
SO: I have an almost empty phone, and no way of putting any ROM whatsoever on there. Can anyone point me in the right direction?
note: i have a Mac, so AFAIK ODIN doesn't work for me.
I'm in "Clockwork 2.5.1.0 lagfix edition", and was previously rocking Eugene's Macnut R12 with the JFS+RFS lagfix.
EDIT: "adb push" has saved the day!
thanks!
~peter in oakland
Click to expand...
Click to collapse
I also use a mac. You need to be careful how you delete and format your sd cards. I just deleted some stuff off my sd card by dragging it into the trash and it didnt free up any space on the sd card. I have also seen problems with formatting them with the mac also. Also ODIN is a great way to put things back to stock. you will need to use bootcamp to install windows on the partition. If I weere you I would still ODIN back to stock and reflash to make sure you dont have errors in the future
Format sd card through clockworkmod recovery. Itll wipe everything, but it should bring it back to being usable. Also heimdall works with mac right? I havent used heimdall but read its an open source rom flasher replacement for odin.
Sent from my SGH-T959 using XDA App
I was going to suggest Heimdall as well. You should be able to flash back to a stock firmware, then sort things out from there. If you want to do that and then report back here, we could help from there.
Information about Heimdall is available in this thread along with a link to download the program.
Good luck.
Hi everyone,
In my overzealous attempts to reformat an old 4gb external SD card through CW Recovery, I managed to reformat my internal SD card (I was using the Clockwork Recovery version 2.5). I thought that "format sd card" would reformat my external memory card and not leave me without a usable phone, but I guess I misunderstood.
I spent at least five hours going through all of the ODIN tutorials and trying them out, and found that using Eugene's 2.2 with 2E recovery ROM actually allows me to boot up (hooray! ), while the stock rom from this thread simply forces a bootloop on my poor phone, with occasional freezes. Even using AIO's "Flash to Stock" from Eugene's 2.2 doesn't work.
Further searching has lead to the thread about partitioning using parted, which has been hard for me to use effectively (I made a new partition, but I couldn't get it to mount properly).
I was really excited to come across this tutorial, but it didn't solve my problem. After getting through all of the steps, at step 5, ODIN3 versions 1.0, 1.7, and 1.81 (I tried all 3 on 3 different walk-throughs of the tutorial) never were actually capable of repartitioning the sdcard properly. Every time after the first time of using "parted" to reduce the card to a single partition, I found that that lone partition was always the only one there (15.5 gb /SYSTEM Fat32). No changes had been made to the sd card's partitions.
I don't know if it helps any, but the ROM I was running before I reformatted the card was Bi-Winning 3.0, and Voodoo had not been disabled at the time of the reformat, which may be why I can't flash new ROMs through the recovery as well.
As near as I can tell, ODIN can't actually return my vibrant's partitions to factory settings, so is there a way for me to do that manually? I think that would solve my problem.
Thanks,
-NewbieCube
My guide (you linked to) clearly states its not for this intent... if you read it, you would also see I linked to Eugenes froyo that does not brick. If you did it, THEN you did my guide ODIN to JFD, you are on a fully functional stock 2.1 JFD build.
If your intent was to just format the external sd, go to menu settings, sd card/phone storage, unmount the external and format it.
Right, I know that. In fact I read all through your thread and tried to flash to Eugene's first, and then to JFD, but JFD does not boot properly. It just gives me a black, unresponsive screen. I'll definitely go back through once more and try that again, though, as you clearly know what you're talking about.
I basically formatted the wrong storage (internal sd vs external sd), and would like to get that internal back to stock, so you are right that Eugenes -> JFD should work. I'll report back with results.
^ yeah, exactly... that should work with no issues. let me know if it does not.
Oddly enough, that didn't work for me either. Since my phone still can boot into Eugene's (albeit with 0.00B available to apps), I know this should work, just from reading through your guide. So once more, here's what I did:
1. Download mode -> ODIN 1.70: Flash Eugene_2E_JK2_Froyo.tar.md5, and s1_odin_20100512.pit (from Eugene) Re-Partition NOT checked (Eugene's thread says not to)
2. Boot up into Unbrickable Froyo, with no application space remaining Mount sdcard and move Update.zip (s15274n's) into the root folder without issue.
3. Download mode -> ODIN 1.70: Flash s1_odin_20100512.pit, and T959UVJFD.tar (s15274n's) with Re-Partition checked
4. Boots once automatically into recovery, saying something about a failed MBR checksum and failure to clear userdata
5. Bootloops that never get past the VIBRANT logo screen
6. Boot into recovery and try deleting user data and cache data manually and to reinstall packages, but bootloops continue.
I really don't know what I'm doing wrong here...
UPDATE:
I even used Heimdall on another computer and got the same result, so it isn't ODIN. Why is reformatting the internal SD card to stock so difficult to do?
delete my post
I FIGURED IT OUT!!! ...by random chance
For my problem, it was indeed the voodoo lagfix that was messing things up, and this post:
http://forum.xda-developers.com/showthread.php?t=888084
helped me out tremendously.
I am running into SD card mounting problems on MIUI. After I load the rom, everything works fine for a while. Then the SD card will show up as having been ejected. I remove and replace the card, and if it is read at all, it's read as blank or damaged. It reads fine both on a computer and on this phone running other roms. What's even weirder is that, although the card reads fine on CWM at first, once I start having problems with it in the ROM, it won't mount in CWM either.
I have reloaded the rom three times now. First time was from DL09 stock, second time from EB01 stock, last time from CM7. Both times I went to stock I used the instructions from development (atlas.pit, repartition). All times I wiped cache, data, dalvik. I've flashed both from CWM4 and CWM3. I've used two different SD cards (both sandisk, a 2g and 32g) I've tried wiping and formatting the cards, both on the phone and on the computer. I've tried battery pulls and reboots. I've tried both cards. I've tried restoring apps from Titanium (just apps, no data) as well as fresh from the market.
From where I am now (card never mounts on ROM or on CWM, even if blank and freshly formatted), the only thing that has worked in the past is to go back to stock and reflash the ROM. But that doesn't seem to be a long term fix, because each of the three times I've done it, the problem just returns, and I can't identify anything I'm doing wrong. I haven't had problems with CM7 or comrom, but I really want to make MIUI work! Help!
I am curious as well about SD issues on AOSP in general. I was having the same issues on CM7 then shortly after it started I lost roughly 5 gig of data off my card, including all my pics. I was able to recover the pics with Recuva but I am still wondering why.
I remember reading a short blurb about this some weeks ago but haven't been able to find it again.
Hi all,
I searched long and hard for an answer to this one, but I can't make heads or tails of it. It started when I noticed that any apps I installed wouldn't stay through reboots, and any uninstalled apps came right back. So I tried reflashing Flashback 7.0 and 7.2, but the apps were still there. It does look like 7.2 installed correctly, although the apps were still there.
Then I tried flashing several different roms (TnT, Cyanogen, Vegantab, stock), but they wouldn't boot. Flashing back to Flashback allowed the tablet to boot, but the data was still there.
I tried manually formatting /data through cwm, but I got the lovely "Error formatting /data" message. Doing the normal cwm data wipe and repartition (4096,0 and 2048,0) didn't do anything either. I tried NVFlashing back to stock 4349, no good. I tried Flashback loaded with cwm 3.0.2.8 and the stock 1.2 recovery, but no avail. I blew away the partition table and nvflashed, no good. I tried pulling the battery, no good. I tried flashing the FORMAT utility, still stuck with this data. No matter what I do, it will only boot after installing Flashback 7, and then it retains the state it was in before going wonky.
The tablet works more-or-less for every app currently installed, apps load fine, all hardware appears to work fine, but once it's rebooted everything goes back to how it was when it went belly-up.
This has gotten the better of me, I'm hoping there's some nuance that you brilliant folk know of that I'm missing. Thank you for your time.
Both /data & /sdcard reside on the internal sd and are not touched by nvflash or by installing a new rom (all of which go on the internal nand (not sdcard). There are serveral ways to clear them. You can clear /data by doing a "factory/data reset" & repartitioning in CWM wll destroy/recreate both /data & /sdcard (so make sure you backup anything you want to save on /sdcard before you repartition). The standard repartition is 2048,0, but in some situations it is benefitial to repartition to 4096, 0 & then immediately repartition back to 2048,0.
After installing a new rom you should always do a factory/data reset, wipe cache & wipe dalvik to clear out data/installs from the prior rom.
Al
Thanks Al,
I forgot to mention, I've already repartitioned several different times, going up to 4096,0 then down to 2048,0 as I've seen recommended elsewhere. The wipe data/factory reset option also doesn't seem to be affecting the data staying put.
I remember a person with a similar situation. I believe rajeevvp had the person do some testng & it came out (in that case) to be a bad internal sd. He developed a way to use the external sdcard as the internal sd. I'll see if I can find the post or you can PM him.
Al
See this post http://forum.xda-developers.com/showthread.php?t=1156200 and specifically post #44 Guide to swap internal and external SD card assignments on the ViewSonic gTablet for users with partly-functional internal SD cards.
Al
Looks like the same issue all around. Thank a million, here's to hoping it works.
Get me a dmesg output first.
Second, since you're on the 1.2 bootloader branch, don't flash the custom CWM zip file which is only for bl 1.1. Just skip that step (step 1). The rest of the steps are bootloader-independent. Step 1. is only for letting you make backups and restores using the external SD card instead of the internal one.
Third, I'd like to see the results of the test commands given in the thread that aabbondanza posted above.
Finally, for CWM 3.x and higher, I have another (and easier) technique that I think will work for backups and restores, but, I never tested as I didn't want to change bootloaders. Let me know if you're willing to be a guinea pig for testing this.
rajeevvp, the result of the test directory/file creation on /data and /sdcard were similar to the other poster, with the directories and files not being retained after unmount or reboot.
The results of the test commands are attached. Thanks again for all your help. Additionally, of course I'm willing to be a guinea pig for anything you've got in mind.
sktsswth said:
rajeevvp, the result of the test directory/file creation on /data and /sdcard were similar to the other poster, with the directories and files not being retained after unmount or reboot.
Click to expand...
Click to collapse
From the dmesg1.txt file I see that you have the non-standard internal SD card make that seems to cause this sort of problem:
<6>[ 10.001007] mmc2: new high speed SDHC card at address aaaa
<6>[ 10.007139] mmcblk3: mmc2:aaaa SE16G 14.8 GiB
<6>[ 10.011722] mmcblk3: p1 p2
Click to expand...
Click to collapse
You can either return the tablet to VS or try my workaround hack along with a new CWM for 1.2-based bootloaders (soon).
Either way, I'd like to continue this discussion further in this thread.
rajeevvp said:
From the dmesg1.txt file I see that you have the non-standard internal SD card make that seems to cause this sort of problem:
You can either return the tablet to VS or try my workaround hack along with a new CWM for 1.2-based bootloaders (soon).
Either way, I'd like to continue this discussion further in this thread.
Click to expand...
Click to collapse
Since some of these tablets are showing up with different internal sd cards than most of us, is it possible that when we are having these people nvflash back to stock, that the bct's config of these new chips would be different & we are causing the problem by flashing the incorrect bct back to the device? Would it be safer to modify our nvflashes to read & use the user's bct when nvflashing back to stock?
First off, I am no expert so please be gentle! I previously rooted my old Samsung Galaxy S i9000 and installed ICS, which went OK, but the phone became quite slow and unstable. I was advised to install RemICS and downloaded all the zip files from this forum, and put them on the external SD card. I followed the developer's instructions to the letter, as well as reading everything I could find on the subject. The reset and data wiping went fine, but the installation of the ROM didn't. It halted with an error message -`ROM incompatible, trying to use an invalid partition'. I repeat that this is supposed to be the specific ROM for the i9000. The phone now won't boot into recovery. It stops with an orange Android logo and the text `Powered by Mackay Kernel'. It won't boot into download mode either. The Mackay screen stays there however long I leave it. I really need help from the ROM developer but I can't post to that forum. How can I either boot into recovery or into download mode? Is this ROM reliable? What could I have done wrong?
More info:
Presumably everyone is on holiday! But just in case anyone is reading, there is further news. The reason I could not start recovery mode was that the button sequence was different from what I had been told. It now boots reliably into Mackay (which of course is TWRP). I have found that the phone is unable to mount the partitions DATA and SYSTEM - they seem to be corrupted. Hence it has not wiped DATA, although TWRP wrongly reports success. I have tried updating the partitions to ext3 or ext4 but this fails every time. I could format the thing from Windows but that will wipe everything including recovery of course. I need a tool to repair these partitions, but have not found anything so far. This may well have been the reason the phone was getting creaky in the first place.
I have copied a new ROM to the external SD card, using a card reader, and inserted this into the phone. Strangely the TWRP file manager reports that EXTERNAL SD is a sub-folder of SD CARD, and that is empty. The file manager does not show the real external SD card. But the real external SD shows up on the Windows USB connection. What is going on?
When I try to mount the partitions, DATA and SYSTEM can't be checked - the other partitions (Cache, sdcard, and emmc are all checked).
kingGrn Copeland
Well for the benefit of anyone else with the same problem, I have managed to re-flash the ROM back to stock. It just took 3 days of intensive web browsing until I understood how to do it, and found software that worked - a lot of stuff out there has errors.
To summarise, the problem was:
1. Data and System partitions became damaged, so phone became unstable.
2. Attempt to upgrade ROM failed because of damaged partitions.
3. Could not boot phone into recovery or download because button combination was different from what I was told.
The solution was:
4. Boot into download mode using correct button combination.
5. Re-flash back to stock ROM and re-partition using Odin.
Yes, someone did tell me that, and I would have done that straight away if I could have gotten into download mode. We live and learn
The solution was:
4. Boot into download mode using correct button combination.
5. Re-flash back to stock ROM and re-partition using Odin.
Click to expand...
Click to collapse
Thanks this wa useful for me too.