Hey,
this started that I wanted to create a NANDROID backup using AlphaRev; the recovery worked fine, I was able to copy everything to my computer (using AlphaRev's mass storage mount function). However then, after I unmounted, somehow everything broke. I could no longer access my sd card, neither in the bootloader (which just returns E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)), and also not in Android itself (I'm running Oxygen, and that is still running, except that all programs are missing, probably due to missing sd card or whatever).
So I searched, and found this post which led me to this USB unbrick tutorial. As I'm unable to use adb (can't find the device), I guess it is a USB brick.
However in the bootloader, it says "HBOOT USB PLUG", so it at least seems to see the USB somehow. Anyhow, I tried to restore the SD card functionality using that first step, and got an error:
Code:
> fastboot oem enableqxdm 0
...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s
I also tried a few other options, like a simple "fastboot reboot-bootloader", but that fails as well. "fastboot devices" does list my device ("phoneid fastboot"), so at least that works. However I have no idea how to proceed now, given that the fix to restore my phone doesn't even work.
What can I do? Please help me.
Okay, I have no idea how I did this now, but the "fastboot oem enableqxdm 0" suddenly worked. As expected this did not restore my USB connection, so I really am bricked. I could however restore my NAND-backup, so I am running a fully working Android again.
I wanted to continue in the USB-Brick Fix howto now, but I actually have no idea how to put those files on my SD card. I don't have a Micro-SD card reader, and accessing the sd card via my phone obviously doesn't work. Is there any other way? Otherwise I'm going to buy myself a Micro-SD card reader now.. :/
Also I wanted to use the CID Generator in that post (as my CID is "HTC__102"), however where do I find out the ROM version? I'm using a custom ROM, so obviously HTCs version number does not apply. Do I have to use the first version number from my backup RUU (that's the only number that has the same format)? Because that one would be "2.29.405.5".
Thanks for your help!
[edit]
God, I'm stupid! I do have a working Android… so I can just download the files on my phone and place them there myself.. Doh..
[edit2]
Okay, I got everything working again! Now I can try to do what I initially wanted to start with (flashing a different partition layout..); or I'll wait for tomorrow, because this really made me worry a lot D:
Thanks anyway
Related
So today, I was upgrading from modaco 2.7 to 2.7.1,
after the upgrade (using recover mode and the signed zip file (core chinese)), I did a system wipe and reboot the device with the USB still plugged in my PC, and everything seems to be normal until my pc's tray notification pops up with the "unknown device found" message - i thought it was a little bit odd, so then I waited for the hero to boot up completely - it reboots after showing the HTC logo once, and then it boots normally to the setup wizard (select language, etc);
I then followed the normal procedure of typing all the wifi, flickr, gmail stuff in, and when i got into Rosie, it shows a notification icon on the hero saying "SD Card removed". I can't access the SD card, nor my pc can recognize the hero. I ejected the SDCard and re-insert it but it's not detected either. HTC Sync on the device does not give a notification nor the mass storage notification shows up either.
I tried rebooting into recovery mode, (Hero 1.2.3) and i can see the menus just fine; however, when i try to mount SD card as usb, or flash update.zip or any zip, or fix ext3, or clear dalvik-cache or wipe the sdcard's ext partition, it keeps giving me errors saying
error: run 'whateverprogram' in terminal
when i try to set 'USB Mass storage on', it says "Error enabling USB mass storage! Run ums_enable manually from console.
I then try to login the device using adb shell through window's command prompt, it says device not found as well.
giving up, i tried to reboot teh device into fastboot mode, the PC recognizes the USB device just fine. it's really odd.
Anyway I can do a recovery on this to make these device work again?
p.s. when i try to choose zip file in recovery mode, it says
Code:
"E: Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)
Can't mount sdcard, aborting".
after every reboot (shutdown, start), the setup wizard shows up again as if I have not written anything on my device after any setup.
I can't download anything to run on the Hero as it requires the SD card. I can't flash any recovery images either as again it requires the SD card.
Any ideas??? I'm left with a half-brick now
Update1: using ConnectBot I can login my own device using root,
it shows the following when i run df -h:
Code:
/dev/block/mtdblock3 1700M 157.3M 12.7M 93% /system
/dev/block/mtdblock5 165.8MB 12.8M 152.9M 8% /data
/dev/block/mtdblock4 130.0M 1.2M 128.8M 1% /cache
kazuni,
Can you read SD card in your PC?
Several persons reported problems with SD card after upgrading to modaco 2.7 or 2.7.1. They have to format SD card.
Al936 said:
kazuni,
Can you read SD card in your PC?
Several persons reported problems with SD card after upgrading to modaco 2.7 or 2.7.1. They have to format SD card.
Click to expand...
Click to collapse
Thanks for the quick reply.
I have tried doing so, in fact, i have 4 SD cards to try and none of them are readable in the Hero; they are readable using a card reader in my PC though.
kazuni said:
Thanks for the quick reply.
I have tried doing so, in fact, i have 4 SD cards to try and none of them are readable in the Hero; they are readable using a card reader in my PC though.
Click to expand...
Click to collapse
Update2: the only way that my pc can detect my device as "My HTC" is when i boot it into fastboot mode; unfortuantely there are no way for me to update the device in this mode, so i can't do anything to modify the rom, or to check it using dropbear or any shell client. =\
C:\Documents and Settings\user>fastboot devices
HT97RL900725 fastboot
it sees it just fine.
I wonder if the goldcard method + fastboot update will work or not; let me give it a shot and try to flash it back to 405.5 first ;\
update3: can't. fastboot update is still locked for any rom type.
damn man. its freaking. i am not going to update to 2.7.1 untill this issue is resolved.
still no go.
im left with a half-bricked device that:
1) clean wiped, normal boot, cannot detect SD card nor the Hero is detectable by XP.
2) clean wiped, recovery mode, can't run any of the script except :
Reboot System Now
Wipe data/factory reset
Fix apk uid mismatches
Fix rotate
3) can't download anythign from browser as it needs to save onto sd card.
4) android market doesn't have flashrec so i can't reinstall the recovery image.
wget ftp://myhost/system.img /data/
flash_image system /data/system.img
hope this works
When you are in the shell check out the file /proc/cmdline.
Would be interresting to see if the HBOOT send a command line to the kernel to disable the SD card.
packetlss said:
When you are in the shell check out the file /proc/cmdline.
Would be interresting to see if the HBOOT send a command line to the kernel to disable the SD card.
Click to expand...
Click to collapse
can't. It doesn't even boot into normal mode, nor boot loop. it just holds at the HERO logo.
I think I have the same problem, i can charge my phone but trying to mount my phone to either my pc or mac it just won't be picked up
tried using RUU with a goldcard, no go. remote not allowed (fastboot flash system system_rel.img, nor fastboot boot boot.img or fastboot flash boot boot.img. no go. sigh.)
now i have a brick :\
wonder if there is any way to go into fastboot mode and flash ANY part of the blocks (device, recovery, or system, if at all).
Some progress: using hboot mode, i placed HEROIMG.zip into the sdcard and it loads successfully. it works! and im now rolled back to official 2.7.405.5; however, the USB and the sd card is still dead ;\
I guess I'll be bringing it back to HTC to see if they would do anything about it (fortunately It's now back to stock recovery and 2.74.405.5)
I managed to do the same thing, i'm hoping the tmobile will replace my phone
hi all,
I am having the same issue... what I don't understand is: it has to be a software problem, because, from what I've read, everyone of us have been installing radio and firmware updates to the htc hero, and since some of these updates the USB and sdcard mounting is not properly working... I believe it's not possible to break a USB port just by installing software...
so there should be a way to fix this other than sending the phones back... If anyone has any suggestion I can try it on my phone
cheers : )
I know it's weird! Funny thing is, official updates includes radio + recovery + pretty much every part of the rom is being re-flashed (including hboot, from what i understand); how ever, ONLY in hboot mode, the device is recognized properly as "Android USB" by windows.
Some of your problems I had to. To be exact: that my pc wouldn't recognize the phone when connected with usb except for fastboot and charging.
For weeks I searched and found some people with similar problems, but never a solution.
I had no problems with my sdcard however.
Now my problem is gone. How? I had the HTC Generic 2.73.405.5 ROM (pre-rooted and packaged as update.zip by MoDaCo) and decided to update to Paul's ROM v2.5.
After I was finished with the installation wizard and connected the phone with usb to my pc everything suddenly worked again!!!
So I got the usb and HTC Sync notification at the top of the screen and can mount the sdcard using the notification bar.
This tells me that in my case it definately wasn't a hardware problem as I always thought, but a software one.
I hope you can something with my experiences because I know how frustrating it is when this doesn't work!
dennis333 said:
Some of your problems I had to. To be exact: that my pc wouldn't recognize the phone when connected with usb except for fastboot and charging.
For weeks I searched and found some people with similar problems, but never a solution.
I had no problems with my sdcard however.
Now my problem is gone. How? I had the HTC Generic 2.73.405.5 ROM (pre-rooted and packaged as update.zip by MoDaCo) and decided to update to Paul's ROM v2.5.
After I was finished with the installation wizard and connected the phone with usb to my pc everything suddenly worked again!!!
So I got the usb and HTC Sync notification at the top of the screen and can mount the sdcard using the notification bar.
This tells me that in my case it definately wasn't a hardware problem as I always thought, but a software one.
I hope you can something with my experiences because I know how frustrating it is when this doesn't work!
Click to expand...
Click to collapse
I tried this but it didn't seem to work for me, so I just put the official rom update and sent the phone back to my network saying that it was broken, now i've gotta wait for another 2-3 weeks to get my phone back , but i'm hoping they'll give me a new phone as i did kinda drop it and there two scuff marks on it
hello dennis333,
today I tried going from 2.8 to the HTC generic ROM you told, and then to 2.5. no results.
I also installed the official HTC / Orange Rom update, which I have now. It has improved a bit because now when I plug the USB cable the PC detects something, but it does'nt work... it says 'unknown device' (tried this on two computers)
when I boot to fastboot ( BACK + POWER BTN ) my computer detects Hero ok (My Htc)
I really don't know what else to try...
I saw another post from someone who had the exact same problem and got it fixed by installing SPL and ROM from fastboot menu
http://forum.xda-developers.com/showthread.php?t=556038
I tried it too, but when trying to use the SPL zip file he says I get an error ( I guess it's because he has a T-Mobile and I have an Orange Hero)
[update]: I finally got the SPL to flash correctly and then installed a modaco 2.8 ROM, but I still cannot connect the Htc Hero to the PC via USB.
regards
cwm v3.2.0.0
cwm v3.0.0.5
RA v2.0.0
All now
"E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(no such file or directory)
E:Can't mount /sdcard"
This happens with both cm7 and bravo Hboots and different SD cards repartitioned SD card (well recovery reported 'done'), SD card works fine in my PC.
I'm s-off, the trouble all started when I noticed that there was a new cwm recovery this morning and applied it through Rom Manager.
Got a bricked phone now unless someone can help, OS doesn't load past my custom boot splash screen. I can flash new Hboots and recoveries but can't get a rom to load from a recovery.
Help please
Matt
(searched the forum to no avail!)
Hboot will not see a PB99IMG.zip either
SOLUTION
Yes, I was totally unable to see the sdcard, the problem was the phone not the sdcard:
With phone in Hboot Fastboot mode
At the commant prompt on my Win 7 32 bit PC:
C:\adb\tools\fastboot devices
SH11APL03395 fastboot
C:\adb\tools\fastboot oem boot
Blah blah blah
INFOCID is ORANG001
Blah Blah Blah
C:\adb\tools\fastboot oem enableqxdm 0
...OKAY [ 0.164s]
finished. total time: 0.165s
C:\adb\tools\fastboot oem eraseconfig
...INFOEraseconfig complete
All recoveries and Hboots can now mount the sdcard, The last command which I initially omitted gave me USB connection and Bluetooth problems.
Now all sorted, hope this helps someone.
Thanks for all your efforts guys
Matt
would the clockwork mod recovery topic be a good place to post?
Last post on there might help you - have you repartioned your sd?
--------------------------------------------------------------------------------
hello I just wanted to test this new recovery, to be updated ^^
I had installed on my phone RA_recovery 2.0.0 which works fine, so I flashed ClockworkMod Recovery - 3.2.0.1 zip file and during restart my system can no longer mount my SD card .... now I'm trying to debrick it
Be careful before flashing this file, it's just an advise !
Edit: I looked better at my problem and it seems to come from the EXT partition that no more recognized...
hi,
@msivister try this command => fastboot oem enableqxdm 0
you do this in fastboot (boot into bootloader), i guess this is not a brick device.
hope this help
I get
... FAILED <status malformed <1 bytes>>
finished. total time: 0.002s
I had a look at the modaco downgrade hboot thread but the CID editor page is obsolete, should I persue that avenue?
Thanks
Matt
did you try re-partioning your card? maybe your ext is corrupt
Or try another sd card
Blank sd, reformat, put new rom zip on sd via PC, sd in phone, full wipe then flash it?
msiviter said:
I get
... FAILED <status malformed <1 bytes>>
finished. total time: 0.002s
I had a look at the modaco downgrade hboot thread but the CID editor page is obsolete, should I persue that avenue?
Thanks
Matt
Click to expand...
Click to collapse
I'd try again, make sure your in fastboot not the bootloader screen.
I had the exact same problem last night (i used clockworkmod to flash their recovery over amonras) and that modaco thread (link below) worked for me.
Still took a lot more steps after that to get a working ROM on there though.
I'll stick with AmonRa and flashing though the recovery from now on!
http://android.modaco.com/content/htc-desire-desire-modaco-com/309939/usb-brick-rickrolled-b0rked-fixed/
hi, agree with stringer, seems to be a bad partition table... redo your partition with gparted
fragargon said:
hi, agree with stringer, seems to be a bad partition table... redo your partition with gparted
Click to expand...
Click to collapse
If the problem is similar to mine then he's not going to see the sdcard from his phone no matter how its partitioned.
Sent from my HTC Desire using Tapatalk
unable mount sdcard - solved
Yes, I was totally unable to see the sdcard, the problem was the phone not the sdcard:
With phone in Hboot Fastboot mode
At the commant prompt on my Win 7 32 bit PC:
C:\adb\tools\fastboot devices
SH11APL03395 fastboot
C:\adb\tools\fastboot oem boot
Blah blah blah
INFOCID is ORANG001
Blah Blah Blah
C:\adb\tools\fastboot oem enableqxdm 0
...OKAY [ 0.164s]
finished. total time: 0.165s
Alpharev bravo Hboot
CWM v3.1.0.1
All recoveries and Hboots can now mount the sdcard, I dont know why the 'enableqxdm' command worked this time, I'm by no means an expert! All I know is that my phone is useable again- hurrah!
Thanks for all your efforts guys
Matt
Cool, glad your up and running.
I'm having a bit of a weird problem now I've managed to put a rom (insert coin) back on. Neither the phone or my pc see each other over usb and bluetooth will not turn on.
Do I need to run the usb brick fix or something?
I've tried putting the recommended radio on.No change.
Any ideas?
Edit: sorted,see first post.
Yeah, that's what I had to do. (Flash the update.zip fix from modaco)
Sent from my HTC Desire using Tapatalk
Instructions in first posted sorted me out, thanks a lot!
Thanks a lot!! Sorry for reviving this thread, but I looked for ages around the web for a solution to this problem, tried lots of stuff and only your solution worked for my Desire. So I'm posting some details about the problem that haven't been referenced in the thread, to make the topic come to the surface of search results more easily. Perhaps a sticky would be in order, since I saw this affects quite a number of people?
Anyway, the problem is that, at some point, the phone stops seeing the sdcard. Can't mount it from Recovery, can't access it to install zips, can't even partition it. For some, like in my case, not even Android can see the SD, which causes some grand headaches.
The error messages in the recovery (from what I've gathered, it seems the problem has been linked to ClockwordMod recoveries) are the following:
- E:Can’t mount /sdcard
when trying to access the SD card directory
- Unable to open ums lunfile (No such file or directory)
when trying to mount the card as USB storage
The real bummer in this case is that the SD card appears (and is) perfecty healthy and can be viewed and manipulated on a PC via card readers. The solution is a bit obscure with all those commands to issue to fastboot, and this is the only thread listing them that I found.
So, thanks!
billerr.g said:
Thanks a lot!! Sorry for reviving this thread, but I looked for ages around the web for a solution to this problem, tried lots of stuff and only your solution worked for my Desire. So I'm posting some details about the problem that haven't been referenced in the thread, to make the topic come to the surface of search results more easily. Perhaps a sticky would be in order, since I saw this affects quite a number of people?
Anyway, the problem is that, at some point, the phone stops seeing the sdcard. Can't mount it from Recovery, can't access it to install zips, can't even partition it. For some, like in my case, not even Android can see the SD, which causes some grand headaches.
The error messages in the recovery (from what I've gathered, it seems the problem has been linked to ClockwordMod recoveries) are the following:
- E:Can’t mount /sdcard
when trying to access the SD card directory
- Unable to open ums lunfile (No such file or directory)
when trying to mount the card as USB storage
The real bummer in this case is that the SD card appears (and is) perfecty healthy and can be viewed and manipulated on a PC via card readers. The solution is a bit obscure with all those commands to issue to fastboot, and this is the only thread listing them that I found.
So, thanks!
Click to expand...
Click to collapse
it's funny you should mention that this should be stickied because a few hours ago I added this to my troubleshooting guide.. which is a sticky
I had the same issue a week ago
i have same issue like this
Thanx
I've just needed to go through this and thankfully it helped. Any idea what causes it?
(Btw. Probably first post should underline to check whether you are in fact in fastboot. I booted into HBOOT waited till buttons were available then selected fastboot and I stayed in Hboot. Which I did not notice so I also got errors on fastboot commands. Selected fastboot again and then it worked.)
And as an FYI. Fastboot.exe was accidentally left out of recent SDK installs (R14, R15), so you have to manually download it [There's a link in Android Issue 21115 on google code (comment 3). This is the link: http://tools.android.com/knownissues#tools_r14 ,look at the end of section Tools R14] and put it in /platform-tools ! (As adb itself was moved from /tools to platform-tools).
Saved me from a dead SDcard slot
Many thanks, this thread also worked for me - Desire with ICS, lost all sight of the SDcard, whether from recovery or from ICS.
After "C:\adb\tools\fastboot oem boot" I got a black screen with a flashing green LED - most odd! But I took the battery out, rebooted into Fastboot USB, typed "fastboot oem enableqxdm 0" and it worked. Phew!!
Hi there, I'm having a bit of a crisis, I'll try and describe as accurately as possible:
- I decided I wanted to install a new rom, with Android 2.3 and HTC Sense 3.5
- The rom required going back to to the stock hboot, which as far as I know and can tell (I'm far from even averagely knowledgeable) turned S-ON (the hboot I've got now is 0.93.0001)
- It also required a 1024mb Ext4 partition on my SD card, which I created
- The rom got stuck in a loop at boot, so I entered recovery to try and restore my previous rom (which I had backed up both on the SD card and a copy on my hard drive)
- While there I discovered that recovery was finding an error with the Ext4 partition, and wasn't able to mount it
- I went back and reformatted my SD card to get rid of the Ext4 partition, thinking that if I was restoring to the rom I was using previously I should put the SD card back the way it was
- I transferred the hard drive backup of my previous rom onto the SD card
- When trying to restore the backup I get an error saying:
E:Can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)
(Invalid argument)
E:Can't mount /sdcard
Click to expand...
Click to collapse
- Googling and looking around here led me to download the Android SDK files and attempt to go through fastboot to "USB unbrick". I've tried
fastboot oem enableqxdm 0
Click to expand...
Click to collapse
Which works, and
fastboot oem eraseconfig
Click to expand...
Click to collapse
Which doesn't, presumably because the phone is S-ON
- so I go to adb to try and turn S-OFF by following the steps here: wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Rooting, because I figure it's likely to be the same way for a Desire as it is for a Desire Z. When I try the first command ("adb push busybox /data/local/tmp/) I get back "error: device not found". This is despite fastboot commands working, and the SD card showing up on the PC if I mount it through recovery.
That's everything I think so far. I've tried a few solutions here and on various sites, but everything fails.
If anybody has any suggestions they are extremely gratefully received, whether they work or not! I'll try anything, really.
I think that if I can get the SD card to actually mount I'll be good to go; I'll be able to restore my previous rom and all should be well. But I expect I need to find a way to turn S-OFF for anything to work? Is that right? And is there any way to do that another way using adb (or getting the adb method I was trying to work) or without an sd card/an actual loading and running operating system?
Again, anything at all appreciated. I think I've included all the information I have?
Thanks!
phonicparty said:
- so I go to adb to try and turn S-OFF by following the steps here: wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Rooting, because I figure it's likely to be the same way for a Desire as it is for a Desire Z. When I try the first command ("adb push busybox /data/local/tmp/) I get back "error: device not found". This is despite fastboot commands working, and the SD card showing up on the PC if I mount it through recovery.
That's everything I think so far. I've tried a few solutions here and on various sites, but everything fails.
Click to expand...
Click to collapse
What made you think that what works on DesireZ would work on Desire?? There's a separate section on that wiki for HTC Desire. Just sayin.
If you want root, check http://revolutionary.io
But don't go ahead and do anything yet. Your story is lacking some info. So what was your old rom, what was the new one you tried. How did you manage to change the hboot? If you weren't using stock hboot before, then you should already know the correct tools to s-off your phone. Oh and one more thing so do you have a Desire or a DesireZ??
Please post more information from hboot (start phone with pressed volume down + power button).
In my opinion the best way for you is to flash 2.3.3 RUU for a fresh rom and then use revolutionary to get S-OFF and root.
Gday
I was wondering if it were possible to get some help. I have been playing around with my HTC one x and have unlocked the bootloader, placed the clockwork recovery on there and have flashed cyanogen 9 onto the device. It booted up just fine but when i tried to flash a different rom suddenly i couldnt see any of my files from within clockwork recovery. Now i can only get into fastboot and clockwork recovery and cant mount usb within clockwork as i get an an error saying um lunfile cant be found.
Since then i have tried everything i could do within clockwork recovery and fast boot, as well as using adb and quick adb pusher to try and get some files onto my device so i can get it back up and running. Nothing seems to be working. It seems as though I have lost the connection with my sd card somehow?
The closest i have gotten to getting things to work is within quick adb pusher where it will detect my device but when i browse to tell it where to put the files on my device there are no folders, just an error folder called '"/error: device not found/". In the information it says that it faled to mount as r/w.
I have also been trying out adb with commmands such as "fastboot erase cache" but just get a
"failed (command write failed (unknown error))".
Does anybody know what might be going on here? is this something ive done and can be fixed or has my sd card just failed? if so do you think HTC will fix it for me?
Many thanks in advance to any help i can get here!
... Camm
use the newest ClockworkMod (5.8.4.0), that bug (ums lunfile) has been fixed since June. You're likely on 5.8.3.1 or older.
Hey guys I need help, I've been trying to fix my phone for days now with no luck.
(HTC Desire)
Basically this is what happend. I had an MIUI Rom for ages and decided I want to update it. So I used my SD card and downloaded the new rom and flashed it all worked fine.
I then read I should make a ext partition and in the process of it I broke my sd card some how and my phone stopped booting. So I followed a tutorial to put the Rom back on my phone by using adb push to put the rom in the data partition of my phone. But the data partition on my phone was only 140mb and the miui rom was 180mb so I got a smaller 120mb rom and pushed it to the phone and flashed it using adb shell recovery --update_Package=DATA:Rom.zip or something along those lines.
So the rom was working fine but I really didn't like it so my friend offered for me to use his sd card to put my old rom back. So i went through the process but when I clicked install file from zip it just said "no files found" but I know the rom was there. I tried using the adb shell recovery command except with /sdcard/ rather than DATA and I just got signature verification failed. I disabled signature verification in recovery and it still gave me the same error on the phone but on the command prompt window i keep getting these errors:
insmod: can't insert '/res/modules/crc16.ko': invalid module format
insmod: can't insert '/res/modules/jbd2.ko': invalid module format
insmod: can't insert '/res/modules/ext4.ko': invalid module format
After messing about a bit more my phone crashed so I had to remove the battery and my friends SD card became unreadable and needed formatting. He won't let me use it now lolol.
So now im in a position where my phone won't boot at all and when I try to use adb shell to flash a new rom I get those errors in command prompt and signature verification failed. I've also discovered im getting these errors regardless of whether the rom is there or not.
Sorry for the long post but im desperate and any help would be very much appreciated!
Does your phone still boot in hboot?
You need to find a working sd-card. What did you use to partition it? How did you break it?
abaaaabbbb63 said:
Does your phone still boot in hboot?
You need to find a working sd-card. What did you use to partition it? How did you break it?
Click to expand...
Click to collapse
I used minitool partition wizard I think. I followed some steps in a guide and when I put the SD card into my phone after it said "unrecognised SD format" or something similar so I tried the process again and which point my phone doesn't pick up the SD card at all anymore. So I put it in a memory card reader on my pc and it still picks it up so i deleted all the partitions and reformated it and still only my PC will pick it up phone just says insert SD card.
When I turn on my phone it says HTC for a split second then goes straight to fastboot as if i was holding down vol down + power when I power it on.
Why doesn't the push rom to DATA partition and recover from there work anymore?
giflet said:
I used minitool partition wizard I think. I followed some steps in a guide and when I put the SD card into my phone after it said "unrecognised SD format" or something similar so I tried the process again and which point my phone doesn't pick up the SD card at all anymore. So I put it in a memory card reader on my pc and it still picks it up so i deleted all the partitions and reformated it and still only my PC will pick it up phone just says insert SD card.
When I turn on my phone it says HTC for a split second then goes straight to fastboot as if i was holding down vol down + power when I power it on.
Why doesn't the push rom to DATA partition and recover from there work anymore?
Click to expand...
Click to collapse
You broke your sd-card by using Minitool. Why do you guys use it anyways?!? If you get a new sd-card, check the guide in my sig.
I think you don't need an sd-card to flash a RUU by the exe method. Get the Official 2.3 RUU by these means:
http://forum.xda-developers.com/showthread.php?t=1772499
Extract the "RUU_HTC Desire Android 2.3 Upgrade (Gingerbread).exe" from within the "HTC Desire Android 2.3 Upgrade.zip:" then connect your phone to your PC in fastboot, and run the exe.
You will probably need HTC Sync installed, and fastboot drivers.
abaaaabbbb63 said:
You broke your sd-card by using Minitool. Why do you guys use it anyways?!? If you get a new sd-card, check the guide in my sig.
I think you don't need an sd-card to flash a RUU by the exe method. Get the Official 2.3 RUU by these means:
http://forum.xda-developers.com/showthread.php?t=1772499
Extract the "RUU_HTC Desire Android 2.3 Upgrade (Gingerbread).exe" from within the "HTC Desire Android 2.3 Upgrade.zip:" then connect your phone to your PC in fastboot, and run the exe.
You will probably need HTC Sync installed, and fastboot drivers.
Click to expand...
Click to collapse
Thank you so much! Got the phone to boot using your method but now it says insert simcard =/ is this because I used the wrong rom or something?
Thanks!
I don't know. The RUU is fine. Maybe there's dust in the sim slot.
Or maybe, if it's locked, there's somehow a sim lock problem. Try unlocking it with the sim unlocking utility.
abaaaabbbb63 said:
I don't know. The RUU is fine. Maybe there's dust in the sim slot.
Or maybe, if it's locked, there's somehow a sim lock problem. Try unlocking it with the sim unlocking utility.
Click to expand...
Click to collapse
I can still acess fastboot actually and my phone recognises the phone when im in fastboot, but as soon as the phone boots the pc stops recognising it and cant find drivers for it anymore
Sorry for being a pain.
Edit: Unplugged my phone from the pc and plugged it in again and I got "Qualcomm CDMA Technologies MSM X No driver found"