startup.txt is just fine that is not an issue. I booted up the first time and it worked b ut then after a restart it tells me that userdata.img and system.img could not be found however they are where they should be at.
I have Energy.Leo.21911.Sense2.5.Cookie.Aug.06 rom and I have shubCRAFT_v1.3_1GB android. I do not have the android files in android folder because that didn't work either so I just put them in the main sd card directory.
Ok so anyway once it gives me that error it continues on with the long string of numbers and I think RAAC and it goes like it's going to boot up but it takes forever. Anyone have any clue?
sherlockpwnz said:
startup.txt is just fine that is not an issue. I booted up the first time and it worked b ut then after a restart it tells me that userdata.img and system.img could not be found however they are where they should be at.
I have Energy.Leo.21911.Sense2.5.Cookie.Aug.06 rom and I have shubCRAFT_v1.3_1GB android. I do not have the android files in android folder because that didn't work either so I just put them in the main sd card directory.
Ok so anyway once it gives me that error it continues on with the long string of numbers and I think RAAC and it goes like it's going to boot up but it takes forever. Anyone have any clue?
Click to expand...
Click to collapse
Put it all in an 'Android' folder AND change the startup.txt 'set cmd' line?
worth a try.
failing that, format and start again.
as said, reformat your card and try again. Oddly enough that happened on my sons phone until I formated within windows which is suppose to be a no no for sd cards...but desperate times called for desperate measures.
by the way, this isnt a development post.
If you store your Android files in the root of your SD card (haret, zimage, etc), then sometimes Android makes a folder called Android on your SD card and then tries to boot from there.
If your keep your Android files in the root of your SD card, just delete that Android folder, it should only have like one data file in it that gets rewritten anyway. That should let you boot up fine.
Well it was the Tom and the way I extracted it on my SD card
sent from my HTC HD2 running chuckydroidXrom and shubcraft 1.3 cm6
Related
I've been using android on my phone for awhile, and tried a bunch of different builds and never got this error. Yesterday when i was switching back to shubcraft all of the sudden the boot loader gives me
mounting /dev/block/mmcblk0p1 on /sdcard failed: invalid argument
failed
failed to mount sd card. cannot continue.
/bin/sh: cant't access tty; job control turned off
i tried loading just about ever build and get the same thing.
I've changed the startup.txt and i always reformat before i switch builds. i was thinking it might be the sd card itself, but it works fine in winmo.
if anyone can help me it would be much appreciated, im having android withdrawls...
oh and its the stock 16gb class 2
EDIT: It randomly started working again...strange...
This Is What I Do
I was getting either the same thing or something very close to it on about 2 rom to the best of my understanding is when your trying to flash (for lack of better words) a new rom you still have some left over traces either on your storage card or the phone so what you need to do is format your SD card and reflash your phones rom.
I took the origin file put it on my sd card unzipped it there went into the android rom folder cut the plain android folder paste it withe the other folders then reased every folder EXCEPT the PLAIN ANDROID FOLDER now put the sd card in the phone enable the the sound then install android.
To be able to watch the process after you flash your rom go to settings, system, power (battery) and uncheck everything so it doesn't sleep. when you install now you will see the progress and will be able to read the progress if you see 2 things have failed
This is my process and it hasn't failed yet when I didn't do it this way I had fails.
Striving said:
I was getting either the same thing or something very close to it on about 2 rom to the best of my understanding is when your trying to flash (for lack of better words) a new rom you still have some left over traces either on your storage card or the phone so what you need to do is format your SD card and reflash your phones rom.
I took the origin file put it on my sd card unzipped it there went into the android rom folder cut the plain android folder paste it withe the other folders then reased every folder EXCEPT the PLAIN ANDROID FOLDER now put the sd card in the phone enable the the sound then install android.
To be able to watch the process after you flash your rom go to settings, system, power (battery) and uncheck everything so it doesn't sleep. when you install now you will see the progress and will be able to read the progress if you see 2 things have failed
This is my process and it hasn't failed yet when I didn't do it this way I had fails.
Click to expand...
Click to collapse
you can search a tool named SDFORMATER V2.0, it will be worked.
okay this is now happening to me as well!
had been using Android and various different builds without hitch.
but today after trying the Hyperdroid build the sd card fails to mount on startup.
Editing the startup.txt does nothing, have also flash to the latest chuckyrom and formatted the sd card time and time again and tried different builds.
anyone have any other suggestions?
Ta
working again now.
the fix for me was to reupload my backup to the sd, format then upload the required new build.
very odd...
snigs said:
working again now.
the fix for me was to reupload my backup to the sd, format then upload the required new build.
very odd...
Click to expand...
Click to collapse
odd indeed...for me i had to reformat my sd card using my phone, didnt really make any sense to me but it worked
Hi guys,
I've been trying out different android builds but after a while it won't boot in android anymore.
I run the CLRAD and HaReT, it show the command lines and then freezes on the HTC screen.
It is not the first time I'm launching it, everything is allways set up the way I like it and then I want to reboot a final time and it freezes. (first boot only takes 10 min.) Then I have to take out the battery to reset, but everytime after it freezes, tried waiting for +1 hour but no changes.
When I delete all the android files from my SD card and copy the original ones it restarts again and I have to setup everything again.
I tried new wm roms (Miri HD2 wm6.5.x) different radios (now 2.12.50.02.2),
the new HSPL3 but nothing seems to solve this.
edit: now I'm trying to use the mdeejay froyo HD v3.7 rom
I've searched the forum and other users seem to have the same problem, but no solutions have come forward. The people replying allways seem to think it is the first boot that takes 10 min. but it's not that. First boot works fine.
I would love to have a solution so I can start using android on a daily basis.
If you need more info, just ask.
I was having the same problem initially...very frustrating. Now i found the permanent solution for this problem. The problem on the second time or more on rebooting is depending how do you install the code in the root of SD card. Please follow the instruction carefully as each ROM (depending on which one you use) may require the files to store diffrently in the "root" of SD card. So read carefully after you unzip the code, where should you transfer the files in the SD card. Either under SD root or SD\Android (directory).Eg. I'm using FroyoStone_Sense V3.2 ; use 7-Zip File Manager program (can be download), then execute (click on the downloaded file : FroyoStone_Sense-V3.2.7z ) with the 7-Zip File Manager then you will get 2 directory 1. Android 2. Media and one readme.txt file. Copy the directory 1 and 2 in you root of your SD card. Then you run thru file manager, CLRCAD.exe follow by haret.exe . This the first setup. Let it run and setup your device. It will work and the second time you reboot, just run CLRCAD.exe and haret.exe as usual, your device will work perfectly..Good luck.
Hi, Just to add another note for you convenience if you are using different android build ef Mdeejay_Froyo_Sense_v.2.4.2_NextSense; when you extract the downloded file using 7-Zip File Manager, you will get 2 directories 1. AndroidApps and 2. Media with the rest of files including CLRCAD.exe and haret.exe .Copy and paste exactly the structure into your SD card. It will run beautifully and you will not have probelm on freesing on 2nd reboot even for the next reboot...hope it helps and try it out.thx.
I've the very same situation and Khairon i tried that method doesn't work...
Still same issue...
Any one can solve this?
cheers
Hi, use file using 7-Zip File Manager program to extract the downloaded zipfile. I've tried severals Android ROM builds and it works well on my HD2 after 2 weeks of trial and error on the freezing after the 2nd reboot. To increase your chance of success, reformat the SD card only then copy the files into the SD card.
Thx
all done, still same 2nd boot = freez
dont understand wots wrong
i am using the mjeedy's revolution build
is there any way to completely burn the android to HD2 like wince roms?
cheers
i was having exactly same problems as u, so i formatted my card with a card formatter, not through windows but used a card formatter, installed android agian and bingo it works, im using droidrom, radio 2.12, with the card format do full reset not quick this should work
full format is not working either
I also noticed that there is a file popping up on my SD card : EncFiltLog.menc
Searching around points to SD card encryption, but this is turned of in windows.
I checked with Miri, who made my windows rom and he said it's not set in the rom itself.
But this might explain everything, when I reboot the linux bootloader can't read the SD card because of the encryption.
Only thing now is to turn it off, but how can I do this when it is off in windows
I also had that file today on my "goldcard", the old 2GB SD-card shipped with my HD2. I tried the old card, because I can't start android (on 16GB sandisk) anymore.
Hi, I have the same problem.
Reboot freeze on 16GB Kingston.
Working fine on 2GB SD.
On both SD card is the same formating.
it doesn't seem to be related to the SD card i guess, I also tried my original 2GB card instead of my regular 16GB.
Both give me the same problems.
Hey anyone got a resolution to this??
my build works on my gb but not my 6gb card???
I followed directions correctly, i even played with my new android os for hours. now this happened
I have a big problem now I have chose the reboot option in android and it took me back to windows like normal I then choose ctrcad and I'm getting an error on both clrcad and Haret this is what it said " the file Haret cannot be opened. Either it is not signed with a trusted certificate or one of it's components cannot be found. If the problem persists try reinstalling or restoring the file". What's going on. I worked hard in setting up android the way I like it. I can't access it anymore
I sugest you post this in the thread from the rom you installed as it could be one of many
neverworld said:
I followed directions correctly, i even played with my new android os for hours. now this happened
I have a big problem now I have chose the reboot option in android and it took me back to windows like normal I then choose ctrcad and I'm getting an error on both clrcad and Haret this is what it said " the file Haret cannot be opened. Either it is not signed with a trusted certificate or one of it's components cannot be found. If the problem persists try reinstalling or restoring the file". What's going on. I worked hard in setting up android the way I like it. I can't access it anymore
Click to expand...
Click to collapse
You should never choose the "reboot" option in Android on HD2, It can corrupt data on sd card which is what has likley happened here. If you want to go back to Windows when using a SD Android rom you should just power down and power on.
copy your data.img (if you want to save apps/data within android) and other data you may need from card and then format it with SDFormatter (FULL>Overwrite+Size Adjust) then put stuff back on card, rom and the data.img and boot back in.
or try to format your sd card with mini tool wizard.
(•.•) said:
or try to format your sd card with mini tool wizard.
Click to expand...
Click to collapse
Does this actually do a proper format, ie overwrite data or does it simply delete TOC or re-create partition?
Anyway, seems a bit overkill loading up a bloated partitioning tool just to format your card when you can use a simple small clean app like Panasonic SDFormatter.
I have set up a dual boot on my HTC HD2 following one of the threads on this forum.
The phone boots into wm7 ok, but the problem is the Android boot (AmericanAndroid build)
I copied the Android folder as per the instructions
I go into magldr and select option 2. Boot AD SD
I then get the following messages.
Android load 1800000
From Microsd
Load Zimage
k: /ANDROID/Zimage
SD kernel open failed
Any suggestions as to what I may have done wrong?
is this your first AmeriCan Android install?
Edit; Have you tried;
"In MAGLDR go to services(10)>Boot Settings(1)>AD SD Dir(3)>"choose your Android folder. Make sure you have all the files you extracted in sd/android."
(from HearMeWhisper)
Warren and Cope have recently changed the way ACA boots up
Thanks for the reply.
Yes it is my first American Android install. and I set it to boot from the Android folder.
I extracted all the files, changed the rootfs and statrup files as per the instructions.
I previously tried the Warren and Cope build, but had the same problem
It's worked for me without any problems, try to put all the files in the root of your SD card, not in folder
"In MAGLDR go to services(10)>Boot Settings(1)>AD SD Dir(3)>"choose your Android folder. Make sure you have all the files you extracted in sd/android."
The "Android" folder is usually at the end and must not be confused with Androi~
Keep scrolling until you find it
Thanks Win_XP and Robbie P.
Tried both suggestions, but still the same.
Excuse my ignorance as I am new to this although computer literate.
Looking at the setup text file it seems to point to the Android folder and part of the bootup message tells me it is looking at k: /Android/zImage
I cannot see the file zImage. Should I be able to see it or is it contained in another file?
Not sure where the K: bit comes in either.
zimage should be in Android folder.
try deleting the files on the android partition (it is set to Primary Yes?)
do the rootfs manouvre
copy the folder "Android" to SD card. (dont bother editing startup for now)
In Magldr point to the Android folder as above (option 10 etc)
see if it boots from option 2
What is your sd card size, and what are the partition sizes?
Thanks for all the suggestions.
I have managed to get a bit further in that ALZip was not extracting zImage so this was the problem.
Managed to extract it and now have phone sitting on 'powered by AmeriCan Android' screen.
Not sure how long it should stay like that, but at least moving forward.
Just out of curiosity what do you people use to unzip files?
7zip, its free and unlimited.
others like winrar expire after a time.
Hope its gone OK
I had the same issue when I first try to boot AmeriCanDroid but now it's work like a charm
What I've done?
Simply forgot to choose the android SD boot directory under Services>BootSettings>AD SD Dir and also don't forget to replace the rootfs.img with MAGLDR version (see readme in AmeriCanDroid folder>SDMAGLDR)
Thanks Robbie P - all working ok now
I'll have a look at 7zip
I've always booted Android from my SD card using RunDroid under Windows 6.5. But I broke my HD2 so I bought another used HD2.
This "new" HD2 already has Android (NAND) installed and it's using MAGLDR 1.13. The installed Android version runs fine so I don't want to remove it. Instead, I simply want to run the same Android I've been running on my old HD2 from SD.
So I boot into MAGLDR, goto Services -> Boot Settings-> AD-SD Dir to pick the directory I want to boot my Android from.
Problem is, the directory list MAGLDR is showing isn't anywhere near complete. It only shows the first 9 directories on the SD card (there are about 30 directories on the SD card). So I'm unable to choose the right directory to boot from.
This is a 16GB SD card formatted as FAT32. My old HD2 had no problems whatsovere reading from it (not in Win6.5, not in Android).
So does anybody know what's wrong here?
Thanks in advance for your help.
Perhaps some folders have an attribute set that is hiding them? -h for instance. Personally I'd create a new folder, test if mgldr can see it, and if it can, move the contents of the android folder into it. If itccan't, I'd backup the SD, and do a complete reformat of the card, including rebuilding the partition from scratch.
All directories can be viewed from within Android without problem...
Odd thing is, that MAGLDR is displaying all directory names in 8.3 format. In fact, I think it only shows the directories created from within WM 6.5. The directories it doesn't show are created from within Android.
I've copied the contents of the SD Card to my PC's harddrive, reformatted the SD Card and copied everything back.
It's still only showing the first 9 directories (only this time 9 different directories).
The card was formatted using FAT32 since I want the card to be readable under WM6.5 as well. But that shouldn't be a problem considering Android can read the SD card just fine.
Zippy1970 said:
It's still only showing the first 9 directories (only this time 9 different directories).
Click to expand...
Click to collapse
try this just for kicks, if youcan be bothered,,,, empty teh card, put the dirs on in the ordser you want them to appear, one at a time. Im betting the first nine you drag across will appear.
Ive seen harddisks do the 8.3 thing unexpectedly, i'd be looking hard at the sd card. If you have another card available, definitely give it a test to compare.
As for the fat32 formatting, perhaps a non standard block size was used (or at least one magldr wasn't expecting, , remember magldr is a handfull of lines of code compared to androids many hundred thousand lines, , just saying 'well android can read it fine' is a bit like saying 'hey what gives, , my binoculars can't see the horsehead nebula, but the hubble can'
(astronerds, calm yourselves, yes i know you can see it thru a nice set of decent binos with a good lense/filter, it was just the first commonly known astro object i could think of )
Yeah it's showing the first 9 directories only so I did what you said and cleared the SD card and copied the Android folder first, then the rest. MAGLDR now saw the right Android directory and I was able to set it as boot directory. But now I have another weird problem. I've started a new thread since it's (I think) an unrelated problem.
Zippy1970 said:
I've always booted Android from my SD card using RunDroid under Windows 6.5. But I broke my HD2 so I bought another used HD2.
This "new" HD2 already has Android (NAND) installed and it's using MAGLDR 1.13. The installed Android version runs fine so I don't want to remove it. Instead, I simply want to run the same Android I've been running on my old HD2 from SD.
So I boot into MAGLDR, goto Services -> Boot Settings-> AD-SD Dir to pick the directory I want to boot my Android from.
Problem is, the directory list MAGLDR is showing isn't anywhere near complete. It only shows the first 9 directories on the SD card (there are about 30 directories on the SD card). So I'm unable to choose the right directory to boot from.
This is a 16GB SD card formatted as FAT32. My old HD2 had no problems whatsovere reading from it (not in Win6.5, not in Android).
So does anybody know what's wrong here?
Thanks in advance for your help.
Click to expand...
Click to collapse
i extremely stuck i was trying to use native sd method so i created a new ext partition but when i tried to create it i am unable to see any folders in the Services -> Boot Settings-> AD-SD Dir to pick the directory I want to boot my Android
why is this please help me asap
That was a problem to me when I started playing with nativesd, seeing only the first few directories, but if you just use the volume rocker to scroll down, you will get another page of the remaining directories and files, simple.
Just great reply - Thanks
:good:
phochiom said:
That was a problem to me when I started playing with nativesd, seeing only the first few directories, but if you just use the volume rocker to scroll down, you will get another page of the remaining directories and files, simple.
Click to expand...
Click to collapse