Related
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
In this guide I will show you how to use adb to move files to or from your device. Especially helpful if your device has MTP and you can't get it to work with mtpfs on GNU/Linux.
What do you need?
Computer with GNU/Linux.
Connection to the Internet.
The 32bit adb binary or the 64bit adb binary, they are added as attachment to this post. (1)
An Android phone with USB debugging on.
Steps:
Connect your phone with a USB cable to your computer. Make sure you have USB debugging on! (2) Put the adb binary in a folder where you can open a terminal. With the terminal open type:
Code:
./adb devices
Make sure it says something like this:
Code:
List of devices attached
XXXXXXXXXXXXXdevice
Now you know you properly connected your device type:
Code:
./adb pull /sdcard/
or
Code:
./adb push /sdcard/
More info on adb commands you can find here:
http://developer.android.com/tools/help/adb.html
(1): If you are using the Debian or Ubuntu distro (or another wich allows you to install *.deb files) you can install the 32- or 64 bit adb packages and use adb from every folder. Download them from the attachments. If you use this type adb instead of ./adb.
(2): Don't know how to turn on USB debugging? Go to settings, scroll down to the About phone menu item. Tap it and scroll down again to Build number and tap it many times! Then go to settings, and tap developer options and find the USB debugging option.
I hope this was helpful, but I think not, because I get no replies...
AW: [GUIDE] MTP doesn't work for you on GNU/Linux? Use adb.
http://www.webupd8.org/2012/12/how-to-mount-android-40-ubuntu-go-mtpfs.html
I usually use sftp to transfer files. No cable and shell access included.
Sent from my GT-I9100 using xda app-developers app
If you want to copy lots of files, like your music collection or movies, wireless is not fast enough. That's why I use adb, because it's very fast.
*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??
READ THIIS!
*this thread is for E8. it will NOT work on m7,or any older device. please check the general forum for your particular device for a similar thread.
this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock.
advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.
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. its not a way to magically unlock
the usual disclaimers:
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 comand protocol
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
-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 older)
-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 "lock status flag"
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(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 you are now locked
_____________________________________________________________________________________________
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(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 you are now unlocked
(yes this is m7. i dont have an E8. if someone wants to provide correct screenshots,ill add them)
other useful threads:
remove tampered banner: http://forum.xda-developers.com/one-e8/general/how-to-remove-tampered-banner-t3019164
change mid without an eng bootloader: http://forum.xda-developers.com/one-e8/general/how-to-change-mid-eng-bootloader-t3019148
sorry for the delay,guys. hope you find it useful
This way doesn't wipe out all the data, right?
buggerman said:
This way doesn't wipe out all the data, right?
Click to expand...
Click to collapse
Correct. It will not wipe any data
Sent from my HTC One max
Good job.
Any way to do S-OFF to S-ON ??
greg
gregferns said:
Good job.
Any way to do S-OFF to S-ON ??
greg
Click to expand...
Click to collapse
Sunshine again..
windows 8 and above
am using windows 10 but it seems the required tool does not support the operating system
any other option for me?
cant get # prompt
hi, when i enter the Su command it says su not found and the prompt still remains $ instead of #. Is it something am not getting right or something. Thanks
Hi all,
I was running LineageOS 14.1 Official Latest Build lineage-14.1-20180119 and I have updated the TWRP from 3.0.2-0 to 3.2.1-0. After flashing to boot from within recovery it does not reboot. Just nothing.
No Screen or LEDs. When pressing the power key it vibrates. No fastboot or Recovery mode.
Red LED flashes when connected to PC. That's it. Nothing else.
Please help!!!!!
I had this too. To recover:
- Download lineage-14.1-20180119.zip, unpack it and locate the file "boot.img".
- Download flashtool (I used v0.9.23.1).
- Boot into fastboot mode:
- Disconnnect the USB cable, Turn off phone and wait a bit.
- Hold volume+ and connect the USB cable.
- The phone should show a blue status light.
- Flash boot.img using FlashTool (press Flash icon, Flash kernel only).
- Reboot phone to system in FlashTool
This should bring your phone back up.
To install TWRP, I always use one of those procedures:
- Connect phone via USB and enable ADB
- Copy .img to some location on phone, eg. /storage/sdcard1
- Start ADB shell
- Run command via ADB:
su
dd if=/storage/sdcard1/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
OR:
- Connect phone via USB and enable ADB
- Run on host computer:
adb root
adb wait-for-device
adb push "PATH_TO_TWRP_IMG_FILE" /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
If adb is complaining about "no premissions" for your device, try:
sudo adb kill-server
sudo adb start-server
Awesome!!
OverBim said:
I had this too. To recover:
- Download lineage-14.1-20180119.zip, unpack it and locate the file "boot.img".
- Download flashtool (I used v0.9.23.1).
- Boot into fastboot mode:
- Disconnnect the USB cable, Turn off phone and wait a bit.
- Hold volume+ and connect the USB cable.
- The phone should show a blue status light.
- Flash boot.img using FlashTool (press Flash icon, Flash kernel only).
- Reboot phone to system in FlashTool
This should bring your phone back up.
To install TWRP, I always use one of those procedures:
- Connect phone via USB and enable ADB
- Copy .img to some location on phone, eg. /storage/sdcard1
- Start ADB shell
- Run command via ADB:
su
dd if=/storage/sdcard1/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
OR:
- Connect phone via USB and enable ADB
- Run on host computer:
adb root
adb wait-for-device
adb push "PATH_TO_TWRP_IMG_FILE" /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
If adb is complaining about "no premissions" for your device, try:
sudo adb kill-server
sudo adb start-server
Click to expand...
Click to collapse
You are AWESOME!!! that actually worked!! Thank you very much @OverBim
I was very hopeless about recovering the phone. Thank you again.
And if you can, please tell me what did I do wrong or what happened to cause that.