Develop Bugs

Having problems to install android

hi there
i really need your help. i'm trying to install android on my HTC TyTnII. But i'm having problems to install.
can you please help me to get Android run on my Kaiser?
Right now i'm running the windows mobile 6.1. I want to install Android as a secondary OS.
i followed this installation guide.
androidonhtc.com/wiki/Installing_Android
1. I went to this link to download files.
androidonhtc.com/wiki/Latest_Builds_%28Kaiser%29
2. I downloaded the basefiles-20091116.zip
vogue-android.googlecode.com/files/basefiles-20091116.zip
3. Unzipped this zip file. Renamed the default-kaiser.txt to default.txt and moved the whole folder "android" to my storagecard.
4. then i downloaded the haretinstall.zip and unzipped that file as well. I moved the folder "andboot" to my storagecard.
sourceforge.net/projects/androidhtc/files/2010-02-20/haretinstall.zip/download
5. then i downloaded the polymod_2.1g.zip and unzipped that file. I moved the file "androidinstall.tar" to my storagecard as well.
ponack.net/poly/2.1g/polymod_2.1g.zip
6. i clicked than on "haret.exe" and clicked on Run. the android started to load but then it stops. It gives me this error.
--------
....
Checking for partition...
s2fsck 1.41.4 (27-Jan-209)
ext2fs_check_if_mount: No such file or directory while determing whether /dev/block/loop0 is mounted.
/dev/block/loop0 was not cleanly unmounted. check for ced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/loop0: 11/65536 files (0.0% non-contigous), 10335/262144 blocks
losetup: /dev/block/loop1: No such file or directory
Failed
Failed to find system.im on SD Card
/bib/sh: can't access tty1 job control turned off
/ #
--------
Can anyone help me out to solve the problem?
Do i need to do some partition? if yes...how can i do it? i'm using a windows xp OS.
This is how my SD-storagecard looks like:
/[android]
/[android]/[andboot]
/[android]/androidinstall.tar
Thank you for your support.

The androidinstall.tar should be in andboot folder, with all the haret files. andboot must be in root of SD card.
/
/andboot
If you were installing to nand it'd be :
/KAISimg.nbh
/andboot
You do not need to partition the SD card, just make sure it is formatted FAT32, not FAT

hi zenity
thanks for the response. I did what you said. Still having the same problem with the same error message.
how do i check format of my sd card? i've never formated it before. it's the original sd card.

Depends if you have an sd card reader and adaptor for micro-sd, if you do you can just format it in windows.
It's likely that it's formatted FAT, most new pre-formatted micro-sd are formatted FAT as standard, how are you transferring files to the sd at the moment?

i connected my htc with microsoft activesync then transfered the files via windows explorer.
i'm still struggeling to get android run on my device.
are those steps correct? or am i doing something totally wrong?
those installation guide are too complicated for me. the instructions are mostly for total replacement of the OS. But i would like to keep my windows mobile because of tomtom navigator. I want to make both OS run with Dual booting function.
if you are so kind...can you please guide me to make this run? I'll be thankful for that.

Best way to format an SD card is to use a card reader and micro-sd adaptor, I've never tried to format an SD with winmo or through activesync, so I'm not sure how easy that is.
I have transferred the files via activesync before, and that works fine, but your SD card must be FAT32, winmo probably does not know the difference, I'm sure there must be a way to format the card FAT32 in winmo, but I cannot think of one, I'll look into it though. I think total commander is able to show what type of format the sd card is, but don't know if it's able to format it.
All the Haret files plus the androidinstall.tar must be in the andboot folder on the SD card, you do not need any other files or folders on the card, but it should not matter if there are any.
You will need an SD card of at least 1GB, 2Gb is better.
I know the guide is meant for Nand install, but does show the installer screen part clearly, and the install procedure is the same for nand and haret, and shows the installer screen you should see when installing on FAT32, (haret).

Download Card Export or WM5Storage to mount the card. Then format it like you would do with a usb stick.

me too
I get the same error.
I have haretinstall and androidinstall.tgz in the /andboot folder.
I renamed default.txt to default.txt.no
I renamed default-kaiser.txt to default.txt
I edited default.txt to point to zImage-eclair
I tried with the regular zImage
I wait till it ask for dpad or vol up button then I press and hold dpad. It never recognizes? Or thats my guess from what has been said here.
right clicking on the drive from within windows using a card reader it says fat32.
When I press dpad it prints a ^@ to the screen, ironically it does the same key for ok. I don't see how I can hold down the vol up/down key cause its a jog wheel? Should I try dpad down?

Volume Up Is the RIght SOftKey. FOr some build only that work.

@zenity: i manage to format my miniSD to fat32. it was fat before. but the problem is still there..does anyone else know how to deal with this?
as tyler51773 already mentioned..i fi start the "haret" which is stored in "andboot" folder it request to hold down the vol button. although i pressed the vol. button,,,it still doesn't work. getting the same error message like tyler51773
seems like i'm totally lost. someone please help!!!

can anyone write down a clean instruction how to install the kaiser on SD incl. the right link (instead of telling users to find out the right one) without wiping out the windows mobile. this would be more helpful to us.
i'm sure there are other users who might be interested in this too.
thankx

When you run Haret and see scrolling text, immediately hold down the d-pad or vol button. Don't wait for it to ask.

hi all,
i have the same problem. the instructions seems to be bad. i cant run it and tried many things. in install-instructions says "androidinstall.tar" but download is androidinstall.tgz.
i don't know if its a big mistake, but someone should make a new "correct" instruction with correct files. maybe it then will be worked.
i also stuck on "can't found system.img"
greetz an sorry for my english

@dukennukemx: i did what you said. no improvement.
@lenzen24: i'm 100% with you!

i tried again,
but also failed on find system.img on sd-card
hope someone has a solution, becaused i woudn't flash a image over my wm6.5.
greetz lenzen

progress
The right soft key button worked, (i.e. the one right above the mail, to the left of the red phone to the right of the dpad just to be perfectly clear for anyone else).
I got the menu, and then it said unbalanced irq 102, unbalanced irq 86?, unbalanced irq 87? it froze then rebooted.
Second try, I hold down the right softkey after i see the penguin. I get the menu with the ok warning. I try all the buttons the warning stays up. I open up the keyboard. I press enter I now am in the menu.
The install option is missing? I have 1. fix permisions. (vs it saying install?) The dpad doesn't seem to work. I have 7 options. The last option is quit. The 6th one is recovery. 5 is wipe. As I'm staring at errors and not the menu I forget which the rest are. I remember seeing a backup/restore. Then their is wipe. Their was also the wipe cache options.
When I try to navigate the menu its a no go. The only real options I have is fix permissions. That leads to errors due to a missing system.img that hasn't been made yet? And then their is quit. I get to quit using the left opt key, and I can get to fix perms using the right opt key. If i open up the keyboard and try every key the only key the menu responds to is enter. I also tried w/ fn lock, but not shift, no responce to the arrow keys was a bummer. When I accessed a shell I can atleast confirm that qwerty mapping was right, but didn't hang out long enough to see the rest of the keymap.
Should I try zimage-eclair? I will of course do that at some compulsive moment, but hey, maybe I wont, or maybe I will and say I haven't yet - maybe I already have {knowingly or not}.. do I need some options in my default.txt? Should I try a different androidinstall? this is polymod-2.1g
This is actually a Tilt vs a Kaiser.
Thanks for the speedy replies and help!
Tyler

Problems with the install option not appearing are usually caused by not formatting the sd as FAT32, or a wrongly set up sd card, for haret installs, everything goes in andboot folder, for nand, androidinstal.tar, (or tgz), in andboot folder, kaisimg.nbh in root, the install instructions are clear enough, they are just not as easy to follow for inexperienced users, and tilt and kaiser are the same thing, if you look under the battery it will say 'kaisxxx'.

zenity
Your last post you can tell someone got under your skin...
I'm a fairly experienced user. I have had troubles installing android since the nand came along.
I feel that if I were willing to nuke my winmo it would be installed. my primary objective with this phone is voip. I'm hoping sipdroid gets fixed or the reports of sipagent working better than sipdroid are true. I'd like to investigate that. I'm poor and with winmo I pretty much make free calls. Albeit I have reliability issues, and I have lots of things i should script to make things work which is all the more motivation to move over. Especially with winmo7 stripping voip out completely [rumor mill]. Anyhow, I am not willing to nuke my winmo. It's quite cryptic to call the volume key, the volume key, when on the kaiser its the right opt key. Perhaps the problem is that I am running a tilt vs a kaiser, another cryptic difference? good thing we don't have a lot of sidekicks running around either. Anyhow. My card is formatted right. I even tried another almost virgin 2gb card, never been formatted but did have a raw filesystem that was only used on sundays while driving to church, it was freshly formatted with fat32 and still it was a no go.
I also just tried myns build. I get an install option, when I press enter it warns me that it is about to delete my all my stuff. So I would say no, but after feeling wrath I tried to say yes, but of course I can't navigate nothing I push will let me choose yes. So I safely run with no.
If I did have a dpad where it says backup data could I backup my winmo? That makes me feel good I've always wanted that. That feature alone would make my day as it would let me finally upgrade my sacred voip setup w/o fear of having to find all those little f!&@&# registry entries again.
Enter does a carriage return in shell? New line in any event..
Dpad/Ok on the front both print a ^@, so does the side ok button, and so does the keyb ok button. {so does; Winkey, MailKey, GreenPhone{send}}
Dpad/Keyb/Jog Up does a ^[[A
Dpad/Keyb/Jog Down does a ^[[B
Dpad/Keyb Left does a ^[[D
Dpad/Keyb Right does a ^[[C
Left Opt: ^[[26~
Right Opt: [BLANK]
e does ^[[1~
red phone{end} ^[[4~
PwrOff ^[[4~
Admittingly this is using myn's androidinstall.tar as i just got done trying that, not sure if the keymap would vary at all (I highly doubt that). Anyhow I also did see the sdcard mounted. I cd'ed into it and did an ls. Everything showed up. It was mounted rw.
Let me know if I can do anything else to speed along the development.
Hate to ask a dumb question? But why not continue to distribute the sqsh builds if they're so much easier to test out for winmo users? Isn't that what the installer is trying to do is process the androidinstall.tar file into either one of three options one of which is cacheable - the sqsh files?
But still, I'd love to hear I now have a back up option..
Zenity thank you for your hard work and even diligent support! I totally get the stress that comes with messing with software for long periods of time. If it helps we can sacrifice a user to the /dev/null ? Hope you're feeling better.

tyler51773 said:
Your last post you can tell someone got under your skin...
Zenity thank you for your hard work and even diligent support! I totally get the stress that comes with messing with software for long periods of time. If it helps we can sacrifice a user to the /dev/null ? Hope you're feeling better.
Click to expand...
Click to collapse
Lol, sorry if it came over like that, I was typing it at a cafe on my kaiser, so I didn't spend as much time as I usually try to on a post, I usually try to structure them as carefully as possible to avoid misunderstandings
To be more accurate, I feel that the present sets of install instructions do assume a lot more knowledge than a lot of those new to Android actually have, this is not a disrespectful statement, simply that most builds have grown and changed so much, and the users who have been using them have also grown in specific knowledge of the install process, this, naturally, has led to some instructions assuming that those users all know the basics, which of course would be true if there were no new users.
It is difficult to produce a generic set of install instructions, since there are still a number of ways to get android onto our devices, and some builds are designed for other hardware originally, myn's for Vogue for example, so the install instructions tend to be more focused on those devices.
As far as the actual installer is concerned, the only time you will wipe winmo is if you have already flashed to nand, running via haret will not wipe winmo, the warning about wiping the system, or data, applies only to the Android build you are installing.
The present installer will process the androidinstall.tar or .tgz and install either to nand, if that is available, EXT2 partition, again, if available, or FAT32 partition, most commonly known as SD card or Haret install, the actual installation will then unpack the tar file to the proper destination, and on haret will produce a system and data img file, I'm unsure if it produces a sqsh file, since it's been a long while since I ran from anything but nand, but I do understand the confusion the install produces for those wishing to stay with winmo, and would prefer that it was clearer, but as with most of android development, once it works, development ceases until it breaks
Rest assured, unless you flash to nand, your winmo should be completely safe, I have not yet seen anyone wipe winmo using the SD/Haret method, not in all the time that we have been running Android on our kaisers.
I'm confused now however, I was always under the impression that the Tilt was merely another kaiser model, and unless you have forgotten to edit the default.txt file to reflect your hardware, the keypad/dpad should function properly, which as far as the escape sequences you have posted, would seem to be the case, ( dpad centre should give ^@ in console etc), so navigating the installer should be as easy as pressing the left, right up or down keys, followed by centre to choose options.
What I am now tempted to do is reflash my secondary Kaiser to winmo stock, and try a few haret installs just to check out things, since most of the above is mainly from memory, although a lot of the Nand install procedure is similar, may not be identical.
Sacrifices will not be necessary, however offerings may be made of caffeine, and/or chocolate, this may help me continue to function in my role as helpful user, and reduce my occasional visits to the mild irony I call my sense of humour

cool
I feel you about short emails making one sound bad! I made that mistake a few times. I actually hate email. I wrote this very funny email to my advisor, he liked it, and forwarded to his boss - just communicating, not to share a laugh or to complain, but to answer a question he did not know; atleast I was told that as I was then later forced to ask him 'did I make you mad?'. Anyhow I got chewed out for professionalism by the department chair which is not the way to a elect a major. Funny enough, I had decided writing funny was the way to go after i had peeved someone off for writing short almost angry sounding emails. In short I hate email/communicating via text.
I was thinking about the whole solution thing. If i need to do a key remap maybe we could just write up a shell script and I could execute it from /sdcard and then re-execute the installer ? unknown.sh??
Also, if you produce some img files what's to stop you from sharing those? I'd totally be willing to try it, maybe it'll work, maybe it'll break wifi calibration? who knows?
Bug found:
http://code.google.com/p/vogue-android/issues/detail?id=124#makechanges
set cmdline "ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend board-kaiser-keypad.atttilt=1"
just tried to change board-kaiser-keypad.atttilt=1 with no results
Just my .02c

How to install froyo on sd card

So first of all i must say that im a completly noob at the android instalation on kaiser
I search for a noob tutorial but i coudnt fiind can someone post here a tutorial including files thanks

Here is the Guide in Sticky
How to replace Windows Mobile with Android (Guide) by Dukenukemx
scroll down to Installing Applications Onto SD Card using Ext2
This should help. The guide help me greatly, very easy to follow.
Hope this helps.

Its not tricky, I mean even I can do it, come on
I did edit a wiki page on this, but appears to be down, so here goes, from memory.
Backup any data first, just in case, not taking any responsibility for loss of data.
Firstly ensure your SD card if formatting correctly (FAT32), use on Gparted (linux live CD) to do this, (for me, I created two ext 2 partitions as well as I thought this would work best, works for me).
You then need the HaRET application to allow you to run Android. Google "haret.exe"
Extract the files this should create the right directory.
You then need to choose a build, this is personal choice, but I'll post the one I am testing right now. milanche's CyanogenMod 6 Kaiser
Put the installandroid.tar into the folder you created above.
Move to your SD card.
Find and run HeRET.
When screen shows text, tap and hold the center of the screen until you get a menu.
Choose install (ensure the options are set to SD).
Select Install
Once done, select Quit.
This then installs Android and can take a while, just leave it to get on with it.
You should then been booted into Android.
I might have forgotten something, as I am doing this from memory, but it should be fresh since I installed this last night.

Looks good to me, nice guide, don't think you missed anything

Thatnk you Zenity, but I know I couldn't have done this without your help in the begining when I first tried it. I know how it can seem all a bit over whelming.
I know a lot of people say 'search for it' but I did that just to see what I would find, and to be honest, I didn't get anything but that was of any use, so I can sympathis the search doesn't always get you the right results.
I could not remember the direcotry names when I wrote that at work and had to do it in a hurry as the entire office can see my magnified screen so it was a quick brain dump, not as nice as I would have liked to have written it given the time (which I did on the wiki but its down).
Anyway Keeps it fresh in my mind too.
I can only do this when I'm given the right files, I got confused myself when people started talking about different zImages. I tend to go for the builds where everything is bundled into one packing, as some can seem fragmented, ie Fresh Foryo, I don't doubt that it may be a good rom, but its deleivery is complicated (for me ).
Wish I had more time an experience to make my own build, I have done a bit of linix hacking in my time with shell scripts (getting wifi cardds working ona laptop etc), Its all interesting stuff.

thanks guys u helped me alot in the end i will instal android on an ext2 partition

Dear Leona,
The link seems no longer valid, can you tell where to find the latest HaRET application? Besides, how should I format my SD card? by special software? Thanks.
Dave

If you'd have problems with using Gparted Live CD like me... just because it does not mount SD card in adapter... here is what I did to partition the SDHC 4GB card...
I booted with HARET but did not select to install.. it gracefully fails to terminal
command: su
command: fdisk /dev/block/mmcblk0
deleted all current patrition (d)
created new partitions whith calculated size (8192 for 256MB)
changed type of the first and biggest patririon to FAT32 (t => c)
written all the changes to the partition table (w)
Than you should take out the card before rebooting and format FAT32 partition in win to upload all te android boot files, rebot the phone and follow with instalation...
But I must say, now I am using Scooters Cyanogen in NAND and it it far far easier

After I choose run, then a list of Linus commands ran, then it said
:loseup:/dev/block/loops: No such file or directory
Failed
Failed to reach system.img on SD card
By the way, anywhere I can download a complete set of files for running? Thanks.

try this:
http://forum.xda-developers.com/showthread.php?t=813382&page=31
look for the 4th post...
or this:
http://forum.xda-developers.com/showthread.php?t=855733
read a lot before attempting to do anything! use the search tool too, could be of some help.

For SD Partitioning, I remembered this Thread, which might help.
http://forum.xda-developers.com/showthread.php?t=619290
Sounds like you are not holding the centre Dpad button (or pressing the centre of the screen) while haret is loading, yes this can be Hit and Miss it winds me up no end.
If you have access to a Linux machine (or boot a Live CD), as well as being useful for SD partitioning it also maybe used to try out Atools (you'll need to install python and python-tk (via the package manager)) as this will get you the right Kernels, images and configure your default.txt file for you, though I haven't managed to get the build script bit working yet, but that is down to my lack of understanding the instructions

Update troubles with my Wildfire S

This has been a problem with my device since the very begining, and I would like to know if it's a general problem with Android, if it's a specific problem with the Wildfire S, or if it's just that god hates me and he gives me the devices with all the horrible bugs (see this thread for my other inexplicable bug that no one else seems to have).
Sometimes, when I go into the market and try and download app updates, the update goes through it's process of installation, the progress bar fills up and everything... then right as it's about to finish I get an error. "Update failed, please try again." It's very inconsistent too, sometimes I'll try and download an update a few times, and on the third attempt it gets it. Other times the app won't be able to update for months at a time. My mobile has been trying to get an update for "Cut the Rope" for over 3 weeks now. It gets so annoying I turn the WiFi off because he keeps throwing "Updates Available!" notifications at me that are completely useless to me.
Anyone else have this? Or is my WF-S just cursed?

Philippe Lemay said:
This has been a problem with my device since the very begining, and I would like to know if it's a general problem with Android, if it's a specific problem with the Wildfire S, or if it's just that god hates me and he gives me the devices with all the horrible bugs (see this thread for my other inexplicable bug that no one else seems to have).
Sometimes, when I go into the market and try and download app updates, the update goes through it's process of installation, the progress bar fills up and everything... then right as it's about to finish I get an error. "Update failed, please try again." It's very inconsistent too, sometimes I'll try and download an update a few times, and on the third attempt it gets it. Other times the app won't be able to update for months at a time. My mobile has been trying to get an update for "Cut the Rope" for over 3 weeks now. It gets so annoying I turn the WiFi off because he keeps throwing "Updates Available!" notifications at me that are completely useless to me.
Anyone else have this? Or is my WF-S just cursed?
Click to expand...
Click to collapse
Try clearing your cache. How much room have you got on your cache partition and in your data paritions?
It has to download a 15 meg or whatever installer for Cut the rope, then unpacking it then install it then delete the original installer. That takes more than 15 megs.

How do I clear the cache?
Also, can't it use my microSD? I have a 32GB card in there.

Philippe Lemay said:
How do I clear the cache?
Also, can't it use my microSD? I have a 32GB card in there.
Click to expand...
Click to collapse
Use it for what? Can you give me some details? Is your phone S-OFF, rooted, etc?. How much internal memory do you have right now, etc.

d33ps1x said:
Use it for what? Can you give me some details? Is your phone S-OFF, rooted, etc?. How much internal memory do you have right now, etc.
Click to expand...
Click to collapse
You said that when an app is downloaded it needs to first download a 15 MB "cache partition", I was wondering why it can't use some of the space on the microSD. As for rooting, I have a GSM Wildfire S, from what I understand those are difficult to Root... so no, I've never rooted it, and I don't think it's S-Off (I'm not sure how to check that...)
I think I have 31 MB of free internal memory capacity...

pm setInstallLocation 2 and Apps2SD with Tutorial
Forget all you heard from me before as it seems to have served to confuse you which is fine. No worries.
Read this thread
Where it says to type "adb shell pm setInstallLocation" instead to be safe type:
"adb shell pm setInstallLocation 2" which tells the phone to try to install an app to your sd card by default. 0 is auto and 1 is internal.
Keep in mind that it doesn't move 100% of the app to the phone. App libraries, Dalvik cache data and application cache data will stay on the internal memory but it will buy you some space.
That's it.
PS:
Go somewhere and get your phone XTC-Clipped. You will have a lot more options to create space such as Link2SD which moves the apps, app libraries and dalvik cache files to a second external partition you create.
The nice thing about it is DOES allow you to move widget apps and they work.
Another nice thing about it is when you put your phone into usb mass storage mode, even though the primary partition on it with all your own data, pics etc, gets unmounted in the phone and unusable, the second partition doesn't unmount and you can still run all your apps that are linked to it.
Get clipped! If you have enough for a 32 GB card you have enough to spend $20 to get your phone clipped.
Now
When you are done this REBOOT your phone.
Go to this Android Marketplace link and download apps2sd
WATCH the video tutorial and then start moving apps off your internal memory to your SD card.
Beware not to move things that have widgets you want to use like say Doubletwist music player or Battery Monitor. The widgets will no longer function.
Somewhere in that program is a clear application cache choice as well. Clean up your cache for more room.
30 megs is not enough to download AND install Cut The Rope to your internal memory plus your auto sync will stop working when you drop below 18 megs or so of internal space.
Buy yourself some S-ON room with that setup.
If you want to move individual programs to or from the SD card to the phone and back, etc, you can go to /Settings/Applications/Manage/ scroll to and click on the application in question and choose the option to "Move to Phone" or "Move to SD Card".
Cheers.

I see... and this is all low risk right? I mean, getting updates to Cut the Rope would be nice, but it's not the biggest priority in the world, lol.
Also... I'm working on getting that Clip, if I have to I might just buy one... 67$ would still be cheaper than going out to buy a Nexus (from what I hear those are the easiest to Root). This clip would work with a GSM device right? That's how it does it's thing, by plugging into the SIM slot?

Link to bash

Hey-
I've been playing around with the shell, installed bash 3.2 according to this:
forum.xda-developers.com/showthread.php?t=537827
aaaand I was trying to make a link from /system/bin/sh to /sdcard/bash but it didn't take. The reason I want to do that is because I'm experimenting with bash 4.1 and it hasn't quite worked. But when my shell breaks I have to wait for a restore because I can't get write access to the dang /system folder (I guess you need the shell for that).
I know it's not that huge of a deal to have it all in the /system folder once it's how I want it, but I'm going to be playing with other stuff too (bash_profile, etc) and it's a bit of a pain doing the whole trial/error thing. Well, at least with how long it takes. I'm doing trial/error anyway.
So my question is why wouldn't that link work? I know I'd set the link up correctly, tried it several times in case I had a typo. Maybe I just don't understand symlinks like I think I do. I tested also something where I tried to make a link within only the /sdcard folder (always writeable no matter what, thinking that had something to do with it) and just got "operation not permitted". But on my linux box a link between directories is totally cool. Not sure what the difference is. Any help appreciated.

Something else I'm seeing that I really don't understand is that I can create links just not that have to do with my /sdcard partition. I can't even change permissions in /sdcard. From ADB. I run as root:
chmod 0644 filename
and it's as if it accepts the command, but perms stay the same. I did it not as root but it said operation denied. Why if I've got root can't I do some of these operations in /sdcard?

Scooterx3 said:
Hey-
I've been playing around with the shell, installed bash 3.2 according to this:
forum.xda-developers.com/showthread.php?t=537827
aaaand I was trying to make a link from /system/bin/sh to /sdcard/bash but it didn't take. The reason I want to do that is because I'm experimenting with bash 4.1 and it hasn't quite worked. But when my shell breaks I have to wait for a restore because I can't get write access to the dang /system folder (I guess you need the shell for that).
I know it's not that huge of a deal to have it all in the /system folder once it's how I want it, but I'm going to be playing with other stuff too (bash_profile, etc) and it's a bit of a pain doing the whole trial/error thing. Well, at least with how long it takes. I'm doing trial/error anyway.
So my question is why wouldn't that link work? I know I'd set the link up correctly, tried it several times in case I had a typo. Maybe I just don't understand symlinks like I think I do. I tested also something where I tried to make a link within only the /sdcard folder (always writeable no matter what, thinking that had something to do with it) and just got "operation not permitted". But on my linux box a link between directories is totally cool. Not sure what the difference is. Any help appreciated.
Click to expand...
Click to collapse
it's about a fat32 part? then will not work
You should post a log

Thanks, I was poking around somewhere and saw that other people have had problems if it's using a windows format. However, I'm burning my brains out trying to figure out how to see what format it uses and how to then change the format. It's the Samsung Galaxy S, and it's an internal memory card. I wouldn't think I could format it from my computer, it's not removable. Or else I'd have found out already using gparted or something (in fact I tried, said 'unallocated' is all). I *perhaps* could use gparted to format it as ext4 or whatever though, but I'm not sure the effect that'll have. I'd have to do some research.
In any case, I'd love to post a log but I'm not sure what log that is that you're referring to, would you mind telling me how to get that?

Scooterx3 said:
Thanks, I was poking around somewhere and saw that other people have had problems if it's using a windows format. However, I'm burning my brains out trying to figure out how to see what format it uses and how to then change the format. It's the Samsung Galaxy S, and it's an internal memory card. I wouldn't think I could format it from my computer, it's not removable. Or else I'd have found out already using gparted or something (in fact I tried, said 'unallocated' is all). I *perhaps* could use gparted to format it as ext4 or whatever though, but I'm not sure the effect that'll have. I'd have to do some research.
In any case, I'd love to post a log but I'm not sure what log that is that you're referring to, would you mind telling me how to get that?
Click to expand...
Click to collapse
If you work in adb post console output the same if you made that symlink from phone shell
do not forget to switch to root ("su" command )
by this you get part info
Code:
cat /proc/mtd
or system log here
Code:
adb logcat -d > logcat.txt
- it's saved to adb folder
(do not blame me if you already know these things)
also here is an interesting thread
maybe that part is mounted as read-only ?
make things simple as possible use Root Explorer/ES File Explorer (just tap screen to mount r-w)

Thanks, I liked that article you'd mentioned. Though I also tried the suggestion that was provided when I realized that /sdcard/ is really just /mnt/sdcard/ but still no dice.
I checked those logs, didn't see anything relevant. They're attached so if I just don't know what I'm looking for then someone would see it?
The /sdcard isn't read only, I'm able to write files to it.
I'm thinking really that it's just a windows format, but I still haven't an idea how to actually prove that, nor do I know how to format it for linux. Again- it's not removable. Anyway, if there's something that I need to see in the log, it'd be appreciated if you could point it out to me, thanks.

Scooterx3 said:
I'm thinking really that it's just a windows format, but I still haven't an idea how to actually prove that, nor do I know how to format it for linux. Again- it's not removable. Anyway, if there's something that I need to see in the log, it'd be appreciated if you could point it out to me, thanks.
Click to expand...
Click to collapse
-nothing interesting in log file
(a mount/df output is better here)
-also post this problem in Galaxy S I9000 sub-forum
I think your internal sdcard is vfat-type then try to format as ext4-type
here is a good article on this problem

[Q] Data recovery on Xperia S (rooted)

Hi all,
Just wanted to start by saying, big thanks to DooMLoRD and the rest of the xda-developers forum for providing me the tools to get root access to a friends phone, who has recently accidentally deleted all their photos and videos. If we are successful, I'll definitely be suggesting that they make a donation to Doom for his epic contributions
I'm trying to help them recover the lost media. I know that typically performing data recovery on a phone requires root access, so I have gone ahead and done this. On with...
My question:
I've got an Xperia S running Jellybean (4.1.2) which is rooted. However attempting to use my data recovery tools on the phone, the device is not shown as a storage device. As you may well be aware, the S does not come with external storage. The S also has the 'mass storage mode' removed. Nice one Sony, give professionals another reason to avoid your products in the future...
I don't want to Flash the phone since any added files will start destroying the potentially recoverable data (plus I'd simply rather not format the phone if possible).
Is it possible to mount the internal storage of the Sony Xperia S as a drive so that I can run my PC based data recovery tools on it?
I imagine App Store apps are too lightweight to handle a file-based undeletion. If I could just see the device in my recovery apps I'm sure I'd be in business! I've attempted Recuva and R-Studio.

Doing some more research (like a good little n00b) I imagine I'm going to need SD Mounter.
I'm a little thrown off because 'SD' usually describes SD cards (of which the Xperia S has none). Also, the screenshots (for SD mounter) seem to indicate it's for ICS so I'm not sure if there's going to be a compatibility issue there.
Am I barking up the wrong tree by making this assumption? Should JellyBean have access to the mass storage and the option is simply not showing for some reason? Anyway, I'll continue working under my assumptions until someone suggests otherwise...
To get SD Mounter running, I'm going to need BusyBox. The problem is, I'm trying to read the BusyBox installation FAQ, and I'm finding it very vague. Like...
and save it under the name "busybox"
Click to expand...
Click to collapse
but it does not specify WHERE. Make a folder called 'busybox' on the root folder of the phone? Somewhere on my PC (the page suggests its for the PC rather than the phone)? Also I'm seeing Linux-looking command lines, but I'm on a PC... can I run this via the command prompt in Windows? I downloaded the 'binaries' like it said, but there aren't any executables in here...
Can anyone shed some light?

There's an app called BusyBox Installer, that installs it correctly on my Xperia S. That SD Mounter app works perfectly on 4.1.2, though. I use time to time. It just messes up a bit with Media Scanner, requiring me to do a reboot on the phone to make it work again.
I wish you lot of luck trying to recover your files. I once tried something like that, but came unsuccessful. There were some media I wish I had saved, but it wasn't THAT important, so I just gave up.
Suggest to your friend, though, to get an account on Mega, Box.net or Dropbox. All of them has auto backup of camera media to the server. All of them has options to backup only on WiFi, and even when charging only. The first two has 50 Gb of free storage for life (Box, you just need to sign with your Xperia device), and the later only 2 Gb, but you can get more and more with promotions.
Alternatively, he can enable the Google+ Auto Backup. There is 15 Gb (shared with Gmail and Google Drive) for pictures on original resolution or unlimited on 2048px, compressed. On Google+, though, you have the Auto Awesome, which make some awesome images.
Hope it helped. If I can help any further, just tag me
Sent from my LT26i using Tapatalk

Hey Felimenta97, thanks for your swift response!
Felimenta97 said:
There's an app called BusyBox Installer...
Click to expand...
Click to collapse
I see 'BusyBox Installer' in the Play Store, is that the one? Seems strange that the Play Store would add an app that requires rooting. Just wanna make sure I shouldn't be looking for it somewhere else (plus I'm away from that phone at the moment)
Felimenta97 said:
It just messes up a bit with Media Scanner, requiring me to do a reboot on the phone to make it work again.
Click to expand...
Click to collapse
That's okay. I've warned them this process might even brick their entire phone. They are prepared (I hope) for complete loss/compromised apps
Felimenta97 said:
...I wish you lot of luck trying to recover your files. I once tried something like that, but came unsuccessful...
Click to expand...
Click to collapse
*touches wood*. Gah I'm suddenly 10 times less confident this file recovery is gonna work. Wish me luck! They'll be crushed if I can't get their media back...
Felimenta97 said:
...get an account on Mega, Box.net or Dropbox...
Click to expand...
Click to collapse
Oh trust me, I've already given them the lecture
Thanks for your help!

TheWaste said:
Hey Felimenta97, thanks for your swift response!
I see 'BusyBox Installer' in the Play Store, is that the one? Seems strange that the Play Store would add an app that requires rooting. Just wanna make sure I shouldn't be looking for it somewhere else (plus I'm away from that phone at the moment)
That's okay. I've warned them this process might even brick their entire phone. They are prepared (I hope) for complete loss/compromised apps
*touches wood*. Gah I'm suddenly 10 times less confident this file recovery is gonna work. Wish me luck! They'll be crushed if I can't get their media back...
Oh trust me, I've already given them the lecture
Thanks for your help!
Click to expand...
Click to collapse
As I'm a lazy person, who can't find a way to break quotes into multiple parts (serious, how do you Do that, without having to write the quote code every time? It is not much, but I'm really lazy, so yeah.
Yep, that's the app. There's no reason for Google to block root apps. It's a function of the OS itself, just hidden from users. It's one of the easiest things to do on a Nexus device, after all. It's hidden because, if used without caution, can soft brick your device. But, don't worry, that shouldn't do any harm. At it least it hasn't with my device until now haha
As I said, I had already lost lots of stuff, and I didn't bothered much to go any further to recover it. It was a simply Install Recuva, run on the SD card and see if I could restore anything. Nothing? OK, no worries. As you already mentioned in your first post, avoid at all costs writing new files to the SD Card partition.
About the lecture, yeah, I imagined you had already told them, but it doesn't hurt to tell anyway.
About the SD Card on the Xperia S, another technical info you might or might not know, and also doesn't hurt to tell. Until Android 2.3, devices with a big internal storage required a partition for cache, one for data (apps and their own data), one for system, and one SD Card. The last one in Fat32 (plus others, but those are just too small and insignificant, for most, anyway) Think of a normal hard drive with plenty of partitions. Since Xperia S was developed (and launched) with 2.3 (one of Sony's biggest mistakes with this phone), it had to follow those "guidelines".
With Android 4.0 and beyond, the above mentioned data and SD Card turned into one partition, in Ext4 format. That data partition stores both apps and their data, and also other types of media, like media, documents, and etc. That storage goes into a mounted folder.
Anyway, again, wish you good luck. If they aren't very close friends/relatives, you should charge some money for all the hassle if you recover haha
Sent from my SGP311 using Tapatalk

Felimenta97 said:
how do you Do that, without having to write the quote code every time?
Click to expand...
Click to collapse
Haha, actually I still kinda do. #hen I hit 'reply' I empty the quote block, copy the empty quote block a few times, then copy-paste the parts of the text I'm replying to as I go
Felimenta97 said:
avoid at all costs writing new files to the SD Card partition.
Click to expand...
Click to collapse
Yeah absolutely.
Felimenta97 said:
Until Android 2.3, devices with a big internal storage required a partition for cache, one for data (apps and their own data), one for system, and one SD Card
Click to expand...
Click to collapse
Jeaz. Thank god I don't have to eff around with that!
Felimenta97 said:
With Android 4.0 and beyond, the above mentioned data and SD Card turned into one partition, in Ext4 format. That data partition stores both apps and their data, and also other types of media, like media, documents, and etc. That storage goes into a mounted folder.
Click to expand...
Click to collapse
I don't need to re-format the internal storage of the phone to attempt recovery do I?
Thanks again Felimenta!

TheWaste said:
Haha, actually I still kinda do. #hen I hit 'reply' I empty the quote block, copy the empty quote block a few times, then copy-paste the parts of the text I'm replying to as I go
Yeah absolutely.
Jeaz. Thank god I don't have to eff around with that!
I don't need to re-format the internal storage of the phone to attempt recovery do I?
Thanks again Felimenta!
Click to expand...
Click to collapse
Not in Xperia S case. As I said, it is on Fat32, so it is easily mount-able on Windows.
On any phone with Android 4.0 or more, you'd need a Linux to do the recovery. You can't format it, or else you will turn the device into a really expensive paperweight.
Sent from my SGP311 using Tapatalk