Unable to write to ums lunfile (No such file or directory) - myTouch 3G, Magic General

Hi every:
Recently and I don't know why my sdcard leave working as usual. I try to mount from recovery and get this message:
E:Unable to write to ums lunfile (No such file or directory)
Click to expand...
Click to collapse
So I don't know how to solve it. I try to read the SD in another phone and it reads OK without problem so SD isn't the problem, also I did format from Windows as FAT32 but still having the same problem, any help on this? It's possible it's a SW problem or it's HW problem? I'm freaking out

I have the same problem.
any solution?

I got the same problem, but I noticed my s off was now on too, I have the files to turn it back on from UNREVOKED through CWM or even flash back to stock image but I'm concerned this may brick my device as I'm not the most experienced user, any tips,knowledge or warnings before I try would be appreciated.

I'm having the same issue trying to reload my recovery mostly trying to get into recovery to instally my gummy rom. I cannot access my sd card via cwm 3.0.0.8 on my droid charge gummy charged 2.1 rom. Please help!

Ok, finally and after a deep, long, tedious Google search I found a solution, at least for me works and for now my memory and my phone are OK. Here is the steps:
1. If you have any recovery rename it to recovery.img and copy to the folder where you have fastboot.
2. Extract your SD and run this command:
Code:
fastboot.exe -c board_sapphire.disable_sdcard=0 boot recovery.img
3. Insert SD again
4. Run this command from adb shell
Code:
#mount /sdcard
Run as many times you need in order to get SD mounted.
This works for me so good lock for every of you that have the same problem as me in the past

Related

Hero's Kryptonite?

I tried to flash the Hero rom by partitioning my stock micro sd (the 1 that came with the phone)
...yeah i know it says not recommended but my 16gb card is being mailed and i couldnt wait.
anyway...now it will show the boot image and play the sound and then it will just be a black screen and wont go any further.
would i able to salvage this when my 16 gig card comes somehow?
could i flash back to an older rom? is the app_s folder in the ext partition going to interfere with that at all?
Please help!!!
Unbelievable
CC CEO said:
I tried to flash the Hero rom by partitioning my stock micro sd (the 1 that came with the phone)
...yeah i know it says not recommended but my 16gb card is being mailed and i couldnt wait.
anyway...now it will show the boot image and play the sound and then it will just be a black screen and wont go any further.
would i able to salvage this when my 16 gig card comes somehow?
could i flash back to an older rom? is the app_s folder in the ext partition going to interfere with that at all?
Please help!!!
Click to expand...
Click to collapse
i would recommend to go back to your backup (you did do a backup right?)
just flash the data, system, and boot .img files back
since you're doing Hero im guessing you have the newer SPL
you might run into a roadblock trying to fastboot so if you cant get the fastboot to work then boot into recovery mode and then go into a command prompt and run the following:
adb shell
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
Click to expand...
Click to collapse
this will let you access your memory card
get the HardSPL from here
copy it into your card as "update.zip"
now apply the update with ALT+S
after its done you can reboot back into the bootloader with ALT+X and typing
reboot bootloader
Click to expand...
Click to collapse
now you should be able to flash you backups like usual
nope didnt make a backup...i know..
but...
i was able to format my sdcard back to its original state and i flashed google ion back on the phone. question is are there any lingering affects to the phone itself? in setting up the ext2 or anything on the stock card might i have pushed or pulled something i shouldnt have from the internal storage if i didnt create a backup??
if so. how would i fix this?
if you Alt+W'd the phone there wont be any lingering effects,,,, its wiped and wont bother you no sunder!
I was having the same problem as you, as I too am only using the stock 1gb sdhc that came w/ the g1.
just did searching on here and I got it up n running.
I'm thinking maybe you did like me and pushed the /app_s/ folder while the SD was mounted to your pc, this is what I am guessing was my issue.
I've come to that conclusion since I've done the push w/o mounting the SD
Also I found that I had to be in the app_s folder on my computer to push it right, at first I was pushing it and it was going into /system/sd/app_s/app_s
Here's Haykuro's original instruction's
Installation:
1. Download http://www.droiddeveloper.com/hrbuilds/app_s.zip
2. extract "app_s" into your sdcard's ext2 partition.
3. Download http://www.droiddeveloper.com/hrbuilds/hero-signed.zip
4. Place on regular sd card.
5. Reboot into recovery, wipe and flash.
6. Enjoy.
--
for step 2... make sure you are in the actual app_s folder when you do the following command and make sure the sd card is NOT mounted.
adb push app_s /system/sd/app_s
--
follow the rest of the instruction's as stated and you should be fine.
now, to get it running smoother...
follow the tutorial here...
http://forum.xda-developers.com/showthread.php?t=521251
also within the thread there's tip's on moving the Rosie.apk along w/ widget's to internal memory, I just focused on the larger widget's, the largest being the weather one.
hope this help's.
just one noob tryna help another noob out ;-)
please help
When i am doing the update.. i am getting this error.. .
E: Can't chown/mod /system/xbin (not such file or dir)
E: Failure at line 12: set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin
installation aborted."
please help!!

Cannot Get Phone To Start Anymore

So today i rooted my phone installed JF1.41, i partitioned my sd card IN MY G1, since i have a mac and for some reason it wont partition the card right. Then i did the apps2sd deal... Then i wanted to use a theme, well that screwed everything, and it wouldnt get back to normal or even start again. So completely formatted my card, which now has NO PARTITIONS(i guess just 1), and i think the phone is trying to read files on a partition that dont exist now, and NOTHING is working. Anyone on here that can help? I am rather smart with this stuff, but really am going to need someone to help me. I need my phone tomorrow.
Thanks.
How did you reformat your sdcard? Did you check in parted to see that you in fact only had 1 partition again? I suggest you flash a new updated ROM like Cyanogen 4.2.5. That has apps2sd script built into the rom. It will do it automatically so you don't have to mess with all that.
ok ill try it right now and see
I know FOR SURE i dont have a 2nd partition cuz i formatted it with only 1
illthinking said:
ok ill try it right now and see
I know FOR SURE i dont have a 2nd partition cuz i formatted it with only 1
Click to expand...
Click to collapse
you're going to need a second partition for apps2sd to work. I suggest you do that first before you flash a rom, or else you will just have to end up reflashing.
Ok Downloaded Cyanogen4.2.5
This is the problem i keep having when i try to apply the update it say
Installing from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount SDCARD:update.zip
Installation aborted.
So i think it has to do with the fact it wants to read /dev/block...etc from the partition of the sdcard that is now non existent
problem is i have a mac and cant properly fromat the 2nd partition (ext2)
unless you know of a way
the way i first did it was using some code i got off of here to have the phone do it itself... now that i cant start the phone i cant do the partition
what recovery do you have? I suggest you put this one on your phone.
http://forum.xda-developers.com/showthread.php?t=566669
It partitions your sd card for you.
Also for Cyanogen, you need to flash the htc OTA update one, then flash his update for those to work.
ok...
so i found some plugins for the new Snow Leopard OS for mac called MacFuse 2.0 along with its counterpart fuse-ext2 and i partitioned my card
you might want to upgrade to ext3. it's faster than ext2 and runs smoother
just tried to flash the recovery found here
http://forum.xda-developers.com/showthread.php?t=566669
with no avail and tried to start the phone(power+camera) and said no image
heres what it said for the recovery
/ # mount -a
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: Invalid argument
mount: mounting /system/modules/modules.cramfs on / system/modules failed: No such file or directory
mount: mounting /system/xbin.cramfs on /system/xbin failed: No such file or directory
I mean, what i want to know is how to build the file format back on my sd card so itll work, or build it so it will look on my actual phone... People put up the code to have it switch where it reads things from, there MUST be a way to switch it back manually as well
Use fastboot and write the recovery image
here's a link to fastboot
http://developer.htc.com/adp.html
then when thats running plug in your G1 and turn on holding Power and camera when the screen turns on you might have to press back to enable FB but once its enabled type in terminal
Code:
cd *where ever your recovery image is*
fastboot flash recovery *recoveryname*.img
reboot
can someone hook up a quick step by step on how to hook my phone up fastbooted? I have a mac and i can get the phone to say fastboot, but im lost after that... If you want to reroute me to a different thread, please verify that it REALLY has the info before posting it.
i have been trying to find the name of the device and im getting
/dev/tty.Bluetooth-Modem as the device name, but a Permission Denied thing... now i cant just go click something in the phone menus, since i cant get the phone to start, so is there a way to get permissions through the Terminal application?
that error you get when you type mount -a is normal continue as instructed:
flash_image recovery /(whatever your recovery image is called)
if you have adb you could try parted /dev/block/mmcblk0 and type print to see your parttitions.
so i can get it to say it flashes the recovery, but still not starting
so when i try to do any updates it says SDCARD wont mount
any input?
Looks like im going to go for a broken record, until SOMEONE can help me figure my phone out... I need to get it running, and i know someone can figure it out

SD Card Problem with Kyrillos' ROM v3.3 Extreme Edition

Hello, I have a Problem with my SD Card after I Partitioned the SD Card with
mad_team_app2sd app and restarted my Phone I tried to fix it as said in the thread
2open adb or terminal emulator and type the commands.
adb shell (if you are using terminal emulator type "su" instead of "adb shell")
mkfs.vfat /dev/block/mmcblk0p1 (and wait ~30 secs)
Click to expand...
Click to collapse
but that doesnt worked out for me, I got this error message:
mkfs.vfat: can't open "/dev/block/mmcblk0p1": Permission denied
Click to expand...
Click to collapse
can anybody help me please?
btw: sry for my bad english: i'm from austria
also when i enter recovery mode it says in red letters
E: Can't mount /dev/block/st18 (Invalid Argument)
E: Cant't mount CACHE:log/recovery.log
E: Can't open CACHE: log/recorery.log
E: Can't mount /dev/block/st18 (Invalid Argument)
Click to expand...
Click to collapse
please help i dunno what to do
Hi,
The second error you can ignore. I have it all the time when flashing.
What's the problem with your SD ? Can you view anything on it ?
What does mount tell you in adb shell ?
no i cant see anything on it,
dunno what you mean with Mount in ADB Shell, dont have a linux pc
help please, I'm getting pretty frustrated since i Cant get it to work
are u trying form pc using ADB or from mobile using Terminal Emulator??
if ur using ADB then type -"adb shell"--Without quotes
If ur using terminal emulator(inbuilt to rom) type-"su"
Make sure there is space b/n "mkfs.vfat" and "/dev/....."
wait till # comes to next line then type reboot
I tried this, about several thousand times but i always geht this error:
mkfs.vfat: can't open "/dev/block/mmcblk0p1": Permission denied
have u checked whether u have rooting permissions and did u flash the rom WITH SD CARD INSIDE THE PHONE????
is ur sd card working otherwise??
yes i flashed the Rom with the SD Card inside the ROM, i just removed the sim as i flashed the ROM
other Root Apps work fine, so i would say I have rooting permission.
the SD Card is working fine right now, but its not Partitioned right now, and i want to change that.
should i flash new and remove the SD Card first?
Try reflashing and if you are using mad team app2sd you don't ned to keep the sd card inside while flashing.. It doesn't make any difference though.. Reflashing should work for you.. Good luck
i reflashed, about 10 times now, but the Bug doest go away,
anybody a Idea?
Format ur card from settings>sd card> eject and format
and check if ur card is working
Sent from my GT-I5800 using XDA App
my SD Card is working fine, no problems, also formated it a couple of times now,
the bug still persists
extract the adb folder in the zip file to C drive on your machine
Enable USB debugging on your phone
Connect the phone through USB (Make sure that G3 drivers are installed)
Open command prompt , go to c:\adb by command "cd c:\adb"
type "adb shell"
You will see a $ with blinking cursor after it
type "su" (it should ask for superuser permission access on your phone)
Once granted you will see # and blinking cursor behind it
Then type your command
WoW! Thanks mate, you saved my day, It finally worked!!!!
Thanks! Thanks! Thanks!

help with root i9020a

hi can i have some help?
stuck on the adb push part, cmd window says failed to copy ____ to _____ read-only file system.
any idea how to fix this?
(from step by step rooting guide for 9020a)
I assume you mean the "adb push su-2.3.6.1-ef-signed.zip /sdcard/su-2.3.6.1-ef-signed.zip" part. Maybe you forgot the /sdcard at the beginning, otherwise no need to worry about adb anyway. Just copy that file over to the sdcard by any means you like (adb, mount usb storage, etc).
However, i would be using a newer su zip from the official web page, just to save hassle if you are using ICS. Guaranteed to work
If you have already flashed the recovery... easiest way is just to boot into recovery then mount the USB storage and copy it that way. Then unmount and flash the zip while still in recovery.
Sent from my Nexus S using XDA App
thanks for the help!
sorry to ask another question (first time rooting), but I can't find any sdcard folder after i go into usb mass storage?
and the new su zip will work on 2.3.6? (planning on using cm9)
New su works on 2.3.6 fine. Mount USB storage is the sdcard partition, so anywhere in there.

Restore Rom Install Failed (Simple Touch) Tried Everything - no Dice. Please Help :)

The Issue
Hi, I have a Nook Simple Touch that gets stuck trying to boot. First I see the Barnes and Noble Screen, Next for a brief moment it tries to load a Rom and shows a small nook icon with a loading bar. Next it says "Install Failed". I am unable to do anything other than a factory reset, which doesn't help.
Background
I should add that the device previously was working fine, then one day it froze as I was highlighting some text. When I tried to boot it, it was stuck in the scenario described above. I believe it was already updated to 1.2.2 with seemingly no issues.
What I've tried:
I have tried restoring it back with noogie and a backup, and I have also tried the Nook Manager- Rescue from .zip and Rescue from backup to no avail. Still get that same blasted "Rom Restore Image" Screen followed by "Install Failed".
I have an update from Barnes and Noble called "nook_1_2_update.zip" which I tried to copy over to the nook but the file is too large.
Any ideas? I love this thing and don't want to let it go!:crying::good:
I guess You can insert an SD card with NookManager back and boot properly?
If so lets connect to Your nook via ADB, mount /boot partition and prepare copy of its files.
Code:
mount -o rw,remount rootfs /
mkdir boot
mount -t vfat /dev/block/mmcblk0p1 /boot
[B]...
copy files inside boot partition from
...[/B]
mount -o ro,remount rootfs /
umount /boot
Then put this exact copy onto new (vfat formatted) SD card, and try to boot from new card.
Let us know whats happen.
Is this booting from new SD, showing same fail screens?
Thanks so much for the assistance! I will give it a try and report back.
Also , to note, I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Trigrammaton said:
... I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Click to expand...
Click to collapse
Im not quite sure. Another version, etc...
You can use NST boot partition image from this post
For preparing another booting SD card too...
Trigrammaton said:
Thanks so much for the assistance! I will give it a try and report back.
Also , to note, I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Click to expand...
Click to collapse
If you restore the image from a different device the serial number, MAC address, etc. will be messed up. You will never be able to register the device. This may not be an issue, but just so you are aware.
nmyshkin said:
If you restore the image from a different device the serial number, MAC address, etc. will be messed up.
Click to expand...
Click to collapse
The serial number is written inside the little door for the SD card (if you haven't worn it off).
The serial number and the MAC are also on a sticker in the inside.
ucy74 said:
I guess You can insert an SD card with NookManager back and boot properly?
If so lets connect to Your nook via ADB, mount /boot partition and prepare copy of its files.
Code:
mount -o rw,remount rootfs /
mkdir boot
mount -t vfat /dev/block/mmcblk0p1 /boot
[B]...
copy files inside boot partition from
...[/B]
mount -o ro,remount rootfs /
umount /boot
Then put this exact copy onto new (vfat formatted) SD card, and try to boot from new card.
Let us know whats happen.
Is this booting from new SD, showing same fail screens?
Click to expand...
Click to collapse
Ucy - It boots from nook manager and I am able to use that utility just fine without the failed rom screen. What do you mean by "new" sd? If i put a blank sd into the slot and boot?
When you talk about ADB above and using that - I just download the sdk then use the code you pasted above to copy over the boot partition you linked to my nook (not sd) and try booting like that, correct?
Thanks! I can figure things out with a little guidance, I'm just not really well versed on some of this. Appreciate your help very much!
Trigrammaton said:
Ucy - It boots from nook manager and I am able to use that utility just fine without the failed rom screen.
Click to expand...
Click to collapse
Super, it means so You can connect to Your Nook and dump boot partition files to PC using ADB.
What do you mean by "new" sd? If i put a blank sd into the slot and boot?
Click to expand...
Click to collapse
You can copy files dumped above onto vfat formated SD card. Then try to boot from this "new" - freshly prepared card. Check whats happen.
When you talk about ADB above and using that - I just download the sdk then use the code you pasted above to copy over the boot partition you linked to my nook (not sd) and try booting like that, correct?
Click to expand...
Click to collapse
NOT SO FAST!!! Do not put linked partinion into nook! There are different cases and commands to do that. If You are new to ADB lets try to dump boot partition first, as mentioned before. Maybe there will be not necessary to replace whole partition rather than single file.
Thanks! I can figure things out with a little guidance, I'm just not really well versed on some of this. Appreciate your help very much!
Click to expand...
Click to collapse
Prepare this dumped SD first. We try to heal it to make bootable...
Thanks! I will give it a whirl this weekend and report back. Really appreciate you taking time to respond - Very kind of you!

Categories

Resources