So my razr is softbricked. I have been reading the forums here for the last 4 days, probably around 10 hours+ reading for solution. Anyways, my phone refuses to turn on and it pulls up the "downgraded security version" on the fastboot screen. Now, adb recognizes my phone in fastboot mode, and I tried flashing back the stock firmware (I had it updated to 9.30 locked bootloader) to no luck. I read that RSDlite is the way to go, but it refuses to recognize my phone. I have updated the drivers close to 9 times already, and I honestly doubt that's the issue, as adb can recognize my phone just fine. Under configuration/Flash Modes there's an option for fastboot, which is greyed out and unclick-able. Is there something I could do to get it to recognize my phone? I'm not ready to give up on it just yet.
I figured the reason RSDlite wasn't working. For those who are experiencing similar issues with RSDlite not recognizing your device, I can confirm that it does not work with windows 8.1. You will have to run it in windows 7, or else it will not recognize your device.
When you say windows 7, do you mean a true physical win 7 machine, or windows 8.1 with rsdlite being executed in win 7 compatibility mode? I can't get rsdlite to work on my laptop as well and have no other machine..
Sent from my RAZR HD using Tapatalk
I have another old desktop running windows 7. I tried it there and it was able to recognize my razr in fastboot. My laptop runs windows 8.1, and no matter what I did, rsdlite didn't recognize my razr. I think rsdlite just doesn't support 8.1 yet.
Thanks for the clarification, although it was not the answer I was hoping to hear
I honestly would switch my laptop to windows 7, if i didn't have to pay the 100$ for the OS. I still can't seem to adapt to windows 8. I don't like the answer any more than you do, I messed around with the settings enough to give up. Hopefully they might make a patch in the near future to allow it to work on windows 8.1.
Needs to be USB2.0 and you need to use the original moto cable.....generally it does matter
I used a USB 2.0 port on my laptop and desktop, same sync cable on both. If the cable was the only thing stopping it in windows 8.1, then I'm sure it would had been the same in windows 7. However, I was fully able to use RSDlite on my windows 7 desktop without any issues.
cmh714 said:
Needs to be USB2.0 and you need to use the original moto cable.....generally it does matter
Click to expand...
Click to collapse
unfortunately I don't even have a USB2.0 port anymore on my ultrabook.. ah well, who needs RSDLite anyway, but still weird that it doesn't work.
Virtualize a W7 Os
Yeah, my RSD Lite doesn't recgonizde mi device, just in w7. You guys could install a virtual machine program like VM Ware or Virtual Box and Install the drivers, RSD Lite and the desired Firmware.
Related
Hi
Just for the fellas having problems when upgrading to a custom or signed ROM on the HTC FUZE on a computer with windows 7 and windows mobile device center.
you MUST be online at the time of installing a new rom
so the windows update downloads the " qualcomm cdma technologies msm" driver that recognizes your FUZE when windows mobile " is not present ".
I don't think I was connected when I did mine.
And that was flashing the Energy rom onto my Fuze.
I can't remember 100%, but I'm ~80% sure I wasn't. Maybe I just got lucky?
EDIT: Though that wasn't the first time I'd flashed. Maybe that was the differentiating factor.
alfmetal said:
Hi
Just for the fellas having problems when upgrading to a custom or signed ROM on the HTC FUZE on a computer with windows 7 and windows mobile device center.
you MUST be online at the time of installing a new rom
so the windows update downloads the " qualcomm cdma technologies msm" driver that recognizes your FUZE when windows mobile " is not present ".
Click to expand...
Click to collapse
i'm guessing this is the first time you're flashing for W7, the phone goes to bootloader mode and requires drivers that can be gained from Windows Update... after the first time, if you flash again using the same USB port, you'll be fine... using another USB port requires installing drivers again but you'll have the drivers saved in the windows folder
Is there some trick to get customruu.exe working?
Also i have problem syncing, i can only get it working if i disable fast data syncing.
I'm running latest energyrom and win7 ultimate x64 rtm
BigJayDogg3 said:
I don't think I was connected when I did mine.
And that was flashing the Energy rom onto my Fuze.
I can't remember 100%, but I'm ~80% sure I wasn't. Maybe I just got lucky?
EDIT: Though that wasn't the first time I'd flashed. Maybe that was the differentiating factor.
Click to expand...
Click to collapse
yeah, i think thats the difference, i was using a tmobile MDA with WM 5 like 2 years ago, and used to install custom roms but back in the time i had dsl so i never had a problem doing it.
so, BTW, how fast is the Energy rom?
the one i have looks nice but i feel is very slow
paperWastage said:
i'm guessing this is the first time you're flashing for W7, the phone goes to bootloader mode and requires drivers that can be gained from Windows Update... after the first time, if you flash again using the same USB port, you'll be fine... using another USB port requires installing drivers again but you'll have the drivers saved in the windows folder
Click to expand...
Click to collapse
i wonder if there is an offline mode to do this?, without an internet connection.
Daniehabazin said:
Is there some trick to get customruu.exe working?
Also i have problem syncing, i can only get it working if i disable fast data syncing.
I'm running latest energyrom and win7 ultimate x64 rtm
Click to expand...
Click to collapse
not that i know, but i have win7 32 bits version, so maybe its has something to do with the 64 version
It could be that there are no 64bit drivers for the phone available. I use Win7 x32 and it is a hassle getting it first sync'd up. What I normally do is just put the phone in bootloader mode before plugging in the USB cable. That way it only downloads the drivers it needs the first time.
Usually takes me a few resets of the PC and a couple Mobile Device Center restarts to get it to start ticking. Perhaps try downloading the latest Mobile Device Center, even if yours is the latest... just install over the existing installation. That's worked for me a few times.
Is it your first time flashing? Is it a newer Fuze? Because the latest Fuze's have a newer bootloader that is 1.95 (vs 1.90). I haven't found a way around it yet unless perhaps flash an official AT&T rom that has the 1.90 bootloader that may downgrade it... then HardSPL.
Just to add, windows 7 64bit here and haven't noticed one difference or problem with anything.
player911 said:
It could be that there are no 64bit drivers for the phone available. I use Win7 x32 and it is a hassle getting it first sync'd up. What I normally do is just put the phone in bootloader mode before plugging in the USB cable. That way it only downloads the drivers it needs the first time.
Usually takes me a few resets of the PC and a couple Mobile Device Center restarts to get it to start ticking. Perhaps try downloading the latest Mobile Device Center, even if yours is the latest... just install over the existing installation. That's worked for me a few times.
Is it your first time flashing? Is it a newer Fuze? Because the latest Fuze's have a newer bootloader that is 1.95 (vs 1.90). I haven't found a way around it yet unless perhaps flash an official AT&T rom that has the 1.90 bootloader that may downgrade it... then HardSPL.
Click to expand...
Click to collapse
Nah, had my raphael a long time, have flashed a couple of roms before, i'll try to put it in bootloader mode and let it install the driver, i'll keep searching for a customruu that works for 7 x64, Thanks for the reply
i got syncing working, uninstalled the driver for the mobile remote adapter, and let it download a new one from windows uppdate, and now it works, stange since it's the same driver as before...
I was having the same problem with windows 7 x64 and the fuze... found my solution elsewhere so i thought i'd post it here in case someone checks here first like me... I needed to install Windows Mobile Device Center to get the driver to work correctly with an active sync connection =)
I have W7 ultimate x64 and I can't flash either. But I don't mind. I just put the .nbh on the memory card, start up customRUU and it puts my phone in boot loader itself then installs the ROM off th ememory card.
even there's already a WMDC on win7, I tried to download it again from brothersoft, then it's update the driver..... done!
btw I'm using win7 x86, so I haven't tried on x64...
img707.imageshack.us/img707/3830/51947559.jpg
I can't post a pic or link...
I posted this in another thread, but created this new one specifically for these users that are having this issue and can't solve it because they don't have access to an XP machine.
I solved my issue late last night. I am running Windows 7 64bit. I saw that a lot of the guys here used XP to run the KDZ flasher and that wasn't an option for me until I installed XP Mode.
XP Mode allows you to run a virtual XP machine inside Windows 7. I was able to run the KDZ flasher in there and successfully flashed the KDZ GB file to my phone.
You do need to flash stock recovery first. I tried unsuccessfully to flash the KDZ with CWM recovery installed. It would not work until I flashed stock recovery.
One other problem I ran into is, in XP Mode, you are "attaching" USB devices to the virtual XP session via a "stub USB driver." For some reason during the KDZ flashing process the USB modem driver for LG kept releasing from my session. What I did to counteract this was manual attach it each time it released. This was easy, but I had to stay on top of it until the flasher finished the job. I have two monitors so I had the "Devices and Printers" window open in Windows 7, and when I heard the ding indicating the USB driver had left the session, and saw the LG devices appear in the Devices and Printers window, I would just click attach on the USB pulldown in the XP session.
I know this sounds a little complex for some (and possibly vague), but once you get into the XP Mode session you will see what I'm talking about.
I hope this helps you guys still stuck on SW Update screen that don't have XP.
hey guys whats up
i lost my nerves for 2 days tr5ying everything to bring back to life my P990..
since im huge noob with android i messed up everything when i tried to update phone with cm7. anyway i can bring it back to life with rom for p999 and thats it...
all other techniques dont work. cant even boot phone or whatever.. tried smartflash but i dont get anything what should be automaticaly assigned.. like communication driver..com port etc. i wanted to try kdz but this file cant be downloaded..its forbidden on lg site and now it cant be downloaded on megaupload. can i download file from somewhere else? im really pissed off cuz im stuck like this. please help
http://forum.xda-developers.com/showthread.php?t=1056847
And if you have a P990, you're in the wrong forum (this forum is for the P999).
omerika.emir said:
hey guys whats up
i lost my nerves for 2 days tr5ying everything to bring back to life my P990..
since im huge noob with android i messed up everything when i tried to update phone with cm7. anyway i can bring it back to life with rom for p999 and thats it...
all other techniques dont work. cant even boot phone or whatever.. tried smartflash but i dont get anything what should be automaticaly assigned.. like communication driver..com port etc. i wanted to try kdz but this file cant be downloaded..its forbidden on lg site and now it cant be downloaded on megaupload. can i download file from somewhere else? im really pissed off cuz im stuck like this. please help
Click to expand...
Click to collapse
The Roms for the p999 and the p990 are not inter changeable. Different frame work.
jrfaulkin said:
I posted this in another thread, but created this new one specifically for these users that are having this issue and can't solve it because they don't have access to an XP machine.
I solved my issue late last night. I am running Windows 7 64bit. I saw that a lot of the guys here used XP to run the KDZ flasher and that wasn't an option for me until I installed XP Mode.
XP Mode allows you to run a virtual XP machine inside Windows 7. I was able to run the KDZ flasher in there and successfully flashed the KDZ GB file to my phone.
You do need to flash stock recovery first. I tried unsuccessfully to flash the KDZ with CWM recovery installed. It would not work until I flashed stock recovery.
One other problem I ran into is, in XP Mode, you are "attaching" USB devices to the virtual XP session via a "stub USB driver." For some reason during the KDZ flashing process the USB modem driver for LG kept releasing from my session. What I did to counteract this was manual attach it each time it released. This was easy, but I had to stay on top of it until the flasher finished the job. I have two monitors so I had the "Devices and Printers" window open in Windows 7, and when I heard the ding indicating the USB driver had left the session, and saw the LG devices appear in the Devices and Printers window, I would just click attach on the USB pulldown in the XP session.
I know this sounds a little complex for some (and possibly vague), but once you get into the XP Mode session you will see what I'm talking about.
I hope this helps you guys still stuck on SW Update screen that don't have XP.
Click to expand...
Click to collapse
I'm running Windows 7 Home premium 64 Bit and Virtual XP Mode is not compatible with this version of Windows 7... Is there another way around this issue...???
Erocks said:
I'm running Windows 7 Home premium 64 Bit and Virtual XP Mode is not compatible with this version of Windows 7... Is there another way around this issue...???
Click to expand...
Click to collapse
VMware with XP on it/Google how to bypass limitation?
Found this to get Xp Mode on home edition idk if it works I just use VMware personally
http://m.tomshardware.com/news/windows-xp-mode-windows-7-win7,10213.html
Sent from my LG-P999
Hi folks,
wasn't really sure where to post this thread as my phone doesn't have a separate section and since this is more of a general issue rather than one related to a specific phone model, thought I'd try my luck here.
Anyways onto the problem - was gifted a Micromax A092 a few days back. Worked fine until last night when Windows stopped detecting it. When this issue first cropped up, a few times of disconnecting & reconnecting the USB cable got the phone working again but after I plugged in another phone to transfer data and reconnected mine, the issue became permanent and continues to persist.The phone charges when connected to the wall but doesn't charge nor does it get detected when plugged into the PC.
Now when I pull the USB cable and stick it into a different port on the PC, for a second or two, the "connected in charging mode" message appears in the pull down menu and Windows detects phone memory/storage briefly before both disappear. I haven't had the opportunity to plug it into a different machine to check whether its being detected but I can assure you that the USB cable isn't the issue as every other phone in the house works with all the cables I have been using ( 3 to be precise - 2 Micromax and a Sony cable).
Another strange thing I think I should mention in the hope that it could lead to a resolution is that ever since this issue started, none of the phones are being detected by fastboot/adb and don't appear in Device Manager under Android Device as Android ADB Interface. Just two days back, I flashed an Xperia M with fastboot but now the phone doesn't show up under Android Devices, just as Sony 0104 or something. Same with a Galaxy Star Pro. I have reinstalled Android SDK, usb drivers, fastboot/adb but no dice. Opening up the command prompt in the adb/fastboot folder and typing fastboot devices doesn't list any of these phones either.
So can someone please help me in determining whether this is a software or a hardware issue? Any suggestions are welcome and truly appreciated. Thanks.
If you updated your Windows to Windows 8.1 than have following problem:
Since Windows 8.1 MS expects a USB BOS descriptor - USB 2.0/3.0
see htthttp://blogs.msdn.com/b/usbcoreblog/archive/2013/11/26/why-does-my-usb-device-work-on-windows-8-0-but-fail-on-windows-8-1-with-code-43.aspx
There is a dirty solution which works on updated Windows 8.1 update 1:
http://forum.xda-developers.com/showthread.php?t=2598155
Maybe you need a reboot.
fanmile said:
If you updated your Windows to Windows 8.1 than have following problem:
Since Windows 8.1 MS expects a USB BOS descriptor - USB 2.0/3.0
see htthttp://blogs.msdn.com/b/usbcoreblog/archive/2013/11/26/why-does-my-usb-device-work-on-windows-8-0-but-fail-on-windows-8-1-with-code-43.aspx
There is a dirty solution which works on updated Windows 8.1 update 1:
http://forum.xda-developers.com/showthread.php?t=2598155
Maybe you need a reboot.
Click to expand...
Click to collapse
Thanks for the reply
No I haven't updated Windows. Mine's a standalone Win 8.1 installation that's been running for a good few months now.
Like I said, w/o any rhyme or reason, it stopped working in the middle of the night and so did fastboot/adb. I remember typing fastboot devices and having the phone detected just prior to Windows acting up and in following time period, I don't remember installing any software or applying any Windows updates. This issue basically just came out of nowhere.
I'll take a look at the links but will it work for someone who was already using 8.1?
XenolithicYardZone said:
I'll take a look at the links but will it work for someone who was already using 8.1?
Click to expand...
Click to collapse
These work arounds are only for Windows 8.1. The MS Patch should work, if you have not the latest patches. I have the latest patches installed and I cannot install the patch. I need the dirty solution for my old samsungs galaxy models and HTC One X with cyanogenmod 11 - M8.
At the moment I have no further ideas to help you.
fanmile said:
These work arounds are only for Windows 8.1. The MS Patch should work, if you have not the latest patches. I have the latest patches installed and I cannot install the patch. I need the dirty solution for my old samsungs galaxy models and HTC One X with cyanogenmod 11 - M8.
At the moment I have no further ideas to help you.
Click to expand...
Click to collapse
No worries man....guess what? On a whim, I plugged it back in and voila...there was detection. I have no idea how it started working but I have been at it all day and something probably did the trick though I have no clue what it was which is annoying me because if this were to happen again, I would be back to square one.
Ah I see...I did download the patch you had linked to but before I could get around to installing it, this thing started working again. Anyways good to know it won't work with the latest updates as I installed the latest Windows update just this morning myself.
Although now my phone's being detected, the fastboot problem still persists. Neither my phone or any other phones I have access to are detected via fastboot. They all show up under Device Manager as Android ADB Interface but are not recognized by fastboot. Its really irritating me because only 2 days back I flashed the Xperia M on the same damn OS but no dice now. I applied the Windows update hoping it would fix this issue but no luck so far. No software installations, no Window's tweaking...nothing. Hell I haven't even rebooted the PC in the last few days until this started happening. Strange. More research....yay
If you happen to recollect or come across any other workarounds, please do let me know.
use this driver worked for me
download these driver this is only driver fault
d-h.st/ZUh
copy link and download lenovo.zip and in device manager select android and use update driver option to install driver and its done try it works for me
get drivers from
micromax official website
Have the latest version of Moto Drivers and RSD Lite. installed under Windows 8.1 64 bit.
Phone is detect as a media device with factory cable, but in fastboot on the phone I get nothing with RSD Lite. Is there some issue with Windows 8.1? I can get it to detect just fine on a spare Windows 7 machine.
Any pointers or suggestions would be greatly appreciated.
It sounds like you are missing the fastboot drivers. With the phone plugged into the PC, boot to fastboot. then enter the windows device manager screen (from a run box type mmc devmgmt.msc and hit enter).
Make sure there is nothing with a yellow ? next to it. If there is, try completely removing the moto driver package you have installed, and reinstalling it from the moto site
asuhoops8628 said:
It sounds like you are missing the fastboot drivers. With the phone plugged into the PC, boot to fastboot. then enter the windows device manager screen (from a run box type mmc devmgmt.msc and hit enter).
Make sure there is nothing with a yellow ? next to it. If there is, try completely removing the moto driver package you have installed, and reinstalling it from the moto site
Click to expand...
Click to collapse
Thanks for the input and suggestions. Done and done, still no joy. Tried different ports and went back and forth uninstalling and reinstalling from the Moto website. RSD Lite just won't see the phone in AP Fastboot Flash mode.
I know I have used RSDLite before on this machine with this phone when I did the SlapmyMoto or RockmyMoto to gain root a while back. Just can't figure out what is holding me back at this point... Any other other suggestions?
rtaylor429 said:
Have the latest version of Moto Drivers and RSD Lite. installed under Windows 8.1 64 bit.
Phone is detect as a media device with factory cable, but in fastboot on the phone I get nothing with RSD Lite. Is there some issue with Windows 8.1? I can get it to detect just fine on a spare Windows 7 machine.
Any pointers or suggestions would be greatly appreciated.
Click to expand...
Click to collapse
try and older RDS lite that worked for me
rtaylor429 said:
Have the latest version of Moto Drivers and RSD Lite. installed under Windows 8.1 64 bit.
Phone is detect as a media device with factory cable, but in fastboot on the phone I get nothing with RSD Lite. Is there some issue with Windows 8.1? I can get it to detect just fine on a spare Windows 7 machine.
Any pointers or suggestions would be greatly appreciated.
Click to expand...
Click to collapse
I had the same problem. Using the USB 2.0 ports in my laptop instead of USB 3.0 ports solved my issue. If that doesn't work and you want to make sure you are completely uninstalling the appropriate drivers and software before attempting a reinstall, try using Revo Uninstaller.
rtaylor429 said:
Have the latest version of Moto Drivers and RSD Lite. installed under Windows 8.1 64 bit.
Phone is detect as a media device with factory cable, but in fastboot on the phone I get nothing with RSD Lite. Is there some issue with Windows 8.1? I can get it to detect just fine on a spare Windows 7 machine.
Any pointers or suggestions would be greatly appreciated.
Click to expand...
Click to collapse
and any reason you dont just use your win7 machine to flash if its working on that one?
asuhoops8628 said:
and any reason you dont just use your win7 machine to flash if its working on that one?
Click to expand...
Click to collapse
Well yeah sort of, I could have done that. However, The Win7 unit is a machine that serves another purpose on my network. It doesn't have any of my phone tools installed on it and didn't want to have to go back and forth between my main rig and this secondary machine. Keeping track of what is installed where gets to be a headache pretty quickly.
RSDLite, is a pretty basic tool, or at least I thought it was. But for the life of me, it just doesn't like Windows 8.1 on my main rig.
hey all...i need help did anyone been able to succefly msm his phone on a virtualbox? i had setup everything on a win7 wnd win 10 machine every driver and all so the msm detect my phone and all and its says conected but as soon as i press start boom "sahara conexion failed" its driving me nuts i have tried everything drivers the + and power button nothing work.....i need help urgently
so here is the conclusion after long testing msmtool does not work on virtualisation i tried (virtualbox and qemu/kvm)....my problem was almost similar to this
crispy-cat said:
So, my phone's bricked - it won't boot, just brings up fastboot. As the solution to this problem appears to be to use the MSM tool to do an "actual" factory reset, I downloaded the MSM tool, and the decrypted ROM from this link: https://androidfilehost.com/?fid=8889791610682918291.
First I tried this on a Windows 7 VirtualBox VM (I use Ubuntu on my actual computer). The drivers didn't even install right it seems, and the device (in EDL mode) wasn't even recognized. Then I tried it on my mom's Windows 10 laptop. MSM never showed the device as connected. I think possibly the lack of a USB 2 port could be the cause.
Finally I set up a basic VM with Windows 10 and a USB 2 controller, and it worked-ish. MSM recognized the device, showed it as connected and started doing its thing, but stopped at "Sahara Communication failed". What is preventing it from getting past this? I'm using the cable provided in the box. Everything is recognized correctly. I've retried multiple times but still the same result.
SUCCESS!
I had a spare laptop lying around, and it has USB 2 ports. I loaded WIndows 10 onto it and tried the MSM from there -- AND IT WORKED!
As much as I hate Qualcomm for their monopolistic business practices, I thank them for EDL mode. I also thank OnePlus for somehow failing to prevent the MSM tool from entering the hands of the public every time, and @Some_Random_Username for trafficking this good. Yeet!
Click to expand...
Click to collapse
crispy-cat said:
The USB controller is part of VirtualBox. I think you need to download and install the extensions pack for the USB 2.0 version. The problem is that the controller is not capable of the absolute direct communication that the software needs to work, or it just doesn't connect fast enough. This would be a great example of why Windows on a USB would be great, since you could just boot it. But then MS wouldn't be able to make its billions. So we lose.
I'd try VMWare and KVM to see if they do any better. I'm not sure if WINE supports USB passthrough or not. Otherwise try to find a Windows box you can use.
Click to expand...
Click to collapse
so i dualbooted windows and i was able to flash so in future references dont try on virtual box if your on linux or mac... ahh wish there was msmtool for linux
wasted-potential said:
so here is the conclusion after long testing msmtool does not work on virtualisation i tried (virtualbox and qemu/kvm)....my problem was almost similar to this
so i dualbooted windows and i was able to flash so in future references dont try on virtual box if your on linux or mac... ahh wish there was msmtool for linux
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...ad-tool-to-work-on-a-virtual-machine.4475529/ this person seemed to manage to get it working. My issue is now that I cant get edl to work. No matter what I do..
pyry666 said:
https://forum.xda-developers.com/t/...ad-tool-to-work-on-a-virtual-machine.4475529/ this person seemed to manage to get it working. My issue is now that I cant get edl to work. No matter what I do..
Click to expand...
Click to collapse
i have no clue i did exact same steps as he did even more with multiple attempts no luck so i gave up...
if you are stuck just dual boot temporarly install a light version of that spyware windows and set up your stuffs its flashed at first attempt for me even with a usb 3.0 port i read that its buggy with msm but wasnt the case for me
wasted-potential said:
i have no clue i did exact same steps as he did even more with multiple attempts no luck so i gave up...
if you are stuck just dual boot temporarly install a light version of that spyware windows and set up your stuffs its flashed at first attempt for me even with a usb 3.0 port i read that its buggy with msm but wasnt the case for me
Click to expand...
Click to collapse
I might just do that. I only wanted msm as a back up option. I am pretty sure I can fastboot flash back to stock atm anyway and I am not bricked, yet..