I have a problem with RSD lite.... before rsd can easily detect my xt720 but after flashng the xda special rom the rsd lite cannot anymore detect the phone... all moto drivers are updated... please help.....
RSDLite not detecting phone
abet1017 said:
I have a problem with RSD lite.... before rsd can easily detect my xt720 but after flashng the xda special rom the rsd lite cannot anymore detect the phone... all moto drivers are updated... please help.....
Click to expand...
Click to collapse
This doesn't sound good, I hope their is a solution for you. I will repost in the XDA special thread for you as I am hoping it isn't a bug caused by the Special. I will need RSDlite again sometime soon lol.
Thanks....
Have you Resolved it?
Mioze7Ae said:
I don't think it is possible for a change on the phone to cause this problem as it is described. If you can boot into the bootloader (power on with both volume up and camera shutter down) then the problem is on the computer's side. The locked bootloader guarantees this. It could possibly be a problem with the hardware (USB cable, USB port) but driver problems seem to be pretty common on Windows+RSD Lite. If you have access to Linux/Mac OS, you could try sbf_flash.
The symptoms are not very well described. It sounds like what might be going on is a bootloop or stuck (M) after a successful flashing. I would try a factory reset. Let's continue this in the General thread rather then here.
Click to expand...
Click to collapse
Not yet... I tried to use other windows-based computer but still it did not work. The computer can recognize the phone and I can get to bootloader mode... the only problem when i opened the rsd lite, no detection at all. The only option i have is to flash other rom using nandroid and try again to use RSD. If it does not work then it is a problem for me to go back to the 2.1 stock rom... Hope there is other way to do that. Thanks.
After flashing the cbw rom, then go to bootloader mode, but the same problem the rsd cannot detect the phone....
Not to hijack a thread here, but I am experiencing a similar issue. The difference for me is that my phone is recognized, but RSD Lite won't allow the flashing to start even after selecting the SBF file. It's almost as if RSD Lite isn't getting info about the file (doesn't show up in the window on the right).
This happened with both the Singapore SBF and the CBW SBF in an attempt to flash when trying to get to the XDA Special Stock (beta). I've even uninstalled and reinstalled both the Moto drivers and RSD Lite. Running Win7 Pro.
banshee56 said:
Not to hijack a thread here, but I am experiencing a similar issue. The difference for me is that my phone is recognized, but RSD Lite won't allow the flashing to start even after selecting the SBF file. It's almost as if RSD Lite isn't getting info about the file (doesn't show up in the window on the right).
This happened with both the Singapore SBF and the CBW SBF in an attempt to flash when trying to get to the XDA Special Stock (beta). I've even uninstalled and reinstalled both the Moto drivers and RSD Lite. Running Win7 Pro.
Click to expand...
Click to collapse
Not sure how to help, but do you have debugging checked in settings/applications/develpoment/USB debugging and are you using the right sbf here is what I used Singapore SBF
Seems a little weird multiple people having rsdlite issues the last few days
Yes, USB debugging was on. It appears that I used the SBF you are referencing. As the OP is I'm sure concerned, this is a real issue if I can't get back to stock SBF for warranty issues. I suppose I could flash to the CBW Froyo and hook CBW up for warranty issues, but that's...meh...kinda cheating.
I have also read the Windows 7 doesn't like RSDlite and also read somewhere else that the version of RSDlite has been known to cause problems with recognization. I use 4.6 since day one and won't upgrade. Old saying, "If it aint broke, don't fix it." I think the latest version is 4.9 or something like that.
Hmm...I've been on Win7 for the entire time I've been flashing my XT720. I have version 4.6 installed and it said during an update check that it was the latest. I'm pretty sure I've tried doing this with the SD card both installed and uninstalled. It recognizes the phone fine, but for some reason, when I browse and select the SBF, it doesn't recognize the file.
That is wierd. See if someone can give you a nandroid of the stock SBF and maybe try that route through OR. Flash barebones stock nand/sbf and then move on from there. Not sure if the kernal will transfer with the nandroid. I am at work roght now, so I can't up/download anything. Seems to me that if RSDlite recognozes your phone but doesn't recognize the sbf it may have something to do with the file path. Not sure at this point.
OK, I may have figured it out. I'm at work right now (on a WinXP machine, not sure that is the diff) and started RSD Lite and plugged in the phone. It installed the OMAP3430 drivers and will now allow me to flash. I'm thinking the OMAP drivers at home are messed up. When I plug in my phone in bootloader mode into RSD Lite, it already recognizes it as model "S Flash OMAP3430". Perhaps an uninstall of those drivers and let the phone/PC do it over again.
Actually my computer OS is windows 7 ultimate... if my rsd issue will never be resolved so I think I need to have a nandroid of Singapore sbf... hope it is possible....
banshee56 said:
Hmm...I've been on Win7 for the entire time I've been flashing my XT720. I have version 4.6 installed and it said during an update check that it was the latest. I'm pretty sure I've tried doing this with the SD card both installed and uninstalled. It recognizes the phone fine, but for some reason, when I browse and select the SBF, it doesn't recognize the file.
Click to expand...
Click to collapse
I don't know bud, I have done that once and it was simply cause i clicked on the wrong file or wrong part of the file.
Related
Hi, I recently rooted my Droid 2 Global (The white one, if it matters) and attempted to put on the GB leak which caused it to get stuck in Bootloader mode.
Now Ive tried flashing multiple D2G .sbf files with RSD Lite v4.8 with no luck, and tried using the Linux one.
It is the Bootloader D0.11 and it says Code Corrupt.
Is this thing completely bricked or is there anything I can do to save it?
Thank you in advance.
Also upon flashing on RSD Lite After it fails I just looked at my phone and it says
Critical Error: FEBE 0047
Can you get into the selection menu by pushing the search key on the keyboard
He flashed D2 (not global) leak on His D2 global. If I remember right, P3Droid said if you do so you may hard brick your phone.
Does bootloader say "ready to program"? Or just that "corrupt code"?
Try using the latest moto drivers and rsdlite. If they find the phone you might be able to recover it.
How did you flash the GB leak? Via SBF or using clockwork mod?
Sent from my DROID2 GLOBAL using Tapatalk
1. if you have researched a bit you would have seen that d2 gingerbread doesnt work on the d2g, im not bashing you or anything just telling you that a little research would help next time
2. youre using the wrong reslite version, 4.8 wont work, you need to use 4.9
3. what version sbf are you using? could be that you flashed the d2 sbf as well
Hi there,
I flashed the CronosX 2.3.7 firmware onto my xt720.
it was running superbly until i messed it up .
i purchased a class 6 sd card to test the HD recording smoothness, but it all went wrong. i had no apps installed to sd, and i cloned the data on the OE sd to the new class 6.
the phone went a bit psycho after powering up force vlosing everything repetitively. i reinstalled open recovery, and reflashed the firmware. its not running correct, so i thought of rsd flashing 2.1 and start fresh
RSD picks up the phone in usb bootloader mode, but refuses to flash 2.1. the device description has no IMEI number. even on the phone, the phone details seem corrupt.
Any ideas how to proceed?
Try following the hints in this topic. Might be the same issue.
http://forum.xda-developers.com/showthread.php?p=23327622
OMGN00B said:
Try following the hints in this topic. Might be the same issue.
http://forum.xda-developers.com/showthread.php?p=23327622
Click to expand...
Click to collapse
thanks for the link, but not the same issue.
RSD lite does not recognise it as a motorola xt720 anymore. there are no device details, hence the 'start' button on rsd is ghosted.
i got the firmware[2.3.7] and sd card functional once again. but will consider flashing a 2.2 rom using open recovery if i need to go back for any reason. at the moment i dont want to mess it up further
In case you change your mind:
1. Make sure you run RSDLite as administrator if you run it under vista/7 (Didn't work for me when running it normally)
2. In the list, my device is listed as "S Flash OMAP3430" and not Milestone XT720
3. The IMEI and some other details of my phone are N/A too but I flashed successfully several times.
Also: The bootloader you should be in black with some text.
PS. Found this video on youtube to help:
ID: KA67WaBfGWQ
OMGN00B said:
In case you change your mind:
1. Make sure you run RSDLite as administrator if you run it under vista/7 (Didn't work for me when running it normally)
2. In the list, my device is listed as "S Flash OMAP3430" and not Milestone XT720
3. The IMEI and some other details of my phone are N/A too but I flashed successfully several times.
Also: The bootloader you should be in black with some text.
PS. Found this video on youtube to help:
ID: KA67WaBfGWQ
Click to expand...
Click to collapse
Ok, So i did change my mind. i have flashed 2.2 in attempt to get back rsdlite functionality with no luck.
Rsd recognizes the device as "S Flash OMAP3430" but the start button on rsd is not clickable.
i have tried to flash it on more than one pc, with the same result. i have even tried downloading a different stock rom [German].
Can someone please assist
No matter what I do, I cannot get the LG Support Tool to recognize my phone being plugged into the PC. I'm trying to do the new baseband install.
Running Win7 x86, already have the necessary files installed, getting to the last portion of the update, where LG support has to boot up, and it keeps telling me to install the driver.
I've downloaded the driver from the LG site, I already have the Nvidia driver installed on this PC. I plug in my phone and i see the P999 in the Device section of Manage Computer, has an exclamation point next to it so I search for driver automatically, no luck.
I don't know what the issue is.
dont do it automatically do it manually... and next time just post this in a thread already pertaining to this kind of stuff, less clutter the better.
mt3g said:
dont do it automatically do it manually... and next time just post this in a thread already pertaining to this kind of stuff, less clutter the better.
Click to expand...
Click to collapse
I've tried it manually, but no LG USB driver i've installed gives me a folder, it always is an EXE file.
Screw it, was reading that the phone needs a valid T-Mobile sim card. But my IMEI is blocked....sooooo this wont work for me.
Sent from my LG-P999 using XDA
watch a video on how to install it, I believe it is as easy as putting the folders in a dedicated folder (i have mine in a folder named "android") and just directing the files to the apx folder... not any .exe extensions
Are you currently running an ICS rom? I had the same issue but I flashed a rooted stock rom then I was able to get the LG tool to work. Might try that. Good luck.
The problem is that the USB driver is not recognized on my PC.
stevew84 said:
The problem is that the USB driver is not recognized on my PC.
Click to expand...
Click to collapse
I understood exactly what you meant. I had the same problem. The LG driver did not recognize my phone when I was running the Hellfire sandwich rom. The software did not detect that my phone was connected. I was beating my head on the desk trying to figure it out. Then I decided I would try restoring to a stock rom and try to pull the update. Restored to stock and no OTA update avail. So I went back to the LG software and it recognized it on stock. Still had CWM installed. All I had done was use the stock nand restore from here http://forum.xda-developers.com/showthread.php?t=1048274 If you need the file let me know and I will host it for you for a faster download.
Yatyas said:
I understood exactly what you meant. I had the same problem. The LG driver did not recognize my phone when I was running the Hellfire sandwich rom. The software did not detect that my phone was connected. I was beating my head on the desk trying to figure it out. Then I decided I would try restoring to a stock rom and try to pull the update. Restored to stock and no OTA update avail. So I went back to the LG software and it recognized it on stock. Still had CWM installed. All I had done was use the stock nand restore from here http://forum.xda-developers.com/showthread.php?t=1048274 If you need the file let me know and I will host it for you for a faster download.
Click to expand...
Click to collapse
Alright well thanks.
Hi guys. First, trust me that I have looked at every post I could find regarding this issue and the reason I am starting a new thread it because the fixes are not working for me. First, my phone:
Droid Razr HD Dev Edition, I believe it's the T926, though it doesn't boot now so.....
I had rooted this phone with the Droid Razr HD Utility 1.1. I had it running on T-Mobile fine for quite some time (only HSA speed or whatever they call it, but that's fine I'm out of range for anything better anyway). I had Superuser installed and something like root keeper I think it was called. Anyway my point is everything worked great.
I started getting this popup that seemed to say Motorola wanted to do an update. Now I had ignored the update on my phone for a while as I didn't want to go through the process just yet. Finally I gave in and I let the Motorola from my Windows PC try to push an update. That was the last my phone has booted.
So now all I get is Fastboot. Now if I do the buttons and manually go to fastboot it looks normal and I connect USB and it looks fine. But if I try to run the HD Utility 1.10, 1.20 both fail, RSDLite 5.6 and 6.0 both fail. All I can come up with is No valid PIV block in sp for system. The phone does seem to respond when I try the utility but all I get is failures and it clearly says the phone is locked. RSDLite has no such luck and immediately fails.
I still have the original XT926 xml I used and I also downloaded a VZW_XT926. I'm really SOL here guys and I would so appreciate any help.
I guess the last bit of info I can think to add is that when I plug USB in fresh what looks like Motorola software (what messed me up to begin with) pops up and tells me it wants to repair the phone. Of course like an idiot I've tried that as well.
My guesses are; you are using an outdated utility, outdated fastboot files, outdated RSD lite (there is 6.1 and higher out) and/or your system is corrupted. So make sure all of your tools and files are up to date and report back if you get any further.
Were you on ICS or JB before the update nag? Pretty sure if you were on Jellybean you will have to wait for an xml to be released, I remember reading something like this on DroidRzr.com
coolloser said:
My guesses are; you are using an outdated utility, outdated fastboot files, outdated RSD lite (there is 6.1 and higher out) and/or your system is corrupted. So make sure all of your tools and files are up to date and report back if you get any further.
Were you on ICS or JB before the update nag? Pretty sure if you were on Jellybean you will have to wait for an xml to be released, I remember reading something like this on DroidRzr.com
Click to expand...
Click to collapse
I was on JB so I'll do some more research on that. I saw a 6.1 for RSD but skipped it due to reg req. I'll hunt it down. How do you update Fastboot? I was just updating Razr HD Utility and letting it do it's thing. I have 1.2 now and it has Fastboot inside. Is that what you mean or am I missing a step?
Thanks for your help.
Dagroth said:
I was on JB so I'll do some more research on that. I saw a 6.1 for RSD but skipped it due to reg req. I'll hunt it down. How do you update Fastboot? I was just updating Razr HD Utility and letting it do it's thing. I have 1.2 now and it has Fastboot inside. Is that what you mean or am I missing a step?
Thanks for your help.
Click to expand...
Click to collapse
After Jellybean there needed to be new Fastboot files because of some security change in Android, the newest utility most likely has it. I found this file
http://sbf.droid-developers.org/vanquish/VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml.zip
in this thread:
http://www.droidrzr.com/index.php/topic/15828-rsd-lite-stock-412-firmware-restore-not-working/
If you are still stuck after that I suggest signing up on DroidRzr.com and joining the chatroom, those guys know far more than I!
Just an update that nothing I have tried has worked and I remain bricked. I've updated the DroidRAZR Utility, RSDLite, tried numerous images... still bricked. No valid PIV block in SP for system.
Dagroth said:
Just an update that nothing I have tried has worked and I remain bricked. I've updated the DroidRAZR Utility, RSDLite, tried numerous images... still bricked. No valid PIV block in SP for system.
Click to expand...
Click to collapse
Well I finally got it working. I tried as much as I could find, RSD 6.1.4, Droid RAZR Utility 1.2, many many many images since my original wasn't working. Anyway I'll skip all that didn't work.
My problems got compounded when my battery died. The internet goes on about how bad this is. True to form when I found and tried to manually push an image with fastboot I kept getting errors about the batter. Now this phone is the developers edition and I read somewhere about how you can buy this special cable. Like most of you I have dozens of USB cables and at one point my original was misplaced. Ah, your catching on now aren't you? I went hunting and dug up my original cable and the blasted thing just booted right up. No re-imaging, nothing, just booted right up.
Now I "had" successfully (today) sent a fastboot of a new system.img from the Droid RAZR Utility 1.2 and checking my system I do see that indeed that is the img I am on. So this may have been a two fold rescue.
So in the hopes it helps any other poor sap out there. Here is how I fixed my bricked Droid RAZR HD xt926 that had a near dead battery.
Boot into AP Fastboot
On windows computer, navigated to folder where I had extracted Droid_RAZR_HD_Utility_1.20
fastboot flash system system.img >>This worked
fastboot flash boot boot.img >> this failed
I then dug up my original cable, plugged directly into wall adapter and voila - it booted up!
Unfortunately I think I'm on JB now, but hell at least my phone is working again!
Thanks for the replies, thanks for your hard work tearing these phones down and giving us tools to work with and thanks to the *** *** internet for being so awesome and giving us so much at our finger tips!
Unbricked
Dagroth said:
Well I finally got it working. I tried as much as I could find, RSD 6.1.4, Droid RAZR Utility 1.2, many many many images since my original wasn't working. Anyway I'll skip all that didn't work.
My problems got compounded when my battery died. The internet goes on about how bad this is. True to form when I found and tried to manually push an image with fastboot I kept getting errors about the batter. Now this phone is the developers edition and I read somewhere about how you can buy this special cable. Like most of you I have dozens of USB cables and at one point my original was misplaced. Ah, your catching on now aren't you? I went hunting and dug up my original cable and the blasted thing just booted right up. No re-imaging, nothing, just booted right up.
Now I "had" successfully (today) sent a fastboot of a new system.img from the Droid RAZR Utility 1.2 and checking my system I do see that indeed that is the img I am on. So this may have been a two fold rescue.
So in the hopes it helps any other poor sap out there. Here is how I fixed my bricked Droid RAZR HD xt926 that had a near dead battery.
Boot into AP Fastboot
On windows computer, navigated to folder where I had extracted Droid_RAZR_HD_Utility_1.20
fastboot flash system system.img >>This worked
fastboot flash boot boot.img >> this failed
I then dug up my original cable, plugged directly into wall adapter and voila - it booted up!
Unfortunately I think I'm on JB now, but hell at least my phone is working again!
Thanks for the replies, thanks for your hard work tearing these phones down and giving us tools to work with and thanks to the *** *** internet for being so awesome and giving us so much at our finger tips!
Click to expand...
Click to collapse
I was trying to load a different ROM (running 4.4.2) so I could unlock the bootloader and root and hard bricked my phone with the same error message as a result of a failed flash. Using the fastboot command (fastboot flash system system.img) I was able to load the system.img from VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF_SVC.xml and now am booting successfully once again.
Dagroth, you pulled my fat outta the fire! Many thanks. I hope this message helps others.
Hello everyone!
Recently I have installed, Danik's ROM and Kernel on my Milestone 2, but I wanted to flash back the CM11 and the original Kernel. So I went to bootloader mode, and flashed the right sbf, but now the phone is dead... when I plug into computer, the white charge led lights but the screen is black, and Windows doesn't recognise the device.
What should I do, to get back to the roots?
Thanks in advance
rkrisi said:
Hello everyone!
Recently I have installed, Danik's ROM and Kernel on my Milestone 2, but I wanted to flash back the CM11 and the original Kernel. So I went to bootloader mode, and flashed the right sbf, but now the phone is dead... when I plug into computer, the white charge led lights but the screen is black, and Windows doesn't recognise the device.
What should I do, to get back to the roots?
Thanks in advance
Click to expand...
Click to collapse
factory reset your phone with stock recovery
-turn off your phone
-Hold button key X on keyboard with power key
Hello,
in case of big troubles, follow precisely in each step this guide: http://forum.xda-developers.com/showthread.php?t=1032372
to find RDSlite use google to avoid any driver/permission problem, if you can, use an old Win XP computer or a virtual machine.. let us know if it works..
thanks for the replies, I always use XP for flashing, because Win 8.1 isn't supported. Now the only problem is, that windows doesn't recognise the phone, I think the battery is too low, now I am trying to charge it up with an external charger... Anyway someone know what to do if I used Danik's kernel and I want the original back? I don't have to flash some kernel sbf or something like that before flashing the original rom with rsd lite?
Now if I connect the phone to the PC it recognises, but the screen is black. If I start flashing it with the right sbf, the phone screen shows the SW Update In progress screen, and when the flashing complete, the phone reboots, but always gets back to Bootloader mode with black screen
I think I have this BL version problem, because before bricking my phone the original rom was 2.2 AsiaRetail.. What should I try, I dont know what bootloader version installed last, but I read that this problem is caused when trying to flash a rom with an older bootloader than installed
rkrisi said:
I think I have this BL version problem, because before bricking my phone the original rom was 2.2 AsiaRetail.. What should I try, I dont know what bootloader version installed last, but I read that this problem is caused when trying to flash a rom with an older bootloader than installed
Click to expand...
Click to collapse
Did you try one of these ?
http://sbf.droid-developers.org/phone.php?device=29
rkrisi said:
I think I have this BL version problem, because before bricking my phone the original rom was 2.2 AsiaRetail.. What should I try, I dont know what bootloader version installed last, but I read that this problem is caused when trying to flash a rom with an older bootloader than installed
Click to expand...
Click to collapse
hello, sorry for the late reply.. I hope I have understood your problem but if I'm wrong, tell me.. well, I always kept my MS2 to the first *.sbf version (froyo) to avoid problems but in your case, you may try using the latest *sbf (the gingerbread one) and then upgrade to the rom you want.. or, if you have upgraded you can try the downgrade procedure: http://forum.xda-developers.com/showthread.php?t=1497263
or, I have found this: http://forum.xda-developers.com/showthread.php?t=1236296 have a read, it may be usefull..