• 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

tehsusenoh said:
It does.

I'm currently re-making the ZIP for the Released Root to be compatible with 5.9.901 in a moment, check in the Sticky, and here.

EDIT:

I've created my own script, here:

http://androidforums.com/bionic-all-things-root/486871-introducing-tehroot-v1-0-a.html
Click to expand...


I'm relatively new to this, but when you say "the sticky" what do you mean? i have seen this in many posts and am clueless.

What's the status on r3l3as3d root for 5.9.901 ? that may be the only thing to save me. RSD lite is not working.
 
al23 said:
I'm relatively new to this, but when you say "the sticky" what do you mean? i have seen this in many posts and am clueless.

What's the status on r3l3as3d root for 5.9.901 ? that may be the only thing to save me. RSD lite is not working.
Click to expand...


What was the error in fastboot? If you flash the 5.5.893 fxz in rsdlite coming from 5.9.901 you will get a fastboot error. Don't worry that is normal. You will then have to fastboot the cdt.bin file from .901. I will post a link.

If you do go here unbrick your bionic and follow the steps for .901 cdt.bin file in the op. You will need fastboot for this
 
There is no error on the phone in fastboot flash. (pressing volume down key and power keys) However, RSD lite does not recognize the device when the phone is connected to the computer with RSD lite running. At least not now.

It only seems to recognize it when I try to boot up. Of course this is unhelpful because i need the phone in fastboot.

Previous efforts running RSD resulted in flash failure.

So what you are saying is that the cdt bin file would need to be in the zipped folder i open from rsd lite?

(sorry, I'm a noob. I'll learn fast)
 
OK. I had a similar problem. Rsdlite would only recognize my phone when in fastboot mode. With the phone off, press and hold the volume down button and the power button at the same time. The fastboot menu will pop up. Now RSDlite should see your phone and you flash the file. once the file is flashed and the phone goes to boot up you will get an error. That is when you will push the cdt.bin file with fastboot. I added the steps and files in http://androidforums.com/bionic-all...5-893-rsdlite-including-coming-5-9-901-a.html
 
That's what I'm saying. When I do press volume down and power button, the phone enters fastboot. However, RSD Lite does NOT recognize the phone. Sorry, my wording should have been clearer. Thanks for the link. I will read the info in the link.
 
I had the same problem. Check out the thread I started on 1/10, "Help, bricked my phone". If you go to the last post there is a link to the info that I used to get mine working again.

Love your comment on hiding the bricked phone from your wife. I did the same thing!
 
All my efforts have failed. As i am traveling a week from tomorrow, I have no choice but to get another phone from ebay. I will say it is great having the resources of the users on this forum. All of you have been very patient and helpful...
 
The phone is back up and running. I am back on 5.5.886. I will upgrade and root. But for now that's all.
 
Well, one thing at a time. The update failed and the phone is back to being a brick in fastboot.

Why root? Well, I can kill all the verizon bloat (i would not uninstall, I would just kill). That's something. If a rom catches my fancy and i can install it risk-free (reading instructions carefully, reading the experience of others, etc) then I would install it.

Frankly I seem to be having no manner of luck with this. So for now, rooting and debloating is what I would risk.

As for my current issue, it may result from stuff on my SD card. All I know is, I need to fix things so I can take an update without issues. Right now, I am not there.


Edit: Phone is good again. I ran a then run the FixCDT script...(there was a cdt error) in fastboot. Strange thing is, the update i was trying to install took. I am now on 5.5.893. If this is what I need to do to update.....is not worth the stress. I need a drink.
 
al23 said:
Why root? Well, I can kill all the verizon bloat (i would not uninstall, I would just kill). That's something. If a rom catches my fancy and i can install it risk-free (reading instructions carefully, reading the experience of others, etc) then I would install it.
Click to expand...

OK ... so you are planning to do SOMETHING that requires you to be root-ed.

99% of the bloat can not be uninstalled.

I sure hope "kill" means "freeze" and not "delete". When you install a production OTA it is going to check for the existence of some of that bloat on your current system and it will terminate installation with an error if it doesn't find it. So freeze what you want to freeze and unfreeze it all before attempting to install the production OTA.

The other idea to pass on to you is ... slow down. Give the problems time to surface before you take the next step. Like ... really slow down ... like days.

... Thom
 
al23 said:
Well, one thing at a time. The update failed and the phone is back to being a brick in fastboot.

Why root? Well, I can kill all the verizon bloat (i would not uninstall, I would just kill). That's something. If a rom catches my fancy and i can install it risk-free (reading instructions carefully, reading the experience of others, etc) then I would install it.

Frankly I seem to be having no manner of luck with this. So for now, rooting and debloating is what I would risk.

As for my current issue, it may result from stuff on my SD card. All I know is, I need to fix things so I can take an update without issues. Right now, I am not there.


Edit: Phone is good again. I ran a then run the FixCDT script...(there was a cdt error) in fastboot. Strange thing is, the update i was trying to install took. I am now on 5.5.893. If this is what I need to do to update.....is not worth the stress. I need a drink.
Click to expand...


Glad to see you got it working.
 
Thom Little said:
OK ... so you are planning to do SOMETHING that requires you to be root-ed.

99% of the bloat can not be uninstalled.

I sure hope "kill" means "freeze" and not "delete". When you install a production OTA it is going to check for the existence of some of that bloat on your current system and it will terminate installation with an error if it doesn't find it. So freeze what you want to freeze and unfreeze it all before attempting to install the production OTA.

The other idea to pass on to you is ... slow down. Give the problems time to surface before you take the next step. Like ... really slow down ... like days.

... Thom
Click to expand...

Kill means freeze. I would be asking for trouble if I uninstalled something important. I know updates definitely would not take if i uninstall apps. It also makes the phone buggy. I read that here :-).

Thanks for the tip. Seriously it's good advice. Right now, i am just reading posts here and leaving my phone alone. I will do nothing to it for a while. I almost would prefer that it not ring :).
 
Thom Little said:
OK ... so you are planning to do SOMETHING

The other idea to pass on to you is ... slow down. Give the problems time to surface before you take the next step. Like ... really slow down ... like days.

... Thom
Click to expand...

Oh, by the way, I had to laugh when I read your other idea (slow down). I had that very thought BEFORE installing the 893 update. Here I was thinking I was playing it safe. It was a Verizon update after all...

I have to say I would be in a worse place (using my phone strictly as a paperweight) if it weren't for tehsusenoh, dfib and yourself. Many thanks to you all.
 
You must log in or register to reply here.
Back
Top Bottom