[how to] remove your "tampered" banner - HTC Rezound

now that we know rumrunner works on this device(some pointers in this thread),and the process can leave you with a tampered banner in your bootloader,i thot there might be a demand for this. this will legitimately change the flag that causes hboot to display the tampered banner,without the inconvenience of having to run an RUU.
this is NOT a patched or hex edited hboot. this is legintimately restoreing the tampered flag to its "untampered" setting
*you must be s off.
*you must have superuser installed(see this thread if you need help installing superuser)
read this:
this will not work if your s on
the usual disclaimers:
i have tested this my my rezound,but use this info at your own risk. if it melts your phone into a little pile of plastic goo,its not my fault.
credits
-beaups for schooling me on echo command protocol
request that you do not repack this into any one clicks or tools without permission. i spent a great deal of time comparing before and after hex edits to find this flags location
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
-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/mmcblk0p7 bs=1 seek=4391940
(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
(yes the pics are of m7. ill try and get some rezound pics up later)

Worked like a charm! Thank you for this. I'm out of thanks for today but I will catch you tomorrow

So... What about on JuopunutBear HBoot? Do I need to flash the stock one first?
Sent from my Nexus 4 using Tapatalk

acejavelin said:
So... What about on JuopunutBear HBoot? Do I need to flash the stock one first?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
The jpbear hboot is ignoring the flag,so the banner isn't displayed.
You will need to be on a stock hboot to witness the banner disappear,but it actually doesn't matter what you're running to reset it.
Sent from my HTC6435LVW using Tapatalk

scotty1223 said:
The jpbear hboot is ignoring the flag,so the banner isn't displayed.
You will need to be on a stock hboot to witness the banner disappear,but it actually doesn't matter what you're running to reset it.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
So this might be a silly question, is there any real reason to do this? It won't make any functional difference to my knowledge.
So other than making the banner go away, is there any beneficial use to doing this?
Sent from my Nexus 4 using Tapatalk

You would not want to send in the phone for warranty repair with the tampered banner,but running a signed ruu will make it go away as well.
Other than that, there is no real reason. its completely cosmetic,it doesn't affect any functionality. For some folks,its presence really gets under their skin. Personally,I kind of like the tempered banner.
you actually can turn it back on with a similar command
Sent from my HTC PG09410 using Tapatalk 2

This seems pretty cool!
My only comment is that one need not do all of the fastboot-related driver business, because your command is done using only adb. (Yes, sadly, this is relevant for post-Win 7 versions of Windows, which often can see devices via adb but not fastboot...)
cheers,
john

jrredho said:
This seems pretty cool!
My only comment is that one need not do all of the fastboot-related driver business, because your command is done using only adb. (Yes, sadly, this is relevant for post-Win 7 versions of Windows, which often can see devices via adb but not fastboot...)
cheers,
john
Click to expand...
Click to collapse
I've purposely stayed with windows 7,since phone stuff is 95% of what i use my pc for. you are correct,you don't need fastboot at all for this,after verifying the banner is gone,one can simply manually reboot from the bootloader menu.
Sent from my HTC PG09410 using Tapatalk 2

So removing the tampered flag is only helpful if you need to turn in your phone for warranty reasons..... However if it still says S-off aren't they still going to know it's been tampered with?

Worked great!!!! I know there's not much reason to do this but fun to tinker. Thanks for the step by step instructions. Verified tampered flag removed. See before and after pictures.
Sent from my ADR6425LVW using xda app-developers app

Uncleheff said:
So removing the tampered flag is only helpful if you need to turn in your phone for warranty reasons..... However if it still says S-off aren't they still going to know it's been tampered with?
Click to expand...
Click to collapse
Pre-release phones legitmately come s off,so its existance does not imply an otherwise stock,locked and non-tampered phone has been messed with.
Plus,you can turn s on if you want to.

Works like a charm. Thanks!

Related

help am I an idiot part 2

I spent the whole of yesterday trying to add MoDaCo custom rom. from this post http://forum.xda-developers.com/showthread.php?t=552591 The first of my problems was that I couldn't get the right driver which now seems to be fixed now comes up as - ADB Interface -HTC Bootloader.
So this now means that when i go to fastboot I can load cyanogenMod (system recovery) by typing fastboot boot cm-hero-recovery.img
However none of these commands below in the CMD work. All i get is error: device not found
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
Any ideas please
robboy said:
I spent the whole of yesterday trying to add MoDaCo custom rom. from this post http://forum.xda-developers.com/showthread.php?t=552591 The first of my problems was that I couldn't get the right driver which now seems to be fixed now comes up as - ADB Interface -HTC Bootloader.
So this now means that when i go to fastboot I can load cyanogenMod (system recovery) by typing fastboot boot cm-hero-recovery.img
However none of these commands below in the CMD work. All i get is error: device not found
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
Any ideas please
Click to expand...
Click to collapse
Still sounds like a driver issue.. have you installed HTC + the SDK?
Restert ur handset into bootloader, hold power + back, then plugin the USB cable.. "FASTBOOT" (,In the red square) shoud change to FASTBOOT USB..
Skip the "adb shell reboot bootloader" and go straight to the next line and boot the recovery image via fastboot
should be plain sailing from there
It does change to fastboot usb on red. The only thing I can think of is do you have to install the sdk as I couldn't see a setup app. I just have all the files on the c dive. Will try skipping the first step when I get home
you dont install the sdk, just unzip it
thats right just the unzip, sorry, the drivers come with the SDK, if you still have no sucsess, do a Controll pannel > system >device manager then scan for device changes, if it finds the device select to install drivers and point it to the SDK folder
jackdaniels_lee said:
Still sounds like a driver issue.. have you installed HTC + the SDK?
Restert ur handset into bootloader, hold power + back, then plugin the USB cable.. "FASTBOOT" (,In the red square) shoud change to FASTBOOT USB..
Skip the "adb shell reboot bootloader" and go straight to the next line and boot the recovery image via fastboot
should be plain sailing from there
Click to expand...
Click to collapse
Grrrr still no joy. Just device not found. Im deleting all files that I have downloaded for drivers sdk etc and try and start again from scratch.
Do I need to partion my SD card before I do this as i have been having probs with that as well.
jackdaniels_lee said:
thats right just the unzip, sorry, the drivers come with the SDK, if you still have no sucsess, do a Controll pannel > system >device manager then scan for device changes, if it finds the device select to install drivers and point it to the SDK folder
Click to expand...
Click to collapse
Done that as well. If My device runs fastboot this should mean the drivers are correct.
robboy said:
Done that as well. If My device runs fastboot this should mean the drivers are correct.
Click to expand...
Click to collapse
yes if u succeed to enter fastboot, it means it had recognised the phone? are u using windows 7 by the way? cause u have to download the precise drivers for the OS u r using whether x64, win 7 ....
I seem to remember having problems with this until I enabled the USB debugging mode in the options somewhere.
As for drivers, I'm running Windows 7 x64 and the x64 Vista drivers did the job fine.

[Q] Adb commands to install TWRP

So I unlocked my Prime on .21 and I've been trying to get a recovery on it with no luck. Obviously, I can't use Rom or Goo Manager as it's not rooted. I can't flash a zip file because I don't have a recovery. I've tried installing it in fastboot with no luck. From what I've read fastboot is not an operable command on the Prime so I tried installing the universal naked driver and using the provided commands with it. According to the directions I have to unistall previous drivers....I have a LOT. If that's the case I might as well try on a fresh PC as I have Moto, HP, HTC, Samsung, etc drivers installed.
Back on topic - TWRP's page ( http://teamw.in/project/twrp2/93) provides commands for "ADB / Terminal" to install their recovery but the commands provided are clearly for terminal emulator which I'd have to be rooted to use. So how do these commands convert to ADB?
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Any help is much appreciated! I really don't want to downgrade to root and install recovery. If I can't get fastboot or adb to work, I'll keep that as plan C.
Sent from my DROID RAZR using Tapatalk
Use fastboot it's easier. http://transformerprimeroot.com/tra...orkmod-recovery-5-8-2-0-on-transformer-prime/ and obviesly replace cwm with twrp.
Sent from my Transformer Prime TF201 using XDA Premium App
Makrilli said:
Use fastboot it's easier. http://transformerprimeroot.com/tra...orkmod-recovery-5-8-2-0-on-transformer-prime/ and obviesly replace cwm with twrp.
Sent from my Transformer Prime TF201 using XDA Premium App
Click to expand...
Click to collapse
I cannot get fastboot commands to work on my Prime. Do you have the Universal Naked Drivers installed and have you used this method?
Sent from my DROID RAZR using Tapatalk
I used this one and I didn't have to install any drivers, worked out of the box. What do you mean about you couldn't get fastboot to work. Did you also write -i 0x0B05 between fastboot and flash
?
Sent from my sgs2 running cm9
I probably should post this as a seperate guide, here :
-----
* Install ADB and Fastboot onto your system, as well as the universal USB naked driver which you can find on this forum.
* Search for DotTech install ADB and Fastboot - follow this guide, it's probably the easiest way to get a working fastboot and ADB environment up and running.
* Enable USB debugging on the tablet under developer options.
* Set up the universal driver, you'll need to reboot your TF201 and hold the POWER and VOLUME DOWN buttons until you see some text in the top corner. Do NOT press volume up to go into Recovery Image mode or you'll just walk into a dead end.
* Shortly after you'll see three icons, press volume down ONCE and then volume UP once, the USB icon in the middle should be highlighted and you should see text saying "Entering Fastboot Protocol" or similar.
* Plug the USB cable into the tab and the PC, test whether you have a working fastboot install by typing fastboot -i 0x0b05 reboot, if your tablet reboots without you touching it, then you've got working fastboot access. Remove the cable, reboot to fastboot mode as described above.
* Meantime, download openrecovery-twrp-2.1.3-tf201.blob from the team win site, and stuff it in the same directory that you set up Fastboot/ADB, rename it to twrp.blob. Plug your tablet back in and then issue the command fastboot -i 0x0b05 flash recovery twrp.blob , if this goes to plan you'll see a couple of lines of text on the command window which will tell you that it's been successfully flashed in. YOU STILL DO NOT HAVE ROOT THOUGH, SO NO SILLY STUFF
* Finally, download the ROM of your choice, place it in the base /sdcard directory, then reboot the tab and hold POWER and VOLUME DOWN, when you see the text, this time hit VOLUME UP, and you'll be sent into the team win recovery suite, at this point you can wipe and flash the newly prepared ROM as per normal.
* For the first occasion I -strongly- recommend you use Virtuous Prime-S as you can generate a solid backup environment out of it, as well as the fact it's not too departed from Stock, so it's a good way to break yourself in.
----
Hope this helps.
Hobbesian said:
I probably should post this as a seperate guide, here :
-----
* Install ADB and Fastboot onto your system, as well as the universal USB naked driver which you can find on this forum.
* Search for DotTech install ADB and Fastboot - follow this guide, it's probably the easiest way to get a working fastboot and ADB environment up and running.
* Enable USB debugging on the tablet under developer options.
* Set up the universal driver, you'll need to reboot your TF201 and hold the POWER and VOLUME DOWN buttons until you see some text in the top corner. Do NOT press volume up to go into Recovery Image mode or you'll just walk into a dead end.
* Shortly after you'll see three icons, press volume down ONCE and then volume UP once, the USB icon in the middle should be highlighted and you should see text saying "Entering Fastboot Protocol" or similar.
* Plug the USB cable into the tab and the PC, test whether you have a working fastboot install by typing fastboot -i 0x0b05 reboot, if your tablet reboots without you touching it, then you've got working fastboot access. Remove the cable, reboot to fastboot mode as described above.
* Meantime, download openrecovery-twrp-2.1.3-tf201.blob from the team win site, and stuff it in the same directory that you set up Fastboot/ADB, rename it to twrp.blob. Plug your tablet back in and then issue the command fastboot -i 0x0b05 flash recovery twrp.blob , if this goes to plan you'll see a couple of lines of text on the command window which will tell you that it's been successfully flashed in. YOU STILL DO NOT HAVE ROOT THOUGH, SO NO SILLY STUFF
* Finally, download the ROM of your choice, place it in the base /sdcard directory, then reboot the tab and hold POWER and VOLUME DOWN, when you see the text, this time hit VOLUME UP, and you'll be sent into the team win recovery suite, at this point you can wipe and flash the newly prepared ROM as per normal.
* For the first occasion I -strongly- recommend you use Virtuous Prime-S as you can generate a solid backup environment out of it, as well as the fact it's not too departed from Stock, so it's a good way to break yourself in.
----
Hope this helps.
Click to expand...
Click to collapse
Thanks for the tutorial. I'm fairly familiar with adb and fastboot. My problem lies in the fastboot drivers. I was not able to install the Universal Naked Drivers. If I tried to install them over the existing drivers it failed. If I deleted the existing drivers, I was not able locate the device to install the new drivers. I would either reboot the computer OR unplug and plug the device in but each time the old drivers would auto install. Again, thanks for your input and I'll give this a go when I have some more time.
Sent from my DROID RAZR using Tapatalk
I had a similar issue getting the USB drivers in the first time. The best bet is to uninstall, unplug and then re-plug the tab in fastboot and then intercept the little window doohickey that comes up when it says it's dealing with an unknown device and tell it specifically not to go fishing on the web, then point it at the driver folder.
Hobbesian said:
I had a similar issue getting the USB drivers in the first time. The best bet is to uninstall, unplug and then re-plug the tab in fastboot and then intercept the little window doohickey that comes up when it says it's dealing with an unknown device and tell it specifically not to go fishing on the web, then point it at the driver folder.
Click to expand...
Click to collapse
I didn't have an issues with the adb drivers. I don't why fastboot is being such a pain.
Sent from my DROID RAZR using Tapatalk
joshw0000 said:
I didn't have an issues with the adb drivers. I don't why fastboot is being such a pain.
Sent from my DROID RAZR using Tapatalk
Click to expand...
Click to collapse
All the problems you see is with people that is using Windows.
Sent from my i9250
Hobbesian said:
I had a similar issue getting the USB drivers in the first time. The best bet is to uninstall, unplug and then re-plug the tab in fastboot and then intercept the little window doohickey that comes up when it says it's dealing with an unknown device and tell it specifically not to go fishing on the web, then point it at the driver folder.
Click to expand...
Click to collapse
Just wanted to shoot a quick thanks. I finally found time to tinker with my Prime and turns out I had the drivers properly installed but was booting to recovery not fastboot, hence fastboot device wasn't found. When booted properly, it flashed the first try. I'm now TWRP recovered and Gummy rom'ed. Its amazing how one can overlook a simple step and until someone plainly states it, they never even question it.
Sent from my Transformer Prime using Tapatalk

My method for S-Off on a 64bit OS (lengthy sorry).

This is the method I used to S-Off several devices (8 in total) on Windows 7 64 bit.
Remember, Team Unlimited does not recommend that you use any OS that is not supported as the drivers can cause some issues.
I have included a method that will test whether your drivers in your current setup will perform in a way that reduces the chance of all hell breaking loose.
Before starting, make sure you have downloaded and installed the HTC drivers for your phone and have Adb downloaded. A great place to get this is from “Team fireballas FakeCid AUTOMATIC bootloader unlock” thread.
We will need this file for a later process as well. (File Download)
Once downloaded, unzip it to C:\Root.
Verifying that your drivers are working correctly. (Typed commands are in red)​
1) Attach your phone to you computer with the supplied USB cable.
2) Enable USB Debugging (Settings>Developer Options>USB Debugging)
3) Open a command prompt and navigate to the location you extracted the adb files to by typing: cd\
Then type: cd c:\Root\stuff
Your Prompt should read:
c:\Root\stuff>
4) Now type adb devices
You should see the following output in the command prompt.
C:\ Root\stuff >adb devices
List of devices attached
HT26KS311633 device
Your device will have a different device ID than what is listed above. Just make sure it shows a device ID and device listed after it.
5) Now type: adb reboot bootloader
At this point your phone should reboot into the bootloader with Fastboot selected.
6) Type: fastboot devices
You should see the following output in the command prompt.
C:\inc4>fastboot devices
HT26KS311633 fastboot
Ensure that your device is listed. Your device will have a different device ID than what is listed above. Just make sure it shows a device ID and fastboot listed after it.
7) Type: fastboot reboot
You should see the following output in the command prompt.
C:\inc4>fastboot reboot
rebooting...
finished. total time: 0.070s
Your phone should be rebooting.
You have now verified that your drivers are working correctly even after rebooting into fastboot.
At this point I cannot give you alternative instructions per Team Unlimited. So follow the directions listed HERE.
When you reach step 12 which states:
“Temproot your phone via any method available - we cannot help with this step and it is REQUIRED!”
Follow the following steps that were originally written by captainrewind in the “Team fireballas FakeCid AUTOMATIC bootloader unlock” thread.
Go to Settings -> Connect to PC and change Default connection type to Disk drive and disable Ask me.
Navigate to the folder in the command Prompt by typing
cd c:\Root\stuff
Now that you're there, type:
adb devices
If your phone pops up in the list, you're good to go!
Next, type
adb restore fakebackup.ab
DO NOT click OK to the restore on the device just yet!
Now type:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"
(errors will appear, ignore)
Accept the restore on the device, then type:
adb reboot
(At this time, you are temprooted, and the phone UI will be in an unusable state, with temproot shell.)
After reboot type:
adb shell
Verify that the prompt is "#" (meaning root) or "$" (meaning normal user). If it's not "#", please start over.
You can now return to Team Unlimited’s instructions and continue with step 13.
This should take you the rest of the way to S-Off.
*Madmoose* said:
I have included a method that will test whether your drivers in your current setup will perform in a way that reduces the chance of all hell breaking loose.
Click to expand...
Click to collapse
Excellent suggestion and great advice. Always make sure your computer can recognize your device in all device states before attempting root.
I found the hard way on a Kindle Fire and now always do this test (a couple of times) to make sure the device being rooted can be seen in all states by the PC. For whatever reason, my (original) Kindle Fire has a different USB Enum for each state and my Windows 7 64-Bit computer didn't recognize it in fastboot which caused a lot of irritation.
This is helpful but I believe unlimited specifically asked not to have any other how to threads
Sent from my Nexus 7 using Tapatalk 2
This isn't a how to about Unlimited's process. And frankly, they can request anything they want, but they will not control other peoples threads. They were talking about their own thread.
*Madmoose* said:
Next, type
adb restore fakebackup.ab
DO NOT click OK to the restore on the device just yet!
Now type:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"
(errors will appear, ignore)
Accept the restore on the device, then type:
adb reboot
Click to expand...
Click to collapse
I'd like to comment on this part, since it threw me off a bit and scared the daylights out of me.
After you issue the "while..." command, you'll get infinitely scrolling errors/warnings, or at least I did in Ubuntu. Just ignore them, nothing is wrong. While they are infinitely repeating in your terminal, just accept the restore on the phone and they stop. I don't remember the exact text of the error, but if someone could put it here that would probably be helpful to anyone wondering.
Very cool. Thanks madmoose!
Is It Working with HTC ONE V (GSM) ???
No dude this is the incredible 4G threads
I am so going to do this. Soon. Hawk might have an Ecliptic release some day.
Linch89 said:
No dude this is the incredible 4G threads
Click to expand...
Click to collapse
Will this make my laptop s-off
Sent from my Nexus 7 using Tapatalk 2
Only if your laptop is an Incredible 4G...
Add me to the list of S-OFF via Win7 64bit. I restored my Viper TWRP backup and all is running smootly. Now, I am off to customize my bootloader with RegawMOD Bootloader Customizer.
Used a modified version of this to achieve s-off but what really helped me was the "Verifying that your drivers are working correctly." section. When I had tried unlocking earlier I keep getting stuck in the error looping screen when restoring the fakebackup. This little set of instructions pointed me in the right directions for getting the drivers installed correctly.
Many thanks MadMoose and Happy New Year! :victory:
Many thanks to MadMoose. Everything worked for me on Win7 64bit as well, and would have worked more smoothly if I had done it your way
Yesssssssssssssssssss
Wow what a journey, used it on my 64 bit computer per another post here that gave a very nice detailed instructions. had to relock, temproot, s off, flash recovery, and then restore... but i would do it 100 times again! thanks everyone for your activeness in this community, hopefully it continues to grow
Has anyone tried to get s-off with Windows 8 x64 yet? I copied in the drivers, tried all the commands, and they replied normally. Will I brick my phone if I try?
I'm afraid it won't work unlimited said that 64 win7 wasn't officially supported it just happens to work
It may work but unlimited won't help/support you if you have problems.
bberryhill0 said:
It may work but unlimited won't help/support you if you have problems.
Click to expand...
Click to collapse
I'm just wondering if it doesn't work, then am I bricked? Or can I just pull the battery and restart?
spectre559 said:
I'm just wondering if it doesn't work, then am I bricked? Or can I just pull the battery and restart?
Click to expand...
Click to collapse
Went ahead with s-off in win 7 x64. Success!

Flashing HBOOT Question

I'm having some issues with this device connecting to ADB and I need to flash a different HBOOT so I dont get the error message on boot up. Because of said issue I cant flash a newer HBOOT version to my device via ADB. Is there another way that you can flash other than ADB? I know on previous HTC devices you were able to flash it from the bootloader itself if I remember correctly. Any ideas? Thanks.
Place the hboot in a zip with the android-info.txt file, in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
Code:
fastboot oem rebootRUU
(this puts the device in RUU mode)
Code:
fastboot flash zip hboot.zip
(this flashes the hboot zip file)
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
Code:
fastboot reboot-bootloader
(this reboots the device to bootloader)
santod040 said:
Place the hboot in a zip with the android-info.txt file, in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
Code:
fastboot oem rebootRUU
(this puts the device in RUU mode)
Code:
fastboot flash zip hboot.zip
(this flashes the hboot zip file)
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
Code:
fastboot reboot-bootloader
(this reboots the device to bootloader)
Click to expand...
Click to collapse
Thank you for the response, maybe I wasn't clear enough. I cannot use ADB from my computer AT ALL with this device. It recognizes other devices and shows them when I do adb devices but on the DNA it shows as offline and commands do not work because of that.
spincredible said:
Thank you for the response, maybe I wasn't clear enough. I cannot use ADB from my computer AT ALL with this device. It recognizes other devices and shows them when I do adb devices but on the DNA it shows as offline and commands do not work because of that.
Click to expand...
Click to collapse
what devices does it show?
thayl0 said:
what devices does it show?
Click to expand...
Click to collapse
This is what it shows in ADB:
List of devices attached
FA34GSXXXXXX offline (shows full device but was told by somebody in the past leave most of that info out.)
I know that its DNA related as ADB works just fine on my Gnex without issue.
Are you using Windows 8? There is no HTC drivers for windows 8 that will work. You must use a different windows version or dual boot with Linux.
If you are on a compatible version of windows, try reinstalling the drivers.
Sent from my DNA using my mind.
I'm using Windows 7
Sent from my VS980 4G using Tapatalk

Trying to apply Nexus 6P bootloop fix

Downloaded and installed ADB. Following tutorial here:
https://www.xda-developers.com/nexus-6p-bootloop-fix/
Specifically:
- Connect your smartphone or tablet to your computer with a USB cable. Change the USB mode to “file transfer (MTP)” mode. Some OEMs may or may not require this, but it’s best to just leave it in this mode for general compatibility.
- In the Command Prompt window, enter the following command to launch the ADB daemon: adb devices
- On your phone’s screen, you should see a prompt to allow or deny USB Debugging access. Naturally, you will want to grant USB Debugging access when prompted (and tap the always allow check box if you never want to see that prompt again).install adb
- Finally, re-enter the command from step #6. If everything was successful, you should now see your device’s serial number in the command prompt. Yay! You can now run any ADB command on your device! Now go forth and start modding your phone by following our extensive list of tutorials!
https://www.xda-developers.com/install-adb-windows-macos-linux/
I did all the above. But don't see anything from:
C:\ADB>fastboot devices
C:\ADB>fastboot flash boot 6p48C.img
< waiting for any device >
Nexus 6P was plugged into the USB cable on Win10 machine. Am in MTP mode. Most recent Google USB drivers installed.
I have done OEM Unlock in setup|Developer options. I have also turned on USB debugging in same options.
I am [obviously] lost. Anyone know what else I might try?
OK, I have made a little progress messing around on my own. It seems that running from the CMD line in Win 10, ADB command works but Fastboot does not. WHY? Bith are in the same directory.
If I type Fastboot by itself, then I get a list of the associated parameters, which means that the CMD system DOES recognize the Fastboot command.
Now, if I run CMD====> "ADB devices", it looks like my device is recognized and attached (that is my serial# below).
But if I try CMD=====> "Fastboot devices", as the instructions require, I get nothing. And if I try to run the flash job via Fastboot, that does not work either.
==================
C:\ADB>adb devices
List of devices attached
8XV5Txxxxxxxxxxx device
C:\ADB>fastboot flash boot 6p48C.img
< waiting for any device >
===================
Wondering if I need to install the Android SDK on Windows for this process to work?
I Think You need to Redo The process from Step One.
I Heard about This and Never Did An OTA.
If it Persists Try Using A Different PC and If After That It doesn't work Then Yes Android SDK is The last Option.
Sent from my Nexus 6P using Tapatalk
Solved. I needed to add the ADB install directory to the environmental path. Don't quite understand why, but doing so allowed me to get the problem fixed.

Categories

Resources