Forced OTA 1.70.605.0 and rooted but stock - help :(

[Andy19]

First off, I'm sorry if I need to post this somewhere else. I figured the rooting forum would be my best option though.

The forced OTA was sneaky and just installed itself, partially, because I caught my phone where it said it was re-starting in two minutes and then pulled the battery to prevent anything else.

What should I do from here? I need my phone lol

After some Google-ing, is this what I need to try and flash before my phone tries installing the new OTA?

[ROM] Official 1.70.605.0 MR2 OTA Deodexed Rooted Busybox Mirrors Added - xda-developers


I am an idiot when it comes to this stuff and I never returned my TB to stock because I'm too worried I will mess it up. I read the the un-rooting process thread less than an hour ago after I caught my phone trying to update, but I just need a few more clear explanation steps so I don't mess it up. A friend of mine helped me root it originally, but he is out in Seattle, so I can't bother him at the present time. Haha.


If this sounds familiar to any of you, last time I did the OTA, when I didn't know you should not, I just about bricked my phone and luckily a few of you helped me out.


Thanks for the help. I do not plan on touching my phone until I am instructed on here what to do!


Andy

 

[fatboy97]

Where to start... just reading what you are saying here it doesn't sound like you should have a rooted device. you have no clear reason for being rooted. If you get the OTA, this will unroot your device. Why did you root your device in the first place???

 

[Andy19]

Where to start... just reading what you are saying here it doesn't sound like you should have a rooted device. you have no clear reason for being rooted. If you get the OTA, this will unroot your device. Why did you root your device in the first place???

I definitely should not be rooted, nor have messed with it in the first place! Haha. I rooted since my friend said it would remove all the bloatware and would unleash the phone's full potential. I had problems the first night with rooting and didn't like the BAMF layout either. So that's why I wanted stock again, but did not realize my phone would still be rooted if I just did the factory system restore.


The OTA is currently "in limbo" so to say. I'm 99% sure it downloaded since it said my phone would be restarting in two minutes and that's when I pulled the battery.

How do you know for sure it will un-root and work as "normal"? The last time I did the OTA, by accident, it tried installing and half way through installation stopped, leaving me with a paper-weight.

 

[zero neck]

If you unroot, you could load the MR2 RUU zip file without root enabled - that will bring you up to date safely, without root. There is a chance that accepting the update with root access on your phone could result in a serious problem, however most likely it will just update you to the latest release (mr2) and remove your root access.

 

[fatboy97]

I definitely should not be rooted, nor have messed with it in the first place! Haha. I rooted since my friend said it would remove all the bloatware and would unleash the phone's full potential. I had problems the first night with rooting and didn't like the BAMF layout either. So that's why I wanted stock again, but did not realize my phone would still be rooted if I just did the factory system restore.


The OTA is currently "in limbo" so to say. I'm 99% sure it downloaded since it said my phone would be restarting in two minutes and that's when I pulled the battery.

How do you know for sure it will un-root and work as "normal"? The last time I did the OTA, by accident, it tried installing and half way through installation stopped, leaving me with a paper-weight.

You did not like the BAMF layout??? I'm guess you went back to stock, is that correct??? Otherwise I don't think you would have received the OTA.

And as far as knowing what is going to happen when you put the battery back in your device is anyone's guess right now, since I don't know what ROM you have loaded right now. Part of the debloating procedure actually does say that if you install an OTA you should put all the files back onto your device and reset all permissions back to factory before an OTA to be sure your device does not get stuck installing the OTA.

Normally there a deny update button on the OTA.... but again there is no way of knowing what will happen or what's available until you put the battery back in your device and boot it up.

 

[ClintRo]

True, might as well put the battery back in an see where you are. Without a battery you have a paperweight anyhow...lol

 

[Andy19]

If you unroot, you could load the MR2 RUU zip file without root enabled - that will bring you up to date safely, without root. There is a chance that accepting the update with root access on your phone could result in a serious problem, however most likely it will just update you to the latest release (mr2) and remove your root access.

I don't know how to un-root. I would have done it a while ago, and as I mentioned in my first post, I looked at the un-rooting thread once again this morning, but I need a few more steps to make things more clear for me. I am unsure about the boot loader stuff.

You did not like the BAMF layout??? I'm guess you went back to stock, is that correct??? Otherwise I don't think you would have received the OTA.

And as far as knowing what is going to happen when you put the battery back in your device is anyone's guess right now, since I don't know what ROM you have loaded right now. Part of the debloating procedure actually does say that if you install an OTA you should put all the files back onto your device and reset all permissions back to factory before an OTA to be sure your device does not get stuck installing the OTA.

Normally there a deny update button on the OTA.... but again there is no way of knowing what will happen or what's available until you put the battery back in your device and boot it up.

Post with image software: http://forums.androidcentral.com/901802-post6.html

First OTA problem thread: http://forums.androidcentral.com/thunderbolt-rooting-roms-hacks/83969-help-asap-please.html

It's the stock sense or whatever, just rooted.

Oh and I couldn't cancel it when I tried to. The first time it happened, it ended up saying "could not connect to server". Then somehow this morning when I caught it two times, it said "user cancelled", but there was no button or anything saying I could cancel it.

 

[ClintRo]

I would wait for someone that is more of an expert than I am, but if you get impatient first thing would be to boot that baby up and see what happens. Let us know what it says.

 

[fatboy97]

I'm sorry, but I'm not sure what is the best steps right now... but you will need to boot it up sometime to see where you are.

 

[yodatom10]

I would try booting it

 

[Andy19]

Well, the reason I am worried to try booting it is due to the last OTA update which stopped and had the android character with an X.

 

[ClintRo]

I understand your concerns but not sure you have any other option at this point. What has me curious is that I didn't think rooted users should have received the update. Are you sure you are rooted?


BAMF THUNDERBOLT

 

[zero neck]

I understand your concerns but not sure you have any other option at this point. What has me curious is that I didn't think rooted users should have received the update. Are you sure you are rooted?


BAMF THUNDERBOLT

You can get the OTA with just the rooted stock rom.

Andy, i think your options are to reboot the phone, and see if it installs the update - probably this will just return you to stock with the updated software/radio, and remove root. There is a small chance it will cause a problem, however.

The other option would be to flash the root-enabled MR2 ruu in hboot, which will bring you up to date on software while preserving root, however I don't know where your phone is at as far as the OTA goes, so i don't know how safe it would be to try this.

 

[Andy19]

I'm pretty sure I'm rooted because Super User was still on once I did the factory reset forever ago since I thought that would wipe the root.

I think I will be able to flash the root enable MR2 since I flashed that other software in my other problem thread and as stated, I'm pretty sure I'm still rooted. Haha.

I just don't know if this update would cause anymore random problems for me if I try to install it and what happens if I can't access my HBoot or whatever it is to install the MR2?

 

[fatboy97]

Boot it up... you have to see where you are after it comes up... stop talking about it and do it!!! How many people have to say boot it up before you do it.

 

[Andy19]

Everything appears to be fine, as far as I know. Took a little longer to boot up.

I only had 1X for a little while, but now it's back to 3G. No 4G here.


I guess I'll see what happens and if anything crazy does, I'll obviously be back here.

I apologize for wasting your time if I did. I was just trying to avoid a bigger problem due to last time.

 

[fatboy97]

Maybe this is a good time to unroot your phone now... there is the http://forums.androidcentral.com/thunderbolt-rooting-roms-hacks/77617-auto-root-unroot-windows-updated-5-20-w-mr1-update.html

 

[Andy19]

That was what I've looked at a few times as well as this morning.

My problem is that I'm not 100% sure what to do.

If I flash the PG05IMG_MR1_no_hboot.zip, how am I supposed to flash PG05IMG_hboot_1.4.0000.zip through the boot-loader after?

I thought that first one would remove the boot-loader?

 

[PJnc284]

Assuming you are rooted and have s-off, the no_hboot.zip flashes the factory mr1 (minus s-on). If you just install that, you still have s-off. If you then install the hboot_1.4.0000.zip, it will return you back to full factory firmware with s-on. This is what you want if you're going to return a device. Flashing hboot before the no_hboot.zip could put you in a mess.

 

[fatboy97]

I'm not into reading stuff I don't need to... but unroot your phone and be done with it... if you unroot it you will not be flashing ANYTHING again... when you are unrooted and you will be getting OTA's.