So im still pretty new to this, but im pretty technical so I pick up on this stuff pretty quick. When I first started getting into this stuff I was using CWM as I saw it used most often around the forums. After getting root and unlocking I backed up my stock rom, and then tried to restore it just to test, and it failed. I tried a few times, with different settings, and it failed everytime, so I pretty much had no choice but to go to custom roms at this point. After switching to TWRP 2.6.3, and messing around with a few CM7.2 and CM9 roms, I decided to flash the 4.5.141 sbf (came from 4.5.145), which bricked me untill i flashed the pudding file again, then flashed a 4.5.145 update fruitcake, so i was back to where I was. Backed up the stock rom again with TWRP, wiped everything just in case that was the problem before, and it still failed when I attempted to restore. Again tried different settings, restoring from the SD card, from the internal, mounted and unmounted partitions. Nothing. I flashed CM9, backed up, and it restored flawlessly. Reflashed 4.5.141, pudding, and 4.5.145 update again, repeated the backup and restore. Fail.
All partitions restore except the system partition. No errors are given in the dialog box. The last line of text is "Restoring system..." However, looking through the log, I find this at the bottom;
Code:
==> tar_extract_regfile(t=0x139110, realname="/system//etc/spellchecker/pt_BR.dic")
==> extracting: /system//etc/spellchecker/pt_BR.dic (file size 4581228 bytes)
FAILED RESTORE OF FILE i: /system//etc/spellchecker/pt_BR.dic
E:Unable to extract tar archive '/sdcard/TWRP/BACKUPS/TA20708E1R/4.5.145_Stock/system.ext3.win'
I:extractTarFork() process ended with ERROR=255
Whats the problem here? I flashed CM9 and it backed up and restored without a flaw. Why is it just the stock roms that are failing me?
BUMP
No ideas from anybody?
Iirc, thete was an issue oreventing the correct decompression of system. On the international fruitcake thread this is discussed.
I had that trouble also, but since the stick rom is a piece of crap, just deleted the backup and installed other roms hehe
Enviado desde mi MB860 usando Tapatalk 2
Related
I thought I had this down and well, I guess not....
I had a great running Superclean v2.6 nonvoodoo running on my DL09 and I did a factory reset from inside the settings. I was trying to setup my Google account so my Google Voice would work right. I had made a backup using red Clockwork so I thought I'd be okay. The phone rebooted and hung on the Samsung screen.
I've been able to Odin the new cwm-recovery-ALL.tar to the phone but it still hangs. I tried using the old version CWMrecovery.tar and it boots in the factory recovery (2e) and won't allow me to apply the update.zip file since it can't mount the drive.
Um, is there a way out? I thought I saw a tar file for the DL09 and that would take me back to stock and then I could install the red recovery and restore my back up. Any help would be appreciated. Thanks!
Error in factory recovery (2e):
E:Can't mount /dev/block/vold/179:9
Can't mount SDCARD:update.zip
Installation aborted.
You can flash to EB01 with all the stuff in this post:
http://forum.xda-developers.com/showthread.php?t=977493
Thanks! I think I found another route, but your solution looked good.
I used Odin and put the cwm-recovery-ALL.tar on after having put CWMrecovery.tar (the older version) and it started into red. I applied the update.zip and installed cwm-recovery-ALL.zip and then am now in the process of restoring my backup. Whew! That was close.
*EDIT*
So, that didn't actually work. When I tried to restore with RED Clockwork it froze during the restore. It specifically froze on restoring the "tegra_flash_image". I even tried using the DL09_stock.zip and that didn't work either. I used the method you recommended and it worked very well. In fact If I need to go back to stock this method seemed the fastest and most straightforward. Thanks again.
For those who read this later. I then installed my ROM choice, which is non voodoo Superclean v2.6 after doing everything listed here http://forum.xda-developers.com/showthread.php?t=977493 and it was much cleaner than what I had originally.
To make a long story short my gtab broke so I got another one. Prior to shipping the bad one back I did an nandroid backup and copied to my computer.
I received my new one today, installed clockwork and trying to do a restore.
Error while flashing boot image!
Click to expand...
Click to collapse
is what I receive. What gives? Any thoughts on why I'm seeing this?
I managed to get the "md5 sum mismatch" on my dx, but that was because I renamed the original file and used spaces in the name...
Never managed to get the error you got though
Sent from my DROIDX using XDA App
I've tried so many things. I flashed Vegan ROM over again, performed reboot, went into the fresh clean ROM..then rebooted into recovery to restore. Same error.
I tried partitioning over again, wiping, etc then restoring..same thing. I even tried another nandroid that I took days prior....!! I'm at a loss... argh! I want this image back from my nandroid
Also to add confusion to the mix: I tried taking a backup of nothing basically, and then restoring that and it worked fine. However just none of my 3 nandroid backups takin off my old device restore on this device. Is there a coorelation?
There has to be a way to flash back my nandroid backup...right?
Maybe my bootloader is locked, thus stalling on the boot.img?
ok so now I really jacked it up...tried downloading rom manager from market, installing some recovery and restoring my image, which did nothing but freeze at the viewsonic screen. Now I can't get into recovery anymore
Now I tried nvflashing back to stock... windows 7 crashed at the 11_app_img but it copied scucessfully, and now the tablet won't turn on?wtf!
Okay so I recently got this phone more or less as a toy and have been playing with its hardware and software to get it up to par and usable. I've been very impressed by this thing. I ended up with Trackball optional recovery and CM7 Condemned running very well. I seen Gin-sen-tazz and decided to give it a whirl.
Booted into recovery, did a nandroid then wiped data cache and dalvik and then went to flash the rom. It wouldn't go, told me to do something via adb. So I went to restore the backup of cm7 and get a new download ( didnt verify any md5's )
The back up restore gave me the same sort of error, then told me to do something else via adb. I was pretty peved off at this point and went into rom manager and flashed cwr and made a back up of the fresh cm7 install via cwr, and then tried to install the rom via rom manager and then manually in cwr and it still failed.
I'm still downloading my second copy of the rom and I'll be reporting back, but is there any harm in having both recovery's? I really would prefer to run cwr but I have heard of a few bricks, how wide spread is the epidemic? Boot loader still pushes me into trackball optional recovery when selected.
Just kinda sucks that I have two recoveries and neither will work. I am not very new at the whole rom flashing thing but I am not an expert by any means, and have not yet taken the time to learn my adb skills which I know I should
Alright downloaded and put the new rom on the sd card, booted into trackball optional and it flashed just fine.
I also used cwr to back up cm7 and then restore cm7 just to see if that backup indeed worked, and it did. Now I'm concerned that I don't have a stock back up, I made one in trackball recovery but it wont restore... The only back up I have that's working is the cm7 one via cwr... what would you guys recommend i do?
If you decide you want to flash back to stock 2.1 at some point, there's a couple simple options.
Flashback21 will get you back to the latest OTA(March 2011)...unrooted completely stock 2.1.
http://forum.xda-developers.com/showthread.php?t=792026
This other also gives you the latest March 2011 unrooted stock OTA but leaves your custom recovery.
http://forum.xda-developers.com/showthread.php?t=984274
Dunno if this is what was going on, but the Nandroid restore in Amon_RA for the Eris (and derivatives including the trackball-free recovery, I presume) have a 30% battery charge requirement.
If your battery isn't charged above that level, you'll just get a cryptic message about running nandroid-mobile.sh from adb; it won't say "charge your battery, please".
It pays to read Amon_RA's original post, where he points out that you should always check the recovery log file - the exact reason that you could not run the restore operation is reported in that log file. Rather than complaining about an unknown problem on a forum, you would instead know exactly what the problem was.
You can get at the file ( /cache/recovery/log ) via adb while the same recovery session is running, or you can use the Amon_RA menus to copy it to your SD card for later review. It's just a plain text file. Every time you boot the recovery, it gets overwritten - so you need to either review it right away after a problem occurs, or save it to the SD card.
bftb0
I unlocked and rooted my Atrix 4g (international) yesterday, and though everything seemed to go well I have two big problems now.
I've tried two ROMs so far, Avatar http://forum.xda-developers.com/showthread.php?t=2140902 and another CM 10 one http://forum.xda-developers.com/showthread.php?t=1781970
With each of them, the flash goes fine, but once everything is booted up I have less than a minute before the phone resets itself. the problem is exactly the same between the two roms.
Fine, says I, I'll go back to the CWM backup I made. Nope. When I try to restore one of the two nandroid backups, I get an error "error while restoring /system.
SO, while any help finding a solution to the reset problem would be a huge help, just getting back to my restore point is probably better - I'm pretty clearly out of my depth.
Re: [Q] >1min. crashes and can't restore /system
Did you try formatting /system through CWM?
ravilov said:
Did you try formatting /system through CWM?
Click to expand...
Click to collapse
I haven't, but I managed to find a fruitcake of the stock ROM for my phone and flashed it, so I have a functioning phone at least. I'm curious about the reset problem, but I don't think I'll be messing with my phone any more.
A week ago I was getting ready to do a nandroid backup before flashing a new ROM. When I tried backing up, it said that I didn't have enough storage. When I went to look at what was being backed up, I saw that the /data partition was 40 terabytes in size. I reformatted everything and flashed a new ROM and started having problems trying to enter a new APN (I'm on AT&T with Verizon Note 2). Eventually I ODIN'd back to stock 4.1.2 and then re-unlocked the bootloader. I reflashed TWRP and saw that /data was back to normal. Then I flashed a new ROM and encountered this.
http://imgur.com/Pqpnr7k,tXyMW7e#0 (two images)
I tried a few different ROMs and the problem persists, and I can't enter new APNs which is rather inconvenient for the times when I need use the phone part of the device. Anyone have any ideas what is going on with the internal storage? Perhaps the NAND has gone bad? Any information or insight into this would be greatly appreciated.