Database Develop

Bootloader and S-OFF

Just a question, can anybody execute this on an XL with unlocked bootloader using HTCDev and tell me the output please?
Code:
fastboot oem h
cause I was wondering, if we can execute this to get S-OFF as the bootloader is unlocked so it may give us more permissions?:
Code:
fastboot oem writesecureflag 0
Just wondering if it asks for SMART_IO.CRD or not
Any idea guys?

About htc sensation xl s-off
hi there if you could write set on teminal app see what is writen ?

turkish0852 said:
hi there if you could write set on teminal app see what is writen ?
Click to expand...
Click to collapse
I don't understand what you mean, can you please say it in a clearer way?
thank you

about s-off sensation xl
sorry about that,there's that app called termanel emulater in the market,I was messing around with it, I wrote ( set ) & it showed lots of data, wich I asked what it realy ment if anything,my phone is HTC sensation xl with beats audio permanetly rooted ,bootloader unlocked, s-on,sorry for sbelling.
---------- Post added at 01:04 AM ---------- Previous post was at 12:53 AM ----------
hope it's something worth looking into,type ( set ) then enter,

turkish0852 said:
sorry about that,there's that app called termanel emulater in the market,I was messing around with it, I wrote ( set ) & it showed lots of data, wich I asked what it realy ment if anything,my phone is HTC sensation xl with beats audio permanetly rooted ,bootloader unlocked, s-on,sorry for sbelling.
---------- Post added at 01:04 AM ---------- Previous post was at 12:53 AM ----------
hope it's something worth looking into,type ( set ) then enter,
Click to expand...
Click to collapse
maybe this can help
Code:
ort PATH=/data/local/bin:$PATH
$ su
# set
ANDROID_ASSETS=/system/app
ANDROID_BOOTLOGO=1
ANDROID_DATA=/data
ANDROID_PROPERTY_WORKSPACE=9,65536
ANDROID_ROOT=/system
ANDROID_SOCKET_zygote=10
ASEC_MOUNTPOINT=/mnt/asec
BOOTCLASSPATH=/system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar:/system/framework/HTCDev.jar:/system/framework/HTCExtension.jar:/system/framework/com.htc.framework.jar:/system/framework/com.scalado.util.ScaladoUtil.jar:/system/framework/com.orange.authentication.simcard.jar:/system/framework/android.supl.jar:/system/framework/com.ecrio.sip.jar
EXTERNAL_STORAGE=/mnt/sdcard
IFS='
'
LD_LIBRARY_PATH=/vendor/lib:/system/lib
LOOP_MOUNTPOINT=/mnt/obb
OPTIND=1
PATH=/data/local/bin:/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
PS1='# '
PS2='> '
PS4='+ '
TERM=screen
#

turkish0852 said:
sorry about that,there's that app called termanel emulater in the market,I was messing around with it, I wrote ( set ) & it showed lots of data, wich I asked what it realy ment if anything,my phone is HTC sensation xl with beats audio permanetly rooted ,bootloader unlocked, s-on,sorry for sbelling.
---------- Post added at 01:04 AM ---------- Previous post was at 12:53 AM ----------
hope it's something worth looking into,type ( set ) then enter,
Click to expand...
Click to collapse
nicky1980 said:
maybe this can help
Code:
ort PATH=/data/local/bin:$PATH
$ su
# set
ANDROID_ASSETS=/system/app
ANDROID_BOOTLOGO=1
ANDROID_DATA=/data
ANDROID_PROPERTY_WORKSPACE=9,65536
ANDROID_ROOT=/system
ANDROID_SOCKET_zygote=10
ASEC_MOUNTPOINT=/mnt/asec
BOOTCLASSPATH=/system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar:/system/framework/HTCDev.jar:/system/framework/HTCExtension.jar:/system/framework/com.htc.framework.jar:/system/framework/com.scalado.util.ScaladoUtil.jar:/system/framework/com.orange.authentication.simcard.jar:/system/framework/android.supl.jar:/system/framework/com.ecrio.sip.jar
EXTERNAL_STORAGE=/mnt/sdcard
IFS='
'
LD_LIBRARY_PATH=/vendor/lib:/system/lib
LOOP_MOUNTPOINT=/mnt/obb
OPTIND=1
PATH=/data/local/bin:/sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
PS1='# '
PS2='> '
PS4='+ '
TERM=screen
#
Click to expand...
Click to collapse
thanks a lot guys! but unfortunately that's nt what I needed
I wanted to know if executing the command in the first post from your SDK tools will get you S-OFF or not with unlocked bootloader!

bootloader and s-off
hi there again,i exacuted those commands in the first posts the outcome is as follows;
fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloadre) lock
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.031s]
finished. total time: 0.031s
fastboot oem writesecureflag 0
...
(bootloader) [ERR] Command error !!!
OKAY [ -0.000s]
finished. total time: -0.000s
hope this helps..

bootloader s-off
so any more idea's there,did that help in anyway?

turkish0852 said:
so any more idea's there,did that help in anyway?
Click to expand...
Click to collapse
I'm thinking of something, I dunno
turkish0852 said:
hi there again,i exacuted those commands in the first posts the outcome is as follows;
fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloadre) lock
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.031s]
finished. total time: 0.031s
fastboot oem writesecureflag 0
...
(bootloader) [ERR] Command error !!!
OKAY [ -0.000s]
finished. total time: -0.000s
hope this helps..
Click to expand...
Click to collapse
thanks a lot, HTC has limited the oem commands on their bootloader :/
can you try this please?
fastboot oem rebootRUU
fastboot oem h
fastboot oem writesecureflag 0
to restart your phone:
fastboot reboot
and copy and paste me the output, thank you

C:\Users\Turkish>fastboot oem rebootRUU
...
(bootloader) erase sector 163328 ~ 163839 (512)
OKAY [ 0.484s]
finished. total time: 0.484s
C:\Users\Turkish>fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) lock
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\Turkish>fastboot writesecureflag 0
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\Turkish>fastboot reboot
rebooting...
finished. total time: 0.312s
hope this helps,if anything else please let me know...

turkish0852 said:
C:\Users\Turkish>fastboot oem rebootRUU
...
(bootloader) erase sector 163328 ~ 163839 (512)
OKAY [ 0.484s]
finished. total time: 0.484s
C:\Users\Turkish>fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) lock
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\Turkish>fastboot writesecureflag 0
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\Turkish>fastboot reboot
rebooting...
finished. total time: 0.312s
hope this helps,if anything else please let me know...
Click to expand...
Click to collapse
Thank You!
Seems like there is no real way of gaining S-OFF using oem..
I'll get an XL in several days and will see if I can do anything (but I don't really think I'll be able to anyway)!
We'll need to find a signed Engineering hboot that can be flashed to gain S-OFF after that!
Doesn't seem fair from HTC anyway.. They should unlock and S-OFF too in their unlocking process..
it was supposed to be "fastboot oem writesecureflag 0" I wrote it wrong, but anyway, as writesecureflag isn't accessible using oem, so it's useless to try it.
If anybody has any other idea, please share

bootloader and s-off
i exacuted the wright command again "fastboot oem secuerflag 0" but it gave me that same error "bootloader err Command error !!! "
But when i exacuted command " fastboot oem rebootRUU " the sensation xl screen whent black with black and white HTC letters in the midle of the screen,haven't seen that before...

I have XL with bootloader S-Off....tell me please, what I can do, to let you see, what the difference is

bootloader and s-off
icecream 4.0.1 has just been realeased for the sensation xe 1.0 beta version,i'd like to see this rom on the xl,iv had devices with bootloader s-off its bloody fantastic ,all htc's should come with bootloader s-off its a shame,i sapouse it's a waiting game,im shore great minds a working on it, I don't know if the sensation xl came with bootloader s-off in Australia......

jammysunny said:
I have XL with bootloader S-Off....tell me please, what I can do, to let you see, what the difference is
Click to expand...
Click to collapse
Ship s-off or Eng s-off?

ship s-off.....

turkish0852 said:
i exacuted the wright command again "fastboot oem secuerflag 0" but it gave me that same error "bootloader err Command error !!! "
But when i exacuted command " fastboot oem rebootRUU " the sensation xl screen whent black with black and white HTC letters in the midle of the screen,haven't seen that before...
Click to expand...
Click to collapse
yea, it wont work I know!
Its totally normal abt the rebootRUU thing, it just puts the phone in a state that accepts the flashing of any signed (or unsigned I think) images and many other things we may not know! Haha
jammysunny said:
ship s-off.....
Click to expand...
Click to collapse
interesting! may I ask how did you get it?

Would be good to acheive s-off but unlocked bootloader isnt half bad. We have permanent root and at least one custom rom so guess things will get up to speed as more people get the device. Alpha rev should do their thing soon so we can get full control over this device
Sent from my EPAD using xda premium

I got it with it....so, where you can see the difference between a normal and a ship s-offed Bootloader??
tapatraced with Sensation XL

pull the battery and then boot into hboot.Volume down and power.
eng hboot with S-off is hboot version 1.25.2003.

[Q] Please Help, Broke my HTC One

So yesterday i bought myself a new HTC ONE phone from Egypt, the original owner used it for just 48 hours then sold it. When i received it i found the SuperUser installed and the OTA updates were not installing sin11ce the phone has been modified.
I followed a tutorial on XDA about getting back to stock rom and after flashing custom recovery and moving the stock rom to SD card i flashed it from recovery and it failed in the process.
Now the phone just boots into recovery, can anyone please post me a quick tutorial on getting the stock firmware back? i would really appreciate it.
Here is the info from the recovery:
*** UNLOCKED ***
M7_U PVT SHIP S-OFF RH
CID- 11111111
HBOOT- 1.54.0000
RADIO- 4A.21.3263.04
OpenDSP- v31.120.274.0617
OS- 2.24.401.9
eMMC-boot 2048MB
AUG 9 2013, 16:20:20.0

hello 1.....relock bootloader with htcdev from google
2.....download this ruu and run it from fastboot http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ sorry i fixed the link
3..change cid to 0_32 as bellow
now let's change CID so we can run the RUU.EXE for your ModelID: PN0712000
in bootloader/FASTBOOT USB, change your CID:
Code:
C:\ADB3>fastboot oem writecid CWS__0_32 <-- two underscores
...
(bootloader) Start Verify: 0
OKAY [ 0.023s]
finished. total time: 0.023s
C:\ADB3>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.041s
then take all the avalible updates
good guid here http://forum.xda-developers.com/showthread.php?t=2541082

bygrave said:
hello 1.....relock bootloader with htcdev from google
2.....download this ruu and run it from fastboot http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ sorry i fixed the link
3..change cid to 0_32 as bellow
now let's change CID so we can run the RUU.EXE for your ModelID: PN0712000
in bootloader/FASTBOOT USB, change your CID:
Code:
C:\ADB3>fastboot oem writecid CWS__0_32 <-- two underscores
...
(bootloader) Start Verify: 0
OKAY [ 0.023s]
finished. total time: 0.023s
C:\ADB3>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.041s
then take all the avalible updates
good guid here http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Thanks a lot for your reply. I am downloading the RUU now and till it finishes i have a quick question. Why should i change the CID to (0_32) instead of (11111111)?
Thanks again.

because you cant update with cid 11111111
once you have updated you can change it bk to 11111111 if you like:
---------- Post added at 05:25 PM ---------- Previous post was at 05:21 PM ----------
bygrave said:
because you cant update with cid 11111111
once you have updated you can change it bk to 11111111 if you like:
Click to expand...
Click to collapse
also write cid like this fastboot oem writecid HTC__032
capital HTC, two underscores, then 032

bygrave said:
because you cant update with cid 11111111
once you have updated you can change it bk to 11111111 if you like:
---------- Post added at 05:25 PM ---------- Previous post was at 05:21 PM ----------
also write cid like this fastboot oem writecid HTC__032
capital HTC, two underscores, then 032
Click to expand...
Click to collapse
Thanks a lot, now i get it.
One last question, should i change the CID before running the RUU or after running it?

yes it needs to be changed before u run the ruu. i always run the ruu from in fastboot mode
Sent from my HTC One using Tapatalk

let us know how u got on
Sent from my HTC One using Tapatalk

bygrave said:
let us know how u got on
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Unfortunately although i changed the CID but the RUU failed with an error that the RUU doesn't match my phone model number. :crying:

fastboot getvart all
and give us the results.
u did relock you're bootloader didn't u
Sent from my HTC One using Tapatalk

C:\mini-sdk>fastboot getvart all
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an

DArkSm4sh said:
C:\mini-sdk>fastboot getvart all
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
Click to expand...
Click to collapse
fastboot getvar all
NOT getvarT
Remove your imei and serial number

sorry its fastboot getvar all
Sent from my HTC One using Tapatalk

bygrave said:
sorry its fastboot getvar all
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
The bootloader is still unlocked, should i relock it first?
C:\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4324mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s

yes needs to be locked for it to work
---------- Post added at 11:21 PM ---------- Previous post was at 11:14 PM ----------
just looking for a ruu u are in tawian is that write

did you get this sorted

[Q] HTC ONE Bricked S off

ok I am new here and I have messed up my phone. I can get to bootloader but i'm lost after that. the PC doesn't see the SD card the phone has TWRP but there isn't anything in it to recover to
what should I do. I see a lot about cmd prompt but I know nothing about getting to the phone that way.

Jamesdbritt said:
ok I am new here and I have messed up my phone. I can get to bootloader but i'm lost after that. the PC doesn't see the SD card the phone has TWRP but there isn't anything in it to recover to
what should I do. I see a lot about cmd prompt but I know nothing about getting to the phone that way.
Click to expand...
Click to collapse
if you can get to bootloader you're not bricked.
don't fiddle with your phone - just leave it like it is.
someone here who knows way more about this stuff than I do will be able to tell you what you need to do.

Jamesdbritt said:
ok I am new here and I have messed up my phone. I can get to bootloader but i'm lost after that. the PC doesn't see the SD card the phone has TWRP but there isn't anything in it to recover to
what should I do. I see a lot about cmd prompt but I know nothing about getting to the phone that way.
Click to expand...
Click to collapse
get into fastboot mode and type "fastboot getvar all" in Command Prompt without the inverted commas. Post the output AND REMOVE IMEI AND SERIAL NO.
This is necessary to obtain a little more info abt the phone's current condition

raghav kapur said:
get into fastboot mode and type "fastboot getvar all" in Command Prompt without the inverted commas. Post the output AND REMOVE IMEI AND SERIAL NO.
This is necessary to obtain a little more info abt the phone's current condition
Click to expand...
Click to collapse
How do I get into Carrboro from command?
Go step by step like talking to a four year old..Lol I'm 28

Jamesdbritt said:
How do I get into Carrboro from command?
Go step by step like talking to a four year old..Lol I'm 28
Click to expand...
Click to collapse
Download and install latest android sdk http://developer.android.com/sdk/index.html
download in install latest htc sync (for drivers installation) then uninstall it, the drivers still be installed. http://www.htc.com/www/software/htc-sync-manager/
go to the folder you installed the android sdk then ---> sdk/platform-tools. Adb.exe and fastboot.exe should be in this folder. Always work in this folder (where adb and fastboot.exe are).
boot your phone in bootloader mode, select fastboot and connect usb cable to computer
Right click on a blank space in the folder where fastboot/adb are then select ''open a cmd prompt here''
in the command prompt type
Code:
fastboot getvar all
and copy paste output here MINUS IMEI AND SN
and please tell us what operating system are you using on your ocmputer? windows 7, 8.0 or 8.1?

How do I get into fastboot mode?

Jamesdbritt said:
How do I get into Carrboro from command?
Go step by step like talking to a four year old..Lol I'm 28
Click to expand...
Click to collapse
and how did you messed your phone?
---------- Post added at 03:26 PM ---------- Previous post was at 03:25 PM ----------
Jamesdbritt said:
How do I get into fastboot mode?
Click to expand...
Click to collapse
when you are in bootloarder mode, select ''fastboot''. use vol up and down to navigate then power button to select.
{
"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"
}
When in fastboot mode you'll have a screen similar to this with fastboot highlighted in red:

When I right click there is no cmd option

Jamesdbritt said:
When I right click there is no cmd option
Click to expand...
Click to collapse
sry my bad
hold left SHIFT + right click

Ok found cmd typed above and it came with a list of commands
Update
Flashall
Etc..

Jamesdbritt said:
Ok found cmd typed above and it came with a list of commands
Update
Flashall
Etc..
Click to expand...
Click to collapse
please can you make a screenshot of your cmd prompt and post it here? I want to see the command you typed and the ouput

commands:
update <filename> reflash device from
flashall flash boot + recove
flash <partition> [ <filename> ] write a file to a f
erase <partition> erase a flash parti
format <partition> format a flash part
getvar <variable> display a bootloade
boot <kernel> [ <ramdisk> ] download and boot k
flash:raw boot <kernel> [ <ramdisk> ] create bootimage an
devices list all connected
continue continue with autob
reboot reboot device norma
reboot-bootloader reboot device into
help show this help mess
options:
-w erase userdata and
if supported by par
-u do not first erase
formatting
-s <specific device> specify device seri
or path to device p
-l with "devices", lis
-p <product> specify product nam
-c <cmdline> override kernel com
-i <vendor id> specify a custom US
-b <base_addr> specify a custom ke
default: 0x10000000
-n <page size> specify the nand pa
2048
-S <size>[K|M|G] automatically spars
an
size. 0 to disable

Jamesdbritt said:
commands:
update <filename> reflash device from
flashall flash boot + recove
flash <partition> [ <filename> ] write a file to a f
erase <partition> erase a flash parti
format <partition> format a flash part
getvar <variable> display a bootloade
boot <kernel> [ <ramdisk> ] download and boot k
flash:raw boot <kernel> [ <ramdisk> ] create bootimage an
devices list all connected
continue continue with autob
reboot reboot device norma
reboot-bootloader reboot device into
help show this help mess
options:
-w erase userdata and
if supported by par
-u do not first erase
formatting
-s <specific device> specify device seri
or path to device p
-l with "devices", lis
-p <product> specify product nam
-c <cmdline> override kernel com
-i <vendor id> specify a custom US
-b <base_addr> specify a custom ke
default: 0x10000000
-n <page size> specify the nand pa
2048
-S <size>[K|M|G] automatically spars
an
size. 0 to disable
Click to expand...
Click to collapse
type this command:
Code:
fastboot devices
what is the output?

C:\Users\James\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>FASTBO
T GETVAR ALL
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater t
an
size. 0 to disable
C:\Users\James\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>

Jamesdbritt said:
C:\Users\James\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>FASTBO
T GETVAR ALL -------> 1 ''o'' is missing from fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater t
an
size. 0 to disable
C:\Users\James\SDK\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
Click to expand...
Click to collapse
fastboot is case sensitive don't use capitals letter unless specified
type
''fastboot getvar all'' NOT ''FASTBOT GETVAR ALL''
and there is a letter missing at fastboot

C:\SDK\ADT\sdk\platform-tools>fastboot devices
FA39DS900733 fastboot
C:\SDK\ADT\sdk\platform-tools>

Jamesdbritt said:
C:\SDK\ADT\sdk\platform-tools>fastboot devices
FA39DS900733 fastboot
C:\SDK\ADT\sdk\platform-tools>
Click to expand...
Click to collapse
ok so now type ''fastboot getvar all'' DON'T USE CAPITALS!

C:\SDK\ADT\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.12.41.1112_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.605.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA39DS900733
(bootloader) imei: xxxxxx
(bootloader) meid: xxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3769mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
C:\SDK\ADT\sdk\platform-tools>

Jamesdbritt said:
C:\SDK\ADT\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.12.41.1112_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.605.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei: xxxxxx
(bootloader) meid: xxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3769mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
C:\SDK\ADT\sdk\platform-tools>
Click to expand...
Click to collapse
ok so you want to go back to stock rom or you want to install a custom rom?

alray said:
ok so you want to go back to stock rom or you want to install a custom rom?
Click to expand...
Click to collapse
stock right now I know SuperSU is not installed if that means anything
I was having data connection problems before all this started

Brick or no brick?

Been a long time away from xda (stock android's come a long way). Back with a messed up Moto X. Here's the rundown.
Moto X 2014 dev edition XT1095
Purchased May 2015
Bootloader unlocked upon arrival
Rooted and TWRP for a while, no custom roms, eventually flashed back to stock with firmware image from Motorola
Have received multiple OTA updates since - running latest version
Have encrypted since
Ever since the marshmallow and subsequent updates my phone has been acting strangely - weird periods of rapid battery drain, misreported battery life, etc. Thought it might be a good time for a wipe, so after backing up the few pieces of data I wanted I rebooted to recovery.
Wipe cache appeared to execute properly.
Wipe userdata did not. It failed with an error that I remember including "blkdiscard on partition failed", or something along those lines, and messages about not being able to access recovery logs. Subsequent tries produced the same error. Reboot resulted in a boot loop on the initial warning bootloader unlocked boot animation, would sometimes progress past for a few seconds and freeze on the moto globe animation, and twice got a few seconds past that to a screen that explained my encrypted data was corrupted and I would need to reset my phone, with a big reset button that, when pressed, told me it would reset and restart my phone but simply turned it off.
At this point I figured I had some corrupted partitions, and what better way to repair that than start over and reflash clean? Problem is I naively assumed moto would have the latest and greatest on their firmware page, didn't pay attention to version numbers and just downloaded the highest version on there for the XT1095 - later found it was 5.1, which is obviously a downgrade and not what I wanted. Flashing that image with mfastboot produced an error during each part, starting with gpt.bin. Couple examples.
Code:
C:\Users\Dan\Desktop\motox>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.011s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.092s
Code:
C:\Users\Dan\Desktop\motox>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.399s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.545s
A little troubleshooting led to the realization that I was flashing an old android version, so I found the latest - VICTARA_TMO_XT1095_6.0_MPE24.49-18_cid9_CFC.xml.zip - at the firmware.center website. This produced the same errors.
Here's where I stand.
I've tried fastboot, mfastboot, rsdlite and windroid, nothing works
I can no longer access recovery - attempting to do so produces a red message - "Invalid boot image header!"
Whenever I try to flash an img my phone displays a pink message - "version downgraded for primary gpt", or primary recovery, etc
Attempting to format or erase partitions through fastboot produces a remote failure as well
Motorola Device Manager reports no updates for my device, current version is 24.201.3.victara_tmo.tmo.en.us
Currently my phone is in a fastboot bootloop, but fastboot appears functional - I can reboot-bootloader
The result of getvar all is:
Code:
C:\Users\Dan\Desktop\motox>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6018
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Hynix S8 SDRAM DIE=8Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: TA44909E26
(bootloader) cid: 0x0000
(bootloader) channelid: 0x85
(bootloader) uid: 7A05AE100B000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: prefer not to share, but matches
(bootloader) meid:
(bootloader) date: 05-06-2015
(bootloader) sku: XT1095
(bootloader) iccid: prefer not to share, but matches
(bootloader) cust_md5: 48718E6D7332FB353113EE5EA0335438
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Aug 30 5:20:21 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/victara_tmo/victara:6.0/M
(bootloader) ro.build.fingerprint[1]: PES24.49-18-3/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.3.victara_tmo
(bootloader) ro.build.version.full[1]: .tmo.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8974BP_42352121.25.09.24R VICTARA_T
(bootloader) version-baseband[1]: MO_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g7820355 ([email protected]
(bootloader) kernel.version[1]: ilclbld71) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri May 20 02:41:33 CDT 2016
I'm thinking either my emmc was corrupted to begin with and there was no coming back, or there was a chance at recovering but I bricked after accidentally attempting to downgrade the bootloader, even though it seemed like nothing actually flashed. If anyone has any thoughts I would be grateful, I've been down the rabbit hole today and don't have any answers. If not I suppose it's time for a new phone - or a moto claim, if possible?

try https://mirrors.lolinet.com/firmware/moto/victara/official/TMO/VICTARA_TMO_6.0_MPES24.49-18-3_cid9_CFC.xml.zip
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package.
E.g:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Good luck.

kyo167 said:
try https://mirrors.lolinet.com/firmware/moto/victara/official/TMO/VICTARA_TMO_6.0_MPES24.49-18-3_cid9_CFC.xml.zip
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package.
E.g:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Good luck.
Click to expand...
Click to collapse
Thanks for the quick reply but I'm getting a 403 Forbidden on that download.

Never mind I figured out how to access the file. Downloading now, will report the results. Thanks again.

kyo167 said:
try https://mirrors.lolinet.com/firmware/moto/victara/official/TMO/VICTARA_TMO_6.0_MPES24.49-18-3_cid9_CFC.xml.zip
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package.
E.g:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Good luck.
Click to expand...
Click to collapse
Little different result this time, but the ending is still the same and all flashes fail. No more pink "version downgraded for primary gpt" messages though. Here's the output from the gpt flash. Any thoughts?
Code:
[email protected]:~/Desktop/motox$ sudo fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 5.099s

Next command (fastboot flash motoboot motoboot.img) throws "(bootloader) Failed to erase partition" or not?

kyo167 said:
Next command (fastboot flash motoboot motoboot.img) throws "(bootloader) Failed to erase partition" or not?
Click to expand...
Click to collapse
Yes.
Code:
[email protected]:~/Desktop/motox$ sudo fastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2022 KB)...
OKAY [ 0.082s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 5.258s

Try again with https://mirrors.lolinet.com/firmware/moto/victara/official/TMO/XT1095_VICTARA_TMO-RETUS_6.0_MPES24.49-18-7_cid9_CFC.xml.zip
If no luck, try
https://firmware.center/firmware/Motorola/Moto%20X%20%282nd%20gen-2014%29/Stock/XT1095/VICTARA_TMO_XT1095_6.0_MPE24.49-18_cid9_CFC.xml.zip

Phone Stuck on Bootloader After Magisk Uninstall

I restored my boot.img from within Magisk because I need to OTA update. Now the phone will only boot into the bootloader with the message
AP Fastboot Flash Mode(Secure)
No Bootable A/B Slot
Failed to Boot Linux, falling back to fastboot
Nothing will work through fastboot. I've tried switching slots, re-flashing the boot.img, and re-flashing the ROM, but the flashing won't even start. Every command I try to run brings up a code on the phone that says "cmd: getvar:slot-count." My phone can be found by the fastboot devices command.Has anyone encountered and fixed this before?

doodalydoo said:
I restored my boot.img from within Magisk because I need to OTA update. Now the phone will only boot into the bootloader with the message
AP Fastboot Flash Mode(Secure)
No Bootable A/B Slot
Failed to Boot Linux, falling back to fastboot
Nothing will work through fastboot. I've tried switching slots, re-flashing the boot.img, and re-flashing the ROM, but the flashing won't even start. Every command I try to run brings up a code on the phone that says "cmd: getvar:slot-count." My phone can be found by the fastboot devices command.Has anyone encountered and fixed this before?
Click to expand...
Click to collapse
Just re-flash the system back manually from fastboot. You can find instructions all over the place.

johnjingle said:
Just re-flash the system back manually from fastboot. You can find instructions all over the place.
Click to expand...
Click to collapse
It won't work. When I input the fastboot command into cmd, it doesn't proceed and then I get a code on my phone that says "cmd: getvar:slot-count." No fastboot commands will work, even though my phone is detected as a fastboot device. I don't get it.

doodalydoo said:
It won't work. When I input the fastboot command into cmd, it doesn't proceed and then I get a code on my phone that says "cmd: getvar:slot-count." No fastboot commands will work, even though my phone is detected as a fastboot device. I don't get it.
Click to expand...
Click to collapse
That doesn't sound fun.
Have you tried:
fastboot getvar all
or
fastboot boot ****.img (TWRP image.)
just to see if fastboot can output the details about your phone?

johnjingle said:
That doesn't sound fun.
Have you tried:
fastboot getvar all
or
fastboot boot ****.img (TWRP image.)
just to see if fastboot can output the details about your phone?
Click to expand...
Click to collapse
I turned "Tools mode" on and now I actually get the progress of the fastboot command.
C:\adb>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-suffi: not found
(bootloader) slot-suffixes: not found
(bootloader) max-download-sizestem: not found
target didn't report max-download-size
sending 'system' (524284 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.016s
C:\adb>fastboot flash system system.img_sparsechunk.1
(bootloader) slot-suffi: not found
(bootloader) max-download-: not found
target didn't report max-download-size
sending 'system' (524284 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.016s
C:\adb>fastboot flash system system.img_sparsechunk.2
(bootloader) slot-countad-: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) partition-: not found
target didn't report max-download-size
sending 'system' (524284 KB)...
It freezes after this.
C:\adb>fastboot getvar all
(bootloader) allt-count: not found
getvar:all FAILED (remote failure)
finished. total time: 0.000s
C:\adb>fastboot boot twrp-3.2.3-1-payton.img
downloading 'boot.img'...
OKAY [ 0.642s]
booting...
(bootloader) Failed to load/authenticate boot image: Not Found
FAILED (remote failure)
finished. total time: 0.658s
This is what it says when I try to run the commands you suggested.
Edit: My bootloader was unlocked before this happening, I just want to make sure it didn't relock and that's the problem. When it says "flashing_unlock" in recovery mode, that means the bootloader is unlocked right?

Ok a weird thing happened. Somehow the phone went from a soft brick to a hard brick. It didn't hard brick during the whole time I was trying to fix it. The last thing I did was put it on the charger and when I took it off the charger, it was hard bricked. This actually turned out to be exactly what I needed because it put the phone in the position where I could use the blankflash file. My phone is now working!

Ok it's back to not working again! I managed to get the phone booted, but it kept crashing so I booted into TWRP to wipe the system so I could do a clean install. Now none of the fastboot commands are working again. The recovery mode looks like it supposed to now unlike last time. I'm also able to sometimes run "fastboot getvar all" now, but it doesn't work all the time. I have no clue what is going on.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-190305
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY2253DPJK
I've managed to get the phone to boot up again, but the fastboot commands have also stopped working again. I don't know what to do at this point and I'm also afraid the next thing I do will just break the phone again.. If the phone is booting up properly, why aren't the fastboot commands working?

doodalydoo said:
Ok it's back to not working again! I managed to get the phone booted, but it kept crashing so I booted into TWRP to wipe the system so I could do a clean install. Now none of the fastboot commands are working again. The recovery mode looks like it supposed to now unlike last time. I'm also able to sometimes run "fastboot getvar all" now, but it doesn't work all the time. I have no clue what is going on.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-190305
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY2253DPJK
I've managed to get the phone to boot up again, but the fastboot commands have also stopped working again. I don't know what to do at this point and I'm also afraid the next thing I do will just break the phone again.. If the phone is booting up properly, why aren't the fastboot commands working?
Click to expand...
Click to collapse
Try downloading mfastboot, don't use a script, manually install each file and see what happens after each flash, etc.
For example:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot reboot-bootloader
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
---------- Post added at 06:34 PM ---------- Previous post was at 06:27 PM ----------
doodalydoo said:
Ok it's back to not working again! I managed to get the phone booted, but it kept crashing so I booted into TWRP to wipe the system so I could do a clean install. Now none of the fastboot commands are working again. The recovery mode looks like it supposed to now unlike last time. I'm also able to sometimes run "fastboot getvar all" now, but it doesn't work all the time. I have no clue what is going on.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-190305
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY2253DPJK
I've managed to get the phone to boot up again, but the fastboot commands have also stopped working again. I don't know what to do at this point and I'm also afraid the next thing I do will just break the phone again.. If the phone is booting up properly, why aren't the fastboot commands working?
Click to expand...
Click to collapse
Also, did you have anything like this at the bottom of that fastboot command?
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above

johnjingle said:
Try downloading mfastboot, don't use a script, manually install each file and see what happens after each flash, etc.
For example:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot reboot-bootloader
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
---------- Post added at 06:34 PM ---------- Previous post was at 06:27 PM ----------
Also, did you have anything like this at the bottom of that fastboot command?
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Click to expand...
Click to collapse
The phone is working again and I think for good this time. Getting the fastboot commands to work was just a matter of luck I guess. I had no method, I was just randomly unplugging, plugging in, holding different keys, and powering on and off until I was lucky enough to get it to work. Once the fastboot started working, I just wiped the phone completely and clean flashed the newest ROM. I haven't had any problems since then. I think what caused all of this was I was dirty flashing improperly. I tried picking out the commands I thought were necessary from the ROM flashing commands, but wouldn't erase my data. I must have left out critical flash commands. Just so I'm sure and I don't have to go through this again, will running the ROM flash commands you posted except "mfastboot erase userdata" work to properly flash the ROM while leaving my data intact?

doodalydoo said:
The phone is working again and I think for good this time. Getting the fastboot commands to work was just a matter of luck I guess. I had no method, I was just randomly unplugging, plugging in, holding different keys, and powering on and off until I was lucky enough to get it to work. Once the fastboot started working, I just wiped the phone completely and clean flashed the newest ROM. I haven't had any problems since then. I think what caused all of this was I was dirty flashing improperly. I tried picking out the commands I thought were necessary from the ROM flashing commands, but wouldn't erase my data. I must have left out critical flash commands. Just so I'm sure and I don't have to go through this again, will running the ROM flash commands you posted except "mfastboot erase userdata" work to properly flash the ROM while leaving my data intact?
Click to expand...
Click to collapse
The only line I "usually" usually leave out is the erase "mfastboot user data", unless I am coming from a ROM or want a completely fresh start.