[q] tried to root - Droid Incredible Q&A, Help & Troubleshooting

I tried to root unrevoked 3 but i get a message that my firmware is new? any help?

Desertburn said:
I tried to root unrevoked 3 but i get a message that my firmware is new? any help?
Click to expand...
Click to collapse
Read on the help page prior to rooting so remembered it being mentioned:
The program says “Error: failed to get root. Is your firmware too new?”
If you're on EVO 4G, we've seen this happen with some applications from the market that cause incompatibilities; try uninstalling other apps. If you're on Wildfire, then the message is as it suggests; your firmware is in fact too new, and has the vulnerability that we use to get root patched. Sorry.
Click to expand...
Click to collapse
Bet it applies to Dinc's also

I got that three times today. Then I realized I had it mounted as disk drive. Make sure you have it set to charge only. Then it should work. I was on the latest OTA from the November RUU with S-ON from taking it to VZW. My warranty was expired anyway, so I just rerooted. Long story. So the latest Unrevoked does root the newest firmware. For now. Won't be surprised if the Gingerbread update patches it.

Related

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

Rooted & Getting System Update?!?!?

So I have stock 2.2... rooted.... and I removed verizon crapware.
I just got the notification that an update is ready for me? this is the one that contains the verizon app store... as well as I think a new kernel.
Is it safe to install? would it even install? If I did would I lose root?
You would loose root if it takes.
The update may fail depending on if it checks for stock apps. Not sure if this update will.
Sent from my Incredible
thehoovie said:
You would loose root if it takes.
The update may fail depending on if it checks for stock apps. Not sure if this update will.
Sent from my Incredible
Click to expand...
Click to collapse
Well...since the root process also gives s-off... I'm a little confused about all of this. Shouldn't that let me get root back? and wouldn't the update fail since I don't have stock recovery?
Do I say install? Aaaaaigh
If you let it try to restart and install the update ClockworkMod will deny it, and the notification will go away for a while (either one day or one week, I can't remember).
I got the notification an hour or so ago on myn's warm twopointtwo.
NYC Coyote said:
Well...since the root process also gives s-off... I'm a little confused about all of this. Shouldn't that let me get root back? and wouldn't the update fail since I don't have stock recovery?
Do I say install? Aaaaaigh
Click to expand...
Click to collapse
Some one might be better able to explain root vs. S-OFF than I but ill give it a try.
Root is for your operating system. It's like in winblows having administrator privileges so you can execute high level commands, modify system settings, etc...
S-OFF allows for your phones bootloader (like a PCs BIOS) to flash unsigned files. So, if we do get an update that removes root, we can flash a custom recovery program, to then install a ROM that does have or can be rooted.
Do a backup. I don't think the update will install or stop bugging you to do it. You should be able to modify your build prop to stop the messages.
http://forum.xda-developers.com/showpost.php?p=9123362&postcount=9
Sent from my Incredible
I'm rooted and have S-Off, standard 2.2 ROM.
I would like to apply this OTA when it arrives, mostly because I'm a developer and have posted a few apps into the VCast store. Need to confirm they are there.
So should I hold off on applying it, or assume I can just use Unrevoked to re-root after the OTA?
greno1 said:
I'm rooted and have S-Off, standard 2.2 ROM.
I would like to apply this OTA when it arrives, mostly because I'm a developer and have posted a few apps into the VCast store. Need to confirm they are there.
So should I hold off on applying it, or assume I can just use Unrevoked to re-root after the OTA?
Click to expand...
Click to collapse
+1 for this, I just want to install this for the sake of being up-to-date. I need my precious root, though.
I would like to apply this OTA when it arrives, mostly because I'm a developer and have posted a few apps into the VCast store. Need to confirm they are there.
Click to expand...
Click to collapse
Why can't you look in the VCast store otherwise? If your phone is not the newest version then it won't have access to it?
Yeah... I would actually love to be able to install this... Especially since if I read correctly I would keep root.
As for the bloat, I can just remove it like the other bloat...
Sent from my HTC Incredible
I want this update but I'm on virtuous 3.1 and didn't get it... I want the apps and what not
Sent from my Incredible using XDA App
Mostly because I'd like to be able to check my vCast stats and comments from my phone, plus I think it's a good idea to be a user of the service if I'm selling apps on it.
*I posted this in another thread, copying here*
We have several Dinc's here at work. The only phones to receive this update so far are the slcd incredibles. Amoled doesn't seem to be getting it. And there appears to be a side effect after the update is applied, if you had a bluetooth device connected you need to unpair and re-pair the device. People are noticing that the scrolling seems much faster after the update so I'm going out on a limb and assuming the update had something to do with updating the slcd drivers.
Also had an issue on one where the phone wouldn't boot up after the reboot until the battery was pulled out and put back in.
***This did not break root on any of the phones***
Carnage9270 said:
*I posted this in another thread, copying here*
We have several Dinc's here at work. The only phones to receive this update so far are the slcd incredibles. Amoled doesn't seem to be getting it. And there appears to be a side effect after the update is applied, if you had a bluetooth device connected you need to unpair and re-pair the device. People are noticing that the scrolling seems much faster after the update so I'm going out on a limb and assuming the update had something to do with updating the slcd drivers.
Also had an issue on one where the phone wouldn't boot up after the reboot until the battery was pulled out and put back in.
***This did not break root on any of the phones***
Click to expand...
Click to collapse
Mine is one of the originals (had it since day one) and I received the OTA... it just didn't take cause I'm rooted (guessing it has something to do with replacing the recovery with clockwork.
I'd love to know how to apply it in case it was more than just crapware (which I will uninstall since i'm rooted)
NYC Coyote said:
Mine is one of the originals (had it since day one) and I received the OTA... it just didn't take cause I'm rooted (guessing it has something to do with replacing the recovery with clockwork.
I'd love to know how to apply it in case it was more than just crapware (which I will uninstall since i'm rooted)
Click to expand...
Click to collapse
I'm in the same situation, rooted original Incredible with Clockwork
This seems to be the info on the ota.
http://theflickcast.com/2010/11/12/htc-droid-incredible-ota-update-rolling-out/
And here's a link if you want the vcast apk
http://phandroid.com/2010/11/09/dro...ate-goes-out-today-v-cast-apps-now-available/
Carnage9270 said:
This seems to be the info on the ota.
http://theflickcast.com/2010/11/12/htc-droid-incredible-ota-update-rolling-out/
And here's a link if you want the vcast apk
http://phandroid.com/2010/11/09/dro...ate-goes-out-today-v-cast-apps-now-available/
Click to expand...
Click to collapse
I'd like those bug fixes, but it's not worth losing root :/
So it looks like someone will need to grab the OTA update... and repackage it as an update.zip for clockwork

[Q] Should I appy the OTA update before rooting with Rage and GFree?

So I'm finally suppose to get my G2 tomorrow by the end of the day according to the UPS tracking, I got mine free with the promotion deal that ends today. I am not just asking a question without looking for myself, I have been reading about root and how to do it for the past week. I would like to know if I should apply the OTA update before I root it. Should I? I have read about bricking a phone and if your at a certain degree of screwed and you are post OTA, then you are totally screwed. But I don't remember if it was post OTA or after you have applied the OTA. To avoid a total brick, should I apply the OTA or not? Or to keep it simple, should I apply the OTA before I root or not? Or does it not matter?
I am sure if you are getting the phone tomorrow it will already have the update on it. If it has Wi/Fi calling it has the update. You can root with gfree either way. Check out the vision wiki page and it takes you step-by-step.
shuka325 said:
I am sure if you are getting the phone tomorrow it will already have the update on it. If it has Wi/Fi calling it has the update. You can root with gfree either way. Check out the vision wiki page and it takes you step-by-step.
Click to expand...
Click to collapse
Yes, I have read the Vision's root tutorial in the Wiki more than 3 times now. But if I were to brick it, would it be safer to be pre OTA or to have already applied the OTA? Because I have read something about if you brick it and are post OTA then you can't fix it with that signed .zip file from HTC. I know that it MIGHT already be pre applied to the phone when I get it but I just want to know which is safer if its not already applied.
KoolKidsKlub said:
Yes, I have read the Vision's root tutorial in the Wiki more than 3 times now. But if I were to brick it, would it be safer to be pre OTA or to have already applied the OTA? Because I have read something about if you brick it and are post OTA then you can't fix it with that signed .zip file from HTC. I know that it MIGHT already be pre applied to the phone when I get it but I just want to know which is safer if its not already applied.
Click to expand...
Click to collapse
You are right if you have 1.19 pre OTA don't apply the update, because if something goes wrong we have a full PC10IMG for 1.19 to restore your phone, we don't have one for 1.22 OTA.
Sent from my HTC Vision using XDA App
KoolKidsKlub said:
So I'm finally suppose to get my G2 tomorrow by the end of the day according to the UPS tracking, I got mine free with the promotion deal that ends today. I am not just asking a question without looking for myself, I have been reading about root and how to do it for the past week. I would like to know if I should apply the OTA update before I root it. Should I? I have read about bricking a phone and if your at a certain degree of screwed and you are post OTA, then you are totally screwed. But I don't remember if it was post OTA or after you have applied the OTA. To avoid a total brick, should I apply the OTA or not? Or to keep it simple, should I apply the OTA before I root or not? Or does it not matter?
Click to expand...
Click to collapse
Generally speaking, I would say that you should root the phone before you apply the OTA update.
I don't have a G2, I am on a DZ, so my suggestion is only general.
I accidentally let mine update after I bought it as I hadn't had a chance to read through the rooting guides yet. I actually did the hex edit version revert but I'm not so sure that was even necessary. I've since run gfree on the 1.22 OTA updated G2 with no problems.
I think you would have to be EXTREMELY unlucky to brick your phone with gfree pre or post OTA. This is due to you controlling all that goes to the phone and if it you type something wrong (minus eng hboot of course) it simply won't take on the phone, giving you an error message and you just have to retype it. Really no way to brick if you just want to root and s-off.

Which root method should I use

Hi guys I have another question and I am thinking I may be able to acheieve re-root by using unrevoked, but I am unsure.
My system:
Version -2.15
PRI -2.15
Software version 5053-651-1
System - 2.3.3
Kernel version - 2.6.35.10-g13578ee
The above is the current information on my phone which has an update available but I haven't performed that task yet. My question I know there is a new root for those which have upgraded to the new gingerbread, but if am correct I don't thing my replace phone has been upgraded yet with the above information listed. Since I knew I was getting a replacement phone i assumed the software info would show it as ver 2.16 which requires the new rooting method? Am I correct in this assumpstion? Also since my system hasn't been updated yet can I still use UNrevoked3 to re-root? I know it seems lenghtly but I was attempting to be clear as possible to get the best answer before I proceeded with either the rooting method or the update.
Only way is for you to root is to use revolutionary.io only way for gingerbread
Should I update my phone before I root then?
Hey,
Yeah you will need to use revolutionary, but dont worry just google it you will get youtube videos walking you how to do it.
No do not update your phone, updates can always patch things and make rooting impossible (Sadface), just jump right in follow the instructions and you will be rooted and flashing roms in no time! just one piece of advice when you are rooted NEVER EVER accept an OTA update otherwise you might just kill your root, or worse D:!
Goodluck my friend! if you need anything just pm me!
Stevo
RamesisX said:
Should I update my phone before I root then?
Click to expand...
Click to collapse
You could root then just flash the latest stock rooted rom. Its up to you really I would just root now instead of updating
Yes I too learned that you must root first, a few months ago i accepted the Gingerbread update - mistake. Oh well, now im rooted using revolutionary.io
It was so easy, literally a few settings in the phone, install the driver, start rev.io, plug in your phone, type in your license key, done. reboot and ROM that *****
Happy ROMming

How to update to latest firmware (and keep root) after rooting?

Hello, this is my first android device, so I'm not too experienced with the whole rooting thing. My device is currently rooted with the original firmware that came on it. (Galaxy Tab S 10.5) not quite sure which version is on here or even where to find out. I tried to do an over the air update and it wouldn't let me because the device is rooted, but apparently there is a new firmware version out, so I definitely want to get on that.
How do I go about getting the latest firmware installed and getting my device rooted again?
Thanks!
How you rooted it the first time, just repeat the steps again.
Well to get an OTA as far as I know you will need to un-root and try the update, BUT if you rooted with Chainfire method probably is gona fail, because that method trips knox, and the update is going to fail.
If for whatever reason you can update, you might loose root and maybe the exploit that worked with your current build this time is not going to work.
To find out what build you have, go to settings>>>general>>about device and there it's
That's why once you root you have to block or deny the updates until the people here with more knowledge report that it's safe.
CyberManiaK said:
Well to get an OTA as far as I know you will need to un-root and try the update, BUT if you rooted with Chainfire method probably is gona fail, because that method trips knox, and the update is going to fail.
If for whatever reason you can update, you might loose root and maybe the exploit that worked with your current build this time is not going to work.
To find out what build you have, go to settings>>>general>>about device and there it's
That's why once you root you have to block or deny the updates until the people here with more knowledge report that it's safe.
Click to expand...
Click to collapse
The build number says:
KOT49H.T800XXU1ANF8
I haven't tried it for marks but auto update via Kies should work. Even if rooted. Does not affect root. And does not factory reset. i. e. you get same effect as OTA.
381
pibach said:
I haven't tried it for marks but auto update via Kies should work. Even if rooted. Does not affect root. And does not factory reset. i. e. you get same effect as OTA.
Click to expand...
Click to collapse
can anyone confirm this?

Categories

Resources