Develop Bugs

Once on 2.2, no root....

What's the best way to get rooted. I've tried te avalauncher way, they tell me I have to be rooted to use it. I've tried the simple root OTA, but when it's suppose to take you to factory restore, my phone goes to a backup/restore screen, so it fails cause I can't restore it. Please give me assistance.
I am running 2.2 from a manual install. No root.

You have to wait until the guys here find a way for p eople to root once they have 2.2 . That could take anywhere from a few days to a few weeks

Most likely you are NOT going to be able to root since you ran the OTA update for 2.2....
That is why you should read what you are flashing and know the consequences prior to doing so. Every thread that contained the download for the 2.2 leak said that it will make you lose root and the ability ( for now ) to gain root status.
You need to wait until one of the geniuses figure out a way to do it.
Sorry about your luck.

The best way is toast method...
Good luck!
Sent from my PC36100 using XDA App

UND3RTAK3R said:
The best way is toast method...you can email me if you have any problems [email protected]
Good luck!
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Not gonna work since he used the 2.2 update man.

EVOme said:
What's the best way to get rooted. I've tried te avalauncher way, they tell me I have to be rooted to use it. I've tried the simple root OTA, but when it's suppose to take you to factory restore, my phone goes to a backup/restore screen, so it fails cause I can't restore it. Please give me assistance.
I am running 2.2 from a manual install. No root.
Click to expand...
Click to collapse
1. wrong forum, should be in Q&A
2. if you did the manual update from Sprint, you will have to wait until the devs here create a root method for stock 2.2 is developed. Any existing root method will not work at all.

EVOme said:
What's the best way to get rooted. I've tried te avalauncher way, they tell me I have to be rooted to use it. I've tried the simple root OTA, but when it's suppose to take you to factory restore, my phone goes to a backup/restore screen, so it fails cause I can't restore it. Please give me assistance.
I am running 2.2 from a manual install. No root.
Click to expand...
Click to collapse
You installed the plain OTA update? The one that says "not rooted yet" on the thread title?
For each new update, HTC tries to protect its software from being rooted. The last update required users to exploit a Flash Lite vulnerability and took a while. You will probably have to wait a long time before you can root this, since it doesn't have Flash Lite.
For future reference, root first THEN update to a rooted rom released by our devs. You can't just install Ava's rom on top of stock 2.2, it prevents you from doing so.

I'm sorry but HOW MANY posts were there saying if you want to keep root, DO NOT INSTALL THE UPDATE?? Ugh...
And yes I know this isn't constructive but sometimes people just need a slap on the back if the head.
Sent from my PC36100 using XDA App

I'm in the same boat. After trying hard to resist the urge, I gave in and installed the leak. After finding the rooted version, I tried to use the 1.47 RUU to go back but it error-ed out. I'm so bummed I can't go back. Oh well; I knew the risk I was taking though so I guess I have to live with it...

Hours my my day wasted....HOURS!!!
Where's my AR-15

Wow, just wow.

I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?

Here we go again
Sent from my PC36100 using XDA App

bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
By digging thru it and finding an exploit.
Which will most likely happen for the 2.2 update as well, just not as of yet.

bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
With a ROM, you can run through the zip file and essentially take out the parts that would remove root and modify as you see fit to put on an already rooted device -- the device isn't running all the security checks on the ROM, since it's already been rooted to remove those. Much easier, almost trivial.
If you have a non-rooted device, though, you have to find a way to get the device, not the ROM, rooted. The device isn't going to take an unofficial ROM. Big difference, since you have to exploit something already on the device somehow. With the last OTA update, it was Flash Lite that could be exploited for root access to the device. With this one, no one has found a method to root the device once the OTA has been applied (and probably won't really try that hard until the official version is released, in case it closes any exploits that are in the version floating around now).

xeno314 said:
With a ROM, you can run through the zip file and essentially take out the parts that would remove root and modify as you see fit to put on an already rooted device -- the device isn't running all the security checks on the ROM, since it's already been rooted to remove those. Much easier, almost trivial.
If you have a non-rooted device, though, you have to find a way to get the device, not the ROM, rooted. The device isn't going to take an unofficial ROM. Big difference, since you have to exploit something already on the device somehow. With the last OTA update, it was Flash Lite that could be exploited for root access to the device. With this one, no one has found a method to root the device once the OTA has been applied (and probably won't really try that hard until the official version is released, in case it closes any exploits that are in the version floating around now).
Click to expand...
Click to collapse
Beat me to it and said it better.

bludragon742 said:
I'm in the same boat. After trying hard to resist the urge, I gave in and installed the leak. After finding the rooted version, I tried to use the 1.47 RUU to go back but it error-ed out. I'm so bummed I can't go back. Oh well; I knew the risk I was taking though so I guess I have to live with it...
Click to expand...
Click to collapse
I have no idea how it was "hard to resist" when AVA's rooted version showed up at 5:30pm and netarchy's showed up around 9pm. They showed up before any official sprint OTA. Lets also not forget the hundreds of posts warning people that this would happen.
bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
The "rooting method" allows you to get into restricted areas of the phone to install stuff. The act of rooting is breaking into the phone itself, not into the rom. The rom itself is fully accessable and can be hacked up, its just getting it onto the phone is the hard part.
Essentially your phone, stock, is a box that's locked from the inside. For older versions people figured out how to unlock it, so that you can put any hacked up rom onto it. The new OTA, no one knows how to get in yet.
Don't know if that makes sense. It's pretty easy to understand if you understand OS permissions.
EDIT: what the other guy said.

bludragon742 said:
I just had a thought: If there is no method for rooting yet, then how are the stock roms being rooted?
Click to expand...
Click to collapse
Because someone takes the CONTENT of the update, and applies it piece-by-piece to an already rooted image, ignoring the bits that replace HBOOT and etc.

Mad06STi said:
I have no idea how it was "hard to resist" when AVA's rooted version showed up at 5:30pm and netarchy's showed up around 9pm. .
Click to expand...
Click to collapse
I'll tell you why. The thread gets to 200 pages. There are people saying it works, sucks, bricks, awesome, hate it, stay away, success, etc. After reading 40 pages of it you have no idea up from down. Speaking from someone that is not familiar with Android rooting. It's frustrating. Then you go to one of the other 50 threads and it's all the same.
I never saw anywhere that if I installed the leak i'd be screwed. I'm fine with that though. I have 2.2 and can wait. Just annoyed i've spent hours of my day on this.

This thread was a funny read.
Sent from my PC36100 using XDA App

[Q] How, exactly, does an OTA update break your ability to root, forever?

By the question you can tell that i'm rather inexperienced at this, but a buddy of mine(who has a Droid on VZW) and i were debating whether or not doing an OTA update after you root would cause you to loose your ability to root forever.
I guess it's different on both devices, but he contends that he could unroot his droid, which is running a custom 2.2 ROM, install an OTA update, decide he doesn't like it, then just go back to a 2.1 RUU from VZW or Motorola, and then re-root.
Everything i have read here about the EVO indicates that if i am already rooted, and i accept an OTA update, then i will never be able to root again. Does never, really mean never? Or is it just mean that i won't be able to root using the current methods to root the phone?
What if i had never rooted and then accepted the OTA 2.2 from sprint that may be coming this week, would i then be able to root?
What exactly does the update do to remove the ability to get /root access to the phone? Something with the bootloader, HBOOT, or what?
Thanks for the information. Hopefully, this will settle this question for my friend and I.
Chris

OTA updates typically break any existing root methods, and disable any current root access.
Some OTA's also update the phone in a manner which prevents older official roms (that have working roots) from being reinstalled.
At that point, you have an updated rom with known roots removed, that can't be rolled back, so the only option is to wait until another root exploit is found and released. Which may or may not happen depending on the device and whoever is working on it.
Hope that helps.

You can take and accept as many updates as you want....you just have to modify that update by replacing the new hboot with the engineering one.....that way you can freely flash zip files

HTC is tricksy and they dont let you roll back after the OTA. Motorolla may not have this so your friend may in fact be able to roll back to 2.1 (however he may be misinformed as well).
To root basically they find a bug to exploit that allows us to gain access as a root user. when the OTA updates come out 99% of the time they will fix this bug. HTCat least blocks roll backs so now you are on a new version of the software that you can not go backwards and the bug to root is no longer there.
While there are normally other bugs that can be exploited to get root it is possible that there isnt one or that if there is no one can find it. if they cant find it then it could remove your ability to root permanently.

snandlal said:
You can take and accept as many updates as you want....you just have to modify that update by replacing the new hboot with the engineering one.....that way you can freely flash zip files
Click to expand...
Click to collapse
while true accepting an OTA will not give you the chance to do this for most.

ok, that explains things a little better. thanks.

I'm new to all of this as well. My EVO has already been updated OTA by a Sprint employee while I was purchasing the phone. From what I've read it looks like I'm SOL until someone cracks 2.2. One quick question though... How long did it take people to be able to root the first software on the EVO's?

[Q] Evo with Hboot 2.10 and S/W 3.70. Want to temp root to remove apps,any options?

Hello all!
First I am not new to flashing and/or hacking phones I have done many back in my WM and other phone days,just somewhat new to Android
I have looked around and I think I already know whats up but I can't say I have seen this question asked yet...I did search
Here we go,
I have an Evo with Hboot 2.10 Stock sprint flash (as in from the sprint store) and I updated to S/W 3.70 with out first checking to see what it had...(yea stupid of me )
What I want to do is Temp root into the phone,use Ti backup or whatever to make a back up of the stock apps and then remove them. I only want to remove the sprint tv,nascar,blockbuster and other apps that I don't use that don't tie into the rest of the OS.
I tried with Z4root but seeing as I have S/W 3.70 not much happens
I don't really care to flash to new rom as I am happy with the stock flash just want to get rid of apps I will never use.
So far my only option is to wait from what I have looked up,I just wanted to know if I could execute my plan with out a full system flash.
Thank you for your time and if anyone needs more info I will be glad to give it!

Yes, it seems 3.70 has patched the exploit that z4root was using to get temp root. Until the devs find a way to get a new exploit you'll have to wait.

With the rate these Devs work, I'd give it a week and you should be able to root your phone

Thanks!
I figured that was what I would have to do,but it never hurts to ask

A quick update.
It seems as if Z4root still does work even with the 3.70 OTA update...
I was searching around on Google and found people with this exact set up that had been able to temp root.
Not sure on the why yet but I had to do a reset to factory default first in order to get z4root to give me temp root(Maybe something from the update was hanging around on the phone blocking z4??). I then fired up TI backup and started to remove the Sprint stock apps I don't use and and a few other save to remove ones!
So if anyone is looking to stay on the stock sprint rom and has S/W 3.70 this might work for you as well!

And now I am fully rooted and running the sprintlovers rom. I was able to follow the guides here and get my phone flashed up.
If anyone has the same set up and needs help let me know!

How did you get permanent root on 3.70? I was going to try the'savior' adb method, but I'm afraid of bricking. I did just download unrevoked's new beta root though. I might try that when I get home
Sent from my PC36100 using XDA App

how did you get root? I'm thinking of the savior method too (same evo specs). I'm guessing you used that since you're on sprintlovers?

[Q] Incredible 2, S-off with no CWM, temp root for SU and Busybox

Hello,
I was having a lot of trouble getting s-off for my Incredible 2, I guess because of my Windows 7 64bit operating system. I eventually got it done on a desktop with vista. however, that computer had no internet access so it didnt automatically install CWM. I havent had access to that computer for a while, so iwasnt able to flash CWM on my phone.
Today I tried doing the old temp root method, and once that was done, I installed superuser and busybox from the android market. now, without a new rom, CWM, new kernel, etc, my phone seems to be maintaining root access even after reboots.
Is there anything wrong with this picture? lol... When I was researching, it seemed that most places said you can't have root without installing a rom that has it. But it seems to be sticking without installing a rom. Is there any downsides to doing it this way?
Thank you anyone for your help, and I apologize if this is in the forums somewhere, but I did do a legitimate search and came up blank.

What method did you use and did you have froyo or ginger at the time?
Sent from my ADR6350 using XDA App

Why posting in the wrong forum .
Thread moved.

i used the alpharev x method, starting with froyo, I've never had ginger on my phone.

sorry about that =/ i thought since it was root/rom related it might go in the other forum.

oh, and for the temp root portion after s-off, i used this method--
http://forum.xda-developers.com/showthread.php?t=1039015

I think there may b a problem, similar to people who used z4 root on other phones just to gain access to root apps without caring about custom roms and such. I'm afraid u will try to get pushed new ota updates, since ur still running completely stock, now I don't think that will take away your s off because of the high h boot version you now have, but it will take away your root, and I don't know how big of a deal that would b to you, but I would install clockwork recovery to prevent this. My brother had Droid x with z4 root, he left his phone alone for a while, and he came back to have gingerbread, it updated by itself cause he was completely stock with no recovery, just had Su permissions through z4, so now he's screwed and can't get root, or couldn't last time I checked. I have not even read how to install clockwork manually, I did it with the alpharevx tool, so I don't know of this would be a prob or not if u got updated to the ota gingerbread, hope this helps and makes sense, it does to me but that's a different story lol.
Sent from my ADR6350 using XDA App

lol!! it makes sense to me too.
I didn't know that phones could auto update with OTA's without user consent, pressing an "okay" button type of thing. Dammit. is there any point to having S-OFF without rooting?
installing CWM manually isn't exactly a problem, I just gotta wait til i get access to a non windows 7 64 bit computer again. hopefully that opportunity comes before an OTA is pushed to my phone.
Thank you for your input!
jeremytn86 said:
I think there may b a problem, similar to people who used z4 root on other phones just to gain access to root apps without caring about custom roms and such. I'm afraid u will try to get pushed new ota updates, since ur still running completely stock, now I don't think that will take away your s off because of the high h boot version you now have, but it will take away your root, and I don't know how big of a deal that would b to you, but I would install clockwork recovery to prevent this. My brother had Droid x with z4 root, he left his phone alone for a while, and he came back to have gingerbread, it updated by itself cause he was completely stock with no recovery, just had Su permissions through z4, so now he's screwed and can't get root, or couldn't last time I checked. I have not even read how to install clockwork manually, I did it with the alpharevx tool, so I don't know of this would be a prob or not if u got updated to the ota gingerbread, hope this helps and makes sense, it does to me but that's a different story lol.
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse

I couldn't see an advantage to just being s off, unless it allows u to use different sim cards, but I don't know, I'm no expert. The only thing I can think of is maybe it will leave the possibility of rooting open to u at a later time, but I don't know. I like my set up, its pretty much stock with some of the Verizon crap removed but I have root and can use rooted apps.
Sent from my ADR6350 using XDA App

thanks again for the input. i'll probably end up with that debloated type of rom too.

It depends on what you want. I'd say no problem if all you want is the root access.

Verizon 10/30 - Update.zip file??

Hey all, wondering if anyone has the update.zip file for the 10/30 Verizon update to Software Build: VS98511C
I have a buddy who's rooted (like me) but is receiving errors trying to install it so I'm hoping this will help. His phone is set up basically exactly the same as mine but only he has had the error and we've exhausted all possibly fixes
Thanks guys

Looking for the same.. Do we have a way to upgrade while keeping root?

I am also looking for update.zip for VS98511C.

Cyber Warrior said:
Looking for the same.. Do we have a way to upgrade while keeping root?
Click to expand...
Click to collapse
If you can update via the ota, you will keep root. I did it just fine and it's been reported from others that they haven't had a problem either. My friend's phone is having some sort of unique error that we can't figure out :/

xxxdc5 said:
If you can update via the ota, you will keep root. I did it just fine and it's been reported from others that they haven't had a problem either. My friend's phone is having some sort of unique error that we can't figure out :/
Click to expand...
Click to collapse
So you kept root while updating? No need to re-root? Any tricks like using root keeper? I never took an ota while rooted so it makes me nervous.. I always manually updated with a rooted version. I have some stuff modified and frozen.. I guess un-doing all my mods and putting things back to stock shouldnt be too much of a pain so i can take the ota. Its always been easier to just flash something though. Maybe i'll wait a few days to see if theres a better way.

If you have twrp installed and take the ota you will boot into twrp until you do a twrp terminal hack or tot/kdz back to fresh stock.

I have twrp installed also. So how do we take the update then without going into a twrp boot loop?

Cyber Warrior said:
So you kept root while updating? No need to re-root? Any tricks like using root keeper? I never took an ota while rooted so it makes me nervous.. I always manually updated with a rooted version. I have some stuff modified and frozen.. I guess un-doing all my mods and putting things back to stock shouldnt be too much of a pain so i can take the ota. Its always been easier to just flash something though. Maybe i'll wait a few days to see if theres a better way.
Click to expand...
Click to collapse
ThePagel said:
If you have twrp installed and take the ota you will boot into twrp until you do a twrp terminal hack or tot/kdz back to fresh stock.
Click to expand...
Click to collapse
marcogiudice said:
I have twrp installed also. So how do we take the update then without going into a twrp boot loop?
Click to expand...
Click to collapse
I don't have twrp installed so I'm not sure
I didn't use any tricks or special apps or anything. I saw that others took the ota while rooted and it turned out fine so I just went for it. I figured there's really no scenario I could get into that I wasn't comfortable finding a fix for so I just lazily shrugged and pushed update LOL. I didn't need to worry though as everything updated fine and normal for me.
Again though, I don't have a custom recovery installed so idk how it'll work out with twrp :/

I didnt have a custom recovery..only root with xposed and some other mods. I defrosted anything that i froze.. put back any tinkered system files..uninstalled xposed. I took the ota system update.. Everything is working great and still have root access.