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.

Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

---

Used goo manager and worked perfectly. On both nexus devices.... Thnx

Sent from my Galaxy Nexus using xda app-developers app

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

Sent from my Galaxy Nexus using xda app-developers app

Originally Posted by matthew0776

Backups not restoring on ns4g...on 2.4.0 and 2.4.1. Any body else having issues

Sent from my Galaxy Nexus using xda app-developers app

I backup my rom with 2.3.3.0 and restored with 2.4.1.0

Originally Posted by 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.

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

Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

---

Originally Posted by 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

If you first fix it by re flashing boot then try to get a log, then the log won't contain anything useful.

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.

Originally Posted by Dees_Troy

If you first fix it by re flashing boot then try to get a log, then the log won't contain anything useful.

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:

http://codepad.org/Xk2dT2Q9

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

[RECOVERY] TWRP 2.4.2.0 touch recovery [2013-02-25]

[RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]

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

Sent from my Galaxy Nexus using xda app-developers app