[HC 3.1] – OTA (update.zip) – (Update: 6/18/11)
- Thread starter pershoot
- Start date
that means something failed. go back to recovery and do a restore of your backup.
boot back in. then go back to cwm (use the latest, 0608 that i posted here in the forums/droidbasement), and restore system/boot only from the dload posted this morning. check /tmp/recovery.log for any issues. then reboot and try to boot it.
if it happens again, go back to cwm, do a full wipe (dont worry, you can restore data later on), then restore system and boot only. then try to boot it.
i did two restores this morning myself, and all checks out fine on my specific device.
Last edited:
So I'm having a fastboot driver issue, and I'm about at the end of my rope.
Question- if I have CWM already installed (using ROM Manager), can I unpack the zip, copy the folder to clockworkmod/backups, and restore using CWM like I was just flashing a backup I had made myself? My guess is that if it were that easy, pershoot would have set it up that way, but hope springs eternal...
Thanx again for posting the backup, pershoot. Good looking out.
Question- if I have CWM already installed (using ROM Manager), can I unpack the zip, copy the folder to clockworkmod/backups, and restore using CWM like I was just flashing a backup I had made myself? My guess is that if it were that easy, pershoot would have set it up that way, but hope springs eternal...
Thanx again for posting the backup, pershoot. Good looking out.
i havent tested CWM from RM, so i cant advise at this current moment. please get fastboot working. it is crucial to have this functionality, not only for now but for later on.
You're right, of course. I'll keep working at the driver issue- better safe than sorry. It's frustrating because it works with both my evo and my tb, but not the tab. Where's that damned sledgehammer?
Thanx again for the help & the quick response.
reinstall the driver set from droidbasement. you can find it under drivers in galaxy folder (for windows only).
now try.
if a no go, then remove the driver (if using windoze), in device manager (fastboot or some such), then unplug/replug. you should be able to see it.
also, take note of this:
http://xdaforums.com/showpost.php?p=14601619&postcount=18
my device is not encrypted (and also we dont usually backup the efs partition in normal backups).
if your device is encrypted, this may not work for you.
i will add this to the blog posting.
http://xdaforums.com/showpost.php?p=14601619&postcount=18
my device is not encrypted (and also we dont usually backup the efs partition in normal backups).
if your device is encrypted, this may not work for you.
i will add this to the blog posting.
OTA
So I totally just did the OTA update to 3.1 on the I/O LE Tab and noticed that live wallpapers can't really be set as lock-screen wallpapers... WTF - anybody else notice any changes? The system still seems kinda laggy compared to the Xoom 3.1 that I have. Weird...
So I totally just did the OTA update to 3.1 on the I/O LE Tab and noticed that live wallpapers can't really be set as lock-screen wallpapers... WTF - anybody else notice any changes? The system still seems kinda laggy compared to the Xoom 3.1 that I have. Weird...
is it possible to have to competing recoveries, the stock and clockwork which make this thing bootloop?
when are you bootlooping? when you restore and try to boot in, or when you try to add su/superuser after a successful boot to 3.1?
i restore fine and everything works great but yes when i try to push su it boot loops when i reboot
flash the tools pack (as advised in the other thread).
use the one before 5/16 (the one without the boot.img in the zippy).
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
521Pershoot
just brought my tab back from the dead using ODIN , after doing the advanced recovery, my tab just hung on the samsung logo
this version: http://www.megaupload.com/?d=DDN6BYB2
and this pda md5: http://www.mediafire.com/?gcenefqc3khcc0c
