Database Info

[Q] MotoG XT1032 soft-bricked - need some help

Hi Mates!
Ive got a soft bricked moto g, it says bl is locked, i cant flash retail firmware (hab check fail error), ive got the unlock code, but if i try to unlock the bl with fastboot oem unlock, it says
(bootloader) fastboot oem unlock disabled!
FAILED (remote failure)
finished. total time: 0.025s
Any suggestions?

Here is my fastboot prompt:
d:\MotoG\442>fastboot.exe flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1940 KB)...
OKAY [ 0.147s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.565s]
finished. total time: 1.714s
d:\MotoG\442>fastboot.exe flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (619 KB)...
OKAY [ 0.125s]
writing 'logo'...
OKAY [ 0.125s]
finished. total time: 0.252s
d:\MotoG\442>fastboot.exe flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.429s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.485s
d:\MotoG\442>fastboot.exe flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.395s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.426s
d:\MotoG\442>fastboot.exe flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (255768 KB)...
OKAY [ 8.714s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.851s
d:\MotoG\442>fastboot.exe flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (244360 KB)...
OKAY [ 8.304s]
writing 'system'...
OKAY [ 10.235s]
finished. total time: 18.541s
d:\MotoG\442>fastboot.exe flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (220989 KB)...
OKAY [ 7.533s]
writing 'system'...
(bootloader) Failed to validate sparse image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 19.965s
d:\MotoG\442>
d:\MotoG\442>fastboot.exe flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (47476 KB)...
OKAY [ 1.648s]
writing 'modem'...
OKAY [ 1.479s]
finished. total time: 3.128s
d:\MotoG\442>fastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.066s]
finished. total time: 0.067s
d:\MotoG\442>fastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.067s]
finished. total time: 0.067s
d:\MotoG\442>fastboot.exe flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (102 KB)...
OKAY [ 0.104s]
writing 'fsg'...
OKAY [ 0.076s]
finished. total time: 0.181s
d:\MotoG\442>fastboot.exe reboot
rebooting...
finished. total time: 0.001s

Try using "mfastboot" it could maybe work... Just a thought.

Destr0y3r said:
Try using "mfastboot" it could maybe work... Just a thought.
Click to expand...
Click to collapse
I already tried it with no luck...if you look at getvar data you will see cid is 0xDEAD thats why i am worried.

Try to use another firmware using mfastboot manually and relock your boot loader
Sent from my Moto G using XDA Premium 4 mobile app

pfufle said:
Try to use another firmware using mfastboot manually and relock your boot loader
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried many firmware without luck, the problem is in the BL i see devices locked status 0, but the unlock command doesn't work.

You must be making a mistake...request for the unlock code again
Sent from my Moto G using XDA Premium 4 mobile app

pfufle said:
You must be making a mistake...request for the unlock code again
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is the message i've got after fastboot oem unlock "unlockcode"
(bootloader) fastboot oem unlock disabled!
FAILED (remote failure)
finished. total time: 0.025s
This is the story: the former owner tried to root the phone, as he said he unlocked the bootloader, then something went wrong. He tried to install CM, and he softbricked the phone. It has the IMEI but there is some problem with CID and UID as a look at the prompt from fastboot getvar all. Somehow the unlock commands doesnt work, and i ve got preflash vaildation faild errors, when i try to flash boot or recovery or system img. The phone wont boot if i turn it on it goes to bootloader.

Ask for the unlock code again
Sent from my Moto G using XDA Premium 4 mobile app

pfufle said:
Ask for the unlock code again
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried it last week, but if i enter the command fastboot oem get_unlock_data it won't post the unlock token.

Well I think you are the first person who has faced this problem...I think there is something wrong with the commands you are typing....
Sent from my Moto G using XDA Premium 4 mobile app

my theory
I think your gonna need to wipe the device filly like its partions and such. ThTs all I can think off
Found this http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html?m=1

Awesomeslayerg said:
I think your gonna need to wipe the device filly like its partions and such. ThTs all I can think off
Found this http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html?m=1
Click to expand...
Click to collapse
I was wondering if the former owner unlocked the bl than flashed a stock image with a bl which doesn't support unlock and that why I am getting 0xdead Cid and can't reopen bl...

Wipe simply everything from your phone and then restore the stock firmware
Sent from my XT1032 using XDA Premium 4 mobile app

randras83 said:
I was wondering if the former owner unlocked the bl than flashed a stock image with a bl which doesn't support unlock and that why I am getting 0xdead Cid and can't reopen bl...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2623587
Found this you could try this.

I came across a similar situation after writing an emmc image taken from one XT1032 to a second XT1032.
After rebooting, the second XT1032 (which was already unlocked) behaved just like your device (reported as LOCKED, and when trying to unlock, gave the 'fastboot oem unlock disabled!' error message).
Eventually, and with some trickery, I was able to resolve the issue by restoring the 'cid' and 'sp' partitions to their original state.

check device manager on windows and see if you have unknow devices on your phone and change adb from there

tal.aloni said:
I came across a similar situation after writing an emmc image taken from one XT1032 to a second XT1032.
After rebooting, the second XT1032 (which was already unlocked) behaved just like your device (reported as LOCKED, and when trying to unlock, gave the 'fastboot oem unlock disabled!' error message).
Eventually, and with some trickery, I was able to resolve the issue by restoring the 'cid' and 'sp' partitions to their original state.
Click to expand...
Click to collapse
It has been quite a while since you posted this, but I have the same problem where I overwrote the cid partition and I am unsure how to get it back. Any chance you remember this trickery?
Thanks,
Nathan

I have the same problem. Any fix?

ISSue XT0133
randras83 said:
I tried it last week, but if i enter the command fastboot oem get_unlock_data it won't post the unlock token.
Click to expand...
Click to collapse
same issue, i'm also facing bro any solutions?

[Q] Loopboot on Android logo

Hi,
Just received my opo yesterday and the phone never booted successfully.
When I turn the phone on, the android logo appears and, after a few seconds, it vibrates and then reboots... Over and over again.
Recovery mode doesn't work, but I can enter fastboot mode.
Tried to unlock the bootloader to flash the factory image but it seams that it isn't working even if the command returns successful because when I try to flash something it says that the device is locked.
I filled a ticket on OP's support but I'm afraid I don't get a response before 10+ days.
Does anyone have any suggestion to help?
Thanks!

This situation seems like a situation I've heard in the past. Did you happen to use a toolkit to root?
Are you able to boot into a custom recovery by typing fastboot boot recovery.img (download TWRP and rename it to recovery.img putting it into fastboot)
Please don't use a toolkit to do this.

I didn't tried boot into a custom recovery yet.
I'll try that as soon as I get home.
First I tried manually and then by using a toolkit and the results were the same.
Thanks!

I tried booting into TWRP recovery:
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.442s]
booting...
OKAY [ 0.021s]
finished. total time: 0.463s
But when the booted again it didn't go to the recovery and started the bootloop again.
Any other ideias?
Thanks!

Hi, I believe your phone simply has no rom, so you have to flash one with fastboot. I've seen you already have fastboot working, so that will greatly help.
Follow this and your phone should hopefully work as expected :
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Don't hesitate to ask.
Enviado desde mi GT-P5210 mediante Tapatalk

adlx.xda said:
Hi, I believe your phone simply has no rom, so you have to flash one with fastboot. I've seen you already have fastboot working, so that will greatly help.
Follow this and your phone should hopefully work as expected :
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Don't hesitate to ask.
Enviado desde mi GT-P5210 mediante Tapatalk
Click to expand...
Click to collapse
Thanks for your help.
That was my first thought and I tried to flash the factory image a number of times...here's what I get:
target reported max download size of 536870912 bytes
sending 'modem' (56241 KB)...
OKAY [ 1.996s]
writing 'modem'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 1.999s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ 0.015s]
writing 'sbl1'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.019s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.006s
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.004s]
writing 'dbi'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'aboot' (374 KB)...
OKAY [ 0.017s]
writing 'aboot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.020s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.010s]
writing 'rpm'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.013s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.014s]
writing 'tz'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.017s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.366s]
writing 'LOGO'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.369s
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: afb25fe8
--------------------------------------------
checking product...
OKAY [ 0.003s]
sending 'boot' (5798 KB)...
OKAY [ 0.208s]
writing 'boot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.227s
Press any key to exit...
It seems that the bootloader is unlocked, but I tried to unlock it several times:
...
OKAY [ 0.010s]
finished. total time: 0.010s
But, it still doesn't work!!!

Did you fastboot oem unlock? I don't remember the exact command by memory, sorry. You can probably find it on any One plus forum.
Edit: yep, command is correct.
Enviado desde mi GT-P5210 mediante Tapatalk

adlx.xda said:
Did you fastboot oem unlock? I don't remember the exact command by memory, sorry. You can probably find it on any One plus forum.
Enviado desde mi GT-P5210 mediante Tapatalk
Click to expand...
Click to collapse
Yes...it's the last piece of my last message. Sorry if it wasn't clear.
Apparently, it works fine...but then I get those messages when trying to flash anything.

Hum, I don't know then... Weird.
Enviado desde mi GT-P5210 mediante Tapatalk

adlx.xda said:
Hum, I don't know then... Weird.
Enviado desde mi GT-P5210 mediante Tapatalk
Click to expand...
Click to collapse
Yes, unfortunately it's very weird.
If you remember anything else, please let me know.
Thank you for your help!

What does it return when you issue this command?
Code:
fastboot oem device-info
Transmitted via Bacon

timmaaa said:
What does it return when you issue this command?
Code:
fastboot oem device-info
Transmitted via Bacon
Click to expand...
Click to collapse
Code:
>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.004s]
finished. total time: 0.004s
Thanks!

pr3tender said:
Code:
>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.004s]
finished. total time: 0.004s
Thanks!
Click to expand...
Click to collapse
Your bootloader isn't unlocked so there's no way flashing the factory images is going to work. Can you copy/paste the text from an attempt at unlocking the bootloader?
Transmitted via Bacon

timmaaa said:
Your bootloader isn't unlocked so there's no way flashing the factory images is going to work. Can you copy/paste the text from an attempt at unlocking the bootloader?
Transmitted via Bacon
Click to expand...
Click to collapse
The text from the attempt at unlocking the bootloader is already in a previous post and it returns ok!
Nevertheless, as soon as I get home I will try again.
Thanks!

timmaaa said:
Your bootloader isn't unlocked so there's no way flashing the factory images is going to work. Can you copy/paste the text from an attempt at unlocking the bootloader?
Transmitted via Bacon
Click to expand...
Click to collapse
So, here are the results:
Code:
>fastboot devices
afb25fe8 fastboot
Code:
>fastboot oem unlock
...
OKAY [ 0.011s]
finished. total time: 0.011s
The OPO rebooted and then fastboot mode again:
Code:
>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.004s]
finished. total time: 0.004s
Any ideias?
Thanks!

Did you buy the phone directly from OPO? Or did you buy it from somewhere else? If so, where?
Transmitted via Bacon

Unlock & Tamper Bit
Have a look at this.
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912

timmaaa said:
Did you buy the phone directly from OPO? Or did you buy it from somewhere else? If so, where?
Transmitted via Bacon
Click to expand...
Click to collapse
I bought the phone from OPO and I already opened a support ticket, but I know they take a long time to reply...

ultrawires said:
Unlock & Tamper Bit
Have a look at this.
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Click to expand...
Click to collapse
I read every post of that topic, but it seams that to use that mod it's necessary to have the bootloader unlocked or to temporary boot into a custom recovery...and I can't do neither.

Temp recovery mode is from fastboot.
Get into fastboot mode, connect to PC. From PC, enter
fastboot boot <recovery.img>
You'll need the recovery.img file in you PC. That'll get you into temp recovery mode.

Cant unlock Bootloader

Hello, i have a htc one mini and i need to unlock the lock screen.
I already try factory reset booting with volume - and power but dont work.
So i try to flash recovery but bootloader is locked.
I try to unlock bootloader i write the comand
-fastboot flash unlocktoken Unlock_code.bin-
i get this result
C:\>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 800227328 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.157s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.012s]
finished. total time: 0.171s
But dont pop up anything on the phone.
any help? tanks

i cant install twrp htc u11 version 2.33.401.19 - Unlock Bootloader:ok adb installer

i cant install twrp htc u11 version 2.33.401.19 - Unlock Bootloaderk adb installer
but flach fail
PS C:\Users\HP\Desktop\Fastboot> fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (39476 KB)...
OKAY [ 1.390s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 1.395s
PS C:\Users\HP\Desktop\Fastboot>

abdedaeim said:
i cant install twrp htc u11 version 2.33.401.19 - Unlock Bootloaderk adb installer
but flach fail
PS C:\Users\HP\Desktop\Fastboot> fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (39476 KB)...
OKAY [ 1.390s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 1.395s
PS C:\Users\HP\Desktop\Fastboot>
Click to expand...
Click to collapse
Try fastboot boot twrp.img and then flash it from recovery.

Pixel 3 won't let me flash anything

I have official android 11 without root or anything but it does not let me flash anything or boot and it tells me the fastboot of the mobile that is in the slot: B
PS C:\Users\vickd\Desktop\blueline-rp1a.200720.009> fastboot boot TWRP.img
downloading 'boot.img'...
OKAY [ 2.548s]
booting...
FAILED (remote: Error verifying the received boot.img: Invalid Parameter)
finished. total time: 5.862s
PS C:\Users\vickd\Desktop\blueline-rp1a.200720.009> Fastboot flash recovery TWRP.img
target reported max download size of 268435456 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.621s]
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
finished. total time: 2.773s
PS C:\Users\vickd\Desktop\blueline-rp1a.200720.009>

vickmen said:
I have official android 11 without root or anything but it does not let me flash anything or boot and it tells me the fastboot of the mobile that is in the slot: B
PS C:\Users\vickd\Desktop\blueline-rp1a.200720.009> fastboot boot TWRP.img
downloading 'boot.img'...
OKAY [ 2.548s]
booting...
FAILED (remote: Error verifying the received boot.img: Invalid Parameter)
finished. total time: 5.862s
PS C:\Users\vickd\Desktop\blueline-rp1a.200720.009> Fastboot flash recovery TWRP.img
target reported max download size of 268435456 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.621s]
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
finished. total time: 2.773s
PS C:\Users\vickd\Desktop\blueline-rp1a.200720.009>
Click to expand...
Click to collapse
TWRP has not worked on Pixel 3 since Android 9. There is a test build for Android 10 at https://forum.xda-developers.com/pixel-3/development/twrp-3-2-3-0-pixel-3-t3861622/page29, but the only response to that post was it did not work. There is nothing for Android 11.

dcarvil said:
TWRP has not worked on Pixel 3 since Android 9. There is a test build for Android 10 at https://forum.xda-developers.com/pixel-3/development/twrp-3-2-3-0-pixel-3-t3861622/page29, but the only response to that post was it did not work. There is nothing for Android 11.
Click to expand...
Click to collapse
Thank you, he enters me and everything but he asks me for a password, I put it on him and nothing but at least I know that my mobile is in good condition, I had been scared hahaha