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

Root Dead thread.

Status
Not open for further replies.
alprazolam said:
And why's that? On my winmo phone, all of my applications were on my flash drive except for those that were cooked in. Why not save precious system memory and space when you can?

My opinion is that root will happen before 2.1 OTA but who knows?
Click to expand...

I am very new at the droid devices, by rooting your eris will you be able to use the unlimited data plan without paying the extra 30 dollars? I currently have vzn as my provider.
 
toadster007 said:
I am very new at the droid devices, by rooting your eris will you be able to use the unlimited data plan without paying the extra 30 dollars? I currently have vzn as my provider.
Click to expand...

nope still gotta pay mang. unless you're only using wifi only. suppose, but why bother, most apps won't work unless you're on 3g/wifi and you can't do that if you're in the middle of the dessert. There's 3g but you can't get it or you will get charged up the *** or you don't care and use it.

unless you're being sarcastic, in which I am terrible at noticing.
 
Just curious, but what qualifications are needed to be considered a "developer" ? And no, I'm not interested or asking for that reason.
 
hallstevenson said:
Just curious, but what qualifications are needed to be considered a "developer" ? And no, I'm not interested or asking for that reason.
Click to expand...

I think anyone with a working knowledge of how to program in the android environment. People who are proficient in linux kernal code, arm shell code, or Google's SDK for android could be considered a developer. The term "developer" is definately the new tech buzz word of our day. Basically developer is a more flattering way of saying coder or programmer, someone who wirtes programs for a living or hobby.
 
Yeah, I consider "developer" to be equal to "programmer" too. I ask because one of the "developers" now listed has made posts only a month ago that make me wonder... :-)
 
Rrrracer said:
Rolling back the OTAs? I thought I read in a post somewhere that this could be done, seem to remember Caddyman in the process...

Why can't we roll back and get root? Anyone?
Click to expand...

If you can't roll back your OTA updates, it's a surprise to me.

My understanding is that when you hard reset with the volume, call, and end buttons, you can decide whether you want the OTA updates to be included with your phone's software load.

The first time I ever did a hard reset, I had to re-do my OTA.

Have we not investigated this idea? I thought rolling back OTA's was possible.
 
pkopalek said:
If you can't roll back your OTA updates, it's a surprise to me.

My understanding is that when you hard reset with the volume, call, and end buttons, you can decide whether you want the OTA updates to be included with your phone's software load.

The first time I ever did a hard reset, I had to re-do my OTA.

Have we not investigated this idea? I thought rolling back OTA's was possible.
Click to expand...

But here I read from the xda thread...

bftb0 said:
Binny,

I've done it more than once already :) from 1.17.605.1 -> 1.16.605.1

Steps:

[Binny knows this, but if anyone else is reading, it is the same as a factory reset - you will lose all your settings and apps (but not the contents of the SD card)]

1) Unpack the 1.16.605 RUU - by running it as if you were going to actually do the RUU using the USB cable and your host PC, but stop right before you would apply the update to the phone. Pull the "rom.zip" file out of the temporary area that the RUU installer unpacks.
(Poke around under C:\Documents and Settings\<Username>\??? (I can't remember - you'll see folders with names that look like registry entries). You have to do this while the RUU installer is sitting there waiting for you - if you cancel the install, it will nuke everything it unpacked. I just made copies of the entire subtrees.

2) Cancel the RUU install.

3) Move the ROM.ZIP file to the root folder of your SD card, and rename it PB00IMG.ZIP

4) You can cancel the RUU install session on the PC, and unplug the USB cable if you want (so long as you have a well-charged battery!)

3) Power down the phone, and boot it back up holding the Call and End buttons simultaneously

4) Scroll down (or whatever it asks) to go from Fastboot mode to HBOOT mode

5) The phone will automatically discover the PB00IMG.ZIP file, and unpack it and verify it.

6) It will ask you if you want to install; when you (select and) enter Yes, the phone will reboot, and come up again - appearing as if it is repeating the same thing. This time, however, it won't stop and ask you - it will just begin the install.

7) Wait... Wait... Wait... Wait... and then wait some more. If I recall correctly, it seems to hang a little bit at the HTC splash screen after the reboot. That is normal - just WAIT and let the phone do it's thing.

That's it, except for:

8) You probably will want to dial *228 and choose option 1 to complete the programming of your phone - it will reboot after it completes.

9) Be prepared for the phone to nag you incessantly about an OTA update being available - something like every 10 minutes or so that message will pop up.


Now, to answer the original poster's questions: I did this to try very similar exploits on 1.16.605.1. It doesn't seem to behave any differently than the 1.17.605.1 - everything I have tried has failed on both. That is not a proof though that there isn't some other opportunity by doing this.

cheers,

bftb0
Click to expand...
 
The previous updates were able to be rolled back because they were just minor patches. The fear is that after the new update, the ability to roll back to the old kernel could be blocked. We won't be able to find out until 2.1 starts rolling out.

But it has also been pointed out that our new kernel should be vulnerable to the Tattoo exploit that our dev team though they had working for the eris. So it may be easier to root once it's updated, unless HTC has already patched it.

If the OTA were to come before root, I plan to wait until either a roll back is confirmed or the Tattoo method is proven to work.
 
mj_b90 said:
But it has also been pointed out that our new kernel should be vulnerable to the Tattoo exploit that our dev team though they had working for the eris. So it may be easier to root once it's updated, unless HTC has already patched it.

If the OTA were to come before root, I plan to wait until either a roll back is confirmed or the Tattoo method is proven to work.
Click to expand...
Personally, this is why I think the root team should be kept small, private, and selective about members and announcements. HTC can now know to fix this potential hole...
 
mj_b90 said:
The previous updates were able to be rolled back because they were just minor patches. The fear is that after the new update, the ability to roll back to the old kernel could be blocked. We won't be able to find out until 2.1 starts rolling out.

But it has also been pointed out that our new kernel should be vulnerable to the Tattoo exploit that our dev team though they had working for the eris. So it may be easier to root once it's updated, unless HTC has already patched it.

If the OTA were to come before root, I plan to wait until either a roll back is confirmed or the Tattoo method is proven to work.
Click to expand...

hallstevenson said:
Personally, this is why I think the root team should be kept small, private, and selective about members and announcements. HTC can now know to fix this potential hole...
Click to expand...

I am behind this.

But XDA is way too easy to read for anyone anyway, unfortunately.
 
Thanks all, good information. I'm learning more and more about the process every day... seems as if HTC has been quite thorough in eliminating exploits in the Eris' kernel.

Maybe 2.1 will open up an avenue that the devs can exploit... I certainly hope so :)

mj_b90 said:
If the OTA were to come before root, I plan to wait until either a roll back is confirmed or the Tattoo method is proven to work.
Click to expand...

This is the route I will take as well... as much as I'd like to jump on 2.1 when it hits...

I optimize things for a living (but in this case it's race cars, not smartphones LOL). The idea of removing unnecessary bloat from the phone and a nice overclock is too appealing to me to give up on root just yet :cool:
 
I never really thought about Root very much, and have been waiting for the 2.1 update to fix a lot of things.

Today, though, my friend rooted his droid and I physically got to play with it. Even before he over clocked the processor, it was already running smoother and less laggy.

I am no officially excited for us to get root..hopefully soon :D
 
I will hold off on updating I really want root, now if they find a way to root the 2.1 I'll update then root.. But to me Root is more important then the update. I think it's the only way to make the phone run smoother, taking a lot of the backgroun process, duplicate applications and useless applications out and running some programs from my SDcard
 
So if I understand the rollback correctly, then you could revert to the previous kernal that matches the kernal version on the tattoo. Then the tattoo exploit would work since they would then have the same kernal version. After that no matter what update HTC issues, the exploit will work as long as you can rollback the kernal. Am I missing something with my line of thinking?
 
That was my original line of thinking. Apparently the original Eris kernel was different than the one on the Tattoo and the exploit had been patched, so it won't work.
 
Rrrracer said:
That was my original line of thinking. Apparently the original Eris kernel was different than the one on the Tattoo and the exploit had been patched, so it won't work.
Click to expand...

I thought the exploit was only patched in MR2. So even the original kernal version for the eris is different then the tattoo?
 
Status
Not open for further replies.
Back
Top Bottom