Bricked my friends AT&T Backflip. Need help!

[jessexcruz]

So last week,I was trying to root my friends backflip (which had the latest 2.1 stock rom). When I was finally able to root it, I flashed the j_r0dd recovery and then tried to reboot to it to recovery. I then came across this blue screen that said something like **Security on, fastboot dsiabled** and was unable to boot normally.

Afterwards, I tried flashing the device back to stock firmware using this method: [Instructions] How to flash your phone
and
Backflip Brick Fix for flashing back to 1.5 from official 2.1

But I still can't recover the device.

Now i'm in a bigger mess.. the device only turns on every 30 minutes and goes directly to the USBINIT screen with some sort of error like, BOOT error.. USB INIT, RCHP failed.. USBINIT..

I keep trying to flash the SBF files but I always get this error:

04/09/11 04:52:24  The FlashLog key is turned off.
04/09/11 04:52:25  Multi upgrade started for 1 phones
04/09/11 04:52:25  [Device ID: 0] Flashing phone.
04/09/11 04:53:00  ERROR: Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE002000B Address: 0x17FE800 Command: BIN - on device ID 0.
04/09/11 04:53:00  ERROR: Flash failure: Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE002000B Address: 0x17FE800 Command: BIN (Error Code: e002000b),
Detailed Error Details: Direction of the Error=3000, Command Value=300000, Code Group Number=2 - on device ID 0.
04/09/11 04:53:00  [Device ID: 0] Phone[0000]: Error flashing subscriber unit. Device API Error: 0xE002000B Address: 0x17FE800 Command: BIN
04/09/11 04:53:00  Multi upgrade finished.
04/09/11 05:38:35  --------------------------------------------------------------------------------
04/09/11 05:38:35  New Log Started For Software Download.
04/09/11 05:38:40  000011cc	Phone.cpp	433	0	ERROR	Generic failure when sending command.
04/09/11 05:38:40  000011cc	Phone.cpp	1524	0	ERROR	GetPhoneID failed: ERROR.
04/09/11 05:38:51  The FlashLog key is turned off.
04/09/11 05:38:55  Multi upgrade started for 1 phones
04/09/11 05:38:55  [Device ID: 0] Flashing phone.
04/09/11 05:39:25  ERROR: Phone[0000]: Error sending JUMP command Device API Error: 0xE0030040 Address: 0xB00000 Command: JUMP - on device ID 0.
04/09/11 05:39:25  ERROR: Flash failure: Phone[0000]: Error sending JUMP command Device API Error: 0xE0030040 Address: 0xB00000 Command: JUMP (Error Code: e0030040),
Detailed Error Details: Direction of the Error=2000, Command Value=500000, Code Group Number=No Codegroup - on device ID 0.
04/09/11 05:39:25  [Device ID: 0] Phone[0000]: Error sending JUMP command Device API Error: 0xE0030040 Address: 0xB00000 Command: JUMP
04/09/11 05:39:26  Multi upgrade finished.
04/09/11 05:39:26  000011cc	Phone.cpp	433	0	ERROR	Generic failure when sending command.
04/09/11 05:39:26  000011cc	Phone.cpp	1524	0	ERROR	GetPhoneID failed: ERROR.
04/09/11 05:40:05  The FlashLog key is turned off.
04/09/11 05:40:12  Multi upgrade started for 1 phones
04/09/11 05:40:12  [Device ID: 0] Flashing phone.
04/09/11 05:42:42  ERROR: Phone[0000]: Error getting subscriber unit information. Device API Error: 0xE0030007 Command: RQHW - on device ID 0.
04/09/11 05:42:42  ERROR: Flash failure: Phone[0000]: Error getting subscriber unit information. Device API Error: 0xE0030007 Command: RQHW (Error Code: e0030007),
Detailed Error Details: Direction of the Error=1000, Command Value=800000, Code Group Number=No Codegroup - on device ID 0.
04/09/11 05:42:42  [Device ID: 0] Phone[0000]: Error getting subscriber unit information. Device API Error: 0xE0030007 Command: RQHW
04/09/11 05:42:42  Multi upgrade finished.

Is there anyone out there that knows how to fix this issue?

This isn't my phone.. so I had to let my friend my borrow my old phone until i figured out how to fix it

[phoenixsong6]

I actually don't know what is going on, but here are some ideas to try/questions I have:

1) You mentioned that the phone automatically started in USB Init, have you tried pulling the battery and intentionally booting into USB Init? (Probably won't make a difference)
2) Since the phone had the official 2.1 from ATT, the firmware you use MUST have a secure version of 11 or higher. (In the US section of the firmware, that leaves you with only one firmware option)
3) Did any messages pop up when you tried to flash the recovery.img? (The flash_image command has no output, so anything that showed up on the screen is an anomaly)
4) Do you have the latest version of the Motorola USB Drivers?

I'm honestly just nitpicking to see if something was missed...

[bconover93]

i've had it bricked before and flashed the 2.1 update which unrooted my phone so i had to that all over again. :/ but it all ended up ok. as for your situation--no clue what's going on. good luck!!

[sublime1184]

moved to general section

[Double0EK]

Have RSD Lite Running on your pc and put the phone in the Blue Fastboot USB INIT Screen for a few minutes until RSD Recognizes....it can take as long as 30 mins or more.
Be sure you have the latest firmware version available and already loaded in RSD...once it recognizes it Start the flash.



Sent from my MB200, on CRACK, Using Tapatalk!

[mangusta86]

i've had it bricked before and flashed the 2.1 update which unrooted my phone so i had to that all over again. :/ but it all ended up ok. as for your situation--no clue what's going on. good luck!!

Bricked backflip as well... I installed from rom manager the clockwork recovery, and it said it was successful, and I press "reboot in recovery mode"... great idea, now i'm stuck with the blue screen and RSD doesnt recognise the device... any ideas???

[phoenixsong6]

In general I like to point people to this link: [HOW-TO] Flash with RSD Lite
But since you tried RSD Lite, a question.
Have you installed the latest USB Drivers?
Other than that, I can only suggest following the directions very closely. Good luck, this is my best I have.

[mangusta86]

In general I like to point people to this link: [HOW-TO] Flash with RSD Lite
But since you tried RSD Lite, a question.
Have you installed the latest USB Drivers?
Other than that, I can only suggest following the directions very closely. Good luck, this is my best I have.

i have surely the latest motorola driver... the blue screen says:
usb FastBoot:v0.5
machine id: motus 0aa0
Build date: feb 03 2010 11:18:51

serial number ....
**security on, fastboot disabled**

and now the battery is over.... what can i do?

[Joshp9699]

i have surely the latest motorola driver... the blue screen says:
usb FastBoot:v0.5
machine id: motus 0aa0
Build date: feb 03 2010 11:18:51

serial number ....
**security on, fastboot disabled**

and now the battery is over.... what can i do?

well there's your problem. your on the wrong blue screen. to access the one for RSD, turn on your BF while holding J and D on the keyboard

[mangusta86]

can somebody tell me the procedure from ubuntu/debian?? rsd doesnt work...

[Joshp9699]

can somebody tell me the procedure from ubuntu/debian?? rsd doesnt work...

RSD only works in windows. Sorry dude.

[mangusta86]

well there's your problem. your on the wrong blue screen. to access the one for RSD, turn on your BF while holding J and D on the keyboard

lol... i feel very stupid... fixed!!! thanks

[Joshp9699]

lol... i feel very stupid... fixed!!! thanks

lol, glad you got it working man.

[jessexcruz]

I actually don't know what is going on, but here are some ideas to try/questions I have:

1) You mentioned that the phone automatically started in USB Init, have you tried pulling the battery and intentionally booting into USB Init? (Probably won't make a difference)
2) Since the phone had the official 2.1 from ATT, the firmware you use MUST have a secure version of 11 or higher. (In the US section of the firmware, that leaves you with only one firmware option)
3) Did any messages pop up when you tried to flash the recovery.img? (The flash_image command has no output, so anything that showed up on the screen is an anomaly)
4) Do you have the latest version of the Motorola USB Drivers?

I'm honestly just nitpicking to see if something was missed...

1. Yes, I can't figure out a way to get the device to boot up at all. I tried everything.. removing the battery, putting it back, pressing and holding d+j with and without the battery.

2. I have tried all ATT firmwares.. none worked.. i'm going to retry "C:\att-motus-endive-3.0.1390-secure-production-supermonster-customer.sbf"

3. When I was trying to flash the recovery.img, I kept getting something similar to this:

flash_image recovery /sdcard/recovery.img
mtd: not writing bad block at 0x00000000
mtd: not writing bad block at 0x00020000
mtd: not writing bad block at 0x00040000
mtd: not writing bad block at 0x00060000
mtd: not writing bad block at 0x00080000
mtd: not writing bad block at 0x000a0000
mtd: not writing bad block at 0x000c0000
mtd: not writing bad block at 0x000e0000
mtd: not writing bad block at 0x00100000
mtd: not writing bad block at 0x00120000
mtd: not writing bad block at 0x00140000
mtd: not writing bad block at 0x00160000
mtd: not writing bad block at 0x00180000
error writing recovery: No space left on device

4. Yes, I have "Motorola_End_User_Driver_Installation_5.0.0_32bit .msi"


I have RSD Lite 4.5.7 and it recognizes my device. Everytime I try to flash the sbf file, I get a "failed".

Currently, the device boots up automatically after being plugged in to my comp for like 30 min. It goes directly to the USB Init screen and it says, "RCHD failed. Bootloader USB INIT"

Anyone have some ideas?

Thanks in advance.

[jessexcruz]

So I just tried flashing "C:\att-motus-endive-3.0.1390-secure-production-supermonster-customer.sbf" but failed...

Here's what happened..
after 30 min or so of waiting, the phone finally turned on. It said on the screen ""RCHD failed. Bootloader USB INIT", but RSD Lite was able to detect the backflip. So I selected the SBF file and clicked start
1.png


During the second phase of the flashing, at around 14% the flashing failed. On the phone, it said "Flashing error..."
2.png

Below you'll see the entire message in RSD Lite
3.png


any ideas on what could be wrong?