HTC One V [CDMA], Virgin Mobile US, original (pre-OTA) radio version, TWRP recovery
Has anyone else experienced flakiness with Nandroid backups on this phone? All of them that I've done with major OS changes—even after factory reset—have failed to produce a working restore even though they were taken from a working state.
I'm also unable to get back my previously-working CM 10.1 ROM even though I followed the exact same procedures (with the same files) that I used to get it working before.
This has been happening since my first failed Nandroid restore trying to go back from CM 10.1 to the HTC Sense Nandroid backup I made before attempting CM 10.1 in the first place. I thought this was due to the Sense Nandroid having been made under the OTA-upgraded radio version (I had to use the stock rom.zip from the RUU to get CM 10.1 working at all), but now I'm not so sure. I get the HTC logo and angry red legal text indefinitely now with those setups.
I can't even get back to the Nandroid I made of the stock HTC Sense ROM right after I restored from the RUU's rom.zip.
Anyone have any idea what I'm doing wrong? Or is this model really just that much of a pain?
Are you flashing the correct kernel in fastboot after completing the restore? The recovery is not able to flash a kernel, that still needs to be done through fastboot, even with a nandroid restore.
riggerman0421 said:
Are you flashing the correct kernel in fastboot after completing the restore? The recovery is not able to flash a kernel, that still needs to be done through fastboot, even with a nandroid restore.
Click to expand...
Click to collapse
That's the boot.img, right? I did try flashing that after the restore didn't work the first time. No joy.
EDIT: Actually, that explains why some of my restores have failed, but not all of them.
EDIT 2: Mystery solved. I think. The Nandroid backup I took yesterday evening must be broken somehow. I noticed a few minutes ago that TWRP wasn't actually telling me that it finished restoring the backup—it was just taking me back to the home screen. I switched to CWM Recovery to grab a backup I took yesterday Morning, and that one worked.
So now I'm just left extremely disconcerted that I can't be certain my backups are reliable.
mynewshiny said:
That's the boot.img, right? I did try flashing that after the restore didn't work the first time. No joy.
EDIT: Actually, that explains why some of my restores have failed, but not all of them.
EDIT 2: Mystery solved. I think. The Nandroid backup I took yesterday evening must be broken somehow. I noticed a few minutes ago that TWRP wasn't actually telling me that it finished restoring the backup—it was just taking me back to the home screen. I switched to CWM Recovery to grab a backup I took yesterday Morning, and that one worked.
So now I'm just left extremely disconcerted that I can't be certain my backups are reliable.
Click to expand...
Click to collapse
I originally thought this was just an isolated incident, but it seems to be recurring. Several of the Nandroid backups I've made more recently, both within TWRP Recovery and via the Online Nandroid Backup app, seem to produce this result. (Fortunately, I have a known good backup that I've been able to use reliably.)
Is there a way to validate a Nandroid backup other than trying to restore from it? I don't mean comparing a hash (which is what I find using Google), but rather making sure that the original, uncorrupted file is valid for use as a backup.
As a side note, every backup I've done with CWM Recovery has been reliable, so my fallback plan is to switch to CWM. I just find TWRP easier to navigate.
mynewshiny said:
I originally thought this was just an isolated incident, but it seems to be recurring. Several of the Nandroid backups I've made more recently, both within TWRP Recovery and via the Online Nandroid Backup app, seem to produce this result. (Fortunately, I have a known good backup that I've been able to use reliably.)
Is there a way to validate a Nandroid backup other than trying to restore from it? I don't mean comparing a hash (which is what I find using Google), but rather making sure that the original, uncorrupted file is valid for use as a backup.
As a side note, every backup I've done with CWM Recovery has been reliable, so my fallback plan is to switch to CWM. I just find TWRP easier to navigate.
Click to expand...
Click to collapse
I've played with recovery files before (se my signature) when cwm wasn't working well.
Basicly if you want to know that the backup is correct, you can only compare the hash codes (nandroid.md5) which is practically useless, because hases are made only for the .img files, so the OS itself is not protected like this, which is somehow ok, because the files are compressed to a .tar file, which also means it has it's own validation algorithms itself. So you can validate it if you can decompress the file (don't ask that how it could be done under windows) without errors, it should be allright.
I personnaly can say only this: use CWM 6. i-don't-know-which version (which is online now). There is a possibility for cache not mounting, and of course a backup to not be full, but as you can see from my signature, it can be "bypassed" so the OS will be backed up, and because we don't have S-OFF, it doesn't really matters. All of my backups from CWM is working (have at least 10 gigs at the time, from stock to EV).
I always use android file verifier by scary Allen (free market download). It has saved me many times!
Sent from my HTC One V using xda app-developers app
so as a conclusion, nandroid backup won't restore boot image? and the option in cwm advance restore>restore boot is useless? Me also always got stuck using nandroid restore
Ken-Shi_Kun said:
I've played with recovery files before (se my signature) when cwm wasn't working well.
Basicly if you want to know that the backup is correct, you can only compare the hash codes (nandroid.md5) which is practically useless, because hases are made only for the .img files, so the OS itself is not protected like this, which is somehow ok, because the files are compressed to a .tar file, which also means it has it's own validation algorithms itself. So you can validate it if you can decompress the file (don't ask that how it could be done under windows) without errors, it should be allright.
I personnaly can say only this: use CWM 6. i-don't-know-which version (which is online now). There is a possibility for cache not mounting, and of course a backup to not be full, but as you can see from my signature, it can be "bypassed" so the OS will be backed up, and because we don't have S-OFF, it doesn't really matters. All of my backups from CWM is working (have at least 10 gigs at the time, from stock to EV).
Click to expand...
Click to collapse
sellersj27 said:
I always use android file verifier by scary Allen (free market download). It has saved me many times!
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Confirmed that comparing file hashes isn't helpful for this purpose—I just downloaded scaryalienware's AFV as suggested and ran it against several of my Nandroid backups. It said all of them succeeded, including at least one of which I know will not restore successfully. However, of interest is the fact that it took about half as much time to scan the known "bad" one, and further analysis shows that it's about half the size of the others. I'll have to make some more backups via the various mechanisms to confirm that the size is an indicator; it may be simply that I had fewer apps installed when making those backups.
Too bad there isn't some kind of Nandroid Restore Simulator. But even if there was, this phone probably wouldn't have enough memory to use it. Checking Nandroid backups in a VM would be awesome though!
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?
Hello all,
Yesterday I rooted my HTC One X and then I installed the custom Cyanogenmod 10 nightly build (cm-10-20121105-NIGHTLY-endeavoru), that all went through succesfully. However it was only for testing purposes, to see what Cyanogenmod 10 ROM was offering, but I now want to revert back my stock Android ROM.
During the installation process I followed the guides and I made a back-up straight after installing Clockwork Touch Recovery 5.8.4.0 (recovery-clockwork-touch-5.8.4.0-endeavoru), however when I reboot after restoring my back-up my phone doesn't boot into Android OS it stays at the HTC logo screen. Before I restore I delete data and cache.
I do belive its a boot.img fault and I would love it if someone could help me find a replacement for my stock image.
I originally was using
Android 4.0.3
Unlocked international version (Tegra 3)
I purchased from Virgin in Australia
I really need my old ROM back if possible, can anyone offer me any assistance?
Thank you
You have right, it's a boot.img problem. You have to flash the original boot.img of your stock rom. I think that it's normally in your Nandroid backup, but I'm not sure.
Sent from my HTC One X using xda app-developers app
FabMan_UK said:
Hello all,
Yesterday I rooted my HTC One X and then I installed the custom Cyanogenmod 10 nightly build (cm-10-20121105-NIGHTLY-endeavoru), that all went through succesfully. However it was only for testing purposes, to see what Cyanogenmod 10 ROM was offering, but I now want to revert back my stock Android ROM.
During the installation process I followed the guides and I made a back-up straight after installing Clockwork Touch Recovery 5.8.4.0 (recovery-clockwork-touch-5.8.4.0-endeavoru), however when I reboot after restoring my back-up my phone doesn't boot into Android OS it stays at the HTC logo screen. Before I restore I delete data and cache.
I do belive its a boot.img fault and I would love it if someone could help me find a replacement for my stock image.
I originally was using
Android 4.0.3
Unlocked international version (Tegra 3)
I purchased from Virgin in Australia
I really need my old ROM back if possible, can anyone offer me any assistance?
Thank you
Click to expand...
Click to collapse
You need to flash the original boot.img with fastboot. If you boot into recovery and mount usb storage browse the "sd card" to clockwork mod/back up you will see boot.img, copy to your pc and flash with fastboot.
gr1pper said:
You need to flash the original boot.img with fastboot. If you boot into recovery and mount usb storage browse the "sd card" to clockwork mod/back up you will see boot.img, copy to your pc and flash with fastboot.
Click to expand...
Click to collapse
JonasL1 said:
You have right, it's a boot.img problem. You have to flash the original boot.img of your stock rom. I think that it's normally in your Nandroid backup, but I'm not sure.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
as they said the your boot.img is in the nandroid backup.... just extract it and flash it in flastboot
could i ask you to upload your backup file and share it with the community? i would very appreciate it
matt95 said:
as they said the your boot.img is in the nandroid backup.... just extract it and flash it in flastboot
could i ask you to upload your backup file and share it with the community? i would very appreciate it
Click to expand...
Click to collapse
I think I can do that.
Thanks guys for the suggestions, I'll test later and report my findings.
Half success
Hey guys, thank you for your help. Following the advice given I was able to restore my boot.img and boot into my old phones OS, it states 4.0.3 and looks pretty much how my phone looked.
However I wonder if I could get some more assistance? My knowledge is limited I find it hard to even search for the correct terminologies on this website, let alone understand all the material that pops up. I do try to take care and follow guides, I didn't seem to have any problems with Cyanogenmod on my HTC Desire.
So my problem is difficult for me to explain, I'll try to be detailed.
Before I attempted to test CM10 I always transferred every app to the phone storage. Then starting the process I then installed SuperSU, ROM Manager and Titanium Backup but I did not move them to phone storage. I used HTCDev to unlock, via HTC One X All in One Kit 1.2.2. Then after installing clockworkmod I completed a backup, with a total size of 2.47GB (I'm not sure of a typical size).
I successfully tried a CM10 nightly build 4/11/12 then 5/11/12 an hour later and liked it but wanted to revert, I had my above OP problem now solved. But when after restoring my original backup I only have Titanium Backup, ROM Manager and SuperSu as my installed apps. No other apps are installed or registered at all, I don't have any old text messages (except 6 very recent ones), or call log history. However my details are stored, so it knows my google account details and my wifi details.
Most people here understand how the HTC One X works better than me. It seems the backup is made up of 7 files my guess in brackets:
.android_secure.vfat.tar (contains the stored apps) 1.51GB
boot.img (responsible for how it boots) 8MB
cache.ext4.tar (too small for me to guess) 10.5KB
data,ext4.tar (contains user data, configurations) 63.3 MB
nandroid.md5 (checksum) <1KB
recovery.img (to boot to clockworkmod recovery) 8MB
system.ext4.tar (Stores the OS) 906MB
Can someone help diagnose the problem and offer a possible solution? I'll upload the correct boot.img when this is working.
Thank you all again.
FabMan_UK said:
Hey guys, thank you for your help. Following the advice given I was able to restore my boot.img and boot into my old phones OS, it states 4.0.3 and looks pretty much how my phone looked.
However I wonder if I could get some more assistance? My knowledge is limited I find it hard to even search for the correct terminologies on this website, let alone understand all the material that pops up. I do try to take care and follow guides, I didn't seem to have any problems with Cyanogenmod on my HTC Desire.
So my problem is difficult for me to explain, I'll try to be detailed.
Before I attempted to test CM10 I always transferred every app to the phone storage. Then starting the process I then installed SuperSU, ROM Manager and Titanium Backup but I did not move them to phone storage. I used HTCDev to unlock, via HTC One X All in One Kit 1.2.2. Then after installing clockworkmod I completed a backup, with a total size of 2.47GB (I'm not sure of a typical size).
I successfully tried a CM10 nightly build 4/11/12 then 5/11/12 an hour later and liked it but wanted to revert, I had my above OP problem now solved. But when after restoring my original backup I only have Titanium Backup, ROM Manager and SuperSu as my installed apps. No other apps are installed or registered at all, I don't have any old text messages (except 6 very recent ones), or call log history. However my details are stored, so it knows my google account details and my wifi details.
Most people here understand how the HTC One X works better than me. It seems the backup is made up of 7 files my guess in brackets:
.android_secure.vfat.tar (contains the stored apps) 1.51GB
boot.img (responsible for how it boots) 8MB
cache.ext4.tar (too small for me to guess) 10.5KB
data,ext4.tar (contains user data, configurations) 63.3 MB
nandroid.md5 (checksum) <1KB
recovery.img (to boot to clockworkmod recovery) 8MB
system.ext4.tar (Stores the OS) 906MB
Can someone help diagnose the problem and offer a possible solution? I'll upload the correct boot.img when this is working.
Thank you all again.
Click to expand...
Click to collapse
i'm not quitely sure but i would reboot into bootloader and do a factory reset to see if this solves the problem, but i'm not sure this will
matt95 said:
i'm not quitely sure but i would reboot into bootloader and do a factory reset to see if this solves the problem, but i'm not sure this will
Click to expand...
Click to collapse
Doesn't that clear the data and or cache? Because I've done that, before I restore. I've tried several things including random button mashing
-EDIT-
Looking at the file sizes of other backups, the cache can be quite large. Is it possible during the backup the cache part was fudged? Meaning that its all gone. Or possibly I hit clear cache by mistake? Though I have absolute no memory of doing that or any reason as to why I would. When I install some apps, it picks up old content.
It's maybe better to buy Titanium Back-up Pro. Than you can back-up everything with that. (Apps, text messages, settings,...) And than a Nandroid back-up and you don't lose something. You can just lose your sd card if you do something wrong. I do it always so.
Sent from my HTC One X using xda app-developers app
JonasL1 said:
It's maybe better to buy Titanium Back-up Pro. Than you can back-up everything with that. (Apps, text messages, settings,...) And than a Nandroid back-up and you don't lose something. You can just lose your sd card if you do something wrong. I do it always so.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Its embarrassing but I already own Titanium Back-up Pro, I assumed (incorrectly) that clockworkmod backup was almost like taking a snapshot of the current system operating.
I had already backed up everything on the USB mountable drive space, but not the part that is actually useful to backup. D'oh.
I wondered if anyone was familiar with clockworkmod back up process and could inform me of how I am missing something so obvious and I click X Y Z a voila, its restored.
That's strange if you restored both things and your apps and text messages and more stuff are missing.
Sent from my HTC One X using xda app-developers app
JonasL1 said:
That's strange if you restored both things and your apps and text messages and more stuff are missing.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I know, I used 7-zip and I could successfully extract the *.tar files and there was so much information there, it had all of the apps I used. In the morning (I'm in Australia), I will try to find a way to manually import information. No idea how to start other than with an Internet Search.
Okay that didn't help at all, I'm stuck. I can see the apps but they will not install from the phone storage.
I can see in the .tar files the system apps that come pre-loaded but are not on my phone now, like Facebook. It's frustrating because I cannot do a factory restore because I do not have access to an original HTC installation. Is there an official international 4.0.3 installation image available or am I stuck with a screwed up phone until HTC release the official Australian 4.1 release?
Thanks people.
-EDIT-
I'm making the assumption that something failed during my first backup and that is why it didn't work on restore. I believe its the cache information as the rest are large in size and they pass the MD5 checksum, I don't know this for sure though.
My boot.img would be no good for the collection as it already exists. The boot.img I am using is the one I extracted from the RUU 1.29.728.12 I downloaded, since that should be the one my phone came with and it works.
My experience from this is that Cyanogenmod 10 is not yet ready for me to use but is looking promising. Also that I cannot rely on ClockWorkMod solely as a backup solution and should have used phones included backup features and Titanium Backup Pro that I own.
Cheers everyone.
Hi all,
So I've been on paranoid android for the past few months, and I had to revert back to stock for work reasons tonight; it's been a while since I've done my routine backups.
Having made my standard nandroid backup and restored to stock via ODIN, I was horrified to discover that none of my stored nandroid backups would work, running into system/data restore errors every time. I've just read that clockworkmod uses a new process that keeps each individual backups small but requires the presence of a .blob file of sorts, which must have gotten erased when I flashed stock. I checked the size of my nandroid backups and sure enough, they were only around 20 megs; it looks like my internal memory was wiped clean.
My questions are: is everything pretty much gone? And if so, WTF is the point of nandroids if they're no longer self-contained backups? If the devs indeed made changes that led to this, it reeks of inconsiderateness, if not just plain ineptitude.
I apologize in advance if I'm venting or missed something obvious, but I've been at this for a while now and exhaustion is just turning into frustration.
Thanks for your feedback/help.
Blob backups are incremental. Tar backups are full.
When CWM 6 was released, the devs made blob the default backup format. Later versions changed it back to tar.
You can manually change this setting through the CWM options.
As far as your backups being hosed, its tough to say without having the device in front of me. Are you attempting to restore with the same version that created the backup?
For what it's worth, I mirror your opinion about incremental backups being a terrible idea.
Aerowinder said:
Blob backups are incremental. Tar backups are full.
When CWM 6 was released, the devs made blob the default backup format. Later versions changed it back to tar.
You can manually change this setting through the CWM options.
As far as your backups being hosed, its tough to say without having the device in front of me. Are you attempting to restore with the same version that created the backup?
For what it's worth, I mirror your opinion about incremental backups being a terrible idea.
Click to expand...
Click to collapse
Thanks; I did try multiple recovery versions including older ones, but the internal memory was wiped since I formatted system so I'm pretty sure everything's gone. Clockwork has been such a useful tool but I really have to wonder what they were thinking when they did this, ugh.
C'est la vie
So... I flashed AGAT_Recovery tREC_v0.2.2 and was intending to restore a "nandroid" backup from before I wiped my phone. First of course I made a backup (just Stock Rooted ROM I used to flash the recovery partition). I then tried to restore the previous image of my custom ROM and the restore failed. Investigated and found that the filenames in the nandroid backup folder were named differently from previous nandroid backups I had taken:
system.ext4.tar (0 bytes)
system.ext4.tar.a (large)
data.ext4.tar (0 bytes)
data.ext4.tar.a (large)
I'm not sure how the backup format changed as I don't recall updating the recovery partition, I'm wondering if some ROM I installed did this for me (if so thanks a lot). Looks like this:
http://forum.xda-developers.com/showthread.php?t=2194171
So trying to be clever, I deleted the 0 byte files and renamed all of the stupid .a files to the original (I had no .b, .c files etc.) Then I did a restore.
The restore completed successfully but com.android.Phone was crashing on startup repeatedly, the launcher wasn't working properly and basically the image wasn't usable.
I then decided that it wasn't worth all the trouble and I would just restore to the backup I had taken of the Stock Rooted ROM immediately prior to this whole mess starting (using AGAT_Recovery tREC_v0.2.2). The restore completed successfully but the O/S didn't boot at all (it just showed a black screen after POST of the Samsung logo).
For now I've reflashed stock using ODIN.
So basically my question is: why is this so complicated? Am I missing something here? Is AGAT_Recovery 0.2.2 not a good choice for a recovery partition?
Is the recovery you are trying to restore the sane recovery you are currently running.
I've gotten stuck by being in a different version of the same recovery and it just didn't work. I had to be in the same recovery in order to do a restore.
Just a thought
Bt is right. You should always use the same cwm to restore that you used on the backup. And the latest Agat recovery is essentially bugfree, which is 0.3.5. So I would use that. And it's not difficult, at all . Just takes a few "oh craps" to get it down pat!
Sent from my SPH-D710 using xda premium
thanks
jdsingle76 said:
Bt is right. You should always use the same cwm to restore that you used on the backup. And the latest Agat recovery is essentially bugfree, which is 0.3.5. So I would use that. And it's not difficult, at all . Just takes a few "oh craps" to get it down pat!
Click to expand...
Click to collapse
I suspect part of the reason I couldn't restore the one backup image was because I wasn't using the same version, or perhaps even product. Doesn't explain why the older version of Agat couldn't restore its own backup though. I'll try the newer version out. Thanks!
It's too bad the utilities don't write out some metadata about the format used, what product/version did the backup, etc.
philipdl71 said:
I suspect part of the reason I couldn't restore the one backup image was because I wasn't using the same version, or perhaps even product. Doesn't explain why the older version of Agat couldn't restore its own backup though. I'll try the newer version out. Thanks!
It's too bad the utilities don't write out some metadata about the format used, what product/version did the backup, etc.
Click to expand...
Click to collapse
That was an earlier kernel that probably still had bugs. Could have been a bad backup. It happens. The latest kernel will do solid backups/restores and serve as a very dependable dd. Good luck.
Sent from my SPH-D710 using xda premium
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
¿GotJazz? said:
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
Click to expand...
Click to collapse
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Ramer said:
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Click to expand...
Click to collapse
Thanks, @Ramer - I checked Sammobile earlier this morning, and it wasn't there. They must have posted it later today.
I can't get to it right now, tho, their website may be having issues. I'll try later.
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
ashyx said:
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
Click to expand...
Click to collapse
Unfortunately. @ashyx - I'm not sure exactly where now. The recovery failure was almost instant (within the first 5 to 10 steps), and I remember that the error occurred right after a progress comment about EXT4. I lost the capability to boot up, and I lost the capability to get into Recovery Mode. My only option was to stay stuck in Download Mode, and hope that my battery didn't die before I was able to get a Odin image re-installed.
It was nerve-wracking.
I wasn't sure if the tablet would be charging while in Download Mode, and there was no way (that I knew of) to get out of Download Mode. I thought there was a high probability that I was about to permanently lose my brand-new tablet.
I paid for a subscription to Sammobile to get an older image installed until someone was able to get me the more recent stock image.
I'm too nervous to try and restore the image again without need, but I will definitely do it if you want me to. I understand the urgency to make sure that TWRP makes good images 100% of the time, and I am reluctant to do anything future to my tablet if I can't make a reliable back-up.
¿GJ?
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
ashyx said:
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
Click to expand...
Click to collapse
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
¿GotJazz? said:
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
Click to expand...
Click to collapse
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
ashyx said:
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
Click to expand...
Click to collapse
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
¿GotJazz? said:
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
Click to expand...
Click to collapse
Is this backup also encrypted. I have seen that error with encrypted backups in the official twrp. However this was fixed with an update pushed to the twrp repo which I have incorporated into the latest build.
Does your version of Twrp show your model number at the top?
ashyx said:
Is this backup also encrypted?
Click to expand...
Click to collapse
Yes.
ashyx said:
Does your version of Twrp show your model number at the top?
Click to expand...
Click to collapse
No, it just shows Team Win Recovery Project v2.8.6.2. It doesn't show any Samsung model numbers (If that is what you are asking).
I installed it using your All-In-One Root/Recovery tool.
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
ashyx said:
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Click to expand...
Click to collapse
Thanks, @ashyx! I'll download the SM-T800 F2FS version right now.
BTW, I've been really interested in installing F2FS. One thing I have been worried about, though, is that once I go down the F2FS path, it may be easy to really mess things up. For example, if I update a ROM, I would always need to use a F2FS ROM, or I might lose all my data - is that right?
Normally you would only format the data and cache partition to f2fs. There isn't much point formatting system to f2fs.
Also f2fs requires a special kernel. Myself and Tkkg1994(Iron Rom) have been working together to get this working properly. Still testing.
We are almost there.
Once formatted to f2fs you would need to reformat back to ext4 and flash a kernel to return back to normal. You could then flash your backup.