[Q] Any one got a Verizon OTA 2 nights ago?

Status
Not open for further replies.

kschang

Senior Member
Dec 11, 2010
440
72
0
San Francisco, CA
I got an OTA on Friday night or Saturday morning. Didn't notice any changes.

Next day, I realized I lost root. TiB says root access is denied. SuperUser is still installed, so that's not the problem. It's not even ASKING any more.

I tried running pSouza's one-click root, it failed in the third step. This was using 1.06 off Rootzwiki. I went to PSouza4's website and downloaded 1.07, and tried it again. Same thing.

Strangely my system (about phone) still says 5.5.893 (baseband CDMA_N_03.1c.57R ltdec_u_05.15.01), build number 5.5.1_84_DBN-21 so somehow I never got the 901 update. It stills says I'm on 2.3.4, but the exploit no longer works.

Any ideas?
 

kschang

Senior Member
Dec 11, 2010
440
72
0
San Francisco, CA
I went into SuperUser and it says TiB is still allowed. But when I run TiB it says root was denied.

Root Checker confirms: no root.

I tried 43V3R root and that failed too.

"* Running zergRush exploit..."
833 KB/s (23052 bytes in 0.027s)

[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[+] Found a GingerBread ! 0x00016118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[+] Zerglings found a way to enter ! 0x18
[+] Overseer found a path ! 0x000161e0
[*] Sending 189 zerglings ...
[+] Zerglings caused crash (good news): 0x40122c5c 0x0074
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd25ac9 0xafd39877
[*] Sending 185 zerglings ...

[-] Bad luck, our rush did not succeed :(
* Wait about 30 seconds for the adb server to restart as root
 

hurrrtin

Member
Jul 24, 2008
30
3
0
I had that happen to me as well. Turns out for me, that on .893, the automatic script failed. Doing it using the manual guide here in the dev forum did work.

Sent from my DROID BIONIC using XDA App
 

beard0

Senior Member
Apr 19, 2011
308
21
0
Try going into super user settings and check for an update for the binary..an outdated binary can cause the root being denied

/Droid3
 
Status
Not open for further replies.