I accidentally flashed a rom for a different phone and managed to brick my m9. The phone now doesn't turn on, go to bootloader, or any other place no matter the button combination i use. Nothing lights up when i connect it to charge or USB. After a couple days of trolling the web, i came to the conclusion that the phone is stuck in 'Qualcomm Emergency Download Mode'. One of the solutions i found required a 'mmcblk0.img' backup created from another device. The problem is that i dont have another m9, and no one i know has one either. So if anyone would be kind enough to post one, I'd appreciate it.
I found this method to get the mmcblk0.img from a working phone, but can't really test it myself to check whether it works:
1. Root the phone,
2. Install BusyBox
HTC devices doesn't accept regular "busybox",
so, we have to install it via "BusyBox on Rails",
3. Put an SD Card in the phone (at least 16GB), then enable "USB Debugging",
4. Connect phone to PC and run this commands from PC one by one,
adb shell
su
dd if=/dev/block/mmcblk0 of=/sdcard2/mmcblk0.img
5. Now reading process started and you have to wait for it to finish,
6. After process finish, you will have the "mmcblk0.img" file in your SD Card
Related
Hello,
I have tried attempted to root and flash a new ROM on my phone and now I seem to have lost SD and USB support. it does not recognize any of the SD cards i put it (doesn't realize theres an SD card inside) and does not recognize any USB plugged in.
I have HBOOT .80 and i THINK i got the root correct (lotsa problems along the way so i'm not sure), but i was able to flash a ROM (NexTSENSE) so i think it worked. now, i saw a thread about fixing USB support but that required SD support. and reading that made me feel like i was royally screwed. in any case, any suggestions? I think USB support is still kinda there since I can get it to recognize it in the boot menu. but when i try to do it in recovery and use the flash rom .bat, it says device not found.
it would seem that the main concern right now is that i can't get it to see my SD cards. any of them, even after reformats and whatnot.
i can't connect to HTC Sync or anything of the of the sort. usually when i charge the phone, you get the charging notification but i don't even get that now. sounds like a driver problem but i can't see what is wrong. my computer doesn't even recognize the phone as a device every now and then
Hope i provided sufficient information. New to android scene so don't be too hard on me please =O but yea, any suggestions are welcome. thanks in advance
edit: usb support... ever so slightly back. aka, it charges now. probably was drivers on my lappy getting funny after moving between bootloader and recovery and all that fun stuff
You have the usb brick issue. Check out the thread on that. Also once you are up and running again, root using unrevoked or the fake flash method. All information is available in the dev forum.
ok, i've done some reading and this is what i've found so far. my phone is stuck in USB debug hence no USB support and somewhere along the way, SD support was disabled. from what i see, the fix is to
first:
reload the step1 of root to get back to 1.15 and basic root access.
second:
from there, i can re-enable SD support using the command:
fastboot oem enableqxdm 0
third:
apply USB-Brick fix found in post 1 of thread
and then i should be able to reload ROMs as usual. is this correct?
and where exactly do i put in the command to re-enable SD support? this is what has be confused right now. along with the commands for the USB fix
i am using the tinycore method so i just have the step1.sh. and then in the same console, can i enter that command? should i do it after a reboot? or load back into bootloader to do it. (bootloader or fastloader)
OOOOK. sorry about the continuous posts. putting new info up so it isn't exactly a bump right?
in any case, i used the androidSDK tools and ran the fastboot from there and i think i re-enabled my SD correctly. i was then able to run the USB-brick fix found on modaco forums. all done and done. nowww, since i just went through half the root process (step1.sh with tinycore), do i need to finish it? or since i had already rooted before, is it all done now?
I'm not 100% sure about that as I haven't had to fix the usb brick for ages now!
Download and install titanium backup from the market. If it works fine, then you are rooted. If not, root woth unrEVOked or fakeflash.
All the older root methods that require usb during the root process leave you open to the usb brick again.
Hi fatpandas..
Is your phone ok now? Actually my phone also have a problem like yours last week..until now,i can't fix it..if now your phone ok,can u share with me..thnks in advance..
@csyrix
sorry to hear about your situation. after just being there, i can tell how horrible it is. good news is, if you really have the same problem, then it is definitely fixable.
now, i don't know what method you used to flash yours the first time but from what i've seen, they're mostly the same. what you wanna do first is do that step1 thing where you have a temporary ROM installed. (1.15?) same process as usual.
then you'll need to run 'fastboot oem enableqxdm 0' with phone plugged in while in FASTBOOT (back button + power button thing)
in case you don't know where to put that in, you wanna run that in your command prompt (computer) while operating in the tools folder of the android SDK. (thank god for my limited computer knowledge cuz all the instructions i found just say, "run this command" and like hell if most know how/where)
in any case, the end result will be you having completed step1 and having re-enabled SD support. then turn off phone.
then get the fix from this thread
move that to your SD card (micro SD adapter) and turn back on your phone into bootloader. go to the recovery menu and hold volume up + power to bring up menu and hit the apply: update.zip.
then all should be well. i then moved on to step2 to make sure i had rooted properly. may not be necessary but i remember reading that rooting a rooted device isn't a problem so i just felt the need to do it to be safe.
that should be it. the link provided actually has all the instructions anyways (i hope mine are a bit more clear), but if not, that link should be able to fill in the holes. g'luck sir
Hi everyone.
Please bear with me this is my first Android and first attempt at rooting.
I recently used unrEVOked to root my HTC Incredible. I ran into the SLCD issue discussed here elsewhere on these forums, but I've encountered another (related?) issue that prevents me from implementing the SLCD workaround.
I've downloaded the revised image, but when I go to transfer the image to the device I am unable to mount the phone as a usb drive. When I plug the phone into the computer I do not receive the usb action menu. The battery does charge however. I've tried mounting the phone manually from the command line, but no luck. This behavior continues after rebooting the phone.
Is there a known solution to this problem?
Edit: More information.
Google seems to think yanking the battery is the solution to the device's usb issues but I haven't had any luck with that technique.
adb devices and adb shell hang when I try to run them (Yes, USB debugging is on).
I've attempted to download Adrynalyne's recovery directly onto the phone, but hboot does not recognize it as a valid image. Not a big deal, the phone still works just fine, and I don't mind waiting for a version of clockwork recovery that works with SLCD.
But, I would like to interact with the phone through adb.
Thoughts? Flames? Death-threats?
I tried to flash CM7 RC2 onto my phone last night. I usually do this manually, but last night I did it through Rom Manager which I think was probably my first mistake.
Anyway, the package flashed fine but after a reboot my SIM and SD card were no longer recognised. So I went into recovery (Amonra) and wiped ready to flash the update manually only to find my SD card wasn't recognised: E:Can't mount /dev/block/mmcblk01p (No such file or directory). So, left with a phone with no ROM.
I can still get into recovery and bootloader but that's it. I've seen a few posts on here with regards to USB bricks, but my phone is no longer recognised by adb. However, I haven't accessed the phone via adb for some time now, so not sure of the reason I can't connect is my PC setup or the phone. I've got the HTC Bootloader device appearing when I plug it in via USB though.
Can anyone advise on anything I can do to sort this?
Thanks
Might be a driver issue when your in recovery. Re-install the drivers for the device using Device Manager and point windows to the driver directory within the SDK folder.
Hi chaps, I've done a lot of searching but unlike many who managed to fix theirs I fear that my Desire is dead. Did a nandroid backup and during reboot for one reason or another (likely the cheap Ebay battery) the phone rebooted a couple of times and I suspect it's corrupted the ext4 that was holding data. Phone was running Starburst 1.5 Classic with data2sd. It's also s-off.
Ok, I've read threads where people have plugged it in and using adb have managed to issue a command to have the phone re-enable the sd card. The issue I have is that adb doesn't even recognise that the phone is actually connected. I've tried this on both my PC and laptop with no joy.
I can still get into recovery and also fastboot and there must be some life as the phone recognises the USB connection when plugged into the PC but 'adb devices' gives me nothing so I therefore can't issue commands.
I have also tried putting the original firmware back on via PB99IMG.zip but since the phone's not reading the card at all that too is a dead end. It still boots to recovery and I get the 'Why so serious' logo if I try starting the phone up but I just can't get any further with it.
Anyone any ideas?
You can wipe and flash partitions and files from fastboot
http://android-dls.com/wiki/index.php?title=Fastboot
Once you get it working, restore your nandroid to see if it's working and not corrupted by the reboot. If it's not working, you can rebuild in fastboot!
Ok, I'm doing some more reading and learning, driving me nuts this thing. Cheers.
Edit: That won't work as I cannot gain access to the phone from the PC. adb devices show nothing connected even when it clearly is.
Edit 2: C:\Android\android-sdk\platform-tools>fastboot
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Perhaps I'm missing something???
Sorted I think, was me being a n00b. Will post back if I manage to get it all running again.
Did you get fastboot to work and recognise your device?
Take a look at the thread I posted earlier, the command to check it is
Code:
fastboot devices
HELP!!! yes , its that bad and frustrating for me.
What happened?
I installed the latest CM7#218, and the phone never was able to restart. It was giving the '3-5 vibrates' symptom. After managing to get into recovery mode, i couldnt see anything from SD card. I later erased and reformatted the sd card but to no use.
In detail:
1. Installed CM7#218.
2. phone restart gives 3-5 vibrate symptom, cant even get into recovery mode.
3. tried factory reset , sd card reformat,repair from windows but doesnt help.
4. only when i unplug the device, power on or when i click on recovery mode, and while on the HTC splash screen, if I connect charger, ONLY then i can get into recovery mode or start the base CM7 OS.
5. in recovery mode i cannot see card , tried all possible mounts/unmounts. thus unable to restore any backups
6 when the base OS boots, (using point#4 above), i still cannot see sd card, nor able to format from phone. in file manager i can see my internal storage. But the phone does not give me any usb mount option , so cannot even view the internal memory from windows.
7. referred to the following thread and many other options etc, but doesnt work.
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
the adb shell does not detect my device, tried using 'PDANET' ' ends with 'cannot handshake with device'. tried installing droidexplorer, cannot see my device in the refresh list.
8. Thus as it stands now, i cannot use my internal as well external memory, the web downloads wont go, saying cannot see any memory, same for camera, it cannot see any memory available to it.
9. have already tried N number of restarts, connect disconnect and battery pulls.
10. tried even running the unrevoked, but it cannot connect to device.
11. tried installing all possible drivers as well.
12. its surely not bricked cuz i can use the base OS, and get into recovery through #4 tactics.
HELP!!
Have you seen this?
http://pvillecomp.com/?page_id=33
Firstly my sdb shell is nto detecting the device..."error: device not found"
my device manager show "ADB INTERFACE -> HTC BOOTLOADER" and there are no warning icons aroind any other devices, so driver seems to be fine.
You need to install the adb drivers on your pc. It should say adb composite device. I believe you get them from the android sdk.
ok now that i was playing around from recovery..i ended up formatting everything...even boot....so now i no longer get the base OS...the moment i power on my device it automatically goes into hboot...
So, as per the link you shared. it says my phone need to be in fastboot mode...and in fastboot mode the device manager should read 'android bootloader interface'?
I did go through most of the search items initially...stumbling from one issue to another...finally it boils down to adb -device not found issue....its been 2 days and i've almost given up now...
any last minute help?
only the recover mode is working with no access to sd card,
it can access teh internal memory , but there is no way for me to copy any files to the internal memory...it doesn mount neither the adb is working
Have you tried reformating your sd fat32 with a pc, or tried a different sd card? Thats the only other thing i can sugest to try.
yes, that is the first thing i found in other forums and already tried that....
you think you have any suggestions to atleast access my internal memory , may be, from linux (i am not a linux guy but have a ubuntu live cd) so that use the option 'install zip from internal memory'
Im not sure im not much of a linux guy eithet, mabey someone who is will chime in.