Here's the reply an Acer representative posted on Acer ANZ Facebook page:
"the A501 update has two more security patch integrated hence the slight delay on the update. The date is very likely to be tomorrow, that the first batch of users are going to receive FOTA update notification. Australia & New Zealand are amongst the first countries with the updates made available. Appreciate your understanding and hopefully the update will be with you shortly.".
This was posted around 3.30 PM of the 09/19 (UTC).
Just remember...
DON'T RUSH TO APPLY IT OR YOU'LL LOSE ROOT!
Wait for the devs to modify the OTA and take out the new bootloader and recovery...
This is like the millionth time I've read that 3.2 is unrootable... LoL Repetita iuvant
chiasottis said:
This is like the millionth time I've read that 3.2 is unrootable... LoL Repetita iuvant
Click to expand...
Click to collapse
Considering how many idiots have flashed it and then come in here crying about it, it bares repeating.
So, in your opinion, is everyone that flashed the 3.2 an idiot or just those that are now crying about it?
mac4402 said:
So, in your opinion, is everyone that flashed the 3.2 an idiot or just those that are now crying about it?
Click to expand...
Click to collapse
Very good question. I updated fully knowing I would loose root, however I have full confidence that the devs will work it out.
Sent from my A500 using xda premium
mac4402 said:
So, in your opinion, is everyone that flashed the 3.2 an idiot or just those that are now crying about it?
Click to expand...
Click to collapse
The ones that are crying about it, obviously.
After searching on this forum and others, I updated to 3.2, at the time I could not find anything stating that you couldn't root it, but also nothing saying you could. I did however see a few posts from people doing previous upgrades saying that they managed to maintain root. At the time I realized there was a risk I wouldn't be able to root it, but it seemed likely I would. I also figured that if I couldn't root it, at least I could always flash back to 3.1 and root that.
Unfortunately I was wrong on both counts. Since that time I, and others, have made sure that anyone who asks is very aware of the risks so that others don't make the same mistake that I did.
I'm not really complaining though, I do have full confidence that 3.2 will be rooted in time, and while I enjoy having a rooted tablet, and use many applications that require it, not having root is not a deal breaker for me. and I still enjoy the tablet (though I must say the ads are drivng me nuts!)
I guess this is what I get for being an early adopter.
Looks like that was true. Downloading now on my A501...
I'm calling it "Acer Payback" for originally giving us the most easy to root device I've ever seen
Besides, anybody who roots and installs a custom recovery should know...Never take an OTA factory update, or at least be cautious about doing it.
One poster on another forum, was advised by Acer Support to do a factory reset to roll back to factory
I'm no rocket scientist, but doesn't that involve using that pinhole by the rocker?
Anybody try this yet? Results?
Not sure about what your question means... Update wouldn't install ("update not valid" error), so I did a Factory Reset: Settings -> Privacy -> Factory Reset (backup your internal SD as it'll be formatted). After that the update completed fine.
First impressions: snappier; some stuff (like keyboard) looks crispier on screen; more stable networks; new movie editor; etc.
Definitely a huge improvemente over 3.0.1.
So guys.. could anyone say what should i do to take safe OTA update while i have rooted a501 HV hc3.2 CWM? What are steps to do this not bricking our tab?
As guys said i could wait for way to root stock rom.
This is a judgement call. Basically, if you're happy being rooted, and you're running a custom rom with 3.2, I really see no need to revert back to stock, unless you have a lot of funky issues.
Personally, I wouldn't look forward to setting things up all over again, then having to wait till the devs com eup with another root, which may not be as easy as before. Not to mention I would lose ad-hoc support along with a couple of root required apps.
But if you have issues, then by all means, run the OTA.
If it ain't broke, don't fix it.
Moscow Desire said:
if you're happy being rooted, and you're running a custom rom with 3.2, I really see no need to revert back to stock
Click to expand...
Click to collapse
Reality call: not everyone wants to flash a custom rom. I've been flashing roms on WinMo, then Android for years and I've come to the conclusion that, no matter what, stock is better. The only time custom may be preferable is once the device isn't anymore updated officially.
As a side note, please notice that we A501 users were still running 3.0.1 prior to this update and, as you know, that ROM was terrible. This is why I preferred updating immediately (and having, finally, a device that works well) without waiting for root and other mods, which I can live well without.
You could download the FOTA and modify it to remove the new bootloader and recovery and get it rooted, like ezterry did with the A500 version. Maybe try contacting him on exactly what to modify...
chiasottis said:
Reality call: not everyone wants to flash a custom rom.
Click to expand...
Click to collapse
No reality call needed . If you had looked at the guys post, he/she is running Honey Villain3.2, which I believe is a custom Rom. The post was wether or not there was a need to revert back to a non-rootable factory rom, without taking a chance of things going bad.
I really couldn't tell you about 3.0. It lasted about 20 minutes after I bought my 501. To say that "3.0 was a terrible Rom", and then say "Stock is better", is a contradiction in itself.
Flashing any rom, should be a personal choice, of course there are pro's and con's which each person has to decide. And they should do their homework beforehand.
So really, there is no need to get "snippy"
But then again, there are always trolls about
Moscow Desire said:
No reality call needed . If you had looked at the guys post, he/she is running Honey Villain3.2, which I believe is a custom Rom. The post was wether or not there was a need to revert back to a non-rootable factory rom.
Click to expand...
Click to collapse
Ops! Didn't see that post; I thought you had come here to instruct us to discard stock in favor of custom. Sorry.
Moscow Desire said:
So really, there is no need to get "snippy"
Click to expand...
Click to collapse
I didn't get "snippy". I'm just tired to read, every single time there's some problem, "flash a custom" as the only solution. It wasn't your case, though, sorry.
No problemo.
But as you say, flashing is not a cure for everything. But for those of us who like to tweak things, it's nice to know we have that choice.
I just wish people would read about these things, before they get themselves in trouble.
Or the best is "I rooted, now what?"
Or, "I didn't see my exact model, but I flashed one that was close".
yea thats what i meant. I had rooted my device cuz 3.0.1 was awful. Again, i have to roll back to 3.0.1 since i have instaled 3.2 ( some factory default ??) Or what? And as you gays said Id like tu be sure before i start doing anything in this subject.
miszi said:
i have to roll back to 3.0.1 since i have instaled 3.2 ( some factory default ??)
Click to expand...
Click to collapse
Yes, you must go back to stock to update.
Related
This is not a 2.1 speculation thread, I just thought I'd ask it here with all that knowledge floating around.
WHEN (May 7th?) the 2.1 update is OFFICIALLY dropped, will rooted users be pushed the update? Or will it only go out to models registered as running 1.56.
ASSUMING one might want to upgrade and that push comes, you guys think updating might cause any harm to the phone? I'm thinking 1.56RUU..
I don't think I will partake in the official release, I can't imagine it being any better then what I have now, and what will come after that official release is dropped, however I have had this question for a while. So what do you guys think?
I don't think they can actually push a OTW update.....
barnacles10 said:
This is not a 2.1 speculation thread, I just thought I'd ask it here with all that knowledge floating around.
WHEN (May 7th?) the 2.1 update is OFFICIALLY dropped, will rooted users be pushed the update? Or will it only go out to models registered as running 1.56.
ASSUMING one might want to upgrade and that push comes, you guys think updating might cause any harm to the phone? I'm thinking 1.56RUU..
I don't think I will partake in the official release, I can't imagine it being any better then what I have now, and what will come after that official release is dropped, however I have had this question for a while. So what do you guys think?
Click to expand...
Click to collapse
It is not going to be OTA. It will not matter if you are running custom whatever or stock.
If you run the ruu.exe it will load the official 2.1 release on your phone. The only reason it may not work would be if you ran the 2.1 test ruu.exe and for some reason the official release's hboot is lower than 1.47.000 (the hboot that came with the test release).
Other potential nasty side effects you could get with your official release:
No root
Possibly never be able to root again, or at least stuck with no root until a new work around is found. This fully depends on whether old method is patched.
No custom recovery, no custom roms, no ability to flash .zips from recovery. This goes along with the lack of root.
Inability to run 1.56 ruu ever again due to updated hboot.
danknee said:
It is not going to be OTA. It will not matter if you are running custom whatever or stock.
If you run the ruu.exe it will load the official 2.1 release on your phone. The only reason it may not work would be if you ran the 2.1 test ruu.exe and for some reason the official release's hboot is lower than 1.47.000 (the hboot that came with the test release).
Other nasty side effects you could get with your official release:
No root
Possibly never be able to root again, or at least stuck with no root until a new work around is found.
No custom recovery, no custom roms, no ability to flash .zips from recovery. This goes along with the lack of root.
Inability to run 1.56 ruu ever again due to updated hboot.
Click to expand...
Click to collapse
Couldn't have said it better myself! I would just suggest waiting until the cook of your preference updates his to include items from the official release.
And the single most important reason: No nandroid. Having a point in time backup is insanely important to me. If I ever have to return my phone and get a refurb, it's nice to know I've got a nandroid that will get me right back to where I was before I turned in my phone.
It won't be OTA as I have read in more than one place that Sprint limits OTA updates to 9MB. Since this will be close to or over 100MB it's going to be OTW.
I for one will not be updating to it. My phone is working perfectly as is and this would give me no additional functionality so why bother?
As for the whole rooting issue, I wish folks wouldn't be so scared of the new hboot. I used the RUU and I have custom recovery and can flash any ROM I want. Yes, I know the leaked RUU had root already, but I rerooted it properly and installed busybox and all that so I could use the phone how I wanted.
Anyway, sorry to get sidetracked there, my comment about being so scared of the new hboot is simply this...There is no way the new version will not be rooted sooner or later. Obviously Sprint and HTC would like us to not be able to root any phones but someone always finds a way. There is no way that the new firmware will not be rooted sooner or later. Just like how the Evo will get rooted, as will any newer phone released after it. It is inevitable that someone will figure it out especially with all the talented and experienced folks here working on it as soon as it's released.
jlem26 said:
It won't be OTA as I have read in more than one place that Sprint limits OTA updates to 9MB. Since this will be close to or over 100MB it's going to be OTW.
I for one will not be updating to it. My phone is working perfectly as is and this would give me no additional functionality so why bother?
As for the whole rooting issue, I wish folks wouldn't be so scared of the new hboot. I used the RUU and I have custom recovery and can flash any ROM I want. Yes, I know the leaked RUU had root already, but I rerooted it properly and installed busybox and all that so I could use the phone how I wanted.
Anyway, sorry to get sidetracked there, my comment about being so scared of the new hboot is simply this...There is no way the new version will not be rooted sooner or later. Obviously Sprint and HTC would like us to not be able to root any phones but someone always finds a way. There is no way that the new firmware will not be rooted sooner or later. Just like how the Evo will get rooted, as will any newer phone released after it. It is inevitable that someone will figure it out especially with all the talented and experienced folks here working on it as soon as it's released.
Click to expand...
Click to collapse
One big disadvantage/advantage in our case, is that Linux is open source. Anyone who wants to find a root exploit, and is smart enough has the ability to find out where there is potential code to allow for one. So you are correct, my assumption is that we will find a root for it one day. BUT I do think that if the EVO drops soon after, all of the talent that can find one will be on it. Then again, some people are of the mind set "Leave no device un hacked" and it would bother people if they knew we didn't have root LOL
Correct me if I'm wrong, but won't we be able to simply use an older RUU (1.52, etc) to get the phone rootable again?
My intention was going to be to try out the new stock RUU for a bit, then re-flash with an older RUU, get root and RA recovery back on, then go back to Fresh Toast. Will this not be possible?
cicada said:
Correct me if I'm wrong, but won't we be able to simply use an older RUU (1.52, etc) to get the phone rootable again?
My intention was going to be to try out the new stock RUU for a bit, then re-flash with an older RUU, get root and RA recovery back on, then go back to Fresh Toast. Will this not be possible?
Click to expand...
Click to collapse
Not possible if the Hboot updates, which it probably will. Those here who tried the test leak 2.1 ruu.exe were unable to run the 1.56 ruu after.
There is an alternative to restore everything except the hboot from the 1.56 ruu here, but you cannot simply run the .exe. This method won't work if the official build has patched the ability to gain root (you won't be able to nandroid). In that case you will be stuck with official 2.1 only.
BTW, speaking from experience with the test build, ruu, hboot, etc.
Kcarpenter said:
One big disadvantage/advantage in our case, is that Linux is open source. Anyone who wants to find a root exploit, and is smart enough has the ability to find out where there is potential code to allow for one. So you are correct, my assumption is that we will find a root for it one day. BUT I do think that if the EVO drops soon after, all of the talent that can find one will be on it. Then again, some people are of the mind set "Leave no device un hacked" and it would bother people if they knew we didn't have root LOL
Click to expand...
Click to collapse
Open source is never a disadvantage. Ever.
Good to know, would've been awful to have to wait for new root hack just because I tried the new and shiny!
Guess I will sit back and wait for dev magic before I jump the gun.
Sawawa said:
Open source is never a disadvantage. Ever.
Click to expand...
Click to collapse
Mater of semantics, politics, and Ideaologies.
Google has a half belief here, they like open, but they protect that damn search algorithim like its a sacred scripture - Last count I think 8 people on earth knew exactly how it worked.
So the disadvantage to google would be ungodly competition if it was released. Proprietary stuff is a win if you look for profits. Again...depends on which side of the spectrum you are on. Points can be argued either way.
jlem26 said:
It won't be OTA as I have read in more than one place that Sprint limits OTA updates to 9MB. Since this will be close to or over 100MB it's going to be OTW.
Click to expand...
Click to collapse
I think the OP is asking about an OTA 'notification' that the official update is available. If so then yes, everyone with a Hero will get a text message regardless of what rom we have installed.
ramiss said:
I think the OP is asking about an OTA 'notification' that the official update is available. If so then yes, everyone with a Hero will get a text message regardless of what rom we have installed.
Click to expand...
Click to collapse
THAT BETTER NOT COUNT AGAINST MY TEXT LIMIT!!!!
Kcarpenter said:
THAT BETTER NOT COUNT AGAINST MY TEXT LIMIT!!!!
Click to expand...
Click to collapse
ROFL. . . you don't have unlimited text?
lol I would hope having a hero you would have unlimited data and texts
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
yeah, but I still keep track of them. Habitual addiction to knowing everything LOL.
yeah, but I still keep track of them. Habitual addiction to knowing everything LOL.
Click to expand...
Click to collapse
lol! that's great.. ever since sprint gave us that free mobile to mobile in any network I do not bother checking minutes or texts. unless my bill changes.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
One big disadvantage/advantage in our case, is that Linux is open source. Anyone who wants to find a root exploit, and is smart enough has the ability to find out where there is potential code to allow for one.
Click to expand...
Click to collapse
Why is it that people still think open source means insecure? I don't claim to know how previous rooting techniques exploit Android, but I do know that 2 Linux distros have a higher government security rating than any other operating system. I assume most weaknesses in android have to do with the recovery and/or update code, which has nothing to do with Linux.
Sawawa said:
Open source is never a disadvantage. Ever.
Click to expand...
Click to collapse
It IS when HTC bogards it from us and hordes it like cookie monster does cookies. I thought open source meant OPEN SOURCE. Ahh, who knows i probably misunderstood the whole concept
Okay xda, here's a hypothetical situation I'm considering:
I'm running damagecontrol 2.08.1, and I know the official 2.1 is out now. However, I hear mixed reviews. I'd much rather be running the official update, but at the same time not too sure I want to lose root. It'd be good to hop off the root train to avoid pains like this, but then I'll be impatient when Froyo comes around I suppose. Anyways, I was wondering if it were at all possible to:
1.) Backup via Nandroid my system running 2.08.1 rooted.
2.) Update to the official non-rooted 2.1
3.) Test it out, and if I don't like it, restore to my 2.08.1 rooted via Nandroid, and have root access again.
Can anyone confirm whether or not this would work? Also for those that updated, what are your thoughts on Root-vs-Non?
You figure out how to run a nandroid backup without root, after running the Sprint RUU, and you will make 27 people on this forum VERY Happy.
not me, I was smart and didn't load it...or at least i didn't "take one for the team"
colemorris said:
Okay xda, here's a hypothetical situation I'm considering:
I'm running damagecontrol 2.08.1, and I know the official 2.1 is out now. However, I hear mixed reviews. I'd much rather be running the official update, but at the same time not too sure I want to lose root. It'd be good to hop off the root train to avoid pains like this, but then I'll be impatient when Froyo comes around I suppose. Anyways, I was wondering if it were at all possible to:
1.) Backup via Nandroid my system running 2.08.1 rooted.
2.) Update to the official non-rooted 2.1
3.) Test it out, and if I don't like it, restore to my 2.08.1 rooted via Nandroid, and have root access again.
Can anyone confirm whether or not this would work? Also for those that updated, what are your thoughts on Root-vs-Non?[/QUOTE
This will not work, If you upgrade to 2.1 using official Ruu, You will lose root, and it will wipe the custom recovery image, so no more flashing anything, no more root, until someone finds the clink in the htc armour to regain root
Click to expand...
Click to collapse
I see, so that recovery menu isn't stock android recovery? Well then here's another question.
If you could get flash-rec on an unrooted phone through the ASTRO install method, could you flash a custom recovery image like 1.6.2, then do a nandroid restore from backup?
I probably sound like a mega-noob, just wanting to know why we can't do these things.
Nah, I "took one for the team" but am actually working on it. I DO have to say that the official 2.1 is DAMN fast though. Like, faster then pancacke 0.1 hehe
No but seriously, there is almost 0 lag, and the only thing that I have seen wrong is all of the apps in the app drawer
And no, the nandroid thing is NOT possible.
Hmm, thanks regaw for the answer. Is it fast enough to make waiting for a 2.1 rooted unnecessary right now? Cause damage hasn't logged in for ages, and I'm tired of all the force closes and errors I'm getting. I'm just not so sure it's worth upgrading when I may have to wait longer if I update to an unrooted. I mean, I have A2SD, DConfig, all those shenanigans that make the phone so much better. What's your take?
colemorris said:
Hmm, thanks regaw for the answer. Is it fast enough to make waiting for a 2.1 rooted unnecessary right now? Cause damage hasn't logged in for ages, and I'm tired of all the force closes and errors I'm getting. I'm just not so sure it's worth upgrading when I may have to wait longer if I update to an unrooted. I mean, I have A2SD, DConfig, all those shenanigans that make the phone so much better. What's your take?
Click to expand...
Click to collapse
Well, If you would like to do anything other than what Sprint/HTC wants you to do, I would recommend NOT upgrading, but waiting for something to come out. I know that Damageless is really busy, but I know that trevE is working on things too. They just need to finalize some stuff to get it out. While official 2.1 is fast, it doesn't have a whole bunch of things that us on custom ROMs take for granted. This is my first time on an official ROM since January, and, I do not want to keep it on for long, 1) just so I can begin developing again... and 2) so I can figure out the method of getting root back for everyone who ran the RUU.
regaw_leinad said:
Well, If you would like to do anything other than what Sprint/HTC wants you to do, I would recommend NOT upgrading, but waiting for something to come out. I know that Damageless is really busy, but I know that trevE is working on things too. They just need to finalize some stuff to get it out. While official 2.1 is fast, it doesn't have a whole bunch of things that us on custom ROMs take for granted. This is my first time on an official ROM since January, and, I do not want to keep it on for long, 1) just so I can begin developing again... and 2) so I can figure out the method of getting root back for everyone who ran the RUU.
Click to expand...
Click to collapse
Damn it Regaw I just realzied that you have more posts than me.
Any how, good luck on finding that root.
Here is this from Millworm, But it hink Eris devs proved it was fixed long ago.
http://www.milw0rm.com/exploits/9545
This one is also older, but not sure if anyone has tried it.
http://www.milw0rm.com/exploits/8678
Edit - Milw0rm must be dead.
and this, but it looks like only 2.6.30 Kernel maybe, and its just a Null Pointer exploit which is probably not suitable.
http://lwn.net/Articles/341773/
Also:
Possible way to change an MD5:
http://www.rapidleech.com/topic/2860-change-md5-hash/
Just some stuff I have looked at doing, but I am not willing to jump ship on a rooted phone.
you know I have been back and forth on whether or not to go with the official release and lose root, but during that process I loaded up Pure Hero rom which is based off the alysious (sp?) Rom but with Sense removed and man is it fast.
I have no need to lose root and this little phone is very speedy. And yes, I have tried Damage and Fresh (and a few variation based on those two) roms. Although they are decent roms, they just and turtles when compared to Pure Hero.
As far as Sense goes, I did like Sense, if you want it then do the alysious (again sp?) rom. Just that I think removing sense speeds it up, and honestly you can get all those functions through apps.
okay guys, I tried to figure this out without bothering yall, but my newb knowledge is limited and I'm confused as hell. I was planning on rooting my phone today after reading about all the information I've been collecting from you guys, but now that I have updated my phone, will Toast's method using those files still allow me to root? Or do I need new files in order to root my phone? I see some files on developer page on new root but I'm confused if those are for phones already rooted or not...ahhhh
so I guess I'm asking is..if you have stock phone with new update applied, how do I go about rooting my evo?
We don't know yet. You should not have updated.
Quick and straight to the point, thanks for your reply. I guess I'm a motherfreakin idiot with the worst timing in the world for things like this. FML
TheBiles said:
We don't know yet. You should not have updated.
Click to expand...
Click to collapse
quick question; if i root with Toast's method, then install the rooted updated rom that's in the dev section (by Calkulin), that should be fine, right?
jblazea50 said:
quick question; if i root with Toast's method, then install the rooted updated rom that's in the dev section (by Calkulin), that should be fine, right?
Click to expand...
Click to collapse
yes
-----------------------
So in order to fully root and nand unlock stock evo with new update, all I have to do is follow Toast's step 1&2 then apply the new rooted update on developer site? just wanna get things crystal clear so I don't risk bricking my evo..
I don't know or think it has been confirmed to work with the new update yet.
Toast step 1 will root the phone
Toast step 2 will unlock nand
Installing the new rooted update will flash the stock sprint rom without breaking your root.
mizerab1e said:
So in order to fully root and nand unlock stock evo with new update, all I have to do is follow Toast's step 1&2 then apply the new rooted update on developer site? just wanna get things crystal clear so I don't risk bricking my evo..
Click to expand...
Click to collapse
No. We don't even know if you can use Toast's method to root it. You can be the guinea pig and post results, though!
initial said:
yup.
Toast step 1 will root the phone
Toast step 2 will unlock nand
Installing the new rooted update will flash the stock sprint rom without breaking your root.
Click to expand...
Click to collapse
There is some info going around in dev forum saying Toast's method will not work if you have the new OTA update applied on stock EVO saying you will get error messages and stuff although it will not brick your phone which is adding to more confusion..
has anyone successfully rooted their stock evo with new OTA update applied? or do I need to wait until devs come up with new files needed to root the evo?
mizerab1e said:
There is some info going around in dev forum saying Toast's method will not work if you have the new OTA update applied on stock EVO saying you will get error messages and stuff although it will not brick your phone which is adding to more confusion..
has anyone successfully rooted their stock evo with new OTA update applied? or do I need to wait until devs come up with new files needed to root the evo?
Click to expand...
Click to collapse
All you have to do is place a file in the root of your SD card and reboot the phone. Try it out and post your results!
mizerab1e said:
Quick and straight to the point, thanks for your reply. I guess I'm a motherfreakin idiot with the worst timing in the world for things like this. FML
Click to expand...
Click to collapse
You and me both my friend, you and me both. Sat there as the update came up and thought, I bet this is going to prevent me from rooting today ...
Yeah, ALL root is broken if you install the OTA.
Okay so I've been digging around and asking questions in dev forum, seems like there is no way for Stock EVO with OTA update to root their EVO yet. What bothers me is that I haven't seen a single post from a dev announcing that they are working on new root methods for Stock EVO with new OTA update.. they seem to be more concerned about fixing the issue around previously rooted EVOs, and I'm afraid we are getting left out... I hope this isn't the case, and hopefully one of our brilliant devs will give the new stock evo with OTA update owners some attention to this matter.
mizerab1e said:
Okay so I've been digging around and asking questions in dev forum, seems like there is no way for Stock EVO with OTA update to root their EVO yet. What bothers me is that I haven't seen a single post from a dev announcing that they are working on new root methods for Stock EVO with new OTA update.. they seem to be more concerned about fixing the issue around previously rooted EVOs, and I'm afraid we are getting left out... I hope this isn't the case, and hopefully one of our brilliant devs will give the new stock evo with OTA update owners some attention to this matter.
Click to expand...
Click to collapse
They're busy working on the kernel. Everybody was warned not to accept the OTA and those of us that chose to do it have to lie in our beds until the developers get around to it.
EtherealRemnant said:
They're busy working on the kernel. Everybody was warned not to accept the OTA and those of us that chose to do it have to lie in our beds until the developers get around to it.
Click to expand...
Click to collapse
Seems like that is the case, someone from dev forum suggested that downgrading the OTA to previous one then rooting might wield some fruit, If I can figure out how to do that I'll be more than happy to be a guinea pig for you guys.
TheBiles said:
All you have to do is place a file in the root of your SD card and reboot the phone. Try it out and post your results!
Click to expand...
Click to collapse
I'm not quite sure which file you're talking about, could you elaborate some more?
mizerab1e said:
Okay so I've been digging around and asking questions in dev forum, seems like there is no way for Stock EVO with OTA update to root their EVO yet. What bothers me is that I haven't seen a single post from a dev announcing that they are working on new root methods for Stock EVO with new OTA update.. they seem to be more concerned about fixing the issue around previously rooted EVOs, and I'm afraid we are getting left out... I hope this isn't the case, and hopefully one of our brilliant devs will give the new stock evo with OTA update owners some attention to this matter.
Click to expand...
Click to collapse
They busted their asses to get root the first time, and, as of right now, every EVO that you buy is capable of being rooted. Only people who update without heeding the warnings are affected, so it is kind of hard to convince a dev to throw down all of their current work to go back and try to solve this AGAIN. It should be a general rule of thumb that you NEVER install manufacturer's updates on any piece of electronics that you are interested in hacking/modifying/changing in any way. 99% of the time they provide some kind of security fixes that are not announced.
mizerab1e said:
Seems like that is the case, someone from dev forum suggested that downgrading the OTA to previous one then rooting might wield some fruit, If I can figure out how to do that I'll be more than happy to be a guinea pig for you guys.
Click to expand...
Click to collapse
It doesn't work. I've already tried it. The bootloader is locked.
TheBiles said:
They busted their asses to get root the first time, and, as of right now, every EVO that you buy is capable of being rooted. Only people who update without heeding the warnings are affected, so it is kind of hard to convince a dev to throw down all of their current work to go back and try to solve this AGAIN. It should be a general rule of thumb that you NEVER install manufacturer's updates on any piece of electronics that you are interested in hacking/modifying/changing in any way. 99% of the time they provide some kind of security fixes that are not announced.
Click to expand...
Click to collapse
I have no doubt in my mind the devs are doing everything they can to provide us with their brilliant work, I have no one but myself to blame for updating the OTA without heeding their warnings. I'm sure once the devs iron out all the issues with previously rooted system, they will get around to us as they always have. I just wish there was any way I can contribute to putting some light onto this matter for those who made the mistake of updating their OTA..
Yeah, was kicking myself as I knew it was a mistake.
Am willing to try out some ish too, that is if an extra Guinea is needed.
I finally decided I would take the plunge and move from 3.1 to 3.2 after I saw the "voodoo OTA RootKeeper". I had been rooted previously. Sadly, after the update, the software DID NOT work and now I'm stuck with an unrooted device. Will this get me back to rooted? Or should I just downgrade back to 3.1? I would rather NOT lose my data. My current build is Acer_A500_7.006.01_COM_GEN2.
funnyfarm299 said:
I finally decided I would take the plunge and move from 3.1 to 3.2 after I saw the "voodoo OTA RootKeeper". I had been rooted previously. Sadly, after the update, the software DID NOT work and now I'm stuck with an unrooted device. Will this get me back to rooted? Or should I just downgrade back to 3.1? I would rather NOT lose my data. My current build is Acer_A500_7.006.01_COM_GEN2.
Click to expand...
Click to collapse
Yes either will work.
Don't that piss you off? Thanks Acer.
I did the downgrade, since rooting with iconiaroot is so easy, and I was on 3.2.1. The downgrade should work just fine, just make sure you have iconiaroot and acer recovery installer installed before downgrading, it makes life a lot easier since your keyboard wont work after downgrading. The downgrade method rom isnt for normal use, so root with it and install rooted 3.2.
that is sad.. I had just read an article about this app and was going to ask about it around here... Have you contacted the app developer and let them know??
abalsor said:
that is sad.. I had just read an article about this app and was going to ask about it around here... Have you contacted the app developer and let them know??
Click to expand...
Click to collapse
TimmyDeans method, will avoid the crappy keyboard, although you can turn off functions to make it behave.
One of the important things, is the CPUID (I believe it's called) number it generates.
For anybody considering messing with things, this is a number you should always write down, and keep in a safe place.
As if you ever get a true "brick", you will need this number. And if you have a true brick, you won't be able to get it.
Just some friendly advice from a learned person.
VERY good advice from Moscow Desire, another hint is if you have connected your a500/501 to a pc then you can use an app (can't remember what its called) to find the cpuid off the pc. Its available here on xda but I seem to have misplaced it on my pc or I'd give you the name....
So I'm going to go out on a limb and say that there is no solution to root a TP that's already applied the 2.0 update?
I've tried the root methods already obtainable on here and they don't work. I'm guessing (more hoping) that someone is working on finding a solution.
Makes me sad. A co-worker updated it for me because "it said it needed to update it so I did it for you"... *sigh*
OTA2 removed the exploit unless you were already rooted and used Voodoo Rootkeeper to maintain root during the update. I haven't heard the outcome with regards to 2.5. I don't want to risk root so won't be updating unless it's safe.
2.5 is out ? which your version of tablet ?
16gb us. Was delivered last week.
Yeah, I didn't have it rooted before so yeah.
Either people like us find a way to downgrade or wait until a new exploit is found. The former seems easier but my knowledge of these things isn't very high...
Yeah, I'm not sure how to either. I'm good at following directions but when a "friend" upgrades your device for you...
As for downgrading, I don't think that'll be an option until someone finds a Lenovo rom flash utility.
byersbw said:
16gb us. Was delivered last week.
Yeah, I didn't have it rooted before so yeah.
Click to expand...
Click to collapse
2. 5 was not available to US last week. How did you get it? Supposedly it's still going through certification. 0086_US is 2.0. What version are you?
Oh hell.... I've been reading too many posts on the Lenovo forums. My apologies, I am running OTA 2.0 NOT 2.5. I will correct my first post and title.
I'm running ThinkPadTablet_A310_02_0039_0086_US.
Okay. Thanks. No worries, but was scratching my head, looking puzzled.
Haha! I can understand. I have that look a lot sadly. I appreciate you telling me as I had no clue as to what exactly I was saying.
Now, if anyone knows someone on the inside at Lenovo that could get the flash utility...
LOL If only.
And now we wait. Did NOT expect CM9 to come out so fast and be working so didn't care much for root otherwise. Oh well, that was my fault and I knew I'd lose root for the time being. Now I wait patiently, since the primary work of the developers now is making CM9 to work properly so w/e.
Why isn't there a way to downgrade the rom to 075? The tab has a recovery boot. If it could be downgraded, it could then be rooted , then updated.
No way to downgrade, unless you know something the rest of us are unaware of. There's a bunch of folks that either can't root at all, or took OTA2 before getting root/without preserving root. We've been told that there's nothing to be done for the time being.
I don't know how to do it, but I know that's how other tabs got around the problem. I only say it in case someone does.
AFAIK, the problem is the recovery's signature check.. if it recognizes that the update.zip to flash is older than the build actually installed, it won't install the new ROM.
Thanks. Noob enough that I couldn't explain it, just knew it doesn't work.
YassinTP said:
AFAIK, the problem is the recovery's signature check.. if it recognizes that the update.zip to flash is older than the build actually installed, it won't install the new ROM.
Click to expand...
Click to collapse
I wonder what it takes to defeat the check? There must be an update script that performs that check. Editing elements of the update script has been the key to other "can't be done" situations.
http://forum.xda-developers.com/showthread.php?p=22918839[WIP][4.0.3]ICS CM9 ThinkPad Tablet PORT
I'm going to keep putting forth suggestions instead of claiming something can't be done. Afterall, the point of this entire forum is to work togther to overcome obstacles.
While I don't know a lot about these things, if it could be done, it would have been. This forum is overflowing with posts from owners of all kinds devices asking how to downgrade their respective device so they can take root. It's not an uncommon request, and one that I have researched for another device, only to find the same answer. Hey if you find out how to do it, you'll make a fortune.
Two other tablets, the Flyer and the View downgrade to gingerbread, then unlock bootloader, then root, then update to honeycomb, then custom roms are applied. They got the idea from another tab, the Iconia, who got it from the Transformer . . .
I'm just trying to push good and bad ideas to someone with the skills. It's about not taking 'no' as an answer.
Here's the thread for Flyer/View:
http://forum.xda-developers.com/showthread.php?p=21028879[Procedure]No HTC unlock downgrade HC-GB for official OTA