[Q] SD card can't be mounted - Desire PVT4 after rooting - Desire General

Hi guys,
I got a problem:
I rooted my Desire PVT4 with unrevoked and AmonRa-Recovery under Linux Mint Live CD. Everything went fine.
Next, I wanted to prepare for flashing a new rom. I did a Titanium Backup and downloaded Rom Manager. I proceeded to do a nand-backup, which it did, I guess. After that, however, my desire didn't recognize my sd card anymore.
Connecting to Windows 7 didn't work either. (It did work before)
So I went and bought a new sd card. I formatted it and put it in my device. Still, no sd card detected.
Along with the new sd card, I got an adapter, so I can now stick the sd card directly into my computer.
Surprise: I could now see both sd cards in Windows. Still, I formatted both after backing up the files on it.
The Desire wasn't able to boot anymore, though. So I went into recovery mode and partitioned the card manually with AmonRa recovery 2.0.1. This did work.
I can boot the Desire now, but it still won't detect the sd card.
Mounting it with AmonRa doesn't work either.
I read, that the problem might be caused by using RomManager on a PVT4 device.
Installing the HTC drivers didn't help and I can't install the google USB drivers. When I try to do so it says that there were no drivers found in the specified directory (""C:\android-sdk-windows\google-usb_driver")
In the device manager it shows 3 "Qualcomm CDMA Technologies MSM" (bought it in Germany, so shouldn't it read "GSM"?). All of them are marked with a yellow question mark. Upon trying to update the drivers I selected "Install software from a list or source" and specified ""C:\android-sdk-windows\google-usb_driver". I clicked "proceed" but Windows tells me that it couldn't find the drivers. Tried that on Win7 and on my WinXP laptop.
I desperately need help. I'm no pro. Actually I am a complete noob I searched on google but I couldn't find any solution so far.
Since I can't access my sd card (except partitioning in AmonRa, that did work somehow) I can't access any .zip on my sd card.
e. Additional information:
Upon trying to mount in Amonra recovery it says:
""Can't mount /sdcard"
Same, when trying to flash a .zip from sd.
hboot version is 0.93 I think.
I tried the following:
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 :
Quote
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
cd /mnt/cdrom/root
/mnt/cdrom/root/fastboot oem enableqxdm 0
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)...
Click to expand...
Click to collapse
Except that I used Linux Mint Live CD.
All I got was:
Code:
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
mount: block device /dev/sr0 is write/protected, mounting read-only
sudo mount /dev/cdrom /mnt/cdrom
mount: block device /dev/sr0 is write-protected, mounting read-only
mount: /dev/sr0 already mounted or /mnt/cdrom busy
mount: according to mtab, /dev/sr0 is already mounted on /mnt/cdrom
cd /mnt/cdrom/root
bash: cd: /mnt/cdrom/root: No such file or directory
Must I use TinyCore? I read somewhere that it only works for Hboot 0.8 and lower? What exactly is TinyCore anyways?
I almost know nothing about linux

No one?
Now I can't even get a signal anymore. I could cry...

Have you tried this procedure?
http://forum.xda-developers.com/showthread.php?t=691639
It worked for me when i bricked (pvt1 s-off). The problem seems to lie in the misc partition, which you have patch with the edited img file...

When I get into fastboot mode, where is the option to "'fastboot oem boot'"?
e. Also, my PC does not recognize the desire when pluggin into USB.

Eiskrem-Kaiser said:
When I get into fastboot mode, where is the option to "'fastboot oem boot'"?
Click to expand...
Click to collapse
You type that into cmd prompt window on your PC.
There are some instructions on SD card fix in this thread:
http://forum.xda-developers.com/showthread.php?t=691639

It happened to me when I partitioned the SD card in windows. Could you chech if your partitions on your SD are both set as primary and also uncheck "Take ownership of filesystem" (or something like that) when you are using the HD utility in linux.
Basically what happened was that the partitions were logical in stead of primary. Banged my had in the wall for two days before I figured this out. Hope it helps.

I'll try the Usb-brick-fix first. But how do I find out which rom version I have? I managed to get my CID by typing "fastboot oem boot" in the command prompt.
e. This is what I get upon writing the command:
http://www.abload.de/img/unbenannt7njw.jpg
e. I noticed, it says "board_bravo.disable-sdcard=1"
what does that mean?

Eiskrem-Kaiser said:
I'll try the Usb-brick-fix first. But how do I find out which rom version I have? I managed to get my CID by typing "fastboot oem boot" in the command prompt.
e. This is what I get upon writing the command:
http://www.abload.de/img/unbenannt7njw.jpg
e. I noticed, it says "board_bravo.disable-sdcard=1"
what does that mean?
Click to expand...
Click to collapse
I guess it means that sdcard can't be mounted...anyway, have you done the hexeditor thing already?

I just put the two files on the sd card and rebooted in fastmode. However, I'm not sure about my rom version. Where can I find out which one I have?
e. I just typed "cat /sdcard/flash_image > /data/flash_image" in ConnectBot, but it says "cannot create /data/flash_image: permission denied"
e.. When I type in "su" first, it still says "/sdcard/flash_image: No such file or directory"

Eiskrem-Kaiser said:
Where can I find out which one I have?
Click to expand...
Click to collapse
Oh sorry, i didn't read that...well i remember i was confused about that too at this point...too bad i can't remember how i found out.
Anyway, i found another solution on modaco:
"2. Enable the SD Card functionality. Boot your phone in FASTBOOT mode (back + power), and enter this command: 'fastboot oem enableqxdm 0' . This will re-enable your SD card.
3. Put THIS (attached) update.zip on your sdcard.
4. Reboot into recovery.
5. Apply sdcard:update.zip.
6. This will automatically fix your MISC partition with the correct CID. Reboot, and your done!"
Try this and tell me if it works in the while

I just booted into fastmode again and typed "fastboot oem enableqxdm 0" into the command prompt.
Now the Desire detects the sd card again :thumbsup:
Now I will try to use the cat command again.
e. I just did the thing with the "update.zip". Rebooting now.
e. I got my sd card back and a phone signal. That's great so far. Now what?

Still, when typing
"cat /sdcard/flash_image > /data/flash_image"
I get
"/sdcard/flash_image: No such file or directory"

I guess you're done if it worked...are you able to connect normally to your pc now? You should be :s
Also, those commands are meant to be used in a terminal emulator, not on your pc, i hope you didn't misread...anyway if you used the modaco tip you shouldn't need that anymore.
When you're done remember to copy your misc folder to a safe place, it will be enough to replace it via root explorer or similar if someday you'll brick again...

Nope, can't get it to connect to my PC quite yet. But I hope I will get that to work after rebooting the phone and/or windows or installing the htc drivers again.
I can not thank you enough right now. I was going crazy about this. Just bought my desire recently, upgrading from the Legend, with the little spare money I had. It would have been bad, if it was broken now.
So: THANK YOU VERY MUCH.
Also, someone tried to call me yesterday, while my phone signal didn't work. Now everytime I start the Phone, it shows me my missed call.
My girlfriend has a similar problem with a message I sent her. Everytime she boots her phone, she gets that message (fortunately it's "I love you" ).
So, I guess, it has something to do with the SIM?

Hmm, if you can't connect it might mean that the usb isn't fully restored...could you turn off the phone, plug it to pc, turn it back on and see if drivers get installed properly? Just to make sure...

I am stupid.
Hold on, it might work now. I had to switch to "local" in ConnectBot. Thought the app would remember that, but it didn't

Hmm.
Do I have to be in fastboot mode to type in those commands? Because I did type them in and rebooted, but Windows still will not detect my Desire :/
or should I type them in the windows command prompt?

Eiskrem-Kaiser said:
Hmm.
Do I have to be in fastboot mode to type in those commands? Because I did type them in and rebooted, but Windows still will not detect my Desire :/
or should I type them in the windows command prompt?
Click to expand...
Click to collapse
Sorry, i'm not sure i got ya. How would you run connectbot while you're in saftboot mode?? Because that's what i did, to make it clearer:
1. Downloaded image file "mtd0.img" and "flash_image" (from here http://forum.xda-developers.com/showthread.php?t=691639) and put them on sdcard (ofc i edited mtd0.img with my CID using some free hex editor before)
2. Installed Android Terminal Emulator app (from market), but connectbot should be the same.
3. Opened emulator, typed "su" command, accepted to give root permissions
executed this commands:
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/misc.img > /data/misc.img
chmod 755 /data/flash_image
/data/flash_image misc /data/misc.img
4. Rebooted phone, connected to pc.
5. Success
Is this exactly what you did?

Yes. I typed exactly that. I just wanted to type it in again, but now it tells me again, that there is no such file or directory on /sdcard. But I can see the file with Astro being on the sdcard.
e. Maybe I used the wrong rom version number?
e.. Someone suggested to run in fastboot mode and type "fastboot oem eraseconfig". What exactly would this do? Which config would be erased?
What exactly is fastboot?

Eiskrem-Kaiser said:
Maybe I used the wrong rom version number?
What exactly is fastboot?
Click to expand...
Click to collapse
You just need the CID, not the rom version for this...
Anyway, please note that when i write misc.img i mean mtd0.img, that's what you typed right? Sorry if i confused you.
I guess there's no need to mess further with fasboot, i didn't need it, except for mounting sdcard.
If this still fails, you can always move mtd0.img and flash_image to /data manually via root explorer app, then go on from the chmod command.

Related

[Q] No USB functionality, including USB Fastboot

My HTC Desire has no USB functionality at all, including USB Fastboot. It's also got no root access. There's no known reason why this occured.
Similar forum threads suggest that USB functions can be restored if I revert to the stock RUU image. It's possible that an update has been the cause of this problem.
I've tried to install the base ROM - RUU, but because I have Hboot 0.93 I have to downgrade, but can't do that because there is no existing root access and I don't have ClockWorksMod recovery installed to get around the signature verifications.
The device boots up and operates fine (even the SD Card). I have to charge the battery using my partner's phone and can't do any data transfers. I'm running Android 2.2, Radio 32.49.00.32U_5.11.05.27, Hboot 0.93
I'm beginning to think that the motherboard has somehow been fried and can no longer supprt the USB part of it.
Any ideas would be most helpful. Thanks heaps
As you are unrooted, you should have warranty and that is the first way to fix it.
The other is a bit more complicated but if you are cautions, you'll be fine. Use this guide:
quanchi said:
...
This is a specific situation - usb brick and totally stock rom, recovery and hboot. It's not required for people who have a modified recovery and a rooted rom. It's easy like 1-2-3.
Before doing anything else enable the Debug Mode in the Applications / Dev menu
1. Download the rageagainstthecage exploit from the authors site:
http://c-skills.blogspot.com/2010/08/please-hold-line.html
2. Download the flash_image and misc (mtd0.img) partition image from this thread.
http://forum.xda-developers.com/showthread.php?t=691639&highlight=usb+brick
Modify the mtd0.img according to your phones CID (how to get the CID also explained in the thread)
2. Download Android Terminal Emulator from the Market
3. Copy the exploit binary (rageagainstthecage-arm5.bin), the flash_image and modifed mtd0.img to the sdcard via an external card reader
4. Start the Terminal
5. Copy the files to the Terminal app data directory (the only place on the data partition you will have write access while running the Terminal), and make the binaries executable
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/shared_prefs/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/shared_prefs/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/shared_prefs/mtd0.img
cd /data/data/jackpal.androidterm/shared_prefs/
chmod 755 rageagainstthecage-arm5.bin flash_image
6. Run the exploit
Code:
/data/data/jackpal.androidterm/shared_prefs/rageagainstthecage-arm5.bin
After the exploit exits/finishes there should be a short system freeze, followed by inablity to issue any command from the terminal (don't worry). Exit the Terminal by long pressing HOME and force close the Terminal app from the Application Manager
7. Start the terminal again, a root prompt should be visible
8. Flash the misc partition
Code:
cd /data/data/jackpal.androidterm/shared_prefs
./flash_image misc mtd0.img
9. Reboot
...
Click to expand...
Click to collapse
No luck unfortunately, one of the steps requires the CID, and as you know I have not got USB to access fastboot mode.
Is there any other way to get the CID?
You should read the whole thread for the usb-fix
If I remember correctly you should use "cat /sys/class/mmc_host/mmc1/mmc1:*/cid" (without quotes) command from the terminal emulator.
The terminal emulator in your case will be the substitute for the fastboot, so everything is done via the former.
If you click the link to the quote, you'll see that there are number of people who got it sorted using this method. So just be patient and do the reading.
Ive got same problem, but have fastboot access.. Can I use regular terminal in windows then?
Well, you can use it to find the CID ("fastboot oem boot"), but the other commands in the guide quoted above are for a terminal emulator and are not the same as the ones used with fastboot. So in order not to get confused I recommend you to just use a terminal emulator, it's not harder than fastboot.
Well, i figured out that one on my own.. At least I learn something of this.. Anyway, when i try to execute first command in emulator I just get up "cannot create, directory nonexistent. Ive tripple checked the commandlines.. What could be wrong??
bump.........
Well I followed all the instructions, could get temp root access and flash a modified mtd0.img (which had the correct CID and Rom version) but still no USB. I tried it several times over and can't get anywhere. The hardware must be cactus! Time to throw it over a cliff !!

[Q] HTC Desire USB Bricked & Not Rooted [Q]

HTC Desire USB Bricked Without Root​
Hey guys, got a really tricky one for you here...
Some people may have seen a thread I posted the other day about problems that had arisen with my HTC Desire, well I have managed to find out that these problems are being caused by a USB Brick.
As of now I have managed to restore SD Functions however my phone will still not connect to the computer, and the phone won't recieve a network signal from Orange.
I read through this tutorial here and also this one here. My problem is, all the requirements of the fix, my device does not meet. My phone is not rooted, it is running the latest software and has the latest HBoot.
I also found this that looked very promising, however when I tried to log into my Google account on my phone, everytime it said it couldn't make a connection, I left it for a few hours and the same thing, I can't help but think this is due to the USB brick?
I just really need some help, is there anything I can do to restore USB functionality? The phone is being sent to HTC tomorrow, however I can cancel at any point. Please, I know there are so many amazing people on XDA that can help me. Thankyou
*UPDATE* - After using the Fastboot code to enable the SD Card, my Sim Card is now working. I have been able to log into my G-Mail account and download the terminal emulator which is an apparent fix in one of the posts I linked above, however this doesn't work. Please can someone help me
hy did you try to reinstal the software ???? the original os or an upgrade??
en_mih said:
hy did you try to reinstal the software ???? the original os or an upgrade??
Click to expand...
Click to collapse
I have done a factory reset, re-installed the PB99IMG and also flashed an RRU. All the problems persist
Really need help with this guys! E-Mail - [email protected]
jaaystott said:
Really need help with this guys! E-Mail - [email protected]
Click to expand...
Click to collapse
Hi.
If I understand well, you have got an USB brick, and your current situation is the following :
No S-OFF hboot, no ROOTED ROM, but SDCard reenabled, thanks to "fastboot oem enableqxdm 0" command in fastboot mode.
I'll try to drive you through the whole process for getting your phone back, since I've already encoutered this situation, and successfully solved it.
First step => Get a 'mtd0.img' file :
Go to "Menu>Settings>About phone>Software information>Kernel version", and write down your ROM version (2.6.32.15, for example)
Then, in fastboot mode, with USB cable connected to your PC, issue the following command
Code:
fastboot getvar cid
You should see your phone's CID, something like 'HTC__022'.
You then go to this site, provide both information 'cid' and 'rom version', and you'll get a 'mtd0.img' file.
Let me know when you've gone through this first step
leinad said:
Hi.
If I understand well, you have got an USB brick, and your current situation is the following :
No S-OFF hboot, no ROOTED ROM, but SDCard reenabled, thanks to "fastboot oem enableqxdm 0" command in fastboot mode.
I'll try to drive you through the whole process for getting your phone back, since I've already encoutered this situation, and successfully solved it.
First step => Get a 'mtd0.img' file :
Go to "Menu>Settings>About phone>Software information>Kernel version", and write down your ROM version (2.6.32.15, for example)
Then, in fastboot mode, with USB cable connected to your PC, issue the following command
Code:
fastboot getvar cid
You should see your phone's CID, something like 'HTC__022'.
You then go to this site, provide both information 'cid' and 'rom version', and you'll get a 'mtd0.img' file.
Let me know when you've gone through this first step
Click to expand...
Click to collapse
Hi,
I am very much interested in knowing about the complete procedure. Assuming we have done this first step, how to proceed from here?
HQRaja said:
Hi,
I am very much interested in knowing about the complete procedure. Assuming we have done this first step, how to proceed from here?
Click to expand...
Click to collapse
Next step will aim at flashing this 'mtd0.img' file onto the 'misc' partition.
Since we are S-ON, and the ROM is not rooted, we'll have to get temp root access. To do so, follow the steps below.
1.- Download the two files rageagainstthecage.tgz and flash_image, extract rageagainstthecage-arm5.bin, and copy rageagainstthecage-arm5.bin, flash_image, and the file mtdo.img at the root of your SD using any SD card adapter.
2.-Install 'Terminal Emulator' (free app on the Android Market) on your phone
3.- Issue the following commands from Terminal Emulator
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/mtd0.img
cd /data/data/jackpal.androidterm/
chmod 755 rageagainstthecage-arm5.bin flash_image
This will copy all three files to the right directory on your phone, and give exec rights to the files.
4.- Then run the program rageagainstthecage-arm5.bin from the Terminal Emulator
Code:
/data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
in order to get temp root access. Be aware that the phone will have some kind of erratic behavior, and will seem to crash.
5.- Quit Terminal Emulator, stop it (Menu>Settings>Applications>Manage applications>Terminal Emulator>Force stop), and relaunch it. You should see a pretty # character, indicating you've got temp root access.
6.- You then issue the following commands, in order to flash the misc partition of your phone with the correct mtd0.img file
Code:
cd /data/data/jackpal.androidterm/
./flash_image misc mtd0.img
7.- Reboot your phone, and enjoy !!!
PS : All credits come to Antubis, from the French forum FrAndroid, who posted a very clever tuto in french
leinad said:
Next step will aim at flashing this 'mtd0.img' file onto the 'misc' partition.
Since we are S-ON, and the ROM is not rooted, we'll have to get temp root access. To do so, follow the steps below.
1.- Download the two files rageagainstthecage.tgz and flash_image, extract rageagainstthecage-arm5.bin, and copy rageagainstthecage-arm5.bin, flash_image, and the file mtdo.img at the root of your SD using any SD card adapter.
2.-Install 'Terminal Emulator' (free app on the Android Market) on your phone
3.- Issue the following commands from Terminal Emulator
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/mtd0.img
cd /data/data/jackpal.androidterm/
chmod 755 rageagainstthecage-arm5.bin flash_image
This will copy all three files to the right directory on your phone, and give exec rights to the files.
4.- Then run the program rageagainstthecage-arm5.bin from the Terminal Emulator
Code:
/data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
in order to get temp root access. Be aware that the phone will have some kind of erratic behavior, and will seem to crash.
5.- Quit Terminal Emulator, stop it (Menu>Settings>Applications>Manage applications>Terminal Emulator>Force stop), and relaunch it. You should see a pretty # character, indicating you've got temp root access.
6.- You then issue the following commands, in order to flash the misc partition of your phone with the correct mtd0.img file
Code:
cd /data/data/jackpal.androidterm/
./flash_image misc mtd0.img
7.- Reboot your phone, and enjoy !!!
PS : All credits come to Antubis, from the French forum FrAndroid, who posted a very clever tuto in french
Click to expand...
Click to collapse
I already tried this process, it didn't work, when I did the RageAgainstTheCage command, it said searching for ADB, then something about not being able to find it, then when I restart the terminal and do the final command, it says permission denied -_-
jaaystott said:
I already tried this process, it didn't work, when I did the RageAgainstTheCage command, it said searching for ADB, then something about not being able to find it, then when I restart the terminal and do the final command, it says permission denied -_-
Click to expand...
Click to collapse
In order for rageagainstthecage to find adb process, you should tick 'USB debugging' in "Menu>Settings>Applications>Development>"
leinad said:
In order for rageagainstthecage to find adb process, you should tick 'USB debugging' in "Menu>Settings>Applications>Development>"
Click to expand...
Click to collapse
I could have fixed this myself aswell :| **** i just sent off my HTC Desire 30 seconds ago, no joke, the UPS guy just came and got it
jaaystott said:
I could have fixed this myself aswell :| **** i just sent off my HTC Desire 30 seconds ago, no joke, the UPS guy just came and got it
Click to expand...
Click to collapse
:-( (10 characters)
leinad said:
:-( (10 characters)
Click to expand...
Click to collapse
I really appreciate the help you gave me mate, even if I asn't able to fix my device, thankyou for the time.
leinad said:
Next step will aim at flashing this 'mtd0.img' file onto the 'misc' partition.
Since we are S-ON, and the ROM is not rooted, we'll have to get temp root access. To do so, follow the steps below.
1.- Download the two files rageagainstthecage.tgz and flash_image, extract rageagainstthecage-arm5.bin, and copy rageagainstthecage-arm5.bin, flash_image, and the file mtdo.img at the root of your SD using any SD card adapter.
2.-Install 'Terminal Emulator' (free app on the Android Market) on your phone
3.- Issue the following commands from Terminal Emulator
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/mtd0.img
cd /data/data/jackpal.androidterm/
chmod 755 rageagainstthecage-arm5.bin flash_image
This will copy all three files to the right directory on your phone, and give exec rights to the files.
4.- Then run the program rageagainstthecage-arm5.bin from the Terminal Emulator
Code:
/data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
in order to get temp root access. Be aware that the phone will have some kind of erratic behavior, and will seem to crash.
5.- Quit Terminal Emulator, stop it (Menu>Settings>Applications>Manage applications>Terminal Emulator>Force stop), and relaunch it. You should see a pretty # character, indicating you've got temp root access.
6.- You then issue the following commands, in order to flash the misc partition of your phone with the correct mtd0.img file
Code:
cd /data/data/jackpal.androidterm/
./flash_image misc mtd0.img
7.- Reboot your phone, and enjoy !!!
PS : All credits come to Antubis, from the French forum FrAndroid, who posted a very clever tuto in french
Click to expand...
Click to collapse
Thanks, will feature your method in a guide at my blog (while giving you and Antubis full credit for it of course). =)
trying to follow your guide to restore my phone to work again! having trouble though...
i have got to the point of installing terminal emulator but at the point of issuing second cat command it says no such file or directory..
moley10 said:
trying to follow your guide to restore my phone to work again! having trouble though...
i have got to the point of installing terminal emulator but at the point of issuing second cat command it says no such file or directory..
Click to expand...
Click to collapse
I found a way around this, as I was having the same problem. Try This ->
cat /sdcard/rageagainstthecage-arm5.bin > data/data/rageagainstthecage-arm5.bin
Do that for the two other commands that follow that, then follow the instructions as given, that should work.
HQRaja said:
Thanks, will feature your method in a guide at my blog (while giving you and Antubis full credit for it of course). =)
Click to expand...
Click to collapse
Link to your blog? =)
ok, so i did that, no longer got errors.. seemed to work but after reboot still the same, doesnt connect to my pc, and device manager it is still being shown as 'qualcomm cdma technologies msm' in other devices!
is the purpose of those commands to moved the files to certain directory? i can get temp root with visionary to perhaps just move the files in root explorer?
thanks for all the help. its much appreciated!
Hello,
I've got a similar problem but this solutions doesn't work for me, because I cannot create a CID.
Any ideas?
Thanks in advance
hi,
i managed to create files etc and still am stuck with the same problem... searched hi and low for days,
hopefully someone will be able to find us a solution..
You mean creating the mtd from that site? Thats because you need to type the Build Number not the kernel version.

Fix USB Brick No Root

Hi Guys, sorry if this has been posted before but i have just spent 14 hours trying to un usb-brick my desire. Each method seemed to need root which i had lost.
Eventually i found these instructions, they are not mine, i only found them so total kudos to the author. to keep it simple (and remember this is for unrooted desires:
Requirements:
Fastboot (part of Android SDK) installed. For instructions on setting up fastboot, search guide on how to install ADB & Android SDK.
HTC Desire USB Unbrick Files .
Android Terminal Emulator app (Install from Android Market)
Procedure:
Reboot your device into its bootloader (fastboot) mode and connect it to your computer via USB.
Launch a Command Prompt window on your computer and enter this command:
fastboot oem enableqxdm 0
On your phone, Go to Menu > Settings > About phone > Software information and note down the Kernel version that you see there. If you see more than just numbers, only note down the numbers e.g. 2.6.32.15.
In the Command Prompt window on your computer, enter this command:
fastboot getvar cid
Note down the CID that you get. It should be something similar to ‘HTC__022’.
Visit this site, enter the CID from step 4 and the kernel version from step 3 as the ROM version, and click ‘OK’. This will generate an mtd0.img file and prompt you to download it. Save it somewhere you will remember.
Now connect your SD card to your computer using a card reader device or another phone, and transfer the extracted HTC Desire USB Unbrick files as well as this mtd0.img to it. Make sure the files are in the root of the SD card and not in any folder.
Insert the SD card back into your phone.
Launch Terminal Emulator on your phone and enter these commands:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/mtd0.img
cd /data/data/jackpal.androidterm/
chmod 755 rageagainstthecage-arm5.bin flash_image
/data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
In case your phone seems to crash or shows erratic behavior, ignore it for now.
Completely quit Terminal Emulator: First press the ‘Home’ button and then go to Menu > Settings > Applications > Manage Applications > All, find ‘Terminal Emulator’ there and tap ‘Force Stop’.
Launch Terminal Emulator again. This time, you should see a # prompt instead of $, indicating you have achieved temporary root access necessary for the next step.
Enter these commands in Terminal Emulator:
cd /data/data/jackpal.androidterm/
./flash_image misc mtd0.img
Finally, reboot your phone and you’re done.
That’s all there is to it – your USB brick issue should now be fixed.
If Mods believe this is easily accessible elsewhere on XDA, please delete the post but it took me 14 hours of trawling the net to get my desire un-bricked
regards
Whilst the info is good it's quite useless without the actual links. I'm sure I've seen similar info within these forums before though. Fortunately I've not managed to brick mine (yet).
Parva4 said:
Whilst the info is good it's quite useless without the actual links. I'm sure I've seen similar info within these forums before though. Fortunately I've not managed to brick mine (yet).
Click to expand...
Click to collapse
Sorry about that, files now added to first post
Regards
Jamadant
Try to get visionary+ I don't think you can get it from the market but there are other places, this will give you temporary root as I couldn't get root using the rageagainstthecage, then extract the flash image and paste it with the mtd file in data, then carry on with the commands in as above after the root (so dnt enter commands for rageagainstthecage as that is a process for getting root)
If you need more details let me know as I know how it feels to almost have a very expensive paperweight
Sent from my HTC Desire using XDA Premium App
thanks for you to share this method
USB Brick HELP!
Hi, last night I got my htc desire bricked. Pc can't detect my phone and sd card.
As a requirement on your posted guide, i need to install ADB and Android SDK. But when I plugged my phone into my pc to install software drivers its showing "Qualcomm CDMA Technologies MSM Driver not found". Where can I get this drivers?
I tried also to enable SD card by "fastboot oem enableqxdm 0' in command prompt but "'fastboot' is not recognized as an internal or external command"
My phone details for reference:
Android 2.2
Hboot 0.93
Software 2.14.207.1
PVT3 Ship S-On
RAdio 5.09.05.30_2
Unrooted, O2 branded
How can I continue to unbrick my phone with these initial problems?? Can you suggest newer guide for my case?
PLEASE HELP!
USB Brick help...
after i force stop the terminal emulator when i try to lounch it again doesn't run.
i get a white screen and nothing more
have you guys any ideea why is this happening?
rugarai_3x said:
Hi, last night I got my htc desire bricked. Pc can't detect my phone and sd card.
As a requirement on your posted guide, i need to install ADB and Android SDK. But when I plugged my phone into my pc to install software drivers its showing "Qualcomm CDMA Technologies MSM Driver not found". Where can I get this drivers?
I tried also to enable SD card by "fastboot oem enableqxdm 0' in command prompt but "'fastboot' is not recognized as an internal or external command"
How can I continue to unbrick my phone with these initial problems?? Can you suggest newer guide for my case?
PLEASE HELP!
Click to expand...
Click to collapse
Follow my instructions here for fastboot :- http://forum.xda-developers.com/showthread.php?t=1176663
HBoot 1.02 S-On No Root
Hi!
I USB-Bricked my Desire PVT4. Now it is with HBoot 1.02 and official unrooted Gingerbread.
I tried common methods, but I cant get access to write misc partition.
I got my SD card working with fastboot oem enableqxdm 0. I made a valid mtd0 Image etc... but after copy the flash_image, rageagainstthecage and mtd0 the terminal emulator wont run after stopping the task.
Cant downgrade HBoot without root. Alpharev (revolutionary4-4) needs USB running in ROM.
Please !!!! I need help!!!!!
Thanx guys
Search for guide for usb brick.
TouchPaled from Oxygen with Transparent XDA App
MatDrOiD said:
Search for guide for usb brick.
TouchPaled from Oxygen with Transparent XDA App
Click to expand...
Click to collapse
I did (with help of Leinad):
http://forum.xda-developers.com/showthread.php?t=955845
Cant pass step 5! Relaunching the Terminal Emulator fails! Doesnt open anymore. I read, that writing Misc partition in HBoot 1.02 is not possible using this method.
Need working method for HBoot 1.02 with official gingerbread 2.3.3 in order to USB-unbrick my Desire!
Any ideas?
dexterm1 said:
I did (with help of Leinad):
http://forum.xda-developers.com/showthread.php?t=955845
Relaunching the Terminal Emulator fails!
Click to expand...
Click to collapse
Try to re-do all the steps..if it fails to open, before u can flash the misc partition, maybe u did something wrong..at least it should open and u should be able to run the commands to flash the misc

Kindle Fire Brick Utility not working

So i think I bricked my kindle fire. It is rooted and when trying to install a new ROM, i accidentally selected the fastboot option. Now, when I power it on, all i get is the logo and it never loads. I cannot get into the boot manager to try anything. I have tried the Kindle Unbrick utility from this link: http://forum.xda-developers.com/showthread.php?t=1428428 and it says waiting for device when I run the stuck on logo option. Is there anything else I can do? I really dont want to get another one. Any help would be appreciated! I can't post in the development forum so thats why i posted here. Thanks everyone.
What version of Windows are you using?
Read the WHOLE first post of the Unbrick Utility thread. It's a driver problem.
Thanks I got it to work now but now when I plug it into the USB, it does not show that I can open it and drop files. I go into TWRP and try to mount the USB and it will not let me and I am unsure what to do!
roykurka said:
Thanks I got it to work now but now when I plug it into the USB, it does not show that I can open it and drop files. I go into TWRP and try to mount the USB and it will not let me and I am unsure what to do!
Click to expand...
Click to collapse
If you're using an ICS ROM I don't believe mounting "mass storage" works on all of them.
Does it saying anything when trying to mount USB in TWRP? What does "won't let me" imply? Windows or TWRP throws an error message?
When I go into TWRP and go to MOUNT and then try to select Mount SDCard it will not let me check the box. I have a ROM running on it now but I cannot access the SD card when I plug it into the computer.
roykurka said:
When I go into TWRP and go to MOUNT and then try to select Mount SDCard it will not let me check the box. I have a ROM running on it now but I cannot access the SD card when I plug it into the computer.
Click to expand...
Click to collapse
What ROM are you using?
nchevaux said:
What ROM are you using?
Click to expand...
Click to collapse
i am using CyanogenMod 9.0.0-RCO-otter-UNNOFFICIAL
Also, when i go to the about tablet on the Kindle and look at Model Number, it shows Galaxy Nexus.....
Any other suggestions or help?
roykurka said:
Any other suggestions or help?
Click to expand...
Click to collapse
Boot into TWRP and get to a prompt using adb shell. Then use this command to open parted...
Code:
parted /dev/block/mmcblk0
When you get to the "(parted)" prompt...
Code:
print
The last line, the media partition, is what gets mounted as /sdcard on your device. It should have a "fat32" file system type. If you don't have that, you need to make a new filesystem on that partition.
Code:
mkfs 12 fat32
12 is the partition number and fat32 is the filesystem type you want to use to format the partition. If memory serves, parted will ask you for this information again to confirm. Remember... 12 and fat32. Once you are done, you can...
Code:
quit
Once you've done that, TWRP should be able to see the partition and allow you to mount it on your host computer. You might have to restart TWRP... I don't remember.
I have not been able to get adb to run. When i boot to TWRP and go to the command prompt and type adb devices it says " 'adb' is not recognized as an internal or external command, operable program or batch file."
I set the path to where the android sdk is located and it still doesnt work.
Im sure I sound like a newb or something but I am just not as tech savy with these kind of things. thanks everyone for your help with this.
roykurka said:
I have not been able to get adb to run. When i boot to TWRP and go to the command prompt and type adb devices it says " 'adb' is not recognized as an internal or external command, operable program or batch file."
I set the path to where the android sdk is located and it still doesnt work.
Im sure I sound like a newb or something but I am just not as tech savy with these kind of things. thanks everyone for your help with this.
Click to expand...
Click to collapse
Find the adb executable through Windows Explorer. Once you find the folder containing adb, shift-right-click inside that folder and select "Open command window here" and then you'll be able to use the adb command.
Another way to do it is to download the Kindle Fire Utility distribution and follow the third post in this link...
http://forum.xda-developers.com/showthread.php?t=1552547
You don't have to set the path to anything special if you do it one of those two ways.
roykurka said:
I have not been able to get adb to run. When i boot to TWRP and go to the command prompt and type adb devices it says " 'adb' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
It seems you have set your path incorrectly. I found it easiest to just copy the entire platform-tools folder to the root of C:\ and run adb from there (You could also use a Windows shortcut to cmd with "start in" filled out, or use shift-right click through explorer).
Definitely try to get adb working; when I first rooted my Kindle it took me an hour to fix a boot-loop without adb (damn drivers), and only seconds with adb.
kinfauns said:
Boot into TWRP and get to a prompt using adb shell. Then use this command to open parted...
Code:
parted /dev/block/mmcblk0
When you get to the "(parted)" prompt...
Code:
print
The last line, the media partition, is what gets mounted as /sdcard on your device. It should have a "fat32" file system type. If you don't have that, you need to make a new filesystem on that partition.
Code:
mkfs 12 fat32
12 is the partition number and fat32 is the filesystem type you want to use to format the partition. If memory serves, parted will ask you for this information again to confirm. Remember... 12 and fat32. Once you are done, you can...
Code:
quit
Once you've done that, TWRP should be able to see the partition and allow you to mount it on your host computer. You might have to restart TWRP... I don't remember.
Click to expand...
Click to collapse
When i try the first command, i get the same response saying parted is not recognized as an internal or external command, operable program or batch file.
I have the kindle in TWRP and connected to the PC. What do I do now?
roykurka said:
When i try the first command, i get the same response saying parted is not recognized as an internal or external command, operable program or batch file.
I have the kindle in TWRP and connected to the PC. What do I do now?
Click to expand...
Click to collapse
okay... I'm going to make this super easy for you... get ADB working...
1. Download attached "adb.zip"
2. Extract adb.zip to a folder
3. Double-click "CLICK ME!!!"
4. Type "adb" and see instructions come up
5. Type "adb devices" and see a 12-digit code
now reread your own thread and try all those instructions again in ADB
P.S. type "ADB shell" before trying the instructions from kinfauns
When I type the adb devcies it says "list of devices attached but does not show anything.
I apologize for probably something so simple
roykurka said:
When I type the adb devcies it says "list of devices attached but does not show anything.
I apologize for probably something so simple
Click to expand...
Click to collapse
I think you should back up a bit and read this...
http://forum.xda-developers.com/showthread.php?t=1552547
Start at post #1... follow the steps in #2 and confirm your device drivers are getting loaded properly... study #3 for fastboot and adb commands.
#2 is going to be the most important for you because it looks like there's a problem with your device drivers or you are missing a necessary initialization file. Following the directions there will get you fixed up.
After doing all that, go back to my previous post.
It works, I got to mount the SD card and everything. Thank You everyone for all of your help!

[Q] ROM install SDCard USB issues.

So, my problem is that I have recently unlocked the bootloader on my HTC One X using my Mac and the very helpful guide provided on this YouTube link
http://youtu.be/8Y3VbFJIwWU
No problems with the process in that video and I've gotten to the end with the phone bootloader definitely.
My problem is that I've then attempted to install a custom ROM from the SD card. Again, this seems to work fine, but upon reboot I'm immediately hit with a continual pop-up 'unfortunately, the process com.android.phone has stopped' with the only option to press ok. It loops continuously.
I suspect I may have to reinstall the ROM onto the SD card, but this is my problem. I cannot get my phone's USB access to work on my Mac as I am stuck with the above pop-up preventing me. I can't seem to access it via Recovery either.
Can I use fastboot to 'flash' over the *.img or *.zip of a new ROM to get it onto the SD card? Stuck with a phone I can't use otherwise. :crying:
Thanks.
Mount usb storage from the recovery.
Sent from my HTC One X using xda app-developers app
or while in recovery type
Code:
adb push rom.zip sdcard/
Thanks for that, athulele . :good:
I have tried that. On a Mac, for USB access requires that I use software called 'Android File Transfer' rather than the way Windows would do it. That software doesn't kick in via Recovery mounting. So, I'm going to need a different approach.
Since I have Windows installed via Bootcamp, I think I'll try to connect the phone up via Windows and see whether I can access the SD card via USB using that route.
Any other help is most welcome.
you do not need that file, just boot into recovery and type the command above... it's the easiest way
matt95 said:
you do not need that file, just boot into recovery and type the command above... it's the easiest way
Click to expand...
Click to collapse
Having booted into recovery, using Terminal on my Mac and typing
adb push sentinelrom_v4_30_endeavoru.zip sdcard/
gives the following message:
-bash: adb: command not found
Am I doing something wrong here?
well, have you got the sdk installed on your mac?
matt95 said:
well, have you got the sdk installed on your mac?
Click to expand...
Click to collapse
I've now downloaded the sdk for mac. It's a adt bundle folder with many files inside. I've installed 'Eclipse' but I'm still getting the same message as before from the Terminal. What else do I need to do here?
Im not into macs .... but don't you need to enter sudo commands before the adb/fastboot commands ?
no, he only needs to navigate to the adb directory with the terminal and then type
Code:
./adb push rom.zip sdcard/
matt95 said:
no, he only needs to navigate to the adb directory with the terminal and then type
Code:
./adb push rom.zip sdcard/
Click to expand...
Click to collapse
Hi matt95
I'm grateful for the help you are giving me here. I've found the adb file within the following downloaded directory path:
act-bundle-mac-x86_64-20130219 - sdk - platform-tools - adb
When I changed directory in Terminal to this path and ensured the specific rom.zip was also in that path, Terminal is still giving me this:
./adb push sentinelrom_v4_30_endeavoru.zip sdcard/
-bash: ./adb: No such file or directory
I must be doing something not right. Please help further.
that's strange, could you provide me the platform-tools folder and the rom.zip folder? i'll write down what you exactly have to write...
matt95 said:
that's strange, could you provide me the platform-tools folder and the rom.zip folder? i'll write down what you exactly have to write...
Click to expand...
Click to collapse
Folder contents as described.
Thanks.
ok now i need their directory, for ex. /User/yourusernane/Docuemnts/ecc ecc......
matt95 said:
ok now i need their directory, for ex. /User/yourusernane/Docuemnts/ecc ecc......
Click to expand...
Click to collapse
/Users/srafferty73/Downloads/adt-bundle-mac-x86_64-20130219/sdk/platform-tools
and
/Users/srafferty73/Downloads/adt-bundle-mac-x86_64-20130219/sdk/platform-tools/sentinelrom_v4_30_endeavoru
Thanks.
ok, now open the therminal ans type
Code:
cd /Users/srafferty73/Downloads/adt-bundle-mac-x86_64-20130219/sdk/platform-tools
./adb push (drag the rom.zip into terminal) sdcard/
now it should work
matt95 said:
ok, now open the therminal ans type
Code:
cd /Users/srafferty73/Downloads/adt-bundle-mac-x86_64-20130219/sdk/platform-tools
./adb push (drag the rom.zip into terminal) sdcard/
now it should work
Click to expand...
Click to collapse
Slowly making progress. Latest Terminal message after doing that reads 'error: device not found'.
I am using ClockworMod Recovery v5.8.2.7 and have clicked on 'mount /sdcard'. I have tried to 'mount USB storage' but am getting an error message which reads 'E: Unable to open ums lunfile (No such file or directory).'
What should I do next?
Thanks.
fingerbob said:
Slowly making progress. Latest Terminal message after doing that reads 'error: device not found'.
I am using ClockworMod Recovery v5.8.2.7 and have clicked on 'mount /sdcard'. I have tried to 'mount USB storage' but am getting an error message which reads 'E: Unable to open ums lunfile (No such file or directory).'
What should I do next?
Thanks.
Click to expand...
Click to collapse
Flash a newer recovery.
Mr Hofs said:
Flash a newer recovery.
Click to expand...
Click to collapse
I managed to find a copy of ClockworkMod Recovery v5.8.4.0 and flashed this as advised. This has somehow enabled the USB facility on my phone to start working again and I can replace the ROM I've downloaded onto it.
I just tried reinstalling the ROM I had again, but once again got the original message stated in my first post. I'm about to now try a different ROM to see if that makes any difference.
:good:

Categories

Resources