Related
Guys,
I've looked long and hard on t'interwebs for an answer to this. I'm currently trying to do do a fresh reinstall on my Prime. My Prime hasn't been unlocked, it was rooted before I did the Jellybean update though and I removed a few Asus apps with Titanium backup. I'm trying to get it to run super smooth so that's why I want the complete fresh reinstall.
I've downloaded the latest V10.4.2.15 WW firmware off the Asus website, and upzipped the file so I'm left with the 2nd zip file which is contains. Put this on a FAT32 formatted SD card. I've also tried to copy this onto the root of the internal memory of the Prime. I just can't get the device to see the firmware and reinstall though. Is this because the device is already running V10.4.2.15? Is their any way around this without unlocking the Prime? I've also tried to reinstall using the boot menu, but it won't give me the option either.
Please help!
I also tried to reinstall the update by putting it on a sdcard and had no luck. I concluded that this method must only work for a true upgrade.
Chicaned_UK said:
Guys,
I've looked long and hard on t'interwebs for an answer to this. I'm currently trying to do do a fresh reinstall on my Prime. My Prime hasn't been unlocked, it was rooted before I did the Jellybean update though and I removed a few Asus apps with Titanium backup. I'm trying to get it to run super smooth so that's why I want the complete fresh reinstall.
I've downloaded the latest V10.4.2.15 WW firmware off the Asus website, and upzipped the file so I'm left with the 2nd zip file which is contains. Put this on a FAT32 formatted SD card. I've also tried to copy this onto the root of the internal memory of the Prime. I just can't get the device to see the firmware and reinstall though. Is this because the device is already running V10.4.2.15? Is their any way around this without unlocking the Prime? I've also tried to reinstall using the boot menu, but it won't give me the option either.
Please help!
Click to expand...
Click to collapse
Outside of trying in flash/recovery mode try this:
Rename the Zip file you put on the SDCard for JB to the same name as the last 9.4 OS: US_epad-user-9.4.2.28.zip
With that on the SDCard it may take a removal/reinsert of the SDCard but it should offer to "Downgrade" but once you reboot in to recovery it will be a full flash of new OS. It did NOT wipe my data. I would recommend doing that after. Shutting down and then booting with vol down and power on until the recovery menu comes on then using vol down I believe it is to move the selected option over to "WIPE" then vol up to initiate.
This should yield a "Clean install".
For those nay-sayers out there, I had partial root until I did the above and lost it so I know it overwrites the OS paritition.
Cheers. I'll give that a go when I get home. I'm not too fussed about losing root. I'm even thinking about trading my Prime in for a Nexus 10 depending on the performance of my Prime after the rebuild.
Hmm.. renamed the .zip to WW_epad-user-9.4.2.28.zip but when I when the Prime sees it, I get no notification Tried a reboot but still get nothing. Anyone with any other ideas for this? Can anyone else confirm this works for them?
Chicaned_UK said:
Hmm.. renamed the .zip to WW_epad-user-9.4.2.28.zip but when I when the Prime sees it, I get no notification Tried a reboot but still get nothing. Anyone with any other ideas for this? Can anyone else confirm this works for them?
Click to expand...
Click to collapse
Hrm, I just did it again with the US version because my exchange syncing broke.
My file was called US_epad-user-9.4.2.28.zip
Again, this assumes you have unzipped the official ASUS ROM download from their site and unzipped that file. This will yield a new zip file which is what I renambed and put on the ROOT of my SD card formated as FAT.
I just wrapped it up too, did a full app backup with the asus tool, wiped, reflashed this ROM again and restored and resynced exchange.
You might try giving it the US name. I don't think it would matter because the contents are correct for your device.
I'll try and format the card as FAT instead of FAT32. I'll also try US. Really hope this works!
Sent from my Galaxy Nexus using Tapatalk 2
No dice I'm afraid. Tried a different SD card and renaming it US but get no option to update
Sent from my Galaxy Nexus using Tapatalk 2
I've been experimenting with a few different ROMs. First, I used UltimaRom, before moving onto Paranoid Android, and then CM10. Currently, I am using RootBox - Its been the best one so far (rivalling UltimaROM)
However, I've been left with lots of '0' directories in the file system. So, if I'm on root using ES File Explorer, I can click on '0' repeatedly to get sdcard/0/0/0.
Now, this 0 folder is taking a lot of space. Previously, the folder was 3.61GB in size(!). I've deleted it, now - reducing the size to 1.8GB.
However, the problem is that the UltimaROM ... ROM simply does not go away. The ROM is 1.8GB in size! So, its taking quite a bit of space. I've tried ES, Astro, and the delete option from 'Storage' in the settings yet, although they indicate they've deleted it, it doesn't actually go - and instead it just comes back again and again!
I'm sure I've full wiped in every instance. So, factory reset, cleared cache, cleared dalvik cache, and I even cleared system before moving between the ROMs.
I know two of the '0's were formed by bad installs of RootBox - one install failed, then, forgetting to format before retrying, the next one installed. To rectify this, I installed RootBox again - formatting this time before doing so.
How do I delete this thing permanently?! I really want to avoid wiping again, because it takes so long to get all my apps back. And, there's no guarantee wiping will even work! Although, if that is the only way, I will try it!
Sent from my Nexus 7 using xda app-developers app
Download a stock ROM, flash it in recovery, and that should get rid of the 0 folder. Just make sure the 0 folder doesn't contain any files or data that you might want to save.
Better yet, update your recovery to at least 6.0.27.
Sent from my GT-I9300 using xda app-developers app
Will updating my recovery really fix the issue?
Seems like an unusual method... But I'll try it!
Also, I'm trying to avoid reflashing, so in going to look for other solutions before i completely must flash to get rid of the 0 folder,
Sent from my Nexus 7 using xda app-developers app
Recovery has nothing to do with this, you miss understood him.
Stock Rom? Why? Would this realy overwrite the (perhaps r/o) folders?
I think it's the savest way to format your internal /data /system etc from recovery, and flash your ROM clean. Theretical you can move/ delete your existing folders, but this can be very confusing. Some folders/ mounts may be read only at the moment...
If you switching from 4.2 to 4.1 you are left with the 0 folder. Flashing a stock ROM will reformat your file system and get ride of the 0 folder. If you are switching between 4.2 ROMs you may get a 0/0/0/... folder. Updating recovery should revert the 0/0/0/... folder back to the 0 folder.
When I went from CM10.1 to 4.1 I was left with the 0 folder. Formatting the system in recovery didn't solve the problem and flashing a stock ROM did.
Best method use the search function as per Q12 FAQS .
Question has been asked and solved recently .
jje
Hi, i'm new at the forums, but this have been my first option for android related solutions and info for a long time ago, but i finally decided to join it.
Well, this is embarrasing, but my first post it's about a problem in my pretty new SGS3 GT-i9300 i got a couple of weeks ago.
The problem is..., well, i've been testing some roms as 2nd roms with the help of the Siyah kernel. I've done the basics things..., root my phone, install my first kernel (siyah...), killed the stock rom so i learned how to flash a new stock rom for my country without all the operator's junk, then i overclocked (just a bit only), then i started with the 2nd roms....
My first try was UltimaROM, pretty good but i wanted to test MIUI, no problem, i worked but i didn't like it completely since it deleted all the samsung goodies, so i tried to flash ihackers, no luck..., it wouldn't just boot. So i tried with FoxHound, the same thing. So just dissapointed, i came back to UltimaROM and installed it again as 2nd rom (all in just 2 days). Well, it worked ok but then i noticed a serious problem...
Since the last time, when i flashed UltimaROM with the 2nd Rom Utils from Siyah, i came back to the stock rom (1st rom) because i wanted to record the fireworks outside my home (because of new year ), but, the camera said "Error al grabar" and just closed..., then i remember a couple of random massages saying that i was running out of space in the internal memory, so i dicided to temporarily delete the 2nd rom (i've been so gross these two days...), and..., according to the 2nd rom utils from siyah, the 2nd rom was succesfely removed, but just to be sure, i fixed permissions (i did this everytime i tried to flash a new 2nd rom).
Now back to the stock rom, the camera problem not being able to record to the internal memory still there, but now, i looked into the internal memory with root explorer and there is a big folder named "ADM" with a...¡¿copy?! of the UltimaROM zip, which weights 1.5Gb, and i can't delete it, EVEN WORSE!, now a lot of random files and folders in the internal memory are "locked", i can't delete any of these, or even change permissions (my DCIM folder for example). I then tried the CWM option to "fix permissions", on the main CWM recovery as well as in the siyah 2nd rom utils recovery..., but all the same
Thinking that the internal memory file system got corrupted, i though that my best option was to flash the stock rom from samsung again, but this time with the option "Re-partition" checked. I tried it in Odin but...damn it..., it won't make it!, however, i can soft-flash the stock rom without "re-partition" check..., but this doesn't fix the internal memory...
In short, i CAN boot into my main stock rom, i can FLASH the stock rom trough Odin but i can't if i check the Re-partition option, and until i get i fix for the internal memory, i'll have to use my 2Gb External SD Card.....
So..., what can i do? Is there anything i can do to safely format the internal emmc completely and then flash the stock rom again? Or maybe do i have to...assume...that the locked internal memory problem...is a hardware problem? That's what i'm afraid of...
Anyway, i'll leave the details here.
OS: Stock Rom Samsung JB 4.1.2 (I9300UBEMH2_I9300UVOEMH1_ARO)
Kernel: Siyah Kernel 1.9.1
Recovery: CWM-based Recovery v5.5.0.4 CF-v1.5
I would leave a dump file of the failing Odin process now, but i don't know if that is possible and neither how to do it. But he most i can give is a screenshot attached.
Thanks in advance!
P.D.: let me know if this post is on the wrong place inside the forum
alpha-ro said:
Hi, i'm new at the forums, but this have been my first option for android related solutions and info for a long time ago, but i finally decided to join it.
Well, this is embarrasing, but my first post it's about a problem in my pretty new SGS3 GT-i9300 i got a couple of weeks ago.
The problem is..., well, i've been testing some roms as 2nd roms with the help of the Siyah kernel. I've done the basics things..., root my phone, install my first kernel (siyah...), killed the stock rom so i learned how to flash a new stock rom for my country without all the operator's junk, then i overclocked (just a bit only), then i started with the 2nd roms....
My first try was UltimaROM, pretty good but i wanted to test MIUI, no problem, i worked but i didn't like it completely since it deleted all the samsung goodies, so i tried to flash ihackers, no luck..., it wouldn't just boot. So i tried with FoxHound, the same thing. So just dissapointed, i came back to UltimaROM and installed it again as 2nd rom (all in just 2 days). Well, it worked ok but then i noticed a serious problem...
Since the last time, when i flashed UltimaROM with the 2nd Rom Utils from Siyah, i came back to the stock rom (1st rom) because i wanted to record the fireworks outside my home (because of new year ), but, the camera said "Error al grabar" and just closed..., then i remember a couple of random massages saying that i was running out of space in the internal memory, so i dicided to temporarily delete the 2nd rom (i've been so gross these two days...), and..., according to the 2nd rom utils from siyah, the 2nd rom was succesfely removed, but just to be sure, i fixed permissions (i did this everytime i tried to flash a new 2nd rom).
Now back to the stock rom, the camera problem not being able to record to the internal memory still there, but now, i looked into the internal memory with root explorer and there is a big folder named "ADM" with a...¡¿copy?! of the UltimaROM zip, which weights 1.5Gb, and i can't delete it, EVEN WORSE!, now a lot of random files and folders in the internal memory are "locked", i can't delete any of these, or even change permissions (my DCIM folder for example). I then tried the CWM option to "fix permissions", on the main CWM recovery as well as in the siyah 2nd rom utils recovery..., but all the same
Thinking that the internal memory file system got corrupted, i though that my best option was to flash the stock rom from samsung again, but this time with the option "Re-partition" checked. I tried it in Odin but...damn it..., it won't make it!, however, i can soft-flash the stock rom without "re-partition" check..., but this doesn't fix the internal memory...
In short, i CAN boot into my main stock rom, i can FLASH the stock rom trough Odin but i can't if i check the Re-partition option, and until i get i fix for the internal memory, i'll have to use my 2Gb External SD Card.....
So..., what can i do? Is there anything i can do to safely format the internal emmc completely and then flash the stock rom again? Or maybe do i have to...assume...that the locked internal memory problem...is a hardware problem? That's what i'm afraid of...
Anyway, i'll leave the details here.
OS: Stock Rom Samsung JB 4.1.2 (I9300UBEMH2_I9300UVOEMH1_ARO)
Kernel: Siyah Kernel 1.9.1
Recovery: CWM-based Recovery v5.5.0.4 CF-v1.5
I would leave a dump file of the failing Odin process now, but i don't know if that is possible and neither how to do it. But he most i can give is a screenshot attached.
Thanks in advance!
P.D.: let me know if this post is on the wrong place inside the forum
Click to expand...
Click to collapse
Use es file explorer and click on root manager. And click mount r/w. Make sure both is rw.
Sent from my GT-I9300 using xda app-developers app
Give a thank if I helped you
JellyYogurt said:
Use es file explorer and click on root manager. And click mount r/w. Make sure both is rw.
Sent from my GT-I9300 using xda app-developers app
Give a thank if I helped you
Click to expand...
Click to collapse
Thanks JellyYogurt, Yeah, i tried it as one of my first options, even with root permissions
Now, i'm really REALLY consufed...maybe, can Android get stuck for periods and lock access to some files? because after a while, i came back to take a screenshot in windows showing me a "Read-Only" mode error when trying to delete those damn files, at least, that's what said to me before, because now i connected in MTP as usual and the things i tried to delete with error earlier are...gone? I don't get it yet, and i'm hope it won't happen again, maybe tomorrow i'll try reflashing again
If the problem happens to vanish, i'll let you know so u can delete this post, just give a couple of days, i want to make sure i can make a full reflash with repartitioning in case of future emergencies
Thanks again! Really
Well, it looks like the MTP lied to me, i checked inside /sdcard/ again and the locked files still there and locked :/, i tried again mounting as R/W with no luck. When i try to take a screenshot with power + home, it says that the usb storage could be ON...this is weird, i double check my usb mass storage app and swtich to usb mass storage mode and then back to mtp (i know it's only for the extSdCard...but i don't know what else can i do)
Any ideas plz? Thanks again
Sent from my GT-I9300 using xda app-developers app
alpha-ro said:
Well, it looks like the MTP lied to me, i checked inside /sdcard/ again and the locked files still there and locked :/, i tried again mounting as R/W with no luck. When i try to take a screenshot with power + home, it says that the usb storage could be ON...this is weird, i double check my usb mass storage app and swtich to usb mass storage mode and then back to mtp (i know it's only for the extSdCard...but i don't know what else can i do)
Any ideas plz? Thanks again
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Have u tried a factory reset? Copy paste all ur pics and data to the computer first as u seem to be able to do so.
Well, i tried and tried and let me say this an awful way to begin the year :crying:
I tried using doing the factory reset from within CWM and apparently all was succesful, but again in android, the internal /sdcard/ still the same, it didn't delete anything that my settings!
Now i can't avoid being a bit desperate, is there any way to format the internal /sdcard/ (or /sdcard0/, whatever) so i can start from scratch again? In fact i don't have anything useful in there, 'cause i made a full backup 4 days ago before this problem even appeared. Now i would just be fine if i could format the internal /sdcard/, just that..., i tried the "format /sdcard" option from within CWM...but it formatted the external sdcard, what a mess
I'll be waiting, thanks again!
Use philz recovery instead, format internal sd card, wipe for new rom.
Sent from my GT-I9300 using Tapatalk
You are just a master! I tried flashing a Philz recovery via Odin and, like you told me, i formatted the internal /sdcard/, then without exitting the recovery, i check inside the sdcard with the "install zip" option, and it says "No files found", i would never have imagined how beautiful would those words look .
Now, just to make sure, i would like to repartition with odin, and (at least for now) come back to my stock rom, but the problem i mentioned earlier about "can't open file" when i tried to repartition, was because i missed the .pit file hehe
So i searched for the .pit file for the S3 16GB edition and i found it, in the corresponding forum, they said that the .pit file ending in 329 worked good for all of them.
Now with all in hand, i powered on in Download mode, opened Odin v3 once more, selected Re-partition, choosed the .pit file (ending in 329) and the stock rom .md5, flashed, waited 10min and..., no errors, until i saw the "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" problem, so i flashed again the Philz Touch recovery over the stock one (because when i tried to access the stock recovery the error always appeared), so fine! I booted into Philz and wiped cache, data and...it's so beautiful...:crying:, Android finally started! As if it were just when i bought the S3
So, i fixed it finally! I think the only thing that remains is to reset the counter with TriangleAway and get back my last backup
Thank you so much friend! At the end, i'll stay with Philz Recovery, i didn't know it before but is far better than CWM. Thanks again!
P.D.: now that i know how to unbrick completely, i'll tell my journey to my friend Dany
[Q] Very Weird "Symptoms" Internal+External Storage deleted files instantly reappear
orbital_71 said:
It call magic
Sent from my SM-N9005 using Tapatalk 2
Click to expand...
Click to collapse
For real though what's going on. Whether I use ES file explorer or root explorer, Even TWRP's built in file manager. The first two mentioned will delete the file and say "File Successfully Deleted" and the Storage for Internal/External (which ever it's located in) Reflects the correct change as if it was actually deleted. Yet once you back out of the folder the storage changes right back and I go back in the folder and the file is back...
Another example is moving files,
Just a few minutes ago I downloaded the Latest BeanStalk. I proceeded to move it to my External SD Card. And I deleted several files as well(Several Movies and a Nandroid), I then reboot to TWRP. I get ready to do a backup and notice that the damn storage sizes are back to the same sizes they were before I downloaded the ROM and deleted files. And the ROM is gone, not on Internal where it was downloaded to and moved from. Nor in the External Storage in the folder I moved it to.
Doesn't matter if I delete 17kb or 25GB the storage goes right back to what it was. And what ever files are there no matter if I delete/move/alter. It all goes back to identically the same...
Another odd thing, I made a Nandroid to my internal SD and once I booted back into the system it was gone. Even though it said backup successful. And before rebooting I checked the restore tab and the backup was there
What in the hell could cause that?
Tw1sted247 said:
For real though what's going on. Whether I use ES file explorer or root explorer, Even TWRP's built in file manager. The first two mentioned will delete the file and say "File Successfully Deleted" and the Storage for Internal/External (which ever it's located in) Reflects the correct change as if it was actually deleted. Yet once you back out of the folder the storage changes right back and I go back in the folder and the file is back...
Another example is moving files,
Just a few minutes ago I downloaded the Latest BeanStalk. I proceeded to move it to my External SD Card. And I deleted several files as well(Several Movies and a Nandroid), I then reboot to TWRP. I get ready to do a backup and notice that the damn storage sizes are back to the same sizes they were before I downloaded the ROM and deleted files. And the ROM is gone, not on Internal where it was downloaded to and moved from. Nor in the External Storage in the folder I moved it to.
Doesn't matter if I delete 17kb or 25GB the storage goes right back to what it was. And what ever files are there no matter if I delete/move/alter. It all goes back to identically the same...
Another odd thing, I made a Nandroid to my internal SD and once I booted back into the system it was gone. Even though it said backup successful. And before rebooting I checked the restore tab and the backup was there
What in the hell could cause that?
Click to expand...
Click to collapse
Make sure u are on freezas latest kernel. And twrp linked in my op. Issues with sd otherwise...
Sent from my Samsung Galaxy Note 3 using JellyBombed Tapatalk.
JoshBeach said:
Make sure u are on freezas latest kernel. And twrp linked in my op. Issues with sd otherwise...
Sent from my Samsung Galaxy Note 3 using JellyBombed Tapatalk.
Click to expand...
Click to collapse
It's internal and external though.. And on multiple ROM's
Tw1sted247 said:
It's internal and external though.. And on multiple ROM's
Click to expand...
Click to collapse
Did you update ES File Manager? One of the updates turned on the recycle bin by default, so a bunch of stuff, and space, started appearing (stuff I'd deleted) and depleting (space) until I deselected that option from settings.
Worth a shot.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Unfortunately I checked and that option is not enabled on ES file explorer.
Tw1sted247 said:
Unfortunately I checked and that option is not enabled on ES file explorer.
Click to expand...
Click to collapse
Well that sucks.
Might be time for a full wipe and restoration of your rom of choice.
I'm unclear if killing the internal USB storage is a good idea, but at least the default wipe in recovery (system, data, dalvik) makes sense, though you may end up having to do everything.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Well that sucks.
Might be time for a full wipe and restoration of your rom of choice.
I'm unclear if killing the internal USB storage is a good idea, but at least the default wipe in recovery (system, data, dalvik) makes sense, though you may end up having to do everything.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Everytime that I switch ROM's( with the exception to when I am upgrading a build number from the same ROM) I always go to Advanced and check Cache, System, Dalvik Cache .... I then proceed to back up one menu and swipe the "Factory Reset" Wipe option built into TWRP.
I can't even make Nandroids at this point, they just Disappear after I Reboot. So I went side door on this pesky little bastard. And brought in my OTG and 64GB Thumb Drive. And these Nandroids are sticking. Although the current ROM I am running atm (BeanStalk) isn't recognizing OTG inputs. As it's built off of CyanogenMod, and this is one of the known bugs ATM.
Anywasy One of the Kind fellows on the International N3 forum notified me of a certain Build.prop edit that may tackle this issue. So off I go
**Fingers CRossed:good:
Tw1sted247 said:
Everytime that I switch ROM's( with the exception to when I am upgrading a build number from the same ROM) I always go to Advanced and check Cache, System, Dalvik Cache .... I then proceed to back up one menu and swipe the "Factory Reset" Wipe option built into TWRP.
I can't even make Nandroids at this point, they just Disappear after I Reboot. So I went side door on this pesky little bastard. And brought in my OTG and 64GB Thumb Drive. And these Nandroids are sticking. Although the current ROM I am running atm (BeanStalk) isn't recognizing OTG inputs. As it's built off of CyanogenMod, and this is one of the known bugs ATM.
Anywasy One of the Kind fellows on the International N3 forum notified me of a certain Build.prop edit that may tackle this issue. So off I go
**Fingers CRossed:good:
Click to expand...
Click to collapse
OK, this sounds bloody awful.
I am way unfamiliar with AOSP roms (I have clean rom on my Nexus 7 2013, however, so I get the simplicity of it), just isn't my cup of tea for this phone.
I am wondering if you switching between the 2 platforms hasn't caused some issues. I've wondered this before with other major issues, different from this but similar movement (AOSP to TouchWiz KitKat and back).
I'd like to see some definitive input on properly moving from one to the other.
Sent from my SM-N900P using Xparent BlueTapatalk 2
I've found the culprit and its Permissions. Going to the AOSP ROM which was a KitKat ROM set the Permissions on my SD Card to read only. And I don't have the "authority" to change the permissions back.
I've tried editing the platform.xml to no avail. It's starting to get pretty damn frustrating. Even now when I go back to 4.3 ROM's following a clean wipe(dalvik, system, cache... Then factory reset) my permissions remain the same.
I have been having the same problem. I decided to order a new sd card and change my buildprop using ROM Toolbox Pro. I modiified "ro.securestorage.support" from "true" to "false". I will be receiving my new card either today or tommorow. I have had some bad luck with SanDisk and I am going to try lexar. I'm really considering reformatting back to the tried and true FAT32.
Tw1sted247 said:
Everytime that I switch ROM's( with the exception to when I am upgrading a build number from the same ROM) I always go to Advanced and check Cache, System, Dalvik Cache .... I then proceed to back up one menu and swipe the "Factory Reset" Wipe option built into TWRP.
I can't even make Nandroids at this point, they just Disappear after I Reboot. So I went side door on this pesky little bastard. And brought in my OTG and 64GB Thumb Drive. And these Nandroids are sticking. Although the current ROM I am running atm (BeanStalk) isn't recognizing OTG inputs. As it's built off of CyanogenMod, and this is one of the known bugs ATM.
Anywasy One of the Kind fellows on the International N3 forum notified me of a certain Build.prop edit that may tackle this issue. So off I go
**Fingers CRossed:good:
Click to expand...
Click to collapse
I was having similar issues for awhile, not sure if this is what fixed it or if it was something I did unintentionally but here's what I think may have worked: flashed my modem with MI3 once without auto reset on odin and then again with it then I changed my permissions on my external storage with root file explorer, i went into system/etc/permissions/platform.xml and added <group gid="media_rw" /> under the write_external_storage. I wasn't sure if that was the issue so for good measure I used triangle away and reset the flash counter, id been flashing a lot so I thought maybe that had something to do with it. idk. anyways, I haven't had the problem since. aside from APNs, still cant get custom apns to stick for some reason.
---------- Post added at 06:00 AM ---------- Previous post was at 05:54 AM ----------
Tw1sted247 said:
I've tried editing the platform.xml to no avail. It's starting to get pretty damn frustrating. Even now when I go back to 4.3 ROM's following a clean wipe(dalvik, system, cache... Then factory reset) my permissions remain the same.
Click to expand...
Click to collapse
what twrp are you running?
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!