Hello people. I have a 32 GB Wi-Fi only Tab, running seraphimserapis' CM9 preview kang.
I'll dive right into things here. Earlier today, I flashed the above ROM, everything went perfectly, booted up just fine, and got all my apps back up and running. I was using my tab fine for the entire day with no problems to speak of. Later in the day, I began transferring some misc. files (documents, music, etc) to my internal SD card via MTP USB transfer. After the transfer was complete, I unplugged my tab, and went on my merry way. The next time I booted up, everything began FCing on me, and nearly every app I tried to open immediately FCed. Thinking it was a temporary bug, I rebooted my tab, but the same problem persisted, multiple different processes fced upon boot, and almost all my apps would fc as soon as I opened them. After trying a few more times, I gave up, and booted back into CWM (which I can do perfectly fine), cleared cahce and delvik cache, and did a factory reset. This however,seemed to only augment the problem. Upon booting up (after doing that initial tab setup), trebuchet FCes (in a "FC loop", as it continually tries to open), and the tablet is completely unusable. I have tried wiping cache, reformatting and rebooting several times, each time with the same result
I am able to get into settings however, by plugging in the tab, and clicking USB debugging (for whatever reason, settings does not FC), and am able to connect to my internal memory via MTP. When the tab pops up in my computer, it says I have 25 GB out of 28 available GB, but when I click on the folder, it is completely empty. If i try to move files over to my tab, or even create a new folder, I get an error message saying "the device has stopped responding or has been removed". (Pictures below)
http://img141.imageshack.us/img141/9855/75464072.jpg
http://img190.imageshack.us/img190/3395/61277691.jpg
I do not believe this is a problem with the rom for two reasons. (1) no one else has had this problem (to my knowledge), and (2) it was working fine the whole day, until i did that file transfer (that being said, this is my own amateur opinion, which you may choose to completely disregard it in your diagnosis). I am 99% sure I didn't unplug the tab while files were still transferring, but I did not unmount the storage or eject it or anything fancy of that nature before I unplugged it.
My question is, is there any way I can somehow reformat the internal memory of my tab? Otherwise, is there some other possible fix you experts may possibly have? Or am I screwed?
I apologize in advance if you ask me to try something and I cant respond promptly. Its 3AM here and i need to wake up early tomorrow. Thank you in advance
Edit:
I am quite convinced there is some kind of internal memory corruption problem here, but I really am not an expert enough to know for certain. The tablet still boots up fine, but is completely unusable as trebuchet fc loops 90% of the time i reboot the tab. Obviously, the entire thing isnt trashed as it appears to boot and get into the system fine, but I it's still completely unusable from that point on.
I have tried formatting the /data and /cache partitions of the internal memory to no avail. I would try formatting /system, but from my understanding, thats only advisable if you are able to flash a new rom after formatting, but if i cannot write into my internal memory, then there's no way i can flash a new rom. Conveniently enough, I deleted the .zip file for the rom off my internal sd, and i cannot access my clockworkmod recovery from CWM (gives an error, I don't think that would have worked anyway) since the internal sd is (i believe) corrupted. I also tried mounting as USB from CWM, and that also gives an error...
I am clean out of ideas. I'm not sure if this is a completely unfixable problem, or if self repairing is well within the realm of possibility. If someone can shed some light on me that would REALLY be appreciated. Otherwise i might have to send it back to sammy (still under warranty), which i dont mind doing, but if they boot it to find an ICS rom, they probably wont be so keen to repair it...perhaps there's a way to brick it further so they can't tell?
UPDATE 2:
Problem fixed! I still don't have a clue as to what the problem was, but thankfully I managed to escape out of this one. I tried pushing a new ROM via adb, and it worked (apparently), but this just forced me into a boot loop (never hit the homescreen).
As a last ditch effort I pushed the stock ROM, and completely removed root, and it worked. I can now boot up past the spash screen without all all my processes crashing. Really a strange issue, I have my theories, but they're probably blatanly wrong so I'll just keep them to myself. Im just glad I don't have to send it back to sammy... I plan to re-root shortly. I am confident I will get no further issues.
Even though no one helped me directly, it was thanks to the plethora of information available on this forum that I was able to resolve my issue...and for some reason, making a thread where I'm just talking to myself helps a bit too...maybe im just weird. Anyway if anyone's reading this, thanks again xda
.......HOW??
brennanyama said:
UPDATE 2:
Problem fixed! I still don't have a clue as to what the problem was, but thankfully I managed to escape out of this one. I tried pushing a new ROM via adb, and it worked (apparently), but this just forced me into a boot loop (never hit the homescreen).
As a last ditch effort I pushed the stock ROM, and completely removed root, and it worked. I can now boot up past the spash screen without all all my processes crashing. Really a strange issue, I have my theories, but they're probably blatanly wrong so I'll just keep them to myself. Im just glad I don't have to send it back to sammy... I plan to re-root shortly. I am confident I will get no further issues.
Even though no one helped me directly, it was thanks to the plethora of information available on this forum that I was able to resolve my issue...and for some reason, making a thread where I'm just talking to myself helps a bit too...maybe im just weird. Anyway if anyone's reading this, thanks again xda
Click to expand...
Click to collapse
I'm hoping you see this reply as its been quite a while since you've had the issue. I'm working with a Galaxy S2 Skyrocket with the same intenal memory corruption/ files system corruption you were facing. I followed what you did regarding push a rom thru adb and that worked for me, but my question is, how did you get the roms to successfully write if you couldnt write to internal memory? My system is mounted as read only apparently and locked itself with whatever I had on there on August 28th. No matter how many times I format, erase, or wipe it, it returns to the same state as if its a deep lock on it.
Related
So yes there have been other threads recommending cleaning/tightening battery connectors, using monitoring programs to assess and alert on things like high temp and process cpu spikes etc... a lot of the time the issues raised have been to with someone only recently acquiring their SGS2, or after having "upgraded" their ROM.
Mine seems not to fit any of those scenarios.
A week ago, I found the phone off, so I switched it on and it bootlooped. Nothing new had installed prior, although the was an update to the ZD Box app which I read had problems, but I'd already uninstalled that. So, I rebooted the phone and it seemed to work fine. But no...
At random times whether the phone has been in my pocket or sitting on the desk, I will find the screen is black and none of the hardware buttons do anything. I have to hold the power button for quite some time before I see the Samsung logo and the phone boots up.
It happens several times a day. Battery/CPU monitoring/stats/alert apps show nothing out of the ordinary. I've uninstalled several recentish apps just in case, and no fix. Cleared all caches, fixed permissions, changed modems, no fix.
I'm now in the process of wiping data and flashing a different ROM (a newer version of illusion-xt to the one I've been using... excellent ROM btw), and I'll see if that solves anything.
What's weird is that I've had this phone for nearly a year and it's only just started happening now.
I'm wondering whether this sort of issue has become common with the SGS2 recently. Anyone else experiencing this, and is there are solution for it?
See how you go with the new rom.
If it's still happening, go back & do a completely clean install of stock; format cache, data, system, & internal sd card then flash stock rom in Odin (don't install any apps at all) & run that for a few days. If it's still happening on a relatively 'clean' stock phone, that probably indicates a hardware issue. Could be something simple like the battery, could be the USB/charging circuitry problem we see on here a bit or some other hardware problem.
See how you go with it & post back here.
MistahBungle said:
See how you go with the new rom.
If it's still happening, go back & do a completely clean install of stock; format cache, data, system, & internal sd card then flash stock rom in Odin (don't install any apps at all) & run that for a few days. If it's still happening on a relatively 'clean' stock phone, that probably indicates a hardware issue. Could be something simple like the battery, could be the USB/charging circuitry problem we see on here a bit or some other hardware problem.
See how you go with it & post back here.
Click to expand...
Click to collapse
Followed your recommended steps with the newer ROM. Seemed to be good for a day. I then found my phone off again while it was sitting next to me. I had just installed an app (from "untrusted" sources) just prior to this. So I uninstalled that. Found my phone off again a few minutes ago. This time the phone was hot and about 20% of the battery had drained.
Think I need to do another wipe of everything (except external SD) in case that app was the culprit?
[got a I9100]
if i were you i do this....
save my video/mp3.. stuff
remove microsd
remove sim
using cwm format system, data cache, dalvik, sdcard/emmc (depends on your cwm)
using odin flash a GB rom (i usually go with LA2 / JPLPC [ICS])
after first boot and few minutes dial *2767*3855#
next boot ill setup google account but will not do auto restore / untick auto restore.
shutdown remove battery put the simcard and see how it goes for a day or 2
It's switched off three more times today. The last time it happened the app "Battery Monitor Widget" alerted a "Voltage out of range" warning.
So far nothing's ever gone wrong while the phone is charging.
I may try formatting as has been suggested, but I think I'll try using a new battery first.
Please forgive my daftness as it seems I've misunderstood the instructions here.
Upon booting into CWM Recovery (I have v5.0.2.7) and navigating to "Mounts and Storage" I've discovered what you both mean by "format" in your instructions.
Would this mean following the Gingerbread section of the guide at http://forum.xda-developers.com/showthread.php?t=1457458 is what I need to do to get up and running, and then continue with the remaining instructions in this thread?
MonkeyScrotum said:
Please forgive my daftness as it seems I've misunderstood the instructions here.
Upon booting into CWM Recovery (I have v5.0.2.7) and navigating to "Mounts and Storage" I've discovered what you both mean by "format" in your instructions.
Would this mean following the Gingerbread section of the guide at http://forum.xda-developers.com/showthread.php?t=1457458 is what I need to do to get up and running, and then continue with the remaining instructions in this thread?
Click to expand...
Click to collapse
I have had this issue with certain ROMs in the past where I would get a black screen and no response from the hardware buttons. I found that on installing the ROM everything worked fine. Then I would go ahead and restore my apps, still everything was fine.... but once I configured Exchange sync I would run into the issue. My only option was to go back to a ROM that I knew worked on my device correctly.
In reply to your question above, If you have a ROM downloaded that you can flash in CWM then so long as it is stored on your SDCard you can format the system, data, internal SD and wipe cache, delvik cache from CWM. In doing this I would recommend making sure you know exactly what "internal SD" CWM is talking about. To be sure you could remove your SD card. I made the mistake of formatting the wrong card once and spent the next day recovering the data from it.
If you have the same issue with a new ROM then i'd recommend going back to a stock ROM using the link you posted.
Hope this helps.
I took my sdcard and sim out and rebooted just so I could see what would show up in the file manager. It would seem like there are no apps or mp3's or pics or anything "additional" available.
Strange as I don't recall ever using app to SD, and I could've sworn I saved at least a few MP3s and pics to the phone.
Maybe I'm just not looking in the right place. Where would I normally find my app folders without the sdcard being present?
Ahh... so once you put the sim in (but still without sdcard) apps folders show up in "/sdcard"
hmm... does this sound correct?
why are you making things difficult?
put your sdcard back, open file browser goto sdcard dcim
you will find pics and videos there if they are saved on your phone storage. copy them to micro sdcard.
simple
if you are on aosp rom than the structure is little different
PS: doesn't matter your sim is in or out.
Stock ROM
/sdcard
/sdcard/external_sd
AOSP ROM
/sdcard
/emmc
As instructed I formatted partitions, installed latest official ICS ROM (for Australia) from sammobile.com using ODIN. Didn't install any apps. Didn't sync. I still have the "black-screen-freeze" at least once a day for several days. Today it's done it 5 times already. Sometimes I find the phone is hot, sometimes not, and a couple of times I've found the battery drained as well.
I can't seem to find a standard pattern that's reproducible.
What now?
I own a rooted Samsung Vibrant running cm7, overclocked to 1.3ghz, with cwm recovery. My external SD was full to a byte and my internal had about 100mb free, so I decided to move all my apps on SD to internal. I used an app called App2SD that, among other things, lets you batch move apps. I selected everything on the SD and started a batch move. Like normal, it had to bring up the settings page for each individual app -- annoying, but necessary for the app to work on nonrooted phones. After repeatedly hitting "move to phone" -- back -- "move to phone" -- back -- "move to phone" etc. After almost freezing, and a few metric tons of lag, I finally finished. However, the phone immediately started acting weird. Apps would crash, even after reinstall. This included built in apps like "messaging." It also had the "low memory" alert on, even though the only memory that had gone down was the internal, and it still had >1gb free. (The notification might have actually appeared before, not sure.) Today, after getting into a bit of a jam because I couldn't text, I rebooted the phone. It stopped at the boot animation. I happen to have Live Dmesg, by Chainfire, which replaces the animation with the BIOS output at startup, so I could see that it was getting stuck in a loop after the normal PHONE_ACTIVE=1 message that is the last one I can read (it stops for a few seconds after that, the rest moves way too fast, and the phone boots less than a second later). I have tried rebooting several times, booting to recovery, rebooting, removing battery, etc. Nothing worked. I could probably get it working, as I can access CWM without much trouble, but that would require losing all my data. Yes, I use Titanium, and USB debugging is on, but it would still be a lot of trouble, and I would lose a significant amount of app data.
Any help would be welcome, thanks!
I suppose, in CWM you could mount your internal SD, and backup all of your data and such. Maybe try to move things around manually, and get it to a working state again.
Toast6977 said:
I suppose, in CWM you could mount your internal SD, and backup all of your data and such. Maybe try to move things around manually, and get it to a working state again.
Click to expand...
Click to collapse
When you say to back up the internal memory, do you mean for safety, or to then reset to stock cm7, or what? I don't see how simply backing it up could help.
I don't think I could just move things around, unless I can get a hint from the output from live dmesg. I don't even know where the problem is -- are there any app2sd-able apps that are necessary for system stability?
Well, I guess I assumed you may have an idea of some of the offending apps that may have caused the problem by moving them. If you mounted, could have manually tried to move or remove them and maybe your phone wouldnt be borked anymore.
Probably would be easier to Odin to stock and start over.. move things over a bit slower and possibly one at a time so you can catch any errors or problems with the transfer.
Toast6977 said:
Well, I guess I assumed you may have an idea of some of the offending apps that may have caused the problem by moving them. If you mounted, could have manually tried to move or remove them and maybe your phone wouldnt be borked anymore.
Probably would be easier to Odin to stock and start over.. move things over a bit slower and possibly one at a time so you can catch any errors or problems with the transfer.
Click to expand...
Click to collapse
I don't think I would even have to Odin, I can easily access CWM and reflash cm7 from there, right?
Also, I don't think the problem would happen again, I have done the same several times and I think it was due to the extreme lag and freezes that something got mis-moved.
I will examine the bios output, and if that doesn't give me any new info, revert to stock cm7 with cwm. Or with Odin through AIO if that doesn't work.
EDIT:
CWM'd back to a May backup. Old, but better than stock CM. Boots fine. Will try transferring apps a bit more calmly.
Just preferential to me, I rarely do it, so when I need to start fresh I just go that route.
Glad you got sorted out.
What do you mean stock CM?
sent from the depths of helly bean
CyanogenMod as downloaded. Not "stock" exactly, but you know what I mean.
I recently flashed to Helly Bean. even better. However, the superuser is acting odd, denying access and asking repeatedly. ANy help would be welcome, though you guys have already helped me out, and thanks for that.
I'm currently using sgs2 with stock gingerbread.
My problem is, my phone seems to be locked on a specific state dated march 3rd 2013.
whenever i format usb storage or reboot my phone, it always back the way it was
e.g. when i tried to un/install apps or deleting files (succesfully), and then i rebooted it, the apps or files are still there such way unharmed.
i remember its somewhat like deep frezee. but usually, something like this only works on settings right?
its really nonsense when i deleted 8 gigs of file then i do a format/reboot, the 8 gigs files came up again like nothing has happened.
Already tried factory reset and unchecked restore backup settings.
Never faced something like this before, help is much appreciated
Sound like a problem with the rom, best thing you can do is backup everything (data) and do a complete wipe through recovery and flash a clean rom again. Very strange but have never (in all my experiece of IT etc) come across stuck dates and data that wont dissapear.
Edit: maybe this is a damaged or corrupt filing system? Still, the fix for tha would to be a complete format.
jl10101 said:
Sound like a problem with the rom, best thing you can do is backup everything (data) and do a complete wipe through recovery and flash a clean rom again. Very strange but have never (in all my experiece of IT etc) come across stuck dates and data that wont dissapear.
Edit: maybe this is a damaged or corrupt filing system? Still, the fix for that would to be a complete format.
Click to expand...
Click to collapse
before this, a had an issue with the sd card, it suddenly went corrupt and cant be read anywhere. maybe this is one of the factors too?
i do planned reflashing it with jelly bean, but i'm still curios what has caused this so i can prevent and understand the problem..
my phone cant make new memories as well, new files are nowhere to be found after reboot.
thanks for the reply jl10101
btw this reminds me of memento
So here's my problem. I recently bought a Nook Tablet (hardly used) at a garage sale. The owner had rooted it when she got it, and she said she simply "no longer needed it", but I think she simply just screwed it up beyond her ability to repair. She factory reset it (which obviously did not get rid of root) before she sold it, and now that I have it I cannot download any apps. However, I can download books. Also, whenever I turn it off and then back on, I get this error message: "The application DownloadAdmin (process com.bn.nook.dadmin) has stopped unexpectedly. Please try again." I took it to a Barne's and Noble a few days ago and explained the situation, and the lady there said that what the problem is is that when they rooted it they turned off automatic updates, so now the only way to fix it is to reroot it and turn auto-updates back on.
I attempted to reroot it, but so far I have not gotten any luck. I tried installing CWM by reformatting an SD card and using that, but instead of automatically booting into recovery mode it just booted like normal, presenting the files on the card simply as unreadable, useless files. I don't really know what to do, as it seems that no matter what I do I am unable to complete the process because of whatever problem my Nook is having. Any advice, leads on what I should do, etc?
zschimp92 said:
So here's my problem. I recently bought a Nook Tablet (hardly used) at a garage sale. The owner had rooted it when she got it, and she said she simply "no longer needed it", but I think she simply just screwed it up beyond her ability to repair. She factory reset it (which obviously did not get rid of root) before she sold it, and now that I have it I cannot download any apps. However, I can download books. Also, whenever I turn it off and then back on, I get this error message: "The application DownloadAdmin (process com.bn.nook.dadmin) has stopped unexpectedly. Please try again." I took it to a Barne's and Noble a few days ago and explained the situation, and the lady there said that what the problem is is that when they rooted it they turned off automatic updates, so now the only way to fix it is to reroot it and turn auto-updates back on.
I attempted to reroot it, but so far I have not gotten any luck. I tried installing CWM by reformatting an SD card and using that, but instead of automatically booting into recovery mode it just booted like normal, presenting the files on the card simply as unreadable, useless files. I don't really know what to do, as it seems that no matter what I do I am unable to complete the process because of whatever problem my Nook is having. Any advice, leads on what I should do, etc?
Click to expand...
Click to collapse
Well before doing anything else I recommend just using the repart image which will take your Tablet back to stock 1.4.2. Write this image file to a SD card (using win32diskimager) and put it in your NT. Once you get the green checkmark take the SD card out and it will start to restore your NT to stock.
http://raywaldo.com/2012/06/make-unbrick-repartition-image/
If you have any problems just shout them out.
Whether you...
go back to stock and then root, and just use the device like that (which is not really what I think most might consider the best option), or
just go straight to a full Android ROM (which is already rooted "out of the, errr, 'box'")
My recommendation would be focus on the second option.
http://forum.xda-developers.com/showthread.php?t=2056626 is the way to go, just use the latest versions of files as follows:
The newest version of cwm_6.0.*.*_acclaim_recovery_sdcard.img from here instead of the others in step 2b.
The newest or the stable version (your choice) of CyanogenMod from here instead of the one in step 2c.
The newest gapps-jb-2013* from here for step 2d.
If you have any problems, describe the steps you took and we'll help you out.
Good luck!
Don't confuse the eMMC and SDC versions of the ROMs. The SDC image isn't the same as the .zip files. You write the .img files to an SD card and it creates the 4 partitions (boot, system, data, sdcard) for the SDC version of the ROM. You can use the .img file to create the partitions then install the zip, or manually create the partitions and install the zip.
If you want to internally install CM then follow the instruction InUrKitchen gave and use a non SDC file.
Hi, I'm in desperate need of help, please.
I'm using SGS2. Several months ago my device suddenly started acting weird, thumbnails in gallery didn't load, apps didn't refresh (instagram, facebook etc.)... Rebooting would help but only for a certain amount of time, until it suddenly started to happen again. I realised the internal SD card simply becomes read-only randomly, but I didn't know why. I made peace with it since I'm not a big smartphone user.
Anyhow, today I went through my phone files and saw that several cache folders were oddly big, so I deleted a ****load of files, and then(!!) that one folder would not delete... So I clicked it and saw a bunch of gibberish files that do not want to get deleted.
I tried SD Maid app, but the thing is, once I browse to that specific corrupt folder the SD card goes crazy and becomes read-only, so basically at that moment I realised that folder is what's making the phone act like this.
Connecting it to PC and deleting doesn't work either. Renaming the files doesn't work. Copy/paste does work but is useless. Factory reset/installing new ROM/kernel/whatever doesn't work either. The files will still be there, I've tried.
Anything, please?
yellowjellow said:
Hi, I'm in desperate need of help, please.
I'm using SGS2. Several months ago my device suddenly started acting weird, thumbnails in gallery didn't load, apps didn't refresh (instagram, facebook etc.)... Rebooting would help but only for a certain amount of time, until it suddenly started to happen again. I realised the internal SD card simply becomes read-only randomly, but I didn't know why. I made peace with it since I'm not a big smartphone user.
Anyhow, today I went through my phone files and saw that several cache folders were oddly big, so I deleted a ****load of files, and then(!!) that one folder would not delete... So I clicked it and saw a bunch of gibberish files that do not want to get deleted.
I tried SD Maid app, but the thing is, once I browse to that specific corrupt folder the SD card goes crazy and becomes read-only, so basically at that moment I realised that folder is what's making the phone act like this.
Connecting it to PC and deleting doesn't work either. Renaming the files doesn't work. Copy/paste does work but is useless. Factory reset/installing new ROM/kernel/whatever doesn't work either. The files will still be there, I've tried.
Anything, please?
Click to expand...
Click to collapse
What rom were you using when the errors started happening?
What have you tried as far as flashing roms/kernels/custom recoveries?
I'm using Omega v24 XWLSW (4.1.2). What I did was factory reset and every single format option in that CWM recovery screen. I then flashed that same ROM again but fresh.
I don't think this has anything to do with ROM/kernels etc. This is simply a bunch of corrupt files in Device\sdcard\Android. I've tried googling with no success. I need a way to forcibly delete that folder with all those files inside. Any directions on how format?
yellowjellow said:
I'm using Omega v24 XWLSW (4.1.2). What I did was factory reset and every single format option in that CWM recovery screen. I then flashed that same ROM again but fresh.
I don't think this has anything to do with ROM/kernels etc. This is simply a bunch of corrupt files in Device\sdcard\Android. I've tried googling with no success. I need a way to forcibly delete that folder with all those files inside. Any directions on how format?
Click to expand...
Click to collapse
The first thing I would try is to reinstall a stock samsung rom. This sometimes is the only way to fully reset your phone back to original condition. Sammobile.com is the website I have used. You would have to root again but....
Also check out this thread -
http://forum.xda-developers.com/galaxy-s2/help/qa-friendly-qa-thread-t1648351
There are some similarities with possible corrupt partitions another guy has(the last few pages of thread), that they are trouble-shooting. You might find some answers there.
yellowjellow said:
I'm using Omega v24 XWLSW (4.1.2). What I did was factory reset and every single format option in that CWM recovery screen. I then flashed that same ROM again but fresh.
I don't think this has anything to do with ROM/kernels etc. This is simply a bunch of corrupt files in Device\sdcard\Android. I've tried googling with no success. I need a way to forcibly delete that folder with all those files inside. Any directions on how format?
Click to expand...
Click to collapse
Hey mate.
If you haven't fixed the problem i recommend performing a checkdisk.
To perform a checkdisk you need to:
1. Connect your phone through USB via mass storage mode.
2. The computer should prompt you to perform a checkdisk automatically, in that case just accept and let the computer perform it. If it doesn't prompt automatically you need to do it manully by right-clicking the correct partition on the computer, click properties and then on the 'Tools' bar. Now mine is in Swedish, i don't know how it is in english but press the button on the first alternative. (i.e the button with 'Control' and the administrator logo).
After pressing, just let it be (it will take quite a while) and when finished.. tell me if it worked or not.
Good luck!
Hey, I tried chkdsk and defrag just in case, the files are still there, although some of them are now gone. My phone doesn't go crazy anymore though, which is nice. Maybe I'll just let the corrupt files be there in peace, they won the war XD And as long as my phone works properly I don't really care about them.
Thanks everyone!