Unrooted issue with OTA update

Splitshot

Senior Member
Jun 7, 2013
52
6
0
Winnipeg
Hi there,

I had a quick question on my issue.
I found my appropriate file to flash and loaded it in the twrp-backup folder and flashed. Then used the hassoon2000 program to close the bootloader. I was already S-on. Used the program to close the bootloader. Now the bootloader says relocked in red. Rebooted and started up. Everything works great. I'm with Rogers and emmidiately it says an update is available. After I download it asks if I want to flash. It unzips and reboots to the bootloader. What is the next step? I'm also wondering why I'm in the bootloader. Shouldn't it just reboot and finish the upgrade?
I'm convinced there's an issue.
Is there something I should change.
I'm lost. Any help would be appreciated.
 
Last edited:

ckpv5

Recognized Contributor
Feb 11, 2008
14,359
18,290
0
Kuala Lumpur
Being a tester for Viper as stated in your signature, you shouldn't make this silly mistake.
Don't relock bootloader .. not needed at all and a hassle for you to fix problems.

You need non-rooted backup & stock recovery to update.

Read how-to and files needed in my thread linked in my signature.

You need to unlock bootloader again to fix it.
 
  • Like
Reactions: Splitshot

Splitshot

Senior Member
Jun 7, 2013
52
6
0
Winnipeg
Its been a year and a half since I tweaked anything on my phone. Viper has been solid but wanted to upgrade to marshmellow then install newer vipper. Anyways, thats just the back ground reasons.
If I open the bootloader ( I'll have to search for this step as I'm sure using the "open bootloader" option in Hassoon's program would require many more steps) the update would take me to recovery. I spent hours searching through folders trying to find the OTA to install with no luck.
 

ckpv5

Recognized Contributor
Feb 11, 2008
14,359
18,290
0
Kuala Lumpur
Don't use tools...

1. Unlock bootloader with unlock_code bin that you should already have. If no, request again from htcdev

2. Install TWRP

3. Restore non-rooted nandroid backup for your current firmware.
What's your current firmware ?

4. Install current firmware stock recovery

5. Do OTA checking, download & install

You won't find the OTA file after you already tried to install it .. it will be removed by the system after you tried to update (and failed)
 
  • Like
Reactions: Splitshot

Splitshot

Senior Member
Jun 7, 2013
52
6
0
Winnipeg
Don't use tools...

1. Unlock bootloader with unlock_code bin that you should already have. If no, request again from htcdev

2. Install TWRP

3. Restore non-rooted nandroid backup for your current firmware.
What's your current firmware ?

4. Install current firmware stock recovery

5. Do OTA checking, download & install

You won't find the OTA file after you already tried to install it .. it will be removed by the system after you tried to update (and failed)
Again I apprecoate the insight into this. I did some reading and it looks like the tool kit hasn't been updated in a few years. I followed your link/page and went through the unlock with htcdev. It said successful and they were emailing me the code and further instructions. That was originally 12hrs ago. I redid it about 3hrs ago but again still waiting on the email( I did check the spam folder but still nothing.
As for previous firmware, I have:
CID Rogers_001
Version main(OS) 4.20.631.2
HBoot 3.19.0.0000
 

Splitshot

Senior Member
Jun 7, 2013
52
6
0
Winnipeg
I was just thinking, maybe its a different token number each attempt. So again I redid the process. Now I wait. I've also looked at my account in the htcdev and it is correct. This is strange.
 

ckpv5

Recognized Contributor
Feb 11, 2008
14,359
18,290
0
Kuala Lumpur
Sometime it happens the delay.

If I remember correctly, I have RUU for your current version. If there is, while waiting for the unlock_code.bin, you can run RUU for a fresh system and do OTA up to Marshmallow.
Then you can unlock bootloader to install your favorite ROM.

I'm already in bed, I'll check my hdisk tomorrow and upload for you

I assume your device is S-On, if it is S-Off you don't need the unlock code to unlock bootloader.
Am I right about the device is S-On. I hope I am wrong then it's easier to fix it.
 
Last edited:

Splitshot

Senior Member
Jun 7, 2013
52
6
0
Winnipeg
Sometime it happens the delay.

If I remember correctly, I have RUU for your current version. If there is, while waiting for the unlock_code.bin, you can run RUU for a fresh system and do OTA up to Marshmallow.
Then you can unlock bootloader to install your favorite ROM.

I'm already in bed, I'll check my hdisk tomorrow and upload for you

I assume your device is S-On, if it is S-Off you don't need the unlock code to unlock bootloader.
Am I right about the device is S-On. I hope I am wrong then it's easier to fix it.
You are correct as its still S-On. I had to redo my registration as my old account didn't have all the Capitals, hexadecimal stuff the latest user name/passwords require. but after that the email came through and I'm back to being unlocked. If you stumble on the RUU I'd very very thankful for the copy. In the meantime I'll look up the RUU and the install. chances are this is what your thread is all about.
 

ckpv5

Recognized Contributor
Feb 11, 2008
14,359
18,290
0
Kuala Lumpur
I'm back to being unlocked. If you stumble on the RUU I'd very very thankful for the copy. In the meantime I'll look up the RUU and the install. chances are this is what your thread is all about.
No .. my thread is not about RUU but nandroid backup. You don't need the RUU when your target is to have Marshmallow firmware and install custom ROM ..

Now the bootloader is unlocked and you have the unlock_code, the fastest method for you is:

Restore directly Marshmallow nandroid 6.13.631.7 (instead of going for OTA) then relock bootloader and install 6.13.631.7 signed firmware.zip .. reboot.

After all setup done .. you can unlock bootloader, reboot .. after setup is completed, install latest TWRP and install your favorite custom ROM.

The usual method :
Restore 4.20.631.3 backup (yes, not 4.20.631.2 backup), install 4.20.631.3 stock recovery - reboot - setup - check OTA - download and install 6.13.631.7 OTA. Once completed, install latest TWRP and install your favorite custom ROM.

The usual method is better, no hassle of relocking and unlocking bootloader.
 
Last edited:
  • Like
Reactions: Splitshot

Splitshot

Senior Member
Jun 7, 2013
52
6
0
Winnipeg
followed your procedures but after downloading the marshmallow update it unzips and reboots to the install part after about 1 minute it reboots to factory recovery. is there a step here? because I wiped twrp before restoring the 4.20.631.3 file I have no twrp( That's what I'm familiar with not this factory recovery).
 

ckpv5

Recognized Contributor
Feb 11, 2008
14,359
18,290
0
Kuala Lumpur
Make sure you install either 4.20.631.3 or 6.13.631.7 stock recovery.

When it stops in recovery, there's an error log on why it stops.
But it never stops in recovery, if there is error, it will boot to bootloader or reboot back to system without installing update.
 
Last edited:

Splitshot

Senior Member
Jun 7, 2013
52
6
0
Winnipeg
Make sure you install either 4.20.631.3 or 6.13.631.7 stock recovery.

When it stops in recovery, there's an error log on why it stops.
But it never stops in recovery, if there is error, it will boot to bootloader or reboot back to system without installing update.
So if I reDL your 4.20.631.3 and place it back into twrp/backups/phone serial/ and get back into the factory recovery would I be able to restore from here? I don't remember there being a restore option only install.
Or is my only option now to reinstall twrp and go through the paces a 2nd time?
 
Last edited:

ckpv5

Recognized Contributor
Feb 11, 2008
14,359
18,290
0
Kuala Lumpur
I asked you to 4.20.631.3 or 6.13.631.7 stock recovery, what it got to do with redownload 4.20.631.3 (which I believe you refer to nandroid backup)

Nandroid & stock recovery are two different thing.

There is no need to redo the process of restoring 4.20.631.3 nandroid (if it was done correctly) .. just make sure 4.20.631.3 or 6.13.631.7 stock recovery is installed, not any other version.

Reboot, check OTA, download and select install now. The system will boot to RUU mode to install the update .. it won't go to recovery (that's why I don't understand your above post saying it stop in recovery - no manual installation too)

Read the How-To all the 14 steps and tick what you have done so you'll know that you don't skip any step
 

Splitshot

Senior Member
Jun 7, 2013
52
6
0
Winnipeg
I asked you to 4.20.631.3 or 6.13.631.7 stock recovery, what it got to do with redownload 4.20.631.3 (which I believe you refer to nandroid backup)

Nandroid & stock recovery are two different thing.

There is no need to redo the process of restoring 4.20.631.3 nandroid (if it was done correctly) .. just make sure 4.20.631.3 or 6.13.631.7 stock recovery is installed, not any other version.

Reboot, check OTA, download and select install now. The system will boot to RUU mode to install the update .. it won't go to recovery (that's why I don't understand your above post saying it stop in recovery - no manual installation too)

Read the How-To all the 14 steps and tick what you have done so you'll know that you don't skip any step
I apologize as if never seen this screen before. My assumption was it's a stock android recovery. But I must admit I do not know.
Attached is the pic of what I'm talking about.

https://drive.google.com/file/d/0B--VfMbsbBNCMEl6X3UyN3NIdGtXS29kRmE1R0tiaWdjVm9n/view?usp=sharing
 
Last edited:

ckpv5

Recognized Contributor
Feb 11, 2008
14,359
18,290
0
Kuala Lumpur
Yeah ... that's stock recovery with error log ...

It says the system expect stock recovery 4.20.631.3 (463267.3) or 6.13.631.7 (667457.7) is installed for it to proceed the update, but the device has wrong stock recovery image 4.20.631.2 (463267.2) installed so it stops the installation (Status 7)

As I said above, no need to redo the nandroid restore process. Just install recovery image 4.20.631.3 or 6.13.631.7 then redo the OTA checking, download and install.

Note : I believe you followed the instruction written on post #9. There was a typo on recovery version that I edited an hour after posting it yesterday.
That's why you got this error ... sorry for that.
 
Last edited:

Splitshot

Senior Member
Jun 7, 2013
52
6
0
Winnipeg
Yeah ... that's stock recovery with error log ...

It says the system expect stock recovery 4.20.631.3 (463267.3) or 6.13.631.7 (667457.7) is installed for it to proceed the update, but the device has wrong stock recovery image 4.20.631.2 (463267.2) installed so it stops the installation (Status 7)

As I said above, no need to redo the nandroid restore process. Just install recovery image 4.20.631.3 or 6.13.631.7 then redo the OTA checking, download and install.

Note : I believe you followed the instruction written on post #9. There was a typo on recovery version that I edited an hour after posting it yesterday.
That's why you got this error ... sorry for that.
no worries. I have been feeling like a jerk for not following what your saying. I never wanted to frustrate you like this.
Last quick question before I stress over this. My next steps are:
DL your 6.13.631.7
Install in twrp/backups / 6.13.631.7
reboot
DL the OTA
install.
I'm just not sure about where to put the 6.13.631.7 file?
 
Last edited:

ckpv5

Recognized Contributor
Feb 11, 2008
14,359
18,290
0
Kuala Lumpur
I think you still confused with nandroid & stock recovery.
There is no need to download 6.13.631.7 nandroid and no need to put it in twrp/backups

You just need to download the stock recovery image. Let's forget about 6.13.631.7 for now ...

1. download stock recovery image 4.20.631.3 - https://mega.nz/#!TdZg1aID!einylYid2QmN8OoxehNcnTrh6iijFqJ2-klrRsb-5MI

2. Put your device on bootloader/fastboot mode and install stock recovery image 4.20.631.3

fastboot flash recovery 4.20.631.3_recovery.img

3. reboot, check OTA, download OTA, select install now and let the system do it stuff.

4. Once completed, it will reboot and greet you with new Marshmallow 6.13.631.7 ROM.

5. Put your device on bootloader/fastboot mode and install latest TWRP

6. install your custom ROM .... done
 
  • Like
Reactions: Splitshot

Splitshot

Senior Member
Jun 7, 2013
52
6
0
Winnipeg
I think you still confused with nandroid & stock recovery.
There is no need to download 6.13.631.7 nandroid and no need to put it in twrp/backups

You just need to download the stock recovery image. Let's forget about 6.13.631.7 for now ...

1. download stock recovery image 4.20.631.3 - https://mega.nz/#!TdZg1aID!einylYid2QmN8OoxehNcnTrh6iijFqJ2-klrRsb-5MI

2. Put your device on bootloader/fastboot mode and install stock recovery image 4.20.631.3

fastboot flash recovery 4.20.631.3_recovery.img

3. reboot, check OTA, download OTA, select install now and let the system do it stuff.

4. Once completed, it will reboot and greet you with new Marshmallow 6.13.631.7 ROM.

5. Put your device on bootloader/fastboot mode and install latest TWRP

6. install your custom ROM .... done
I really don't know whats happened to all my knowledge and abilities. It's like my frustrations have literally taken over.
I was able to push the recovery image to the phone. rebooted and am now DL'ing the update.
for the last little while I've downloaded twrp but have yet to succeed on pushing it to the phone. I've downloaded the latest file, changed the name to twrp.img and used this while in bootloader/fastboot mode.
fastboot flash recovery twrp.img
error cannot load "twrp.img"
 
Last edited:

Splitshot

Senior Member
Jun 7, 2013
52
6
0
Winnipeg
At the end of the day today I was able to install your nandroid file, upgrade to marshmallow, install the latest TWRP and about to flash a marshmallow ROM. I cannot thank you enough for all your insight, patience and help with this. You truly have an amazing talent. It is amazing the support you find on XDA and your name should be at the top of that list.
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone