Related
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 would like to get the OTA update that comes out today, but assume I cannot do that with root and the custom recovery. Are there directions somewhere on how to do this for the unrevoked3 setup? Thanks.
If you are running a rooted stock rom and all you've done is push super user, busybox, and maybe a modified host file for adfree, I don't understand why you would need to unroot to receive the OTA update. None of the core system has been modified. Am I totally off base here? To my mind, the worst that would happen is you would loose root.
need stock recovery to flash the ota properly. downgrade via the instructions posted in this forum and do the two ota. then reroot using unrevoked 3
I'd just wait for the devs to clear the new OTA. Didn't take long with the EVO.
No need to jump the gun quite yet...
shoman24v said:
I'd just wait for the devs to clear the new OTA. Didn't take long with the EVO.
No need to jump the gun quite yet...
Click to expand...
Click to collapse
Yeah, this is what I'm waiting for. A similiar EVO solution to the OTA
seriously, you open a thread to answer your other thread? while the answer you looking for is right in the 1st page.
I've reported both threads and suggested a temp ban. **** on the first page there is a huge orange font telling me how to install the ota. I wish this phone woulda came out on anything but verizon. To many kids on verizon....and idiots.
Lol
Sent from my Droid Incredible using the XDA App
I'm not issuing warnings yet for questions posted in development which may fall under that scope. I have requested a Q&A sub-forum be created for DI. We'll see how that pans out. Until then, please post questions in the thread where you believe your issue is arises. Otherwise, please post questions in the DI/General sub-forum until a Q&A forum is created. Thanks!
Question is pretty straight foward. Do I have to unroot? Do I lose root if I update and have to wait until the real froyo is rooted?
Sent from my SPH-D700 using XDA App
Very quickly (perhaps hours) after the official Samsung update becomes available OTA, one of the developers here will surely post a stock rom for Froyo that is already rooted and Clockwork Recovery ready. There will probably be versions flashable by both Odin and Clockwork. Custom roms will be updated soon after that.
To actually answer your question you would most likely be safe with just using odin back to an older build 2.1 then let the ota take over after you boot in to your homescreen.
However, answering your question completely. Losing root is a big maybe better yet a most likely. There is a root already out that i'm almost positive will work with the official 2.2 also though.
What if I just want to update to froyo using my phone and then root later?
Sent from my SPH-D700 using XDA App
iwantAdollar said:
What if I just want to update to froyo using my phone and then root later?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
That would be a bad idea because it's possible that samsung/sprint will have patched all the currently known root exploits. Most likely there will be a flashable zip available on xda within hours of release that will let you maintain root. The froyo update can be altered easily to maintain root but if you use it unmodified to update and then expect to reroot you will likely be screwed.
So far I have yet to flash one OTA that has intervened with root...though doesn't the exploit effect ADB which google needs to fix..I dont think its that simple to just patch up..
If someone is rooted but has not modifed their phone in any way or removed any stock apps, would they still be able to receive OTA?
gTen said:
So far I have yet to flash one OTA that has intervened with root...though doesn't the exploit effect ADB which google needs to fix..I dont think its that simple to just patch up..
Click to expand...
Click to collapse
There have not been any major OTAs yet so I don't see why that would be much of an argument that this huge OTA won't kill root. We had OTA's on the hero that preserved root and others that patched it. If you want to go ahead and take your chances with the OTA be my guest, but I was just trying to let the OP know that the risk to reward ratio is way to high in my opinion.
richse said:
There have not been any major OTAs yet so I don't see why that would be much of an argument that this huge OTA won't kill root. We had OTA's on the hero that preserved root and others that patched it. If you want to go ahead and take your chances with the OTA be my guest, but I was just trying to let the OP know that the risk to reward ratio is way to high in my opinion.
Click to expand...
Click to collapse
The ops question is whether or not the OTA would not work if he is rooted..similar to removing stock apps..hence I answered based on that, not maintaining root...
Elixis said:
If someone is rooted but has not modifed their phone in any way or removed any stock apps, would they still be able to receive OTA?
Click to expand...
Click to collapse
Sent from my Epic 4G
Yes u will still get ota and it should work fine. U might need to reroot after but that's all. The 2.2 ota might break root on ur current setup, but I don't think the update will patch the root exploit so u should be able to run the same oneclick and get root again.
how about we wait till it happens? it could all change depending on what the OTA update does to our phones. The advice has always been wait ... Wait.. and wait.. when it is safe then do the OTA.
gTen said:
The ops question is whether or not the OTA would not work if he is rooted..similar to removing stock apps..hence I answered based on that, not maintaining root...
Click to expand...
Click to collapse
Maybe you should try reading the OP again. It says:
iwantAdollar said:
Question is pretty straight foward. Do I have to unroot? Do I lose root if I update and have to wait until the real froyo is rooted?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
He was asking a lot more than if he would get the OTA. I answered his question and gave some advice. You chimed in with some crap about never having lost root with an OTA. That was crap advice so I responded.
richse said:
Maybe you should try reading the OP again. It says:
He was asking a lot more than if he would get the OTA. I answered his question and gave some advice. You chimed in with some crap about never having lost root with an OTA. That was crap advice so I responded.
Click to expand...
Click to collapse
I could have sworn the question was different when I read it :/..and I'm pretty sure I reread it after you posted..but I dont see edited, unless it got lost or..hmm..am I going senile? :/ lol
So i recently rooted my MT4G and all and that really killed my brain haha. And i wasnt sure if i wanted to keep it rooted. So i read one of the post how to unroot. I was quite confused. Its pretty much like the same process as to root it. Now i watch a video on youtube where a guy used a program to root it and unroot it was With a special program or something and i was curious to know if anyone was working on something like that or knows of something like that in the future.
Even though its a different HTC phone. I was just wondering if some day it will be that easy to root and unroot.
I cant post a link yet because this is my first post. but go to youtube.com> seach How to unroot your mytouch 4g. And one came up as How to Root and Unroot your Samsung vibrant. 2.24
There are guides on how to root and unroot in the android development section. I can't imagine why you would want to unroot? it doesn't hurt anything and even if you never install a custom rom it is still good to have to backup your current rom and apps with ROM Manager and titanium.
Although the process is not a one click solution it is almost. temp root with visionary r14. Copy one file and run it from the terminal app on the phone then use visionary r14 to permroot with one click
Please post questions in Q&A Section.
Well it did hurt the wifi. Cause i keep getting Error. And when i looked at the solution patch to fix it. i went what the ****?!?!?! im more of the visual learner. If there are videos on how to root/unroot or whatever it would make my life alot easier.
To unroot its the same process as to rooting just put the unroot folder in?
or should we use KFU 0.9. I ask because IMHO, this forum has the most confusing series of threads on rooting/recovery/TWRP installation that I have ever read.
Without meaning to be disrespectful to the valiant efforts of the devs, I informally count at least ten times the number of posts stating issues as for successes and every time I check, there is yet another "method" for unbricking or installing, etc...particularly for the notorious yellow triangle.
Could one or more mods please clean up this forum to provide a guiding light.
BurritoRoot is the only software root method available, so yeah, it's relevant. KFU uses it to perform the root, it doesn't have its own exploit or rooting method. It was created to make common tasks more convenient, so it compiles all kinds of different functions into one application. There's nothing in KFU that can't also be done manually (as far as I know), but it can sure makes things a hell of a lot faster.
kfu .9 seems to have a serious problem with the recovery image that is part of the zipped file. It is an 8 kb file. It is the wrong file. The correct file is 10,624 kb.
If you are going to use the script, then for goodness sakes copy the proper .img file into the Recovery directory. If you need help finding it, it's at:
http://teamw.in/project/twrp2
I agree 100% the kindle fire forum needs better flow and direction showing people exactly what needs to be done if you want to root and flash Roms on a brand new fire. I see things like burritoroot, twrp, kindle fire utility v.9 , ext... what do we do first?
Sent from my Kindle Fire using xda premium
You do realize that the kindlefire utility is just a script which grabs the various pieces to do the rooting?
In the batch file (which makes up the kindlefire utility)
Code:
set twrpurl="http://techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img"
Which IS the correct twrp install image...
Also, the website for the TWRP project was down a lot of the day, so perhaps you tried it when it was down and got a truncated corrupt file?
docfreed said:
or should we use KFU 0.9. I ask because IMHO, this forum has the most confusing series of threads on rooting/recovery/TWRP installation that I have ever read.
Without meaning to be disrespectful to the valiant efforts of the devs, I informally count at least ten times the number of posts stating issues as for successes and every time I check, there is yet another "method" for unbricking or installing, etc...particularly for the notorious yellow triangle.
Could one or more mods please clean up this forum to provide a guiding light.
Click to expand...
Click to collapse
Videos or links to videos would be tits too!
Sent from my Kindle Fire using xda premium
I agree with the others as far as the rooting of the Fire has become mass confusion. Ever since 6.2.1, there has been no "sure way" of rooting this firmware. There are several "guides" and "official ....", and personally, I'm not sold on any of them.
I was rooted prior to the 6.2.1 update, and I'll stay unrooted until a new root procedure is given that has a better success rate than the other 10 procedures posted.
Personally, I think only a MODERATOR should be able to title a thread as "Official".
This is my official opinion.
YMark said:
I agree with the others as far as the rooting of the Fire has become mass confusion. Ever since 6.2.1, there has been no "sure way" of rooting this firmware. There are several "guides" and "official ....", and personally, I'm not sold on any of them.
I was rooted prior to the 6.2.1 update, and I'll stay unrooted until a new root procedure is given that has a better success rate than the other 10 procedures posted.
Personally, I think only a MODERATOR should be able to title a thread as "Official".
This is my official opinion.
Click to expand...
Click to collapse
Burrito root works perfectly fine, what're you talking about
YMark said:
I agree with the others as far as the rooting of the Fire has become mass confusion. Ever since 6.2.1, there has been no "sure way" of rooting this firmware. There are several "guides" and "official ....", and personally, I'm not sold on any of them.
I was rooted prior to the 6.2.1 update, and I'll stay unrooted until a new root procedure is given that has a better success rate than the other 10 procedures posted.
Personally, I think only a MODERATOR should be able to title a thread as "Official".
This is my official opinion.
Click to expand...
Click to collapse
You are mistaken, BurritoRoot is a sure way of rooting it, it is 100% effective at what it does. It restarts adbD as root.
It is an official thread, as it's mine, and I wrote the damn thing. Other people were making threads about it. I asked a moderator to sticky it so people would stop using the threads started by un-associated people.
As far as 10 procedures, I have only seen 2. One using a factory cable/hardware hacking and Burrito root.
the other 8 or so are just people telling you how you can use BurritoRoot.
docfreed said:
or should we use KFU 0.9. I ask because IMHO, this forum has the most confusing series of threads on rooting/recovery/TWRP installation that I have ever read.
Without meaning to be disrespectful to the valiant efforts of the devs, I informally count at least ten times the number of posts stating issues as for successes and every time I check, there is yet another "method" for unbricking or installing, etc...particularly for the notorious yellow triangle.
Could one or more mods please clean up this forum to provide a guiding light.
Click to expand...
Click to collapse
Burrito Root is relevant because... its the only way to root 6.2.1 without using a factorycable, or doing hardware hacking.
If you read/watch KFU you will see he is using a custom version of BurritoRoot I wrote for him.
KFU uses a version of BurritoRoot Jcase wrote specifically for me out of generosity to make KFU relevant again and help people out.
My tool is not to take away from what jcase does, but rather take what he has given us, and try to make things better.
YMark said:
I agree with the others as far as the rooting of the Fire has become mass confusion. Ever since 6.2.1, there has been no "sure way" of rooting this firmware. There are several "guides" and "official ....", and personally, I'm not sold on any of them.
I was rooted prior to the 6.2.1 update, and I'll stay unrooted until a new root procedure is given that has a better success rate than the other 10 procedures posted.
Personally, I think only a MODERATOR should be able to title a thread as "Official".
This is my official opinion.
Click to expand...
Click to collapse
Hai, it are legit
TheDeadCpu said:
Hai, it are legit
Click to expand...
Click to collapse
i R developer
I do not believe that burrito root is the problem at all, in my opinion this is very str8 forward way of rooting. I think that the real problem that this thread was started over is people trying to install twrp & firefirefire. So many people keep getting stuck in a boot loop, and is very hard to follow what the problem or the actual fix was. There should be a new thread started stating the official way of installing twrp, firefirefire, and cm7. Honestly to stop the confusion completely a video of one doing it step by step would be the best resolve for this. jcase did an amazing job with burrito root and is NOT the problem at all so to answer the question is burrito root relavent? It is not only relavent but the only and easiest way to root!!! Keep up the great work jcase
[-_-] said:
I do not believe that burrito root is the problem at all, in my opinion this is very str8 forward way of rooting. I think that the real problem that this thread was started over is people trying to install twrp & firefirefire. So many people keep getting stuck in a boot loop, and is very hard to follow what the problem or the actual fix was. There should be a new thread started stating the official way of installing twrp, firefirefire, and cm7. Honestly to stop the confusion completely a video of one doing it step by step would be the best resolve for this. jcase did an amazing job with burrito root and is NOT the problem at all so to answer the question is burrito root relavent? It is not only relavent but the only and easiest way to root!!! Keep up the great work jcase
Click to expand...
Click to collapse
Precisely
Thanks
[-_-] said:
I do not believe that burrito root is the problem at all, in my opinion this is very str8 forward way of rooting. I think that the real problem that this thread was started over is people trying to install twrp & firefirefire. So many people keep getting stuck in a boot loop, and is very hard to follow what the problem or the actual fix was. There should be a new thread started stating the official way of installing twrp, firefirefire, and cm7. Honestly to stop the confusion completely a video of one doing it step by step would be the best resolve for this. jcase did an amazing job with burrito root and is NOT the problem at all so to answer the question is burrito root relavent? It is not only relavent but the only and easiest way to root!!! Keep up the great work jcase
Click to expand...
Click to collapse
In my post earlier, I was awkwardly trying to say this. No disrespect meant to JCase. In fact, a big THANKS. I'm trying to use this burrito procedure now, only from a Mac.
jcase said:
Precisely
Thanks
Click to expand...
Click to collapse
Most definitely
I would hate for people to get the wrong idea about such a well written method when the confusion lies with something entirely different. I am working on going back to factory default on my kindle, and will work on a video that hopefully will clear up the confusion with the twrp, and firefirefire install correctly...
As for people trying to install burrito root here is a video that is correct and fairly simple to follow...!
http://www.youtube.com/watch?feature=player_embedded&v=KapnjR89ICA
---------- Post added at 09:29 PM ---------- Previous post was at 09:24 PM ----------
YMark said:
In my post earlier, I was awkwardly trying to say this. No disrespect meant to JCase. In fact, a big THANKS. I'm trying to use this burrito procedure now, only from a Mac.
Click to expand...
Click to collapse
A great way to show your thanks to a developer that uses his time to make our lives a little easier is by donating to them a little goes a long way, and really proves to the dev that they are and should continue to keep up the fabulous work... I will not link jcase's donation link in this post because I am not aware what the rules are on that but I am sure if you have all found his root then finidng the donation site is not far from that..!
YMark said:
In my post earlier, I was awkwardly trying to say this. No disrespect meant to JCase. In fact, a big THANKS. I'm trying to use this burrito procedure now, only from a Mac.
Click to expand...
Click to collapse
The thing is BurritoRoot is just for one thing, starting adbD as root. Everything after is entirely unrelated, and had nothing to do with me. I haven't even laid hands on a kindle fire yet so I can't even comment on any of it, nor do I know the specifics.
With OSX I believe you can just run adb from developer.android.com as root without any system changes, if its like linux.
jcase said:
The thing is BurritoRoot is just for one thing, starting adbD as root. Everything after is entirely unrelated, and had nothing to do with me. I haven't even laid hands on a kindle fire yet so I can't even comment on any of it, nor do I know the specifics.
With OSX I believe you can just run adb from developer.android.com as root without any system changes, if its like linux.
Click to expand...
Click to collapse
I rooted my Fire yesterday using a Mac and it took hardly 2-3 minutes. All the commands are same as given in the thread at rootzwiki. Just fire up terminal after setting up adb. Nothing special needed. No drivers or changing usb.ini needed. It detected Kindle fire right away. Works without a problem.
Big Thanks to all the developers here and all there hard work. The work that has gone into the Kindle Fire in such a short amount of time is Amazing.
I first looked at the title of the thread and thought - is this guy on crack? But I thought about it and with the updates and different root method the forum is pretty confusing, especially if someone just got a Kindle Fire over Christmas and just showed up here. I am rooted and using the secured pre-rooted 6.2.1 boot image Not the OTA and I am not sure what to do to prepare for the next OTA.
I think it would probably help if someone(I'd do it but I am a bit confused, too) did a short "START HERE TO ROOT thread. Something like"
6.2? ---- rooted? -------- Go here
unrooted? ------ Go here
6.2.1? ---- unrooted OTA? ------------------ Go here (KFU - FFF/TWRP/Burrito)
pre-Rooted Boot image ------- Go here/ do nothing?
... just a suggestion