• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root 5.9.901 - Root issues

Vehtemas

Android Expert
Jul 6, 2010
946
146
Hey guys,

I did the path saver thing and managed to get my Bionic from 5.7.893 (or where ever it was), to 5.9.901.

However the root was lost when I went from 5.5.893...

And I cannot find an option that doesn't require me to drop back to 5.5.893.

I was hoping to avoid any further difficulties but it looks like I might be cursed, unless someone here knows a way to root 5.9.901?

Thanks guys.
 
You'll have to bit of digging, but I think I've seen instructions on how to do this on other forums. However, the easiest and most successful way to do it that I've seen is to go to the .893 OTA update, 43V3R Root, and then install the .901 update. Someone smarter than I may be able to help you with the former, but the latter is the way I handled it to be safe.
 
  • Like
Reactions: Vehtemas
Upvote 0
You'll have to bit of digging, but I think I've seen instructions on how to do this on other forums. However, the easiest and most successful way to do it that I've seen is to go to the .893 OTA update, 43V3R Root, and then install the .901 update. Someone smarter than I may be able to help you with the former, but the latter is the way I handled it to be safe.

Eh... I was hoping to avoid that but I guess I could always redo the path saver thing...

Was just hoping to avoid having to do this again...
 
Upvote 0
Upvote 0
  • Like
Reactions: SNeitzel and al23
Upvote 0
That actually doesn't.

To get back to stock, you have to go through the pathsaver again.

Bionic Path Saver 1-Click Method - Page 3

Then once that's done, just bootstrap and make a backup of stock so you don't have to re-do everything again.

Lol silly me. I forgot I am on stock 5.9.901 and had to do a wipe because of some problems I was having and used that to redo everything. But yes you're right it doesn't. I haven't been on any rom since Kin3tx. Was so much easier with an unlocked bootloader on my OG Droid...damn Motorola...give us our unlocked bootloader...that's the least you can do since you're way too focused on your other phones D:. Give us something to play with since you're treating the Bionic like a stepchild >.>...
 
Upvote 0
Lol silly me. I forgot I am on stock 5.9.901 and had to do a wipe because of some problems I was having and used that to redo everything. But yes you're right it doesn't. I haven't been on any rom since Kin3tx. Was so much easier with an unlocked bootloader on my OG Droid...damn Motorola...give us our unlocked bootloader...that's the least you can do since you're way too focused on your other phones D:. Give us something to play with since you're treating the Bionic like a stepchild >.>...

An awkward stepchild that you replaced in a little over a month with a skinnier one.
 
Upvote 0
That actually doesn't.

To get back to stock, you have to go through the pathsaver again.

Bionic Path Saver 1-Click Method - Page 3

Then once that's done, just bootstrap and make a backup of stock so you don't have to re-do everything again.

Okay, it seems hung on Daemon started successfully:

[*]


[*] Motorola universal root script (Windows version)


[*] by P3Droid


[*]


[*] Before continuing, ensure USB debugging is enabled, that you


[*] have the latest Motorola drivers installed, and that your phone


[*] is connected via USB.


[*]


[*] Press enter to continue after you have changed your USB Mode to Charge Only.

..
Press any key to continue . . .

[*]


[*] Pushing the update zip file to your sdcard...


[*] Do not wipe data or cache...


[*] Pushing 5.5.893...

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1183 KB/s (57116385 bytes in 47.138s)

[*] Pushing 5.9.901...

1116 KB/s (59018834 bytes in 51.640s)

[*] Rebooting phone to bootloader...


[*] Press enter to continue if both files pushed to sdcard without an error...


[*] If either file failed to push to device disconnect phone and exit this windo

w...
Press any key to continue . . .

[*] Fastboot flashing needed partitions...

< waiting for device >
sending 'system' (262144 KB)... OKAY [ 32.196s]
writing 'system'... OKAY [ 15.955s]
sending 'system' (229120 KB)... OKAY [ 28.235s]
writing 'system'... OKAY [ 11.911s]
sending 'preinstall' (262144 KB)... OKAY [ 32.112s]
writing 'preinstall'... OKAY [ 15.023s]
sending 'preinstall' (49152 KB)... OKAY [ 6.025s]
writing 'preinstall'... OKAY [ 2.661s]
sending 'webtop' (262144 KB)... OKAY [ 31.736s]
writing 'webtop'... OKAY [ 17.128s]
sending 'webtop' (262144 KB)... OKAY [ 32.139s]
writing 'webtop'... OKAY [ 13.719s]
sending 'webtop' (262144 KB)... OKAY [ 32.300s]
writing 'webtop'... OKAY [ 13.680s]
sending 'webtop' (262144 KB)... OKAY [ 32.109s]
writing 'webtop'... OKAY [ 13.696s]
sending 'webtop' (262144 KB)... OKAY [ 32.106s]
writing 'webtop'... OKAY [ 13.639s]
sending 'webtop' (54016 KB)... OKAY [ 6.633s]
writing 'webtop'... OKAY [ 3.253s]

[*] Rebooting phone...

rebooting...

[*] Rebooting the Phone


[*] Waiting for device...

* daemon not running. starting it now on port 5037 *
* daemon started successfully *
And the phone continually tries to reboot and loops the droid bionic startup screen (the red eye) continuously.
 
Upvote 0
Initially I got a boot failure. Last time I tried, it did not even recognize the phone.

I am getting ready to try again.


Damn, I keep getting interrupted. My wife leaves, and the damn phone rings. As soon as I am off the phone, my wife comes back in the bloody room. I am trying to do this without her knowing I bricked the phone....
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones