Database Info

Changing Hboot from 6.98.1002

I rooted a while back using revolutionary, and currently have hboot 6.98.1002.
I could really do with getting back to s-on and stock etc etc, but every guide I follow just doesn't seem to work.
I have searched, and searched and searched, but I'm a week down the line and still unable to change my hboot.
I'm at pains to start a new thread, but this thing is drving me bonkers.
I've read the instrcutions here for Alphareved:
http://forum.xda-developers.com/showthread.php?t=1236890
but typing the 'adb devices' in cmd but it just doesn't work. Is there some kind of zip file i should be extraxcting to get the sdk (i think it's called that?).

did u try this exe?
http://dl.google.com/android/installer_r16-windows.exe
edit: what is the output of "adb devices"?

-Download this file, it has the adb and fastboot files needed to proceed
-Extract the file to "c:\" so that the path looks like this C:\android-tools
-Install HTCDriver (Fastboot drivers) (should already be installed from revolutionary) but here's the link again
-Open cmd and type "cd/"
-then type "cd android-tools"
*To test whether you have set up all the files correctly and your phone is connected correctly you can do the following;
*Plug your phone in (when plugging in select CHARGE ONLY (i.e. leave on the home screen)
*In cmd type "adb" and press enter, it should show a list of commands, then type "fastboot"and press enter, it should also show a list of commands)
*If both these commands work you have extracted the files to the right place and have setup cmd right.
*then type "adb devices"
*Should show connected phone serial if not then try get the latest HTCdrivers
Flash the ENG HBoot
To flash the ENG HBoot you can use one of these methods;
1) Fastboot
-Place the .img file (extracted from PG88IMG.zip) in C:\android-tools
-Boot phone into fastboot
-Run command "fastboot flash hboot engHBOOToverARX.img" in CMD
2) Android Flasher
-Download from here
-Select phone, select Hboot .img (bootloader)
-Boot phone into fastboot and select FLASH
3) Updater file (PG88IMG.zip)
-Download the PG88IMG.zip (make sure is called that EXACTLY, not pg88img.zip or PG88IMG.zip.zip)
-Place file on your SD card root, and boot into HBoot, and follow onscreen instructions
4) adb shell (LAST LAST resort, one typo and you can brick your phone, do some reserch before doing it
-Place the hboot on your SD card and remane it to "hboot.img"
-Boot into recovery
-adb devices - Must show your serial
-adb shell
-su (it should show #, that means you have the right permission, if it shows $ afterwards you dont have permission)
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img (backup your current hboot)
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18 (flashes new hboot)
If you have any problems first check out this thread for answers
Install the RUU
How to check if downloaded RUU is compatible with your phone:
To avoid errors etc, you need to confirm your phone is unbranded, i.e. check if your CID matches the CID check list in the RUU you downloaded.
To do this Run the installer, then go to your Windows Temp Folder, sort the folder by date and pick the folder with the latest date, and locate the rom.zip file inside, open it up and open the android-info.txt file. Your CID should be in the list, if not then you need to create a GoldCardto install that RUU.
Here is a list of RUU's you can download for your phone [ROM]Shipped Desire S ROM Collection - xda-developers
Here and here are two great threads for HTC Desire S Guides

Thanks so much for the replies fellas. I'm away from my comp until this evening, but I'll relpy once I've tried these out.

This will work
hycaet said:
I rooted a while back using revolutionary, and currently have hboot 6.98.1002.
I could really do with getting back to s-on and stock etc etc, but every guide I follow just doesn't seem to work.
I have searched, and searched and searched, but I'm a week down the line and still unable to change my hboot.
I'm at pains to start a new thread, but this thing is drving me bonkers.
I've read the instrcutions here for Alphareved:
http://forum.xda-developers.com/showthread.php?t=1236890
but typing the 'adb devices' in cmd but it just doesn't work. Is there some kind of zip file i should be extraxcting to get the sdk (i think it's called that?).
Click to expand...
Click to collapse
I just did for my HTC Desire S (India).
This should help . Read

foX2delta said:
Flash the ENG HBoot
To flash the ENG HBoot you can use one of these methods;
1) Fastboot
-Place the .img file (extracted from PG88IMG.zip) in C:\android-tools
-Boot phone into fastboot
-Run command "fastboot flash hboot engHBOOToverARX.img" in CMD
Click to expand...
Click to collapse
This did it. Perfect. You're a star. This has bugged me for so long. You've made my bloody day. God bless and seasonal greetings.

foX2delta said:
Install the RUU
How to check if downloaded RUU is compatible with your phone:
To avoid errors etc, you need to confirm your phone is unbranded, i.e. check if your CID matches the CID check list in the RUU you downloaded.
To do this Run the installer, then go to your Windows Temp Folder, sort the folder by date and pick the folder with the latest date, and locate the rom.zip file inside, open it up and open the android-info.txt file. Your CID should be in the list, if not then you need to create a GoldCardto install that RUU.
Click to expand...
Click to collapse
How can i check my CID number to match with the RUU version?

terragady said:
How can i check my CID number to match with the RUU version?
Click to expand...
Click to collapse
Not sure of the command right now, Google it, like how to check you cId, then when you run the RUU go to your temp folder, I think there is a file called android.txt in the folder with the rom.zip is and it has the list.

[GUIDE]How to update from 5.0 to 5.x without loosing data if you're not 100% stock

Instead of having instructions all over the place inside various threads I felt a clear guide should be available as it's own thread. Now since Google implemented this great feature (all hail google) where normal OTA's no longer work on Nexus devices with Android 5.0 that isn't 100% stock i.e. rooted with or without custom recovery a lot of people don't know how to update their devices.
IMO opinion the easiest way without losing any data is to use Fastboot and this is an attempt of a how-to-guide. This is made on a windows PC, probably works with other OS's too.
What you need:
1. You need ADB.exe and fastboot.exe inside an easy accessed folder i.e. put in c:\ADB.
The easiest way to get these are with this tool: http://forum.xda-developers.com/showthread.php?t=2317790
You can also get this by installing the whole Android SDK but that is just a waste of bandwidth and time.
2. You also need to download the latest factory image for Nexus 5. Do this here: https://dl.google.com/dl/android/aosp/hammerhead-lrx22c-factory-0f9eda1b.tgz
3. You might need adb drivers but you'll have to find instructions for this by yourself.
The procedure:
1. Extract necessary files. The factory image you'll download is named hammerhead-lrx22c-factory-0f9eda1b.tgz
This is an archive which can be opened with an extractor of your choice e.g. 7-zip
Inside this archive is another file with no file type extension. Extract this file and rename it to whatyouwant.zip since it's a regular zip file. Then extract all files within this file (very meta with zips inside zips inside zips etc).
The files you need for updating with fastboot are:
system.img
boot.img
radio-hammerhead-m8974a-2.0.50.2.22.img (rename this to radio.img for more convenience)
put all these files in the ADB folder (it will make things easier).
2. plug your phone to your PC. You need to have USB debugging activated in developer mode.
3. open a command prompt and orient yourself to the adb folder (c:\ADB)
4. type adb reboot bootloader and wait until your phone is in bootloader mode.
5. type fastboot flash system system.img and wait until it's finished.
6. type fastboot flash radio radio.img
7. type fastboot flash boot boot.img
8. reboot your device (type fastboot reboot).
Hopefully this will work and you will update without loosing any data. Then you can proceed with rooting, flashing custom recovery etc. This is easiest done with WUG nexus root toolkit (http://forum.xda-developers.com/showthread.php?t=2389107)
I couldn't find any other guide's but if there's already one please remove this.

Just a note, you don't need adb.exe at all, and the drivers are actually USB drivers.
Its also worth noting that 95% of us prefer to recommend users not use toolkits.
Also, you could simply say:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash radio radio.img
...then point them to the existing adb and fastboot thread which would have saved you writing all the installation stuff out.

Thanks for the guide @mertzi. I've just used to upgrade my Nexus 5 to 5.0.1 without any loss of data. I appreciate the help!

rootSU said:
Just a note, you don't need adb.exe at all, and the drivers are actually USB drivers.
Its also worth noting that 95% of us prefer to recommend users not use toolkits.
Also, you could simply say:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash radio radio.img
...then point them to the existing adb and fastboot thread which would have saved you writing all the installation stuff out.
Click to expand...
Click to collapse
Do I still use "fastboot flash radio radio.img" even though the radio image from the tgz file is "radio-hammerhead-m8974a-2.0.50.2.22.img"?

optoisolator said:
Do I still use "fastboot flash radio radio.img" even though the radio image from the tgz file is "radio-hammerhead-m8974a-2.0.50.2.22.img"?
Click to expand...
Click to collapse
No. The 4th section is the file path and location.

So this keeps user data? Just updated the system to 5.0.1?
Maintains root and all?
Sent from my Nexus 5 using XDA Free mobile app

Keeps user data but you will have to re-root.

Thank you, thank you, thank you.
I've spent last couple days trying to make heads or tails out of other "tutorials". Some of them linked the OTA update and gave instructions for full image, others gave instructions but lacked the links to the image. I am surprised that none of my searches took me here until today.

Thanks a lot for this guide I was ale to update to 5.0.1 thanks to this guide.

Can I use this method to update from 4.4.4 to 5.0.0 ?

... Not aire if you can jump from 4.4.4 to 5.0 this way...
I actually jumped flashing radio and baseband and THEN flashing CM12.1

[Q] NOT your average stuck in bootloop

Bear with me: Right now my nexus is stuck in a bootloop. My nexus had been partially rooted, everytime i went to download the OTA 5.0.1. update it would just take me to TWRP, and i didn't know what to do with that. So I finally tried to fully root the phone, and also use TWRP to install the OTA update. Now I'm stuck, I've tried wiping the cache/factory reset. How do I got about flashing it back to stock without losing all my data?
(apologies for the title, I thought originally that I had killed mtp and adb, but I figured out how to get them back just after posting)
Thanks!

As I saw your post before the edit.... Stop using toolkits and read about adb. If it's bootlooping then it's 95% not bricked so don't panic and read the guides
Just download system.img you want and fastboot it
Edit -
Don't see this as me being mean or a ****. This is stuff everyone needs to know, it's really not hard at all so don't worry. Once you've used it a few times you'll wonder why you ever used toolkits

Ben36 said:
As I saw your post before the edit.... Stop using toolkits and read about adb. If it's bootlooping then it's 95% not bricked so don't panic and read the guides
Just download system.img you want and fastboot it
Edit -
Don't see this as me being mean or a ****. This is stuff everyone needs to know, it's really not hard at all so don't worry. Once you've used it a few times you'll wonder why you ever used toolkits
Click to expand...
Click to collapse
I don't think you're being a ****. I'm very grateful for your input. I used to be very into jailbreaking when I had an iPhone, but i haven't been able to put the same time towards getting the hang of rooting (which I think has a steeper learning curve to begin with|). I sort of understand adb but I obviously need to learn more. I've been using the toolkit because it was simpler. I remember from trying to use adb before that I need to place the files I want to transfer in the same folder as adb (i think?) but I could never get that to work.
I also don't understand system.img.'s relevance here. I'm not getting the "Error: Update package missing system.img" error.

The reason I say read the guides is simply it saves me or anyone else typing out a massive guide that already exists in many places.
If you're looping then something is more than likely wrong with the system not the data. So flashing just the system will keep your data safe (as long as you flash the same android version as you previously had, lollipop or kitkat)
You need to be in the bootloader not recovery and use the command fastboot flash system system.img
Google img's are here - https://developers.google.com/android/nexus/images
(just keep unzipping until you find the individual img files)

photobumm said:
I don't think you're being a ****. I'm very grateful for your input. I used to be very into jailbreaking when I had an iPhone, but i haven't been able to put the same time towards getting the hang of rooting (which I think has a steeper learning curve to begin with|). I sort of understand adb but I obviously need to learn more. I've been using the toolkit because it was simpler. I remember from trying to use adb before that I need to place the files I want to transfer in the same folder as adb (i think?) but I could never get that to work.
I also don't understand system.img.'s relevance here. I'm not getting the "Error: Update package missing system.img" error.
Click to expand...
Click to collapse
He's saying to flash a system image to get you up and running again, and I agree that that is what you should do. As far as placing the files in the same folder as adb and fastboot is concerned (you'll use fastboot to flash the image), you need to do just that. I created a folder on my desktop called "ADB" and that's where both adb and fastboot are, as well as all the files that I flash with fastboot ie. system images, recoveries, etc... Here's a great guide to get you going with adb and fastboot- http://forum.xda-developers.com/showthread.php?t=2277112
Now when you go to flash it, if you decide to use the flash-all.bat to flash everything (the full factory image) and bring you back to stock, you'll have to open the .bat file with a text editor and remove the "-w" from the script and that way it won't wipe your phone. If you want to just reinstall the OS without everything else (worth a shot), just flash the system with the command
Code:
fastboot flash system system.img
and that should get you running again. If what I just said is confusing, read the guide I posted and it should become clear.
Here is where you'll download the factory image from- https://developers.google.com/android/nexus/images
Just unzip it, pull the system.img out and place it in the same folder that fastboot is in and flash away.
And one final thing- definitely avoid toolkits at all costs. You spent a good chunk of change on your phone, take the time to learn how to mod it the correct way.
Good luck!

_MetalHead_ said:
He's saying to flash a system image to get you up and running again, and I agree that that is what you should do. As far as placing the files in the same folder as adb and fastboot is concerned (you'll use fastboot to flash the image), you need to do just that. I created a folder on my desktop called "ADB" and that's where both adb and fastboot are, as well as all the files that I flash with fastboot ie. system images, recoveries, etc... Here's a great guide to get you going with adb and fastboot- http://forum.xda-developers.com/showthread.php?t=2277112
Now when you go to flash it, if you decide to use the flash-all.bat to flash everything (the full factory image) and bring you back to stock, you'll have to open the .bat file with a text editor and remove the "-w" from the script and that way it won't wipe your phone. If you want to just reinstall the OS without everything else (worth a shot), just flash the system with the command
Code:
fastboot flash system system.img
and that should get you running again. If what I just said is confusing, read the guide I posted and it should become clear.
Here is where you'll download the factory image from- https://developers.google.com/android/nexus/images
Just unzip it, pull the system.img out and place it in the same folder that fastboot is in and flash away.
And one final thing- definitely avoid toolkits at all costs. You spent a good chunk of change on your phone, take the time to learn how to mod it the correct way.
Good luck!
Click to expand...
Click to collapse
So I have adb and fastboot running. And I changed the flash-all.bat file. However, I don't understand what I do now? I downloaded the Hammerhead zip and it has a bunch of things in it. Which files do I put into the adb/fastboot folder and how do I then flash them?
In the hammerhead file it lists the bootloader, flash-all, radio and then a zip file "image-hammerhead...". What files am I using and what is the code that I input? Is this the same sa flashing a rom?
I also tried placing the system.img in the adb folder, and then using the
Code:
fastboot flash system system.img
but it gives me an error "cannot load 'system.img'

So now my issue is I get a "error: could not load 'system.img'. after running
Code:
fastboot flash system system.img [code/] . I also tried with boot.img. Same error.
I ran the "flash all" script, by accident, a screenshot of the terminal is attached.. I'm still stuck in a the boot loop, however, and if try to enter recovery mode an android lying down with a red triangle is present. The above "error: could not load..." is still present.

Create a folder and put fastboot in it.
So you unzipped the stock image. You said you have some images in the folder and a zip image.
Unzip that second zip.
There you will find the rest of the images you need.
Now take the recovery, bootloader, system, userdata, cache, and radio images and move them into the folder which you created for fastboot.
Rename the bootloader image to bootloader. img
Now when looking at that open folder containing all the images and fastboot hold down shift and left click and select "open command promt from window"
Type
/fastboot erase bootloader
/fastboot flash bootloader bootloader.img
/fastboot reboot-bootloader
/fastboot erase recovery
/fastboot flash recovery recovery.img
/fastboot erase radio
/fastboot flash radio radio.img
Repeat for the rest of the image files
Finally type /fastboot reboot
Profit.
---------- Post added at 10:54 PM ---------- Previous post was at 10:51 PM ----------
P. S. Make sure your phone is booted in fastboot mode first.

Oh and that android is stock recovery

U fixed it?

So for some reason I still kept getting that error. I ended up restoring to stock using the nexus root toolkit. So it all worked out in the end.

Installing CM13 on untouched HTC Desire S

Hi lovely people,
I'd like to install CM13 on my HTC Desire S S510e. I have found way too many different instructions on how to proceed and I was wondering if there's a simple, step-by-step (I really mean step-by-step) guide on how to do it. By now, as far as I understand I should:
1. S-OFF my phone (although I heard it's possible to install a custom rom even with S-ON?). I've read that you can do it using HTCDev or Alpharev. However the HTC Desire S doesn't appear on the list of supported devices in the first link. Which device should I select from the list? On the other hand, the Alpharev website says that Alpharev is deprecated and one should use Revolutionary but the Revolutionary website is empty. Finally a more general question: what's the benefit of using HTCDev or Alpharev?
2. Flash sagaopt TWRP 2.8.7.1. I use ArchLinux. In Linux I'd have to install android-tools to have adb and fastboot, then do "adb reboot bootloader" followed by "fastboot flash recovery TWRP-recovery-sagaopt-2.8.7.1.img"? Or do I have to first install an older version of TWRP to convert my sdcard to EXT4 to then install the sagaopt 2.8.7.1 version?
3. Use TWRP to convert my sdcard to EXT4.
4. Install cm-13.0-XXXXXXXX-UNOFFICIAL-sagaopt.zip and gapps by putting the files into the sdcard using adb (what's the command to do this?) and then flash the files using TWRP.
What steps am I missing? What are the perils? What should I be particularly careful with?
Please help me understand and condense the heaps of information found in this forum.
Thanks,
Ricardo

rikardo.h said:
Hi lovely people,
I'd like to install CM13 on my HTC Desire S S510e. I have found way too many different instructions on how to proceed and I was wondering if there's a simple, step-by-step (I really mean step-by-step) guide on how to do it. By now, as far as I understand I should:
1. S-OFF my phone (although I heard it's possible to install a custom rom even with S-ON?). I've read that you can do it using HTCDev or Alpharev. However the HTC Desire S doesn't appear on the list of supported devices in the first link. Which device should I select from the list? On the other hand, the Alpharev website says that Alpharev is deprecated and one should use Revolutionary but the Revolutionary website is empty. Finally a more general question: what's the benefit of using HTCDev or Alpharev?
2. Flash sagaopt TWRP 2.8.7.1. I use ArchLinux. In Linux I'd have to install android-tools to have adb and fastboot, then do "adb reboot bootloader" followed by "fastboot flash recovery TWRP-recovery-sagaopt-2.8.7.1.img"? Or do I have to first install an older version of TWRP to convert my sdcard to EXT4 to then install the sagaopt 2.8.7.1 version?
3. Use TWRP to convert my sdcard to EXT4.
4. Install cm-13.0-XXXXXXXX-UNOFFICIAL-sagaopt.zip and gapps by putting the files into the sdcard using adb (what's the command to do this?) and then flash the files using TWRP.
What steps am I missing? What are the perils? What should I be particularly careful with?
Please help me understand and condense the heaps of information found in this forum.
Thanks,
Ricardo
Click to expand...
Click to collapse
3.check android version in system settings if it is lower or lower2.3.X (if its not it could be ****ty) than check bootloader version
3.1 turn off fastboot in battery settings
3.2 power don phone
3.3 boot phone with vol down clicked and if its -REVOLUTIONARY- or if its 0.98.x s-off or 2.0X s-off go to 6
if its 0.98 s-on you go to 5
if its 2.02 ask anyone else on my desires with 2.02 s-off newer worked for me but you can try it (go to 4) or only unlock it
http://www.htcdev.com/bootloader select HTC Desire HD and dont upgrade anything (start at step 1 skip preparation) after that go to 8
if its 2.00 contine
4.download the oldest rom with you branding from http://androidruu.com/?developer=Saga
4.1 http://forum.xda-developers.com/showpost.php?p=18746686 downlad misc_version
4.2 http://forum.xda-developers.com/showthread.php?t=1312859 download DooMLoRD_v4_ROOT-zergRush-busybox-su.zip and extract zergRush
4.3 go to folder with misc_version and zergRush and open cmd there and type
adb push misc_version /data/local/tmp/
adb push zergRush /data/local/tmp/
adb shell
cd /data/local/tmp/
chmod 777 zergRush
chmod 777 misc_version
./zergRush
./misc_version -s 1.27.405.6
exit
exit
exit
4.4 execute the firmware form step 4
5 download and follow http://rev.alpharev.nl
6 follow http://forum.xda-developers.com/showthread.php?t=1679338 (optional)
7 follow B in http://forum.xda-developers.com/showthread.php?t=1858508 (optional)
Installing
1.Flash TWRP 2.8.7.0
2.Format SDcard ext4
3.Flash TWRP 2.8.7.1 sagaopt
4.boot recovery
5.use "adb push your-system-sagaopt.zip /sdcard/"
6.Flash it with TWRP
7.(Optional) download GAPPS pico copy it do "internal storage" and install it with TWRP
for the complete tutorial look at http://forum.xda-developers.com/htc-desire-s/general/trying-to-install-cm13-htc-desire-s-t3414878 page 2 for the first one and page 1 for the second
---------- Post added at 09:36 PM ---------- Previous post was at 09:28 PM ----------
CM13 is to heavy for the phone CM12.1 is stable but slow (sometimes you miss a call because the mobile is too slow) CM11 is fast but old (i used CM12.1 now im using CM11 nightly but the gallery doesnt play videos i deleded it)

Thank you for reposting that guide and for suggesting CM11 instead of CM12.1 or CM13. In that guide it says that unlocking the 2.02 s-on using the htcdev tool doesn't work for him if I understand correctly. Also I went to the htcdev website and they say that the tool will remove all personal data including applications, text messages and personalized settings. However I wanted to install a recovery and make a backup of the phone as it is now and that wouldn't work if everything gets removed before installing the recovery. Is there a way to install a recovery without removing anything?

rikardo.h said:
Thank you for reposting that guide and for suggesting CM11 instead of CM12.1 or CM13. In that guide it says that unlocking the 2.02 s-on using the htcdev tool doesn't work for him if I understand correctly. Also I went to the htcdev website and they say that the tool will remove all personal data including applications, text messages and personalized settings. However I wanted to install a recovery and make a backup of the phone as it is now and that wouldn't work if everything gets removed before installing the recovery. Is there a way to install a recovery without removing anything?
Click to expand...
Click to collapse
I think you can try titanium backup with an oneclickroot (kingroot or framaroot) or unlock it with the risk of loosing data first backup contacts/sms and callhistoy with apps of the playstore and your sdcard isnt affected

Oh i could be that you need the win8+ fastboot fix for htcdev http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337
and if it doesnt work use windows 7 (dont forget to install htc sync)
if its 2.00.0002/2.00.2000 you can s-off it if its 2.02.0002 its ****ty

I use linux. It's 2.00.0002 so I guess I should follow step 4, but step 4.4 asks me to execute a window's exe file which I can't execute. What should I do instead? Unlock it using htcdev as if it was 2.02 s-on or will that mess my phone up?

rikardo.h said:
I use linux. It's 2.00.0002 so I guess I should follow step 4, but step 4.4 asks me to execute a window's exe file which I can't execute. What should I do instead? Unlock it using htcdev as if it was 2.02 s-on or will that mess my phone up?
Click to expand...
Click to collapse
sorry for that step you need windows there is no other way
you can only unlock but the best way is to use a windows PC/Laptop of a dude or use a VM with windows 7 or XP with usb pass
google windows 7 iso and look for one you can use in vm

I found this https://code.google.com/archive/p/htc-flasher/wikis/HTCFlasher.wiki
Do you know if it would help?

you can try (you need your rom as NBH and the desire s (saga) isn't supported its risky) it but save is a Virtual Machine with windows and usb passthrough

How to unroot, lock bootloader and go back to stock?

For background, I have Verizon pixel 2 and am using a Mac.
I went down a massive rabbit hole last night reading through these forums and all the posts and was able to unlock bootloader, flash the January OTA and then root by doing the modified boot file with magisk. (interestingly enough the booting into recovery gives me red ! Over a dead Android and I could not load the OTA that way, nor did the adb sideload OTA comand work either, I had to push the extracted walleye img and then the zip file as discussed in one of the steps in some other thread here)
So anywho, in the end I now have a phone that gives me 2 errors when it reboots, one for unlocked bootloader and another for root telling me something is wrong with my phone and i should contact the manufacturer (which I read on here is normal), but my biggest issue is that my ADT alarm app doesn't work anymore (even if i check it off for hide in magisk). I feel like the root is just not worth it for me and I want to revert to completely stock image, even if it resets my phone and I have to re back everything up all over again like did when i had to do the unlocking of the boot loader.
So -- What are the steps I should take?
1)uninstall magisk from magisk manager?
2)delete magisk manager?
The above will unroot me, correct?
3)Do I push the stock boot image file onto the phone?
4) do I have to repush the latest OTA walleye image and zip file onto the phone again?
5) do I then do the adb reboot and do the flashing lock command (same command i did to unlock the boot loader) to lock up the bootloader and reset to stock?
If someone could be as explicit as possible in correctiong or validating my steps above it would be much, much appreciated.
I don't want to do any more unnecessary steps in flashing things than is needed so if I have extra steps above (perhaps 4 is not needed?) Let me know.
Thanks

Proceed with Caution
I am not an expert by any means, but can speak from personal experience. I was in the exact same situation as you. I followed the detailed steps to unlock the bootloader on my pixel 2, received similar issues, and the same prompt when the phone rebooted. All that to say proceed with caution.
My thoughts on questions 1 & 2: I personally wouldn't recommend you remove or delete magisk from the manager. When I did i had to reinstall it via twrp. My phone functioned fine, apart from the error at reboot.
My thoughts on questions 3 -5: When I followed the steps on XDA for your questions here I ended up bricking my Pixel 2 with locked bootloader from Verizon. Probably an error on my part, but wouldn't want someone else to go through the headache, hours of issues, and then an expensive paper weight.
My suggestion would be to:
1. Leave your phone as is and attempt to trouble shoot the app or apps you are having issue with
2. contact Google support on your phone and see if they would replace it
3. wait for an established method to unroot the pixel 2 here
Thankfully Google replaced my phone due to the error after rebooting, prior to me bricking it. I knew I had a replacement phone coming. So I attempted to go back to stock and that is when I messed it up.
Note sure this is exactly what you were looking for, but hope this helps you.

Dozens of posts with hundreds of pages on how to root but no advice on how to go back to stock cleanly?

iridium7777 said:
Dozens of posts with hundreds of pages on how to root but no advice on how to go back to stock cleanly?
Click to expand...
Click to collapse
Your version is Verizon which is making things more complicated. Generally when the bootloader is unlocked, you just hit flash-all.bat and then relock the phone. Given that the Verizon I'm not sure.
So you are on stock ROM with all these apks loaded ? If you go to settings, then do a factory data reset, you'll reset the phone back to stock and completely wipe the phone and return it to stock, at that point you can go into bootloader mode and relock.
Again your bootloader is unlocked, so the flash-all is your best option. If you see the red exclamation point with the error android laying on his back, you press power and up volume and toggle that and it will bring in the stock recovery which you can sideload the OTA however it may fail since you have magisk.
I bought my phone stock last year and have not rooted it or modified it in anyway. Too many problems and it only gets harder and harder as Google releases a new phone.

@mikeprius -- thank you for replying. after reading more on here, it seems like that's the way to go -- flash-all script, seems like i don't really need to do 1&2 that i wrote above as the flash-all will wipe that out by itself.
at that point i should be running the latest stock 8.1 but with an unlocked bootloader (and according boot up message screen) and i should be able to re-do the fastbook unlocking command to lock the phone back up.
(and yes, after reading even more now -- and i tried this yesterday -- i completely missed the portion about PWR + Vol Up button, that's why i think i had that issue, but still, i was able to push the update by pushing img and then the zip through).

iridium7777 said:
@mikeprius -- thank you for replying. after reading more on here, it seems like that's the way to go -- flash-all script, seems like i don't really need to do 1&2 that i wrote above as the flash-all will wipe that out by itself.
at that point i should be running the latest stock 8.1 but with an unlocked bootloader (and according boot up message screen) and i should be able to re-do the fastbook unlocking command to lock the phone back up.
(and yes, after reading even more now -- and i tried this yesterday -- i completely missed the portion about PWR + Vol Up button, that's why i think i had that issue, but still, i was able to push the update by pushing img and then the zip through).
Click to expand...
Click to collapse
If I were in your situation and the bootloader is unlocked, just use flash-all which has a wipe script then call it a day. I think trying to screw around even more is just a waste of time and I wouldn't even bother with the OTA, just erase and flash stock. You don't have to relock your bootloader if you don't want to, if you stay fully stock you may still be able to get OTA updates. I'm not sure if a bootloader locked is required someone can chime in as it has been awhile since I've done this, but over 1 yr ago, I just kept the bootloader unlocked, kept things stock and everything was good to go. Obviously there are security issues with an unlocked bootloader, but I'm sure you know this already

@mikeprius you keep saying reset/erase, do you suggest i re-set the phone and then flash the stock image?
i was just going to flash the stock image, i figured it already wipes the phone, and locking the bootloader would wipe it again, so what's the point of erasing all data prior?

Not to hijack this thread, but a question to add... I thought that there were kernels that would mask certain things to allow all of those apps to work, and get rid of the "problem with device" message.
Is that correct?

iridium7777 said:
@mikeprius you keep saying reset/erase, do you suggest i re-set the phone and then flash the stock image?
i was just going to flash the stock image, i figured it already wipes the phone, and locking the bootloader would wipe it again, so what's the point of erasing all data prior?
Click to expand...
Click to collapse
Just flash the stock images. It will auto reset.
Again, don't mess with anything just flash stock images, then go from there.
Also flash the newest version of the stock images out there. The pixel 2 will error if you try to downgrade any version.

here are all the steps to UNROOT and LOCK the boot loader on your Pixel 2 on a Mac (windblows users simply ignore all the "./" references).
1) download the latest ADB tools from google
2) download the latest factory Walleye image
3) unzip files from 1&2 into a common directory
4) edit flash-all.sh file and add "./" infront of every instance of "fastboot" in the script [windows users ignore this step]
5)hook up your phone to your computer in debug and file transfer mode. check that "./adb devices" loads your devide
6)type " ./adb reboot bootloader"
7) check that your device is still connected by typing "./fastboot devices"
8) type "./flash-all.sh"
===the script will run and your phone will be restored to stock, and UNROOTED. upon boot up skip through all of the setup steps and get to the phone settings as fast as you can. enable developer option, enable debug mode, set phone to data transfer ====
9) check that your phone is connect to your computer by "./adb devices"
10) type "./adb reboot bootloader"
11) check your devices is still connected by "./fastboot devices"
12) type "./fastboot flashing lock"
===== this will re-wipe your device again, you'll see the circle of death, and this will LOCK your boot loader back up again======
side note, feel free to skip over the steps where you check that your phone is still connected to the computer (./fastboot devices) if you're less paranoid and comfortable.

iridium7777 said:
here are all the steps to UNROOT and LOCK the boot loader on your Pixel 2 on a Mac (windblows users simply ignore all the "./" references).
1) download the latest ADB tools from google
2) download the latest factory Walleye image
3) unzip files from 1&2 into a common directory
4) edit flash-all.sh file and add "./" infront of every instance of "fastboot" in the script [windows users ignore this step]
5)hook up your phone to your computer in debug and file transfer mode. check that "./adb devices" loads your devide
6)type " ./adb reboot bootloader"
7) check that your device is still connected by typing "./fastboot devices"
8) type "./flash-all.sh"
===the script will run and your phone will be restored to stock, and UNROOTED. upon boot up skip through all of the setup steps and get to the phone settings as fast as you can. enable developer option, enable debug mode, set phone to data transfer ====
9) check that your phone is connect to your computer by "./adb devices"
10) type "./adb reboot bootloader"
11) check your devices is still connected by "./fastboot devices"
12) type "./fastboot flashing lock"
===== this will re-wipe your device again, you'll see the circle of death, and this will LOCK your boot loader back up again======
side note, feel free to skip over the steps where you check that your phone is still connected to the computer (./fastboot devices) if you're less paranoid and comfortable.
Click to expand...
Click to collapse
hey there. what is the command suppose to look like? every combination I try gives me an error:
first, I don't even enter the Fastboot command the same wayit given me an error:
Asads-MacBook:~ asad$ ./fastboot devices
-bash: ./fastboot: No such file or directory
so I try this: Asads-MacBook:~ asad$ fastboot devices
[serial #] fastboot
these are all the errors I get:
Asads-MacBook:~ asad$ cd /Users/asad/Desktop/walleye-opm1.171019.021
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: fastboot./: No such file or directory
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: ./fastboot: No such file or directory
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
fastboot: usage: unknown command ./flash
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: fastboot./: No such file or directory
...
how is the command suppose to look that I can edit it the right way?

"fastboot: No such file or directory" means that you didn't do step 1, step 3 on the file you didn't download, and there should probably be a "cd /<whatever the 'common directory'>" is. (I just created a directory named adb. That's good enough for me to know what it's for.)
You have to download adb and fastboot (which come in the adb tools file), unzip them to whatever directory you're going to use for flashing the phone, and cd to that directory.
Then, since you're evidently on MacOS, each command has to have ./ in front of it (that says "the current directory"). Try all that, then see what happens.

Rukbat said:
"fastboot: No such file or directory" means that you didn't do step 1, step 3 on the file you didn't download, and there should probably be a "cd /<whatever the 'common directory'>" is. (I just created a directory named adb. That's good enough for me to know what it's for.)
You have to download adb and fastboot (which come in the adb tools file), unzip them to whatever directory you're going to use for flashing the phone, and cd to that directory.
Then, since you're evidently on MacOS, each command has to have ./ in front of it (that says "the current directory"). Try all that, then see what happens.
Click to expand...
Click to collapse
yayy! that worked!
so i had adb and fastboot in a folder (platform-tools) and i had the factory image in its own seperate folder (walleye-files). i was making the cd; walleye folder and trying to flash-all.sh there.
so i had to put the files from the walleye folder into the platform-tools folder. Then I made platform-tools the cd. now when . i could now follow all the steps from 4-12 and got the pixel 2 the way it was OTB.
thanks!

Great! I'm not a Mac expert (last time I used one was the 128K Mac in 1985), so I'm not sure how to export a path in MacOs, so I gave you the complicated way, but you got it done anyway. (If you ever find out how to add the platform-tools folder to your path, you can leave adb and fastboot in there and keep the ROMs [walleye] in their own folder, cd to it and adb and fastboot will still work.)