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
--

Yoga 2 8' - 830L - probably erase bootloader - HELP !

hello, I hope that I write in the right place and I will not be scolded.
I have a big problem. I'll start from the beginning.
I did root my tablet and everything was OK.
Before root I made data backup in TWRP recovery.
I used a moment then something began to manifest errors.
That's why I thought that restore backup.
Everything I've done with the use 'IntelAndroid-FBRL-07-24-2015'.
When I restored a backup system will not boot.
He hang on the logo LENOVO and after a while tablet restarted.
I thought that restore everything as it was at the factory.
I downloaded "YT2-830L_USR_S000067_1410301707_WW21_ROW" and I launched the program "PhoneFlashTool_4.4.4.1_external_win32".
At the beginning everything was ok.
Then there was about 50/60 percent and jumped an error.. Unfortunately, I do not remember what.
The device was restarts and and appeared logo LENOVO + Subtitles "Boot Failed. EFI HARD DRIVE" "Boot Succeed - enter startup"
and then pops up
"VALLEYVIEW C0 PLATFORM
INTEL (R) ATOM ....
...
...
CONTINUE
SELECT LANGUAGE
> BOOT MANAGER
> DEVICE MANAGER
> BOOT MAINTANCE MANAGER
"
I tried again to upload the original tablet software..
and so it looked like:
"12/25/15 23:18:44.251 INFO : Phone Flash Tool V 4.4.4-1 Win32 External (build on Mon Apr 28 09:56:35 UTC 2014)
12/25/15 23:18:44.251 INFO : Using xFSTK version: 1.5.3
12/25/15 23:18:44.361 INFO : Using Android Debug Bridge version 1.0.31
12/25/15 23:18:44.361 INFO : OS version detected: Windows 8 (x64)
12/25/15 23:18:44.580 INFO : Adb and fastboot binaries OK
12/25/15 23:18:44.580 INFO : Phone Flash Tool initialized successfully
12/25/15 23:18:44.595 INFO : Loading Flash file ...
12/25/15 23:18:44.595 INFO : Ready to flash!
12/25/15 23:19:28.233 INFO : Loading Flash file (C:/Users/X/Desktop/FLASH_LENOVO/YT2-830L_USR_S000067_1410301707_WW21_ROW/YT2-830L_USR_S000067_1410301707_WW21_ROW/YT2_8_row_lte-blankphone-user-YT2-830L_USR_S000067_1410301707_WW21_ROW/flash.xml)
12/25/15 23:19:28.233 INFO : GP_Flag is set to 0x80000045
12/25/15 23:19:28.249 INFO : Ready to flash!
12/25/15 23:19:30.689 INFO : Port 1/1: Flashing OS
12/25/15 23:19:30.689 INFO : Port 1/1: fastboot -s BaytrailF0B3F8A3 -S 500M flash osloader "C:/Users/X/Desktop/FLASH_LENOVO/YT2-830L_USR_S000067_1410301707_WW21_ROW/YT2-830L_USR_S000067_1410301707_WW21_ROW/YT2_8_row_lte-blankphone-user-YT2-830L_USR_S000067_1410301707_WW21_ROW/efilinux.efi"
12/25/15 23:19:32.830 INFO : Port 1/1: fastboot -s BaytrailF0B3F8A3 -S 500M boot "C:/Users/X/Desktop/FLASH_LENOVO/YT2-830L_USR_S000067_1410301707_WW21_ROW/YT2-830L_USR_S000067_1410301707_WW21_ROW/YT2_8_row_lte-blankphone-user-YT2-830L_USR_S000067_1410301707_WW21_ROW/droidboot.img"
12/25/15 23:19:35.537 INFO : Port 1/1: sleep 25000 ms"
AND THE TABLET RESTART AND SEE AGAIN WINDOW
"VALLEYVIEW C0 PLATFORM
INTEL (R) ATOM ....
...
...
CONTINUE
SELECT LANGUAGE
> BOOT MANAGER
> DEVICE MANAGER
> BOOT MAINTANCE MANAGER
"
(in THE PROGRAMME IS 23 %)
So I run again tablet and TO FASTBOOT AND IN THE PROGRAM POPS ERROR
"12/25/15 23:20:00.538 INFO : Port 1/1: fastboot -s BaytrailF0B3F8A3 -S 500M oem wipe ESP
12/25/15 23:23:32.881 WARNING: Port 1/1: Failed to execute ""C:/Program Files (x86)/Intel/Phone Flash Tool/fastboot.exe" -s BaytrailF0B3F8A3 -S 500M oem wipe ESP":
< waiting for device >
...
FAILED (remote: unknown command)
finished. total time: 0.003s
12/25/15 23:23:34.884 WARNING: Port 1/1: Retry to execute fastboot -s BaytrailF0B3F8A3 -S 500M oem wipe ESP
12/25/15 23:23:34.978 WARNING: Port 1/1: Failed to execute ""C:/Program Files (x86)/Intel/Phone Flash Tool/fastboot.exe" -s BaytrailF0B3F8A3 -S 500M oem wipe ESP":
...
FAILED (remote: unknown command)
finished. total time: -0.000s
12/25/15 23:23:36.994 WARNING: Port 1/1: Failed to execute non mandatory command fastboot -s BaytrailF0B3F8A3 -S 500M oem wipe ESP, ignoring error
12/25/15 23:23:36.994 INFO : Port 1/1: fastboot -s BaytrailF0B3F8A3 -S 500M oem start_partitioning
12/25/15 23:23:37.088 WARNING: Port 1/1: Failed to execute ""C:/Program Files (x86)/Intel/Phone Flash Tool/fastboot.exe" -s BaytrailF0B3F8A3 -S 500M oem start_partitioning":
...
FAILED (remote: unknown command)
finished. total time: 0.000s
12/25/15 23:23:39.098 WARNING: Port 1/1: Retry to execute fastboot -s BaytrailF0B3F8A3 -S 500M oem start_partitioning
12/25/15 23:23:39.207 WARNING: Port 1/1: Failed to execute ""C:/Program Files (x86)/Intel/Phone Flash Tool/fastboot.exe" -s BaytrailF0B3F8A3 -S 500M oem start_partitioning":
...
FAILED (remote: unknown command)
finished. total time: -0.000s
12/25/15 23:23:41.223 ERROR : Port 1/1: Flash failure"
ON THE TABLET IS "FASTBOOT STARTING ..."
when I choose continue on this screen
VALLEYVIEW C0 PLATFORM
INTEL (R) ATOM ....
...
...
CONTINUE
SELECT LANGUAGE
> BOOT MANAGER
> DEVICE MANAGER
> BOOT MAINTANCE MANAGER"
i see this window WHERE WRITE:
"BOOT FAILED. EFI HARD DISK"
"BOOT SUCCEED - ENTER SETUP"
if anyone knows how to solve , how to restore the tablet to work please help !!!
SORRY I did not give photos, but I'm new and I could not INSERT...

progdvb said:
hello, I hope that I write in the right place and I will not be scolded.
Click to expand...
Click to collapse
you were on Lollipop when you bricked and now you are trying to flash a kitkat rom, this will not work as the kiktak rom files (IA32) pushed by the Phone Flash tool are not recognized by the Lollipop bios (x64).
since there is no publicly available (leaked) lollipop stock rom for the 830L model you will have to:
1. downgrade first your bios to the kitkat version using the steps in here, do the steps in 'how to use'
2. now flash your kitkat stock rom, remember to set your country code when finished flashing, on your first boot, or you will fail in the future when attempting to update using an OTA
3. optional, update to lollipop using the OTA when prompted by your (now) running kitkat android

ionioni said:
you were on Lollipop when you bricked and now you are trying to flash a kitkat rom, this will not work as the kiktak rom files (IA32) pushed by the Phone Flash tool are not recognized by the Lollipop bios (x64).
since there is no publicly available (leaked) lollipop stock rom for the 830L model you will have to:
1. downgrade first your bios to the kitkat version using the steps in here, do the steps in 'how to use'
2. now flash your kitkat stock rom, remember to set your country code when finished flashing, on your first boot, or you will fail in the future when attempting to update using an OTA
3. optional, update to lollipop using the OTA when prompted by your (now) running kitkat android
Click to expand...
Click to collapse
I tried this way now and the program stay in position "waiting for access to root shell".
It takes a fewww minutes...
in the video demo it quickly went...
what now?
ON THE TABLET IS WINDOW AND WRITE "CMD 'STOP_PARTITIONING' COMPLETE.

progdvb said:
I tried this way now and the program stay in position "waiting for access to root shell".
It takes a fewww minutes...
in the video demo it quickly went...
what now?
Click to expand...
Click to collapse
if it went to that point the bios restoring has not yet started (yet it confirms you are on lollipop bios) so you can close the tool exe window safely
this can mean one of these things:
1. (most likely) your drivers need to be reinstalled, download from here and install both files in the zip (accepting whatever it prompts you and using defaults) and reboot at the end your pc, then try again the downgrading the bios, if it still hangs on that 'waiting for root shell' try when you get ther and some seconds have passed to unplug and replug the usb to force a redetection of the new usb mode (windows does it automatically, never met a case where it didn't yet you can try it)
2. (unlikely) you are using windows in a virtual environment such as virtualbox or vmware (are you?) and it did not detected the usb changing mode, if that is the case (only if you are using windows in virtualbox, i doubt) unplug and replug the usb when it says 'waiting for root shell'
3. (almost impossible) your usb controller is bricked

I did reinstalling drivers.
Went two steps further.
[pc] transfering control to yogatab device for bios restoring.
AND Unfortunately, he jumped error:
adb server is out of date. killing...
abd server didnt ACK
*failed to start daemon *
error:

progdvb said:
I did reinstalling drivers.
Went two steps further.
[pc] transfering control to yogatab device for bios restoring.
AND Unfortunately, he jumped error:
adb server is out of date. killing...
abd server didnt ACK
*failed to start daemon *
error:
Click to expand...
Click to collapse
but the tablet rebooted?
NEVER POWER OFF YOUR TAB AFTER IT SAYS "TRANSFERING CONTROL" ALWAYS WAIT 4-5 MINUTES BEFORE TRYING TO REBOOT THE TAB IF YOU GOT DISCONNECTED SOMEHOW!
that means the bios restore could have been started and you must wait 4-5 minutes and ONLY if it doesn't reboot by itself in 4-5 minutes then you can try to reboot
you must take care with this as if the bios restore is started (and you were disconnected meaning no more messages from your tab) if you power off by force your tab you can hard-brick and nothing can be done to save it (you must send it to a service).
READ THE INSTRUCTIONS IN THE DOWNGRADING POST!
do this:
UNINSTALL everything: adb/fastboot, drivers installed in the past, Intel Phone Flash Tool, everything you installed related to the tab
REBOOT
INSTALL the two files provided in the link
REBOOT
TRY AGAIN to downgrade
also, you should use when flashing your kitkat a more recent stock rom (the one you used is old) download extract and use this (after you managed to downgrade the bios of course)

ionioni said:
but the tablet rebooted?
NEVER POWER OFF YOUR TAB AFTER IT SAYS "TRANSFERING CONTROL"
that means the bios restore could have been started and you must wait 4-5 minutes and ONLY if it doesn't reboot by itself in 4-5 minutes then you can try to reboot
you must take care with this as if the bios restore is started (and you were disconnected meaning no more messages from your tab) if you power off by force your tab you can hard-brick and nothing can be done to save it (you must send it to a service).
READ THE INSTRUCTIONS IN THE DOWNGRADING POST!
Click to expand...
Click to collapse
Yes, I wait 5-6minute and power off tablets.
he did not restarted itself.
Now I try uninstall, and install program and all drivers.
--------------------------------------------------------------------
OK,
I uninstalled and install anew driver, I open program and now is hang on
[pc] transfering control to yogatab device for bios restoring.
========================================
adb server is out of date. killing...
so this situation has been going 5min

progdvb said:
Yes, I wait 5-6minute and power off tablets.
he did not restarted itself.
Now I try uninstall, and install program and all drivers.
Click to expand...
Click to collapse
ok, read above i edited some stuff... the bios restoring is a safe process (as long as you don't do stupid things) but you have issues on your pc, solve them first
after you downgrade the bios use the stock rom i linked in the prev post for your kitkat stock rom flashing, the one you used is old (should work but you will wait forever after for the ota's)
---------- Post added at 11:24 ---------- Previous post was at 11:13 ----------
progdvb said:
Yes, I wait 5-6minute and power off tablets.
he did not restarted itself.
Now I try uninstall, and install program and all drivers.
--------------------------------------------------------------------
OK,
I uninstalled and install anew driver, I open program and now is hang on
[pc] transfering control to yogatab device for bios restoring.
========================================
adb server is out of date. killing...
so this situation has been going 5min
Click to expand...
Click to collapse
reboot and go to the intel phone flash tool folder C:\Program Files (x86)\Intel\Phone Flash Tool Lite and delete the adb.exe file inside and try again
you have some adb.exe (old) file that starts automatically and that makes things go wrong (have you uninstalled your stuff?) also make sure you run the exe as Administrator

ionioni said:
ok, read above i edited some stuff... the bios restoring is a safe process (as long as you don't do stupid things) but you have issues on your pc, solve them first
after you downgrade the bios use the stock rom i linked in the prev post for your kitkat stock rom flashing, the one you used is old (should work but you will wait forever after for the ota's)
---------- Post added at 11:24 ---------- Previous post was at 11:13 ----------
reboot and go to the intel phone flash tool folder C:\Program Files (x86)\Intel\Phone Flash Tool Lite and delete the adb.exe file inside and try again
you have some adb.exe (old) file that starts automatically and that makes things go wrong (have you uninstalled your stuff?) also make sure you run the exe as Administrator
Click to expand...
Click to collapse
OK, I used other computer. Its work.
Program passed with no errors.
Now I have to use 'Phone Flash Tool Lite',
upload a rom from the link you gave me and everything should be ok ?

progdvb said:
OK, I used other computer. Its work.
Program passed with no errors.
Now I have to use 'Phone Flash Tool Lite',
upload a rom from the link you gave me and everything should be ok ?
Click to expand...
Click to collapse
yes, use the rom i linked extract and flash from dnx mode ("fastboot starting" message on screen pwr+volup+voldown to start in dnx)

ionioni said:
yes, use the rom i linked extract and flash from dnx mode ("fastboot starting" message on screen pwr+volup+voldown to start in dnx)
Click to expand...
Click to collapse
when I had to choose a country that updates work later?
and how?
during the first run I introduced tablet in dialer ####6020# ?
next choose my country and tablet restart and next #### 59930# to check the chosen country?

progdvb said:
when I had to choose a country that updates work later?
and how?
during the first run I introduced tablet in dialer ####6020# ?
next choose my country and tablet restart and next #### 59930# to check the chosen country?
Click to expand...
Click to collapse
you open Contacts app and input there

ionioni said:
you open Contacts app and input there
Click to expand...
Click to collapse
OK. For now uploads a rom .
By the way, I ask yet .
Is it possible for me I've loaded rom that will allow me to call from the tablet?
I read this article but I could not quite understand everything
http://forum.xda-developers.com/thi...guide-make-lenovo-tablet-yoga-2-830l-t2950933
Do you know where can I download Lenovo Tablet Yoga 2 830LC to fit what you gave me?
the manual says to replace the file called "esp.img"..

progdvb said:
OK. For now uploads a rom .
By the way, I ask yet .
Is it possible for me I've loaded rom that will allow me to call from the tablet?
I read this article but I could not quite understand everything
http://forum.xda-developers.com/thi...guide-make-lenovo-tablet-yoga-2-830l-t2950933
Do you know where can I download Lenovo Tablet Yoga 2 830LC to fit what you gave me?
the manual says to replace the file called "esp.img"..
Click to expand...
Click to collapse
this is the 830LC stock kitkat rom flash it and see...

ionioni said:
this is the 830LC stock kitkat rom flash it and see...
Click to expand...
Click to collapse
THE TABLET IS WORKING !!!!!!
YOY are GREAT !!!!!!!!!!!!!!!!!!!!!!!!!!!!
Tell me again, which country should I choose for Polish ?
the same Chinese stamps and some strange abbreviations are...

progdvb said:
THE TABLET IS WORKING !!!!!!
YOY are GREAT !!!!!!!!!!!!!!!!!!!!!!!!!!!!
Tell me again, which country should I choose for Polish ?
the same Chinese stamps and some strange abbreviations are...
Click to expand...
Click to collapse
the abbreviations are the standard iso country alpha 2 letter code https://en.wikipedia.org/wiki/ISO_3166-1
if you don't have PL then chose a neighbour one, not sot important (this is not the language in which your Android interface will be shown that you can set with the Language on your Settings)

ionioni said:
the abbreviations are the standard iso country alpha 2 letter code https://en.wikipedia.org/wiki/ISO_3166-1
if you don't have PL then chose a neighbour one, not sot important (this is not the language in which your Android interface will be shown that you can set with the Language on your Settings)
Click to expand...
Click to collapse
ok . I found a country close to the Polish (germany)
if I set this country I will be able to use the system updates ?
I will be able to upgrade to 5.0 android?

progdvb said:
ok . I found a country close to the Polish (germany)
if I set this country I will be able to use the system updates ?
I will be able to upgrade to 5.0 android?
Click to expand...
Click to collapse
yes, as i told you is not so important, whatever you will chose you will be able to complete updates (to lollipop included)

ionioni said:
yes, use the rom i linked extract and flash from dnx mode ("fastboot starting" message on screen pwr+volup+voldown to start in dnx)
Click to expand...
Click to collapse
if I install rom which allows ringing ,
whether later I will be able to update it eg. to 5.0
and still I could call from tablet ?

progdvb said:
if I install rom which allows ringing ,
whether later I will be able to update it eg. to 5.0
and still I could call from tablet ?
Click to expand...
Click to collapse
you can update, if it works in kitkat will work in lollipop

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

Multitude of hurdles trying to get bootloader unlocked

Hi all! I am attempting at the end of this project to have Dirty Unicorns running on my device, but I am having a rough time just trying to get the boot loader unlocked.
1st OS: Ubuntu 16.04
I had android-tools-fastboot and adb installed. The phone has developer options and USB debugging turned on.
I started the phone in fastboot(volume down + power), I see the droid bot with the 'hood open' It states to connect the USB cable. I have the USB cable connected to a USB 2.0 port.
Phone states that the USB is connected. From the computer's log:
[Thu Dec 27 11:13:50 2018] usb 1-1: new high-speed USB device number 10 using ehci-pci
[Thu Dec 27 11:13:50 2018] usb 1-1: New USB device found, idVendor=22b8, idProduct=2e80
[Thu Dec 27 11:13:50 2018] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Thu Dec 27 11:13:50 2018] usb 1-1: Product: Fastboot potter S
[Thu Dec 27 11:13:50 2018] usb 1-1: Manufacturer: Motorola Inc.
[Thu Dec 27 11:13:50 2018] usb 1-1: SerialNumber: ZY224G4BVW
So it is seeing it.
When I run sudo adb devices(ran with and without sudo) all I get is "List of devices attached" with nothing listed.
Did some searching(most of the posts are about WIndows) and found this
I implemented those rules and restarted the services, but the permissions never changed. - and yes I changed OWNER= to my username.
So I say, let's try Windows. I have a Win10 machine here. I first go here to download the driver, but when I click on either link at the bottom of the Windows column(32bit or 64bit) It sends me to a page that states "There has been an error with your request." If I click the Mac link, it starts a download. Could you try to test the download link?
I contacted Moto about this and the reply was that I needed to be using Chrome. I have tried FF, Chrome, Opero, IE and Egde. I have tried it from home, work and mobile data, all with the same result.
Could someone help me out here? These pretzels are making me thirsty!
Thanks!

Don't worry about
Code:
adb devices
not showing, you will be using fastboot for the unlocking steps. Type
Code:
fastboot devices
and it should show your devices #. You can then follow the steps for getting unlock code and unlock the bootloader.

[email protected] said:
Don't worry about
Code:
adb devices
not showing, you will be using fastboot for the unlocking steps. Type
Code:
fastboot devices
and it should show your devices #. You can then follow the steps for getting unlock code and unlock the bootloader.
Click to expand...
Click to collapse
Appreciate the reply.
fastboot devices also returns nothing

TheFlashNewb said:
Don't worry about not showing, you will be using fastboot for the unlocking steps. Type
Appreciate the reply.
fastboot devices also returns nothing
Click to expand...
Click to collapse
You need to install Motorola driver to get device. Here is the link from my gdrive to download it:-https://drive.google.com/file/d/1silF8KibEfODhRt7j0twUNI_GLsnKvOW/view?usp=drivesdk
Then all command will run and you need to enable OEM unlock in developers options. So you can unlock your bootloader.

TheFlashNewb said:
Hi all! I am attempting at the end of this project to have Dirty Unicorns running on my device, but I am having a rough time just trying to get the boot loader unlocked.
1st OS: Ubuntu 16.04
...................................
...................................................
Could someone help me out here? These pretzels are making me thirsty!
Thanks!
Click to expand...
Click to collapse
On a Linux distro, like my Debian, we must add "rules" to udev to make your devices discoverable:
1) create a new file in /etc/udev/rules.d called "51-android.rules".
2)copy the following content:
Code:
#adb mode
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="685c", MODE="0666", GROUP="plugdev"
#fastboot mode
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="685c", MODE="0666", GROUP="plugdev"
3) Replace 04e8 and 685c with your usb address. Run the command
Code:
lsusb
TWICE!!
The first time with adb debug ON (grab the usb address, the second time in the fastboot mode).
You'll get 2 different usb address.
4) make sure your user is in the group "plugdev".
5) restart udev as root with:
Code:
service udev restart
6) Then try with usual commands:
Code:
adb devices or fastboot devices

1st off I appreciate all of your input and help!
On a third computer with Lubuntu installed I finally got it to work! Had to use sudo (which did not work on the Ubuntu install).
Well here I go, wish me luck!
Just for a refresher:
#1 - Unlock through Motorola(no backup needed - phone has never been used)
#2 - Install TWRP
#3 - Reboot into recovery - if I don't I will have to reinstall TWRP
#4 - Flash ROM(Dirty Unicorns potter), then flash gapps
(Question - Should I use the Gapps package from the OpenGapps website or the one on the Dirty Unicorns page?)
#5 - Have fun!
Thanks!

TheFlashNewb said:
1st off I appreciate all of your input and help!
On a third computer with Lubuntu installed I finally got it to work! Had to use sudo (which did not work on the Ubuntu install).
Well here I go, wish me luck!
Just for a refresher:
#1 - Unlock through Motorola(no backup needed - phone has never been used)
#2 - Install TWRP
#3 - Reboot into recovery - if I don't I will have to reinstall TWRP
#4 - Flash ROM(Dirty Unicorns potter), then flash gapps
(Question - Should I use the Gapps package from the OpenGapps website or the one on the Dirty Unicorns page?)
#5 - Have fun!
Thanks!
Click to expand...
Click to collapse
You can use opengapps they recommend to use stock gapps as it doesn't have inbuilt AOSP apps. Means it doesn't have dialer , contacts , message , clock , calculator , default browser app.

sinchan_nohara said:
You can use opengapps they recommend to use stock gapps as it doesn't have inbuilt AOSP apps. Means it doesn't have dialer , contacts , message , clock , calculator , default browser app.
Click to expand...
Click to collapse
Thanks for the reply!
On wiping, which partitions should I wipe before installing the ROM? The phone is currently stock and updated to 8.1.

TheFlashNewb said:
Thanks for the reply!
On wiping, which partitions should I wipe before installing the ROM? The phone is currently stock and updated to 8.1.
Click to expand...
Click to collapse
Cache , dalvic cache , system and data. But before doing anything take backup of efs and persist and keep it safe somewhere in cloud or your PC or both. It would be helpful in future if by chance you messed up your device and lost IMEI.

sinchan_nohara said:
Cache , dalvic cache , system and data. But before doing anything take backup of efs and persist and keep it safe somewhere in cloud or your PC or both. It would be helpful in future if by chance you messed up your device and lost IMEI.
Click to expand...
Click to collapse
Oh wow thanks! Does the stock TWRP for potter(from the TWRP website) have an option to backup those partitions? I cannot find an answer. V 3.2.3-1-potter
Also, does it need to be rooted in order to backup EFS and persist?

TheFlashNewb said:
Oh wow thanks! Does the stock TWRP for potter(from the TWRP website) have an option to backup those partitions? I cannot find an answer. V 3.2.3-1-potter
Also, does it need to be rooted in order to backup EFS and persist?
Click to expand...
Click to collapse
Yes twrp has option to backup efs and persist. You don't need root for this.

[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