Have space issues, also obsessively flashing various ICS and JB ROMs. When I find one for further testing I make a backup.
Question: can I move the TWRP backups to my PC for safe-keeping?
Using TWRP 2.2.0 and FFF 1.4a.
I would have done this automatically without thinking about it except even renaming a backup in TWRP gives an ominous warning about it not being able to be undone. Also saw a post from May alluding to whether storing backups on NTFS would cause issues.
TIA
I cannot tell you about 2.2.0, but I have 2.1.1 and I also do it a lot, move to PC, and back to restore. Never had any issues. What is important it is to keep the name as it is, and put it in the right folder when moving back to kindle. Otherwise, TWRP isn't even showing the name of the backup when trying to restore.
In the meantime: as I understand this 2.2.0 version is quite buggy, especially that devs of it never tested it on an actual KF?
I agree to be a tester of TWRP, but what's the point if the devs would not be able to make corrections, because they cannot test on KF?
It's like trying to operate a black cat in a dark room with closed eyes
Hope it will still get into a stable state in the near future
The virtues of men are of more consequence to society than their abilities; and for this reason, the heart should be cultivated with more assiduity than the head. – Noah Webster, On the Education of Youth in America, 1788
I have an issue that I thought was just a very random thing but now it has become more than a random occurrence, so I figured I'd report it. When flashing a Jellybean rom, I get the error message that it's unable to open the zipfile. When this first happened, I figured either a bad download, or maybe I accidentally ticked the check MD5 box or signature verification or something but that wasn't the case. I mounted USB in TWRP, deleted the zip and re-copied it over from my PC, still wouldn't work. Decided to reboot recovery and this time the zip installed.
This happened a couple of times on 2.2, so I went back to 2.1.1 but the issue persisted. I don't recall this ever happening on an ICS rom, so I don't know if it's something peculiar to Jellybean with TWRP. I do a lot of flashing and yesterday I flashed 3 rom zipfiles, the first 2 no problem, on the third I got that error message. As mentioned earlier, this has become a much more common occurrence, so I never know if my zipfile will flash or not. Tapping the reboot to recovery from TWRP always works in getting the zip to flash.
If it matters, I generally transfer the zipfile from my PC to the Fire from within TWRP using USB Mount. Thanks again for all your efforts, as well as TW.
I have an issue that I thought was just a very random thing but now it has become more than a random occurrence, so I figured I'd report it. When flashing a Jellybean rom, I get the error message that it's unable to open the zipfile. When this first happened, I figured either a bad download, or maybe I accidentally ticked the check MD5 box or signature verification or something but that wasn't the case. I mounted USB in TWRP, deleted the zip and re-copied it over from my PC, still wouldn't work. Decided to reboot recovery and this time the zip installed.
This happened a couple of times on 2.2, so I went back to 2.1.1 but the issue persisted. I don't recall this ever happening on an ICS rom, so I don't know if it's something peculiar to Jellybean with TWRP. I do a lot of flashing and yesterday I flashed 3 rom zipfiles, the first 2 no problem, on the third I got that error message. As mentioned earlier, this has become a much more common occurrence, so I never know if my zipfile will flash or not. Tapping the reboot to recovery from TWRP always works in getting the zip to flash.
If it matters, I generally transfer the zipfile from my PC to the Fire from within TWRP using USB Mount. Thanks again for all your efforts, as well as TW.
Mike T
I've been flashing Twa_Priv's jellybean ROM regularly without any problems using 2.2. However I haven't been transfering them using USB.
I have an issue that I thought was just a very random thing but now it has become more than a random occurrence, so I figured I'd report it. When flashing a Jellybean rom, I get the error message that it's unable to open the zipfile. When this first happened, I figured either a bad download, or maybe I accidentally ticked the check MD5 box or signature verification or something but that wasn't the case. I mounted USB in TWRP, deleted the zip and re-copied it over from my PC, still wouldn't work. Decided to reboot recovery and this time the zip installed.
This happened a couple of times on 2.2, so I went back to 2.1.1 but the issue persisted. I don't recall this ever happening on an ICS rom, so I don't know if it's something peculiar to Jellybean with TWRP. I do a lot of flashing and yesterday I flashed 3 rom zipfiles, the first 2 no problem, on the third I got that error message. As mentioned earlier, this has become a much more common occurrence, so I never know if my zipfile will flash or not. Tapping the reboot to recovery from TWRP always works in getting the zip to flash.
If it matters, I generally transfer the zipfile from my PC to the Fire from within TWRP using USB Mount. Thanks again for all your efforts, as well as TW.
Mike T
When I first installed 2.2 I had that happen once simply returned to home screen of twrp then it flashed... just a wild off the wall suggestion you may wanna update your su binaries and busybox couldn't hurt. I never have any issues using mount in twrp or transfer in os most the time I simply just download the file straight to my kindle and flash it from my download folder probably the wrong way to do it but I really haven't noticed anything unsightly by doing it this way ... if you continue to have issues use smirkis scripts to overwrite twrp and try again
Guys, thanks for all suggestions but there's definitely something going on with TWRP. I always use smirkis' scripts to install my recoveries, matter of fact, I've already gone the scenic route. LOL Went from 2.1.1 to 2.2 and then back to 2.1.1. When the issue persisted, went to 2.2 again and it still happened. So, because I had a theme that I made for 2.1.1, went back again to 2.1.1, all with smirkit. Thank you very much smirkis.
I don't feel I need or want to update busybox or su binaries, I have no issues with apps getting root privileges. smirkis, as for transferring files with USB mount in recovery, if you read the end of my post, that's how I've been doing it.
I've done some searching and it seems that TWRP may/does have issues with mount points in Jellybean. As I mentioned in my OP, it doesn't happen every time I flash and it's easily correctable by just rebooting from within TWRP to recovery. But it's a bit of a PITA, so hopefully TW will get a fix for it.
Okay ive been having this problem with twrp ever since i got my kindle, but ill boot into twrp ready to flash somthing and ill select it and then press flash but nothing happens. I can press every other button and they respond. but when i press flash, it always does nothing. can someone help me?
It turns out.. it was the frickin theme.. but idk how i managed to flash somthing about 3 times with the same theme
OLD DEVICES
Overclocked Motorola Olympus 4G
LG Revolution Blitz'd & 2.0 Gingervolted
Kindle Fire on MIUI V5
Sony Ericsson Xperia Play with UK Framework
AT&T Samsung Galaxy S II on MIUI v4
I was able to install TWRP2.2.0, it loads up fine to the recovery screen.... However no matter what rom I flash it always boots & reloads to the TWRP recovery screen.
I've installed (using direction in each of their threads): [ROM}[26-6-2012] gedeROM v1.7 {Linaro - Swipe Controls} [bootloader][05-26] FFF 1.4A bugfixes + new look + recovery boot [.zip file size] [ROM][ICS] |July 31| Energy™ -.¸¸.·´¯ ICS CM9 3.0 Kernel / Lightly Themed ¯´·.¸¸. -
None of these seem to work. I can unstall the drivers on my Win7 x64 PC so that I can see the Kindle partition. Then I can copy more zip files to try to the drive. At that point I reinstall the driver batch file to make it seen as a ADB device again instead of a Kindle. When I run the run.bat file it states that the device is offline. Please help me fix this. Thank you in advance.
(My Current Phone/Tablets) Verizon Motorola Droid 4 Stock (Stock for the moment) Nook Color (Rooted), NookDevs OS Acer Iconia Tab A500 32GB (Rooted), ICS 4.0.3 - Taboonay 3.0.1
--------------------------------------------
(Old Phone)T-Mobile G2 (Rooted), CM7.1.0-vision & ClockworkMod 3.0.2.4 Google G1 (Rooted), 8gb Recovery: RA-dream-v1.7.0-cyan | Rom: Super F 1.0 "Froyo On Crack" (Gifted to my Nephew) HTC T-Mobile Wing running Open Touch 7.5 (Saved as a backup phone).
***Update***
LOL, my fault.... I was not understanding the way it was doing the boot sequence. I didn't realize that the power button needed to be hit to cycle through the choices for boot-up. Pressing the power button a few times got me going into the normal boot up and not recovery, my ICS ROM Install loaded right up without issue at that point.
Out of curiosity.... Is there a way to block my kid from blowing it up in recovery if he finds his way in there? Anyway to place a password on it, or anything like that? Thank you again for your hard work on this.
Tom
(My Current Phone/Tablets) Verizon Motorola Droid 4 Stock (Stock for the moment) Nook Color (Rooted), NookDevs OS Acer Iconia Tab A500 32GB (Rooted), ICS 4.0.3 - Taboonay 3.0.1
--------------------------------------------
(Old Phone)T-Mobile G2 (Rooted), CM7.1.0-vision & ClockworkMod 3.0.2.4 Google G1 (Rooted), 8gb Recovery: RA-dream-v1.7.0-cyan | Rom: Super F 1.0 "Froyo On Crack" (Gifted to my Nephew) HTC T-Mobile Wing running Open Touch 7.5 (Saved as a backup phone).
Recovering iPad users may still remember the multitasking function where you can swipe left or right to … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?