Database Users

SP Flashing under linux

Any one tried flashing using Linux version of SP flash tool? . I tried but seems the device not recognized by pc.

hohassan444 said:
Any one tried flashing using Linux version of SP flash tool? . I tried but seems the device not recognized by pc.
Click to expand...
Click to collapse
Do you mind providing a link to the linux version so that i can test?

kirito9 said:
Do you mind providing a link to the linux version so that i can test?
Click to expand...
Click to collapse
http://www.needrom.com/download/sp-flash-tool-v5-1424-00/
note: currently latest version on that page actually is SP Flash Tool v5.1520.00

Nofan Tasi said:
http://www.needrom.com/download/sp-flash-tool-v5-1424-00/
note latest version on that page actually is SP Flash Tool v5.1520.00
Click to expand...
Click to collapse
Alright, thanks

I found a solution for S_BROM_CMD_JUMP_DA_FAIL (2035) here:
The “modemmanager” package integrated by default on your computer it is not compatible with the MTK Flash Tool for the Linux (14.04 and 14.10) latest versions, and must be uninstalled beforehand. This package is used as a protective USB modem device. Any user configuration file will remain after you uninstall and install the package. Though, we can reinstate our current configuration if necessary, after using the tool.
The following steps will be necessary for the latest versions of Ubuntu:
º Uninstall the designated package using the following commands:
♦sudo apt*-get remove modemmanager
♦sudo service udev restart
Udev restart the service without restarting the computer
Udev restart the service without restarting the computer
This may have the side effect of removing the kernel module “cdc_acm”. To check if so, run the following command:
♦lsmod | grep cdc_acm
Check kernel module
Check kernel module
º If it gives you an empty list in return, you must install the following module:
♦sudo modprobe cdc_acm
Click to expand...
Click to collapse
After this, the tool connected to my phone without errors.
I reinstalled modemmanager after flashing:
Code:
sudo apt-get install modemmanager
I slightly modified Sergio Riveros excellent! marvellous! perfect! tutorial and translated it into German for android-hilfe.de
I will post an English version here within the next couple of days...

I finally can put the ancient XP netbook back where it came from to (hopefully) never have to come out again.
The linux SP flash tool works just fine and, yes: cdc_acm module is needed as dmesg shows:
--
usb 1-5: new high-speed USB device number 6 using ehci-pci
usb 1-5: New USB device found, idVendor=0e8d, idProduct=2000
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-5: Product: MT65xx Preloader
usb 1-5: Manufacturer: MediaTek
cdc_acm 1-5:1.1: ttyACM0: USB ACM device
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
--

[ROOT] Amazon Fire TV Gen 2 (4k)

There is an updated thread now for rooting the AFTV2 that supports both 5.0.3.1 and 5.0.4 and maybe others in the future, see http://forum.xda-developers.com/fire-tv/general/root-amazon-fire-tv-2-updated-t3277556. The new method is simpler than this method and requires less to download and less steps to run.
To be safe run checkver.py every time you handshake since 5.0.4 is starting to roll out! Checkout the 5.0.3.1 tag in order to use this older method.
If you were able to root your AFTV2 we'd appropriate if you report your success on the poll located here.
NOTE: Root was obtained a few weeks ago so... this procedure is not the most time efficient, but it is just a few simple steps that anyone with a technical background can follow. There are ideas and some work in progress to make it easier. It depends also on serial port stability, which is somewhat random luck. Linux experience will be beneficial. The usual disclaimers apply, which means this rooting procedure comes with some risks and the scripts involved haven't been tested in all environments. Any harm that may come from rooting your device using this procedure is at your own risk and I assume no responsibility for any damage it may cause. I will do my best to help you get through it and recover if possible.
Root the Device
It's taken quite a bit of effort, but I've finally managed to create a pre-rooted system image (as well as backup the original) and provide a semi-efficient way to flash the rooted system image. Before attempting any of the steps listed below YOU MUST BE RUNNING 5.0.3.1. You should also have a unmodified/pristine system partition. You would probably know if you had any modifications and at this point that would be uncommon. If the patching fails for some reason just power off the device, reboot your computer (resets the serial port buffer), start the handshake script, then turn on the device. Once the handshake completes run the patching command again. There is no harm running the patching command two or more times. If it keeps hanging try a different computer.
To get started you will need a system that meets the following requirements:
Linux (Mac OS X or Windows w/ changes)
Python 3.x
PySerial
sudo yum install python3-pyserial # Fedora or RedHat
sudo apt-get install python3-serial # Ubuntu or Debian
USB Male A to Male A cable
R/W access to /dev/ttyACM0 (or use sudo)
ADB USB access (optional, but helpful)
Stop ModemManager (if you have it setup, which blocks handshaking)
Now run the following sequence of commands:
Code:
git clone --branch 5.0.3.1 https://gitlab.com/zeroepoch/aftv2-tools.git
cd aftv2-tools
wget http://download.zeroepoch.com/aftv2/5.0.3.1/system.root.img.gz
wget http://download.zeroepoch.com/aftv2/5.0.3.1/system.diff.gz
gunzip system.root.img.gz
gunzip system.diff.gz
adb reboot ; ./handshake.py # or restart but run ./handshake.py first
./checkver.py # STOP if it reports NO!
./patch_mmc.hs 0x00000000058e0000 system.root.img system.diff # takes ~2 hours
# last address is 0x50dce600
For Macs (see post #115, thanks @ians325) to satisfy the requirements above you will need to install python 3.5.0 for Mac OS X from python.org then run "sudo pip3 install pyserial" to install pyserial. Instead of "wget $URL" use "curl -O $URL".
Windows is working now, but it's constantly improving to make it easier for novice users. The bash script has been ported to a batch file (no cygwin needed) and the serial port has some auto-detection built in now. The files needed for Windows have already been added to the repo but the README is constantly evolving. @ImCoKeMaN (big thanks) and myself are working to improve the process and make it easier for Windows users.
Anyone interested in rooting using an Ubuntu VM should watch the YouTube video by @ultimate_spy_binns, https://www.youtube.com/watch?v=CZQqLoO6ojM. There is also a script to help automate the process if you are doing this on an Ubuntu live CD/USB found here (by @BagiMT).
To test that root is working you should first connect to adb shell and then run the command "su". You will need to accept a prompt on the screen (HDMI port) at least once. The shell should change from a dollar-sign ($) prompt to a hash (#) prompt.
If you would like to disable updates after rooting you can use the following commands:
Code:
adb shell
su
pm disable com.amazon.device.software.ota
To go back to stock in case you want to update or for whatever other reason:
Code:
wget http://download.zeroepoch.com/aftv2/5.0.3.1/system.orig.img.gz
gunzip system.orig.img.gz
adb push system.orig.img /data/local/tmp
adb shell
su
pm enable com.amazon.device.software.ota
dd if=/data/local/tmp/system.orig.img of=/dev/block/platform/mtk-msdc.0/by-name/system bs=1m
sync
reboot
I don't always have the best luck transferring large files over ADB so another option is to copy the uncompressed image file to a microSD card and changing the path to /storage/sdcard1/system.orig.img. Be extremely careful that you have the right path, that the file you are reading exists, and that the file is around 1.2 GB in size. Otherwise you may potentially trash your system.
Background Info
This root method works by rebooting the device and halting the boot process at the MediaTek preloader. Once halted at the preloader we can use the preloader binary API to send a series of MMC commands to the flash chip which allows 512 byte blocks to be read and written using a simple FIFO. Since we have both the original and modified system images we can generate a list of blocks that are different between the two images and only patch those blocks. This means we need to write less than 10 MB instead of 1.2 GB. If we had to send the entire system image at the speeds the preloader is limited to it would take about 2 weeks. If for some reason the system partition becomes unbootable that would be your only option to recover right now. By sending just the differences the patching only takes about 2 hours. There are ways to speed this up (about 5-10 minutes instead), but you'd need to obtain limited root access first using a much much more complicated procedure. I choose to provide instead a slower but much simpler series of commands.
The MT preloader is a process that runs before the regular bootloader (lk/fastboot) and of course before the kernel boots. It only shows up for about 3 seconds. Unfortunately the preloader is writable and could potentially be updated. The entire boot chain is cryptographically signed from what I've been able to inspect including the preloader. An unlocked bootloader would most likely be needed to flash a custom kernel (no kexec built-in of course, but modules/device drivers can be loaded) and create ROMs not based on stock. @rbox has been working on getting kexec working as a module but no ETA yet. So in conclusion the tools here allow you to modify the flash contents and using these facilities we have add SuperSU binaries to the system partition.
Anyone interested in how root was obtained should look at the history starting with this post. You should also read the README file from the aftv2-tools git repo. Also feel free to PM me if you have any questions.
Tips
If you want to disable the pop-up message when becoming root you can change notify=1 to notify=0 in /data/data/eu.chainfire.supersu/files/supersu.cfg. You need to reboot the device after making this change. It's also suggested to make the file read-only because it seems to get reset sometimes. (Thanks @ultimate_spy_binns)
Special Thanks
@qwertytical
@budokaiboy

great news
i never powered on my unit - awaiting root
can we have a 5.0.3.1 image to safely flash before root
otherwise the system might update to different version
now that rooting is out
amazon might be quick ...

reiteravi said:
great news
i never powered on my unit - awaiting root
can we have a 5.0.3.1 image to safely flash before root
otherwise the system might update to different version
now that rooting is out
amazon might be quick ...
Click to expand...
Click to collapse
Yeah, mine pre-ordered one is still in a box so I'd need to update it too. I guess I can do that tonight before a new version comes out.

reiteravi said:
great news
i never powered on my unit - awaiting root
can we have a 5.0.3.1 image to safely flash before root
otherwise the system might update to different version
now that rooting is out
amazon might be quick ...
Click to expand...
Click to collapse
Unfortunately you will need to do a normal update first before patching the system partition. It just takes too long to flash a full system image, original or modified, using the methods we have available to us now. Also the boot partition and other partitions are updated with each OTA. I hope we can continue to provide rooted versions of updated system images, but as you know there is no guarantee of that. I'd update now before there is any new updates and then root it. We could in theory root the older versions as well and even before first boot, but without the OTA updates and applying them in reverse I can't go back and patch the older releases. I strongly think the method used to write the system partition can not be fixed since I believe the preloader code is in a ROM.

Mac Update
A few notes for Mac users willing to experiment a little:
I installed python 3.5.0 for Mac OS X from python.org and then ran "sudo pip3 install pyserial" to install pyserial for python 3.x. The final change I needed to make was to change PORT in handshake.py and read_mmc.py/write_mmc.py (only tested reading the boot partition, but everything else should work). In my case the PORT was /dev/cu.usbmodem1430. The device filename seems to be based on the USB port it's connected to. I'm not sure if there is an easier way to find the device filename besides scanning /dev and looking for new devices matching a given pattern. Maybe others on this forum have some better ideas. The final caveat was I need to unplug and replug the USB cable after the handshake completed otherwise the read_mmc.py script would hang on the first read.

I succeeded in rooting mine! For comparison purposes, here's the md5sums of my partitions:
Code:
0e450c032ddce170667ba3ddc26cb960 DKB
a3ad800f012a153953b403ef1fa36e14 EXPDB
d693da95eb68b40e4315333bcf74918b KB
50f24ce4c7ac388b33310bff6f79636a LOGO
59071590099d21dd439896592338bf95 MISC
f9b5ef697fde92c42bbbec35e5a6cad4 PRO_INFO
8a9d058f87711c2e8ccc698647f5026b TEE1
eda2733e1d0214873d9cb9d78c68425f TEE2
97a2ccdb7a02838b26b9a57e4f31d51d boot
fbd20aa58cd63c07392080cad7627e18 lk
74f0bac463bae8141acf20594987a559 recovery
a06c3d6a8c73923ed5c38b479c4410d3 system
So my DKB, KB, and system partitions are different from yours.

NaturalBornHaxor said:
I succeeded in rooting mine! For comparison purposes, here's the md5sums of my partitions:
Code:
0e450c032ddce170667ba3ddc26cb960 DKB
a3ad800f012a153953b403ef1fa36e14 EXPDB
d693da95eb68b40e4315333bcf74918b KB
50f24ce4c7ac388b33310bff6f79636a LOGO
59071590099d21dd439896592338bf95 MISC
f9b5ef697fde92c42bbbec35e5a6cad4 PRO_INFO
8a9d058f87711c2e8ccc698647f5026b TEE1
eda2733e1d0214873d9cb9d78c68425f TEE2
97a2ccdb7a02838b26b9a57e4f31d51d boot
fbd20aa58cd63c07392080cad7627e18 lk
74f0bac463bae8141acf20594987a559 recovery
a06c3d6a8c73923ed5c38b479c4410d3 system
So my DKB, KB, and system partitions are different from yours.
Click to expand...
Click to collapse
That is awesome news! The first confirmed case I've heard of someone else repeating my success
About the DKB and KB partitions being different it makes me wonder what those partitions are for? I didn't include cache and userdata in the MD5SUM of course, which you noticed, because those change all the time. NVRAM when I looked inside appeared to have a few things that looked to be device specific. The system partition being different is actually expected because I found every time I rebooted my system partition changed checksums. Also that is the MD5SUM of the unmodified system partition. I noticed this weird MD5SUM behavior when I was first gaining root and doing some sanity checks. It happens right after daemonsu is started. My best guess is that the SuperSU tools mount the system r/w quickly and that causes the last mounted timestamp to change. Don't know for sure what causes it, but don't worry that's not unexpected. The main reason I kept those hashes in the repo was so when the next version comes out I know which partitions were changed and need to be updated by users who wish to maintain root.

------------------SOLVED-----------------
Please read on if you have problems with handshake script looping forever...
-----------------------------------------------
Hi zeroepoch,
meanwhile I received my Fire TV 2 and tried your scripts but unfortunately without success.
As far as I can see, there are 2 problems:
- The /dev/ttyACM0 device appears on rebooting the Fire TV, but only for some 100th of a second, then it disconnects again.
- If I give it another try, the device will appear as /dev/ttyACM1, next time /dev/ttyACM2, aso.. So I either have to update the handshake script for every try or reboot my computer (then it starts with /dev/ttyACM0 again).
When I first tried it, the handshake-script ran forever, it just missed the short time of availability of /dev/ttyACM0. So I reduced the sleep-timeout in the script from 0.25 to 0.001. Now the handshake script detects the serial device but runs into an I/O Error during one of the next steps (each time different, seems to be a "race condition").
Can you offer any advice? Could my Laptop be too slow somehow or is there some trick to make the Fire TV keep the port open for a longer time?
Greetings, Christian
Code:
shell:
[email protected]:~/aftv2-tools# adb reboot ; ./handshake.py
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Traceback (most recent call last):
File "./handshake.py", line 17, in <module>
dev = serial.Serial(PORT, BAUD)
File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 261, in __init__
self.open()
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 282, in open
self._reconfigurePort()
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 413, in _reconfigurePor t
termios.tcsetattr(self.fd, TERMIOS.TCSANOW, [iflag, oflag, cflag, lflag, ispeed, ospeed , cc])
termios.error: (5, 'Input/output error')
Code:
/var/log/syslog;
Nov 11 11:25:41 DeepThought systemd[1111]: Reached target Default.
Nov 11 11:25:41 DeepThought systemd[1111]: Startup finished in 15ms.
Nov 11 11:27:28 DeepThought kernel: [ 217.460463] usb 8-2: USB disconnect, device number 2
Nov 11 11:27:31 DeepThought kernel: [ 220.608049] usb 8-2: new high-speed USB device number 3 using ehci-pci
Nov 11 11:27:31 DeepThought kernel: [ 220.741857] usb 8-2: New USB device found, idVendor=0e8d, idProduct=2000
Nov 11 11:27:31 DeepThought kernel: [ 220.741860] usb 8-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Nov 11 11:27:31 DeepThought kernel: [ 220.741862] usb 8-2: Product: MT65xx Preloader
Nov 11 11:27:31 DeepThought kernel: [ 220.741864] usb 8-2: Manufacturer: MediaTek
Nov 11 11:27:31 DeepThought mtp-probe: checking bus 8, device 3: "/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-2"
Nov 11 11:27:31 DeepThought mtp-probe: bus: 8, device: 3 was not an MTP device
Nov 11 11:27:31 DeepThought kernel: [ 220.855737] cdc_acm 8-2:1.1: ttyACM0: USB ACM device
Nov 11 11:27:31 DeepThought kernel: [ 220.884047] usbcore: registered new interface driver cdc_acm
Nov 11 11:27:31 DeepThought kernel: [ 220.884050] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Nov 11 11:27:31 DeepThought kernel: [ 220.924931] usb 8-2: USB disconnect, device number 3
Nov 11 11:27:31 DeepThought ModemManager[511]: <warn> (ttyACM0): tcgetattr() error: 5
Nov 11 11:27:31 DeepThought ModemManager[511]: <warn> (ttyACM0): port attributes not fully set
Nov 11 11:27:31 DeepThought kernel: [ 220.928861] cdc_acm 8-2:1.1: failed to set dtr/rts
Nov 11 11:27:31 DeepThought ModemManager[511]: <info> (tty/ttyACM0): released by modem /sys/devices/pci0000:00/0000:00:1d.7/usb8/8-2
Nov 11 11:27:31 DeepThought ModemManager[511]: <warn> (Plugin Manager) (Cinterion) [ttyACM0] error when checking support: '(Cinterion) Missing port probe for port (tty/ttyACM0)'
Nov 11 11:27:31 DeepThought ModemManager[511]: <warn> (Plugin Manager) (Nokia) [ttyACM0] error when checking support: '(Nokia) Missing port probe for port (tty/ttyACM0)'
Nov 11 11:27:31 DeepThought ModemManager[511]: <warn> (Plugin Manager) (Iridium) [ttyACM0] error when checking support: '(Iridium) Missing port probe for port (tty/ttyACM0)'
Nov 11 11:27:31 DeepThought ModemManager[511]: <warn> (Plugin Manager) (Generic) [ttyACM0] error when checking support: '(Generic) Missing port probe for port (tty/ttyACM0)'
Nov 11 11:27:33 DeepThought ModemManager[511]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-2': not supported by any plugin
Nov 11 11:27:35 DeepThought wpa_supplicant[837]: nl80211: send_and_recv->nl_recvmsgs failed: -33
Nov 11 11:27:36 DeepThought kernel: [ 226.092142] usb 8-2: new high-speed USB device number 4 using ehci-pci
Nov 11 11:27:37 DeepThought kernel: [ 226.225936] usb 8-2: New USB device found, idVendor=1949, idProduct=0241
Nov 11 11:27:37 DeepThought kernel: [ 226.225945] usb 8-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Nov 11 11:27:37 DeepThought kernel: [ 226.225951] usb 8-2: Product: FireTV
Nov 11 11:27:37 DeepThought kernel: [ 226.225956] usb 8-2: Manufacturer: Amazon
Nov 11 11:27:37 DeepThought kernel: [ 226.225961] usb 8-2: SerialNumber: G070GV05544205DE
Nov 11 11:27:37 DeepThought mtp-probe: checking bus 8, device 4: "/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-2"
Nov 11 11:27:37 DeepThought mtp-probe: bus: 8, device: 4 was an MTP device
After taking a closer look at my syslog and doing some research on problems with /dev/ttyACM0, I finally found the problem. It's the modemmanager. That service immmediately "grabs" the device and tries to do some invalid settings, which leads to an near immediate disconnect.
After I uninstalled the modemmanger (which seemed preinstalled in debian jessie, at least I never installed it on purpose) with
Code:
apt-get remove modemmanager
both of my problems were gone. The device stayed up for 3 seconds and after reboot of the Fire TV it had the same devicename /dev/ttyACM0 again. So I could undo my changes to the handshake script and had instant success with it.
Now I'll try rooting. WHOOT!

Thank you very much for your efforts!
I'd just like to check my understanding - are the instructions you posted comprehensive to obtaining root from absolute scratch?
I know soldering of eMMC and such things were used in development, but that is not needed now after you've done the hard work, correct?
I can just follow your steps above and root the FTV2?

gu3stZA said:
Thank you very much for your efforts!
I'd just like to check my understanding - are the instructions you posted comprehensive to obtaining root from absolute scratch?
I know soldering of eMMC and such things were used in development, but that is not needed now after you've done the hard work, correct?
I can just follow your steps above and root the FTV2?
Click to expand...
Click to collapse
Yes, you're right. No need to solder anything. You just need the tools stated in the instructions.
Hardware:
- a computer running Linux (or something very close)
- a A to A USB cable
Software:
- python3 and python3-serial packages
- adb package (not necessary but recommended)
- zeroepochs scripts and patchfiles
That said, a certain amount of base knowledge regarding Linux doesn't hurt .

Thanks! I've played around with Linux but would definitely classify myself as a beginner. I guess we'll see how user-friendly the instructions are

This is good news, definitely progress, could this be integrated into ADBFire for windows

Jay794 said:
This is good news, definitely progress, could this be integrated into ADBFire for windows
Click to expand...
Click to collapse
This would be perfect. Or even adb. I've just never used Linux

zeroepoch said:
It has only been tested on a US device and I don't know at this point if non US devices are different, maybe not.
Click to expand...
Click to collapse
Hi zeroepoch,
I just used your rooting scripts successfully on a non US (in my case German) version of the Fire TV 2!
Greets,
Christian

skyball2 said:
Hi zeroepoch,
I just used your rooting scripts successfully on a non US (in my case German) version of the Fire TV 2!
Greets,
Christian
Click to expand...
Click to collapse
Thanks for the feedback. Glad to hear it worked!

Successful root under arch Linux! Thanks for your hard work.

By any chance does this root work for the original fire TV ?
Sent from my SM-N910F using Tapatalk

Savage13 said:
By any chance does this root work for the original fire TV ?
Click to expand...
Click to collapse
No. It's MediaTek specific. It may work on most MediaTek devices though.

how can u tell handshake is ok and start patching ?

reiteravi said:
how can u tell handshake is ok and start patching ?
Click to expand...
Click to collapse
It will print "Handshake Complete". Also the serial device will remain present rather than disappear after a few seconds.

[HOW TO] Unbrick Kindle Fire HDX (QHUSB_BULK) with firmware <=1314.3.2.6

First of all - this is works only if you bricked on firmware <=1314.3.2.6.
So it don't works for "rollbacked 3.2.8(7)" bricks(
Sorry but need leak of newest version of flash programmer for higher sw.
I understand that there is not many people with this type of bricks but it is better that nothing=)
Of course you can try - you can not do worse=) I test this method on 13.3.2.3 and 13.3.2.4.
Apollo users should read post to the end before doing anything!
Manual in progress. Additions and comments are appreciated.
Logs of flasher to examine errors locates at C:\Program Files(X86)\Xiaomi\MiPhone\
My English isn't perfect) - PM me with OP corrections.
​
1. Download archive - https://drive.google.com/file/d/0B2twXJIOgv-UR0dZTVJUeFFsVU0/view?usp=sharing and unpack it. Two folders inside - fw and tools.
2. Install ./tools/MiPhone2015731.exe
2a. For x64 system you need disable drivers signature verification before installing. Google it.
3. Start and setup Miflash:
3a. Press 'Browse' and select folder "fw" from archive. Press OK.
3b. Press down arrow on this button, Press "Advanced" and fill fields with files in folder 'fw' by "Browse" :
- flashprogrammer - .\fw\prog_emmc_firehose_8974.mbn
- raw xml file - .\fw\rawprogram0.xml
- patch xml file - .\fw\patch0.xml
- other fields no need to touch
{
"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"
}
4. Ok. Now you need put your device in QHSUSB Bulk - mode and install Drivers.
4a. Your device can be in this state already. Just connect it to PC.
4b. If you have working adb (who knows) - type "adb reboot oem-2" or "adb reboot emergency" in cmd (i suppose you know that is adb drivers and adb). This is reboot kindle into emergency mode Qdloader 9008.
4c. Your device is stucked at greylogo or bootlooping without adb access. You need fastboot cable. Reboot device with plugged fastboot-cable.
5. Navigate to device manager and check for new device named QHSUSB_BULK . Drivers will install automatically or you need install it manually from .\tools\QualcommDrv.
In device manager at COM-Ports section you must obtain HS-USB Qdloader 9008 (COMx) without exclamation!
6. Go to Miflash , press Refresh, you should see your com port and empty bar under "progress" section.
7. Press "Flash". You should see messages like "WriteFile position 0x00000000840000, size 131072"
8. If all gone successfully disconnect kindle from PC and reboot it by holding power+vol up.
8a. If unsuccessful - reboot device and start over. In this mode for reboot sometimes needs above 5 min holding of power button.
If you get "Opening port" after some loading - you probably have > 1314.3.2.6 fw version.
9. Grats. You are in TWRP. You could flash stock 1314.3.2.3 firmware renaming bin to zip. Do not forget to block OTA immediately!
10. BTW you aboot partition is 13.3.2.3 version so you can do procedure of unlock without downgrading to 13.3.2.3 - http://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Apollo users !!! - you need to replace recovery.img and emmc_appsboot.mbn with these (rename twrp and aboot_vuln).
CREdits:
bournezhang - for leaked programmer.
FSmp - for testing at 13.3.2.4
For advanced users - this works with any unlocked devices too (aboot<= 13.2.3.2).
By filling "filename" at rawprogram0.xml you can flash any partition to your device. Big partition like system.img must be sparsed I assume and rawprogram0 need to correct.
Of course all of it could be done with dd or maybe with fastboot. But just FYI.
ps. Anyone who knows something about newest version of emmcbld.mbn or lab126 insiders =) feel free to send anonymous e-mail to 2457678atgmaildotcom. Thank you.

Reserved

sorry，I don't have the newest version.
i think we can only get it from lab126 or amazon.
by the way, in factory ,they have to flash the device to a special mode， and then reflash all the system images.

ONYXis said:
Reserved
Click to expand...
Click to collapse
Hope these files can help you. they are old version

bournezhang said:
Hope these files can help you. they are old version
Click to expand...
Click to collapse
Thank you. I already have it. Nothing interesting.

bournezhang said:
by the way, in factory ,they have to flash the device to a special mode， and then reflash all the system images.
Click to expand...
Click to collapse
there is no any difference, i use same protocol as Amazon. i can make fullflash instructions with system, cache, userdata, but I see no sense of this. just bigger download size - approx 2.5 GB.
With twrp you can flash what you want by yourself.

But most user's version is 4.5.2 or higher now .
Look forward this issue be solved.

really nice job

@FotixChiang , thanks. btw maybe "our friend" with that dev 4.1.1 firmare has this file for 4.x ?

I just followed your steps, but when I flashed the program failed. I then reset my device, but it no longer recognizes it as QHUSB BULK. All it says is "Unknown USB Device (Descriptor Request Failed)". Any ideas on how to get it back into QDLoader mode for another shot at flashing?

Hold power button long. Above 5 min sometimes. It always works.

ONYXis said:
First of all - this is works only if you bricked on firmware <=1314.3.2.6.
So it don't works for "rolbacked 3.2.8(7)" bricks(
Sorry but need leak of newest version of flash programmer for higher sw.
I understand that there is not many people with this type of bricks but it is better that nothing=)
Of course you can try - you can not do worse=) I test this method on 13.3.2.3 and 13.3.2.4.
Apollo users should read post to the end before doing anything!
Manual in progress. Additions and comments are appreciated.
Logs of flasher to examine errors locates at C:\Program Files(X86)\Xiaomi\MiPhone\
My English isn't perfect) - PM me with OP corrections.
​
1. Download archive - https://drive.google.com/file/d/0B2twXJIOgv-UR0dZTVJUeFFsVU0/view?usp=sharing and unpack it. Two folders inside - fw and tools.
2. Install ./tools/MiPhone2015731.exe
2a. For x64 system you need disable drivers signature verification before installing. Google it.
3. Start and setup Miflash:
3a. Press 'Browse' and select folder "fw" from archive. Press OK.
3b. Press down arrow on this button, Press "Advanced" and fill fields with files in folder 'fw' by "Browse" :
- flashprogrammer - .\fw\prog_emmc_firehose_8974.mbn
- raw xml file - .\fw\rawprogram0.xml
- patch xml file - .\fw\patch0.xml
- other fields no need to touch
4. Ok. Now you need put your device in QHSUSB Bulk - mode and install Drivers.
4a. Your device can be in this state already. Just connect it to PC.
4b. If you have working adb (who knows) - type "adb reboot oem-2" or "adb reboot emergency" in cmd (i suppose you know that is adb drivers and adb). This is reboot kindle into emergency mode Qdloader 9008.
4c. Your device is stucked at greylogo or bootlooping without adb access. You need fastboot cable. Reboot device with plugged fastboot-cable.
5. Navigate to device manager and check for new device named QHSUSB_BULK . Drivers will install automatically or you need install it manually from .\tools\QualcommDrv.
In device manager at COM-Ports section you must obtain HS-USB Qdloader 9008 (COMx) without exclamation!
6. Go to Miflash , press Refresh, you should see your com port and empty bar under "progress" section.
7. Press "Flash". You should see messages like "WriteFile position 0x00000000840000, size 131072"
8. If all gone successfully disconnect kindle from PC and reboot it by holding power+vol up.
8a. If unsuccessful - reboot device and start over. In this mode for reboot sometimes needs above 5 min holding of power button.
If you get "Opening port" after some loading - you probably have > 1314.3.2.6 fw version.
9. Grats. You are in TWRP. You could flash this stock 1314.4.5.5 image - http://forum.xda-developers.com/kindle-fire-hdx/development/twrp-flashable-stock-images-t3194914
10. BTW you aboot partition is 13.3.2.3 version so you can do procedure of unlock without downgrading to 13.3.2.3 - http://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Apollo users !!! - you need to replace recovery.img at folder "fw" with this one - https://drive.google.com/file/d/0B2twXJIOgv-UYzhORVczQ3E3cWM/view?usp=sharing
CREdits:
bournezhang - for leaked programmer.
FSmp - for testing at 13.3.2.4
For advanced users - this works with any unlocked devices too (aboot<= 13.2.3.2).
By filling "filename" at rawprogram0.xml you can flash any partition to your device. Big partition like system.img must be sparsed I assume and rawprogram0 need to correct.
Of course all of it could be done with dd or maybe with fastboot. But just FYI.
ps. Anyone who knows something about newest version of emmcbld.mbn or lab126 insiders =) feel free to send anonymous e-mail to 2457678atgmaildotcom. Thank you.
Click to expand...
Click to collapse
Great job bro. About one year ago I was reading many posts on this forum to get enough information to unbrick my Kindle Fire HDX (stuck on grey logo). by reading most of the posts related to Kindle Fire HDX I found out that the only way to unbrick it was a FactoryCable/ FastbootCable. so I made a factory cable and got my Kindle be recognised by my PC as Qdloader 9008 or Qcomm HS-USB Bulk or something like that. but after that I did not know how to flash files on it so my KFHDX was taking rest till today
thanks to you that I am able to revive it now thanks again. I have a lot of usefull files and information including some interesting drivers which might help you create tools or find other methods to unbrick the KFHDX. if you need some help or files just drop me a message to my inbox. I will be checking it frequently thank you

it's really worked method!
I restored gray logo (QHUSB_BULK) 3rd HDX 8.9 Apollo. I have been waiting this for 2 years))
the only thing I have not load the firmware http://forum.xda-developers.com/kindle-fire-hdx/development/twrp-flashable-stock-images-t3194914 - it's not loaded
http://forum.xda-developers.com/kin...ent/rom-cm-12-unofficial-apollo-thor-t3050199 - it's work
BIG THX!

Thanks for response. I'll edit manual soon.

ONYXis said:
Thanks for response. I'll edit manual soon.
Click to expand...
Click to collapse
I congratulate you for your work and effort.
you are very good

need help.. I did the roll back, re-installed 4.5.2. 4.5.2 is now rooted. I followed the disable OTA instructions in the forum, (rename the file etc...)..
However that information may not be totally correct, because as soon as I connected to Wi Fi , kindle fire stated downloading 4.5.4. I shut the Wi Fi off, found another tutorial on disabling OTA updates. This one worked. However, I have a 100% downloaded update, and I'm fearful it will try to install itself. I need to know where to go with ES File Explorer to Delete this update file, so it does not install itself.
Thanks to all who can help.

why are you posted this here?
anyway, update file locates in /cache. need root to navigate there.
please do not offtop in this thread. thank you.

rlkellyjr said:
need help.. I did the roll back, re-installed 4.5.2. 4.5.2 is now rooted. I followed the disable OTA instructions in the forum, (rename the file etc...)..
However that information may not be totally correct, because as soon as I connected to Wi Fi , kindle fire stated downloading 4.5.4. I shut the Wi Fi off, found another tutorial on disabling OTA updates. This one worked. However, I have a 100% downloaded update, and I'm fearful it will try to install itself. I need to know where to go with ES File Explorer to Delete this update file, so it does not install itself.
Thanks to all who can help.
Click to expand...
Click to collapse
Third duplicate post in as many threads. Great way NOT to get noticed next time you need help.

I guess I should say thanks for the point in the right direction, but you coming across and telling me in different areas is not a way to get help. I posted in the wrong area to start with, and was told so. So thanks for the help.
---------- Post added at 11:33 PM ---------- Previous post was at 11:32 PM ----------
[/COLOR]
Davey126 said:
Third duplicate post in as many threads. Great way NOT to get noticed next time you need help.
Click to expand...
Click to collapse

Ali Ejea Mc said:
Great job bro. About one year ago I was reading many posts on this forum to get enough information to unbrick my Kindle Fire HDX (stuck on grey logo). by reading most of the posts related to Kindle Fire HDX I found out that the only way to unbrick it was a FactoryCable/ FastbootCable. so I made a factory cable and got my Kindle be recognised by my PC as Qdloader 9008 or Qcomm HS-USB Bulk or something like that. but after that I did not know how to flash files on it so my KFHDX was taking rest till today
thanks to you that I am able to revive it now thanks again. I have a lot of usefull files and information including some interesting drivers which might help you create tools or find other methods to unbrick the KFHDX. if you need some help or files just drop me a message to my inbox. I will be checking it frequently thank you
Click to expand...
Click to collapse
Good evening: I have an Apollo HDX that is an continuous gray and yellow splash screen when booted.
I have no idea what OS version it is running since it has been a long while setting in my junk pile.
I also do not know the history of the HDX since I acquired the unit second hand.
It sounds like there is some hope for recovery?
Can someone point me in the right direction for getting this unit resurrected?
On my LINUX workstation I do not see any logging when plugged in using a standard USB cable:
However, when a Kindle fire HD factory cable (2012 HD Fastboot cable) is used to connect to the HDX, I receive this logging:
Jan 31 20:38:43 me-9100 kernel: [193518.636064] usb 1-4: new high-speed USB device number 12 using ehci-pci
Jan 31 20:38:43 me-9100 kernel: [193518.768771] usb 1-4: New USB device found, idVendor=05c6, idProduct=9008
Jan 31 20:38:43 me-9100 kernel: [193518.768779] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 31 20:38:43 me-9100 kernel: [193518.768784] usb 1-4: Product: QHSUSB__BULK
Jan 31 20:38:43 me-9100 kernel: [193518.768789] usb 1-4: Manufacturer: Qualcomm CDMA Technologies MSM
Jan 31 20:38:43 me-9100 kernel: [193518.769693] qcserial 1-4:1.0: Qualcomm USB modem converter detected
Jan 31 20:38:43 me-9100 kernel: [193518.769908] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB0
Jan 31 20:38:43 me-9100 mtp-probe: checking bus 1, device 12: "/sys/devices/pci0000:00/0000:00:04.1/usb1/1-4"
Jan 31 20:38:43 me-9100 mtp-probe: bus: 1, device: 12 was not an MTP device
Jan 31 20:38:43 me-9100 kernel: [193518.636064] usb 1-4: new high-speed USB device number 12 using ehci-pci
Jan 31 20:38:43 me-9100 kernel: [193518.768771] usb 1-4: New USB device found, idVendor=05c6, idProduct=9008
Jan 31 20:38:43 me-9100 kernel: [193518.768779] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 31 20:38:43 me-9100 kernel: [193518.768784] usb 1-4: Product: QHSUSB__BULK
Jan 31 20:38:43 me-9100 kernel: [193518.768789] usb 1-4: Manufacturer: Qualcomm CDMA Technologies MSM
Jan 31 20:38:43 me-9100 kernel: [193518.769693] qcserial 1-4:1.0: Qualcomm USB modem converter detected
Jan 31 20:38:43 me-9100 kernel: [193518.769908] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB0
Jan 31 20:38:43 me-9100 mtp-probe: checking bus 1, device 12: "/sys/devices/pci0000:00/0000:00:04.1/usb1/1-4"
Jan 31 20:38:43 me-9100 mtp-probe: bus: 1, device: 12 was not an MTP device
When USB is disconnected:
Jan 31 20:40:16 me-9100 kernel: [193612.201809] usb 1-4: USB disconnect, device number 12
Jan 31 20:40:16 me-9100 kernel: [193612.202101] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
Jan 31 20:40:16 me-9100 kernel: [193612.202128] qcserial 1-4:1.0: device disconnected
Is the factory cable mentioned in this post the same factory cable used on the 2012 Kindle Fire HD?
I have worked on hundreds of the 2012 HD fires but, don't do anything with the HDX devices since they can't be bootloader unlocked. However, I would like to bring the HDX back to life it is possible. The tools for the HDX I see in this and other posts are for windows I presume and not LINUX?
Any help and direction would be helpful:::
Regards

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!

[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