Un-root And update download the file from here: http://forum.xda-developers.com/showthread.php?t=975888 and apply. This will give you stock and S-on.
That simple!
Thanks for the info, but the fun is just beginning. This is always good to have just in case you have to return it.
You should be able to load any stock RUU. As long as the hboot and the recovery exist in the RUU, it should return you to a stock condition.
Jaywan, how about a simple root and s-off?
It's simple to make a app run the commands needed to make a one click rooter. And easier to edit a already working rooter to work for this phone. Idk why he don't want the one click released. Took me 30 minutes to root.. maybe he only want people to root using his method. I not gonna step on his toes by posting one tho...
Sent from my ADR6400L using XDA Premium App
ok ok, I hear yah. I will just bite the bullet and type in all 90 of the commands tomorrow when I get off work.
BTW, I left the MT4G and came over to verizon also. I went to the SGS4G before I left tmobile. Lack of dev support for that phone made me give it up. Thanks for coming over to the Thunderbolt.
also, take a look at this thread I started. Somethings up with this one click unroot deal.
http://forum.xda-developers.com/showthread.php?t=1004567
Jaywan said:
It's simple to make a app run the commands needed to make a one click rooter. And easier to edit a already working rooter to work for this phone. Idk why he don't want the one click released. Took me 30 minutes to root.. maybe he only want people to root using his method. I not gonna step on his toes by posting one tho...
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I heard him meantion he wants people to learn adb so if something happens further down the line they can use it
Seriously I'm with him, the hardest part about adb for me was getting it installed. The root was easy and took 30 min
sent from my Thunderbolt
For what its worth, he said feel free to post the one clicks, just give credit. I dont honestly care however, copy, paste, seemed simple enough. Was no where near as hard as the original root method for the DInc.
Sent from my ADR6400L using XDA App
The only legitimate reason I could buy about not wanting a one click released, is if SOMEHOW it would make our phones vulnerable to some sort if attack.
As background, I've ben using custom roms since my old g1 was new and JesusFreke was just getting started and I dont ever recall ANY dev with holding something that would make the users lives easier. In recent history I've done a ton of flashing roms with both mine and my wifes old vibrants and the only time I used adb was if I wanted to push a file to the phone without mounting it on my computer.
PERSONALLY, this whole mess sounds of ego and elitism. I am incredibly greatful to the devs who have paved the way, but fearful of what they are trying to do. No one should have the right to prevent another from releasing something, it's in gross violation of the gpl. If a dev wants to code something under a different license, fine. However it needs to be clearly annotated as such, and devoid of any gpl work itself. In other words, it basically can't contain anything related to android unless it was developed 100% blind through an emulator.
Sent from my ADR6400L using Tapatalk
Can't step on my toes, I got stealtoe boots...
I want a chance to review any one clicks before release. I REALLY want new users to understand what they are doing BEFORE they try one clicking.
I want proper md5sum verifications, I want proper warnings, etc.
I already stopped the release (until fixed) of one 1click root that would of been REALLY bad for the community and anyone using it.
Ppl need to stop blaming me for this crud.
ShanDestromp said:
The only legitimate reason I could buy about not wanting a one click released, is if SOMEHOW it would make our phones vulnerable to some sort if attack.
As background, I've ben using custom roms since my old g1 was new and JesusFreke was just getting started and I dont ever recall ANY dev with holding something that would make the users lives easier. In recent history I've done a ton of flashing roms with both mine and my wifes old vibrants and the only time I used adb was if I wanted to push a file to the phone without mounting it on my computer.
PERSONALLY, this whole mess sounds of ego and elitism. I am incredibly greatful to the devs who have paved the way, but fearful of what they are trying to do. No one should have the right to prevent another from releasing something, it's in gross violation of the gpl. If a dev wants to code something under a different license, fine. However it needs to be clearly annotated as such, and devoid of any gpl work itself. In other words, it basically can't contain anything related to android unless it was developed 100% blind through an emulator.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Are you a troll or do you really believe all that crock you just posted?
The issue with one clicks was an increased risk of bricking with this method. And where does the GPL even come in here at, any GPL code we used as released before the root was even up.?
I stopped a one click from being released today that not only left your phone vulnerable to an attack, but also left you with an outdated, faulty radio and other faulty firmware.
Either you are a troll, have a personal issue with me, or have a seriously problem.
jcase said:
Can't step on my toes, I got stealtoe boots...
I want a chance to review any one clicks before release. I REALLY want new users to understand what they are doing BEFORE they try one clicking.
I want proper md5sum verifications, I want proper warnings, etc.
I already stopped the release (until fixed) of one 1click root that would of been REALLY bad for the community and anyone using it.
Ppl need to stop blaming me for this crud.
Click to expand...
Click to collapse
omfg most of us been rooting since g1 came out THE FIRST DAY come on if modaco was working on this aka paul. like his app visionary he would have it out.... who cares most of us know adb... but i dont want to turn s off i just want root access to remove **** and do a couple mods. why is this such a big fuc88ing deal just release the app and we will all be grateful of who release one click root
jesemalave1 said:
omfg most of us been rooting since g1 came out THE FIRST DAY come on if modaco was working on this aka paul. like his app visionary he would have it out.... who cares most of us know adb... but i dont want to turn s off i just want root access to remove **** and do a couple mods. why is this such a big fuc88ing deal just release the app and we will all be grateful of who release one click root
Click to expand...
Click to collapse
o.m.g.
Dude it doesn't work that way on this phone. It is not the G1, z4/visionary/anyonphoneroot does not work, root REQUIRES adb (even with one click).
Fact is, you can't root this phone, temp or perm, one click or not, without ad.
If you can find a way, please do. We are awaiting your one click, root that does not use adb, and is not dangerous.
fyi one click has been released, hours before your post.
Code:
while (true) {
facepalm();
}
I'm going to cut out all your attacks, because you've clearly missed my point in its entirety and decided to get defensive.
jcase said:
The issue with one clicks was an increased risk of bricking with this method. And where does the GPL even come in here at, any GPL code we used as released before the root was even up.?
Click to expand...
Click to collapse
I brought the GPL in because like it or not, you don't have the right to say who can and cannot release anything regarding "one click" roots UNLESS you yourself made an essential piece of the current rooting method, that is in its entirety your own. To make an analogy, you can't patent (and thus control the distribution) to a Toyota Carolla, simply because you assembled the whole thing from spare parts. If you were to completely design and fabricate a motor vehicle without using off-the-shelf parts you WOULD have that right.
There is nothing personal in my view of this against you, I don't hold any grudges against anyone; but its the mentality here that irritates me, and it just happens that you're the one that posted it:
jcase said:
I want a chance to review any one clicks before release. I REALLY want new users to understand what they are doing BEFORE they try one clicking.
Click to expand...
Click to collapse
I understand you want people to learn; I really do. I've done enough work with computers that I too get really irritated at people who demand answers to questions answered much faster by doing a quick search. I also understand why you want to avoid screw ups because of a poorly made one click. HOWEVER, just because you WANT people to get them cleared through you first; does not mean they HAVE to or that you have a right to demand that they do.
jcase said:
I stopped a one click from being released today that not only left your phone vulnerable to an attack, but also left you with an outdated, faulty radio and other faulty firmware.
Click to expand...
Click to collapse
And thus you've found the wonder of open source software. Sometimes crap gets released. But guess what? Every one of us here are supposed to be adults, or at the very least the authorized users of our phones; which means that if we screw something up, or use something that screws up; its our own damn fault.
The whole purpose of OSS is to allow freedom of ideas and development. I don't know how old you are, or what your experience with OSS outside of Android phones are; but I personally have seen PLENTY of OSS software that started out as utter crap, turn into wonderful software packages. Maybe you're old enough to remember KDE2 vs KDE4, or how about pre v1 Mozilla vs modern versions of Firefox.
I'm not some OSS nutter; I've got no problem with closed source or proprietary software; just a problem with others trying to control things they have no right to.
All that having been said, maybe you DO hold software rights related to some piece of the current rooting method. If so I've seen nothing indicating so, nor anything indicating that any part of the rooting method is not OSS; however if you DO, then you have my apologies, as you would indeed have control over distribution of that specific piece. You still would not be able to prevent distribution of any one click that were released provided they simply had users download your piece separately.
You are missing the point, and obviously did not read anything. This will be my last time wasting time with you until then.
I never said THEY CANT release, I asked them not to, until we had a safer way and time to check it out. Big difference. I stopped one from going out today that would of more or less ruined phones until someone fixed them.
Fact is, MOST of the one clicks I have seen lately, violate the GPL, why don't you go after them, or hell even better we could really use you to go after HTC (in all seriousness).
ShanDestromp said:
I'm going to cut out all your attacks, because you've clearly missed my point in its entirety and decided to get defensive.
I brought the GPL in because like it or not, you don't have the right to say who can and cannot release anything regarding "one click" roots UNLESS you yourself made an essential piece of the current rooting method, that is in its entirety your own. To make an analogy, you can't patent (and thus control the distribution) to a Toyota Carolla, simply because you assembled the whole thing from spare parts. If you were to completely design and fabricate a motor vehicle without using off-the-shelf parts you WOULD have that right.
There is nothing personal in my view of this against you, I don't hold any grudges against anyone; but its the mentality here that irritates me, and it just happens that you're the one that posted it:
I understand you want people to learn; I really do. I've done enough work with computers that I too get really irritated at people who demand answers to questions answered much faster by doing a quick search. I also understand why you want to avoid screw ups because of a poorly made one click. HOWEVER, just because you WANT people to get them cleared through you first; does not mean they HAVE to or that you have a right to demand that they do.
And thus you've found the wonder of open source software. Sometimes crap gets released. But guess what? Every one of us here are supposed to be adults, or at the very least the authorized users of our phones; which means that if we screw something up, or use something that screws up; its our own damn fault.
The whole purpose of OSS is to allow freedom of ideas and development. I don't know how old you are, or what your experience with OSS outside of Android phones are; but I personally have seen PLENTY of OSS software that started out as utter crap, turn into wonderful software packages. Maybe you're old enough to remember KDE2 vs KDE4, or how about pre v1 Mozilla vs modern versions of Firefox.
I'm not some OSS nutter; I've got no problem with closed source or proprietary software; just a problem with others trying to control things they have no right to.
All that having been said, maybe you DO hold software rights related to some piece of the current rooting method. If so I've seen nothing indicating so, nor anything indicating that any part of the rooting method is not OSS; however if you DO, then you have my apologies, as you would indeed have control over distribution of that specific piece. You still would not be able to prevent distribution of any one click that were released provided they simply had users download your piece separately.
Click to expand...
Click to collapse
I agree!! If anyone is in violation of GPL license it is HTC.
And once we have that kernel source in the hands of the community amazing things will happen!!
Once the custom kernels start flying you will see the TB doing crazy things. I can only imagine 2GHz speeds or insanely efficient battery life (to name a few)!
ShanDestromp says "And thus you've found the wonder of open source software. Sometimes crap gets released. But guess what? Every one of us here are supposed to be adults, or at the very least the authorized users of our phones; which means that if we screw something up, or use something that screws up; its our own damn fault. "
This has got to be the stupidest statement I have read in a long time, I can guarantee, If you used a 1-click method and it bricked your phone you would be screaming " where's the oversight in this forum, I cant' believe that that mods would allow faulty programming to be posted."
Jcase I for one am glad you are stepping up and doing what needs to be done to prevent a potential $750 brick, thank you sir.
jcase said:
I never said THEY CANT release, I asked them not to, until we had a safer way and time to check it out. Big difference. I stopped one from going out today that would of more or less ruined phones until someone fixed them.
Click to expand...
Click to collapse
I'm not privy to any private conversations, nor do I read every thread here on XDA, so my general impression, which I'm sure is shared based upon what others have said, was of a more explicit "No you cannot," not a "do you mind if I take a peek first". Furthermore, I did not name any one individual "responsible" for any blockade; I only began to interact with you once you brought yourself into the thread. Beyond that, if you go back to my original post, I explicitly thank the people who made root possible at all.
jcase said:
Fact is, MOST of the one clicks I have seen lately, violate the GPL, why don't you go after them
Click to expand...
Click to collapse
For starters I don't know much, if anything about them other than they exist. Unless I personally see something that I think is in violation, I assume good faith. I certainly don't seeking violations.
jcase said:
or hell even better we could really use you to go after HTC (in all seriousness).
Click to expand...
Click to collapse
I'm guessing you're referring to the fact that they didn't release the kernel source as expected this week? I'd mentioned it in another thread, though I don't recall which anymore; but from what I recall of GPLv2 developers have 60 days from the "official" binary release to provide source. To expand on that, HTC has 60 days from when the phone officially went on sale, to provide upon request the source code to any GPL licensed software, however it is version specific. That is to say 60 days from March 17th to make available the source to the firmware that was on the phone when released (since to the best of my knowledge there have been no other OFFICIAL firmware versions released).
Of course any such source will inherently exclude any third party proprietary software, for example if HTC used a closed-source bluetooth stack (not saying they did, just a hypothetical example). Additionally, there isn't any specific method to release stipulated. If HTC wishes they could mail out copies of the source on 3.5" floppies and still be within the rules; and all this assumes GPLv2 is how Android is licensed. If its v3 then I honestly have no clue if any time provisions exist.
I just want to reiterate, I have no ill-will to you nor anyone else. It appears as though the whole issue stems from miscommunication.
Related
Just looking for a list (if any) of Devs who are actively (or passively) working on Rooting Eris with the 1.49 bootloader.
jvward has a wave thread here:
forum.xda-developers.com/showthread.php?t=703219
where he is diligently tracking any information regarding the root status of Eris.
As a part of this thread, we wanted to gather information on who is working on the root and donation links (where possible).
Let's not let this thread get ugly.
if there is already a thread why are you posting another thread?
Father_Vic said:
Just looking for a list (if any) of Devs who are actively (or passively) working on Rooting Eris with the 1.49 bootloader....
Click to expand...
Click to collapse
No. not too much. I watch the exploit sites but noting has shown up and I am not digging through the source in hopes of finding a bug. Mostly because i have rooted my phone and am am not that altruistic.
One thing to keep in mind is that the eris was never rooted in the true sense of the word. the Devs did nothing technical to root the phone. A pre-rooted leak was obtained. HTC has this thing locked down very well.
Photex said:
if there is already a thread why are you posting another thread?
Click to expand...
Click to collapse
There are threads on Root Status. For all intents and purposes they are dead except for a trickle of despondent users looking for answers.
There is no thread asking for a list of Devs working on root.
If this thread irritates you, don't look at it. Don't go looking for a fight; it's not productive.
thisismyanonymousaccount said:
No. not too much. I watch the exploit sites but noting has shown up and I am not digging through the source in hopes of finding a bug. Mostly because i have rooted my phone and am am not that altruistic.
One thing to keep in mind is that the eris was never rooted in the true sense of the word. the Devs did nothing technical to root the phone. A pre-rooted leak was obtained. HTC has this thing locked down very well.
Click to expand...
Click to collapse
Yeah, this is the biggest problem in my estimation. No real root was explored which leaves a good portion of Eris users swinging in the breeze.
I was happily rooted until I cracked the screen on my phone. My replacement came flashed with 2.1 and a shiny new 1.49.0000 S=ON bootloader. As a result I am twisting in the wind waiting for a root that will never happen because I fear no one worth their weight in gold is working on it.
I guess the only hope is that if Froyo OTA (if it is ever released for the Eris) will require a new bootloader and push the Dev community into action. One can dream, or go back to my iPhone *shudder*
Father_Vic said:
I guess the only hope is that if Froyo OTA (if it is ever released for the Eris) will require a new bootloader and push the Dev community into action. One can dream, or go back to my iPhone *shudder*
Click to expand...
Click to collapse
HTC has already said they're only bringing phones released in 2010 up to 2.2, so it's fair to assume we're SOL. FWIW, my iPad was jailbroken within 20 minutes of me owning it, while my Eris is woefully unmodifiable.
Mostly you wont find out who is working on rooting the 1.49 bootloader simply because the Devs who might be doing so dont want to be bothered daily/hourly with questions about it. Thats why alot of the threads about it have died down, no one was answering them.
abn75 said:
Mostly you wont find out who is working on rooting the 1.49 bootloader simply because the Devs who might be doing so dont want to be bothered daily/hourly with questions about it. Thats why alot of the threads about it have died down, no one was answering them.
Click to expand...
Click to collapse
Good point.
abn75 said:
Mostly you wont find out who is working on rooting the 1.49 bootloader simply because the Devs who might be doing so dont want to be bothered daily/hourly with questions about it. Thats why alot of the threads about it have died down, no one was answering them.
Click to expand...
Click to collapse
I'm sure i will take heat but this is bullsh*it. Not the keeping quit because they don't want to be bugged but to think there is a team of people working on it and not posting their results in a bit naive. So far we have had "confirmation" a race condition exists when NOBODY ever got any (non root) version of the leak to get abd running in recovery. we have zinfabs bug that nobody has found a way to exploit and that was over a month ago.
The last very concerted effort ended up in the Tattoo being rooted and was very public throughout the whole process.
Please... Someone prove me wrong.
If you are sitting here thinking that root is just around the corner i fear you may be wasting your time. I am sure once a development occurs it will be plastered all over the forum.
I hope this didn't offend too many people and it in no way was meant to diminish the contributions of all the devs who donate their time energy an resources to the Eris.
Regards
Personally, I don't think anyone is actively working on rooting the Eris. In the case of the race condition that the Incredible had, it prompted some activity. Or, the issue that zifnab posted about 1-2 months ago, that got some people poking again.
I think the best hope is for someone at HTC to leak a rooted ROM again.
Seems to me like my next phone is going to be a Motoral Droid something because these Droid Verizon HTC phones are getting no action. Just saying, HTC was like no way in hell that anyone will be able to tinker with our phones on Verizon lol
thisismyanonymousaccount said:
I'm sure i will take heat but this is bullsh*it. Not the keeping quit because they don't want to be bugged but to think there is a team of people working on it and not posting their results in a bit naive. So far we have had "confirmation" a race condition exists when NOBODY ever got any (non root) version of the leak to get abd running in recovery. we have zinfabs bug that nobody has found a way to exploit and that was over a month ago.
The last very concerted effort ended up in the Tattoo being rooted and was very public throughout the whole process.
Please... Someone prove me wrong.
If you are sitting here thinking that root is just around the corner i fear you may be wasting your time. I am sure once a development occurs it will be plastered all over the forum.
I hope this didn't offend too many people and it in no way was meant to diminish the contributions of all the devs who donate their time energy an resources to the Eris.
Regards
Click to expand...
Click to collapse
Yeah, just as I thought. We have been left behind by the devs. No one is willing to come forward.
http://forum.xda-developers.com/showthread.php?t=709450 look in here
Father_Vic said:
Yeah, just as I thought. We have been left behind by the devs. No one is willing to come forward.
Click to expand...
Click to collapse
They've no doubt been trying but at what point do they decide it's not worth the effort ? Isn't that their choice to make ?
Ok, so I was going a lot of playing around with my phone last night. On the scale of hacking, I am not even in the same realm as the skilled folks here. I tinker with things now and then... and sometimes I get ideas... like now.
So, my EVO is setup to work with my corp exchange server for work emails. I noticed that under Settings / Security / Select Device Administrators, the exchange security policy is in there. This section also seems to suggest that you can "add / remove" but it appears to only allow removal from the UI.
Then I got to some more thinking... an app essentially installed itself and granted itself this right. Why cant we study what that app is doing a do something similar? Or at a minimum, exploit those very roles that are already there on the device?
Am I even thinking along the right lines? Or am I way off?
Makes sense to me but I'm also a novice but good contribution dude. Maybe it could get the ball rolling on this thing.
Sent from my PC36100 using XDA App
Joeriginal said:
Makes sense to me but I'm also a novice but good contribution dude. Maybe it could get the ball rolling on this thing.
Click to expand...
Click to collapse
heck yeah, cause it's long overdue. You even mention 2.2 root in here, and you get barked at like you're in "The Village" and that is "the thing of which we don't speak." LOL
Well, frankly, it's the only reason I check XDA daily: to see if someone finally rooted 2.2, so like it or not, it's gonna be what many people are waiting for....
So, way to go on the idea. This at least gives hope that we are still looking for an exploit.
IRepTheKing said:
heck yeah, cause it's long overdue. You even mention 2.2 root in here, and you get barked at like you're in "The Village" and that is "the thing of which we don't speak." LOL
Well, frankly, it's the only reason I check XDA daily: to see if someone finally rooted 2.2, so like it or not, it's gonna be what many people are waiting for....
So, way to go on the idea. This at least gives hope that we are still looking for an exploit.
Click to expand...
Click to collapse
Come on, you know that's not true. The reason people get crap for asking about rooting 2.2 is that the info and answers are all already here on the front pages.
But I like that people are still thinking and suggesting like the OP. That's how things are going to keep moving.
Side note: My Evo just spell-corrected "crap" to "veal." It was like an Easter egg or something.
now we just need a hacker
So... thanks for the chime-ins on the idea. I thought it was a good one too. I am curious now to see what one of the big hackers has to say about it. Knowing my luck, it would be a squashed dream.
SilverZero said:
Come on, you know that's not true. The reason people get crap for asking about rooting 2.2 is that the info and answers are all already here on the front pages.
But I like that people are still thinking and suggesting like the OP. That's how things are going to keep moving.
Side note: My Evo just spell-corrected "crap" to "veal." It was like an Easter egg or something.
Click to expand...
Click to collapse
Hummm "crap" to "veal" I love it you know what some developer thinks of veal LOL
IRepTheKing said:
heck yeah, cause it's long overdue. You even mention 2.2 root in here, and you get barked at like you're in "The Village" and that is "the thing of which we don't speak." LOL
Well, frankly, it's the only reason I check XDA daily: to see if someone finally rooted 2.2, so like it or not, it's gonna be what many people are waiting for....
So, way to go on the idea. This at least gives hope that we are still looking for an exploit.
Click to expand...
Click to collapse
That's the main reason I check in daily too...
Sent from my PC36100 using XDA App
Not bad......
Just had an idea ( warning I am a noob.) So the previews exploit was found by running flash. If any developer can create an app and install the old flash to allow the old exploit. Then this will allow us to flash.
edufur said:
Ok, so I was going a lot of playing around with my phone last night. On the scale of hacking, I am not even in the same realm as the skilled folks here. I tinker with things now and then... and sometimes I get ideas... like now.
So, my EVO is setup to work with my corp exchange server for work emails. I noticed that under Settings / Security / Select Device Administrators, the exchange security policy is in there. This section also seems to suggest that you can "add / remove" but it appears to only allow removal from the UI.
Then I got to some more thinking... an app essentially installed itself and granted itself this right. Why cant we study what that app is doing a do something similar? Or at a minimum, exploit those very roles that are already there on the device?
Am I even thinking along the right lines? Or am I way off?
Click to expand...
Click to collapse
Not to burst your bubble or anything, but I'm pretty sure this is mostly related to corporate security so that IT can lock the phone down even more than carriers/manufacturers do. Think stuff like not being able to install apps, email restrictions, password management, etc.
Breaking this security feature will at most give you the access non-corporate users enjoy with their unrooted phones.
I'm sure there are plenty of dev's looking for exploits on a daily basis. No need to get peoples hopes up early is why there isn't much talk about it. Same reason people get dumped on for asking on a daily basis. If there was one found already it would be posted so quit asking sort of issue.
I like the thoughts though.
SilverZero said:
Side note: My Evo just spell-corrected "crap" to "veal." It was like an Easter egg or something.
Click to expand...
Click to collapse
You know I noticed that the other day when I sending a text and thought the same thing.. I couldn't figure out how spelling crap was even close to the spelling of veal! So yes I think it was on purpose too! I wonder how many other 'Easter eggs" are programmed into this phone......where is the root egg...hehe....
bluediablito said:
Not bad......
Just had an idea ( warning I am a noob.) So the previews exploit was found by running flash. If any developer can create an app and install the old flash to allow the old exploit. Then this will allow us to flash.
Click to expand...
Click to collapse
I asked same thing other day... They said that htc closed thee flash exploit and reverting to an older version won't be able to access that same exploit since they closed and patched thee exploit
Sent from my second wife using swype on xda app
sprink0281 said:
You know I noticed that the other day when I sending a text and thought the same thing.. I couldn't figure out how spelling crap was even close to the spelling of veal! So yes I think it was on purpose too! I wonder how many other 'Easter eggs" are programmed into this phone......where is the root egg...hehe....
Click to expand...
Click to collapse
To further derail this thread, this "easter egg" is actually a feature from Google, the reasoning being that is probably better to send a nonsensical word over a swear word in case you didn't actually mean to write the swear word.
sk63 said:
To further derail this thread, this "easter egg" is actually a feature from Google, the reasoning being that is probably better to send a nonsensical word over a swear word in case you didn't actually mean to write the swear word.
Click to expand...
Click to collapse
Still derailing I understand what your saying as you are probably correct, its just funny how they related crap to veal...as you know lots of people don't approve of veal, so the code writer must be one of them...there are so many different words they could have chosen..just funny that's all! Done with the derail, back on this exhausted topic
SilverZero said:
Side note: My Evo just spell-corrected "crap" to "veal." It was like an Easter egg or something.
Click to expand...
Click to collapse
Sorry... I hate to be off topic, but this sparked a memory. I was sending my wife a txt a couple weeks ago and I can't remember the word I was typing, but it was definitely a legitimate word--no reason for Android to mess with it anyway. It effectively turned that word into "gay"...go figure.
Like sk63 said, that just relates to the Exchange admin role. Nothing to do with root access on the device.
sprink0281 said:
You know I noticed that the other day when I sending a text and thought the same thing.. I couldn't figure out how spelling crap was even close to the spelling of veal! So yes I think it was on purpose too! I wonder how many other 'Easter eggs" are programmed into this phone......where is the root egg...hehe....
Click to expand...
Click to collapse
OK -
V is to the right of C
E is to the left of R
A is the same as A
L is left under P
I hope this puts an end to this veal crap!
ok, back to topic
So, for the point about exchange administration... I am aware of what it is used for... since I myself am a user of it. My point was that it has administrative power over the phone since it can perform a wipe (among other highly privileged tasks)... so the idea was to try and use that system somehow to exploit.
I also liked the thinking behind installing old flash. That is at least a good question. One that I would love to hear the answer to.
Any time I spell Uber it tries to write ubersexual lol
Sent from my PC36100 using XDA App
N00dle said:
I'm sure there are plenty of dev's looking for exploits on a daily basis. No need to get peoples hopes up early is why there isn't much talk about it. Same reason people get dumped on for asking on a daily basis. If there was one found already it would be posted so quit asking sort of issue.
I like the thoughts though.
Click to expand...
Click to collapse
Wow! So (1) we aren't allowed to make any kind of new thread about 2.2 and rooting and (2) we can't share ideas about possible exploits, at least not in your presence.
I gotta say, kick me, kill me, put me on probation, but you are truly one GIANT ASS. Who put you on that high horse? What an Asshole. Hey, what prompted you to open this thread? Was it to review some interesting literature tied to an intriguing title, or did you open it knowing full well when you clicked that you were going to scroll to the bottom and post the most close-minded, rude, obtrusive comment you could think of?
I saw a story on BoingBoing indicating that the G2 has a rootkit installed on it.
boingboing.net/2010/10/05/t-mobile-sneaks-root.html
I am wondering if anyone can confirm this? I haven't received my phone yet, but that would suck.
yeah, any changes you make are reversed upon reboot
It is a very loose use of the term "rootkit", but from the owner's perspective, it is technically correct.
So is that it. Game over?
sinistersai4d4d said:
So is that it. Game over?
Click to expand...
Click to collapse
I'd wait for some credible evidence first. I haven't seen any at all yet...
I'm hoping there is no real merit to this and that the XDA community finds a workaround. I have faith in the devs here. The first one to get a working, solid root will definitely get a donation from me, lol.
My question is.. if the phone always resets the firmware.. what happens when T-Mobile pushes out the next OTA?
They obviously have a work around that needs to be exploited.
you know, when Motorola was doing this ****...everyone was like "no need to worry, HTC doesn't do this kind of stuff, and they make great phones"
What now? Seems like this is the future for sure
hydrogenman said:
you know, when Motorola was doing this ****...everyone was like "no need to worry, HTC doesn't do this kind of stuff, and they make great phones"
What now? Seems like this is the future for sure
Click to expand...
Click to collapse
I think in cases like these, their hands are probably tied. It's hard to say who to put the blame on. The carrier could've requested the block or they would've rejected HTC. Either way, it leaves a bad taste in my mouth. The end user pays a monthly bill and has purchased the phone. Why are they now disallowed to alter their investment? I don't see how the carrier or HTC loses. Preventing us from tinkering will just make us grow to hate the carrier, the phone manufacturer or both.
Where are we supposed to go when Android gets completely locked down? That doesn't sound like open source to me and open source is what drove me to Android in the first place.
I'm sure the big difference with the OTA is the fact that it's:
1) a newer version
2) signed
Failing to meet these requirements probably prevents writing to the "permanent" memory.
Well this is quite irritating. Has this sort of thing been implemented on other devices? And if so, has XDA been able to root it?
I guess what im trying to ask is, if this is true, does that mean the G2 can not be rooted? Need to know because im purchasing one soon and if its impossible to root and get roms on, It would be a deal breaker for me.
Well, it can't really be impossible, but if it requires hardware mods or for the signature to be cracked...it may never happen.
Honestly, I'm happy enough with the phone that I wouldn't be upset it if it was never rooted, but of course I'd prefer that it was. I'm just keeping my fingers crossed that one of the expert rooters can get the job done.
Yellowfrizbee said:
Well this is quite irritating. Has this sort of thing been implemented on other devices? And if so, has XDA been able to root it?
I guess what im trying to ask is, if this is true, does that mean the G2 can not be rooted? Need to know because im purchasing one soon and if its impossible to root and get roms on, It would be a deal breaker for me.
Click to expand...
Click to collapse
Anything that can be engineered, can ultimately be reverse engineered. I'm sure once devs like Cyanogen and others get a G2 in hand, they'll have some sort of solution or at least a better explanation than what this website gives. One can only hope. If it turns out to be hardware-driven, that scares me a bit.
Wow, what a boneheaded move by Tmo considering that so many people considered the G2 to be the successor to the N1 as a dev phone.
Jorsher said:
I'm sure the big difference with the OTA is the fact that it's:
1) a newer version
2) signed
Failing to meet these requirements probably prevents writing to the "permanent" memory.
Click to expand...
Click to collapse
That shouldn't matter then.. remember the CLIQ and DROID were rooted by adding SU to a signed OTA w/o changing the signature bits in the compressed OTA.
iT cant be impossible cause then we would never be able to get updates so like everyone is saying im sure some Pro Moders / Hackers will find a way. Will it be as simple as other roots? Prly not but im sure at some point we will have it. I to am happy with the phone as is and rly the only thing that we are lacking (correct me if im wrong) is the built in teathering and becoming a WiFi hotspot. I can live without those things but some people might need them. At any rate my fingers are crossed =)
Kubernetes said:
Wow, what a boneheaded move by Tmo considering that so many people considered the G2 to be the successor to the N1 as a dev phone.
Click to expand...
Click to collapse
The G2 is not a dev phone and they dont have dev phones of the G2 available for purchase..not sure what your inferring? The G1 had dev phones as did the N1.. nothing on the G2 though as of yet.
Well, if this is the case, then the phone goes back today. *sigh* I really like Android 2.2 over 1.6.
genibus said:
The G2 is not a dev phone and they dont have dev phones of the G2 available for purchase..not sure what your inferring? The G1 had dev phones as did the N1.. nothing on the G2 though as of yet.
Click to expand...
Click to collapse
He wasn't referring to an actual "dev" G2 phone...he meant the G2 was perceived as the next big "open" phone for devs to have just how the N1 was widely accepted/perceived as a phone for devs (being able to root, load custom ROMS, etc. freely) (ie. moto's execs telling disgruntled X owners that if they wish to have custom roms and such they should buy a google n1).
Jorsher said:
... I wouldn't be upset it if it was never rooted, but of course I'd prefer that it was. ...
Click to expand...
Click to collapse
The problem with this position is if you have a need that T-Mobile refuses to meet, then you cannot override them.
But as others have pointed out, it can be reversed engineered. Physical access to the hardware essentially makes it vunderable to whatever security counter-measures you wish to invest in.
Okay so I've got a theory about Motorola encrypted bootloaders like the ones on DX and Milestone. What I'm looking for is definitive information on the droid x lockout mechanism. Any information would be greatly appreciated. Also, if anyone knows of a broken DX to utilize for this experiment please let me know. It involves a hardware based process so a complete functional phone is not necessary. This method has been known to work with RSA encryption so it shows promise. Thank you.
MrKaz
From what I've heard, the "key" so to speak, in burned into the CPU itself. Its my understanding the only true way to unlock the BL is with Moto's keys, which we wont be getting any time soon. Whatever your plan is, I wish you the best. But we've had roughly 20+ of these threads come and go on here with everyone thinking they can crack it, and nothing ever pans out. Its a matter of the right people with knowledge and the right equipment to do the job, but those things have just not come together yet.
Once again, I wish you the best!
You may want to contact @aliasxerog, @_mrbirdman_, and/or @nenolod on twitter as they have all worked on trying to break/circumvent the bootloader. @P3Droid may be knowledgeable as well.
Yeah, I realize there's been a lot of threads on this. Having read a good deal of them I've determined that for the most part the consensus is that it can't be done, or at least not by any brute force means. However, I'm interested in other ways like signal injection and other hardware based avenues. After all, it is a chip and chips have flaws... Maybe I don't know enough to realize what it would take, and maybe being too stupid to understand that it can't be done is exactly what is required...
Thanks for all your input
MrKaz
MrKazman said:
Yeah, I realize there's been a lot of threads on this. Having read a good deal of them I've determined that for the most part the consensus is that it can't be done, or at least not by any brute force means. However, I'm interested in other ways like signal injection and other hardware based avenues. After all, it is a chip and chips have flaws... Maybe I don't know enough to realize what it would take, and maybe being too stupid to understand that it can't be done is exactly what is required...
Thanks for all your input
MrKaz
Click to expand...
Click to collapse
MrKaz,
+1 to your idea. Hey, who knows what will work.. with all that is going on, I wouldn't be surprised if the one idea that works..is some off the wall idea such as a chip flaw... Go for it man... I say take the idea and run with it.
best of luck
Your idea is one that I have been working on. All that needs to happened is find a way to dump the info to a computer and resign or make a dummy key to patch and inject back in.. unfortunately I have yet been able to inject anything because once dumped and cleared it doesn't regonize still active.. blah DX
MrKazman said:
Okay so I've got a theory about Motorola encrypted bootloaders like the ones on DX and Milestone. What I'm looking for is definitive information on the droid x lockout mechanism. Any information would be greatly appreciated. Also, if anyone knows of a broken DX to utilize for this experiment please let me know. It involves a hardware based process so a complete functional phone is not necessary. This method has been known to work with RSA encryption so it shows promise. Thank you.
MrKaz
Click to expand...
Click to collapse
Is this the electron starvation method that you speak of? From my understanding, that's a server exploit. Not really useful for a DX.
You want to be gamed up with the isht? #milestone-modders on freenode
gpaulu said:
You may want to contact @aliasxerog, @_mrbirdman_, and/or @nenolod on twitter as they have all worked on trying to break/circumvent the bootloader. @P3Droid may be knowledgeable as well.
Click to expand...
Click to collapse
Boooooooooooooooo...
_mrbirdman_ & nenolod dropped the ball and jumped ship.
P3Droid is better at BS and espionage than development. I mean, who actually uses tranquility? Or hasn't been bricked by it? Beside, what's been the biggest draw TBH has had to their app? The tether patch? If you were me, you'd be LYAO... LOL
As for @aliasxerog, from what I've seen, I've got very little faith that his efforts will pan out. Unless he stops looking to the above mentioned "devs", and starts working with the milestone guys. Especially yakk, who's probably done the most work on the kexec kernel module(Funny, aliasxerog's src makes no mention. He just says he ported it from the milestone efforts.). Yakk hasn't even released all of his code for kexec, so what aliasxerog is working with is incomplete, and certainly not up-to-date. His source doesn't even compile. Not even on my trusty build system that built the first DX overclock kernel module for Froyo, which jumped off JRummy's DX career(Jared didn't even bother to say "hey, mind if I use the module you built?"). Gotta love the DX devs! They bring so much laughter into my life!
.....
With that said, MrKazman, good luck in your efforts.
http://www.and-developers.com/boot:boot_chain
You may want to take a look at this. I think it's about the milestone, but it is similar to if not the same as the droid x
tekahuna said:
Is this the electron starvation method that you speak of? From my understanding, that's a server exploit. Not really useful for a DX.
You want to be gamed up with the isht? #milestone-modders on freenode
Boooooooooooooooo...
_mrbirdman_ & nenolod dropped the ball and jumped ship.
P3Droid is better at BS and espionage than development. I mean, who actually uses tranquility? Or hasn't been bricked by it? Beside, what's been the biggest draw TBH has had to their app? The tether patch? If you were me, you'd be LYAO... LOL
As for @aliasxerog, from what I've seen, I've got very little faith that his efforts will pan out. Unless he stops looking to the above mentioned "devs", and starts working with the milestone guys. Especially yakk, who's probably done the most work on the kexec kernel module(Funny, aliasxerog's src makes no mention. He just says he ported it from the milestone efforts.). Yakk hasn't even released all of his code for kexec, so what aliasxerog is working with is incomplete, and certainly not up-to-date. His source doesn't even compile. Not even on my trusty build system that built the first DX overclock kernel module for Froyo, which jumped off JRummy's DX career(Jared didn't even bother to say "hey, mind if I use the module you built?"). Gotta love the DX devs! They bring so much laughter into my life!
.....
With that said, MrKazman, good luck in your efforts.
Click to expand...
Click to collapse
I love your honesty!
Sent from my DROIDX using Tapatalk
Syco54645 said:
I love your honesty!
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Beesley doesn't... LOL
http://twitter.com/TheRealBeesley/status/30036655129763840#
@LexusBrian400
build.prop edits vs. Droid X Froyo Overclocking & AP Mode Tethering
Maybe I should put up a donation link, huh? LOL
P.S. I can't help but think your username is a reference to B-Legit's verse on Sideways... Little known fact: The Ambassador himself gave me the handle FreeWELL.
http://www.youtube.com/watch?v=3YXGvsbSjLw
Didn't notice that you mentioned jared. I rather like him. Let's just leave it at that...
Sent from my DROIDX using Tapatalk
Update
I'm getting more and more familiar with this situation every day. I'm also starting to realize what a big problem this is. I've spent a good deal of time pouring over the work they're doing with the Milestone which is kind of the same thing but isn't. Nonetheless I applaud the work they do and donate my CPU to Androinc. After that I've been reading and collecting every Block Diagram, Datasheet, Whitepaper, and post about mbmloader, m-shield, omap, and the like. Yeah, its complicated alright. The fact is though that its just a lock. A lock is a system based on deterrent not prevention. Systems built for mass production have accepted flaws to keep costs down. Chips aren't perfect, code is not perfect. Use the weakness against the system and the lock is picked. The more complex the system the more chances to get in....
Eh, I digress...
Anyone wanting to learn more about this let me know.
The search continues....
Kaz
Motorola, I paid for the Hardware. I can handle my own software and security...
The Bootloader has been bypassed, its just that the custom kernel has no drivers to run.
Ubermicro13 said:
The Bootloader has been bypassed, its just that the custom kernel has no drivers to run.
Click to expand...
Click to collapse
Well ill drive to help out...as long as someone has some snaps on the petro!
Sent from my DROIDX using XDA App
If this is anything like any other locked software, it's based around asymmetric encryption: Motorola HQ has a super-secret key that they use to encrypt their bootloaders, and they put the decryption key on every device, so that only things that are encrypted with their key will be decrypted correctly. The only way we're going to get the encryption key is by sleeping with the CEO of Motorola. It is - by design - not on the device.
The only way to replace the bootloader would be to replace the decryption key with one of our own or by bypassing it completely(using a buffer overflow or something similar).
As much as I want to believe that this can be done, its close to impossible and honestly not worth the persons time to try it, they did a good, well great, job of locking this thing down but ill say that liberty actually makes this feel like a new phone.
Sent from my DROIDX using XDA App
IWHBYD said:
If this is anything like any other locked software, it's based around asymmetric encryption: Motorola HQ has a super-secret key that they use to encrypt their bootloaders, and they put the decryption key on every device, so that only things that are encrypted with their key will be decrypted correctly. The only way we're going to get the encryption key is by sleeping with the CEO of Motorola. It is - by design - not on the device.
The only way to replace the bootloader would be to replace the decryption key with one of our own or by bypassing it completely(using a buffer overflow or something similar).
Click to expand...
Click to collapse
Just take one for the team there buddy.... lol
Sent from my DROIDX using XDA App
what does the CEO of motorola look like?
Enjoy
http://mediacenter.motorola.com/Executive-Team/Sanjay-Jha-31da.aspx
openbox9 said:
Enjoy
http://mediacenter.motorola.com/Executive-Team/Sanjay-Jha-31da.aspx
Click to expand...
Click to collapse
not it *noses*
I keep reading post after post about how pissed off someone is that they don't have SD support, and now that they have it with the 3.2 update, they are pissed that they have to hook it up to their computer to write to it.
My question to them is this:
If you can root your Xoom, put a custom kernel on it and have full access to your sd card, then take it back to stock if you need to send it back to Motorola, why don't you stop being a baby and just do it?
I mean, you care enough to complain on this forum so that we all have to read about how upset you are, but you are unwilling to follow the simple steps spelled out here to fix it?
Today I had an epiphany . I figured it out. It's not that they feel that they shouldn't have to; they just don't want to admit the true reason. These people are afraid to root their Xoom. If they weren't afraid, then they would be rooted already and moving on with their lives, instead of complaining on this forum and getting all upset about it.
I mean, it's 100% fixable. There is no other logical explanation.
How about people that want to get movies from the Android Market but you can't if you are rooted. That's not fear, that's not wanting to loose features. That's just one example, I am sure there are plenty of others. So maybe you shouldn't be a self-righteous pr*k and realize there may be reasons beyond your comprehension.
I have mine setup the way I want it, and AFAIK there is no way of rooting without wiping during the unlock process. So until then, I will have to live without the ability to change the main font. Which is a shame, but meh.
VaKo said:
I have mine setup the way I want it, and AFAIK there is no way of rooting without wiping during the unlock process. So until then, I will have to live without the ability to change the main font. Which is a shame, but meh.
Click to expand...
Click to collapse
True, that's unappealing...just when it's perfect you have to wipe and then you have to set it up again. I used to worry more about that but now that I've had to set-up again about 5 or 6 times I've become a master at doing it quickly and better than before. I totally love having root...wouldn't do it any other way.
I dare say people don't root because they are happy as they are, while those of us who enjoy using all of our devices are dumbstruck by people not doing so.
Sent from my DROIDX using XDA Premium App
chbennett said:
I dare say people don't root because they are happy as they are, while those of us who enjoy using all of our devices are dumbstruck by people not doing so.
Sent from my DROIDX using XDA Premium App
Click to expand...
Click to collapse
I just don't see too much of a need until we get some source code and custom roms.
Charlie_Don't_Surf said:
I just don't see too much of a need until we get some source code and custom roms.
Click to expand...
Click to collapse
undervolting each freq by 125mV is way to good to pass up
no way would I ever use stock
It's just not the right time. I wait until a "real" custom rom comes out.
What for? I can use my SD card if I need to. Which I don't. Got 3.2 a couple of days ago. If I want to play with roms and overclocking I have my phone rooted. But for now I don't need it.
Sent from my Xoom using XDA Premium App
Really?
crisisinthecity said:
I keep reading post after post about how pissed off someone is that they don't have SD support, and now that they have it with the 3.2 update, they are pissed that they have to hook it up to their computer to write to it.
My question to them is this:
If you can root your Xoom, put a custom kernel on it and have full access to your sd card, then take it back to stock if you need to send it back to Motorola, why don't you stop being a baby and just do it?
I mean, you care enough to complain on this forum so that we all have to read about how upset you are, but you are unwilling to follow the simple steps spelled out here to fix it?
Today I had an epiphany . I figured it out. It's not that they feel that they shouldn't have to; they just don't want to admit the true reason. These people are afraid to root their Xoom. If they weren't afraid, then they would be rooted already and moving on with their lives, instead of complaining on this forum and getting all upset about it.
I mean, it's 100% fixable. There is no other logical explanation.
Click to expand...
Click to collapse
For all the positive posts on this forum, and how helpful the "experts" are for us neophytes, this post is a huge fail. I'm not sure I could state the value of why it is even here........
Am I pissed I paid $500 for a computer that doesn't do what it claims? Yes. Am I pissed the salesperson sold me a bill of goods? Yes. Am I pissed I didn't have the chance to understand what I was reading about the unit and bought it anyhow? Yes.
Am I afraid to brick my device? Yes. Am I worrying when I read a full page of "if you do this" on the screen, while rooting, I lose my warranty and evil will come to my door? Yes. Am I afraid, while knowing the instructions provided on this forum are pretty darn good, that I might miss something and cause the end of life as we know it on this planet? [ or, at least having to explain to my wife why our $500 paperweight needs dusted off ]. Yes.
So, I'm in. I've used what I've learned here and taken the risk, however small you may think it is. But I'm 50, not 20. I'm considered a "nerd" in my circle of friends, but I can't carry the water for most of you guys. So, yes, I'm a bit worried about killing it. So what?
And unless you're better than I think you are (and I have no doubt you're pretty darn good - seriously), in computers there is no such thing as 100%.
KerryG said:
How about people that want to get movies from the Android Market but you can't if you are rooted. That's not fear, that's not wanting to loose features. That's just one example, I am sure there are plenty of others. So maybe you shouldn't be a self-righteous pr*k and realize there may be reasons beyond your comprehension.
Click to expand...
Click to collapse
Good point. Any more reasons?
newskate9 said:
For all the positive posts on this forum, and how helpful the "experts" are for us neophytes, this post is a huge fail. I'm not sure I could state the value of why it is even here........
Am I pissed I paid $500 for a computer that doesn't do what it claims? Yes. Am I pissed the salesperson sold me a bill of goods? Yes. Am I pissed I didn't have the chance to understand what I was reading about the unit and bought it anyhow? Yes.
Am I afraid to brick my device? Yes. Am I worrying when I read a full page of "if you do this" on the screen, while rooting, I lose my warranty and evil will come to my door? Yes. Am I afraid, while knowing the instructions provided on this forum are pretty darn good, that I might miss something and cause the end of life as we know it on this planet? [ or, at least having to explain to my wife why our $500 paperweight needs dusted off ]. Yes.
So, I'm in. I've used what I've learned here and taken the risk, however small you may think it is. But I'm 50, not 20. I'm considered a "nerd" in my circle of friends, but I can't carry the water for most of you guys. So, yes, I'm a bit worried about killing it. So what?
And unless you're better than I think you are (and I have no doubt you're pretty darn good - seriously), in computers there is no such thing as 100%.
Click to expand...
Click to collapse
It's here so that we can understand why people won't root their Xoom. Getting some good answers.
I Agree
I cannot imagine using any of my android devices without at least su file capabilities
crisisinthecity said:
It's here so that we can understand why people won't root their Xoom. Getting some good answers.
Click to expand...
Click to collapse
Your answer to my post, leads me to believe I missed the point and tone of your OP. I took quite a bit of attitude, perhaps mistakenly. If so, accept my apologies please.
Give me one good reason I should.
While rooting would give me some slight benefit, the juice is simply not worth the squeeze. I am happy with what Ive got and have seen no compelling reason why I should go through the trouble since SD support isnt even an incentive anymore and it was the only thing I was lacking.
Cielmerlion said:
Give me one good reason I should.
While rooting would give me some slight benefit, the juice is simply not worth the squeeze. I am happy with what Ive got and have seen no compelling reason why I should go through the trouble since SD support isnt even an incentive anymore and it was the only thing I was lacking.
Click to expand...
Click to collapse
This is great because it says that people love the Xoom right out of the box, or fresh from the stock update.
As I said, having experienced both, I will choose the ability to truly customize to my hearts content. But for those who are happy with plain vanilla, enjoy!
chbennett said:
I dare say people don't root because they are happy as they are, while those of us who enjoy using all of our devices are dumbstruck by people not doing so.
Sent from my DROIDX using XDA Premium App
Click to expand...
Click to collapse
+1 I have no reason to root.
the speed, battery life, etc. etc. are all fine for what I use it for - nothing heavy - just a replacement for browsing the web and a few games like angry birds
Charlie_Don't_Surf said:
I just don't see too much of a need until we get some source code and custom roms.
Click to expand...
Click to collapse
there's no real custom roms out that give you any benefit to flashing a new rom, and I am on 3.2 - not even put an sdcard in the xoom yet.
all movies/tv shows are streamed direct to TV or to Xoom via Plex, so i dont need extra space to store movies,
I only have the wifi version so i dont need space for travelling around with 3g.
the only time I may need more space and thus an sdcard would be if i go on holiday and want to take a few films on the sd - but even in a readonly state i can do that by loading films onto an sd and sticking it in now...
my only grief was that motorola were taking an aeon to push out any updates to the UK image I had on - but flashing the US fixed that and I decided I dont need to go any further down the rooting process... I'm happy - surely that's the best way to be
newskate9 said:
Your answer to my post, leads me to believe I missed the point and tone of your OP. I took quite a bit of attitude, perhaps mistakenly. If so, accept my apologies please.
Click to expand...
Click to collapse
I was basically trying to get some conversations started as to why and why not to root the WiFi xoom so people on this forum understand where the other team is coming from. Thought this thread title and my choice of words would draw some good debate. And it would keep the debate here and not all over the forum.
Sent from my HTC Sensation 4G using XDA Premium App
I get what people are saying here, if you're happy with what you've got then by all means you should stick to it. No-one should be telling you what to like.
However, I do support the OP. If you are NOT happy with what you've got but there is a fix for it, why not just apply the fix instead of complaining?
crisisinthecity said:
I keep reading post after post about how pissed off someone is that they don't have SD support, and now that they have it with the 3.2 update, they are pissed that they have to hook it up to their computer to write to it.
My question to them is this:
If you can root your Xoom, put a custom kernel on it and have full access to your sd card, then take it back to stock if you need to send it back to Motorola, why don't you stop being a baby and just do it?
I mean, you care enough to complain on this forum so that we all have to read about how upset you are, but you are unwilling to follow the simple steps spelled out here to fix it?
Today I had an epiphany . I figured it out. It's not that they feel that they shouldn't have to; they just don't want to admit the true reason. These people are afraid to root their Xoom. If they weren't afraid, then they would be rooted already and moving on with their lives, instead of complaining on this forum and getting all upset about it.
I mean, it's 100% fixable. There is no other logical explanation.
Click to expand...
Click to collapse
I for one am too new to Android to root my Xoom. I have a G2x phone. It has a one step Root method and a one step Recovery method. I'm ok with that. But looking at all the ABD steps and the instructions on how to make them work....I feel its too complicated for a limited return at this time.
If someone put together the Bible of rooting the Xoom, that does NOT begin with , " This assumes you have an understanding of xxx", then maybe I would...
I took the Xoom out of the box...I want to Root, do this, then this, then this. Include what needs to be installed, what to type, etc, etc.
If that sounds whiney...so what, you asked.