Database Develop

[Q] Bricked razr i help - locked bootloader

Well, this is embarrassing...
Current Status:
After a factory wipe and reinstalling (phone was OK after that) and an OTA, i managed to nearly brick my razr.
Currently every time i start it lands in fastboot (according to RSD Lite mode S) with the message fastboot reason: flash failed
after 'fastboot reboot-bootloader' i can operate the menus but only changing the console type and power off work, everything else results in a freeze.
Reflashing CFC_signed_customer_8.7.1I-110_IFW-DE-32_O2DE.xml.zip or 31 is not possible, since the OTA update apparently changed boot[1], gpt[2], and few other things to version "8.7.1I-110_IFW-DE-39" (the only thing i can flash from those are the recovery partitions and from the new one the gpt.bin)
Custom fastboot also does not work, since i'm not eligible according to Motorola ( tis was my first thought to check the custom boots & finally unlock the bl *g*)
I already ordered the factory adapter (hey, you never know, when you're gonna need one) & My Battery still has ~3.9v left, so i think a few tries should not hurt that much : >
TL;DR, Here's my question:
1) is it possible to patch the images provided in CFC_signed_customer_8.7.1I-110_IFW-DE-32_O2DE.xml.zip with the binary patches from Blur_Version.81.5.32002.XT890.O2.en.DE (updates to: 8.7.1I-110_IFW-DE-39_O2DE) and then maybe re-flash them to get my razr back from the near death zone?
2) should i hope and pray that Motorola announces JB upgrade and provides us with the full system images within the next few days?
3) can anyone find a full system image / full update with the version: 8.7.1I-110_IFW-DE-39_O2DE ?
References:
[1]: from update-script:
assert(apply_patch("MTD:boot:11534336:affeb8868070f6e6f061143b662e03b5bf65b2f3:11534336:19bf404a393a50d08a809affd45df5692e36e1db",
"-", 19bf404a393a50d08a809affd45df5692e36e1db, 11534336,
affeb8868070f6e6f061143b662e03b5bf65b2f3, package_extract_file("patch/boot.img.p")));
[2]: There is a brand new gpt.bin file within the OTA package
Cheerio,
Andy

The Problem is, without unlocking your Bootloader, you can't downgrade the Boot. img.
I would suggest you to grap the 39002 O2 Homemade Fastboot from Mattlgroff and flash only the Boot. img out of it. If you're an lucky guy, you're able to boot after that.
An Guy from my Home Forum tried the downgrade from 40002 today with an locked boot loader. RSD stopped @ point 1 GPT. His solution to boot his phone again was to flash the gpt.bin out of the 40002 OTA .zip.
So your only chance to get your phone back is to find flashable Images from the 39002 or 40002 because of the secure Level.
The easiest way is to unlock the device, I can downgrade to any FW. Or you'll have to wait for an updated Fastboot File to flash with RSD.

Hokay, apparently i had a typo yesterday when i tried to unlock the bootloader
But, now after trying the custom fastboot, i still land in fastboot with reason: Sticky bit fastboot
and all other menus still cause a freeze : /

If you're now unlocked, get an EU FW, regardless what Version. Open the XML with Notepad + or any similar Programm and delete ONLY the complete Line that contains MOTOBOOT. Save the XML and start RSD 6.1.4.
After that you should be good to go.

HSD-Pilot said:
If you're now unlocked, get an EU FW, regardless what Version. Open the XML with Notepad + or any similar Programm and delete ONLY the complete Line that contains MOTOBOOT. Save the XML and start RSD 6.1.4.
After that you should be good to go.
Click to expand...
Click to collapse
Purrrrfect, i owe you a bottle of wine.
Problem solved : >

Yeah, I'm glad I could help you out... RazR I Nr. 8 > Strike

bricked
hi guys the same thing happen to me i cant use rsd or fastboot because it says stigki bit fastboot.and in rsd it fails tryin to flash boot. im in mexyco i was using the new ota for 30006 that would be 40002. i just try to erASE THE BOOT LINE AND IT DIDNT WORKIT SAID THE SAME. HELP

So you're on 40002 and tried to flash back with RSD and your Bootloader is locked?
RSD failed on step one, right?

brick
Yes sir. Iwas on 40002 and with the rsd i was trying to go back to stock 30006,but on step 3 it says fail. Then i try to fastboot 40002 but it tqkes me again to fastboot and its freezes when i try to open a command like normal boot or recovery. I tried to eras the lineinside of motoboot where it says motoboot like the guy you just helped. But in my case still gets stuck on step 3in the rsd. So could you send me images of how erase the line of motoboot on text editor?? Im boot unlocked.

You mean 31006...Here ya go (unpack it > i can't attach an .xml)

Thank u sir. So i flash this on rsd,right? Vause i think that this is the one i have.the last digits are 31 on mine an starts cfc . Something else. I cant really tell u cause im at work but tonight i'll try ur method. Hope it works.

http://www.mediafire.com/download.php?ud9kowzk1uw2bcb
Use RSD 6.1.4 and copy the xml into the fastbootfolder. That's all...BTW: Charge your battery if possible or hope you got enough juice!

unbricked
thank you sir. everything like new!!!!!!!!
i"ll buy u some beers.

my razr i is workin now but i cant update the ota for the 31006 thats going to take me to 40002??

You're trying to update regular over the Phone or the manual over the leaked Update.zip? If you're trying it over the leaked zip, than beware. There's one if you're coming from 31006 and one from 32002.
Sent from my XT890

I go into software update, then i download the file, its like 50mb. Then it goes into rwcovery but the android dies and says aborted. So then i tried in recovery mode to flash zip blur ota 310006 but it happen the same. So i decided to stay in mis rom the 31006 from sept. But i was wondering if now i could flash in fastboot another rom like 40002? I saw u guy have the ota update for that rom.
---------- Post added at 03:04 PM ---------- Previous post was at 02:07 PM ----------
I go into software update, then i download the file, its like 50mb. Then it goes into rwcovery but the android dies and says aborted. So then i tried in recovery mode to flash zip blur ota 310006 but it happen the same. So i decided to stay in mis rom the 31006 from sept. But i was wondering if now i could flash in fastboot another rom like 40002? I saw u guy have the ota update for that rom.

Thank you - you're the best
HSD-Pilot said:
If you're now unlocked, get an EU FW, regardless what Version. Open the XML with Notepad + or any similar Programm and delete ONLY the complete Line that contains MOTOBOOT. Save the XML and start RSD 6.1.4.
After that you should be good to go.
Click to expand...
Click to collapse
My RAZR i works again thanks to HSD-Pilot. You saved my life.
THANK YOU
Roman

how found fastbootfolder me friend, sorry im newbie and me phone is death, please help

Razr i black screen after update phone not getting on
After i have unlock bootloader and root the phone....i have to do a fresh update to last Jelly Bean....phone have got turno of for starting insatll the update....and have rest like that...............When i press Power or Power and Vol Down is just doinf a short vibrate and the Notification led stay On for 10 sec after led OFF and a short vibrate.....>>Connecting to PC no getting any device on RSD or Fastboot and in Windows detect as a MEDFIELD device for wich no driver i found anywhere.........Phone was having 100% POWER before doing all this....adn i have try on several Pc with diferent Windows and diferent 32 or 64 bit with all RSD, drivers Sdk, etc installled and same results.....if anyone have a ideea how to repair will be a really expert on this modding devices....thank you and ...HELP

Boot Loop When Flashing ROMs

Hey guys I'm not exactly experienced with troubleshooting these kinds of problems. Hopefully I can learn something with the help of the community. I'll go ahead and lay out the situation and problem.
Problem:
Whenever I flash a rom with CWM, the phone will either A: Get stuck on a blank screen with the green LED on or B: Go through the boot animation and crash on "preparing android" and loop the process.
Info:
My AT&T Atrix HD has an unlocked bootloader, I have had several successful flashes in the past, and they have all worked well. I am able to flash the stock firmware back to the phone and it will load just fine. I have tried to go back to stock and start over, but I keep getting the same result. I've tried multiple roms with no change. This started happening when I was trying to load HoloBlur X according to the directions. It went through the whole installation in CWM without errors, but boot looped until it went dead. I did format and clear all the caches and all that too.
I'm not really sure what I'm missing here. I just hope someone might have a suggestion for me.
Thanks in advance for any help!

you could try format system in cwm

frog1982 said:
you could try format system in cwm
Click to expand...
Click to collapse
Thank you, and I appreciate the suggestion, but I have done that multiple times with no change in result.

Your positive your unlocked? Rooted?
Sent from my PACMAN MATRIX HD MAXX

deeje00 said:
Your positive your unlocked? Rooted?
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Absolutely positive.
I unlocked using the Motopocalypse method, and have rooted using Motochopper with the Mythtools tool.

does cwm say that it cannot mount the cache after flashing the rom

Safestrap VS. CWM
Austin Connell said:
Absolutely positive.
I unlocked using the Motopocalypse method, and have rooted using Motochopper with the Mythtools tool.
Click to expand...
Click to collapse
Are you using a version of Safestrap recovery or are you ABSOLUETLY positive that you are using a custom recovery? Most newer ROMs (4.1 and up) usually require you to use a custom recovery.

I'm sure he knows the difference between the 2.
Sent from my PACMAN MATRIX HD MAXX

Wipe and Restore
Hey guys I'm not exactly experienced with troubleshooting these kinds of problems. Hopefully I can learn something with the help of the community. I'll go ahead and lay out the situation and problem.
Problem:
Whenever I flash a rom with CWM, the phone will either A: Get stuck on a blank screen with the green LED on or B: Go through the boot animation and crash on "preparing android" and loop the process.
Info:
My AT&T Atrix HD has an unlocked bootloader, I have had several successful flashes in the past, and they have all worked well. I am able to flash the stock firmware back to the phone and it will load just fine. I have tried to go back to stock and start over, but I keep getting the same result. I've tried multiple roms with no change. This started happening when I was trying to load HoloBlur X according to the directions. It went through the whole installation in CWM without errors, but boot looped until it went dead. I did format and clear all the caches and all that too.
I'm not really sure what I'm missing here. I just hope someone might have a suggestion for me.
Thanks in advance for any help!
Click to expand...
Click to collapse
If you indeed are positive that you flashed the correct custom recovery, then follow these steps to fully Wipe, Restore to stock, and reflash.
Please read all of these steps before attempting to follow them!
** Note: I am not responsible for any damage done to your phone by following these instructions. **
Charge your device to a reccomended 80% (at least)
Make sure you have a Windows computer
Download the latest USB drivers from Motorola
Boot into your current recovery and make a nandroid backup, just in case.
Boot your device into Fastboot by powering off device and holding the Power+Volume Up+Volume Down and scrolling using the Volume Down button.
Plug your device into your computer
Download Fastboot if you don't already have it. (A simple Google search should result in a download link)
Type "fastboot erase data"
Type "fastboot erase cache"
Type "fastboot erase system"
Type "fastboot erase boot"
Type "fastboot reboot"
All of these commands should pass without conflict.
Your phone should reboot, but have no bootable OS. Don't panic if you get this error. Just manually power off your device and put it in bootloader mode once again (Power+Volume Up+Volume Down).
After that, follow these steps to flash to stock.
Download and install RSD Lite 6.1 here : www.mediafire.com/?3ckiknmwcpjolb2
Download the correct Fastboot Package for Jellybean here: http://sbf.droid-developers.org/dinara/list.php -- It should be MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip for 4.1.1 Jellybean on AT&T.
Make sure your phone is in bootloader mode with the directions in the first set of instructions and select Fastboot flash mode.
Open RSD Lite and select the downloaded Zip file in the box at the top.
Your device should appear at the list view towards the bottom of the screen. Click it and the "Start" button should be clickable. Click start and wait.
Wait for RSD Lite to say success and do not unplug it until the phone COMPLETELY BOOTS UP.
After all of this, you can now root, unlock bootloader, flash CWM, and install your custom rom. This should take care of any bootloops while installing Custom ROMs.
Click the thanks button if I helped!
PM me if you have any problems during this so I can help!

lol no, I'm not using a safestrap. I'm using a CWM Recovery.
I will give the rsd method a try tonight. thank you guys for all the help so far. luckily i have another phone to use in the meantime.

PHP:
Austin Connell said:
lol no, I'm not using a safestrap. I'm using a CWM Recovery.
I will give the rsd method a try tonight. thank you guys for all the help so far. luckily i have another phone to use in the meantime.
Click to expand...
Click to collapse
Okay. Make sure to tell us the results! Good luck!

I had very similar problems because I unwittingly attempted to flash the wrong cwm recovery file... which seems to have affected the Boatloader behaviour. I made it to #6 of the RSD steps in the help offered by lucasantarella (I was using RSD Lite 6.1.4), but the flash fails with:
Model Port No. Port Type IMEI / ESN / MEID Status Progress Result
Fastboot QINARA S 1 USB N/A Failed flashing process. Unknown fastboot command. (getvar) FAIL
Here's the complete story on the phone:
Brand new Factory Atrix HD, 4.1.1.
Installed MythTools (V1.1) on Windows XP and downloaded the USB Motorola Drivers
Used MythTools to unlock the bootloader
Installed superuser-4.3-beta2.zip
Installed ROM Manager 5.5.2.0 (which I can't use until the customized CWM for AHD is installed)
Downloaded mb886-cwm-6.0.3.6-touch-recovery-flashable-signed.zip
Using MythTools, I selected the wrong recovery file (selected a stock cwm instead) which failed to flash,
and the bootloader is now reporting a Flash failure. Here's the entire screen:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is UNLOCKED. Status Code: 3
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Flash Failure
usb connected
When I power it down and then hold the vol + and - together, I get the following menu:
Boot Mode Selection Menu (10.9B)
Vol Up Selects, Vol Down Scrolls
Available Boot Modes:
Normal Powerup
Recovery
AP Fastboot
Factory
BP Tools
Selecting any of those puts the AHD into the stock AT&T 4.1.1 normal screen and its ready for use.
Using Myth Tools to "Reboot normally" (option A) does the same thing as Option B, "Reboot to fastboot mode", which puts me back into the fastboot screen showing "Flash failure".
It appears that I'm locked to 4.1.1... because of Bootloader problems.
Any comments/thoughts/insight? It's been a year since I did any flash/RSD work and have poured over the various pages/threads on the AHD for the last three days... Apparently I didn't read enough...
Am currently using a Motorola Bravo running the CyanogenMod-72-20120506-NIGHTLY-Kobe and was hoping to migrate up to the AHD.
-ricer1

whew!!! The Atrix HD works!!!!
I thought my phone was crippled forever.. but I followed leanix's instructions here and am running epinter's rom on my Atrix HD:
http://forum.xda-developers.com/showthread.php?p=45306485#post45306485
Many thanks to leanix for posting his MUCH needed help.
- ricer1

lucasantarella said:
If you indeed are positive that you flashed the correct custom recovery, then follow these steps to fully Wipe, Restore to stock, and reflash.
Please read all of these steps before attempting to follow them!
** Note: I am not responsible for any damage done to your phone by following these instructions. **
Charge your device to a reccomended 80% (at least)
Make sure you have a Windows computer
Download the latest USB drivers from Motorola
Boot into your current recovery and make a nandroid backup, just in case.
Boot your device into Fastboot by powering off device and holding the Power+Volume Up+Volume Down and scrolling using the Volume Down button.
Plug your device into your computer
Download Fastboot if you don't already have it. (A simple Google search should result in a download link)
Type "fastboot erase data"
Type "fastboot erase cache"
Type "fastboot erase system"
Type "fastboot erase boot"
Type "fastboot reboot"
All of these commands should pass without conflict.
Your phone should reboot, but have no bootable OS. Don't panic if you get this error. Just manually power off your device and put it in bootloader mode once again (Power+Volume Up+Volume Down).
After that, follow these steps to flash to stock.
Download and install RSD Lite 6.1 here : www.mediafire.com/?3ckiknmwcpjolb2
Download the correct Fastboot Package for Jellybean here: http://sbf.droid-developers.org/dinara/list.php -- It should be MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip for 4.1.1 Jellybean on AT&T.
Make sure your phone is in bootloader mode with the directions in the first set of instructions and select Fastboot flash mode.
Open RSD Lite and select the downloaded Zip file in the box at the top.
Your device should appear at the list view towards the bottom of the screen. Click it and the "Start" button should be clickable. Click start and wait.
Wait for RSD Lite to say success and do not unplug it until the phone COMPLETELY BOOTS UP.
After all of this, you can now root, unlock bootloader, flash CWM, and install your custom rom. This should take care of any bootloops while installing Custom ROMs.
Click the thanks button if I helped!
PM me if you have any problems during this so I can help!
Click to expand...
Click to collapse
Hey i tried this in bot rsd lite and myth tools but it won't work
I can't get back into recovery, or boot up the phone. it only boot into fast boot
my phone is locked and status code 0
I really don't know what to do.
when I use myth tools is says fastboot not found or as a command on internal or externel
or attrib internal or external
please help me

alki1979 said:
Hey i tried this in bot rsd lite and myth tools but it won't work
I can't get back into recovery, or boot up the phone. it only boot into fast boot
my phone is locked and status code 0
I really don't know what to do.
when I use myth tools is says fastboot not found or as a command on internal or externel
or attrib internal or external
please help me
Click to expand...
Click to collapse
Follow this guide http://forum.xda-developers.com/showthread.php?t=2259661

Having a tough time going back to stock. Decided to give lucasantarella's wipe and restore process a go. At step #8 I got this:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>fastboot devices
TA30001GGN fastboot
C:\>fastboot erase data
erasing 'data'...
Invalid partition name data
FAILED (remote failure)
finished. total time: 0.105s
C:\>
I've ensured that I have the latest drivers installed and have the latest fastboot. Any help on what to try next would be appriciated. Thanks.
Edit: Would trying leanix's post on using the command lines be advisable for me at this time? PhilZ touch and CM 11 are currently installed on my device. PhilZ seems to run ok but clearing the dalvik cache doesnt seem to work and all I get is the arrow spinning around CM's head on bootup.

ifixgse said:
Having a tough time going back to stock. Decided to give lucasantarella's wipe and restore process a go. At step #8 I got this:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>fastboot devices
TA30001GGN fastboot
C:\>fastboot erase data
erasing 'data'...
Invalid partition name data
FAILED (remote failure)
finished. total time: 0.105s
C:\>
I've ensured that I have the latest drivers installed and have the latest fastboot. Any help on what to try next would be appriciated. Thanks.
Edit: Would trying leanix's post on using the command lines be advisable for me at this time? PhilZ touch and CM 11 are currently installed on my device. PhilZ seems to run ok but clearing the dalvik cache doesnt seem to work and all I get is the arrow spinning around CM's head on bootup.
Click to expand...
Click to collapse
If you're trying to wipe user data/do factory reset through fastboot, try "fastboot -w". Also are you using the snapdragon fastboot?
Sent from my MB886 using Tapatalk

[Q] atrix hd stuck in M logo

Hi, my best friend she had a HD phone, one day got stuck into the M logo, the only thing I can do is get into the fastboot, no recovery no nothing.. So i try to reinstall the rom, have download several tools but i cant do anything, after several intents to install roms i hace in AP fastboot flash mode, device is unlocked status code 1fastbookt Reason sticky bit factoy_fastboot. for a 2nd time but i can install roms, I dont know if phone bootloader unlock and cant check... I dont know if phone is usb debugging cause it wont load the system. I dont see any internal files from phone I also try rsd lite, but the same it says that it start doing the process but nothing else happen.. any ideas on how to get a rom install there..
thanks

SAME thing..
Please do help us...No recovery...No debugging...stuck at logo..!!

If you don't have an unlocked bootloader, I don't think you can use Myth or RSD to flash an ICS rom over a JB rom.
Did you load the latest Motorola USB drivers? When you connect the phone, run adb to list the devices. Does your phone appear?

not for me doesnt show any devices... and while trying to do other commands always get stuck ad *daemond started succesfully* but doesnt do anything.. also when trying to use motorola device manager it says it will update and never connect to server and close the app.
if i do fastboot commands like reboot-loader it does work it reboots the phone, but if i try to flash something doesnt it doesnt do anything.. i try using mfastboot also and the same happen.
Is there a way to flash a rom or something so i can fix this phone or it is dead?

On the Fastboot screen, if it says UNLOCKED in capitals next to "Device Status:" , then this problem is easily fixable.
Download RSD Lite from here: http://forum.xda-developers.com/showthread.php?t=2231249
Download Motorola Stock Firmwares:
Stock Jellybean for AT&T: http://sbfdownload.droid-developers...MB886_NII_TA-2-16-release-keys-NII-MX.xml.zip
Stock Jellybean for Bell Canada: http://sbfdownload.droid-developers...FFW-11-4-release-keys-BellMobility-CA.xml.zip
Open up your zip file and replace the .xml with the new XML you will download from this link: https://www.box.com/s/num1eshkf0c2or2h4160 You really can't forget to do this!
Launch RSD, connect device to PC, make sure RSD recognizes it. Navigate to your firmware file, select it, and press the start button. Sit back, relax, and let it do its work. It will take around 5-10 minutes. Do not unplug the cable, and do not attempt if you are in a situation in which you think you may lose power (especially if running from a desktop PC).
If RSD Lite won't work, then this thread will show you how to manually flash your stock firmware: http://forum.xda-developers.com/showpost.php?p=40929335
Basically, you repeat all the instructions I just gave you and then manually input some lines in Command Prompt.

mb886 hard bricked with no salvation yet

Hi friends, first of all I am here because I don't have another options to try or I haven't found it yet here or in internet, I have a MB886 unlocked from AT&T, it was running AOSB 1.3.4(kk 4.4.2) had philz touch recovery and it just stays in infinite boot loops only turning off by entering in the ap fastboot option, from the causes I could mention the installation of the EB40 battery, but it was trouble free, and the cleaned of cache and dalvik from recovery, maybe a bad charge of static when installation? or a failure in philz touch?...
After search all about the problematic, download drivers and the computer ( windows 8) recognizing the fastboot quinara s from my cellphone, this is what I did:
-firstly, followed this post http://forum.xda-developers.com/showthread.php?t=2334000 and nothing positive, then this http://forum.xda-developers.com/dro...-bricked-razr-m-4g-xt907-hd-preflash-t3135462 and nothing positive with the fastboot commands and rsd lite doesn't recognized my cellphone fastboot in wondows 8.( tried to flash MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml, MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml and ATT_MB886_4.1.1-9.8.0Q-97_MB886_FFW-28_CFC_1FF.xml)
- I tried MYTH tools too, but it doesn't work, tried to flash MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml and ATT_MB886_4.1.1-9.8.0Q-97_MB886_FFW-28_CFC_1FF.xml it shows commands like "varable not supported" or "target reported max download size of" but finished the flashing and still bootlooping.
-Followed this guide: http://forum.xda-developers.com/dro...-bricked-razr-m-4g-xt907-hd-preflash-t3135462 by fastboot, windows 8 and the motorola factory cable( pin 1 and 4 with +5v) could flash sucesfully MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml it works like a charm but was while it stayed connected to the computer, after this, flashing process only could be with the gpt_main0 file from the nextel firmware.
- Even in a sometime, I dont remember after how many flashings of the nextel firmware but was using the motocable, I could entered to my twrp recovery, cleaned all and did a clean install for AOSB KK from my SD, rebooted and bootlooping, then, I flashed again and entered to TWRP again and did a factory reset, and nothing.
- I tried MYTH tools again, but it doesn't work, tried to flash MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml and ATT_MB886_4.1.1-9.8.0Q-97_MB886_FFW-28_CFC_1FF.xml with the file gpt_main0 from the nextel firmware and in one time only reach the AT&T animation then froze.
- I combined the method from the razrs and the another one for the AHD to flash all the files from the firmwares and nothing happened, even the moto cable stops of functioned , because it showed responds from the fastboot like "varable not supported" "target reported max download size of " "FAILED (remote failure)"and with a normal usb cable everything was well flashed and nothing.
- flashing with rsd lite 6.1.6 in win xp used to get Error with MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml because the step of flash gpt_main0.
- I substituted gpt_main0 from MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml and it work with rsd in win xp (says SUCCES), just the last step when rebooted the phone, the phone stayed in boot loop.
-flashed MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml with RSD in win xp and fails in the last step when reboot, it stays bootlooping even when rsd says "SUCCES".
-tried to flash in ubuntu(fastboot method) with moto cable and a usb cable but never was like in windows 8, just boot loop and more boot loop.
so, here is the history of what I did it to my cellphone and he doesn't want to live anymore, so the question is, what I missed out? or what I can do it?, discarding throw it to the trash or having like a nice paperweight...
Any kind of help, suggestion, comments, or hardware modification will be appreciated and sorry for my english, I wrote the best I could.
P.D: always had a good porcentage of charge in the battery while did the flashings,charged it with 5v and 500ma directly to the battery and tested with multimeter when fastboot alarmed low battery, and anytime while phone had been flashed with AT&T relase keys rom, bootlooping was with the advertisement about the bootloader unlocked, and when had been flashed with nextel firm it shows motorola dual core logo boot loop.

I don't remember the exact name of the thread but search Atrix HD command line and you should find another guide that always worked for me. I never had luck with rsd lite or mythtools.
Sent from my LG-D850 using XDA Free mobile app

failed flashing partition gpt_main0
thank you for the help, I found that post: http://forum.xda-developers.com/showthread.php?t=2259661 and following the instructions, but I don't have more than a "FAILED" message in the first step when I try to flash gpt_main0 partition, with att release keys and with nextel firm, even when I use "mfastboot" instead of fastboot, it gets error message, there is a newer firmware version than the nextel one? or the partition is corrupted?... thanks.

The nextel firmware is the newest. There was an ota from att for the heartbleed bug, but I think that's all that was in it.
Sent from my Nexus 7 using XDA Free mobile app
---------- Post added at 11:06 PM ---------- Previous post was at 11:04 PM ----------
Are you sure you have an atrix HD? You mentioned TWRP in the op, but we don't have a fully functioning twrp.
Sent from my Nexus 7 using XDA Free mobile app

Philz touch instead twrp
Ok, thanks again buddy, and yes , the cellphone is an atrix hd, but you are right I used to have a philz touch recovery instead twrp (my mistake), the only error I have is flashing gpt_main0 partition and if I flash completely there is no more fails, with "mfastboot" every flash step is running like a charm and with "fastboot" shows messages like bootloader variable not supported or maximum size errors, the cellphone turns on bootlooping but stills enter to boot menu selection and ap fastboot mode...

Help! My Motorola RAZR I XT890 cannot be "unbricked" and I tried several methods...

Help! My Motorola RAZR I XT890 cannot be "unbricked" and I tried several methods...
Hello!
I unlocked the bootloader successfully, then I tried to root my phone using The Razr guy method and I used the "RAZRi_Root_Windows" file, while rooting my phone went to the "warning bootloader unlocked" screen and it just loops forever from that screen, the bat file, showed that it successfully rooted my phone. I tried to fix it using rsd lite, but it never detects my phone, so I searched for a way to make my pc able to detect it, so I found I could use Intel xFSTK, installed it but still nothing it doesn't appear as shown in the tutorial, I even downloaded the dll file that it needed to run, but after running the xFSTK DLDR or something like that, the application is completely empty, and I saw it should show some tools to download something. Also tried using Linux Zorin, but it only says that my XT890 cannot be accessed and shows an usb error code.
I am able to enter the fastboot screen, the one you get by pressing POWER and VOLUME DOWN, also it charges my batter completely normal. Also my pc is able to show that the XT890 is connected, but only before installing the drivers and it shows the CD installer for the Motorola Device Manager and some other files (all this while looping), and if I enter the fastboot flash mode, it appears as "fastboot smi S", with a yellow triangle and an exclamation sign while in Windows device manager. It has Jelly Bean update from telcel (mexico), and I already have the xml.zip file to reinstall it.
I use windows 8.1 , and as mentioned Linux Zorin on my PC.
Could some help me with it...if you now how to fix it please list every single step on how to do it T_T, THANKS IN ADVANCE!!!!

It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.

Hazou said:
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Click to expand...
Click to collapse
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T

weird_user said:
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
Click to expand...
Click to collapse
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error

Thanks again!!!
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
I am able to enter RECOVERY MODE NOW (I installed CWM, before this I was only able to see the android lying on the floor ans saty dead right there, I was supposed to press Volume + and - and the camera button at the same time, but nothing happened), it seems to be easier to unbrick it this way, but now the problem is that after I follow the steps to reinstall the original ROM, it aborts installation. I read this may be caused due to a file on the zip file, I looked for it, but nor the Folder META-INF, whic is supposed to contain a "update-script" file, nor that file is anywhere in the ROM folder...
I've even tried cyanogenmod (after first trying Telcel original ROM and then the retail GB ROM) cuz it actually contains the folder previously mentioned and the file is in a different path, but it is there, I modified it, but got a "Can't open tmd/update.zip (bad) Installation aborted" error...I don't know what else to do T_T...
Note: I also used sideload and CWM to install it, but the same thing happens. Also checked some other post about this issue, but none has helped me...

What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.

Hazou said:
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Click to expand...
Click to collapse
It's done! Thanks!
I actually used another computer with windows 10, also I used RSD Lite and it worked just fine, now I have the stock ROM from Telcel and it it is working almost normal. The only abnormality I've seen is that my phone turns itself off when battery is at 20%, I searched info about that problem and it says I may re calibrate the battery, so it may work fine again, but now I need to root again to be able to do that T_T, hope it works this time...
THANKS! again!