Root Error while rooting...but still rooted?

[Calamachino]

I went though the unrEVOked3 rooting procedure outlined in the stickied thread "Rooting for dummies" but received a "Unsupported radio version (Status 42)" error at the end of the process. The windows software said done, but my EVO simply displayed that error information.

I rebooted my phone, and noticed I had "Superuser Permissions" in my app list, and both Wireless tether and Titanium backup seemd to work.

So despite the error, is my phone rooted?

I want to flash CM6.1, but i'm afraid of doing anything risky after getting the error.

Thanks.

 

[wrapkgb]

You need to go to the unrevoked website and download unrevoked forever and then flash it. Ut has been happening a lot lately

 

[Calamachino]

You need to go to the unrevoked website and download unrevoked forever and then flash it. Ut has been happening a lot lately

I saw that suggested in other threads, but is that still necessary if i'm able to run rooted apps?

 

[wrapkgb]

Hold on. Man I am getting threads mixed all up today.

Yes you should have to flash unrevoked forever and here is how we will know.

Power your phone off.
Power into hboot (power and volume down at the same time)
At the top of hboot does it say S-ON or S-OFF?

I'm guessing S-ON... If so you need to flash unrevoked forever to obtain S-OFF. Right now you only have partial root and you need full root. Im not sure why the new version of unrevoked is doing this.. They must have a bad forever file in 3.22. Amyways do this and you should be square!

 

[Calamachino]

Hold on. Man I am getting threads mixed all up today.

Yes you should have to flash unrevoked forever and here is how we will know.

Power your phone off.
Power into hboot (power and volume down at the same time)
At the top of hboot does it say S-ON or S-OFF?

I'm guessing S-ON... If so you need to flash unrevoked forever to obtain S-OFF. Right now you only have partial root and you need full root. Im not sure why the new version of unrevoked is doing this.. They must have a bad forever file in 3.22. Amyways do this and you should be square!

Dang, I was afraid of that. Yeah, S is ON.

I didn't wanna do that many steps, I'm kinda paranoid of bricking my phone. Ugh.

Thanks.

 

[wrapkgb]

You wont brick your phone. The hard part is over!

 

[wrapkgb]

Follow these instructions:

1. Download the urevoked forever zip - http://downloads.unrevoked.com/forever/current/unrevoked-forever.zip
2. Place the zip on the root of your SD card (meaning directly on the SD card and not in any folder).
3.Power the phone off.
4. Once the phone is off, power back on into hboot (power button and volume down button at the same time)
5. Use the volume keys to navigate. Select recovery and press the power button to select.
6. Once recovery loads, navigate down to flash zip from SD card and select.
7.Navigate to the unrevoked forever zip
8. Press power to select the file
9. Then select power to confirm install.
10. Let it do its thing, it shouldn't take very long.
11. When its complete reboot and you are good to go!

Seriously don't worry, its just as easy as flashing a rom. It should only take a matter of minutes from start to finish. Your phone will be fine.

 

[jebo_4jc]

I ran into the same problem, but the above steps worked. Thanks!

 

[hortstu]

The way things are going with unrevoked this thread will need a sticky!

 

[jreuschl]

It looks like they provide a way to undo the forever version. Has this been tested working? The reason would be if I need to bring the phone in for repair.

I did some Google searches on unrevoked forever and all of them said this is permanent.

 

[wrapkgb]

It looks like they provide a way to undo the forever version. Has this been tested working? The reason would be if I need to bring the phone in for repair.

I did some Google searches on unrevoked forever and all of them said this is permanent.

Yes it is reversible. You have to use the S-ON tool that can be found on the unrevoked website and the rooting for dummies sticky. Just and FYI though, unrevoked forever is INCLUDED in Unrevoked 3.22 and has been included since Unrevoked 3 was released. It seems Unrevoked 3.22 is having problems flashing it during the rooting process.

 

[hortstu]

unrevoked forever is INCLUDED in Unrevoked 3.22 and has been included since Unrevoked 3 was released. It seems Unrevoked 3.22 is having problems flashing it during the rooting process.

I assume they know about this issue? Why wouldn't they just leave up 3.21 in the meantime?

 

[wrapkgb]

Im not sure if they are aware... its almost impossible to get in touch with those guys and i don;t have a twitter account

 

[hortstu]

Im not sure if they are aware... its almost impossible to get in touch with those guys and i don;t have a twitter account

I avoid twitter myself. Is that the only way they take feedback? If so could someone with a twitter account please let them know about this problem?

 

[Calamachino]

Wow. OK, that was easy. Thanks again!

 

[wrapkgb]

Glad you finally got root! Now go have some fun

 

[Justin.G11]

Technically your _were_ rooted even with the S-ON flag in the radio. "Root" simply meens you have root level access ... aka supersuer.

The difference between root and S-ON/S-OFF, is the later makes a change to the radio antanea which effectively flags your device as a developer phone .... aka future OTA/Downloaded updates will not remove root access.

The way it stands you can root your phone ... then lose it when the next OTA update streams in (as well as having the exploit that was used to gain root removed). Consider having your radio set to S-OFF as insurance that you never have to root again (unless you bring your phone in for repairs ... but with warranties how they are ... I can't imagine ever doing it).

 

[Calamachino]

Good to know.

Im not too worried about the warranty. Its nice to know everything can be reset if I need to take it in.

I just installed the latest cyanogenmod with no issues! However, my phone is randomly rebooting; two times so far. Both times while the phone was completely idle. I was on the computer, and heard it reset across the room.

Is this a common issue?

 

[wrapkgb]

Good to know.

Im not too worried about the warranty. Its nice to know everything can be reset if I need to take it in.

I just installed the latest cyanogenmod with no issues! However, my phone is randomly rebooting; two times so far. Both times while the phone was completely idle. I was on the computer, and heard it reset across the room.

Is this a common issue?

I am running CM6.1 with no issues. Are you on the stock kernel? And did you wipe data, cache and dalvik prior to flashing CM?

 

[Calamachino]

I am running CM6.1 with no issues. Are you on the stock kernel? And did you wipe data, cache and dalvik prior to flashing CM?

I didn't change the kernal.

I did wipe the data and cache with Rom manager, but not dalvik.

 

[wrapkgb]

Technically your _were_ rooted even with the S-ON flag in the radio. "Root" simply meens you have root level access ... aka supersuer.

The difference between root and S-ON/S-OFF, is the later makes a change to the radio antanea which effectively flags your device as a developer phone .... aka future OTA/Downloaded updates will not remove root access.

The way it stands you can root your phone ... then lose it when the next OTA update streams in (as well as having the exploit that was used to gain root removed). Consider having your radio set to S-OFF as insurance that you never have to root again (unless you bring your phone in for repairs ... but with warranties how they are ... I can't imagine ever doing it).

You are correct. But don't be mistaken that you can accept an OTA even though unrevoked forever turns S-OFF at the radio level. In theory yes you should be able to re root with out a problem if you accept an OTA and unroots you. However unrevoked forever does not work as they thought. For instance if you were on software version 3.26 rooted with S-OFF (unrevoked forever) and accepted the 3.29 OTA, the OTA would unroot your phone with S-OFF (no super user access). The problem was with 3.29, along came a ned hboot (.97) which at the time was not rootable. So people were briefly stuck unrooted with S-OFF. Now its not that big of a deal because about 2 weeks later unrevoked released version 3.21 which could obtain root, but for the period between 3.29 and UR3.21 people were stuck half root. Regardless its a bad idea to accept OTA's. And not to mention there is really no reason to accept an OTA. The only thing included in an OTA is updated software and sometimes a new radio and or hboot. Those can all be flashed and usually much sooned than sprint releases it.

 

[Calamachino]

Phone was on and fine for a good amount of time, until I started using the camera and it locked up and reset itself. I gotta try out some new ROMs.

 

[bytes2bits]

Dang, I was afraid of that. Yeah, S is ON.

I didn't wanna do that many steps, I'm kinda paranoid of bricking my phone. Ugh.

Thanks.

I'm in the same exact boat as you. I haven't done the final Unrevoked Forever step but I plan to do it now that I have read through your posts and see that it worked out for you. I'm anxiously following any further news of your progress. Thanks for the very helpful post. Please post if the phone once again becomes stable after changing to a different rom than the one you're currently using.

 

[bytes2bits]

I took the plunge and performed the final Unrevoked Forever patch. It worked perfectly. I now have the addition of S-Off. My next step will be to flash a new ROM. I read on the Unrevoked site that "When doing updates, be sure to flash all partitions at the same time. For instance, on Incredible, running a 0.92 hboot and a 2.15 radio with a 2.6.29 Linux kernel will result in the system becoming unusable until reflashed". Are they referring to flashing roms? If so, do the roms generally come with all of that already in them (hboot, radio, kernel) or am I mixing this all up with something else?

 

[wrapkgb]

They are not talking about roms. Rom only include the rom itself and a kernel.