Hi all ! I have a bit of a problem...My internal sd is kinda blocked in a "read" state. Neither the (rooted) system, me, odin, nor windows can write or delete anything. When I flash a new rom or a new recovery, it looks like it succeed, but when the tablet restarts it's at the same state as it was at a t instant. This means I'm blocked on Philz 6.0.x and Slimkat with a few apps and pictures. As the system can't write, the tablet freezes and reboots after a few minutes of usage. I've tried tens of methods trying to reinitialize the rom or flashing a new rom, I've even tried a Nand erase all, flashing a pit file, but whatever I do, it's stuck on the same rom with the same apps. Wipes are shown as successful but actually wipe nothing... It looks like the internal sd is dead. Note that I've formated and pulled out the external sd so the problem doesn't come from it. Has anyone faced once such an issue ?
Sorry for my english...
Related
Hey everyone,
So I got my tablet today and have been working on it for the past 8 hours!! I finally got CWmod on it and running. Had a nightmare of a time getting it to work correctly and after using NVFLASH to nuke the whole tablet and install the stock ROM, then updating i was able to get CWmod to run. Now I'm having a really odd issue.
I can boot into CWmod. I repartitioned the SD card, mounted it. I can see the device in windows but when I add ANYTHING to the internal SD card it is completely gone once I reboot the device. I'm trying to get a ROM on it but it's like the drive is locked or something really weird. It copys onto the tablet just fine. the second I reboot everything is deleted.
I feel like I'm missing something here. I had that issue with it when I ran the stock ROM. I could change something and it would not stick after a reboot. For example registering my device on kindle and then downloading books. as soon as I reboot the machine it's as if i never registered it. I'm really at a loss as to what to do with this. I can't seem to get it to save anything on the internal storage.
Well after fiddling with it for a while longer I'm about to give up. I used NVFLASH to get it to the stock ROM again. updated to 3588 and yet again, I can't get any changes to stick. I can change anything and everything on it while it's powered on. The second I power it off and reboot it nukes everything I did (and takes close to 5-6 minutes to boot). I even mounted it and deleted every single file on the internal storage. They all came back upon reboot. I reformatted the entire SDCARD, I reformatted all the user data, did a cache wipe.. nothing works. I'm wondering if my unit is defective? at this point I would love to just have a tablet that I can actually use. I can't understand how it's even possible to not be able to make any changes on the device unless it's reinstalling the ROM everytime I reboot?
What version of CWM are you using and how did you install it?
I was running CWM 8. I couldn't install it via the internal storage. It would boot into recovery mode and "install" but once the machine rebooted it would not boot into CWM. I tried it several times same deal. I could install it but once it rebooted, nothing :/..
So I had to use the micro SD card to install it. I edited the recovery command file and pointed it to the SDCARD2. It installed finally, and stuck!
I tried using the microSD card to install the other ROMs. But unfortunately it will not mount in CWM.
I'm trying to get CWM back on it after doing yet another wipe with NVFLASH. We'll see if I can get it to work..
So i'm basically sitting here with a brick.. unless I never power it off lol!
Ok well another odd thing is going on with this. I'm up and running with CWM 08 again. I can turn on USB mass storage mount. The tablet shows up in windows and on my linux box. I can make whatever changes I want, adding files, deleting everything on it. Nothing matters cause once I unmount and remount the device it's all back to normal. It seems like nothing is allowed to write to the internal storage even though it thinks it does write to it??
Im having real problems with my Nexus S on 2.3.4 rooted
When I start it up I just get constant force close messages from a load of apps, including system apps. I cant use the phone at all because everything crashes. I've not really made any changes apart from manually flashing the 2.3.4 update and thats been running stable for about a week
I figured I would try and flash a new ROM and/or go back to stock 2.3.1 ROM which I found in the forums here to fix it but whatever I save to my SD Card does not appear in clockwork recovery when I select "Install from zip"
I then tried to copy the ROM again which was showing on the phone through windows explorer, then when I unplugged the cable and plugged it back in, the file had disappeared and any files/folders I created on the SD Card have gone.
Any help would be much appreciated
edit*
All of the apps crashing seem to complain about the database. Im getting SQLiteExceptions from everything, either unable to find file or cannot write to a read-only database
I've tried to lock/unlock the boot loader, wipe everything via recovery (clockwork and stock) and factory resets but everytime i restart, its always the same as if i haven't wiped and the errors keep on coming
grateful for any help
i think these problems are all linked to being unable to save to the sdcard/internal storage. Is there a way to flash a rom without using the internal storage? say have it linked to the PC and do it from there?
So I have had CM10 on my phone for probably 8 months now (almost since I got the phone) and have had no issues with the ROM whatsoever.
I got a notification about an updated version of CM10 today and went ahead and downloaded and installed it, but when I finished the update, I had no personal data left on the phone, could not set up accounts to recover the data, could not (and still can't) recover backups through ROM Manager, and cannot recover backups through CWM. I get an error message which I can't remember at the moment and leads to a bricked phone upon reboot until I do a fresh install of CM10.0.
I read after I started having the issues that I wasn't supposed to directly upgrade from the CM Updater with an S3, but it was already too late. Supposedly the issue is something along the lines of an emulated version of my phone's internal storage? If that makes sense. So whenever it's pulling a piece of information it's looking in the spot it should be in, but on a non-physically-existent SD card, essentially. That's what I gathered anyways.
I have a 32gb external SD Card that is also in use with my S3. I have tried moving my ROM Backups to there and recovering from the External SD Card, but the same error message occurred, although ROM Manager was at least able to find the backups after they were moved (I also had to change the setting and request that it prefer to look through an external SD Card).
So I have a usable ROM as far as the software itself, but I no longer can use any accounts or information that is stored with them or any of the same widgets (not a game-breaker) as I was able to previously. Is there a way to fix this? I've never just been completely stuck before >.<
jkremis said:
So I have had CM10 on my phone for probably 8 months now (almost since I got the phone) and have had no issues with the ROM whatsoever.
I got a notification about an updated version of CM10 today and went ahead and downloaded and installed it, but when I finished the update, I had no personal data left on the phone, could not set up accounts to recover the data, could not (and still can't) recover backups through ROM Manager, and cannot recover backups through CWM. I get an error message which I can't remember at the moment and leads to a bricked phone upon reboot until I do a fresh install of CM10.0.
I read after I started having the issues that I wasn't supposed to directly upgrade from the CM Updater with an S3, but it was already too late. Supposedly the issue is something along the lines of an emulated version of my phone's internal storage? If that makes sense. So whenever it's pulling a piece of information it's looking in the spot it should be in, but on a non-physically-existent SD card, essentially. That's what I gathered anyways.
I have a 32gb external SD Card that is also in use with my S3. I have tried moving my ROM Backups to there and recovering from the External SD Card, but the same error message occurred, although ROM Manager was at least able to find the backups after they were moved (I also had to change the setting and request that it prefer to look through an external SD Card).
So I have a usable ROM as far as the software itself, but I no longer can use any accounts or information that is stored with them or any of the same widgets (not a game-breaker) as I was able to previously. Is there a way to fix this? I've never just been completely stuck before >.<
Click to expand...
Click to collapse
HY, try to flash cm again from theyre website (dont update it), but this time,erase cache 3 times with the command;fastboot erase cache,this may solve your problem.IF I HELPED PLEASE PRESS THANKS!!!!
johnyvlad said:
HY, try to flash cm again from theyre website (dont update it), but this time,erase cache 3 times with the command;fastboot erase cache,this may solve your problem.IF I HELPED PLEASE PRESS THANKS!!!!
Click to expand...
Click to collapse
Just to be clear, you're saying to try and flash CM10.0 and then do not update when prompted from the notification? The other part was clear enough lol.
Edit: Tried the above and did not fix the problem, but I didn't use fastboot specifically because I have a Samsung phone.
The error I'm getting is "unable to mount /system" when I try and restore a backup.
Bump. Still haven't figured this out.
Problem solved.
Re-flashed CM10.1; doing full data, cache, and dalvik wipes before and after the flash; and the problem was corrected.
I wiped everything on my wife's phone in recovery, including internal sdcard, and flashed BeanStalk from external sdcard. It experienced a lot of sudden reboots in seemingly any situation--updating apps, recording video, answering a call, or even just waking. I wiped and flashed again later with the same results. I didn't have time to learn how to log with ADB, so I just went with a different ROM (Dirty Unicorns) to try to get her a stable phone ASAP and it's been completely stable. The only thing I did differently was, instead of wiping the sdcard in Recovery before flash, I erased it with BeanStalk before going into recovery.
I'm wondering if it's possible the internal sdcard partition wasn't set up right the first time since I just did a wipe?
Now that, I think about it, I didn't check the BS's md5 once it was on the card since the phone's USB connection is limited to MTP. Later with DU, I had the idea to put the card in a USB card reader and check md5 that way. So there's a chance the BS zip might have been broken.
Ok heres the story (its not too long don't worry)-
But I URGENTLY need help to fix it please please.
I have an LG GT 540.
I got it 2months ago, and it came as factory standard, and on LG's android 1.6 operating system (so unusable basically).
Over the 2months I managed to upgrade it to a Cyanogen 4.2.1 custom rom, managed to learn how to partition my SD card into fat32 & ext2 and then installed Mounts2sd and used it to freeup space on phone.
(The phone comes with only 138mb storage, so is unusable without mounts2sd quite simply).
The phone was constantly freezingup everytime I tried to load any app ever,
but after clicking the 'Fix Permissions' tab in the recovery menu, it was all working fine and everything was working fine.
HOWEVER as 1 thing wasn't working on an app I love, and re-installing the app didn't fix the issue, I decided to wipe the whole phone, reinstall the ROM and try re-installing the app then.
But when trying to clear and wipe everything from the phone, in addition to clicking data wipe/cache wipe/dalvik cache wipe, I also clicked on the buttons saying ''Format system / Format SDcard / Format sd-ext''.
When I tried to reboot phone it was bricked, as had no boot screen logo, just was plain dark screen.
I fixed this by removing sd card from phone, putting it into laptop, placing the Cyanogen 4.2.1 rom file directly onto the sdcard, placing sd back into phone, rebooting into recovery menu, and then re-installing the ROM from the sd card.
However I now have a massive issue in that whilst the phone will now work without Mounts2sd installed (well it works but I cant install any apps as no space to do that),
As soon as I install Mounts2sd on the phone and try to use it, whilst it does freeup the memory its meant to, it totally mucksup the entire phone by making every app freeze, making phone not turn off straight away when clicked to... ect
I have removed sdcard, re-partitioned it on my laptop into Fat32 & Ext2, re-installed the ROM multiple times, and then re-installed mounts2sd on the fresh rom and tried to use it,
But everytime I try it just screwsup the phone and makes all the apps and everything on the phone freeze!!
Ive now wiped all data/cache/dalvik,
re-flashed that cyanogen rom onto the phone again (mustve done that 50x now in last 2months),
and am about to try formatting the sd card again on my laptop, then re-partitioning it to Fat32 & Ext2.
But before I re-install Mounts2sd and get the exact same issue all over again,
please please can someone tell me how I can fix this or what im doing wrong??
And so how exactly I can install Mounts2sd back onto my phone again, but without it messingup the whole phone and making everything on it freeze?
Thankyou soooo much inadvance