Database Users

[Q] Did I brick my Nexus 4?

Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil

I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?

ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.

Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.

aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).

aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.

You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app

try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688

Okay, thanks guys. I'm on it. Will let you know when I'm done.

That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd

I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?

aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.

chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images

aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.

chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:

Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!

Stuck in recovery after OTA but stupidly formatted SD card...need help please!

Hi all,
I have an LG D802, was running standard ROM just rooted and with PhilZ recovery. Well I was silly and tried an OTA update, and got stuck at recovery...unfortunately I panicked, cleared everything and tried to flash another ROM but I'm still stuck at recovery.
I tried the instructions in the thread about being stuck after an OTA update but as I;ve formatted the sd partition it didn't work.
I want to go back to stock, I just have no idea how....I have ADB access though if that helps! I'm not really experienced in this kind of thing so please dumb it down for me!
Any help much appreciated!
Callum

calistheman said:
Hi all,
I have an LG D802, was running standard ROM just rooted and with PhilZ recovery. Well I was silly and tried an OTA update, and got stuck at recovery...unfortunately I panicked, cleared everything and tried to flash another ROM but I'm still stuck at recovery.
I tried the instructions in the thread about being stuck after an OTA update but as I;ve formatted the sd partition it didn't work.
I want to go back to stock, I just have no idea how....I have ADB access though if that helps! I'm not really experienced in this kind of thing so please dumb it down for me!
Any help much appreciated!
Callum
Click to expand...
Click to collapse
can you get into download mode either try the adb reboot download mode or turn phone entirely off and hold volume up(only volume up) and plug it into the pc usb, if you can use the back to stock guide to get your phone working again

XxZombiePikachu said:
can you get into download mode either try the adb reboot download mode or turn phone entirely off and hold volume up(only volume up) and plug it into the pc usb, if you can use the back to stock guide to get your phone working again
Click to expand...
Click to collapse
hi no I cannot get in to download mode by any means.

calistheman said:
hi no I cannot get in to download mode by any means.
Click to expand...
Click to collapse
have you tried adb pushing/sideloading a rom and flashing to see if it helps?

XxZombiePikachu said:
have you tried adb pushing/sideloading a rom and flashing to see if it helps?
Click to expand...
Click to collapse
Yes trued flashing a custom ROM, however in my haste to try and stop the OTA forcing me to recovery I may have formatted some partitions I shouldnt have.
Can I restore everything by downloading the kdz with all the correct IMG files in, converting to a flash able zip (saw a guide on here) and trying that?

calistheman said:
Yes trued flashing a custom ROM, however in my haste to try and stop the OTA forcing me to recovery I may have formatted some partitions I shouldnt have.
Can I restore everything by downloading the kdz with all the correct IMG files in, converting to a flash able zip (saw a guide on here) and trying that?
Click to expand...
Click to collapse
Yes that is possible to do I should know because we have something like that for d800
Sent from LG-G2 D800 on AEONFLEX 4.4.2

[Q] File recovery From Bootloop'ed Nexus 4

Hi,
I Need help .
I have nexus 4 with stock ROM and stock recovery.
Two days after OTA update to Lollipop, the phone got stuck on boot-loop.
The problem is that on the phone i have a very important voice recording of a cop that says he will lie in court.
The court time is coming and i need that recording!
Everywhere i looked, no one has an idea how to recover a boot-loop'ed phone.
The 2 options that people recommended are:
1. RE-Flash the ROM.
Maybe it wont delete the files.
2. Wipe everything and hope that the file is recoverable with one of the software's.
A. What do you recommend?
B. Did someone try any of the recovering software's with any luck of actually recovering?

Your bootloader is locked, correct?

ashyossi said:
Hi,
I Need help .
I have nexus 4 with stock ROM and stock recovery.
Two days after OTA update to Lollipop, the phone got stuck on boot-loop.
The problem is that on the phone i have a very important voice recording of a cop that says he will lie in court.
The court time is coming and i need that recording!
Everywhere i looked, no one has an idea how to recover a boot-loop'ed phone.
The 2 options that people recommended are:
1. RE-Flash the ROM.
Maybe it wont delete the files.
2. Wipe everything and hope that the file is recoverable with one of the software's.
A. What do you recommend?
B. Did someone try any of the recovering software's with any luck of actually recovering?
Click to expand...
Click to collapse
If your bootloader is unlocked you can try flashing TWRP recovery which has a built in file manager and mtp function to copy files to computer. You can also try to "dirty flash" another lollipop rom which will not wipe the data, but may not work.

Yeah, this is the only option, however, this can only happen if his bootloader is unlocked

lolcakes203 said:
Yeah, this is the only option, however, this can only happen if his bootloader is unlocked
Click to expand...
Click to collapse
unfortunately, the bootloader is locked.
what are the chances that "Dirty Flash" wont delete the files?
and what rom should i flash? the same build or maybe try to flash kitkat insted...?

ashyossi said:
unfortunately, the bootloader is locked.
what are the chances that "Dirty Flash" wont delete the files?
and what rom should i flash? the same build or maybe try to flash kitkat insted...?
Click to expand...
Click to collapse
Unfortunately, as far as I know you can't flash any Rom's while your bootloader is locked. You need either fastboot or a custom recovery to flash a custom ROM and both need an unlocked bootloader.

theminikiller said:
Unfortunately, as far as I know you can't flash any Rom's while your bootloader is locked. You need either fastboot or a custom recovery to flash a custom ROM and both need an unlocked bootloader.
Click to expand...
Click to collapse
and flushing the same STOCK rom that i got as OTA should work or does it only work with custom ROM's?

i've looked again.
seems that the bootloader is unlocked!
so, should i flash a TWRP recovery?

ashyossi said:
i've looked again.
seems that the bootloader is unlocked!
so, should i flash a TWRP recovery?
Click to expand...
Click to collapse
Yes, after you've flashed twrp you should be able to access your files from a computer if you're booted in recovery.

soooooo.....
i flashed the TWRP Recovery.
very easy. no errors.
and it shows as the storage is completely empty! as if someone in all this time wiped everything...
so now, what recovery software do you know/used/heard of?

ashyossi said:
soooooo.....
i flashed the TWRP Recovery.
very easy. no errors.
and it shows as the storage is completely empty! as if someone in all this time wiped everything...
so now, what recovery software do you know/used/heard of?
Click to expand...
Click to collapse
When the storage is completely empty, are you booted in recovery, the bootloader or just trying to boot normally? When you say it's empty, do you actually see the device on your computer? If so, is it completely empty with no folders or files or anything, or just stock stuff?

Can you check mount and make sure all the storage volumes are mounted? It's usually blank when they are all manually unmounted.

Unable to install any rom with recovery.

I have a Note 3 N9005.
I installed the latest TWRP recovery.
No matter which rom I try to flash to the system, the same thing happens.
I see that the Aroma installer is strarting and than it just resets for no reason, no install made.
The only sulotion I have found so far is to install a 5.0 stock rom via Odin.
I want to install a custom rom 6.0.1.
Does anyone know what the hell?

Sae problem but a lil worse!!
vashthestampede! said:
I have a Note 3 N9005.
I installed the latest TWRP recovery.
No matter which rom I try to flash to the system, the same thing happens.
I see that the Aroma installer is strarting and than it just resets for no reason, no install made.
The only sulotion I have found so far is to install a 5.0 stock rom via Odin.
I want to install a custom rom 6.0.1.
Does anyone know what the hell?
Click to expand...
Click to collapse
I tried to do the same but ended up bricking my phone. So then I try to unbrick/unroot my phone by flashing the stock rom but I can't do that either cause now it says "Volume Size is too big 4620288<4718599. Need help!!!! ASAP!

Hey guys, I had the same problem at first and it freaked me out too.
Try installing the older 2.8.7.0 version for TWRP through the app, instead of the latest or any other after v3 for that matter. Apparently I've read from other forums that it's due to lack of Aroma Installer Support.
Hope this helps

Confirm the phone's model # by booting into download mode befor flashing TWRP or a stock ROM from sammobile.com.

Will try
I flashed the stock rom packege with odin.
saved my phone after brick.
so you are saying that by downgrading the TWRP recovery i can use aroma insatller based roms again?
cause i also tried to install reserection remix rom (I think this has no aroma in it), i got a massage that said that i cannot install it as well.
refuses to let me change into anything but stock rom.
rooting did not help at all.

vashthestampede! said:
so you are saying that by downgrading the TWRP recovery i can use aroma insatller based roms again?
cause i also tried to install reserection remix rom (I think this has no aroma in it), i got a massage that said that i cannot install it as well.
refuses to let me change into anything but stock rom.
rooting did not help at all.
Click to expand...
Click to collapse
To be honest I don't really know about Cyanogen Mod, however this was just my personal experience with Aroma Installer. I've tried DarkWolf_FW and Aryamod ROMs which are both S7 Edge Port ROMs, and they both use Aroma Installer.
- Also! Take the opportunity to make a Nandroid backup just in case the installation goes bad, then you can restore to where you are right now. Honestly downgrading just worked for me so please don't make me liable if anything goes to pot, at least you will have a full device backup to the exact point in your system which I have found extremely useful when trying different ROMs and Kernels.

tnks
don't worry man
1. I always backup the whole phone before ANY change.
2. your suggestion sound interesting, cause i tried the same rom's you did but no install was made.
3. i'll maybe try a different recovery... maybe CWM.

vashthestampede! said:
don't worry man
1. I always backup the whole phone before ANY change.
2. your suggestion sound interesting, cause i tried the same rom's you did but no install was made.
3. i'll maybe try a different recovery... maybe CWM.
Click to expand...
Click to collapse
Hey, just randomly thinking, did you reset all your System, Data and Cache and Dalvik Cache files before you tried to install the ROMs? Sorry, this might not make a difference, but I don't think I have any more advice to give (I'm kinda new to this too ).
Hope CWM recovery goes well, let me know how it goes

vashthestampede! said:
don't worry man
1. I always backup the whole phone before ANY change.
2. your suggestion sound interesting, cause i tried the same rom's you did but no install was made.
3. i'll maybe try a different recovery... maybe CWM.
Click to expand...
Click to collapse
Doing a complete backup before anything is always the safest bet.
From my experience, TWRP 3+ is fine for CM and AOSP based ROMs.
TWRP 2.8.7-0 is the one you should use to flash ROMs using AROMA Installer.
If you read the OP (opening post) on any ROM forum, it will usually include installation instructions and generally states which TWRP version should be used.
Good Luck.

theawesomecw said:
To be honest I don't really know about Cyanogen Mod, however this was just my personal experience with Aroma Installer. I've tried DarkWolf_FW and Aryamod ROMs which are both S7 Edge Port ROMs, and they both use Aroma Installer.
- Also! Take the opportunity to make a Nandroid backup just in case the installation goes bad, then you can restore to where you are right now. Honestly downgrading just worked for me so please don't make me liable if anything goes to pot, at least you will have a full device backup to the exact point in your system which I have found extremely useful when trying different ROMs and Kernels.
Click to expand...
Click to collapse
Well I'm now stuck in a boot loop. I cannot turn my phone on at all. how do I install a lower version of TWRP on my phone and how do I unbrick it?

kurosaki999 said:
Well I'm now stuck in a boot loop. I cannot turn my phone on at all. how do I install a lower version of TWRP on my phone and how do I unbrick it?
Click to expand...
Click to collapse
You just need download mode to flash it.
Sent from my SM-G925F

kurosaki999 said:
Well I'm now stuck in a boot loop. I cannot turn my phone on at all. how do I install a lower version of TWRP on my phone and how do I unbrick it?
Click to expand...
Click to collapse
I presume when you say it doesn't turn on you mean it doesn't boot into the Android environment. Have you tried unplugging the battery and pressing the Volume Up + Home + Power Button? Yes... I was surprised you don't have to be an octopus too..
Then restore the Nandroid backup from before.
You can also flash TWRP through Odin without root, have a look at the TWRP website for more info.

re
kurosaki999 said:
Well I'm now stuck in a boot loop. I cannot turn my phone on at all. how do I install a lower version of TWRP on my phone and how do I unbrick it?
Click to expand...
Click to collapse
all you need is to flush new stock rom via Odin.
Search the web (like I did) to find a stock rom with 4 .tar files in it.
There should be instructions on how to install but usually all needs to be done is this:
1. load odin 3.*
2. enter the phone in download mode.
3. After you see the line 'add' in odin, load the .tar files to the correct place each (not hard they are tagged by same name)
4. Flush and pray.
5. After a successful install the phone will reboot, this will take a while so don't get streesed.
after about 10-15 min the phone will load again.
Root one more time via odin and try to install again.

vashthestampede! said:
all you need is to flush new stock rom via Odin.
Search the web (like I did) to find a stock rom with 4 .tar files in it.
Click to expand...
Click to collapse
Try Sammobile as they have a large database of firmwares for your phone and the country variants.

Stuck On bootanimation

No matter what custom firmware i flash it always is stuck on the boot animation, Ive left it booting for 5 hours today and it never reached the setup screen, just constant booting, I erase EVERYTHING everytime I go to twrp, except for my internal and external storage. Aswell as If i flash/restore my stock rooted and unrooted firmware, it does boot, but NO wifi or data works, even with the removal and reinsertion of the simcard. Please help. If i didnt explain it well enough i can reply and add more detail.

DeliriousHD said:
No matter what custom firmware i flash it always is stuck on the boot animation, Ive left it booting for 5 hours today and it never reached the setup screen, just constant booting, I erase EVERYTHING everytime I go to twrp, except for my internal and external storage. Aswell as If i flash/restore my stock rooted and unrooted firmware, it does boot, but NO wifi or data works, even with the removal and reinsertion of the simcard. Please help. If i didnt explain it well enough i can reply and add more detail.
Click to expand...
Click to collapse
You may have to follow this https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110 to get back to stock. There's a section about returning to stock without relocking the bootloader.

ccic2491 said:
You may have to follow this https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110 to get back to stock. There's a section about returning to stock without relocking the bootloader.
Click to expand...
Click to collapse
Ill try that. Ill report back if it works or fails.

ccic2491 said:
You may have to follow this https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110 to get back to stock. There's a section about returning to stock without relocking the bootloader.
Click to expand...
Click to collapse
It did not work, Keeps saying "Could not find 'meta-inf/com/google/android/update-binary' in zip file.

DeliriousHD said:
It did not work, Keeps saying "Could not find 'meta-inf/com/google/android/update-binary' in zip file.
Click to expand...
Click to collapse
One thing to try is formatting the internal storage to make sure you have a clean start. TWRP wipes /data without wiping userdata by default; to completely wipe the internal storage you have to go into the format data wipe where you must type "yes" to confirm instead of a slider. Sometimes leftover files can cause permissions problems and roms fail to boot. It is more common on other phones than this one, but I've seen some people report your problem before here too.
If you do this, obviously make sure you back up all the files you care about on internal storage to a microSD or off device. Also make sure you have rom/gapps to flash and a working TWRP backup stored on a microSD, or you've verified you can USB copy with MTP or adb push files from a computer to your phone before formatting. Don't find out after wiping and formatting that your computer is missing something it needs to copy files to your phone properly when your phone is booted into TWRP, test it first if you're going this route. Otherwise you could be stuck with a blank phone and nothing to flash on it.
I do this every once in a while just to keep internal storage from getting too cluttered from chronic flashing; just be careful about how you go about it.

Okay, I can try that.

jason2678 said:
One thing to try is formatting the internal storage to make sure you have a clean start. TWRP wipes /data without wiping userdata by default; to completely wipe the internal storage you have to go into the format data wipe where you must type "yes" to confirm instead of a slider. Sometimes leftover files can cause permissions problems and roms fail to boot. It is more common on other phones than this one, but I've seen some people report your problem before here too.
If you do this, obviously make sure you back up all the files you care about on internal storage to a microSD or off device. Also make sure you have rom/gapps to flash and a working TWRP backup stored on a microSD, or you've verified you can USB copy with MTP or adb push files from a computer to your phone before formatting. Don't find out after wiping and formatting that your computer is missing something it needs to copy files to your phone properly when your phone is booted into TWRP, test it first if you're going this route. Otherwise you could be stuck with a blank phone and nothing to flash on it.
I do this every once in a while just to keep internal storage from getting too cluttered from chronic flashing; just be careful about how you go about it.
Click to expand...
Click to collapse
I did this and its still stuck on boot. Im trying to flash AICP

DeliriousHD said:
I did this and its still stuck on boot. Im trying to flash AICP
Click to expand...
Click to collapse
It was worth a try. What bootloader and twrp version are you using?

jason2678 said:
It was worth a try. What bootloader and twrp version are you using?
Click to expand...
Click to collapse
regular bootloader for the xt1575 I havent chnged it, and twrp 3.0.2-0

DeliriousHD said:
regular bootloader for the xt1575 I havent chnged it, and twrp 3.0.2-0
Click to expand...
Click to collapse
TWRP 3.1 is out. I doubt that's your problem since you're flashing successfully and failing to boot, but updating recovery is something else to check off the list.
Are you on the L or M bootloader? It changed. Just looking for anything that might be causing the trouble.
Code:
getprop ro.bootloader
returns 0xA04C for me, and aicp is working good.

jason2678 said:
TWRP 3.1 is out. I doubt that's your problem since you're flashing successfully and failing to boot, but updating recovery is something else to check off the list.
Are you on the L or M bootloader? It changed. Just looking for anything that might be causing the trouble.
Code:
getprop to.bootloader
returns 0xA04C for me, and aicp is working good.
Click to expand...
Click to collapse
I think im on L but do i just put that in cmd when in bootloader? I also just updated twrp to 3.1 just now.
EDIT: I actually cant even do that in cmd.

DeliriousHD said:
I think im on L but do i just put that in cmd when in bootloader? I also just updated twrp to 3.1 just now.
Click to expand...
Click to collapse
Fastboot says what bootloader version you're on close to the little reclining robot, but I think it displays it a bit differently. A0.4C trailed by a date if I recall correctly.
You could enter that command in TWRP's built-in terminal. I think the terminal is under the Advanced menu. That should get you the same output.

jason2678 said:
Fastboot says what bootloader version you're on close to the little reclining robot, but I think it displays it a bit differently. A0.4C trailed by a date if I recall correctly.
You could enter that command in TWRP's built-in terminal. I think the terminal is under the Advanced menu. That should get you the same output.
Click to expand...
Click to collapse
I just tried putting that into terminal and it does nothing.

jason2678 said:
Fastboot says what bootloader version you're on close to the little reclining robot, but I think it displays it a bit differently. A0.4C trailed by a date if I recall correctly.
You could enter that command in TWRP's built-in terminal. I think the terminal is under the Advanced menu. That should get you the same output.
Click to expand...
Click to collapse
also BL: A0.1C (SHA-E29F91E, 2015-7-28 16;16;36)

DeliriousHD said:
I just tried putting that into terminal and it does nothing.
Click to expand...
Click to collapse
Well that's odd

jason2678 said:
Well that's odd
Click to expand...
Click to collapse
In your code you put to not ro XD

jason2678 said:
Well that's odd
Click to expand...
Click to collapse
Mine is 0xa01C

DeliriousHD said:
also BL: A0.1C (SHA-E29F91E, 2015-7-28 16;16;36)
Click to expand...
Click to collapse
2015-7-28 date is definitely from lollipop. I'd suggest heading over to the firmware thread and grabbing the newest marshmallow full firmware update (I think the sept patch is the newest out there), fastboot flash all of that, then try again.

jason2678 said:
2015-7-28 date is definitely from lollipop. I'd suggest heading over to the firmware thread and grabbing the newest marshmallow full firmware update (I think the sept patch is the newest out there), fastboot flash all of that, then try again.
Click to expand...
Click to collapse
Which thread? I can go looking but ive been to so many its confusing how to use the files.

jason2678 said:
2015-7-28 date is definitely from lollipop. I'd suggest heading over to the firmware thread and grabbing the newest marshmallow full firmware update (I think the sept patch is the newest out there), fastboot flash all of that, then try again.
Click to expand...
Click to collapse
This thread https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833 Shows a couple firmwares. but idk if i should get MPH24.49-18 , MPH24.49-18-3 or MPH24.49-18-4