Database Users

[how to]restore software status official

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

mine too

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

deleted. Better to wait Scotty's stock guide.

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

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

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

Worked for me! Thanks!

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

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

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

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

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

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

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

Stock Locked bootloader?? @scotty1223

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

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

Problem ROM LENOVO YOGA TABLET 2

Hello guys!
A person of my family has bought a Lenovo Yoga Tablet 2 1050F from China. The problem is there are only chinese and english language to select. The firmware are chinese, and i have downloaded a firmware with multilanguage from NEEDROM.
I not know how can i flash this firmware, I have instaled Phone Flash Tool 4.4.4., but when I try to start flash and the device it reboots in Flashboot mode, my computer not detect the device, and the operation finish without any profit result for me.
Device start normal boot when I unplug the usb cable.
Thank for all.
ABOUT DEVICE:
- Model number: YOGA Tablet 2-150F
- Android 4.4.2
- Software version: YOGA Tablet 2-1050f_150428
- Build number: YOGATablet2-1050F_S000175_150428
Serial Num: BaytrailD482531E
DROIDBOOT VERSION 2.0
PRODUCT: YT2_10_PR
Please, help me.

Best to install adb and fastboot.
Do adb devices from command prompt and see if they it displays your device
You need to go on to device manager when you phone is in fastboot mode, connected to your PC. There WILL be a ! Next to your device.
Click update driver and then select from my PC Not windows update. Select the the driver installed when in normal mode and select adb driver
Sent from my SM-G901F using Tapatalk

Hi Rob
VictorVL90
In the settings when you go to Language and input,can you change to the language you want there.

pug1 said:
Best to install adb and fastboot.
Do adb devices from command prompt and see if they it displays your device
You need to go on to device manager when you phone is in fastboot mode, connected to your PC. There WILL be a ! Next to your device.
Click update driver and then select from my PC Not windows update. Select the the driver installed when in normal mode and select adb driver
Sent from my SM-G901F using Tapatalk
Click to expand...
Click to collapse
work, but... stop at 26%
02/24/16 20:09:15.881 INFO : Phone Flash Tool V 4.4.4-1 Win32 External (build on Mon Apr 28 09:56:35 UTC 2014)
02/24/16 20:09:15.881 INFO : Using xFSTK version: 1.5.3
02/24/16 20:09:15.959 INFO : Using Android Debug Bridge version 1.0.31
02/24/16 20:09:15.959 INFO : OS version detected: Windows 8 (x64)
02/24/16 20:09:16.147 INFO : Adb and fastboot binaries OK
02/24/16 20:09:16.147 INFO : Phone Flash Tool initialized successfully
02/24/16 20:09:16.163 INFO : Loading Flash file ...
02/24/16 20:09:16.163 INFO : Ready to flash!
02/24/16 20:09:40.479 INFO : Loading Flash file (C:/Users/Víctor Valle/Downloads/YOGA-Tablet-2-1050F/YOGA-Tablet-2-1050F/target_bin/flash.xml)
02/24/16 20:09:40.479 INFO : GP_Flag is set to 0x80000045
02/24/16 20:09:40.479 INFO : Ready to flash!
02/24/16 20:09:46.464 INFO : Port 0/3: Flashing OS
02/24/16 20:09:46.464 INFO : Port 0/3: fastboot -s INTD482531E flash osloader "C:/Users/Víctor Valle/Downloads/YOGA-Tablet-2-1050F/YOGA-Tablet-2-1050F/target_bin/efilinux.efi"
02/24/16 20:09:48.604 INFO : Port 0/3: fastboot -s INTD482531E boot "C:/Users/Víctor Valle/Downloads/YOGA-Tablet-2-1050F/YOGA-Tablet-2-1050F/target_bin/droidboot.img"
02/24/16 20:09:51.381 INFO : Port 0/3: sleep 25000 ms
02/24/16 20:10:16.384 INFO : Port 0/3: fastboot -s INTD482531E oem wipe ESP
02/24/16 20:13:56.682 WARNING: Port 0/3: Process TIMEOUT Failed to execute ""C:/Program Files (x86)/Intel/Phone Flash Tool/fastboot.exe" -s INTD482531E oem wipe ESP"
02/24/16 20:13:58.690 WARNING: Port 0/3: Retry to execute fastboot -s INTD482531E oem wipe ESP
Click to expand...
Click to collapse

VictorVL90 said:
work, but... stop at 26%
Click to expand...
Click to collapse
Have you installed http://forum.xda-developers.com/showthread.php?p=48915118#post48915118.
I use this method without fail on win10 pro
Sent from my SM-G901F using Tapatalk

Try using this Rom , tinyurl.com/hn9m7rc
also copy the easyimage zip file in the download to a memory card in the tablet to enable you to set the country code.
It is clean,it's the one I used.

pug1 said:
Have you installed http://forum.xda-developers.com/showthread.php?p=48915118#post48915118.
I use this method without fail on win10 pro
Sent from my SM-G901F using Tapatalk
Click to expand...
Click to collapse
GREAT! Tablet work full 100%
Thanks!

One more question...
Occasionally, the System try to update a patch, but the installation always failure. What can i do for prevent this automatically update?

VictorVL90 said:
One more question...
Occasionally, the System try to update a patch, but the installation always failure. What can i do for prevent this automatically update?
Click to expand...
Click to collapse
Usually you are asked if you want to install the update,just say no.

VictorVL90 said:
One more question...
Occasionally, the System try to update a patch, but the installation always failure. What can i do for prevent this automatically update?
Click to expand...
Click to collapse
Are you on stock unrooted firmware? If so you could try going into stock recovery and factory reset. Then try to let the update install. I would always go with an update.

corasman said:
Usually you are asked if you want to install the update,just say no.
Click to expand...
Click to collapse
Impossible to say no. It appears on the screen counts down and automatically restart.

All is correct. I have rooted the device and i have frozen the process that causes update.
Now I can say that everything is correct.
Very thanks!

Nexus 6P not recognized via adb devices on Mac

Hi everyone,
I have a Nexus 6P which simply refuses to connect via USB on my Mac (i.e. it doesn't show up as a valid device under adb devices or via Android File Transfer). I believe it was working at some point but it seems to have stopped now. Might be worth noting, I did try connecting it to my car's charger a few months ago but had the worst time with it, it would charge and disconnect every few seconds (may or may not be relevant in this case as it pertains to the USB). I tried a different charger and it works fine with it though.
I have tried a lot of different things (which I'll list below) but have had no luck getting my Nexus 6P being recognized as a device when I connect it to my Mac (or any other). I do have the Developer settings enabled and I am able to switch to MTP but I never get the prompt to change USB mode. Anytime I connect my device, adb devices doesn't list it at all. I tried ADB File transfer as well and that also says "Please connect your device".
Here are some of the things I have tried so far:
1. Used different cables - no luck
2. Used a different mac - no luck
3. Tried a different Nexus 6P with my cable, it works fine (so it is not a cable issue)
4. Tried a different Nexus 6P with my mac, it works fine (so my Mac seems to be OK too)
5. Restarted in recovery mode - no luck
6. Tried removing a bunch of apps in case there was something conflicting - no luck so far
7. Chatted up Google support - They couldn't tell me much outside of the last option - Factory Reset - I have been holding off on that since I want to be able to transfer my files out first but I really want to avoid having to try that before exhausting all other options. They did offer to replace with a refurb'ed device but I had to decline that.
I did create a bug report dump using the device to see if anything interesting showed up and the only thing noticeable there is an exception related to USB. I am putting that info here in case it is useful in helping with this.
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
USB Host State:
USB Port State:
otg_default: port=UsbPort{id=otg_default, supportedModes=dual}, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false
USB Audio Devices:
USB MIDI Devices:
Settings for user 0:
Device permissions:
Accessory permissions:
Device preferences:
Accessory preferences:
Any help here is really appreciated! Thanks

desimunda42 said:
Code:
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
Click to expand...
Click to collapse
That seems suspicious. Was this taken while the phone was connected to your mac?
Here's my phone's dump while NOT connected to a computer
Code:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
[COLOR="red"] Last key received: blahblahblahblah (not null)
User keys: blahblahblahblah (no exception)
[/COLOR] System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
Here it is when connected to computer
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
[COLOR="red"] mConnected: true
mConfigured: true
[/COLOR] mUsbDataUnlocked: false
mCurrentAccessory: null
[COLOR="red"] Kernel state: CONFIGURED
[/COLOR] Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
[COLOR="Red"] Last key received: blahblahblahblah (not null)
User keys: blahblahblahblah (no exception)
[/COLOR] System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
Are you on a custom rom? Do you get an authorization prompt if you call "adb device" after doing "Revoke USB debugging authorizations" from Develop options?

adotkdotjh said:
That seems suspicious. Was this taken while the phone was connected to your mac?
Are you on a custom rom? Do you get an authorization prompt if you call "adb device" after doing "Revoke USB debugging authorizations" from Develop options?
Click to expand...
Click to collapse
I wasn't connected to my Mac at the time I pulled the report (I confirmed by repeating it just now and still get that 'FileNotFoundException" in the logs for USB device. I don't have a custom rom, I have the standard OEM from the Google Store and didn't do anything else with it.
Also, I did revoke the USB debugging auth multiple times and inspite of that I never get any prompt when I connect.
I also got the report while connected to the Mac and am still seeing the same exception:
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
USB Host State:
USB Port State:
otg_default: port=UsbPort{id=otg_default, supportedModes=dual}, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false
USB Audio Devices:
USB MIDI Devices:
Settings for user 0:
Device permissions:
Accessory permissions:
Device preferences:
Accessory preferences:

desimunda42 said:
Hi everyone,
I have a Nexus 6P which simply refuses to connect via USB on my Mac (i.e. it doesn't show up as a valid device under adb devices or via Android File Transfer). I believe it was working at some point but it seems to have stopped now. Might be worth noting, I did try connecting it to my car's charger a few months ago but had the worst time with it, it would charge and disconnect every few seconds (may or may not be relevant in this case as it pertains to the USB). I tried a different charger and it works fine with it though.
I have tried a lot of different things (which I'll list below) but have had no luck getting my Nexus 6P being recognized as a device when I connect it to my Mac (or any other). I do have the Developer settings enabled and I am able to switch to MTP but I never get the prompt to change USB mode. Anytime I connect my device, adb devices doesn't list it at all. I tried ADB File transfer as well and that also says "Please connect your device".
Here are some of the things I have tried so far:
1. Used different cables - no luck
2. Used a different mac - no luck
3. Tried a different Nexus 6P with my cable, it works fine (so it is not a cable issue)
4. Tried a different Nexus 6P with my mac, it works fine (so my Mac seems to be OK too)
5. Restarted in recovery mode - no luck
6. Tried removing a bunch of apps in case there was something conflicting - no luck so far
7. Chatted up Google support - They couldn't tell me much outside of the last option - Factory Reset - I have been holding off on that since I want to be able to transfer my files out first but I really want to avoid having to try that before exhausting all other options. They did offer to replace with a refurb'ed device but I had to decline that.
I did create a bug report dump using the device to see if anything interesting showed up and the only thing noticeable there is an exception related to USB. I am putting that info here in case it is useful in helping with this.
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
USB Host State:
USB Port State:
otg_default: port=UsbPort{id=otg_default, supportedModes=dual}, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false
USB Audio Devices:
USB MIDI Devices:
Settings for user 0:
Device permissions:
Accessory permissions:
Device preferences:
Accessory preferences:
Any help here is really appreciated! Thanks
Click to expand...
Click to collapse
I usually only get the key prompt for ADB authorzation when I connect my device and type "adb devices"..... If worse comes to worse, You can restore your phone to factory settings without wiping your sd card. Then you could test that option with compromising your data. Just flash each image from the archive yourself when restoring the firmware as opposed to using the flash-all scipt, or resetting the phone from settings... DO NOT flash the "userdata.img" included in the factory firmware archive or issue the command "fastboot format userdata" during the restore process and all of your files will be fine. This may be an option as long as fastboot is still functional on your device. Ive come across so many different devices in so many different conditions over the years, as long as the device could power on and the usb port was functional, fasboot has worked time and time again.
PS adb on Mac can be a bit tricky especially if this is the first time youre attempting to o install and use it. Unless you set the correct enviornment variables during the install process, you will oly be able to access adb from inside the folder that its stored in on your mac. Youll have to pull up your terminal and and direct it to the folder containing adb and fastboot. Its usually ina a folder called "platform-tools" Which can be found in the dictory in whch you installed the Android SDK or SDK Tools packages... Now that I think about it, you have to download adb from the SDK package I just mentioned. After doing so, youll find the platform tools folder and it should contain what you need. As long as java is correctly installed on your mac then everything should work once you issue the "adb devices" command in a terminal session thats points at the "platform-tools" folder. YOU ALSO HAVE TO HAVE JDK INSTALLED in order for it to work with your device. I just looked at what you posted and it looks like youred missing JDK"...
If you havent done any of this yet the thats the problem. If everything I just typed seems confusing then you can try this which explains everything you need to do to set up adb a whole lot better than my attempt above lol buts its going to take some time to accomplish https://seo-michael.co.uk/how-to-setup-adb-on-os-x/
or
You can also install and configure adb a whole lot easier by issuing the following commands from within your mac terminal.... (This will install Brew on your Mac, if you arent familiar with what it is, Its a software distrobution platform. Sort of like git hub and linux software repos. When in doubt, do a little reading first. It'll solve all your problems....
-Install Brew - Copy and paste this command into a mac terminal and follow the prompts that show up.
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
-Once that finishes, next use this command
brew update && brew cask install java
-Once that is complete enter this last command
brew install android-platform-tools
Those 3 commands will do 99 percent of the work. When its done just find the platform tools folder and go from there. Hope this helps.

Sass86oh said:
PS adb on Mac can be a bit tricky especially if this is the first time youre attempting to o install and use it. Unless you set the correct enviornment variables during the install process, you will oly be able to access adb from inside the folder that its stored in on your mac. Youll have to pull up your terminal and and direct it to the folder containing adb and fastboot. Its usually ina a folder called "platform-tools" Which can be found in the dictory in whch you installed the Android SDK or SDK Tools packages... Now that I think about it, you have to download adb from the SDK package I just mentioned. After doing so, youll find the platform tools folder and it should contain what you need. As long as java is correctly installed on your mac then everything should work once you issue the "adb devices" command in a terminal session thats points at the "platform-tools" folder. YOU ALSO HAVE TO HAVE JDK INSTALLED in order for it to work with your device. I just looked at what you posted and it looks like youred missing JDK"...
Click to expand...
Click to collapse
He says he already tried adb devices which didn't list anything. That tells me adb is configured correctly. Otherwise it should've given errors. Plus, he also said another Nexus 6P worked on the same mac.

adotkdotjh said:
He says he already tried adb devices which didn't list anything. That tells me adb is configured correctly. Otherwise it should've given errors. Plus, he also said another Nexus 6P worked on the same mac.
Click to expand...
Click to collapse
Yep
Sass86oh said:
I usually only get the key prompt for ADB authorzation when I connect my device and type "adb devices"..... If worse comes to worse, You can restore your phone to factory settings without wiping your sd card. Then you could test that option with compromising your data. Just flash each image from the archive yourself when restoring the firmware as opposed to using the flash-all scipt, or resetting the phone from settings... DO NOT flash the "userdata.img" included in the factory firmware archive or issue the command "fastboot format userdata" during the restore process and all of your files will be fine. This may be an option as long as fastboot is still functional on your device. Ive come across so many different devices in so many different conditions over the years, as long as the device could power on and the usb port was functional, fasboot has worked time and time again.
PS adb on Mac can be a bit tricky especially if this is the first time youre attempting to o install and use it. Unless you set the correct enviornment variables during the install process, you will oly be able to access adb from inside the folder that its stored in on your mac.
Click to expand...
Click to collapse
Thanks for the detailed steps but like adotkdotjh mentioned, I already have a working adb (and it worked fine with a different Nexus 6P on the same mac). How would 'fastboot' work if the computer does not even see my device under list of devices? I've never done any image flashing before so that would be quite an unfamiliar territory but I'd be willing to explore. Where would I get these image files and how do I issue the command to the device while it is not being recognized? Thanks

desimunda42 said:
Yep
Thanks for the detailed steps but like adotkdotjh mentioned, I already have a working adb (and it worked fine with a different Nexus 6P on the same mac). How would 'fastboot' work if the computer does not even see my device under list of devices? I've never done any image flashing before so that would be quite an unfamiliar territory but I'd be willing to explore. Where would I get these image files and how do I issue the command to the device while it is not being recognized? Thanks
Click to expand...
Click to collapse
Fastboot (also refered to as "download mode") is a tool used to essentially reprogram your device in the event that you are unable to enter into recovery mode in oreder to fix whatever issue your device is having. Android devices have 3 working modes, normal function, recovery mode, and fastboot. Number one is obvious, recovery allows you to completely reset your device without using a computer if every other measure youve tried hasn't worked. When you use this feature everything on your device is erased and your phone is completely restored to factory settings. Its convienet becuase not everyone is computer savvy and its to the point. But say you were updating (system update) your phone and accidently dropped it causing the battery to fall out and the device to shut off in the middle of the update process. What will most likely happen is the system partition will become corrupt, causing the phone to stick at the initial boot screen. Usually if that happens you can still access recovery mode and just reset but if for some reason that didnt work you would go to the manufacturers website and download the latest firmware for your device. You put the phone into fastboot mode by holding volume down and then pressing and holding the power button at the same time (while the phone is off).The process varies bydevice, If done correctly you will see on your screen a bunch of info along with Andy (the Android) chillin with his hatch open. You connect your phone to your computer and as long as your computer is set up correctly with adb and fastboot, you now have the abailty to reprogram (flash) your device using a series of commands that are issued from either the command line (windows) or terminal (linux/mac).
YOUR BOOTLOADER NEEDS TO BE UNLOCKED BEFORE CONTINUING. IF YOU DONT SEE A LITTLE LOCK AT THE BOTTOM OF YOUR DEVICE UNDER THE GOOGLE LOGO WHEN YOU FIRST TURN IT ON THEN YOU NEED TO GO TO SETTINGS, ABOUT DEVICE, FIND BUILD NUMBER AND TAP IT RAPIDLY UNTIL YOU SEE A MESSAGE POP UP SAYING YOU UNLOCKED DEVELOPER OPTIONS. GO BACK TO THE SETTINGS MENU AND SELEC DEVELOPER OPTIONS WHICH SHOULD NOW BE THERE AND INSIDE THERES AN OPTION CALLED "ALLOW OEM UNLOCKING" TURN IT ON. AND CONTINUE
Eextract the firmware archive you downloaded which will produce a folder containing 2 ".img files" files, another ".tar" archive, and some script files that you can use to make the process pretty much automated.
There are two of them, one for Windows (flash-all.bat) and one for Linux and Mac (flash-all.sh)....
Open the folder that was extracted from the firmware archive... Hold shift then right click a blank area in the folder. Select "open command prompt here" (Windows)
or
Type in terminal : cd ~/downloads/xxx where "xxx" is the name of the folder that was extracted but make sure that folder is moved to your "downloads" directory first
Then type the following commands:
IF YOU HAVENT UNLOCkED YOUR BOOTLOADER BEFORE THEN THIS IS WHERE YOU WILL NEED TO:
For Mac/Linux type: ./fastboot flashing unlock **Make sure you use the ./ or the command wont be recognized**
For Windows type: fastboot flashing unlock
Select yes on the phone when it asks if youre sure..... BAM, unlocked bootloader.
Your phone is completely free of restrections if you want to install custom firmware now. If not you can relock it after flashing the stock firmare by enterning fastboot mode again and typing
fastboot flashing lock or ./fastboot flashing lock (mac/linux).....
Now we can proceed with flashing the device...
For Windows: flash-all.bat and hit enter. The computer will do the rest.
Linux/Mac: ./flash-all.sh Make sure you use the ./ or the command wont be recognized.
If youre feeling brave you can do the entire process yourself by extracting the files in that second archive that was produced and flash each of them individually using a series of command in a specific order.
The 2nd extracted archive will give you a folder with five .img files
boot.img
cache.img
system.img
recovery.img
userdata.img ***** DO NOT FLASH THIS IMAGE. FORGET ITS EVEN THERE****
Take all five and move them to the original folder that was extracted. There are 2 other .img files that were extracted from the first archive also like I mentioned above, one that says "BOOTLOADER.xxx.xx.img" and one that says "RADIO.xxx.xxx.img"... Rename RADIO.xxx.xxx.img to | radio.img |and the other to| bootloader.img |ALL LOWER CASE keep them in that folder along with the other five. Now you should have 7 total image files in one folder. (Its smart to use the folder that your command prompt or terminal was opened in, if you decide to use a different folder then you have to direct each fastboot command to the folder where the .img file is located.
from the command line you flash each img individually with the following commands.....
(Mac/Linux need to include ./ before every fastboot command begins like this: ./fastboot or it wont work.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader (phone will reboot then go back into fastboot mode, dont worry should only take seconds)
fastboot flash radio radio.img
fastboot reboot-bootloader (reboots again)
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot format userdata (this command takes place of the "userdata.img" file I told you to forget about)
fastboot reboot
As long as you see action on the screen and a "complete" after every command then youre in business. If you get an error check your spelling. THE COMMAND LINE IS CASE SENSETIVE. You might type the correct words but if one letter is capital the command wont work. If theres an extra space between words then the command wont work so check everything. Safe rule: Everything should be in lower case letters with 1 space after every word.... THIS S*** MATTERS
Its not as hard as it seems if you arent familiar with the process, but its also not something to mess with unless youve done your homework. Read up on it, there are so many good posts and people in here so you'll be able to find everything you need without any issue.
Fastboot can also be used to install a custom recovery like TWRP which would then allow you to install custom firmware (roms) on your device as long as theres support for it. Nexus devices are built for that very reason! They tend to have a huge selection of development within the Android community. They come with Android as Google intended it to be! No extra BS.... And its wicked easy to unlock the bootloader. That is why they are, in my opinion, the best Android devices available. But someone who doesnt really care much for things like modding and installing custom firmware might see the Nexus as plain device which lacks the bells and whistles included in other devices. Which is ok! I personally love the simplicity of pure Android and the whole philosophy behind the Nexus Program. To each is own! If you need anything else send me a message!

Have not read it all on here lol install this on your Mac https://www.android.com/filetransfer/ and see if it sees you 6p make sure you plug in them change from charging to file transfer on the phone then exit out of the app and reboot that will tell you if your Mac sees your phone

Correct Partition Set Up

Hi all...
I have a Nexus 6P that just sticks in a Google bootloop.
The phone has USB debugging on and the bootloader unlocked.
I have the correct Google USB driver installed and in windows 10, Device Manager it shows up as 'Android Bootloader Device"
-- properties of this tab shows device working ok
When i connect the USB data lead (i have tried now several) to the PC and phone... the PC makes a tone to confirm connection.
I have downloaded the latest Fastboot and ADB driver package (platform-tools_r28.0.1-windows).
When i command prompt into the folder that houses Fastboot / Adb , i am able to do the following:-
ADB Version --> Android Debug Version 1.0.40 Version 4986621
ADB DEVICES --> List of devices attached (blank)
---> i tried ADB KILL-SERVER --> * daemon not running; starting now at tcp:5037 *daemon started successfully
I then retry the command ADB DEVICES and again i am shown --> List of devices attached (blank)
When i use the following Fastboot commands, i fair better:
FASTBOOT DEVICES --> "Serial number xxxxxxxxxxxxx" fastboot
FASTBOOT FLASH RECOVERY TWRP.IMG --> Sending 'recovery' 16425kb Failed (write to device failed in Sendbuffer () Unknown error Finished Total time: 5.006s
I am confused as i know i have connection from PC to device?
I have tried in Win10, Win 7 and Linux...all the same as above?
I believe that my partition tables are screwed?
Is there a command I can execute that will reset the phone partition to make the partition writeable...thus it will take a custom recovery?
Many thanks for everyones help
xx

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

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

Tuto updated for latest TWRP recovery

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

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

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

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

Thank you .I did it by following your guide.

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

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

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

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

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

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

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

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

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

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

Hi, tutorial and pack updated for Android 11

thx for the guide!

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