Since I will be starting work next week and activating my Thunderbolt I had to return to stock & unroot
After following the instructions below....
http://forum.xda-developers.com/showthread.php?t=1009423
I noticed after the first flash, that when I shutdown and started up in bootloader it automatically asked if I wanted to update and did so almost instantaneously....
I just wanted to know if there is anyway I can confirm that I'm back to stock and unrooted... Also will I be able to get the recent update from Verizon now that I returned to stock MR1?
ace2525 said:
Since I will be starting work next week and activating my Thunderbolt I had to return to stock & unroot
After following the instructions below....
http://forum.xda-developers.com/showthread.php?t=1009423
I noticed after the first flash, that when I shutdown and started up in bootloader it automatically asked if I wanted to update and did so almost instantaneously....
I just wanted to know if there is anyway I can confirm that I'm back to stock and unrooted... Also will I be able to get the recent update from Verizon now that I returned to stock MR1?
Click to expand...
Click to collapse
Boot to bootloader and make sure S-on and no custom recovery.
Check rom for Superuser.apk
Make sure baseband matches mr1 baseband.
If bootloader wanted to update immediately, you probably left a radio PG05IMG.zip file on your sdcard. Delete it.
Yes, after returning to stock you should get the OTA. You can manually force a software update to check for OTA too.
after doing the first step, i removed the first pg05img and replaced it with the next steps file...so like i said, it just took an update and completed in seconds. I assume that was the restoring of the original bootloader. No superuser so no more root
I cant restart just yet to check if S is back ON b/c OTA update is taking FOREVER to download....setting up my screens in the meantime. Thanks bro
baseband updated?
Another quick question....
my baseband is 1.39.00.0627r, 0.01.69.0625r meanwhile this ad for the OTA verizon update has a different baseband listed, 1.39.00.0613w, 0.01.69.0613w_1
source:
http://www.techwafer.com/wp-content/uploads/2011/07/HTC-ThunderBolt-software-update.jpg
Do i have the latest, whats the deal?
THANKS in advance!
bump...anyone??? above post
ace2525 said:
Another quick question....
my baseband is 1.39.00.0627r, 0.01.69.0625r meanwhile this ad for the OTA verizon update has a different baseband listed, 1.39.00.0613w, 0.01.69.0613w_1
source:
http://www.techwafer.com/wp-content/uploads/2011/07/HTC-ThunderBolt-software-update.jpg
Do i have the latest, whats the deal?
THANKS in advance!
Click to expand...
Click to collapse
The first baseband is the OTA MR2 Radio. I'm not sure about the other one.
Source:
http://support.vzw.com/system_update/thunderbolt.html
Hit "Benefits of Software Update" and it will show you the baseband.
Related
Help.
So, my boss asks me to root his thunderbolt, so I do. Then, he goes and tries to install an OTA update on the thunderbolt and wonders why it won't work. I get into work this morning and he says, "I need you to unroot my phone so I can install OTA updates"???
I'm very confused, but hey, he wants it unrooted. Problem is, I can pull the battery, startup like normal, boot into the rooted OS and immediately the thing shuts down and tries to install the OTA update he installed.
This results in the android guy and the triangle with an exclamation point in it showing and I can't go any further.
ADB DOES see the device when I do adb devices.
How do I push the stock ROM back on to the phone and have it update that back to stock?
Help.
WHY he wants the phone unrooted or even decided to update it with an OTA ROM is beyond me.
Please and thank you in advance.
Wrong section but if the bootloader still has s-off, I would install custom recovery again and flash the rooted ota rom.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1009423
You should be able to flash the latest ota by booting into bootloader. If adb is working then I believe you can...
adb reboot bootloader
here is a link to the file you will need with instructions...
how to flash the latest ota
1. I realized too late it was the wrong section, apologies.
2. I don't need to flash a ROOTED ROM, he wants this device back to being stock UNROOTED.
Can I, using recovery, flash PG05IMG_MR1_no_hboot.zip over what is there now and go back to unroot and stock?
I use an Evo and can do almost anything on that, but the thunderbolt is a little new to me. Not my device, shouldn't have offered to root it for my boss without knowing he was going to try to install an OTA update.
Any help with unrooting and reflashing the Stock OTA would be very helpful.
It's one of the big issues with running stock rooted. Nothing stopping it from trying to update itself and screw the pooch
Honestly, if he wants OTAs just for the latest goodies/stability and battery improvements he'd be better off with something cooked... Just my opinion though
Sent from my ADR6400L using XDA App
sanjsrik said:
2. I don't need to flash a ROOTED ROM, he wants this device back to being stock UNROOTED.
Any help with unrooting and reflashing the Stock OTA would be very helpful.
Click to expand...
Click to collapse
Hmmm - not sure why you didn't just use the link that I provided? I will quote from there...
Code:
Using this RUU will wipe all data on your device!
Please make a backup of all sensitive data before
proceeding. Similarly, you will [B]LOOSE ROOT IF
YOU FLASH THIS[/B]. It is unclear right now
whether or not this version is easily rootable.
[B]PROCEED WITH CAUTION[/B]
This is not a link to a rooted rom.
thepolishguy said:
Hmmm - not sure why you didn't just use the link that I provided? I will quote from there...
Code:
Using this RUU will wipe all data on your device!
Please make a backup of all sensitive data before
proceeding. Similarly, you will [B]LOOSE ROOT IF
YOU FLASH THIS[/B]. It is unclear right now
whether or not this version is easily rootable.
[B]PROCEED WITH CAUTION[/B]
This is not a link to a rooted rom. It is a link to the full unrooted ota ruu that has been put in a flashable (from hboot) PG05IMG.zip.
Click to expand...
Click to collapse
Update: Worked like a charm.
Thanks, polishguy, that wasn't clear originally, will follow your link. Much appreciated.
sanjsrik said:
Thanks, polishguy, that wasn't clear originally, will follow your link. Much appreciated.
Click to expand...
Click to collapse
No problem. It wasn't clear originally bc I am not sure how XDA views links to "this sort of file". As in a "Romeo Uniform Uniform"
thepolishguy said:
No problem. It wasn't clear originally bc I am not sure how XDA views links to "this sort of file". As in a "Romeo Uniform Uniform"
Click to expand...
Click to collapse
I would guess it's fine considering there are an abundance of RUU links in the dev section.
When the OTA was released, I took my stock unlocked and rooted Rezound and did an RUU on it. I relocked it and RUU'd and made it completely stock.
I then took the OTA. I watched it do it, it downloaded and went into some sort of recovery mode and installed it.
I then re-unlocked it, rooted it, installed Amon Ra and then debloated and set it up. I did NOT restore a Nandroid on this phone.
And now every morning my phone is downloading the OTA and wanting to install it. If I say defer it tells me I can't. If I tell it OK, it doesn't do anything and tomorrow it will try to do it again.
What gives?
Did this phone take the update or not?
My guess is no. Go into more info on the screen that you have above.
Build starts with 1 no update.
Build starts with 2 OTA update
Build starts with 3 you took one of the early ICS Roms
Sent from my ADR6425LVW using Tapatalk
paulhoop said:
My guess is no. Go into more info on the screen that you have above.
Build starts with 1 no update.
Build starts with 2 OTA update
Build starts with 3 you took one of the early ICS Roms
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
I guess that means no? I suppose I should just RUU with the new OTA version, rather than the original and try to get the OTA to take?
SquireSCA said:
I guess that means no? I suppose I should just RUU with the new OTA version, rather than the original and try to get the OTA to take?
Click to expand...
Click to collapse
You have many paths in front of you my friend, depends on where you want to go.
It appears that you are original stock still, rooted with recovery.
Not sure what went wrong. You might want to check for a PH98IMG.zip file on root. Delete it, causes issues with HTBOOT and bootloader.
SquireSCA said:
When the OTA was released, I took my stock unlocked and rooted Rezound and did an RUU on it. I relocked it and RUU'd and made it completely stock.
I then took the OTA. I watched it do it, it downloaded and went into some sort of recovery mode and installed it.
I then re-unlocked it, rooted it, installed Amon Ra and then debloated and set it up. I did NOT restore a Nandroid on this phone.
And now every morning my phone is downloading the OTA and wanting to install it. If I say defer it tells me I can't. If I tell it OK, it doesn't do anything and tomorrow it will try to do it again.
What gives?
Did this phone take the update or not?
Click to expand...
Click to collapse
Didn't even look at the screenshots, but it took me downloading the update twice for it to completely update it. I did the exact same process, but noticed when it rebooted the first time it didn't complete the update because I checked right away and my radios didn't update. I downloaded it again and the second time it flashed everything properly.
So from what I can gather, the OTA was fairly buggy process for alot of people. That's why I even checked prior to unlocking and rerooting again. I wanted to make sure it worked properly.
mjh68 said:
Didn't even look at the screenshots, but it took me downloading the update twice for it to completely update it. I did the exact same process, but noticed when it rebooted the first time it didn't complete the update because I checked right away and my radios didn't update. I downloaded it again and the second time it flashed everything properly.
So from what I can gather, the OTA was fairly buggy process for alot of people. That's why I even checked prior to unlocking and rerooting again. I wanted to make sure it worked properly.
Click to expand...
Click to collapse
Yeah, seems like the best way to do it is to just grab the latest RUU and install that and call it a day. No having to worry about it taking, it already includes the latest radio and stuff.
How do you tell what radio your phone is running??
jmorton10 said:
How do you tell what radio your phone is running??
Click to expand...
Click to collapse
Settings->Phone->Software Information->More->
Baseband version is radio
paulhoop said:
Settings->Phone->Software Information->More->
Baseband version is radio
Click to expand...
Click to collapse
Lol, I realize that but what is it supposed to say??
Edit: NVM, I found the info
OK so here is the story and I was debating if this is the right place to post but I do feel it is more on the developing side. I originally rooted and unlocked my bootloader following Casuals method and everything was just fine. I had an option to sell the phone in preparation for buying the GS4 so I used the return to stock method posted in the forums to return my device completely to stock. After doing so everything was also fine. I received an update to LL4 and that went OK straight from Verizon but last night when the VRAMC3 update was pushed to my phone it soft bricked it. It ultimately was stock on the splash screen stating Samsung Note 2. After trying to ODIN back to stock with multiple FAILS I was able to get it back to the Root66 MR Robinson by using the pit file but every time I try to update and or root/unlock bootloader it soft bricks again. I am assuming that the update that was pushed updated my bootloader and as of now I am stuck till there is a new bootloader Jailbreak. If not I would love some instruction on how to get my phone rooted with an unlocked bootloader or a flashable ODIN file that will at least get me to the latest VRAMC3 fully stock ROM. Thank you for the HELP.
Next time read the stickies...when they say NOT to accept OTA updates, usually there is some meaning behind it.
Shawnkanan said:
OK so here is the story and I was debating if this is the right place to post but I do feel it is more on the developing side. I originally rooted and unlocked my bootloader following Casuals method and everything was just fine. I had an option to sell the phone in preparation for buying the GS4 so I used the return to stock method posted in the forums to return my device completely to stock. After doing so everything was also fine. I received an update to LL4 and that went OK straight from Verizon but last night when the VRAMC3 update was pushed to my phone it soft bricked it. It ultimately was stock on the splash screen stating Samsung Note 2. After trying to ODIN back to stock with multiple FAILS I was able to get it back to the Root66 MR Robinson by using the pit file but every time I try to update and or root/unlock bootloader it soft bricks again. I am assuming that the update that was pushed updated my bootloader and as of now I am stuck till there is a new bootloader Jailbreak. If not I would love some instruction on how to get my phone rooted with an unlocked bootloader or a flashable ODIN file that will at least get me to the latest VRAMC3 fully stock ROM. Thank you for the HELP.
Click to expand...
Click to collapse
I had the same problem. Flash the pit file with odin and wait for the phone to turn on. the problem is fixed to get the phone working. Then you can flash other stuff.
Thank you for the replies even though one was not helpful at all. I have flashed the root66 file with the pit and it does work but if I try to run the casual jailbreak or flash any other odin files it fails. My assumption is my bootloader got updated and has locked me out and I will just have to wait for a new boot loader exploit. Thanks
Sent from my SCH-I605 using xda premium
droidstyle said:
Next time read the stickies...when they say NOT to accept OTA updates, usually there is some meaning behind it.
Click to expand...
Click to collapse
Is best advice u can get to avoid unwanted situations
XT912 CDMA
1droidmod said:
Is best advice u can get to avoid unwanted situations
XT912 CDMA
Click to expand...
Click to collapse
No I can give more, but I get tired of repeating myself all the time...especially when its posted in every section of this sub forum.
Read Read, Search Search... U will figure it out..
XT912 CDMA Pac Man 4.2.2
1droidmod said:
Read Read, Search Search... U will figure it out..
XT912 CDMA Pac Man 4.2.2
Click to expand...
Click to collapse
Is there a sticky or something definitive on the subject of rooted (via Casual) Verizon Note 2 users getting the OTA update and retaining root? I'm currently VRALL4, rooted via Casual, with SDM frozen to avoid the OTA update. But I'd rather not stay in this state indefinitely.
madtowner11 said:
Is there a sticky or something definitive on the subject of rooted (via Casual) Verizon Note 2 users getting the OTA update and retaining root? I'm currently VRALL4, rooted via Casual, with SDM frozen to avoid the OTA update. But I'd rather not stay in this state indefinitely.
Click to expand...
Click to collapse
Once you are rooted via Casual there is no such thing as accepting Verizon's OTA if you want your phone to keep working. (This info can be found in 1 or 2 basic searches, which everyone should do first.)
If you want to get the 4.1.2 features there are 3 options that I know of: 1) flash a zip of the 4.1.2 update, 2) flash a full 4.1.2 stock rom, or 3) flash a custom rom that has 4.1.2 features in it. You can find all 3 options in the Original Development section of xda. Imnuts has implemented #1 but read the forum on the ins and outs. Beanstown106 has created #2. And Beanstown106's latest Jellybeans 16 is a custom rom that incorporates 4.1.2.
Hey, I'm rooted and s-off, running (firmware, I think) 2.06.605.1 710RD. I've been ignoring the software update Verizon sent out a while ago by pressing the home button on my phone whenever the update popup appears, but I'd like to make it go away for good, and the best way to do that is to update.
The thing is, I'd like to do it without the hassle of unrooting and going back to s-on (if I even need to do that) to update, then getting s-off and root again. I heard it's possible if you flash a pre-rooted ROM of the update through a custom recovery, and I found a pre-rooted, updated rom a while ago on the forum, but now I can't find it. The update is called HTC6435LVW_2.07.605.1-2.06.605.1.
First of all, will this work?
Secondly, I'm going to keep searching for the 2.07 rom, but can anyone let me know if they have a link to the thread?
Thanks for your help.
Edit 2: To all who saw my first edit, I have confirmed that this is the TTY update, not the 4.2.2 update. However, I think the 4.2.2 update will be available after I flash the 2.07 update, so please let me know if flashing a pre-rooted rom still works for entire OS updates (and if there even is a pre-rooted rom for 4.2.2 yet).
Edit 3: Wow, I should have finished reading xda's article on the subject before I edited last time. Apparently there's already a pre-rooted rom for the 4.2.2 update, so that won't be a problem. Ok, that should be all.
Now Available!! 5.0.1!!!
Go get your lollipop ON!!!
Hopefully this will result in some bugs squashed with CM12. I am hoping for a better modem and better Bluetooth.
Queuing up downloads now, I have two of them pending for my device
are you able to capture the updates
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
dgutierrez04 said:
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
Click to expand...
Click to collapse
you could try taking it, then flashing the nc5 kernel through odin, and then (if someone's able to do this) get the kernel from nk4 and flash that
dgutierrez04 said:
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
Click to expand...
Click to collapse
How many updates are there? What does it mean 1st update? are there more updates?
meazz1 said:
How many updates are there? What does it mean 1st update? are there more updates?
Click to expand...
Click to collapse
apparently this is a 2-part update
part 1 is a build where the last three characters are NK4. this is a kitkat ROM that was likely used to prepare for lollipop
part 2 is the actual lollipop build, OC1. i think it's 5.0.1 but i'm seeing conflicting things from the internet
for some reason verizon likes doing major updates this way (i dont think they did it for jelly bean to kitkat though). but i've had a few of their phones, they've been doing two-part updates since the original galaxy s in 2010 lol
Hey everyone! Has anyone solved the mystery of the lollipop update fail? Seems alot of us are getting the first update without any issues, but the lollipop update is failing. It gives error 402, which one person at Vz told me was an error thrown due to having root. ( I don't have root ) Any suggestions appreciated!
gsmitchell said:
Hey everyone! Has anyone solved the mystery of the lollipop update fail? Seems alot of us are getting the first update without any issues, but the lollipop update is failing. It gives error 402, which one person at Vz told me was an error thrown due to having root. ( I don't have root ) Any suggestions appreciated!
Click to expand...
Click to collapse
My update is failing as well.
I've wiped cache in recovery, wiped data and cache in download manager...
Still fails.
I was rooted at one time - not rooted anymore.
I do still get the "custom" boot screen with the padlock though...
Can someone that has taken the OC1 ota update test to see if the 4.4.2 kernel has been blacklisted by:
1. Flash the I545_NK4_Stock_Kernel.tar.md5 using Odin. The device will not boot after flashing but we are just interested to see if the kernel will successfully flash.
2. To go back to normal flash the I545_OC1_Stock_Kernel.tar.md5 also in Odin.
This is the first test to determine if a downgrade workaround will be available for those that took the OC1 ota update.
muniz_ri said:
Can someone that has taken the OC1 ota update test to see if the 4.4.2 kernel has been blacklisted by:
1. Flash the I545_NK4_Stock_Kernel.tar.md5 using Odin. The device will not boot after flashing but we are just interested to see if the kernel will successfully flash.
2. To go back to normal flash the I545_OC1_Stock_Kernel.tar.md5 also in Odin.
This is the first test to determine if a downgrade workaround will be available for those that took the OC1 ota update.
Click to expand...
Click to collapse
Nope, it fails to flash
Here is the short log from the screen:
Code:
START [224, 1440]
SYS REV CHECK FAIL[K] : Refer 1 > Binary 0
SECURE MAGICCODE CHECK FAIL : boot
Is there a stock Odin TAR for this yet?
xdabens said:
Nope, it fails to flash
Here is the short log from the screen:
Code:
START [224, 1440]
SYS REV CHECK FAIL[K] : Refer 1 > Binary 0
SECURE MAGICCODE CHECK FAIL : boot
Click to expand...
Click to collapse
Not good. The 4.4.2 kernel has been blacklisted. Thx for testing.
Successful update (in two part harmony) yesterday. Stock system. Fox-Fi still works over Wi-Fi so I'm happy. No issues except 2nd update took a loooonngg time on the red Verizon screen. Make sure your battery is full or you are plugged in. No comments on battery life as I've been able to stay charged today. Getting used to it.
Hey everyone! If you getting the 402 Error, there is a thread that might have the fix. Go to the Error 402 when updating to Lolipop? thread. I am going to try it when I get home tonight.
dgutierrez04 said:
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
Click to expand...
Click to collapse
Thanks! Muniz_ri mentioned that you also captured the OC1 OTA package. I searched a lot but did not find it. Could you provide the link? Thanks again!
danielzink said:
My update is failing as well.
I've wiped cache in recovery, wiped data and cache in download manager...
Still fails.
I was rooted at one time - not rooted anymore.
I do still get the "custom" boot screen with the padlock though...
Click to expand...
Click to collapse
I had the same custom boot screen--even after unrooting. Tried using Triangle Away to reset the binary count, but the count was already at 0. So ultimately I had to re-flash the NC5 kernel via Odin to get things truly back to being recognized as stock.
Then updates started rolling in for NG6, then NK1. Finally the two-part update for Lollipop.
Sent from my SCH-I545 using XDA Free mobile app
People getting tthe 40 error did you at one time have safestrap installed? ??
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
I've always found taking out sd card then a fresh Odin back to stock then doing my updates lead me to a flawless update process every time
Guys I'm on NC5 only rooted by towelroot what do I do please?!