Database Users

[GUIDE] Workaround for attaining S-OFF (for Windows 8.1. users)

For those on Windows 8.1 who have just about given up trying to get S-OFF...
For reference I have an ATT HTC One, but showing in bootloader as m7ul (didn't seem to make a difference to any downloads/steps anyway so meh)....
hboot = 1.44
S-ON (hence the inability to install the new GPE 4.4 ROMs)...
So I have tried every single fix imaginable on these forums and the Internet in general... absolutely nothing has worked... trust me....
I then seen a comment from someone mentioning using Ubuntu to do it... I thought... no way, I'm not bothering, all that effort, and it'll still fail... well tell you what, via various forums, sites, fixes etc (lol) I got there in the end.
Prerequisites:
Rooted
hboot 1.44 (I haven't tested newer versions... assume you're looking here really because you had the same problems as me - test with other hboot versions at your own risk I guess)
Not sure if the version of Rom you are currently on matters, I was on 4.3 Google edition (Eragon V14), so don't ask me which to be on
Let's do the following:
1) Download Windows Ubuntu from here:
http://www.ubuntu.com/download/desktop/windows-installer
Click "Get the Installer"
Download and save the .exe to wherever you want
2) Right click the .exe and create shortcut
3) Change the target of the shortcut (right click --> Properties) to end with the following: \wubi.exe --32bit
4) Run the installer, and just go with any defaults
5) Once rebooted in to Ubuntu we are going to download and install fastboot and adb
6) Click the Windows key, type "Terminal" and hit RETURN
7) type the following at the "command" prompt: (do not type [RETURN] <-- lol)
sudo add-apt-repository ppa:nilarimogard/webupd8 [RETURN]
sudo apt-get update [RETURN]
sudo apt-get install android-tools-adb android-tools-fastboot [RETURN]
When prompted, enter the password you set up when you installed Ubuntu in the first place.
8) To confirm Fastboot now works (yes... it was that easy)
Boot your phone in to Fastboot (hold VOL DWN + Power --> Fastboot)
Connect up the phone to USB
In the terminal, type the following then press RETURN
sudo fastboot devices
You should see your device serial, confirming it is recognised by Fastboot ----
9) Now to download Rumrunner -- get the archive from the following location:
http://rumrunner.us/rumrunner_downloads/rumrunner_HTC_0.5.0.tgz
Open the download (rather than save), and extract all files to the Home/Download folder (you can just click and drag them over)
10) Now, we need to allow the "soju" file to be executed
Right click the extracted file "soju" --> go to Properties --> Permissions tab --> Tick "allow executing file as program"
Almost there.....
11) Boot the phone back up and enable USB Debugging via Developer Options
Also change display timeout to 10mins, and set screen security to None
12) Disable Fastboot where applicable (Settings --> Power --> Fast boot)
13) Now to run the Rumrunner application....
Again, within the terminal, type the following:
cd Downloads [RETURN]
(if this doesn't work, you need to navigate to the folder you extracted the "soju" file to, so the cd (change directory) DOS command works fine here)
Now type the following (once you are in the same location as "soju")
sudo ./soju
If you are ready (definitely) to start the process, now press RETURN.
14) You will be asked twice to type "Yes" exactly as displayed followed by RETURN to confirm, please do not type Yes to the warnings that will come up periodically after the script starts (if you give them a moment, you will see them continue without any input from yourself)
15) Sit back... and wait for it to complete. The process took about 20mins in total to complete on my phone... and I've now got S-OFF. If you keep getting prompted for what to do with your phone being plugged in - just press cancel to the prompts.
p.s. if this worked - please press THANKS :good:
If anyone needs any clarification, let me know, I will try and respond as soon as possible (if others could help - that would be appreciated too)

Registered here just so I could say you are awesome! Your guide worked for me after literally months of trying to get s-off for my AT&T HTC One hboot 1.55.
A couple things I had to do differently:
1. I used a ISO image of Ubuntu 12.04.3 32 bit burned to a dvd and just booted off it to the option to try Ubuntu without installing. I could not get your link to work with my Windows 7 installation.
2. Since I was not actually booting from my hard drive but rather a read only DVD, I had to do some improvising for the extracting of the rumrunner files. I put them on the desktop, but then had to search a bit to find them in order to run the soju file in terminal.
Again, thank you!

EM101 said:
Registered here just so I could say you are awesome! Your guide worked for me after literally months of trying to get s-off for my AT&T HTC One hboot 1.55.
A couple things I had to do differently:
1. I used a ISO image of Ubuntu 12.04.3 32 bit burned to a dvd and just booted off it to the option to try Ubuntu without installing. I could not get your link to work with my Windows 7 installation.
2. Since I was not actually booting from my hard drive but rather a read only DVD, I had to do some improvising for the extracting of the rumrunner files. I put them on the desktop, but then had to search a bit to find them in order to run the soju file in terminal.
Again, thank you!
Click to expand...
Click to collapse
whats yer firmware fella?

painnpleasure said:
whats yer firmware fella?
Click to expand...
Click to collapse
It was 3.17.502.3 but since I achieved s-off I am now a "converted to Google Edition" with firmware 3.62.1700.1.

EM101 said:
It was 3.17.502.3 but since I achieved s-off I am now a "converted to Google Edition" with firmware 3.62.1700.1.
Click to expand...
Click to collapse
Ok thnx fella.im on 3.63.111.3 and having difficulties running rumrunners.ill give it another go then. I want to get to go Google edition aswel.

sudo ./soju
I get err command not found!!
help plz should I be using the linux?
No prob I gut it :laugh:

skythunder83 said:
sudo ./soju
I get err command not found!!
help plz should I be using the linux?
No prob I gut it :laugh:
Click to expand...
Click to collapse
Use the ls command to see what is in the directory you are in. Use the cd command to change directories. Keep searching til you find the directory where you put the soju file. Good luck.

Does my HTC One still have to be unlocked from HTC-Dev? Thank you in advance.

EM101 said:
Registered here just so I could say you are awesome! Your guide worked for me after literally months of trying to get s-off for my AT&T HTC One hboot 1.55.
A couple things I had to do differently:
1. I used a ISO image of Ubuntu 12.04.3 32 bit burned to a dvd and just booted off it to the option to try Ubuntu without installing. I could not get your link to work with my Windows 7 installation.
2. Since I was not actually booting from my hard drive but rather a read only DVD, I had to do some improvising for the extracting of the rumrunner files. I put them on the desktop, but then had to search a bit to find them in order to run the soju file in terminal.
Again, thank you!
Click to expand...
Click to collapse
Glad to hear buddy. I also spent a considerable amount of time trying to find a solution to this and had just about given up.
Thanks for providing some additional notes on your steps too, might help someone else get theirs working too.
Sent from my One using XDA Premium 4 mobile app

alessiomoro1994 said:
Does my HTC One still have to be unlocked from HTC-Dev? Thank you in advance.
Click to expand...
Click to collapse
By whatever means, you will need to initially be rooted. Unlocking via HTC Dev was how I got root.
Ironically this also (at the time, not sure if it's changed) doesn't work in Windows 8.1 lol and I had to root my phone using my parents laptop with Windows 7 installed.
They then upgraded to 8,1 so I couldn't use it to get S-OFF later on.
Sent from my One using XDA Premium 4 mobile app

I finally got s-off on my att htc one. Was pretty much trying the same thing as OP stated here, but had some difficulties with other things.
1. OP's instructions didn't work for latest ubuntu (13.10)
2. Had linux mint installed on my pc, but it was 64bit.. tried quite a bit to get it working there (adb and fastboot work), but rumrunner was not happy with 64bit
3. Finally tried it on Ubuntu 12.04.3 LTS 32 bit and everything was smooth with it
One other thing to note.. I used live USB instead of installing ubuntu on my pc. had no issues, but had to use a bit older version of ubuntu and 32 bit (even tho my pc has 16Gigs of memory)

Don't know what's different, but Rumrunner worked for me - hboot 1.56, ARHD 41.0 and Windows 8.1

I'm using crouton install of Ubuntu on my chromebook and after trying to install adb and fastboot I get:
E: Unable to locate package android-tools-adb
E: Unable to locate package android-tools-fastboot
Any ideas guys? I really want s-off! Any help would be appreciated!
Sent from my Nexus 7 using XDA Premium 4 mobile app

roose21 said:
I'm using crouton install of Ubuntu on my chromebook and after trying to install adb and fastboot I get:
E: Unable to locate package android-tools-adb
E: Unable to locate package android-tools-fastboot
Any ideas guys? I really want s-off! Any help would be appreciated!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sounds like the location of those packages has changed? Unless the reason it isn't working is because of the version of Ubuntu you're on. Hmm.
Sent from my One using XDA Premium 4 mobile app

Try this:
http://vondroid.com/threads/how-to-...on-ubuntu-and-other-linux-based-systems.9793/
Sent from my One using XDA Premium 4 mobile app

My computer finally can recognize my phone in fastboot mode. Thanks !
Sent from my HTC One using Tapatalk

punisher195 said:
My computer finally can recognize my phone in fastboot mode. Thanks !
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Use the "thanks" button and rate the thread then
Sent from my One using XDA Premium 4 mobile app

[Q] Working with ADB & Fastboot

Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!

feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.

feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
Which OS are you using (Windows, Mac, Linux)?

Elrondolio said:
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.
Click to expand...
Click to collapse
It's the latest SDK.
bsara said:
Which OS are you using (Windows, Mac, Linux)?
Click to expand...
Click to collapse
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Hope this helps someone. Cheers!

feered said:
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Click to expand...
Click to collapse
I had the same issue on Ubuntu. You need to run ADB with sudo...why? I have no idea...but I found a post suggesting it on StackOverflow and it worked...so I'm not questioning it.
Before doing anything below, have you installed adb via apt-get? If so, remove it and just put a link to your SDK manager adb and fastboot in a folder included in your PATH or add the directory to the path, then start a new shell before proceeding. The adb and fastboot provided by apt-get are old.
Do the following:
Have your device plugged in and fully booted and with USB debugging enabled
run this command: "sudo adb kill-server && adb start-server"
You should be prompted on the device to authorize the access of your computer via adb
run "adb devices" to make sure that it all worked correctly

[how to]restore software status official

*this thread is for m9+. it will NOT work on m7,m8,m9(or anything else). search your device general forum for a specific thread
if you have recently s-off'ed using an exploit that changed your banner in the bootloader screen to software status: modified,then this thread is for you.
*you must be s off.
*you must have superuser installed
read this:
this will not work if your s on
the usual disclaimers:
this has been tested,but if it melts your phone into a little pile of aluminum goo,its not my fault.
credits
-beaups for schooling me on echo command protocol
-strace for originally discovering the location of the lock status flag(check out this thread for more info) wich started off my love for chasing such things.
- @omar302 for getting the ball rolling,providing dumps,and lots of testing. he s-on'ed his phone several times during the tests,and has provided a huge amount of valuable info
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and lower)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "tampered flag"
enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00' | dd of=/dev/block/mmcblk0p11 bs=1 seek=39940
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify software status: official
if this does not work for you
*first reread this thread in its entirety. make sure you have met the prerequisites,and double check your code and make sure you have not forgotten a step,or screwed something up trying to type it (especially if using a terminal emulator),and check that you have not gotten any errors.
if youre still confident you did things correctly,you need to PM me:
1)the results of: fastboot getvar all
2)a link to an uploaded p11.
you get fastboot getvar all by:
-place phone in fastboot
-enter in fastboot getvar all right click,click mark,highlight in white,hit enter or right click to copy
you dump p11 by:
adb shell
su (if needed to get a #)
dd if=/dev/block/mmcblk0p11 of=/sdcard/mmcblk0p11
transfer the file on internal storage to your pc and upload it
im not trying to be a ****,but its not helpful to post "didnt work" if you screwed something up,or if your not willing to help find a solution. especially if others have found it to work on their same variant.
important:
from now on,i will need a copy of your cmd window as well if we want to get to the bottom of whats happening. some folks seem to be simply writing extra bytes,wich is screwing up the flag location. please make sure this shows an entire session,not just a last part where it looks correct. we cant figure it out if you only show part of what you did.

mine too

scotty1223 said:
mine too
Click to expand...
Click to collapse
@Scotty. What we need is how to change from Relocked to Locked on Bootloader.

deleted. Better to wait Scotty's stock guide.

west2cool said:
@Scotty. What we need is how to change from Relocked to Locked on Bootloader.
Click to expand...
Click to collapse
You cannot do it without turning s on. P9 is now being protected,and any attempts to modify it in any manner result in security being turned back on
Planning a back to stock guide once I'm fairly certain it can be done safely
Sent from my Nexus 9

yvtc75 said:
echo -ne ......
Click to expand...
Click to collapse
Don't do this unless you're ready to be stock and s on,and have all your ducks in a row. It could leave you bricked or stuck in the bootloader with a security warning.
There's good reason I didn't post it.
Sent from my Nexus 9

Just to confirm that it worked fine on my phone as per the screen photo in OP post. Also, just a warning to others, S-Off through SunShine might give you problems or would fail in case of repeated attempts (going back & forth between S-ON & S-OFF).
Thanks again to @scotty1223 for his help & work time this possiblef or the M9+.

Worked for me! Thanks!

omar302 said:
Just to confirm that it worked fine on my phone as per the screen photo in OP post. Also, just a warning to others, S-Off through SunShine might give you problems or would fail in case of repeated attempts (going back & forth between S-ON & S-OFF).
Thanks again to @scotty1223 for his help & work time this possiblef or the M9+.
Click to expand...
Click to collapse
Could you please detail, what problems? I s offed twice, but I'll be cautious if I knew there might be a problem

tbalden said:
Could you please detail, what problems? I s offed twice, but I'll be cautious if I knew there might be a problem
Click to expand...
Click to collapse
Apparently SunShine has some security system that detects if you are unlocking many times & then would just stop stop working & gives you message that your device is acting in an unusual way. I then had to contact their support to get it resolved.

i am rooted but s on, how can i s off to use your method? can someone help me

Rabia said:
i am rooted but s on, how can i s off to use your method? can someone help me
Click to expand...
Click to collapse
Currently they are using sunshine
Sent from my HTC One using Tapatalk

scotty1223 said:
Currently they are using sunshine
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
is that the paid thing, do they send a file accross or is it a physical thing

Rabia said:
is that the paid thing, do they send a file accross or is it a physical thing
Click to expand...
Click to collapse
http://theroot.ninja
Sent from my HTC One using Tapatalk

Rabia said:
is that the paid thing, do they send a file accross or is it a physical thing
Click to expand...
Click to collapse
You install the app & run it on your phone with a internet connection, after the app makes some tests & confirms your device is compatible you will be prompted to pay through the app itself ($25.00). The app itself will run & phone restart & then you get S-OFF. My M9+ was also from UAE (official-UAE version) & S-OFF worked from the 1st time. Very simple process.

Stock Locked bootloader?? @scotty1223

jureca said:
Stock Locked bootloader?? @scotty1223
Click to expand...
Click to collapse
Not possible currently. Attempting to modify p9 will cause you to turn s on. It may be possible to use it to your advantage if you need to be 100% stock,but I haven't had a chance to come up with a process that I believe would be 100% safe for all users
Sent from my Nexus 9 using Tapatalk

scotty1223 said:
Not possible currently. Attempting to modify p9 will cause you to turn s on. It may be possible to use it to your advantage if you need to be 100% stock,but I haven't had a chance to come up with a process that I believe would be 100% safe for all users
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
Ok thank you, see if you can :good:

Nexus 7 2012 bricked, adb/fastboot connection ok but unauthorized. Can You help?

Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?

Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.

Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.

Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.

Following
I have the same error and like to follow

Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.

thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.

No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.

Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.

[GUIDE/TUTORIAL/HOWTO] HTC One M8 Stock to Android 12

[GUIDE/TUTORIAL/HOWTO] HTC One M8 from Stock to Android 12.1 / LineageOS 19.1
[GUIDE/TUTORIAL/HOWTO] HTC One M8 any version (single SIM: m8ul, m8vzw and m8spr or dual SIM: m8dug and m8dwg) stock to Android 12.1 / LineageOS 19.1
This detailed step-by-step guide helps you transform your HTC One M8 (any version) to a powerful one with Android 12.
Make sure you have the One M8 model, in Android, go to Settings > About phone and check the model.
CHANGELOG
v6. Moved to Android 12
v5. Moved to Android 11, improve readability, update pack
v4. Prepare for Android 11, Updated pack with latest TWRP
v3. Updated pack with latest Magisk
v2.1. Drop ADB 15 sec installer and use latest adb and fastboot.
v2. Update pack and tutorial for TWRP 3.4.0-1
v1. Initial release
1) DOWNLOAD
- djibe HTC One M8 pack (~40 Mo) : https://bit.ly/djibe-onem8-pack
(includes HTC USB Drivers, recovery TWRP 3.6.1_9-0 for all m8, Magisk Root, adb & fastboot.exe).
Unzip the djibe folder from the zip on root folder of C:\ drive.
- ROM Unofficial LineageOS 19.1: https://forum.xda-developers.com/t/rom-12l-unofficial-m8-m8d-lineageos-19-1-stable.4464733/
Download latest build here (compatible with all M8 signel/double SIMs variants): https://www.androidfilehost.com/?w=files&flid=334966&sort_by=date&sort_dir=DESC
# M8 GPe partition layout is no longer supported. The device must first be converted to Sense firmware, otherwise installation will fail.
# Android 13 is incoming
+ MindTheGApps ARM 12.1: https://androidfilehost.com/?w=files&flid=322935&sort_by=date&sort_dir=DESC
+ Charge phone to 100%
+ MicroSD card formatted in FAT32
+ Copy ROM + Google Apps + both Magisk files on microSD card. Insert it in phone.
WARNING. This tutorial uses Microsoft Windows.
WARNING. Warranty is now void.
WARNING. Read carefully the sentences starting with ###.
2) BACKUP DATA AND INSTALL DRIVERS
Disable Antivirus.
Install drivers from my pack:
right click on HTCDriver.exe > click on Run as administrator and continue the setup.
Connect HTC One (while phone on) to PC, let drivers install.
In Windows explorer, HTC One should be available.
### If not make sure phone connection is in File transfer mode (see Android notifications).
### Phone is still not visible in Windows Explorer ? See fix at end of tutorial.
Collect all personal photos, videos, etc ... and backup these on PC.
Use an app like Backupyourmobile/SMS Backup & Resotre to backup texts, contacts, etc.
Check that backup is located on microSD card.
Then copy the backup on your PC.
Disconnect phone.
Check that you have the latest official updates.
### If your phone is Simlocked/carrier locked/Network locked, don't go further.
Visit official website of your network carrier (or call their support) to retrieve your desimlock code.
Ask them for details on how to remove simlock.
How do I know my phone is simlocked ? When you insert a SIM card from another operator, network is inaccessible.
Only a stock ROM can remove simlock.
To go back from custom ROM to stock, see dedicated section at the end of tutorial.
3) UNLOCK BOOTLOADER
In Android, go to Settings > About > Software information > More.
Tap 7 times on Build number. It unlocks Developer options.
Go back to the About menu, you can see the new Developer options menu.
Tap on it, accept the warning.
Toggle on the USB debugging option.
Connect phone, a message appears on phone : Allow USB debugging?
check Always allow and confirm by tapping on OK.
Now, open a Windows command on my "flash" folder (hold Shift + right click on folder -> Open a windows command here).
### Then navigate to my flash folder (if it is on desktop) with this command :
Code:
cd /d C:\djibe\flash
Enter command :
Code:
adb devices
, confirm by pressing Enter.
Command returns :
Code:
List of devices attached
HT35****** device
### If no device is found, uninstall and reinstall properly the drivers while antivirus is off. Or see fix at the end of this tuto.
### Or start fresh on another PC.
Now type :
Code:
adb reboot bootloader
Phone restarts in Fastboot mode. Wait till phone screen is blank in fastboot mode.
Type:
Code:
fastboot devices
Command returns :
Code:
HT35**** fastboot
### You may have to fix drivers again (see fix at the end of tuto)
Type:
Code:
fastboot getvar all
Bootloader must be in version 3.19 (Thx @sterphles)
Type:
Code:
fastboot oem get_identifier_token
, confirm by pressing Enter.
Command returns multiple lines.
Select with your mouse all the lines from
Code:
<<<< Identifier Token Start >>>>
(included)
to the line
Code:
<<<<< Identifier token end >>>>>
(included).
Now on keyboard copy (Ctrl + C combo), then open Notepad.
In Notepad, paste those lines (Ctrl + V combo).
Now manually remove all the (bootloader) strings from each line.
Your notepad should now look like this :
<<<< Identifier Token Start >>>>
37A5DBF4FE5F0D9F4425E54AA91AFDBF
2A20E9C67C3BB4FAE60263F76BDEC6AC
847BF9FFB11DAEA4AB88AC8710435449
9BC12E93DF4C54FFE3D064C4C810C49A
2CDAF2E0CD3A164FED4A568CB0FD2AC6
C01AA991733D949C00987062D691DE91
8AA1C97CEBC3ACE83FECE75A1D03CE72
62414C7DC36A73AFCBF433E1EBE2EDC7
E272F73309632D3EF8C86E472B65E8EF
37E46B52FE3F94FC69D1854CA3DE6F48
C3E10001B233A70B1EAF35134F51FCC6
353E0CC98534E6E60A241A7063D0BE2F
A5B752E75C1C47E6F739BDBE67D024DA
3292A14278247557632639802722A86C
E61424F7666AE085AA9905096FEED1AD
5ECBBD867544E95ABDDA277690B8CB55
<<<<< Identifier Token End >>>>>
Now visit this website : https://www.htcdev.com/bootloader/
Register on the site. Confirm registration with your email.
In the select menu, chose HTC One (M8), click Begin unlock Bootloader button.
Agree to legal terms.
Next page, go to the bottom and click continue to step 5.
In the bottom of this page, in the lower textarea "My Device Identifier Token",
copy and paste the multiple lines you just edited (my example is just above).
Click Submit.
HTC tells you : Token Submitted Successfully.
Open your mailbox (associated to your HTC account).
Copy the Unlock_code.bin file attached to email in my "flash" folder you unzipped.
In Windows command, type :
Code:
fastboot flash unlocktoken Unlock_code.bin
, confirm with Enter.
Command should return :
Code:
unlock token check successfully
Back to phone, press Volume+ to select "Yes, unlock bootloader", then Power button to confirm flash.
Now wait while phone is going to Factory reset.
Don't let Android restart by holding both Power + Volume- to enter bootloader immediately.
FASTBOOT menu is overlined in red.
4) FLASH TWRP RECOVERY
Using the same Windows command prompt, enter :
Code:
fastboot devices
to make sure phone is still available.
Then
Code:
fastboot flash recovery twrp-3.6.1_9-0-m8.img
Command returns :
Code:
finished. total time: x.xxxxs
Now on phone, press Volume- to highlight HBOOT, confirm with Power button.
You are back to the booloader screen (UNLOCKED is written on top line), press Volume- to navigate to RECOVERY, and confirm with Power button.
Phone reboots in TWRP recovery.
5) BACKUP STOCK SYSTEM
In TWRP, check Never show this screen and Swipe to Allow Modifications.
You land on TWRP Home screen.
Always make a backup of your stock system. We never know when a weird bug will decapitate the system.
Go to Backup menu, select all partitions and Backup to microSD card.
Backup the generated TWRP folder content from your microSD card to PC.
6) WIPE PARTITIONS
Back to Home menu, go to Wipe > Advanced wipe.
Select Dalvik / ART Cache, Cache, System, Data, Internal Storage then Swipe to Wipe, go back to Wipe menu.
### Don't wipe SDcard
7) FLASH ROM, ROOT/MAGISK AND GAPPS
Back to Home screen, tap on Install > choose lineage*.zip,
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active)
then Add more Zips -> Magisk*.zip,
then Add more Zips -> mindthegapps*.zip,
then Swipe to confirm Flash.
Wait for operation to end (can be long).
When completed successfully, tap on Reboot.
Tap on Do not install when TWRP asks for the app install.
Wait during long first boot.
Setup Android.
8) You can use Backupyourmobile to restore data,
use GPS Status & Toolbox app to enhance GPS fix.
That's it.
Enjoy,
djibe
THANKS to TWRP team, LineageOS team, tarkzim, ckpv5, alray, , Flyhalf205, icxj1, R1ghtC, gimmeitorilltell, All M8 contributors.
##################################################
A) Fastboot devices doesn't show any device connected
Install HTC USB drivers
Reboot PC
Open Windows Device Manager (Windows + R shortcut on keyboard > devmgmt.msc > hit Enter)
Search for phone at Other devices submenu > Device is named Android 1.0 or My_HTC
### If it is My_HTC > select it > right click > Uninstall. Disconnect phone. Reconnect phone. Now recognised as Android 1.0.
Select device Android 1.0 > right click > Update Driver
Search locally for driver > Show a list
Select ASUS Android Device.
Manufacturer: select Google, Inc. and set driver to Android Bootloader Interface
Confirm install.
B) Go back to stock from a custom ROM with a HTC One M8
- Either restore your TWRP backup with TWRP recovery
- Or restore a community TWRP backup with TWRP recovery (https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860 see posts 2 & 3)
### With S-ON and keep device Unlocked
To find suitable backup for device, boot phone in Bootloader mode (Power + Volume-)
Look at your hboot version (hboot 3.19.0000 is most frequent)
Launch a fastboot command:
Code:
fastboot getvar all
Make sure IMEI is a valid number.
Look at your CID and MID values. Try to find exact same TWRP backups for your phone.
### Flash only exact model versions.
Then wipe all partitions and restore the correct TWRP backup an angel made for you.
- If TWRP restore fails, start with these posts :
You will need a Rom Update Utility (RUU) for your exact model version.
This is compatible with S-ON, will need to relock your Bootloader (save your Unlock_code.bin +++) and need original recovery
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
https://forum.xda-developers.com/htc-one-m8/general/guide-restore-european-htc-one-m8-to-t3072235
C) No IMEI visible and no cellphone network detected with HTC One M8
Composing *#06# shows an empty IMEI dialog window.
or Settings > About phone > IMEI. IMEI: Unknown, IMEI SV: Unknown
Refer to B) tutorial to get back to stock.

Tuto updated for latest TWRP recovery

Please remove the 15 second adb. The OP of adb 15 second states in his post that it's outdated and should not be used.

Never_Sm1le said:
Please remove the 15 second adb. The OP of adb 15 second states in his post that it's outdated and should not be used.
Click to expand...
Click to collapse
Very nice !
Thx, pack and tutorial updated.

Can I use this guide for my m8wl?
And if it's possible, which of the two builds should I download?

Alexcxvtr said:
Can I use this guide for my m8wl?
And if it's possible, which of the two builds should I download?
Click to expand...
Click to collapse
Hi, look at this first: http://droider.eu/2014/09/20/htc-one-m8-models/
Then pick the correct ROM.

Thank you .I did it by following your guide.

murphylim said:
Thank you .I did it by following your guide.
Click to expand...
Click to collapse
Thanks, it is always encouraging to have support.
Still a good phone

Hi, I updated pack with latest Magisk root version and checked download links.

For Windows 10 users, use HTC drivers version v4.17.0.001 - Download them from here - Zippyshare.com - HTC Mobile Driver v4.17.0.001.exe
Everything else works just fine. @djibe89 thank you.

hymnz said:
For Windows 10 users, use HTC drivers version v4.17.0.001 - Download them from here - Zippyshare.com - HTC Mobile Driver v4.17.0.001.exe
Everything else works just fine. @djibe89 thank you.
Click to expand...
Click to collapse
Hi, thanks for feedback.
Drivers 4.2.0.001 didn't work ?

djibe89 said:
Hi, thanks for feedback.
Drivers 4.2.0.001 didn't work ?
Click to expand...
Click to collapse
No. Not on Windows 10.

djibe89 said:
Now type :
Code:
adb reboot bootloader
Phone restarts in Fastboot mode. Wait till phone screen is blank in fastboot mode.
Type :
Code:
fastboot devices
Command returns :
Code:
HT35**** fastboot
### You may have to fix drivers again (see fix at the end of tuto)
Click to expand...
Click to collapse
Hi,
I'm at the stage of trying to unlock the bootloader. The phone restarts in fastboot mode but when i type in fastboot devices nothing happens.
and then if i skip that and type get_identifier_token. the return is waiting for any devices. and nothing happens.
What have I missed?
Thanks
i've since been able to get past this stage. I used htc driver 4.17. I'm now stuck on the token. cmd prompt keeps saying cannot load the file no such file or directory. but i'm so sure i have the file in the right folder

juggled_balls said:
Hi,
I'm at the stage of trying to unlock the bootloader. The phone restarts in fastboot mode but when i type in fastboot devices nothing happens.
and then if i skip that and type get_identifier_token. the return is waiting for any devices. and nothing happens.
What have I missed?
Thanks
i've since been able to get past this stage. I used htc driver 4.17. I'm now stuck on the token. cmd prompt keeps saying cannot load the file no such file or directory. but i'm so sure i have the file in the right folder
Click to expand...
Click to collapse
Hi, when
Code:
fastboot devices
doesn't return anything, it means there is an USB driver problem.
You'll have to try to fix from Windows Device Manager.

hymnz said:
No. Not on Windows 10.
Click to expand...
Click to collapse
Hi, the Driver installer from my pack (HTCDriver_4.2.0.001) sends an error during install, but then drivers finally install.

djibe89 said:
Hi, when
Code:
fastboot devices
doesn't return anything, it means there is an USB driver problem.
You'll have to try to fix from Windows Device Manager.
Click to expand...
Click to collapse
Thanks for your work. I managed to plod my way through everything and get it working. Very happy the old phone can keep going on.

juggled_balls said:
Thanks for your work. I managed to plod my way through everything and get it working. Very happy the old phone can keep going on.
Click to expand...
Click to collapse
Awesome !
Enjoy

Hi, tutorial and pack updated for Android 11

thx for the guide!

seamonkey420 said:
thx for the guide!
Click to expand...
Click to collapse
Hi, glad you liked it !
Enjoy your phone