can t mount /sdcard/update zip - Eee Pad Transformer Q&A, Help & Troubleshooting

So, here is an interesting problem I ran into. And I am sure it has been answered elsewhere. But my searches for keywords has turned up nothing.
I am running Android Revolution HD 3.2.1 and wanted to update to their new version (3.5). I have clockworkmod recovery flashed and am trying to use the update.zip i have downloaded. Problem is, when I boot into recovery (vol down + power then hit Vol up to select recovery), i cannot get the update.zip to apply. I keep getting the error "can't mount /sdcard/update zip" I have re-flashed recovery, checked the signature verification, and even mounted all areas. Nothing works. What can i do to fix this issue? Is there another recovery i need for my TF101? Thanks in advance.

Related

[Q] failbooted recovery from CWM ROM Manager stuck

Dear people of awesomeness,
The story: I was following the exciting thread about the new CWM support for SGS4G by krylon360 and team, followed the directions (overwriting the recovery file WITH R/W enabled, placing update.zip into the root of my SD card...), and got stuck. Didn't know what to do exactly after that, other than try to use ROM Manager to backup my phone. Saw the "Reboot into recovery" option in the ROM manager menu and thought hey, let's see what this does. Most careless, stupidest thing I've done this year. fail.
The question: What is/are the way/s to boot into stock recovery mode? I can't seem to find a definitive method for booting into "stock recovery mode", though I've found plenty of ways to boot into download mode (a whole thread of them lol). I managed to find ONE method after reading through hundreds (honest) of posts in dozens of threads here and elsewhere: Hold vol+ Vol- and Power simultaneously from a powered off state.
The secondary fail: Obviously this didn't work for me, and although I'm near certain I'm going to have to do the "Odin" thing, I just wanted to ask if anyone could clearly explain the method to boot into stock recovery?
The shameless 2nd question: This question may have been asked elsewhere, shame on me, but... the .tar I'm downloading ([ROM-ODIN]T959VUVKB5 Stock + Root -- (hxxp://forum.xda-developers.com/showthread.php?t=978836)) will it wipe my phone?
akira6968 said:
Dear people of awesomeness,
The story: I was following the exciting thread about the new CWM support for SGS4G by krylon360 and team, followed the directions (overwriting the recovery file WITH R/W enabled, placing update.zip into the root of my SD card...), and got stuck. Didn't know what to do exactly after that, other than try to use ROM Manager to backup my phone. Saw the "Reboot into recovery" option in the ROM manager menu and thought hey, let's see what this does. Most careless, stupidest thing I've done this year. fail.
The question: What is/are the way/s to boot into stock recovery mode? I can't seem to find a definitive method for booting into "stock recovery mode", though I've found plenty of ways to boot into download mode (a whole thread of them lol). I managed to find ONE method after reading through hundreds (honest) of posts in dozens of threads here and elsewhere: Hold vol+ Vol- and Power simultaneously from a powered off state.
The secondary fail: Obviously this didn't work for me, and although I'm near certain I'm going to have to do the "Odin" thing, I just wanted to ask if anyone could clearly explain the method to boot into stock recovery?
The shameless 2nd question: This question may have been asked elsewhere, shame on me, but... the .tar I'm downloading ([ROM-ODIN]T959VUVKB5 Stock + Root -- (hxxp://forum.xda-developers.com/showthread.php?t=978836)) will it wipe my phone?
Click to expand...
Click to collapse
does your phone still boot up normally?
also when you get to the recovery menu it should be blue. scroll down to reinstall packages, and that will get you to CWM recovery
Ok first, Rom Manager should not be used until Koush incorporates our device in it.
Your findings are correct, the vol+,vol-, + the power button should get you into recovery, besides that the only other way is to use an app/power menu mod but that requires the phone to be on.
It sounds like the next thing for you is Odin. From your phones current state you can, hold vol+, vol- and then plug USB Cable into phone (Brings you into download mode), ive read some users pull battery and put it back in, but the first way i explained it should get you into download mode. From there, choose Roms KB5, KC1, or KD1, and yes your device will be factory reset. Your documents should be on your SD. I dont know if you have Titanium Backup to restore your apps, if not, you will have to manually install them after your odin session.
hope this helps
E:signature verification failed
chris.... said:
also when you get to the recovery menu it should be blue. scroll down to reinstall packages, and that will get you to CWM recovery
Click to expand...
Click to collapse
When I boot into recovery mode and select reinstall packages it starts out:
install from SD card
Finding update package
Opening update package
verifying update package...
E:signature verification failed
installation aborted
I have downloaded krylon360's cwm final update.zip and put it in my root directory.
The only posibility I can think of was a friend rooted my phone with an older update.zip file and i am trying to put the new one on. I deleted the old update.zip and copied over the new one.
i then downloaded odin and followed the instructions on a post to flash my rom with the t959+root from krylon360 as well. I believe that worked, because a lot of the apps that came with the phone are back now.
i tried reinstalling packages after this and still the verification error.
i have been doing a lot of browsing, searching and reading tons of posts on here... cant seem to figure this one out. any ideas?
Thanks
If you successfully flashed your phone and have root access, double check the update.zip is in the root and make sure its the latest one. Another thing is to make sure you copied over the Recovery file and pushed (Copied) it over to System/bin folder. Once you have those two in place you can reboot into stock recovery then "re-install packages" to get to CWM Recovery.
Hooray!
I did the ODIN thing, according to the post mentioned in my OP, and it fixed everything My custom shutdown vid, startup/shutdown sounds were gone, but my apps were still there, even paid apps. No titanium backup.... guess I got lucky lol. Scared the crap outta me when it wouldn't load past the T-Mobile startup image.
I knew not to use CWM yet, was following the thread about imminent implementation of sgs4g support for CWM, but just didn't really think that booting into recovery mode from CWM would get me stuck like that. Didn't even try to install recovery for CWM, knowing that "Epic 4G" and "Vibrant", etc were not the right choice despite the seeming similarities.
I had been keeping up with moving all apps i could to SD, so maybe that saved me, I dunno.
Followed pixelbrains post to use odin and worked perfect. Thank you all!!
glad you got your phone back. \m/
fknfocused said:
If you successfully flashed your phone and have root access, double check the update.zip is in the root and make sure its the latest one. Another thing is to make sure you copied over the Recovery file and pushed (Copied) it over to System/bin folder. Once you have those two in place you can reboot into stock recovery then "re-install packages" to get to CWM Recovery.
Click to expand...
Click to collapse
Thank you for that info.... I actually finally figured it out, but it took me forever. the key kind of is what i thought, that i did not have the recovery file in the right spot. I finally found a free file manager, super manager (recommonded on one of theses posts, i read so many cant remember which one ) after fiddiling with that for like 30-40 mins i finally figured the correct procedure to allow me to paste that recovery file and once i did that, bam, cwm recovery worked fine.
so, the fact that i am able to get to that screen and the latest update.zip file is in my external sd cards root dir. i am all goo there right?
i also used odin to flash "PDA_KD1.tar.md5" my phone after i got that recovery file in the correct place, and then when that was done i booted into the cwm recovery after i downloaded "Bali_SGS4G_v1.4UV.zip" and then i hit install zip from SD card, and i selected choose zip file and selected that bali one, and then i had to scroll down like 7 spots to hit yes to install and it went for a few seconds and then acted like it was done, so i just hit back and then reboot. how do i know if that worked? cuz i dont see anything saying bali at all on my phone...
does it sound like i did that right?
thanks again
edge228 said:
Thank you for that info.... I actually finally figured it out, but it took me forever. the key kind of is what i thought, that i did not have the recovery file in the right spot. I finally found a free file manager, super manager (recommonded on one of theses posts, i read so many cant remember which one ) after fiddiling with that for like 30-40 mins i finally figured the correct procedure to allow me to paste that recovery file and once i did that, bam, cwm recovery worked fine.
so, the fact that i am able to get to that screen and the latest update.zip file is in my external sd cards root dir. i am all goo there right?
i also used odin to flash "PDA_KD1.tar.md5" my phone after i got that recovery file in the correct place, and then when that was done i booted into the cwm recovery after i downloaded "Bali_SGS4G_v1.4UV.zip" and then i hit install zip from SD card, and i selected choose zip file and selected that bali one, and then i had to scroll down like 7 spots to hit yes to install and it went for a few seconds and then acted like it was done, so i just hit back and then reboot. how do i know if that worked? cuz i dont see anything saying bali at all on my phone...
does it sound like i did that right?
thanks again
Click to expand...
Click to collapse
settings menu then go to about phone and check the kernel
Sent from my SGH-T959V using XDA Premium App
thank you, it shows the bali as kernel... so glad to see i did it correctly

OTA update

So, today i did the following:
-rooted
-installed ClockworkMod Recovery v4.0.1.0
-downloaded the available OTA Update available (mine was still 1.18.)
-pressed install, the phone powered off, loaded the image with Android with the exclamation mark above it and it's been like that for about 45 minutes now... is that normal ? How long should it take to update ?
What do i do ?
I am afraid to press the power button as I fear it will brick it.
once you have this image with the exclamation mark in red, you have to press the power button + volume up.
now you have to choose to update from SD Card...
Ok, got it !
Now, it says "Cannot mount SDCARD:downloaded/OTA_Chacha_HTC_Europe_1.54.......Zip
Installation aborted."
I assume i must revert to Stock Recovery and then do it again, right ?
yep.
and to be sure, rename the file to "update.zip", since the recovery searches for this specific file name.
Which one should be renamed ?
Stockrecovery.zip or OTA_Chacha_HTC_Europe_1.54xxxxxxxxxx.zip ?
the OTA update.
Sorry for this but I'm stuck again.
I got the stockrecovery.zip from http://forum.xda-developers.com/showthread.php?t=1164468 but when I try to install it in CWM Recovery it says:
"E:Error in /sdcard/stockrecovery.zip
(Status 0)
Installation aborted."
What am I doing wrong ?
Isn't this the right Zip for me considering that I am trying to go back to Stock recovery for 1.18 and this one is for 1.33 ?
I just don't know how to flash to stock recovery ...
Ok, so I installed a clean 1.33 and after that I updated OTA 1.54.
But the way reverting to stock recovery is still a puzzle for me.
I tried with Terminal Emulator but it said that the file was not found on SDCARD.It was there, believe me.
I don't know, maybe someone will figure it out someday.
To revert to stock recovery you should rename the stock recovery to PH06IMG.zip.
The OTA update can be named whatever you like as you will select it manually, but the recovery has to be PH06IMG.zip. If you need any other infos you can hit me up on GTalk or Yahoo.

[Q] Asus bricked, wiped system and data, no fastboot, working adb, cant mount sd card

First things first, I am using the SL101 but as I could not find a place for that, I figured this is the best place for this post.Also I hate posting and creating new threads but there is absolutely no other thread like this, I have been searching for 3 days.
So I rooted my SL101 using vipermod with ease, then downloaded ROM manager but I think here is where I hit an issue, When cwm was installed it asked for me to confirm my device and the only device available to click was "Asus Transformer". As every other transformer tf101 firmware has worked on my tablet, I thought it would be fine. Then I was in the process of flashing Revolver 4.2.1 and my battery went flat so that was not ideal and this is when the issues began.
I booted into cwm recovery (vol- + power and then vol+ on the splash screen) and tried to "install zip from sdcard", I got the "Cant mount sdcard" dialog. I then rebooted and tried to flash the rom from ROM manager, when it rebooted, cwm went through a 20 second loop waiting for sdcard, and it did not find the sdcard so the operation was aborted. I tried a factory reset through cwm and when it rebooted, I would get the splash screen and the ASUS logo with the spinning dots loading, but it would not go past that (bootloop?). From here I could not access the OS at all.
Again into cwm and used the peri OneClick R&R Easyrecoveryv0.4. It went through all the unbricking dialog with three reboots, but one of the commands said it could not find "sdcard/recoveryblob". The system still did not work. I then put it into APX mode (vol+ and power) and installed the APX driver, used the download.bat method but the minute it opens commandprompt, it immediately disconnects the APX driver, the tablet remains in APX mode. This method did not work.
Somewhere along the lines I also managed to format the system and data so not when I turn it on it just goes into the splashscreen with the EEEpad logo and nvidia Tegra.
Also tried adb push to push revolver rom onto the system /sdcard/ directory, that works fine but then again it cant mount sdcard so I cant actually do anything with it. adb devices lists the device as 0123456789ABCDEF recovery. Finally I did try boot twrp.img using fastboot with the "fastboot boot twrp.img" command but it hangs on "waiting for device". fastboot devices also does not list any devices.
So I basically have a tablet whose cwm cant mount sdcard, adb works, fastboot doesnt see the device and I can only go onto cwm on the tablet or splashscreen. Can somebody help me out? I have spent a long time trying to fix this.
Fixed
Hi again, sorry for the double post but after posting that I realised the answer was pretty much staring me in the face and now this has been fixed. so this thread can be closed by the bigdogs.
For future reference to anybody who has this or a similar problem, especially if you format the system and fastboot is not working, the issue is cwm v6.0.1.3 (cant mount sdcard issue), I used the PERI oneclickrecovery v0.4. The unbrick selection did not work for my slider as I had already pretty much wiped any data from the system that could have been salvaged by the unbrick, but if you press "r" in the main menu it flashes a new recovery tool over cwm, and this new tool can access external sdcard so just upload the rom zip file onto there and flash. :fingers-crossed: Revolver 4.2.1 is now flashed and working. :victory:

Red exclamation mark coming out of android mans chest when trying to go to recovery

Has anyone else had this issue? I have loaded the CWM recovery, with success according the the message i get after loading it. I try to boot into recovery to flash my SU zip, and when i hold down the volume buttons and power to boot into recovery, i get a little android man with a red caution sign coming out of his chest. I did do some sort of Motorola OTA update before i loaded this recovery, wasnt sure if that was affecting it. Anyhow, it lets me go into recovery if I keep pressing buttons, but then when i try to run my SU zip, it says signature verification failed, and when in recovery, it doesnt say anything about it being CWM recovery. Any help is appreciated!
edit: When i am in recovery, at the very top, it says Android System recovery <3e>
does that mean my recovery didnt load properly?
Well I did a factory data reset, then flashed my recovery again and the custom recovery loaded and I was able to do the SU zip update. So I am guessing this means that the update is somehow messing with recovery loading? Thought this might be something good for you developers to know.
Assuming you're using the stuff from shabby's post that was put up not long after the phone was released, I've not yet seen anyone say that this still works after performing the Moto update.
Moved as this is not development therefore doesn't belong in the development forums.
Thanks
AvRS
OP, it sounds like you didn't flash CWM correctly the first time...
The behavior you describe is the stock recovery.
whitelightnin3006 said:
Has anyone else had this issue? I have loaded the CWM recovery, with success according the the message i get after loading it. I try to boot into recovery to flash my SU zip, and when i hold down the volume buttons and power to boot into recovery, i get a little android man with a red caution sign coming out of his chest. I did do some sort of Motorola OTA update before i loaded this recovery, wasnt sure if that was affecting it. Anyhow, it lets me go into recovery if I keep pressing buttons, but then when i try to run my SU zip, it says signature verification failed, and when in recovery, it doesnt say anything about it being CWM recovery. Any help is appreciated!
edit: When i am in recovery, at the very top, it says Android System recovery <3e>
does that mean my recovery didnt load properly?
Click to expand...
Click to collapse
The problem is that either the CWM recovery didn't take, or it did but when you updated, it reverted to stock recovery. I don't know which as I'm not familiar with the OTA you are referring to
Either way, you can try flashing CWM again and see if it takes
Sent from my PG06100 using xda premium
I installed the latest OTA update to my reverted back to stock, but still unlocked Q. CWM recovery and SuperSU worked on first try.
It sounds to me that CWM just didn't take. I remember reading something saying that the photon q will re-install the default recovery upon boot. It took a couple tries but I think what worked for me was flashing it through fastboot, then immediately rebooting into the recovery without ever letting the system boot up. After that it went right into CWM and has since gone there everytime.

A700 - Can't go into Recovery Mode ,OS OK, Root OK, FBoot Unlocked

Hello Guys,
i have made something wrong. i wanted to install the OTA JB Image from internal SD and i was thinking it would work with CWM.
First step i have made is, unlocked the bootloader with adb.exe etc...
The Second Step was to get root and superuser (here maybe i have done something wrong) but in the end i got superuser to work with a patched bootloader or something.
The Third Step i installed CWM and started to flash the recovery image.
But it doesnt go any further, if i try to go into recovery mode, it stucked always at the message "boot recovery kernel". from here its frozen.
i have two recovery images to choice with CWM, One is calling TeamWin Recovery Image and the other is the CWM Recovery. But both doesnt work. I tried to go directly from CWM to the recovery mode and with the Power Button and Vol + Method. Both not working. If i try to boot manually first it says "it update via sdcard" or something, and immiadately it follows the message "boot recovery kernel" and stucked....Nothing happened
Thats a big problem because i cant update anymore and i dont have an externel sd card here. And via google i cant find a solution to this problem.
Is there a Method to install a new Recovery.img via adb? that work properly?
Maybe someone can help me out?
Greetings
Jack
Sorry for my bad English.
[EDIT] i have solved the problem by my own. I've flashed the wrong recovery img. Now i have flashed that version for ICS with vorbeths Easy Root. And now i can Update the version. Hope there will be no more problems...
Please steps
JacKJodel23 said:
Hello Guys,
i have made something wrong. i wanted to install the OTA JB Image from internal SD and i was thinking it would work with CWM.
First step i have made is, unlocked the bootloader with adb.exe etc...
The Second Step was to get root and superuser (here maybe i have done something wrong) but in the end i got superuser to work with a patched bootloader or something.
The Third Step i installed CWM and started to flash the recovery image.
But it doesnt go any further, if i try to go into recovery mode, it stucked always at the message "boot recovery kernel". from here its frozen.
i have two recovery images to choice with CWM, One is calling TeamWin Recovery Image and the other is the CWM Recovery. But both doesnt work. I tried to go directly from CWM to the recovery mode and with the Power Button and Vol + Method. Both not working. If i try to boot manually first it says "it update via sdcard" or something, and immiadately it follows the message "boot recovery kernel" and stucked....Nothing happened
Thats a big problem because i cant update anymore and i dont have an externel sd card here. And via google i cant find a solution to this problem.
Is there a Method to install a new Recovery.img via adb? that work properly?
Maybe someone can help me out?
Greetings
Jack
Sorry for my bad English.
[EDIT] i have solved the problem by my own. I've flashed the wrong recovery img. Now i have flashed that version for ICS with vorbeths Easy Root. And now i can Update the version. Hope there will be no more problems...
Click to expand...
Click to collapse
How did you do that? could please put steps or that alike? I rooted my a700 and put the iconian rom but i wanted to put Cyanogen but it gets stuck like you said, I also installed iconian using Rom managerm please help!

Categories

Resources