I am a newbie and just bought my first PDA phone - O2 Atom
Trying to learn as much about it so that I can fully utilize it.
Reading the posts in this site is my first step.
I know this may sound stupid to the experienced users but
I've been reading posts asking about unlocking the Ext. Rom
What is the purpose of doing this ? What are the additional things I can do if I can unlock my ext. Rom vs just leaving the device "as is" ?
Anyone care to enlighten me ?
When you unlock the ext-rom you can see what's in it? Also you can turn it writeable, so you can do anything you like with it, make a copy of the content first. As it it persistent storage on most devices the content won't be erased by hard-reset.
On my magician for instances the ext-rom is concatenated to the internal storage folder enlarging it from 7 to 27MB.
Regards, M
Basically, the ext (extended) rom includes extra settings like operator network settings, extra operator programs and operator visual customisations. Really, if you are new to this, it is best to leave as-is, as unlocking only allows you to edit the Ext rom, which you will probs not want to do yet.
Thanks all for the info. I guess I need to find out more before I try this.
There seems to be 3 kinds of memory on my device:
1. Storage
2. Memory Card
3. Device (which itself seems to be broken into 2 ? One for programs and another for program storage ?)
One of the reasons I asked this question is because I encountered a low memory warning but when I checked the Settings/memory 1 & 2 still showed lots but on the General tab it showed Storage as .5KB left not sure how to interprete the info.
The memory on your device is called RAM & is devided dynamically, by the OS, in a storage & a program part. When you install programs Via Act.sync & choose default they end up in ram, program files folder, this will cost precious space to run an application. So try to install to SD or storage folder. that's why BS is nice. You can use cabinstl to choose where you want to install when you install a cab directly on your magician.
Got the idea
You mentioned the operator blah blah.. does that means that i can unlock my simcard by unlocking the ext rom?
no extented rom and sim locks are 2 different things
Actually, oltp is a bit mistaking in his description of the memory regarding your specific phone.
The Atom is Windows Mobile 5 device.
On WM 5 phones there are two physical types of memory:
RAM and FLASH.
Unlike in older models, on WM 5 the RAM also called 'program memory' is only used to run programs, just like RAM in your PC.
The ROM or flash memory (slower, but isn't erased when power is lost) is divided in to 3 partitions:
ROM / OS - locked partition where the operating system resides. Only special tools like ROM upgrade utilities can write to this section.
Ext ROM - a locked partition where the operator / vendor of the phone stores some extras which are automatically installed after hard reset. As you already know you can unlock it and use as regular storage. Any data stored there will not be erased during hard reset.
Storage memory - this is the part of internal memory (flash) where you can install apps and store your documents and other files. Just like a PC hard drive.
...
Is there a sticky or a thread somewhere about editing ROM/Ext.Rom?
Thank you.
It's all in the WiKi!
I did NOT (for example) changed/upgraded ROM. I just put new 2GB SD card and scanned some folder on it in Today Player for mp3s. It hanged. So I restarted it, aaaand I can't get to my phone at all
Sometimes it gave me message with something about Voice Commands (and hanged) and now it just hangs on Today screen - bottom "buttons" (Calendar/Contacts) aren't displayed on the screen, but everything else looks "proper". It just isn't reacting to _anything_ (I mean keyboard or touch-screen).
update1: I just noticed that Calendar and Contacts _do_ appear for less-than-a-second then disappear - and at this moment system gets unresponsive
update2: the message that sometimes appear is: "Voice Command has encountered a problem. Restart Voice Command and try again.". I googled for it but nothin helpful.
HELP!
Of course I will probably try to perform some ROM upgrade, but... (for various reasons - don't ask) ...I didn't perform any synchronization. Is there any way to backup data (most important being Contacts and SMSes) ..before performing any ROM upgrade (and assuming it will going to work)... ((
Funny thing is: I was postponing ROM update (from current 6.0) for some time, because I didn't want to loose any data...
Have you checked your battery?
Are you sure you flashed a ROM according to your RAM capacity? (128Mb or 64Mb)
Have you done a hard reset?
Please have a deep read here:
http://forum.xda-developers.com/showthread.php?t=549207 (post 2)
Hope it helped,
1. I did NOT flash the ROM. It happened "by itself". the only thing that I could suspect is TodayPlayer trying to read folders recursively and writing something in memory.. (some kind of buffer overflow?) ..damaging the content.
2. I don't want to loose my SMSes and Contacts, so I didn't try hard reset *yet*. It's the last resort and basicaly I would be willing to even desolder the memory to get the data from it - even loosing the phone. (yes. everyone -including me- will now say: if those data were so important - why didn't you made a backup? that's why I said in my post above: "don't ask")
Is there ANY way to get to those data from software that boots from SD card? I mean - when upgrading the ROM - is there any way to backup other-than-rom contents to SD card?
Sorry to ask a simple question, but can you connect via active sync, or is the system unresponsive to this too?
I don't know what 'Today Player' is, but it sounds like that it cached stuff to the main memory (maybe making a database of music files) and has filled it up without respecting to leave any memory for the OS to use.
no prob.
I tried that and apparently it freezes cold within that fraction of a second. computer reacts to "new device" but then ActiveSync hangs because it's already unresponsive...
THIS TOOL HAS BEEN DISCONTINUED. IF YOU REALLY NEED A LAGFIX, USE VOODOO. HOWEVER, WITH LATEST ROMS I DONT PERSONALLY FEEL A LAGFIX IS STILL NEEDED, THUS I DON'T USE ONE, AND WILL NOT CONTINUE DEVELOPING ONE
About
Here it is, yet another LagFix tool. It's certainly not the first, but it does offer some things others do not (at the time of this writing).
This patch uses the ext2/ext3 image in /data method.
IMPORTANT NOTICE FOR FROYO USERS
(1) Use ext2. ext3 is NOT supported on Froyo, only Eclair
(2) The installation will fail if you apps installed to SD. Go to Settings -> Applications -> Manage -> On SD card. Click each app and click "Move to phone". In the end, the "On SD card" list should be empty. Reboot. Install CFLagFix. When the fix is installed, you can move apps back to the SD card if you wish.
Features
- Lots of checks to make sure the fix is possible
- This is not just based on a script, but a lot of commands are performed and their results rigorously checked to be what is expected
- You can select (from a set of presets) which folders you want to lagfix
- You can select how big the image should be (between 128mb and all the free space in /data minus 250mb, to prevent low storage space warnings)
- The actual moving of data from RFS to the image is done in a boot loop, while the files are not in use. This minimizes the chance of corruption during move (settings being lost, etc)
- Comes with e2fsprogs, and e2fsck is performed each boot to fix a corrupted image
- Comes with it's own busybox, so no need to install it, and no chance for conflicts
- If an ext2 image is used, it is tuned to not reserve any blocks
- If an ext3 image is used, it is tuned to not reserve any blocks and use journalling
- Also moves databases (safely)
- Uninstall option
- Resize option, resize your partition whenever you want, to whatever (possible) size you want
- "Full automatic" option, this will max out the image size while still preventing the low storage space warning, and will also reclaim the space from the backup folders and automatically resize the image to max again after that space is reclaimed. This generally results in an image of about 1.5 GB. It'll also leave some space in case the system still needs to write in /data but not in the image.
- Progress monitor ("educated guess" about progress, not exact, but pretty close, usually!)
A fair number of these seem to be unique at the time of this writing.
Notes
- e2fsck result is stored in /data/cflf/e2fsck_result.txt
- list of mounted directories is stored in /data/cflf/mountlist.txt
- if ext3 is used /data/cflf/imageisext3 file will be present
- my own test rom is JM2+root-with-update.zip+ClockworkMod
Known issues
- In case the image is heavily corrupted, e2fsck may take longer to fix it than the rest of the boot process. Theoretically this could result in data loss
- ext3 does not seem to be supported on Froyo ROMs JP1/JP2/JP3
Credits
- mimocan, ykk_five, RyanZA, and all others who have chipped in for various lagfixes
- cynogen, e2fsprogs built for ARM
- kalpik, busybox APK
- ofcourse the original authors of those tools as well
- myself, this is all based on ADB Magic code
Donations
Please feel free to donate: http://www.jongma.org/dx.php
Requirements
- Windows
- Microsoft .Net 3.5 framework
- Phone in USB debugging mode
- SuperUser
Before using ...
I strongly recommend using ClockWorkMod and making a backup of your ROM. Just in case Also, during any operation, I advise having your phone hooked up so I can draw power from the computer.
Usage
- Unzip the attached file somewhere
- Make sure your phone is connected in USB debugging mode
- Make sure you have SuperUser installed
- Run CFLagFix.exe
There are three tabs:
Install LagFix
This tab allows you to install the LagFix, and lets you configure some options.
I recommand leaving the "Full automatic" option turned on, if you do, just press "Install !" and everything will be arranged for you. If you turn this option off, you can configure some settings manually, but note that using this does not reclaim wasted space of the backup files.
Note that you can still select to use ext3 instead of ext2, even if in "Full automatic" mode.
When you press "Install !", the program will be finished quickly, but your phone may continue working for 30 minutes or so, and keep rebooting very often. If you have a lot of data installed, it may take even longer.
Do NOT even touch your phone until Android boots up again!
A lot of things are checked before the install will start. You will need about 50% free in /data for the operation to work, but it will check this before making any modifications on your phone.
Resize Partition
This tab allows you to change the current ext2/ext3 partition size. The slider will only let you select values that are actually possible, i.e., bigger than your current data usage and smaller than the total space that could be occupied by the image.
Clicking "Resize !" will reboot your phone and resize the partition. Again, this can take an awfully long time! Don't panic, just wait it out.
Uninstall LagFix
This will uninstall the LagFix. It will completely remove it. Before removing it, however, it will move all files out of the image and back into the normal filesystem again, so no data is lost.
Clicking "Uninstall !" will reboot your phone and perform the uninstallation. Again, this can take an awfully long time! Don't panic, just wait it out.
Note that uninstallation will only work if you are using less than 50% of the device's capacity, but again the program will check this before making any modifications on your phone.
You can only uninstall installations of CFLagFix 1.20 and newer !!
BETA
This is very beta, use at your own risk!
WARNING
This patch is NOT compatible with ANY other lagfix tools. Either undo those completely, or just don't use this. If you were using one of those, I'd personally recommend a complete reflash of the firmware before using this patch.
WARNING #2
Before trying 1.80, please see this post.
Download
<< 1.70: 632
Changelogs
1.80, 15-08-10
- Redone some crucial parts of the patching procedure (for all install, resize and uninstall). Should fix all remaining issues!
1.70, 13-08-10
- Added /data/app-private/ folder
- Added progress monitor (estimates.... not exact)
- Moved /dbdata/databases to it's own partition, much faster for smaller read/writes
1.60, 12-08-10
- Updated codebase to ADB Magic 0.9, fixes issues with some weird pre-existing installations of busybox
1.50, 12-08-10
- Added "full auto" mode, "one click" solution for beginners
- Added ext3 support
- Added resize support
- Added uninstall support
- Fixed some issues
- Update scripts
1.20, 11-08-10
- Everything has been moved to /data/cflf/ , this - amongst other things - fixes issues with JP3
1.01, 11-08-10
- Adusted a permission error which could cause the system to be unable to create any new databases
Fix for 1.00 users: there isn't any yet. This is *beep* to fix manually. I would advise this "unpatch" method posted here: http://forum.xda-developers.com/showpost.php?p=7616676&postcount=29, then repatch with the latest version.
CFLagFix.exe doesn't even run for me.
"The application failed to initialize properly (0xc0000135). Click OK to termiate the application."
lyno said:
CFLagFix.exe doesn't even run for me.
"The application failed to initialize properly (0xc0000135). Click OK to termiate the application."
Click to expand...
Click to collapse
You sure you have MS .Net 3.5 framework installed ?
http://www.microsoft.com/downloads/...fd-ae52-4e35-b531-508d977d32a6&displaylang=en
The error message is a DLL initialization error... as CFLagFix doesn't explicitly use any DLLs, my guess would be the .Net framework.
Chainfire said:
You sure you have MS .Net 3.5 framework installed ?
http://www.microsoft.com/downloads/...fd-ae52-4e35-b531-508d977d32a6&displaylang=en
The error message is a DLL initialization error... as CFLagFix doesn't explicitly use any DLLs, my guess would be the .Net framework.
Click to expand...
Click to collapse
Ah yes! I removed all .net frameworks on this works laptop to be able to install some old COM files. Will re-install and test.
This looks so awesome! Thank you!
Any chance for open sourcing this?
installing now
Well im gonna give this a shot, have just installed the african jg8 and rooted,am doing this fix now.
Then ill try the 1.2 overclock on top, ill post a score shortly .
Not bad though i see one problem... it's windows only ^^
select which folders you want to lagfix
Click to expand...
Click to collapse
Sorry, bit of a noob here - what exactly do you mean by this? Why would we only want to 'lagfix' certain folders and not the whole thing?
just tried out your tool on my stock DXJF4 (with apps in it, not clean condition). With default size as well (around 1200 mb)
Actually I used mimocan's fix before but everything was wiped by mistake and everything went to default condition.
After the process finished, the Android displayed information about damaged internal SD, but everything was working. Is that expectable?
Now I got 2260 using Quadrant, leap from 1700 with mimocan's fix.
Nice job Chainfire!!
Can't wait to use JM2 / DDJG4
btw, can I post this on my blog?
:update :
whenever I open gallery, it always says no sdcard detected... do you know how to fix this? -> it doesn't recognize both my internal & external sd, but i can browse them properly in Estrongs/astro
veenone said:
After the process finished, the Android displayed information about damaged internal SD, but everything was working.?
Click to expand...
Click to collapse
That sounds scary, think I'll wait a while before trying!
RyanZA said:
This looks so awesome! Thank you!
Any chance for open sourcing this?
Click to expand...
Click to collapse
Not at the moment, but maybe in the future
Tayutama said:
Not bad though i see one problem... it's windows only ^^
Click to expand...
Click to collapse
Can't be helped. Not going to release a non-Windows versions. Perhaps wine/mono will make it work, though I doubt it
danamoult said:
Sorry, bit of a noob here - what exactly do you mean by this? Why would we only want to 'lagfix' certain folders and not the whole thing?
Click to expand...
Click to collapse
You can't really lagfix all folders, as the process where the image is mounted is run asynchronously with the rest of the boot process. There will be havoc if the system can't load certain files because the image is not mounted yet. This is why you can't just lagfix the entire system, but only certain parts.
In the presets I have only added those folders that I feel are mostly safe to lagfix AND would actually benefit the speed of the phone.
Also, for some folders there is some discussion to whether or not it is beneficial to have them in the image, like /dbdata/databases. I personally feel it should be lagfixed, but not everyone agrees.
veenone said:
just tried out your tool on my stock DXJF4 (with apps in it, not clean condition). With default size as well (around 1200 mb)
Actually I used mimocan's fix before but everything was wiped by mistake and everything went to default condition.
After the process finished, the Android displayed information about damaged internal SD, but everything was working. Is that expectable?
Now I got 2260 using Quadrant, leap from 1700 with mimocan's fix.
Nice job Chainfire!!
Can't wait to use JM2 / DDJG4
btw, can I post this on my blog?
Click to expand...
Click to collapse
I have not seen the "damaged internal SD" message before in any of my tests. It might be ROM specific (I'm personally using JM2). I would recommend rebooting (using the "hold power button + press power off" method) and see if the message still comes up. Let me know what happens.
And yes, feel free to post about it in your blog.
veenone said:
just tried out your tool on my stock DXJF4 (with apps in it, not clean condition). With default size as well (around 1200 mb)
Actually I used mimocan's fix before but everything was wiped by mistake and everything went to default condition.
After the process finished, the Android displayed information about damaged internal SD, but everything was working. Is that expectable?
Now I got 2260 using Quadrant, leap from 1700 with mimocan's fix.
Nice job Chainfire!!
Can't wait to use JM2 / DDJG4
btw, can I post this on my blog?
:update :
whenever I open gallery, it always says no sdcard detected... do you know how to fix this?
Click to expand...
Click to collapse
Replying to the same message again, hehe.
Now that I'm thinking about, how exactly did your device got wiped ? Anything less than an actual firmware flash does not completely remove mimocan's fix, AFAIK. To completely undo it you'd have to completely reflash (and get stock kernel back), and possibly remove the ext partition from your SD. In other words, if you "wiped" from recovery, this is not a removal of mimocan (AFAIK).
Gallery is working fine for me, by the way, and as stated above, I have not seen that message in my tests with JM2 (neither with a lot of apps installed nor a clean flash).
(Then again, this is the first release, so there might be issues )
Is it possible to do this onto an external SD card (provided one has one that is fast enough) so we do not risk any possible further damage to the internal card due to excessive IO.
I believe it would be quite difficult to replace the internal SD card, and in order to load custom roms (with update.zip) it must be mounted to the internal SD.
I'd much rather replace external SD cards if I had to choose between the internal and an external.
well everything was restored to factory state when I went to CSC menu. I think mimocan's fix also removed since I got 800 in quadrant score.
Update: after I rebooted the sgs for a couple times, now it recognize both sd cards.. weird.. But that's fine since the issue is solved now!
Daemos said:
Is it possible to do this onto an external SD card (provided one has one that is fast enough) so we do not risk any possible further damage to the internal card due to excessive IO.
I believe it would be quite difficult to replace the internal SD card, and in order to load custom roms (with update.zip) it must be mounted to the internal SD.
I'd much rather replace external SD cards if I had to choose between the internal and an external.
Click to expand...
Click to collapse
This fix is using exactly same space that is already reserved for user data and programs. And it is on the internal SD. So I really can't think how this fix could cause any damage at all. Thoughts?
I selected maximum Space, and now i have low internal memory. How to remove this fix or change the Space?
Daemos said:
Is it possible to do this onto an external SD card (provided one has one that is fast enough) so we do not risk any possible further damage to the internal card due to excessive IO.
I believe it would be quite difficult to replace the internal SD card, and in order to load custom roms (with update.zip) it must be mounted to the internal SD.
I'd much rather replace external SD cards if I had to choose between the internal and an external.
Click to expand...
Click to collapse
Use mimocan's fix if you want to use external SD - it is especially made for that! His thread is a sticky (at the top) in this forum.
veenone said:
well everything was restored to factory state when I went to CSC menu. I think mimocan's fix also removed since I got 800 in quadrant score.
Update: after I rebooted the sgs for a couple times, now it recognize both sd cards.. weird.. But that's fine since the issue is solved now!
Click to expand...
Click to collapse
Mimocan's fix uses Odin. Like update.zip's, a "factory reset" does not remove patches made in this way, only a real flash does.
Either way, happy to see your problem is solved
I think the problem was the system didn't mount sd cards properly after several boots from CFLagFix. So it needs more reboots to mount the sdcard with structure change properly...
Chainfire said:
Not at the moment, but maybe in the future
Can't be helped. Not going to release a non-Windows versions. Perhaps wine/mono will make it work, though I doubt it
Click to expand...
Click to collapse
It's a shame you can't open source this.
Personally, there is no way I'm going to run something like this without source - I believe you are just trying to help us out, but there is always the chance that you could be doing something damaging by mistake, or even installing a trojan on purpose.
I'll be following release though, looks awesome and hopefully you'll be able to open source this soon!
Good afternoon, dear xda-developers forum members.
I really hope to find some help here.
In last two months I had the following issues:
1. This one happened two times already: after using my phone as a flash in windows 7 and "safely removal" of it, all my applications which were installed on SD card were saying that "Application is no longer installed" when I tried to run it, although other documents and files were readable from ASTRO File Manager, i.e. SD card was mounted. In Settings->Applications all these applications had black icons with SD card image on it and rather with package name than regular application name(for example com.navitel instead of regular Navitel, etc.). I've restored all these applications from Titanium Backup, but I'm afraid that there is something more disappeared also which I don't know about.
2. My "Android" folder on sd card became a file with weird contents(this folder was used for NFS Shift data only). I couldn't restore it. Again: if this folder corrupted, then there is definitely something else also corrupted.
After I saw these things for the first time, I used Windows checkdisk with auto-fix errors. It found a lot of files and put it into "FOUND.000" directory. I recognized in these files few apk-files of installed applications from SD and also few images from my SD. Then I restored applications to SD card and for some time it seemed ok. But one time it happened again.
My assumption is that Android fails to re-mount SD card after I disconnect it from PC.
I don't know what to do... is it Android bug or is it Desire bug or what? I swear that I ALWAYS make "safe USB removal" in Windows before disconnect the USB-cable and I ALWAYS wait for the message "It's now safe to disconnect your device".
I'm very disappointed with all that Please, advise me something useful...
P.S.: If needed I can give you any debug information you want, I'm a programmer, so I've been around
You could try to format your SD card, just backup the contents first, see if that works. As for Android, it does a pretty good job of mounting straight after. What version of Android are you running?
GoogleJelly said:
You could try to format your SD card, just backup the contents first, see if that works. As for Android, it does a pretty good job of mounting straight after.
Click to expand...
Click to collapse
I will, but strange that it happened, because I formatted the flash before using it for the first time...
I have two assumptions:
Maybe I shouldn't press power button to switch the screen off just after disconnecting USB cable from PC. I was doing that as a habit, because every time you disconnect your phone from PC, the screen turns on.
Maybe I shouldn't try to run application which is installed on SD just after disconnecting phone from PC. Maybe I should have waited for a minute. I've tried to do it once, because I wanted to see the result as soon as possible, so the phone said that "Application is no longer installed", I though that Android haven't mount SD yet and tried later. It worked. But next time when I used USB cable, all SD-card apps became uninstalled.
GoogleJelly said:
What version of Android are you running?
Click to expand...
Click to collapse
I'm sorry, forgot to mention. I'm using HTC Desire with Android 2.2(2.10.405.2).
Fast Boot option may be the culprit
In case anyone checks this old thread...
CUT TO THE SOLUTION BELOW -- SEARCH FOR ////
Some (not all) of my apps moved to SD (all by Titanium Backup Pro) have begun to disappear and (sometimes) reappear without warning after I began to add and delete large Virtual Machines created in QEMU from my 16GB SanDisc class 10 microSD card on my HTC Droid Incredible running rooted stock Verizon Android Froyo 2.2.3. I know this thread is far from my phone's "home base", but from what I can tell this problem with disappearing apps located on an sdcard is NOT determined by hardware or even Android version.
I also happen to use LauncherPro by Federico Carnales instead of the built-in HTC Sense launcher. I noted elsewhere on XDA that a user had suggested that because at least some (maybe all) launchers start before the SD Card that this may be a problem, especially if changes are made to the sdcard that the launcher did not perform, or was not active during their performance by other apps such as Titanium Backup. That fits my situation, because I unmounted the SD, physically removed it to a PC, and added/deleted large VM files to save (lots) of time. No problems of this sort before I did this, so there must be some connection.
I noted that other users have tried reformatting SD, substituting different brands of SD, using newer/older SD etc. None of these reliably helped. So I skipped these options.
//// The (simple!) solution I tried that SEEMS to work (only time will tell!) is buried in the main Android Settings (accessed from the Menu button while in Home screen). Under "Applications" there is a setting "Fast Boot" that I checked long ago and forgot about (it seemed like a good thing to do at the time). The text warns "Turn off to use some Market apps" (that shows the age of my 2-yr old used phone and Android OS -- ohmygosh!-- because it refers to Market rather than Google Play Store!) Anyway, I unchecked the option and rebooted the phone.
Yes, it took a bit longer to boot (maybe a whole minute!), but after waiting about another minute ALL my home screen apps had normal icons and loaded properly. Titanium Backup Pro batch scenarios confirmed there were no apps in a forced uninstalled state (i.e. I had not done the deed, the system somehow had done it or at least rendered the apps "invisible" to Titanium, which decided they needed reinstallation).
The only odd behaviour was that auto brightness was turned off after I unchecked Fast Boot and rebooted. Going into Android Settings > Display and rechecking "auto brightness" took care of that. No other oddities or strange behaviours thus far (but it has only been about an hour).
I will report back here on this thread only (Samsung Fascinate > Fascinate Q&A > What just happend? apps on sdcard) if anything else requires reporting. Silence implies success!
link: http://forum.xda-developers.com/showthread.php?t=1873670
(I am copying this post to other relevant threads, but will not post anything further elsewhere -- only there. This is a bit arbitrary (although this thread appears to be the most recent active one on this topic), but I hope this approach pleases the XDA sysops/admins) :angel:
Hello,
I have an Oppo Find 7 for a while and I always thought that the Color OS is not very good, and specially, it comes with a very limiting partition division.
So, when I could no longer decide on which Apps to keep and which to uninstall, since I had no longer space left on my phone due to the stupid small partition for applications, I decided to format my phone, reconfigure the partitions and install a new ROM (CM 13).
I had done it often on my lapton, how difficult could it be to do it on the phone?
It all seemed to work fine, but when I started my "new" phone with CM I noticed that something was wrong. I tried to use the camera and it showed an error saying I did't have a storage device.
Well, I was sure I had left enough space for photos in the other (not OS) partition, and I had also the SD card.
I went to Settings->Storage and I saw that my phone was recognising the OS partition only (about half of all internal storage) and had a portable storage device called "sdcard0" (not the actual SD card) reading "Damaged" below.
I've tried to erase and format that partition, but it shows an error reading "command '41 volume partition disk: 179_0 public' failed with '400 41 Command failed'".
I've tried to rearrange the partitions again, to reinstall CM13, but nothing worked, so I just accepted that my phone could not take pictures. Everything that did't require to have a file system worked fine (well, I cannot see the naked ladies pictures my friends share on whatsapp). This was a few months ago, so I don't remember precisely what I did.
Recently I decided that I actually need a phone that takes pictures, so I went back to trying to fix it.
Unfortunately, I can't. At least without some custom help. I've read plenty of tutorials, forum pages, but there's always something that doesn't work in my case.
Here's what I can do with my phone:
- It boots
- It works
- Computer recognises it
- adb recognises
Here's what I can't do:
- Have any files (the file system is broken)
- Take photos
- Restart with bootloader - when I tried, the screen just shows a sitting penguin for a few seconds and then turns off. I do remember to be able to do so, but I can't now.
I've tried to load bootloader though the phone's interface, through the power+volume down button combination and through adb. They all had the same result. The stupid penguin and then darkness.
Can someone help me?
Hello, you're phone is not bricked. What is the exact name of you're ROM ? Do you have make LVM, or chinese storage partion?