Develop Bugs

ZTE Blade Apex 2 | Unable to Install Firmware

Hello guys,
I have a problem with my phone. I cannot install the correct firmware, I can only install the firmware (Orange Hi 4G) but it's not compatible with my phone, so the phone bootloops and doesn't go into the system.
I cannot install the firmware for my device because it's not signed with the orange's certificate and key, my phone has the orange's recovery and fastboot is disabled on the rom so I cannot use that. I have the certificate and key but I cannot get the key in a .pem file, the certificate is already in one.
Phone: ZTE Blade Apex 2
Recovery in Phone: Orange recovery
Recovery: Stock recovery
Certificate:
MIIErjCCA5agAwIBAgIJAOuCYND5gmZOMA0GCSqGSIb3DQEBBQUAMIGWMQswCQYD
VQQGEwJDTjERMA8GA1UECBMIU2hhbmdoYWkxETAPBgNVBAcTCFNoYW5naGFpMQww
CgYDVQQKEwNaVEUxIjAgBgNVBAsTGVNtYXJ0cGhvbmUgU29mdHdhcmUgRGVwdC4x
DDAKBgNVBAMTA1pURTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEB6dGUuY29tLmNu
MB4XDTExMDMwODA3MTM0M1oXDTM4MDcyNDA3MTM0M1owgZYxCzAJBgNVBAYTAkNO
MREwDwYDVQQIEwhTaGFuZ2hhaTERMA8GA1UEBxMIU2hhbmdoYWkxDDAKBgNVBAoT
A1pURTEiMCAGA1UECxMZU21hcnRwaG9uZSBTb2Z0d2FyZSBEZXB0LjEMMAoGA1UE
AxMDWlRFMSEwHwYJKoZIhvcNAQkBFhJzdXBwb3J0QHp0ZS5jb20uY24wggEgMA0G
CSqGSIb3DQEBAQUAA4IBDQAwggEIAoIBAQC6XMcxr5zlAnZfYCeKPgt+w4y/fmB7
SzZSJvCx4hFKKq6m9CHg60vhlVQ4gLkuKb1l+pFbJdrP8yL1YKQqSrWWDAhPcuIl
Lj3UcmzfbMRQhM4mrXf49ees2xyVZO38KjtSSBw/ygvH5PSrX6KFUqQdxVeciLga
tYYoOEpRGKZdeL+HAI0EMFssOow00jPP44IB9Vi9UiEHOqvTHVmDIdQWOmAgWXlA
36sdWsSebLzWXjm2vB6OJaPV93zxy+tym33mkduc2DHQiH6TFUr4YmtDOZJ7y3jZ
2VzJU3VViYNunm/Da0NAPYwtbyeOgr+5npV7CfzY436lqLYaAlHJjx37AgEDo4H+
MIH7MB0GA1UdDgQWBBS6NVREsJ5wGdTi/26mEwf8h2KDfzCBywYDVR0jBIHDMIHA
gBS6NVREsJ5wGdTi/26mEwf8h2KDf6GBnKSBmTCBljELMAkGA1UEBhMCQ04xETAP
BgNVBAgTCFNoYW5naGFpMREwDwYDVQQHEwhTaGFuZ2hhaTEMMAoGA1UEChMDWlRF
MSIwIAYDVQQLExlTbWFydHBob25lIFNvZnR3YXJlIERlcHQuMQwwCgYDVQQDEwNa
VEUxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAenRlLmNvbS5jboIJAOuCYND5gmZO
MAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQEFBQADggEBAKSJA12gqyhorPk0EkHN
gUTLJoytol5SHPksdhbMjTOTEsaPiOVQZ0sHk9JDPoXRJlZvLXIvZCtzG+YCjpF8
Gv/uK47jHJsBG5L9LyI/LNctPOTefj3aBQklLxUgeblaaK2AFGb+ygmX8plGSwOz
9p4mgr8UQtPsdXP6gxEejI3oZ8Bz4HmttL+GwabCZAxuF9O2Z4vX1oCYbAVLAKz+
SUoMVXY9hzSa/Ttx+HeH0oHPXdZ0A2VyxpLiFIXdbdC9zWjB8AGQgmYINDHlQRG4
hPH9+NppDljxd19T1cEzkFERFEI8dWkTCaE8mRNQfShSt7N3vW+kfELq8rlkvDMW
9JM=
Key:
AAAAAQAAABSR52UCnjiSFiwLKyzthZxY4sJ0ZQAABdEBAAh2ZXJpc2lnbgAAASw2
S2EsAAAAAAAFWC41MDkAAAMGMIIDAjCCAmsCEH3Z/gfPqB63EHln+6eJNMYwDQYJ
KoZIhvcNAQEFBQAwgcExCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwg
SW5jLjE8MDoGA1UECxMzQ2xhc3MgMyBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0
aW9uIEF1dGhvcml0eSAtIEcyMTowOAYDVQQLEzEoYykgMTk5OCBWZXJpU2lnbiwg
SW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MR8wHQYDVQQLExZWZXJpU2ln
biBUcnVzdCBOZXR3b3JrMB4XDTk4MDUxODAwMDAwMFoXDTI4MDgwMTIzNTk1OVow
gcExCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE8MDoGA1UE
CxMzQ2xhc3MgMyBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0
eSAtIEcyMTowOAYDVQQLEzEoYykgMTk5OCBWZXJpU2lnbiwgSW5jLiAtIEZvciBh
dXRob3JpemVkIHVzZSBvbmx5MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDMXtERXVxp0KvTuWpMmR9Z
mDCOFoUgRm1HP9SFIIThbbP4pO0M8RcPO/mn+SXXwc+EY/J8Y8+iR/LGWzOOZEAE
aMGAuWQcRXfH2G71lSk8UOg013gfqLptQ5GVj0VXXn7F+8qkBOvqlzdUMG+7AUcy
M83cV5tkaWH4mx0ciU9cZwIDAQABMA0GCSqGSIb3DQEBBQUAA4GBAFFNzb5cy5gZ
nBWyATl4Lk0PZ3BwmcYQWpSkU01UbSuvDV1Ai2TT1+7eVmGSX6bEHRBhNtMsJzzo
KQm5EWR0zLVznxxIqbxhAe7iF6YM40AIOw7n60RzKprxaZLvcRTDOaxxp5EJb+Rx
BrO6WVcmeQD2+A2iMzAo1KpYoJ2daZH9AQAKb3JhbmdlX3R0ZwAAASw2S6sfAAAA
AAAFWC41MDkAAAOaMIIDljCCAv+gAwIBAgIJAOzGENAox4zdMA0GCSqGSIb3DQEB
BQUAMIGPMQswCQYDVQQGEwJGUjEWMBQGA1UECBMNSWxlIGRlIEZyYW5jZTEOMAwG
A1UEBxMFUGFyaXMxFzAVBgNVBAoTDkZyYW5jZSBUZWxlY29tMSgwJgYDVQQLEx9G
VC1PRi1EVEYtREVYLURFQ0ktRUVEQVRBLU9TQ1BTMRUwEwYDVQQDEwxPcmFuZ2VU
VEctQ0EwHhcNMTAxMTEwMTAzNDQ5WhcNMzAxMTA1MTAzNDQ5WjCBjzELMAkGA1UE
BhMCRlIxFjAUBgNVBAgTDUlsZSBkZSBGcmFuY2UxDjAMBgNVBAcTBVBhcmlzMRcw
FQYDVQQKEw5GcmFuY2UgVGVsZWNvbTEoMCYGA1UECxMfRlQtT0YtRFRGLURFWC1E
RUNJLUVFREFUQS1PU0NQUzEVMBMGA1UEAxMMT3JhbmdlVFRHLUNBMIGfMA0GCSqG
SIb3DQEBAQUAA4GNADCBiQKBgQC+MWWiupCgPdKl2jH2dl2HZ5VzzZPc+T/teetD
qdme17tDAbzEEKc6bf/WB3bUY4qgS2sbB8Gz/jMekfmJ3tLpW93WOwpnmaGAY0+Z
dZylacejycAdOeiPS8bq9zUlfYGPi0MvaPcAoSO75hkV/14xLLKjGY7aCNMC4Ws1
+0PqSQIDAQABo4H3MIH0MB0GA1UdDgQWBBTbMtaQXxFEPq1PYFCzwRirTy6+qzCB
xAYDVR0jBIG8MIG5gBTbMtaQXxFEPq1PYFCzwRirTy6+q6GBlaSBkjCBjzELMAkG
A1UEBhMCRlIxFjAUBgNVBAgTDUlsZSBkZSBGcmFuY2UxDjAMBgNVBAcTBVBhcmlz
MRcwFQYDVQQKEw5GcmFuY2UgVGVsZWNvbTEoMCYGA1UECxMfRlQtT0YtRFRGLURF
WC1ERUNJLUVFREFUQS1PU0NQUzEVMBMGA1UEAxMMT3JhbmdlVFRHLUNBggkA7MYQ
0CjHjN0wDAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQUFAAOBgQBuShubIhCowVw5
e/Zx4O/2es78YXMJBXVQ/7bhM4sGZ6HAsahIXg0l6aP8xROGsfofetz+9WjRMyeU
MzsovcdNnNR/ge0nr5BQb7Ef/4N6DNbd6t0u1InNSRIXemwPI/77ggVf8XgW24Jg
fSb5CwqSq4adfev5K4IUBeQeQmnNMQEAD3ZlcmlzaWduX3NlcnZlcgAAASxVM/4G
AAAAAAAFWC41MDkAAAYwMIIGLDCCBZWgAwIBAgIQbk/6s8XmacTRZ8mSq+hYxDAN
BgkqhkiG9w0BAQUFADCBwTELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMTwwOgYDVQQLEzNDbGFzcyAzIFB1YmxpYyBQcmltYXJ5IENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IC0gRzIxOjA4BgNVBAsTMShjKSAxOTk4IFZlcmlTaWdu
LCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmswHhcNMDkwMzI1MDAwMDAwWhcNMTkwMzI0MjM1OTU5
WjCBtTELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEvMC0GA1UE
AxMmVmVyaVNpZ24gQ2xhc3MgMyBTZWN1cmUgU2VydmVyIENBIC0gRzIwggEiMA0G
CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDUVo9XOzcopkBj0pXVBXTatRlqltZx
Vy/iwDSMoJWzjOE3JPMu7UNFBY6J1/raSrX4Po1Ox/lJUEU3QJ90qqBRVWHxYISJ
pZ6AjS+wIapFgsTPtBR/RxUgKIKwaBLArlwH1/ZZzMtiVlxNSf8miKtUUTovStoO
mOKJcrn892g8xB85essXgfMMrQ/cYWIbEAsEHikYcV5iy0PevjG6cQIZTiapUdqM
ZGkD3pz9ff17Ybz8hHyIXLTDe+1fK0YS8f0AAZqLW+mjBS6PLlve8xt4+GaRCMBe
ztWwNsrUqHugffkwer/43RlRKyC6/qfPoU6wZ/WAqiuDLtKOVImOHikLAgMBAAGj
ggKpMIICpTA0BggrBgEFBQcBAQQoMCYwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3Nw
LnZlcmlzaWduLmNvbTASBgNVHRMBAf8ECDAGAQH/AgEAMHAGA1UdIARpMGcwZQYL
YIZIAYb4RQEHFwMwVjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cudmVyaXNpZ24u
Y29tL2NwczAqBggrBgEFBQcCAjAeGhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhMDQGA1UdHwQtMCswKaAnoCWGI2h0dHA6Ly9jcmwudmVyaXNpZ24uY29tL3Bj
YTMtZzIuY3JsMA4GA1UdDwEB/wQEAwIBBjBtBggrBgEFBQcBDARhMF+hXaBbMFkw
VzBVFglpbWFnZS9naWYwITAfMAcGBSsOAwIaBBSP5dMahqyNjmvDz4Bq1EgYLHsZ
LjAlFiNodHRwOi8vbG9nby52ZXJpc2lnbi5jb20vdnNsb2dvLmdpZjApBgNVHREE
IjAgpB4wHDEaMBgGA1UEAxMRQ2xhc3MzQ0EyMDQ4LTEtNTIwHQYDVR0OBBYEFKXv
CxHOwEEDo0plkEiyHOBXLX1HMIHnBgNVHSMEgd8wgdyhgcekgcQwgcExCzAJBgNV
BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE8MDoGA1UECxMzQ2xhc3Mg
MyBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEcyMTow
OAYDVQQLEzEoYykgMTk5OCBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVk
IHVzZSBvbmx5MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrghB92f4H
z6getxB5Z/uniTTGMA0GCSqGSIb3DQEBBQUAA4GBAGN0Lz1Tqi+X7CYRZhr+8d5B
JxnSf9jBHPniOFY6H5CuOcUgdav4bC1nHynCIdcUiGNLsJsnY5H48KMBJLb7j+M9
AgtvVP7UzNvWhb98lR5eYhHB2QmcQrmy1KotmDojYMyimvFu6M+O0Ro8XhnF15s1
sAIjJOUFuNWI4+D6ufRfAF0Slrj4O266ePon5MC54zEX3hju
I don't know what to do anymore. I tried to get the certificate and key.pk8 to sign the other firmware but no luck. If anyone could help me I would appreciate it. Thank you in advance!

You gotta be kidding me!!! No one helps around here?

Helppppppppppppppppppppppppp!

Helpppppppppppppppppppppppppppppppppppp!!!!!!!!!!!!!!!!!!!!!!!!!!!

Helllllllllllllllllllllllllllllppppppppppppppppppppppp

HEeeeeeeeeeeeeeeeeeeeeeeeeeeelllllllllllllllllllppppppppppppppppppppppppppppppppp :crying:

I'm not familiar with this phone, but I'm sure that a ROM can't disable fastboot. Try to install the previous firmware, if it exists (if it does not, then try a custom firmware.)
Hope this helps,
Drew
Sent from my Nexus 4 using XDA Free mobile app

@drew1ind - Thanks for replying.
The issue is that it doesn't let me enter fastboot mode. I flashed the recovery witch is found in the rom and the phone got stuck in bootloop. And it doesn't let me install any other firmwares but the orange rom or pretty much do anything.

SickAttack said:
@drew1ind - Thanks for replying.
The issue is that it doesn't let me enter fastboot mode. I flashed the recovery which is found in the rom and the phone got stuck in bootloop. And it doesn't let me install any other firmwares but the orange rom.
Click to expand...
Click to collapse
How different is your phone compared to the one which can use the ROM you're trying to install? Only ever install a ROM if it's for your specific phone. An example would be for Samsung phones; some carriers make different versions for some Samsung phones, which require different ROMS. If you installed the bootloader from that phone's ROM, then you probably hard bricked your phone, meaning it's gone for good. How did you flash the recovery if you couldn't access fastboot? Also, why can you only install the orange rom? I would recommend staying with the orange ROM if it's the only one that works. You might not be able to access the fastboot/recovery because you're using the wrong key combination. If nothing else works, I would recommend a nexus phone as they're easily moddable, and almost impossible to brick.
Best of luck,
Drew

drew1ind said:
How different is your phone compared to the one which can use the ROM you're trying to install? Only ever install a ROM if it's for your specific phone. An example would be for Samsung phones; some carriers make different versions for some Samsung phones, which require different ROMS. If you installed the bootloader from that phone's ROM, then you probably hard bricked your phone, meaning it's gone for good. How did you flash the recovery if you couldn't access fastboot? Also, why can you only install the orange rom? I would recommend staying with the orange ROM if it's the only one that works. You might not be able to access the fastboot/recovery because you're using the wrong key combination. If nothing else works, I would recommend a nexus phone as they're easily moddable, and almost impossible to brick.
Best of luck,
Drew
Click to expand...
Click to collapse
The rom is from the same phone, but it's from a different carrier. I think the reason that it just restarts over and over is because my phone only has 4GB and that one has 8GB and the partitions are messed up or not compatible with my phone's storage.
I had access to fastboot mode the first time I flashed it, but I can't access it now or I don't know how to.

SickAttack said:
The rom is from the same phone, but it's from a different carrier. I think the reason that it just restarts over and over is because my phone only has 4GB and that one has 8GB and the partitions is messed up or not compatible with my phone's storage.
I had access to fastboot mode the first time I flashed it, but I can't access it now.
Click to expand...
Click to collapse
It has to be with the same carrier. As for fastboot, either something happened to your volume rockers/power button, or it somehow changed it the combination. Also, is 4GB available for the other phone's carrier? If not, that *may* be the problem. One thing it might have done is flash a different broadband from what your carrier gives you (a broadband is basically a .img file that is also called a radio which dictates how your cellular functions handle). Some phones are known to brick from bad radio files (I think, atleast).

drew1ind said:
It has to be with the same carrier. As for fastboot, either something happened to your volume rockers/power button, or it somehow changed it the combination. Also, is 4GB available for the other phone's carrier? If not, that *may* be the problem. One thing it might have done is flash a different broadband from what your carrier gives you (a broadband is basically a .img file that is also called a radio which dictates how your cellular functions handle). Some phones are known to brick from bad radio files (I think, atleast).
Click to expand...
Click to collapse
The buttons still work, if I press all of the buttons it will bring me to download mode, I assume. It's a black screen with the led always on, but I don't know what I can do there.
What I need to do is either edit the current rom of orange and sign it with the certificate and key, but I need to put the key in a .pem file (the key and certificate is on the main post) but I cannot do it. Or I could flash the recovery of the other rom that works on my phone which is for 4gb phones, but I need to flash the recovery for that rom but I can't seam to do it.

SickAttack said:
The buttons still work, if I press all of the buttons it will bring me to download mode, I assume. It's a black screen with the led always on, but I don't know what I can do there.
What I need to do is either edit the current rom of orange and sign it with the certificate and key, but I need to put the key in a .pem file (the key and certificate is on the main post) but I cannot do it. Or I could flash the recovery of the other rom that works on my phone which is for 4gb phones, but I need to flash the recovery for that rom but I can't seam to do it.
Click to expand...
Click to collapse
I can't help you with that, as I don't have your phone. Also, it doesn't have a sub-forum on the main page, meaning that this phone isn't very popular. Sadly, all I can say for you is to get a new phone. What to learn from this:
Only flash files that are for your specific phone, and possibly carrier
Look through multiple guides, and double-check everything.
Best of luck,
Drew

drew1ind said:
I can't help you with that, as I don't have your phone. Also, it doesn't have a sub-forum on the main page, meaning that this phone isn't very popular. Sadly, all I can say for you is to get a new phone. What to learn from this:
Only flash files that are for your specific phone, and possibly carrier
Look through multiple guides, and double-check everything.
Best of luck,
Drew
Click to expand...
Click to collapse
I just bought this phone, how could I buy a new one?

SickAttack said:
I just bought this phone, how could I buy a new one?
Click to expand...
Click to collapse
Save money, I guess? I would recommend that you get a phone that much more people use.

help!!!!!
Please send a dump of the firmware, for 2 months can't repair hard brick(((( zte blade apex 2

help!!!!!help!!
Please send a dump of the firmware, for 2 months can't repair hard brick(((( zte blade apex 2

Try with voldown +power as you see the logo
Conmect your phone to PC and run "adb devices" if it detects then type "adb reboot bootloader"
When u run adb devices it may show the device I'd like "?" This (in my case it showed like this)
I think it may help
U can try digitel rom for u r device it may work
http://playdroidv.blogspot.in/2015/07/rom-stock-digitel-zte-blade-apex-2.html?m=1

send me the rom of this phone (zte blade apex 2 ) and i show you how to flash

s3 ?bricked? STUCK/LOOP ON DOWNLOAD MODE ONLY

i have my friends phone and he's galaxy s3 is stuck on download mode and its looping there everytime
it happened out of nowhere, he wasn't playing around with it it just happened
now its stuck on downloading and wont go to recovery for me to initialize the device through kies or smartswitch
NO ACCESS TO RECOVERY MODE AT ALLL
i tried numerous ways to retrieve the phone into working condition but no success at all
thru odin i get the pit error and when i place a pit to repartititon with the stock tar file or the cwm recovery tar i failed
it says complete write operation failed and it takes a long time to set up connection with the device before showing me the fail
its a tmobile sgh-t999 prob 16 gb
any genius here got any ideas?

What firmware build was on the device and what build did you try to flash using Odin?
Did you try different versions of odin?
Different driver versions?
Different USB cable?
Different USB port?
If kies is installed on the computer, get rid of it. It interferes with Odin.
If none of that helps it may be a hardware failure.
Sent from my SGH-T999 using Tapatalk

The same thing has happened to my wife's phone and I have done almost the same steps to fix it with similar results.

If you tried everything I mentioned and are sure you weren't flashing an older firmware build (only after 4.3), then theres a good chance it's a hardware failure, probably with the memory.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
If you tried everything I mentioned and are sure you weren't flashing an older firmware build (only after 4.3), then theres a good chance it's a hardware failure, probably with the memory.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
OK, uninstalled Kies and tried to flash T999UVUEOH1_T999TMBEOH1_TMB rom with odin again and got there is no pit partition error. Would post some pictures of the boot screen and a screenshot of the odin program but need 10 posts. Well not sure what version was on phone before all this happened.) Also the ODIN bootloader screen says SYSTEM STATUS: NONE Warrenty Bit: 0 BOOTLOADER AP S?AEV: 1 among other things...forgot to mention I used ODIN v3.10.6 because v3.10.7 gave me a win32 error when I tried to run it on my Windows XP PC.

Here's my suggestion to at least get the phone running a ROM:
download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=...5QWImOPDJboTA_V3D5S9eA&bvm=bv.107763241,d.dmo
download the tar version of TWRP 2.8.6.0 from here: https://dl.twrp.me/d2tmo/
download the latest cm12.1 for the phone from here and save it to a micro SD card: https://download.cyanogenmod.org/?device=d2tmo&type=nightly
place the micro SD card into the phone;
boot the phone into download mode;
open Odin 3.07 and uncheck everything except f. reset time;
click on PDA and browse to the tar TWRP file and select it;
connect the phone and it should show up as a com port in Odin;
flash TWRP;
when you see the word RESET in the status window, remove the USB cable, remove the battery, replace the battery, use the button combination to get into recovery which should now be TWRP;
perform a full wipe of system, data, and cache;
flash CM12.1 from the micro SD card;
reboot the phone.
Hopefully, the above steps will get the phone booted so you can confirm the installed bootloader and modem.

Followed your guide step by step but flash failed in odin Get Pit for mapping..
There is no PIT partition.
All threads completed. (succeed 0 / failed 1):crying: BTW thank for all your help.

You got the pit error flashing twrp in Odin? Any other errors? What model number is shown at the top of the screen when the phone is in download mode?

The only times I've encountered this type of behavior it turned out to be a hardware failure (memory). If that is indeed the case here, I'm afraid there won't be much you can do for it. Don't get me wrong, I'm not saying you should just give up, but you should probably at least start looking at other options.
The main reasons I believe this to be the case are
1. It just died while nothing was being done (not being used)
2. Pit errors indicate either the partition table has been corrupted, or the partitions themselves have. Because it cannot detect any system (SYSTEM STATUS: NONE), it's more likely to be the partitions them selves, not the partition information table (pit).
Something else that doesn't look good, (but that I've never seen before) is the S?AEV. It should be SWREV. (Software Revision). It may mean nothing, but I've never seen it before so I thought I'd point it out.
As I said, I'm not saying you should give up yet. I've been wrong before and I'd hope to be again in this case. But I wouldn't put too much more time and effort into it as I've never seen one of these types of failures restored. They are pretty rare, but they do happen.
My best suggestion at this point is to start looking into replacing either the motherboard or the device. Motherboards can be found for reasonable prices, but you do have to be careful when buying one. (Let us know if you want to do this and we'll give you some tips on what to look for).
I'm sorry that this happened and that there doesn't seem to be much I can do to help. If you had any important data (pics or whatever), there's a small chance it can still be recovered. Don't get your hopes up too much for it, but using ADB while in download mode MIGHT allow you to copy your stuff to the computer. I can't remember if this can be done from download mode though, and if the data partition is also hosed you'd be out of luck there anyway.
If i think of anything else you can try, I'll certainly let you know. Audit13 might have a few ideas you can try too. As I said though, you should also start looking into other options. Let us know what you want to do and we'll continue to help as best as we can!
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
The only times I've encountered this type of behavior it turned out to be a hardware failure (memory). If that is indeed the case here, I'm afraid there won't be much you can do for it. Don't get me wrong, I'm not saying you should just give up, but you should probably at least start looking at other options.
The main reasons I believe this to be the case are
1. It just died while nothing was being done (not being used)
2. Pit errors indicate either the partition table has been corrupted, or the partitions themselves have. Because it cannot detect any system (SYSTEM STATUS: NONE), it's more likely to be the partitions them selves, not the partition information table (pit).
Something else that doesn't look good, (but that I've never seen before) is the S?AEV. It should be SWREV. (Software Revision). It may mean nothing, but I've never seen it before so I thought I'd point it out.
As I said, I'm not saying you should give up yet. I've been wrong before and I'd hope to be again in this case. But I wouldn't put too much more time and effort into it as I've never seen one of these types of failures restored. They are pretty rare, but they do happen.
My best suggestion at this point is to start looking into replacing either the motherboard or the device. Motherboards can be found for reasonable prices, but you do have to be careful when buying one. (Let us know if you want to do this and we'll give you some tips on what to look for).
I'm sorry that this happened and that there doesn't seem to be much I can do to help. If you had any important data (pics or whatever), there's a small chance it can still be recovered. Don't get your hopes up too much for it, but using ADB while in download mode MIGHT allow you to copy your stuff to the computer. I can't remember if this can be done from download mode though, and if the data partition is also hosed you'd be out of luck there anyway.
If i think of anything else you can try, I'll certainly let you know. Audit13 might have a few ideas you can try too. As I said though, you should also start looking into other options. Let us know what you want to do and we'll continue to help as best as we can!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Wow, thanks Doc for replying. I was hopeful for a better result. BTW it does say SWREV I just couldn't quite make out the W at the time so I put ? to indicate that. I do have a little experience working on these phones (replaced the entire LCD/screen and USB port on my Note2) The model of the phone is listed as SGH-T999 in ODIN mode and it is a T-mobile phone. How much is motherboard and what should I look for as far as part number?

Found this with a quick ebay search: http://m.ebay.com/itm/Samsung-Galax...Board-Motherboard-s3-/221940485670?nav=SEARCH
I searched for "galaxy s3 T999 motherboard". That one is 68.50 obo.
It's been a while since I've looked, and it looks like there's a lot fewer of them available now. (Used to get tons of results).
You can also look for an I747 (AT&T) board. The I747 and T999 are fully compatible. No other models will fit into the case. (The T999V and I747M would probably also work. I'm not sure about the T999L or T999N models though. I'm guessing they would, but really have no idea for sure.)
Some terms to search for would be: Galaxy S3 T999 motherboard, I747 motherboard, mainboard, etc.
Also search for the same models with broken screens. Many times people sell these cheap and everything inside works perfectly. Might be cheaper too.
Watch out for certain words and phrases in the listing though. Some sellers will try a little wordplay to make it sound better than it is. If i find an example, I'll post it. Stuff like cracked screen won't power on can be changed to sound like it's only the screen won't come on, when it's really the whole device. Either ask for clarification, or move on.
I like the ones that are very specific, like cracked screen, but does appear to boot up and gives boot sounds.
Ask the seller for the imei number and check it yourself on swappa. I'd also call t-mobile and verify with them.
I hope that helps. Feel free to ask if you're wondering about a specific listing or anything else.
Oh and if buying from an eBay store, make sure they've got very good ratings. Individual people often won't have many ratings, but can sometimes be more trustworthy and more willing to give specifics. Sometimes....
You can also check places like Swappa and Craigslist.
Sent from my SGH-T999 using Tapatalk

The simplest way to get a replacement motherboard would be to look in the used market for a t999 that has smashed or defective screen with working internals.
If it is not too expensive, a jtag repair centre may be able to force flash a rom.

eMMC image for VS986 Needed for Hard Bricked Device

I hard bricked my phone downgrading from 13b to 11a.
I can send it to LG for a repair per their customer support. I might try doing that.
Would anyone be willing to upload their eMMC image?
If you are that lucky person, who is stuck in the NEW “Qualcomm HS-USB QDLoader 9008” mode, to be honest, the steps to be taken are a lot easier. However, you need somebody having the same phone as yours to upload your device’s complete eMMC image for you. To get such image, you could ask your friend to do these steps (root the phone first):
Format your external MicroSD card with “exfat” system file, and the size of this SD card should be morethan 16 GB , which is the size of the whole partition.
Do a full factory reset, meaning wipe your cache, data, and internal storage using either CWM, TWRP, or PhillzTouch.
Insert the SD card to your phone and connect your mobile with ADB, type:
adb shell
su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/backup.img bs=512 count=30535646
The size of the “backup.img” is around 16 GB, However, if you compressed it, it would be around 2 GB.
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Click to expand...
Click to collapse

I've been looking for this for months now. Unfortunately, not a lot of people wanted to help.

There are lots of people willing to help. The problem is that VS986 has not been rooted, and as stated in the post quoted above, root is required to dump the eMMC.
sushi-gee, I am having the same issue and was also told by LG support that I could send it in. Did you end up sending yours in to LG? If so, did they fix it?
I also live in Las Vegas (looking at you, greedness)!

biorpg said:
There are lots of people willing to help. The problem is that VS986 has not been rooted, and as stated in the post quoted above, root is required to dump the eMMC.
sushi-gee, I am having the same issue and was also told by LG support that I could send it in. Did you end up sending yours in to LG? If so, did they fix it?
I also live in Las Vegas (looking at you, greedness)!
Click to expand...
Click to collapse
LG took care of me

biorpg said:
There are lots of people willing to help. The problem is that VS986 has not been rooted, and as stated in the post quoted above, root is required to dump the eMMC.
Click to expand...
Click to collapse
What do you mean VS986 hasn't been rooted?
The Verizon LG G4 (vs98611a and 13b) have been rooted for some time now. And if you're on marshmallow you can downgrade to LP and still root.

sushi-gee said:
LG took care of me
Click to expand...
Click to collapse
Thanks for replying! I'll send mine in once I remember how to stick things to folding paper-pockets and sharpie up boxes for snail-mail.
Spookymyo said:
The Verizon LG G4 (vs98611a and 13b) have been rooted for some time now. And if you're on marshmallow you can downgrade to LP and still root.
Click to expand...
Click to collapse
It is not a full root though, is it enough to allow dumping the eMMC? If so, I will reroot mine to 13b and dump the eMMC for others(and probably myself) to use for recovering the phone from this state so that we can have more attempts to fully brick the thing!

It is a full root. But unlocking the bootloader and therefore installing a custom recovery is not available. There are methods for grabbing your own complete system image.

any luck

majinawaz said:
any luck
Click to expand...
Click to collapse
​I'm still using my G4 to keep my fan from blowing my papers off my desk. The warranty had expired, and I did not have insurance through Verizon, so I may ship it to LG and hope for them to fix it for cheap or free, but it's not on my priority list(as if I keep such a list?!).
​I bought a OnePlus 3T, which is a relieving experience after the G4's constant bull****. I've already flashed TWRP, and then flashed cyanogen, got that working, tried to flash nethunter on top of it all, got stuck in a fastboot bootloop, wiped, reformatted, re-flashed TWRP and cyanogen, and its all working again. That all goes very quickly when the phone is not throwing up road blocks at every step and forcing you to conduct potentially fruitless searches for cryptic error messages or stabbing you in the back with a qualcomm security 'feature' that never gets mentioned until you've triggered it.
​The only drawback with the OnePlus 3T on Verizon is so far it is only capable of making/receiving calls or texts while connected to 3G. If I dial *#*#4636#*#* and choose 'LTE only' it will connect to Verizon 4G, but is then unable to call or text. That was all on the stock ROM, im gonna play around with third party stuffs to see if I can get both to work together.
I am also open to the option of opening up the G4 and retrieving the eMMC via JTAG if someone wants to point me to a guide(I found one a while ago, so it's out there somewhere)

biorpg said:
​I'm still using my G4 to keep my fan from blowing my papers off my desk. The warranty had expired, and I did not have insurance through Verizon, so I may ship it to LG and hope for them to fix it for cheap or free, but it's not on my priority list(as if I keep such a list?!).
​I bought a OnePlus 3T, which is a relieving experience after the G4's constant bull****. I've already flashed TWRP, and then flashed cyanogen, got that working, tried to flash nethunter on top of it all, got stuck in a fastboot bootloop, wiped, reformatted, re-flashed TWRP and cyanogen, and its all working again. That all goes very quickly when the phone is not throwing up road blocks at every step and forcing you to conduct potentially fruitless searches for cryptic error messages or stabbing you in the back with a qualcomm security 'feature' that never gets mentioned until you've triggered it.
​The only drawback with the OnePlus 3T on Verizon is so far it is only capable of making/receiving calls or texts while connected to 3G. If I dial *#*#4636#*#* and choose 'LTE only' it will connect to Verizon 4G, but is then unable to call or text. That was all on the stock ROM, im gonna play around with third party stuffs to see if I can get both to work together.
I am also open to the option of opening up the G4 and retrieving the eMMC via JTAG if someone wants to point me to a guide(I found one a while ago, so it's out there somewhere)
Click to expand...
Click to collapse
Every thing needed for the VS986 "9008" HARD BRICK can be found here on XDA. No Boxes, NO Dongles, No SD cards, No exotic or elusive files. Check this "LG G4 VS986 Super-Hard-Brick-Unbrick / On Any FW version / QComm_9008 Fatality Move"

vs986_27C_QFILRecoveryImage
https://drive.google.com/file/d/0B41ACD_ESYnHbkVzbDloY00tNVk/view?usp=sharing Extract folder / Move folder into QFIL folder as a folder not as individual files / load the firehoseprogrammer, patch, & raw / Flash / Remove battery / insert battery / hold volume up and plug in at same time until "download mode" appears on device / wait for drivers to install ? flash vs98627C.kdz with LGUP.
---------- Post added at 01:40 AM ---------- Previous post was at 01:34 AM ----------
gratefuldeaddougie said:
https://drive.google.com/file/d/0B41ACD_ESYnHbkVzbDloY00tNVk/view?usp=sharing Extract folder / Move folder into QFIL folder as a folder not as individual files / load the firehoseprogrammer, patch, & raw / Flash / Remove battery / insert battery / hold volume up and plug in at same time until "download mode" appears on device / wait for drivers to install ? flash vs98627C.kdz with LGUP.
Click to expand...
Click to collapse
This will only work if the device bricked on 27C or earlier. If you know what FW version you bricked on the extract that FW and replace the appropriate files in the recovery image folder.

Pixel 2 Bricked??! (Solved!)

I started updating the phone to the Jan 2019 update from the Dec 2018 update (I just like having the latest updates) It rebooted into bootloader via ADB just fine. I then ran the flash all.bat without the -w so it wouldnt wipe the phone out completely. It started updating and rebooting just like normal after the bootloader and radio parts. It made it close to the end of the system update and did not reboot the phone. It went back to the bootloader which I thought was odd. Fastboot can no longer see the phone in Fastboot devices. When starting the phone it reboots back into bootloader saying load failed. It also will not boot into recovery (which I expected from the update and not getting to flash twrp back in yet) I have rebooted the phone and my computer as well. I tried my other phone to check the cable and it found it in ADB and Fastboot just fine. I do have the latest SDK installed. Any help would be greatly appreciated.
---Solution---
Chilipepprflea said:
I know this is probably too late for you guys, but maybe it will help someone else. Fastboot commands would result in "waiting on any device" and my Pixel 2 wouldn't boot out of the bootloader. I thought it was done for good based on this thread and others I've read...until I came across this Reddit https://www.reddit.com/r/GooglePixel/comments/b25nso/error_slot_unbootable_load_error/
I did what this guy did and held the power button (ended up being for a couple minutes in my case) and it vibrated and all is good again! adb recognized my phone and I was able to flash again.
Click to expand...
Click to collapse

You'll have to go back into bootloader and do a stock flash follow the steps on googles site. go back to 8.0 or whatever you were on before, make sure that boots up fine. You must not have had updated your sdk before trying to update to 9.0

I was going to just reflash everything but when I do fastboot devices its just blank as if the phone does not exist. Also the computer doesnt do its chime when I plug the USB in while its in bootloader. When the phone is off and I plug it in it shows the charging icon for a split second then boots into bootloader saying ERROR: Slot Unbootable: Load Error. If I try to do any commands in fastboot it just says "waiting for any device"

I was already on 9.0 and was just pushing the January security patch when it stopped near the end of the update. Now I can not get fastboot to even see the device.

Try removing all drivers and fastboot files on your pc. Sounds like you just flashed the wrong file. Were you rooted with magisk? or just on a stock rom. re download the full image and try and re flash. https://developers.google.com/android/images
Because of the slots (a and b) alot of people seem to have trouble flashing things. I have even messed things up as well. On the Pixel devices I havent been able to not go back into stock setups. Even if it took removing all files and starting over.
---------- Post added at 04:19 AM ---------- Previous post was at 04:18 AM ----------
I will keep checking back over here to see if you have any issues.

So I just tried what you had said. Deleted all the SDK files and uninstalled the drivers, rebooted computer and phone redownloaded everything and still can not find the phone via fastboot... magisk was installed but I was doing the full image install without the -w so it would not wipe. it was almost done with it and never actually booted into android it just stayed on the bootloader which I found strange. That is when I noticed that the phone could no longer be found via fastboot devices. I have tried different cords different ports and even a different computer and still have the same result. It did update the bootloader and radio portions of the update. I feel like if I can get fastboot to start working I can save this thing.

I got caught up with friends that came over. You have tried everything I would have tried. Which is good cause you seem to know what you are doing, but not good that it hasnt been resolved. Have you looked at this guide? https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

Coolpente said:
I started updating the phone to the Jan 2019 update from the Dec 2018 update (I just like having the latest updates) It rebooted into bootloader via ADB just fine. I then ran the flash all.bat without the -w so it wouldnt wipe the phone out completely. It started updating and rebooting just like normal after the bootloader and radio parts. It made it close to the end of the system update and did not reboot the phone. It went back to the bootloader which I thought was odd. Fastboot can no longer see the phone in Fastboot devices. When starting the phone it reboots back into bootloader saying load failed. It also will not boot into recovery (which I expected from the update and not getting to flash twrp back in yet) I have rebooted the phone and my computer as well. I tried my other phone to check the cable and it found it in ADB and Fastboot just fine. I do have the latest SDK installed. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Are you *sure* it will not boot to recovery? If you're not used to the stock recovery it can fool you. Many ppl see the dead android and stop there. If you can get into the stock recovery you can try sideloading an OTA via adb (which only works in recovery). I would also be trying different computers and cables. If you cannot use fastboot -and- you have no working recovery you might be dead in the water.

OMG @Coolpente!!!! THIS....HAPPENED...TO....ME!!!!
Holy crap! I can't believe this happened to someone else! I thought it was just me and my bad luck!
I literally was doing the same thing (only difference was on my gf's pixel 2 [walleye])! And those who have seen me around this forum the last year know that I am very knowledgeable and don't make the simple and "noob" mistakes! I've literally have helped and recovered people in this/our position -- so it is doubtful there was a amateur or novice mistake made in the updating process or "stone un-turned" in the recovery process!
So here is what happened to me, particularly, and my observations on it...
- When "crap hit the fan", it was very peculiar that fastboot would identify the phone's serial number as "??????????" (when running the command "fastboot devices"). Only after rebooting and disconnecting/reconnecting the usb cable did it (fastboot) simply just stop detecting. To make sure that my computer, usb port, cable, and fastboot is working correctly and able to process properly, I would make sure the fastboot process/server was not running, then I would actually run the command "fastboot getvar all", and as it would "would for device", I would plug in the phone, nothing would happen, then plug in my phone [taimen] (not my gf's walleye), and it would detect it and display all the pertinent information and device details, I would then unplug it from my phone, run the same getvar command, and lastly replug it into the phone (broken gf's walleye) with no detection or success.
- What's also interesting and of note is that when loading straight into the bootloader (via button combination), it displays no error in the list of device details. But when booting into the recovery (note: I, like the OP, had the TWRP custom recovery already flashed and installed) and also the system and/or from a power-off state, it states in red colored font and yellow background, "ERROR: Slot Unbootable: Load Error". Even more than that is when attempting to boot into Download mode, it states a different error (but in the same font style), "ERROR: Operation Denied"!
- I also attempted to manually change the slot in attempts to address the "slot unbootable..." "...load[ing] error", but -- due to either fastboot not detecting or the device not connecting properly I imagine -- without fastboot properly detecting, the commands wouldn't work and execute properly anyway. I've even taken steps further and attempted to format and custom "re-size" partitions. But, for the aforementioned reasons (presumably), it and attempts at commands like it wouldn't likely work and execute, again as previously reasoned. Also, in attempt to tackle the "slot" aspect of the issue, I tried Deuce's script; but as Deuce's script is, simply put, based off of the flash-all.bat that ends up being an advanced batch (pun intended) of commands that manually and individually flashes the stock images/partitions to the partitions of the device -- so, in essence, uses fastboot and since fastboot can't work.... I even found and attempted to use the (hardly heard of; at least to me) tool Skipsoft Android Toolkit (which looks genuinely super dooper awesome btw...)... all for naught :crying: ...
You know, after a year with the Pixel 2 (XL), and after coming back from messing my phone up (15+ times), and actually purely bricking it once (had to get it replaced), I always thought that, as long as one could access the device via the bootloader, one would always have hope (at least in the Pixel's case). So, it's curious but agonizingly ironic being able to access the bootloader (which was not the case in my one and only instance of bricking my device and having a completely "lost cause") just for me not to be able to do anything about it and/or fastboot to not be able to properly connect and send commands to it...
But to me and Coolpente (and anyone else who this may have happened to) I ultimately can't think of anything else that can be done at this point. To re-iterate, I/we had the most up-to-date platform-tools (r28.0.1), it has been proven that the usb cord, port, computer, and drivers are all working as I was able to get the "getvar all" command to work on another pixel mere seconds before attempting the same on this (broken) device, and even attempted all tools available...
Unfortunately, @Coolpente, it does look as if our phones are irrevocably "bricked" and it's all rather doomed and attempting to get it repaired/replaced by the manufacturer ("The Big G") is the only recourse we may have :crying::crying::crying:
I wrote this (very long) post in hopes of giving as much information and details as possible in the desperate hopes that any other solutions might be brought up...

simplepinoi177 said:
OMG @Coolpente!!!! THIS....HAPPENED...TO....ME!!!!
Holy crap! I can't believe this happened to someone else! I thought it was just me and my bad luck!
-- SNIP---
I wrote this (very long) post in hopes of giving as much information and details as possible in the desperate hopes that any other solutions might be brought up...
Click to expand...
Click to collapse
I am so glad I am not the only one that his has happened to! I have rooted several phones as well as almost bricking the one that ultimately bricked... (not up to date sdk tools) You have word for word the exact same thing that is happening to me. no recovery no booting and no download mode just the bootloader which is not found by fastboot. I thought at first it may have been the usb port in the phone disconnecting somehow but when plugging it in from a completely off state it does show the charging battery screen for a split second then boots into bootloader saying it can not load that slot. I am not very fluent in the disassembly of phones like this or I would check to see if the data parts of the USB port are not connected to the board.. It kills me that the phone is not even a year old and something like this would happen.. I have since gotten a replacement phone but I am very interested in seeing if there is a way to fix it in the near future outside of sending it in.

Coolpente said:
I am so glad I am not the only one that his has happened to! I have rooted several phones as well as almost bricking the one that ultimately bricked... (not up to date sdk tools) You have word for word the exact same thing that is happening to me. no recovery no booting and no download mode just the bootloader which is not found by fastboot. I thought at first it may have been the usb port in the phone disconnecting somehow but when plugging it in from a completely off state it does show the charging battery screen for a split second then boots into bootloader saying it can not load that slot. I am not very fluent in the disassembly of phones like this or I would check to see if the data parts of the USB port are not connected to the board.. It kills me that the phone is not even a year old and something like this would happen.. I have since gotten a replacement phone but I am very interested in seeing if there is a way to fix it in the near future outside of sending it in.
Click to expand...
Click to collapse
I know it is highly unlikely, but I'm hanging in there hoping for the same thing as well...
Yeah, it's troubling that this is can be happening coming from very "seasoned" users!
I was considering the same that it feels more like a hardware issue since everything seems to work on the computer end as well as everything working on another pixel device, BUT I can't see how a failed "fastboot" command and process can effect any kind of hardware or physical connections ("data parts")?!
If anything, I believe it has to do with the sequence of events of how things crapped out... I believe that, in some random manner, the bootloader -- which gets flashed and updated first; referencing the script in the flash-all.bat -- gets replaced, but isn't installed/initialized/"placed" properly -- but curiously enough, is installed "properly" enough that it can be re-entered after turning the device off -- that most everything works BUT the all important fastboot connection/interface/detection! That's why I attempted to manually flash the bootloader image ("fastboot flash bootloader bootloader.img"), but, "head-bangingly" poetic in its irony of course, fastboot is required to accomplish this ("this" being fixing freaking "fastboot"! :crying: )
I'm terrified to update my own Pixel at this point.
Unfortunately, this seems to have only been documented in our two cases (so far)...I wonder if it's even worth creating a Google support ticket in attempts to bring it up to them in hopes that they fix whatever might be causing this -- hopefully assisting and saving others from this disaster -- and/or even pull the update until it is stable (although, like I stated, it seems not a prevalent enough issue that many either have successfully updated via this image and process or most haven't brought it up anywhere) and/or keep it from happening in the next update.
In any case, here's hoping ("pray for the best, expect the worst" kind of scenario is most likely appropriate) any kind of solution materializes, or, at the very least, can be shown as a "word of warning" and caution about the (this, specifically) update....

simplepinoi177 said:
OMG @Coolpente!!!! THIS....HAPPENED...TO....ME!!!!
Holy crap! I can't believe this happened to someone else! I thought it was just me and my bad luck!
I literally was doing the same thing (only difference was on my gf's pixel 2 [walleye])!
Click to expand...
Click to collapse
Find a new girlfriend, your problem will be easily solved.

simplepinoi177 said:
I know it is highly unlikely, but I'm hanging in there hoping for the same thing as well...
Yeah, it's troubling that this is can be happening coming from very "seasoned" users!
I was considering the same that it feels more like a hardware issue since everything seems to work on the computer end as well as everything working on another pixel device, BUT I can't see how a failed "fastboot" command and process can effect any kind of hardware or physical connections ("data parts")?!
If anything, I believe it has to do with the sequence of events of how things crapped out... I believe that, in some random manner, the bootloader -- which gets flashed and updated first; referencing the script in the flash-all.bat -- gets replaced, but isn't installed/initialized/"placed" properly -- but curiously enough, is installed "properly" enough that it can be re-entered after turning the device off -- that most everything works BUT the all important fastboot connection/interface/detection! That's why I attempted to manually flash the bootloader image ("fastboot flash bootloader bootloader.img"), but, "head-bangingly" poetic in its irony of course, fastboot is required to accomplish this ("this" being fixing freaking "fastboot"! :crying: )
I'm terrified to update my own Pixel at this point.
Unfortunately, this seems to have only been documented in our two cases (so far)...I wonder if it's even worth creating a Google support ticket in attempts to bring it up to them in hopes that they fix whatever might be causing this -- hopefully assisting and saving others from this disaster -- and/or even pull the update until it is stable (although, like I stated, it seems not a prevalent enough issue that many either have successfully updated via this image and process or most haven't brought it up anywhere) and/or keep it from happening in the next update.
In any case, here's hoping ("pray for the best, expect the worst" kind of scenario is most likely appropriate) any kind of solution materializes, or, at the very least, can be shown as a "word of warning" and caution about the (this, specifically) update....
Click to expand...
Click to collapse
I have considered going to a custom rom and avoiding the stock rom completely... Which would avoid ever needing to use fastboot to update in the future.. but its to late for one phone but not to late for the other. I havent even looked into roms since CM broke down...

Coolpente said:
I have considered going to a custom rom and avoiding the stock rom completely... Which would avoid ever needing to use fastboot to update in the future.. but its to late for one phone but not to late for the other. I havent even looked into roms since CM broke down...
Click to expand...
Click to collapse
Yeah....but, if you think of it, I've been updating by way of Full Factory images via fastboot for over a year (14 months to be exact), so the last 13 times and 13 out of 14 times it worked perfectly....so, pure statistics, I wonder if swearing off fastboot forever is truly pertinent just yet...
Well, at least the pixel 2's been out for....14 months, apparently...so there seems to be a lot of good, stable custom ROMs that have been long in development to choose from, if anything... **~shrugs~**

simplepinoi177 said:
Yeah....but, if you think of it, I've been updating by way of Full Factory images via fastboot for over a year (14 months to be exact), so the last 13 times and 13 out of 14 times it worked perfectly....so, pure statistics, I wonder if swearing off fastboot forever is truly pertinent just yet...
Well, at least the pixel 2's been out for....14 months, apparently...so there seems to be a lot of good, stable custom ROMs that have been long in development to choose from, if anything... **~shrugs~**
Click to expand...
Click to collapse
As far as statistics are concerned yea I have been updating 2 pixels by full factory images for the last year and one has survived all 12 months while the other made it through 11 of 12. but in fear of bricking another pixel device knowing this could potentially happen again... it feels as if going to custom roms would for sure be the safest method and still keep root. Of course losing root and going pure stock would be 100% the best... I love having root and dont want to lose it.

Coolpente said:
As far as statistics are concerned yea I have been updating 2 pixels by full factory images for the last year and one has survived all 12 months while the other made it through 11 of 12. but in fear of bricking another pixel device knowing this could potentially happen again... it feels as if going to custom roms would for sure be the safest method and still keep root. Of course losing root and going pure stock would be 100% the best... I love having root and dont want to lose it.
Click to expand...
Click to collapse
Yeah, I see what you're saying and in the exact same boat (2 pixels, gf's is a walleye, mine's a taimen, both have been updated monthly with no issues or def bricking issues, so 14 of 14 and 13 of 14...)...
But I guess that's definitely one of the "safest" methods, just that support for ROMs come and go (hell, even one of the original custom kernels [Flash] is EOL)...but Pixel 2 is only a year "in" and Google will continue to support it for the foreseeable future so it may look like regular support for walleye/taimen-related mods will continue to get regular updates and support as well...
But still, as I enjoy our conversations, it also serves to "bump" this thread as well...
Anyone have any idea on how to reinstall bootloaders, switch slots, enter custom recovery, flash anything all without -- and this is key -- fastboot (because fastboot will not detect and connect with the device)?!?!

I just tried to update to Feb from Jan and this happened to me....
Anything I can do about it?

James1258 said:
I just tried to update to Feb from Jan and this happened to me....
Anything I can do about it?
Click to expand...
Click to collapse
Awww crap! Super sorry to hear that! As you can see, not a lot of ideas or thoughts were submitted, and haven't been in a long while, so there doesn't seem to be much/anything that can be done it seems...
If you truly have the exact same thing, then that means that the USB connection is not working, so, you're not able to get into the recovery nor able to run any commands, so the only recourse it seems me and @Coolpente is to contact Google and attempt at a RMA...
But, as this is a third instance -- there may be more; I'm convinced there are, they just have not spoken up here specifically -- I wonder if this is something to be brought up to Google Support (https://productforums.google.com/forum/#!forum/phone-by-google) and their support forums? I mean, although this might not be a widespread widely known issue, this issue does make the device completely unusable and able to be rescued! For me, that's a serious matter -- as most other issues you can learn to live with it (while still being able to use the device for the most part) and/or it's something that can be worked on, repaired, debugged, etc. -- that needs to be attended to, dealt with, or at the very least brought to their attention.

simplepinoi177 said:
Awww crap! Super sorry to hear that! As you can see, not a lot of ideas or thoughts were submitted, and haven't been in a long while, so there doesn't seem to be much/anything that can be done it seems...
If you truly have the exact same thing, then that means that the USB connection is not working, so, you're not able to get into the recovery nor able to run any commands, so the only recourse it seems me and @Coolpente is to contact Google and attempt at a RMA...
But, as this is a third instance -- there may be more; I'm convinced there are, they just have not spoken up here specifically -- I wonder if this is something to be brought up to Google Support (https://productforums.google.com/forum/#!forum/phone-by-google) and their support forums? I mean, although this might not be a widespread widely known issue, this issue does make the device completely unusable and able to be rescued! For me, that's a serious matter -- as most other issues you can learn to live with it (while still being able to use the device for the most part) and/or it's something that can be worked on, repaired, debugged, etc. -- that needs to be attended to, dealt with, or at the very least brought to their attention.
Click to expand...
Click to collapse
I just contacted Google for an RMA. Hope it doesn't occur on the phone that will be shipped to me. Now I am without a phone for a couple weeks...

James1258 said:
I just tried to update to Feb from Jan and this happened to me....
Anything I can do about it?
Click to expand...
Click to collapse
Did you also ran the flash all without - w?
Sent from my Pixel 2 XL using Tapatalk

Trying to get a clean install on a crippled SM-T540 (Galaxy Tab Active Pro).

Edit 3: USIC, after further investigation, has confirmed the tablet was actually one lost in shipment and compensated for by insurance, the sale was legitimate (not a stolen device) and they unenrolled it from KNOX before I could ask if they would do so. So, overall a satisfactory outcome, even if the tech part of me wanted to find a way to defeat a technical challenge.
EDIT 2: The device may not be stolen after all, seller has given a plausible explanation. Withholding further judgement until more information comes in.
EDIT: I was originally thinking of 'USIC' as a subsystem of Android or KNOX. A user on Reddit suggested I reach out to the company USIC and see if the tablet was stolen from them. I did. It was. Will be getting the tablet back into their hands and pursuing a refund from the eBay seller. Will leave this post up in case anyone has a use for the technical rabbit hole I went down.
Backstory: Found a good deal on a new Galaxy Tab Active Pro from an IT liquidator company on eBay, it was listed as locked and price reduced because of that. I thought along the lines of 'hardware access is total access' and figured I would be able to wipe / reset it.
Device arrived today, the crippleware (MDM or administration software actually, but I'm feeling ornery at it) installed is Soti Mobicontrol. I can boot into the OS but a bunch of stuff is disabled. First I initiated a factory reset from Settings - it resets and during setup lists "This tablet is protected by Knox Cloud Service. To continue setup, connect to a Wi-Fi or mobile network." From there it states "Your admin can monitor and manage settings".... a bunch of stuff ending with "USIC will manage and monitor this device using the following app: MobiControl" with the only option being 'Accept & continue'.
Tried another factory reset through the boot menu (hold down vol down and power to reboot followed by hold down vol up) - same result.
Found and downloaded the same version firmware the tablet currently has: SM-T540_XAR_T540XXU2BTG5_fac.zip where XAR appears to be the US/Canada region code and T540XXU2BTG5 is the exact version of firmware the tablet currently has installed (verified by going to 'Software information' in settings).
Downloaded latest version of Odin (3.13), booted the tablet into the correct mode and flashed clean firmware (just the AP firmware) to the device. Went through first install sequence to no change in behavior, still installs Soti Mobicontrol as a device admin.
I've looked into maybe getting TWRP installed (so I can delete KNOX from TWRP file browser perhaps as demonstrated here:
) but as far as I can tell there isn't a build for this version of the tablet - closest I can get is for the SM-T547 XDA forum post on it here: https://forum.xda-developers.com/t/...alaxy-tab-active-pro-10-1-snapdragon.4284347/. Also not sure how I would get it installed since I can't enter dev options in the tablet (tapping on Build number, even in safe mode, results in a popup: Action not allowed This action is disabled by MobiControl. Contact your organization's administrator to learn more.)
I've found someone on YouTube (
) who removed the software just by intentionally entering a wrong password until a factory reset tripped - but I am already able to use the factory reset option and the software comes back. I'm thinking Soti Mobicontrol and the KNOX service are separate issues and in this person's example he was only dealing with Soti and not KNOX Enrollment.
Next I found this gentleman on Youtube:
who specifically mentions using the 'Nand erase' option in Odin along with flashing all files in the stock firmware to remove management software. Tried that, no luck. Same as each install I get the message 'Updating... Updating Knox Enrollment Service... X%' after being required to connect to wifi to continue setup with the 'Skip' option greyed out.
So, that's where I am right now with it, and I refuse to give up. Ideas?

@studentoflife don't know this device but might be a chance to flash the multiple part stock ROM you can get via Samfirm_reborn.

bmwdroid said:
@studentoflife don't know this device but might be a chance to flash the multiple part stock ROM you can get via Samfirm_reborn.
Click to expand...
Click to collapse
I am unfamiliar with Samfirm_reborn. What is this project? I can't seem to find much in the way of descriptive notes.
Edit: apologies, did some googling and now know what Samfirm_reborn is. I'm pretty sure I've already flashed all parts of the stock ROM - downloaded the T540XXU2BTG5 version firmware and flashed the BL, AP and CSC images. No CP image given this version of the device does not have a cellular modem.
Hm. I suddenly wonder what will happen if I reflash with the earliest version instead of the current one. I know I don't want to update it to the latest firmware in case that applies some security patch that can't be downgraded and locks out some workaround I haven't found yet, but downgrading... maybe.

I have a similar tablet with mobicontrol. I can't unlock OEM so all the methods of flashing new firmware I tried, failed. Have you had any luck since your last post?