I've restored successfully using RRU a couple of times using UK TMO images but I'm no longer able to.
What I did was RRU an image and then OTA update to a version which is unavailable as a RRU. It's currently bricked I just see the pink circle although I can get to the bootloader via power-back (although not via power-vol down oddly).
I think the RRU isn't allowing downgrade now. Is there anyway of either forcing the Windows RRU updater to ignore version or flash more directly?
Enter recovery and flash a stock rooted Rom then ruu it
Or enter fastboot plug phone in then run ruu as administrator
Sent from my HTC Desire using XDA Premium App
I lost recovery it just goes to the pink circle. I only have bootloader.
And I can't run RUU on any of the available UK T-Mobile images without error.
gruntling said:
I lost recovery it just goes to the pink circle. I only have bootloader.
And I can't run RUU on any of the available UK T-Mobile images without error.
Click to expand...
Click to collapse
Hmm. If you have s-off, can you try to flash recovery via fastboot, then wipe everything and flash rom of choice? Never done that but I think my logic is good?
What is long hex code for goldcard?
I think the issue with my failing RUU update is that I have 2.12.110.4 and there isn't a RUU for T-Mobile for that version -- the last is 1.12.110.4 and RUU gives error "error 140 bootloader version error".
I've tried the OTA update as a PB99IMG.ZIP via fastboot but that doesn't work. I assume the ZIPs are signed and I can't mix the RUU extracted rom and OTA.
I think my best option is a goldcard but I don't have access to read the long hex CID from the phone.
I can see cid::T-MOB005 from fastboot.exe oem boot. Is there any way of translating that to the long hex code?
gruntling said:
I think the issue with my failing RUU update is that I have 2.12.110.4 and there isn't a RUU for T-Mobile for that version -- the last is 1.12.110.4 and RUU gives error "error 140 bootloader version error".
I've tried the OTA update as a PB99IMG.ZIP via fastboot but that doesn't work. I assume the ZIPs are signed and I can't mix the RUU extracted rom and OTA.
I think my best option is a goldcard but I don't have access to read the long hex CID from the phone.
I can see cid::T-MOB005 from fastboot.exe oem boot. Is there any way of translating that to the long hex code?
Click to expand...
Click to collapse
This may help I think:
http://forum.xda-developers.com/archive/index.php/t-921398.html
Related
So i somehow went hiroshima on my one x. I'll keep it short and simple. Had my BL unlocked but was running CWM recovery and the stock rom. Tried installing the cyanogenmod 9 and things went to hell after i flashed the boot.img. Now I am stuck at the white HTC screen. I read the disaster recovery but I am still having no luck. I relocked the bootloader and reflashed stock recovery then i tried using the ruu utility but it said that it didnt match and then rebooted with some developer text on the boot screen. I used the getvar command and it says:
version-main: 1.28.720.10
Before the blowup I had ran the OTA.I was on 1.26.720.10. This is the ruu i tried to reflash. I cant seem to find the 1.28.720.10. I also tried pulling the sys and boot img files from the temp directory and manually flashing, it gave an error.
as of right now i have the bootloader unlocked again and CWM recovery reinstalled so i can charge.
please help! $20 reward via paypal to the person that helps me get back to complete stock!
The worst part is i dont even want this damn phone...lol
Try this mate. If you can still get to bootloader and recovery it recoverable. I'd go back to stock so its as if you bought the phone, just to be safe. So...
Open cmd and CD to your fastboot file location. Plug phone in and...
First flash a stock boot.img from your stock.zip
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
Then relock your bootloader.
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
Then run the RUU.
But make sure you have the correct one. So that includes region. If you started on 1.26 and you haven't done any OTA updates then you need 1.26 but with your region code.
Good luck!
Sent from my HTC One X using xda premium
i did do the ota to 1.28 before i blew it up. also, how do i find the right region code? WHen i searched google for the results of my getvar version-main i found a bunch of threads referring to that being the ota for india, so thats the ruu i downloaded from the fileshare. i was working off a hunch though.
Will I be able to use a 1.26 RUU if I updated to 1.28, seeeing as how my getvar says 1.28?
applejoos said:
i did do the ota to 1.28 before i blew it up. also, how do i find the right region code? WHen i searched google for the results of my getvar version-main i found a bunch of threads referring to that being the ota for india, so thats the ruu i downloaded from the fileshare. i was working off a hunch though.
Will I be able to use a 1.26 RUU if I updated to 1.28, seeeing as how my getvar says 1.28?
Click to expand...
Click to collapse
Yeah if you did the OTA you need to use the 1.28 RUU as your hboot will have updated along with either things so 1.26 won't work.
Sent from my HTC One X using xda premium
benjamin.j.goodwin said:
Yeah if you did the OTA you need to use the 1.28 RUU as your hboot will have updated along with either things so 1.26 won't work.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
So since there is no RUU matching my version number I am screwed now right?
Use the 1.29 ruu?
backfromthestorm said:
Use the 1.29 ruu?
Click to expand...
Click to collapse
there is no 1.29 for my region code.
applejoos said:
So since there is no RUU matching my version number I am screwed now right?
Click to expand...
Click to collapse
Do you know how to push a ROM.zip on to your SD card via command prompt?
Try downloading a custom ROM and flash the boot.img then, clear cache, then boot to recovery and flash the ROM. Then reboot. Should work.
Sent from my HTC One X using xda premium
RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe
http://www.filefactory.com/file/7c4y4xrx25w3
MD5: 02f5c589d6d2bb0cc8678c7b76f2951b
Source: http://forum.xda-developers.com/showthread.php?t=1335368 (Football)
....and just after I finally managed to get the ota installed
Hi,
i have S-ON, bootloader unlocked, root, 2.13.401.3
after this update 2.26.401.3 stay still bootloader unlocked?
EDIT: maybe i need S-OFF, not possibly update my mobile...
you need to relock the bl in order to install any ruu.
i had a hard time updating my phone to 2.26
if you take a look at the first thread for this update, the ota update, there are details for how to update to this version and still keep bl-nlocked and easily root
RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe
Can anyone send me this file not via filefactory? There are no free slots in there at all
I relock bl and try new RUU 2.26, but problem with flashing. Can you pls describe steps by steps how can is possibly update from 2.13 to 2.26 ? I'm S-ON
I have Rom with 2.26 but I want update radio too....
Sent from my HTC Wildfire S A510e using xda premium
http://forum.xda-developers.com/showthread.php?t=1679010
try the process in this thread, if you can't get it to work straight away, try using the method i used (thanks to rezo).
1 - install the ruu for 2.14.401.1
(http://www.mediafire.com/download.php?o6ox43q3taa33iu)
1.5 - if you can't do this because you already have the rom from 2.26 (but old radio etc), follow this tutorial so that you can go back to ruu 2.14.401.1
http://forum.xda-developers.com/showthread.php?t=1540952&highlight=downgrade
2 - use htcdev process (without ruu step) to unlock bootloader
3 - install cwm recovery by flashing this file (http://www.mediafire.com/download.php?1rdxmtpx26201or) via "fastboot flash recovery recovery(custom).img"
4 - put update.zip (http://www.mediafire.com/download.php?vycb7415nn9boct) on the root of your sd card and install from cwm recovery.
4.5 - if the update doesn't work (i.e. if you still get "triangle !" logo flash this file (http://www.mediafire.com/download.php?bqni648c46r5e44) via cwm and choose the option "supervision", then try the update again.
5 - after installation and first boot (take a while) boot back to cwm and flash this root.zip (http://www.mediafire.com/download.php?dumbffr3n8igau4)
you should now have the latest stock rom, latest hboot, latest radio, and be root.
What's different in this new update 2.26. ?
Hi guys
I'm trying to download this new ruu for 2 days now from "filefactory" an still: "no free slots"! Ca anyone help me to download this new ruu from other sites?
Thank's in advance!
my current software version is 2.14.401.2, what is the difference if i update to 2.26.401.3? Does it gives any improvement on the performance or battery life?
Thx...
Gloris said:
http://forum.xda-developers.com/showthread.php?t=1679010
try the process in this thread, if you can't get it to work straight away, try using the method i used (thanks to rezo).
1 - install the ruu for 2.14.401.1
(http://www.mediafire.com/download.php?o6ox43q3taa33iu)
1.5 - if you can't do this because you already have the rom from 2.26 (but old radio etc), follow this tutorial so that you can go back to ruu 2.14.401.1
http://forum.xda-developers.com/showthread.php?t=1540952&highlight=downgrade
2 - use htcdev process (without ruu step) to unlock bootloader
3 - install cwm recovery by flashing this file (http://www.mediafire.com/download.php?1rdxmtpx26201or) via "fastboot flash recovery recovery(custom).img"
4 - put update.zip (http://www.mediafire.com/download.php?vycb7415nn9boct) on the root of your sd card and install from cwm recovery.
4.5 - if the update doesn't work (i.e. if you still get "triangle !" logo flash this file (http://www.mediafire.com/download.php?bqni648c46r5e44) via cwm and choose the option "supervision", then try the update again.
5 - after installation and first boot (take a while) boot back to cwm and flash this root.zip (http://www.mediafire.com/download.php?dumbffr3n8igau4)
you should now have the latest stock rom, latest hboot, latest radio, and be root.
Click to expand...
Click to collapse
I have problem with install RUU, why?
Zlobizlob said:
I have problem with install RUU, why?
Click to expand...
Click to collapse
what is the error code?
things to remember when you flash an ruu :-
you should not have modified system files (except for root)
you should have stock recovery to start with
you may need to create gold card
you should be relocked bootoader
if you are already on a software number which is higher than the ruu you are trying to install, you may need to downgrade first, using the guide posted above.
Is there anyway without S-OFF to update the radio? I would rather not loose any data too. I've manage to update everything but the radio.
Stevk said:
Is there anyway without S-OFF to update the radio? I would rather not loose any data too. I've manage to update everything but the radio.
Click to expand...
Click to collapse
if you're s-off already, can't you just flash the radio.img?
don't quote me on that, i'm not s-off myself, so i'm not reallu 'up' on all the thigns you can do and how you do them. but i was under the impression that with s-off you can flash it same as you flash recovery.img or system.img?
Do I need to flash radio? Because my girlfriends WFS has been t-mobile branded so I think I'm not able to flash RUU without gold crad?
Is it possible to flash system.img and boot.img only? Or will there be conflicts with radio/ramdisk etc...
BL is unlocked and device is rooted atm!
I installed this RUU to my Wildfire S by this tutorial
Code:
http://forum.xda-developers.com/showthread.php?t=1540952
My phone had unlocked bootloader (via htcdev.com), Root, S-On and my Hboot version was 1.09.0099. When I was trying to install RUU I got ERROR 140(bad hboot version). So I used mentioned tutorial to downgrade hboot and then I install new RUU.
I downloaded RUU 2.26.401.3 from this site because on Football's FileFactory link are allways full slots.
Code:
http://narod.ru/disk/51502291001.c558c29e878e383684edd1a956d417fd/RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe.html
And there is a ZIP version if someone want
Code:
http://narod.ru/disk/51500892001.cf33d25826e44363856289cb11302527/PG76IMG%20-%20Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M.zip.html
Sorry for poor english.
Can anyone please upload the RUU to another server?
FileFactory is always overloaded. And the russian site is too slow to download from America. 3kbps gg.
Any issues unlocking BL and rooting this update? Any compelling reason to stay with 2.13.401.2/3?
Heritz said:
Can anyone please upload the RUU to another server?
FileFactory is always overloaded. And the russian site is too slow to download from America. 3kbps gg.
Click to expand...
Click to collapse
I can upload RUU from russian site. Choose on which file hosting server. I dont know which is good.
EDIT - I solved it.
I have installed CyanogenMod10 and want to return to the the original factory image. All my attempts have failed.
I receive the mesage "Hboot Version is older!" then " Update Fail!"
I have extracted the RUU ROM.zip file and tried to upload manually but all my attempts fails.
Any help how to proceed will be appreciated
Moved to Q&A. Please ask all questions there.
romah1 said:
I have installed CyanogenMod10 and want to return to the the original factory image. All my attempts have failed.
I receive the mesage "Hboot Version is older!" then " Update Fail!"
I have extracted the RUU ROM.zip file and tried to upload manually but all my attempts fails.
Any help how to proceed will be appreciated
Click to expand...
Click to collapse
That is possile if the RUU is older than the one currently on your phone. If this is not the case, try to flash the RUU via the program and from hboot.
Ken-Shi_Kun said:
That is possile if the RUU is older than the one currently on your phone. If this is not the case, try to flash the RUU via the program and from hboot.
Click to expand...
Click to collapse
Obviously , since I have Cyanogenmod 10 installed the RUU version is older. CM10 is somehow preventing the RUU to execute correctly,
I have tried to run the RUU with Hboot but it didn't recognized the phone.
your backup is older than the bootloader version now you have .
Sent from my HTC T320e using xda premium
romah1 said:
Obviously , since I have Cyanogenmod 10 installed the RUU version is older. CM10 is somehow preventing the RUU to execute correctly,
I have tried to run the RUU with Hboot but it didn't recognized the phone.
Click to expand...
Click to collapse
Sorry I will be clearer. The ruu has two thing before start. It evaluates your cid and hboot version. If you had (my example here) a 2.22 stock and you want to flash the ruu of the 2.02 version it will not work because the hboot in your phone is newer. This is a security measurement for you not to be able to downgrade your os.
Even more, ruu needs stock recovery, stock kernel, and the phone to be either "locked" or "relocked". And more, if you has custom is on the phone that time, the ruu will only work from fastboot usb mode.
It is a joke tough that in these phones unlock and custom os is easily achivable, while going back to stock is like a pain in the ass.
Sent from my CM10 One V
Hello,
so I got the HTC 10 from my brother but I can not get the latest updates via OTA. Reason: Bootload unlocked und TWRP Recovery.
Now I wanna relock the bootloader and back to the Stock Recovery in order to get the OTA upates. I found files in the thread but I do not really know how to proceed at all
Is there any step by step guide for this situation which a newbie would understand?
Some Info's to the phone itself:
Recovery: TWRP 3.03-10_Unofficial
S-On
Unlocked Bootloader
CID: HTC_034
Android 7.0, January Security update
Software: 2.41.401.4
Kernel: 3.18.31-perf-g9ec8cbc and @aabm#1 SMP PREEMPT
Baseband: [email protected]_79.07_F
Is there any way to simply flash the stock recovery again put the bootloader to locked and then get the OTA?
Any help is appreciated
(And no can not ask my brother as he is for several months abroad)
pyo[st said:
;73891974]Hello,
so I got the HTC 10 from my brother but I can not get the latest updates via OTA. Reason: Bootload unlocked und TWRP Recovery.
Now I wanna relock the bootloader and back to the Stock Recovery in order to get the OTA upates. I found files in the thread but I do not really know how to proceed at all
Is there any step by step guide for this situation which a newbie would understand?
Some Info's to the phone itself:
Recovery: TWRP 3.03-10_Unofficial
S-On
Unlocked Bootloader
CID: HTC_034
Android 7.0, January Security update
Software: 2.41.401.4
Kernel: 3.18.31-perf-g9ec8cbc and @aabm#1 SMP PREEMPT
Baseband: [email protected]_79.07_F
Is there any way to simply flash the stock recovery again put the bootloader to locked and then get the OTA?
Any help is appreciated
(And no can not ask my brother as he is for several months abroad)
Click to expand...
Click to collapse
Bootloader status does not affect ability to take OTAs.
You need two things mainly to take the OTA:
1. Stock recovery matching your current software
2. An untouched backup image of the system partition matching your current software. This is needed if you're currently rooted.
Both can probably be found in the thread you linked. The backup image is flashed from twrp. The stock recovery is then flashed from download mode using this command:
Fastboot flash recovery yourrecoveryfile.img
But even after doing that, you might still get an error when trying to take the OTA. Easiest way to take it is to start from scratch, backup your phone's contents to your pc or sd card, and then run the latest ruu for your phone. This will bring you up to date, and will also allow you to make a backup system image from twrp before rooting so that you can easily take future OTAs. The ruu will also completely wipe your phone's contents.
So you can try the first method I mentioned, and if it doesn't work go with the ruu.
As your brother may root it before so the system may got modify, in this case the best and easiest way is flash a RUU.
Try this RUU, http://dl3.htc.com/application/[email protected]_79.07_F_release_495903_signed_2.exe
A RUU will restore your HTC 10 back to stock and wipe out everything. It require a match CID or super CID, if not it will not flash.
I tried to flash RUU via sd card method as well as fastboot method. Both got failed
sd card: Header Error
fastboot: load_file: could not allocate 1950335038 bytes
error: cannot load '2PS6IMG.zip'
Im running on venom rom , S ON with oem unlocked. How can i go back to stock rom??
Mine is 2.41.401.41
DummyPLUG said:
As your brother may root it before so the system may got modify, in this case the best and easiest way is flash a RUU.
Try this RUU, LINK
A RUU will restore your HTC 10 back to stock and wipe out everything. It require a match CID or super CID, if not it will not flash.
Click to expand...
Click to collapse
This RUU worked perfectly. And no the phone was not rooted, just unlocked Bootloader and TWRP as Recovery.
After flashing the RUU I got the July Security Patch and that is what I wanted.
Thank you very much, Problem solved
$tark3 said:
I tried to flash RUU via sd card method as well as fastboot method. Both got failed
sd card: Header Error
fastboot: load_file: could not allocate 1950335038 bytes
error: cannot load '2PS6IMG.zip'
Im running on venom rom , S ON with oem unlocked. How can i go back to stock rom??
Mine is 2.41.401.41
Click to expand...
Click to collapse
It is a EXE, you should run on windows instead of using the sdcard method, as for the not enough space I am not sure about
DummyPLUG said:
It is a EXE, you should run on windows instead of using the sdcard method, as for the not enough space I am not sure about
Click to expand...
Click to collapse
Nah, i downloaded the exe and the zip file also.
Anyway fixed it. Just restored from a nandroid backup. Now back in stock
PS:In btw, anyone facing any battery drop issue??
So I run in another Problem. I got the latest OTA for Europe (July Security Patch) but now my Phone gets shown as uncertified in the google play app which means I can not download certain apps like Netflix via Appstore.
Now I already figured out why I get shown uncertified: the Bootload is still unlocked. I thought the RUU would fix this as well. And if I wanna go in to the recovery (there was an TWRP Recovery on it before) I just get a red triangle with an "!" in it. It wont boot into recovery. Had to hard reset the phone to be able to boot normally to android then.
Now I wanna flash the stock recovery and lock the Bootload again to get again the certified status from google again.
Now here I need help.
1. Can't find the matching recovery version (EU unlocked, July Securtiy Patch, 2.41.401.41). Can anyone help me find the recovery image I need?
2. How do I get the bootload locked again? My Brother unlocked it via HTCdev.com back then, that I know already. But the command fastboot oem lock does not work at all. It just does nothing.
So how can I lock the bootloader?
Thanks for the help.
If you ran the RUU you already have stock recovery...red triangle with an "!" in it.
Are you running the fastboot oem lock from bootloader or download mode?
Sloth said:
If you ran the RUU you already have stock recovery...red triangle with an "!" in it.
Are you running the fastboot oem lock from bootloader or download mode?
Click to expand...
Click to collapse
Haha well then everything is ok with the recovery ^^
I tried both (download and bootloader mode), both times nothing happens. In download mode my PC does not even recognize the phone as the command "adb devices" does not list my phone and the command "fastboot oem lock" does nothing. HTCsnyc installed and ofc adb shell, worked even as when I normally checked with adb devices when my phone was on it was recognized.
pyo[st] said:
Haha well then everything is ok with the recovery ^^
I tried both (download and bootloader mode), both times nothing happens. In download mode my PC does not even recognize the phone as the command "adb devices" does not list my phone and the command "fastboot oem lock" does nothing. HTCsnyc installed and ofc adb shell, worked even as when I normally checked with adb devices when my phone was on it was recognized.
Click to expand...
Click to collapse
Try fastboot devices
Sent from a Glade Plugin.
Sloth said:
If you ran the RUU you already have stock recovery...red triangle with an "!" in it.
Are you running the fastboot oem lock from bootloader or download mode?
Click to expand...
Click to collapse
Sloth said:
Try fastboot devices
Sent from a Glade Plugin.
Click to expand...
Click to collapse
Alright this command works and shows my device.
Now I am in bootloader (Shows Software Status: Modified; Unlocked, S-ON). Then I type in "fastboot oem lock" and I get:
FAILED (remote: unknown command)
finished. total time: 0.014s
Well at least now I get something, before just nothing happened. Any clue what I might do wrong here?
*edit*
So I am a big noob
Phone has to be in download mode then the command works and my phone shows me a message if I want to lock again. Unfortunately it will factory reset my phone as well (at least it says that) so I have to backup my data (again) first.
But thank you for your help, appreciate it.
Cheers!
So I did lock the phone again and flashed again the RUU.exe BUT again my Phone shows in Bootloader Software Status as Modified...and it shows as Relocked.
So how do I get it to official status again?
pyo[st said:
;74318325]So I did lock the phone again and flashed again the RUU.exe BUT again my Phone shows in Bootloader Software Status as Modified...and it shows as Relocked.
So how do I get it to official status again?
Click to expand...
Click to collapse
By buying sunshine S-OFF. Only way to see the bootloader back to "locked" instead of "relocked"
Mr Hofs said:
By buying sunshine S-OFF. Only way to see the bootloader back to "locked" instead of "relocked"
Click to expand...
Click to collapse
Ye found a thread to it. But seems I dont need it. My Phone gets shown as certified again at google play store so I assume just "relocking" the bootloader seems to be enough.
.....
ATT One M9. Currently on Version 3.38.502.31, S-ON, Rooted, TWRP. I'm trying to get it back to stock so it can accept the Nougat OTA. I read that I could just run the RRU from HTC to restore it. Finally had the time today to do it however I get a 132 signature error. I relocked the bootloader but still got the error. As I read up on it it turns out for some reason the encryption was changed between the 3.xx and 4.xx versions so the update won't work. I don't want to pay to get S-OFF so the only other option I can find is to get an older RRU for either my current version or the one after it (3.38.502.31 or 3.38.502.41) and then allow the phone to OTA. I can't find one. I can find the 3.38.502.41 .ZIP but from what I understand i NEED the .EXE version. Does anyone have one of these older .EXE RRU files or another method to get my phone to accept the Nougat OTA?
There is no difference between the *.zip and the *.exe. (Well, aside from the fancy installer that gets used by the *.exe. It's not needed, though.) Besides, re-locking isn't just unnecessary it's actually highly not recommended unless you have a working RUU at hand due to the FRP that Google introduced with android 5.1.
Where did you read that you need an *.exe and/or that you need to re-lock your phone?
Sent from my HTC One M9 using XDA Labs
I figured that I needed the .exe because if you try to flash an official update .zip but the phone system is modded it will fail. So you are telling me that I can flash the RRU .zip with TWRP and it will work?
Please take the time to carefully read the ReadMe thread. You're mixing up a lot of things.
OTAs fail if your phone is modified. RUUs don't check whether you tinkered with your phone. They simply overwrite everything. As said before, there's no real difference between a RUU.zip and a RUU.exe for the same firmware version. If one can be flashed then so can be the other.
And no, you can't flash a RUU.zip via TWRP. RUUs get made by HTC and TWRP is a custom made recovery. They're not compatible with each other. (In other words, you can't flash RUUs via TWRP.)
Sent from my HTC One M9 using XDA Labs
I recommend that you unlock your bootloader as there is no reason for it to be relocked. Especially if you plan on rooting it again.
For the zip method:
Find the FIRMWARE zip that matches your current version on the phone. x.xx.xxx.yy where yy can be any number, xx MUST MATCH.
Check the md5 matches before you mess with the firmware file.
Rename the firmware zip file to 0PJAIMG.ZIP and copy it to the external sd card.
Reboot phone to download mode and in yellow writing at the bottom of the screen it should say to press vol up to flash. Make sure the phone is plugged into a charger and press vol up.
That flashes it back to stock stock and wipes root priveliges, flashes a stock recovery, flashes a stock system.
Once back to stock you can accept the ota updates. Bootloader and s-on/s-off have no influence at all. As flippy states, if you leave it as relocked you may encounter issues with google's frp (factory reset protection).
shivadow said:
I recommend that you unlock your bootloader as there is no reason for it to be relocked. Especially if you plan on rooting it again.
For the zip method:
Find the FIRMWARE zip that matches your current version on the phone. x.xx.xxx.yy where yy can be any number, xx MUST MATCH.
Check the md5 matches before you mess with the firmware file.
Rename the firmware zip file to 0PJAIMG.ZIP and copy it to the external sd card.
Reboot phone to download mode and in yellow writing at the bottom of the screen it should say to press vol up to flash. Make sure the phone is plugged into a charger and press vol up.
That flashes it back to stock stock and wipes root priveliges, flashes a stock recovery, flashes a stock system.
Once back to stock you can accept the ota updates. Bootloader and s-on/s-off have no influence at all. As flippy states, if you leave it as relocked you may encounter issues with google's frp (factory reset protection).
Click to expand...
Click to collapse
A little late but I wanted to thank you for your advice, I tried it today and it worked perfectly.