Hello,
Long story short;
Using SP flash tool I did "Format all" in stead of " format all except bootloader".
So after a looooong long time, I got almost everything back to normal.
But now, somehow, My sim card doesn't even get detected by MIUI, but it does when I flash the standard GSI.
can someone help me out with this? I'd like for MIUI to see the sim card...
Related
Okay first off im gana start off saying sorry im a complete newb and jsut got my first WM phone the other day i got the Verizon VX6900 and i wana upgrade to WM 6.5. Ive read over cody bear's FAQ for NFSFAN's rom several times and although im kinda scared to screw it up hopefully i wont brick my fone. my first question is i know you suppose to upgrade you radio first but especially since mine is 1.60.30 no where near 3.42.50. So can someone point me to a how to do it and do i have to get a verizon one because i saw a file to upgrade for Bell's radio and im not sure if thats the same.
Also can everyone put my fears to rest that im gana destroy my fone when i reflash it. It dosnt seem that hard im just kinda nervous.
Sorry again for being newb and making a thread there is just so much information and its hard to figure it all out without someone guiding you in the right direction
First you need to unlock your phone using the cokeman unlocker.
From there, if you have the SD card that came with your phone (the 512MB one). YOu can download a radio upgrade that changes nothing but the radio on your phone. This is a good idea as verizon can be tricky.
http://forum.ppcgeeks.com/showpost.php?p=389964&postcount=8
That file has the radio flash in it.
So to install it, you first make sure your phone is unlocked. Then copy the file from inside that zip to the SD CARD (note: the sd card must be formatted FAT32). Then enter bootloader mode by pressing holding down the power and camera buttons while pressing the reset button with the stylus. Do not have a USB cable plugged in. WHen the boot loader loads up it should be a tricolor screen that says COkeman unlocker or bootloader ver 2.41 or something like that. It will say serial at the bottom and after a few seconds ask you if you want to install the rom. If it asks you to confirm do what it says to confirm. IT shoudl flash then restart. When it restarts check the red text at the bottom and see if it says 3.42.50 next to r. If so you properly flashed your radio.
From there you can install ANY upgaded rom you like.
okay thanks i dont have the 512mb sd card i only have a 2gb sd card will that work?
As long as it is a regular microSD, not microSDHC. It should say so on the card. Mine 8GB card says microSDHC on the card itself. More than likely the card is standard SD (as I think SDHC doesn't start until 4GB).
So the requirements for flashing from the card are:
I think you need to have the device unlocked
microSD Card (NOT microSDHC)
Card has to be formatted FAT32
The file must be named VOGUIMG.nbh
No USB cables plugged in.
ok so im getting a little nervous i unlocked it and then flashed the radio update and it installed and says update complete update success but its not restarting do i have to restart it. did i just brick my phone?
Hard reset it yourself.
well i managed to get it to work and installed NFSFANs 6.5 rom and it runs amazing. i installed the vzw mms cab but i still cant get my MMS to work
nickbutterz said:
well i managed to get it to work and installed NFSFANs 6.5 rom and it runs amazing. i installed the vzw mms cab but i still cant get my MMS to work
Click to expand...
Click to collapse
Read the FAQ for that ROM over on this thread HERE all your issues with MMS, GPS, ETC can be found there
Detroit Doug
Detroit_Doug said:
Read the FAQ for that ROM over on this thread HERE all your issues with MMS, GPS, ETC can be found there
Detroit Doug
Click to expand...
Click to collapse
thanks man got mms working now just gata start working on the GPS. hrm just wondering if anyone else has this problem sometimes when i accidently click the persons name in the SMS thread the fone just freezes
Sorry, I'm another noob when it comes to flashing roms as well. Once you flash from the microsd, will the new rom be compatible with a microsdhc after its upgraded? Or can I only use Microsd from here on out??
Thanks for the help.
No problem. The only time you NEED a standard microsd card is when you are flashing a file to the device. To be exact, when you are upgrading the radio as all of the ones I have seen load from the microSD card, otherwise all of the custom roms can be upgraded over USB. The reason you need a standard microSD card to flash from the SD Card is that microSDHC requires a specific driver to be loaded and at the bootloader point that driver has not been loaded. This means at the boot loader point, the port can only funciton as a microSD port. Once the OS has loaded, the driver has been loaded as well, therefore it can read both times.
hi,
i had a whole bunch of issues with my defy (self inflicted) http://forum.xda-developers.com/showthread.php?p=12349345#post12349345
anyhow, i have now managed to flash, update.zip (which happened to be for t-mobile usa) and now i cant get my, or any other formatted sdcard to work???
when i put one in it begins to mount the sd card, then instantly says "sd card is safe to remove"
i want to flash my defy with blueginger but i cant work out how to seeing as i cant access my sd card?
luckily the phone is still rooted but i cant put clockwork or anything else on as it wants to install it on my sd card, is there a way around this?
please help!!!!
Hey i had the same issues search the android development section for the solution or search for the post posted be me,,
http://forum.xda-developers.com/showthread.php?t=988592
hahahaha problem solved (after 6 days of hell)
turns out that rds lite doesnt work too well on windows 7, so i gave it a crack on the old comp (xp), and bang, rom is flashed, phone is fixed
thanks to all that gave me help along the way!!!!
Help..
I'm in the same situation as earlier described..
I've been trying to get Adlxmod F4D on to my defy, but in the process I screwed up a few things..
I'm back on track though and I've currently flashed my defy with the 3.4.3-11 .. BUT now my problem is first of all, that after I've rooted the phone using superoneclick (and also before doing this) my phone says that I've got NO SD card.. When I do the recovery reboot to wipe and restore then my touch screen doesn't work (it boots, though).. It's the same if i tryk to boot using power + vol down - here I get no response when I push in the down right corner..
This problem is not only with my 16gb sd card (which was in the phone during wipe + flash + root), but also when I try the 2gb that came with the phone.
Does anyone have a solution to my problem??
Hi everyone,
I've had a bit of a search on here, and although I can find threads about SD bricking, I can't quite find one that matches my situation.
I tried to root my phone and flash my first ROM today, I thought it'd gone ok, partitioned using GParted and flashed the GingerBurst ROM, and seemed to start up again ok. I was going to add something to my SD cards though, and found my USB connection menu didn't included the usual use as disk option and the SD card is now inaccessible from both my computer and the phone.
Under Settings->SD & Phone Storage, both Total and Available Space fields are 'Unavailable' and Mount SD Card and Erase SD Card are greyed out.
I've tried getting the bootloader up to see if I can do anything by holding down the volume down button and the power button (phone doesn't even turn on and screen remains blank), so I think my phone no longer sees that as a recognised option. I've tried back+power and up vol+power (for fastboot), and I get nothing. All my phone will do is power on if I hit the power button, so now I really have no idea of how to get the SD card back up and functioning.
I haven't tried repartitioning it because if my computer can't see it, and neither can my phone, GParted surely won't... I also don't have a card reader.
Is there anything I can do? Is there another way to get the bootloader up? Did the key combination change with gingerbread? Maybe I went wrong somewhere during my rooting... I don't know. Any help would be very much appreciated!
Thanks,
Daisy
You need to either get a new spare card, Format in FAT32 then add a 1gb EXT3 partition, or get a card reader and reformat you old card again with FAT32 first then EXT3 second- if it doesnt work, bin it
Dont worry about losing applications you can download these again from market.
Ensure your card is properly formatted if using A2SD
Wipe your phone and caches
Install your ROM from the SD card
re install applications
Enjoy
Please use the Q&A Forum for questions Thanks
Moving to Q&A
You have to press and hold first volume down (for hboot) or back (for fastboot) and then the power button. It seems as if you doing it the other way around.
Otherwise, you can do it so: When running rom, use restart option from shutdown menu. Then press and hold back button.
After you successfully booted your phone into fastboot mode, set up adb / fastboot (for a guide see my sig), connect your phone to computer, open command line on computer and type
Code:
fastboot oem enableqxdm 0
.
Now reboot into rom. Your desire should now recognize the sd card.
Hi, thanks for the info! I've tried all the instructions here: cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK#Windows
I got to 14 - but no drivers were automatically installed, and at 16 what looked like a command prompt style window popped up for a split second and disappeared - no information that I could read on it in that moment anyway, I did try again but same thing, so I continued with the steps to check, and tried it again after step 28 with the same thing happening again.
When I try to boot in fastboot mode my phone looks as though it's just starting normally - should anything be different? I don't know what fastboot is meant to be like! I also tried the piece of code you included in your message there and brought up a window that said it was waiting for the device, but made no progress...
I am correct in thinking I should be entering these prompts by going Start-> and typing 'run' in the search field, and then entering the prompt there? If not then that might explain something!
Seems to be an usb brick. On xda you find a guide how to solve it.
TouchPaled from Oxygen with Transparent XDA App
Many months ago my Desire somehow managed to brick the SD card it came with. I put it down to a manufacturing fault and bought a brand-name other; everything's been fine for months.
Last night I was playing around with the Desire's text to speech settings when my phone rebooted unexpectedly. When I turned it back on I'd lost all data ability and the ability to make calls receiving calls and sending/receiving texts was fine.
I had a quick search around here and tried various different things, ultimately rebooting the phone a couple of times, however I am now in the state where by SD card is no longer recognised in the Desire, nor in recovery mode, nor in Windows using an adapter.
Does anyone have any bright ideas as to what to do to fix this?
what rom you running? any ext partitions? Probably your card died... try it reformat under gparted live cd
Format card with this http://www.box.com/s/4yxtn33zh4h2915bzcyx
Options, Full erase if you have time go for full rewrite. Better use SD card reader.
THIS WILL WIPE ENTIRE CARD!
DO NOT UNPLUG CARD WHILE ITS WIPING!
Tried both linux and the SD card formatter - both failed. The latter even reported the card was write protected... the card doesn't even have a physical write protect switch!
I bit the bullet and decided to buy a new card this afternoon. I've just gone ahead and flashed a new cyanogen rom and flashed the latest radio - unfortunately the call issue still persists. I make an outgoing call and it doesn't even attempt to ring... just get a single beep and it hangs up!
Any ideas how to fix this?
pcdj said:
Tried both linux and the SD card formatter - both failed. The latter even reported the card was write protected... the card doesn't even have a physical write protect switch!
I bit the bullet and decided to buy a new card this afternoon. I've just gone ahead and flashed a new cyanogen rom and flashed the latest radio - unfortunately the call issue still persists. I make an outgoing call and it doesn't even attempt to ring... just get a single beep and it hangs up!
Any ideas how to fix this?
Click to expand...
Click to collapse
I've had this issue on the TELUS network in certain locations. It has to do with capacity of the network. I still have some trouble with it, single beeb, no explanation by voice or on screen mesage. Basicly the network you are on is overloaded. I imagine you miss calls durring the same time period as well. Try the same call on another HSPA phone next time it happens. Likely you'll get the lack of connection.
i had a similar problem with my sd card its cant be seen in rom recover or hboot but can be seen in windows makes me mad as i still cant use it and ive tried lots of other cards
onester2006 said:
i had a similar problem with my sd card its cant be seen in rom recover or hboot but can be seen in windows makes me mad as i still cant use it and ive tried lots of other cards
Click to expand...
Click to collapse
Try with phone in fastboot mode via USB cable
fastboot OEM enableqxdm0
Fastboot OEM erasecongig
Sent from my HTC Desire using XDA Premium App
It seems that your card had been broken.There's nothing can do when u fail to load a card using adapter...
Kotag82 is right. I had this problem about a month ago and used fastboot commander (search xda for it) to enter the following commands:
fastboot oem enableqxdm 0 (unblock your sd-card)
fastboot oem eraseconfig
(fix misc partition)
All data is still on the card and everything works again.
Sent from my HTC Desire using Tapatalk
The other day my CM7 desire suddenly crashed, and so I had to take the battery out. Since then it has not been able to read SD Cards in any way. I have tried multiple SD cards, and formatted them with different file systems. Even in Clockwork recovery I could not mount the sd card. The cards work fine on my computer and in my girlfriends phone.
I gave up, and decided to restore my phone to stock to try and return it to Orange for a replacement. I phoned them and they told me it was out of warranty so they could do nothing. In hindsight I should've waited for them to tell me this before I restored to stock!
My phone is now running Android 2.3 from the HTC dev site, which I installed by just executing the update within the .zip.
I have tried to root with unrevoked, but it gets stuck at "waiting for bootloader" in both windows and ubuntu.
I gained S-off using revolutionary in order to perform the commands (as the last command only works with s-off:
Code:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
Since going back to stock, I have tried different cards again. With certain cards (I don't remember which ones), my phone says "preparing SD card" but then tells me I have a "blank sd card or has unsupported filesystem". It gives me the option to format the the card, but this does nothing, and sometimes "unmounts" it.
This has given me hope, so does anyone have any ideas before I do give up?
It seems to me you somehow damaged the sdcard connector inside the phone when ripping out the battery. Did you check to make sure all the pins are not bend or bricked and all can make good contact with the sdcard ? Maybe the card cannot be pushed in the proper way ? something is holding it back or so ?
Doesn't seem to me as a rom/software related issue.
Yeah definitely seems like a hardware issue. Can push the sd card in like normal - at least it doesn't feel any different. Can't see the pins of the sd card reader as they are behind a piece of immovable metal.
Bluetooth is working?
As far as I know, it turns on and off and can discover and pair with devices.
http://forum.xda-developers.com/showpost.php?p=20873122&postcount=12
it worked on my desire
name.vic said:
http://forum.xda-developers.com/showpost.php?p=20873122&postcount=12
it worked on my desire
Click to expand...
Click to collapse
Thanks for the suggestion but it didn't work. I think this is a hardware issue unforunately.