[Q] Should I do anything with this Defy? - Defy Q&A, Help & Troubleshooting

Hi,
got a questions to ask anyone response will help. This is my third Defy from Moto. First one screen went crazy after 9 mos. some part on screen stop working so i got replace then when i getting 2nd one found this website and of course everything look interesting who would want to stuck on 2.2.1 version right when you can get to 2.3.7 now. So I start reading, save all files that needed everything seem easy so i start w/o reading some parts lol...I had tmobile MB525 so I go with top one on list SBF page. Root with superoneclick 1.95 -> flash with RSD Lite 4.9 everything went fine....finished said reboot manually (that something haven't seen on any thread) it stuck on M logo with red circle won't let me do anything else (Power+ or Power-, remove battery all that) so read again found thread said fix with JORDN_U3_97.21.51 and process went fine up and running again but this time back to 2.1, simcard no signal, all app not work beside browser with wifi which assume can fix later. did this and that (don't even remember what else I did) but don't want to mess up again which end up the phone won't even turn beside white light while connect to PC so contact Moto that the phone ran out of battery put to charge over nite been 2 days and the phone never turn back on hope to get lucky which i told them while on the phone that i know the phone was a refurblish when I got it maybe something went wrong. Yup, they send me a replacement one again so this is my 3rd Defy in one year...
I'm not sure I still want to play with it anymore but like i said I don't want to stuck on 2.2.1. but there're lot of thing I don't understand and seem risky like the 2nd Init don't even have idea how to put it in the phone with apk file which i have a zip file w/o any .apk. PPl said just put in SD card it's already apk so I did but in the file manager still can't run the dang file. so everything stop....I got another file call defy_recovery-1218-0326-signed.apk and it work but don't think it does like 2nd Init.
And if still a go, which SBF you guy do, CM7.2 or CM9. I did wrote down all info in about phone this time just incase it will help anything in future.
Thnks in advance

I suggest you not to do a thing until you understand what you're doing - and it doesn't seem to be the case here. Keep reading.

Related

help! Defy wont boot, white light at top, rsdlite doesnt recognise

Deleted by user
I suggest you to completely charge your phone for half a day and then try to power it on. It should at least get stuck in the M logo.
Sent from my MB525 using XDA App
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Was your battery low when you tried flashing? It will not charge in bootloader mode so if you're battery is low you will have issues. If you boot with volume up pressed does it give you a message?
Try the Mcgyver battery fix found in this forum.
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse
Deleted by user
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
gookia2000 said:
Hi all, I am a proud owner of a t-mobile defy (for about 2 months now!) and my hands got itchy today and went ahead to "debrand" it following the guide by Higgsy.
I was trying to flash a uk 2.21 rom onto my t-mobile defy (rooted with z4root).
Well, I managed to do all the steps of the guide. my phone was recognised by rsdlite, i selected the uk 2.21 sbf file, i clicked start, and it started flashing the different code groups. Finally, it said "finished" and "PASS". Here is when the problem started. The phone did not reboot into android. It was just a blank screen with a white light on the top (where the green led is to inform you about new messages.)
i panicked and disconnected the phone (the white light turns off after disconnecting), took out the battery, tried rebooting, tried rebooting into recovery (power + vol down), tried rebooting into bootloader (power + vol up). Nothing worked. it just stayed dead.
I then plugged it back into the computer. immediately the white light came back on and rsdlite recognised my phone. i tried flashing again - same result. I then tried flashing the 2.52 uk rom - same result.
even more panicky now, i unplugged everything and decided to take a nap and hopefully think of some ingenious solution to the problem. now, after a 3 hour rest, i tried plugging the phone back into the computer. the white light comes on, but now rsdlite doesnt even recognise the phone.
In essence, is my phone bricked? I cannot:
1) load into recovery to do a nandroid restore (yes, i have a nandroid backup copy)
2) load sbf files from rsdlite. every sbf file i tried doesnt seem to work. now its worse as rsdlite doesnt even recognise my phone.
i have even tried doing a nandroid restore via adb. but i get the error message that no phone was detected in the command prompt. perhaps its because the phone was not started in recovery mode.
The only explanation i can think of is that i have recently updated to the t-mobile 3.6.360 update and that might be the reason why so many people before me were able to flash their defy's roms successfully while i got stuck.
Can anyone please help? I LOVED my defy more than any other phone, and 2 months was too shortlived!
Click to expand...
Click to collapse
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse
Deleted by user
Actually, all you have to do is press the power button while the LED is on and RSDLite is running. You will hear the USB detection sound and your phone will appear on the list. It won't appear as it normally would but it will be listed.
Then just choose the Froyo ROM and then click start to flash it. It'll take less than 10 minutes...
There's no other way that I know of to get it working. Even in the link that I posted, you can check and see that no one even bothered to give me an idea of what to do. I had to figure this out myself.
I figured it was the bootloader protection that was causing the problem so the logical choice was to flash the only T-Mo ROM available which happens to be the leaked Froyo.
It's been almost 24 hours and I've had no problems with FroYo so as far as I'm concerned, I'm good.
gookia2000 said:
Beach Head, thanks for your reply. you have provided me with a glimmer of hope!!! the leaked tmobile froyo sbf is one i have not tried. I will certainly try to flash my defy with that once i have gotten it recognised by rsdlite.
I believe my phone is currently not being recognised by rsdlite due to insufficient battery. (cant confirm this, as all i see when i plug in the usb is a white light on my phone. but ever since i started this entire nightmare, i think i have attempted flashing at least 5 different sbf files and considerable battery has been drained.) I will try the Mcgyver battery fix next.
skateguitar, THERE IS HOPE!!! i havent confirmed it yet but i think we all got stuck cos we were trying to flash from a "non-downgradeable" 3.6.360 firmware. and rsdlite does not recognise our phones due to low battery (your phone was left with a white light on after flashing for 1 whole night.) SO... i propose this course of action: 1) perform the Mcgyver battery fix and try to get our phones recognised by rsdlite first. 2) once recognised, flash with the leaked tmobile froyo sbf.
Does anyone have any better suggestions before i plunge head first to save my phone?
Click to expand...
Click to collapse
Yes all i wanted to say was that you might have lost your downgradability and thats why phone does not boot. Simple thing is to flash the original sbf like what beachhead suggested. It definitely should work.
Sent from my MB525 using XDA App
Guess what, it works!!!
Deleted by user
Glad I could help you out!
Enjoy Froyo!
gookia2000 said:
OHMYGOODNESS!!! I LOVE YOU GUYS!!!
My Defy has been flashed with the t-mobile froyo leaked rom and IT WORKS!!! I was so mentally set with the idea that my defy has been bricked and I just threw $400 down the drain... NOW I AM SO HAPPY!!!
Anyway, just for your information, here is what I did:
- I first tried to get my defy recognised by rsdlite. I tried Beach Head's suggestion of pressing the power button while the led is on to no effect. I reckon that the battery has just been drained too low. So, i went ahead with the McGuyver battery fix.
- Alas, with the wires protruding precariously from my phone, rsdlite finally recognised my phone. I went to load the leaked t-mobile froyo rom and went ahead flashing it.
- And, guess what, IT WORKS!!!
Thank you all so much, especially beach head, for your help in this forum! I would have gone to the mobile store to get another phone if not for you guys!!!
Click to expand...
Click to collapse
I have the same problem, and will probably end up trying to flash the leaked Tmobile Rom.
Can you point me to where you downloaded this file? I think I found the thread, but I want to be sure
Deleted by user
got it! Thanks!
Now to ultimately decide if I want to flash this, since it's non-downgradeable
To update, flashing this rom has fixed my phone. Yay! Thanks!
I wonder if it was the 3.66x update that Moto pushed out - this phone was brand new, bought in Dec 2010, no other hacking done on it...
Beach_Head said:
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
Click to expand...
Click to collapse
How did you get it to show up in rsd
I'm not working on my phone because i think i messed it up enough, so i took it to a store that fixes phones. The guy told me that he had my battery on a universal charger and he still cant get rsd lite to recognize it... What can i do
Another Happy Defy User
Just to confirm, I was seeing the same thing gookia2000 was seeing. Here was my resolution in case it helps anyone:
I was able to get mine working by flashing the US Stock Froyo build as explained in this thread: http://forum.xda-developers.com/showthread.php?t=938708&highlight=bricked&page=2
I found this thread to be super helpful as it helped me confirm my suspicion that the battery being low was the issue: http://forum.xda-developers.com/wik...#Recover_Nearly_Bricked_Phone_.28hopefully.29
Thankfully my wife has the same phone so I borrowed her battery, otherwise I would have been going McGyver style per Sorensiim (da' man) as seen here:
http://forum.xda-developers.com/showthread.php?t=892026
So happy this nightmare is over - running Froyo is a little bonus love!
Thanks to all @ XDA!!!
-Dave
Defy wont come on get a white light!
im having the same prob i did the the steps but its not working is there anything else i can do or is there a video of the proceeder
I have the same issue with a Telstra defy. I can get RSD to recognise something is connected but it isnt listed as MB525 like before but as "S Flash OMAP3630" I have flashed various SBF files but nothing is changing.

[Q] Looks like I hard bricked it...

My full apologies in advance if there has been a similar thread, I've honestly been looking for the past couple of hours. If there is one and I've just missed it, feel free to open-fire on me.
I have an AT&T Atrix running on 2.3.4 Gingerbread; rooted and unlocked bootloader with the Alien 4 ROM and the Alien 4 Theme. I'm really new to rooting and have only been rooted for about a week now. Today though, I was going to trade my Atrix for an HTC Inspire. I used to have one, switched to the Atrix, and I've come to the conclusion that I prefer the Inspire. While wiping my personal info off of my phone, I did something I clearly shouldn't have though, and everything went downhill from there. Not really thinking, I had already wiped my SD card (which had the Alien ROM), and I still needed to clear off the phone itself, so I figured it'd be okay to just go to the Settings and wipe my phone through the Privacy option. When it booted back up I saw that almost all apps (including necessary ones like Phone and Browser, among others) were gone. I didn't think it'd be a problem and I could just download them again through the Market, but my Settings app was also gone, so I couldn't configure a Wifi connection. I couldn't configure anything. My SIM card didn't work either, nor did the SIM of the person I had met to trade for an Inspire.
When I got home, I went through the different options in Android Recovery on my phone... Still nothing. So I fired up RSDLite on the Windows 7 comp in the computer room, downloaded the 1.5.2 Atrix SBF from here to try and flash it back to the stock Atrix ROM, and clicked Start. My phone rebooted once or twice and it looked fine, but then RSD said that the flash had failed. Now whenever I try to turn my phone on, it stays at the big M logo with "Dual Core Technology" underneath (it doesn't even change to the pulsing M). I haven't been able to boot it up since... Sorry for the novel, but it'd be really greatly appreciated if someone could help me out here. Thanks for your time.
hayatohuseman said:
My full apologies in advance if there has been a similar thread, I've honestly been looking for the past couple of hours. If there is one and I've just missed it, feel free to open-fire on me.
I have an AT&T Atrix running on 2.3.4 Gingerbread; rooted and unlocked bootloader with the Alien 4 ROM and the Alien 4 Theme. I'm really new to rooting and have only been rooted for about a week now. Today though, I was going to trade my Atrix for an HTC Inspire. I used to have one, switched to the Atrix, and I've come to the conclusion that I prefer the Inspire. While wiping my personal info off of my phone, I did something I clearly shouldn't have though, and everything went downhill from there. Not really thinking, I had already wiped my SD card (which had the Alien ROM), and I still needed to clear off the phone itself, so I figured it'd be okay to just go to the Settings and wipe my phone through the Privacy option. When it booted back up I saw that almost all apps (including necessary ones like Phone and Browser, among others) were gone. I didn't think it'd be a problem and I could just download them again through the Market, but my Settings app was also gone, so I couldn't configure a Wifi connection. I couldn't configure anything. My SIM card didn't work either, nor did the SIM of the person I had met to trade for an Inspire.
When I got home, I went through the different options in Android Recovery on my phone... Still nothing. So I fired up RSDLite on the Windows 7 comp in the computer room, downloaded the 1.5.2 Atrix SBF from here to try and flash it back to the stock Atrix ROM, and clicked Start. My phone rebooted once or twice and it looked fine, but then RSD said that the flash had failed. Now whenever I try to turn my phone on, it stays at the big M logo with "Dual Core Technology" underneath (it doesn't even change to the pulsing M). I haven't been able to boot it up since... Sorry for the novel, but it'd be really greatly appreciated if someone could help me out here. Thanks for your time.
Click to expand...
Click to collapse
That definetly doesn't sound like a hard brick. Use romracers recovery and try to flash a fruitcake http://forum.xda-developers.com/showthread.php?t=1163009 which are much safer then sbfs.
By the way theres no need to apologize when posting in the "correct" forum .General or QandA is where this thread belongs. if this were development though then you'd be in a world of ****! LOL
if you are on big M (without any "failed to boot" ) you're soft bricked,
try to power on button+ volume down button...
if says "fastboot" then just volume up,
download the .img files in the fruitcakes section and follow the fastboot mode instructions...
you'll get back your phone.
read carefully the instruction where to put the files in your windows 7 user directory etc etc, 90% of the problem is because people don't understand where to place executables and run them
hope it helps
Thank you guys so much!! The solution was actually even simpler than what you both suggested; all I had to do was flash to 2.3.4 with moto-fastboot. I had never used fastboot before, so it took me forever to figure it out, but I finally got it and my Atrix is back to the way it came. Thanks again, you two. Cheers!
hayatohuseman said:
Thank you guys so much!! The solution was actually even simpler than what you both suggested; all I had to do was flash to 2.3.4 with moto-fastboot. I had never used fastboot before, so it took me forever to figure it out, but I finally got it and my Atrix is back to the way it came. Thanks again, you two. Cheers!
Click to expand...
Click to collapse
Kudos for doing some research and figuring out how to resolve the problem. Not enough of that going on. Doesn't it feel like more of an accomplishment?!
KeRmiT80 said:
follow the fastboot mode instructions...
you'll get back your phone.
Click to expand...
Click to collapse
hayatohuseman said:
all I had to do was flash to 2.3.4 with moto-fastboot
Click to expand...
Click to collapse
* 10chars

[GUIDE] "Unbrick" (no boot, no adb, no sbf_flash, no access, no nothing)

Good morning, Motorola Milestone 2 Users.
Today I will tell you something I've been through while trying to install a new ROM.
First of all, I've used RSD Lite v4.9 to flash the 2.2 version of android on an already 2.3 MS2, which made me has the impression I've bricked the phone.
I was flashing the 2.2 with the RSD and then suddenly the phone stopped working and the progress on the software asked me to power up manually the phone, which was impossible.
I removed the battery and have put it again, but for my desperation, nothing.
This will be basically a manual to:
http://forum.xda-developers.com/showthread.php?t=1420276
If your phone don't boot or show anything, but it brights the charger light on the left of the phone, it means it's already on bootloader screen, so, just put a usb data cable and plug it in your computer and run RSD and put the newest .sbf file and flash it.
Is your phone working ok now though?
If you don;t mind this shameless plug of my own thread, some more information can be found here
It contains information about what custom roms you can use other such things, and hopefully I have included how to fix any other problems you might run into. Should you look it over and think im missing something just let me know and I'll add it in with due thanks
Holy mother DreadPirateDan, I am really sorry, I tried to help, I looked for it over and over and didn't find this post of yours, I am really ashamed, really sorry.
If and admin could, please delete this post.
And again, sorry mate.
lol it's all good you encouraged me to reformat my thread... Looking back at it I decided it was pretty sucky and confusing, Hopefully it's more straight forward now.
It's not like it's taken off or anything so it's quite understandable that people might not know of it's existence .

A500 UNBRICK/RECOVERY Major Assistance Needed

OMG I am SUCH AN IDIOT!! And now I've gotten myself into a real jam here.
-Acer A500, official ICS 4.0.3.
-Broken Rotation Swtich
-Missing MICROSD Card but can get a blank one.
Little old smart me tried to be cute and change the build.prop in attempt to get a non-supported app to work....I made a backup of the original INTERNALLY....didnt know what the hell I was really doing, rebooted the tablet and now I get a blank black screen after the acer logo. Tried to go into recovery but since I have no SD card I get the dead Android with a Red Exclamation point.
Can't try factory reset method because the rotation switch is broken!!
I just wanna get this thing back to WORKING condition.
I did some research and tried doing all of these things but couldn't proceed since I do not have the CUID and get find a way to get it in this situation since my sis-in-law came to visit a few days ago and she found this tablet.
I need some serious help to get this working ASAP.
sagemaster2000 said:
OMG I am SUCH AN IDIOT!! And now I've gotten myself into a real jam here.
-Acer A500, official ICS 4.0.3.
-Broken Rotation Swtich
-Missing MICROSD Card but can get a blank one.
Little old smart me tried to be cute and change the build.prop in attempt to get a non-supported app to work....I made a backup of the original INTERNALLY....didnt know what the hell I was really doing, rebooted the tablet and now I get a blank black screen after the acer logo. Tried to go into recovery but since I have no SD card I get the dead Android with a Red Exclamation point.
Can't try factory reset method because the rotation switch is broken!!
I just wanna get this thing back to WORKING condition.
I did some research and tried doing all of these things but couldn't proceed since I do not have the CUID and get find a way to get it in this situation since my sis-in-law came to visit a few days ago and she found this tablet.
I need some serious help to get this working ASAP.
Click to expand...
Click to collapse
You probably don't want to hear this, but I think that without the CUID, you are hosed. I might be wrong and that is only necessary for unlocking the bootloader, but I know that I have read a ton of posts that mention you should write your CUID down and put it somewhere safe.
Thanks for the consideration. Being that all I did was change the build.prop and not end up with my situation by screwing up a ROM install or something along those lines, I was able to recover by downloading the latest update a D putting that update.zip onto a fresh sd card and booting into recovery.
Recovered with no issues and even no data loss!
Glad you got it worked out.

[Q] defy cant get to any bootloader at all

first off im not a noob at this kinda stuff ive rooted tablets and other phones before. so ive spent the past week or so every night for hrs searching around for an answer to my problems.
phone info
carrier:Straight Talk
MN: XT555C
AV:2.3.7
Base band vr: PCR
Kernel vr:Apps_2.6.38.6-perf
Build number:1_67D_1014
OK on to the proses i used:
first rooted phone with VROOT
pic 1(the pic with the Foreign letters)
gained root
pic2 (pic with root checker)
easy enough right
then tried 2int every vr of it witch said they installed just fine
but every time i would try to go in into the boot-loader nothing no blue light no auto boot loader screen just nothing.
so i searched for different kinda boot loaders witch lead me to twrp and only like two more
nothing couldn't get any of them to work on account of the fact that they needed a Boot-loader to install them.
then i decided i would try rsd lite
downloaded sbfs
http://sbf.droid-developers.org/umts_jordan/list.php
ive tried the first and last one not sure witch one is for my phone
when i hit VOL+ power i get this screen:
pic 3(white screen with blue letters)
and rsd reconised the phone but phone info came up mostly as
N/A and nothing would flash just kept giving me
error:failed flashing process. failed flashing process phone 0000 error sending ram to bootloader
then when i had the phone try to just boot normaly with rsd open i got this screen:
pic 4(black screen with white letters)
all things aside i have gained root but to no avail can i get a Boot-Loader to work. im just looking for some one to help shed some light on this matter and help me get off of Ginger Bread
jimbob60 said:
sorry about pic i cant post them
they are on my fb my only public album
my fackbook url:
/jacob.g.shaffer
first off im not a noob at this kinda stuff ive rooted tablets and other phones before. so ive spent the past week or so every night for hrs searching around for an answer to my problems.
phone info
carrier:Straight Talk
MN: XT555C
AV:2.3.7
Base band vr: PCR
Kernel vr:Apps_2.6.38.6-perf
Build number:1_67D_1014
OK on to the proses i used:
first rooted phone with VROOT
pic 1(the pic with the Foreign letters)
gained root
pic2 (pic with root checker)
easy enough right
then tried 2int every vr of it witch said they installed just fine
but every time i would try to go in into the boot-loader nothing no blue light no auto boot loader screen just nothing.
so i searched for different kinda boot loaders witch lead me to twrp and only like two more
nothing couldn't get any of them to work on account of the fact that they needed a Boot-loader to install them.
then i decided i would try rsd lite
downloaded sbfs
when i hit VOL+ power i get this screen:
pic 3(white screen with blue letters)
and rsd reconised the phone but phone info came up mostly as
N/A and nothing would flash just kept giving me
error:failed flashing process. failed flashing process phone 0000 error sending ram
then when i had the phone try to just boot normaly with rsd open i got this screen:
pic 4(black screen with white letters)
all things aside i have gained root but to no avail can i get a Boot-Loader to work. im just looking for some one to help shed some light on this matter and help me get off of Ginger Bread
Click to expand...
Click to collapse
Have you tried this: http://forum.xda-developers.com/showthread.php?t=1743764
It worked for me.
i have now tried that and it was useful as far as the commands in the bat file but still nothing i did worked
i unrooted it the wipe cash and factory restore the Zerg Exploit did not work it would not root it so i used the commands to install bootloader it worked with no errors my led turned green to show success but still no blue light or Boot-loader. even when i use
E:\android\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
$ su
su
# reboot boot-loader
reboot boot-loader
it just reboots normally
any one else have some info?
so i still cant get a bootloader to come up ive been at this for a while and am still stumped i gain root and su but no custom boot loader just the stock one.
Root, install 2ndinit, install CM10, install CM10.2, install update-recovery.zip, REBOOT (without any wipe), install CM11 and GApps.
^
so this is just so people can see where im at in the chain of things here. im at the install 2ndinit
nother update so i desided i needed to push the files from bootmenu.tar.gz onto my system and see if it changed anything(also did the same for twrp and a few vrs of other bootloaders)
so i went and got http://forum.xda-developers.com/showthread.php?t=1687590
witch worked well and after i used the program to send the files where they need to be and tryed to reboot into bootmenu the phone still just restarted normally.so now the files are where they need to be adn it should let me into the bootloader but no im at a loss i dont understand how sompthing so simple could turn out to be like this. every one else can get it and ive followed like every set of direction i could find on this site over and over agen then i started experimenting with it and still nothing no matter how the files get there still no bootloader all i want is to be able to install JB and get the hell off of GB. and its not like im getting any help from this post i hope a dev can come by here soon and help me shed some light on things. untill then ill keep updating the post
jimbob60 said:
nother update so i desided i needed to push the files from bootmenu.tar.gz onto my system and see if it changed anything(also did the same for twrp and a few vrs of other bootloaders)
so i went and got http://forum.xda-developers.com/showthread.php?t=1687590
witch worked well and after i used the program to send the files where they need to be and tryed to reboot into bootmenu the phone still just restarted normally.so now the files are where they need to be adn it should let me into the bootloader but no im at a loss i dont understand how sompthing so simple could turn out to be like this. every one else can get it and ive followed like every set of direction i could find on this site over and over agen then i started experimenting with it and still nothing no matter how the files get there still no bootloader all i want is to be able to install JB and get the hell off of GB. and its not like im getting any help from this post i hope a dev can come by here soon and help me shed some light on things. untill then ill keep updating the post
Click to expand...
Click to collapse
I don't think the XT555c has a JB or even a ICS ROM. You can debloat GB and stay on it.
Sent from my Nexus 7 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2392187
http://forum.xda-developers.com/showthread.php?t=1216982
http://forum.xda-developers.com/showthread.php?t=1768702
http://forum.xda-developers.com/showthread.php?t=1032212
ive read thru a few threads other than those also and other people with the same mn and build have done it......
thats from my understanding that they wer able to get a boot-loader to work witch i can not get into a bootloader at all.and RSD wont flash anything to the phone evern tho ive used diffrent vr of rsd and the moto drivers.
so am i to assume that it just cant b done? that i could understand but other people with this phone/67d have done it and ive sent them pms but no reply same with some of the devs here who have helped others get this phone going so i guess im at a loss with this straight talk phone at least with installing a custom boot-loader/ROM.at least the phone works.....just outdated.screw you motorola
just a reply
@jimbob it my feelings that the "USA Moto defy xt555c, Straighttalk" does not have a blue LED built in. There is no evidence of it other than i have never seen one during the last year or so of having the phone (yes i do a lot of bluetooth stuff). Also to shed some light on your situation it is my understanding that 67d firmware has patched an exploit with the older bootloader and now has been upgraded to bl7. if this is your bl ver number then it is slim you will find the answer to your problems here. the only option i can come up with is to get or make fixed sbf for the device and flash/ downgrade. fixing the sbf only lies to the phone and tells it you have a higher ver android than you really do.... go figure motorola would be good at burning bridges! LMAO
thanks for replying. not to sure how to make a fixed sbf and the ones i found would not work because i couldn't get the program to flash anything to the phone. but then agen i never made a custom one

Categories

Resources