MB860 logic circuit includ the CPU 、DDR memory and 16G memory . Produced when the plant has not erased the memory of the CPU on the binding of 16G memory chip ID. So if phone bricks or canot boot. Need to be replaced 16G memory chips, but. CPU already has the only non-erasable old 16G chip ID. we can only replace the new CPU. to re-write the factory version of the boot process, otherwise the CPU is denied write the boot process.
you can see
http: //item.taobao.com/item.htm?id=15194812740&wwlight=cntaobao%E6%B7%B1%E5%9C%B3%E5%8D%8E%E7%BB%B4%E7%A7%91%E6%8A%80-%7B15194812740%7D
Hi Guys,
I've recently been messing with the ICS SD Card encryption (not encrypted the device itself yet) and being conscious of security, i'm not happy with the 16 digit restriction the screen lock has, nor the fact that its tied into the same password as the screen lock as i can breach those pretty easily.
Can i use CLI commands like you can when using the full disk encryption against the SD Card encryption process?
i.e. cryptfs as shown here: http://nelenkov.blogspot.co.uk/2012/08/changing-androids-disk-encryption.html
i'm not fussed about being prompted for a separate password.
Thanks guys.
Anybody?
Hello,
as the title suggests, is there a way to securely erase an Android device's internal storage (eMMC or NAND flash memory) without wearing it out. As it is known, flash memory has a limited amount of Write/Erase cycles, so I assume that writing zeroes to each page would wear it out pretty quickly.
So is there a way to securely wipe an Android device? For example is there a way to call a native secure erase command from select Android devices? (I think hdparm does this).
Thanks!
If I enable encryption will it interfere with my ability to flash roms at all?
I can't find the link but I know I've read that if you encrypt your SD card then flash another ROM you won't be able to read the data. Never read anything about encrypting the main memory and its effects on flashing.
I have the same question. Can I encrypt my phone after rooting and installing a custom boot loader?
I understand the limits of encrypting the SD card.
Anyone here encrypt there phone after rooting?
@Gargantuantua did you encrypt your phone? If so, any limitations afterwards?
Sent from outer space.
Hello guys,
I am having problems with my phone, so i am seeking an advice. Do you know any method of how to move files from internal storage to sd card while you are in recovery, or, even better, by using computer, through terminal or something like that? If not of how to move them then at least of how to delete them (only specific files)?
I know that you can factory reset phone what will delete all of your files, but i want to copy (or remove) only a few specific files.
[additional details]
If you want to know more, here is why i need to do it. So, i have Huawei y7 prime, and it has become strange. Ever since i got it, whenever the amount of free space in internal storage dropped below 100 MB, phone popped out low memory warning. But the problem is that it is not possible to dismiss this warning. It is drawn on top of other apps, it offers one and only one option (to perform memory cleaning) and it does not want to go away unless you acctually allow it to perform automatic memory cleaning. The problem is that this very violent warning is repeated every 60 seconds as long as the amount of free memory is below 100 MB. So, in case if this automatic memory cleaning does not clean enough memory to free at least 100 MB, phone will enter infinite loop. It will show low memory warning, then 60 seconds later show another one and so on. And since this message is not dismissible, you actually have to play along and actually start memory cleaning every 60 seconds.
But the real reason why is this a problem is that memory cleaning is so resource intensive operation that all apps often start freezing and not responding while memory cleaning is in progress. But since, if memory cleaning does not recover at least 100 MB of space, phone forces you to perform another memory cleaning, in such case, you have 60 seconds to complete the memory cleaning and switch to another app to manually delete or remove files before another warning pops out and forces you to perform another memory cleaning. Often, after memory cleaning is complete, you have only a few seconds of useful time to try to open another app and delete or copy files. That is not enough, and in case of infinite loop, your phone becomes practicly useless. You have to connect it to a computer and delete or move files through a computer to get rid of this infinite loop.
This all is really bad, but it is solveable. The real problem is that apps become unresponsive while scan is in progress, and in case of infinite loop, they often do not become responsive for a long time. In that case, they start failing and getting closed. Including system ones! So in case of the infinite loop, apps start getting closed one by one and it is only matter of time before some critical system app is closed what forces device to reboot. This behaviour was present ever since i had my first low memory incident on that device after i got it. Surprisingly, after reboot, first memory cleaning usually does recover more than 100 MB of space and infinite loop is broken.
There is another special case of low memory situation, and that is the case when there is no free memory at all, that is, where there is 0 b of free memory left. In such case, the same cleaning loop happens which eventually results with device reboot if i am not able to move or delete files through computer in time to prevent this. But, case when there is exactly 0 b of free memory is special because in that case, when device reboot happens, it sometimes does not manage to boot on the first try and has to reboot twice.
At least that was the case until a few days ago. Things got drasticly worse in the last few days. 0 b low memory incidents started to cause boot loops, the worst kind, infinite ones. Two low memory incidents ago, when incident happened, phone attempted to reboot 4 times before exiting the boot loop. On the previous low memory incident, it took about 16 boots to break out of the boot loop. Now, i am facing another 0 b low memory incident involving a boot loop spanning at least 64 boots and i have no reason to believe that this boot loop is going to end any time soon. Those boot loops only happen when there is 0 b low memory incident. When there is some other low memory incident involving a reboot but with more than 0 b of memory free, the boot loop does not happen. Device reboots only once after what on the first memory cleaning it is able to recover more than 100 MB of free space after what the devices continues functioning normally.
My guess is that Android has to write something durring boot what it cans not in case if there is 0 b of free memory what causes a boot to fail and triggers reboot what causes the bootloop. Although until a few days ago the device was able to boot with 0 b of free memory without problem. So this is strange.
0 b low memory incidents are very common on my phone since i have apps installed which download some live streams automatically in the background, and those streams can take up to 8 gb of free space per stream. So, if live stream happens when i am not around my phone, this app for downloading live streams can easily eat all phones internal memory and create 0 b low memory incident. And, untill few days ago the phone was able to recover from those incidents, almost on a daily basis.
However, now those boot loops started and i am now neither able to recover from 0 b low memory incident by moving or deleting files via phone nor via computer. Since phone does not want to boot as long as there is no free memory in internal storage, both options no longer work.
So this is why i came here, to Android experts. Now, i need a way to copy or delete files from the device while device is not booted. I know the exact paths to files to be moved to sd card, and there is only a few of them, so it can be done one by one by hand.
So, i can not boot the device, but i can turn it off, put it in recovery mode or put it in download mode. Whatever of those 3 is reqired. So, i do have the recovery, but it only offers to do factory reset, to format internal storage, to clean cache and to refresh Android without loosing data by downloading the latest firmware and installing it. The key word here is downloading, what is absolutely useless in case when the reason why phone needs to be recovered is 0 b low memory incident. So, this will not work. I can do factory reset, sure, but i would rather not to have to reinstall everything and set up phone all over again. Unfortunately, recovery does not offer any file manager.
So this is what i am seeking. Some file manager that can be run from recovery, that will enable me to move files to my sd card. Or, the preffered option, some computer program or console (terminal) utility that will act as file manager, that can operate on a device while it is in the download mode, recovery mode or while it is powered off.
Do you know of any such program and what do i need to do to move files to my sd card?
Thank you for any help.
Technically, Android Recovery Mode refers to a special bootable partition, which contains a recovery application - Android Recovery Mode menu - installed in it. A phone's Stock Android Recovery never offers you the option to deal with Android OS's filesystem because when being in Recovery Mode it's not mounted at all - but some Custom Android Recoveries may do.