Database Info

RSD Lite issue

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.

[GUIDE] How to fix "Failed image LNX 0x0002 / RSD mode 2

I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!

mowassasin said:
I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!
Click to expand...
Click to collapse
So I went and bought the factory cable from the Black Hat guys, and luckily haven't had the need to use it. Any advice you'd like to give in case I need to at some point?

I guess the only advice I can give is: don't re-lock the boot loader when you have a custom rom loaded

You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk

bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
It wouldn't recognise any fastboot commands nor the RSD Lite program for me.
But if it does, then thats good.
Merely a heads up for those who were in the same situation I was

bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.

yaturner said:
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.
Click to expand...
Click to collapse
Over the course of a few hours I was able to fix this, so I am going to write this little walkthrough for you using a rom from bwcorvus's page (CLICK HERE) and then used the guide from dirtymindedx -(CLICK HERE)
The reason it took me this long (as well as doing other things) was because I used the wrong set up to unroot my tablet. I was using the Unofficial images that are on bwcorvus's link. Because I didn't read thoroughly enough in his breakdown, I made myself look like a fool...
What you want is NOT
UNOFFICIAL STOCK IMAGES
Click to expand...
Click to collapse
because you will not be able to lock the bootloader (IF you want it to be that way, which I did, and so it gave me a 0x000004 Error, and yes i see that you are having a 0x000002 but somewhere i read this could help that.) I just wanted to get rid of Clockwork Recovery Manager cause it was not working on my 3.2 rooted tablet, and thought that because i messed up teh whole image with playing around and upgrading and seeing how i could break the image without overclocking, i thought i should actually try and make it back to stock too. With this... I needed to do these steps...
1. Upgrade the Motorola drivers while the XOOM was plugged in, so then I would be able to use the Fastboot Correctly.
2. Download the correct roms for my tablet, (Wi-Fi is mine, just grab the one that fits your version and just follow along.)
3. Upgrade my ADB from google because for soem odd reason my fastboot did not like the xoom till i did that...
4. Used the STOCK CABLE. I can Confirm that the STOCK CABLE that allows you to recharge the phones, WILL WORK for this...
5. Once the ADB was set up, I restarted it, aka Hit the red X and then loaded it back up and then closed it again, just to make sure the services were updated somewhat...
6. Opened Command prompt and navigated to the folder that help the zipfile for the fastboot flashing guide (aka dirtymindedx's guide at the top), be using CD (Drive Letter):/location/of/the/folder/that/is/unzipped
7. I then checked over the information in the folder by using dir /a and then proceeded to read through the guide
7-1. A note here... I did the fastboot erase userdata instead, because I wanted to see if it would brick it again... (sorry, I was in a fowl mood with the world last night so I was waiting for it to get bricked so i had a reason to use it as an ice scraper on my car... (not like i would really do it... just wanted a reason for justification haha)
8. ???
9. Profit
This is only to get rid of a "already slightly bricked" device... which I had done after relocking the Rom that was not official to Motorola and now, after a few updates, i now have Android 4.0.3 for the Xoom that was OTA'ed, looking to see how easy it will be to root to reload my rpg game saves that i got caught up in (hence my disappearance from the forums haha...) but I hopefully helped you out in a direction to heads towards... and as long as you don't lock the boot-loader (which someone posted about it before i did...) you should be fine with any changes to the rom after the updates... Also, you can skip steps on this too... you can just flash the image and not the recovery menu and so forth, allowing you to keep other settings that are not part associated to the rom image.
Also sorry for the insanity in my words... I have been up for a good 36 hours with a half hour nap somewhere in there...

[Q] Motorola Defy default restore

Hello, I have a Motorola Defy which i have rooted and installed clockworkmod on it. I tried to install Cyanogen mod 7.1 from the website. The phone got to the boot screen where it continued to cycle through it thing and nothing more. I restarted the phone and now it gets stuck at the first screen where its says "google". I tried to enter recovery again (power + volume down) and clockworkmod is completely gone. I want to go back to the stock OS so it atleast works again. Ive tried using the update.zip option in the stock recovery mode but I keep getting an error "failed to verify whole-file signature" when using a signed copy of cyanogen mod. I also tried putting my backup in a zip with the same error. Ive even tried formatting my sd card. What do i do?

I was more or less where you are around June or so. I'm no expert by any means, but perhaps I can help. If memory serves I used a program called RSD Lite to flash it back to the stock unlocked rom I got from the "bl7 finally rooted" thread - if you unlocked a different way, I'd try to find your original rom.
Once you get to where you understand how to get back to stock it makes the whole thing a lot less scary, or it did for me. Once you get back up and running, try flashing Whiterabbit. I didn't have luck getting anything else to run, but that one worked the first time I tried it, and I'm very happy I persevered. Miles better than the stock OS.

Marvelicious75 said:
I was more or less where you are around June or so. I'm no expert by any means, but perhaps I can help. If memory serves I used a program called RSD Lite to flash it back to the stock unlocked rom I got from the "bl7 finally rooted" thread - if you unlocked a dirrerent way, I'd try to find your original rom.
Once you get to where you understand how to get back to stock it makes the whole thing a lot less scary, or it did for me. Once you get back up and running, try flashing Whiterabbit. I didn't have luck getting anything else to run, but that one worked the first time I tried it, and I'm very happy I persevered. Miles better than the stock OS.
Click to expand...
Click to collapse
I cant use the program as my phone doesnt get detected when connected to my pc.

OK, lets start with the basics, if I can remember it right... Have you used RSD Lite successfully before this? Drivers installed? Using bootloader mode? If any of this is unfamiliar go hit the beginner's thread - if you have done all this you may be beyond my help and in need of someone a bit more experienced.

Marvelicious75 said:
OK, lets start with the basics, if I can remember it right... Have you used RSD Lite successfully before this? Drivers installed? Using bootloader mode? If any of this is unfamiliar go hit the beginner's thread - if you have done all this you may be beyond my help and in need of someone a bit more experienced.
Click to expand...
Click to collapse
I fixed it, there were a different set of buttons to hold to get into boot loader. The default recovery was not over written as i thought (happened to all my other phones). Thank you very much for you help. It has been very much appreciated.

Glad to hear it.

Phone dead, help needed!

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..

[solved] Touchscreen only works with stock rom, how to go back from cm12 to stock?

Hi. Half a year ago, the touchscreen of my photon q (xt897 with cornholio sim-mod) broke and was replaced. The repair shop ran into difficulties, namely, the touchscreen would stay unresponsive if booted with a custom rom and not the stock rom. No joke.
They asked me if they could re-install the stock rom, which I had no problems with, little did I know that after installing a custom recovery and custom rom, these problems would occur.
The thing is: with the stock rom (or stock recovery?) everything worked, but after flashing a custom rom, it doesn't: the touchscreen is inresponsive.
So I tried different recoveries, flashed with fastboot. twrp is nice, even works with adb connect, but I can't use it, because the touchscreen doesn't work. cwm recovery (to fit cm12.1) can be handled via power button and camera button, but the afterwards booted rom can't be set up and used without touch, and from the keyboard only key "9" and some combinations are recognized.
What could have caused this?
I reflashed roms and recoveries and wiped, etc, all without success.
I don't know how to downgrade to stock again now after kitkat or lollipop.
Help would be very much appreciated! (I'm using linux terminals or windows through a virtual machine on the mac)

I can't say I recommend using a VM to do this, but I would think RSD Lite could get you back to a completely stock device. A physical Windows machine is recommended.
Good luck. In the future, it's always good to research how to get back to completely stock before you make any changes to the device... Just in case

Hi. Thanks for your answer. I've already tried with RSD Lite 5.6. but couldn't succeed.
The phone is recognized but the flashing ends already beginns with errors.
I tried the two stock images you provided in some other thread (the ones you uploaded at dev host). But I get the getvar error with either of the images, and after deleting the corresponding lines
"<step operation="getvar" var="max-download-size" />" flashing still doesn't work.
"Fastboot returns flash error" or something.
Are you sure this should work coming from lollipop and downgrading?
Since I read somewhere the partition table gets altered (didn't read that before flashing, that's true).

santamanga said:
Hi. Thanks for your answer. I've already tried with RSD Lite 5.6. but couldn't succeed.
The phone is recognized but the flashing ends already beginns with errors.
I tried the two stock images you provided in some other thread (the ones you uploaded at dev host). But I get the getvar error with either of the images, and after deleting the corresponding lines
"<step operation="getvar" var="max-download-size" />" flashing still doesn't work.
"Fastboot returns flash error" or something.
Are you sure this should work coming from lollipop and downgrading?
Since I read somewhere the partition table gets altered (didn't read that before flashing, that's true).
Click to expand...
Click to collapse
Please read the notes in the FXZ thread - you have to remove some lines to get a successful flash.
I would also recommend using a later version of RSD Lite. I believe I was using 6.1.5 last I flashed my PQ.
It should work in every scenario, that's the point of RSD. There have been issues with some users in the past, but I honestly believe most of those were machine or user related.

arrrghhh said:
Please read the notes in the FXZ thread - you have to remove some lines to get a successful flash.
Click to expand...
Click to collapse
Did you mean this thread?
http://forum.xda-developers.com/photon-q-4g-lte/general/rsd-lite-to-stock-t2908884
Sorry, I posted the wrong version before, I was using 6.1.5 (the last version available on rsdlite.com) when i got the errors. I'll try to locate 6.1.6
edit: That version didn't work neither; already with flashing the gpt0 partition I get the "phone returned error" message. So next I will try without the virtual machine, which means finding a windows latop. I'd rather flashed manually with fastboot on osx.

santamanga said:
Did you mean this thread?
http://forum.xda-developers.com/photon-q-4g-lte/general/rsd-lite-to-stock-t2908884
Sorry, I posted the wrong version before, I was using 6.1.5 (the last version available on rsdlite.com) when i got the errors. I'll try to locate 6.1.6
edit: That version didn't work neither; already with flashing the gpt0 partition I get the "phone returned error" message. So next I will try without the virtual machine, which means finding a windows latop. I'd rather flashed manually with fastboot on osx.
Click to expand...
Click to collapse
Do NOT use a VM as I stated before when flashing with RSD Lite. You could potentially brick your phone - what if the USB connection fails in the middle of flashing? I wouldn't risk it.
Also, that thread is not exactly what I was talking about but does have the issue in there:
you may have to open the zip and edit the xml, and delete the 2 lines "<step operation="getvar" var="max-download-size" />" if you get unknown command fastboot getvar max-download-size
Click to expand...
Click to collapse
That is from the original FXZ thread - make sure you do it........

I really don't believe touchscreen problems might be caused by incompatibility of custom ROMs, and guess installation of stock ROM won't help. In my PQ first problems with front camera started, then touchscreen worked only when keyboard was completely slided up, and after a day or so it stopped to respond at all. I believe what was responsible was a ribbon cable leading from screen to main phone part with PCB and keyboard. I replaced it by myself (nothing hard - had to unscrew several T4 or T5 screws and reconnect two ribbon cables), and it's working well now. You can buy complete screen/digitizer module on ebay or aliexpress for about 50$.

Hi.
Flashing through RSDLIte without the virtual machine in a genuine windows 7 worked without problems.
The mobile boots and behaves normally again, I then flashed twrp and a custom image, everything stays working as it should.
@rabinhood
Before flashing back to normal with RSDLite, in CM recovery I could select with the Power Button and move around (down) with the camera button only. Now that everything works again, navigation there is done via volume see-saw up+down, not through the camera button. (Of course now the hw keyboard and touchscreen work too) So I guess, a very basic layer must have been flashed broken before.
Thanks again for your help to get my device back to life.