Develop Bugs

[Q] Please Help Soft Brinck, No RUU will take

I have been having call issues with my phone and need to send it back to VZW.
This phone was Rooted, with S-Off and Unlocked in the Bootloader, I started researching today how to put it back to stock and in the process I have simply soft bricked my phone and have tried and exhausted everything I could find.
When I reboot into RUU and try to flash the Decrypted file for my 1.10.65.10 it fails:
C:\fastboot>fastboot flash zip M7RUU.zip
sending 'zip' (1178304 KB)...
OKAY [ 60.146s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 196.594s
I am not able to go into or load any recovery files either, I am only able to do fastboot commands and no adb commands.
I really have searched all over xda forums and have not found the answer
My HTC currently will not boot and is able to fastboot only.
It is Displaying:
TAMPERED
RELOCKED
Security Warning
M7_WLV PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-1.12.42.1104
OpenDSP-v31.120.274.0617
OS-1.10.605.10
eMMC-boot 2048MB
Sep 9 2013, 11:53:38.0
FASTBOOT USB
ETC..
Here are the notes from fastboot get var
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 1.12.42.1104
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.10.605.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA37YS901096
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4011mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-57eb7f637d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please if you have any advice or assistance, I woudl love to hear it I am on Win 7 32bit machine and is the same machine and cable I have used to do all the previous rooting and set it to s-off in the first place.
Thank you

Another error I receive:
C:\fastboot>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.001s]
finished. total time: 0.001s

You must run an encrypted version of the RUU since you are back to S-ON. If you stayed at S-OFF you can run the decrypted RUU. Try to S-OFF again and then PM me and I will send you a link to help you out. If you can't. Run the following RUU. Link below.
http://bit.ly/vzwone-15

Flyhalf205 said:
You must run an encrypted version of the RUU since you are back to S-ON. If you stayed at S-OFF you can run the decrypted RUU. Try to S-OFF again and then PM me and I will send you a link to help you out. If you can't. Run the following RUU. Link below.
http://bit.ly/vzwone-15
Click to expand...
Click to collapse
Not to mention he's not even in ruu mode.
Sent from my HTC6600LVW using Tapatalk

dottat said:
Not to mention he's not even in ruu mode.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
Very tru dottat..
@tomwatez make sure when you hook to usb. In the command
fastboot oem rebootRUU
fastboot flash zip ruu.zip <---- You'll most likely have to do this command twice with the signed encrypted RUU

Flyhalf205 said:
Very tru dottat..
@tomwatez make sure when you hook to usb. In the command
fastboot oem rebootRUU
fastboot flash zip ruu.zip <---- You'll most likely have to do this command twice
Click to expand...
Click to collapse
And yes....if s-on make sure the ruu isn't older than software running on the phone.
Sent from my HTC6600LVW using Tapatalk

Flyhalf205 said:
You must run an encrypted version of the RUU since you are back to S-ON. If you stayed at S-OFF you can run the decrypted RUU. Try to S-OFF again and then PM me and I will send you a link to help you out. If you can't. Run the following RUU. Link below.
http://bit.ly/vzwone-15
Click to expand...
Click to collapse
Thank you I'll give it a shot!

Flyhalf205 said:
You must run an encrypted version of the RUU since you are back to S-ON. If you stayed at S-OFF you can run the decrypted RUU. Try to S-OFF again and then PM me and I will send you a link to help you out. If you can't. Run the following RUU. Link below.
http://bit.ly/vzwone-15
Click to expand...
Click to collapse
Flyhalf205 said:
Very tru dottat..
@tomwatez make sure when you hook to usb. In the command
fastboot oem rebootRUU
fastboot flash zip ruu.zip <---- You'll most likely have to do this command twice with the signed encrypted RUU
Click to expand...
Click to collapse
I actually have been using those commands and have been running it in RUU mode all day, been at it for about 8 hrs trying all sorts of different things.
The thing different now is that I have a link to a signed ru instead... trying it now, its been running for about 10 mins and is at this point:
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.043s]
finished. total time: 0.043s
C:\fastboot>fastboot flash zip RUU.zip
sending 'zip' (1178525 KB)...
OKAY [ 57.957s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...

tomwatez said:
i actually have been using those commands and have been running it in ruu mode all day, been at it for about 8 hrs trying all sorts of different things.
The thing different now is that i have a link to a signed ru instead... Trying it now, its been running for about 10 mins and is at this point:
C:\fastboot>fastboot oem rebootruu
...
(bootloader) start verify: 3
okay [ 0.043s]
finished. Total time: 0.043s
c:\fastboot>fastboot flash zip ruu.zip
sending 'zip' (1178525 kb)...
Okay [ 57.957s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
Click to expand...
Click to collapse
blah blah blah>> nothing to read here

Flyhalf205 said:
Very tru dottat..
@tomwatez make sure when you hook to usb. In the command
fastboot oem rebootRUU
fastboot flash zip ruu.zip <---- You'll most likely have to do this command twice with the signed encrypted RUU
Click to expand...
Click to collapse
Is thsi why you said to run twice?
C:\fastboot>fastboot flash zip RUU.zip
sending 'zip' (1178525 KB)...
OKAY [ 57.957s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 1031.357s

tomwatez said:
Is thsi why you said to run twice?
C:\fastboot>fastboot flash zip RUU.zip
sending 'zip' (1178525 KB)...
OKAY [ 57.957s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 1031.357s
Click to expand...
Click to collapse
Yes. Run it again. and It should run fine.

looks successful.. Now before I do anything else.. end goal is stock but want to wait after I get my replacement tomorrow to see what is on it.
what is the next step from here:
(bootloader) [RUU]UZ,radio,94
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,34
(bootloader) [RUU]WP,radio,68
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,100
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,100
(bootloader) ...... Successful
OKAY [410.428s]
finished. total time: 468.138s

tomwatez said:
looks successful.. Now before I do anything else.. end goal is stock but want to wait after I get my replacement tomorrow to see what is on it.
what is the next step from here:
(bootloader) [RUU]UZ,radio,94
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,34
(bootloader) [RUU]WP,radio,68
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,100
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,100
(bootloader) ...... Successful
OKAY [410.428s]
finished. total time: 468.138s
Click to expand...
Click to collapse
Your all good. So why are you getting it replaced after we just got it to stock?

Been having lots of issues with breaking up and dropped calls, not to mention the speaker is crackling..Verizon exhausted the troubleshooting and said we will send you a replacement. I wanted to try putting it back to stock to see if those things were still happening... So now that it is stock and I had s-off previously should I be good to go to redo s-off and rom, root it if I chose to keep it and it works better

tomwatez said:
Been having lots of issues with breaking up and dropped calls, not to mention the speaker is crackling..Verizon exhausted the troubleshooting and said we will send you a replacement. I wanted to try putting it back to stock to see if those things were still happening... So now that it is stock and I had s-off previously should I be good to go to redo s-off and rom, root it if I chose to keep it and it works better
Click to expand...
Click to collapse
Hope it all works out...I fear the supply of pre-4.3 phones is dwindling
Sent from my Nexus 7 using Tapatalk

dottat said:
Hope it all works out...I fear the supply of pre-4.3 phones is dwindling
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
The directions and link that was listed worked perfectly and I'm back up and running.
Thank you All! Lets see if the one I get is pre 4.3 or not.. I may just send it back if mine is working better.

tomwatez said:
The directions and link that was listed worked perfectly and I'm back up and running.
Thank you All! Lets see if the one I get is pre 4.3 or not.. I may just send it back if mine is working better.
Click to expand...
Click to collapse
Got the replacement today, sounds and looks great.. Best of all it was on 4.2.2 and 1.10.605.10, s-on, however the hboot is on 1.54.
I'm trying s-off right now and it seems to be going good so far, will report if it doesn't unlock...
Thanks again for your great support!

Sorry the pros are helping
Sent from my HTC6500LVW using XDA Premium HD app

C:\adb>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1178525 KB)...
OKAY [ 53.441s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 186.403s
I'm using the instructions from this thread: http://forum.xda-developers.com/showthread.php?p=51514093
what should I do? please help me

You can S-off an m7vzw on 4.4.2 now. Use WeakSauce.apk for temp root, then firewater to s-off.
http://forum.xda-developers.com/showthread.php?t=2699089

[Q] ViperOne 4.0.0 Wifi problem; How to go back to stock International HTC M8

Yesterday I upgraded to to the ViperOne Lollipop ROM from the viperOne 3.2.2. kitkat and WiFi keeps getting disconnected after some time. Usually happens after ~45 minutes of inactivity. Turning Wifi on and off doesn't help, on the contrary it doesn't detect any Wifi after I do WiFi Off -> On. After restarting the phone Wifi comes back and I face the same problem all over again after a little while.
Phone info is as follows(took out Serial No. and IMEI):
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any Solutions?
Should I revert back to stock, get the Lollipop OTA and then install ViperOne? If that will help can someone please let me know how to revert back to stock. The backup that I had before I flashed viperOne kitkat got corrupted.
Thanks XDA

http://forum.xda-developers.com/showthread.php?t=2735235

You need firmware 4, look in the op, otherwise its in the op of maximus hd

EddyOS said:
http://forum.xda-developers.com/showthread.php?t=2735235
Click to expand...
Click to collapse
This requires S-OFF. I am still S-ON.

a3adil said:
This requires S-OFF. I am still S-ON.
Click to expand...
Click to collapse
Not all of it. You just need step 3

EddyOS said:
Not all of it. You just need step 3
Click to expand...
Click to collapse
K thanks. Let me try this out.

EddyOS said:
Not all of it. You just need step 3
Click to expand...
Click to collapse
which recovery version should I be using for this? the latest one .401 or the one already on the phone i.e. 3.28.401.6 ? I am confused. I tried both (maybe not a smart thing to do) and this was the result. My Steps so far and yes I am using a macbook.
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot oem lock
ERROR: could not get pipe properties
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 1.187s
Imraans-MacBook-Prolatform-tools imraanameen$ ./adb shell
error: device not found
error: device not found
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot flash recovery recovery.img
ERROR: could not get pipe properties
target reported max download size of 1826414592 bytes
sending 'recovery' (16092 KB)...
OKAY [ 1.993s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.568s
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot reboot-bootloader
ERROR: could not get pipe properties
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.010s
Imraans-MacBook-Prolatform-tools imraanameen$ ./adb shell
error: device not found
error: device not found
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot oem rebootRUU
ERROR: could not get pipe properties
...
(bootloader) Start Verify: 3
OKAY [ 0.010s]
finished. total time: 0.010s
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot devices
ERROR: could not get pipe properties
SH44XWM02716 fastboot
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot flash zip r
recovery.img ruu.zip
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot flash zip ruu.zip
ERROR: could not get pipe properties
target reported max download size of 1826418688 bytes
sending 'zip' (1536838 KB)...
OKAY [ 47.189s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 103.571s
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot reboot
ERROR: could not get pipe properties
rebooting...
finished. total time: 0.008s
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot flash recovery recovery_4.16.401.10.img
ERROR: could not get pipe properties
target reported max download size of 1826418688 bytes
sending 'recovery' (16044 KB)...
OKAY [ 1.670s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.243s
Imraans-MacBook-Prolatform-tools imraanameen$ ./fastboot flash recovery recovery_3.28.401.6.img
ERROR: could not get pipe properties
target reported max download size of 1826418688 bytes
sending 'recovery' (14556 KB)...
OKAY [ 1.540s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.059s
Imraans-MacBook-Prolatform-tools imraanameen$

Step 3 does not say you need to fastboot flash stock recovery, neither 4.16.401.10 nor 3.28.401.6. And you can't fastboot flash a recovery after bootloader is relocked.
a- relock bootloader - you already did
b- ./fastboot oem rebootRUU
c- ./fastboot flash zip ruu.zip
d- ./fastboot reboot-bootloader

ckpv5 said:
Step 3 does not say you need to fastboot flash stock recovery, neither 4.16.401.10 nor 3.28.401.6. And you can't fastboot flash a recovery after bootloader is relocked.
a- relock bootloader - you already did
b- ./fastboot oem rebootRUU
c- ./fastboot flash zip ruu.zip
d- ./fastboot reboot-bootloader
Click to expand...
Click to collapse
I unlocked the bootloader again and followed the same steps you mentioned. Always came out with Failed message and some error. I should mention again that I am still S-ON. What would you advise?

Because your device is S-On, you need to relock bootloader then follow b, c, d
If you prefer the backup/restore method, get your backup here : http://forum.xda-developers.com/showpost.php?p=56979449&postcount=2960
Use the 3.28.401.9 instead of 3.28.401.6 and its stock recovery img.
1. Restore backup
2. fastboot flash 3.28.401.9 recovery.img
3. Reboot do OTA
For these, no need to relock bootloader
Good luck.. gotta go now

ckpv5 said:
Because your device is S-On, you need to relock bootloader then follow b, c, d
Click to expand...
Click to collapse
I've honestly tried that twice already. Let me try it again just so I can post the Error that comes up

Read what I update in previous post
If that also cannot work, I'll tell other method when I'm back in next 5 or 6 hours.

[Q] Unknown command "unlocktoken" and "43 main version check fail"

[Q] Unknown command "unlocktoken" and "43 main version check fail"
Hello,
I try to apply a CustomROM to a Wildfire S. Two years ago I did it with another Wildfire S but the current device doesn't work...
At first some details of the device:
Code:
$ fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0099
(bootloader) version-baseband: 7.60.39.12M
(bootloader) version-cpld: None
(bootloader) version-microp: 0451
(bootloader) version-main: 20.26.401.4
(bootloader) serialno: SH26LTR04002
(bootloader) imei: 359144046869429
(bootloader) product: marvel
(bootloader) platform: HBOOT-7227
(bootloader) modelid: PG7610000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3940mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 510e562c
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.005s
I received the unlock token by HTCdev but on flashing a error message appears that the command is unknown.
Code:
$ fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 0.000s
HBOOT is in version 1.09.0099 - the same as mentioned in RUU "HTC EU". Unfortunally I can't figure out what version of Fastboot I have. So I've tried to flash the newest one.
I downloaded the "HTC EU"-RUU, extracted the rom.zip by executing with wine and tried to flash.
Code:
$ fastboot oem rebootRUU
...
OKAY [ 0.098s]
finished. total time: 0.098s
$ fastboot flash zip rom.zip
sending 'zip' (212 KB)...
OKAY [ 0.513s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 7.146s
It doesn't will be sucessfull even if I repeat the flash command.
Does anybody know what's going wrong? Am I right that I need to flash the new RUU. Why that doesn't work?
Bye Markus

The execution of the RUU.exe on a fresh installed WinXP showed that there was already a newer version than necessary. The problem was simply the old version of Linux' fastboot binary of Ubuntu's repository. Another old one by my own or the binary of htcdev.com worked fine.

[HELP] My Htc one M8 phone will not boot.

hello, i'm new to this site and to rooting. I believe i tried to root this phone probably a good 3 years ago and failed, so i left it. i cant remember exactly what failed. but now my htc one m8 will not boot, however I can access the basic recovery however i can not factory reset it from here. just swaps to the htc logo. I can not flash TWRP or any type of recovery, it is unlocked and s-on. here is my error when i try and flash the recovery:
Invalid sparse file format at header magic
Sending sparse 'recovery' 1/2 (16380 KB) OKAY [ 1.710s]
Writing sparse 'recovery' 1/2 FAILED (remote: image error! (BootMagic check fail))
Finished. Total time: 1.898s
i don't know any other information i should give in this post ill try my best and give any info required, i just dont know what is., I deeply appreciate any effort in getting my device back up and running

heres more info
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.11.161.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0b9a12e3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001

pmccaul1410 said:
Writing sparse 'recovery' 1/2 FAILED (remote: image error! (BootMagic check fail))
Click to expand...
Click to collapse
You have the M8s variant. Are you flashing the TWRP version specific to the M8s? It is required, as the TWRP for the "standard" M8 will not work (and probably the reason for the error message).
See the M8s section for more info, the right TWRP version, etc: https://forum.xda-developers.com/htc-one-m8/one-m8s-general

hi, thanks for taking the time to help me out. i flashed the recovery from there and got a different error
target reported max download size of 16773120 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 4941824 is not a multiple of the block size 4096
sending sparse 'recovery' (16379 KB)...
error: write_sparse_skip_chunk: don't care size 4941824 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 4941824 is not a multiple of the block size 4096
OKAY [ 1.827s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.845s

De-Bricking Support and Questions for my XT1789-06

Hi,
I am stuck, and figured I need to ask you guys some questions.
As I have done previously with other phones, I bought a used Moto Z2 Force to fix up. I bought a bricked phone with no hardware problems. The previous user said he updated it in Stock to Android Pie, and after the update the phone wouldnt boot anymore, so he sold it. I figured I would just debrick it and use it with LineageOS.
But I didnt succeed, and dont know what else to try, so Im asking you.
It is a XT-1789-06 bought in Germany.
So: When I start the phone up, it says: "Your device is corrupt. it cant be trusted and will not boot." and that I should turn to the official Motorola unlocking portal.
I did that, followed the instructions, was able to boot into fastboot mode, and got the Code, and with that the one from motorola, but when I try the
Code:
fastboot oem unlock XXXXXXXXXXXXXX
I get the following:
Code:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.008s]
finished. total time: 0.008s
Obviously I cant do that, because the phone wont boot up. But event though it says OKAY, there is no change to the variable: securestate: flashing_locked, and i still cant flash anything, and the startup error remains the same. When I try "fastboot flashing unlock" I get the same message.
So, the next thing I tried was the LMSA software. It did the Flash-> rescue-> choose model XT1789-06 -> and flash, and it downloaded the NASH_PPX29.159_23_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip ROM, and apparently did something to the phone, but it didnt change the outcome, still the phone shows the same error on bootup.
Then I did a fastboot -w, after which the phone didnt show anything anymore on bootup, just blank screen, and the tried both steps described above again, stil no change.
Then I tried to boot into the newest Twrp image with "fastboot boot twrp.....img" but it fails with the error: too many links.
Then I tried all of the above in Ubuntu, then on windows with the fastboot files given in the guide in this forum, and then with the mfastboot, that I found somewhere else. Same outcome.
Then I tried just flashing the Stockrom that LMSA downloaded with the flashall method from the same guide, but flashing fails with: Permission denied.
So, do you have any ideas what more I can try to unbrick this phone? I will be happy to give you any further information. I will append fastboot getvar all as soon as I reboot my PC in 2 min.
Edit:
Code:
F:\motoz2force>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-cd73d31dc
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224ZCL4C
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 81C2C8EF
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 05-17-2018
(bootloader) sku: XT1789-06
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4120
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:8.0.0
(bootloader) ro.build.fingerprint[1]: 9-34-21/21:user/release-
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.481.21.
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NE
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g3c2
(bootloader) kernel.version[1]: [email protected]) (gcc version 4
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SM
(bootloader) kernel.version[3]: Fri Nov 2 11:29:48 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_retail-cd73d31dc-180828
(bootloader) git:xbl: MBM-3.0-nash_retail-9869834-180828
(bootloader) git:pmic: MBM-3.0-nash_retail-9869834-180828
(bootloader) git:rpm: MBM-3.0-nash_retail-b13e14f-180828
(bootloader) git:tz: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:hyp: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:devcfg: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:cmnlib: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:keymaster: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:storsec: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:prov: MBM-3.0-nash_retail-22c9393-190327
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(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: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 1
all: listed above
finished. total time: 0.177s
Edit 2: While I can boot into fastboot mode, when I try to start recovery mode from there, I get the same "Your device is corrupt", so no adb for me.
Edit3:
"fastboot -w" results in:
Code:
F:\motoz2force>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.012s

It's odd that it says 'a' is unbootable, most updates and roms usually go to 'b' so if there was trouble I'd expect it to be on 'b' slot.. Anyways, it's possible that the chain of trust is corrupt and you can try to blankflash to remedy that and hopefully be able to flash (even with a locked bootloader). You can follow this guide to try and blankflash, if successful then you can try to flash your firmware again. *Note - with a locked bootloader you can only flash the same firmware or newer, that means you should try the one that was downloaded by lmsa. Also, look by your charger port to verify that it is indeed an -06 variant and not just saying -06 because that was what was flashed.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
If no success all around, you can try switching slots and making 'a' the active slot. Once it is active, try to boot it and see if it will, if not, try flashing the firmware you have on that slot.

Thank you for your help. Unfortunatley it didnt get me very far. I installed the drivers on my Vista-PC. When I executed the blank-flash.bat It just said <waiting for device>. Then I removed Motorola and te qualcomm drivers, rebooted, installed the qualcomm-drivers again, rebooted, but then in the device manager the phone just showed up as "Fastboot nash S" without proper drivers. I couldnt get the qualcomm drivers to recognize the device. blank-flash.bat still showed the same thing.
Other ports, same behaviour.
Then I reinstalled moto drivers to test the other commands.
When I tried "fastboot oem blankflash" I got:
Code:
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: 0.005s
Then I tried
Code:
F:\motoz2force>fastboot set_active a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.008s
I checked next to the charging port, it is really a XT1789-06.
Stuck again. Any other pointers? that would be so great. thanks in advance. I am still learning a lot here, even without progress.

I'm in the same situation, but with an xt1789-05, but it turns on normal, but I don't have Wi-Fi and no data network, and I've tried everything to remove the OEM lock, but without success, and whenever I try a ROM new, it gives me bootloader failure or error.

I'm sure your command to set the other slot is wrong fastboot --set-active=a
As for the blankflash, you need to be in edl mode which isn't always the easiest to get into manually and it's even harder when your system is jumbled. (You think it would be easier since that's when you need it). Either way, that's why blankflash isn't running.

When I wanted to get into edl mode I was holding volume up+power while connecting USB to PC.

OK, thanks for your further tips.
So my goal is to get the phone into edl/blankflash mode, correct?
I would consider myself successful if theres a device showing up in the windows device manager thats called "Qualcomm HS-USB QDLoader 9008" or something similar, correct? Alternatively if the QFIL-Tools recognizes a port.
What I tried:
"fastboot oem blankflash" in fastboot mode, unsuccessful, results shown in a previous post.
Pressing Volume up + power while plugging the phone in, nothing happens.
And I even tried this: https://www.youtube.com/watch?v=DexLELi04XY, but nothing happens, neither the phone showing anything, nor the PC recognizing any device.
... to bad.
I tried to follow this Guide: https://www.droidsavvy.com/unbrick-qualcomm-mobiles/ , but when I try to set the variables in the admin terminal for the first step, it says (translated) "The storage for the startup-configuration files could not be opened. The system could not find the files."
I am close to giving up here. A shame, I really had my hopes up, but I am kind of out of my league here.

You should try running the lmsa tool again. Were you ever successful in switching slots? If you're unsure of the syntax, type fastboot --help that should show you the proper way. Blankflash should be your last option.

wolzotan said:
OK, thanks for your further tips.
So my goal is to get the phone into edl/blankflash mode, correct?
I would consider myself successful if theres a device showing up in the windows device manager thats called "Qualcomm HS-USB QDLoader 9008" or something similar, correct? Alternatively if the QFIL-Tools recognizes a port.
What I tried:
"fastboot oem blankflash" in fastboot mode, unsuccessful, results shown in a previous post.
Pressing Volume up + power while plugging the phone in, nothing happens.
And I even tried this: https://www.youtube.com/watch?v=DexLELi04XY, but nothing happens, neither the phone showing anything, nor the PC recognizing any device.
... to bad.
I tried to follow this Guide: https://www.droidsavvy.com/unbrick-qualcomm-mobiles/ , but when I try to set the variables in the admin terminal for the first step, it says (translated) "The storage for the startup-configuration files could not be opened. The system could not find the files."
I am close to giving up here. A shame, I really had my hopes up, but I am kind of out of my league here.
Click to expand...
Click to collapse
Hi There I have same situation as you, did you fix your phone?
and how you fixed your phone?
I have XT1789-05, please help me, thanks a lot

hi AHMN48, i saw your posts around and figured you have the same problem. I have not yet found a solution unfortunately.
I have tried some more suggestions made here:
Code:
F:\motoz2force>fastboot --set_active=_a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.016s
Code:
F:\motoz2force>fastboot set_active a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.016s
Code:
F:\motoz2force>fastboot reboot emergency
rebooting into emergency download (EDL) mode...
OKAY [ 0.000s]
finished. total time: 0.000s
I got really excited when that happened, but it just came up in fastboot mode again.
this is my screen, if it helps anything
and I tried those commands on all of my usb ports, and most of the ports on my docking station. Its a Lenovo W520, and I have windows 7 and Ubuntu 18.04 available.

Anyways, the only thing I can do to the phone that apparently does something ist the rescue-flash with LMSA. When I do that, It shows the whole "Your device is corrupt"-Thing, and the yellow line from the fastboot screen linked above that says "Software status: modified" vanished. This line reappears as soon as I try to send any of the above fastboot commands, be it the slo-switching-thing or "fastboot -w", doesnt matter. As soon as this happens, the phone also doesnt show the "Your device is corrupt"-alert anymore too, just a black screen. then I rescue flash with LMSA again, and so on.
I tried RSD lite, and it recognizes a device called "fastboot nash S" and status "connected...", but when I try to flash anything, it tells me: "The phone failed to switch to fastboot mode" even though it still is in fastboot mode from the beginning. But Im also not sure if Im doing it right, because i dont know which of the decompressed files from the stock-rom Im supposed to choose for a flashfile

wolzotan said:
Anyways, the only thing I can do to the phone that apparently does something ist the rescue-flash with LMSA. When I do that, It shows the whole "Your device is corrupt"-Thing, and the yellow line from the fastboot screen linked above that says "Software status: modified" vanished. This line reappears as soon as I try to send any of the above fastboot commands, be it the slo-switching-thing or "fastboot -w", doesnt matter. As soon as this happens, the phone also doesnt show the "Your device is corrupt"-alert anymore too, just a black screen. then I rescue flash with LMSA again, and so on.
I tried RSD lite, and it recognizes a device called "fastboot nash S" and status "connected...", but when I try to flash anything, it tells me: "The phone failed to switch to fastboot mode" even though it still is in fastboot mode from the beginning. But Im also not sure if Im doing it right, because i dont know which of the decompressed files from the stock-rom Im supposed to choose for a flashfile
Click to expand...
Click to collapse
RSD is a bit antiquated and we use a flashall.bat in the command prompt to do the same thing. In your OP you posted your getvar output and it looks like it still has oreo on it. Whether lmsa has actually done anything and flashed pie, it would appear not according to you. Run fastboot getvar all again and look at your build fingerprint, if it is still oreo 8.0 then lets try flashing the last oreo version instead of trying to jump to pie.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

ok. Thanks so much 41rw4lk, for walking me through this. Still no luck unfortunately.
I ran the following commands on a new laptop, new windows 10, that I hadnt tried before. However the outcome was identical, as far as i see.
I did download the firmware you linked. I ran the preparation.bat, and then the flashfile.bat. this is the log. It shows the same error messages, that I got with the Pie firmware.
Code:
max-sparse-size: 268435456
finished. total time: 0.000s
...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.234s]
finished. total time: 0.250s
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.547s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.656s
target reported max download size of 536870912 bytes
sending 'modem_a' (97411 KB)...
OKAY [ 6.896s]
writing 'modem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 6.896s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.297s]
writing 'fsg_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.312s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4496 KB)...
OKAY [ 0.219s]
writing 'bluetooth_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.234s
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.828s]
writing 'dsp_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.844s
target reported max download size of 536870912 bytes
sending 'logo_a' (3524 KB)...
OKAY [ 0.172s]
writing 'logo_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.187s
target reported max download size of 536870912 bytes
sending 'boot_a' (23353 KB)...
OKAY [ 1.172s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.172s
target reported max download size of 536870912 bytes
sending 'system_a' (516200 KB)...
OKAY [ 30.593s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 30.608s
target reported max download size of 536870912 bytes
sending 'system_a' (522116 KB)...
OKAY [ 26.218s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 26.233s
target reported max download size of 536870912 bytes
sending 'system_a' (519014 KB)...
OKAY [ 25.927s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 25.927s
target reported max download size of 536870912 bytes
sending 'system_a' (516292 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 126.811s
target didn't report max-download-size
sending 'system' (523200 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
target didn't report max-download-size
sending 'system' (413555 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
target didn't report max-download-size
sending 'system_b' (515182 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
target didn't report max-download-size
sending 'system_b' (319593 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
target didn't report max-download-size
sending 'oem' (163061 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
erasing 'modemst1'...
FAILED (command write failed (No error))
finished. total time: -0.000s
erasing 'modemst2'...
FAILED (command write failed (No error))
finished. total time: 0.000s
erasing 'carrier'...
FAILED (command write failed (No error))
finished. total time: -0.000s
erasing 'cache'...
FAILED (command write failed (No error))
finished. total time: 0.000s
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: -0.000s
erasing 'ddr'...
FAILED (command write failed (No error))
finished. total time: 0.000s
target didn't report max-download-size
sending 'fsg' (5600 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4496 KB)...
OKAY [ 0.270s]
writing 'bluetooth_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.290s
...
OKAY [ -0.000s]
finished. total time: -0.000s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
-------------------------------------------------------------------------
And then a current flashboot getvar all:
Code:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190705
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224ZCL4C
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 81C2C8EF
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 05-17-2018
(bootloader) sku: XT1789-06
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3922
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:8.0.0/OPXS27.10
(bootloader) ro.build.fingerprint[1]: 9-34-21/21:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.481.21.nash.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NED
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g3c2ab17 (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 Nov 2 11:29:48 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_retail-43c7c77-190705
(bootloader) git:xbl: MBM-3.0-nash_retail-4fc2afc-190705
(bootloader) git:pmic: MBM-3.0-nash_retail-4fc2afc-190705
(bootloader) git:rpm: MBM-3.0-nash_retail-404f7ba-190705
(bootloader) git:tz: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:hyp: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:devcfg: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:cmnlib: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:keymaster: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:storsec: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:prov: MBM-3.0-nash_retail-3537781-190705
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 4
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.147s
It seems at some point some command was successful in switching the slots. Strange... I am really fishing in the dark here.
Still the Phone says: Device corrupted, and to unlock the bootloader, and when I try t unlock the bootloader in fastboot, it still tells me to check "OEM Unlocking" in the developer options.

You won't be able to unlock the bootloader until you're able to boot, sign in, and enable oem unlocking in dev options. Since it changed a few things around, try running the lmsa tool again.

NOthing new here. Ran LMSA again, it says "flash successful", but on reboot: "Device corrupt, wont boot, unlock bootloader". Then I tried "fastboot -w", but it showed the same results again as above. Then again LMSA, same behaviour again.
I think Ill just try to sell this thing again.
What kind of stupid error message is this? I shall unlock the bootloader because its bricked, but I have to boot it into OEM to unlock the bootloader?

wolzotan said:
NOthing new here. Ran LMSA again, it says "flash successful", but on reboot: "Device corrupt, wont boot, unlock bootloader". Then I tried "fastboot -w", but it showed the same results again as above. Then again LMSA, same behaviour again.
I think Ill just try to sell this thing again.
What kind of stupid error message is this? I shall unlock the bootloader because its bricked, but I have to boot it into OEM to unlock the bootloader?
Click to expand...
Click to collapse
Make sure you're running lmsa and such as an admin, some users depending on their pc have had to pay attention to this, while most don't.

Yeah I did that.