Related
Hey guys,
I have kind of a serious issue right now. I used Touch Recovery 5.8.0.2 and made a full backup today of my whole ROM (2.5GB) before trying out some mods which eventually didn't work. So I decided to wipe and restore the backup I made. No matter what I do I cannot get it to restore my data partition properly. I keep getting "Error while restoring /data!" message, however it does the boot image and system fine but doesn't continue to cache and sd-ext because of the failed data. Whenever I boot it up, some of my apps are missing from the home screen and practically all of them are not working when I launch them (force close). I also get boot up error of Google+ force close, among a bunch of other issues. This is happening even when I try to restore an older backup as well. My device is not working state right now and although I can just restore the stock images to get it working again, it is urgent that I restore my data ASAP! I tried wiping several times and even using the non-touch 5.5.0.4 recovery to restore and same thing keeps happening.
Any help would be highly appreciated!
Please don't tell me my backup is corrupt
Update 1: Eventually I gave up and started from scratch but I have confirmed already this happened on a fresh backup as well, at this time we are trying to figure out what is causing this so I can go back to safely backing up and restoring backups.
Update 2: We have test builds of TWRP Recovery that may have resolved this issue! We need testers!
Please see this post: Link Here
Update 3: We have test builds of ClockworkMod Recovery 6 that may have resolved this issue as well! We need testers!
Please see this post: Link Here
***Always see last few posts on the thread for updates on what we discovered just in case I don't update the OP***
Unfortunately I also have the same error today!
Please help us out.
JayantSparda said:
Unfortunately I also have the same error today!
Please help us out.
Click to expand...
Click to collapse
is your phone encrypted?
are you running stock recovery?
are you running a stock Rom?
have you done a factory reset yet?
Hi Spectre85,
My phone did fine yesterday, I was running AOPK Milestone 3 with FAUX123 kernel.
But when I woke up, my phone looked like it's battery was emtpy.
- When I plugged the phone with the charger, I started the phone again.
- Unfortunately my phone keep looping at the Google screen over and over.
So I pulled the battery and put the battery back again in the phone.
- I went to the bootloader and went to CWM recovery.
Deleted Data, Cache and Dalvike cache.
- Tried to retrieve my backup rom, but keep getting this "Error while restoring /data!" message.
I've tried to install other roms as well, but I still keep getting the bootloop at the Google screen.
Have you guys have any advice for me?
spectre85 said:
is your phone encrypted?
are you running stock recovery?
are you running a stock Rom?
have you done a factory reset yet?
Click to expand...
Click to collapse
For me, no, no (CWM Touch 5.8.0.2), yes (stock rooted 4.0.4), no but my goal is to restore my data not erase it.
I had this happen to me before, what I did was flash a factory image through fast boot and it was fine after.
Sent from my Galaxy Nexus using xda premium
Thanks guys..I flashed the factory image through Fastboot mode and the phone works perfectly again! Too bad I lost all my data, but I'm happier that I have my phone fully functional again
You can't access your backup right? There's no way you can copy the file to your desktop?
mohitrocks said:
You can't access your backup right? There's no way you can copy the file to your desktop?
Click to expand...
Click to collapse
I did copy it. I have full access to the file. Also, just fyi my goal here is not just to get to working state (I'm aware of the stock images) but to actually recover my data. My phone is currently on stock images completely blank and working now.
Fast boot flash the nand images just like u did the stock ones.
Sent from my Galaxy Nexus
bwcorvus said:
Fast boot flash the nand images just like u did the stock ones.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Nanadroid files can be flashed in fastboot? Are you sure? First time I'm hearing this. Doesn't fastboot need .img files? These are .tar files.
Open it up and see if its image...sorry all my recoveries use images.
Sent from my Galaxy Nexus
bwcorvus said:
Open it up and see if its image...sorry all my recoveries use images.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I guess it depends on the recovery version you use. I remember older versions actually had .img files. However 5.5.0.4 and Touch 5.8.0.2 both have ext4.tar files.
Which version of recovery do you use?
If you have root, you can restore your data partition using Titanium Backup. Use "Export from Nandroid Backup" within TB, select the nandroid backup and then select all apps that you want to restore
Immix said:
If you have root, you can restore your data partition using Titanium Backup. Use "Export from Nandroid Backup" within TB, select the nandroid backup and then select all apps that you want to restore
Click to expand...
Click to collapse
Interesting...will this include settings as well like my home screen icon/widget layout, wallpaper, etc?
open1your1eyes0 said:
Interesting...will this include settings as well like my home screen icon/widget layout, wallpaper, etc?
Click to expand...
Click to collapse
Yes. Titanium Backup can restore all your system apps as well as downloaded apps from a nandroid backup. Not as clean as a nandroid restore from CWM but essentially the same thing. But try to see if Titanium Backup can extract your nandroid backup. It all depends on what exactly went wrong with your nandroid backup to begin with. I don't think it restores cache. So not sure about wallpaper.
Immix said:
Yes. Titanium Backup can restore all your system apps as well as downloaded apps from a nandroid backup. Not as clean as a nandroid restore from CWM but essentially the same thing. But try to see if Titanium Backup can extract your nandroid backup. It all depends on what exactly went wrong with your nandroid backup to begin with. I don't think it restores cache. So not sure about wallpaper.
Click to expand...
Click to collapse
You're right. This works great for restore data to select apps (got my notes and game saves back). I think the icon layout is held in the launcher settings, I'm about to try and restore the data to the launcher app and see what happens. I'm making a CWM backup of first of my current state (that's assuming this backup will actually work).
EDIT: Yes! That did it! Widgets position weren't saved but it's ok I only had a few so I manually put them back. Thank you! I never knew TB had the ability to work with nandroid backups.
I guess this now just leaves me figuring out what went wrong with the CWM backup. It happened twice (I have two backups from the same day that won't restore). Does anyone else use CWM Touch 5.8.0.2 and have successful backups? I would experiment to see if it works now but I don't want to end up with a corrupt backup and redo everything again.
Yes with me its the same thing my data its corrupt is even worse every time I do a nanobackup and restarted my phone the phone freezes on the boot logo and I have to go back to recovery trying to use my backups but I can't so I have to flash a new from again and start from the beginning again!!!! Anybody here has the same experience with that ???
So AGAIN, I'm having the same issue. This time on a recovery 5.5.0.4 that used to work for me when I originally got my phone. I think either my data partition might be too big or something but this really needs to fixed pronto. Anyone know how to contact Koush directly in regards to this matter?
Specs: I had Galaxy Nexus LTE 4.0.4 w/ unlocked bootloader and root access. I have the GN toolkit if that helps.
Cause: I used the Font Installer app to change system font. I now know that not all of the fonts are working properly and emailed the developer about it. However, I am currently stuck in a boot loop after changing to one of the fonts.
I would prefer to not lose everything and if I didn't care about that, then I would just go for it and I think that I could get it working again. But since it was just a font change, I thought it might be possible to fix it without going through all of that. I am hoping I can just change some system files or something and get it to boot then select a different .tff font that I know works. THANKS!
If I reload the 4.04 update.zip that I still can access, will that wipe everything/will I have to re-setup a bunch of things? Is it OK to clear cache partition and Dalvik Cache? Thank you.
Did you take a nandroid backup of this ROM at any point? If so, you could do an advanced restore of system only.
Sent from my Galaxy Nexus using Tapatalk
cmstlist said:
Did you take a nandroid backup of this ROM at any point? If so, you could do an advanced restore of system only.
Click to expand...
Click to collapse
No, unfortunately I did not, but I will look into that once I am back up and running.
**EDIT: I have CWM Recovery v5.5.0.4 running now. Is it possible to do a backup at THIS point in time and then restore everything but system?
Druas said:
No, unfortunately I did not, but I will look into that once I am back up and running.
**EDIT: I have CWM Recovery v5.5.0.4 running now. Is it possible to do a backup at THIS point in time and then only restore system?
Click to expand...
Click to collapse
Okay. In that case, flashing the ROM's update.zip should work and shouldn't wipe your data. Best to take a nandroid backup first, just in case of trouble.
Sent from my Galaxy Nexus using Tapatalk
cmstlist said:
Okay. In that case, flashing the ROM's update.zip should work and shouldn't wipe your data. Best to take a nandroid backup first, just in case of trouble.
Click to expand...
Click to collapse
Ok I made the backup first. When I try to load the update.zip though, it says, "assert failed: appy_patch_check("/system/fonts/Roboto-Regular.ttf" <then a whole BUNCH of numbers and letters which I can type out if they will actually be helpful> "E:Error in /sdcard/Download/update.zip (Status 7) Installation aborted."
Is that an incremental update.zip for upgrading? What you need is a zip containing the entire ROM.
Alternately use fastboot to flash system.img from the stock ROM if you were already using stock.
Sent from my Galaxy Nexus using Tapatalk
cmstlist said:
Is that an incremental update.zip for upgrading? What you need is a zip containing the entire ROM.
Click to expand...
Click to collapse
Yeah I used: http://forum.xda-developers.com/showthread.php?t=1481044 So I need to install 4.0.2 first? Unfortunately that is the only upgrade.zip I have on my phone and I don't know how to load new ones on there without booting into Android.
cmstlist said:
Alternately use fastboot to flash system.i mg from the stock ROM if you were already using stock.
Click to expand...
Click to collapse
What? Can you explain further? I was using stock 4.0.4
Druas said:
Yeah I used: http://forum.xda-developers.com/showthread.php?t=1481044 So I need to install 4.0.2 first? Unfortunately that is the only upgrade.zip I have on my phone and I don't know how to load new ones on there without booting into Android.
What? Can you explain further? I was using stock 4.0.4
Click to expand...
Click to collapse
You can download another zip to your computer and use adb push to get it onto the GN's internal storage.
I don't have the CDMA version but here's what I am able to find. Check this thread:
http://forum.xda-developers.com/showthread.php?t=1481613
A completely stock 4.0.4 (aside from root, busybox, de-odex) from that thread is here:
http://dev-host.org/uMJ
So you download that to your computer and put it in the same folder as adb. Boot the phone into Clockwork Recovery and then plug it into your computer. (There are other guides to getting adb to work on your phone so I won't cover that here.) Run adb devices to make sure it sees your phone. In Clockwork you also have to go to mounts and storage and make sure /data is mounted.
Then:
adb push GalaxyNexusCDMA-4.0.4-StockRootedNoRadio.zip /sdcard/stock.zip
Subsequently in Clockwork, you will be able to find that stock.zip in the list of zips you can apply. After applying that zip, any damage caused by messing with the fonts should be reverted.
---- or ----
The alternative would be to download the factory 4.0.2 image from here:
https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz
Inside that archive is a system.img file which you can flash to the phone by fastboot over USB. Immediately afterwards, you would then boot into CWM and apply the incremental update.zip you already have on there. This will take you to stock 4.0.4 unrooted and hopefully bootable!
cmstlist said:
The alternative would be to download the factory 4.0.2 image from here:
Inside that archive is a system.img file which you can flash to the phone by fastboot over USB. Immediately afterwards, you would then boot into CWM and apply the incremental update.zip you already have on there. This will take you to stock 4.0.4 unrooted and hopefully bootable!
Click to expand...
Click to collapse
While your instructions were good, I tried some things on my own about 20 min before you made that post and screwed up and erased userdata. So, I cannot say for sure if it would have worked, but I bet it would have and I wish I had been more patient.
Sorry to hear. Is it bootable now at least?
The userdata erase problem is why I now have to remember in every phone recovery situation - adb pull the entire contents of internal storage from within CWM before doing anything risky.
Sent from my Galaxy Nexus using Tapatalk
Yeah the phone has booted, I just have to spend some time recovering what I can. I will hopefully make better backups for the future. At least I learned some stuff. I still can't believe this was all caused by changing a FONT in a program designed to change fonts.
Druas said:
Yeah the phone has booted, I just have to spend some time recovering what I can. I will hopefully make better backups for the future. At least I learned some stuff. I still can't believe this was all caused by changing a FONT in a program designed to change fonts.
Click to expand...
Click to collapse
Right, well this font changer program edits the system partition of your phone, which makes it risky. In the future, the best course of action with any "risky" change is:
- Take a nandroid backup first.
- Copy the nandroid backup out of the phone (it's in a subfolder of clockworkmod on internal storage).
- If you are doing anything that leads you to fear that the whole internal storage could get blanked, copy all of that out of the phone too.
- Now if you can't boot, you can selectively restore the system partition or the whole thing to try and fix it.
- And now if your internal storage gets blanked, your backup is safe.
cmstlist said:
Right, well this font changer program edits the system partition of your phone, which makes it risky. In the future, the best course of action with any "risky" change is:
- Take a nandroid backup first.
- Copy the nandroid backup out of the phone (it's in a subfolder of clockworkmod on internal storage).
- If you are doing anything that leads you to fear that the whole internal storage could get blanked, copy all of that out of the phone too.
- Now if you can't boot, you can selectively restore the system partition or the whole thing to try and fix it.
- And now if your internal storage gets blanked, your backup is safe.
Click to expand...
Click to collapse
Yeah I had no idea that there was a significant risk involved, otherwise I would have been more cautious. Some questions I have:
-With Titanium Backup, the only thing I need to be running batch backups of is all user apps + system data correct? And only restore apps not system data unless I am on the exact same ROM as before?
-Again with TB, is there stuff it consistently misses that I should backup manually?
-I always launched CWM Recovery through the GN toolkit using "6. Flash CWM Recovery, Standard." And sometimes I would select Recovery from the Fastboot menu and it would be back at the regular recovery. Is there a different way I should have been going about getting to the nandroid backup?
-I have now installed ROM Manager and hit "Flash CWM Recovery" and I have a nandroid backup when I reboot into recovery. Does this mean any time I choose Recovery from the Fastboot menu that it will boot into CWM Recovery?
Thanks again for all your help and advice!
Hello again.
Since I am under 10 posts and not allowed to participate in the relevant thread plus searching didn't yield any results I am posting here.
After one month of using my nexus I want to play with it and try some custom things that all people talk so much about.Fact is I first want to backup current state where everything works fine in case something goes wrong.
I 've already backed up my apps and their data with Titanium Backup.
Now I need current OS state bootloader, etc.Am I right to believe this is the NANDROID backup? Is this the backup that can bring the phone back to its current state?
Second thing is that the Galaxy Nexus Toolkit v7.8.0 I am using recommends backing up the EFS partition.Did some research that revealed this hidden partition is about the IMEI - I can't understand how such a valuable data isn't hardcoded inside the phone.But nevertheless I would like to know where are those backups (NANDROID and ESF partition) stored (already checked backups folder in toolkit).
My phone's current state is: unlocked bootloader, CWM recovery, rooted and on stock 4.1.1.No mods or any other custom file.
Another question regarding the CWM recovery.How is it possible to go back to the stock recovery? By flashing the stock ROM?
Also from GN Toolkit I flashed CWM Touch but after trying an update through CWM ROM Manager I got the manual version (both 6.0.1).Can I reflash the touch version from Toolkit?
Sorry if some of those questions sound silly but I am new in Android and prefer the safe path.
Thank you in advance.
TR-909 said:
Hello again.
Since I am under 10 posts and not allowed to participate in the relevant thread plus searching didn't yield any results I am posting here.
After one month of using my nexus I want to play with it and try some custom things that all people talk so much about.Fact is I first want to backup current state where everything works fine in case something goes wrong.
I 've already backed up my apps and their data with Titanium Backup.
Now I need current OS state bootloader, etc.Am I right to believe this is the NANDROID backup? Is this the backup that can bring the phone back to its current state?
Second thing is that the Galaxy Nexus Toolkit v7.8.0 I am using recommends backing up the EFS partition.Did some research that revealed this hidden partition is about the IMEI - I can't understand how such a valuable data isn't hardcoded inside the phone.But nevertheless I would like to know where are those backups (NANDROID and ESF partition) stored (already checked backups folder in toolkit).
My phone's current state is: unlocked bootloader, CWM recovery, rooted and on stock 4.1.1.No mods or any other custom file.
Another question regarding the CWM recovery.How is it possible to go back to the stock recovery? By flashing the stock ROM?
Also from GN Toolkit I flashed CWM Touch but after trying an update through CWM ROM Manager I got the manual version (both 6.0.1).Can I reflash the touch version from Toolkit?
Sorry if some of those questions sound silly but I am new in Android and prefer the safe path.
Thank you in advance.
Click to expand...
Click to collapse
toolkit is not a safe path for you.
read these:
http://forum.xda-developers.com/showthread.php?t=1812959
http://forum.xda-developers.com/showthread.php?t=1626895
http://forum.xda-developers.com/showthread.php?t=1529058
http://forum.xda-developers.com/showthread.php?t=1420351
learn how to troubleshoot and search, you'll be a whole lot happier. don't use toolkits.
TR-909 said:
Now I need current OS state bootloader, etc.Am I right to believe this is the NANDROID backup? Is this the backup that can bring the phone back to its current state?
Click to expand...
Click to collapse
nandroid doesn't backup the bootloader. if you ever need to go back to a specific bootloader version (which you won't), it is available online.
bk201doesntexist said:
toolkit is not a safe path for you.
read these:
http://forum.xda-developers.com/showthread.php?t=1812959
http://forum.xda-developers.com/showthread.php?t=1626895
http://forum.xda-developers.com/showthread.php?t=1529058
http://forum.xda-developers.com/showthread.php?t=1420351
learn how to troubleshoot and search, you'll be a whole lot happier. don't use toolkits.
nandroid doesn't backup the bootloader. if you ever need to go back to a specific bootloader version (which you won't), it is available online.
Click to expand...
Click to collapse
That's a lot of reading.
Anyway thanks for pointing me to those threads (I don't mind reading hehe) but still I don't understand why toolkit is so bad.In my view the toolkit just automates a set of commands which otherwise I would have to give through a command prompt.Only good thing I can find avoiding a toolkit, is getting a deeper knowledge on the subject but maybe the risks of doing something wrong are increased (say a typo)?
Anyway let me read those and I may be back.
TR-909 said:
That's a lot of reading.
Anyway thanks for pointing me to those threads (I don't mind reading hehe) but still I don't understand why toolkit is so bad.In my view the toolkit just automates a set of commands which otherwise I would have to give through a command prompt.Only good thing I can find avoiding a toolkit, is getting a deeper knowledge on the subject but maybe the risks of doing something wrong are increased (say a typo)?
Anyway let me read those and I may be back.
Click to expand...
Click to collapse
Toolkit is a automated set of other people's command, programme are coded by humans and human errors are bound to happen, not to mention if something went wrong somewhere, you won't know what went wrong. By doing the steps yourself, you will know exactly what went wrong, and it will simplify things should you have to ask questions here, which you most likely don't have to once you know how to use adb and fastboot, trust me.
Typos while doing your commands won't hurt because it simply will fail and not do anything. Immediately you will know you typed something incorrectly and know you have to do it again. With the kit you will not know at which step it failed so figuring out something will become a task. Doing it yourself sounds like it's longer and difficult but once you do it you will see how easy and simple it is plus you will understand what you did and why.
Sent from my Galaxy Nexus
TR-909 said:
[snip]
Now I need current OS state bootloader, etc.Am I right to believe this is the NANDROID backup? Is this the backup that can bring the phone back to its current state?
Click to expand...
Click to collapse
Yes and yes.
TR-909 said:
Second thing is that the Galaxy Nexus Toolkit v7.8.0 I am using recommends backing up the EFS partition.Did some research that revealed this hidden partition is about the IMEI - I can't understand how such a valuable data isn't hardcoded inside the phone.But nevertheless I would like to know where are those backups (NANDROID and ESF partition) stored (already checked backups folder in toolkit).
Click to expand...
Click to collapse
I won't comment on the toolkit, but nandroid backups are stored in /sdcard/clockworkmod/backup/ on your device.
As for the efs partition, you could back it up, but I don't really see what the necessity of it is. That partition is never written to by any ROM (stock or otherwise), so the only way it will get messed up is if you do something to it.
If you want to back it up on your device, just open a terminal window and type:
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/efs of=/sdcard/efs.img
That will store it in /sdcard, and then just copy it off your device.
TR-909 said:
Another question regarding the CWM recovery.How is it possible to go back to the stock recovery? By flashing the stock ROM?
Click to expand...
Click to collapse
Just pull the recovery.img file out of the version of the stock factory image that you are currently using, place it in the same directory where you have your fastboot.exe file, reboot your device into fastboot mode and type:
fastboot flash recovery recovery.img
Or, just save it to /sdcard on your device and type the following in a terminal:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
TR-909 said:
Also from GN Toolkit I flashed CWM Touch but after trying an update through CWM ROM Manager I got the manual version (both 6.0.1).Can I reflash the touch version from Toolkit?
Click to expand...
Click to collapse
Can't help you out with any toolkit, sorry.
Hello efrant.
Seems you are the n00bs hero in here! I was reading your FAQ and threw some basic ADB commands through cmd to see how it feels ,lol.
Well reading made some good, I backed up through CWM but the backup size baffles me - only 21.4MB in total.Is this normal?
Also took a fresh backup with Titanium for all apps and data - this is a lot bigger 728MB in total.Still Storage (in Settings) reports that applications and their data hold 3.54GB.Is there some kind of ultra compression involved?
As for the stock bootloader I found that image (recovery-stock-jro03c-maguro) which I think is for my GN (GSM).I am asking in case something bad happens and go for a warranty claim.In that case I believe I 'll need to flash the stock bootloader, stock ROM and finally lock the bootloader.
As for the EFS partition is it impossible to be harmed? Say File System corruption, sdcard bad blocks, etc?
It's ok.I clearly understand your position on the toolkit and any similar programms out there.It's just they are so "convenient" and "time savers".Still you 're all right that most of the time you do not understand what you are doing when using toolkits.
Thanks to all of you for your great help. :good:
PS - to test my progress I am going to flash stock recovery through flashboot.I just hope I won't mess it up. :fingers-crossed:
To clear a few things:
TR-909 said:
As for the stock bootloader I found that image (recovery-stock-jro03c-maguro) which I think is for my GN (GSM).I am asking in case something bad happens and go for a warranty claim.In that case I believe I 'll need to flash the stock bootloader, stock ROM and finally lock the bootloader.
Click to expand...
Click to collapse
we don't have any custom bootloaders, as of yet.
TR-909 said:
As for the EFS partition is it impossible to be harmed? Say File System corruption, sdcard bad blocks, etc?
Click to expand...
Click to collapse
not impossible, but many many users never had any issues. to be on the safe side, back it up.
TR-909 said:
It's ok.I clearly understand your position on the toolkit and any similar programms out there.It's just they are so "convenient" and "time savers".Still you 're all right that most of the time you do not understand what you are doing when using toolkits.
Thanks to all of you for your great help. :good:
Click to expand...
Click to collapse
glad you understand. just because something is convenient doesn't mean that it's the best for you.
TR-909 said:
PS - to test my progress I am going to flash stock recovery through flashboot.I just hope I won't mess it up. :fingers-crossed:
Click to expand...
Click to collapse
easy. you can't fail with fastboot. like said before, if you type it wrong, it won't go through. :good:
'fastboot flash recovery recovery.img'
done.
Regarding the nandroid, copy off the whole clockworkmod folder.
Will the next nexus have a longer screen?
@bk201doesntexist: yes you 're right I was reffering to the stock recovery image.Thanks for correcting me
@Mach3.2: I 've read just the backup folder is needed (the one with the date and time).
For the sake of learning, I started in ADB then:
adb devices : to check I am online
adb reboot-bootloader: to get into fastboot
fastboot devices: check again status
and then
fastboot recovery recovery-CWM-touch-6.0.1-maguro
blah...
blah...
blah...
Finished and voila CWM touch recovery installed. :victory:
I am going to try with stock recovery but I am trying to find an official source to download it (if any).
EDIT: I see the only way to find the original recovery img is to extract it from the official ROM.So I am downloading from Google a .tgz and will continue from there.
Any comments for my backup sizes?
Now with my backups in hand what is the possible way to verify them? In theory with nandroid (from CWM recovery) and Titanium, I can restore phone in today's state.Right or wrong?
I am thinking of going a bit further flashing the stock ROM again (wiping everything) and then recovering from the backup archives as my next learning exercise.I should obviously backup photos, music, etc but I was wondering if SMS history is taken care by Nandroid or have to use a seperate application.Contacts are in google's server so np on that.
Thanks again.
TR-909 said:
[snip]
Well reading made some good, I backed up through CWM but the backup size baffles me - only 21.4MB in total.Is this normal?
Also took a fresh backup with Titanium for all apps and data - this is a lot bigger 728MB in total.Still Storage (in Settings) reports that applications and their data hold 3.54GB.Is there some kind of ultra compression involved?
Click to expand...
Click to collapse
If you are using the 6-series CWM, it does backups a little differently (incrementally), and stores the backup in two locations in /sdcard/clockworkmod. I personally use 5.5.0.2, which does a full backup and stores it in one location.
TR-909 said:
As for the stock bootloader I found that image (recovery-stock-jro03c-maguro) which I think is for my GN (GSM).I am asking in case something bad happens and go for a warranty claim.In that case I believe I 'll need to flash the stock bootloader, stock ROM and finally lock the bootloader.
Click to expand...
Click to collapse
As was mentioned above, all bootloaders available are stock bootloaders. A list can be found in the bootloader thread (link in my signature).
TR-909 said:
As for the EFS partition is it impossible to be harmed? Say File System corruption, sdcard bad blocks, etc?
Click to expand...
Click to collapse
But if you have bad blocks in the efs partition, you would probably need to get a new device, at which point you have no need for the backup, no? But I guess yes, better safe than sorry.
TR-909 said:
In theory with nandroid (from CWM recovery) and Titanium, I can restore phone in today's state.Right or wrong?
Click to expand...
Click to collapse
With a nandroid alone you can return to today's state.
TR-909 said:
I am thinking of going a bit further flashing the stock ROM again (wiping everything) and then recovering from the backup archives as my next learning exercise.I should obviously backup photos, music, etc but I was wondering if SMS history is taken care by Nandroid or have to use a seperate application.Contacts are in google's server so np on that.
Click to expand...
Click to collapse
Wiping from CWM does not wipe the data you have on /sdcard, so no need to backup photos, music, etc.
SMS will get wiped, but both Titanium and a nandroid will back them up. However, you can use a third-party app (there are many of them) to do it as well, which is simpler actually.
TR-909 said:
@bk201doesntexist: yes you 're right I was reffering to the stock recovery image.Thanks for correcting me
@Mach3.2: I 've read just the backup folder is needed (the one with the date and time).
For the sake of learning, I started in ADB then:
adb devices : to check I am online
adb reboot-bootloader: to get into fastboot
fastboot devices: check again status
and then
fastboot recovery recovery-CWM-touch-6.0.1-maguro
blah...
blah...
blah...
Finished and voila CWM touch recovery installed. :victory:
I am going to try with stock recovery but I am trying to find an official source to download it (if any).
EDIT: I see the only way to find the original recovery img is to extract it from the official ROM.So I am downloading from Google a .tgz and will continue from there.
Any comments for my backup sizes?
Now with my backups in hand what is the possible way to verify them? In theory with nandroid (from CWM recovery) and Titanium, I can restore phone in today's state.Right or wrong?
I am thinking of going a bit further flashing the stock ROM again (wiping everything) and then recovering from the backup archives as my next learning exercise.I should obviously backup photos, music, etc but I was wondering if SMS history is taken care by Nandroid or have to use a seperate application.Contacts are in google's server so np on that.
Thanks again.
Click to expand...
Click to collapse
The backup is just a shell, it's backed up in blobs, so you will need to copy the whole thing off.
You 're both right that in that the CWM recovery "image" is incremental and the base backup is the blops folder - now the total size is 1.75GB which is logical.
@efrant: thanks for clarifying on backup now it all starts making sense.I 've read Titanium Backup can pull individual files (may I call it selective restore) from a Nandroid backup, say a single app and its data.If that is so then the Titanium Backup could be used as a reserve app and that could save me some precious space.
efrant said:
SMS will get wiped, but both Titanium and a nandroid will back them up. However, you can use a third-party app (there are many of them) to do it as well, which is simpler actually.
Click to expand...
Click to collapse
I prefer to use less apps for doing the job so if Nandroid has the data it is fine with me.I hope it isn't that complicated to pull the data out.
@Mach3.2: You were right, my bad.The article I read was about CWM recovery 5.5.0.2 so now I copied the whole thing on PC. :good:
TR-909 said:
[snip]
I prefer to use less apps for doing the job so if Nandroid has the data it is fine with me.I hope it isn't that complicated to pull the data out.
Click to expand...
Click to collapse
The issue is that SMS's are stored as data for a specific system app (I can't remember which one at the moment). If you change ROMs, it is generally not a good idea to restore system apps or system app data via Titanium Backup, as those apps/data could cause some instability. You may get lucky, you may not.
efrant said:
The issue is that SMS's are stored as data for a specific system app (I can't remember which one at the moment). If you change ROMs, it is generally not a good idea to restore system apps or system app data via Titanium Backup, as those apps/data could cause some instability. You may get lucky, you may not.
Click to expand...
Click to collapse
Point taken.:good:
A bit more on the backup subject...
As I can see CWM recovery backups boot image, recovery image and the /system partition.I also saw in one of efrant's posts about different bootloaders but honestly I fail to comprehend the need for flashing a bootloader.
*In your "convert to latest yakju" post you recommend flashing it "5) Optional (NOT optional for n00bs) -- Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img (or whatever the name of the bootloader image that you downloaded)."
** Also the radio partition is a mystery so far.And I 've read a lot of guys talking of better connectivity (be it GSM, 3G, WiFi) through flashing custom (?) radio images.On list to be explored...
The recovery image is pretty straight and the system partition is the one with the OS - now all this can't be 1.7GB unless it backups the userdata partition too.
EDIT: It seems it also backups the data folder (hence the apps) so the size now makes sense.I reverted to 5.5.0.2 because incremental backup is fast and slick but brings two issues: first the "blops structure" gives me problems when I want to transfer those thousands of files via MTP and second it is much more practical when I want to backup completely different "builds" (that is my guess).
Also in between flashing ROMs a standard procedure is recommended about wiping data, clearing dalvik cache, etc
Could you please give me in details the series of tasks needed (or point me to a thread) for properly preparing a custom ROM installation when unlocked and rooted?
About restoration in the "new enviroment" I read this:
"If your bootloader is unlocked: yes, you can root (if you haven't done it already) and use TiB to backup apps + app data. Installing a ROM will not wipe your /sdcard. It's always a good idea to back it up though before a flash. Use TiB to restore apps + appdata to your new ROM. Be careful with system apps and settings, restoring such data can lead to issues."
Am I right in that "illegal" system apps are those painted with red colour in TiB?
Final steps I am going to backup SMS history and find a custom ROM to install.Any ROM recommendations for a "novice user" are welcome...
Off Topic: what would be the adb commands to push/pull folders (or files) from /sdcard to PC (eg. \sdcard\clockworkmod --> C:/Nexus) .Right now I am doing MTP transfers but would prefer the "adb way" if possible.
Thanks a lot for your support and sharing of knowledge!
PS - So much reading!
Wow, that's a lot of questions for one post! I'll try to tackle some of them.
TR-909 said:
As I can see CWM recovery backups boot image, recovery image and the /system partition.I also saw in one of efrant's posts about different bootloaders but honestly I fail to comprehend the need for flashing a bootloader.
*In your "convert to latest yakju" post you recommend flashing it "5) Optional (NOT optional for n00bs) -- Flash the bootloader: fastboot flash bootloader bootloader-maguro-primela03.img (or whatever the name of the bootloader image that you downloaded)."
Click to expand...
Click to collapse
I don't think anyone knows what changes are in each new bootloader revision (given that they are closed source), but some have had issues with running Jelly Bean on bootloaders older than LA03. I guess "newer is better" holds true in this case.
TR-909 said:
** Also the radio partition is a mystery so far.And I 've read a lot of guys talking of better connectivity (be it GSM, 3G, WiFi) through flashing custom (?) radio images.On list to be explored...
Click to expand...
Click to collapse
Again, no one know what changes are made in each radio revision. I personally have not noticed much difference among a lot of the radios, but others have said otherwise. (And no, there are no "custom" radios. All radios are stock -- just from different versions of Android. (A list of radios can be found in the radio link in my signature.)
TR-909 said:
The recovery image is pretty straight and the system partition is the one with the OS - now all this can't be 1.7GB unless it backups the userdata partition too.
EDIT: It seems it also backups the data folder (hence the apps) so the size now makes sense.
Click to expand...
Click to collapse
Yup, it backs up the cache, boot, recovery and system partitions, and everything in /data except /data/media (which is /sdcard).
TR-909 said:
I reverted to 5.5.0.2 because incremental backup is fast and slick but brings two issues: first the "blops structure" gives me problems when I want to transfer those thousands of files via MTP and second it is much more practical when I want to backup completely different "builds" (that is my guess).
Click to expand...
Click to collapse
I also like 5.5.0.2. I found it to be the most compatible, i.e., it has no issues flashing anything (that I have tried anyway), whereas other versions have issues with certain things.
And I personally wouldn't use MTP to transfer files -- it is flaky at best. ADB is much more stable.
TR-909 said:
Also in between flashing ROMs a standard procedure is recommended about wiping data, clearing dalvik cache, etc
Could you please give me in details the series of tasks needed (or point me to a thread) for properly preparing a custom ROM installation when unlocked and rooted?
Click to expand...
Click to collapse
There is not much to do:
1) Download ROM to /sdcard
2) Reboot into recovery
3) Nandroid
4) Wipe /data and /cache
5) Flash ROM
6) Reboot
TR-909 said:
About restoration in the "new enviroment" I read this:
"If your bootloader is unlocked: yes, you can root (if you haven't done it already) and use TiB to backup apps + app data. Installing a ROM will not wipe your /sdcard. It's always a good idea to back it up though before a flash. Use TiB to restore apps + appdata to your new ROM. Be careful with system apps and settings, restoring such data can lead to issues."
Am I right in that "illegal" system apps are those painted with red colour in TiB?
Click to expand...
Click to collapse
I think so. I haven't use TB in a while, so I just checked and it looks like you are correct -- red.
TR-909 said:
Off Topic: what would be the adb commands to push/pull folders (or files) from /sdcard to PC (eg. \sdcard\clockworkmod --> C:/Nexus) .Right now I am doing MTP transfers but would prefer the "adb way" if possible.
Click to expand...
Click to collapse
Have a read of the "basics" link in my signature. ADB is covered there.
Wow that's some great answers and a big motive for me to continue "digging".:good:
I will leave you in peace for the time being as here it's about to dawn.
Big thanks and have a nice day.
PS - To be continued...
There is a article on the main xda site about running a FTP server on your phone, maybe that will transfer the blobs faster than MTP.
Mach3.2 said:
There is a article on the main xda site about running a FTP server on your phone, maybe that will transfer the blobs faster than MTP.
Click to expand...
Click to collapse
Hey mach3.2.
FTP wouldn't help because WLAN (802.11g) can't beat USB 2.0 speeds.In fact it is quite slow for such file sizes.You 're right though in that through ES File Explorer I can send the whole Clockworkmod folder (and the blobs) normally to my PC without the "invisible files" issue I encountered with Windows Explorer and MTP.
Thanks for suggestion!
TR-909 said:
Hey mach3.2.
FTP wouldn't help because WLAN (802.11g) can't beat USB 2.0 speeds.In fact it is quite slow for such file sizes.You 're right though in that through ES File Explorer I can send the whole Clockworkmod folder (and the blobs) normally to my PC without the "invisible files" issue I encountered with Windows Explorer and MTP.
Thanks for suggestion!
Click to expand...
Click to collapse
With MTP, copying using FTP may just be faster
And just to mention, there's 802.11N on you devices, although it's only single stream w/ 1 antenna..
So I've been trying out a bunch of roms and I've decided I want to go back to a previous nandroid backup on TWRP that I made. I wipe everything, restore the backup and reboot, but it never boots past the stock Google animation (4 spinning dots, running CleanRom). Does anybody know how to fix this? Am I improperly restoring the backup, and if so how should I do it?
tannerrblake said:
So I've been trying out a bunch of roms and I've decided I want to go back to a previous nandroid backup on TWRP that I made. I wipe everything, restore the backup and reboot, but it never boots past the stock Google animation (4 spinning dots, running CleanRom). Does anybody know how to fix this? Am I improperly restoring the backup, and if so how should I do it?
Click to expand...
Click to collapse
Restoring a nandroid backup is as easy as it gets. More than likely your backup nandroid is corrupt. You probably just have to install the basic ROM and start new.
That's what I ended up doing. Is it just bad luck on my end that it ended up like that? I don't want to continue making backups that won't work haha.
tannerrblake said:
That's what I ended up doing. Is it just bad luck on my end that it ended up like that? I don't want to continue making backups that won't work haha.
Click to expand...
Click to collapse
germanguy is correct, you will need to start afresh
may be prudent to reflash a fresh recovery also
and if you have no rom or working backup on your internal sd, see my sig
exocetdj said:
germanguy is correct, you will need to start afresh
may be prudent to reflash a fresh recovery also
and if you have no rom or working backup on your internal sd, see my sig
Click to expand...
Click to collapse
How would I go about flashing a new recovery? Thanks for the replies, appreciate it.
tannerrblake said:
How would I go about flashing a new recovery? Thanks for the replies, appreciate it.
Click to expand...
Click to collapse
get your custom recovery img and place it in your fastboot (or adb or whatever you called it) folder on your pc, for ease, rename it recovery.img
boot phone into fastboot
open up cmd and then type "fastboot flash recovery recovery.img"
then "fastboot erase cache"
then you should have a fresh recovery without any issues installed
exocetdj said:
get your custom recovery img and place it in your fastboot (or adb or whatever you called it) folder on your pc, for ease, rename it recovery.img
boot phone into fastboot
open up cmd and then type "fastboot flash recovery recovery.img"
then "fastboot erase cache"
then you should have a fresh recovery without any issues installed
Click to expand...
Click to collapse
Thanks so much. Now that I think about it I don't know for sure if I'm on the latest version of TWRP, so I'll try that.
tannerrblake said:
Thanks so much. Now that I think about it I don't know for sure if I'm on the latest version of TWRP, so I'll try that.
Click to expand...
Click to collapse
always best to be on latest version, i use philz but its down to personal preference, they all do the same thing well lol
What version of TWRP?
I had the same thing happen on my M8 back when I got it in early May. Couldn't get the nandroid to restore, so I ended up just flashing the desired ROM again and setting up the phone manually.
I've since updated TWRP and the restore works (new nandroid). Not sure if it was just a random thing, or a bug with that particular version of TWRP. But updating TWRP is a good place to start.
when you enter tw you make a factory reset
thats clear
but what with this clear dalvik and restore boot option
here must be the troubleshooting solution
Hi,
I recently tried a custom rom on my old phone and it worked pretty well. I liked the OS and now want to also do that on my current phone. But i do still have a few questions i hope you can help me with.
- Can i make a full backup of my phone (with app data) to my PC or maybe to my old phone? I am currently not rooted and tried helium backup but saw that sadly not all apps allow a backup.
- I know about titanium backup. Is there some way (if the above cant be done) i can root my phone without wiping the phone? So i can then use titanium backup to make a proper backup with data, then install the custom rom and after restore the apps+data.
In short: I hope i can somehow make a full backup with app data so i can install the custom rom and restore my app data again.
Looking forward to your replies.
Thanks in advance.
Nothing? No one ? =(
To root you need to unlock the bootloader, which wipes all user data. So you can't use root to backup your data. This is why I unlock the bootloader immediately after getting a phone.
You can try an adb backup though.
razr96 said:
To root you need to unlock the bootloader, which wipes all user data. So you can't use root to backup your data. This is why I unlock the bootloader immediately after getting a phone.
You can try an adb backup though.
Click to expand...
Click to collapse
Thank you for your reply and thx for the tip. Ill be doing that too from now on when i get a phone.
As long as i can make a full backup with abd (with app data), Im fine with wiping to root it. But just wanted to make sure i can get app data back after the root process.
Do you happen to have a link to a proper backup using abd guide?
Thanks
no
sm00th4f3 said:
https://forum.xda-developers.com/android/general/how-to-backup-restore-android-device-t3602583
You might wanna read this and try it
https://forum.xda-developers.com/android/help/adb-fastboot-commands-bootloader-kernel-t3597181
Click to expand...
Click to collapse
Well with a few side searches i was able to open the cmd (admin), do a adb devices (which found a device) and then run the app + data command.
('adb backup -apk -shared -all -system -f C:\backup.ab')
I saw the screen on my phone to start it, which i did but it stays on Shared Storage (where before this mentioned the apk's that were being backed up). This is taking pretty long (as in hours). Is this normal or did something went wrong and is it stuck on that part?
Edit (Update): I stopped the whole thing and tried again. Now it finished in about 10 - 15 min. I did get a message "backup finished". However in the folder i gave up, there is nothing to see. folder is still empty
Edit2 (update): Found the backup.ab file. Apparently it was in a different folder i thought it would be. So if i then also make a copy of the internal storage and do this command, i should be good right? After doing that, unlock and root, i can use the 'adb restore C:\backup.ab' and have all apps + app data back as it was before the unlock/root ?
no
sm00th4f3 said:
In a sense. Yes, but you might wanna read some threads about that first.. Otherwise. No one would wanna go back after unlocking his phone. Since restoring a backup from a locked phone on an unlocked phone can cause some issues.
Click to expand...
Click to collapse
I'm not really sure what you mean though.
If i unlock my phone with my code and then make the backup with adb and just in case, a copy of my internal storage, can't i use restore on the unlocked/rooted phone to have the apps + their data back and use them again ?
no
sm00th4f3 said:
No you can't. It will brick your device. The backup can only be used when your phone is still locked. So it is basically not needed at all.
Click to expand...
Click to collapse
So you are saying that there is no possibility to backup my apps+data, unlock/root/custom rom, and then restore my apps+data at all?
That was some what the question of my first post.
So its either, fully wipe with everything lost, then root etc. etc. or just keep it the way i have it now?
no
sm00th4f3 said:
The normal procedure is as follows:
After an unlock.- your data always gets formatted. So a backup is totally wasted time.
The backup isn't wasted time - if it is done after unlocking your phone, while it still has stock rom.
In case flashing goes wrong, make the backup while not having flashed twro etc at all.
You don't have to wipe anything if you just want root, since the phone will reset-wipe your data on its very own.
Just unlock it, let it reboot, Flash twrp, install root zip file. Reboot
In case of flashing a custom rom. Flash twrp, boot to twrp. Use the Reboot menu and reboot again into recovery
Reboot->Recovery (in twrp menu).
Then Wipe-> Factory Reset
Wipe-> Advanced Wipe-> Wipe System partition only
Wipe-> Advanced wipe-> select Data partition-> Change file system to ext4
Reboot Menu in TWRP->Recovery
Wipe Dalvik and Cache
Flash Rom
Flash Gapps if not stated otherwise in Instructions of Rom Thread
Flash Magisk or SUperSu , depends if you want root or not. If you don'T want encryption on older Roms, flash one of the two.
Encryption will later on be optional through Phone Security Options.
Wipe dalvik and cache.
Reboot.
Wait a bit.
Setup phone, done.
Click to expand...
Click to collapse
Yes but as you mentioned, unlocking means a full wipe. And i cant restore apps + their data from a stock phone backup to an unlocked phone as it can cause issues.
In my very first post i asked if i could make a backup of the apps + their data to restore them after unlocking/rooting/custom rom or whatever. Simple answer then is no.
So i either have to just wipe my phone and basically start all over, only unlock/root etc etc first.
Or just keep my phone stock like how it is now and just do nothing and wait until i get a new phone (which will be in a long time still)