yashsingh1/xdaforums huggingface dataset:
[Nexus S 4G Android Development] Nexism:
I have been trying to use this recovery and running into restore probs also. 3 different backups 3 recovery attempts and ended up with a wiped phone every time none of my data backed up.

Too bad because flashing multiple zips at once made flashing new ROMs so easy. More important I need be able to trust my backups..

Switched back to cwm until fix for backup/restore.

Sent from my Crespo4g
[Nexus S 4G Android Development] nwo122383:
i too had that problem. I read on another forum to just take the boot.img from the rom you are trying to restore back to and use fastboot to flash it after you do the restore. This obviously isn't the best solution if you do not have access to a computer, but since i did it worked out for me. Hope this helps some people out. this way you wont have to redo your entire rom and then you can flash a different recovery until they fix this problem
[Nexus S 4G Android Development] Nexism:
Thank you for the tip. No computer but being a flash-addict I have lots of practice re-doing my ROM. I can do it pretty fast and always makes me feel good to have a fresh n clean build.

To dev, please look into this. This could be an awesome recovery.
[Nexus S 4G Android Development] vinnypel2ella:
I also had restore problems. No matter what it wouldn't restore. Tried turning encryption on and off. Shame cause I like team win as a whole. I've just gone back to clockwork (non touch).
[Nexus S 4G Android Development] styckx:
Thanked! I just had this restore problem and I was pissed so I ran here to see if anyone else had the issue and a solution.. Fastbooting over the boot.img did the trick..

Going to have to go back to CWM because I can't be dealing with sketchy restores..
[Nexus S 4G Android Development] Dees_Troy:
Updated to 2.3.0.0!
[Nexus S 4G Android Development] Sputnikk23:
+1 on restore issues. Had that problem a few months ago. Obviously still a problem. It ****ed me good too. I really needed it. Back on clockwork ever since and I don't think I can trust twrp. Its like I got cheated on. Would be doubly paranoid considering this latest is "a complete rewrite of the base code". Recovery backups are our last failsafe :(
[Nexus S 4G Android Development] Dees_Troy:
Most likely the restore issues on the NS4g are now fixed. Give it a shot and let me know if they're not. Either way the restore issues seemed to only deal with boot and only seemed to affect the NS and NS4G. Other devices were unaffected by those issues.
[Nexus S 4G Android Development] DMardroid:
Restored backups fine on 2.3 :thumbup:

EDIT: Spoke too soon

Trouble restoring Slim and cm10 m2 backups

Wont boot stuck google logo

2.2.2.0 was perfect
[Nexus S 4G Android Development] Nexism:
Damn! That's bad news. I am watching this thread closely. Loved the recovery until restore prob came up. I would like to switch back to TWRP anyone with a NS4G having any success with restore?

Sent from my phone using my thumbs and a keyboard
[Nexus S 4G Android Development] DMardroid:
Reverted back to 2.2.2.0

All good now

My restores work again
[Nexus S 4G Android Development] Xaelius:
Just installed the latest version...have not done a backup with it, but straight off the bat it fails to mount ANYTHING when attempting to run a permissions fix...just thought I would point this out.
[Nexus S 4G Android Development] DominoDoug:
Confirmed
[Nexus S 4G Android Development] Dees_Troy:
Updated to 2.3.1.0. If you're having problems with something, pull and post a recovery.log or I won't be able to help. I don't have a Nexus S or Nexus S 4G.
[Nexus S 4G Android Development] Xaelius:
Haven't done a backup or restore with 2.3.1.0 but I can confirm the permissions fix mounts everything except sd
[Nexus S 4G Android Development] noizy1234:
I'm trying to install with the goo manager app but it said its been installed but when I go to recovery it takes me back to cwm
[Nexus S 4G Android Development] Siya Nová:
My girlfriends nandroid will not show in her recovery, the last version or this version. It's there, I checked via rootexplorer and it there, haven't tried fixing permissions. Will report back with what I find

Sent from my Team Venom LTE with Z power

---------- Post added at 11:17 PM ---------- Previous post was at 11:15 PM ----------

And if you have a PC and adb this may help you out, this should be added to the OP for those whose have goo manager problems.

Here ya go

http://goo.im/devs/OpenRecovery/crespo4g/openrecovery-twrp-2.3.1.0-crespo4g.img

Sent from my Team Venom LTE with Z power
[Nexus S 4G Android Development] Dees_Troy:
If you changed devices then your serial number changed which changes the backup path. It's not recommended to restore a backup from a different device but you are welcome to try it. You will need to move or rename the serial number folder.
[Nexus S 4G Android Development] bettzysdaddy:
Sorry for the noobish question, what is adb and OP? What if you're on a Mac? I have the same issue of using the Goo manager and when reboot, I'm still on TWRP 2.0.0

---------- Post added at 11:17 PM ---------- Previous post was at 11:15 PM ----------

[/COLOR]

And if you have a PC and adb this may help you out, this should be added to the OP for those whose have goo manager problems.

Here ya go

http://goo.im/devs/OpenRecovery/crespo4g/openrecovery-twrp-2.3.1.0-crespo4g.img

Sent from my Team Venom LTE with Z power[/QUOTE]
[Nexus S 4G Android Development] DominoDoug:
I am having issues with fixing permissions on 2.3 & 2.3.1. 2.2 on the other hand works fine. Haven't tried to do a restore yet.
[Nexus S 4G Android Development] mercado79:
Just finished doing some testing on version 2.3.1.0. I had no problems running any of the tools/options, including backup, restore, and fix permissions.

I'm curious why you say you're having issues fixing permissions. Just an FYI, but fixing permissions no longer takes more than a few seconds. If that's what you're experiencing, you should know that it's SUPPOSED to finish super quickly. See the changelog which states:

Full disclosure. I had an issue restoring the backup, but that was only after I'd changed the settings to use rm -f instead of a standard format. I toggled that back, wiped dalvik manually just in case, and it restored without any problems.
[Nexus S 4G Android Development] Nexism:
I like the idea of "batch flashing" too much. I am switching back to TWRP as I seem to remember it working fine before I started messing wit the settings. I think it is important to have options when it comes to a recovery rather then just one and what that dev says goes (like not being compatible with other apps, that really burns me when I thought the whole idea of android was freedom from being rail roaded into one option). Enough of my rant, back to TWRP for testing. Keep ya'll posted

Thanks again Team Win for another option.

Sent from my phone using my thumbs and a keyboard
[Nexus S 4G Android Development] Nexism:
No go. Installed but could not flash a few thins I use like wipe all boot animation and font packs...I am sad again.

Sent from my phone using my thumbs and a keyboard
[Nexus S 4G Android Development] Dees_Troy:
Updated!
[Nexus S 4G Android Development] matthew0776:
Re: [RECOVERY] TWRP 2.3.3.0 touch recovery [2012-12-19]

Using twrp 2.3.3.0 and when I do a factory reset and flash new rom it not prompting me to sign back into Google and set up phone... Is twrp fully functioning correctly on ns4g. Have it on Nexus Galaxy and love it....!
[Nexus S 4G Android Development] jesusice:
Re: [RECOVERY] TWRP 2.3.3.0 touch recovery [2012-12-19]

Did you forget to flash Gapps?
[Nexus S 4G Android Development] matthew0776:
Re: [RECOVERY] TWRP 2.3.3.0 touch recovery [2012-12-19]

Yup...
[Nexus S 4G Android Development] dzee206:
everytime i download 2.4.0.0 its always 3.64mb and not 3.65 like it states on the site, also it keeps hanging at 99% on my comp no matter what browser i use or download mangers. havnt tried on mobile yet gf has the phone now.
[Nexus S 4G Android Development] matthew0776:
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

Used goo manager and worked perfectly. On both nexus devices.... Thnx
[Nexus S 4G Android Development] matthew0776:
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

Backups not restoring on ns4g...on 2.4.0 and 2.4.1. Any body else having issues
[Nexus S 4G Android Development] CB620:
I backup my rom with 2.3.3.0 and restored with 2.4.1.0

:good:
[Nexus S 4G Android Development] sleepyEDB:
The restore problem is still present. I installed TWRP 2.4.0.1 via GooManager without issue, created a backup, wiped cache, etc. Booted into Android and back into TWRP and restored the backup. Upon rebooting the system, I am put into the bootloader and cannot boot into Android. I will try the boot.img solution posted above, and will pull & post a TWRP log if possible.

sleepy
[Nexus S 4G Android Development] Dees_Troy:
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

If you first fix it by re flashing boot then try to get a log, then the log won't contain anything useful.
[Nexus S 4G Android Development] sleepyEDB:
I wasn't able to get it to flash the boot.img. Windows wouldn't recognize my phone when it was connected and sitting at the bootloader screen, and the fastboot commands wouldn't work when Windows recognized my phone in TWRP. At that point I tried flashing a zip of ClockworkMOD from my SD Card, but the fastboot commands were still unrecognized. Fortunately, I was then able to flash my most recent ROM from the CyanDelta folder and I am back in Android.

I told TWRP to copy the log file to the SD Card before I attempted to restore the boot.img, so hopefully it's useful. Sorry for not using pastebin, but it's blocked here:

[URL]http://codepad.org/Xk2dT2Q9[/URL]

Towards the bottom of the file I see these entries:

I:Backup command: 'dump_image recovery '/sdcard/TWRP/BACKUPS/<serial number removed by me>/CM10.1-N0208-02-11-2013//recovery.mtd.win''

mtd: read error at 0x00000000 (Out of memory)

mtd: read error at 0x00040000 (Out of memory)

mtd: read error at 0x00080000 (Out of memory)

mtd: read error at 0x000c0000 (Out of memory)

mtd: read error at 0x00100000 (Out of memory)

mtd: read error at 0x00380000 (Out of memory)

Maybe the nandroid backup was bad to begin with, and the restore problem wasn't with TWRP after all? I would have expected an error message if this was the case, but I don't know.

sleepy
[Nexus S 4G Android Development] Dees_Troy:
[RECOVERY] TWRP 2.4.2.0 touch recovery [2013-02-25]
[Nexus S 4G Android Development] Dees_Troy:
[RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
[Nexus S 4G Android Development] matthew0776:
Re: [RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

The screen turn weird colors when it times out on my ns4g ...but not on my gnex. Seems to be working OK I think. But can't see buttons after timeout. Anyone else having this issue.? Also looking for flash able zip for previous ver. Thanx
[Nexus S 4G Android Development] Dees_Troy:
[RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]
[Nexus S 4G Android Development] ahow628:
Any luck with this? I put 2.4.3.0 on my brothers Crespo4G and had the same issue. Could barely make out button labels by holding it at an angle. Will try to update to 2.4.4.0 and see if that fixes it. Let me know if you found a fix.
[Nexus S 4G Android Development] :
[deleted]
[Nexus S 4G Android Development] ahow628:
Good call. I actually figured that out when I disabled the timeout on my Evo LTE last night.
[Nexus S 4G Android Development] kkkhattak:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

Any themes for TWRP?
[Nexus S 4G Android Development] Unjustified Dev:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

Is the epic ever going to see twrp 2.4.4 I tried and failed building it.
[Nexus S 4G Android Development] Dees_Troy:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

I need to update my build script to make zips, just a matter of finding the time.
[Nexus S 4G Android Development] Unjustified Dev:
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

[/COLOR]
[Nexus S 4G Android Development] Dees_Troy:
[RECOVERY] TWRP 2.5.0.0 touch recovery [2013-04-09]
[Nexus S 4G Android Development] rg2:
How come in the advanced wipe menu for 2.5.5.0 there are two entries for "Internal SDcard" and no entry for "Android Secure"? For my CM10 TouchPad, there is only 1 entry for the "SDcard" and an entry for "Android Secure", so I am a bit confused...

I only bring this up as I thought one would wipe boot/android_secure as part of a full wipe (I usually do last) and don't know if this is even possible on the NS4G now (although it is mentioned in the default wipe).

Again, I am sorry if this sounds noobish, but I am just a bit confused. Any/all help is appreciated :)
[Nexus S 4G Android Development] QMaverick:
wrong thread

Edit: oops, wrong thread
[Nexus S 4G Android Development] cyanide01:
Does this version TWRP work to flash kit kat ROMs?? Anyone tested it yet...
[Nexus S 4G Android Development] hp420:
Thank you for still supporting this device man!! It's seen a lot of abandonment lately, but it's nice to know that recovery is still on the bleeding edge!
[Nexus S 4G Android Development] mathuaerknedam:
The First Post says to download TWRP Manager from the Play Store and then install twrp2 from there. The directions seem out of date. "Advanced->Install Recovery" doesn't exist, but I used the side-menu to select "Install TWRP". I then tapped on "Device name", but I can't seem to find Nexus S or Crespo4g there. Does this still work?
[Nexus S 4G Android Development] galland1:
Delete
[Nexus S 4G Android Development] Taji34:
Where is the download for 3.0.0?
[Nexus S 4G Android Development] jeremydk:
Has Nandroid restore been tested yet? I made a (compressed) image, flashed to a different rom for testing, and on restore, TWRP is showing successful, but I get returned to bootloader because I appear to have no (edit) boot data.

Reflashed rom, and restored everything but boot and I'm good to go.
[Nexus S 4G Android Development] Dees_Troy:
Check your sdcard for a twrp folder. In there (and inside some other subfolders) you should find your backup. Look for one called boot.win. Rename this to boot.img and try to open it with a image viewing tool. Make sure that it isn't 0 bytes in size. Also might help if you upload the file somewhere like dropbox or the like and provide a link. Do you know what kernel you were using?
[Nexus S 4G Android Development] TheBurgh:
Thanks..I will give it a shot
[Nexus S 4G Android Development] Igotsanevo4g:
This is effing awesome:D
[Nexus S 4G Android Development] jeremydk:
Boot.win is 8MB, and is not compressed -- As I'd selected to compress backups, it is trying to decompress this and flash the output?
[Nexus S 4G Android Development] snandlal:
problem here..............was using latest 4g teamwin recovery and it did not restore properly. Sent me to fastboot. So i flash clockwork back and now any backup i try to restore gives me an error: "error while flashing boot image!". Anyone got any idea? I did fastboot erase recovery and then i did fastboot flash recovery recovery.img

UPDATE: Ok so i did a fresh backup with clockwork and then restored. Apparently for me, no backup (from clockwork) that was made before i flashed Teamwin Recovery will work. Only a fresh one made after an install and uninstall of Teamwin. Weird.
[Nexus S 4G Android Development] Maximilian Mary:
I'm not sure how I feel about backup images that are not compatible with fastboot. Other than that, this is mighty tasty.

P.S. You lost your horse? Whatever...
[Nexus S 4G Android Development] AssassinsLament:
Who said they weren't?
[Nexus S 4G Android Development] Maximilian Mary:
Dees_Troy did:
[Nexus S 4G Android Development] spiicytuna:
Just gave this a whirl on mine and it worked 100%. I did a full wipe first. Restored my compressed backup. Booted (see my boot animation below).
[Nexus S 4G Android Development] NYYFan325:
So being I'm currently on CMW 4.0.0.2 what advantage (if any) is there to switching to this recovery? Does it do certain things better? Faster?

I'm not knocking the work just curious as to what benefits this has over cwm :)
[Nexus S 4G Android Development] Igotsanevo4g:
Try it and find out, you can always switch back with no problems.

... Though I don't think you will :p
[Nexus S 4G Android Development] TheBurgh:
Thanks for the help. I had to flash it twice but now its working like a champ
[Nexus S 4G Android Development] Dees_Troy:
10 chars...
[Nexus S 4G Android Development] plmiller0905:
So you mean..we can't use efs to backup wimax then until further notice?

If so, what's the issue. Because last night, I deselected everything with the exception of efs and backed up my wimax...like the first post stated.
[Nexus S 4G Android Development] Dees_Troy:
We're pretty sure that this issue doesn't affect NS4G - only the Nexus S. I've removed the warning as our own testers didn't find any issues with EFS backup/restore so far.
[Nexus S 4G Android Development] kijp15:
Switching themes within the recovery is tripping me out. Ha. I love twrp! :) Thanks TW!
[Nexus S 4G Android Development] plmiller0905:
Cool...I was getting a little worried for a bit.

Also one quick question...is it still ok to rename backups after we make them?

The reason being is because I made a backup yesterday as well as a backup of my wimax. Both were automatically named according to the date. I just don't want to revert to a backup and accidentally flash my wimax backup instead of my rom backup
[Nexus S 4G Android Development] Maximilian Mary:
Yes. I renamed mine to datetime_rom_kernel/, and it restored fine. When you restore, it will select only the partitions that were included in that backup.
[Nexus S 4G Android Development] TheBurgh:
Need some help: should you backup all partitions for a standard nandroid backup. Process is more involved than nandroid through cwm.
[Nexus S 4G Android Development] styckx:
Just tried this recovery today for the first time.. Good stuff. I dig it. Did a backup, then factory reset, and restored perfectly. No issues..

I dig it.. Nice clean interface, not overwelming. Thanks guys!
[Nexus S 4G Android Development] weusi2:
Where would I find the "Fix UID Permissions" option in this software?
[Nexus S 4G Android Development] Dees_Troy:
Yes, you can rename the date/time folders in the twrp folder on your sdcard. I renamed my EVO 3D WiMAX backup to wimax so I could keep better track of it. Also, when you go to restore a backup, you can choose which partitions to restore, so even if you choose to back up WiMAX (or EFS in this case), you can choose whether or not to restore it with all of the other partitions.

Our NS4G tester has confirmed for me that EFS backup works fine for him. He backed up EFS and restored it and everything worked. It appears that the EFS issue is limited to the GSM Nexus S. We were worried that the issue would affect both the Nexus S and the NS4G and didn't want anyone harmed by the issue.

Usually you'll just want to back up boot, system, and data. You'll probably want to make a separate backup of EFS and keep that in a safe place and only restore it if you need to restore it.

It's already coded and will be included in the next release of twrp which should be out very soon.
[Nexus S 4G Android Development] dmarden:
Not .android_secure?

Sorry, first time having this much control over the process.

Nice work. :)

Thanks for the effort.
[Nexus S 4G Android Development] dmarden:
When I backed up EFS, it told me it was <20MB and it went very quickly. At the completion of the EFS backup it said it backed up 11798MB. That seems to be the space I have free in sd storage.
[Nexus S 4G Android Development] AssassinsLament:
Nothing to worry about, a bug in calculating disk space. It's fixed in the next update, which should be later today.
[Nexus S 4G Android Development] dmarden:
Sounds good, I didn't think it was anything serious... just reporting. :)

Thanks again for the effort of all involved parties.
[Nexus S 4G Android Development] jeremydk:
Turns out that my boot issues were due to the nand dying.

Problem solved! :(
[Nexus S 4G Android Development] raznalab:
I have the Nexus S 4G from Sprint and I was trying out the new recovery. Here is what I did:

flashed TeamWin recovery, boot into recovery, made nandroid backup (compressed), reboot into recovery, full wipe, restore nandroid, reboot.

With those steps everything went fine and my phone was running as normal, so I decided to add another step to my testing of the new recovery.

reboot into recovery, full wipe, flash cm7 nightly, boot into freshly installed rom, setup rom as normal. Then I booted back into recovery, full wipe, restore nandroid, reboot.

This time it boots into bootloader saying no boot image or recovery found and this is where the trouble begins. I booted into recovery, and its still teamwin recovery so I try to restore nandroid again and same results. So I go and fastboot flash clockworkmod recovery and boot into it. I try to restore clockworkmod nandroid that I have backed up and it says can't write boot image. I tried newer version of clockworkmod with no result.

Flashed TeamWin recovery and tried to flash zip from sd, same rom as nandroid and here is the error:

assert failed: write_raw_image("/tmp/boot.img", "boot")

E:Error in /tmp/sideload/package.zip

(status 7)

Anybody have any ideas that I can try, or am I just screwed?
[Nexus S 4G Android Development] jeremydk:
This is exactly what happened to me. Can you fastboot flash to boot at all? My boot nand was entirely toasted, and I couldn't flash it via fastboot, odin, or recovery.

The steps are identical too. Nandroid backup, flash CM7 nightly, test something, boot to recovery, full wipe, restore my nandroid backup, dead boot partition.
[Nexus S 4G Android Development] plmiller0905:
You guys got me feeling a little bit uneased. I think I'm gonna revert back to clockwork for the time being. Or are the issues you all having just isolated issues?

However, I do like the design of the recovery. :-)
[Nexus S 4G Android Development] Igotsanevo4g:
Been using this for awhile now with no issues, its sweet. I especially like the default folder for flashing feature.

Great stuff :)
[Nexus S 4G Android Development] raznalab:
looks like we are on the same boat my friend. I can't fastboot flash to boot, odin isn't working though i haven't found a pit file to try, and recovery isn't able to flash to boot either. I'm tempted to flash stock recovery, oem lock and try my luck with the sprint store.
[Nexus S 4G Android Development] jeremydk:
In a pinch you can flash a boot image to your recovery partition, and use fastboot erase boot to force it to always go to the BL screen. Selecting "recovery" will then boot the phone, but it's really a hack.
[Nexus S 4G Android Development] raznalab:
I read that somewhere, is that what you have going right now? I'm really hoping that someone will have an idea we have tried yet on how to fix our boot partition.
[Nexus S 4G Android Development] thedudejdog:
so the issue is restoring nandroids? as long as i don't do that i should be good right?
[Nexus S 4G Android Development] Maximilian Mary:
Instead of rebooting, I usually cold boot to avoid any problems, especially when flashing:

Unplug. Power off. Boot into partition of choice. Re-plug.

Warm booting into or out of any recovery can get wanky. E.g. twrp "reboot into system" reboots into recovery the first time, then system the second time.

Other ideas:

fastboot flash boot.img

fastboot flash cwm/boot.img

fastboot boot twrp.img

then restore boot image.

fastboot boot cwmrecovery.img

and restore it from there.

I'm not sure about these:

fastboot boot cwm/boot.img

or restore cwm backup and

fastboot boot cwm/system.img

then don't reboot away from your computer until it's fixed. (I'm not sure if this would work or might cause trouble.)

It seems to be just the boot.img. I restored stock, booted, then restored back to deck just fine. I did not wipe before restoring. I did uncheck efs, boot, and recovery before restoring. (I figured if you didn't change it, don't mess with it. :eek:)