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.
Related
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.000s]
finished. total time: 0.156s
Unlock device bootloader with htcdev. What is the problem?
haqd999 said:
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.000s]
finished. total time: 0.156s
Unlock device bootloader with htcdev. What is the problem?
Click to expand...
Click to collapse
There doesn't appear to be a problem... Please be more specific.
Step 13 doesn't apear
i018.radikal.ru/1208/af/122517befc24.jpg
I don't see the disclaimer on the phone
haqd999 said:
Step 13 doesn't apear
i018.radikal.ru/1208/af/122517befc24.jpg
I don't see the disclaimer on the phone
Click to expand...
Click to collapse
So what did you do?
Hi all,
My moto g has a problem. It is stuck at the "warning bootloader unlocked screen"
I can boot into fastboot and flash stuff but when i try to boot it keeps displaying the "warning bootloader unlocked screen"
i have tryed several guides to flash orignal firmware but somehow it doesnt work.
Stange thing is is that i have CMW installed but when i flash TWRP or something it says its ok but then when i go to recovery CMW always comes back.
Had the same problem, white boot logo. Download from here http://forum.xda-developers.com/showthread.php?t=2646415 During the process it will say something about boot loader, but never mind. U should have a OTA update when it finished and will lose root, but its not a big problem
regards
bobrda said:
Had the same problem, white boot logo. Download from here http://forum.xda-developers.com/showthread.php?t=2646415 During the process it will say something about boot loader, but never mind. U should have a OTA update when it finished and will lose root, but its not a big problem
regards
Click to expand...
Click to collapse
Yeah i tryed that one but it doesnt work even the logo doesnt work.
Beukhof1 said:
Yeah i tryed that one but it doesnt work even the logo doesnt work.
Click to expand...
Click to collapse
Maybe to try this one? Its the GPE rom but it may fix the phone .. http://forum.xda-developers.com/showthread.php?t=2646404
bobrda said:
Maybe to try this one? Its the GPE rom but it may fix the phone .. http://forum.xda-developers.com/showthread.php?t=2646404
Click to expand...
Click to collapse
Same thing its says its all ok but when i boot i just keeps showing the logo.
Code:
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>SET fastboot=fastboot
.exe
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe getvar m
ax-sparse-size
max-sparse-size: 268435456
finished. total time: 0.002s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe oem fb_m
ode_set
... FAILED (remote failure)
finished. total time: 0.036s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash pa
rtition gpt.bin
sending 'partition' (32 KB)... OKAY [ 0.081s]
writing 'partition'... INFOThis may take a few seconds, if a
INFOdifferent partition table is being
INFOflashed since we need to backup
INFOand restore a few partitions
INFOFlashing primary GPT image...
INFOFlashing backup GPT image...
OKAY [ 0.469s]
finished. total time: 0.550s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash mo
toboot motoboot.img
sending 'motoboot' (1940 KB)... OKAY [ 0.205s]
writing 'motoboot'... INFOflashing tz ...
INFOflashing rpm ...
INFOflashing sdi ...
INFOflashing aboot ...
INFOflashing sbl1 ...
OKAY [ 1.380s]
finished. total time: 1.586s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash mo
dem NON-HLOS.bin
sending 'modem' (47484 KB)... OKAY [ 4.088s]
writing 'modem'... OKAY [ 0.732s]
finished. total time: 4.820s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash fs
g fsg.mbn
sending 'fsg' (719 KB)... OKAY [ 0.109s]
writing 'fsg'... OKAY [ 0.032s]
finished. total time: 0.142s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase mo
demst1
erasing 'modemst1'... OKAY [ 0.035s]
finished. total time: 0.035s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase mo
demst2
erasing 'modemst2'... OKAY [ 0.046s]
finished. total time: 0.046s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash lo
go logo.bin
sending 'logo' (2563 KB)... OKAY [ 0.271s]
writing 'logo'... OKAY [ 0.085s]
finished. total time: 0.356s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash bo
ot boot.img
sending 'boot' (10240 KB)... OKAY [ 0.896s]
writing 'boot'... OKAY [ 0.731s]
finished. total time: 1.627s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash re
covery recovery.img
sending 'recovery' (10240 KB)... OKAY [ 0.897s]
writing 'recovery'... OKAY [ 0.729s]
finished. total time: 1.626s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash sy
stem system.img_sparsechunk1
sending 'system' (248834 KB)... OKAY [ 21.396s]
writing 'system'... INFOInvalid signed image
OKAY [ 4.452s]
finished. total time: 25.848s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash sy
stem system.img_sparsechunk2
sending 'system' (253442 KB)... OKAY [ 23.077s]
writing 'system'... INFOFailed to validate sparse image
OKAY [ 4.052s]
finished. total time: 27.131s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash sy
stem system.img_sparsechunk3
sending 'system' (210534 KB)... OKAY [ 19.748s]
writing 'system'... INFOFailed to validate sparse image
OKAY [ 3.446s]
finished. total time: 23.195s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase ca
che
erasing 'cache'... OKAY [ 0.014s]
finished. total time: 0.015s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase us
erdata
erasing 'userdata'... OKAY [ 0.036s]
finished. total time: 0.037s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe oem fb_m
ode_clear
... OKAY [ 0.021s]
finished. total time: 0.022s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>pause
Press any key to continue . . .
Beukhof1 said:
Same thing its says its all ok but when i boot i just keeps showing the logo.
Code:
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>SET fastboot=fastboot
.exe
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe getvar m
ax-sparse-size
max-sparse-size: 268435456
finished. total time: 0.002s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe oem fb_m
ode_set
... FAILED (remote failure)
finished. total time: 0.036s
Sorry I cant help you than. This two rooms work on my phone.. talking about xt 1032
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash pa
rtition gpt.bin
sending 'partition' (32 KB)... OKAY [ 0.081s]
writing 'partition'... INFOThis may take a few seconds, if a
INFOdifferent partition table is being
INFOflashed since we need to backup
INFOand restore a few partitions
INFOFlashing primary GPT image...
INFOFlashing backup GPT image...
OKAY [ 0.469s]
finished. total time: 0.550s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash mo
toboot motoboot.img
sending 'motoboot' (1940 KB)... OKAY [ 0.205s]
writing 'motoboot'... INFOflashing tz ...
INFOflashing rpm ...
INFOflashing sdi ...
INFOflashing aboot ...
INFOflashing sbl1 ...
OKAY [ 1.380s]
finished. total time: 1.586s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash mo
dem NON-HLOS.bin
sending 'modem' (47484 KB)... OKAY [ 4.088s]
writing 'modem'... OKAY [ 0.732s]
finished. total time: 4.820s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash fs
g fsg.mbn
sending 'fsg' (719 KB)... OKAY [ 0.109s]
writing 'fsg'... OKAY [ 0.032s]
finished. total time: 0.142s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase mo
demst1
erasing 'modemst1'... OKAY [ 0.035s]
finished. total time: 0.035s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase mo
demst2
erasing 'modemst2'... OKAY [ 0.046s]
finished. total time: 0.046s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash lo
go logo.bin
sending 'logo' (2563 KB)... OKAY [ 0.271s]
writing 'logo'... OKAY [ 0.085s]
finished. total time: 0.356s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash bo
ot boot.img
sending 'boot' (10240 KB)... OKAY [ 0.896s]
writing 'boot'... OKAY [ 0.731s]
finished. total time: 1.627s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash re
covery recovery.img
sending 'recovery' (10240 KB)... OKAY [ 0.897s]
writing 'recovery'... OKAY [ 0.729s]
finished. total time: 1.626s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash sy
stem system.img_sparsechunk1
sending 'system' (248834 KB)... OKAY [ 21.396s]
writing 'system'... INFOInvalid signed image
OKAY [ 4.452s]
finished. total time: 25.848s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash sy
stem system.img_sparsechunk2
sending 'system' (253442 KB)... OKAY [ 23.077s]
writing 'system'... INFOFailed to validate sparse image
OKAY [ 4.052s]
finished. total time: 27.131s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash sy
stem system.img_sparsechunk3
sending 'system' (210534 KB)... OKAY [ 19.748s]
writing 'system'... INFOFailed to validate sparse image
OKAY [ 3.446s]
finished. total time: 23.195s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase ca
che
erasing 'cache'... OKAY [ 0.014s]
finished. total time: 0.015s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase us
erdata
erasing 'userdata'... OKAY [ 0.036s]
finished. total time: 0.037s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe oem fb_m
ode_clear
... OKAY [ 0.021s]
finished. total time: 0.022s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Sorry I cant help you. It works on my phone. model xt 1032
bobrda said:
Sorry I cant help you. It works on my phone. model xt 1032
Click to expand...
Click to collapse
I have the same model
Beukhof1 said:
I have the same model
Click to expand...
Click to collapse
Don't know whats couching you the problem. try to push rom via adb
or maybe this one http://forum.xda-developers.com/showthread.php?t=2542219
i had no success with this rom, but...
it's beyond my knowledge
bobrda said:
Don't know whats couching you the problem. try to push rom via adb
or maybe this one http://forum.xda-developers.com/showthread.php?t=2542219
i had no success with this rom, but...
it's beyond my knowledge
Click to expand...
Click to collapse
Every thing i flash even recovery doesnt seem to stick because when i fastboot twrp i still have my cmw.
Beukhof1 said:
Every thing i flash even recovery doesnt seem to stick because when i fastboot twrp i still have my cmw.
Click to expand...
Click to collapse
Few dayes ago i download Gb 4.4.2 rom and flash it with no mistakes thru the flash! It have no errors while flashing. After that had a update to 176.44.1
So my phone is for European market and with sparsechunk.0 sparsechunk.1 sparsechunk.2 have no errors. With 1.2.and 3sparsechunk i have errors, but i can but in the rom normally...
Then i use a mototool 3 and root my phone with twrp recovery...
Beukhof1 said:
Hi all,
My moto g has a problem. It is stuck at the "warning bootloader unlocked screen"
I can boot into fastboot and flash stuff but when i try to boot it keeps displaying the "warning bootloader unlocked screen"
i have tryed several guides to flash orignal firmware but somehow it doesnt work.
Stange thing is is that i have CMW installed but when i flash TWRP or something it says its ok but then when i go to recovery CMW always comes back.
Click to expand...
Click to collapse
Did you manage to get a fix for this? I have the exact same issue, did all the steps you mentioned and have not found a fix, did you hace any luck?
Iggyavendano said:
Did you manage to get a fix for this? I have the exact same issue, did all the steps you mentioned and have not found a fix, did you hace any luck?
Click to expand...
Click to collapse
Nope sorry man. Mine is stille dead. I think the flash memory is defectieve.
Beukhof1 said:
Nope sorry man. Mine is stille dead. I think the flash memory is defectieve.
Click to expand...
Click to collapse
I went back to my carrier rom and It worked... after a few flashes on lollipop I couldn't get it to work even on stock lollipop...
hope it helps.
Try with mfastboot-v2. You can find the link with a quick search. mfastboot may help with flashing larger system images than normal fastboot. Just give it a try.
And if you are on lollipop & trying to downgrade to kitkat, skip flashing motoboot.img & gpt.bin
legolas06 said:
Try with mfastboot-v2. You can find the link with a quick search. mfastboot may help with flashing larger system images than normal fastboot. Just give it a try.
And if you are on lollipop & trying to downgrade to kitkat, skip flashing motoboot.img & gpt.bin
Click to expand...
Click to collapse
I had the same problem, and tried everithing said here, the only thing that worked, was mfastboot - v2, thank a lot for the sugestion.
Device not seen
I'm having the same problem – stuck on "Warning Booloader Unlocked" screen. Can't get to the bootloader screen. 'adb devices' and 'mfastboot devices' both show empty device lists, which means that I can't execute any adb or mfastboot commands...
Moto G XT1032 (Gen 1, 2013), attempted to install 5.1 firmware using steps at www . droidviews . com/restore-moto-g-to-stock-and-downgrade-firmware (sorry, not allowed to add live link). Bootloader unlocked, USB drivers installed, USB debugging enabled. All mfastboot steps executed without error, but I missed sparsechunk.0 – duh. Finished with a 'mfastboot reboot', and ever since, can't get past the bootloader warning, and no device seen by adb or mfastboot... Can't imagine it's a connectivity or PC driver issue, as was working fine minutes ago before the reboot.
All the solutions I've found depend on adb or mfastboot being able to see my device. Any tips to get the device seen again?
Thanks!
aussiejim said:
I'm having the same problem – stuck on "Warning Booloader Unlocked" screen. Can't get to the bootloader screen. 'adb devices' and 'mfastboot devices' both show empty device lists, which means that I can't execute any adb or mfastboot commands...
Moto G XT1032 (Gen 1, 2013), attempted to install 5.1 firmware using steps at www . droidviews . com/restore-moto-g-to-stock-and-downgrade-firmware (sorry, not allowed to add live link). Bootloader unlocked, USB drivers installed, USB debugging enabled. All mfastboot steps executed without error, but I missed sparsechunk.0 – duh. Finished with a 'mfastboot reboot', and ever since, can't get past the bootloader warning, and no device seen by adb or mfastboot... Can't imagine it's a connectivity or PC driver issue, as was working fine minutes ago before the reboot.
All the solutions I've found depend on adb or mfastboot being able to see my device. Any tips to get the device seen again?
Thanks!
Click to expand...
Click to collapse
Problem solved – eventually got into bootloader screen on phone, after at least 20 tries... If you have same problem, keep on trying.
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?
I did all the set and get my unlock code from HTCdev. Tried all but never UNLOCKED the bootloader !
D:\--- MOBILE\Android\android\platform-tools>fastboot flash unlocktoken Unlock_c
ode.bin
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.144s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.152s
Click to expand...
Click to collapse
The phone has a problem it start with Logo HTC then Logo Of operator then it OFF screen.
You still need to run fastboot oem unlock. That just flashes the key.
shinji257 said:
You still need to run fastboot oem unlock. That just flashes the key.
Click to expand...
Click to collapse
I tried but STIll not wotrking
D:\--- MOBILE\Android\android\platform-tools>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.003s]
finished. total time: 0.004s
Click to expand...
Click to collapse
Hello,
I need help to unbrick my phone please,
After trying to back to stock i got stuck while dload method with BLL-L22C636B150 (android 6.0) Firmware after flashing RollbackPackage from same firmware (android 7.0 to 6.0)
My phone's screen is now only black, no boot logo anymore or recovery.
It's only show connected fastboot while plug in, i can only reboot to fastboot.
PS C:\adb> fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.006s
PS C:\adb> fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NRD90M test-keys
finished. total time: 0.005s
PS C:\adb> fastboot oem get-product-model
...
(bootloader) HUAWEI BLL-L22
OKAY [ 0.007s]
finished. total time: 0.008s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/spcseas
finished. total time: 0.005s
PS C:\adb> fastboot oem get-psid
...
(bootloader) SN:YCP7XXXX
(bootloader) IMEI:8646XXXX
(bootloader) IMEI1:8646XXXX
What can i do please ?
Try team mt tool for unbrick provide file from marshmallow update.app
siddhrsh said:
Try team mt tool for unbrick provide file from marshmallow update.app
Click to expand...
Click to collapse
13:00:27: All images are found, everything is ready for the unbricking process.
13:00:29: Unbricking started. Your computer may freezes during the process.
13:00:29: flash boot "C:\adb\348\boot.img"
13:00:31: The Boot image is flashing successfully
13:00:31: flash system "C:\adb\348\system.img"
13:03:26: The System image is flashing successfully
13:03:26: flash cust "C:\adb\348\cust.img"
13:03:49: target reported max download size of 471859200 bytes
sending sparse 'cust' 1/2 (458414 KB)...
OKAY [ 13.115s]
writing 'cust' 1/2...
OKAY [ 3.142s]
sending sparse 'cust' 2/2 (4100 KB)...
OKAY [ 0.109s]
writing 'cust' 2/2...
OKAY [ 0.035s]
finished. total time: 16.401s
13:03:49: Error#1
13:03:49: flash recovery "C:\adb\348\recovery.img"
13:03:51: The Recovery image is flashing successfully
13:03:51: Completed
13:03:51: Something went wrong (((
Still black screen rebooting only on fastboot mode
Demodark said:
13:00:27: All images are found, everything is ready for the unbricking process.
13:00:29: Unbricking started. Your computer may freezes during the process.
13:00:29: flash boot "C:\adb\348\boot.img"
13:00:31: The Boot image is flashing successfully
13:00:31: flash system "C:\adb\348\system.img"
13:03:26: The System image is flashing successfully
13:03:26: flash cust "C:\adb\348\cust.img"
13:03:49: target reported max download size of 471859200 bytes
sending sparse 'cust' 1/2 (458414 KB)...
OKAY [ 13.115s]
writing 'cust' 1/2...
OKAY [ 3.142s]
sending sparse 'cust' 2/2 (4100 KB)...
OKAY [ 0.109s]
writing 'cust' 2/2...
OKAY [ 0.035s]
finished. total time: 16.401s
13:03:49: Error#1
13:03:49: flash recovery "C:\adb\348\recovery.img"
13:03:51: The Recovery image is flashing successfully
13:03:51: Completed
13:03:51: Something went wrong (((
Still black screen rebooting only on fastboot mode
Click to expand...
Click to collapse
Did you flash marshmallow files
Images
Yes i tried to unbrick with : Huawei_GR5_2017_BLL-22_C636B150_South_East_Asia_6.0.zip
17:49:30: All images are found, everything is ready for the unbricking process.
17:49:32: Unbricking started. Your computer may freezes during the process.
17:49:32: flash boot "C:\adb\B150\boot.img"
17:49:34: The Boot image is flashing successfully
17:49:34: flash system "C:\adb\B150\system.img"
17:52:03: The System image is flashing successfully
17:52:03: flash cust "C:\adb\B150\cust.img"
17:52:26: target reported max download size of 471859200 bytes
sending sparse 'cust' 1/2 (458414 KB)...
OKAY [ 12.833s]
writing 'cust' 1/2...
OKAY [ 3.181s]
sending sparse 'cust' 2/2 (4100 KB)...
OKAY [ 0.114s]
writing 'cust' 2/2...
OKAY [ 0.045s]
finished. total time: 16.173s
17:52:26: Error#1
17:52:26: flash recovery "C:\adb\B150\recovery.img"
17:52:29: The Recovery image is flashing successfully
17:52:29: flash userdata "C:\adb\B150\userdata.img"
17:52:36: target reported max download size of 471859200 bytes
sending 'userdata' (143361 KB)...
OKAY [ 3.784s]
writing 'userdata'...
OKAY [ 1.013s]
finished. total time: 4.797s
17:52:36: Error#1
17:52:36: Completed
17:52:36: Something went wrong (((
Huawei Multi-Tool by Team MT v. 8.0.3.1 beta
I dont know wich one i can try now ?
http://pro-teammt.ru/firmware-database/?firmware_model=bll-l22&firmware_page=0
Black Screen
I tried to unbrick with update.zip (full OTA B150 version) script said all done without bug, but still black screen (no light) stuck in fastboot mode.
Demodark said:
I tried to unbrick with update.zip (full OTA B150 version) script said all done without bug, but still black screen (no light) stuck in fastboot mode.
Click to expand...
Click to collapse
Just flash the small data file via dload method.it should be 700-800 MB i guess. Once flashed, reboot to stock recovery and factory reset and boot
shashank1320 said:
Just flash the small data file via dload method.it should be 700-800 MB i guess. Once flashed, reboot to stock recovery and factory reset and boot
Click to expand...
Click to collapse
What is "the small data file" please ?
PS C:\adb> fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.007s
PS C:\adb> fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NRD90M test-keys
finished. total time: 0.005s
PS C:\adb> fastboot oem get-product-model
...
(bootloader) HUAWEI BLL-L22
OKAY [ 0.006s]
finished. total time: 0.006s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/spcseas
finished. total time: 0.006s
PS C:\adb> fastboot oem get-psid
...
(bootloader) SN:YCP7N17609000963
(bootloader) IMEI:864646034450028
(bootloader) IMEI1:864646034717855
OKAY [ 0.005s]
finished. total time: 0.005s
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.009s
PS C:\adb>
Demodark said:
What is "the small data file" please ?
Click to expand...
Click to collapse
Let me check the firmware and get the link for you
shashank1320 said:
Let me check the firmware and get the link for you
Click to expand...
Click to collapse
News ?
Demodark said:
News ?
Click to expand...
Click to collapse
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v74004/f1/full/hw/spcseas/
Unzip and see if there is update.app file in it, if so, dload it and it should be fine
shashank1320 said:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v74004/f1/full/hw/spcseas/
Unzip and see if there is update.app file in it, if so, dload it and it should be fine
Click to expand...
Click to collapse
Link is dead.
Demodark said:
Link is dead.
Click to expand...
Click to collapse
Let me recheck
What can i do ?
Always black screen, but phone detected as fastboot mode, reboot only leads to fastboot mode.
have you tried unlocking again your bootloader? updating or rollbacking of EMUI makes your bootloader locked by default.
try to unlock it first and flash your OS
if you want to use the dload way. try flashing the stock recovery after unlocking your bootloader.
Demodark said:
Link is dead.
Click to expand...
Click to collapse
K.. But after that how reset the DNS to its original state