The issue:
I upgraded to Jelly Bean 4.1.2. Eventually (within hours) I was unable to open the Gallery to view photos; the error message: "Not enough space. Delete unnecessary items such as downloaded software, pictures, videos and documents"; screen shots cannot be saved to the internal memory; images from within MMS messages cannot be viewed; neither Kies or TitaniumPro will allow me to perform a backup.
After attempting to "Clear data" (successful) and "Clear cache" (unsuccessful; cache remains full after hitting radio button) from Application Manager --> All --> Gallery, I noticed that my cache supposedly contains 88.17GB of data, which is WAY more storage than my phone has available. I went searching for these files, and their location is /sdcard/Android/data/com.sec.androud.gallery3d/cache.
Assumptions (and we all know what those do...):
-If I'm able to delete these files, it will solve the aforementioned issues.
-This is as a result of the auto-syncing of photos within my Google account; I believe this is supported by the fact that I was initially able to open the gallery post-update, but as the files continued to sync and the cache got too large, it disallowed my opening of the gallery.
-Other folks have had similar issues, and a factory reset did not resolve their problem (so it won't resolve mine).
Attempted fixes:
-I disabled syncing Picasa and photo albums from my Google account.
-In addition to the offending files (a parent folder and files named with symbol/wingding characters; many of the files supposedly contain 3.5GB worth of data... totaling the 88+GB of data), I was unable to delete anything from within the cache folder (which included Picasa folders) in MyFiles. As a result, I rooted my phone with Framaroot 1.6.0, enabled Root Explorer in ES File Explorer and changed all the permissions available to RW and restarted the phone. The files still "cannot be deleted".
Please help.
Phone info:
Samsung Galaxy SII i777
Android version 4.1.2
Baseband version I777UCMD8
I don't want to make any assumptions before I offer suggestions. So...
Did you upgrade via Kies?
What kind of experience do you have modifying phones, if any?
creepyncrawly said:
Did you upgrade via Kies?
What kind of experience do you have modifying phones, if any?
Click to expand...
Click to collapse
I did upgrade via Kies. I've little experience modifying phones, but I'm willing to put in a little leg-work to figure out how. If I could save my SMS/MMS messages and phone log in this process, that'd be great. That said, I'd rather put off buying a new phone, so I can live with it if I lose the data.
I'm not sure what went wrong with the Kies update, but as far as I know, there is no easy way to correct the problem. Actually, most of the people who frequent this forum are using custom firmware, rather than stock. In general, when things go wrong with a flash, (or update in your case), it is much easier to just re-flash. Of course, if you are an experienced developer, you can look at the log files and determine what went wrong, but even then fixing it is questionable.
You will most likely find that if you perform a wipe data/factory reset in 3e recovery and then perform a fresh Odin install of the firmware, you will have no problems. You can stay with the stock 4.1.2 UCMD8 firmware, or you can install the custom firmware of your choice. If you opt for custom firmware, there are a number of choices. Since you are accustomed to running stock, you may be more comfortable with a rom that uses Samsung Touchwiz as a base rather than one that is based on the Android Open Source Project (AOSP). I run SHOstock3 which is modified from the latest Samsung firmware for the International SGSII and is also 4.1.2 based. It is extremely stable and has many many features that you do not have with stock.
Since you are rooted, you should install Titanium Backup and do a complete backup of all your applications in it. You will then be able to restore application data so that you don't lose anything. With it you can also restore your SMS & MMS messages, and possibly wifi access points, call logs, and bookmarks of the stock browser. I'm not sure about the last three if you would be changing to a different base. I think the call log would restore from stock to SHOstock3 since they are similar applications.
If you will be flashing firmware in the future, you should consider purchasing Titanium Backup Pro, which gives you batch restore along with some other features. It is very tedious restoring things one application at a time.
Also, before you wipe and re-flash firmware, you could first install a custom kernel and do a nandroid backup. Titanium Backup will read and can restore things selectively from a nandroid backup so you would have access later to additional items if you need them.
Hope that's helpful and if you have any questions, just ask. You can find a lot of resources in my signature, including a link to the Download Repository.
Oh, and the call log is not your address book. Titanium Backup will not restore that, but you can save it in Google and restore it from Google which is what most people do, or I believe you can find a stand alone backup program for it.
Simple Solution:
1. Download your current ROM .zip file -- in my case ShoStock3 4.0 zip
2. Reboot into Recovery Mode
3. Locate your zip file -- in my case extSD card
4. Run your ROM .zip file -- no need to do a full wipe or anything.. Just run the zip file
5. Reboot once the installation finishes
6. ENJOY!
YEAH! to my first post!
Related
Hi,
I'm sorry if I'm asking something that has been asked a thousand times before, but I can't seem to find a satisfying answer..
At this moment my S3 is running on standard Samsung firmware that I have rooted with Samsung GS3 ToolKit v3.0.
I think I read somewhere that it is advisable to make a backup of some certain parts of your phone, copy the ROM to your phone (I want to install CM9) and reboot your phone with the button combination (home, vol up, pwr) to get it in CWM mode(?).. Then you have to erase something, I think.. and choose the .zip that you've copied to the phone.
Now the next thing that I can't quite figure out, what will happen to all my settings? Like the Wi-Fi networks from friends that I have saved and conversations in Whatsapp.. Will I lose all of that? Or is there a way to save that (with Titanium Backup? although I'm not quite sure what to choose there..)
Can someone tell me if I'm somewhat in the right direction? Or maybe tell me what forum post I should take a look at to get all of this figured out..
Thanks!!
rioohhh said:
Hi,
I'm sorry if I'm asking something that has been asked a thousand times before, but I can't seem to find a satisfying answer..
At this moment my S3 is running on standard Samsung firmware that I have rooted with Samsung GS3 ToolKit v3.0.
I think I read somewhere that it is advisable to make a backup of some certain parts of your phone, copy the ROM to your phone (I want to install CM9) and reboot your phone with the button combination (home, vol up, pwr) to get it in CWM mode(?).. Then you have to erase something, I think.. and choose the .zip that you've copied to the phone.
Now the next thing that I can't quite figure out, what will happen to all my settings? Like the Wi-Fi networks from friends that I have saved and conversations in Whatsapp.. Will I lose all of that? Or is there a way to save that (with Titanium Backup? although I'm not quite sure what to choose there..)
Can someone tell me if I'm somewhat in the right direction? Or maybe tell me what forum post I should take a look at to get all of this figured out..
Thanks!!
Click to expand...
Click to collapse
If you have an International S3 and NOT a US model just:
- Download and install the latest CF Root by Chainfire with Odin v3 3.0.4 (you now have root + busybox + cwm)
- Make a nandroid backup in cwm
- Download the latest CM9 nightly + gapps
- Copy them to you internal memory card
- Go into recovery and wipe cache/dalvik cache, data/factory reset and format system in mounts and storage
- Flash the nightly and straight after that gapps
- Fix permissions and then Reboot.
You can generally backup and restore any apps you installed via Titanium. No sytsem apps though, they are known to have issues.
Then use "sms backup+" to safely store your Sms and call log on Gmail.
Make sure you ticked Sync settings for Contacs in your Google account and also ticked to backup your phone data to Google (that will backup your wifi passwords too)
Use an app to backup efs or do it manually through Shell.
Now, download Cm9 + Gapps and optionally eg Siyahkernel, put them in an easily accessible folder on your storage (i call it Ainstall since it will be in the top of the directory listing)
If you're on an older baseband (radio), get DXLF3 modem too.
Reboot in CWM and install cm9 - (siyah) - gapps in that order.
Without leaving recovery, factory-reset your phone. Reboot and enjoy.
Restore your data with the same apps you used for backup (obviously). Again, do not attempt to restore system apps.
Sent from my GT-I9300 using xda premium
(unfinished!)
Gobbledygook and what it means
ROM
A package including the operating system (Android) and pre-installed apps and configuration. There are 3 types of ROM's:
Original:
The ones released by Samsung. They can be downloaded on http://samfirmware.com and are flashed through Odin.
Sammy-based:
ROM's that have been altered, tweaked, enhanced, modified but are based on an Original Rom.
A list of Sammy-based ROM's can be found here: http://forum.xda-developers.com/showpost.php?p=26583587&postcount=1
AOSP-based:
These ROM's have been built from the official Google Android sources without any carrier-interference. Cyanogenmod is among these.
Here's a list of those: http://forum.xda-developers.com/showpost.php?p=27583422&postcount=2
FD / Fast Dormancy
Fast Dormance. usually shortened FD or depending on the technology NCFD for network controlled fast dormancy, is a protocol between your phone and the network which basically allows it to suspend the data connection when it's not used to save battery and resources.
Here's a description: http://galaxy551.wordpress.com/2011/09/05/fast-dormancy-and-battery/
Modem or Radio
The modem, also called radio or baseband processor, is the system within your phone which is responsible for all cellular activity, be it data transfer, calls, ... and their corresponding low-level parts. It has it's completely own operating system (firmware), which is usually called 'modem' for short. Depending on the carrier and locations, different modems have a better stability and/or data throughput than others. The best ones are often not the one destined for your region.
Modems for the S3 are not compatible with all ROM's, a list of modems and some hints can be found here
Root
Rooting is the procedure of gaining root (=privileged, "admin") access to your phone. Pure rooting consists of only minor changes to the original ROM and neither causes data loss nor is it risky when following step-by-step instructions. It allows to control your device's behaviour in all regards. Rooting is considered to void warranty (although that may not be entirely correct)
EFS
EFS is a partition on your phone which contains the ONLY data that will cause your phone to be unusuable if lost or corrupted.
It includes your MAC addresses (Machine adress code) which is a unique identifier for all Bluetooth and (W)Lan devices aswell as your IMEI (basically the same as MAC but for mobile networks). Loosing/corrupting your IMEI causes the device to no longer be accepted by your operator . There is no known successful way to restore the IMEI other than sending it in for (paid) repair through Samsung customer service.
A backup is highly recommended if your device is rooted. Refer to "How do I backup my EFS" below.
CWM
ClockWorkMod (CWM) is an aftermarket recovery with extended functionality and the ability to flash non-Samsung Update files.
It's usually used for Nandroid backups, updating custom ROM's and flashing tweaks/features to a Rom.
However it also includes an ADB console to recover from issues and run commands on the system.
Most custom kernels include a copy of CWM.
Odin/Heimdall
Odin (Windows-only) and Heimdall (Windows, Mac, Linux) are tools which allow you to use the factory ROM-flashing system to update and replace the firmware or parts of your phone. It can also be used to recover the phone from bad flashes if it does not go to Recovery mode again.
ADB
Android Debug Bridge is a tool allowing you to execute commands and send/receive files of an USB-attached Android phone from your computer. It requires "USB Debugging" to be enabled in the Settings->'Developer options' of your phone.
It's usually used to test apps or send commands to the phone's command line.
A copy of ADB is attached to the post. To install it, copy the contents of adb.zip into C:\Windows and open a Dos Promt (cmd). Then type 'adb shell' to gain command-line access to your phone.
About upgrades and Updates
When will I get an update?
Official OTA updates are often delayed or not released at all for certain countries, regions. Additionally, carrier-branded ROM's are usually
further delayed by the carrier himself. See "How can I manually update"
Is the update Jellybean?
No. Jellybean is'nt out for probably a couple of months. However that doesn't mean you shouldn't install the upgrade since they often contain important bugfixes and tweaks.
How can I manually update?
You want that new ROM but it's (not yet) released for your country or region? No worry! Head over to http://samfirmware.com and get the ROM of your choice (within the Samsung Galaxy S3 i9300 range of course). Then flash it through Odin. It will not cause data loss and upgrading (newer Version) should always go painlessly, downgrading may need a factory-reset (=data loss).
About flashing in general
How do I access download / recovery mode?
Recovery mode
Make sure your phone is powered off and not plugged in
Press and hold Volume-Up and Home button.
Press Power-button until the Logo appears
Release Power-button but keep the other 2 pressed.
Repeat if it does not work. If it still does not work, remove the battery for 1-2 minutes and try again.
Download mode
Same steps as 'recovery mode' but replace 'Volume-Up' with 'Volume-Down'.
What is a JIG
A jig is a little (and very cheap, +- 2$) electronic component in form of a microUSB-plug helping you to access download-mode when it either turns on but does not go to Download/ Recovery mode or does not react at all. Upon plug-in the phone will start in download mode, allowing it to be fixed.
Do I need a backup
If you ask, you probably don't have any. Neither Titanium Backup, nor CWM. It's highly recommended since, according to Murphy's law, "what can go wrong, will go wrong". Don't blame other users if you don't have any ready and you lost everything you stored on the phone!
It's probably a good idea to always store backups on the external SD card (if any is present).
See "How can I make a backup" for further info.
How can I make a backup
There are 2 possibilities:
Full-backups (aka Nandroid)
These are capable of restoring your entire phone including the ROM, configuration, apps, data, ... exactly as it was at the time of the backup.
Nandroid backups can be created and restored through the 'Backup & Restore' menu in CWM.
Partial backups (for ROM migration or experimentation)
+ Use Titanium Backup to backup and restore non-system apps including their data (all apps that are not colored red).
+ Make sure you enabled "Sync contacts" in Settings->Accounts&Sync->[Your account] and let it sync
+ Use Sms Backup+ to backup your SMS and call-logs to your GMail account.
How do I backup my EFS
Use this tool: http://forum.xda-developers.com/showthread.php?t=1308546
---TO--BE--CONTINUED---
-RESERVED-
Some stickys here for SGs2 that are in many cases relevant to SGS3 dont know if you want to cut and paste .
Thanks for the good work anyway .
http://forum.xda-developers.com/showthread.php?t=1442549
jje
Keis as well as Odin, pls.
Re:
"Original:
The ones released by Samsung. They can be downloaded on http://samfirmware.com and are flashed through Odin."
Can be flashed by Keis too, Samsungs proprietary flasher (and hence sticking with the "Original" theme).
Can be flashed by Keis too, Samsungs proprietary flasher (and hence sticking with the "Original" theme).
Click to expand...
Click to collapse
Afaik Kies doesn't allow you to flash any ROM of your choice, only the official updates for your region. Or am I wrong?
d4fseeker said:
Afaik Kies doesn't allow you to flash any ROM of your choice, only the official updates for your region. Or am I wrong?
Click to expand...
Click to collapse
Indeed. I was correcting the line as "Original" ROM's can be flashed by Odin and Keis. Only Odin is mentioned in the OP.
recovery just says something is wrong, look at log?
I tried a few versions (of the backup sets), same error.
What am I doing wrong? How do I fix it? :crying:
Log from recovery run...
Starting recovery on Thu Aug 16 21:58:52 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
RA Revamped
Build : RA-VIGOR-v3.15-getitnowmarketing
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
fuzzynco said:
recovery just says something is wrong, look at log?
Click to expand...
Click to collapse
This happens all the time to people.
You can't simply restore a backup from another device because then your new device will actually appear as your old device on Google and Verizons servers, which will cause all sorts of problems if Verizon were to ever successfully restore your old phone and try and send it off to someone else. To avoid this problem, the recovery won't even let you restore a backup from another phone, even if its the exact same hardware.
Go to play.google.com, go to view your devices in the settings section. You should see two Rezounds. One will have been activated in the past, and one whenever you first turned on your replacement after receiving it and logging in with your account. So the one that was activated in the past is clearly your original Rezound that you've returned. You can give it a name, like "DEAD REZOUND" so that you know by looking at the name which Rezound Google thinks you're using.
There is a workaround that will let you restore the backup anyway if you want to search for it, but I highly recommend you don't. If you do, you can then go to play.google.com again, view your existing devices in the settings section, and you'll see that Google thinks your new phone is the same one you just sent back to Verizon. It should show "DEAD REZOUND" as being registered again today (or whatever day you successfully restored a backup from your old phone)
To sum up: Don't restore a backup from another Rezound. You pretty much have to start over again.
I kind of follow... RA is an image backup
so it would duplicate the serial and device specific data.
I could do a TiBu of the user apps and data (and the
new xml files of the call log and sms's), though.
Use an app to export the calendar data to an
.ics (iCal file) and the phone book to a .vcf
for import on the 'new' phone.
Since Google added some 800+ empty
phone book entries and messed up my phone
book, I don't sync with it. I export the whole
thing to a vcf.
So the missing /dev/tty0 device file
error from the restore is just AR not
letting me shot myself in the foot,
right?
I'll need to install my ROM, then
restore the user apps and data
from TiBu then rebuild my 'desktop'?
Is it worth doing the RUU for ICS
to get there? The new phone was
offered the upgrade OTA, but I think
it was wiped by the unlock prior to
S-Off process. Would I flash
the ICS RUU, then flash the ICS/JB
hboot, to get fastboot commands,
then reflash recovery?
I have seperate micro cards for
the 600mb RUU zip and the
ICS firmware/radio/hboot(JB)
zip.
I'm thinking since I have to rebuild
the desktop anyway, maybe doing
the ICS RUU first is a good idea.
fuzzynco said:
so it would duplicate the serial and device specific data.
I could do a TiBu of the user apps and data (and the
new xml files of the call log and sms's), though.
Use an app to export the calendar data to an
.ics (iCal file) and the phone book to a .vcf
for import on the 'new' phone.
Since Google added some 800+ empty
phone book entries and messed up my phone
book, I don't sync with it. I export the whole
thing to a vcf.
So the missing /dev/tty0 device file
error from the restore is just AR not
letting me shot myself in the foot,
right?
I'll need to install my ROM, then
restore the user apps and data
from TiBu then rebuild my 'desktop'?
Is it worth doing the RUU for ICS
to get there? The new phone was
offered the upgrade OTA, but I think
it was wiped by the unlock prior to
S-Off process. Would I flash
the ICS RUU, then flash the ICS/JB
hboot, to get fastboot commands,
then reflash recovery?
I have seperate micro cards for
the 600mb RUU zip and the
ICS firmware/radio/hboot(JB)
zip.
I'm thinking since I have to rebuild
the desktop anyway, maybe doing
the ICS RUU first is a good idea.
Click to expand...
Click to collapse
In reply to the bolded part: Basically, yes. AR's nandroid places the backups in a folder with your phone's serial as the folder name. Attempting to restore any backup from a folder with any other name will fail to prevent the issues I mentioned above.
I do not and have not ever used Titanium Backup, so in regards to that, I can't be of any help.
If you have a linux machine, you can mount the data.img from any of your backups and then copy all the files from /data/app and data/data to your phone. This will restore most of your apps, and app data/settings. There will still be a few things you'll have to redo from scratch, and this may not work 100% for every app on your phone, but at least this way you don't have to redownload every single app and manually redo all your settings...
I did the RUU zip (it restarted itself, as expected), the firmware/radio/hboot(JB) zip
and then reflashed AR 3.15 from fastboot. Everything seems to be working now.
Do you know if the debloat script (freeze VZW apps) works for ICS OTA ROM?
fuzzynco said:
I did the RUU zip (it restarted itself, as expected), the firmware/radio/hboot(JB) zip
and then reflashed AR 3.15 from fastboot. Everything seems to be working now.
Do you know if the debloat script (freeze VZW apps) works for ICS OTA ROM?
Click to expand...
Click to collapse
not sure...
I couldn't get ViperROM 1.0.3 to not crash (com.android.phone kept crashing).
Trying a couple of others that are prerooted and deboated. So far the ICS &
Sense 3.6 looks fine. Still have the 'social network' stuff to freeze though,
Could I do something like make a zip (from adb shell) of the user apps
/data/app & /data/data directories (to preserve the unix permissions).
and leave that on fat32 sd card? Then merge that into the zip for the
rom to be installed so the installer will reload them?
Would I need to add lines to the installer script to have it load /data (with
the subdirs ../app and ../data)?
hmms maybe better to make a seperate zip to preinstall my saved
/data subdirs? Can I copy the ROMs installer binary and build
a installer script to mount /data, then install the /data directory,
umount /data?
a.mcdear said:
This happens all the time to people.
You can't simply restore a backup from another device because then your new device will actually appear as your old device on Google and Verizons servers, which will cause all sorts of problems if Verizon were to ever successfully restore your old phone and try and send it off to someone else. To avoid this problem, the recovery won't even let you restore a backup from another phone, even if its the exact same hardware.
Go to play.google.com, go to view your devices in the settings section. You should see two Rezounds. One will have been activated in the past, and one whenever you first turned on your replacement after receiving it and logging in with your account. So the one that was activated in the past is clearly your original Rezound that you've returned. You can give it a name, like "DEAD REZOUND" so that you know by looking at the name which Rezound Google thinks you're using.
There is a workaround that will let you restore the backup anyway if you want to search for it, but I highly recommend you don't. If you do, you can then go to play.google.com again, view your existing devices in the settings section, and you'll see that Google thinks your new phone is the same one you just sent back to Verizon. It should show "DEAD REZOUND" as being registered again today (or whatever day you successfully restored a backup from your old phone)
To sum up: Don't restore a backup from another Rezound. You pretty much have to start over again.
Click to expand...
Click to collapse
not really. im on my third rezound and i restored the same viper rom i had before.
this is what i did with AR
1. back up current rom
2. boot into rom
3. use root explorer and find the nandroids
4. noticed 2 folders in the same nanadroid folder ( light bulb)
5. move old back up to the location where the new one was.
6. boot into recovery and did a full wipe
7. restored old back up.
8 boot phone
9. BAM!
This app might work. I use it and it works great but I'm not sure if it restores data.
synisterwolf said:
not really. im on my third rezound and i restored the same viper rom i had before.
this is what i did with AR
1. back up current rom
2. boot into rom
3. use root explorer and find the nandroids
4. noticed 2 folders in the same nanadroid folder ( light bulb)
5. move old back up to the location where the new one was.
6. boot into recovery and did a full wipe
7. restored old back up.
8 boot phone
9. BAM!
Click to expand...
Click to collapse
Yeah this works perfectly fine, but can cause the new phone to register on the network as if it were the old one. It is perfectly possible to restore a backup from another phone, and it works fine... its just a bad idea because if your old phone is ever "recovered" and turned back on, VZW might see two identical devices on the network, which will cause problems in the future.
a.mcdear said:
Yeah this works perfectly fine, but can cause the new phone to register on the network as if it were the old one. It is perfectly possible to restore a backup from another phone, and it works fine... its just a bad idea because if your old phone is ever "recovered" and turned back on, VZW might see two identical devices on the network, which will cause problems in the future.
Click to expand...
Click to collapse
Good to know. Thanks
In my case, the backup is from a device that i bricked totally. couldnt get into download mode so im thinking they will just use it as parts
Sent from my iPhone...
I have installed a Custom Rom in my Galaxy GT I9100 last night. Details: cm-10.1-20130105-NIGHTLY-i9100 & Gapps: gapps-jb-20121212-signed
My Problems:
1) I am not able to read my External SD Card (32 GB). When i plug in to my computer, I am able to read it, but cannot read it via phone.
2) I had backed up my files at Titanium Backup & My Backup Pro before installing this ROM. I am not able to restore some of the Apps & shows error. I read it somewhere that Titanium Backup has a problem with this ROM. Can someone let me know which back up app to use for future back ups, if I want to change my ROM to a different one.
3) Not able to use Samsung Kies?
4)Where to find the option for USB Debugging & developmental. I am not able to find it in Settings.
5) I read in this form about delete Battery Cache. Whats that? Will it help to increase my battery performance?
1) Format the card in CWRecovery (make sure you check the mount points/select the right option; last thing you want to do is accidentally format your internal SD).
2) Check the CM10 discussion thread re: issues with Ti Backup (can't advise from personal experience as I've never used it), maybe an issue with locations of files/file data ? Or...Do a clean install when you switch to a completely different rom (obviously you don't need to do this if you're flashing a nightly/different version of the same rom unless instructed to by the creator of the rom). This is what I do; takes a bit of time, but absolutely worth it if you want a troublefree experience for months to come if you install a different rom. If you absolutely must, restore app data for apps you can't use without the data.
3) Use Kies for what ? Why would you want to have anything to do with Kies if you're running a custom rom ? Kies is rubbish (I'm being kind). There are other apps that do a better job at the things Kies does anyway (Ti Backup & CWRecovery for backups, various other apps that enable you to transfer files to/from via WiFi as examples).
4) You need to look harder in settings. It's there (or you've got a bad install), should be in settings/developer options like it normally is.
5) Deleting battery stats will do exactly that; delete the battery stats. This will not improve the performance of your phone or anything else. This post on G+ from Google's Dianne Hackborn should explain the purpose of battery stats & why deleting them achieves nothing
6) I highly recommend you read most of the threads in the Stickies, these threads contain the 'basics' that everyone who tinkers with their SGS2 should know.
(You're welcome)
MistahBungle said:
1) Format the card in CWRecovery (make sure you check the mount points/select the right option; last thing you want to do is accidentally format your internal SD).
2) Check the CM10 discussion thread re: issues with Ti Backup (can't advise from personal experience as I've never used it), maybe an issue with locations of files/file data ? Or...Do a clean install when you switch to a completely different rom (obviously you don't need to do this if you're flashing a nightly/different version of the same rom unless instructed to by the creator of the rom). This is what I do; takes a bit of time, but absolutely worth it if you want a troublefree experience for months to come if you install a different rom. If you absolutely must, restore app data for apps you can't use without the data.
3) Use Kies for what ? Why would you want to have anything to do with Kies if you're running a custom rom ? Kies is rubbish (I'm being kind). There are other apps that do a better job at the things Kies does anyway (Ti Backup & CWRecovery for backups, various other apps that enable you to transfer files to/from via WiFi as examples).
4) You need to look harder in settings. It's there (or you've got a bad install), should be in settings/developer options like it normally is.
5) Deleting battery stats will do exactly that; delete the battery stats. This will not improve the performance of your phone or anything else. This post on G+ from Google's Dianne Hackborn should explain the purpose of battery stats & why deleting them achieves nothing
6) I highly recommend you read most of the threads in the Stickies, these threads contain the 'basics' that everyone who tinkers with their SGS2 should know.
(You're welcome)
Click to expand...
Click to collapse
I tried with the Format option but no success. I was able to do it by the use of Directory Bind http://forum.xda-developers.com/showthread.php?t=1536568
For the Developer Options, I needed to tap the Build Number 7 times and then I could get this option.
Titanium Backup, I made the mistake of restoring the system apps also .
Thanks for the Stickies Thread URL.
This is a repost - the original is here but no one could forward me to a proper section of the forums.
Some update to the info below:
- on the initial 4.2.x version of the running android I had most of my apps moved to the external sdcard (sdcard0) - that was their location (.assec) when I did the adb backups
- in the meantime I checked more of my backups and they seem OK - I could uncrypt the ab to normal tar archives and see the contents of apps and shared folders
I would post more links to the device info but I am not allowed to post links.
Some forum posts related to the device:
http://forum.xda-developers.com/showthread.php?t=2639416
http://forum.xda-developers.com/showthread.php?t=2399708
#######
Hello there,
I need some info on how or if it is possible to make use of my full adb restore file or I just throw it away and restart fresh of my device.
Device is allview viper v1 (16Gb) -
NO ROOT and not interested in rooting it.
I believe I made a few versions of good back-ups including at least one good full backup including apks by using UBT (1.3.2 version if I am not mistaking).
My problem: I can't restore the phone by using any of the created ab files by using adb which drives me nuts.
It's worth to mention that in between I upgraded the phone software from 4.2 to 4.4 by using the producer's update images... I did a factory reset with 4.4 and re-installed most of the apps I had. I even copied most of the data from a file-sync backup...
Every time I try to use adb restore I get to the screen to input (now 2 passwords which basically are the same), I get the message "restore starting" and quite fast "restore finished" on the phone screen though while using the full back-up I definitely see that adb is still accessing / reading the file for longer time...
What I tried further: I used abe (android backup extractor by tweaking their .sh script) to create both standard individual .ab-s but also kitkat compatible ones (with abe pack-kk) with no luck in restoring the apps and their data.
It is quite annoying since after converting to .tar and un-tar-ing I can see that the backups seem ok and I can even see the sqlite data and xml settings for the apps but I do not know how to import those to the new OS running on the phone.
I tried this using both USB storage, picture mode, etc., input only the desktop pass and afterwards inputing both of the asked passwords.
So the question is: can I restore the data (about 32Gb including the pics and docs) or should I delete all the "working" files I created and put it on the "learn by error"?
Should I try to downgrade to 4.2. (if it is even possible..) and try the adb restore there?
Cheers and thanks in advance.
this is [not necessarly] a bump... but maybe a sad discovery...
are all the users of this portal just dumb script kiddies and no real user / developer of android (... use here all the smart-device-OS) apps and hackers?!
I am kind of disappointed that not even one "dev" tried to answer this post with valuable info...
i guess this is just a ad-catcher portal for the consumer-ignorant mass of users of "smart" devices...
sad, really sad.
take care and sleep well!