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

Root After update lost root after using 43v3R root

wichita6

Well-Known Member
I ran the 43v3R root and it said success but after the 5.8.894 update I have no root or at least I assume I don't. I can't get Titanium Pro to launch. "error, I could not aquire root privileges..."
Is there a way to revert back or am I screwed?

:confused:
 
Did you reboot after rooting? Did you DL and install the Superuser app? Did it verify that you're rooted and update superuser (and su)?

Also, moving this to the ATR since it is root related.
 
Yes, I did reboot and installed Titanium pro but upon opening it I received the message. I downloaded superuser and installed. I just downloaded root checker and it states that I am NOT rooted.
is there anything I can do to get rooted?
 
I think it is very specific in which files it looks for, but I won't have time to post more details until tomorrow.

Better safe than sorry - unfreeze everything, apply update, then freeze again (after rooting if need be).
 
I rooted using: R3L3AS3DRoot and 43V3R root for the BIONIC v2.1 - xda-developers

I haven't gotten any official OTA push yet, guess I wasn't part of the general population the soak test got randomly pushed to. I've read that a lot of other people who used this method were able to retain root through the update and that most of the problems with loosing root came from rooting with pete's one click method. Time will tell once the official OTA gets pushed. Hope I don't loose root (I've got about $20 in root apps)!
http://forum.xda-developers.com/showthread.php?t=1279825
 
I feel like an idiot - I follow directions well but when it come to manual methods I get lost in all the apks and shells and bins etc.....

SO - I one click rooted a while back and I've blocked the updates for now. Theoretically if I run the forever root above (and it looks simple enough) we should be good?

Keep me posted :)

I maintained root after installing the OTA update last night but I used that program originally to both root / forever root. My theory is that people not maintaining root may have used an earlier version of that program than 2.1.

Since you're already rooted, you probably just want to choose option #3 when you run the program: "3. 43V3R Root a Rooted Bionic" Before running the program, make sure that USB debugging is enabled on your phone and that you have already installed the Motorola PC/USB drivers on your PC: USB and PC Charging Drivers - Motorola Mobility, Inc. USA

Finally to make sure that the 43V3R Root actually applied, after reboot, use your preferred file explorer to go into "/system/bin/" and "copy" the file "mount_ext3.sh" Place the copy somewhere on your sd card (sdcard-ext directory). Now use a text editor to open that copied mount_ext3.sh file (that way your not messing with opening the original system file). The text editor that comes in QuickOffice with the phone works fine. Scroll to the very bottom of the file and make sure these 3 lines are present at the very bottom:
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 4755 /system/app/Superuser.apk

If those lines are there, you're golden. If they aren't present then 43V3R Root did not apply properly and you'd have to add those lines manually to the original mount_ext3.sh file to be forever rooted. Be careful if you have to do that though, I read that if you use the ES File Explorer text editor to make the changes that it changes the permissions of mount_ext3.sh and cause a boot loop if you don't set them back to how they were originally.
 
I think it is very specific in which files it looks for, but I won't have time to post more details until tomorrow.

Better safe than sorry - unfreeze everything, apply update, then freeze again (after rooting if need be).

Wait by freezing something you mean uninstalling right?
 
Freezing is a feature in the pro version of Titanium Backup. As it states it freezes (halts) the program. The program is unable to do anything. It is a feature a lot of people use to stop bloatware from working without deleting it initially to ensure that it wont break something else.
 
Freezing is a feature in the pro version of Titanium Backup. As it states it freezes (halts) the program. The program is unable to do anything. It is a feature a lot of people use to stop bloatware from working without deleting it initially to ensure that it wont break something else.

Well I am having some trouble restoring some of my apps such as:
IM 3.0.4.6
IM Presence 2.3.4
Backup Assistant 2.3.4
Backup Assistant Client 1.0
Email 2.3.4
Email Authenticator 2.3.4

I dont know what happens when I try to restore them it just continuously says it is restoring but doesnt do it
 
Finally to make sure that the 43V3R Root actually applied, after reboot, use your preferred file explorer to go into "/system/bin/" and "copy" the file "mount_ext3.sh" Place the copy somewhere on your sd card (sdcard-ext directory). Now use a text editor to open that copied mount_ext3.sh file (that way your not messing with opening the original system file). The text editor that comes in QuickOffice with the phone works fine. Scroll to the very bottom of the file and make sure these 3 lines are present at the very bottom:
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 4755 /system/app/Superuser.apk

If those lines are there, you're golden. If they aren't present then 43V3R Root did not apply properly and you'd have to add those lines manually to the original mount_ext3.sh file to be forever rooted. Be careful if you have to do that though, I read that if you use the ES File Explorer text editor to make the changes that it changes the permissions of mount_ext3.sh and cause a boot loop if you don't set them back to how they were originally.

I get this far and it tells me I can't paste the file onto the card because it's a system file and "read only."
 
nevermind - got it!

and those 3 lines are indeed there.

Now am I brave enough to let the update through.......

Just take the leap, if those 3 lines are in there you will retain root. I did, and so did everyone else that went through that process and verified that 43V3R root did actually apply itself to that file. Good luck!

Update has been great for me so far. No more high pitched hiss sound when using ear buds and my 4G signal in fringe area is a lot more consistent / rarely any data drops. Camera seems to focus much quicker for me now too.
 
Just take the leap, if those 3 lines are in there you will retain root. I did, and so did everyone else that went through that process and verified that 43V3R root did actually apply itself to that file. Good luck!

Update has been great for me so far. No more high pitched hiss sound when using ear buds and my 4G signal in fringe area is a lot more consistent / rarely any data drops. Camera seems to focus much quicker for me now too.

thank you SO MUCH!

It totally rocked the update and TiBu still has superuser access!!
 
Lol - Nice to see you making the move over here to the dark side MBC

Enjoy your updated snappier phone with root preserved.
 
Sorry i might have misplaced this post sorry if so but
I rooted my bionic using petes on click method
Then updated the device...i need to send my device back
i tried the unroot button its not working...help pls
 
Sorry i might have misplaced this post sorry if so but
I rooted my bionic using petes on click method
Then updated the device...i need to send my device back
i tried the unroot button its not working...help pls


What did you update to? Did you use forever root? If you used forever root you might be able to remove the comand lines for forever root and reflash the last update you did in stock recovery.
 
What did you update to? Did you use forever root? If you used forever root you might be able to remove the comand lines for forever root and reflash the last update you did in stock recovery.

I didnt run any roms i rooted my self an left it
How ever im currently trying to use rsd lite but my the
Zip im using to big when compressed
 
Sounds like it is the webtop package - you might need to use the motorola fastboot tool instead, which eliminated the size restriction. Unfortunately, i'm not sure how to use it with rsd lite, but I'll be back home this evening, and can research it then, if you have not gotten an answer before then....
 
Back
Top Bottom