Database Info

[Q] First time rooting.

Couldn't find a very clear tutorial anywhere, just a number of different threads saying different things lol. Anyways, need to know how to root my Droid Charge. Also need to know how to install CyanogenMod after.
I know rooting will void my warranty but I heard from a few people that if I unroot the phone, the warranty will be put back in place. Is this true?
If I somehow manage to brick my phone, I can always unbrick in most cases, correct?
Phone Info:
Hardware version - i510.06
Firmware version - 2.3.6
Kernel version - 2.6.35.7-EP4
Build number - SCH-I510.EP4
Not sure what information is important, but I believe it was mainly the kernel and Android version lol.
EDIT: Never mind about Cyanogen, I just want the best/fastest ROM I can get.

First things first. It's very difficult to hard brick this phone. I had to do a warranty return before and it is easy to go back to stock. If you get a soft brick, you can follow this thread and get it back to stock: http://forum.xda-developers.com/showthread.php?t=1111486
Next thing, you can't install CyanogenMod on this phone. We don't have any AOSP rom on this phone. All we have is repackaged stock roms.
As for how to root, it really depends on what you want. Do you just want root, or do you want a rom?

For right now, I just want to root. I've found out how to do that, kinda. I'm stuck now.
I'm trying to install imoseyon's kernel through CWM but I used the backup option before I installed the kernel. So now when I boot into recovery it oly gives me the optinos to "reboot system now", " apply update from sdcard", "wipe data/factory reset", and "wipe cache partition". I tried to apply update from sdcard and when I selected my kernel zip, it gives me back this:
"
-- Install /mnt/sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.

You need to reflash CWM.
CWM does not survive a reboot unless you're on a custom kernel, or root and remove the updater script. You have to flash CWM and immediately boot into it. If you let it boot up fully on the stock kernel, it will overwrite CWM with the stock recovery, so you'll have to flash it again, and immediately boot in and flash.

Will I keep the backup I made? Or should I just not worry about the backup and use Titanium?

It will keep the backup. It does the backup to SD, and the only folder on SD that CWM will touch in a wipe is .android_secure.

It worked. All rooted, thank you. Any suggestions for themes, apps to get, or ROMs?

ratchetlock2 said:
It worked. All rooted, thank you. Any suggestions for themes, apps to get, or ROMs?
Click to expand...
Click to collapse
The two most are using are TweakStock and Infinity. I strayed but came back to
TweakStock. Dont think it has a true theme available yet but you could atleast do something like Go launcher or something. With Ifininity there is a theme available. Read about both in the Dev section then decide.

Will do. Any OCable kernels yet? Saw someone post on here that there wasn't any yet.

ratchetlock2 said:
Will do. Any OCable kernels yet? Saw someone post on here that there wasn't any yet.
Click to expand...
Click to collapse
No custom kernels at all, other than repackaged stock kernels, but Tegrak Overclock works with any GB kernel. The free version only lets you change clock speeds. The pay version lets you change voltages as well, and lets you apply at boot.

Uh oh, got stuck in an infinite reboot loop. Tried turning my phone on only to come up to the first Samsung post screen, goes to black eventually for a little bit, then goes right back to the Samsung screen. How do I fix it? Can't find a solid answer.
I went into CWM and tried to restore a backup but it said it was missing the MD5 file or something; can't remember what exactly the error was with the restore. I'll try reflashing CWM soon.

Now I can't do anything... Can't put phone in DL mode, recovery, nothing. Won't even say it's charging.
I'm still under warranty, I'm considering bringing it in and saying I need a replacement because I know they won't be able to fix this on the spot.
EDIT: Got into DL mode luckily and I'm getting into DL mode smoothly now. But I still can't power on or get into recovery...
EDIT2: Using this thread to try and fix my problem. http://forum.xda-developers.com/showthread.php?t=1111486
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Are these the right settings?
Trying to odin this file: http://forum.xda-developers.com/showthread.php?t=1172182
EDIT3: What a headache... Fully back to stock now. Going to try and restore everything that I backed up onto my SD card.

Are you leaving in the battery while flashing?
Sent from my SCH-I510 using xda premium

Nope.
numberfix

ratchetlock2 said:
Nope.
numberfix
Click to expand...
Click to collapse
There's your problem. Once you're in download mode and detected by Odin, pop the battery back in.
Sent from my SCH-I510 using xda premium

[Q] Rooted Droid 2 Global issues

So I recently bought a Droid 2 Global off of ebay. I got the phone and it was relatively fine. It came with the android 2.3.3 system. I decided that I want to flash cyanogenmod onto it. I rooted it and that went fine. I then attempted to open up the cyanogenmod from clockworkmod recovery. This didnt work. I kept getting an error message. So I gave up and did a factory reset and wiped everything. Unfortunately this solved none of my problems. The phone would boot up only to get stuck at the motorola "m". I couldnt go into either the stock recovery or the clockworckmod. I thought maybe if I pull the battery, my sd card, and the sim card things would get better. Nope. The phone wouldnt even turn on after that. Maybe its a battery issue? I let it charge in the wall charger all night. Currently its on only when plugged into the wall and is still stuck at the "m".
I have no idea what to do anymore. Any help would be appreciated!!

reanjo said:
So I recently bought a Droid 2 Global off of ebay. I got the phone and it was relatively fine. It came with the android 2.3.3 system. I decided that I want to flash cyanogenmod onto it. I rooted it and that went fine. I then attempted to open up the cyanogenmod from clockworkmod recovery. This didnt work. I kept getting an error message. So I gave up and did a factory reset and wiped everything. Unfortunately this solved none of my problems. The phone would boot up only to get stuck at the motorola "m". I couldnt go into either the stock recovery or the clockworckmod. I thought maybe if I pull the battery, my sd card, and the sim card things would get better. Nope. The phone wouldnt even turn on after that. Maybe its a battery issue? I let it charge in the wall charger all night. Currently its on only when plugged into the wall and is still stuck at the "m".
I have no idea what to do anymore. Any help would be appreciated!!
Click to expand...
Click to collapse
Have you heard of "sbf" ing?
I'll try to find a link...
SBFing allows you to install a complete stock firmware image - should fix those problems. Factory data resetting only deletes all of your data (everything past the /data partition)
Your android system (OS, firmware, etc, etc) is in the /system partition
If you got an error while installing CM, you may have put it into a bootloop - depending on where the error was at. Installing a rom starts by formatting the /system partition, then copies the CM version of /system from the zip file. If you got an error after the format, then you don't have an os to boot from. Also that means your recovery is gone. That means your only choice is an SBF. (what you did is commonly called soft-bricking)
(any mods/devs may correct me as needed but I'm fairly sure this is right...
---------- Post added at 01:31 AM ---------- Previous post was at 01:09 AM ----------
Links can be found on a text file on my website. It's at ftp:// kd8rho (dot) net (slash) factory_reset_links.txt
I can't post links, so that's what I have to do... I hate these new member restrictions!
Link for rsdLite: link 1 on the text file
rsdLite is the program you need to use to sbf back to stock.
They have instructions on there, but you need to use the sbf file found at link 2 on the text file, instead of the one on their page.
Instructions:
Download rsdLite.
Install rsdLite
download the sbf file above (NOT THE ONE ON CYANOGENMOD'S SITE!!!!!)
use the instructions to flash the SBF
If you get an error or can't flash, follow the instructions on link 3 on the text file

if your phone is stuck at the m
most likely not charging
if battery gets too low, it will be unusable
try ezSBF
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
also lots of links sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
Sent from my DROID X2 using xda premium

Reference the DROID Wiki for instructions on re-flashing stock firmware and information about the different firmware versions available. Note that if your phone has ever had the newest firmware version installed (4.5.629/Android 2.3.4) it will not boot after flashing any older version.
If you are able to boot into ClockworkMod Recovery, you may still be able to flash CyanogenMod without first re-flashing a stock firmware. Be sure to select a CM build based on the same kernel version as the one installed on your phone (if your Motorola "M" logo during boot is red, you have a Gingerbread kernel; if it's white/silver, you have a Froyo kernel). Official builds of CM target the Froyo kernel only; unofficial builds work with the Gingerbread kernel and are generally better-adapted to the specific model handset you're using. Look in other threads on this forum or on RootzWiki for information on and download links for unofficial builds.

Help needed - Stock Firmware reinstallation via KIES caused Boot Loop

Hi guys.
I have a little problem with my tab now . Originally my machine had a little hiccup ever since I upgraded to Lollipop. The problem was that it tried to upgrade apps to Lollipop every time I did a boot cycle. Usually ending with a message that an app called "a...a" closed. I did not bother me much for a while. But Today I thought it was past time I resolved this so I tired to reinstall the firmware with Kies. Bad idea in retrospect, since it caused a boot loop at first (I did not touch it for 1-2 hour) than after seeing that it did not progressed. I tired a forced restart by holding down the power button. Strangely somehow after 2 or 3 tries it did started to do something. Saying that it has to update 190 apps and it did so, after then I found myself at the first setup page. However it did not worked because a lot of warnings come up constantly like: google process stopped, maps stopped, etc... making it unusable to set up anything, since even if you OK the warning the next comes up constantly. Also Kies no longer detects the phone, so I was forced to use Odin to reflash it. But here's the twist: even after reinstalling the same version of the stock image via Odin the continuous boot loop occurs again and again. (The image I got it from samdownloads de). I'm unsure where the problem can be, the only thing I can suspect is that I only used AP with Odin since the rar did not contain any bl cp csc or anything (I also tired full wipe via recovery but it did not help). So if anybody have any idea as to what direction should I take, please say so. I would really appreciate the guidance.
Disclaimer: My machine is completely stock with an untripped Knox, and it was bought from Germany.

quarros said:
Hi guys.
Disclaimer: My machine is completely stock with an untripped Knox, and it was bought from Germany.
Click to expand...
Click to collapse
Try to flash your AP file with Bootloader
http://forum.xda-developers.com/showpost.php?p=62573251&postcount=21

Beut said:
Try to flash your AP file with Bootloader
http://forum.xda-developers.com/showpost.php?p=62573251&postcount=21
Click to expand...
Click to collapse
Thanks for the tip. My problem is that I don't know how different region Bootloader relates to my machine.
The linked one is for the US version of the machine. And I'm unsure whether flashing a different region's
ROM trips the Knox or was there any difference in hardware between units sold to different region
(seems very unlikely but not impossible). My tablet is from Germany with the DBT region firmware.
So is it right to mix the two parts together?

quarros said:
Thanks for the tip. My problem is that I don't know how different region Bootloader relates to my machine.
The linked one is for the US version of the machine. And I'm unsure whether flashing a different region's
ROM trips the Knox or was there any difference in hardware between units sold to different region
(seems very unlikely but not impossible). My tablet is from Germany with the DBT region firmware.
So is it right to mix the two parts together?
Click to expand...
Click to collapse
There is no problem as all region is the same hardware, the one sold in Europe has no different than a tablet sold in US.
For example, software for UK has more languages than US, the rest is the same. I used to load UK or Korean version for the US tablet to fix Bluetooth issue, go back and forth Kitkat and Lollilop without tripping Knox as the firmware is official.
Like this one, I loaded Korean firmware to an US tablet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Beut said:
There is no problem as all region is the same hardware, the one sold in Europe has no different than a tablet sold in US.
For example, software for UK has more languages than US, the rest is the same. I used to load UK or Korean version for the US tablet to fix Bluetooth issue, go back and forth Kitkat and Lollilop without tripping Knox as the firmware is official.
Like this one, I loaded Korean firmware to an US tablet
Click to expand...
Click to collapse
Thank you so much for the info I'm sure it will come handy later on (Probably I wont be so nervous to install custom rom next time). :good:
Thankfully it is now solved even without flashing a new bootloader.
For future reference here is what I did:
I used a different freshly installed computer with Windows 7 to flash it.
I also downloaded Odin version 3.10.7 form the forum (I previously used 3.09, also downloaded from here)
I started up the Tab booting to recovery (p + home + volume up). Erased data and wiped cash.
Than immediately rebooted to Odin mode (p + home +volume down) as to not let anything written to the previously wiped partitions.
Than with Odin I reflashed it with the previously downloaded firmware I got from samdownloads de (P900XXU0BOI1_P900DBT0BOH1_HOME)
All seems working properly now. And the initial problem also went away.
Thanks again

quarros said:
Thank you so much for the info I'm sure it will come handy later on (Probably I wont be so nervous to install custom rom next time). :good:
Thankfully it is now solved even without flashing a new bootloader.
For future reference here is what I did:
I used a different freshly installed computer with Windows 7 to flash it.
I also downloaded Odin version 3.10.7 form the forum (I previously used 3.09, also downloaded from here)
I started up the Tab booting to recovery (p + home + volume up). Erased data and wiped cash.
Than immediately rebooted to Odin mode (p + home +volume down) as to not let anything written to the previously wiped partitions.
Than with Odin I reflashed it with the previously downloaded firmware I got from samdownloads de (P900XXU0BOI1_P900DBT0BOH1_HOME)
All seems working properly now. And the initial problem also went away.
Thanks again
Click to expand...
Click to collapse
From my experiences, these things have nothing to do with flashing a firmware:
1- Fresh installed windows, I use XP or Windows 7, there is nothing different as long as you have correct Samsung USB driver.
2- Odin versions have no differences, I use old or new, they are both the same.
3- Home button is not needed to access Download or Recovery Mode
Your problem went away probably from fresh install of the system.

Please help me! Freshly softbricked SGS7, SM-G930W8, No OS Installed

I have tried goddamn near everything and lurked everywhere.
This is just me trying to fix a huge mistake. I got this phone yesterday, everything was fine. I just wanted to install a custom recovery so I could back up the phone.
I flashed TWRP with Odin, I may have done it wrong or something... But I'm pretty sure I followed some directions. Odin did it in a snap, my device rebooted into TWRP... but then, I just barely noticed the "No OS installed!" message.
I have attempted, in no particular order:
- Using Kies 3 to initialize my device. It will download to 100% and then stick on 0% going to install the OS. Tells me the device is not supported.
- I then tried SmartSwitch because someone told me that's what you need for Android 4.3+. Same exact thing.
- Tried flashing my stock firmware, both 6.0.1 that it came with and the 7.0 that was available before it was bricked, with Odin 13.2 (I also tried others)
What's interesting here is when I add in the AP, BL, CP and HOME_CSC and press start, I get Odin's log to fail just after cm.bin - every time.
Here is a screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
At that point, I am no longer able to re-attempt until I restart and re-enter DL mode, and a black-backgrounded red text appears on the Download Mode screen, that says:
SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1
My device is the Canadian version, in the XAC region.
I have downloaded and attempted flashing firmwares G930W8VLU2BQB6_G930W8OYA2BQB6_XAC and G930W8VLU1APG1_G930W8OYA1APG1_XAC.
Both give the exact same errors and so I don't think the firmwares I got are the issue. I just have no idea what it could be, since the only problem with my phone is there's no OS installed.
Actually, I do have a problem with TWRP, as well.
TWRP is unable to do much. It cannot mount /data (among others), and those folders are all still there as I can adb push files to the device, and I attempted pushing the actual firmware to the /data folder and I could see the progress by pressing Install in TWRP and then looking in the /data folder... but that was the only file that told me "No space left on device" once it 100% completed, when there's obviously ~30GB.
The first error TWRP gives is that it cannot find the crypto footer.
Am I screwed here? Is this a harder softbrick? What am I missing? Please reply quickly, working by tomorrow would be very ideal.
Thanks in advance!

The last time I tried to flash stock - I got errors in Odin. Disconnected phone, restarted download mode and tried again. Don't know why but it took four tries before flashing complete - good luck
Sent from my SM-G930W8 using Tapatalk

bill_in_mtl said:
The last time I tried to flash stock - I got errors in Odin. Disconnected phone, restarted download mode and tried again. Don't know why but it took four tries before flashing complete - good luck
Sent from my SM-G930W8 using Tapatalk
Click to expand...
Click to collapse
I tried many more than four times. Should I be using CSC rather than HOME_CSC, just to wipe everything and maybe that'll work?
You say you got 'errors' in Odin, but it's always different for a different cause. You didn't get an error before cm.bin, did you?
EDIT: Attempting CSC rather than HOME_CSC for both v7 and v6 firmwares.
UPDATE: Ugh... I guess it's not the same every time. Using CSC with the Marshmallow md5s, I got Odin to err earlier this time, before even getting to cm.bin!:
UPDATE2: I have just tried flashing Nougat with Odin, using CSC instead of HOME_CSC, and IT'S WORKING??? WTF. Got past recovery, now going through system... Perhaps I posted too soon? Sorry for wasting anyone's time. I will update this thread if it doesn't work.
I'd say this thread isn't worth deletion because I think somebody could come by, take this information and help themselves with it.

I had similar issue - error would be different with every attempt until finally it just flashed and passed. Glad you got it working .
sent from SGH-1337M using Tapatalk

Yeah, that's the thing though... With this one, I got the same error no matter how many times I tried one specific way.
I suppose just never attempted the 7.0 firmware with CSC instead of HOME_CSC. Thanks anyway

Question Massive system storage use on Stock OnePlus 9 5G

Hey everyone. I've been looking through Forum posts everywhere and can't seem to see anything recent concerning this issue that actually solves it.
My system data is taking up an extremely abnormal amount of space. So much so that I have to routinely prune my already limited photo, video, and file storage or my device runs out of space to store temp and application files. Has anyone found a decent way to fix this outside of starting from scratch?
I have a stock OnePlus 9 5G running Android 12 (LE2115_11C.48), tho it had been an ongoing issue since before Android 12...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

It seems like a known issue that has no resolution but factory reset and switch to a non-OOS ROM.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
There is some suggestion that it's dump files being constantly created.

Hmmm... Do you know if root is possible without factory reset? I bet I could find the problem files pretty quick if I could get access to those files.

dallen.baldwin said:
Hmmm... Do you know if root is possible without factory reset? I bet I could find the problem files pretty quick if I could get access to those files.
Click to expand...
Click to collapse
Not that I'm aware of. Temp root exploits are closed pretty quickly once discovered and the act of unlocking the bootloader causing the phone to be wiped is a security mechanism since having an unlocked bootloader could potentially give way to an easier method of extracting your data off of the device.

until support arrives, there's no choice but to reset and reinstall OS.
the problem with the other option of using a custom OS is kinda scary.
because installing/using a custom OS is no longer as straight forward as previous like in oneplus 3t.

jmadiaga said:
until support arrives, there's no choice but to reset and reinstall OS.
the problem with the other option of using a custom OS is kinda scary.
because installing/using a custom OS is no longer as straight forward as previous like in oneplus 3t.
Click to expand...
Click to collapse
What's scary about it? It's really not that bad as long as you read the instructions. I have flashed this thing 3 or 4 times now and it's no worse than any other phone I have ever had.

That's good to know. I previously had a Xiaomi Mi Mix 3 (may it rest in peace) and ran several custom ROMs on it before its untimely demise. I imagine the process on this device is equally nerve wracking the first couple of times and totally normal afterwards.
Any suggestions while we're on the topic?

dallen.baldwin said:
That's good to know. I previously had a Xiaomi Mi Mix 3 (may it rest in peace) and ran several custom ROMs on it before its untimely demise. I imagine the process on this device is equally nerve wracking the first couple of times and totally normal afterwards.
Any suggestions while we're on the topic?
Click to expand...
Click to collapse
If you can type fastboot commands into command prompt, it's really not that difficult. I actually often found flashing with TWRP to be more irritating because of weird errors and sometimes it would refuse to factory reset and make a really big mess for me.
Now you just download the ROM and the recommended recovery, flash the recovery, boot to recovery, flash ROM, and you're done. Obviously read each ROM's instructions though because some like StagOS require you to do other stuff (you have to flash a partition file with that one).
I personally recommend StagOS. The only thing I found wrong with it was that it didn't support Verizon (no signal with a Verizon network SIM) but the dev is working on that and the fingerprint sensor icon wasn't lined up properly which apparently not everyone had that problem. I have tried a few others and had different issues with each of them. Derpfest is pretty good too but sometimes my apps act like I have never run them and I had a weird crash when swiping down on the status bar earlier. I plan to go back to StagOS. In fact, I am going to just go ahead and do that right now.
If you want to save yourself some annoyance, if the phone doesn't have OOS 12 on it when you get it, don't flash it to OOS 12 or you'll have to downgrade it to make sure you have a firmware match.

Dang.. I thi k I already went to OOS 12 since I'm on Android 12

dallen.baldwin said:
Dang.. I thi k I already went to OOS 12 since I'm on Android 12
Click to expand...
Click to collapse
Yep, you definitely did. The easiest way to get back to being ready IMO is to run the global MSM tool to get back to OOS 11, then when that's done, unlock the bootloader (make sure you do it in this order, I had my phone refuse to boot twice when I unlocked the bootloader after installing 11.2.10.10), then when the phone has booted back up, install 11.2.10.10 OTA for global (it's in the pinned update post), then you're ready for custom ROMs.

EtherealRemnant said:
Yep, you definitely did. The easiest way to get back to being ready IMO is to run the global MSM tool to get back to OOS 11, then when that's done, unlock the bootloader (make sure you do it in this order, I had my phone refuse to boot twice when I unlocked the bootloader after installing 11.2.10.10), then when the phone has booted back up, install 11.2.10.10 OTA for global (it's in the pinned update post), then you're ready for custom ROMs.
Click to expand...
Click to collapse
When you go back to os 11 you will experience duplicate media storage issue.. I just flashed os13 stable currently shows 7GB of data on ' others ' , don't know if will continue grow..keep my eye peeled..