Hello. I have rooted, stock, tab. OTA's would never install right. I tried downgrade to.30 to reroot JB. I tried several times. Didn't work. Then, somehow, I'm stuck on boot screen. I tried the soft brick recovery options, didn't work. I can access stock recovery, but when I rename file and put on SD card, it says file not found. Any help or suggestions would be very appreciated.
redheadplantguy said:
Hello. I have rooted, stock, tab. OTA's would never install right. I tried downgrade to.30 to reroot JB. I tried several times. Didn't work. Then, somehow, I'm stuck on boot screen. I tried the soft brick recovery options, didn't work. I can access stock recovery, but when I rename file and put on SD card, it says file not found. Any help or suggestions would be very appreciated.
Click to expand...
Click to collapse
Most likely you are doing something wrong if the recovery said that no file is found.First make sure your MicroSD is formatted in FAT32 and then check the filename and keep in mind that if you use Windows usually you don't need to use the .zip file extension. Also make sure that you extract the zip from the file you download from Asus site.
Pretoriano80 said:
Most likely you are doing something wrong if the recovery said that no file is found.First make sure your MicroSD is formatted in FAT32 and then check the filename and keep in mind that if you use Windows usually you don't need to use the .zip file extension. Also make sure that you extract the zip from the file you download from Asus site.
Click to expand...
Click to collapse
did everything again. Reformated SD. Still nothing. Here's what it tells me
Finding update package
E: failed to mount /SD card (no such file or directory)
E: can't mount /sdcard/ASUS_BUNDLE.zip
E: failed to mount /sdcard (no such file or directory)
E: can't mount SD card
Installing update...
Finding update package...
E: failed to mount /sdcard (no such file or directory)
E: can't mount /sdcard/EP201_768_SDUPDATE.zip
SD installation aborted
redheadplantguy said:
did everything again. Reformated SD. Still nothing. Here's what it tells me
Finding update package
E: failed to mount /SD card (no such file or directory)
E: can't mount /sdcard/ASUS_BUNDLE.zip
E: failed to mount /sdcard (no such file or directory)
E: can't mount SD card
Installing update...
Finding update package...
E: failed to mount /sdcard (no such file or directory)
E: can't mount /sdcard/EP201_768_SDUPDATE.zip
SD installation aborted
Click to expand...
Click to collapse
This is odd, i heard that with the new JB bootloader the fastboot mode can be accessed even with locked bootloader, can you boot in fastboot mode (USB ICON) when pressing Volume Down +Power?
Pretoriano80 said:
This is odd, i heard that with the new JB bootloader the fastboot mode can be accessed even with locked bootloader, can you boot in fastboot mode (USB ICON) when pressing Volume Down +Power?
Click to expand...
Click to collapse
Not on JB. was trying to go back to ICS to root it again. I went from .30 to JB and back down 3 times trying to keep root. Didn't work cause OTA's would never install. Finally left it at ICS .30. Everything was fine for about an hour, then I rebooted. It never came back alive. Spinning circle.
redheadplantguy said:
Not on JB. was trying to go back to ICS to root it again. I went from .30 to JB and back down 3 times trying to keep root. Didn't work cause OTA's would never install. Finally left it at ICS .30. Everything was fine for about an hour, then I rebooted. It never came back alive. Spinning circle.
Click to expand...
Click to collapse
In this case you can't do anything to restore it if the recovery doesn't work. Try to Wipe Data and then check the recovery again, if still doesn't work ask a RMA ticket from Asus.
Just to be clear, what are you renaming your file to? It needs to be renamed to "EP201_768_SDUPDATE.zip" and on an SD card formatted to FAT32. Also, if you're working with a .zip you downloaded from ASUS, you need to extract that zip and rename the EXTRACTED zip file and place that one on the SD.
I'd also try a different SD card if that's not doing it for you. "E: failed to mount /SD card (no such file or directory)" already sounds like it's just not liking that particular SD card right now.
You could also try to download JB from ASUS and flash that file instead of ICS. That way, you will have your fastboot option back so that you can send ICS via fastboot, re-root, and upgrade. That's what I did when I was going through this yesterday trying to reroot after I was bricked.
Once you've over come that part, on to the rooting (and keeping root). It wasn't working with the JB from the ASUS site. I was able to flash it, but I kept losing root. I had to use the dlpkgfile method from my OTA to upgrade to JB in order to keep root. If you don't have that file, you can find one somewhere here or I can provide you with mine.
Good luck!
Alitheia said:
Just to be clear, what are you renaming your file to? It needs to be renamed to "EP201_768_SDUPDATE.zip" and on an SD card formatted to FAT32. Also, if you're working with a .zip you downloaded from ASUS, you need to extract that zip and rename the EXTRACTED zip file and place that one on the SD.
I'd also try a different SD card if that's not doing it for you. "E: failed to mount /SD card (no such file or directory)" already sounds like it's just not liking that particular SD card right now.
You could also try to download JB from ASUS and flash that file instead of ICS. That way, you will have your fastboot option back so that you can send ICS via fastboot, re-root, and upgrade. That's what I did when I was going through this yesterday trying to reroot after I was bricked.
Once you've over come that part, on to the rooting (and keeping root). It wasn't working with the JB from the ASUS site. I was able to flash it, but I kept losing root. I had to use the dlpkgfile method from my OTA to upgrade to JB in order to keep root. If you don't have that file, you can find one somewhere here or I can provide you with mine.
Good luck!
Click to expand...
Click to collapse
I tried all of those things. I stayed up all night trying everything I could think of. Nothing. I might just have to trip and drop it off a balcony and use best buy replacement warranty. I took it back several days ago cause of glitches. They wouldn't do anything cause they said my warranty covers breakage, not software.
redheadplantguy said:
I tried all of those things. I stayed up all night trying everything I could think of. Nothing. I might just have to trip and drop it off a balcony and use best buy replacement warranty. I took it back several days ago cause of glitches. They wouldn't do anything cause they said my warranty covers breakage, not software.
Click to expand...
Click to collapse
If you still can get to recovery mode, can you take about all your sd card(s), do a factory reset (data wipe) and see if boot up?
buhohitr said:
If you still can get to recovery mode, can you take about all your sd card(s), do a factory reset (data wipe) and see if boot up?
Click to expand...
Click to collapse
Thanks for those that tried to help, but that tablet overheated and melted down. burned my fingers. best buy exchanged it under factory defect. New one is rooted JB.
this thread can be closed now, thanks.
That would qualify as a 'terminal failure', indeed. Did you help it a bit? ; )
(This is just me having a sick mind, and a background in (bio)chemistry -- all (bio)chem guys/girls I know, including myself, are pyromaniacs -- when reading your last post, I cannot help but see large, now-empty bottles of easily combustible liquids and you swaying back and forth while on your knees, hands high up in the air, chanting "burn, m*****f*****, BURN!" Imagine the surprised faces at BB -- "overheated... oh, I see..." <takes over small, charred metal pancake>)
Haha, no.
Sent from my SGH-T679 using Xparent ICS Blue Tapatalk 2
redheadplantguy said:
Thanks for those that tried to help, but that tablet overheated and melted down. burned my fingers. best buy exchanged it under factory defect. New one is rooted JB.
this thread can be closed now, thanks.
Click to expand...
Click to collapse
Ya, they do that when you take a torch to them
Related
trying to install rom from sd card (phone has been wiped after trying to install leedroid 3.0.3) and I get the following messages when in recovery;
unable to moun't sd card
E: Can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)
(no such file or directory)
E: Can't mount /sdcard
HELP!!!!
Does this when I try installing from SD, formatting SD, all sorts. I cna access the card though from the computer when I select mount USB storage.
any ideas? I'm phoneless at the moment. eek. Thanks
westleydan said:
trying to install rom from sd card (phone has been wiped after trying to install leedroid 3.0.3) and I get the following messages when in recovery;
unable to moun't sd card
E: Can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)
(no such file or directory)
E: Can't mount /sdcard
HELP!!!!
Does this when I try installing from SD, formatting SD, all sorts. I cna access the card though from the computer when I select mount USB storage.
any ideas? I'm phoneless at the moment. eek. Thanks
Click to expand...
Click to collapse
This sort of happened to me before. try downloading and installing the file attached. It should do the trick. N.B- You need to have root access.
ok thanks. I have root access (i think, fairly new to all this, apologies).
How do I run the file??
Thanks.
sorry to be a pain
westleydan said:
How do I run the file?? Thanks. sorry to be a pain
Click to expand...
Click to collapse
Boot your phone (make sure the file is on your phone), then simply select the file and follow the onscreen instructions. After that, select it's icon in the menu and choose to allow it to automatically operate when USB is connected. Then just allow root access and you're good to go. Try your rom flashing again and it should be successful.
hey
thanks for your help, but I currently have no ROM / OS installed on the phone, so can only boot into recovery / fastboot etc.
not into android os.
westleydan said:
hey
thanks for your help, but I currently have no ROM / OS installed on the phone, so can only boot into recovery / fastboot etc.
not into android os.
Click to expand...
Click to collapse
Since you can boot into recovery and access your phone from your computer, then just flash the stock windows mobile rom to your phone. I think that would work and it does make sense. If it does work then you can continue doing what you want after you have done it.
Do you mean flash it via fastboot? I'm sturuggling to get files across from my pc... sorry to be a pain...
I can access the SD card to drag files in recovery. but cant isntall from the sd on my phone.
tried flashing files direct to phone with fastboot but coundt. probably just got it wrong. gahhh.
westleydan said:
Do you mean flash it via fastboot? I'm sturuggling to get files across from my pc... sorry to be a pain...
I can access the SD card to drag files in recovery. but cant isntall from the sd on my phone.
tried flashing files direct to phone with fastboot but coundt. probably just got it wrong. gahhh.
Click to expand...
Click to collapse
Have you tried a different SD Card or a sdhc card? One of them might help.
I haven't tried another card yet no.
I need to purchase one first, hopefully will get chance this week.
Any links to best guide to make a goldcard btw?
Thanks.
westleydan said:
I haven't tried another card yet no.
I need to purchase one first, hopefully will get chance this week.
Any links to best guide to make a goldcard btw?
Thanks.
Click to expand...
Click to collapse
Go here and read my first post [OP]: http://forum.xda-developers.com/showthread.php?t=1052063. Hope this helps.
Have CWM v3.1.0.1 installed and can boot just fine but when I install the new CWM, I get "E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
This happens with any zip file I'm installing. I get "E:Can't open /sdcard/*.zip (bad)"
I thought maybe I had a bad download so I downloaded and re-downloaded the zip files. Nothing.
I've Rooted using One Click Universal root v4 and during the root process installed CWM 3.1.0.1. No problems. All worked fine.
Was thinking my sdcard might be the problem so I installed on my PC brk's Universal root toolkit v7.1 and tried to use NVflash on Revolver and Prime 2.0.3. Well it just sits there for an hour hung about 30% into it.
Will try brk's Universal root toolkit and attempt recovery install.
Any suggestions/ideas would be greatly appreciated.
Maybe try to format your micro sd card again using the pc.
sdformatter is a good program.
Well I fired up, brk's Universal root toolkit v7.1 and ran the restore recovery and then installed Prime v2.0.1 with success. Installed using NVflash option.
After going through reboots to ensure Prime installed (which looks really good), I decided to try to install the Prime v2.0.3 patch (zip file) using the updated CWM 3.2.0.1.
Well, that didn't work. Got the same error, "E:Can't open /sdcard/*.zip (bad)".
Can't figure this out. Never had this problem before.
Maybe the next course of action is the formatting of the sdcard.
Doesn't the tablet format the card? Or do you recommend using this, sdformatter?
I usually use the PC.
Keep in mind it only work with FAT32 on the micro sd
and you're using the micro sd on the tablet itself correct?
Yes.
Sent from my Transformer TF101 using xda premium
Have exactly same problem, it seem like problem somewhere in CWM 3.1.0.1
In details:
Had rooted 8.5.6.13 with Brk.root.toolkit.v7.1 (that one includes CWM 3.1.0.1),
Put cwm_recovery-3201_roach-tf101-r1.zip in root of MicroSD.
Loaded in CWM , try to update to 3.2.01 (selected install zip from SDcard) -> got "E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Downloaded CWM-ready images from
http://forum.xda-developers.com/showthread.php?t=1334673
and
http://forum.xda-developers.com/showthread.php?t=1341533
Both installed OK (yes, with same CWM 3.1.0.1 !),
Another attempt to update CWM (now on 8.5.6.19)->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Checked root->root disappeared (do not know why), rooted 8.5.6.19 again with Brk.root.toolkit.v7.1,
Another attempt to update CWM->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Got another 512MB MicroSD, formatted in FAT 32 (on PC ), put cwm_recovery-3201_roach-tf101-r1.zip in root of MicroSD.
Another attempt to update CWM->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Formatted it in FAT (on PC ), put cwm_recovery-3201_roach-tf101-r1.zip in root of MicroSD.
Another attempt to update CWM->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Looks like I am stuck on CWM 3.1.0.1 with no chances to update in future, any suggestions would be appreciated.
P.S. MD5 of cwm_recovery-3201_roach-tf101-r1.zip is correct. Transformer of WW version.
Lechaxda-developers said:
Have exactly same problem, it seem like problem somewhere in CWM 3.1.0.1
In details:
Had rooted 8.5.6.13 with Brk.root.toolkit.v7.1 (that one includes CWM 3.1.0.1),
Put cwm_recovery-3201_roach-tf101-r1.zip in root of MicroSD.
Loaded in CWM , try to update to 3.2.01 (selected install zip from SDcard) -> got "E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Downloaded CWM-ready images from
http://forum.xda-developers.com/showthread.php?t=1334673
and
http://forum.xda-developers.com/showthread.php?t=1341533
Both installed OK (yes, with same CWM 3.1.0.1 !),
Another attempt to update CWM (now on 8.5.6.19)->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Checked root->root disappeared (do not know why), rooted 8.5.6.19 again with Brk.root.toolkit.v7.1,
Another attempt to update CWM->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Got another 512MB MicroSD, formatted in FAT 32 (on PC ), put cwm_recovery-3201_roach-tf101-r1.zip in root of MicroSD.
Another attempt to update CWM->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Formatted it in FAT (on PC ), put cwm_recovery-3201_roach-tf101-r1.zip in root of MicroSD.
Another attempt to update CWM->"E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)"
Looks like I am stuck on CWM 3.1.0.1 with no chances to update in future, any suggestions would be appreciated.
P.S. MD5 of cwm_recovery-3201_roach-tf101-r1.zip is correct. Transformer of WW version.
Click to expand...
Click to collapse
Hi - Here's some things to check:
1) A note from the original post(s) on cwm-3101/3202 in the dev forum:
Code:
Originally Posted by Warboy
does 3.2.0.1 skip internal storage too?
Also I would really Install Updates from Internal Storage, Install Updates from SdCard that would be awesome if you 2 guys could do that lol
It does skip internal media unless you put a file called eraseData into the clockworkmod folder on your MicroSD card.
So make sure you've got no file on the MicroSD called eraseData.
2) Have you check the md5sum? Here are the details:
Download
3.2.0.1 roach-tf101-r1
MD5: b28dca7b9dce48627e5e849586f633d1
If you don't know how to do that, then you could download an md5sum verify program for windows if you use it from somewhere, and check the zip file against the md5sum below it, or if you use linux, then just do "$ md5sum 3.2.0.1* and compare it to the md5sum above.
3) I'm not recalling the syntax of cwm errors, but it looks like "E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)" is hopefully where "E" means error, and /sdcard really means /Removable/MicroSD/, which would at least stick you in the right area.
4) Make sure you can unzip this file using 'unzip'/7zip/windows unzip/' or whatever on your PC before you start all this. If you can't unzip it there, then you can't unzip it on the TF. You'll get an error if it won't unzip.
SO: Just make sure you have 1 & 2 & 4 right first and then just for the heck of it rename the long filename to something smaller like cwm3201.zip and put it on a) the microsd and b) /sdcard, and try it again using that name.
Good luck -
Many thanks for your help,
I have stepped again through points above:
1.I did not found any eraseData file neither on MicroSD nor on Internal memory(/,/data,/system) (checked this with RootExplorer), actually I do not completely understood where to search: clockworkmod folder does not exists on those locations.
2.As i wrote, I have checked MD 5, in any case redownloaded file, checked MD5 again: to be precise- MD5 for zip: MD5 (cwm_recovery-3201_roach-tf101-r1.zip) = f71f9b672396be5e494b3d355ed21c9a
MD5 for content (i.e extracted zip): MD5 (cwm_recovery-3201_roach-tf101-r1) = b28dca7b9dce48627e5e849586f633d1
3.” E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)" is exact error message, as far as I can see, /sdcard here is really /Removable/MicroSD/ (I can see folders structure and update file self than I have to select it from CWM), have no idea about E, did not found any documentation on CWM error codes.
4.I can unzip just normally (see 2.)
5. Put cwm_recovery-3201_roach-tf101-r1.zip in /sdcard (i.e root of visible internal memory) seems to have no effect: CWM does not see files on /sdcard (or I did not found a way to make CWM search there).
6.Renamed cwm_recovery-3201_roach-tf101-r1.zip to cwmupdate.zip, put into root of MicroSD. Result you can see on screenshot below.
Has anybody other ideas ?
Lechaxda-developers said:
Many thanks for your help,
I have stepped again through points above:
3.” E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)" is exact error message, as far as I can see, /sdcard here is really /Removable/MicroSD/ (I can see folders structure and update file self than I have to select it from CWM), have no idea about E, did not found any documentation on CWM error codes.
4.I can unzip just normally (see 2.)
5. Put cwm_recovery-3201_roach-tf101-r1.zip in /sdcard (i.e root of visible internal memory) seems to have no effect: CWM does not see files on /sdcard (or I did not found a way to make CWM search there).
6.Renamed cwm_recovery-3201_roach-tf101-r1.zip to cwmupdate.zip, put into root of MicroSD. Result you can see on screenshot below.
Has anybody other ideas ?
Click to expand...
Click to collapse
Are you choosing "apply update from sdcard" or "install zip from sdcard"?
Are you choosing "apply update from sdcard" or "install zip from sdcard"?
Click to expand...
Click to collapse
install zip from sdcard,
Should i rename cwm_recovery-3201_roach-tf101-r1.zip tj update.zip and try another option?
Lechaxda-developers said:
install zip from sdcard,
Should i rename cwm_recovery-3201_roach-tf101-r1.zip tj update.zip and try another option?
Click to expand...
Click to collapse
No "install zip from sdcard is correct" shouldn't have to rename the zip at all.
CWM only read from micro sdcard not internal sdcard that's why you can't see it there.
Have you tried Gnufabio RecoveryInstaller? It install the newer CWM IIRC.
http://forum.xda-developers.com/showthread.php?t=1346180
I think the idea above this is a good one for a first try at this point.
Also: I reread the original post and see that obviously cwm finds the file, attempts to or succeeds in opening it, and then shouts "bad". I see you tried unzipping from the PC, and all the rest.
I wonder if this could somehow be a permissions error and if somehow there are no meaningful permissions either on the sdcard mount (just run $mount in a terminal emulator or adb to see what they are). I'm guessing that well, it's a zip file, so no matter what else cwm must do, it has to unzip the thing and extract the data to someplace. I'd have to go stare at the github code to figure out where that place is, but the target "could" be mounted r/o. It seems like the target can't be the sdcard or you're never be able to write the zip there in the first place.
If there's a github URL in the solarnz/roach post I'll see what it extracts it to and get back to this.
Lechaxda-developers said:
Many thanks for your help,
I have stepped again through points above:
1.I did not found any eraseData file neither on MicroSD nor on Internal memory(/,/data,/system) (checked this with RootExplorer), actually I do not completely understood where to search: clockworkmod folder does not exists on those locations.
2.As i wrote, I have checked MD 5, in any case redownloaded file, checked MD5 again: to be precise- MD5 for zip: MD5 (cwm_recovery-3201_roach-tf101-r1.zip) = f71f9b672396be5e494b3d355ed21c9a
MD5 for content (i.e extracted zip): MD5 (cwm_recovery-3201_roach-tf101-r1) = b28dca7b9dce48627e5e849586f633d1
3.” E:Can't open /sdcard/cwm_recovery-3201_roach-tf101-r1.zip (bad)" is exact error message, as far as I can see, /sdcard here is really /Removable/MicroSD/ (I can see folders structure and update file self than I have to select it from CWM), have no idea about E, did not found any documentation on CWM error codes.
4.I can unzip just normally (see 2.)
5. Put cwm_recovery-3201_roach-tf101-r1.zip in /sdcard (i.e root of visible internal memory) seems to have no effect: CWM does not see files on /sdcard (or I did not found a way to make CWM search there).
6.Renamed cwm_recovery-3201_roach-tf101-r1.zip to cwmupdate.zip, put into root of MicroSD. Result you can see on screenshot below.
Has anybody other ideas ?
Click to expand...
Click to collapse
You have to copy the .zip file to /removeable/micro sd card/ and not to /sd card. For now its not possible to flash something from the internal sd card.
If you allready did this you can try to "toggle signature verification" in Recovery i had to do this when i flashed the su on my sensation xe. you have to do this till it says disabled and then flash the .zip
Hope it helps
Sent from my Revolver powered AsusTransformer using Tapatalk
hachamacha said:
I think the idea above this is a good one for a first try at this point.
Also: I reread the original post and see that obviously cwm finds the file, attempts to or succeeds in opening it, and then shouts "bad". I see you tried unzipping from the PC, and all the rest.
I wonder if this could somehow be a permissions error and if somehow there are no meaningful permissions either on the sdcard mount (just run $mount in a terminal emulator or adb to see what they are). I'm guessing that well, it's a zip file, so no matter what else cwm must do, it has to unzip the thing and extract the data to someplace. I'd have to go stare at the github code to figure out where that place is, but the target "could" be mounted r/o. It seems like the target can't be the sdcard or you're never be able to write the zip there in the first place.
If there's a github URL in the solarnz/roach post I'll see what it extracts it to and get back to this.
Click to expand...
Click to collapse
OK: I grabbed both git's (solarnz and roach) and there is only one spot the error could be coming from originally which is in top-level install.c and is basically just a call to mcOpenZipArchive in Zip.c. If returns an error, then that's apparently the error you got (has E: up front, (bad) in rear, and your stuff in between).
mcOpenZipArchive looks at ~4 criteria to open, and one thing that seems kind of important is that I don't see any changes in this Zip.c file in either git repo so if it fails on solarnz, it "ought" to fail on roach.
What Zip.c checks are these things:
1) Is the file there and openable at all? (based on a few things first on /MicroSD (wheverever you pointed it), or on /sdcard if those other oddball things were setup but you said they weren't.
2) Can it map the memory for this file in shared mem?
3) Did the map return an endpoint(amount of mem) that would hold the entire file?
4) Can it parse the file into mapped mem?
I don't have time to go through more code but if any of those things cause some alarm to go off in your head, then good and there's hope of figuring it out, and if not, well, maybe we can get roach to look it over as if he hasn't got enough going on
The other possible obvious thing might just be that your cwm is corrupt and useless. I've had this happen to me, but have used nvflash to blow another img of it onto the tf. I don't know if you've got that capability or not. Like all errors, it could be a million things, and by the time I finish this paragraph, I hope you've solved it.
Thanks again for advices, solved in 1 minute with
Gnufabio RecoveryInstaller
http://forum.xda-developers.com/show....php?t=1346180
Bad point here I didn’t figured out what was the reason of the problem, I would agree with hachamacha:
The other possible obvious thing might just be that your cwm is corrupt and useless.
Click to expand...
Click to collapse
With only one exception: it was “partly” corrupted (see in my first post, with same CWM I have installed 2 zip- images without any problem), only with conjunction with cwm_recovery-3201_roach-tf101-r1.zip problem appears.
In any case: for guys who having problems "updating CWM with CWM" - just use Gnufabio RecoveryInstaller
hey guys and girls, hopefully you can help me out.
I'm using a t-mobile galaxy S, trying to flash a new rom after I rooted it. I followed the instructions, and I have CWM able to load. when I got into select the install from the SD card, I'm able to select the file (trying bionix frost), it tries to load it, but then comes back telling me 'Can't mount /sdcard' and any subsquent attempts to even browse for the install zip give me the same error. I can boot the phone into the rooted stock image, access anything on the SD card there fine, copy files to it, etc, but CWM will not install the ROM's or keep the /sdcard mounted.
anyone here run into this issue? I'm using CwM Voodoo lagfix Recovery 3.0.2.8x
It's been awhile since I flashed that ROM...
Did you change the mounts manually? Does the OP say to change mounts? Back then we had to change the mounts ourselves in CWM to UMMU.
I'm at work and just sending a quick reply..check the OP to see what your mounts should be
to clarify a bit, this isn't just on a specific ROM, this is for ANY rom I try, after I access any ZIP file through CWM, it unmounts the SD Card and won't let me get back to it unless I reboot, and the cycle repeats.
Ok. Sorry I can't help you with that. I'm still kinda new.
I'm sure you'll get the help you need soon especially with your last reply.
Good luck and sorry I couldn't be of help.
I'm backing up and will format my SD card to see if this is the problem, saw this fixed a couple of errors like this for other peeps.
So since I couldn't get CWM to install the rom, I used ODIN and flashed to gingerbread. that's installed and working (had it fail the first time, but the 2nd installed and was up inside 10 minutes)
I've been having problems with ICS and USB mass storage support, or lack of. Is there anything I can place on my micro SD. then copy it to the internal SD and boot from there?
Just grabbing at straws here!
Thansk
TF101 B50 by the way.
honkinn said:
I've been having problems with ICS and USB mass storage support, or lack of. Is there anything I can place on my micro SD. then copy it to the internal SD and boot from there?
Just grabbing at straws here!
Thansk
TF101 B50 by the way.
Click to expand...
Click to collapse
If you're still able to boot into the OS and is able to R/W files than yes, put the files on the micro sd, and using a file manager transfer it to internal sd.
Thanks for the help, but as a neebie, I need a suggestion on WHAT file to place on the internal SD that will I can boot from.
I still get the robot with the red triangle when I try to boot into recovery. I'm assuming that is because there wasn't a bootable file on the internal SD.
Does that make sense?
honkinn said:
Thanks for the help, but as a neebie, I need a suggestion on WHAT file to place on the internal SD that will I can boot from.
I still get the robot with the red triangle when I try to boot into recovery. I'm assuming that is because there wasn't a bootable file on the internal SD.
Does that make sense?
Click to expand...
Click to collapse
Oh I see you're on stock recovery, is the ROM stock also?
Only thing is download the latest firmware from Asus, extract the zip from within, renamed it EP101_SDUPDATE.zip and put it on the micro sd card. Boot into stock recovery and see if it will flash, maybe that will help get USB working again.
Thanks for the suggestion. I did what you told me and still nothing. When I try to boot into recovery, I still get the dead robot with the red triangle, then it boots stock.
IS there a particular folder on the SD or the Micro Sd I need to put the EP101_SDUPDATE.zip file into?
Is there a specific folder on the Intenal SD that the system boots from, that I could replace the update zip with a before ICS version?
Are these dumb questions?
Thanks in advance for taking the time to help me.
Forgot to mentioned, did you extract the zip from within the file you download?
I did extract the zip and placed it on the micro AND the internal SD in the Android folder.
IS there something else I should be doing?
This is driving me nuts.
Try it in the root of the sd card should automatically detect it there
Going on 2 weeks now
Is anyone else stuck in the situation I am? I cannot re-gain Mass Storage, SD support. When I try to boot into recovery, I get the Robot with the red triangle. The only way I can see my internal SD is through the stock file manager that is on the tablet. I don't know if I can move an appropriate file into a certain folder to get this thing to boot up to where I can reflash a ROM.
What is with this POS? I no longer have CWM and root after the OTA update. I e-mailes ASUS and they gave me the " pull the micro card, then do a wipe and re boot" Which did nothing but waste time. as you can probably tell, I am getting tired of dead ends on this Tf101 B50. does anyone have any idea what could have went wrong with the OTA update? Why did I loose the SD? and What can I do to fix/revert back to an earlier state.
self admitted noobie here...Feel free to kick the **** out of me!
Thanks for your help.
With a B50, see if you can get NVFlash working.
Download the NVFLash package
http://forum.xda-developers.com/showpost.php?p=23222380&postcount=414
Get an NVFLash compatible ROM here
http://forum.xda-developers.com/showthread.php?t=1524302&highlight=nvflash+rom
honkinn said:
Is anyone else stuck in the situation I am? I cannot re-gain Mass Storage, SD support. When I try to boot into recovery, I get the Robot with the red triangle. The only way I can see my internal SD is through the stock file manager that is on the tablet. I don't know if I can move an appropriate file into a certain folder to get this thing to boot up to where I can reflash a ROM.
What is with this POS? I no longer have CWM and root after the OTA update. I e-mailes ASUS and they gave me the " pull the micro card, then do a wipe and re boot" Which did nothing but waste time. as you can probably tell, I am getting tired of dead ends on this Tf101 B50. does anyone have any idea what could have went wrong with the OTA update? Why did I loose the SD? and What can I do to fix/revert back to an earlier state.
self admitted noobie here...Feel free to kick the **** out of me!
Thanks for your help.
Click to expand...
Click to collapse
Sounds like your OTA update was fudged so you need to reflash the ROM. I thought people with root and CWM can't do OTA updates?
Does adb or apx mode work? If apx mode works, then you can NVFlash so it shouldn't be a problem.
If ADB works, you can gain root with vipermod so you can install CWM.
I used to have root access. But, My last flash stuck in boot. Had to Nv flash it back to stock. Then the OTA hit, I had no more root or NVflash. So that is where I am. I hope there is something I can do to fix this.
Thanks for the help
OK lets try this method.
The firmware you download, don't rename it.
On the root of your sd card made a folder name ASUS
inside that make a folder name Update
extract the zip file from inside the download firmware and put it in the Update folder.
Just cold boot the TF and see if you get a notification of update avaiable on the status bar.
Outside of that not sure anything can be done except RMA
Hi all.
I've been searching the net for hours for a solution to this issue, to no avail.
I have an Asus Slider SL101 that I wanted to upgrade to KatKiss so here's what I've done...
- Root successfully (1-click transformer root 1.1 from here: https://forum.xda-developers.com/showthread.php?t=1689193)
- Installed CWM Recovery (6.0.1.3) successfully (also using above)
- put all the relevant zips (katkiss, gapps, slider comp pack) on the sd card ready for flash
- booted into recovery...
Next I went to wipe data/factory reset... but it froze so I did a hard boot and tried again: same thing.
So I went to install the rom zip from sdcard and I get error message 'can't mount /sdcard/'
Also getting 'error mounting /data' and 'unknown volume for path [/sdcard/].
I can't get back to my original Android settings at all, I'm assuming it's all gone or something. Maybe the reset did work.
The big issue is I can't access the damn zip files on the sd card to install a rom.
I have these ADB tools (with adb and all these random executables and various files scattered about) but if I can't start Android then I can't use them can I?
It's a bit of a mess really. I'm thinking if I can just get the slider to mount the sd card then I can install the rom and I should be back in.
I'm not sure how to go back to stock recovery (whatever that means) so if you advise that I should 'flash' then I'm afraid I'm going to need some clear instruction.
Stupidly, I forgot to do a backup, which is probably half the reason I'm here, although that still doesn't account for the sdcard error...
Anyway, please help a moron out?
sliderfan said:
Hi all.
I've been searching the net for hours for a solution to this issue, to no avail.
I have an Asus Slider SL101 that I wanted to upgrade to KatKiss so here's what I've done...
- Root successfully (1-click transformer root 1.1 from here: https://forum.xda-developers.com/showthread.php?t=1689193)
- Installed CWM Recovery (6.0.1.3) successfully (also using above)
- put all the relevant zips (katkiss, gapps, slider comp pack) on the sd card ready for flash
- booted into recovery...
Next I went to wipe data/factory reset... but it froze so I did a hard boot and tried again: same thing.
So I went to install the rom zip from sdcard and I get error message 'can't mount /sdcard/'
Also getting 'error mounting /data' and 'unknown volume for path [/sdcard/].
I can't get back to my original Android settings at all, I'm assuming it's all gone or something. Maybe the reset did work.
The big issue is I can't access the damn zip files on the sd card to install a rom.
I have these ADB tools (with adb and all these random executables and various files scattered about) but if I can't start Android then I can't use them can I?
It's a bit of a mess really. I'm thinking if I can just get the slider to mount the sd card then I can install the rom and I should be back in.
I'm not sure how to go back to stock recovery (whatever that means) so if you advise that I should 'flash' then I'm afraid I'm going to need some clear instruction.
Stupidly, I forgot to do a backup, which is probably half the reason I'm here, although that still doesn't account for the sdcard error...
Anyway, please help a moron out?
Click to expand...
Click to collapse
))
Ive got the same problem. CWM cant mount the sd card. Ive been searching for days, but all the links in any solution i did find are outdated. I did read somewhere that it means that the CWM version isnt compitable with the Sl101. I can't find any other/older versions then the Manager i downloaded from Playstore. I want to flash the Twrp Recovery and then the kisskat ROM, compability pack.. Gapps
.etc but i cant seem to get any of that done if CWM can't mount the damn sdcard. (Sorry i got a bit frustrated over this). Ive never rooted anything before so im new to this. Did anyone find a solution for this? Or has an link to some other version of CWM that is compitable to mount the sdcard? Thank you very much in advance)
Probably not what you wanna hear, but I didn't find a solution and had to throw my beloved slider away!