Database Users

Rooting updated EVO

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.

Can the OTA update be rooted?

I'm just gonna stick with rooting. Will rooting hold up against the update or will I have to nandroid unlock and flash a stock rooted rom?

This has been asked several times. Please visit the Android development section and you will see. A little searching doesn't hurt.
Sent from my PC36100 using Tapatalk

Well there is so much information being thrown around at the moment, that I haven't been able to find a stock rooted 1.47.xx rom, either, and all I do is search.
OP: If you find it, let me know and I will do the same.

thats because one doesnt exist.

Use a patched version of the OTA or a ROM with it baked in and you keep root. Flash non-patched OTA and you loose root. eazy-peazy.
http://forum.xda-developers.com/showthread.php?t=712695

the OTA will break your root.
however, if you've already done that, you can reroot since the most recent OTA has been rooted.

Short answer is yes.
Long answer will involve you going to a different sub forum for evo and looking it up.

nenn said:
thats because one doesnt exist.
Click to expand...
Click to collapse
Ha! Thanks.....believe it or not, that actually explains a lot. I think I'll wait for a stock rooted rom to be available.

Things can change quite quickly around here:
http://forum.xda-developers.com/showthread.php?t=718889
Herein lies the answer to your quest. ;-)

seankent4uf said:
Things can change quite quickly around here:
http://forum.xda-developers.com/showthread.php?t=718889
Herein lies the answer to your quest. ;-)
Click to expand...
Click to collapse
Yea, I saw that earlier, but this is for people who upgraded via the OTA 1.47.xx and then lost root. For this to work for me, I'd have to willingly upgrade to the OTA, and then run through these steps. I don't think I want to do that.
I'm in the process of unlocking NAND now since I'm going to need to have that done in order to proceed with anything related to 1.47.xx, so once I get this done, I'll worry about finding something that works.

I am pretty sure this is what you are looking for... It is a Rooted rom, based off the 1.47 update.
http://forum.xda-developers.com/showthread.php?t=712695

or this one...
http://forum.xda-developers.com/showthread.php?t=715915

which one of those work?

I was actually running the first of the 2 links myself, since I was having major problems with my EVO, and could only use limited ROMs. It was very reliable, but I wanted the flexibility to run other ROMs. I have not run the one posted in the 2nd link, but from some of the replies, it works well also. If you are already rooted, and are comfortable flashing ROMs, I would recommend the first, since it loads just like any other ROM. It all depends on how much work you want to do.

3.2 OTA update for A501 rolling out tomorrow?

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.

[Q] Bootloader on NEW A500

Hey,
I've looked through the forum and I'm a bit puzzled how is it with the bootloader "lock" on newly purchased models as I was thinking a bit of buying A500.
I read that the bootloader only checks for checksums when booting kernel / recovery (unless set to generate them), so you can put there custom kernel (get rid of Java Android) when you root it, which I read is not a problem even with 3.2.1 .
The thing I'm puzzled about is that I read there was a BL update and some say the BL is locked since that update and others not - so if I decide to buy A500 and there will be 3.2 with the BL update on it, is it locked and requiring signed kernel image or is it still the checksum only thing?

Skrilax_CZ said:
Hey,
I've looked through the forum and I'm a bit puzzled how is it with the bootloader "lock" on newly purchased models as I was thinking a bit of buying A500.
I read that the bootloader only checks for checksums when booting kernel / recovery (unless set to generate them), so you can put there custom kernel (get rid of Java Android) when you root it, which I read is not a problem even with 3.2.1 .
The thing I'm puzzled about is that I read there was a BL update and some say the BL is locked since that update and others not - so if I decide to buy A500 and there will be 3.2 with the BL update on it, is it locked and requiring signed kernel image or is it still the checksum only thing?
Click to expand...
Click to collapse
No problem. I'll try to put it in "laymans" terms.
Manufacturers don't want you mucking with things. It causes more tech support for them, and also a bad image reputation when stupid people screw things up.
So what they do, is change bootloaders, the part that tells the tab, that the os they are loading, is 100% Acer. If it's not, it's just going to give you a silly face.
So we, here in the Acer community, try to find a way around the bootloader. And invent ways to install a operating system other than Acer.
It's an ongoing battle it seems. We find a way around it, Acer changes the rules, so we have to find another way.
The thing is, our dev's are smarter than their devs. Even HTC gave up, and just offer bootloader unlocks. Besides, they take our innovations, and incorporate them into their newer releases.
So the point is, if you buy a 500, or a 501, XDA community will give the means to unlock it. Root, so we say. And people will help you get it running right.
Here at XDA, we have many roms, from plain rooted stock roms, to cooked roms with OC kernels.

Ah, oops, placed the question incorrectly, I know how the things work around bootloaders and have designed some workarounds. I was rather asking whether new a model of A500 can run custom kernel (don't mean modifications with modules now) or not - but summarizing what you've said: every A500 can run custom kernel, right? Thanks for answering in any case.

Currently on a new A500 with root and kernel. Manufactured in December 11. whole process took an hour. Hope this helps.

Skrilax_CZ said:
Ah, oops, placed the question incorrectly, I know how the things work around bootloaders and have designed some workarounds. I was rather asking whether new a model of A500 can run custom kernel (don't mean modifications with modules now) or not - but summarizing what you've said: every A500 can run custom kernel, right? Thanks for answering in any case.
Click to expand...
Click to collapse
IIRC, only 3.2.1 locked the bootloader, so even if your a500 comes with 3.2 you're safe.
That said, even with 3.2.1 and a locked bootloader, there is a downgrade trick that allows you to go from 3.2.1 (or 3.2, or 3.1) to 3.0 and run an app called iconiaroot and acer recovery installer. Iconiaroot is like z4root, VISIONary, gingerbreak, etc and recovery installer installs CWM recovery from within android. After doing all this you can flash any rom or kernel you want.

Skrilax_CZ said:
Ah, oops, placed the question incorrectly, I know how the things work around bootloaders and have designed some workarounds. I was rather asking whether new a model of A500 can run custom kernel (don't mean modifications with modules now) or not - but summarizing what you've said: every A500 can run custom kernel, right? Thanks for answering in any case.
Click to expand...
Click to collapse
YES if your a500 has Stock android 3.2 or above.. you will have to fallow the downgrade rom flashing.Then you can flash any rom of your choice . there are several threads on this forum explaining how to do this..
Do a search for the thread by Timmy Dean.. his method i think has been called the easiest. It flashes your tablet to a rooted 3.21 stock rom thru adb . from your windows computer..
Acer has yet to plug this hole. So i would not take ANY OTA UPDATES. Im looking for ics if ever releases to plug such holes in the boot loader and stop its magic .
Happy Flashing just please understand everything before proceeding.. there are enough help i bricked my iconia threads.. Boohoo i hate to see anyone do that to such a expensive device..

Thanks. Ordered a piece
So basically I need to store UID, first x bytes in mmcblk0 (for the mmcblk0_start) from sc2k thread (http://forum.xda-developers.com/showthread.php?t=1129873) and I'm pretty much brick safe (should I screw both kernel & recovery).

Happy Flashing
That in theory will give you the resources to recover . BUT BY NO MEANS A Get of of trouble free pass..
do not flash nothing you don't trust and Fallow all instructions Carefully.. You sound well on your way to Making the best of your tablet...
Enjoy your time on xda Iconia forum. There are some awesome people on here. NO im not including myself in that .. Im just a bored thread reading chic. that repeats what i have read... nothing i know is my own work..
Happy Flashing..

erica_renee said:
Im just a bored thread reading chic. that repeats what i have read... nothing i know is my own work..
Happy Flashing..
Click to expand...
Click to collapse
Aren't we all..... Not necessarily a chic though...

Allright, all went smooth (was 3.2 preinstalled). Thanks all.

you are very welcome..
Its simple easy with just a bit of reading up front..

Can't update to latest patch

Hi,
I've already make a factory reset via settings but the update still can't install... After a little work, a RED "!" icon appears on android when trying to install it...
I'm on STOCK rom and STOCK recovery... very very strange....
Someone can help me?
Thx!

So, when you typed this thread title in did the posts you saw regarding this exact issue not seem like something you should have read?......

really can't understand... someone else had the same problem? Can't find the other post, sorry.... where is it pls?
edit: founded thx

Hello,
I'm sorry, I don't find this thread. I really searched.
I'm in the same case than asder00.
My Transformer is rooted, B50, European, and actually 9.2.1.11 official build.
The only way to update HoneyComb -> ICS was to use the version posted by MrNago http://forum.xda-developers.com/showthread.php?t=1514658<br />
Today, I tried to update to 9.2.1.17 build. I received this update, but when my tablet reboot to install it, a triangle appears at approximately 30%. Exactly the same thing than when I wanted to install ICS.
I tried to install official ROM stock ICS of Asus with CWM recovery. Doesn't work (Status 7). No error about the version. I took WW build.
Same with ROM Revolution HD.
But retried with MrNago ROM, It works.
I don't know what to do to recover working updates.
PS : I think to know about which thread you speak.
I have read it. I don't think our problem to asder00 and me (and many others) should be over there. In my case, this impossible installation didn't appear after ICS.
And, those who posted our problem didn't have solution.
PPS : Sorry for my poor english. I'm not a moron. English is not a language I use every day.

Go to this thread and download and flash the file .
Note When you have CWM you cant ota.
http://forum.xda-developers.com/showthread.php?t=1551652

Yeah, that's what I've done.
This micro update has worked with this file.
That's right, CWM is installed.
It was not when I tried to upgrade to ICS.
And if this is really source of our problem, I don't know how to remove that.
I have seen a method which match with what I've alreay done (reboot in recovery, install ROM stock... /!\ doesn't worked).
I believe I'm condemned to upgrade with files found over the web.

asder00 said:
really can't understand... someone else had the same problem? Can't find the other post, sorry.... where is it pls?
edit: founded thx
Click to expand...
Click to collapse
What did you do to fix this problem (with stock recovery and stock rom)?
I'm having the same issue, red exclamation mark. I never rooted my device.

1. Root
2. Install CWM
3. Flash update through CWM
it's really not that hard.

OK, that's a way. But keep in mind there are customers without knowlegde of rooting and stuff... what about them? The update should work, right?

ProLen said:
OK, that's a way. But keep in mind there are customers without knowlegde of rooting and stuff... what about them? The update should work, right?
Click to expand...
Click to collapse
Then you talk to Asus about it, not here.
Here is a place where people come to find information and learn how to do things.
If you just want a magic one click fix, call Asus.
I was also in a similar situation as you. I went back to stock rom and stock recovery and noticed I wasn't getting the OTA update to 9.2.1.17. Guess what?
I rooted my TF with a root kit found on this website. It literally rooted my TF with a click of a button. It was so easy.
I then installed CWM with an app posted on this website. It was just an APP. All I had to do was run the app and it installed CWM. So frigin easy
Finally, I manually flashed the update through CWM, which was made possible because some nice dude on this website posted a CWM flashable zip for the 9.2.1.17 update.
This entire procedure took less than 30 minutes.

horndroid said:
Then you talk to Asus about it, not here.
Click to expand...
Click to collapse
You're totally right about that. I'm just curious what the problem might be. Would be interesting to know.
I'm now going to use the CWM method you suggested.

Same thing.
I would like to know if someone knows why few peoples have this problem, and many others not.
Why, since ICS is came, auto updates doesn't work.
There are solutions, of course. Sometimes we can search 30 minutes, 1 hour, 2 hours, more. For some people, it's easier than for others.
And what we all are sure, if we call Asus, they don't tell us how to resolve that. They will tell us to send the tablet to them. It's not what we want.
So, if messages like that irritate you, I think you should drink a herb tea.
Or close your eyes, take a full breath, and read another thread.
Because there will be always messages like that.
I don't tell that to provoke you. I would like that you understand that when people have problems, they go where they think to find the best solutions.