Related
Hello,
I have strange defect in my phone: after every power cycle phone wakes up in state it was at about February 13 2012. I can not permanently change anything. I also can not change firmware. I even have made full three stage recovery from broken nand write, as described elsewhere here, without changing anything.
What is strange: no warnings or failure notices. Phone is working normally. Flashing is also seemingly working okay. But after restart nothing is changed. Only when I work with big files, random apps start to crash. I discovered this when downloading maps.
My question is: can sgs2 with Android 2.3.3 seemingly work O.K. with totally nonfunctional nonvolatile memory writing?
Because I don't know your history....
Did you full wiped that is
Format cache data system sdcard
Dalvik.
atifsh said:
Because I don't know your history....
Did you full wiped that is
Format cache data system sdcard
Dalvik.
Click to expand...
Click to collapse
I did. Nothing gets erased. If you know, how Android system works: in your opinion is it possible that system under light usage works O.K. in spite that nonvolatile storage is effectively read only?
Strange issue, but yes in theory, if your storage is busted in a way that it actually works as a read only, but when an application need to write something it fails and crashes.
atifsh said:
Strange issue, but yes in theory, if your storage is busted in a way that it actually works as a read only, but when an application need to write something it fails and crashes.
Click to expand...
Click to collapse
When an application needs to write something it does not fail, at least when it does not write large amounts of data. I can do everyday tasks: add or remove contacts, add few apps (which then actually work), move icons on screens and so on. Is all this possible with NVmemory working as ROM? Because after power cycle all that is gone and all reverts to February 13 2012 state.
Just a thought but have you tried erasing all the contents of your phone?
Using ODIN you can install an odin Cyanogenmod rom, use the pitfile and select repartition. This I believe wipes everything except the 14gb user data portion. Then, just format that under settings.
Perhaps a full wipe would fix it.
MikeMurphy said:
Just a thought but have you tried erasing all the contents of your phone?
Using ODIN you can install an odin Cyanogenmod rom, use the pitfile and select repartition. This I believe wipes everything except the 14gb user data portion. Then, just format that under settings.
Perhaps a full wipe would fix it.
Click to expand...
Click to collapse
That's what I think too, but didn't told him because using pit got a high chance of bricking.
And the way he is using suggests he is out of warranty.
MikeMurphy said:
Just a thought but have you tried erasing all the contents of your phone?
Click to expand...
Click to collapse
The phone does not effectively wipe at all. After any wiping or installing new roms/bootloaders/pits/anything the phone wakes up in state it was 2012/02/13, except date and time, which is current.
If you have used pit and tick repartition, and still nothing erased, boy your internal storage is shouting get rid of me fast or I'll go dead on you soon.
Or I could be wrong and your phone will out lived you
I am pretty much convinced that my phone is irreparable. I do not look for solution to make it work normally again (although I would very much welcome one if I'm wrong).
I seek an answer from somebody who intimately knows, how Android filesystem works: Is it possible, that phone works seemingly O.K. under very light usage in spite that it cannot in fact write to flash memory? And work like this for 2 months without giving warning/error messages?
I compare my situation to a PC with ram-disk setup and an unwritable hard disk. This would not work long. Can Android?
Hey Zie, you may not get this notification of reply, but I wanted to ask, did you ever reach a solution with you SGS II? I'm on the Skyrocket and the same thing happened to me a few days ago. So far nothing has worked and I just upgraded. This was my second Skyrocket coming from an Infuse 4g.
Can't return the phone because all can tell its a rooted device with a custom rom on it. AOKP Milestone 6. Let me know what u did to get around this if u can....
Sent from my SGH-I727 using xda premium
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'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
Yesterday I installed a ROM (Unofficial Resurrection Remix) thanks to EndLess and it seemed great, really very good work with the system. But when I went to restore the original rom of the phone "TWRP" asks me for an unlock pattern, after putting it and restoring the original system image, I am ready to boot the system. The system starts well, but asks me for the same pattern to start the boot. Then the loading process continues and I get to the part of setting the unlock pattern to start Android. Here's my problem, the pattern I used is the same one that I used the previous 2 times and it does not work.
Therefore I have 4 questions:
1- Is it possible to delete the encryption of the phone and leave it as it was before installing Android 8.1?
2- Is it possible to access my previous system?
3- I noticed that this room does not come with root activated, is it possible to root the ROOM?
4- If I put a new unlock pattern, will the current one be overwritten in the encryption or will the phone simply not find a way to boot and I will have a beautiful paperweight?
Thanks in advance.
Please forgive my English, it is not my native language
brito9112 said:
Yesterday I installed a ROM (Unofficial Resurrection Remix) thanks to EndLess and it seemed great, really very good work with the system. But when I went to restore the original rom of the phone "TWRP" asks me for an unlock pattern, after putting it and restoring the original system image, I am ready to boot the system. The system starts well, but asks me for the same pattern to start the boot. Then the loading process continues and I get to the part of setting the unlock pattern to start Android. Here's my problem, the pattern I used is the same one that I used the previous 2 times and it does not work.
Therefore I have 4 questions:
1- Is it possible to delete the encryption of the phone and leave it as it was before installing Android 8.1?
2- Is it possible to access my previous system?
3- I noticed that this room does not come with root activated, is it possible to root the ROOM?
4- If I put a new unlock pattern, will the current one be overwritten in the encryption or will the phone simply not find a way to boot and I will have a beautiful paperweight?
Thanks in advance.
Please forgive my English, it is not my native language
Click to expand...
Click to collapse
As it seems that you encrypted your device somehow by chance.
1. Before installing any rom you have to format your data First. That'll Remove the pattern.
2. Accessing the old system depends upon your access. If you are now encrypted then no actually.
3. Yea just flash magisk zip and the rom will be rooted.
4. Expect an out of the world paper weight.
MyNameIsRage said:
As it seems that you encrypted your device somehow by chance.
1. Before installing any rom you have to format your data First. That'll Remove the pattern.
2. Accessing the old system depends upon your access. If you are now encrypted then no actually.
3. Yea just flash magisk zip and the rom will be rooted.
4. Expect an out of the world paper weight.
Click to expand...
Click to collapse
Thanks for the quick response, would you be so kind as to explain to me what do you mean by "format your data first"?
You mean to delete all the partitions of the phone and install everything from 0 ??
How am I supposed to do that? I have a save from the previous system, I told "TWRP" to save all the partitions in my phone. If I restore that backup, will my device be decrypted?
brito9112 said:
Thanks for the quick response, would you be so kind as to explain to me what do you mean by "format your data first"?
Click to expand...
Click to collapse
Boot to TWRP, and select "Format data". You will lose all your data, plus the contents of your internal SD - but the encryption will be gone. You should back up your internal SD (either to an external SD drive, or your PC, etc) before trying any of this. I hope you have backups of your data.
DarthJabba9 said:
Boot to TWRP, and select "Format data". You will lose all your data, plus the contents of your internal SD - but the encryption will be gone. You should back up your internal SD (either to an external SD drive, or your PC, etc) before trying any of this. I hope you have backups of your data.
Click to expand...
Click to collapse
Thanks for answering, i will try your method in a few minutes, by the way, with format you mean wipe data partition, right?
brito9112 said:
Thanks for answering, i will try your method in a few minutes, by the way, with format you mean wipe data partition, right?
Click to expand...
Click to collapse
When you select "wipe" on main menu. There will we two options at bottom. One will say "Format data" and another will say "Partition" select format data. It will open a new screen saying that format data will delete all the data and Remove encryption. Type yes and continue. However backup your data before doing this. Better copy the files using mtp from recovery or system.
MyNameIsRage said:
When you select "wipe" on main menu. There will we two options at bottom. One will say "Format data" and another will say "Partition" select format data. It will open a new screen saying that format data will delete all the data and Remove encryption. Type yes and continue. However backup your data before doing this. Better copy the files using mtp from recovery or system.
Click to expand...
Click to collapse
I saw that option later, thanks to all who help, my system was recover. The only strange thing was the lock pattern. I delete from /data/system/ this 2 files, "gatekeeper.password.key" and "gatekeeper.pattern.key". Use TWRP as file manager and my phone good as new.
Hi folks.
I've just acquired a Xiaomi Redmi Note 3, and I have officially unlocked the bootloader, and installed Redwolf Recovery, Magisk, and the Pixel Experience Oreo ROM, and the phone was working for a few days without issues.
Today however, whenever I boot into my phone, force close errors pop up at three errors per second, and when I try to perform a factory reset and reinstall a ROM, the current, yet corrupt installation remains, and I cannot get rid of it.
Is there any way to solve this issue, as this is the first time I have experienced this?
Thanks.
aha360 said:
Today however, whenever I boot into my phone, force close errors pop up at three errors per second, and when I try to perform a factory reset and reinstall a ROM, the current, yet corrupt installation remains, and I cannot get rid of it.
Click to expand...
Click to collapse
Hi, you need to do advanced wipe in recovery and wipe /system, /data, /cache, /dalvik, /ART before installing a new ROM.
Should your preferred ROM still produce this issue, please try for a quick test https://download.lineageos.org/kenzo
You don't need Magisk to root LOS.
:good:
k23m said:
Hi, you need to do advanced wipe in recovery and wipe /system, /data, /cache, /dalvik, /ART before installing a new ROM.
Should your preferred ROM still produce this issue, please try for a quick test https://download.lineageos.org/kenzo
You don't need Magisk to root LOS.
:good:
Click to expand...
Click to collapse
Thank you very much for that. I actually did that before you suggested this to me, and I'm back up and running now.
However, one thing I have learned is that you shouldn't add any files to internal storage AFTER doing a full, destructive wipe and AFTER installing anything from there, as those files will disappear while the storage gets occupied in the process, so I ended up having to repeat the process, but with the required files ON THE microSD CARD.
Another thing I have learned from this is to not install a custom ROM on encrypted storage and double-check the encryption status BEFORE flashing a ROM as I now know that some stock ROMs automatically encrypt the /data/ and /data/media/ partitions, which is a huge pain in the backside.
Lesson of the day: even if you think you're familiar with custom ROMs and installing them, there are times whereby you'll end up hitting brick wall dilemmas like this one.
aha360 said:
Thank you very much for that. I actually did that before you suggested this to me, and I'm back up and running now.
However, one thing I have learned is that you shouldn't add any files to internal storage AFTER doing a full, destructive wipe and AFTER installing anything from there, as those files will disappear while the storage gets occupied in the process, so I ended up having to repeat the process, but with the required files ON THE microSD CARD.
Another thing I have learned from this is to not install a custom ROM on encrypted storage and double-check the encryption status BEFORE flashing a ROM as I now know that some stock ROMs automatically encrypt the /data/ and /data/media/ partitions, which is a huge pain in the backside.
Lesson of the day: even if you think you're familiar with custom ROMs and installing them, there are times whereby you'll end up hitting brick wall dilemmas like this one.
Click to expand...
Click to collapse
U only need to do format data option if u come from miui rom. Coz miui encrypts the data and internal sd. So format data option is must.
Moving from one custom rom to another u dont need format data. Only wipe data reset is enough.
If u have any important document . keep it in external sd. If something goes wrong or custom rom cant boot then we use format data option which erases ur internal sd too.
No need to encrypt the device. Just install the rom which comes with selinux enforcing which is enough to protect ur userspace.
naik2902 said:
U only need to do format data option if u come from miui rom. Coz miui encrypts the data and internal sd. So format data option is must.
Moving from one custom rom to another u dont need format data. Only wipe data reset is enough.
If u have any important document . keep it in external sd. If something goes wrong or custom rom cant boot then we use format data option which erases ur internal sd too.
No need to encrypt the device. Just install the rom which comes with selinux enforcing which is enough to protect ur userspace.
Click to expand...
Click to collapse
Muchos gracias.
Also, I have a microSD card for that very reason, which is to keep all my files that I want to keep separate and safe from destructive deletion, and I have now learned that stock ROMs like the MIUI ROM encrypt the data and internal shared storage partitions, and that I have to do a full, destructive, internal storage wipe whenever I migrate to a custom ROM FROM a stock ROM.
Also, I frankly don't give a two sh!ts about storage encryption and SElinux policies as they're far too inconvenient for the trade-off in terms of technological security versus technological freedom, so I installed The SELinux Switch app from here, and I intend to leave the device decrypted for the aforementioned reasons.
aha360 said:
Also, I frankly don't give a two sh!ts about storage encryption and SElinux policies as they're far too inconvenient for the trade-off in terms of technological security versus technological freedom, so I installed The SELinux Switch app from here, and I intend to leave the device decrypted for the aforementioned reasons.
Click to expand...
Click to collapse
Exactly. When we unlock bootloaders and root our devices we choose freedom and the remaining constrictions like SElinux and encryption are, in this context, completely useless shackles. Furthermore, encryption contributes to NAND flash wear and premature device failure.
:highfive:
k23m said:
Exactly. When we unlock bootloaders and root our devices we choose freedom and the remaining constrictions like SElinux and encryption are, in this context, completely useless shackles. Furthermore, encryption contributes to NAND flash wear and premature device failure.
:highfive:
Click to expand...
Click to collapse
Not only that - SELinux, when set to Enforcing, restricts certain simple commands and shoves them unnecessarily behind root privileges, like "reboot bootloader", or "reboot -p", or "reboot fastboot", or "reboot recovery", or "reboot". I'm not going to wait 60 seconds for a device to reboot into recovery - screw that.
Hell, even having SELinux set to Enforcing can interfere with or block infrared beam access. Stupid crap I tell ya.