68 replies to this topic

[arcanexvi]

Dumb question as I think it needs to be a little more clear in the OP. Are you saying ppl should temp unroot, or NOT temp unroot using Rootkeeper before updating. I've seen to many posts on the leaks not being clear where some say yes do it & others say no just protect root. Speaking for myself to date in any of the files I have tried/tested I've never temp unrooted. I just protect root using Rootkeeper and then update and have not had a problem.

There have been claims that not temp unrooting causes the process to fail. After 100+ flashes and never temp unrooting I can tell you that temp unrooting is not what is causing people's problems.

[JungleKing76]

Dumb question as I think it needs to be a little more clear in the OP. Are you saying ppl should temp unroot, or NOT temp unroot using Rootkeeper before updating. I've seen to many posts on the leaks not being clear where some say yes do it & others say no just protect root. Speaking for myself to date in any of the files I have tried/tested I've never temp unrooted. I just protect root using Rootkeeper and then update and have not had a problem.

This may not answer your question but it seems everyone had different experiences. I have always temp uprooted before installing ota. With 176, I forgot to and for some reason , the root method for 2.3.6 would not work. I had to fastboot back, root, temp unroot, install 176, then restote root. But I have heard others just rooted after 176 was installed with no issues.

Sent from my DROID RAZR using Xparent Purple Tapatalk

[arcanexvi]

This may not answer your question but it seems everyone had different experiences. I have always temp uprooted before installing ota. With 176, I forgot to and for some reason , the root method for 2.3.6 would not work. I had to fastboot back, root, temp unroot, install 176, then restote root. But I have heard others just rooted after 176 was installed with no issues.

Sent from my DROID RAZR using Xparent Purple Tapatalk

Rootkeeper and the 2.3.6 root method both failed?

[Aixelsyd]

There have been claims that not temp unrooting causes the process to fail. After 100+ flashes and never temp unrooting I can tell you that temp unrooting is not what is causing people's problems.

Thanks bud I'm with you on that as well. I've never temp unrooted either and have never had a problem updating a device. 9 out of 10 times an update failure has nothign to do with root. In all honesty it can't because rooting has nothing to do with the Assert check the update looks for before letting a device update

[Mr.Rzr]

ok guys so i'm new to the razr just got it in the mail yesteray. soon as i powered it on got an update to 173, so i updated it and then rooted it using the one click method. so i've been reading about ota rootkeeper, could i just download that do a temp un root, flash this and then re root? never used the ota rootkeeper so not sure how it works.

[orcsbane13]

ok guys so i'm new to the razr just got it in the mail yesteray. soon as i powered it on got an update to 173, so i updated it and then rooted it using the one click method. so i've been reading about ota rootkeeper, could i just download that do a temp un root, flash this and then re root? never used the ota rootkeeper so not sure how it works.

No need to temp unroot, use it to backup root then flash this and use it to restore root. Pretty simple.

Sent from my XT912 using Tapatalk

[Mr.Rzr]

No need to temp unroot, use it to backup root then flash this and use it to restore root. Pretty simple.

Sent from my XT912 using Tapatalk

Awesome thanks for the update!

Overclocked like a boss

[JungleKing76]

Rootkeeper and the 2.3.6 root method both failed?

No.. it would not root so I had to go back and root on 173, then rootkeeper. I forgot to protect root the first time. :/

Sent from my DROID RAZR using Xparent Purple Tapatalk

[chuckboy1129]

How can i go back to 173 from 174 so i can install this update

[PillClinton]

How can i go back to 173 from 174 so i can install this update

ADB, RSD Lite or mattlgroff's utility!

[JimmyInTheROC]

How can i go back to 173 from 174 so i can install this update

Use mattlgroff's Droid Utility 1.4 to go back to .173. Very easy, and this is a new feature today!

[chuckboy1129]

Use mattlgroff's Droid Utility 1.4 to go back to .173. Very easy, and this is a new feature today!

Thank you

[bikebuilderdude]

.176 already, what are they, fixing one problem per update? By the time we get ICS, they will be up to .200 at this rate. lmao

[snives]

.176 already, what are they, fixing one problem per update? By the time we get ICS, they will be up to .200 at this rate. lmao

Yes... and that is the correct method for debugging. If you change more than one thing at a time, it makes verifying results impossible. This are internal releases, not intended for public.

[arcanexvi]

Yes... and that is the correct method for debugging. If you change more than one thing at a time, it makes verifying results impossible. This are internal releases, not intended for public.

This. And if you keep complaining I'll never give you 177+ (which I may or may not be running already)

[bikebuilderdude]

Makes sense, just hate all the bloatware they add with each OTA update (how many music apps do we really need). Thanks.

[JimmyInTheROC]

.176 already, what are they, fixing one problem per update? By the time we get ICS, they will be up to .200 at this rate. lmao

Don't bite the hand that feeds you dude, it's a gift that we get to see these at all. You need to understand the concept of "leaks" and "daily builds".

Google Chrome has dozens of builds every single day, for example.

[arcanexvi]

Don't bite the hand that feeds you dude, it's a gift that we get to see these at all. You need to understand the concept of "leaks" and "daily builds".

Google Chrome has dozens of builds every single day, for example.

I may or may not also run chrome canary

[bikebuilderdude]

Sorry, i didn't mean it in a bad way, just can't believe how fast the updates are coming out lately.

[JimmyInTheROC]

Sorry, i didn't mean it in a bad way, just can't believe how fast the updates are coming out lately.

No worries from me. I figured you didn't mean it like that.

Flash on!