I've got a problem where I'm unable to access my SD card from Amon Ra 3.15. When I try and open it from the Flash menu, I get an empty directory. When I try and USB mount it, Amon Ra acts normal, but no computer recognizes that there's a USB storage device connected.
This hasn't been an issue for me much in the past because I just put anything I need to flash on internal storage. But right now, I'm wanting to be more active in the weekly ROM flashing, and would like to be able to make nandroid backups.
I'm not sure if this is an "I didn't format my SD card correctly" issue or an HBOOT version issue, or an "I didn't follow all the directions when I did the S-OFF wire trick" issue
Vigor PVT SHIP S-OFF
HBoot 2.27
Thanks for the help.
I've got a similar issue.
Whenever I go to sd card in recovery all I find is lost.dir.
Unlike the op, I can find the sd card using astro, file explorer or computer, which makes me think it's not a format issue.
The only other odd thing I've noticed is that I cant save a picture sent to me through go sms. It gives me an sd card error.
Sounds like the sdcard is not mounted. Try mounting it in the amon ra menu.
Sent from my Rezound using Tapatalk 2
Probable format issue
dbighead77 said:
I've got a problem where I'm unable to access my SD card from Amon Ra 3.15. When I try and open it from the Flash menu, I get an empty directory. When I try and USB mount it, Amon Ra acts normal, but no computer recognizes that there's a USB storage device connected.
This hasn't been an issue for me much in the past because I just put anything I need to flash on internal storage. But right now, I'm wanting to be more active in the weekly ROM flashing, and would like to be able to make nandroid backups.
I'm not sure if this is an "I didn't format my SD card correctly" issue or an HBOOT version issue, or an "I didn't follow all the directions when I did the S-OFF wire trick" issue
Vigor PVT SHIP S-OFF
HBoot 2.27
Thanks for the help.
Click to expand...
Click to collapse
It could be a format issue. The newer ROMs will read NTFS, xfat and other formats. Amon Ra and other recoveries will only read fat 32 formatted devices.
Related
So I htcdev unlocked. install amon ra, then I used nanbackup, then i install RezROM ICS
now i need to restore
and according to this post
http://forum.xda-developers.com/showthread.php?t=1447432
I need to flash the original PH98IMG.zip from the bootloader. I however don't know how to get PH98IMG.zip on my internal sdcard. I dont have access to android. or and sdcard adapter
so how can i do this
is there an adb command perhaps that will allow my to push the PH98IMG.zip to internal storage... Please help
boot into recovery. you can copy that to the sd card while it is in recoery
in recovery connect your phone to the computer and put the original PH91IMG.ZIP in the same folder as your adb.exe then run "adb push ph91img.zip /sdcard2/" without quotes. im not 100% sure of if thats it but if not just ask and ill test it till i figure it out still somewhat a noob haha
Also, correct me if I'm wrong, but will the phone read from the internal SD? I thought it only looked on external?
You are correct, you'll want to make sure that it's on the external sdcard (sdcard2).
I usually use either amon ra to mount the external sd card to Windows, or use adb to push. I usually find adb push to be my method of choice.
Also, I've found sometimes that when using the adb push command, you may need to first mount the external sd card in the mount menu in amon ra. For the sake of ease, I recommend just turning on use mass storage on the external card through amon ra.
I tried flashing the new ICS leak (3.11.605.22), somewhere in the process I messed it up. I flashed the RUU then I flashed CleanROM 4.0. the ROM booted up fine, however I cannot access internal or external storage (sd card). AmonRa recovery could read my SD card. I think I need to reflash the RUU, however fastboot wont read the PH198IMG.zip off my sd card. I tried flashing the PH198IMG.zip using adb, however I keep getting an error (FAILED (remote:not allowed)) and I'm not very good with adb. Long story short I guess I need help returning my phone to stock even without using an sd card, or any other work around would be helpful.
xarmorx said:
I tried flashing the new ICS leak (3.11.605.22), somewhere in the process I messed it up. I flashed the RUU then I flashed CleanROM 4.0. the ROM booted up fine, however I cannot access internal or external storage (sd card). AmonRa recovery could read my SD card. I think I need to reflash the RUU, however fastboot wont read the PH198IMG.zip off my sd card. I tried flashing the PH198IMG.zip using adb, however I keep getting an error (FAILED (remote:not allowed)) and I'm not very good with adb. Long story short I guess I need help returning my phone to stock even without using an sd card, or any other work around would be helpful.[/QUOTR
Did u get Scott's Ph98 off the sd card, then put the leak ruu back on and relock to rerun ?
Click to expand...
Click to collapse
yes, i took scotts PH off and downloaded the RUU and renamed it to PH198IMG and put that on the SD card, however the bootloader doesnt find it.
well, I feel stupid. the file was named PH198IMG.zip. I renamed it to PH98IMG.zip and it found it. go figure.
xarmorx said:
well, I feel stupid. the file was named PH198IMG.zip. I renamed it to PH98IMG.zip and it found it. go figure.
Click to expand...
Click to collapse
yea, gotta name it right.
There's a patch to allow people who've run the ICS leaks to see their SD cards after returning to GB. Why is this necessary, and what does the patch do?
I ask because since S-off I've completely reverted to GB, and I'm still having problems seeing my SD, perhaps because it either had its format changed due to ICS, or because I previously applied the patch to the ROM I'm currently running.
cpurick said:
There's a patch to allow people who've run the ICS leaks to see their SD cards after returning to GB. Why is this necessary, and what does the patch do?
I ask because since S-off I've completely reverted to GB, and I'm still having problems seeing my SD, perhaps because it either had its format changed due to ICS, or because I previously applied the patch to the ROM I'm currently running.
Click to expand...
Click to collapse
It's probably more due to the s off process I've seen a lot of users with this issue who weren't on gingerbread also.
Take the data from your SD card and copy it to a folder on your computer. Wipe the card completely and format it in windows. Then put it in the phone and format it in Settings/Storage. then once you've done that put some stuff on it and see if it's being recognized. Finally you can copy all of your data over to the sd card again from the backup you made at the first step.
Yeah, I've got s-off, and I've reverted to GB OTA. But I've restored the ROM I was running on top of the ICS firmware, which must have the SD patch on it. So I'm trying to understand what's changed in order to navigate out of it.
In fact, I am already copying the files off so I can format the SD on another device. Something about great minds, I suppose...
Just wondering what's causing it, because I really don't know if the format's gonna help. Right now the phone doesn't even recognize the card from the ROM. Sees it fine in recovery though.
The mount points changed, if you had installed the patch to allow you to run a GB rom on the ICS firmware your mount points would be broken now. You should be able to flash the patch to allow you to run ICS on the old firmware and you should be good.
The patch just updates /system/etc/vold.fstab
So it looks like a device number associated with a drive is incremented. Apparently the ICS firmware reports this device at a higher number than the GB firmware, and so the GB won't see it unless fstab points to the correct index.
Since I'm on GB firmware now (thanks, s-off!) I can set the number back to the value in the GB RUU.
Having done that, my phone still does not recognize the card -- except in Amon Ra. Furthermore, the card was not recognized in an unmodified Droid X belonging to a co-worker. So something's wrong with the card, but it's not a clear failure.
I'm now running a FAT32 format from Windows, through Amon Ra, and I'm doing the full format rather than the quick version. Taking forever. We'll see. If this doesn't work, maybe I need to look for a card reader to format it.
Why might Amon Ra recognize the card, but not Android?
cpurick said:
So it looks like a device number associated with a drive is incremented. Apparently the ICS firmware reports this device at a higher number than the GB firmware, and so the GB won't see it unless fstab points to the correct index.
Since I'm on GB firmware now (thanks, s-off!) I can set the number back to the value in the GB RUU.
Having done that, my phone still does not recognize the card -- except in Amon Ra. Furthermore, the card was not recognized in an unmodified Droid X belonging to a co-worker. So something's wrong with the card, but it's not a clear failure.
I'm now running a FAT32 format from Windows, through Amon Ra, and I'm doing the full format rather than the quick version. Taking forever. We'll see. If this doesn't work, maybe I need to look for a card reader to format it.
Click to expand...
Click to collapse
HBOOT 2.21 simply mounts the "/sdcard" partition to a different EMMC block than previous 2.10/2.11 HBOOTs did. That is it. Its that simple. WHY did they make the change? I have no idea.
So, if you're on GB and you can't access your internal storage (/sdcard), all you need to do is simply flash an earlier HBOOT (2.10, or the 2.11 ENG HBOOT from the dev section) and make sure you're also using the corresponding GB radios. Then you have no more issues.
I have the 2.11 HBOOT and GB radios.
The problem is the External SD. I can share it between Amon Ra and Windows, but I can't mount it from Android. Android shows it unavailable. When I go to mount it, it briefly says, "Preparing SD Card," followed by a message telling me I can remove the SD card. The same thing is seen on multiple phones.
I did a long format, Fat32, from Windows 7 while the card was mounted in Amon Ra. I put a zip on the card and Amon Ra seems willing to flash it. I can definitely read and write it via recovery. But Android doesn't see it, and I think it's the card rather than my phone. Ideas? Anything I can do with partitions? Maybe there's something that can be "reset."
Each time I explore the card I find "lost.dir". I don't recall seeing that before.
cpurick said:
Each time I explore the card I find "lost.dir". I don't recall seeing that before.
Click to expand...
Click to collapse
Yup. Leave it alone. Been there all along, and not anything new. I've seen that directory going back to my Incredible two years ago, and I'm sure it goes back before that.
Try flashing the patch for gb firmware
Sent from my ADR6425LVW using Tapatalk 2
cpurick said:
I have the 2.11 HBOOT and GB radios.
The problem is the External SD. I can share it between Amon Ra and Windows, but I can't mount it from Android. Android shows it unavailable. When I go to mount it, it briefly says, "Preparing SD Card," followed by a message telling me I can remove the SD card. The same thing is seen on multiple phones.
I did a long format, Fat32, from Windows 7 while the card was mounted in Amon Ra. I put a zip on the card and Amon Ra seems willing to flash it. I can definitely read and write it via recovery. But Android doesn't see it, and I think it's the card rather than my phone. Ideas? Anything I can do with partitions? Maybe there's something that can be "reset."
Each time I explore the card I find "lost.dir". I don't recall seeing that before.
Click to expand...
Click to collapse
It was probably the formatting that did it. I would take it out, remove all partitions on it, and let the phone reformat it on its own.
cpurick said:
So it looks like a device number associated with a drive is incremented. Apparently the ICS firmware reports this device at a higher number than the GB firmware, and so the GB won't see it unless fstab points to the correct index.
Since I'm on GB firmware now (thanks, s-off!) I can set the number back to the value in the GB RUU.
Having done that, my phone still does not recognize the card -- except in Amon Ra. Furthermore, the card was not recognized in an unmodified Droid X belonging to a co-worker. So something's wrong with the card, but it's not a clear failure.
I'm now running a FAT32 format from Windows, through Amon Ra, and I'm doing the full format rather than the quick version. Taking forever. We'll see. If this doesn't work, maybe I need to look for a card reader to format it.
Why might Amon Ra recognize the card, but not Android?
Click to expand...
Click to collapse
I will tell you I tried hand editing mine and it would not take the changes no matter how many times I rebooted it. Flashed one of the patches and it worked like a charm. Don't ask me why, that was just my experience.
Okay so I have this htc rezound, it was running ICS when I got it but the guy formatted it so it was stuck in the bootmanager or whatever you call it. I flashed recovery and then flashed a file that was on the sd card already. It says im running android 2.3.4 now. It wont read my sd card or take pictures at the moment, says theres an error when I go into gallery and the sd card won't mount. I can't see it on my computer either. i want to put on scotts clean rom because the guy i bought it from said that it fixed his sd card problems. I'm not really sure what to do because I can't get any files onto the sd card if it won't mount. Any suggestions? And if he was already runnig scotts cleanrom do I need to update to ICS firmware or whatever or should I install it like I was updating from gingerbread?
EDIT: I also forgot to add that when i try it mount it just says "preparing sd card" then it says "sd card safe to remove" and i have tried two different cards.
Can you boot into HBOOT (power off the phone, pull the battery, replace it, and then hold down the Power+Volume down buttons) and let us know the information on that screen? that will tell you what HBOOT the phone is running as well as radios to see what RUU you can run to return the phone to stock.
Edit: A card reader or spare phone would be great to mount the Sdcard and place the needed files on it btw
Did you try doing the SD card fix? It will format your SD card unfortunately.
Yeah im in hboot now. it says ***tampered*** and ***unlocked*** at the top ad it says the hboot is 2.21.0000 and the radio is 1.22.10.0310r/1.22.10.0308r
and yeah i heard theres a way i can get files onto the sd card through fastboot or something? I don't have an external sd card thing for my computer but i may be able to use my brothers droid x to put files on it.
If you can get to your recovery you can mount your USB through it.
If you're having trouble because you have a PH98IMG on your zip preventing you from getting past the bootloader...you can pull your MicroSD halfway out and angle your battery in such a manner that the bottom contacts are touching but not fully in the phone.
You get past the PH98IMG check and then slide the SD card all the way in and then push the battery in. Voila.
i dont know if im doing it wrong or i just don't know how but i can't get it to mount in recovery either!
shakeandscream said:
i dont know if im doing it wrong or i just don't know how but i can't get it to mount in recovery either!
Click to expand...
Click to collapse
Do you have another SD card to check? It could be that your SD card needs to go through the SD card fix:
http://forum.xda-developers.com/showthread.php?t=1615418
yeah the second sd card wouldn't work either. and i have s-on so idk if that tut will work for me. i appreciate the help though!
EDIT: yeah I can't get busybox to install because it says my sd card is mounted or there isn't enough free space but it's empty and not showing up. so freakin confused haha
Are you still on GB or ICS firmware?
Did you try running a stock RUU and see if it fixes everything? Get the RUU.exe file and put your phone in Fastboot mode and run it. Yes this will basically wipe everything and restore you to stock. You have to have your bootloader re-locked too.
im not sure which firmware im on. I assume ICS because that's what the guy flashed it too before i got it but when i got it it was just in the hboot and it wouldn't boot up so he didn't have a rom on there. i haven't tried the ruu but i guess i could give it a go
What hboot version are you on?
I actually got it figured out but now my camera still won't work. It's giving me an error when I try to take pics that says its unable to save to sd card due to insufficient file permissions. Removing the sd card won't fix it and neither will reformatting the card
Hi folks. I had an unrooted Rezound. I used the HTC Dev site to get it to an unlocked bootloader. I installed the Amon-Ra recovery and used it to flash the Infection JB ROM. Now it boots into the white HTC screen, goes slightly darker white and doesn't move. I can get back into recovery but after some wipes to clear up problems, now I'm stuck. It won't mount the internal or external SD cards. I *can* boot into fastboot but when I try to push a different ROM, I get the message that it doesn't an android info file.
I think I might be okay if I can use flashboot to flash maybe an ICS based ROM but I'm not sure. It seemed the phone originally didn't like the 32 gig SD card in there (one boot prior to the flashing it said damaged SD card). I popped it out, put it in a USB card reader and formatted it to fat32. Recovery threw an error when trying to access the SD card to do the flashing of the Infection ROM so I just flashed it from the copy I had placed on the internal SD. I'm guessing I might have to flash a standard boot.img from flashboot and try things again?.
NapalmDawn said:
Hi folks. I had an unrooted Rezound. I used the HTC Dev site to get it to an unlocked bootloader. I installed the Amon-Ra recovery and used it to flash the Infection JB ROM. Now it boots into the white HTC screen, goes slightly darker white and doesn't move. I can get back into recovery but after some wipes to clear up problems, now I'm stuck. It won't mount the internal or external SD cards. I *can* boot into fastboot but when I try to push a different ROM, I get the message that it doesn't an android info file.
I think I might be okay if I can use flashboot to flash maybe an ICS based ROM but I'm not sure. It seemed the phone originally didn't like the 32 gig SD card in there (one boot prior to the flashing it said damaged SD card). I popped it out, put it in a USB card reader and formatted it to fat32. Recovery threw an error when trying to access the SD card to do the flashing of the Infection ROM so I just flashed it from the copy I had placed on the internal SD. I'm guessing I might have to flash a standard boot.img from flashboot and try things again?.
Click to expand...
Click to collapse
Try using the usb mount to access sdcard. you may have to reformat one if you have an extra one. Or format it prior to putting it in your Rezound. As long as you can access recovery you are not bricked.
dragonstalker said:
Try using the usb mount to access sdcard. you may have to reformat one if you have an extra one. Or format it prior to putting it in your Rezound. As long as you can access recovery you are not bricked.
Click to expand...
Click to collapse
Provided I can gain access to the SD card, what would be my next step? Flash an ICS rom?
When trying to access the internal SD from recovery, I get this error-can't mount /dev/block/mmcblk0p37 or mmcblk0p38. Invalid argument. If I try to flash anything from the SD card, it says that it is opening the package, gives another line and then kicks me right back to the recovery menu. From there, trying to pull up the external card leads to a blank directory unless I yank the battery and reseat the card (or potentially just reseating the battery). Does anybody have any ideas?
fixit if you are s-0n
Look around xda, or google and find/download RUU 3.14.605.12, which should be an *.exe executable file.
Use a md5 checksum utility to confirm validity, boot into fastboot, and run this RUU.
It should make everything OK again.
@Napalm
Format the sd card using your recovery.
If you still have it in its current state open the rom's zip file, copy out boot.img, and fastboot flash it. Then attempt booting like normal.
Thanks Michael and hi Snuzz! After doing more searching, I did notice an extra step in one of the roms I used. It mentioned about flashing the boot.img in hboot if S-On was true. For my rezound, yeah it's still S-on for me. When I get back to my main PC, I'll see what I can do. I really hope I can come back from it as I'm really looking fwd to upgrading from my Tbolt. The Rezound has such a nice camera and processor, I'd prefer not to have to go another route.
Oh my god. This is so horribly screwy. The problem all along.....it ws the stupid 32 gig SD card I was using. I put Rage 2.3 on a 16 gig card, tried to flash from that one and it worked perfectly. No need for the RUU. I'm happy I didn't need it because of this warning.
This will not work if you used the HTC Bootloader unlock tool. Your device must be fully stock with a locked bootloader or you must have S-Off
Click to expand...
Click to collapse
On the 32 gig card, the zip flash would go by very fast and then basically reboot the recovery. From there, well the thread covers that. As of right now, Rage 2.3 has booted and asking for initial setup info. Since Rage is going to be my first ROM on this device, anybody have any thoughts on it or comments on another they like more?