Database Develop

Total Noob - need to install generic HTC software

Hi there, I currently have an HTC One M7 with Tmobile UK firmware and I am fed up waiting for update to KitKat and Sense 6. I understand that this is the correct place to ask a question on how to change the software so that it will take HTC official updates rather than tmob approved updates.
From what I have read I need to s-off with firewater first and flash a recovery. Is that correct? Does anyone have step by step instructions on what to do please as I do not want to brick my phone? I would like to install the "normal" HTC software and receive updates from HTC rather than wait for tmobile.
Thanks

BrownTrout said:
Hi there, I currently have an HTC One M7 with Tmobile UK firmware and I am fed up waiting for update to KitKat and Sense 6. I understand that this is the correct place to ask a question on how to change the software so that it will take HTC official updates rather than tmob approved updates.
From what I have read I need to s-off with firewater first and flash a recovery. Is that correct? Does anyone have step by step instructions on what to do please as I do not want to brick my phone? I would like to install the "normal" HTC software and receive updates from HTC rather than wait for tmobile.
Thanks
Click to expand...
Click to collapse
can you post your fastboot getvar all please ? remove imei and seial number beforeposting

Seanie280672 said:
can you post your fastboot getvar all please ? remove imei and seial number beforeposting
Click to expand...
Click to collapse
Hi Seanie, how do I do that? Sorry for the noobness but I really am new to this. Thank you for your help.

BrownTrout said:
Hi Seanie, how do I do that? Sorry for the noobness but I really am new to this. Thank you for your help.
Click to expand...
Click to collapse
do you have fastboot and adb installed on your computer ?

Seanie280672 said:
do you have fastboot and adb installed on your computer ?
Click to expand...
Click to collapse
No, I have downloaded adt-bundle-windows-x86.zip though, is this the correct thing?

easiest way is to download and install this, you need to run as administrator for it to work:
http://forum.xda-developers.com/showthread.php?t=2317790
---------- Post added at 11:57 AM ---------- Previous post was at 11:52 AM ----------
once installed, reboot your phone to fastboot mode, basically restart it and whilst its shutting down hold down the volume down button, you will enter the bootloader, plug it into the computer and select fastboot on the phone screen, if its not already there, its should now say fastboot usb.
Open a command window in the fastboot and adb window you have just installed on your computer, (control + shift + right mouse click on any white area in that folder, open command window here)
The type:
Code:
fastboot getvar all
post the output here minus imei and serial number

Seanie280672 said:
easiest way is to download and install this, you need to run as administrator for it to work:
http://forum.xda-developers.com/showthread.php?t=2317790
---------- Post added at 11:57 AM ---------- Previous post was at 11:52 AM ----------
once installed, reboot your phone to fastboot mode, basically restart it and whilst its shutting down hold down the volume down button, you will enter the bootloader, plug it into the computer and select fastboot on the phone screen, if its not already there, its should now say fastboot usb.
Open a command window in the fastboot and adb window you have just installed on your computer, (control + shift + right mouse click on any white area in that folder, open command window here)
The type:
Code:
fastboot getvar all
post the output here minus imei and serial number
Click to expand...
Click to collapse
Thanks, I have installed that and a DOS window has popped up and after entering the command it says "Waiting for device". Do I need to boot the phone pressing volume down to get this to work as I am currently on my "normal" boot i.e. what it looks like when phone is powered on.

BrownTrout said:
Thanks, I have installed that and a DOS window has popped up and after entering the command it says "Waiting for device". Do I need to boot the phone pressing volume down to get this to work as I am currently on my "normal" boot i.e. what it looks like when phone is powered on.
Click to expand...
Click to collapse
type adb reboot bootloader in that command window (DOS window)

{
"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"
}

BrownTrout said:
Click to expand...
Click to collapse
perfect :good:
Right your on hboot 1.55 s-off should be easy, boot back to android, type fastboot reboot in the command window (if you've not already rebooted that is)
use either rumrunner to s-off http://rumrunner.us/
or
Firewater to s-off http://firewater-soff.com/
Do not update before getting s-off, follow the instructions on each of the sites to use the tools, rumrunner is the easiest, just download the package, extract it and run the file, firewater is a little more complicated.
once done, report back here, there will only be 2 more steps to do after that, but keep adb and fastboot on your computer, do not remove them.

Many thanks, I am getting an error though

ahh ok try firewater temp root method, its the 3rd method down, you will have to download 2 files and put them in the same folder as fastboot and adb, where you open the dos window from, the whole thing is run from the dos window, so just copy and paste the commands one at a time as listed on the page.
ahh do you have USB debugging enabled on your rom ?

Thanks, it is attempting to acquire root just now. Will update when complete.

Thanks, I have temproot and s-off now.

excellent, now that you have s-off, you have to be very careful, if you flash the wrong thing, where the phone will stop you and tell you its wrong with some sort of error with s-on, it wont anymore, it will expect that you know what you are doing and still flash it, if its wrong it will brick.
---------- Post added at 01:19 PM ---------- Previous post was at 01:15 PM ----------
so fist all, if your phone is booted into android still, open a dos window again inside the fastboot / adb folder as before and again, type:
Code:
adb reboot bootloader
once there, make sure to says fastboot USB on the phone screen.
then be very careful with this one, CID is ALWAYS 8 characters long, bear that in mind with the next command, so the next command is 2 underscores not one inbetween the HTC and the 001. always capital letters, take note of your current cid though, you will need it for warranty purposes.
Code:
fastboot oem writecid HTC__001
when complete:
Code:
fastboot reboot-bootloader
---------- Post added at 01:28 PM ---------- Previous post was at 01:19 PM ----------
Its should now say this on your screen or something close to it:
M7_UL PVT SHIP S-OFF ??
CID-HTC__001
HBOOT-?????????
RADIO-??????????
OpenDSP-?????????
OS??????????
etc etc etc, can you confirm please ?

It's been hanging at < waiting for device > after I typed in the fastboot reboot bootloader command

BrownTrout said:
It's been hanging at < waiting for device > after I typed in the fastboot reboot bootloader command
Click to expand...
Click to collapse
the 3rd command or the 1st command ?

Managed to get it working.

BrownTrout said:
Managed to get it working.
Click to expand...
Click to collapse
so sorry, my bad, if it was the 1st command it should of been adb reboot bootloader not fastboot, ive edited the post above.

Seanie280672 said:
so sorry, my bad, if it was the 1st command it should of been adb reboot bootloader not fastboot, ive edited the post above.
Click to expand...
Click to collapse
I have manually rebooted and ran the commands that you mentioned and it appears to have worked as the phone displays what you have posted above.

Deleted OS//No Drivers//OTG Don't work

Hello.
I wanted to flash CM12.1 to friends One(M7) but while flashing I have some kind of error.
I removed OS .. there is just TWRP 2.5.0.0 which seems don't recognize OTG USB.
Drivers for ADB or Fastboot while I'm in bootloader seems don't work I have windows 10 and only 3.0 USB Ports.
So now is there TWRP without nothing and I don't know what to do.. I have only 2 days for fix it.
//EDIT// It was unlocked and rooted so I just wanted to flash ROM like in others phones but like I'm reading more and more forums with HTC it's quite difficult and I'm not sure if everything is as it should be. Whats is S-ON/OFF?? What is RUU and how I know if "my" One is the right for which I can flash ROM. (But theses questions aren't important)
I see lot of theard with same problem but I can't find any real solution. I hope someone help me :fingers-crossed:

What happens when you type "fsstboot devices" in bootloader menu?

donkeykong1 said:
What happens when you type "fsstboot devices" in bootloader menu?
Click to expand...
Click to collapse
Typo, should be "fastboot devices".

in ur devices no os??? maybe can't flash because corrupt emmc..,.. sory for bad english

Fastboot devices don't show nothing
How to fix corrupt emmc? Without os or possibility connection with pc

dasti555 said:
Fastboot devices don't show nothing
How to fix corrupt emmc? Without os or possibility connection with pc
Click to expand...
Click to collapse
Hard to suggest much without knowing specifics of the phone but I think we are a long way from assuming the emmc is corrupt.
Try this link to get your drivers working, then give us the output of "fastboot getvar all"
http://forum.xda-developers.com/showthread.php?t=2317790

if ur device can bootloader it's means u can repair emmc maybe
I have experienced 0gb on my EMMC , but can bootloader ,it can repair EMMC with emmcblkp.zip , but I forgot his link
sory for bad in english

1-the rom did not flashed because you are using the wrong recovery version. You need at least 2.7.1.1 to flash Cyanogenmod roms (assuming your phone is a M7_UL variant)
2- Since you are using such an old recovery, it would make sense to me that it was flashed on the phone back in 2013 so maybe the phone never got any Ota updates and the hboot version is still 1.44? If yes you won't be able to get fastboot connectivity using Win8/10, only with win7/linux/OSx. That might be the problem.
3-can you write down all the information you see when in bootloader, with this we should at least be able to confirm what I said above
---------- Post added at 04:35 PM ---------- Previous post was at 04:32 PM ----------
bintang456 said:
if ur device can bootloader it's means u can repair emmc maybe
I have experienced 0gb on my EMMC , but can bootloader ,it can repair EMMC with emmcblkp.zip , but I forgot his link
sory for bad in english
Click to expand...
Click to collapse
There is nothing pointing to a bad emmc for now. He is at step 1 (getting the phone detected) and you are talking about a "possible" step 20.... Not saying you're wrong but it's way too early to assume a bad emmc

alray said:
1-the rom did not flashed because you are using the wrong recovery version. You need at least 2.7.1.1 to flash Cyanogenmod roms (assuming your phone is a M7_UL variant)
2- Since you are using such an old recovery, it would make sense to me that it was flashed on the phone back in 2013 so maybe the phone never got any Ota updates and the hboot version is still 1.44? If yes you won't be able to get fastboot connectivity using Win8/10, only with win7/linux/OSx. That might be the problem.
3-can you write down all the information you see when in bootloader, with this we should at least be able to confirm what I said above
---------- Post added at 04:35 PM ---------- Previous post was at 04:32 PM ----------
There is nothing pointing to a bad emmc for now. He is at step 1 (getting the phone detected) and you are talking about a "possible" step 20.... Not saying you're wrong but it's way too early to assume a bad emmc
Click to expand...
Click to collapse
One more thought on this phone. Did you also wipe the data partition? If not are you sure that the person that originally installed twrp didn't leave a nandroid backup on the device. Have you looked under restore in twrp? LIkely too simple but worth a shot!!

Yes you are absolutelly right!
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
Apr 20 2013, 15:46:23-1
So what should I do now?
I wanted to install today Windows7 but it failed and I ****ed it and I removed my old windows so I must 2 hours searching for new windows. Now I'm finally at Windows10 again.
So.. Maybe Windows7 in virtual box? Anyway one guy have Linux at his computer what can I do now?

sorry for my assume...

dasti555 said:
Yes you are absolutelly right!
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
Apr 20 2013, 15:46:23-1
So what should I do now?
I wanted to install today Windows7 but it failed and I ****ed it and I removed my old windows so I must 2 hours searching for new windows. Now I'm finally at Windows10 again.
So.. Maybe Windows7 in virtual box? Anyway one guy have Linux at his computer what can I do now?
Click to expand...
Click to collapse
Windows 7 in a virtualbox won't work afaik. Better to use a live Ubuntu usb/cd, setup adb and fastboot then you'll be able to update your twrp recovery and flash the rom. Also worth to post a "fastboot getvar all" at the same time. Maybe we could update the firmware easily (depending what the getvar all returns) and fix that connectivity problem at the same time.
Here is aguide how to use Ubuntu without having to install it on your computer: http://forum.xda-developers.com/showthread.php?t=2606577
It was writted for a different purpose so just ignore the steps talking about rumrunner.
---------- Post added at 10:59 AM ---------- Previous post was at 10:57 AM ----------
bintang456 said:
sorry for my assume...
Click to expand...
Click to collapse
No need to be sorry, everyone tries their best, thats what matters :good:
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
Btw here is the reference for the minimum recovery requirement to flash CM:
TWRP recoveries with version greater than or equal to 2.7.0.8 support this fstab change.* If you have a favorite recovery maintainer, encourage them to incorporate "block: by-name" support into their recovery kernels!
Official 2.7.1.0 for m4, m7, m7spr/m7wls, and m7vzw/m7wlv mistakenly did not include the necessary fstab support, so 2.7.1.1 was released for these devices, addressing the issue.
More recent unofficial builds of TWRP can be found at android.cmphys.com. You'll find source code for all these devices linked there as well.
Click to expand...
Click to collapse
https://wiki.cyanogenmod.org/w/HTC_fstab_updates

So what I have to do now is
Connect phone to PC with Ubuntu then write in terminal "fastboot getvar all" and then write here again? Or Just "fastboot flash recovery.img"
Well ... I'm at Ubuntu and when we try "fastboot flash recovery recovery.img" then just waiting for devices .. need i some kind of fastboot drivers for ubuntu or what?
We tried download some kind of" # sudo apt-get install android-tools-adb android-tools-fastboot "
but phone is still not recognized

mb_guy said:
Typo, should be "fastboot devices".
Click to expand...
Click to collapse
Sorry, big fingers, small keyboard on my phone [emoji20]

dasti555 said:
So what I have to do now is
Connect phone to PC with Ubuntu then write in terminal "fastboot getvar all" and then write here again? Or Just "fastboot flash recovery.img"
Click to expand...
Click to collapse
I'll copy/paste from the guide linked above the step you need only:
(1) a copy of 32bit Ubuntu. NOT 64!! http://www.ubuntu.com/download/desktop
(2) no need to install-boot into it as if trying it (IMAGE 3)
(4) drivers NOT needed
I know others have had zero issues but some of us have had nothing but nightmares. This is who I'm sharing this for.
I hope it helps... Even just one!
Have fun all!
IF BY CHANCE YOU ARE HAVING ISSUES WITH ADB OR FASTBOOT IN UBUNTU SEEING YOUR DEVICE, TYPE sudo BEFORE YOUR COMMANDS. IT WANTS PERMISSION TO ACCEPT YOUR COMMANDS. WHEN YOU TYPE sudo THEN YOUR PASSWORD YOU ARE GRANTING THOSE PERMISSIONS. SOMETIMES THE ISSUE WON'T APPEAR TIL YOU GET INTO FASTBOOT. SO CHECK FIRST BY TYPING IN adb devices WHEN YOU FIRST OPEN THE TERMINAL. IF YOU GET A SERIAL NUMBER YOU SHOULD BE FINE. AFTER YOU GET INTO BOOTLOADER, TYPE fastboot devices IF YOU GET A "no permission" ERROR THEN YOU NEED TO TYPE sudo BEFORE all INSTRUCTIONS. SOME VERSIONS OF LINUX HAVE AN SU TERMINAL. THAT WOULD BE THE BEST TO USE AS IT REQUIRES ROOT/PERMISSION TO EVEN START AND WILL MAINTAIN THOSE PERMISSIONS THROUGHOUT.
UBUNTU STEPS.....
Image 3- Boot into Ubuntu
Image 7- Open Terminal in Ubuntu (Top left gear like symbol, click it and a search bar will appear, start typing terminal, it will appear below the bar, just select it)
Image 8- You need to install adb fastboot these are the instructions you need to type in the terminal you just opened. Type one line at a time and press enter after each. Allow Ubuntu to do it's stuff.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Image 9-12 Shows how the terminal should look as it finds, downloads and install the appropriate files.
Image 13- After the downloads are finish you can check to make sure things were installed correctly. Type “adb” and your screen should look like this
Image 14- Type “fastboot” and this is the information that should appear.
Image 15- To make sure your device is seen type “fastboot devices” and it should show devices with a serial number.
then you can use "fastboot getvar all' and "fastboot flash recovery <file_name>.img"

We made all this now .. fastboot devices command not show nothing just new line which is waiting for command and when we try fastboot flash recovery recovery.img then <waiting for device>
we still dont have drivers or what?

dasti555 said:
We made all this now .. fastboot devices command not show nothing just new line which is waiting for command and when we try fastboot flash recovery recovery.img then <waiting for device>
we still dont have drivers or what?
Click to expand...
Click to collapse
You don't need drivers on linux. Is the phone booted in bootloader and in the fastboot menu? You should see "fastboot usb" in red when in the correct mode to use fastboot commands.
like on this image:
{
"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"
}

yes it is
its like transfer isnt working but charging is
edit : uh no :/ there is only fastboot in red not fastboot usb I should boot there while I'm connected via cable? // booting there while cable is pluged-in and still only fastboot in red

dasti555 said:
yes it is
its like transfer isnt working but charging is
edit : uh no :/ there is only fastboot in red not fastboot usb I should boot there while I'm connected via cable? // booting there while cable is pluged-in and still only fastboot in red
Click to expand...
Click to collapse
are you using the original usb cable? some cheap cable are only providing power but no data connection. I also just have noticed from your first post that you are using usb 3.0. You have to use a 2.0 port to avoid problems. you should have "fastboot usb" in red when there is a connection as opposed to "fastboot" only if there is none.
bootib there before or after doesnt matter

@alray We are trying it with different PC which have Ubuntu and also Kali Linux as dualboot.
Have only 2.0USB Ports..
I will try different cable.... Nope .. Still only fastboot without USB
My OnePllus One with same cable find but this HTC no :/

Problem with ADB

Hey guys,
i have an big problem with my HTC One M7:
I installed "One_M7_7.15.401.1_stock_system_dump.zip" from HD Revolution to get on Lollipop but it showed an Error and after restarting i cant get into the Phone and i cant get into the recovery. The recovery pops up for like one second or less and throws me into a bootloop.
I wanted to flash a new Recovery via adb/fastboot but my Computer doesnt shows me my device. On the bootloader in the fastboot menu it shows "Fastboot USB" in red.
I installed much different drivers but it just doesnt show up. In device manager it says: Unknown USB Device (device failed enumeration) and the error code 43 in details.
I just dont know what to do anymore...
Anyone got an solution for that?

Mrdestroierr1 said:
Hey guys,
i have an big problem with my HTC One M7:
I installed "One_M7_7.15.401.1_stock_system_dump.zip" from HD Revolution to get on Lollipop
Click to expand...
Click to collapse
Not really sure why you installed this one. This is a non-official/leaked version before the official one was released (7.19.401.2) and the latest version is 7.19.401.51.
but it showed an Error
Click to expand...
Click to collapse
Would help to be more precise, what error exactly?
and after restarting i cant get into the Phone and i cant get into the recovery. The recovery pops up for like one second or less and throws me into a bootloop.
Click to expand...
Click to collapse
What recovery (name + version) is installed on your phone?
I wanted to flash a new Recovery via adb/fastboot but my Computer doesnt shows me my device. On the bootloader in the fastboot menu it shows "Fastboot USB" in red.
Click to expand...
Click to collapse
well at least you have "fastboot usb" which mean there is actually a working data connection between the phone and your ocmputer
I installed much different drivers but it just doesnt show up. In device manager it says: Unknown USB Device (device failed enumeration) and the error code 43 in details.
Click to expand...
Click to collapse
You need the latest drivers from htc. What is your windows version? What is your bootloader version?

sorry i had to make a new account:/
alray said:
Not really sure why you installed this one. This is a non-official/leaked version before the official one was released (7.19.401.2) and the latest version is 7.19.401.51.
Would help to be more precise, what error exactly?
some changes failed
What recovery (name + version) is installed on your phone?
i had cwm but i dont know which version (the m7 was inactive for 1-2 years)
well at least you have "fastboot usb" which mean there is actually a working data connection between the phone and your ocmputer
You need the latest drivers from htc. What is your windows version? What is your bootloader version?
i downloaded the drivers yesterday. i got windows 10 (im now trying with ubuntu). it got hboot 1.44
Click to expand...
Click to collapse
---------- Post added at 03:47 PM ---------- Previous post was at 03:25 PM ----------
I think i got it. Ubuntu worked. thanks alray for your answer. Because of you i checked HBoot 1.44 and this isnt compatible with Windows 10/8. In Ubuntu adb doesnt work but fastboot does. Now i flashed TWRP and installed the Rom again.
Now it boots up but it is in the boot screen since 5 Minutes:/
#Edit It doesnt boot up... and adb doesnt work so i cant push another rom on the phone..
#edit 2 adb works when im in recovery (tought i had to be in bootloader -> fastboot) now it could work with a downloaded nandroid backup :good:

mrdestroierrr1 said:
sorry i had to make a new account:/
Click to expand...
Click to collapse
You shouldn't, its against forum rules
http://forum.xda-developers.com/announcement.php?a=81
You should contact a moderator to disable the other account or this one might also be disabled.
I think i got it. Ubuntu worked. thanks alray for your answer. Because of you i checked HBoot 1.44 and this isnt compatible with Windows 10/8
Click to expand...
Click to collapse
Yep, exactly why I wanted to know, good job.
In Ubuntu adb doesnt work but fastboot does.
Click to expand...
Click to collapse
ADB will only work from a booted rom or from a custom recovery, not in bootloader mode.
{
"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"
}

help htc one m7
I am trying to send a ROOM from the computer to my internal memory via ADB sideload command to be able to install by twrp, so it is not going to talk that it is not possible to read, I tested with ADB devices and perfectly motra my device, someone can you help me?
C:\HTC>adb devices
List of devices attached
SH3ALW904272 sideload
C:\HTC>adb sideload Rom.zip
loading: 'Rom.zip'
* cannot read 'Rom.zip' *
C:\HTC>

ewvisjean said:
I am trying to send a ROOM from the computer to my internal memory via ADB sideload command to be able to install by twrp, so it is not going to talk that it is not possible to read, I tested with ADB devices and perfectly motra my device, someone can you help me?
C:\HTC>adb devices
List of devices attached
SH3ALW904272 sideload
C:\HTC>adb sideload Rom.zip
loading: 'Rom.zip'
* cannot read 'Rom.zip' *
C:\HTC>
Click to expand...
Click to collapse
What version of TWRP are you using?

Anyone being able to access recovery?

I haven't found any way to access to stock recovery. Only success I had has been entertaining safe mode.
There are several suggestions that says to hold volyme up and power buttons while being plugged in and stuff... But nothing really seems to work. Anyone that actually accessed recovery?
Sent from my TA-1004 using Tapatalk

How about through ADB?
ADB reboot recovery...
I have tried button combos but no recovery.
I am currently on vacation, so can't access pc, will try as soon as I get to home.

Adb reboot recovery works, but idk what to do then...
{
"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"
}
Powered by Nokia 8

From the first picture it looks almost like there is no recovery installed on the recovery partition. Or it's locked behind some specific button combination.

Now this is getting really really sad... There are no usb driver for Linux. Even talked with support after I couldn't find it on their web site..

Now this is getting weird, I cannot get the ADB to see my Nokia 8 even on windows... Although I installed the driver.
Edit. Never mind, just haven't used windows in a while..
---------- Post added at 09:49 PM ---------- Previous post was at 09:11 PM ----------
Ok so, I can get the device to boot into bootloader(download mode) and somekind of a recovery, trough ADB in windows.
But no luck on "fastboot oem unlock" command. --FAILED <remote : flashing unlock is not allowed

lorditler said:
Can't you just plug it in and use MTP? Or are you talking about a driver for ADB?
Click to expand...
Click to collapse
Yes, I mean driver for ADB to work.
Mtp works just fine!

after "adb reboot recovery" it is in download mode.
pressing power and volume up is getting it into recovery mode.
so far i found no way to get it into bootloader.

Alttu said:
Now this is getting really really sad... There are no usb driver for Linux.
Click to expand...
Click to collapse
Hmmm... I just enabled USB debugging in the developer options, connected the Nokia 8 to my Linux machine, typed
Code:
adb devices
, and it worked right away.

shredzone said:
Hmmm... I just enabled USB debugging in the developer options, connected the Nokia 8 to my Linux machine, typed , and it worked right away.
Click to expand...
Click to collapse
Really?!
I tried many times, must be something on my end then

Alttu said:
Really?!
I tried many times, must be something on my end then
Click to expand...
Click to collapse
Could be the distribution (I'm using Fedora)... Maybe all you need is to add an udev rule for HMD Global (vendor id 2e04).

shredzone said:
Could be the distribution (I'm using Fedora)... Maybe all you need is to add an udev rule for HMD Global (vendor id 2e04).
Click to expand...
Click to collapse
Thanks mate, will try.
I am using Ubuntu...
Strange thing is, I haven't got any problems with other phones before...

Got the adb command working by simply installing the adb from the repo in Sabayon. What remains is a problem... What if the phone does not boot or is locked with a bugged unlock pattern without having adb debugging enabled?
Send to service?
If it does not boot I assume there is some kind of failsafe using the a/b partitions... But besides that I don't see how the user can recover if a big problem comes
Sent from my TA-1004 using Tapatalk

2WildFirE said:
Adb reboot recovery works, but idk what to do then...
Powered by Nokia 8
Click to expand...
Click to collapse
Press and hold power key, then press volume up.

Here's my experience using Ubuntu (make sure adb tools are installed)
1. Connect the phone to PC via USB
2. Ensure debugging on the phone is turned on
3. Set USB mode to "File Transfers" via the notification shade on the phone
4. From the PC terminal run "adb reboot recovery", without the quote marks
5. The phone will reboot to an image of Android robot with red exclamation mark and the words "no command" on screen
6. Now hold the power button down and then press Volume Up
You should be in recovery menu

Phone bricked!

My Mi A2 has got BRICKED!!!!!!!! when i am trying to flash stock rom i MI FLASH TOOL phone doesnt support because USB DEBUGGING MODE not enabled. i cant open my phone for brick. So now what can i do?

can you put phone in fastboot?

DiesFrae said:
can you put phone in fastboot?
Click to expand...
Click to collapse
yes. in fastboot. and command "fastboot oem edl" its not working, says Waiting for device

Oline1032 said:
yes. in fastboot. and command "fastboot oem edl" its not working, says Waiting for device
Click to expand...
Click to collapse
did you check if fasboot reads your device?
cmd: fastboot devices

DiesFrae said:
did you check if fasboot reads your device?
cmd: fastboot devices
Click to expand...
Click to collapse
i checked command "fastboot devices" but it show blank. no message

Oline1032 said:
i checked command "fastboot devices" but it show blank. no message
Click to expand...
Click to collapse
it should show an ID for your device. Have you installed latest adb & fastboot drivers?
link to adb drivers https://androidfilehost.com/?fid=24686681827312411

DiesFrae said:
it should show an ID for your device. Have you installed latest adb & fastboot drivers?
Click to expand...
Click to collapse
yes latest adb + fastboot installed. and i had done unlock bootloader + flashing unlock critical with this adb+fastboot

Oline1032 said:
yes latest adb + fastboot installed. and i had done unlock bootloader + flashing unlock critical with this adb+fastboot
Click to expand...
Click to collapse
fastboot should reads your device. try running cmd.exe as admin and switch to another USB port or cable and see the results. just make sure that fastboot devices shows an ID

DiesFrae said:
fastboot should reads your device. try running cmd.exe as admin and switch to another USB port or cable and see the results. just make sure that fastboot devices shows an ID
Click to expand...
Click to collapse
not working:crying::crying::crying::crying::crying:

Oline1032 said:
not working:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
ask on telegram group then man, i don't know what's going on tbh

Try edl mode
Fastboot oem edl

Oline1032 said:
My Mi A2 has got BRICKED!!!!!!!! when i am trying to flash stock rom i MI FLASH TOOL phone doesnt support because USB DEBUGGING MODE not enabled. i cant open my phone for brick. So now what can i do?
Click to expand...
Click to collapse
Hello, I currently have the same problem. Today I was converting my xiaomi mia2 to mi6x. Everything was normal, until at one point of the transfer miflash gave an error and the transfer stopped, checking the logs I find that simply the USB stopped working, the phone now does not signal by the usb. Now we have a paperweight, apparently. I have researched and apparently can try to repair the phone using the "test point method", which forces the EDL mode on the phone for a few seconds that you should take to flash the rom from MiFlash.
Please check this and try to do so, for the moment I have no tools because we have to disassemble the phone. I hope you have appropriate tools and you can tell me if it works! -> https://en.miui.com/thread-3524265-1-1.html
This other guide is for the A1, but it has information that may be able to help you. -> http://en.miui.com/thread-1680467-1-1.html
EDIT: I can confirm that I solved the brick with this method.
{
"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"
}