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

[sargentmajord]

No credit needed, this is your baby... but that part (erasing the SDCard partiton) seems like a humbug part of the flash, so if unecessary, then removing it would be a nice addition

quick qestion is the system image ona different partition than the internal storage that we can access without root cuz if its not the wouldnt the flash fail cuz it cant earase the internal storage to put the new image on plus if u try flashing an system image over a bad one wont that make things worse? if it is on a different partition like i think it is the fix should be fine

 

[hilltophunter]

were u in ap fast boot when u applied the cdtfix? if not try it an the other exploit . the .902 exploit it will work with all system versions not just .902

negative result

 

[Mbk]

quick qestion is the system image ona different partition than the internal storage that we can access without root cuz if its not the wouldnt the flash fail cuz it cant earase the internal storage to put the new image on plus if u try flashing an system image over a bad one wont that make things worse? if it is on a different partition like i think it is the fix should be fine

system partition is completely different that the the external memory... erase userdata is what erases that, like wiping data in recovery except its done via the XML...so I'm gathering that erase emstorage is referring to the sdcard external memory...the SDCArd -ext partiton is left untouched

 

[sargentmajord]

negative result

ok pm me everything u have done to get u to where u are now i unfortunately cant help for the next 2 hrs i have some things i need to do an ill get back to u ASAP as long as ur phone is working will u be able to wait a little bit?

 

[JerseyDroid]

new to the thread, but i did read the complete t32 pages. WOW you guys are amazing!! I am on 901 forever rooted using pathsaver method a while back. Did PB2.2 unthrottle script and also the webtop mod hack from Droidmodderx to avoid the dock purchase and now i am failing with the status 7 error (Dockservice.apk) I tried both the OTA 22.5 mb update and the file from this site and attempted it thru stock recovery both fail. Can I FDR and just take the 902 push and then root it? any help is appreciated.

 

[Mbk]

new to the thread, but i did read the complete t32 pages. WOW you guys are amazing!! I am on 901 forever rooted using pathsaver method a while back. Did PB2.2 unthrottle script and also the webtop mod hack from Droidmodderx to avoid the dock purchase and now i am failing with the status 7 error (Dockservice.apk) I tried both the OTA 22.5 mb update and the file from this site and attempted it thru stock recovery both fail. Can I FDR and just take the 902 push and then root it? any help is appreciated.

Yes, flashing the FXZ will return you to stock 5.5.893, then you root and forever root, from there you can accept the .893 to .902 OTA and you would end up with stock .902 forever rooted...

 

[JerseyDroid]

another question, if i just factory reset can i then take the 902 update and then root?

Sent from my DROID BIONIC using DroidForums

 

[sargentmajord]

another question, if i just factory reset can i then take the 902 update and then root?

Sent from my DROID BIONIC using DroidForums

it may or may not work all i know is my FXZ will fix it cuz with an FDR u dont know what it will do

 

[sargentmajord]

Yes, flashing the FXZ will return you to stock 5.5.893, then you root and forever root, from there you can accept the .893 to .902 OTA and you would end up with stock .902 forever rooted...

thanks for the help an hey just finished the FXZ file that doesnt require a back up. lol finally got it sorted out after 5 bricks an for some reason a essential image file disappearing from my desktop like a black hole just came an took it (wtf) so had to redownload my own FXZ file (how embarrassing) an replace the image file but after that 4 hr hell lol i have reaped my rewared currently uploading it as we speak.

 

[Mbk]

Yeah figured that the emstorage erase and flash commands were basically uneccessary and would help avoid the need to backup your sdcard...or for some who didn't make that backup, loss of all their info on their sdcard...
Now your FXZ will be even better...

 

[JerseyDroid]

ok I just started and rsd lite just said "error !!!! Failed to write to preinstall.img Please check if there is enough free disk space" what should I do now?

 

[Cinoib]

Do I have to Unroot before using Sargentmajord's exploit to regain root after OTA.902

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).

 

[sargentmajord]

Yeah figured that the emstorage erase and flash commands were basically uneccessary and would help avoid the need to backup your sdcard...or for some who didn't make that backup, loss of all their info on their sdcard...
Now your FXZ will be even better...

na it wasnt the img file cuz when i took it out the FXZ flashed but i caused the phone to be come a unstable an resulting in a brick all i had to do was edit the erase user data line in the script. an when i did a side by side comparison of the .886 .893 i noticed that the .886 didnt have a emstorage img file but had a userdata img file where as the .893 had the emstorage img file but not the userdata img file

 

[sargentmajord]

ok I just started and rsd lite just said "error !!!! Failed to write to preinstall.img Please check if there is enough free disk space" what should I do now?

which FXZ are u using?

 

[sargentmajord]

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).

no u shouldnt have to un root since with the update all traces of root are gone except the super user apk hich is ok all the script will do is root the phone an fail at the installation process of super user since its already there so u will be fine just run the exploit