Hello everyone.
please forgive the harsh tone, but this is really getting me crazy.
In preparation to migrating from Android 2.3.5 to Cyanogen on my Samsung Galaxy SII (yep, it's still kicking...) I wanted to make a full backup like, A COMPLETE CLONING. But I've stumbled into a big problem....
let's face it: google mostly points to payware sofwtare from dodgy companies that in turn invest lots of money to climb up the research ladder. Their website are absolutely crap, with wall of text that don't apport any information whatsoever. So, how does one make a full full full full backup of an android phone? and I mean full, in the real meaning of the word: FULL. COMPLETE BACKUP. I mean: If I restore that backup, EVERYTHING WILL COME BACK. Why do I read that, for example, /sdcard ISN'T INCLUDED? what's the point of calling it a full backup?
On my computer, I barely slap in a new HDD, insert the clonezilla disc, and tell him "copy the whole device on the other device". This brings the full package of partitions, file, EVERYTHING. Of course it wouldn't include a USB drive attached to the laptop (the miniSD equivalent, i suppose). also, no point into telling me that a full ANDROID backup wouldn't include the contents of the SD card. The SD card is there to be safely removed during any dodgy operation, am i right? we don't solder miniSD card to phones, and I think I can use the "we" without fear. rooting the phone, for instance, was a breeze.
so to make the point, what do we have on the table?
- Samsung Galaxy SII, GT-I9100, that has been successfully rooted;
- a capable laptop with lots of space to accomodate my backup, with Odin.
I'd like to have a copy of the phone so that if I don't like it, I can flash everything back. and I mean: EVERYTHING. is it possible to accomplish such a thing? and why do backups don't include certain partitions?
Thanks in advance to all the holy souls who are going to answer. Thanks thanks thanks.
Related
I did NOT paritition my gTablet after I installed CWM 0.8. My CM7-based ROMs have installed and worked just fine, including the new Market app. Do I need to partition?
The only real error I have had is the inability to transfer files (using Astro) between my internal 16 GB memory (/mnt/emmc/) and my installed 2GB sd card (/mnt/sdcard). Will partitioning help solve this?
TIA!
I think partitioning is an important step and really should be a mandatory step at least for the first flash. It sets up your memory structure in the same architecture that the roms and recovery were built in. Its quick, painless and can solve many issues before they even start. Its best done right when you first start flashing as it destroys all data on the tablet, so anything you want to save needs to be backed up on a PC first.
Mantara said:
I think partitioning is an important step and really should be a mandatory step at least for the first flash. It sets up your memory structure in the same architecture that the roms and recovery were built in. Its quick, painless and can solve many issues before they even start. Its best done right when you first start flashing as it destroys all data on the tablet, so anything you want to save needs to be backed up on a PC first.
Click to expand...
Click to collapse
I agree with Mantara. I think it reduces the chances of corrupting the tablet's data. Also, repartitioning is a bigger pain if you decide to do it later when you have a like a ton of files in your internal memory and have to back it up because repartitioning reformats the internal sd card.
McGoo,
I don't disagree with Mantara that prevention might be good. You'll have to make that call.
I look at re-partitioning from the recovery perpective -- it simply hinges on the fact
that I have noticed what I believe is a correlation between Boot Loops and the need
to re-partition. Re-partitioning (and the associate wipes/etc.) seems to fix the boot
loops most of the time.
If your tablet is working fine, I go with the old computer quote "If it ain't broke, don't fix it!!!"
*********
Your other question -- I don't have a firm answer. The Android file system and the
USB stuff on the tablet -- to me operate in a strange. Kind of an OS with an arm or
two tied behind it's back. I know that's not an answer, so I'll quit.
Rev
butchconner said:
McGoo,
I don't disagree with Mantara that prevention might be good. You'll have to make that call.
I look at re-partitioning from the recovery perpective -- it simply hinges on the fact
that I have noticed what I believe is a correlation between Boot Loops and the need
to re-partition. Re-partitioning (and the associate wipes/etc.) seems to fix the boot
loops most of the time.
If your tablet is working fine, I go with the old computer quote "If it ain't broke, don't fix it!!!"
*********
Your other question -- I don't have a firm answer. The Android file system and the
USB stuff on the tablet -- to me operate in a strange. Kind of an OS with an arm or
two tied behind it's back. I know that's not an answer, so I'll quit.
Rev
Click to expand...
Click to collapse
that's the approach i'll take for now. when time comes for officially official CM7 tablet releases, i'll reformat then. until then i'll just enjoy things as they are. thanks for the feedback, all.
I'm sure there is an article or thread somewhere that outlines things like what is stored to the 2gb miniSD, what goes on the 16gb, if there is a built in memory chip and what is on that.
If anybody can point to one, I would be very appreciative.
I'd also like a link to a definitive explanation of what happens during the different types of recoveries. What is the difference between using zip files and pkg files, for example. How come some zip updates only make small changes but others can completely rewrite the phone and brick it?
What does it take to do the equivalent of formatting your computer and starting completely over with a fresh phone? I mean cleaning everything out.
What is it about this phone that a full nandroid backup will successfully bring back the phone one day and fail miserably the next?
I want to really understand this phone, because I am not going back to a smaller screen so it looks like I'm stuck with it for a while because there just doesn't appear to be a mad rush of manufacturers releasing 5 inch phones.
mid_life_crisis said:
I'm sure there is an article or thread somewhere that outlines things like what is stored to the 2gb miniSD, what goes on the 16gb, if there is a built in memory chip and what is on that.
If anybody can point to one, I would be very appreciative.
I'd also like a link to a definitive explanation of what happens during the different types of recoveries. What is the difference between using zip files and pkg files, for example. How come some zip updates only make small changes but others can completely rewrite the phone and brick it?
What does it take to do the equivalent of formatting your computer and starting completely over with a fresh phone? I mean cleaning everything out.
What is it about this phone that a full nandroid backup will successfully bring back the phone one day and fail miserably the next?
I want to really understand this phone, because I am not going back to a smaller screen so it looks like I'm stuck with it for a while because there just doesn't appear to be a mad rush of manufacturers releasing 5 inch phones.
Click to expand...
Click to collapse
There are many out there, too many to list as a matter of fact... if you just use the Search function you will find all your answers. I hate to sound rude but this is just the type of thing the search is meant for. There are several guides that outline all you want to know, but I point them out to you, you won't be any the wiser by just clicking on them. The jargon you have to go through to get to the meat of your questions will teach you everything you need to know along the way.
I've tried searching. The problem is choosing words that get usable results without also getting a ton of useless ones to wade through.
mid_life_crisis said:
I'm sure there is an article or thread somewhere that outlines things like what is stored to the 2gb miniSD, what goes on the 16gb, if there is a built in memory chip and what is on that.
Click to expand...
Click to collapse
There is no single article where you can get all of this info. Best general resource is the XDA Wiki on the Streak.
For more info on the workings of the inner SD Card see this thread at MoDaCo.
mid_life_crisis said:
I'd also like a link to a definitive explanation of what happens during the different types of recoveries. What is the difference between using zip files and pkg files, for example. How come some zip updates only make small changes but others can completely rewrite the phone and brick it?
Click to expand...
Click to collapse
The stock recovery will install .pkg files (update.pkg or OTA upgrades). These are a full replacement for the software on your phone. When installing as an update.pkg file it is best to use the recovery for the version you are installing.
When installing an OTA update the recovery that preceded the one you are installing should work if your are 'upgrading' to a ROM from the same region, the checks that are done during an OTA update will prevent a phone from one region using an OTA update from another region. The advantage to using the OTA update process is that you retain your apps and settings. OTA updates are done by downloading the file to your phone and then tapping the DL notification in the notification bar.
A custom recovery (use StreakMod recovery) will write .zip files. These files can be a theme like a new notification bar or a ROM like StreakDroid or SimpleStreak. Custom recoveries are able to write a subset of the phones software. Most custom ROMS are not a full replacement for the the phones software, which is why they may include directions to flash a certain baseband or other additional files.
mid_life_crisis said:
What does it take to do the equivalent of formatting your computer and starting completely over with a fresh phone? I mean cleaning everything out.
Click to expand...
Click to collapse
Installing a stock rom with a stock recovery from recovery mode will do this. Since a stock ROM is the whole software package this will also make sure that the baseband and amss.nbn files are all in sync (same version). Doing this or a factory reset formats the internal SD Card.
mid_life_crisis said:
What is it about this phone that a full nandroid backup will successfully bring back the phone one day and fail miserably the next?
I want to really understand this phone, because I am not going back to a smaller screen so it looks like I'm stuck with it for a while because there just doesn't appear to be a mad rush of manufacturers releasing 5 inch phones.
Click to expand...
Click to collapse
I have never had a nandroid backup fail. I use StreakMod recovery.
If you check out the links in my signature you may find more answers.
Posts like that last make me really pissed off that I can only click "Thanks" once per post.
Modding your Streak - where to start expands on my answer posted here.
There's a guy over at the official Motorola support forum with a sad problem that really could have bitten any of us at some point... he naively saved everything to the internal flash, then his phone got messed up and can no longer boot into Android. Motorola told him he has to do a factory reset, which will reformat everything, including /sdcard and the data in it (hmmm. Will it really? That does seem kind of harsh & extreme, but I can see them doing it.)
I *know* he could almost certainly pull the data off with a little help from a JTAG programmer (if only because he could probably use it to write something like Clockworkmod onto the phone, then boot into it and use THAT to copy /sdcard to an external card's /sdcard-ext), but the Photon seems to be hardcore virgin JTAG territory. I haven't even been able to find so much as a commented teardown pic with an arrow saying, "These are the JTAG testpoints", let alone something like a RIFF box with official support for the Photon. Does anybody have any ideas?
Is this the english language? I don't understand any of that lol. I have a buddy who jtags xbox's but thats it lol. Im limited to cooking roms and compiling from source. No experience to help you but ill be following this thread to learn a thing or 2.
Can you link us to the thread on the official forums?
From what you have told us, I can't figure out much. Is the phone not booting? Or is it hanging at the bootloader? Or is it stuck a the boot animation? Or is it crashing after loading the homescreen?
Basically, how much of the phone is still functional?
If the phone can still get to bootloader, put it in RSD mode. Then run RSD Lite with the same SBF version as the one thats on his phone. This will reflash the system.img, recovery, bootloader, etc, but should allow him to keep his apps and settings.
Oh, and the I believe the lesson learned here is to use Titanium Backup to backup everything on the SD card (the real sd card, not the fake internal one). TB backups everything short of the ROM and recovery/bootloader (you need a NANDroid for that). It will get his contacts, apps, data, wifi points etc.
I have flashed sbf and reset through the privacy menu. It will not clear the internal storage. There is a separate option to clear it. Not sure if they want him to clear it a different way.
Sent from my MB855 using XDA App
Here's the relevant thread, in case anybody can put him in touch with somebody who has the equipment and expertise to do the job: https://supportforums.motorola.com/thread/59942
According to my research, the Photon 4G uses a MDM6600 (according to posts in various forums). You can find the data sheet for that chip by Googling "80-Vr001-1" (I can't post links yet). It has some JTAG info in it.
If I'm not mistaken, I think the early iPhone unlocks were found by locating the JTAG pins on the radio chip, then following the circuit on the phone's PCB to find where to solder in to.
Wow
I have JTAG routers and those are easy, but a phone is much smaller in size.
All I can say is good luck -
did anyone find the correct jtag points for the board?
I have Verizon Samsung Galaxy S4 (SCH-i545) with the MDK bootloader. It is rooted, ROMed (GPE 4.4.4), has a custom kernel and custom recovery (PhilZ). I am using a Windows 7 PC (a 32 bit version.) I have nandroid backups and Titanium Backups, and now I want to do a backup to my computer to safeguard the nandroids, titaniums and also stuff like my pictures, other data, and frankly, I want as much of my phone on my computer (and browseable) as possible.
Essentially, I want a backup of my full internal sdcard (aka the built-in storage) and the microSD card. If it's easy I'd also like to backup stuff like the lowest level stuff (you know, the stuff that requires root access to modify when using a file explorer,) however that's secondary.
I am not sure what method will make the most thorough backup, but I know that dragging and dropping isn't the answer. If possible, I'd also like the backup to be broweable on Windows.
At first I was thinking just an adb pull (as detailed here), but I'm not sure if that'll capture everything that I need. Apparently Motorola blocks this method from getting everything, and I'm not sure if Samsung does too.
Then I found the natural backup function of adb, but I've heard mixed reviews, AND I'm not even sure it works if your phone has a locked bootloader (the MDK bootloader is locked; there's a workaround named loki for flashing stuff, but I doubt that matters in this case.)
This way looks like it might be very thorough, but it's a bit on the complex side, so if there's another way, I'd certainly prefer it.
Can someone please shed some light on how I could/should do this?
Hello community,
today I found myself in the situation where I was to make "the step" and try to install a cyanogenmod on my old, trusty Galaxy S2 GT-i9100 (yep, the oooold one). This phone has served me well, exceptionally well, in the past 4 years. Probably I'll get a new one for christmas, but that's not the point... even if unluckily a model I was considering (asus ze551kl) isn't sold in my country. eh, that's life... no easily replaceable batteries. but let's move on. I'll try to be as clear as possible because even if I'm somewhat ok with technology, I can't remember all terms.
I don't want to be polemic, but I want to clearly understand where I did wrong making a backup of my phone:
- first step, I rooted it. all went well, got ClockworkMod recovery "recovery os"; to me looks like a recovery operative system in all, a tiny version of android that could read the OS partition and clone it somewhere else.
- second step, I made several back-ups from the clockworkmod (Power+VolumeUp+Home) and moved them to the REAL microSD card, the tiny piece I can pull off.
- third... well, saving the cyanogenmod "cooked" .zip in /sdcard folder of the phone. I tried to reset everything, then installing the cyanogen from the CWM... surprise, it failed!
"well nothing bad, i have this nandroid backup manager that goes along pretty well with CWM, seems to see all the backups CWM does, so probably CWM is just cloning all my phone to a file that can be restored is anything goes wrong, and at the next restart I'll have everything back as nothing happened". Because on computers, I've experience that works like that. I cloned the HDD of my laptop (a ssd drive) over another HDD I had (a traditional spinning drive) and... whoah, it worked. I had the exact system on another box that I can place into the laptop and I know it will works, while i can safely do experiments on the other one. that's the purpose of backup, right?
then... I tried to restore my backup with CWM. has restored the wallpaper and the messages. nothing else. how is that possible?
not a single app installed, not one desktop configuration... i used to have 4 screens or "desktops" on my phone, with my widgets and my notes. all gone!
so... what I've missed?
how can I clone my android phone somewhere so I can restore it?
what is preventing me from doing that?
thanks in advance for the answers... has been a long night (it's 3:20 here and most of my time has been passed trying to figure out a solutionto this...) I'll check tomorrow
awambawamb said:
Hello community,
today I found myself in the situation where I was to make "the step" and try to install a cyanogenmod on my old, trusty Galaxy S2 GT-i9100 (yep, the oooold one). This phone has served me well, exceptionally well, in the past 4 years. Probably I'll get a new one for christmas, but that's not the point... even if unluckily a model I was considering (asus ze551kl) isn't sold in my country. eh, that's life... no easily replaceable batteries. but let's move on. I'll try to be as clear as possible because even if I'm somewhat ok with technology, I can't remember all terms.
I don't want to be polemic, but I want to clearly understand where I did wrong making a backup of my phone:
- first step, I rooted it. all went well, got ClockworkMod recovery "recovery os"; to me looks like a recovery operative system in all, a tiny version of android that could read the OS partition and clone it somewhere else.
- second step, I made several back-ups from the clockworkmod (Power+VolumeUp+Home) and moved them to the REAL microSD card, the tiny piece I can pull off.
- third... well, saving the cyanogenmod "cooked" .zip in /sdcard folder of the phone. I tried to reset everything, then installing the cyanogen from the CWM... surprise, it failed!
"well nothing bad, i have this nandroid backup manager that goes along pretty well with CWM, seems to see all the backups CWM does, so probably CWM is just cloning all my phone to a file that can be restored is anything goes wrong, and at the next restart I'll have everything back as nothing happened". Because on computers, I've experience that works like that. I cloned the HDD of my laptop (a ssd drive) over another HDD I had (a traditional spinning drive) and... whoah, it worked. I had the exact system on another box that I can place into the laptop and I know it will works, while i can safely do experiments on the other one. that's the purpose of backup, right?
then... I tried to restore my backup with CWM. has restored the wallpaper and the messages. nothing else. how is that possible?
not a single app installed, not one desktop configuration... i used to have 4 screens or "desktops" on my phone, with my widgets and my notes. all gone!
so... what I've missed?
how can I clone my android phone somewhere so I can restore it?
what is preventing me from doing that?
thanks in advance for the answers... has been a long night (it's 3:20 here and most of my time has been passed trying to figure out a solutionto this...) I'll check tomorrow
Click to expand...
Click to collapse
Probably a wrong recovery
To install cm13 you need a KitKat compatible recovery and to install gapps with cm13 you need to repit your device using one of the methods available, please follow one of these guides:
For (PC guide):http://forum.xda-developers.com/gal...vatives/mod-increase-partition-size-t3011162/
(Non PC guide):http://forum.xda-developers.com/android/software-hacking/tool-lanchon-repit-data-sparing-t3358036/