Database Info

[Q] Cognition 2.3b3 flash fail

Hey guys, I am trying to flash Cognition 2.3b3 from Cognition 2.3b2, and the flash keeps failing in clockwork recovery. I have voodoo lag fix disabled, I flash clockwork recovery, and I have even tried installing the update with the wipe option checked. I keep getting an error during the installation saying "installation aborted. Cannot open /sdcard/Cognition2.3b3.zip.
Does anyone have any ideas?

Did you try redownloading the zip file? It may be a corrupt download?
If not, I wouldn't know since I haven't upgraded to b3 yet

I did try redownloading the zip. I can't figure what the problem is. The file came straight from designgears sight. I do not have winzip installed on my laptop. Could that make a difference?

Just sharing my experiance.
I had stockish eclair with voodoo (deleted one system file by mistake and it wouldn't boot) so i flashed Cognition 2.3b3 thro odin , it went thro without problems kernel detected ext4 present (from previous voodoo) and everything works fine
So you don't need to disable voodoo lag fix if your next rom supports it. And you could also try flashing with odin if clockwork fails.

bparkerson04 said:
I did try redownloading the zip. I can't figure what the problem is. The file came straight from designgears sight. I do not have winzip installed on my laptop. Could that make a difference?
Click to expand...
Click to collapse
Give us a Step by step of what you did so we can help further. When asking for help it helps us alot to give as much information as possable

I think I figured out what the problem was. I was deleting some stuff from my internal sd card, and I deleted the update.zip I used to root my phone when it was stock. I didn't think I needed it anymore. The thought occurred to me just now to put that file back, and I was just able to flash the rom. Go figure. Thanks for all of the input guys. I guess I will always need to keep that update.zip on my root sd.

[Q] Can't mount SD card in CWM?

I've searched........extensively.
I've spent hours here with my end goal being to go from EE4 stock to EE4 rooted with Voodoo lagfix (imnuts). When I got the phone originally I had rooted ED1 using the gingersnap method, from there I OTA'ed to EE4, losing root.
Tonight i've ODIN'ed CWM, then flashed voodoo lagfix via CWM. Everything went great, the only problem being that I couldn't get root access for apps, but verified that lagfix was enabled using the Quadrant benchmark app. I'm guessing it was an SU issue. After trying a few suggestions from the board and still being in the same position, I flashed the stock EE4 ROM zip via CWM posted by imnuts, with the idea that i'd re-try the process from the beginning. Everything still great. Reflashed CWM via ODIN, and that worked with no problem. But the problem i'm having is that when I attempt to reflash the Voodoo lagfix zip via CWM, it says that it can't mount the SD card. The SD card is perfectly readable when the phone is booted into the OS. Even manually mounting the SD in CWM yields nothing. I've tried reflashing CWM 3 times, flashes fine, but still getting the SD card mounting error. I could technically stay on EE4 stock, but i'd really like to have root access.
Any assistance anyone could offer would be greatly appreciated.
I forgot to add, if I boot into CWM directly after flashing it, it works, but if I boot the phone into the OS, then attempt to power off and boot into CWM, it boots into the blue Samsung recovery screen. Every time.

I spoke too soon, I guess I hadn't actually tried everything. In any case, if anyone else ever has the problem, the fix went like this:
Flash back to stockrootedED1-20110517.tar.md5 via ODIN > OTA to EE4 > Flash CWM via ODIN > Flash PBJ Voodoo lagfix via CWM and end up at EE4 with root access and a very stealthy Voodoo lagfix kernal (thanks imnuts!).
If anyone is inclined to answer though, there is one question...is it wise to avoid the update that Market is now telling me I need for Superuser? Or is it ok to install said update? TIA

kgbeezr1 said:
If anyone is inclined to answer though, there is one question...is it wise to avoid the update that Market is now telling me I need for Superuser? Or is it ok to install said update? TIA
Click to expand...
Click to collapse
Go ahead and update. No problems with me when I did.
Never hurts to have a TiBu backup of your apps before updating, just in case...

[Q] Is is Possible to Downgrade from 3.2?

I read some posts about how to downgrade the transformer's firmware, but these were all pretty old and when I followed these steps they didn't work. I was wondering if it is still possible to downgrade from 3.2 to 3.1 build 8.4.4.11.
Thanks

one way would be to follow eepad unroot thread to go back to stock 8.4.4.5 and do microSD card update to stock 8.4.4.11

Which recovery do you have?
There is an update for 8.4.4.11 on the ASUS website. This is NOT the OTA udpate. This is a zipped blob that you can flash from the stock recovery. If you are rooted with CWM, I think it might flash through the staging partition.

gee one said:
Which recovery do you have?
There is an update for 8.4.4.11 on the ASUS website. This is NOT the OTA udpate. This is a zipped blob that you can flash from the stock recovery. If you are rooted with CWM, I think it might flash through the staging partition.
Click to expand...
Click to collapse
I have the stock recovery.

I think you can download the 84411 update from the ASUS website and flash it with the stock recovery.
It is not the OTA, but a full system that will over-write your system files. I think you unzip the file and copy the whole ASUS folder to your SD card. Insert your SD card and it will recognize and prompt you for the update. To be clear, you should have something like /ASUS/Update/US_eeepad....8.4.4.11.zip on your sdcard. It will recognize it when it is inserted.
Double check this and flash at your own peril.... it might not let you downgrade, in which case, there are 2 unroot guides in the dev section.

i want to do this, is the SD card 100% needed? i dont have one right now

Sorta- the sdcard would make it easy, but I think you could extract the pieces and flash them via nvflash.
If you are rooted, you can "flash" them via adb by copying the blob onto the staging partition.

why downgrade? it not needed to root or anything, so am i missing someting?

Have you tried nvflash? That seems to be the best way, but be sure to backup data, I got titanium backup and coped the data to my sdcard
Sent from my revolver!

since few weeks ago my TF its been having problem of deep sleeping and will turn on whenever he wants or when battery has 0% but my friend TF which is stock and bought from the same place and time i did still has 3.1 8.4.4.5.2 build is just fine so i wanted to try downgrading

You might also consider reflashing the ROM you are using now. I did notice some odd SOD issues from a bad flash. I had other issues as well- the screen would dim if I tried to follow a link in an email. I forget the actual cause, but it was fixed when I reflashed the right parts back in.

sorry im kinda newb about this.... how do i know what kind of ROM im using and how do i reflash it?

xtonyx06 said:
sorry im kinda newb about this.... how do i know what kind of ROM im using and how do i reflash it?
Click to expand...
Click to collapse
There is no exact method of knowing, but you can looking in settings/about tablet and look at the kernel version and build number. Then cross reference them with this thread. You might have a custom rom, in which case it might have the name in the build number.
You might have a bad flash. You could try charging the batttery completely (overnight) and then reflashing. If you are having issues, it might be easier to flash a custom ROM such as Prime 1.9.
http://forum.xda-developers.com/showthread.php?t=1251044
Be sure to back up any important data since nvflash will erase everything.

[Q] CWM and stock recovery

Hello -- I'm new to the Charge but have a little experience rooting/flashing ROMS with Motorola devices. At this point all I want is a rooted device and everything else stock (2.2.1 firmware / EE4). To achieve this I placed the Superuser app zipfile onto my sd card, flashed CWM with Odin, booted into recovery and applied the zip update. Everything went smoothly, my device is now rooted and works fine. However, when I boot back into recovery I find that CWM is still installed, I was under the impression that this procedure would overwrite CWM with stock recovery when I rebooted. I don't really mind having CWM, just wondering if the fact that it wasn't overwritten is indicative of some other problem that is likely to bite me in the a** down the road.
Also, if all I have done is rooted and kept the kernel untouched, will I be able to receive the gingerbread OTA when it is released (if ever)? Or will I have to flash back to a stock Froyo ROM?
Thank you thank you thank you in advance.

talbot27 said:
Hello -- I'm new to the Charge but have a little experience rooting/flashing ROMS with Motorola devices. At this point all I want is a rooted device and everything else stock (2.2.1 firmware / EE4). To achieve this I placed the Superuser app zipfile onto my sd card, flashed CWM with Odin, booted into recovery and applied the zip update. Everything went smoothly, my device is now rooted and works fine. However, when I boot back into recovery I find that CWM is still installed, I was under the impression that this procedure would overwrite CWM with stock recovery when I rebooted. I don't really mind having CWM, just wondering if the fact that it wasn't overwritten is indicative of some other problem that is likely to bite me in the a** down the road.
Also, if all I have done is rooted and kept the kernel untouched, will I be able to receive the gingerbread OTA when it is released (if ever)? Or will I have to flash back to a stock Froyo ROM?
Thank you thank you thank you in advance.
Click to expand...
Click to collapse
What zip did you apply IN CWM?
Sounds like you applied a kernel too. Having CWM is not normal if you just flashed the superuser zip.
You will likely need to flash back to stock prior to updating with the GB OTA whenever it comes out.
_____________________________
Bloat frozen EE4 / Stock Kernel
V6 SuperCharger / Loopy Smoothness Tweak

Thank you for the reply.
The only zip I applied was the su-2.3.6.3-efgh-signed file downloaded here.
For CWM I flashed 0817_charge_recovery.tar.md5 found here.
Again I am now rooted but can still boot into CWM. After flashing the CWM file and disconnecting my phone, I initially fat-fingered it trying to boot into recovery and it rebooted. I then powered off and booted successfully into CWM to apply the zip file.
Any thoughts?

Ok, the main difference I see between my config and yours is that I may have used a different version of the superuser package.
The one at the link that you provided is superuser/su-3.0-d-signed.zip.
The one that I used is the su-2.3.6.3-efgh-signed.zip from here
You did start out from stock correct?
What is the kernel version in Settings->About phone->Kernel version?

Actually when I downloaded the Superuser zip file from the site I referenced it was su-2.3.6.3-efgh-signed.zip. This was a few weeks ago -- before version 3.0 was added.
My phone was absolutely stock when I got it 2 weeks ago and I have done no other messing with it. The Kernel version as it reads right now is:
2.6.32.9
[email protected] #1

talbot27 said:
Actually when I downloaded the Superuser zip file from the site I referenced it was su-2.3.6.3-efgh-signed.zip. This was a few weeks ago -- before version 3.0 was added.
My phone was absolutely stock when I got it 2 weeks ago and I have done no other messing with it. The Kernel version as it reads right now is:
2.6.32.9
[email protected] #1
Click to expand...
Click to collapse
Looks like you did the same steps that I did other than your extra boot into CWM. Usually, the stock init will check for the proper recovery, file systems, etc and then "fix" that which isn't right.
I have never seen it not do that before (I have had to reflash CWM several times before due to botching the 3 button bit)
_____________________________
Bloat frozen EE4 / PBJT Voodoo 0730
V6 SuperCharger / Loopy Smoothness Tweak

You cannot apply the OTA if you have CWM recovery. It will fail. Usually you need to have a fully bloated stock rom w/ stock recovery. Root is ok but you will lose it w/ the update

hoppermi said:
You cannot apply the OTA if you have CWM recovery. It will fail. Usually you need to have a fully bloated stock rom w/ stock recovery. Root is ok but you will lose it w/ the update
Click to expand...
Click to collapse
That's kind of why I chose this method to root, thinking that CWM would get overwritten when I rebooted -- but it didn't. Oh well.

talbot27 said:
That's kind of why I chose this method to root, thinking that CWM would get overwritten when I rebooted -- but it didn't. Oh well.
Click to expand...
Click to collapse
Enjoy it. I like CWM much better than stock recovery ;-)
_____________________________
Rooted and Bloat frozen Stock EE4
V6 SuperCharger

[Q] [CWM] Recovery backups not working?

So, I just did a backup of my Glorious Overdose setup using the voodoo recovery it comes with and I got MD5 errors while trying to restore...
Anyone else have this issue?

I never restored from a cwm successfully, I think its not fully functional. Red nor orange... luckily I saved my apps & settings using mybackup

I have also had this problem. if anyone knows why, please let us know. I was able to restore data, but a couple funny things happened. when restoring, i get error restoring boot image or md5 sum mismatch. when restoring data, my phone stuck at restoring android_secure. i pulled the battery and rebooted. luckily that didnt brick my phone.

fiveseven808, did you flash cwm through rom manager? if so, i think that might be the problem. i flashed through rom manager and was having problems backing up/restoring. i went to this thread: forum.xda-developers.com/showthread.php?t=1124453 and downloaded the update.zip file in the first post, saved in my download folder. i then went to the root of my sd card and deleted the update.zip file that was there. i moved the other update.zip from my download folder to the root of my sd card. rebooted into cwm and took a backup no problem.

sidekick_fanatic said:
fiveseven808, did you flash cwm through rom manager? if so, i think that might be the problem. i flashed through rom manager and was having problems backing up/restoring. i went to this thread: forum.xda-developers.com/showthread.php?t=1124453 and downloaded the update.zip file in the first post, saved in my download folder. i then went to the root of my sd card and deleted the update.zip file that was there. i moved the other update.zip from my download folder to the root of my sd card. rebooted into cwm and took a backup no problem.
Click to expand...
Click to collapse
I did! But I was unable to use it... or something really strange happened..
Before Glorious Overdose, I could boot into CWM 3 using the recovery boot method. After Glorious Overdose, I realized I could boot into CWM Voodoo with the three button method getting around the stock recovery, and boot into a VERY broken CWM 4 via ROM manager.
Will your advice fix whatever I did wrong?

I have no idea, but you could try it and see. if it doesnt, your no worse off than you were to start with.

Update: I now know for sure that having the right update.zip file will fix the issue. I had to restore my phone today due to issues caused by unknown sources. I tried to fix the issues before doing a restore, but no luck. so I booted into cwm and hit restore. it worked without a single hitch. So the problem (for me at least) was definitely having the wrong update.zip file.

I have never had this issue, with VooDoo or regular CWM... Bad update.zip sounds like it would be the problem, as you said

i believe the issue is in the update.zip file. when flashing cwm through rom manager, i was unable to properly backup and restore. after switching the update.zip with the one found in the dev thread, i can backup and restore to my hearts content. i am very glad to have fully functional cwm on this device, as i had it on my last phone, the tmobile comet. the comet was my first android device. i was not entirely happy with it, but it gave me enough of a taste of android to figure out i wasnt going back to blackberry. prior to android, the best phone i had ever owned was a blackberry pearl. now, the sk4g is the best phone i have ever had, even better than the blackberry pearl. for me, this keyboard has no parallel, and the setup and ui is nowhere near as tough to get used to as people had been saying it was on the forums. but i digress. cwm is the best alternative to the stock recovery, and its good to have it working on this phone.