Database Users

Recovery mode issues

Hi guys!
I had root my htc hero a month ago then i tried few rom's to see how they are. My phone is locked for Orange UK. Everything was ok. Then i had updated the new ROM from htc website (via RUU file). The phone working fine, but now i can't go into recovery mode. If i reboot into recovery mode i have a white screen with a triangle and a phone sign. Pressing Home+Power again i have acces to 3 options:reboot system now, apply sdcard:update.zip, and wipe data/factory reset but only reboot working. Also i have an error on the same screen: E:Can't open /cache/recovery/command
Trying to downgrade using an older version of RUU i got an error: on phone-Checking customer ID. Upgrade failed; on the computer: Customer ID error.
Everything else working fine.
What can i do?
Thank you.

emilio33 said:
... Then i had updated the new ROM from htc website (via RUU file). The phone working fine, but now i can't go into recovery mode....
Click to expand...
Click to collapse
Which RUU exactly?.... Please do not say the new 2.1?!

As long as it isn't the 2.1 update from a few days ago,... Just follow BTDAGs guide in my signature. You will probably need to downgrade using the goldcard method. But start at the top and you should be fine.

No, is not 2.1update. I want to update to the new 2.1 but can't do because of that issue.
-------------------------------------
Sent via the XDA Tapatalk App

Thanks 'ddotpatel' . I will try to follow that guide. Hopefully will work.
-------------------------------------
Sent via the XDA Tapatalk App

The RUU file version installed is 2.73.61.66 for Orange. Could be a problem?
Thanks.

ddotpatel said:
As long as it isn't the 2.1 update from a few days ago,... Just follow BTDAGs guide in my signature. You will probably need to downgrade using the goldcard method. But start at the top and you should be fine.
Click to expand...
Click to collapse
Followed BTDAG guide with no succes.
On first method with flashrec i've got an error: Backup FAILED: Could not run command.
Second option can't use because i don't have full access to recovery mode
Last option (goldcard), i've got an error when use: cat /sys/class/mmc_host/mmc1/mmc1:*/cid
saying: cat/sys/class/mmc_host/mmc1/mmc1:*/cid not found.
What else i can do? Please guys...
Thank you.

Have you set up the SDK correctly? ... Do you see anything when doing:
cd c:\android\tools\
adb devices
???????

Help Please
I have the same problem.
Tried everything, can't flash new recovery img using apk flasher, can't try the goldcard method cause I get "adb access denied" even though "adb devices" shows my phone. Tried using Droid Explorer to flash the new img or update but that didn't work too. Formatted my sd card a few times using the phone & my OS (when it was mounted and acted as disk on key). I also reinstalled the RUU that caused it a few time to see maybe I did something wrong but nothing (I too had a rooted phone and installed the 2.73 Orange UK root).
What else can I do? I feel like it has something to do with my SD card but I don't know how else to format it. Even on Droid Explorer it doesn't show me any of the folders that are in there when I'm connected (like tmp,rosiescrl, footprints).
Help

Tried to reinstall corect drivers for HTC but in device manager show 'drivers are up to date', so no change yet. Any other ideea?

tried to reinstall RUU file 2.73.61.66. Was working fine, then i tried RUU 2.73.405.5 . No chance. It said 'customer ID error'. Recovery mode still not working.
Help guys.

Well, of course it won't be working. Updating with official rom completely replaces everything on your phone including custom boot. And, of course, you won't be able to install .405.5 since it's lower version than your firmware. You have to downgrade to .405.5 using goldcard and then repeat the root and custom recovery install procedure.

Droid 2 new ota update

Here is the link to the new update to install just rename to update.zip place on the root of your sdcard then reboot recovery and install update.zip
http://www.4shared.com/file/ov_2h3JM/Blur_Version2320A955VerizonenU.html

Why would someone need to download this, shouldn't everyone be able to update over the air.
FYI really like 2.3 runs very nice on droid2

To answer your question, I would. I recently left verizon and now I cannot get the OTA update. I still use my Droid 2 for android development. I just don't use it for a phone.
That said. I can't use the above update. I SBFed my phone back to stock Froyo System version 2.3.20, installed z4root to load clockworkmod Droid 2 recovery, and finally attempted to flash the above file from the SD card. I get the following error:
assert failed: getprop("ro.product.device") == "cdma_droid2" || getprop("ro.build.product") == "cdma_droid2"
blah blah blah
(Status 7)
From the failed assertions I'm assuming this update doesn't recognize my phone as a Droid 2 and refuses to install the update. Does anyone know why that might be? Like I said I restored to stock before attempting this.

Wait a second. The file linked is called Blur_Version.2.3.20.A955.Verizon. That's the stock Froyo version. Is it called that because you need to be on that version or is this just an older file? I'm confused. Is this or isn't this the just released Gingerbread update?

It's an oddly named file, but the last time I saw that one linked it was the OTA. I still feel one is better off SBFing to stock and downloading it that way.

What's going on, I was following the steps on theunlockr but when I tried to extract the OG firmware my laptop said it was probably damaged, any way I can get the firmware somewhere else? I am running on Fission right now and want to go back to stock so I can scoop this update, it looks pretty nice. Please help me out if you can, thank you.

If you want to go back to stock to force the update the right way, the above file won't help you.
1. Get RSD Lite http://www.multiupload.com/HL0ZAL9GK8
2. Get Moto Drivers http://dl.dropbox.com/u/7632904/USB_Drivers_bit_4.7.1.zip
3. Get Froyo SBF http://bit.ly/dir7fq
Install the Moto Drivers on your pc, then boot into your bootloader and connect via usb. Then run RSD and load the SBF file. Once you complete that, reboot the phone and go to settings > phone info > check for updates. The new GB should be waiting for you, all official like.

Good looking out fam, will check in when finished!

Despite the odd name it is the correct file. But do not use CWM or bootstrap to flash it! Rename it to update.zip on root of sd card then use Stock recovery to flash it.
Sent from my DROID2 using XDA App

You're right it worked! I'm finally gingerbreaded. Thanks so much everyone.

Hello again, so my phone is just stuck on the Droid loading screen (Droid followed by the red symbol) I have no idea what to do although I followed the steps stated above.
**EDIT**
So I was able to fix this problem by wiping the cache as well as my data, thank you all!

idefiler6 said:
If you want to go back to stock to force the update the right way, the above file won't help you.
1. Get RSD Lite
2. Get Moto Drivers
3. Get Froyo SBF
Install the Moto Drivers on your pc, then boot into your bootloader and connect via usb. Then run RSD and load the SBF file. Once you complete that, reboot the phone and go to settings > phone info > check for updates. The new GB should be waiting for you, all official like.
Click to expand...
Click to collapse
I tried this exactly as stated and I cant get me droid 2 to be seen in the RSD. I get a drive letter when I reboot to recovery but nothing shows in RSD. Any ideas? I tried wiping data and cache and did a factory reset still nothing.
Back to a rom manager backup from yesterday atm.

Make sure your phone is in PC Mode (and possibly Debugging Mode) so RSD can recognize it.

JDunc said:
Make sure your phone is in PC Mode (and possibly Debugging Mode) so RSD can recognize it.
Click to expand...
Click to collapse
Thanks I made sure I have debugging on and in pc mode. I see Droid 2 when I have my phone powered on but when I reboot in recovery just a drive letter and nothing in RSD.
I just saw this
D2user said:
Despite the odd name it is the correct file. But do not use CWM or bootstrap to flash it! Rename it to update.zip on root of sd card then use Stock recovery to flash it.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Must have missed it the first time I read the thread I will try to install it as update.zip through the standard recovery and see if that works.

Ok I was able to get this on my phone with RSD the trick is to have your phone in PC mode and NOT to reboot it yourself the program will do it automatically. I got my phone updated but now it wont even give me the option to download the update OTA.

Yea I could've told you not to manually reboot. So you did a SBF to 2.3.2 and went into Settings > About > and System Updates and got nothing?

Correct I redid the sbf twice more to make sure it took.. when I go to settings > about > and system updates its greyed out.
UPDATE: I dededeee it, forgot to reactivate my phone after sbf the 3rd time. trying the OTA now

Ok phone is upgraded and rerooted.
1. sbf with RSD 3 times till it took
2. upgrade with OTA
3. rerooted with One Button Root
4. replaced progs with titanium
phone is fast right now, lovin it.

Glad you FINALLY got it working. Try out CM7 for GB. Do a backup before doing so and see if you like it. If not you can always restore back.

I think I may have done something wrong. My phone works but it restarts randomly, is there a way I can get it to stop this? Should I start from scratch or just get a different ROM?

Bricked Atrix can't restore

Ok hello all, I have a bricked atrix here (new user) and cannot restore the previous firmware I backed up.
What I did step by step is:
I followed this guide to unlock phone and install CWM recovery mod. ( I backed up my factory "firmware" )
After that I installed Neutrino ROM 2.2 from here but it was a bit buggy and I wanna revert to my factory settings.
When I try to restore the old firmware checking md5 and bootloader restore ok, system gives me a message: "Error while restoring /system"
At some point I also installed "recovery-en-goapk-0630-1029" which seems just another recovery tool (dont know if this caused the issue)
I also have RSD Lite and the original ATT's 4.5.91 .sbf file but that cant work as well. Once I hit RSD mode on my phone and hit start on pc, phone says after a couple of mins: sec_exception: febe, 35, 35 and then doesnt progress anymore.
By the way my phone is European and it came with 2.3.4 preinstalled out of the box, I just wanna revert it back! please help!

what's that "sec_exception" about? I always get this when I try to RSD-mount the .sbf from ATT 2.3.4 Pudding
RSD tells me a short after: Failed Flashing Process. Phone [0000] . Phone did not re-enumerate after RAM-downloader was sent (0x703E); phone connected (Result FAIL)

First of all, I don't think you should be using an ATT sbf file with your European Atrix. Not a good idea; they are not the same.
Secondly, using a sbf and RSD is tricky business and should be avoided if possible.
If you want to return to stock I suggest using the tool in this thread:
http://forum.xda-developers.com/showthread.php?t=1421522
It is dead simple to use.

since I'm new to this (got some good pc experience tho) I wanna keep things clean and organized, so what can I do to clean previous installations , zips , rsd sbf mounting etc. As I see this, the phone's memory has 2 partitions, 1 for system and 1 for apps? Correct me if I'm wrong I'm just starting to get familiar with all this thing

If you follow the link above it will wipe everything on the phone and return it to stock. You will need to wipe your SD card yourself however.
Sent from my MB860 using XDA App

I had this with all recovery iv try I found out its because the system.ext3.tar backup is over 300mb the only the only. Way back from this was to ever flash a European gingerbread sdf or use fruitcake
the way I got past this was to deodx my rom so it is under 300mb

following the above link is the best method. please do so.

the method is perfect indeed, my phone is back to normal except that AT&T submenus and logo. Is there any program to view root folders and clean previous installations / garbage files? Any guides on what should be left off - uninstalled? (Neutrino 2.2 custom ROM had a file explorer that could navigate between root folders and sd storage
thanks again

i got the same issue but my phone doesnt turn on at all, just the led light in green then it goes off

have you tried to pull the battery off? Do you see the Motorola logo or just black screen?

[Q] Fastboot Reason: Sticky bit factory_fastboot?

I flashed the Eclipse ROM via safestrap and then restored the Eclipse ROM onto the stock ROM slot. For some stupid reason, instead of restoring the stock ROM slot before resetting the phone back to stock, I opted to use RSD Lite 6.1.4 and tried to flash the JB firmware (yes, I got into fastboot). When I tried to do this, the phone reboots past the Motorola M insignia, to the droid startup screen (with the flashing red light/circle), but does not get past the startup screen (yes, I gave it 30+ minutes to no avail). I also tried to reflash the JB firmware, but no matter what, I ended up stuck at the bootup screen.
For this reason, I tried to flash the ICS firmware instead (per instructions on XDA and other websites, I removed the lines in the XML file that had the word var, getvar, and oem). This did work! However, after RSD flashed the firmware, rather than restarting into the OS, the phone reboots into a black screen w/ the phrase "Fastboot Reason: Sticky bit factory_fastboot" at the very bottom. Anytime I try to restart the phone, it automatically boots into this screen. If I hold the volume up and down buttons, together w/ the power button, I am able to get back to the option to start normally.
When I tried to do the OTA JB update, the phone downloads the necessary files, but when the phone tries to reboot to install the OS update, it goes back into that black screen and does not install the update. Also, when I finally do get back into the OS, the phone then constantly reboots as if it were trying to install the OTA JB update.
Does anyone know what "Fastboot Reason: Sticky bit factory_fastboot" means? Also, if anyone knows how to "fix" this issue, I'd greatly appreciate it. If the fix requires command line work (like in this thread), I'd greatly appreciate if someone could walk me through it step-by-step, as I am not familiar w/ the command line process.
Thanks!
Edit 1: The next step I will try is to get root back on my phone, install Safestrap, and see whether I can flash a backup that I previously had.
Edit 2: In some threads for other Moto phones, there is some discussion regarding using ADB to fastboot/flash the stock ROM. Anyone know how this is different from using RSD? Also, can anyone walk me through HOW to ADB? I have zero knowledge in this regard.

Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app

skippid said:
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I attempted to reflash on multiple occasions, both using the stock ICS and the stock JB roms. I must have reflashed close to 10x at this point. In any case, no matter how often I have reflahsed (including after doing a factory reset from within the OS as well as from within recovery), I still get the error. The good news is that I was successfully able to flash the JB ROM and have the phone OS actually start up, whereas, a few days ago, it would be stuck at the red circle/eye thing.
Furthermore, I attempted the command fastboot flash system [system.img], and I got the error:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load '[system.img]': no error
I saved the system.img in both c:\android, as well as the internal SD card of the phone.
The other good news is that I am still able to use the phone if I get into the boot menu and ask the phone to boot normally. However, I am now unable to get root, and anytime I need to restart the phone, it gives me that error message.
I have also tried the command fastboot reboot bootloader but continue to get the same error message.

OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app

You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y

skippid said:
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Skippid, thanks for the suggestions. I tried your method as well. Went into recovery, selected to update from external SD (or something to that effect), selected the JB zip file, and let it flash that way. Unfortunately, I still received the same error message regarding the sticky bit factory_fastboot.

cellzealot said:
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
Click to expand...
Click to collapse
cellzealot, thank you for the link. I've downloaded the file that you linked to. Could you be so kind as to now give me a step-by-step on how to re-attempt the flashing process?

Quick update - I was able to get root back, installed safestrap, and flashed the nandroid that I had made back when I first flashed Eclipse. However, I am still having the same issue:
Whenever I restart the phone, I get the sticky bit factory_fastboot error. If I use the command fastboot continue, the phone boots up as normal; however, it would be great to not have to do this each and every time I reboot the phone. Any help would be greatly appreciated. Thanks!

More updates (still not fixed):
After getting root, I reflashed my nandroid, factory reset (both within the OS and in recovery), and then tried flashing both the ICS and JB stock ROMs. I tried flashing both using mfastboot, as well RSD Lite. The files flash successfully; however, whenever I restart the phone, I continue to get the stick bit factory_fastboot error.
Also, when I get into recovery, I try to flash via "update from external SD". When I do so, recovery simply restarts without flashing the stock ROM.

Here's my last update as to this issue:
After trying all of the methods that I could think of (RSD Lite, flashing via fastboot and mfastboot, flashing from external), the problem did not correct itself.
I brought my phone into a Verizon store, where they told me that they had never seen that problem before. They agreed to replace my phone pursuant to the one-year warranty (I received my phone in December), which I received today. I've again rooted my phone, but have opted to not screw around w/ safestrap and custom ROMs this time around, as I find the stock JB experience to actually be quite good.

Found the soultion!!!!!!
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful

Thank you!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!

Namanati said:
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Click to expand...
Click to collapse
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432

ATTACK said:
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Thanks, but that didn't come up when I googled AP Fastboot: flash failed, and since I didn't get it from rooting or unlocking my phone I didn't think to look for that.

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Oh my god dude thank you so much. That fixed my bootloader issue that was plaguing me for weeks
Thanks again!!!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thanks Man You really saved my razr.:good:

Edit : Sorry I asked stupid question!

Pierro29 said:
Edit : Sorry I asked stupid question!
Click to expand...
Click to collapse
there are no stupid questions if you question its because you dont know something and would like to fulfill the empty space where a reasonable answer could go. and s thanks for the solution to this error.

Okay, I have a "stupid"/newbie question. I flashed an image and I am getting the sticky boot thing. How to a get to a window to type the lines in?
Thanks!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Hey dude ! You save my life
Awesome trick

[Q] [DEFYMB525] Help my old "friend" please :)

Hi!
I know that that I am mentioning now very old device as Motorola Defy MB525 green lense.
I wanted to flash Cyanogenmod 10.1 again in my Defy. I did full wipe and removed some folders on SD card reffering to old apps.
And it seems I messed up with Clockworkmod Recovery folder on SD and I left myself without it. And I tried to reinstall it using official guide found here: wiki.cyanogenmod.org/w/Install_CM_for_jordan[/url]
But I did not unpack all the files, so the installation was not fulfilled and I got like empty Android boot menu 0.6.1 without possibility to boot an operating system or to do anything (got errors whatever I choose: E:Error in /system/bootmenu/script/recovery.sh)
I have read tons of online materials and forums, and I could only restore stock Defy ROM 2.3.4 using RSD lite.
And I didn't find solution how to reinstall the boot menu :crying: So that is why I am asking you for help.
I can run only Download Mode and this useless Android Boot Menu.
How to reinstall Android boot menu/install custom recovery back?
I like my Defy and I do not want to put it in the drawer yet
Thank you in advance!
Vixificent

The bootmenu is housed in the partition system.
All you have to do is flash the stock firmware, root with Framaroot (app) and install the bootmenu and recovery with 2nd init (app). After this simply download the rom and gapps, you do wipe cache, data, dalvik cache and flash it (first rom, then gapps).

cristiand391 said:
The bootmenu is housed in the partition system.
All you have to do is flash the stock firmware, root with Framaroot (app) and install the bootmenu and recovery with 2nd init (app). After this simply download the rom and gapps, you do wipe cache, data, dalvik cache and flash it (first rom, then gapps).
Click to expand...
Click to collapse
Thank you for your reply and suggestion! But the thing is that I cannot boot the device, so usage of any apk is not possible. When I run my Defy it goes directly to Android Boot menu 0.6.1, which is not installed properly (source files missing, eg. ".sh" files).
Should I try to root it via computer? Then, how to do it with only Download Mode available?
Any help would be appreciated!

Vixificent said:
Thank you for your reply and suggestion! But the thing is that I cannot boot the device, so usage of any apk is not possible
Click to expand...
Click to collapse
YOu can recover your device using an appropriate .sdf file and a program called RSD Lite. There are many how-tos on this - the first one I found was http://www.locslikes.com/motorola-defy/unbrick-and-restore-to-default-sbf/. You'll also find a number of tutorials on these forums.

robbak said:
YOu can recover your device using an appropriate .sdf file and a program called RSD Lite. There are many how-tos on this - the first one I found was http://www.locslikes.com/motorola-defy/unbrick-and-restore-to-default-sbf/. You'll also find a number of tutorials on these forums.
Click to expand...
Click to collapse
Quite a late answer, but the solution offered by robbak worked perfectly! Thank you!

Vixificent said:
Quite a late answer, but the solution offered by robbak worked perfectly! Thank you!
Click to expand...
Click to collapse
I have a similar issue. How did you do the fix you used? The SBF files don't seem to be on the site you were referred to anymore.
Years ago, my unmodified (not rooted) Defy (running Android 2.2.1) started to boot loop, so I eventually did a factory reset. That worked for a while, although certain apps were suddenly no longer compatible) and then suddenly the defy froze on the Moto logo (not even cycling to the Blur screen) and I could no longer get to the reset screen.
However I could still get to the bootloader, so I tried to use RDS lite.
I got one sbf to say it passed, but the phone did not reboot. (I could only find 2 SBF's for the US and only got one to work). Now RDS will detect whether the phone is on or off (and if on I'll get a white LED) and I can flash the sbf still, but otherwise the phone is completely bricked - can't get to reset OR bootloader screen.
When I plug the phone into the USB the white LED comes on, but I can't raise ANYTHING on the screen (reset screen or bootloader screen, holding down the volume up or down w/ the power button). However pressing the power button alone does cause the computer to recognize hardware is plugged in, or alternately disconnected. RSD tells me a device is connected, but the only info given is the bootloader version and AP ID info (whatever that is). However, when I load the SBF, the phone lights up and says SW update in progress...
RSD tells me the phone is being rebooted and has passed, but screen goes dark and all I see i the white LED again.
I tried these two SBFs:
T-Mobile_MB525_6.19.0_1FF.sbf
JORDN_U3_6_36_0_SIGNED_USAJRDNTMOB1B4B5DE1028_0R_J ORDANTMO_P022_HWp3_Service1FF.sbf
Only the 1st one works.
I am not that tech savy regarding Android, so i am looking for some help.
Thanks!

Hi DefyVictim,
I understand your concerns - the restore process is a little bit complicated, but still not impossible. There is a strange procedure how to get your phone connected in such a way that RSD lite sees it. In the link given by robbak there is a video which is an exactly described tutorial. Did you follow it carefully?
It goes like - you need to FIRST get the bootloader and then connect it to the PC. If I understood it right, you tried to get the bootloader after you got the phone connected - which did not work.
I had a similar issue but finally figured it out. Oh, and there was just another thing - the battery was too low, so I had to do quite risky McGyver method to charge the battery somehow (no charging when your phone is bricked!), but be careful, this is potentially dangerous. Nothing happend for me, because I charged my phone for a minimum of time (like half an hour) to get it working.
Check this thread if you face battery low warning:
https://forum.xda-developers.com/showthread.php?t=892026
I know now it is a pain to get a SBF file, but not sure if the T-mobile should be working unless your phone wasn't coming from T-mobile (?)