Related
...[from elsewhere] ...I didn't see any mention of this in the how-to threads so I didn't back up my EFS files from the stock rom. Anyone here have had any issues with this after going back to stock?
Click to expand...
Click to collapse
That is an example of things that are scattered in many threads...specifically, what are the things you should DO or SAVE before flashing a new ROM?
Above seems to be one (except is "EFS" a folder or what?). Would folks please offer your suggestions of the "protective" steps to be done/preserved in case of future difficulties.
Actually, in addition to the one quoted, doing a Titanium Backup is in almost all of the how-to discussions, so I guess that is already covered.
efs is really only relevant if you plan on using kies. Your phones product code and imei number are stoped in those files. flashing roms can alter these files. I have never done this. If you want to down load root explorer, or free option android mate. I would pay for root explorer. Find the efs file copy and paste it to your internal sd. Then save it to your pc
Android id. Dl android id changer from market. if you have not already dl busy box from market. Install busy box using app. Open android id changer, click save id, custom flashes change this and it us god to have it saved, you can restore using same app after flash
Do you know what odin is?
Do you know your build number?
mcord11758 said:
efs is really only relevant if you plan on using kies. Your phones product code and imei number are stoped in those files. flashing roms can alter these files. I have never done this. If you want to down load root explorer, or free option android mate. I would pay for root explorer. Find the efs file copy and paste it to your internal sd. Then save it to your pc
Android id. Dl android id changer from market. if you have not already dl busy box from market. Install busy box using app. Open android id changer, click save id, custom flashes change this and it us god to have it saved, you can restore using same app after flash
Do you know what odin is?
Do you know your build number?
Click to expand...
Click to collapse
Recapping this...
EFS is a file. Can save it using Root Explorer or Android Mate.
I have copied down all the data under the battery. Is there more than that in this file?
I am confused about second paragraph. You mention download
Android ID Changer
Busy Box
Which one is it that captures the Android ID? And obviously it saves it, but where?
Yes, odin is mentioned in the how-to's, but it IS part of the flashing process. I am looking for things that should be done BEFORE starting that.
Yes, I know the build (1006). It is part of the data under the battery. And flashing wouldn't destroy or modify that.
Yes the efs had your csc or product code. If you flash a rom that is a port from another device this may be changed. Not an issue if you do not use kies.
Busybox is an app that installs commands onto your phone that certain programs need to operate correctly. Titanium backup and android id changer need this to function correctly. Android id changer saves your id in a file on your internal sd. The file is called update.id when you flash a rom you open the app again click load id, then change id. Phone reboots, id us back to your original id
Odin is a utility that flashes you back to stock 2.1. It is used by many as a safe way to go from rom to rom with a clean install. It is also used to recover from software bricks.
If you have more questions that pop up pm me, this way we are not clogging up the q&a
I think the exchange helps many people who I assume, like me, are trying to sort all this out.
MAIN purpose of the thread is to identify things to do/save before beginning the 'change to another ROM' process--which to me would include the Odin flash back to stock if you aren't there already.
But these side question resolutions are pertinent.
Your Busybox comment threw me a curve. It sounds like you are saying it installs stuff TiBU and Android ID Changer need in order to work. You mean TiBU as downloaded from the market does not work as a standalone app?
tibu needs busy box. If you download tibu and open the app there is a button on the bottom that says problems. If you click it it will also look to install busy box commands.
You are right about the usefulness of threads like this, no disrespect but it looks like you joined xda 4 days ago. These types of discussions are constant and rehashed on nearly a daily basis. For some odd mental quirk I read then all and help when I can. There are a thousand questions you can have, the offer to pm was to keep it easy
I have been reading for two weeks--I mean reading A LOT, not just 4 days ago; that was when I registered on the site. This is a =wonderful= resource, but it is a plain fact that what you need to know is scattered all over the place, both video and written how-to's. I have not found a single one that includes everything you need to know. I mean, for example, they will tell you to do something, which seems trivial to them, but which really involves other knowledge. And that sounds like a non-isue, but in fact it is a complete showstopper for "us" types. Yes, you can go off hunting to clarify the incompleteness, but that is exactly what I am talking about--hunting all over the place.
By the time someone gets to the point they can create something with completeness, the problem is...they are already to the point they can create such a thing. That contradiction arises from it being almost impossible to remember what you didn't know "back then."
I had been studying HARD trying to get "it," everything you need to do to flash a different ROM. Then, a day or so ago, in all that hunting around I speak of, someone mentioned "be sure you ... before you flash." It dawned on me that, when you think you are ready to flash, you aren't. There are things that should be done BEFORE. I started the "hunt" again as alluded to here. Then I said, dang, all us newbies would be well served if all the preliminary do's and save's were in one thread (preferably, ultimately in one LIST). Thus the reason for this thread.
If I am wrong, and other newbies really don't need to know these things, then yes, it can be done in PM. Others will never see it, and still be stuck in the hunting-all-over mode. Thus, I think it is desirable and helpful to others to put it in public, in one thread.
Once again no disrespect. Your point is taken.
Tibu to back up all your user apps, no system information. unless you want to learn how to use odin in the case of issues
Android id changer to back up your android id
Rom manager to back up your current setup, and flasg clockwork recovery. Never restore a backup of one rom on top of another rom
Contacts to external sd, sim, or sync with google
Efs using root explorer to copy folder and save in pc
Odin to flash stock and or recover from software brick. Builds 1010 and above do not use one click odin
No offense taken, and that's a great input. Thanks.
If others see anything else, please contribute.
Ok, I am also new at this, I have flashed 3 Roms. This is what I have done when changing ROMs.
Download Titanium Backup and rom manager. Back up your apps with Titanium Backup.
Download the ROM you want to flash.
Download Odin.
Turn on usb debugging.
Plug phone into the computer, pull down the notification window and click on usb to mount the sd card.
Open this up to look at files.
You should have an update.zip file you can copy to your desktop. You also should have a folder named Titanium Backup that you can save as well.
Once you have this, you can begin.
Take your phone to stock using odin. There are several tutorials available. I used this one,http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36 because I have a 1010 phone.
Once this is done, I push the voume up and down along with the power button. You will get a menu giving you a choice to reinstall packages. You need to click this, go to yes, and it will pull up to the same menu again. Hit reinstall packages again which will get you to clockwork recovery.
Now, I chose to wipe/factory reset to make sure my phone was "clean".
Then, I chose to apply the update.zip.
Then, I chose to install a zip file from the sd card, scrolled down to the rom file, and chose it.
Then it will install the Rom. You will choose go back, then reboot the system. Then your Rom should be installed.
I think I remembered everything. I used a few tutorials:
http://theunlockr.com/2010/08/02/how-to-load-a-custom-rom-on-the-samsung-captivate-vibrant/
and this one:http://forum.xda-developers.com/showpost.php?p=10183875&postcount=4
Hope this helps!
OOPS. Thanks, but this thread is for things to do or save BEFORE starting the ROM change.
So... let's say that you didn't save your android id before you flashed... will that cause problems?
beryxil said:
So... let's say that you didn't save your android id before you flashed... will that cause problems?
Click to expand...
Click to collapse
You tell me. Did you? Are you experiencing problems?
it depends on the rom you are using. You may experience issues downloading from market and certain games may give you issues.
If you did not save it and you are not having problems then no big deal. You can go back to stock and save it, then flash again.
Hello my name is P3Droid,
We (TBH) have a lot of experience in Motorola phones and hacking. This experience dates back to the Razr days.
Here is a word of caution. Do no delete apps from the System partition, I would suggest you only rename them to .bak. When Motorola pushes updates each of the files undergoes a hash check, if the file has been manipulated or is missing the entire update will fail.
Until a system only sbf or similar is released, unless you make a back up with bootstrap and recovery, you will eliminate your ability to take updates moving forward.
You can remove many of the stock apps without rooting just by using the built in app manager.
Those apps are in /data it is the apps that are in /system that count.
jimmydafish said:
Hello my name is P3Droid,
We (TBH) has a lot of experience in Motorola phones and hacking. The experience dates back to the Razr days.
Here is a word of caution. Do no delete apps from the System partition, I would suggest you only rename them to .bak. When Motorola pushes updates each of the files undergoes a hash check, if the file has been manipulated or is missing the entire update will fail.
Until a system only sbf or similar is released, unless you make a back up with bootstrap and recovery, you will eliminate your ability to take updates moving forward.
Click to expand...
Click to collapse
i take it that all the apps you can delete through app manager are on /data therefore are safe to delete right?
This should definitely be sticky'd.
franciscojavierleon said:
i take it that all the apps you can delete through app manager are on /data therefore are safe to delete right?
Click to expand...
Click to collapse
Yes anything that you can delete through the application manager is okay to remove, those have no impact on the update process.
And to complete my thought above. When an update is released, and they are coming, then you need to just change the file names back to normal to take the update.
Sound to me like we ned an ap that lets toys select programs to rename and then can change then back when needed. Would make it alot easier. Ill look onto this...also if some one else can confirm this info I might stick it.
Sent from my MB860 using XDA App
I can confirm that what p3droid is saying is true for all recent Motorola devices, but the point is really that you won't know until an OTA update is released how they have written the updater script in the zip file.
We have been through this with releases for every phone since the Droid X and many people got caught out by it and were stuck until we released SBF files that could safely restore the stock configuration and allow updating to official release versions.
This brings up another important point about modding your phone at this stage in the cycle. Without a full SBF to recover with in the event of a problem that renders the phone unbootable or unable to access recovery, or if you haven't made a complete nandroid, you will be again be stuck and have to return your phone to AT&T/Motorola for warranty replacement. This is never good for anyone.
When we mod our phones against the wishes of the carriers and manufacturers, we should really take responsibility for those actions and not produce a mountain of bricked phones whose cost is passed along to everyone in the form of higher ETFs for smartphones and other ways.
So, until a full SBF is released of the current build, people should be very careful what they change or remove from their phone's system and/or NVM and radio.
I also tried to warn users about this in another thread that was locked before p3droid started this thread. We have watched hundreds or even thousands of users destroy their phones in myriad ways and helped many of them recover them by providing SBF files as a safety net. It's not fun and if it can be avoided it is to everyone's benefit to do so and only requires care and forethought.
Is there anyway we could make a backup of this partition for later use? would each user need to make one or would one for all users suffice?
Assuming a bootstrapped custom recovery is possible, and we know Koush is already working on it, then a nandroid backup of at least the system, userdata and cache partitions would be the first and best step to take. Also assuming that the bootloader is locked/signed and true recovery is not possible, then the boot image and kernel will not be able to be backed up or written to by the bootstrapped recovery. It is always best to make your own backup for your device and store it on the sdcard where you have easy access, but users have also been able to use someone else's nandroid backup to restore their device in many cases as well. The recovery will give you the option to restore each partition separately in the advanced options so that you won't be restoring someone else's data to your phone.
We at TBH have also been able to create our own update.zip files and SBF files to help users recover from various mishaps.
This was because we had access to both official and unofficial files and tools to accomplish those things.
We have no idea if that will be the case here and we will not likely have the device ourselves to work with given we are VZW users primarily.
Again, there are many variables here that are yet to be determined and modes of access to the various partitions and radio baseband will be different with this phone as opposed to previous Qualcomm chipset devices.
All of this means that at this stage extreme caution is advised and being overzealous with root access is very dangerous right now.
I suggest everyone that is rooted use TITANIUM BACKUP to deal with their bloatware issues. The pro version, which you will need, is only a few bucks and is worth it. TB allows you to 'freeze' bloatware apps, which to my knowledge just blocks it fro the system, but does not delete it. The apps you choose to freeze are also removed from the app tray - so no more clutter. This way when an update rolls around, you can run down the list and simply touch 'thaw' to bring those apps back to recognition. This seems like a much more efficient and easy way to go back and forth, rather than renaming the .apk's.
I apologize if someone already mentioned TB in this thread - I just skimmed quickly.
I deleted all the bloat apps using the app manager without root. They were gone!
I did a factory reset on the phone and *surprise* the apps were back!
The things that were not part of the system come back during reset. On the other hand, im ****ed because I went crazy and deleted some actual apps that the system will check. Yay me.
pwndrone said:
The things that were not part of the system come back during reset. On the other hand, im ****ed because I went crazy and deleted some actual apps that the system will check. Yay me.
Click to expand...
Click to collapse
Ouch. Might not work, but have you tried a hard reset?
We should make a list of what's safe to remove like we did for the Captivate. Might be helpful.
I did a full factory reset and those apps that weren't part of the system came back but stuff like the help center are still missing.
Hopefully there will be a way to load the stock firmware sometime in the future.
Sent from my MB860 using XDA App
Would an app like "Autostarts" work in this case?
Guys, I can't emphasize this enough: use Titanium Backup to freeze the apps rather than deleting them, it will make your life much easier.
does this apply to using different font files as well? I'd like to use a ttf font that's a little larger than DroidSans. if i rename and use a different font will that impact OTA updates or anything else for that matter? thanks!
before reading about "freezing" apps, i reset my atrix back to factory settings. i need help rooting my atrix again. it keeps me in "Waiting for Device" where before i had no problem rooting. and another thing, when i had reset back to factory settings...i still have superuser installed. do i uninstall superuser in order to gain root access again?
I have not rooted yet. My question is can we use freeze to turn off BlurAccounts or is it fully baked into the Rom?
Here's a odd one!
I was using my S7 to research an issue with my Samsung LED Smart TV. I found a How To, noticed a file path at the top of the page and backed up one page. It had several links, one of which was "How to Power Cycle a Customers Network". That sounded interesting so I clicked on it.
As soon as I clicked on the link my S7 turned OFF. I turned it back ON and it was stuck on the Dell logo. I pinned holed and tried again. It stuck again.
I booted into the recovery menu and tried to boot from there but it again got stuck. I had to do a factory reset. I use My BackUp Pro with a external SD card, it wasn't that painful and other than my email to setup, I'm back up.
Anyone see anything like this before?
Here a link to the nasty page for the brave to try: http://support-us.samsung.com/cyber/popup/iframe/pop_troubleshooting_fr.jsp?idx=151038&modelname=&modelcode=&session_id=P7mLwJcB60VpLrLWp3vgvhhXtfh2XSS3p78q2QlvhT3McsST29T1%21-1964052360%211228160092%211329276619709
Went to all the links on that page with no ill effects. You're Streak was just ready for a clean install
cdzo72 said:
Went to all the links on that page with no ill effects. You're Streak was just ready for a clean install
Click to expand...
Click to collapse
I just did a full factory reset around 1/7/12. Is the Android OS so fragile that it requires frequent resets? Your not running a stock S7 as I am, are you?
I suppose it was that it just shut off instead of a normal power off sequence that did the damage.
wptski said:
I just did a full factory reset around 1/7/12. Is the Android OS so fragile that it requires frequent resets? Your not running a stock S7 as I am, are you?
I suppose it was that it just shut off instead of a normal power off sequence that did the damage.
Click to expand...
Click to collapse
It's not fragile at all, it's about maintenance, just like a PC... you regularly need to wipe your app and dalvik caches just like you do disk cleanups and defrags on a PC.
You should clean up obsolete databases on your internal and external sd cards.... all those types of things. Many of us don't know what it is to have one single install of a ROM running for that long on our devices as we are constantly flashing updates and fixes, and a after a couple of those come around you naturally combine those into a package and flash clean from a factory reset.
But to answer your other question is no, I have never had stock ROM on any of my devices for no longer than it took me to go in and just have a peek at it to compare it to what I would be about to flash.
cdzo72 said:
It's not fragile at all, it's about maintenance, just like a PC... you regularly need to wipe your app and dalvik caches just like you do disk cleanups and defrags on a PC.
You should clean up obsolete databases on your internal and external sd cards.... all those types of things. Many of us don't know what it is to have one single install of a ROM running for that long on our devices as we are constantly flashing updates and fixes, and a after a couple of those come around you naturally combine those into a package and flash clean from a factory reset.
But to answer your other question is no, I have never had stock ROM on any of my devices for no longer than it took me to go in and just have a peek at it to compare it to what I would be about to flash.
Click to expand...
Click to collapse
I'm sure that a reset must wipe everything out, true? A reset barely a month ago. Your saying that monthly maintenance is needed?
I don't reinstall Windows monthly as that's a last resort at any time.
NOt a montly factory reset, but every week or so I wipe app caches and dalvik caches and let them rebuild themselves from use.... On Froyo for the S7 this is easily done through Clockwork Mod, but in Honeycomb and ICS I use SD Maid to clean app caches and another app called DroidTeaker to wipe the dalvik cache.
cdzo72 said:
NOt a montly factory reset, but every week or so I wipe app caches and dalvik caches and let them rebuild themselves from use.... On Froyo for the S7 this is easily done through Clockwork Mod, but in Honeycomb and ICS I use SD Maid to clean app caches and another app called DroidTeaker to wipe the dalvik cache.
Click to expand...
Click to collapse
Both for rooted devices and no good for me.
wptski said:
Both for rooted devices and no good for me.
Click to expand...
Click to collapse
1) well I have to tell ya, an android device that aint rooted just about isn't much more than a paperweight, so I have to ask why haven't you rooted?
2) I can't remember what version you're running on your S7, freshen my memory please
cdzo72 said:
1) well I have to tell ya, an android device that aint rooted just about isn't much more than a paperweight, so I have to ask why haven't you rooted?
2) I can't remember what version you're running on your S7, freshen my memory please
Click to expand...
Click to collapse
I've read, read and read then I read about some that appeared to have bricked theirs! They ask questions, get answers that are maybe too techy for the average user. Never hear that they solved the issue and I have to "assume" that they had to sent it back for service.
I've never read to date a real "Whatever for Dummies". Anyone can create a post full of links to other posts. What may seem simple to one isn't simple to another. Some have forgotten when they knew nothing.
There are probably more non-rooted S7's out there than rooted ones with perfectly happy users. Of course, there are the ones that get rooted, etc. right out of the box and a few that don't work after that too.
Like my signature states, I have a stock HC 3.2 with build 21700.
Getting back to the Android OS not being fragile. I had a misunderstanding of sdcard meant as in doing an update from sdcard which really means sdcard2 or external. I put the 514 update.pkg in the S7's internal memory. It errored and got stuck on the Dell logo. That was one factory reset because it couldn't handle that error or recover from it properly. Get a SD card and put update.pkg on the SD card. Get a file name mismatch error this time but it does reboot. Read up a bit and find something to rename to Update.pkg. Worked like a charm. Why was it case sensitive for me but maybe not for others??
wptski said:
I've read, read and read then I read about some that appeared to have bricked theirs! They ask questions, get answers that are maybe too techy for the average user. Never hear that they solved the issue and I have to "assume" that they had to sent it back for service.
I've never read to date a real "Whatever for Dummies". Anyone can create a post full of links to other posts. What may seem simple to one isn't simple to another. Some have forgotten when they knew nothing.
There are probably more non-rooted S7's out there than rooted ones with perfectly happy users. Of course, there are the ones that get rooted, etc. right out of the box and a few that don't work after that too.
Like my signature states, I have a stock HC 3.2 with build 21700.
Getting back to the Android OS not being fragile. I had a misunderstanding of sdcard meant as in doing an update from sdcard which really means sdcard2 or external. I put the 514 update.pkg in the S7's internal memory. It errored and got stuck on the Dell logo. That was one factory reset because it couldn't handle that error or recover from it properly. Get a SD card and put update.pkg on the SD card. Get a file name mismatch error this time but it does reboot. Read up a bit and find something to rename to Update.pkg. Worked like a charm. Why was it case sensitive for me but maybe not for others??
Click to expand...
Click to collapse
1) rooting any android device WILL NOT brick it... what the user does AFTER rooting may render it useless and them have to start all over
2) rooting the S7 is as easy as putting the Superuser7.zip file on the external sd, flashing it through Clockwork Mod and that's that, takes about 2 minutes
3) have no idea why for some their recoveries are case sensitive, but the general consensus is that the update.pkg was corrupt to begin with more than likely. I have had problems downloading zip files and update.pkg files in Chrome and Internet Explorer, Firefox consistently gives me a clean file and checksum so I have never experiences the problem. The other issue is not using the correct stock recovery for the package being flashed.
4) when you tried to flash the 514 package and it got stuck on the Dell logo, then it sounds to me you have a glitch in your inner sd, it should not have flashed anything that would make it stick at the Dell logo if there was a problem with the file, thus that may be your entire problem, you have a problem internally that just hasn't truly reared it's ugly head...
5) my personal suggestion would be to flash DJ Steve's Honeycomb R2 ROM via NVFlash, that will wipe clean the innerSD and it's partitions, so any problem there may have been would get cleared up by the process. Then if you still want to remain stock you can flash the factory recovery and flash the 514 package again after your innerSd has been reformatted by the NVFlash
6) all that sounds like a lot, I understand your point, but all in all it all takes about 30 minutes
cdzo72 said:
1) rooting any android device WILL NOT brick it... what the user does AFTER rooting may render it useless and them have to start all over
2) rooting the S7 is as easy as putting the Superuser7.zip file on the external sd, flashing it through Clockwork Mod and that's that, takes about 2 minutes
3) have no idea why for some their recoveries are case sensitive, but the general consensus is that the update.pkg was corrupt to begin with more than likely. I have had problems downloading zip files and update.pkg files in Chrome and Internet Explorer, Firefox consistently gives me a clean file and checksum so I have never experiences the problem. The other issue is not using the correct stock recovery for the package being flashed.
4) when you tried to flash the 514 package and it got stuck on the Dell logo, then it sounds to me you have a glitch in your inner sd, it should not have flashed anything that would make it stick at the Dell logo if there was a problem with the file, thus that may be your entire problem, you have a problem internally that just hasn't truly reared it's ugly head...
5) my personal suggestion would be to flash DJ Steve's Honeycomb R2 ROM via NVFlash, that will wipe clean the innerSD and it's partitions, so any problem there may have been would get cleared up by the process. Then if you still want to remain stock you can flash the factory recovery and flash the 514 package again after your innerSd has been reformatted by the NVFlash
6) all that sounds like a lot, I understand your point, but all in all it all takes about 30 minutes
Click to expand...
Click to collapse
The same PKG file was used both times. I'll throw another oddity at you. I was unable to edit update.pkg to Update.pkg either using File Expert with the S7 or while connected to my PC. I'd edit, hit return and it always reverted back. I actually deleted it from the S7, changed the name from Windows then connected and copied it back. Later on while trying this from ES File Explorer a thing popped up, something about try different name or other. Sure enough, it doesn't allow just case changes. You have to rename it different and back again if you just wanted a case change.
I'm going to save your suggestions.
wptski said:
The same PKG file was used both times. I'll throw another oddity at you. I was unable to edit update.pkg to Update.pkg either using File Expert with the S7 or while connected to my PC. I'd edit, hit return and it always reverted back. I actually deleted it from the S7, changed the name from Windows then connected and copied it back. Later on while trying this from ES File Explorer a thing popped up, something about try different name or other. Sure enough, it doesn't allow just case changes. You have to rename it different and back again if you just wanted a case change.
I'm going to save your suggestions.
Click to expand...
Click to collapse
Then you definitely had/have a corrupt package and the renaming is a sign of a read only problem trying to surface sounds like to me
Hi,
i've imported my photos from my internal memory via sony bridge for mac accidentally in Iphoto. I didn't see the app was faded and crossed. Turns out only the app Photos is still working. So after importing 2700 pics (big trip and behind with backup), the question popped if I wanted to delete the fils on my phone and I said yes. I tried to re install Iphoto, but nothing there, but older pics. I tried the temporary files from the Mac, but nothing.
So now I got my hopes up for a data recovery software thing. But although Windows (Im working on another laptop) did install the drivers correctly and I see my phone in the folder structure, no data recovery software recognises my phone although I switched to MSC and USB-debugging. I think because I haven't rooted it i suppose. Well, that's what all the forum members say
So I think rooting is my only option left? I am wondering if it works for my goal to get my data back. I read that unlocking the boot loader means everything will be erased, so then there would be no point for me to do this. Is it possible to root it without losing my (deleted) data on the internal memory? I know it is being overwritten now as we speak, but I'm sure I can save a few photos!
thanks a million!
First off, I don't fully understand the first bit involving iPhoto. But if I understand correctly, you need to recover files deleted from internal memory.
I think recognizing a phone's internal memory is indeed a steep expectation for general Windows file recovery software. However, there may be some specialized programs out there designed just for that purpose. I know for a fact they exist for iOS for example. Not that I'm a fan. Anyway, googling "recover Android files Windows" showed some interesting results, but as I have no experience I can make no recommendations. I did see Easeus among the results, and I personally would start there based on experience with other software by them: http://www.easeus.com/android-data-recovery-software/free-android-data-recovery.html
This would be your safest bet. As you probably know, your photos are still there as long as they are not overwritten. Being able to recover from an external device (PC) is therefore preferable to making changes to your internal memory. It's also far less complex than rooting
Another thought before getting into rooting: I don't suppose you had an app like Google+ making automated backups of your pictures? If so, you might find them on your Google Drive. This also might be a good idea to avoid trouble like this in the future
Third and last resort: you could try a data recovery app on your phone, like GT Data Recovery. That does requires root. The good news: you don't need to unlock your bootloader to be able to root. Locked bootloader means you're limited to stock roms, but they too can be rooted.
Here's a useful thread describing in detail what you'd need to do:
http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
In your case, I'd run data recovery ASAP, meaning
Downgrade your firmware, leaving data in Flashtool unchecked (!!) (See thread's FAQ for detailed explanation)
Root
Install GT Data Recovery or similar from Google Play and run it
After you've recovered all photos you can and backed up all your other data, follow the procedure in the recommended way, which includes wiping data. Do note however, that the firmware mentioned there is outdated (March 2015). You can find up to date firmware here: http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
Good luck!
(Thanks to @bilboa1 and @istux for their useful posts!)
Thanks!
I did try several data recovery software programs, including EaseUS, but none recognised my internal memory unfortunately. I switched all auto back up programs like Google Plus off, because it was just too much. I take so many pics of my kids and the selection process usually doesn't take place directly, so it backs up everything and I've got to many pics in my Google Plus account. But this was a wise lesson i should backup somehow.
So only option 3 is left. As i read it, when I root it, the data on my internal memory won't be deleted? Stock ROM is fine for me, I'm very happy with my standard software, if rooting is what it takes, that's what i should do.
If you're rooted, you can use the app DiskDigger. Worked for me
Sent from my D5833 using XDA Free mobile app
kjoz said:
Thanks!
I did try several data recovery software programs, including EaseUS, but none recognised my internal memory unfortunately. I switched all auto back up programs like Google Plus off, because it was just too much. I take so many pics of my kids and the selection process usually doesn't take place directly, so it backs up everything and I've got to many pics in my Google Plus account. But this was a wise lesson i should backup somehow.
So only option 3 is left. As i read it, when I root it, the data on my internal memory won't be deleted? Stock ROM is fine for me, I'm very happy with my standard software, if rooting is what it takes, that's what i should do.
Click to expand...
Click to collapse
Generally speaking, wiping data is recommended when flashing a new ROM. Because Giefroot requires older firmware, you need to flash that firmware. Which means a data wipe comes recommended. Technically however, wiping data is optional. It is possible to downgrade without wiping data (by unchecking the respective option in Flashtool). So that is what I'd do in order to recover your pictures.
Once that has been accomplished, along with a backup of all other data you wish to keep, I would start the whole process again as described in the thread I linked to. Because this time, the objective would be not data recovery, but ending up with a stable phone. And that means wiping data. (Highly recommended.)
I don't want to complicate things further, but if you don't care about being rooted after data recovery, you could just upgrade to regular stock firmware instead of pre-rooted firmware. This would allow you to skip a few steps of the process, and also avoid being unable to apply Sony's OTA updates. (Significant updates can cause a loss of root.)
Personally, I would not want to give up root once I have put effort into getting it.
kjoz said:
Hi,
i've imported my photos from my internal memory via sony bridge for mac accidentally in Iphoto. I didn't see the app was faded and crossed. Turns out only the app Photos is still working. So after importing 2700 pics (big trip and behind with backup), the question popped if I wanted to delete the fils on my phone and I said yes. I tried to re install Iphoto, but nothing there, but older pics. I tried the temporary files from the Mac, but nothing.
So now I got my hopes up for a data recovery software thing. But although Windows (Im working on another laptop) did install the drivers correctly and I see my phone in the folder structure, no data recovery software recognises my phone although I switched to MSC and USB-debugging. I think because I haven't rooted it i suppose. Well, that's what all the forum members say
So I think rooting is my only option left? I am wondering if it works for my goal to get my data back. I read that unlocking the boot loader means everything will be erased, so then there would be no point for me to do this. Is it possible to root it without losing my (deleted) data on the internal memory? I know it is being overwritten now as we speak, but I'm sure I can save a few photos!
thanks a million!
Click to expand...
Click to collapse
If you have successfully imported from the phone into iPhoto, then you simply need to import your iPhoto Library into Photos in Mac.
Check if you can find the iPhoto library by going to Finder -> Home -> Pictures
There should be 2 libraries there - one for iPhoto, and one for the newer Photos app that came along in April. Double-click the iPhoto library and wait for Photos to launch, then follow the instructions to import the library into Photos.
Make sure you have enough disk space (on the Mac) to do this. You'll need at least as much free space as the size of the iPhotos library to import it into Photos and possibly more.
Hi everybody,
hopefully someone here can answer a few questions for me.
I have a Samsung Galaxy 3 mini.
android version 4.4.2
kernel version 3.4.0-1670137
baseband version g730aucubng4
my service provider is AT&T
what I want to do is pretty simple, or so I thought.
I read this article ( https://www.androidpit.com/galaxy-s3-note2-memory-bump) about swapping your phone's internal and external storage so the thing doesn't get so full of apps etc. it runs like crap.
I thought "hey, I haven't rooted my phone yet for fear of loosing stuff, but it's old and slow and if it's that easy, why not"
I rooted it using kingo-root, but decided to use o-nandroid backup to create a backup before I did anything. I fallowed these instructions (http://forum.xda-developers.com/showthread.php?t=1620255/) but during the process of flashing the zip file I got a failure message and managed to wipe my memory loosing everything that wasn't on the external sd card.
anyway, to make a long story short, after 4 days of messing with different apps and trying, unsuccessfully, to do various tasks (mainly dealing with creating backups. using twrp, cwm, titanium backup) I think I've discovered the problem.
contrary to what I had read, my android device's boot-loader was not unlocked, or in fact unlockable.
I finally managed to create a backup using Safestrap. but now to my question.
with my bootloader locked, and working through Safestrap, is it possible to use something like the 11extsd2internalsd file from that first article to swap my two hard drives? or am I stuck, since I can't install new kirnels?
--now, someone is bound to say "hey, you should have searched xyz, there is a thread there about this exact thing". I thought I'd respond to that now and save them the trouble. I have spent the past 5 hours searching, googleing, and reading articles about this. so far, I have learned a lot, but I'm tired and quite frustrated with the whole endeavor.
so I thought I would try asking the experts if it's even possible to do what I originally wanted to do, or if I should just delete all these apps, unroot my phone and go back to deleting my pictures and text messages every other day to save space.
Thanks for having the patiance to read through my tale of woes, hopefully someone will be able to help me out and answer my question.
JM
You can swap internal storage with external SD by editing fstab.<device_name>.
Look, here is this file for my phone (yours will be little different) https://github.com/TeamCanjica/andr...dina/blob/cm-11.0/rootdir/fstab.samsungcodina
Just swap in places this code "voldmanaged=sdcard0"/"voldmanaged=sdcard1"
This file you can edit only after unpacking and repacking boot.img (you need to get ramdisk filesystem, more info and how to http://forum.xda-developers.com/showthread.php?t=2036528).
For flashing boot.img (kernel) after making changes, your device must be rooted (minimum this) or have custom recovery which will let you flash zip package.
As I know, last step is to edit from /system/etc/permissions/platform.xml one line (more info http://trendblog.net/fix-kitkat-sd-card-write-restriction/ )