Database Info

sensation stuck on bootloop

i rooted my phone and followed the guide in
http://www.androidauthority.com/how-to-root-htc-sensation-21697/
which worked great and had my phone rooted with S-OFF and full control
then i went to this page and wanted to install a rom and chose
http://forum.xda-developers.com/showthread.php?t=1468683
which i downloaded, after trying to follow the instructions the firmware would install and gave installation aborted so i installed the rom anyways
now the phone boots into the rom but freezes before the loading the phone and restarts.
i am stuck in boot-loop and when trying to recover using the backup it still boot-loops
i think the boot files are corrupt, and i have also tried super-wipe, (super-wipe V2 would load)
even after this i tried installing the custom rom and the backup version and still not working
the firmware still does work and i have tried loading the backup 6 times now using as many different methods such as clearing cache..etc
i even found programs uses to 4EXT_Recovery_Touch_v1.0.0.4_RC3_flashing_tool
and ADB_Fastboot_Windows
but those wont work unless the phone is started and in htc sync/usb mode.
any help would be grateful, i am really getting stressed out for not being able to use my phone

1)You know how to boot into HBOOT, or the bootloader? Do just that.
2) Connect your phone to your computer. You must have all the ADB and SDK drivers installed.
3)Navigate to "Fastboot" using your phones Volume UP and DOWN keys until you reach fastboot. Select using the power button.
4) Go into cmd in Windows.
5)Type the following:
cd C:\Program Files\Android\android-sdk\platform-tools
6)Type the following:
adb getvar cid
7) Remember what the previous command just told you. It could be HTC_001 for example.
8)Thanks to this dev, go to this thread. Find this in the first post:
Firmware from 3.32.401.x & 3.32.401.10x RUU
9)See if your CID is listed. If it is not, DO NOT TRY FLASHING THIS. If it is, download the file and flash in HBOOT using the PG58IMG.zip method. Make sure it isn't called PG58IMG.zip.zip.
10) If it isn't listed, use STEP 4 in this post, then flash it.
RE-POST THIS!!! Save devs time to building ROMs and save hassle.

i have followed your steps to number 3, now it says "fastboot ac" on phone
with step 5 i found the folder in this directory
C:\Program Files (x86)\Android\android-sdk
after typing in the command after navigating there i get this
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Owner>cd C:\Program Files (x86)\Android\android-sdk\platform-tools
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb getvar cid
Android Debug Bridge version 1.0.29
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
and now im stuck as to where to find htc_001
sorry for sounding noobish as im new to this but can you please tell me what i have done wrong to where to go from here ??

Once in that directory type fastboot getvar cid
Then write down the CID that shows up.
If it doesn't match one in the list of compatible firmware then you'll have to super CID to 11111111.
Edited because I wasn't thinking.

You have to use fastboot, not adb
Sent from my HTC Sensation with Beats Audio using xda premium

ok i have tried that now it is saying "waiting for device"
the phone is still not being picked up by the computer either by htc sync or by the program through command prompt.
fastboot changes to fastboot ac, not sure if that means its just on charge only and not any other mode

Unplug the phone and pull the battery. Then boot the phone back into the initial recovery screen (vol down + power on)
Connect phone to computer. In a cmd prompt navigate to cd C:\Program Files\Android\android-sdk\platform-tools
Type adb devices (Should come back with serial number)
Type fastboot getvar cid
Hopefully that pulls the CID. Let us know.

i have tried this over several times , it still does not pick up the device.
any other ways to get this to work ??

Have you just installed the SDK? Open the SDK, and a pop-up should come up. Select Android USB drivers or something similar to it. Check it and install. Try again after this.
Sent from my Wildfire using Tapatalk 2 Beta-5

You also need to have your fast boot drivers in the directory that you cd to to issue your fastboot commands.
sent from HTC Pyramid using Tapatalk

usaff22 said:
Have you just installed the SDK? Open the SDK, and a pop-up should come up. Select Android USB drivers or something similar to it. Check it and install. Try again after this.
Sent from my Wildfire using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
stringer7 said:
You also need to have your fast boot drivers in the directory that you cd to to issue your fastboot commands.
sent from HTC Pyramid using Tapatalk
Click to expand...
Click to collapse
i have made sure that the usb drivers have been installed infact i uninstalled htc sync and android sdk and reinstalled them both and made sure the drivers are installed.
on there is doesnt say anything like android usb drivers but Google usb drivers is the closest, basically the default settings installed.
for the drivers htc sync has been installed it is also failing to detect my phone.
stringer7, i have made sure i am in the directory and it checks for devices, but it fails to find my htc sensation.
Ive had this phone for 2 months now of a 24 month contract.
now i just want to reformat it all and install the stock version over, and see if i can get my backup back as it has all my contacts and messages on it which i thought were on the sim.

wbb1 said:
i have made sure that the usb drivers have been installed infact i uninstalled htc sync and android sdk and reinstalled them both and made sure the drivers are installed.
on there is doesnt say anything like android usb drivers but Google usb drivers is the closest, basically the default settings installed.
for the drivers htc sync has been installed it is also failing to detect my phone.
stringer7, i have made sure i am in the directory and it checks for devices, but it fails to find my htc sensation.
Ive had this phone for 2 months now of a 24 month contract.
now i just want to reformat it all and install the stock version over, and see if i can get my backup back as it has all my contacts and messages on it which i thought were on the sim.
Click to expand...
Click to collapse
u mean that you boot into bootloader, u see written HBOOT on the screen, then u connect the usb cable coming from a computer on which both htc sync and ADK/SDK installed (not running, but installed) and HBOOT turns into FASTBOOT USB on the screen but u cant send fastboot commands?

dowanrac said:
u mean that you boot into bootloader, u see written HBOOT on the screen, then u connect the usb cable coming from a computer on which both htc sync and ADK/SDK installed (not running, but installed) and HBOOT turns into FASTBOOT USB on the screen but u cant send fastboot commands?
Click to expand...
Click to collapse
when i connect the phone to my computer i manually go to fastboot option using the power key then from there it will say fastboot ac
or if i connect after in fastboot it will change to "fastboot ac"
now im gonna try reinstall the whole setup on another machine or try dualboot with ubuntu and try the drivers through that,

wbb1 said:
when i connect the phone to my computer i manually go to fastboot option using the power key then from there it will say fastboot ac
or if i connect after in fastboot it will change to "fastboot ac"
now im gonna try reinstall the whole setup on another machine or try dualboot with ubuntu and try the drivers through that,
Click to expand...
Click to collapse
grab a photo of the screen - bootloader screen when u connect. lets see what u got there.
i think its only a communication problem with pc. message on screen should be fastboot USB. not fastboot AC. so it means u simply dont have the proper drivers. if u get a different computer, just install htc sync, reboot computer after that and make sure htc sync program aint running. then connect phone in bootloader. if it says fastboot usb, go to ADK step. if not... weird...

dowanrac said:
grab a photo of the screen - bootloader screen when u connect. lets see what u got there.
i think its only a communication problem with pc. message on screen should be fastboot USB. not fastboot AC. so it means u simply dont have the proper drivers. if u get a different computer, just install htc sync, reboot computer after that and make sure htc sync program aint running. then connect phone in bootloader. if it says fastboot usb, go to ADK step. if not... weird...
Click to expand...
Click to collapse
heres the photo of the bootloader that shows when connecting to pc
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i also tried this on another computer and it still shows the same message. i would try on linux ubuntu but cant seem to find htc sync for it.
any more ideas ??

Try Google USB Drivers. Install that.
And please DO try and make your pictures a bit smaller

ok i found out my usb cable was the reason and now after getting a new one i get "fastboot usb"
after typing the code on first page i get this, the device is not listed but it shows htc_001 with getvar cid
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar cid
cid: HTC__001
finished. total time: 0.002s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
i am now going to try supercid to see if i can move forward in finally getting my phone working.
EDIT:
it is working now, after 3 long days of no phone,
after installing the rom i used my backup to "advanced backup" to get my data back which gave my old apps and messages along with contacts

Not able to download firmware from link provided.
usaff22 said:
1)You know how to boot into HBOOT, or the bootloader? Do just that.
2) Connect your phone to your computer. You must have all the ADB and SDK drivers installed.
3)Navigate to "Fastboot" using your phones Volume UP and DOWN keys until you reach fastboot. Select using the power button.
4) Go into cmd in Windows.
5)Type the following:
cd C:\Program Files\Android\android-sdk\platform-tools
6)Type the following:
adb getvar cid
7) Remember what the previous command just told you. It could be HTC_001 for example.
8)Thanks to this dev, go to this thread. Find this in the first post:
Firmware from 3.32.401.x & 3.32.401.10x RUU
9)See if your CID is listed. If it is not, DO NOT TRY FLASHING THIS. If it is, download the file and flash in HBOOT using the PG58IMG.zip method. Make sure it isn't called PG58IMG.zip.zip.
10) If it isn't listed, use STEP 4 in this post, then flash it.
RE-POST THIS!!! Save devs time to building ROMs and save hassle.
Click to expand...
Click to collapse
Hello,
Im in the same situation and I know how to boot load the firmware. My problem is that when I go to the link provided to download Firmware 3.32.401.x & 3.32.401.10x RUU, it sends me to another website that is down. is there somewhere ales I can find this file? I have been trying for days and I always get the following message.
Not Found
The requested URL /db_mirror/ROMs/HTC Sensation/Firmware/3.32.401.x/PG58IMG.zip was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2 Server at xda3.androidrevolution.nl Port 80

[how to] remove your "tampered" banner

*this thread is for E8. it will NOT work on m7(or anything older). search your device general forum for a specific thread
if you have recently s-off'ed using an exploit that did not remove your tampered banner from the bootloader screen,then this thread is for you.
*note: if you are on hboot 3.19.0.0000 this thread will change software status: modified banner to: software status: official. to my knowledge,this banner is not completely removable (more info)
you do NOT need to downgrade your hboot. this simple adb command works without any scary hboot downgrades.
*you must be s off.
*you must have superuser installed
read this:
this will not work if your s on
the usual disclaimers:
i have tested this my my m8_ul t mobile variant,but use this info at your own risk. 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
-andybones for testing it on m7_wlv
-WorldIRC and brar.arsh for testing on m8
-ian.anindya and a couple others have provided dumps. let me know and ill add you to the credits. if someone wants to provide screen shots,i can add those as well.
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/mmcblk0p6 bs=1 seek=5314564
(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 tamered is gone
your cmd window should look something(but not exactly) like this(red= my inputs,blue=additional comments):
Code:
c:\miniadb_m8>[COLOR="Red"]adb shell[/COLOR]
[email protected]_m8:/ $ su
su
[email protected]_m8:/ # [COLOR="red"]echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564[/COLOR]
ock/mmcblk0p6 bs=1 seek=5314564 <
1+0 records in [COLOR="Blue"][COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m8>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.022s
c:\miniadb_m8>
other useful threads:
lock/unlock without htcdev:
change mid without eng hboot: http://forum.xda-developers.com/one-e8/general/how-to-change-mid-eng-bootloader-t3019148
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 p6.
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 p6 by:
adb shell
su (if needed to get a #)
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6
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

Working like a Bomb

Many thanks. Works like a charm.

thank you sir, it works on M8Sd MEC_DWGL :good:

Works on the M8sd Indian version HBOOT 3.19.0.0000
Sent from my HTC One_E8 dual sim

how can we remove tampered banner when device is s-on please help me

eminteoman said:
how can we remove tampered banner when device is s-on please help me
Click to expand...
Click to collapse
The only way is to run a signed ruu that meets all the phone's s on criteria

scotty1223 said:
The only way is to run a signed ruu that meets all the phone's s on criteria
Click to expand...
Click to collapse
Can you explain a little further? I really couldn't understand

eminteoman said:
Can you explain a little further? I really couldn't understand
Click to expand...
Click to collapse
Easy way: s-on can't get rid of the text
Send via my CM 12 Gtab3

wildanw2 said:
thank you sir, it works on M8Sd MEC_DWGL :good:
Click to expand...
Click to collapse
Does it works on m8sx??

HOW TO: Go back to stock, unroot, Lock bootloader, go S-ON(non-Tampered.)

This tutorial will hopefully guide you through the process of Returning Your HTC ONE M8 (VERIZON) back to Stock Lollipop, Unrooted, S-ON, “Locked” bootloader.
I assume this would work for other variants but I offer no guarantees. Make sure you get the RUU or FUU for your specific carrier.
Prerequisites:
Backup all your data before proceeding with firmware installation.
HTC One M8 with S-OFF, I used sunshine originally, and it’s still available at theroot.ninja.
Download and install HTC USB Drivers on your computer. If you have installed HTC Sync, uninstall it temporarily to avoid any problem.
You must have ADB (Android Debug Bridge) installed and setup on your computer: Refer to this or this guide to setup ADB, or use Minimal ADB and Fastboot
Enable USB Debugging on your HTC One M8. (Settings > About > Software Info > More > tap Build # several times until you see “You are now a developer” > back to Settings page > Developer Options > Select On > Check on Allow USB Debugging)
Go to Settings> Power and turn off Fastboot option.
Downloads:
Download the Verizon FUU by Dotat Here [/URL]:
[*]If your phone isn’t the Verizon variant DO NOT flash this
(https://www.androidfilehost.com/?fid=95916177934538714)
Run the FUU utility, this will give you a Stock Lollipop Rom and Stock Recovery.
Connect your phone to PC using the USB cable provided by the OEM.
Extract DOTTAT_VZWM8_S_OFF_5.0.1_FUU.zip file and open the folder.
Now double click ARUwizard.exe.
When the FUU launches, follow the on-screen prompts until your One M8 reboots. Please note that your phone might take 5-8 minutes to reboot after firmware installation.
Congrats, you have successfully restored your Verizon HTC One M8 to stock Lollipop pre-rooted ROM!
Relock Bootloader –
Now you’re ready –
Navigate to the directory where you have setup the Android SDK. Open the folder the platform-tools directory where ADB and Fastboot files are found.
( If you’re using Minimal ADB the rest of this step isn’t necessary just open it) Press the Shift key and then do a right-click on the mouse at an empty space in the platform-tools folder. Select Open command window here option to launch cmd prompt.
Connect your phone to the computer using USB cable.
Double check to make sure the phone is recognized by adb by typing in the command:
adb devices
If you see the serial number of the device and says attached, you are good to go.
Type or copy/paste the commands on the cmd line –
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
You should see the bootloader as LOCKED. To check, reboot your M8 into the Bootloader Mode by using the command:
adb reboot bootloader
Unroot/ Uninstall SuperSu –
I put the unroot here unlike other tutorials because this is the last step that you could mess up before going S-ON. After you go S-ON you have to go back w/ Sunshine. Whereas if you trip the tampered flag or something you can just re-run the FUU/RUU.
Go to SuperSu app > Settings > Full unroot option > Reboot
If you are having trouble getting SuperSu to stay off use the Universal Unroot App to remove root. This is the app I had to use.
Get S-On –
Adb reboot bootloader
From Fastboot:
fastboot oem writesecureflag 3
Reboot bootloader and verify S-On
That’s it you’re done!
I compiled this Tutorial from other tutorials, so if it looks a little janky, that’s why.
Sources
DroidViews.com (for instructions on FUU)
Banetech.com (for the rest)
I had to adjust because neither was complete for what I needed.

Unlocking Bootloader [Incomplete]

Note: It would be great to keep this page open while following through on your PC instead of your phone as you'll be rebooting and resetting your phone by following this procedure.
Click to expand...
Click to collapse
Prerequisites:
ADB (Android Debugging Bridge) tools for your OS (Windows/Linux/Mac)
Windows
Mac
Linux
Custom Recovery Image (TWRP or some other that you prefer):
(Official TWRP web hosted version) Nokia 6.1 (2018)
Download from American Mirrors
Download from EU Mirrors
USB Cable to Connect the phone to the computer
The Phone: Nokia 6.1 (2018) (preferably Fully Charged)
The device drivers (for Windows and Mac)
A good and active Internet Connection
An active Email address and client to quickly view it.
In this tutorial I'll be referring to Linux terminal, Mac Terminal & Windows Command prompt/Powershell simply as terminal.
Click to expand...
Click to collapse
Installing adb and fastboot
Google hosts zips including only adb and fastboot. You can set these up for use with the instructions below.
On Windows
Download the (Windows.zip) from Google.
Extract it somewhere - for example, %USERPROFILE%\adb-fastboot
• On Windows 7/8:
1. From the desktop, right-click My Computer and select Properties
2. In the System Properties window, click on the Advanced tab
3. In the Advanced section, click the Environment Variables button
4. In the Environment Variables window, highlight the Path variable in the Systems Variable section and click the Edit button
5. Append ";%USERPROFILE%\adb-fastboot\platform-tools" to the end of the existing Path definition (the semi-colon separates each path entry)
• On Windows 10:
1. Open the Start menu, and type “advanced system settings”
2. Select “View advanced system settings”
3. Click on the Advanced tab
4. Open the “Environment Variables” window
5. Select the Path variable under “System Variables” and click the “Edit” button
6. Click the “Edit Text” button
7. Append ";%USERPROFILE%\adb-fastboot\platform-tools" to the end of the existing Path definition (the semi-colon separates each path entry)
• Install the device drivers linked in prerequisites (or from Nokia support site), and reboot.
On MacOS
Download the MacOS (Darwin.zip) from Google.
Extract it somewhere - for example, ~/adb-fastboot.
Add the following to ~/.bash_profile:
Code:
if [ -d "$HOME/adb-fastboot/platform-tools" ] ; then
export PATH="$HOME/adb-fastboot/platform-tools:$PATH"
fi
Log out and back in.
On Linux
Download the (Linux.zip) from Google.
Extract it somewhere - for example, ~/adb-fastboot.
Add the following to ~/.profile:
Code:
if [ -d "$HOME/adb-fastboot/platform-tools" ] ; then
export PATH="$HOME/adb-fastboot/platform-tools:$PATH"
fi
Log out and back in.
You may also need to set up udev rules: see (this repository) for more info.
Setting up adb
To use adb with your device, you’ll need to enable developer options and USB debugging:
1. Open Settings, and select “About”.
2. Tap on “Build number” seven times.
3. Go back, and select “Developer options”.
4. Scroll down, and check the “Android debugging” entry under “Debugging”.
5. Plug your device into your computer.
6. On the computer, open up a terminal/command prompt and type adb devices.
7. A dialog should show on your device, asking you to allow usb debugging. Check “always allow”, and choose “OK”.
Congratulations! adb is now ready to use with your device.
Unlocking the bootloader
Note: The steps below only need to be run once per device.
Code:
Warning: Unlocking the bootloader will erase all data on your device! Before
proceeding, ensure the data you would like to retain is backed up to your PC and/or
your Google account, or equivalent.
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging & OEM unlocking on your device under Settings->Developer Options. Incase you don't see Developer Options, then you need to unlock it by tapping Build Number 7 times in Settings->About Phone.
3. Get the current status of your bootloader:
Open a terminal on the PC and boot the device to fastboot mode by typing:
Code:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC finds it by typing:
Code:
fastboot devices
If you see "no permissions fastboot" or "<waiting for device>", try running
Code:
fastboot
as root/Administrator.
From the same terminal, type the following command to get the bootloader status:
Code:
fastboot oem device-info
4. Follow the instructions at (Nokia Support) to unlock your bootloader, you will need to register at this site with a working/active email to proceed. They'll verify your device using an app to issue a validation code.
Note: If your device is not supported by the Nokia Bootloader Unlock
website, you will need to use an alternative bootloader unlock method.
Installing a custom recovery using fastboot
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging & OEM unlocking on your device under Settings->Developer Options. In case you don't see Developer Options, then you need to unlock it by tapping Build Number 7 times in Settings->About Phone. This needs to be done again due to resetting of your phone.
3. Download recovery - visit twrp.me to obtain the latest version of Team Win
Recovery Project for your device. Nokia 6.1 (2018) does have an official TWRP recovery that you can find here: Nokia 6.1 (2018) [PL2] respectively.
4. Connect your device to your PC via USB.
5. Open a terminal on the PC and boot the device to fastboot mode by typing:
Code:
adb reboot bootloader
6. Once the device is in fastboot mode, verify your PC finds it by typing:
Code:
fastboot devices
If you see "no permissions fastboot" or "<waiting for device>" , try running
Code:
fastboot
as root/Administrator.
7. Boot into TWRP temporarily:
Code:
fastboot boot twrp.img
8. Use adb to push the zip onto your device:
Code:
adb push twrp.zip /
9. Go to `Install` option on the TWRP menu and browse to the zip (Scrolling to the bottom should have the zip) and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
If you accidentally flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Click to expand...
Click to collapse
This command assumes the recovery image is present in your current working directory (Check using `DIR` on command prompt or `ls` command on terminal)
If it isn't you can change your current directory to the directory containing the recovery image or copy/move the recovery image to your current working directory.
10. Now reboot into recovery to verify the installation:
That's all folks. You may now root your phone, or even flash a custom ROM. I suggest getting openGapps for the custom ROM if you wish to use Google play services on the custom ROM.
Popular adb commands
Code:
adb shell
Launches a shell on the device accessed through the terminal on your computer.
Code:
adb push <local> <remote>
Pushes the file <local> to <remote>
Code:
adb pull <remote> [<local>]
Pulls the file <remote> to <local>. If <local> isn’t specified, it will pull to the current folder.
Code:
adb logcat
Allows you to view the device log in real-time. You can use adb logcat -b radio to view radio logs, and adb logcat -C to view logs in colour
Code:
adb install <file>
Installs the given .apk file to your device
<local> refers to location on your computer (like c:\\Users\%USERPROFILE%\adb-fastboot on windows or ~/adb-fastboot on unix based OS), while <remote> refers to location on your android device (like "/sdcard/", without quotes)

Reserved

What do you do if oem unlocking in developer is greyed out? TA-1045

@toxicmender The official bootloader unlock was only released to the Nokia 8. So, what is the point posting it here?
Or have they silently added the 6.1?

singhnsk said:
@toxicmender The official bootloader unlock was only released to the Nokia 8. So, what is the point posting it here?
Or have they silently added the 6.1?
Click to expand...
Click to collapse
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Code:
fastboot flash signature signature_file.bin
Also it has follow up instructions for flashing TWRP for anyone who has successfully unlocked their bootloader, since flashing TWRP is a bit different from most other phones

toxicmender said:
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Code:
fastboot flash signature signature_file.bin
Also it has follow up instructions for flashing TWRP for anyone who has successfully unlocked their bootloader, since flashing TWRP is a bit different from most other phones
Click to expand...
Click to collapse
Why would you make start this thread then? It is completely pointless and misleading.
It is like making a post saying that there are flying cars and marking it [Incomplete]. It is just ****ing stupid.
I hope you drop your 6.1 and break it so you make **** posts in other phone forums instead of this one.

cmaxwe said:
.
I hope you drop your 6.1 and break it so you make **** posts in other phone forums instead of this one.
Click to expand...
Click to collapse
Hey now, there is really no need for that level of hostility. He knew they were doing unlocks for at least one Nokia phone, and me may not have known that they didn't have it for the 6.1.
Please don't talk to peope like that if they make a simple mistake when trying to provide info and help out the community. We're all human.

toxicmender said:
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Code:
fastboot flash signature signature_file.bin
Also it has follow up instructions for flashing TWRP for anyone who has successfully unlocked their bootloader, since flashing TWRP is a bit different from most other phones
Click to expand...
Click to collapse
Honestly if there was a good amount of roms available for this phone I would gladly pay the $5 to unlock bootloader, although that method leaves me with questions. does that method survive ota? Does it actually work? Can it relock and unlock without paying again?
Is there really not that many people on here willing to try unlocking and flashing the many gsi roms available?

cmaxwe said:
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Why would you make start this thread then? It is completely pointless and misleading.
It is like making a post saying that there are flying cars and marking it [Incomplete]. It is just ****ing stupid.
I hope you drop your 6.1 and break it so you make **** posts in other phone forums instead of this one.
Click to expand...
Click to collapse
It's not like there isn't a way, there is, just not a transparent method. Somehow those (refer to link in reply) are able to generate and send the signature file allowing you to unlock the phone, how it works or if your bootloader be locked again after updating is unknown to me ATM

mymeatb18 said:
Unfortunately no, they haven't, removed the [incomplete] tag prematurely after reading it somewhere.
Currently only known way to unlock Nokia 6.1 seems to be to flash signature file.bin from these guys for fee.
at Step 4:
Honestly if there was a good amount of roms available for this phone I would gladly pay the $5 to unlock bootloader, although that method leaves me with questions. does that method survive ota? Does it actually work? Can it relock and unlock without paying again?
Is there really not that many people on here willing to try unlocking and flashing the many gsi roms available?
Click to expand...
Click to collapse
Well the ROM development begins after an Official TWRP recovery, so the chances are there might be some. I'm not clear on the the OTA being able to relock the bootloader either since I was running Pie update when I got to know about it.

thread closed as per OP request

Op7pro not responding to fastboot commands

Hey, im having trouble finding working ways to root my op7pro GM1913 (OOS 11.0.4.1 GM21BA)
Ive been trying this https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/
Currently trying to unlock bootloader. (Step 2)
I can connect via adb but when i go to bootloader/fastboot i lose connection to the phone.
Ive tried regular adb command tools and "TOOL ALL IN ONE" When the phone is on it responds to adb commands but when i need fastboot commands its not working and i can see the device id dissapear from the all in one tool.
I have tried multiple usb ports (2.0 and 3.0) and multiple usb C cords (Op oem + Samsung) Tried removing Windows signature verification and installing oneplus usb drivers, but it gets stuck at "Execute the commands..." (99% or so) When i try again it finds some installation files. When im in bootloader, Windows device manager still shows a generic android phone. Oem unlocking and usb debugging is on, also set default usb configuration to file transfer. No help.
I want to keep Oxygen os, but i want to be rooted and have magisk, preferably TWRP too but im open to other ways.
Windows 10 20H2 if that matters. (Latest update for me)
Oneplus 7pro GM1913 (Eu nordic)
Oxygen os 11.0.4.1 GM21BA

Download a Linux distro and install adb and fastboot like this: https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/
Just download adb and fastboot tools package from Google, extract it,open command prompt inside where you extract it and enter these in terminal:
sudo install adb dmtracedump e2fsdroid etc1tool fastboot hprof-conv make_f2fs mke2fs mke2fs.conf sload_f2fs sqlite3 /usr/local/bin
sudo mkdir -p /usr/local/lib64
sudo install lib64/libc++.so /usr/local/lib64
Then adb --version (enter) fastboot --version (enter) like Nathan says in guide. Super easy and I guarantee you if you go this route you won't have any hiccups. Sounds like stupid windblows driver issues or outdated adb/fastboot tools. One of the two. Are you flipping on dev options and check marking little box that pops up on your phone to allow it to communicate with PC? A simple : adb devices (enter) should make it appear on phone screen. You don't even have to install Linux, you can boot it off a live USB. Takes about one minute to make one. If you make one you can boot the live USB , download adb and fastboot, and install as Nathan's guide says then reboot when you are done and your back in windblows. IDK why anyone wouldn't want Linux installed though. Best decision I ever made was switching from windows to Linux about 9 years ago. It really makes anything you do to your devices MUCH easier to do!! This may sound stupid but have you rebooted your PC? Because you will definitely need to , probably more than once on windblows to get it to work.

Thank you for the reply. No stupid questions, yes i tried rebooting pc/phone. Ill try your way and report in a couple days.

Solution is simple. From Android 11 on, OnePlus (and Android phones in general) uses the universal drivers, you just need to install them in Windows in order to use fastboot commands. See my answer in this post.

There are a few things you can try if your OP7 Pro is not responding to fastboot commands:
1. Make sure you have the latest drivers installed for your phone.
2. Try using a different USB cable.
3. If you're using Windows, try running the fastboot commands from a command prompt with administrator privileges.
4. Try booting your phone into recovery mode and running the fastboot commands.