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
Related
I loaded the recent update on 12/24 and have not been able to use my tablet since then.. When turned on, it goes thru the ViewSonic screen and the gtablet screen, then just goes to a blank black screen.. It was stock before I loaded the last update..
I have tried to reboot using the power button and vol+
- if there is no microSD card in I get the following message
E: can't mount dev/block/mmcblk2
(no such file or directory)
E: can't mount SDCard2: recovery/command
Formating MISC:...
Rebooting...
- if there is a microSD card with the new download and recovery/command I get the following message
Formatting MISC:...
Rebooting...
Either way, I get a blank screen and no way to change things or update.
Is there anything I can do to get it working again?
This was all stock? Sounds like the flash update failed badly.
Suggestion -- reflash using one of the stock ROM's we've grabbed. Post info: http://forum.xda-developers.com/showthread.php?t=842000. Quick instructions:
- Have a microSD card ready.
- Download the 3338 ZIP file, save it to the root of your microSD card and then rename it to "update.zip".
- Grab the homebrew 1.00 ZIP and extract just the /recovery/command file to the same folder in your microSD.
So, if your microSD is your F drive, you should have the following:
F:\update.zip
F:\recovery\command
- "command" is a text file. Open it in notepad and edit "SDCARD" to "SDCARD2". Make sure notepad doesn't add a .TXT extension when you save it.
Insert the microSD back into your device and reboot into recovery. If you're lucky your device will reflash and reboot.
If this all runs and you still get the same black screen on reboot, my next suggestion is to try one of the older firmware ZIPs and flash as I mentioned above.
edit due to Roebeet answering while I was
It was all stock, with a few added apps...
I tried to reflash the file as noted, with no success... same with the 12/19 -3316 update... it goes thru the recovery reboot, and then to the black screen...
A question on the recovery file.. my computer will not allow a "\" as part of a name... I have been trying this was a recovery file, with just the command file in it... if I need to do something different, let me know..
Sandy A. said:
It was all stock, with a few added apps...
I tried to reflash the file as noted, with no success... same with the 12/19 -3316 update... it goes thru the recovery reboot, and then to the black screen...
A question on the recovery file.. my computer will not allow a "\" as part of a name... I have been trying this was a recovery file, with just the command file in it... if I need to do something different, let me know..
Click to expand...
Click to collapse
The instructions posted by roebeet should work. Make sure your microsd card is formatted as FAT32.
1. The file update.zip should be in the microsd card's root directory.
2. The folder recovery should be in the microsd card's root directory.
3. Inside the recovery folder there should be a file named command.
4. And inside the command file you should have the following line:
--update_package=SDCARD2:/update.zip
Still don't have it working.. I have tried all of the updates, and still have a black/blank screen once it goes thru the ViewSonic and gtablet screens..
I have noticed that when I take the sd card out, and check on my computer, that the recovery folder is empty, but I know it had the command file in it before..
any other suggestions??
I believe it's fixable but at this point you may be happier returning it for a new one. It sounds like your update download was corrupted and borked your install.
Not exactly what I wanted to hear.. but..
I called customer support, and got thru today (tried last night and was put on hold then the call dropped)... I was told I wasn't the only person who had this problem with the last update... they are going to send me instructions on how to send it in for repair...
The only I can tell you to try is the same thing Roebeet said earlier. If you have never installed clockworkmod recovery then go here and download the 3389 update
http://forum.xda-developers.com/showthread.php?t=879534
Rename the file to "update.zip" ....make sure it doesn't get named update.zip.zip
Then go here and download cwm 0.8.zip
http://forum.xda-developers.com/showthread.php?t=865017
Unzip the cwm0.8.zip and you should have this
update.zip
a folder named "recovery" with a file named "command"
update.zip.......DELETE THIS FILE
recovery/command
the command file should have this line in it
--update_package=SDCARD2:/update.zip
If you have a micro sd card then place the 3389 update file that you renamed to "update.zip" on the root of the micro sd card. Not in an folders
Now place the recovery folder on the root of the micro sd card. Make sure the "command" file is in the recovery folder.
When you open your micro sd card you should see this
recovery (folder)...."command" file in this folder
update.zip
Insert the microsd card into the GTab. Make sure tablet is off and then Press power and vol+. hold Vol+ until you see "recovery key pressed". It should install the 3389 firmware and reboot.
If something happens during the install or if your download is corrupted again always check the recovery folder for the command file because it will be deleted on install.
Just a thought, are you sure it has a good charge on the battery? When I first got my gtab I had a similar issue getting it to boot, until I realized the battery was drained
MZ601 Xoom on 3.1HC wifi + 3G rooted using Universal Xoom Root. Now wish to be able to use USB Host mode. Have followed the instructions in [ROM] Team Tiamat Xoom Rom 2.2.1 - Moray [18/9/11] including performing a factory reset (Wipe data/factory reset) from within recovery, and then selected "Install zip from sdcard" and selected the Tiamat zip file. The system reports that it is opening the file but then immediately aborts with the above message.
Assuming that the download was not successful I then downloaded again, went through the whole procedure again but came up with the same error. Hmmm this is a bit of a mystery.
So, is 2.2.0 a prerequisite of 2.2.1 and should I have tried to flash that first? Or could there be something else that this old fart is missing? I guess it must be the latter judging by all the success stories on here. Can somebody please help?
Irobbie.
irobbie said:
MZ601 Xoom on 3.1HC wifi + 3G rooted using Universal Xoom Root. Now wish to be able to use USB Host mode. Have followed the instructions in [ROM] Team Tiamat Xoom Rom 2.2.1 - Moray [18/9/11] including performing a factory reset (Wipe data/factory reset) from within recovery, and then selected "Install zip from sdcard" and selected the Tiamat zip file. The system reports that it is opening the file but then immediately aborts with the above message.
Assuming that the download was not successful I then downloaded again, went through the whole procedure again but came up with the same error. Hmmm this is a bit of a mystery.
So, is 2.2.0 a prerequisite of 2.2.1 and should I have tried to flash that first? Or could there be something else that this old fart is missing? I guess it must be the latter judging by all the success stories on here. Can somebody please help?
Irobbie.
Click to expand...
Click to collapse
So, just to clarify, you are rooted and attempting ti install the Moray Rom, and your Xoom is giving you an error that it can't access the sdcard to flash the Moray file.
My first question is, what version of CWM recovery are you using and is your Moray file on your external micro sdcard which is inserted in your Xoom?
It sounds like you are trying to flash from the Xoom's internal "sdcard" which doesn't work (unless you have the Rogue recovery installed).
Thanks for your reply.
Regarding the recovery mode version, in recovery mode my Xoom tells me "Clockwork Recovery V3.2.0.0 (solarnz-R4c-100611-1150).
Using "My Files", I have confirmed that the Zip file doesn't exist on the "Internal" storage, but does exist on the external SD card. This is where the Universal Xoom Root zip file sits and where it was installed from. The root zip file installed smoothly, and as far as I know I followed the exact same steps in trying to install the new rom. So I remain confused.
Once again thanks for your reply and any further help will be appreciated.
Irobbie
irobbie said:
Thanks for your reply.
Regarding the recovery mode version, in recovery mode my Xoom tells me "Clockwork Recovery V3.2.0.0 (solarnz-R4c-100611-1150).
Using "My Files", I have confirmed that the Zip file doesn't exist on the "Internal" storage, but does exist on the external SD card. This is where the Universal Xoom Root zip file sits and where it was installed from. The root zip file installed smoothly, and as far as I know I followed the exact same steps in trying to install the new rom. So I remain confused.
Once again thanks for your reply and any further help will be appreciated.
Irobbie
Click to expand...
Click to collapse
Ok, Sounds like you should be set regarding recovery. I'm pretty sure that you should be able to go right to Moray 2.2.1.
First, confirm that your sdcard is good and working properly by inserting it into a phone or a card reader. It could be as simple as a bad card. Also, you could redownload the file, but I think it's most likely your sdcard.
Thanks for getting back to me.
I replaced the SD card with another from my mp3 player and checked it out by loading up a song and playing it. No problems. So then I moved the zip file for the rom (which I had previously re-downloaded) over to the root of the sd card from my PC and proceeded through the steps again. Failed again. The message sequence reads:
--Installing: /sdcard/Tiamat-Xoom-rom-2.2.1-Moray.zip
Finding update package... (So its gone looking)
Opening update package... (And it is found?)
E:Can't open /sdcard/Tiamat-Xoom-Rom-2.2.1.Moray.zip
(bad)
Installation aborted
Hmmm. Just to check that the sd card is still viable, after reboot went back to "files", sdcard, music and selected a song and it played as normal. Also checked that the Tiamat rom zip file is on the card and yep, it is. So tomorrow morning I will download the zip file once again and retry. If you can think of anything else it will be much appreciated.
Irobbie.
If you can check to make sure the downloaded file is the right size that will be great. also make sure that you don't add another.zip file extension on the end, somehow. Some pcs are set up to hide file extensions and that's been a problem a few have encountered.
The mystery deepens! Well, for me at least.
Re: zip file extra extension, have show extensions switched on, and there is no extra extension.
So on to file size, it looks the same to me on each download so I went a bit further. I noticed the link to the file has a MD5sum check noted. So I downloaded an open source file "Sigma Informatics Checksum calculator", pointed it to the rom zip file and ran the check, and then cut and pasted the original number from the thread and got the calculator to do a check. Bingo - exactly the same!
So then copied the file from the Xoom back to the PC, ran the same checks and got different answer!
OK, I deleted the rom zip file from the Xoom, copied another over from the PC, then recopied it back to the PC to a different location, ran the check sum, got the correct answer, so now I knew I had a correct file on the Xoom.
Next, reran the installation of the Rom - failed again with the same results and messages as before.
Then copied the Rom zip file back to the PC to another location, ran the checksum and different answer popped out again. Well, could it be that the zip file is being corrupted during the install and that is why it fails? I've never heard of that sort of thing happening before but I suppose it is possible.
Your continued support is much appreciated.
It seems like I have heard of this happening, but why? What would cause that? Can you use a different method to copy the Rom file to the sd card? Using an adapter, and inserting the card directly into the sd slot of the pc? Download right onto the card?
Thanks for the reply and suggestions again.
To make absolutely sure I eliminated everything possible; I went out and bought a new micro sd card, and card reader with a micro sd card slot. Plugged it altogether into the pc and copied over a copy of the rom zip file.
Then did a checksum check on the file on the sd card and it was fine.
So, holding breath, puff, puff, puff, started the procedure all over again.
SUCCESS! It all went as smooth as silk! Thanks for your help and suggestions. But now I am left with a concern about where the problem really was - was it in the copying of the file onto the card through the Xoom, or was it, in fact, a bad card? I don't want to discard the card because it seems to be o.k. in every other respect so I think a little play around is in order. I think in all probability you are right in questioning the process I was using before, and recommending that the file be copied directly to the sd card.
But in the meantime I'm off to explore the new rom and in particular USB hosting.
Yes! I love success!
Enjoy.
Hi!
I'm on SGS2 with Resurrection Remix v2.0 w/ Siyah v 3.2.6+ kernel.
My version of CWM is 4.0.1.5.
For some reason, I can't longer flash anything from CWM.
Whenever I reboot into CWM and choose the "choose zip from sdcard", I only get this error message: "E: Can't mount /sdcard". I don't have any external SD card on my phone, I have always used this method.
I've already tried to wipe cache without luck. If I choose "mount /sdcard", I only get "Error mounting /sdcard!" (This however, may be because it's referring to any external sdcard?)
I appreciate any answers!
RealSpZ said:
Hi!
I'm on SGS2 with Resurrection Remix v2.0 w/ Siyah v 3.2.6+ kernel.
My version of CWM is 4.0.1.5.
For some reason, I can't longer flash anything from CWM.
Whenever I reboot into CWM and choose the "choose zip from sdcard", I only get this error message: "E: Can't mount /sdcard". I don't have any external SD card on my phone, I have always used this method.
I've already tried to wipe cache without luck. If I choose "mount /sdcard", I only get "Error mounting /sdcard!" (This however, may be because it's referring to any external sdcard?)
I appreciate any answers!
Click to expand...
Click to collapse
So, when you put the .zip on your 'sdcard', are you putting it on the internal memory, or the external SD card?
And yep you're right - it's looking for an extsdcard to 'mount'.
juzz86 said:
So, when you put the .zip on your 'sdcard', are you putting it on the internal memory, or the external SD card?
And yep you're right - it's looking for an extsdcard to 'mount'.
Click to expand...
Click to collapse
I'm putting the .zip file in my /mnt/sdcard directory. Btw, when I can boot into the stock recovery, I have an option called "install zip from internal sd card". When I choose this option, I can access all my files and install the update that I want, but in CWM I can't!
RealSpZ said:
I'm putting the .zip file in my /mnt/sdcard directory. Btw, when I can boot into the stock recovery, I have an option called "install zip from internal sd card". When I choose this option, I can access all my files and install the update that I want, but in CWM I can't!
Click to expand...
Click to collapse
Have you tried sticking the .zip on an external SD, and seeing if it shows up that way just to confirm? I remember having a similar issue on the Infuse a while back now, and I had to start flashing off the internal memory.
I think a re-install of CWM fixed things up, but that was a high-Development time, and we were getting new versions every day
Try the external thing, I reckon that's the problem. Might require an update to CWM in order to restore functionality. Alternatively, you may like to look into a replacement such as 4EXT or TWRP.
I found this kernel by Chainfire, which adds root and SU, and also CWM. You can flash it through ODIN as normal, very detailed instructions in there.
I also found this article, which may shed some light on the issue for you?
I cannot believe how hard it is to find a Recovery in the GS2 section. What a nightmare!
juzz86 said:
Have you tried sticking the .zip on an external SD, and seeing if it shows up that way just to confirm? I remember having a similar issue on the Infuse a while back now, and I had to start flashing off the internal memory.
I think a re-install of CWM fixed things up, but that was a high-Development time, and we were getting new versions every day
Try the external thing, I reckon that's the problem. Might require an update to CWM in order to restore functionality. Alternatively, you may like to look into a replacement such as 4EXT or TWRP.
I found this kernel by Chainfire, which adds root and SU, and also CWM. You can flash it through ODIN as normal, very detailed instructions in there.
I also found this article, which may shed some light on the issue for you?
I cannot believe how hard it is to find a Recovery in the GS2 section. What a nightmare!
Click to expand...
Click to collapse
Hi juzz86!
Thank you for your response!
I do not have an external sd-card to try atm. I will look into the CWM alternatives if this does not work.
I found out that I had replaced my stock recovery with the CWM touch version, and this version allows me to use the "internal sd card" menu. This however, only works when shutting down my phone, and holding volume up+power+home. When using the fast option "reboot into recovery" from my phone, I still get the ordinary CWM - and I'm facing the same problem over again.
When trying to "mount /sdcard" in CWM, I get a standard "failed to mount" message
After looking into the Directory-bind app, I see that all my data is stored in my /sdcard folder, and nothing in the /sdcard/external_sd folder, so I followed the guide just for fun (since it doesn't really describe my problem), but it didn't work, and I still can't mount my /sdcard folder in CWM.
I'm going to see over the forums about the mount sdcard error in the forums, and try the kernel as suggested if nothing else works BB!
EDIT: I see that in newer versions of CWM, there should be an option for installing a zip from the internal sd card. My question is: Is it possible for me to update my version of CWM, while using the same kernel? I can't do this in ROM Manager.
Should be, yes. You'll probably need to use Fastboot or ODIN to flash it, so.e devices get zips but I'm unfamiliar with the GS2 Development.
Your best bet will be to find the CWM thread in one of the GS2 forums, and follow the instructions in there.
I wasn't aware that flashing a recovery through ROM Manager changed your kernel?
juzz86 said:
Should be, yes. You'll probably need to use Fastboot or ODIN to flash it, so.e devices get zips but I'm unfamiliar with the GS2 Development.
Your best bet will be to find the CWM thread in one of the GS2 forums, and follow the instructions in there.
I wasn't aware that flashing a recovery through ROM Manager changed your kernel?
Click to expand...
Click to collapse
It didn't. My answer was a bit messy, sorry. I understand that you can flash a new kernel through odin or CWM, and therefore get a new version of CWM bundled - like the customized versions (like the link you provided). I only want to update my version of CWM, but stay on the same kernel as before. What Rom Manager is able to do, is updating your version of CWM (the official ones).
If I'm mistaking, please let me know.
No, that's right you can update CWM by flashing a kernel, but you can also find a standalone recovery.img, sometimes a flashable zip, or you can use ROM Manager. All three of these methods won't touch your kernel
I got the oposite problem...
Hi all i am new .. but basicaly my issue is:
I'm trying to install a custom ROM on my rooted Galaxy SIII I19300.
I've placed the rom inside an external sdcard, entered Recovery mode (clockworkmod CMW-based Recovery) and clicked "install zip from sdcard" then "choose zip from sdcard", after that the console presented me with an error "E:Can't mount /sdcard/".
I've tried to select "mount /sdcard" in the mounts menu and it errors:
"Error mounting /sdcard!"
The sdcard works fine and I'm able to read/write from/to it without any issues in GSIII and in others cellphones..
The SDCARD got 2 gb and its formated in FAT32.
Any one help plz?
Format your sd card !
respected sir,
format your SD card , since cwm, twrp, and other recovery mods require mostly 'FAT32' format.
so, please take a bkp and format it to go ahead without probs!
OK. So here after having some time to sit down after work to get a full idea of what is going on.
I have 2 different ROMS with zips to flash. One is a stock 2.3.4 rooted....the other is ParanoidAndroid CM9 with everything needed to run it.
2.3.4 has caused my phone to read the SD Card as _ExternalSD as a folder.
When on the phone through Astro or through ROM Manager I can find and view the ZIP files on my memory card.
I flashed CWM via NVFlash and CWM is installed on the phone but the issue that comes up is that when I navigate to the _ExternalSD folder and open in within CWM it only has a data folder and all other folders are missing and the ZIP file that is in the root of my SD card is no where to be found.
What can I do??
Don't navigate to that folder. In CWM, your external is simply just that, your external. So when you go to "Install zip" always pick from "choose from external" or however it's worded. It isn't in your internal in that folder that's called _ExternalSD... think of that like more of a shortcut on your ineternal sd card to get to your external sd more easier in file exporers.
So once again, in CWM go to flash/install zip, and choose external SD and it should be there. _ExternalSD is just a quick shortcut for file managers to locate your external.
That isn't the issue. I chose install zip from SD Card....It brings up a list of all of my folders. I have a zip in the root of my SD and it doesn't show up. I have the other zips in a download folder....That folder will not open. None of the other folders will open. The only folder that WILL open is the folder called _ExternalSD........When I open that folder it brings up the SAME list of folders but no ZIP shows up in the root of that folder and when I open my download folder it shows a data folder in it and no files or ZIPs
Nothing???
What do you mean though the folder won't open? Do you get some sort of error or something?
When I boot into CWM and go to install from SD card and what not it brings up the folders that are in the root of my SD card.
There is a ZIP file in the root that does not show up in CWM. My other ROM is located in my download folder.
If i go to the download folder i see and select it the screen blinks and goes to the same list. The folder does not open.
If I go to my ExternalSD and the only folder that shows inside there is a data folder.
Maybe it's a corrupt or incomplete zip file. Hmm have you tried formatting your external at least? Not via your phone but format with an adapter directly to your computer.
Weird problem, but trying to help as much as I can.
Yeah it is a super weird problem. I can try to format the SD card and see what happens.
I don't see that working but I am going to give it a shot but any other ideas on what it could be i'm down to check into.
My last G2x was rooted fine cracked the screen and ended up getting another G2x and now it won't root. LOL super frustrating. I've rooted so many and this one is just being a pain lol.
So far reformatting is not working. Its not doing anything. I'm so dumbfounded as to what is going on.
Try a complete nvflash again? With clockwork 5.0.2.0?
How would I do that? I thought about trying that but I can't seem to be able to get it to reflash it.
How do I boot the phone up so the NVFlash will work. When I plug it in NVFlash cannot find the device
Alright so I think I've figured out the issue now I just need to come up with a solution.
ROM Manager says I am on 5.0.2.0 but when I boot into CWM it shows I am actually on 4.0.1.5.
So I need to flash 5.0.2.0......Issue is here tho that I cannot flash it through ROM Manager and I can't seem to get NVFlash to work in flashing 5.0.2.0.
Can anyone lend some advice on that?
Spectral8x said:
Alright so I think I've figured out the issue now I just need to come up with a solution.
ROM Manager says I am on 5.0.2.0 but when I boot into CWM it shows I am actually on 4.0.1.5.
So I need to flash 5.0.2.0......Issue is here tho that I cannot flash it through ROM Manager and I can't seem to get NVFlash to work in flashing 5.0.2.0.
Can anyone lend some advice on that?
Click to expand...
Click to collapse
Don't use ROM manager.
Sent via G2x on CM7 b135.1 w/faux 52 kernel
(Now, I know this is not in the right section or even in the device's page, but...)
Forewarning: I am NOT responsible for any damages caused by running this tool. (You ran it, not me.) Also, do NOT use on the Thrive 7 or ANY of the Excites! The Thrive 7 has an entirely different bootloader/partition layout than the 10.
Pio_masaki and I have been working hard for almost a year to get root on the ICS version of the Toshiba Thrive 10.
Last night, I was able to finally sneak past sealime.ko and have it work.
It uses the "root any ICS device" tool, with special modifications specifically for the Thrive 10.
(can't post any links, so it's on the "thrive-hackers" github page.)
Special note: While it is set up for OSX ADB, I have not been able to find any binaries.
Are you saying that we are close to a root method for Thrives running Toshiba ICS?
rohads said:
Are you saying that we are close to a root method for Thrives running Toshiba ICS?
Click to expand...
Click to collapse
Saying there is a method to root it now, yes, we got around sealime.ko. This means we can flash the HC bootloader which is unlocked, which allows custom recovery and kernels/ramdisks (boot.img) to be used.
BTW the link is https://github.com/Thrive-Hackers
congrats guys ! very awesome work !
jdsingles deodexed ROM w/ agat63's 1.3 kernel Suped up w/ CB 6.26.13
More specifically, it bypasses sealime to flash the unlocked bootloader. What we did was we MVd /dev/block/mmcblk0p6 to 0p9. It's a pure fluke Pio and I found out that it works. We found out that sealime was explicitly blocking write to 0p6, so he semi-sarcastically said to move it. I ran the mv command, whadda ya know? It worked!
'Course, getting the tool completed wasn't as simple as that...
PS: Could we get this moved to the Toshiba Thrive Development section?
Have instructions been written for the process?
worked for me
I used this tool on Jul 8 and it worked very well. I got it from thriveforums dot org. Thank you pio_masaki and AmEv.
I tried changing the recovery to the latest TWRP using "fastboot flash recovery twrp-2.4.1.0.img" while in bootloader. I was not able to, though as it kept giving me errors.
Does this bootloader not allow flashing a recovery? I noticed the rootme script uses adb commands to push the CWM recovery.
I am now running Dale's latest deodexed rooted ICS rom with the CWM recovery he included.
Other unrelated lessons learned:
If you can't mount your SD card in recovery, try a different card!
And, Dale packages his update.zip inside the downloaded zip file!
navyguy said:
I used this tool on Jul 8 and it worked very well. I got it from thriveforums dot org. Thank you pio_masaki and AmEv.
I tried changing the recovery to the latest TWRP using "fastboot flash recovery twrp-2.4.1.0.img" while in bootloader. I was not able to, though as it kept giving me errors.
Does this bootloader not allow flashing a recovery? I noticed the rootme script uses adb commands to push the CWM recovery.
I am now running Dale's latest deodexed rooted ICS rom with the CWM recovery he included.
Other unrelated lessons learned:
If you can't mount your SD card in recovery, try a different card!
And, Dale packages his update.zip inside the downloaded zip file!
Click to expand...
Click to collapse
Try fastboot flash:raw.
Is there any need to do a backup before rooting?
TubaMeister said:
Is there any need to do a backup before rooting?
Click to expand...
Click to collapse
Not explicitly, but it wouln't hurt in case your tablet got into contact with allspark.... er, the bootloader didn't flash, and you're stuck in a bootloop.
easy root and CWM recovery
walk thru
http://www.youtube.com/watch?v=MXeYJhKCgX8
adb driver
http://www.thriveforums.org/forum/t...vers-usb-adb-driver-installation-package.html
root tool
https://github.com/thrive-hackers/thrive-10-inch-ics-root,
follow this to install CWM
http://www.thriveforums.org/forum/d...0-clockworkmod-touch-recovery-v6-0-1-1-a.html
follow to install touch CWM
http://www.thriveforums.org/forum/d...0-clockworkmod-touch-recovery-v6-0-1-1-a.html
ROMs
http://www.thriveforums.org/forum/dalepl/
Uh oh
robyn402 said:
walk thru
http://www.youtube.com/watch?v=MXeYJhKCgX8
adb driver
http://www.thriveforums.org/forum/t...vers-usb-adb-driver-installation-package.html
root tool
https://github.com/thrive-hackers/thrive-10-inch-ics-root,
follow this to install CWM
http://www.thriveforums.org/forum/d...0-clockworkmod-touch-recovery-v6-0-1-1-a.html
follow to install touch CWM
http://www.thriveforums.org/forum/d...0-clockworkmod-touch-recovery-v6-0-1-1-a.html
ROMs
http://www.thriveforums.org/forum/dalepl/
Click to expand...
Click to collapse
I installed the drivers, used the root tool, the restore was successful, but now the tablet is stuck in a boot-loop mode.
The root tool was running, there was a line that said the screen would go blank, which it did, and it stayed there for several hours. When I came back to check on it, the tablet was off, so I turned it on. That's when I found the boot loop. It'll get to the home page, tell me that nova launcher has stopped, then loop back to the moving stars section of the boot screen.
Any ideas on what to do now?
DLeach4512,
if CWM is still alive, so just flash any ROM via CWM (flashing wipes all your data that exist in internal memory, so you need to make backup via CWM if you wish to save your data; and after flashing ROM you can import all data via Titanium Backup)
Kyonex said:
DLeach4512,
if CWM is still alive, so just flash any ROM via CWM (flashing wipes all your data that exist in internal memory, so you need to make backup via CWM if you wish to save your data; and after flashing ROM you can import all data via Titanium Backup)
Click to expand...
Click to collapse
You know, I feel kinda dumb because I didn't even try that!
Now i've tried it, and I see I can get into CWM.
I put a ROM on an SD card on my PC, then put that SD card into the Thrive and used CWM to install the .zip of the ROM I selected, and it won't install. It starts, then it says Installation aborted, but won't tell me why.
Any ideas where I should start unraveling this mystery?
1. check that your recovery is CWM and not stock recovery
2. check that you put on SD archive that contain folders named system and META-INF, file like boot.img, something other maybe (many ROMs archive contain "archive in archive", so you need to unpack archive from main archive and than put that internal archive on SD); after checking that all right try to flash that archive again
3. try another sdcard (full sized SDHC + formated in FAT32)
DLeach4512 said:
You know, I feel kinda dumb because I didn't even try that!
Now i've tried it, and I see I can get into CWM.
I put a ROM on an SD card on my PC, then put that SD card into the Thrive and used CWM to install the .zip of the ROM I selected, and it won't install. It starts, then it says Installation aborted, but won't tell me why.
Any ideas where I should start unraveling this mystery?
Click to expand...
Click to collapse
also make sure you open the zip and place the update.zip on your card -
From my GSIII - jd's Stock/Rooted/Deodexed 4.3
Kyonex said:
1. check that your recovery is CWM and not stock recovery
2. check that you put on SD archive that contain folders named system and META-INF, file like boot.img, something other maybe (many ROMs archive contain "archive in archive", so you need to unpack archive from main archive and than put that internal archive on SD); after checking that all right try to flash that archive again
3. try another sdcard (full sized SDHC + formated in FAT32)
Click to expand...
Click to collapse
Excellent!
1) I had to extract "update.zip" from the ROM I had downloaded.
2) I re-formatted the card I was using to FAT32 instead of FAT.
3) I was able to get the install started with no trouble after following your directions.
BIG THANK YOU FOR THAT!
I got a successful install message, and then it booted!
Thanks a million!
Problems after Mount Changes
I changed the mount as described on thriveforums.org to allow apks and data to go to the external sd rather than "shared" internal memory.
I now have the situation with less free memory available on the sd card than on internal. The CWM backups went on the physical card- a 32 G one almost full. Will look for a major mfr 64 Gig.
One or so issues with the revised mounts where the external sd card is now internal. They relate to making backups with dalepl's latest CWM 6.0.1: where to put CWM backups for now and are they being made correctly with the revised mounts?
The backup made prior to the mount change looks normal: a single, dated/numbered folder about 2.6 Gb, 6 files: boot.img, cache.ext4.tar, data.ext4.tar, nandroid.md5, recovery.img and system.ext4.tar. However, the one made after the mount change also has a dated, numbered folder of only 15.8 Mb and 7 files: .android_secure.vfat.dup, boot.img, cache.ext4.dup, data.ext4.dup, nandroid.md5, recovery.img and system.ext4.dup. There is a second folder associated with the later bu called "blobs", which is huge --2.76 Gb, 3292 folders and 6581 files. Is this an expected result and any one think it might be a valid bu?
Also, it went on to the external SD (now "internal") and total storage use is now almost 28 Gb out of 30.2. I now have the situation with less free memory available on the sd card than on internal. The stuff there looks ok, pix movies and music plus CWM bups of 5.5 G and App_Backup_Restore archived apks at 2.8 Gb. So, I copied the cwm backups folder to the real internal memory, now sdcard2. I assume this true internal memory might get wiped during a restore so, this is not a valid storage site for this? And, if I put copies on a spare card, will that really work if my downloaded apps are on the original card, eg does the CWM backup copy the external card apps?
As I note, for some reason this 'blobs' folder won't copy easily to a USB via the Thrive or Win 7 pc. It also won't copy to a Win 7 HD partition where I store my Thrive stuff. (Update: I was able to do a wireless transfer to my pc and then, from there, to a spare SD card.)
Any thoughts? Should I go back and change the mounts to default?
BTW, I find FolderMount has no real use with the changed mount on the Thrive unless someone tells me otherwise. With the Thrive mounting the external card as internal, files go to the physical card.
gberpa,
I don't understand your question - it is very long. But I know that custom recovery (CWM / TWRP) itself remounts sdcard and internal memory before wipe process so it will wipe correct memory (only internal memory). If you need to change the ROM you don't need to worry about mounting paths because after wipe mounting paths will be restored to original.
Partition layout of Toshiba Thrive 10.1" ICS
AmEv said:
Also, do NOT use on the Thrive 7 or ANY of the Excites! The Thrive 7 has an entirely different bootloader/partition layout than the 10.
Click to expand...
Click to collapse
Can you give us information on the Toshiba Thrive 10.1" ICS partition layout and their names, please?
We would like to compare it to ours Toshiba Excite Pro (AT10LE-A, tostab12BA). A Dirty Cow enabled KingoRoot has given us a temporary root.
[Q] How Root Toshiba Excite Pro AT10LE-A-108 by dexxxZ
https://forum.xda-developers.com/showthread.php?t=2583677&page=6
Sent from my takee 1 using XDA Labs