What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

5.5.5.893 FXZ .901/.902 compatible and.902 update

after deleting both the xml command an the image file it still wiped data but when i i deleted the erase userdata command only then did the apps an personal data stay intact

erase userdata wipes the system partition...not the sdcard partition...the erase emstorage & flash emstorage commands, and emstorage.img file are for the sdcard partition...deleting all of those out will leave everyone's sdcard data intact,,,

also, by deleting the erase userdata command in the XML, you are opening up potential problems for those that are FXZ'ing from custom ROMs....you don't want to flash the stock system image over unwiped custom ROM data...

As for the CDT post you made...couldn't make sense of it ...sorry... except the first few words, which is basically what I suspect, but is moot since why mess with .886 when they can go directly to your .893 FXZ and flash the newer CDT.bin...
 
erase userdata wipes the system partition...not the sdcard partition...the erase emstorage & flash emstorage commands, and emstorage.img file are for the sdcard partition...deleting all of those out will leave everyone's sdcard data intact,,,

also, by deleting the erase userdata command in the XML, you are opening up potential problems for those that are FXZ'ing from custom ROMs....you don't want to flash the stock system image over unwiped custom ROM data...

As for the CDT post you made...couldn't make sense of it ...sorry... except the first few words, which is basically what I suspect, but is moot since why mess with .886 when they can go directly to your .893 FXZ and flash the newer CDT.bin...
ok ill update the FXZ with ur xml an the OP an can u answer some thing for me i looked in the .886 fxz an found an img file called motoboot thats not in the xml command line an i the .893 i found a img file that is call Dc39 thats also not in the .893s xml command line so what are they for an why include them if the xml does use them?
 
I have no idea what the dc39 img file is or how it's flashed from the XML...but the motoboot.img might be the M logo or bootanimation?? which might flash via the logo.bin file...don't know what that bin file is for
 
I have no idea what the dc39 img file is or how it's flashed from the XML...but the motoboot.img might be the M logo or bootanimation?? which might flash via the logo.bin file...don't know what that bin file is for
ok update the op an also u have tested ur xml an it worked right? also i scanned both .886 xml an .893 xml an no where is there a command to flash these files i am kinda scratching my head hear lol i actually tried to add them to the xml but naturally they failed to flash lol i was kinda thinking in the back of my head these files would magically unlock the boot loader thats why moto didnt incorporate them into the xml lol boy was i dreaming
 
I have no idea what the dc39 img file is or how it's flashed from the XML...but the motoboot.img might be the M logo or bootanimation?? which might flash via the logo.bin file...don't know what that bin file is for
also the motoboot img file is only in the .886 not the .893 an the dc39 img file is only in the .893 not the .886
 
lol...they wouldn't make it that easy, it would've been unlocked in three seconds...:p

And yes, I tested that XML with your compiled FXZ and went from EClipse 2.1, wiped data, then to stock .893 without any errors and with the sdcard partition fully intact...
 
lol...they wouldn't make it that easy, it would've been unlocked in three seconds...:p

And yes, I tested that XML with your compiled FXZ and went from EClipse 2.1, wiped data, then to stock .893 without any errors and with the sdcard partition fully intact...
lol i guess ur right they wouldnt make it easy lol i am thinking for just kicks an giggles i am going to call moto today an ask "so how do you unlock the bootloader on the droid bionic" an see how well that goes over
 
Last edited:
Step 5 open RSD Lite and boot phone into ap fastboot.

What is and how do you ap Fastboot?:blink:
Those with inquiring minds want to know.:D
 
Step 5 open RSD Lite and boot phone into ap fastboot.

What is and how do you ap Fastboot?:blink:
Those with inquiring minds want to know.:D

While powered off, hold down volume button and press power button. Tada!

Sent from my NookColor (CM9 Unofficial) using Tapatalk
 
Dude, you are the effing man:icon_ lala:!!!! Although I went and bought an external battery charger from Verizon, it was all worth it. For those that have had issues in the past or don't want to have issues, I would suggest buying an external battery charger. Even Verizon was telling me to get a new phone because they didn't have an external charger nor a test battery. Wack!! Thanks for the updated files, help, PM's, etc. You have my vote for the man here!!! Take care and let me know where I can donate, it's worth it as well dancedroid.
 
THANK YOU SARGENTMAJORD. Moto_Fail worked!! My Bionic is indeed re-rooted. u r d man

Hi Forum Members.

Thank you to Sargentmajord for your advice in re-rooting my rooted Droid Bionic.

On February 12th, or 13th, I posed a question on this forum.

I have a Droid Bionic. I had pretty much given up on getting the .902 update from Motorola. I did receive the .886 to .894 OTA while rooted with Petes. I lost root of course in that I wasn't rooted with forever root. I found a re-root in this forum to re-root after taking the .894 update.

I bought a Droid Razr Maxx. The day I turned it on, right away, I received an OTA to the Maxx (not yet rooted). I then wifi'd my Razr to the Bionic only to discover a .902 update was there. I then took the update (while wifi tethered to the Razr) on the Bionic and then of course, lost root again.

Once again, I came with my a*% in hand begging for help. Sargentmajord answered my question and even took the time to post a few more reply's as I asked additional questions.

For a few day's, I hesitated because I was fearful I might brick the phone (I paid full retail for the Bionic so I wouldn't have to endure another contract with Verizon). But in the end, Sargenmajord convinced me that I would be fine to take the update. So with that advice, I downloaded the Motorola drivers, pinned the USB cord to the Bionic, and hit the "Press to continue" command in the Moto_fail exploit. Botta bing, botta bang..., I am now once again rooted!!! It took six minutes and two reboots.

In another forum, Sargentmajord asked for others of us to help him help others who are trying to figure out how to do things like this. So in that spirit, if any of you have issues trying to re-root your bionic having lost root, I will do what I can to step you through it.

Folks, these forums are priceless! Thank you Sargentmajord and thanks to rck76 and jbroomwho wrote the script for Moto_fail. IT WORKS!


***Below is a copy of the post that led to my successful rooting of my Bionic***

[h=2]Do I have to Unroot before using Sargentmajord's exploit to regain root after OTA.902[/h]
Hi folks! Just when I gave up on my Droid Bionic, I connected via the Razr wifi and discovered I had .902 update waiting on me. I unfroze any frozen apps with TiBackup and installed the .902 update. Of course I lost root. I was not rooted with forever root. I was rooted with Petes before the .886 update to .894. I found an exploit that allowed me to regain root. Then, I installed the .902 update and again lost root. I was not Cheesecaked.

I noticed the following in a Sticky Note a few minutes ago:

".902 rooting exploit" For those that are on .902 an lost root with the help of rck76 and jbroom we have found a rooting exploit for the .902 update we take no credit for this exploit so enjoy. you can download it here http://www.***********/zip/0Gpdc25p/motofail_windows.html

I downloaded the above mentioned file. I also downloaded from Motorola the Motorola Driver Manager (my guess is that is where the drivers are installed for the Bionic and other Motorola smart phones).

My question is this: do I have to unroot my root that no longer is working or can I just download and install the above mentioned exploit? I am currently at .902 and so far the phone appears to be working fine (as toggled via wifi from my Razr Maxx).
 
Back
Top