Hi guys new to this loaded the android rom onto my hd2 htc works great but when i restart it keeps coming up with failed to find rootfs on sd card. You need to unzip a rootfs zip file pls help
pls in simple instructions as i am new to this thanks guys
I had the same problem...
I was reading some posts and saw some people saying to delete the "Android" folder that is automatically created by the Android OS.
I decided that if that worked, then during boot sequence it must look in the "Android" folder for the rootfs file, I copied all the Android files from my sd card root to the "Android" folder, having the all the files in both locations (sd card root and Andoid folder). After i did that it booted fine. Deleting the folder is great if it works, but then you are not able to use a dual boot program if you must delete the folder each time because it is created again.
Anyways...it worked for me, so good luck!
Just a quick question about rooting to my internal sd cards. Just so everyone knows im using Froyo.
When i mount my phone and go to my computer i click removable disk drive H with 13.4 GB free. After clicking it 5 folders appear: Android, DCIM, external_sd, LOST.DIR, and Nook.
Now i am wondering if the internal sd is what all these folders are located on, or if there should be a folder for my internal sd. I originally assumed that it was all on the internal sd however after trying to root for the last 5 hours and failing its raised question.
after i click "reinstall packages" i then get an error:
_Install from sdcard....
Finding update package...
Opening update package...
Verifying update package...
E:failed to open/mnt/internal_sd/update.zip (No such file or directory)
now i know the "update.zip" file is the file added for the root, but according to this error it should be located to a folder name "internal_sd" however no such folder exists. Like i said before i thought the entire removable drive was supposed to be the internal memory so why would there be need for that folder and if i do need the folder do i just create it is is it a hidden file or... yeah i have no idea, help please?
Unfortunately you can't root Froyo with an update.zip (unless I missed a post). I did it this way Captivate JI6 (v2.2) Hacks (root, non-market, no start up sound)
you are right 2.2 cant be rooted by the update.zip method. Nothing can be loaded by an update zip at the moment due to changes in system
Delldorado said:
Just a quick question about rooting to my internal sd cards. Just so everyone knows im using Froyo.
When i mount my phone and go to my computer i click removable disk drive H with 13.4 GB free. After clicking it 5 folders appear: Android, DCIM, external_sd, LOST.DIR, and Nook.
Now i am wondering if the internal sd is what all these folders are located on, or if there should be a folder for my internal sd. I originally assumed that it was all on the internal sd however after trying to root for the last 5 hours and failing its raised question.
after i click "reinstall packages" i then get an error:
_Install from sdcard....
Finding update package...
Opening update package...
Verifying update package...
E:failed to open/mnt/internal_sd/update.zip (No such file or directory)
now i know the "update.zip" file is the file added for the root, but according to this error it should be located to a folder name "internal_sd" however no such folder exists. Like i said before i thought the entire removable drive was supposed to be the internal memory so why would there be need for that folder and if i do need the folder do i just create it is is it a hidden file or... yeah i have no idea, help please?
Click to expand...
Click to collapse
If you look closely at the messages it is giving you. It has found the update, opened it and then tried to verify it which is where it fails. The reason being that Froyo requires digitally signed updates. The root method we used for 2.1 uses an unsigned update file.
I am curious about the LOST_DIR folder. I have em too. Also note that the external SD card is no longer under /sd but /external_sd.
hmm alright i just hadnt seen anything that said i couldnt do it that way yet, i dont know anything about this stuff. went to that link but have no clue how to do that either so i guess im screwed
Delldorado said:
hmm alright i just hadnt seen anything that said i couldnt do it that way yet, i dont know anything about this stuff. went to that link but have no clue how to do that either so i guess im screwed
Click to expand...
Click to collapse
Read up on how to set up and use ADB from your PC (search this forum), specifically pushing/pulling files and using the shell. Once you've become familiar with that, the instructions for rooting JI6 won't seem so difficult.
i also wish i had read this before spending 7 hours aimlessly in front of my computer thinking i was on the brink of success every time i tried.
Hi guys and gals. I'm a complete newb when it comes to tinkering with Android, I have a little experience with iProducts as I have mucked around with them for a while. Jailbreaking an iProduct is piss easy compared to this!
I have just unlocked & flashed my Xoom with JWTylers One click method here...
http://forum.xda-developers.com/showthread.php?t=1011196
All works well. In the 'about' section it showed the Tiamat kernel to be 1.1.6, or something like that. I also downloaded Rom Manager and flashed CWR through it. What I wanted to achieve was external sdcard functionality, so I tried reflashing with this step to 1.3.1 ...
http://forum.xda-developers.com/showpost.php?p=13036180&postcount=497
Worked a peach.
So, I did everything step by step, and created a new folder called 'sdcard2' in the sdcard directory. After finishing everything I downloaded the 1.3.2 zip and moved it from downloads to sdcard2 folder with Root Explorer? Ran the CWR recovery and when I go to press the flash zip from sdcard I get an error: E: Cant mount /sdcard".
I dont have an sdcard in the slot while I'm doing this, so, I don't know if this is the cause.
Any help to explaining this would be great!
Hey, just flash the new Timat kernal 1.4.0 and download auto mount from the market and your set!
endine said:
Hey, just flash the new Timat kernal 1.4.0 and download auto mount from the market and your set!
Click to expand...
Click to collapse
Hi, thx for your reply. Can I just download the file directly to'my downloads folder on my Xoom, like I did in the second link I pasted in my post, and follow those steps? I also mentioned that I don't have an sdcard inserted. Would this make any difference as to why I'm getting the error message in CWR?
flombs said:
Hi, thx for your reply. Can I just download the file directly to'my downloads folder on my Xoom, like I did in the second link I pasted in my post, and follow those steps? I also mentioned that I don't have an sdcard inserted. Would this make any difference as to why I'm getting the error message in CWR?
Click to expand...
Click to collapse
You need an sd card, that is probably why you got the error.
endine said:
You need an sd card, that is probably why you got the error.
Click to expand...
Click to collapse
Appreciate your help. I'll be getting my sdcard soon, I hope it works.
I also did download an auto mount program from market. What is it exactly suppose to do? It had one option at the top to tick which was to auto mount, and that was it. I suppose it runs in the background doing it's thing?
OK. I got the sdcard working, I flashed to 1.3.2.
I can transfer stuff onto my sdcard2 within my xoom and it will show when i insert the card into my PC. It won't work the other way around though. I can't get the files to show up in root explorer, or with any media player even if its a video file. Why is that? Is there a work around?
All help appreciated.
flombs said:
OK. I got the sdcard working, I flashed to 1.3.2.
I can transfer stuff onto my sdcard2 within my xoom and it will show when i insert the card into my PC. It won't work the other way around though. I can't get the files to show up in root explorer, or with any media player even if its a video file. Why is that? Is there a work around?
All help appreciated.
Click to expand...
Click to collapse
You have to reboot the xoom for them to show up.
Sent from my Xoom
hahaaaa....
That was the simplest advice I could've ever received in my life!
Thanks again.
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