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

Root [CDMA] Not feelin it yet, who's with me?

I have been reading most all the posts about the Perm rooting and revolutionary, and the subsequent issues with phone calls, clockwork mod, error codes and the like. Having come from a fully rooted one step process for my EVO 4G via unrevoked, This does not feel ready yet for those of us who are not quite noobies but not developers either.

I did use the temp root as outlined here [TOOL 07/11] Easy Fre3vo w/ Perma-Temp, Bloatware Disabler & Overclock (Win/Mac/Lin) - xda-developers and it worked great. Have had to redo only once and very please at present.

I think I'll wait just a little longer for the complete one step, no bugs release, just to make my life a little less complicated. Who else is waiting?
 
  • Like
Reactions: EarlyMon
I'm honestly surprised how easy this root procedure was. Anyone else remember the early EVO 4g rooting procedures? Download this, install these drivers, push these files via ADB, turn on these modes in sequence, flip airplane mode on and off during x timeframe, hold ctrl+alt+delete while hitting the home button with your nose, and after all that PRAY that the root worked (or some sequence like that). As for the bugs... meh. What's the fun without a little risk taking? ;)
 
Upvote 0
It was pretty painless for me... Revolution worked great and installed cwm for me with no issue. I did a nandroid first then installed su (correct version) and it worked right from the start. I did get the error 16 which was fixed in a few minutes on the phone and all has been great.

Last night when mik released his rom I figured it was time to start flashing and after seeing that everyone seemed to be leaning towards twrp I flashed it and did a fresh nandroid, then wiped and installed mik. I haven't had any real issues yet...

The only small problem I had was I rebooted with the phone plugged into usb and it went unresponsive, but a battery pull brought it back. Everything else has been cake.

I doubt they'll be able to do anything about the error 16. Honestly I wouldn't worry about it.
 
Upvote 0
Anyone whose gut tells them to wait ought to wait.

This is a developer root, just like temp root was.

Despite success stories, there is huge variability in the results and because this is a developer root, there's no explanations.

Which recovery will you get? Will your phone need re-activating? If so, will hands-free work, or will you be calling Sprint?

When I rooted my Evo and got full nand access in June 2010 I went thru 78 steps. But I knew what I would get and I got it.

This is in no way, shape, or form a ready for prime time root.

Trust your instincts.
 
Upvote 0
I'm waiting, temp root works for me as I only use it to get the wifi. So for now that will do. Plus, if HTC eventually unlocks their phones it will probably be less risky.
I rooted my 4G before the 1 click method was available and it wasn't that difficult. For some reason when I read through this method it seems more involved. Anyway, if HTC doesn't come through, and the root process doesn't simplify then eventually I'll do it no matter what.
 
Upvote 0
Got error code 16 here but other than that the permanent root has been flawless for me.

Something everyone should know about error code 16 is that they are random and can occur anytime your phone is hard reset. This is with any phone on Sprint now, not just the EVO 3D. Whatever process this root takes causesu the phone to think its been hard reset and need reactivation. Error code 16 IS NOT used to track rooting. Do not be concerned if you get the code just talk to the rep and they will reactivate your phone no problem.
 
Upvote 0
Got error code 16 here but other than that the permanent root has been flawless for me.

Something everyone should know about error code 16 is that they are random and can occur anytime your phone is hard reset. This is with any phone on Sprint now, not just the EVO 3D. Whatever process this root takes causesu the phone to think its been hard reset and need reactivation. Error code 16 IS NOT used to track rooting. Do not be concerned if you get the code just talk to the rep and they will reactivate your phone no problem.

Maybe true but this error code issue has been pretty wide spread for those that did root. Before this permanent root how many threads have you seen with someone with a 3vo complain about error code 16? Like I said earlier I have performed several hard rests to 3 different 3vos and haven't had this issue at all. This weekend I rooted 5 3vo's(not including mines) and every last one of them had the error code issue. In my opinion this is more than just something random.
 
Upvote 0
Maybe true but this error code issue has been pretty wide spread for those that did root. Before this permanent root how many threads have you seen with someone with a 3vo complain about error code 16? Like I said earlier I have performed several hard rests to 3 different 3vos and haven't had this issue at all. This weekend I rooted 5 3vo's(not including mines) and every last one of them had the error code issue. In my opinion this is more than just something random.

Totally agree. :) ;)

Yeah, let's not get backwards who did what and start blaming Sprint.

They are releasing an unlocked bootloader soon enough.

Any trouble caused here came from us using a _developer_ root. Not Sprint.

I'd respectfully suggest that the conspiracy thinking gets reined in before insanity ensues.

All phones have security for carrier locking.

You just waltzed past a heavily encrypted system originally designed to not let anyone do that.

And it triggered carrier lock security in some cases.

Where's the surprise? Where's the conspiracy?

Not saying you were out there, it's just a repost to the point.
 
Upvote 0
The only prob. I had that didnt seem to effect anything was when I was on the last step it said something to the effect of,(failed) after the zip was installed I rebooted the phone and everything is working fine so I say yea the phone works great after root.

I got an error flashing the su .zip first try. so I tried again and succeeded. You should check to see if you have the superuser app in your app drawer. if not, you should flash the su .zip again.
 
Upvote 0
I got an error flashing the su .zip first try. so I tried again and succeeded. You should check to see if you have the superuser app in your app drawer. if not, you should flash the su .zip again.
Yea, that was the first thing I checked and it was there so far everything is great , ive been reading through and noticed people having prob. In not claiming to be an expert but I wonder if some people are rooting incorrectly if thats possible. and then blaming it on something other than themselves.
 
Upvote 0
Given that 2 su-zip files went up the other night, and one was corrupted, I would not be so quick to throw rocks at people.

And if you got the documented su-zip flash error and ignored it as you said, I am very impressed. Instructions said to redo for the only error I've read about.
Yea I was worried after the message that I dug myself a hole but thankfully all went well , Come on now my post was not being quick to insult people , Im saying the possibility for human error is there , Im not an insulting guy but the truth is people make mistakes and rarley like to take blame, but I dont want to get off topic I know how you moderator's are LOL.
 
Upvote 0
well, I have hacked phones for a very very long time, and I still haven't done my 3Evo..I am waiting for a native Mac root method, and, also to watch and see the issues that come up the first few days before seriously considering it.
Its funny how some folks jump down your throat if you don't want to root your phone the first second it becomes available.
Check out this thread I started over at XDA, about waiting for a mac root method, and you'll see what I mean!

(REQ) EVO3D ROOT PLEASE Don't Forget about us MACOSX USERS!! - xda-developers
 
Upvote 0
well, I have hacked phones for a very very long time, and I still haven't done my 3Evo..I am waiting for a native Mac root method, and, also to watch and see the issues that come up the first few days before seriously considering it.
Its funny how some folks jump down your throat if you don't want to root your phone the first second it becomes available.
Check out this thread I started over at XDA, about waiting for a mac root method, and you'll see what I mean!

(REQ) EVO3D ROOT PLEASE Don't Forget about us MACOSX USERS!! - xda-developers


That thread made my morning... still reading lol
 
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