is it possible to restore lock bootloader after unlocking it? My phone has been crashing consistently about once every day or every other day since unlocking it.
Well I really doubt unlocking your boot-loader would cause system crashes. The bootloader is a different partition of the phones drive, and its not active while your in system. If you flashed a custom kernel or your on a 8.1 DP build its probably one of those things. I know that a lot of people are having random reboots with 8.1 builds.
Reply back with what kernel and rom build your using; it would help a lot.
As for restoring a locked bootloader; you would need to restore everything to stock by flashing a stock factory image with fastboot drivers. And make sure you restore the original google recovery. I don't know the command on hand, but it is possible. Just many don't do it because it's easy to miss something important and now you can never unlock you bootloader again; its happened!
If I were you, I would just keep my bootloader unlocked and then just wipe and flash a stock factory image.
im_high_tech said:
is it possible to restore lock bootloader after unlocking it? My phone has been crashing consistently about once every day or every other day since unlocking it.
Click to expand...
Click to collapse
What AA said. Unlocking (regular and critical) have nothing to do with your device crashing. I agree you should just leave the bootloader unlocked and clean flash a full image, leaving the -w switch in place. To answer your original question, yes you can definitely relock the bootloader with no ill effects except it will completely wipe your phone and data along with it.
ArminasAnarion said:
Well I really doubt unlocking your boot-loader would cause system crashes. The bootloader is a different partition of the phones drive, and its not active while your in system. If you flashed a custom kernel or your on a 8.1 DP build its probably one of those things. I know that a lot of people are having random reboots with 8.1 builds.
Reply back with what kernel and rom build your using; it would help a lot.
As for restoring a locked bootloader; you would need to restore everything to stock by flashing a stock factory image with fastboot drivers. And make sure you restore the original google recovery. I don't know the command on hand, but it is possible. Just many don't do it because it's easy to miss something important and now you can never unlock you bootloader again; its happened!
If I were you, I would just keep my bootloader unlocked and then just wipe and flash a stock factory image.
Click to expand...
Click to collapse
Thank you @ArminasAnarion and @v12xke
I never ended up flashing ROMS or kernels. I stayed stock. Originally I did flash a modified boot for magisk but that was so unstable I flashed the stock one back.
fastboot flashing lock
fastboot flashing lock_critical
Data will be wiped.
Related
Hi Guys,
Not sure if much can be done, so before I flashed a rom for 5.1.1, I decided to flash the required, firmware 2.9.710.x, but before flashing that, I re-locked my bootloader, as I have s-on. Before that, I was trying to get the OTA to work but it didn't as I had mounted system as r/w. So I had stock recovery, s-on and relocked bootloader. After I flashed the firmware, I could not unlock the bootloader as there is some new developer setting that I am required to enable. BUT the I am still on old 5.0 ROM that will not boot anymore and is stuck on the splash screen - I've tried wipe cache and factory reset. I have an RUU for 1.32 which I cannot use because now I have 2.9.710.x firmware. I've also tried to sideload the OTA but that will not work because system was mounted r/w
Is there anything I can do to get it to work? I feel like I've tried all avenues, but if there is something you guys think I can do to make it work again, I'd be over the moon!
anshuashmeet said:
Hi Guys,
Not sure if much can be done, so before I flashed a rom for 5.1.1, I decided to flash the required, firmware 2.9.710.x, but before flashing that, I re-locked my bootloader, as I have s-on. Before that, I was trying to get the OTA to work but it didn't as I had mounted system as r/w. So I had stock recovery, s-on and relocked bootloader. After I flashed the firmware, I could not unlock the bootloader as there is some new developer setting that I am required to enable. BUT the I am still on old 5.0 ROM that will not boot anymore and is stuck on the splash screen - I've tried wipe cache and factory reset. I have an RUU for 1.32 which I cannot use because now I have 2.9.710.x firmware. I've also tried to sideload the OTA but that will not work because system was mounted r/w
Is there anything I can do to get it to work? I feel like I've tried all avenues, but if there is something you guys think I can do to make it work again, I'd be over the moon!
Click to expand...
Click to collapse
Never relock if your phone is not 100 % stock. Otherwise it won't boot. Besides there are already numerous post written by people that made the same mistake as you did. Even if your phone could boot you wouldn't be able to enable the OEM Unlock option since it's not implemented in the 1.XX roms and by flashing the firmware you do not update your rom.
I guess the only possibility to recover your phone is using this RUU service.
Just because I'm curious: Why didn't you use one of the backups that are provided here?
Flippy498 said:
Never relock if your phone is not 100 % stock. Otherwise it won't boot. Besides there are already numerous post written by people that made the same mistake as you did. Even if your phone could boot you wouldn't be able to enable the OEM Unlock option since it's not implemented in the 1.XX roms and by flashing the firmware you do not update your rom.
I guess the only possibility to recover your phone is using this RUU service.
Just because I'm curious: Why didn't you use one of the backups that are provided here?
Click to expand...
Click to collapse
Thanks for your reply!
I've submitted an enquiry form to them. Didn't know that service existed. Hopefully they have the RUU file that I need.
I did download the stock backup file from that link but I thought before I give it a go, I'll try and get an OTA and get an official update. That failed so I decided to flash the firmware before going to the latest rom. Forgetting I just locked my bootloader with stock recovery, completely unaware of this 5.1 developer option issue. My fault for not doing research, but I didn't know such issue could exist as for the last few years, I haven't had an issue like this. Normally issues occur if I flash a newer ROM without firmware so was trying to avoid that.
Krassermensch's Firmware Update Tool
My situation:
I'm too young to buy the Sunshine App to set my device S-Off but I want to update my device's firmware every time a firmware update's available. Since I compile ROMs and cannot do that via OTA updates the only acceptable way for me is to install signed firmwares in a locked bootloader. After doing that manually I thought I should write a tool that installs the right firmware for your device automatically. As I'm already running the latest firmware on my device after doing the procedure manually I cannot test if the flash part works correctly. Anyway, I achieved to read out the CID as well as the current firmware version and my tool reports that I'm running the latest firmware version I integrated for my device what's correct. So this part works well.
How the tool works:
The tool asks you if you've already installed the HTC USB drivers on your computer. If you haven't you can install it easily using my tool. After that the tool explains you how to set up your phone to be detected by the computer. Then it checks which device you have and checks which firmware's currently installed on it. Right after that the tool installs all the firmwares newer than the one that's currently installed on your phone one after another until the latest firmware my tool is shiped with runs on your device. The procedure doesn't wipe your data since signed firmware-updates are installed.
Requirements:
- An HTC 10
- A computer running windows
- An internet connection
- An unlocked bootloader
- An installed TWRP
Who is this tool for?
All the people who can't or don't want to set their device S-Off while running a non-stock ROM.
Why should I use this tool?
- It updates your firmware to the latest one available for your device automatically
- It doesn't wipe your storage
- You don't need to be S-Off
Download
https://www.androidfilehost.com/?fid=745425885120704223
When the file is downloaded just extract it on your Windows computer and run the batch file. Everything else will be explained.
Important to know
Your boot and recovery partitions will be replaced by the stock ones so after successfully updating your firmware you need to reflash TWRP as well as your Boot partition.
This process is performed automatically now. No need to do that manually.
Tools using ADB just like mine may interfere with other tools that also use ADB. Make sure all these tools are disabled.
Now I need your feedback to be able to optimize the tool! I'll add new firmwares from time to time. I'm looking forward to your reviews
GitLab
https://gitlab.com/Feulner/Firmware-Update-Tool-HTC10
If you like my work consider a donation to support me in financing computer-components which are meant to replace the defect ones in my broken PC.
If you donate you'll donate to my father who will gimme the money. Thank you really much!
This works with unsigned firmware?
Good job, though irrelevant to me
xunholyx said:
This works with unsigned firmware?
Good job, though irrelevant to me
I would guess that you would have to have matching CID and MID of course.
Click to expand...
Click to collapse
No no, not unsigned firmware. I'll explain it more detailed tomorrow or so. The tool just checks your device's CID as well as your device's current firmware version and updates it to the most current firmware version I integrated in my tool. If your firmware is very old the tool also updates again and again until you have the lässt firmware automatically.But it uses signed firmware packages. The biggest advantage is that it should work fully automatic. Try it out and let me know what you think. I go to bed now...
krassermensch said:
No no, not unsigned firmware. I'll explain it more detailed tomorrow or so. The tool just checks your device's CID as well as your device's current firmware version and updates it to the most current firmware version I integrated in my tool. If your firmware is very old the tool also updates again and again until you have the lässt firmware automatically.But it uses signed firmware packages. The biggest advantage is that it should work fully automatic. Try it out and let me know what you think. I go to bed now...
Click to expand...
Click to collapse
I'm s-off since the day after I got my phone, so.......
It sounds like a great idea. I'm sure lot of people will appreciate this. If it does work like you say, WAY better than going back to stock.
xunholyx said:
I'm s-off since the day after I got my phone, so.......
It sounds like a great idea. I'm sure lot of people will appreciate this. If it does work like you say, WAY better than going back to stock.
Click to expand...
Click to collapse
Since when do you have to go back to stock to "fastboot flash zip some_firmware.zip" (as this tool does)?
--beaups
Hm sounds good, but i wont use it until we have some more information what it actually does.
As far as i know, theres no way to just update your firmware with signed zips without partly wiping your device. I had to reflash Viper10 (or restore a nandroid backup) the last time i updated my firmware, cause boot and recovery partitions got replaced. Not completely sure if this affects stock devices, it may work there, but not for devices which are modified with a custom ROM. For this you need a NoWipe firmware from sneakyghosts thread, but these cant be flashed while s-on.
So please explain in more details what your tool does, of course when youve got your sleep .
It most likely flashes firmware zips from OTA updates since those do not wipe the device. He already said it does that, he said if you're on a very old firmware it will keep updating your firmware progressively until you're on the latest version. So if you've never updated before, and there have been three updates since then, the tool will flash the firmware zip of each OTA one after the other.
Updated the main post, hopefully everything's clear now. I need your reviews now. I'm also thinking about an automatic bootloader lock with backup solution so you don't need to lock your bootloader manually and also don't lose your data partition.
Why it doesn't work with unlocked bootloader?
CroCop18 said:
Why it doesn't work with unlocked bootloader?
Click to expand...
Click to collapse
I didn't try but normally your HTC 10 would block the installation if the bootloader is unlocked. Could you try it out and report. It's a bit hard to try it out by myself currently... It will most probably report that your new firmware's flashed but it actually will not be flashed after that if your bootloader's unlocked. If it's flashed anyway it'd be perfect since I'd not have to make a backup solution in that case. But I guess that the 10 isn't different to the M9 for example when it comes to firmware flashing. I read that you can have an unlocked bootloader if your device is S-Off but those are things I haven't been able to try out so far...
krassermensch said:
I didn't try but normally your HTC 10 would block the installation if the bootloader is unlocked. Could you try it out and report. It's a bit hard to try it out by myself currently... It will most probably report that your new firmware's flashed but it actually will not be flashed after that if your bootloader's unlocked. If it's flashed anyway it'd be perfect since I'd not have to make a backup solution in that case. But I guess that the 10 isn't different to the M9 for example when it comes to firmware flashing. I read that you can have an unlocked bootloader if your device is S-Off but those are things I haven't been able to try out so far...
Click to expand...
Click to collapse
Really? You don't know how to unlock your bootloader? You don't need S-Off for it.
This answers the question I had wondered about. How does this install OTAs with a custom recovery? It doesn't, correct?
You need to be stock for this. The first thing you do after unlocking the bootloader (which pretty much anyone here has done) is to flash a custom recovery.
This tool will only work for users who are still completely on stock.
IO would test myself, but I'm already S-Off/unlocked bootloader/custom recovery/modified firmware/custom ROM|, and I don't want to take the time to go back to stock and incrementally update the steps to see what won't work. I think as soon as you flash custom recovery, you can't use this method.
If you want to unlock your bootloader, HTC provides the method and instructions at htcdev.com
xunholyx said:
Really? You don't know how to unlock your bootloader? You don't need S-Off for it.
This answers the question I had wondered about. How does this install OTAs with a custom recovery? It doesn't, correct?
You need to be stock for this. The first thing you do after unlocking the bootloader (which pretty much anyone here has done) is to flash a custom recovery.
This tool will only work for users who are still completely on stock.
IO would test myself, but I'm already S-Off/unlocked bootloader/custom recovery/modified firmware/custom ROM|, and I don't want to take the time to go back to stock and incrementally update the steps to see what won't work. I think as soon as you flash custom recovery, you can't use this method.
If you want to unlock your bootloader, HTC provides the method and instructions at htcdev.com
Click to expand...
Click to collapse
Sure I know how to unlock a boitloader. If you watch my profile you can see I'm a ROM maintainer. I have to use custom recoveries to do that. People interpret my posts wrongly sometimes. I dunno why. Anyway, I use TWRP but after flashing a recovery or any other image file I lock my bootloader again for safety reasons. You just need to have a locked bootloader to use my tool currently... And no, u don't need to be stock. This tool just requires a locked or relocked bootloader. U can use whatever ROM u like. U just need to have a locked bootloader and my tool installs the latest firmware I integrated for your HTC 10 model. I know what I do. You should just read my posts a bit more carefully to prevent yourself from contending wrong things...
krassermensch said:
Sure I know how to unlock a boitloader. If you watch my profile you can see I'm a ROM maintainer. I have to use custom recoveries to do that. People interpret my posts wrongly sometimes. I dunno why. Anyway, I use TWRP but after flashing a recovery or any other image file I lock my bootloader again for safety reasons. You just need to have a locked bootloader to use my tool currently...
Click to expand...
Click to collapse
" I read that you can have an unlocked bootloader if your device is S-Off" quote from you
I did read it wrong. I was thinking that you meant you needed soff to unlock bootloader.\
And yes, now that I understand what you meant, with S-Off you shouldn't need to re-lock your bootloader.
xunholyx said:
" I read that you can have an unlocked bootloader if your device is S-Off" quote from you
I did read it wrong. I was thinking that you meant you needed soff to unlock bootloader.\
And yes, now that I understand what you meant, with S-Off you shouldn't need to re-lock your bootloader.
Click to expand...
Click to collapse
Yeah, dude, I think I wouldn't be able to write a batch tool with fastboot and adb if I didn't know the whole stuff. My broken Nexus 4 has teached me a lot over the last 3½ years
Just to confirm... and thanks for the tool
I have a HTC 10 and nothing has been done to it since I bought it (Stock everything) will this tool keep it that way but give me the latest OTA?
Milamber said:
Just to confirm... and thanks for the tool
I have a HTC 10 and nothing has been done to it since I bought it (Stock everything) will this tool keep it that way but give me the latest OTA?
Click to expand...
Click to collapse
You do not need this tool if you are Stock everything, unless you unlocked your bootloader.
Milamber said:
Just to confirm... and thanks for the tool
I have a HTC 10 and nothing has been done to it since I bought it (Stock everything) will this tool keep it that way but give me the latest OTA?
Click to expand...
Click to collapse
No, I could write a tool for manual OTA flashing, too, but I don't want to do that since OTAs are for stock devices which are notified about OTA updates automatically. If you want to flash OTAs quicker: there's a thread here on xda where OTA zips are shared with an explaination how to flash it manually... This tool can be used by stock device's owners but it wouldn't be necessary...
krassermensch said:
I didn't try but normally your HTC 10 would block the installation if the bootloader is unlocked. Could you try it out and report. It's a bit hard to try it out by myself currently... It will most probably report that your new firmware's flashed but it actually will not be flashed after that if your bootloader's unlocked. If it's flashed anyway it'd be perfect since I'd not have to make a backup solution in that case. But I guess that the 10 isn't different to the M9 for example when it comes to firmware flashing. I read that you can have an unlocked bootloader if your device is S-Off but those are things I haven't been able to try out so far...
Click to expand...
Click to collapse
Thanks for your explanations, now i understand your tool a bit more.
But if it only works with a locked/relocked bootloader i cant use it. Really no offense and i dont want to sound rude (!), but isnt it already a design problem? You said the tool is designed for people with non-stock ROMS, but that does imply that you have an unlocked bootloader to flash and keep your ROM and recovery up to date. To use your tool you have to relock the bootloader after flashing the ROM. But to update the ROM to a newer version you have to unlock the bootloader again via HTCDev (and loosing your data while doing this)? Sounds a bit weird to me...or did i miss something?
So which adb commands are you using? Didnt have the time to check your script yet (sorry!). Because im S-On with my bootloader unlocked an i COULD flash a signed firmware.zip i extracted from an official OTA via ADB. This wiped my boot and recovery partitions, but not data. Just had to restore the two partitions to get everything working again.
-Vulture- said:
Thanks for your explanations, now i understand your tool a bit more.
But if it only works with a locked/relocked bootloader i cant use it. Really no offense and i dont want to sound rude (!), but isnt it already a design problem? You said the tool is designed for people with non-stock ROMS, but that does imply that you have an unlocked bootloader to flash and keep your ROM and recovery up to date. To use your tool you have to relock the bootloader after flashing the ROM. But to update the ROM to a newer version you have to unlock the bootloader again via HTCDev (and loosing your data while doing this)? Sounds a bit weird to me...or did i miss something?
So which adb commands are you using? Didnt have the time to check your script yet (sorry!). Because im S-On with my bootloader unlocked an i COULD flash a signed firmware.zip i extracted from an official OTA via ADB. This wiped my boot and recovery partitions, but not data. Just had to restore the two partitions to get everything working again.
Click to expand...
Click to collapse
So you could flash the firmware-update.zip from the OTA without relocking your bootloader?
And it was really updated after that?
krassermensch said:
So you could flash the firmware-update.zip from the OTA without relocking your bootloader?
And it was really updated after that?
Click to expand...
Click to collapse
Thats what i did, bootloader was unlocked and flash successfully. I extracted the firmware.zip from an official OTA (TMOB-101) for my device and flashed it via ADB from my PC. Since the firmware.zip is signed, it can be flashed. Doesnt work with modified zips however, like the ones from sneakyghosts thread. He removed unnecessary stuff like the flash command for boot and recovery which my broke my phone initially. Thats why you need TWRP to restore them later.
As you already said with your tool, its also important here to get the right file to flash and not to skip a firmware update in between. You have to go from very old -> old -> current without skipping old.
I used the step-by-step instructions from here:
http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520
Friend bought a used 5x from Swappa and it come with an unlocked bootloader, nbd. We flashed stock firmware and left it as is. He's happy.
Now that Android Pay/Safetynet is detecting his bootloader, he's not having any of it. Wants to lock the bootloader back up to restore AP functionality. I just want to confirm, 1.) this will wipe EVERYTHING on it, correct (I told him to get everything backed up)? And 2.), do I need to flash stock images before locking even though it's a bone stock 7.0 setup?
tallgrasshawk said:
Friend bought a used 5x from Swappa and it come with an unlocked bootloader, nbd. We flashed stock firmware and left it as is. He's happy.
Now that Android Pay/Safetynet is detecting his bootloader, he's not having any of it. Wants to lock the bootloader back up to restore AP functionality. I just want to confirm, 1.) this will wipe EVERYTHING on it, correct (I told him to get everything backed up)? And 2.), do I need to flash stock images before locking even though it's a bone stock 7.0 setup?
Click to expand...
Click to collapse
Never done it but to be safe I'd use a tool like this one.
http://forum.xda-developers.com/nex...olkit-skipsoft-android-toolkit-nexus-t3230444
tallgrasshawk said:
Friend bought a used 5x from Swappa and it come with an unlocked bootloader, nbd. We flashed stock firmware and left it as is. He's happy.
Now that Android Pay/Safetynet is detecting his bootloader, he's not having any of it. Wants to lock the bootloader back up to restore AP functionality. I just want to confirm, 1.) this will wipe EVERYTHING on it, correct (I told him to get everything backed up)? And 2.), do I need to flash stock images before locking even though it's a bone stock 7.0 setup?
Click to expand...
Click to collapse
There is a Heisenberg thread that will walk you thru it all. Download the image you want, factory reset while booted, auto reboot, bootloader, flash every file according to the thread, then fastboot OEM lock. Reboot and done. Don't lock until you flash every file.
Sent from my Nexus 5X using XDA-Developers mobile app
Hello all!
I've gotten too lazy to maintain updating my rooted Pixel XL whenever there's a security patch.
I've re-locked the boot-loader and done a full stock flash from google's stock images, but now i get this warning when it boots up:
"Your device has loaded a different operating system. "
It then boots up fine, barring the fact OTA's still fail, the one thing I was trying to get working.
Any advice?
Thanks in advance.
You skipped flashing the bootloader and radio without those ota will fail.
Am i mistaken in thinking the "flashall.bat" from google does that as well?
Thanks
Edit.
Think i found it, your comment made me watch for the radio and boot-loader when i tried the flash-all batch script again, I believe i Locked the boot-loader before flashing it to stock again.
Unlocked, flashed, re-locked and it appears to be working now.
Thanks!
Help me
Vacross said:
Am i mistaken in thinking the "flashall.bat" from google does that as well?
Thanks
Edit.
Think i found it, your comment made me watch for the radio and boot-loader when i tried the flash-all batch script again, I believe i Locked the boot-loader before flashing it to stock again.
Unlocked, flashed, re-locked and it appears to be working now.
Thanks!
Click to expand...
Click to collapse
Can you help me... I have same problem...
DR3W5K1 said:
You skipped flashing the bootloader and radio without those ota will fail.
Click to expand...
Click to collapse
Can you pls explain on how to do that
Follow the guide for flashing stock images via fastboot and you shouldn't have this problem.
Stop after step 4
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
I also had the same issue on Nexus 6p.. after I realised that I forgot to flash boot.img from stock firmware.. anyway it is resolved...
UI Design Services with Compelling and Engaging User-Experience
Get user-centered UI Design for your mobile app or website.
UI Design services
Im replacing my Pixel 6 Pro due to a bad accelerometer sensor. My phone is rooted with latest Magisk, has Kiri kernel installed as well. What's the most efficient way to prep the phone for a return to Google?
Official Google Android Flash Tool
and
Official Instructions for Locking/Unlocking the Bootloader
roirraW edor ehT said:
Official Google Android Flash Tool
and
Official Instructions for Locking/Unlocking the Bootloader
Click to expand...
Click to collapse
So just running the flash tool will remove root, reset to factory default and return kernel to stock? After that just lock the bootloader and good to go?
Starzboy77 said:
So just running the flash tool will remove root, reset to factory default and return kernel to stock? After that just lock the bootloader and good to go?
Click to expand...
Click to collapse
Yes. All of that.
Starzboy77 said:
So just running the flash tool will remove root, reset to factory default and return kernel to stock? After that just lock the bootloader and good to go?
Click to expand...
Click to collapse
If you like, for further explanation, flashing the 100% official stock ROM will both remove root and overwrite whatever kernel you currently have with the stock kernel that's included in the stock ROM. If you choose any option anywhere (on that official stock flashing site of Google's, or via any other method) to *not* factory reset the phone, sure you'd have any root-oriented apps still installed on your phone, but the phone wouldn't be rooted because the stock kernel is 100% official now.
There are many ways to do the same thing, but this is the safest and 100% sure method that it's all stock. i.e. my answering this way isn't dependent on anything you've possibly done to your phone - if you or someone had gone out of the way to modify the software of the phone even more than typically, this method would still completely overwrite any changes you've done, because you're flashing the completely stock ROM.
I haven't used the Official Google Android Flash Tool but countless others in this section alone have reported their situations on their phones being saved by this method - even when flashing the stock ROM in only a slightly more manual way via the official Platform Tools had failed to solve their issues: manually downloading the stock firmware, extracting it, and running the flash-all.bat file included (if on Windows). Since I haven't used it myself, I'm just going by memory of what others have reported about using it and I'm under the impression that it gives you the choice to wipe (factory reset) or not wipe your phone when it flashes it.
I wouldn't be surprised if by default it wipes, as that's what the flash-all.bat script from the manual full factory image zip file does by default.
Also, heads up. You never want to lock the bootloader unless you are 100% certain the phone is 100% stock. Ergo, why even though there are other methods to unroot and "return to stock", there is no good reason to use them unless you just don't have access to a computer, or a cable, or it's some kind of unroot emergency or some other circumstance that calls for more manual methods - which also leave a greater chance for accidental human error and can just plain brick your phone - although that might not matter since you're returning the phone.
roirraW edor ehT said:
If you like, for further explanation, flashing the 100% official stock ROM will both remove root and overwrite whatever kernel you currently have with the stock kernel that's included in the stock ROM. If you choose any option anywhere (on that official stock flashing site of Google's, or via any other method) to *not* factory reset the phone, sure you'd have any root-oriented apps still installed on your phone, but the phone wouldn't be rooted because the stock kernel is 100% official now.
There are many ways to do the same thing, but this is the safest and 100% sure method that it's all stock. i.e. my answering this way isn't dependent on anything you've possibly done to your phone - if you or someone had gone out of the way to modify the software of the phone even more than typically, this method would still completely overwrite any changes you've done, because you're flashing the completely stock ROM.
I haven't used the Official Google Android Flash Tool but countless others in this section alone have reported their situations on their phones being saved by this method - even when flashing the stock ROM in only a slightly more manual way via the official Platform Tools had failed to solve their issues: manually downloading the stock firmware, extracting it, and running the flash-all.bat file included (if on Windows). Since I haven't used it myself, I'm just going by memory of what others have reported about using it and I'm under the impression that it gives you the choice to wipe (factory reset) or not wipe your phone when it flashes it.
I wouldn't be surprised if by default it wipes, as that's what the flash-all.bat script from the manual full factory image zip file does by default.
Also, heads up. You never want to lock the bootloader unless you are 100% certain the phone is 100% stock. Ergo, why even though there are other methods to unroot and "return to stock", there is no good reason to use them unless you just don't have access to a computer, or a cable, or it's some kind of unroot emergency or some other circumstance that calls for more manual methods - which also leave a greater chance for accidental human error and can just plain brick your phone - although that might not matter since you're returning the phone.
Click to expand...
Click to collapse
Thank you for the indepth explanation. Really appreciate it.
Just factory reset it so your data is wiped and send it back. Google has never cared about them being rooted when you return them.
TonikJDK said:
Just factory reset it so your data is wiped and send it back. Google has never cared about them being rooted when you return them.
Click to expand...
Click to collapse
Is this accurate? Can anyone else confirm? What about having a different kernel? Does the bootloader have to be locked?
Starzboy77 said:
Is this accurate? Can anyone else confirm? What about having a different kernel? Does the bootloader have to be locked?
Click to expand...
Click to collapse
As I said, you should not lock the bootloader unless the phone is 100% stock. To me, it doesn't matter what anyone else says about what Google cares about. If it were my phone, I'd restore it 100% stock too. 10 minutes of very little effort for some peace of mind. Rather than meh, they might not care, or meh you might be the unlucky exception. Why take the chance?
But it's your phone, your decision. No one else makes the decision for you.
roirraW edor ehT said:
As I said, you should not lock the bootloader unless the phone is 100% stock. To me, it doesn't matter what anyone else says about what Google cares about. If it were my phone, I'd restore it 100% stock too. 10 minutes of very little effort for some peace of mind. Rather than meh, they might not care, or meh you might be the unlucky exception. Why take the chance?
But it's your phone, your decision. No one else makes the decision for you.
Click to expand...
Click to collapse
This to the millionth degree. and it also goes for when purchasing a used device or a refurbished device. Reflash Android. they make it so simple now that it can be done using another phone. No PC necessary.
Flash Tool changed the game 3 years ago for how easy the process is. Heck I just reflash my phone monthly because it's such great technology (kidding, not kidding?)