Develop Bugs

[Q] SLCD desire cant mount SD on recovery

Hello people,
some things about me: i aint no expert,i am just the "follow the guide step by step" type of guy.
here goes with my problem,
I flashed oxygen v2.0 and my phone after a manual reboot crashed, i tried to boot but it stuck in the oxygen boot logo 4-5 times.
i opened the recovery (clockwork mod-alpharev 2.5.1.8) and wiped everything out (system-data-dalvik cache-ext partition)also formated the whole sd to fat32.
then when i tried to reflash oxygen 1.0.4 my recovery says that it cant mount sd card.the actuall message i get is " E:cant mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)"
i have S-OFF and rooted of course,phone is also with oxygen HBOOT.
i tried with 2 diferent cards and with both of them i get the same message.
also both of them are working fine,tested on a laptop card reader.
is it a device HW problem or something that has to do with the wipes i mentioned i did before?
what can i do to bring it back to life??

What happens if you connect the usb? Might be a usb brick.

Hi,
when i connect it via usb i can see it in "my device manager" on my pc listed as "android USB devices - My HTC" (fastboot)
in boot loader i can see it listed as "Android phone - Android Bootloader interface"
when im in cwm-alpharev recovery i can see it as "other devices - Qualcomm CDMA Technologies MSM"
the problem is that i cant mount my sd in recovery to do a NAND restore
the only thing i can do right now is go to fastboot bootloader and cwm-alpharev recovery
any ideas?

Yes, follow the link I gave you.
Skip step one since your still rooted.

ok thanks but i am gonna need some more help,
in step 2 it sais to boot into fastboot and enter a command
enter it where?

Terminal or command prompt, make suer you have the sdk tools installed and can use fastboot. If you don't know what it is or how to get it working start here.

I LOVE YOU so much right now,
all i did is the 'fastboot oem enableqxdm 0' to restore SD functionality and then a nand restore.
my desire owns you his life,
thanks alot.

need to flash but phone not detecting SD card

Hi,
I needed to flash a ROM onto my phone (prev using leedroid), however as I was going about this process (after I had backed everything up using clockworkmod recovery, and begun wiping), the phone stopped detecting my SD card
this card had been working fine for well over a year before. now error in recovery is something like E: unable to mount xxxx
it is detected using SD card reader on computer, and I have tried re-partitioning it to no avail
now the phone can boot into recovery and also the rom, but the SD card isnt detected in either, and neither now is the SIM card.
normally I would search extensively for a solution myself before posting, but I have done as much as I can, in my current situation I have no WIFI, only an internet dongle with very slow connection.
currently I assume that there is a problem with the radio but I have not had experience flashing this without using SD card in recovery
also, due to the risks involved with flashing radio, I would prefer to try to flash a new rom first, but again I have no experience flashing a new rom without SD card in recovery.
I have adb installed on my computer but not much experience using it.
Sorry for all this, but I am not the kind of guy who flashes roms regularly, the last time I did it was a while ago, and cant really remember how I rooted in the first place (I think I used unrevoked) - therefore uncertain of S-off status - although not sure what the significance of this is
please help i dont know what to do
thanks

This is what you need to do (instructions I wrote for myself in case I ever broke it again) :-
To gain access to SD card:
Put phone into fastboot mode (back button + power)
In CMD, go to dir C:\Android\android-sdk\Tools
Type: path C:\Android\android-sdk\Platform-tools)
Input "fastboot oem enableqxdm 0"
You'll need the Android SDK and once installed (along with the updated USB drivers that are available in the updates it finds) I discovered that 'Fastboot' was in a different directory to ADB so attempting to run Fastboot failed as it couldn't find ADB. My cure was to create a path to the ADB directory (as listed above). Be sure to change the path and directories to wherever you install them.
Alternatively (and far easier) search for 'Android Flasher' which is available on these forums. This has fastboot and adb installed in the same directory and is a much, much smaller download and run the above command from a CMD prompt from the directory that fastboot and adb reside in wherever you install Android Flasher to. I've never tried it this way but no reason why it shouldn't work and far easier than getting the whole SDK thing!

Yep confirmed, Android Flasher will do it. A quick search should find the program, it's a very small download compared to downloading the Android-SDK (and the Java runtime module it requires). Simply change directory in CMD to c:\your android flasher dir\data directory and run that command from there with the phone plugged in and running fastboot, fixed.
Here you go :- http://forum.xda-developers.com/showthread.php?t=794638&highlight=android+flasher
Ignore the S-Off bit, that's to do with the functions of the flasher itself, we're not actually using that.

thanks so much guys, that sorted the problem right out (used AndroidFlasher)
after reflashing the ROM, the problems with the SIM went away, so no need to flash new radio!

Guys same problem here
I backed up, I changed my sd card to an 32gb, restored but then i had the "Can’t mount /dev/block/mmcblk0p1" problem
I solved the problem with your solution (fastboot oem enableqxdm 0) then full wipe then reinstall rom
But now windows can't see my device. On my phone there is no popup menu to ask me what do i want to do when i connect the usb plug
Also, in recovery, i choose mount USB storage but windows dont see my ds card (4gb or 32gb cards)
What is the problem?
ps
when i connect to windows, device driver installation says: device driver software was not successfully installed.
It also listes "Qualcomm CDMA Technologies MSM No driver found" 3 times

Check if it's working with another sd card.
TouchPaled from Oxygen with Transparent XDA App

iceman1979 said:
Guys same problem here
I backed up, I changed my sd card to an 32gb, restored but then i had the "Can’t mount /dev/block/mmcblk0p1" problem
I solved the problem with your solution (fastboot oem enableqxdm 0) then full wipe then reinstall rom
But now windows can't see my device. On my phone there is no popup menu to ask me what do i want to do when i connect the usb plug
Also, in recovery, i choose mount USB storage but windows dont see my ds card (4gb or 32gb cards)
What is the problem?
ps
when i connect to windows, device driver installation says: device driver software was not successfully installed.
It also listes "Qualcomm CDMA Technologies MSM No driver found" 3 times
Click to expand...
Click to collapse
I'm afraid you have what is known as a USB brick, the fact that it asks for the Qualcomm drivers confirms it. Do a search on the forum, there is a fix for it.
Ah here it is :- http://forum.xda-developers.com/showthread.php?t=691639

Life-Saver.
Thanks

I've given you a 'thanks' also for replying to mine. It's a bad road to go down with the USB brick but it's something that everyone playing with rom's should experience as it educates you so much when things go wrong!
Glad you sorted it m8.

Parva4 said:
This is what you need to do (instructions I wrote for myself in case I ever broke it again) :-
To gain access to SD card:
Put phone into fastboot mode (back button + power)
In CMD, go to dir C:\Android\android-sdk\Tools
Type: path C:\Android\android-sdk\Platform-tools)
Input "fastboot oem enableqxdm 0"
You'll need the Android SDK and once installed (along with the updated USB drivers that are available in the updates it finds) I discovered that 'Fastboot' was in a different directory to ADB so attempting to run Fastboot failed as it couldn't find ADB. My cure was to create a path to the ADB directory (as listed above). Be sure to change the path and directories to wherever you install them.
Alternatively (and far easier) search for 'Android Flasher' which is available on these forums. This has fastboot and adb installed in the same directory and is a much, much smaller download and run the above command from a CMD prompt from the directory that fastboot and adb reside in wherever you install Android Flasher to. I've never tried it this way but no reason why it shouldn't work and far easier than getting the whole SDK thing!
Click to expand...
Click to collapse
you "saved my life" thank you so much

hi,just got a dhd s-on.but its not detecting the s card,tried the above method but i just get waiting for device ?... can get into fastboot etc,but cant get rid of the usb brick.looks like the dhd is stopping on stock sense 3.0

markb63 said:
hi,just got a dhd s-on.but its not detecting the s card,tried the above method but i just get waiting for device ?... can get into fastboot etc,but cant get rid of the usb brick.looks like the dhd is stopping on stock sense 3.0
Click to expand...
Click to collapse
You have a Desire HD. So please ask in the forum for Desire HD and not in the one for the Desire.

MatDrOiD said:
You have a Desire HD. So please ask in the forum for Desire HD and not in the one for the Desire.
Click to expand...
Click to collapse
yep,i have a desire bravo as well,was looking to sort the dhd out,could not find anything on dhd threads... thanks for your help ..

[Q] NOOB bricked acer a100 help!

I tried using the simple root and clockwork mod method and now my a100 keeps cycling thru bootloaderversion 0.03.06-ics-ics (unlock mode) with green acer logo. If I reboot holding power+down sd update command recovery
update_package=sd card update.zip
booting recovery kernal image
then it starts cycling again.
Please can someone help!

same
Same thing here (or at least very similar). Hoping there's a simple solution like the "Odin back to stock" I can do on my SGS phone.

are you sure that the bootloader say "unlock mode"?
If so, then try this.
try this
Install the USB drivers on your PC if you haven't done it already. ( http://global-download.acer.com/GDF...A TAB&Step3=A100&OS=a08&LC=en&BC=Acer&SC=PA_6 )
install android SDK. ( http://developer.android.com/sdk/index.html )
copy the update.zip file to your SD card root.
download TWRP recovery ( http://forum.xda-developers.com/showthread.php?t=1608152 ) and place it in the platform-tools dir where the SDK was installed ( ex. C:\Program Files\Android\android-sdk\platform-tools )
Once all that is done follow these steps
1) boot the tablet to fastboot mode
2) run command prompt on PC (cmd.exe)
3) cd to the platorm-tools dir
4) type the following lines one at a time.
adb.exe
fastboot erase recovery
fastboot flash recovery NAMEOFRECOVERY.img (ex. recovery-A100ICS-TWRP.img)
5) hold the vol down button on the tablet
6) type fastboot reboot.
The tablet should now reboot to the recovery program. Goto settings and mount the external SD card, then flash the update.zip by going to install.
Hope this helps

[email protected] said:
I tried using the simple root and clockwork mod method and now my a100 keeps cycling thru bootloaderversion 0.03.06-ics-ics (unlock mode) with green acer logo. If I reboot holding power+down sd update command recovery
update_package=sd card update.zip
booting recovery kernal image
then it starts cycling again.
Please can someone help!
Click to expand...
Click to collapse
Did you rename/delete /etc/install-recovery.sh ?
I think you're not. Try to make hard reset, then boot normaly rename/delete this file and after that flash recovery again, it should work.
All it's explained here.

Thank you
TheBlackshinobi said:
are you sure that the bootloader say "unlock mode"?
If so, then try this.
try this
Install the USB drivers on your PC if you haven't done it already. ( http://global-download.acer.com/GDF...A TAB&Step3=A100&OS=a08&LC=en&BC=Acer&SC=PA_6 )
install android SDK. ( http://developer.android.com/sdk/index.html )
copy the update.zip file to your SD card root.
download TWRP recovery ( http://forum.xda-developers.com/showthread.php?t=1608152 ) and place it in the platform-tools dir where the SDK was installed ( ex. C:\Program Files\Android\android-sdk\platform-tools )
Once all that is done follow these steps
1) boot the tablet to fastboot mode
2) run command prompt on PC (cmd.exe)
3) cd to the platorm-tools dir
4) type the following lines one at a time.
adb.exe
fastboot erase recovery
fastboot flash recovery NAMEOFRECOVERY.img (ex. recovery-A100ICS-TWRP.img)
5) hold the vol down button on the tablet
6) type fastboot reboot.
The tablet should now reboot to the recovery program. Goto settings and mount the external SD card, then flash the update.zip by going to install.
Hope this helps
Click to expand...
Click to collapse
I'm going to try this, one question though. My computer does not read the tablet anymore even though I have the drivers installed will it still work? Yes I'm a serious noob, but I'm trying...and thank you for your help it is much appreciated.

cpu doesnt read tablet anymore
[email protected] said:
I'm going to try this, one question though. My computer does not read the tablet anymore even though I have the drivers installed will it still work? Yes I'm a serious noob, but I'm trying...and thank you for your help it is much appreciated.
Click to expand...
Click to collapse
Okay, I downloaded everything but my computer doesnt recognize my a100 anymore, only if I put the tablet into fastboot then it see's it. My tablet just keeps on rebooting itself repeatedly unless I go into fastboot. Please tell me I dont have a paperweight.

were getting close
Blackshinobi or anyone that can help,
I'm getting close. I make it to: "fast boot flash recovey" cmd prompt
I get two different errors depending hoew I type the cmd prompt:
1. "fastboot flash recovery recovery-A100ICS-TWRP.img"
error (can not load recovery-A100ICS-TWRP.img)
2. "fastboot flash recovery-A100ICS-TWRP.img"
error ( cannort determine image file name for 'recovery-A100ICS-TWRP.img)
I was a little confuse on proper cmd line prompt, but I'm thinking #2 is the correct way.
Thanks so much for your help!

pfisher101 said:
Blackshinobi or anyone that can help,
I'm getting close. I make it to: "fast boot flash recovey" cmd prompt
I get two different errors depending hoew I type the cmd prompt:
1. "fastboot flash recovery recovery-A100ICS-TWRP.img"
error (can not load recovery-A100ICS-TWRP.img)
2. "fastboot flash recovery-A100ICS-TWRP.img"
error ( cannort determine image file name for 'recovery-A100ICS-TWRP.img)
I was a little confuse on proper cmd line prompt, but I'm thinking #2 is the correct way.
Thanks so much for your help!
Click to expand...
Click to collapse
That's awesome news!!!
Number 1 is the correct command.
Just making sure you are actually in fastboot (bootloader) mode. On the command-promt type "fastboot devices", if you see the result below, then you're good
? fastboot (yes that's a question mark)
Now be sure you are in the directory with the recovery image and issue number 1 command (fastboot flash recovery whatever-recovery.img). If you get some errors, be sure to check the MD5 hash of the recovery image cuz it could be a corrupted download.
Of course, you can't flash the custom recovery if you still have a locked bootloader.

you guys rock..even closer
Thank-you everyone ..I am soooo close. I did get the recovery image to load (I accidently had it in android-sdk and not platform-tools...oooops my bad). Now I can reboot to recovery and install the update.zip off my external sd card. However after I install the update.zip and reboot, I still get stuck on the acer screen (bootloader version 0.03.06-ICS (Unlock Mode) at top with acer logo in green at bottom.
Which update.zip am I suppose to be using? Currently I am trying to install one of the stock ROMS from the developer section of this forum. Am I suppose to be using a specific one?
Thanks again, I know I'm close. My tablet has been brick'd for weeks and I'm dedicated to getting it back now that I have time.

pfisher101 said:
Thank-you everyone ..I am soooo close. I did get the recovery image to load (I accidently had it in android-sdk and not platform-tools...oooops my bad). Now I can reboot to recovery and install the update.zip off my external sd card. However after I install the update.zip and reboot, I still get stuck on the acer screen (bootloader version 0.03.06-ICS (Unlock Mode) at top with acer logo in green at bottom.
Which update.zip am I suppose to be using? Currently I am trying to install one of the stock ROMS from the developer section of this forum. Am I suppose to be using a specific one?
Thanks again, I know I'm close. My tablet has been brick'd for weeks and I'm dedicated to getting it back now that I have time.
Click to expand...
Click to collapse
Congrats resurrecting your tab! Gotta be a great relief!
How about Flexreaper ROM? It will require full wipe before flashing: in recovery wipe/factory reset, wipe system, wipe cache, wipe dalvik cache, flash Flexreaper ROM zip file. This is basic guide, follow detailed instructions on this ROM thread (link is in my sig).
Sent from my A100 using xda premium

not quite recovered yet. I still get the hang on Acer screen. anyone know why? I will try flexreaper

I'm BACK
Thanks to all. I'm back up. flexreaper did work.. I hope the guy who actually started this thread is as lucky.

Not so lucky
I'm still stuck my pc doesnt read my acer a100 still....any helps out there?

[email protected] said:
I'm still stuck my pc doesnt read my acer a100 still....any helps out there?
Click to expand...
Click to collapse
Power down the unit. Set screen lock in the up position. Hold volume down and power. When powered on keep holding the vol down button. Then toggle the screen lock to down.
That should do a factory reset.
Then put a stock rom in the root of SD Card. Volume up then power until let the tablet recover.
This worked for me.

did u install the drivers from an earlier post? Also when you power up you your tablet you need to boot into fastboot mode? You're certain you have done both of these things?

I am unable to connect to, my pc doesnt recognize my acer anymore...unless by sd card you mean external card? Thank you for trying to help. I'm a serious noob but trying hard.

i'm in a similar situation. i accidentally deleted the build.prop file and rebooted. now it only displays a black screen after the acer logo drops out. my boot loader is locked but i cant install the mtp usb drivers to fix anything. think i have a paperweight now.

mechpilot_z said:
i'm in a similar situation. i accidentally deleted the build.prop file and rebooted. now it only displays a black screen after the acer logo drops out. my boot loader is locked but i cant install the mtp usb drivers to fix anything. think i have a paperweight now.
Click to expand...
Click to collapse
that's easily fixed, install this through stock recovery, http://forum.xda-developers.com/showthread.php?t=1611696

eww245 said:
that's easily fixed, install this through stock recovery, http://forum.xda-developers.com/showthread.php?t=1611696
Click to expand...
Click to collapse
tried. i had no alternative recovery on it. i could not get the sd card mounted to push the zip to it. both adb and fast boot wont see my tablet. every attempt at unlocking fast boot wouldn't work. I tried to check in device manager to see if it was connected, the driver was working but it had an error message "Device can not start (Code 10)"

My pc only sees my tablet when I boot it into fastboot mode and sees it as an adb interface...Is there anything I can do from there?

[Q] XPERIA Stuck in boot loop? Bricked? :/

Hi XDA,
So I got an Xperia PLAY just the other day. Despite its age, since its capable of running a PS emulator, given the built in controller, I think its rad.
Anyhow, went to install CM10 on it and I screwed up big time.
I actually copied the update.zip file over in USB storage mode instead of adb pushing it.
Phone is now stuck in boot loop.
Here's where I'm at:
-I CAN still access both bootloader and CWRM (I used bootloader to copy the boot.img across)
-I CAN'T get the phone to communicated with adb (no adb device shows up in device manager or "adb devices", the only thing I can see is "MTP Device" which I figure is the problem)
-I CAN'T switch it out of MTP mode (if this is even the issue) as CWRM doesn't offer that option
I have tried:
-Both with and without PC companion to get it to communicate with ADB
-The universal ADB driver.
-I have tried the PC companion "phone repair" but it refuses to help me as it realises I have modified the KERNAL.
Question is:
- Is there anything I can do to copy an update.zip ROM across. A way to make ADB work or any solution other than ADB?
- Am I right in assuming ADB is not working because its set to MTP mode?
Much thanks in advance!

Did you flashed kernel (boot.img file that you extract from zip file)?
What was your previous kernel/rom?

TehKame said:
Hi XDA,
So I got an Xperia PLAY just the other day. Despite its age, since its capable of running a PS emulator, given the built in controller, I think its rad.
Anyhow, went to install CM10 on it and I screwed up big time.
I actually copied the update.zip file over in USB storage mode instead of adb pushing it.
Phone is now stuck in boot loop.
Here's where I'm at:
-I CAN still access both bootloader and CWRM (I used bootloader to copy the boot.img across)
-I CAN'T get the phone to communicated with adb (no adb device shows up in device manager or "adb devices", the only thing I can see is "MTP Device" which I figure is the problem)
-I CAN'T switch it out of MTP mode (if this is even the issue) as CWRM doesn't offer that option
I have tried:
-Both with and without PC companion to get it to communicate with ADB
-The universal ADB driver.
-I have tried the PC companion "phone repair" but it refuses to help me as it realises I have modified the KERNAL.
Question is:
- Is there anything I can do to copy an update.zip ROM across. A way to make ADB work or any solution other than ADB?
- Am I right in assuming ADB is not working because its set to MTP mode?
Much thanks in advance!
Click to expand...
Click to collapse
Go into cwm. Go to mounts and storage. Connect phone to pc and mount the sd and you should be able to connect to adb while in cwm. Copy a rom over and flash or if it was the biktloader and kernel and all that do as per usual
Sent from my R800x using XDA Free mobile app

TehKame said:
Hi XDA,
Flash ftf in flashtool .. go back to rooted Stock !! and carry on from their onwards.
Click to expand...
Click to collapse

rooted and unlocked m9 in boot loop

So I did the factory reset option in TWRP, rebooted the device before installing a new rom and now i'm stuck in a boot loop everytime I try to power on. I was running ViperM9 and was going to switch back rooted stock but now all my backups and roms are wiped from phone and SD card.
When I plug my phone into the computer it fails to install the proper drives every time. I've tried downloading the correct drives independently on the computer and it's still a no go. Then I tried connecting my microsd xc (64gb) to my computer via the SD adapter and the USB adapter it came with. Also doesn't work. The computer recognizes it as a "mass storage device" but won't let me move any files to it.
My brain is fried for the night and hoping I can find some help on here. I can still boot my phone into recovery mode so I'm hoping I can still salvage the situation. I'd like to get my phone working again without losing my root access because I don't want to have to send off to a java key angel again. Lol. I appreciate any and all insights on the matter.

paleost0ner said:
So I did the factory reset option in TWRP, rebooted the device before installing a new rom and now i'm stuck in a boot loop everytime I try to power on. I was running ViperM9 and was going to switch back rooted stock but now all my backups and roms are wiped from phone and SD card.
When I plug my phone into the computer it fails to install the proper drives every time. I've tried downloading the correct drives independently on the computer and it's still a no go. Then I tried connecting my microsd xc (64gb) to my computer via the SD adapter and the USB adapter it came with. Also doesn't work. The computer recognizes it as a "mass storage device" but won't let me move any files to it.
My brain is fried for the night and hoping I can find some help on here. I can still boot my phone into recovery mode so I'm hoping I can still salvage the situation. I'd like to get my phone working again without losing my root access because I don't want to have to send off to a java key angel again. Lol. I appreciate any and all insights on the matter.
Click to expand...
Click to collapse
Sounds like your sdcard failed. You said you can get into recovery, so try getting ahold of another sdcard with Viper ROM zip file on it and flash it.

Boot to the bootloader and flash an RUU using fastboot. An sdcard is not needed, only working adb/fastboot drivers. S-Off status will be unaffected. Root can be regained by installing superSU from recovery.
Get RUU from this thread by cmlusco and twrp from here
Reboot the phone into bootloader mode
Open a command prompt
Fastboot OEM rebootRUU (This assumes you have working drivers in windows. If you're having trouble, use the google drivers and just force windows to use it. In bootloader select the bootloader interface driver, for adb, select the adb interface driver. These are the only two drivers I use but they must be selected manually, windows will not automatically install them for the M9. You might have to do this a couple times.)
fastboot flash zip "path and name of RUU.zip" (This will take probably 10 - 20 minutes to complete but will give status updates.)
Get coffee
fastboot reboot-bootloader
Enter stock recovery
Factory reset
Reboot to bootloader
fastboot flash recovery "path and name of twrp image"
Boot to system
Download superSU
Reboot to recovery
Install superSU
Reboot to system
You should now have a stock rooted phone

l7777 said:
Boot to the bootloader and flash an RUU using fastboot. An sdcard is not needed, only working adb/fastboot drivers. S-Off status will be unaffected. Root can be regained by installing superSU from recovery.
Get RUU from this thread by cmlusco and twrp from here
Reboot the phone into bootloader mode
Open a command prompt
Fastboot OEM rebootRUU (This assumes you have working drivers in windows. If you're having trouble, use the google drivers and just force windows to use it. In bootloader select the bootloader interface driver, for adb, select the adb interface driver. These are the only two drivers I use but they must be selected manually, windows will not automatically install them for the M9. You might have to do this a couple times.)
fastboot flash zip "path and name of RUU.zip" (This will take probably 10 - 20 minutes to complete but will give status updates.)
Get coffee
fastboot reboot-bootloader
Enter stock recovery
Factory reset
Reboot to bootloader
fastboot flash recovery "path and name of twrp image"
Boot to system
Download superSU
Reboot to recovery
Install superSU
Reboot to system
You should now have a stock rooted phone
Click to expand...
Click to collapse
Is this basically the method to recover from a bootloop/ bricked phone? Gonna Sunshine my phone this evening and start flashing. I know I'll eventually brick the thing. Wanna know my recover options when the inevitable happens.
Sent from my HTC6535LVW using XDA-Developers mobile app

mikelikesbikes said:
Is this basically the method to recover from a bootloop/ bricked phone? Gonna Sunshine my phone this evening and start flashing. I know I'll eventually brick the thing. Wanna know my recover options when the inevitable happens.
Click to expand...
Click to collapse
There are many ways. This one uses a computer to send the updates. Having the proper file on the sdcard is another way and bypasses the need for working adb and fastboot drivers which seem to be a pain point for a lot of users.

l7777 said:
There are many ways. This one uses a computer to send the updates. Having the proper file on the sdcard is another way and bypasses the need for working adb and fastboot drivers which seem to be a pain point for a lot of users.
Click to expand...
Click to collapse
I do have working adb/HTC_fastboot on my computer, but having a signed RUU on my external SD card is all I need?
Sent from my HTC6535LVW using XDA-Developers mobile app
---------- Post added at 12:05 PM ---------- Previous post was at 11:48 AM ----------
mikelikesbikes said:
I do have working adb/HTC_fastboot on my computer, but having a signed RUU on my external SD card is all I need? Looking at the instructions I see the SD card must be formatted to fat32. I have no idea if mine is, but I have extras. I can format one of them to fat32, keep that file on it, and in case I ever need it I can pop it in the phone and flash it?
Sent from my HTC6535LVW using XDA-Developers mobile app
Click to expand...
Click to collapse
Sent from my HTC6535LVW using XDA-Developers mobile app

mikelikesbikes said:
I do have working adb/HTC_fastboot on my computer, but having a signed RUU on my external SD card is all I need?
Click to expand...
Click to collapse
Yes. It must have a special name and be in the root of the sdcard. I don't remember exactly what the name is for the M9 but it is posted in the RUU threads.