[Q] can't mount sdcard from AmonRA recovery - Desire Q&A, Help & Troubleshooting

Hello Desirers,
i have had the HTC Desire for a whole year now, i did root it long time ago via Unrevoked 3, and installed the Amon-RA recovery.. and installed LeeDroid 2.2 by then, then made a full wipe some monthes ago and installed LeeDroid 2.3d.. and all went well.. i never had any problem with flashing a zip from the recovery or roms.
yesterday i downloaded the new LeeDroid2.41 rom, to install it.
When i went to Rom Manager to make a backup (my 1st time to use it to backup, thought to use it instead of the usual nandroid backup + from the AmonRA recovery menu... it went okay during the backup (with the different backups...etc) till the restart at the end and it gave me the white flash "HTC" screen and kept on restarting... and that's it.. nothing else happens.. i hadn't install anything new .. i was just backing up stuff.
Note that the HBOOT menu appears normally.. i can go to recovery.. to anything okay.. but can't boot the normal system that was just working and stable.
anyways so i thought to go to recovery and flash the new LeeDroid for that may fix whatever is wrong... but when i go to AmonRA menu and select to flash a zip it tells me :
E:can't mount /dev/block/mmcblk0p1
no such file or directory
E: can't mount /sdcard
Click to expand...
Click to collapse
though the sdcard is working on windows, i tried to restart, to remove the sdcard and insert it again, another sdcard (all gave the same result)... when i choose "Mounts" menu from the AmonRA menu and choose to "mound sdcard" it gives me the same error message.
now the brick is that i can't do anything.. can't change the recovery, can't install a new room or whatever, can't restore it to factory settings <install the original rom> ... because all needs sdcard. and i can't reach my original leedroid rom that was working because the phone keeps on restarting after the white screen.
what's wrong with the sdcard matter anyways ?
=-=
i really hope this shout reaches anyone who can help me, i am phoneless since yesterday Sad
=-=
regards

hi,
did you try this command?
you should have adb installed on your computer the TUT there or use thos one from xda http://forum.xda-developers.com/showthread.php?t=696189
Code:
open a cmd line (hit win key+r) and type cmd + enter)
1) Type in your command without quotes
“fastboot oem enableqxdm 0”
2) Once done reboot ur device
3) Your SD card must be recognized now.
hope this help U

You thought of it as a USB brick? You could use the tutorial to try fix it. Or it could be the bootloader (doubt it) or something else. Can the SD be read in the bootloader?
Sent from CM7

fragargon said:
hi,
did you try this command?
you should have adb installed on your computer the TUT there or use thos one from xda http://forum.xda-developers.com/showthread.php?t=696189
Code:
open a cmd line (hit win key+r) and type cmd + enter)
1) Type in your command without quotes
“fastboot oem enableqxdm 0”
2) Once done reboot ur device
3) Your SD card must be recognized now.
hope this help U
Click to expand...
Click to collapse
Just fixed it... i think the problem erupted because i have AmonRA recovery and used Rom manager (Clockwork mod recovery based) .. there were several reports that this may cause a usb brick. ... any way... i searched for how to unbrick it.. and used a clone cd from modaco ((Tinycore.img)) which is linux based to boot from it (with phone connected to fastboot usb) .. and entered the following commands :
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
cd /mnt/cdrom/root
/mnt/cdrom/root/fastboot oem enableqxdm 0
Click to expand...
Click to collapse
and it enabled the sdcard... i checked the sdcard workability from the recovery (i hadn't format it yet) then thought : WTH, why not to try and restart the phone to see if it will log in normally .. and it did (naturally because the sdcard block was the thing that prevented it from booting from the very start)...
so now it's working ... on the old LeeDroid 2.3d ... gonna do an AmonRA nandroid backup 1st thing... then why not to try to upgrade to LeeDroid 2.41 ;D... if anything goes wrong you will find me back here screaming and kicking like this morning ...
ain't that the beauty of Android ?
=-=
Thanks for ur replies guys
Orion

Related

USB Brick and brick sdcard, please help

USB Brick and brick sdcard, please help
Hi
Maybe giving a bit more detail about what happened to get the usb/sd bricked would help people to reply you
My device is connected to the PC does not recognize the Android and the recovery. currently no driver error: "Qualcomm CDMA Technologies MSM"
(Sorry for my English which should not be used goolge translate)
Do you have ROOT??
I unbricked my Desire yesterday so I know how to do it (only with ROOT).
Just download the correct RUU for your region from one of the post in this forum. Connect the USB cable, run the RUU exe and it flash your phone back to the OTA ROM.
I was put on the original room and then proceed boot, successfully run the STEP1, STEP2, but to the error can not enter the recovery
yolkie said:
Just download the correct RUU for your region from one of the post in this forum. Connect the USB cable, run the RUU exe and it flash your phone back to the OTA ROM.
Click to expand...
Click to collapse
Rom I downloaded OTA and it still can not root, and do not receive equipment, including sdcard
Maybe have a look here: (good q+a)
http://forum.xda-developers.com/showthread.php?t=749551
edit: also to this usb brick fix:
http://forum.xda-developers.com/showthread.php?t=691639
with kind regards..Alex
yolkie said:
Just download the correct RUU for your region from one of the post in this forum. Connect the USB cable, run the RUU exe and it flash your phone back to the OTA ROM.
Click to expand...
Click to collapse
His computer don't have connection with phone. It's BRICK, so how he can use RUU?????
lanh_lung do you have ROOT(modified recovery)???
edit: also to this usb brick fix:
http://forum.xda-developers.com/showthread.php?t=691639
with kind regards..Alex[/QUOTE]
My Desire is: T-Mobile have to follow steps on it?
lanh_lung said:
edit: also to this usb brick fix:
http://forum.xda-developers.com/showthread.php?t=691639
with kind regards..Alex
Click to expand...
Click to collapse
My Desire is: T-Mobile have to follow steps on it?[/QUOTE]
Champion ... no matter if your Desire is or not operator ...
Had the same problem and I was able to retrieve the roles of USB and SD Card making the procedures described in the tutorial past links above ...
Read carefully and make with calm ...You'll see that it is not as difficult as it sounds!
Good luck!
lanh_lung do you have ROOT(modified recovery)???[/QUOTE]
step2 I can not run because of the driver error: "Qualcomm CDMA Technologies MSM"
lanh_lung said:
USB Brick and brick sdcard, please help
Click to expand...
Click to collapse
it's very strange, I have exactly the same problem since yesterday!
SD Card brick is resolved by this command in fastboot mode :
fastboot oem enableqxdm 0
But USB Brick is not resolved and my phone no longer root how can I do? I tried unsuccessfully Z4 root, is there another software to root without USB?
My capital is very little English, I did follow the instructions at the link:http://forum.xda-developers.com/showthread.php?t=691639. But it is not possible, please provide detailed guidance and may include images is very good.
(Each charge to just plug the cable and reboot the machine to receive a new charger)
Hi, I had the Same Problems some Minutes ago. (I was using the new AmonRA Recovery to flash a new ROM).
Here are the Steps what I have done to solve my problem (Rooted ROM is required):
1.) Download Android SDK -> Then open a comand Line and change into the Tools Directory:
cd path\to\AndroidSDK\tools
2.) You need to know your CID.
Turn your Phone into fastboot mode (Pressing Back and Power On). Then in your Comand Line do:
fastboot oem boot
The log will say something like the following:
CODE
.
.
.
#INFOCID is T-Mob101
In this specific case, the CID is T-Mob101.
3.) Get and extract the the attached Rescue.zip File.
Open the File "misc.img" in a hex Editor of your Choice and change "T-MOB101" to your CID
3.) Turn your Phone again into fastboot mode (Pressing Back and Power On) then go to your Command Line and do:
fastboot oem enableqxdm 0 (This will enable your SD Card to be seen in your favorite explorer on your phone)
then "Reboot"
4.) Then get the two files to your SD-Card (email them or dropbox them or what ever).
5.) Open a Terminal Emulator (http://www.appbrain.com/app/android-terminal-emulator/jackpal.androidterm) on our Phone
enter:
su (Enter to get Superuser Rights)
cat /sdcard/flash_image > /data/flash_image (this will copy the file to /data, therefore you need root!)
cat /sdcard/misc.img > /data/misc.img (this will copy the file to /data, therefore you need root!)
chmod 755 /data/flash_image (this makes the file "flash_image" executable)
/data/flash_image misc /data/misc.img (this will execute flash_image the result will be that you overwrite your misc section)
Reboot.
Everything should be ok
Ok this is a bit weird cos my usb got bricked yesterday too but a lot of searching i have managed to get it sorted. i lost root too so used this method http://forum.xda-developers.com/showpost.php?p=9056719&postcount=15 its similar to the above but for people who have lost root.
I've already re rooted and back on my leedroid2.2b
Guys can i just ask if your usb got bricked after you s-offed your desire and upgraded to the new amon ra recovery
I "S-OFF'ed" my Device some Time ago without any Problems. Today I flashed the new AmonRA via Unrevoked. Everthing went fine. After Flashing a new ROM (Oxygen) i had the mentioned USB/SD-Card Problem.
I was able to access my Device via Fastboot and get into Recovery but my SD Card was not able to be mounted anymore. (Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)).
Also i was stuck in a Bootloop after the "S-OFF Bootlogo".
After "fixing" the SD Card Problem, i was able to Boot the new Rom, access the SD Card via FIle Explorer, but my Device was not recognized properly while connected via USB. Something like "unrecognized Quallcom Device" Driver not found.
Yeah i had similar experience i had i flashed new amon ra via fastboot then backed up my leedroid2.2b rom via rom manager just cos i could rename it easily then booted into amon ra wiped and flashed latest leedroid. On the reboot it decided to reboot on the spalsh screen a few times and then the boot animation started when i booted i realised i had sd problem but wasn't aware of usb so ended up going the long way around

[Q] Brick? USB brick? What to do?

Hi,
Today I backed up my mobile ( using amon ra ), partitioned new SD card and placed backup back. All succesful, then my phone got a boot animation loop. Got battery out and tried to flash the ROM again ( insertcoin stable ). Then It can't read my SD card anymore! The error was: E: Can't mount /dev/block/mmcblk0p1
I can't flash a ROM anymore, but I wiped my phone after that for trying to flash, didn't work. Now my phone is turned on. It boots with a grey black android logo, and then I get parts of insertcoin. I'm missing a lot of apps and apk's, ( for example the settings and the lockscreen ). So I'm missing a lot.
I can't power my phone when it's on, only when it's off. So please help me!
And explain it as easy as possible.
Search the forums USB Brick -
it will contain the command:
fastboot enableqxdm 0
Marc. said:
Hi,
Today I backed up my mobile ( using amon ra ), partitioned new SD card and placed backup back. All succesful, then my phone got a boot animation loop. Got battery out and tried to flash the ROM again ( insertcoin stable ). Then It can't read my SD card anymore! The error was: E: Can't mount /dev/block/mmcblk0p1
I can't flash a ROM anymore, but I wiped my phone after that for trying to flash, didn't work. Now my phone is turned on. It boots with a grey black android logo, and then I get parts of insertcoin. I'm missing a lot of apps and apk's, ( for example the settings and the lockscreen ). So I'm missing a lot.
I can't power my phone when it's on, only when it's off. So please help me!
And explain it as easy as possible.
Click to expand...
Click to collapse
if you can get to fastboot, you can use: fastboot oem enableqxdm 0
And that's it?
Just turn phone on ( volume down + power ), then power button for fastboot.
Plug it into PC, start adb and then that command?
And then my phone can read USB again?
Edit: SD again?
Edit2: I am in fastboot, but where to put the command?
first cd and then the android-sdk tools folder? ( ADB is not in there, that is in platform-tools )
So what to do?
Phone must say: FASTBOOT USB
You have to put this where your fastboot is located, not the adb (but i have them in one place )
I think it worked, I've done it using the fastboot thing.
Now flashing Insertcoin again Hope it works!!
Ok, got my SD working again, with Insertcoin. But it recognize the computer or anything very late! When connected to the computer or power, it takes a few minutes before it recognize it, the computer even doen't ask for diskdrive or something like that, it only powers... What to do?
Edit: Do I need to do these options too? http://android.modaco.com/topic/309939-usb-brickrickrolledb0rked-fixed/ numbers 3,4,5 and 6?
Bump... Please help, I need my phone tomorrow and I can't miss it.
Marc. said:
Bump... Please help, I need my phone tomorrow and I can't miss it.
Click to expand...
Click to collapse
Try the Android Flasher, I haven't used it but others say it worked for them
http://forum.xda-developers.com/showthread.php?t=794638
Marc. said:
Ok, got my SD working again, with Insertcoin. But it recognize the computer or anything very late! When connected to the computer or power, it takes a few minutes before it recognize it, the computer even doen't ask for diskdrive or something like that, it only powers... What to do?
Edit: Do I need to do these options too? http://android.modaco.com/topic/309939-usb-brickrickrolledb0rked-fixed/ numbers 3,4,5 and 6?
Click to expand...
Click to collapse
Yes you need to flash something as well, and the instructions there may work as a quick fix, but for me if the wrong image is flashed things like bluetooth don't work and other quirks are introduced.
I had to to generate a CID image specific to your variant of the Desire from this site: http://ks25738.kimsufi.com/misc/
The Rom version is irrelevant I think so enter the example on the site.
For "cid", input the following into the terminal (Mac? and Linux):
Code:
fastboot oem boot | grep #INFOCID
You should get a line like:
Code:
#INFOCID is HTC__E11
Which means you enter "HTC__E11" as the CID.
I you're on Windows (why?) or the above doesn't work, forget the pipe (|) and everything that follows and look for "#INFOCID" in the output which should be several lines long.
Put the generated mtd0.img file in the same directory as fastboot (or anywhere if you think you can handle the paths properly) and enter:
Code:
fastboot flash misc mtd0.img
Obviously you need to be in Fastboot USB mode in the bootloader for any of this to work.
For some probably unrelated reason, USB file transfers still don't work for me so I forced to use the Samba Filesharing app from the market.
I got the info from this page: http://forum.xda-developers.com/showthread.php?t=691639
Ok, where can I find the Rom version? And please give the flash of that file in more steps, I don't understand it.
Bump, I really need my phone in a few hours! Please help!
Ok, I'm further.
I have now a few problems with: 3. Get flash_image from the attached files below
Move this to /data/ , and flash the modified image using:
"/data/flash_image misc /data/mtd0.img"
You can move both mtd0.img and flash_image by putting it on your sdcard, and issueing the following command in a terminal emulator:
'cat /sdcard/flash_image > /data/flash_image'
'cat /sdcard/mtd0.img > /data/mtd0.img'
You might have to do 'chmod u+x /data/flash_image' before you run the commands (or chmod 755 /data/flash_image)
4. Repeat step 3 a couple of times if it doesn't seem to work well.
5. All done! Reboot, you should have normal usb connectivity. Post your 'fastboot oem boot' log and intermediate steps if it fails.
I made a mdt0.img using http://ks25738.kimsufi.com/misc/
My cid was HTC__E11
and ROM version 2.36.405.8 and it gave me a mdt0.img file
Now step 3, I don't know how to let it flash... I don't know what to do now with the file... Please help and give everything in simple steps
Follow The Usb brick fix Link On My sig,hope that will solve your problem.
Exiled_SouL said:
Follow The Usb brick fix Link On My sig,hope that will solve your problem.
Click to expand...
Click to collapse
I read it, but a few questions...
( My phone is S-ON )
1. I'm not on a stock rom, but on Insertcoin
2. I can already acces my SD card, so can I skip the first step? Done that yesterday already.
3. Can I use the mtd0.img generator? If yes I have already the file.
4. With step 3, which files must be in /data/data?
5. With step 2, I have super user, so can I use that instead of the root acces thing?
SOLVED!! Thanks everyone!
I read a lot, and its succesful! Diskdrive, wall charching bluetooth EVERYTHING!!!
Thanks everyone! I really appreciate it.

[Q] NOOB bricked acer a100 help!

I tried using the simple root and clockwork mod method and now my a100 keeps cycling thru bootloaderversion 0.03.06-ics-ics (unlock mode) with green acer logo. If I reboot holding power+down sd update command recovery
update_package=sd card update.zip
booting recovery kernal image
then it starts cycling again.
Please can someone help!
same
Same thing here (or at least very similar). Hoping there's a simple solution like the "Odin back to stock" I can do on my SGS phone.
are you sure that the bootloader say "unlock mode"?
If so, then try this.
try this
Install the USB drivers on your PC if you haven't done it already. ( http://global-download.acer.com/GDF...A TAB&Step3=A100&OS=a08&LC=en&BC=Acer&SC=PA_6 )
install android SDK. ( http://developer.android.com/sdk/index.html )
copy the update.zip file to your SD card root.
download TWRP recovery ( http://forum.xda-developers.com/showthread.php?t=1608152 ) and place it in the platform-tools dir where the SDK was installed ( ex. C:\Program Files\Android\android-sdk\platform-tools )
Once all that is done follow these steps
1) boot the tablet to fastboot mode
2) run command prompt on PC (cmd.exe)
3) cd to the platorm-tools dir
4) type the following lines one at a time.
adb.exe
fastboot erase recovery
fastboot flash recovery NAMEOFRECOVERY.img (ex. recovery-A100ICS-TWRP.img)
5) hold the vol down button on the tablet
6) type fastboot reboot.
The tablet should now reboot to the recovery program. Goto settings and mount the external SD card, then flash the update.zip by going to install.
Hope this helps
[email protected] said:
I tried using the simple root and clockwork mod method and now my a100 keeps cycling thru bootloaderversion 0.03.06-ics-ics (unlock mode) with green acer logo. If I reboot holding power+down sd update command recovery
update_package=sd card update.zip
booting recovery kernal image
then it starts cycling again.
Please can someone help!
Click to expand...
Click to collapse
Did you rename/delete /etc/install-recovery.sh ?
I think you're not. Try to make hard reset, then boot normaly rename/delete this file and after that flash recovery again, it should work.
All it's explained here.
Thank you
TheBlackshinobi said:
are you sure that the bootloader say "unlock mode"?
If so, then try this.
try this
Install the USB drivers on your PC if you haven't done it already. ( http://global-download.acer.com/GDF...A TAB&Step3=A100&OS=a08&LC=en&BC=Acer&SC=PA_6 )
install android SDK. ( http://developer.android.com/sdk/index.html )
copy the update.zip file to your SD card root.
download TWRP recovery ( http://forum.xda-developers.com/showthread.php?t=1608152 ) and place it in the platform-tools dir where the SDK was installed ( ex. C:\Program Files\Android\android-sdk\platform-tools )
Once all that is done follow these steps
1) boot the tablet to fastboot mode
2) run command prompt on PC (cmd.exe)
3) cd to the platorm-tools dir
4) type the following lines one at a time.
adb.exe
fastboot erase recovery
fastboot flash recovery NAMEOFRECOVERY.img (ex. recovery-A100ICS-TWRP.img)
5) hold the vol down button on the tablet
6) type fastboot reboot.
The tablet should now reboot to the recovery program. Goto settings and mount the external SD card, then flash the update.zip by going to install.
Hope this helps
Click to expand...
Click to collapse
I'm going to try this, one question though. My computer does not read the tablet anymore even though I have the drivers installed will it still work? Yes I'm a serious noob, but I'm trying...and thank you for your help it is much appreciated.
cpu doesnt read tablet anymore
[email protected] said:
I'm going to try this, one question though. My computer does not read the tablet anymore even though I have the drivers installed will it still work? Yes I'm a serious noob, but I'm trying...and thank you for your help it is much appreciated.
Click to expand...
Click to collapse
Okay, I downloaded everything but my computer doesnt recognize my a100 anymore, only if I put the tablet into fastboot then it see's it. My tablet just keeps on rebooting itself repeatedly unless I go into fastboot. Please tell me I dont have a paperweight.
were getting close
Blackshinobi or anyone that can help,
I'm getting close. I make it to: "fast boot flash recovey" cmd prompt
I get two different errors depending hoew I type the cmd prompt:
1. "fastboot flash recovery recovery-A100ICS-TWRP.img"
error (can not load recovery-A100ICS-TWRP.img)
2. "fastboot flash recovery-A100ICS-TWRP.img"
error ( cannort determine image file name for 'recovery-A100ICS-TWRP.img)
I was a little confuse on proper cmd line prompt, but I'm thinking #2 is the correct way.
Thanks so much for your help!
pfisher101 said:
Blackshinobi or anyone that can help,
I'm getting close. I make it to: "fast boot flash recovey" cmd prompt
I get two different errors depending hoew I type the cmd prompt:
1. "fastboot flash recovery recovery-A100ICS-TWRP.img"
error (can not load recovery-A100ICS-TWRP.img)
2. "fastboot flash recovery-A100ICS-TWRP.img"
error ( cannort determine image file name for 'recovery-A100ICS-TWRP.img)
I was a little confuse on proper cmd line prompt, but I'm thinking #2 is the correct way.
Thanks so much for your help!
Click to expand...
Click to collapse
That's awesome news!!!
Number 1 is the correct command.
Just making sure you are actually in fastboot (bootloader) mode. On the command-promt type "fastboot devices", if you see the result below, then you're good
? fastboot (yes that's a question mark)
Now be sure you are in the directory with the recovery image and issue number 1 command (fastboot flash recovery whatever-recovery.img). If you get some errors, be sure to check the MD5 hash of the recovery image cuz it could be a corrupted download.
Of course, you can't flash the custom recovery if you still have a locked bootloader.
you guys rock..even closer
Thank-you everyone ..I am soooo close. I did get the recovery image to load (I accidently had it in android-sdk and not platform-tools...oooops my bad). Now I can reboot to recovery and install the update.zip off my external sd card. However after I install the update.zip and reboot, I still get stuck on the acer screen (bootloader version 0.03.06-ICS (Unlock Mode) at top with acer logo in green at bottom.
Which update.zip am I suppose to be using? Currently I am trying to install one of the stock ROMS from the developer section of this forum. Am I suppose to be using a specific one?
Thanks again, I know I'm close. My tablet has been brick'd for weeks and I'm dedicated to getting it back now that I have time.
pfisher101 said:
Thank-you everyone ..I am soooo close. I did get the recovery image to load (I accidently had it in android-sdk and not platform-tools...oooops my bad). Now I can reboot to recovery and install the update.zip off my external sd card. However after I install the update.zip and reboot, I still get stuck on the acer screen (bootloader version 0.03.06-ICS (Unlock Mode) at top with acer logo in green at bottom.
Which update.zip am I suppose to be using? Currently I am trying to install one of the stock ROMS from the developer section of this forum. Am I suppose to be using a specific one?
Thanks again, I know I'm close. My tablet has been brick'd for weeks and I'm dedicated to getting it back now that I have time.
Click to expand...
Click to collapse
Congrats resurrecting your tab! Gotta be a great relief!
How about Flexreaper ROM? It will require full wipe before flashing: in recovery wipe/factory reset, wipe system, wipe cache, wipe dalvik cache, flash Flexreaper ROM zip file. This is basic guide, follow detailed instructions on this ROM thread (link is in my sig).
Sent from my A100 using xda premium
not quite recovered yet. I still get the hang on Acer screen. anyone know why? I will try flexreaper
I'm BACK
Thanks to all. I'm back up. flexreaper did work.. I hope the guy who actually started this thread is as lucky.
Not so lucky
I'm still stuck my pc doesnt read my acer a100 still....any helps out there?
[email protected] said:
I'm still stuck my pc doesnt read my acer a100 still....any helps out there?
Click to expand...
Click to collapse
Power down the unit. Set screen lock in the up position. Hold volume down and power. When powered on keep holding the vol down button. Then toggle the screen lock to down.
That should do a factory reset.
Then put a stock rom in the root of SD Card. Volume up then power until let the tablet recover.
This worked for me.
did u install the drivers from an earlier post? Also when you power up you your tablet you need to boot into fastboot mode? You're certain you have done both of these things?
I am unable to connect to, my pc doesnt recognize my acer anymore...unless by sd card you mean external card? Thank you for trying to help. I'm a serious noob but trying hard.
i'm in a similar situation. i accidentally deleted the build.prop file and rebooted. now it only displays a black screen after the acer logo drops out. my boot loader is locked but i cant install the mtp usb drivers to fix anything. think i have a paperweight now.
mechpilot_z said:
i'm in a similar situation. i accidentally deleted the build.prop file and rebooted. now it only displays a black screen after the acer logo drops out. my boot loader is locked but i cant install the mtp usb drivers to fix anything. think i have a paperweight now.
Click to expand...
Click to collapse
that's easily fixed, install this through stock recovery, http://forum.xda-developers.com/showthread.php?t=1611696
eww245 said:
that's easily fixed, install this through stock recovery, http://forum.xda-developers.com/showthread.php?t=1611696
Click to expand...
Click to collapse
tried. i had no alternative recovery on it. i could not get the sd card mounted to push the zip to it. both adb and fast boot wont see my tablet. every attempt at unlocking fast boot wouldn't work. I tried to check in device manager to see if it was connected, the driver was working but it had an error message "Device can not start (Code 10)"
My pc only sees my tablet when I boot it into fastboot mode and sees it as an adb interface...Is there anything I can do from there?

[HOW-TO]fix sdcard mount/read and usb not working on hero

Next time, our hero know an update to the recovery 5.x , and people say they've got problem with sdcard.
Problem don't come from the "sdcard slot", No !! Its come from a wrong CID.
FIRST YOU NEED A WORKING ANDROID SDK WITH ADB
TO FIX IT, You need to do these step:
1/Download attached files ( mtd0.img and flash_image.zip: extract flash _image from flash_image.zip). Push these file on sdcard with an sdcard reader for computer.
2/Go to the bootloader (press down-volume key and power-on key)
3/Press back to switch on fastboot mode
4/Connect your device to the computer and open terminal
5/Write:
Code:
adb devices
fastboot oem enableqxdm 0
fastboot reboot
NOW sdcard is fix
6/Exit fastboot and disconnect usb
7/Switch on your phone
8/With root explorer push mtd0.img and flash_image to /data/
9/Open android terminal emulator and write
Code:
su
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
reboot
Terminal should gives an ERROR (no fear, it's normal)
NOW usb work :good:
Not work when i type in terminal /data/flash_image misc /data/mtd0.img it show error say not have space on phone although there is nothing installed.I ****ed up phone with that recovery so i can just drop him in trash........
ralph745 said:
Not work when i type in terminal /data/flash_image misc /data/mtd0.img it show error say not have space on phone although there is nothing installed.I ****ed up phone with that recovery so i can just drop him in trash........
Click to expand...
Click to collapse
What do you mean? What went wrong?
Nuustik said:
What do you mean? What went wrong?
Click to expand...
Click to collapse
If you have recovery 5.x don't ever EVER try to install any android 2.1 with sense rom
But you can always go back to the old recovery, or am I missing something here?
SANSYF said:
Next time, our hero know an update to the recovery 5.x , and people say they've got problem with sdcard.
Problem don't come from the "sdcard slot", No !! Its come from a wrong CID.
FIRST YOU NEED A WORKING ANDROID SDK WITH ADB
TO FIX IT, You need to do these step:
1/Download attached files ( mtd0.img and flash_image.zip: extract flash _image from flash_image.zip). Push these file on sdcard with an sdcard reader for computer.
2/Go to the bootloader (press down-volume key and power-on key)
3/Press back to switch on fastboot mode
4/Connect your device to the computer and open terminal
5/Write:
Code:
adb devices
fastboot oem enableqxdm 0
fastboot reboot
NOW sdcard is fix
6/Exit fastboot and disconnect usb
7/Switch on your phone
8/With root explorer push mtd0.img and flash_image to /data/
9/Open android terminal emulator and write
Code:
su
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
reboot
NOW usb work :good:
Click to expand...
Click to collapse
Hi
I tried this commands
"adb devices" - will not show anything
as in fastboot it showed me the device i took chance to run following command-
"fastboot oem enableqxdm 0"
it showed ...OKAY
then "fastboot reboot" but it dodnt boot, so i pressed the menu and took the cable out.
restarted the phone but it still cant take sdcard as my ROM is messed up, its stuck on "sense process error" so cant go beyond.
i haved troubles with that but i fixed it
SANSYF said:
Next time, our hero know an update to the recovery 5.x , and people say they've got problem with sdcard.
Problem don't come from the "sdcard slot", No !! Its come from a wrong CID.
FIRST YOU NEED A WORKING ANDROID SDK WITH ADB
TO FIX IT, You need to do these step:
1/Download attached files ( mtd0.img and flash_image.zip: extract flash _image from flash_image.zip). Push these file on sdcard with an sdcard reader for computer.
2/Go to the bootloader (press down-volume key and power-on key)
3/Press back to switch on fastboot mode
4/Connect your device to the computer and open terminal
5/Write:
Code:
adb devices
fastboot oem enableqxdm 0
fastboot reboot
NOW sdcard is fix
6/Exit fastboot and disconnect usb
7/Switch on your phone
8/With root explorer push mtd0.img and flash_image to /data/
9/Open android terminal emulator and write
Code:
su
chmod 755 /data/flash_image
/data/flash_image misc /data/mtd0.img
reboot
NOW usb work :good:
Click to expand...
Click to collapse
I have managed to get upto this stage and when I give this command -
/data/flash_image misc /data/mtd0.img
it gives me "error writing misc: No space left on device"
I tried again and it gave me -
"mtd: read all-zero block at 0x00000000; skipping
error writing misc: No space left on device"
I am sure there is enough space, my card is 8GB and atleast 3GB is left though
what do i do now?
jdwis said:
I have managed to get upto this stage and when I give this command -
/data/flash_image misc /data/mtd0.img
it gives me "error writing misc: No space left on device"
I tried again and it gave me -
"mtd: read all-zero block at 0x00000000; skipping
error writing misc: No space left on device"
I am sure there is enough space, my card is 8GB and atleast 3GB is left though
what do i do now?
Click to expand...
Click to collapse
If it gives this sentence, your sdcard and usb-mount are fixed
SANSYF said:
If it gives this sentence, your sdcard and usb-mount are fixed
Click to expand...
Click to collapse
Cheers man!!! thanks a zillion... its sorted now... u r genius...
Just wondering what is that "misc" do, the reason is I know just a little bit of Linux not much so I guess your explaining would help me alot..
thanks again my friend.
jdwis said:
Cheers man!!! thanks a zillion... its sorted now... u r genius...
Just wondering what is that "misc" do, the reason is I know just a little bit of Linux not much so I guess your explaining would help me alot..
thanks again my friend.
Click to expand...
Click to collapse
For code line, I am inspired from an other htc device where has the same issue..
I imagine the new recovery has an effect on device information and corrupt sd-card functionality
So I have think "If I re-write devices informations, what it do ?"
In first, I make sdcard readable by the device( "fastboot commands" )
Next I have edited mtd0.img with an hex-editor ( it contain CID and device information)
And flash mtd0.img ( "misc" is a folder where you flash the img)
I have seen, if you flash an old cwm recovery, probleme come back ( but you can fix it with my tuto)
SANSYF said:
For code line, I am inspired from an other htc device where has the same issue..
I imagine the new recovery has an effect on device information and corrupt sd-card functionality
So I have think "If I re-write devices informations, what it do ?"
In first, I make sdcard readable by the device( "fastboot commands" )
Next I have edited mtd0.img with an hex-editor ( it contain CID and device information)
And flash mtd0.img ( "misc" is a folder where you flash the img)
I have seen, if you flash an old cwm recovery, probleme come back ( but you can fix it with my tuto)
Click to expand...
Click to collapse
Good one, now I got the problem again without any stupidity from myside like removing cable while sdcard is mounted.. nothing as such I have done now.
After your tutorial everything started working.
As to make everything work since yesterday and for so many hours the battery was discharging and charging, installing several ROMs to get access etc etc..
As everything was working, I thought to fully charge the battery and wipe battery info from recovery. I had RA 1.7.... then had installed CWM5.xx then installed CWM 2.5xx and then finally got back my RA 1.7 as I had my backup taken by that...
Went into RA recovery, wiped info for battery, came out and the ROM shows "Removed SDcard" - and the whole problem came back... (i was going to work)
Came back from work, quickly did your tuto, things started working again, wanted to make sure is it recovery or was somehting else.. so went back into recovery and went into "Wipe"... then DID NOTHING, I mean it, I didnt execute any other thing in there... came out and same problem "Removed sdcard" on the ROM...
what is going on with this, how can I stop this?
Do you think you would need any info from my phone I will give you, where you could possibly make some specific image for this phone or .... I dont know man... cant think of anything as I am not as clever as you my friend... please help..
I have seen problem come when we change the recovery. If you fix it with amonra recovery, it doesn't come back but when we flash an other recovery, sometime problem come
SANSYF said:
I have seen problem come when we change the recovery. If you fix it with amonra recovery, it doesn't come back but when we flash an other recovery, sometime problem come
Click to expand...
Click to collapse
Ya but I am not changing the recovery, RA is there now, I am just going into recovery's Wipe menu, doing nothing I come out and I have this problem come back..
I think my whole phone tihng has gone corrupt, do you think if I do RUU it will wipe everything, I mean even HBOOT & recovery etc... and that RUU will put original HBOOT image, recovery and stock rom (unrroted) back on phone?
jdwis said:
Ya but I am not changing the recovery, RA is there now, I am just going into recovery's Wipe menu, doing nothing I come out and I have this problem come back..
I think my whole phone tihng has gone corrupt, do you think if I do RUU it will wipe everything, I mean even HBOOT & recovery etc... and that RUU will put original HBOOT image, recovery and stock rom (unrroted) back on phone?
Click to expand...
Click to collapse
You can try, be sure usb and sdcard are fixed before doing it. If it work post some feedbacks please

[Q] HELP! I Can't mount SDcard

Hi!
Something is wrong. I have AmonRA 2.0 recovery and I can't mount sdcard, even when I try to use function Flash zip form sdcard I get this message:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0).
(no such file or directory)
E:Can't mount /sdcard.
Well all started yesterday after installing some games from Google Play and then phone caught bootloop. So I use Full wipe I decided to increase the size of the partition EXT. Then I get message Can't mount sdcard. So I delete partition (fat32 and EXT) on pc and create new. Bat still the same. I can't create partition using recovery, because E:Cant mount.....
I delete again partition on pc and put clean card to HTC, still the same problem.
What already tried:
- change Hboot but no results
- I try reinstall AmonRA using Unrevoked 3 - my phone reboots 2 times and then unrevoked want install
Qualcomm CDMA Technologies MSM Windows driver, but I have GSM!
I ran android and go to Settings>Storage Settings and I see "Insert an SD card for mounting", but my card is already inserted!
any ideas? please help
DUser83 said:
Hi!
Something is wrong. I have AmonRA 2.0 recovery and I can't mount sdcard, even when I try to use function Flash zip form sdcard I get this message:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0).
(no such file or directory)
E:Can't mount /sdcard.
Well all started yesterday after installing some games from Google Play and then phone caught bootloop. So I use Full wipe I decided to increase the size of the partition EXT. Then I get message Can't mount sdcard. So I delete partition (fat32 and EXT) on pc and create new. Bat still the same. I can't create partition using recovery, because E:Cant mount.....
I delete again partition on pc and put clean card to HTC, still the same problem.
What already tried:
- change Hboot but no results
- I try reinstall AmonRA using Unrevoked 3 - my phone reboots 2 times and then unrevoked want install
Qualcomm CDMA Technologies MSM Windows driver, but I have GSM!
I ran android and go to Settings>Storage Settings and I see "Insert an SD card for mounting", but my card is already inserted!
any ideas? please help
Click to expand...
Click to collapse
Try using Gparted or 4ext to partition your sd-card.
abaaaabbbb63 said:
Try using Gparted or 4ext to partition your sd-card.
Click to expand...
Click to collapse
Partition is ok. I can create new. The problem is that the phone will not mount sd card. Is available from the recovery and from the android.
I have 3 different sdcard and it does not matter which is insert, because recovery and android they do not mount.
I can change HBoot, so physically slot is ok. (Function FASTBOOT sees the new hboot file on the sd).
So once again:
The problem is that the phone will not mount sd card. Is available from the recovery and from the android.
Do as @abaaaabbbb63 said.
Since fastboot is obviously working, flash 4ext recovery with fastboot.
Then reboot into recovery and partition/format your sdcard from scratch.
And there's no use in starting a new thread for the same issue, things won't go better!
Two beer or not two beer, that's the question
DUser83 said:
Partition is ok. I can create new. The problem is that the phone will not mount sd card. Is available from the recovery and from the android.
I have 3 different sdcard and it does not matter which is insert, because recovery and android they do not mount.
I can change HBoot, so physically slot is ok. (Function FASTBOOT sees the new hboot file on the sd).
So once again:
The problem is that the phone will not mount sd card. Is available from the recovery and from the android.
Click to expand...
Click to collapse
I had the same problem yesterday, i used the "fastboot oem enableqxdm 0" command, and then i flashed the "4eXT Recovery Touch v1.0.0.5 RC9" (links below) recovery to use the "usb unbrick" feature.
https://dl.dropboxusercontent.com/u/6801709/Envois/Desire/Recovery/PB99IMG.zip
https://dl.dropboxusercontent.com/u/6801709/Envois/Desire/Recovery/4EXT-v1.0.0.5-RC9.img
zinconnu said:
I had the same problem yesterday, i used the "fastboot oem enableqxdm 0" command, and then i flashed the "4eXT Recovery Touch v1.0.0.5 RC9" (links below) recovery to use the "usb unbrick" feature.
https://dl.dropboxusercontent.com/u/6801709/Envois/Desire/Recovery/PB99IMG.zip
https://dl.dropboxusercontent.com/u/6801709/Envois/Desire/Recovery/4EXT-v1.0.0.5-RC9.img
Click to expand...
Click to collapse
But how to use "fastboot oem enableqxdm 0" command? on windows cmd? I have android sdk and Android Commander.
please do not leave me alone
zinconnu said:
I had the same problem yesterday, i used the "fastboot oem enableqxdm 0" command, and then i flashed the "4eXT Recovery Touch v1.0.0.5 RC9" (links below) recovery to use the "usb unbrick" feature.
https://dl.dropboxusercontent.com/u/6801709/Envois/Desire/Recovery/PB99IMG.zip
https://dl.dropboxusercontent.com/u/6801709/Envois/Desire/Recovery/4EXT-v1.0.0.5-RC9.img
Click to expand...
Click to collapse
That my PB99IMG? LOL
jmcclue said:
That my PB99IMG? LOL
Click to expand...
Click to collapse
Yes! :good: (http://forum.xda-developers.com/showthread.php?t=1751258)
DUser83 said:
But how to use "fastboot oem enableqxdm 0" command? on windows cmd? I have android sdk and Android Commander.
please do not leave me alone
Click to expand...
Click to collapse
You have to :
1. Setup fastboot
2. Turn your phone off. Boot it into fastboot using back button + power button, then plug it into your computer. On your phone it should now say "FASTBOOT USB".
3. Open command prompt (cmd) and enter the command
Yes! Yes! Yes!
Thank you very much guys! It works! :laugh::laugh:
Here is what I did:
1. I used these instructions and download ADB&Fastboot.
2. I typed the command "fastboot oem enableqxdm 0" In the window I saw the answer "Finished... OK"
3. Then I download 4EXT-v1.0.0.5-RC9 from the link above i type command "fastboot flash recovery 4EXT-v1.0.0.5-RC9.img".
4. I launched a new recovery and use function "usb unbrick" It shows me 640kb file was missing. So I click FIX and done.
Now sdcard is working.
Thank you again guys. You are amazing!
zinconnu said:
Yes! :good: (http://forum.xda-developers.com/showthread.php?t=1751258)
You have to :
1. Setup fastboot
2. Turn your phone off. Boot it into fastboot using back button + power button, then plug it into your computer. On your phone it should now say "FASTBOOT USB".
3. Open command prompt (cmd) and enter the command
Click to expand...
Click to collapse
I found other toturial, but thank you.
DUser83 said:
Yes! Yes! Yes!
Thank you very much guys! It works! :laugh::laugh:
Here is what I did:
1. I used these instructions and download ADB&Fastboot.
2. I typed the command "fastboot oem enableqxdm 0" In the window I saw the answer "Finished... OK"
3. Then I download 4EXT-v1.0.0.5-RC9 from the link above i type command "fastboot flash recovery 4EXT-v1.0.0.5-RC9.img".
4. I launched a new recovery and use function "usb unbrick" It shows me 640kb file was missing. So I click FIX and done.
Now sdcard is working.
Thank you again guys. You are amazing!
Click to expand...
Click to collapse
You are welcome!

Categories

Resources