Database Users

Reverting From GB to a 340 Based Rom

Just to clarify for several out there new to leaks. Correct me if I'm wrong anyone:
Going from "unrooted" GB leak:
1. unstall RSD Lite and Drivers, Run RSD Lite
2. Hold volume down+camera+power until screen flickers and release and you should have the white lettered bootloader screen.
3. plug phone in and RSD will see it and run the full .340 sbf
4. Phone will reboot when done into old .340 stock
5. Run z4root and then bootstrap in to install new rom.
Going from "rooted/deodexed" GB:
1. Use droid 2 bootstrap (or dx bootstrap with usb debugging disabled) to boot into clockwork.
2. For good measure clear data/cache, dalvik cache, battery stats.
3. flash maderstock or monster 340.zip
4. Immediately reboot only as to not brick
5. Run z4root and then dx bootstrap in to install new rom
**No you can not install a .340 rom directly from GB rooted or otherwise. You must flash back to .340 first**
Thats what I understand is that RSD was only used for the unrooted GB leak due to the fact we couldn't access clockwork. Hope this is correct and helps out.

Hm. It seems that it is easier to get back from deodexed GB than I thought. Yesterday I did it via RSD Lite – it was a REAL PAIN.

Sorry for noob question, my camera doesn't work and I can't play any MP3 file
anybody could help me, please

why wont it show up in rsd lite
my phone isnt being detected in rsd lite any suggestions. i have every possible driver i can think of installed no errors just not working.
please need help asap. trying to fix a friends phones before he goes out of town.

zz0122 said:
Sorry for noob question, my camera doesn't work and I can't play any MP3 file
anybody could help me, please[/QUOTE
You need to update your system. Sbf to the correct bootloader version and the get an OTA update
Click to expand...
Click to collapse

still no luck in getting the phone to be detected by rsd lite and ive tried everything i can find through searching google. any help would be greatly appreciated. thanks.

MahaVoodoo said:
Hm. It seems that it is easier to get back from deodexed GB than I thought. Yesterday I did it via RSD Lite – it was a REAL PAIN.
Click to expand...
Click to collapse
How did you rsd yours back to .340. I cant get mine to be detected by rsd. all appropiate drivers have been installed and have recieved no errors of any sort phone just not being detected by rsd.

Not sure if I answered this in the other thread or my browser didnt update. To get my rsd lite to see phone in bootloader go config >device id>first come first serve.

Make sure you have all the needed Motorola Drivers. rsdLite would not see mine untill i installed all the latest drivers...then a piece of cake

phone boots straight into bootloader and will not flash

I recently tried to upgrade to the new OTA gingerbread and it said that it installed okay, but after I reboot the phone it went straight to the bootloader with these errors: bootloader 30.04 err: a5,69,35,00,27. I then tried SBFing back to VRZ_MB810_2.3.34_1FF_01, but then it got through 97% of the flashing and got this error:: interface BP: loading RAM Downloader for Bootloader
failed flashing process. failed flashing process. interface BP: Error sending RAM Download for bootloader.
I have tried reinstalling the moto drivers with no luck. And it is also not charging. now when it boots into the bootloader it is flashing "battery low, cannot program" I searched all over the Internet and tried all of the recommended solutions like pulling the battery for a few minutes, I tried flashing four or five times, tried using older sbf, all with no luck. I would appreciate the help, thanks

You are going to need to charge your battery before you can sbf again. You might want to redownload the sbf again. If you go to droidxforums there is a linux distro that you download and burn as an iso to a cd that is really easy to run. First get your battery above 80 percent before you flash again. When I get to my computer I willingly post the link.
Sent from my DROIDX using XDA App
update: here is the link for the linux distro......http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html

It sounds like you are missing a driver that installs towards the end of the flash. Sorry I can't post the link, but you can google moto driver download. It's the 4.90 drivers.
Sent from my DROID X in Western Illinois

Xodus83 said:
I recently tried to upgrade to the new OTA gingerbread and it said that it installed okay, but after I reboot the phone it went straight to the bootloader with these errors: bootloader 30.04 err: a5,69,35,00,27. I then tried SBFing back to VRZ_MB810_2.3.34_1FF_01, but then it got through 97% of the flashing and got this error:: interface BP: loading RAM Downloader for Bootloader
failed flashing process. failed flashing process. interface BP: Error sending RAM Download for bootloader.
I have tried reinstalling the moto drivers with no luck. And it is also not charging. now when it boots into the bootloader it is flashing "battery low, cannot program" I searched all over the Internet and tried all of the recommended solutions like pulling the battery for a few minutes, I tried flashing four or five times, tried using older sbf, all with no luck. I would appreciate the help, thanks
Click to expand...
Click to collapse
When you get your battery charged SBF again, when it fails do the "SYSTEM" only SBF and it will work. I believe the error (err: a5,69,35,00,27) you are getting has to do with the stock GB recovery. I had that problem but I was still able to boot into CWR and install a recovery patch by TBH. Let me know if this works for you.

I was wondering if there was a resolution to this issue. I am getting the exact same issue, Err:A5,69,35,00,27 and I have done everything but stand on my head. Previous to reading bigshotrob22's post, I had re-SBF'd from multiple computers, using different SBF versions, driver versions, and RSD Lite versions. All resulted in getting the darn ERR:A5,69,35,00,27.
The only way I ever got anything different was to flash 1.13.604 and then I got an error message Err:A5,70,70,00,1F.
Again, I goto a new version and I go right back to original error though.
I tried bigshotrob22's suggestion and downloaded the system and full sbf files for 340. I flashed the full, got error... Then flashed system, still get error.
I am using RSD Lite 5.4 on Vista 32 with UAC disabled (full admin mode), latest Moto drivers as of this post. Again, I have tried all of the versions of bootable linux SBF's as well. All yield the same result.
Wife's phone, she is very unhappy with me, and if I don't get her back up and running, I guess I will be dropping $500 on a new phone, as she is still under contract. If Mama ain't happy, I sure ain't getting any! LOL!

You could try taking it to a VZ store and telling them that this happened after the OTA. Seems to me that this is their fault and they should fix it.

RSD Lite doesn't find my Defy

Hi,
today I decided to flash CM7 on my Defy (T-Mobile branded, still 2.1). So first I had to update from Android 2.1 to 2.2. But I never made it...
RSD Lite refuses to regconize my Defy on 3 different PCs (Win 7 Pro 64 bit / Win 7 Pro 32 bit / Win XP Home). I installed all drivers, used bootloader mode and "normal" mode, but RSD doesn't find my Defy. In Windows the Defy is found, i can browse the sdcard, the motorla logo is in my taskbar. I tried RSD Lite 4.9 and 5.3.1 I don't know where I messed up...
Before I tried to flash the new sbf, i rooted the defy via superoneclick to install titanium backup, does this affect rsd lite?
Also I made wiped data/cache , and now i have an old market version....
And the MSU Software doesn't find my Defy either, so i'm tipping on driver problems, but i don't know what to do
Can you help me?

did u try using more recent version of superoneclick?
EDIT: i meant rsd lite..mistyped

for what? as i understand it, for flashing a new sbf via rsd lite i dont need root? so whats the use of a newer version of superoneclick?

Gjin said:
for what? as i understand it, for flashing a new sbf via rsd lite i dont need root? so whats the use of a newer version of superoneclick?
Click to expand...
Click to collapse
sorry sorry..mistyped.. i meant RSDlite

Mined worked when i was using windows xp with the 5.2 drivers and rsdlite 5.3.1

even i used rsdlite 5.3.1...worked like a charm..and sometimes with older version i wasnt able to flash it..

hmm i tired 5.3.1 too, but no connection.
i already reinstalled the drivers but no change
/edit
would you suggest to clean my system from all motorla drivers, if yes, whats the best way.
and then in what order do i install what?
first drivers? (Motorola_End_User_Driver_Installation_5.1.0_64bit <- i have this driver) and then rsd lite?
anything else?

Gjin said:
hmm i tired 5.3.1 too, but no connection.
i already reinstalled the drivers but no change
Click to expand...
Click to collapse
what all does it say on the phone when u r in bootloader?

arpith.fbi said:
what all does it say on the phone when u r in bootloader?
Click to expand...
Click to collapse
Bootloader
09.10
Battery OK
OK to Program
Transfer Mode:
USB

hmm...try these
Pull out battery.
Reinsert battery while holding volume up key.
and RESTART your computer..this may help
+ make sure u have installed all the latest drivers..

doesn't help...
i deleted all motorola drivers + software, made a restart and installed everything again. but still nothing...
and not even the motorla update software finds the defy... why?

Gjin said:
doesn't help...
i deleted all motorola drivers + software, made a restart and installed everything again. but still nothing...
and not even the motorla update software finds the defy... why?
Click to expand...
Click to collapse
Could it be the cable? Can you do anything else that involves USB communication? transfer files or such?
If you have a linux box available I think it is easier to flash SBFs as it doesn't involve installing drivers.
Sent from my MB525 using XDA App

Run rsd lite as administrator
Sent from my MB525 using XDA App

lamr said:
Could it be the cable? Can you do anything else that involves USB communication? transfer files or such?
If you have a linux box available I think it is easier to flash SBFs as it doesn't involve installing drivers.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
I tried another cable, but no change. And yes I can do filetransfer. But as I wrote earlier the Motorola Update Software doesn't find my Defy too...
And yes I run RSD Lite as admin.
Can I use a linux live cd to flash sbf?

What about the usb cable?
Are you using the original motorola one?
Sorry, i've just read you've already been asked this question.
If you want to try to flash via linux, look here: http://forum.xda-developers.com/showthread.php?t=1076138

Gjin said:
Hi,
today I decided to flash CM7 on my Defy (T-Mobile branded, still 2.1). So first I had to update from Android 2.1 to 2.2. But I never made it...
RSD Lite refuses to regconize my Defy on 3 different PCs (Win 7 Pro 64 bit / Win 7 Pro 32 bit / Win XP Home). I installed all drivers, used bootloader mode and "normal" mode, but RSD doesn't find my Defy. In Windows the Defy is found, i can browse the sdcard, the motorla logo is in my taskbar. I tried RSD Lite 4.9 and 5.3.1 I don't know where I messed up...
Before I tried to flash the new sbf, i rooted the defy via superoneclick to install titanium backup, does this affect rsd lite?
Also I made wiped data/cache , and now i have an old market version....
And the MSU Software doesn't find my Defy either, so i'm tipping on driver problems, but i don't know what to do
Can you help me?
Click to expand...
Click to collapse
Ok so it seems you're right in saying you're having driver problems.
I can only make a suggestion which worked for me. Try loading the "motohelper" app. This detects your phone and fetches the drivers for you. You can find it here: http://www.motorola.com/consumers/v/index.jsp?vgnextoid=7323cc6e48970210VgnVCM1000008406b00aRCRD
hope this helps.

make sure you run rsdlite as admin and download latest version of rsd lite i used version 4.8 and all worked fine
edit..
i had to go into c:/programs/motorola/rsd lite/SDL.exe and run that as admin

thanks for all of your help, but i'm still stuck here...
at the moment, i'm using motorola driver 5.2.0, and rsd lite 5.3.1, motohelper says i have the newest drivers
And can anyone help me with my "market" problem? Like i said, i made 2 wipe cache/data and now i have another market version, as the one when i got the phone

now its getting a little bit weird ^^
i used a vm with win7 and the defy installed, the drivers in version 4.7.1 and i installed rsd lite 5.3.1. and now rsd lite finds the defy. now i'm not sure if i should use a vm to flash my defy ^^
with driver version 5.2.0 in the vm the motorola update software and rsd lite find my defy. i give it a try and flash inside the vm

yea give it a try..many people have actually used vm when rsdlite was not working properly...even one of my friend used it..it works perfectly..

oops ive killed it

hi guys.......lets cut to the chase......i think ive killed my atrix.i flashed it with the aura rom last night but had a few probs with it..it all booted and worked etc..so in my infinate wisdom i flashed it again.....but now it just hangs on the dual core logo,ive tried full wipes etc caches and all....tried to reinstall and all goes ok but it just wont boot,tried other roms but they wont install
if someone could help a noob id be grateful.....a pointer in the right direction or even step by step would be awsome,thanks in advance

Turn ON while pressing the volume UP button and see if "Starting RSD protocol" shows up.
If yes, I think you can use RSD Lite to flash the original rom SBF of your phone.
Which one do you have? An AT&T?

sorry should of said its t mobile uk and yes i can get up the starting rsd but ive never used rsd lite or flashed sbf things before

Using RSD Lite isn't recommended. But in your case I think it's necessary.
You can search for the original SBF rom of your phone while waits for someone more experienced to answer your question.
I've killed my phone 3 or 4 times and RSD Lite + my original SBF rom always "ressurected" it.
But wait for someone more experienced.

ok will do ....but i have no idea what im looking for,but thanks for the reassurance

this is the rom i had used if it helps for info
http://forum.xda-developers.com/showthread.php?t=1186990
and when connected to rsd lite i get this info
IMEI/ESN/MEID: N / ATechnology: N / ASoftware Version: N/aFlex Version: N/aBootloader Version: v0x000007DRM Version: N / A

RE:
Sorry for the hijack but i am having the same issue. Now my battery is dead and it says its starting RSD lite protocol but then says battery is too low to flash but it won't charge it at all. Anyone have a link to the battery cable hack?

RE: fixed
I got my issue fixed by rigging a charging cable straight to the battery... Risky but it worked!
As far as fixing the other issue, I downloaded the stock 4.5.141 sbf file and flashed it through RSD lite so that should fix your issue as well. Once i did that I followed this guide and rooted, unlocked, installed cm9.
http://forum.xda-developers.com/showthread.php?t=1136261

well bit suprised at the lack of input but ive sorted it myself anywa.....flashed it with fruit cake and tht got it up and running (lucky as when it fired up it had 11% battery left)
i formatted the storage both internal and external,i then reflashed it with
cm7 mod 3
so its up and mended

Help with Defy with Android Eclair 2.1

Hi,
I think I've tried everything and was almost losing hope, but decided to ask for help before giving up.
I just bought an used defy, because I've had this phone before and I love it. But since it's still rocking Android Eclair 2.1 and the Google Play Store does not work, it's not very useful. So I wanted to upgrade it to Kitkat (CM, don't remember if it's 7 or 11) like I did to my previous phone.
First steps: what worked:
I've downloaded and installed Framaroot and 2ndInit (v2.3) without much issues. The problems started when I've tried to use ClockworkMod to flash an update.zip image. No matter what I did, I could make it mount the sdcard problem. I've tried with multiple sdcards, formatted the card using the phone itself, transfered the files with the card in the phone, but ClockwordMod could not mount it for anything.
I have read somewhere (maybe here) that ClockworkMod with Eclair had these kind of problems, and I would have to flash an SBF and upgrade it to Froyo before flashing anything else.
For that, I needed RSDLite, fine, did it with my other phone a few years ago. The problem is, I only have a MacBook and a PC with Windows 10 and no version of RSDLite would work with Windows 10, I've tried multiple compatibility settings with different versions of RSDLite and Motorola Drivers and nothing worked. When I was about to give up, I found out about sbf_flash utility for mac osx and linux (from here). I thought my problems were solved, but when trying to flash the sbf with my MacBook, the phone freezes and I get a "Waiting for phone" message on the screen. If I disconnect the cable, the phone instantly reboots and when it comes back to the bootloader, I get an error on the screen (attached). Again, tried with multiple variants of sbfs found on this page, with and without sudo, always with the exact same outcome. Maybe it could be an osx problem, but the only machine with linux that I have access is a raspberry-pi with ARM arch, and the sbf_flash linux binary is for intel platform and it doesn't work, so I can't test it on linux.
I have a feeling this phone was downgraded back to Eclair after being flashed to be sold, and now I can't manage to flash anything else to it.
Does anyone else has any idea about what else I could try?
Thank you all in advance, this community is amazing.

First of all,make sure you have the correct firmware
Not using mac...But i'd guess it might be solved with a flash in windows7 or xp,you can just use a vitual machine and delete it later.
I faced problem like this bcuz i connected to the front usb rather than the back one,so notice this.
Hope it would be helpful,it is great to see there is still someone using our beloved defy:laugh: