Develop Bugs

[Q] HTC one M8 (dual sim) stuck on bootloader! What can I do?

Hello everyone! glad to be a new member of this amazing community! I am a new member with a tough problem, would love if I get ideas on how to solve it.
So After flashing stock unrooted GPe rom as per the most common methods circulating around (changing CID, MID, S-Off, etc), I was thrilled to see the boot splash screen change into google's except that it keeps booting into the bootloader; for some reason I could not get into recovery either (but I flashed TWRP again and it works now)
So as it stands now I have the following:
S-Off
Unlocked
Software status: Official
Working TWRP (which keeps saying NO OS IS INSTALLED)
Unable to mount /data (whatever that means) + "error: closed" when attempting to sideload the RUU roms via ADB
I did not install any firmware or kernels
and whenever I try to boot the OS I get put back in bootloader over and over.
As far as im concerned this phone seems bricked for me, but im also new so I wouldn't know, having said that, I am open for the most radical of options and procedures to get this working.
Thank you all in advance!

Flash it again via adb, the flashing command must be executed twice.

I get an error "E:Unable to mount '/Data'" as soon as I open up the sideload option. when attempting to sideload I get "error: closed". I am starting to sense I have a problem with my storage. what to do next?
Thank you so much for your reply!

Megaliths said:
I get an error "E:Unable to mount '/Data'" as soon as I open up the sideload option. when attempting to sideload I get "error: closed". I am starting to sense I have a problem with my storage. what to do next?
Thank you so much for your reply!
Click to expand...
Click to collapse
That unrooted GPE was for dual sim? I see you have a dual sim.
Make a screenshot.
Details about the ROM would help.
Do a fastboot getvar all command also.

Actually I don't know if the Rom is for dual sim or not, I figured as long as I get CID and MID right it should fit? pardon my ignorance on the matter. ill post a screenshot as soon as possible!

Getvar all:
C:\Users\Megalith\Desktop\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s

Megaliths said:
Getvar all:
C:\Users\Megalith\Desktop\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Click to expand...
Click to collapse
Delete the IMEI.

OP - Do you want it back to Sense?

EddyOS said:
OP - Do you want it back to Sense?
Click to expand...
Click to collapse
I really prefer to get GPE working but sense is better than a bricked phone.
Also, thanks for the replies!

EddyOS said:
OP - Do you want it back to Sense?
Click to expand...
Click to collapse
Come to think about it now, I'd rather go to stock now if it all possible.

Megaliths said:
I really prefer to get GPE working but sense is better than a bricked phone.
Also, thanks for the replies!
Click to expand...
Click to collapse
Megaliths said:
Come to think about it now, I'd rather go to stock now if it all possible.
Click to expand...
Click to collapse
OK. First things first, did the GPe ROM ever work? The reason I ask it was designed for the single-SIM M8 so don't know if it worked with the dual-SIM version. If not, we should be OK to get back to stock...

EddyOS said:
OK. First things first, did the GPe ROM ever work? The reason I ask it was designed for the single-SIM M8 so don't know if it worked with the dual-SIM version. If not, we should be OK to get back to stock...
Click to expand...
Click to collapse
It never booted up correctly no. I'd love if you can help me go to stock with such a messed up state my phone had gotten into.

We should be able to sort things out, but I'll need to get to a proper PC and get links together

EddyOS said:
We should be able to sort things out, but I'll need to get to a proper PC and get links together
Click to expand...
Click to collapse
Thank you so much!

OK, this isn't particularly straight forward but should hopefully work...
Download the following files and place in your fastboot folder:
- Dual-SIM RUU - https://drive.google.com/file/d/0B17smFr95pleaW9iTFBiSUE2OVE/view?usp=sharing (rename to anything you want but I'd recommend ruu.zip, not ruu.zip.zip obviously!)
- htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249
- Sense FW - https://www.androidfilehost.com/?fid=23329332407589439 (again, rename to anything but I'd recommend firmware.zip)
1. First things first, boot into fastboot and set your CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader and confirm it's done - fastboot reboot-bootloader
3. Assuming it's done, boot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the firmware package - fastboot flash zip firmware.zip
5. It'll fail the first time and reboot. Do the exact same command again once back in RUU mode - fastboot flash zip firmware.zip
6. Once finished, reboot back to the bootloader to confirm it's on the white 'Sense' version - fastboot reboot-bootloader
7. Assuming it's done, reboot into RUU mode again - fastboot oem rebootRUU
8. Now flash the RUU using the HTC fastboot version - htc_fastboot flash zip ruu.zip
9. This will go through a few passes but once finished reboot to the bootloader - fastboot reboot-bootloader
10. Once back at the bootloader, disconnect the phone and go into stock recovery
11. Once in stock recovery, hold power and press volume up and once the menu appears do a factory reset
12. Once complete, reboot the phone
It should now boot back into the normal Sense ROM. Now if you changed your MID to the GPe one you'll need to re-root your phone and change it back using the guide by @scotty1223 HERE but if you didn't change it then you're good to go!

EddyOS said:
OK, this isn't particularly straight forward but should hopefully work...
Download the following files and place in your fastboot folder:
- Dual-SIM RUU - https://drive.google.com/file/d/0B17smFr95pleaW9iTFBiSUE2OVE/view?usp=sharing (rename to anything you want but I'd recommend ruu.zip, not ruu.zip.zip obviously!)
- htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249
- Sense FW - https://www.androidfilehost.com/?fid=23329332407589439 (again, rename to anything but I'd recommend firmware.zip)
1. First things first, boot into fastboot and set your CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader and confirm it's done - fastboot reboot-bootloader
3. Assuming it's done, boot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the firmware package - fastboot flash zip firmware.zip
5. It'll fail the first time and reboot. Do the exact same command again once back in RUU mode - fastboot flash zip firmware.zip
6. Once finished, reboot back to the bootloader to confirm it's on the white 'Sense' version - fastboot reboot-bootloader
7. Assuming it's done, reboot into RUU mode again - fastboot oem rebootRUU
8. Now flash the RUU using the HTC fastboot version - htc_fastboot flash zip ruu.zip
9. This will go through a few passes but once finished reboot to the bootloader - fastboot reboot-bootloader
10. Once back at the bootloader, disconnect the phone and go into stock recovery
11. Once in stock recovery, hold power and press volume up and once the menu appears do a factory reset
12. Once complete, reboot the phone
It should now boot back into the normal Sense ROM. Now if you changed your MID to the GPe one you'll need to re-root your phone and change it back using the guide by @scotty1223 HERE but if you didn't change it then you're good to go!
Click to expand...
Click to collapse
That is amazing thank you, ill try it and get back to you asap.

I have two questions:
Will I still get OTAs even if I don't have the original CID and MID? (I remember the original CID which is J15 but I can't remember the mid).
Also, I am currently on custom recovery and in your guide above I do not see anything about flashing stock recovery, should I do that first?
Thank you again!

The RUU flashes everything stock, so it'll overwrite it all
I'd change the CID back to stock once it's all working again but the MID I'm not sure on so I'll see if I can find out for you

At step 8 I get an error "DNS server not authoritative for zone", how to resolve that?

Nvm I resolved the DNS thin, but now I get error 41 model id check fail. It is probably because of bad MID isn't it?
Thank you again for helping me, I hope it is not much trouble.

Endless bootloop. Can't get into recovery even with fastboot commands

Been stuck with this one for days. Endless searches gets me as far as loading the bootloader (button longpress method) and flashing the usual images with fastboot. I used both the preview and post preview developer images. After successfully flashing (indivisually and clicking flash-all), the phone reboots over and over- never into the system or recovery. Any insight is extremely appreciated. Warranty is recently expired too so that's not an option unfortunately.

kt006 said:
Been stuck with this one for days. Endless searches gets me as far as loading the bootloader (button longpress method) and flashing the usual images with fastboot. I used both the preview and post preview developer images. After successfully flashing (indivisually and clicking flash-all), the phone reboots over and over- never into the system or recovery. Any insight is extremely appreciated. Warranty is recently expired too so that's not an option unfortunately.
Click to expand...
Click to collapse
Wait, so you can get into the fastboot menu, but you can't get into the recovery menu? What happens when you select the recovery menu from the fastboot menu?
As for the problem, the only thing I can think of that might be causing this is if you changed your data partition to f2fs for use with the Negalite custom rom. You'll need to change it back to ext4 either by using TWRP, formatting with the stock recovery menu or using the command fastboot erase userdata.

When trying to enter recovery mode, either with Fastboot command or button press, the phone just restarts and bootloops. I'll try your method later tonight.

TheSt33v said:
Wait, so you can get into the fastboot menu, but you can't get into the recovery menu? What happens when you select the recovery menu from the fastboot menu?
As for the problem, the only thing I can think of that might be causing this is if you changed your data partition to f2fs for use with the Negalite custom rom. You'll need to change it back to ext4 either by using TWRP, formatting with the stock recovery menu or using the command fastboot erase userdata.
Click to expand...
Click to collapse
Tried the fastboot erase userdata and followed with flash-all.bat. What's frustrating is that all the fastboot commands finish with no reported errors. Until it tries to boot into recovery and starts bootlooping again. It's like the watch can't access the recovery. Tried flashing twrp and fastboot boot twrp.img- still bootlooped.

kt006 said:
Tried the fastboot erase userdata and followed with flash-all.bat. What's frustrating is that all the fastboot commands finish with no reported errors. Until it tries to boot into recovery and starts bootlooping again. It's like the watch can't access the recovery. Tried flashing twrp and fastboot boot twrp.img- still bootlooped.
Click to expand...
Click to collapse
Very strange. Did you make any sort of modifications before this started happening? Custom rom, root, etc?

TheSt33v said:
Very strange. Did you make any sort of modifications before this started happening? Custom rom, root, etc?
Click to expand...
Click to collapse
Only the bootloader was unlocked and the developer preview was flashed.
Edit* This is what I get when using getvar all. Anyone notice anything unusual that might be the cause?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) boardid:7N3BDH15BJ065725
(bootloader) macbt:2400BA712168
(bootloader) macwlan:2400BA712167
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4134mV
(bootloader) variant:
(bootloader) off-mode-charge:0
(bootloader) unlocked:yes
(bootloader) secure:yes
(bootloader) version-bootloader:STURGEONV3.8
(bootloader) version-baseband:N/A
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x3d00000
(bootloader) partition-type:boot:emmc
(bootloader) partition-size:boot: 0x1400000
(bootloader) partition-type:recovery:emmc
(bootloader) partition-size:recovery: 0x1400000
(bootloader) partition-type : oem:ext4
(bootloader) partition-size: oem: 0x9678000
(bootloader) partition-type : cache:ext4
(bootloader) partition-size: cache: 0x20000000
(bootloader) partition-type : userdata:ext4
(bootloader) partition-size:userdata: 0x94ffbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x20000000
(bootloader) serialno:MQB*************
(bootloader) kernel:lk
(bootloader) product:sturgeon
all:
finished. total time: 0.078s

kt006 said:
Only the bootloader was unlocked and the developer preview was flashed.
Edit* This is what I get when using getvar all. Anyone notice anything unusual that might be the cause?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) boardid:7N3BDH15BJ065725
(bootloader) macbt:2400BA712168
(bootloader) macwlan:2400BA712167
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4134mV
(bootloader) variant:
(bootloader) off-mode-charge:0
(bootloader) unlocked:yes
(bootloader) secure:yes
(bootloader) version-bootloader:STURGEONV3.8
(bootloader) version-baseband:N/A
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x3d00000
(bootloader) partition-type:boot:emmc
(bootloader) partition-size:boot: 0x1400000
(bootloader) partition-type:recovery:emmc
(bootloader) partition-size:recovery: 0x1400000
(bootloader) partition-type : oem:ext4
(bootloader) partition-size: oem: 0x9678000
(bootloader) partition-type : cache:ext4
(bootloader) partition-size: cache: 0x20000000
(bootloader) partition-type : userdata:ext4
(bootloader) partition-size:userdata: 0x94ffbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x20000000
(bootloader) serialno:MQB*************
(bootloader) kernel:lk
(bootloader) product:sturgeon
all:
finished. total time: 0.078s
Click to expand...
Click to collapse
My readout looks exactly the same except in fields where one would expect it to be different (serial number, mac addresses). The only exception is that I'm on bootloader version 4.2. I'm currently running the most recent official firmware version (the post-preview version is an older version than the most recent. I took several OTAs after I flashed it when I decided I didn't like the wear 2.0 preview), but I don't see why that would matter or cause the problem you're having since your bootloader is unlocked and should therefore not be enforcing anything. When you flash the wear 2.0 preview, does your bootloader version change?

Yes, when flashing the preview it changes to 4.1. I'm looking into kernels. Hopefully it'll get me somewhere

kt006 said:
Yes, when flashing the preview it changes to 4.1. I'm looking into kernels. Hopefully it'll get me somewhere
Click to expand...
Click to collapse
If the kernel was the problem, it would dump you into the fastboot menu instead of bootlooping. Or if it did bootloop, it would be at the bootanimation and not at the initial Huawei screen. The boot logo (not animation) is stored somewhere in the bootloader for many android devices (with some exceptions, but I've never heard of it being stored on /system or anything like that). Also, you flash the kernel at the same time as everything else when you double click on flash-all, so whatever kernel is there should match whatever you flashed. The fact that it isn't loading anything except fastboot and the boot logo makes me think that your bootloader is pretty pissed off. My theory is either it didn't get the memo when you unlocked it and it's still trying to enforce whatever version was on the phone when you did that, or it's totally borked and has lost the ability to understand that all the partitions have officially signed images on them.

TheSt33v said:
If the kernel was the problem, it would dump you into the fastboot menu instead of bootlooping. Or if it did bootloop, it would be at the bootanimation and not at the initial Huawei screen. The boot logo (not animation) is stored somewhere in the bootloader for many android devices (with some exceptions, but I've never heard of it being stored on /system or anything like that). Also, you flash the kernel at the same time as everything else when you double click on flash-all, so whatever kernel is there should match whatever you flashed. The fact that it isn't loading anything except fastboot and the boot logo makes me think that your bootloader is pretty pissed off. My theory is either it didn't get the memo when you unlocked it and it's still trying to enforce whatever version was on the phone when you did that, or it's totally borked and has lost the ability to understand that all the partitions have officially signed images on them.
Click to expand...
Click to collapse
The strangest thing happened. I disconnected the internal battery overnight. When I reconnected it the watch booted into the system perfectly fine. Then after restarting the watch because of a pairing error, I'm back to square one again.

Help! I cannot unlock the bootloader on my tmo z2 force

I recently replaced my previous z2 after it was damaged. I got my replacement and as always I attempted to unlock the bootloader. Every time I run fastboot oem get_unlock_data regardless if it be on Linux or windows, fastboot or mfastboot it fails. It says <bootloader> Failed to get unlock data. I have tried reinstalling drivers, installing alternate drivers, and reflashing the phone to the latest firmware. I saw someone with a similar thread for the z2 but their solution did not work. I have been using Motorola phones for a long time and had unlocked the bootloader on my previous z2 with no problems. The only thing I didn't do yet is trying to format the userdata partition. I highly doubt that will help anyway. Any help will be greatly appreciated.
Thanks,
vibraniumdroid

vibraniumdroid said:
I recently replaced my previous z2 after it was damaged. I got my replacement and as always I attempted to unlock the bootloader. Every time I run fastboot oem get_unlock_data regardless if it be on Linux or windows, fastboot or mfastboot it fails. It says <bootloader> Failed to get unlock data. I have tried reinstalling drivers, installing alternate drivers, and reflashing the phone to the latest firmware. I saw someone with a similar thread for the z2 but their solution did not work. I have been using Motorola phones for a long time and had unlocked the bootloader on my previous z2 with no problems. The only thing I didn't do yet is trying to format the userdata partition. I highly doubt that will help anyway. Any help will be greatly appreciated.
Thanks,
vibraniumdroid
Click to expand...
Click to collapse
go to bootloader mode and execute 'fastboot getvar all' w/o quotes, post the results but not you imei

41rw4lk said:
go to bootloader mode and execute 'fastboot getvar all' w/o quotes, post the results but not you imei
Click to expand...
Click to collapse
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224CQPCT
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 5786D2FB
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: (removed for privacy)
(bootloader) meid:
(bootloader) date: 08-05-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4385
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-7/9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.241.9.nash_tmo_c.
(bootloader) ro.build.version.full[1]: tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998TMO_20207.117.02.41.01R NUS
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g2c64ab8 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Apr 20 09:21:37 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-180420
(bootloader) gitmic: MBM-3.0-nash_tmo-9869834-180420
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-180420
(bootloader) git:tz: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:hyp: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:devcfg: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:keymaster: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:storsec: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) gitrov: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
finished. total time: 0.242s

wtf xda turned some of it into emojis

Everything looks legit, weird. Make sure you have oem unlocking enabled in developer options, grab the utilities zip from the return to stock thread (since it has known good adb/fastboot), unzip, shift+right click to open a command window from inside the folder. Reboot to bootloader mode, verify connection 'fastboot devices", then try to get the unlock data again.

41rw4lk said:
Everything looks legit, weird. Make sure you have oem unlocking enabled in developer options, grab the utilities zip from the return to stock thread (since it has known good adb/fastboot), unzip, shift+right click to open a command window from inside the folder. Reboot to bootloader mode, verify connection 'fastboot devices", then try to get the unlock data again.
Click to expand...
Click to collapse
I have the oem unlock enabled in Dev options

41rw4lk said:
Everything looks legit, weird. Make sure you have oem unlocking enabled in developer options, grab the utilities zip from the return to stock thread (since it has known good adb/fastboot), unzip, shift+right click to open a command window from inside the folder. Reboot to bootloader mode, verify connection 'fastboot devices", then try to get the unlock data again.
Click to expand...
Click to collapse
Also can u link the thread u were talking about.

vibraniumdroid said:
I have the oem unlock enabled in Dev options
Click to expand...
Click to collapse
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
*Linked to the other thread.

41rw4lk said:
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
Click to expand...
Click to collapse
thnx a lot I really appreciate the help

41rw4lk said:
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
*Linked to the other thread.
Click to expand...
Click to collapse
Will let u know if I make any progress

41rw4lk said:
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
*Linked to the other thread.
Click to expand...
Click to collapse
Did not work

vibraniumdroid said:
Did not work
Click to expand...
Click to collapse
What does it say under the oem unlock switch in developer options? You also mentioned that you had reflashed firmware previously but with a locked bootloader you shouldn't have been able to. Are you able to boot and install twrp? If your bootloader is truly locked, you shouldn't be able to.

41rw4lk said:
What does it say under the oem unlock switch in developer options? You also mentioned that you had reflashed firmware previously but with a locked bootloader you shouldn't have been able to. Are you able to boot and install twrp? If your bootloader is truly locked, you shouldn't be able to.
Click to expand...
Click to collapse
You are able to reflash the latest stock firmware USING FASTBOOT on a locked bootloader IF it is signed by Motorola and this is a well known fact.

41rw4lk said:
What does it say under the oem unlock switch in developer options? You also mentioned that you had reflashed firmware previously but with a locked bootloader you shouldn't have been able to. Are you able to boot and install twrp? If your bootloader is truly locked, you shouldn't be able to.
Click to expand...
Click to collapse
I will try to flash twrp also I have the oem unlock switch checked in Dev options

vibraniumdroid said:
I will try to flash twrp also I have the oem unlock switch checked in Dev options
Click to expand...
Click to collapse
Remember when installing TWRP for the first time you must first 'BOOT" TWRP and then flash the TWRP Installer zip. There are a few other steps to follow after installation so please read the guide if you are unfamiliar with the process. Good luck and happy flashing!
Sent from my Moto Z2 Force using XDA Labs

vibraniumdroid said:
You are able to reflash the latest stock firmware USING FASTBOOT on a locked bootloader IF it is signed by Motorola and this is a well known fact.
Click to expand...
Click to collapse
Not always. There have been instances where the phone has relocked itself and won't flash anything, even official signed. Usually the oem unlock switch is greyed out as well with a message near it, that's why I was curious about the oem unlock switch. Usually there is a status message near the switch itself. In this scenario the phone seems locked but is more in some hybrid lock that doesn't allow much of anything.

fast69mopar said:
Remember when installing TWRP for the first time you must first 'BOOT" TWRP and then flash the TWRP Installer zip. There are a few other steps to follow after installation so please read the guide if you are unfamiliar with the process. Good luck and happy flashing!
Click to expand...
Click to collapse
I know. As I mentioned earlier this is my second z2

41rw4lk said:
Not always. There have been instances where the phone has relocked itself and won't flash anything, even official signed. Usually the oem unlock switch is greyed out as well with a message near it, that's why I was curious about the oem unlock switch. Usually there is a status message near the switch itself. In this scenario the phone seems locked but is more in some hybrid lock that doesn't allow much of anything.
Click to expand...
Click to collapse
Also the switch isn't grayed out. do u think a factory data reset would help? Cuz I don't want to do it if I don't need to.

vibraniumdroid said:
Also the switch isn't grayed out. do u think a factory data reset would help? Cuz I don't want to do it if I don't need to.
Click to expand...
Click to collapse
At this point you don't have much of an option. Everything seems in order, you're able to flash, fastboot commands work, except oem unlock. I would.

41rw4lk said:
At this point you don't have much of an option. Everything seems in order, you're able to flash, fastboot commands work, except oem unlock. I would.
Click to expand...
Click to collapse
Okay I will try tomorrow

Boot to BLANK screen with "fastboot boot twrp-3.2.3-0-nitrogen.img" command !!

Boot to BLANK screen with "fastboot boot twrp-3.2.3-0-nitrogen.img" command !!
I'm trying to flash TWRP through ADB in fastboot mode!
And I'm up to "fastboot boot twrp-3.2.3-0-nitrogen.img", but that booted into a BLANK screen...
I'm stuck again :crying:
Code:
Z:\>fastboot boot twrp-3.2.3-0-nitrogen.img
downloading 'boot.img'...
OKAY [ 8.293s]
booting...
OKAY [ 0.076s]
finished. total time: 8.371s
*** the recovery twrp-3.2.3-0-nitrogen.img has been checked with md5 both from official site, aOK!!
Any help is appreciated!

Hi!
1. What do you want to accomplish by executing that? Because you can just press and hold power and vol up together to go to recovery.
2. What command did you run prior? Im asking because you may typed a diff command that could've affected this?

xgneilx said:
Hi!
1. What do you want to accomplish by executing that? Because you can just press and hold power and vol up together to go to recovery.
2. What command did you run prior? Im asking because you may typed a diff command that could've affected this?
Click to expand...
Click to collapse
1. I'm using that command to make sure TWRP is not replaced by original recovery.
* according to the official instruction: https://twrp.me/xiaomi/xiaomimimax3.html , I tried the hard reboot to twrp by holding pwr+vol-up, but it got stuck in Miui logo. So, I tried to use the flash boot command instead to make sure the twrp works correctly, but it isn't on my Mi Max 3 somehow.
2.
> adb reboot bootloader
> fastboot flash recovery twrp-3.2.3-0-nitrogen.img
> fastboot boot twrp-3.2.3-0-nitrogen.img OR > fastboot reboot && pwr+vol-up buttons
I have googled and found similar situation on different devices, and all seems to solved by a working twrp.
Mine max3 is 4G+64G, not sure if that makes a difference, also it's an official global version that comes with 9.6.4.0
Here's the getvar:
Code:
(bootloader) DP:0x0
(bootloader) token:V...4=
(bootloader) crc:1
(bootloader) cpuid:0x8xxxxxxx
(bootloader) board_version:4.19.0
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3905
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM EMMC
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xC7F7FBE00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xC0000000
(bootloader) secure:yes
(bootloader) serialno:4xxxxxxx
(bootloader) product:nitrogen
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi

Mine came also with official global but with 9.6.7.0. Anyways, there are several other recovery app here, have you tried any of it? When you are able to flash other recovery and boot using it, you may flash twrp from it.

xgneilx said:
Mine came also with official global but with 9.6.7.0. Anyways, there are several other recovery app here, have you tried any of it? When you are able to flash other recovery and boot using it, you may flash twrp from it.
Click to expand...
Click to collapse
Great, can you give me some suggestions? I'm not sure which to try, cause after my x10, it's always TWRP.
Is yours a 4+64 model?

totalz said:
Great, can you give me some suggestions? I'm not sure which to try, cause after my x10, it's always TWRP.
Is yours a 4+64 model?
Click to expand...
Click to collapse
Use OrangeFox. It's one of the better ones.

totalz said:
Great, can you give me some suggestions? I'm not sure which to try, cause after my x10, it's always TWRP.
Is yours a 4+64 model?
Click to expand...
Click to collapse
yup. 4x64 model. Read above post for recommendation.

Problem resetting phone.

Hi, I need a little help getting my phone to work - I have the same issue as on this thread: https://forum.xda-developers.com/htc-10/help/black-screen-oreo-update-t3757142
However I can't seem to connect via adb and I'm guessing this is because I don't have developer options enabled?
Here is the fastboot getvar all results:
C:\Users\Home>C:\Users\Home\Desktop\platform-tools\fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: FA65TBN01081
(bootloader) current-slot:
(bootloader) imei: 3575xxxxxxxx
(bootloader) version-main: 2.41.401.4
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: 11111111
There is a little difference between mine and his issue though, I couldn't check for update as it said something about possible corruption at which point I did a factory reset and immediately the screen when dead after doing so. I contacted htc for help after and wasn't anything they could do as the phone is out of warranty.
The only idea I have would be to use a keyboard to enable usb debugging and I can then try rooting and flashing via adb once that is done?
This video is kinda what I want to do although the steps would be different: https://www.youtube.com/watch?v=741MqF5uQDw
If somebody could provide me the steps needed I would really appreciate it, or give me advice on an alternative option to flash my device I would be incredibly grateful.
Thanks in advance.

Download the 2.41.401 ruu.zip, rename it to 2PS6IMG.zip and copy it to the root of the SDCARD. Boot to download mode and confirm to flash it.
After that the device is back to stock and you can update to Oreo if you wish.
ADB only works in TWRP recovery, in a running OS. Bootloader and download mode only work with fastboot commands.

Thanks, that helped but still black screen, perhaps the screen just died and the reset was a coincidence.
Mr Hofs said:
Download the 2.41.401 ruu.zip, rename it to 2PS6IMG.zip and copy it to the root of the SDCARD. Boot to download mode and confirm to flash it.
After that the device is back to stock and you can update to Oreo if you wish.
ADB only works in TWRP recovery, in a running OS. Bootloader and download mode only work with fastboot commands.
Click to expand...
Click to collapse