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
Related
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,
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.
First of all, I'm german, so sorry if something's wrong with my English
Hey I've got a Nexus 5 laying around (I don't use it) and it is bootlooping. I would like to fix it but nothing works.
1. Power button isn't stuck (checked it)
2. I can boot into the bootloader
3. fastboot works fine
4. Can't get into Recovery ( when I boot into Recovery the Google Logo comes up and it keeps restarting)
5. Flashing a fresh Android doesn't work
6. Flashing a custom Recovery doesn't work
7. I don't know anything about the phone (I just got it because i wanted the display for my other Nexus 5)
8. bootloader is unlocked
I have fastboot and adb on a Windows and a Linux machine. Thanks for your help
Your English is perfect (apart from the lower case on "German" ) - if you hadn't started with that sentence I would never have known.
At the risk of boring people who may have already seen this post in other threads, see if this advice helps at all. If you have a working bootloader screen it may work. You can ignore the first sentence about backup, since in your situation it's redundant.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/images#hammerhead) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Didn't work...
Here's my output:
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash bootloader bootloader.img
target didn't report max-download-size
sending 'bootloader' (2506 KB)...
OKAY [ 0.219s]
writing 'bootloader'...
OKAY [ 0.453s]
finished. total time: 0.688s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.094s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash radio radio.img
target didn't report max-download-size
sending 'radio' (42033 KB)...
OKAY [ 1.422s]
writing 'radio'...
OKAY [ 2.891s]
finished. total time: 4.313s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.109s]
finished. total time: 0.109s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 1.109s]
finished. total time: 1.109s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash system system.img
target didn't report max-download-size
erasing 'system'...
OKAY [ 0.516s]
sending 'system' (692940 KB)...
OKAY [ 21.893s]
writing 'system'...
OKAY [ 46.692s]
finished. total time: 69.132s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot erase boot
erasing 'boot'...
OKAY [ 0.234s]
finished. total time: 0.234s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (8620 KB)...
OKAY [ 0.484s]
writing 'boot'...
OKAY [ 0.734s]
finished. total time: 1.234s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.500s]
finished. total time: 0.500s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash cache cache.img
target didn't report max-download-size
erasing 'cache'...
OKAY [ 0.484s]
sending 'cache' (13348 KB)...
OKAY [ 0.625s]
writing 'cache'...
OKAY [ 1.063s]
finished. total time: 2.188s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.094s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (14626 KB)...
OKAY [ 0.672s]
writing 'recovery'...
OKAY [ 1.125s]
finished. total time: 1.797s
C:\Users\Paul\Downloads\hammerhead-krt16m>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.109s]
finished. total time: 0.109s
When i boot to recovery the google logo appears and still restarts all the time.
As i said, i've already tried flashing a custom recovery and Android before... Didn't work for me..
Sorry to hear that. I've never seen the "target didn't report" message. Maybe a hardware problem?
I thinks it's a hardware failure. I found somebody else having this problem on the google forum. They say the flash storage is demaged. Not repairable. But thanks for the quick reply.
Budden6800i said:
I thinks it's a hardware failure. I found somebody else having this problem on the google forum. They say the flash storage is demaged. Not repairable. But thanks for the quick reply.
Click to expand...
Click to collapse
Why you are using krt16m image? It's old...
Please download M4B30Z and try again...
Moto E (4th Gen) xt1766 Sperry
Stock Android 7.1.1 Firmware
Fastboot Restoration Guide
IMPORTANT NOTICE:
Because there are reports of devices becoming bricked due to downgrading, please disregard this thread and firmware. This is a link to the newly added factory firmware package for the most current build version for the xt1766 SPerry. Please go here:
https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
DISCLAIMER: Please take note that the following stock firmware package is not the official Motorola firmware package, nor is it signed by Motorola. This is a package I have compiled with partition dumps from a pure stock & unmodified Android OS. I have tested this procedure, as have other members, and no adverse issues have arisen upon installing the firmware. However, I am not responsible for devices bricked or otherwise rendered inoperable as a result of installing this firmware or using this guide. You and you alone are responsible for your device. Because this guide does involve fastboot flashing bootloader and other sensitive partitions, follow the instructions to the letter. One mishap while flashing a bootloader partition can leave a device fully inoperable. Also, I have only used this guide on Virgin Mobile variants of the xt1766. It should work on the Sprint and Boost Mobile variants as well, but I cannot personally confirm that at this time.
SPECIFICATIONS:
Hardware SKU: xt1766
Carrier/Provider: Sprint, Virgin Mobile, Boost Mobile
Android Version: 7.1.1 Nougat
Build No. NCQ26.69-64
Radio: M8920_15000.280.06.58.02R
Kernel Version: 3.18.31
Security Patch Level: January 1, 2018
NOTES: This firmware is the most recent version of the stock Android OS. It is completely unmodified.
REQUIREMENTS:
--An unlocked bootloader;
--A PC or laptop running Windows 7 or later;
--Motorola Device Manager: https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222;
--Minimal ADB & Fastboot (v1.4.3 or later): https://drive.google.com/file/d/0B1Sfod4HWfk2T0hia0k3Y3pIczA/view?usp=drivesdk;;
--Rudimentary knowledge of fastboot flashing;
--Device charged to at least 60%.
INSTRUCTIONS:
Download the stock firmware package from the link below and save the files in your ADB/Fastboot directory on your PC. Boot your device into fastboot/bootloader mode and connect your device and PC with a suitable data sync cable. Open a command window within the ADB/Fastboot directory and execute the following set of commands:
NOTE: The larger image files (system.img & oem.img) will be automatically dissected into individual sparsechunks and incrementally flashed by fastboot. You will initially receive a "header size" error, but just be patient and wait. Fastboot will resolve this and flash the images.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash aboot aboot.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash dsp dsp.img
fastboot flash modem modem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.img
fastboot flash keymaster keymaster.mbn
fastboot flash oem oem.img
fastboot flash prov prov.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot erase system
fastboot flash system system.img
fastboot erase DDR
fastboot erase userdata
fastboot erase cache
fastboot oem fb_mode_clear
Now boot your device normally. You should now be updated to the most recent pure stock Android build, and your device will be fully capable of installing future OTA updates.
DOWNLOAD LINK:
LINK HAS BEEN REMOVED: Please go here: https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
this is useful. :good:
but please it would be more good if you move this to the Qualcomm section, because seems you posted it in the MediaTek section.
Please do move it so other users don't come wondering what to do and bricking their devices.
iykeDROID™ said:
this is useful. :good:
but please it would be more good if you move this to the Qualcomm section, because seems you posted it in the MediaTek section.
Please do move it so other users don't come wondering what to do and bricking their devices.
Click to expand...
Click to collapse
Yes I see your point. My bad. How can I move this over? Do I need to contact a moderator to get it moved? Thanks much for pointing that out. :good:
MotoJunkie01 said:
Yes I see your point. My bad. How can I move this over? Do I need to contact a moderator to get it moved? Thanks much for pointing that out. :good:
Click to expand...
Click to collapse
yes, you would need a moderators assistance to get it moved. maybe `Az Biker` will help... https://forum.xda-developers.com/member.php?u=4670411
iykeDROID™ said:
yes, you would need a moderators assistance to get it moved. maybe `Az Biker` will help... https://forum.xda-developers.com/member.php?u=4670411
Click to expand...
Click to collapse
Thank you. I sent the thread link and a PM to Az Biker.
Update: The Sperry xt1766 received an OTA update today for minor bug fixes, stability improvements, and security patches for March 1, 2018. The OTA is Bkur_Version 26.11.68.sperry_sprint.en.US. I will be updating this thread to the new build updated by the OTA. In the meantime, should you wish to revert to pure stock and install the OTA update package, the above fastboot firmware package will put your xt1766 in a pure stock state, and thus capable of installing the OTA update. NOTE: Many people skip recovery.img in order to retain TWRP custom recovery. Here, flashing stock recovery is necessary in order to successfully install the OTA update package.
iykeDROID™ said:
yes, you would need a moderators assistance to get it moved. maybe `Az Biker` will help... https://forum.xda-developers.com/member.php?u=4670411
Click to expand...
Click to collapse
Hey friend, thanks again for pointing out my oversight. Moderator Az Biker helped me out and moved the thread.
Ok guys, on a positive note, I just successfully flashed a modified OTA update package with TWRP. I think I figured out the bug that was giving me Error 7 previously. So I am working on both recent OTA packages, for patch level January 1, 2018 and March 1, 2018. Hopefully now I can get these fixed and posted and make for a simple means to update stock firmware, without having to gruel out 25 fastboot commands and without having to download large files. Wish me luck. I thank you all for your support and encouragement.
MotoJunkie01 said:
Ok guys, on a positive note, I just successfully flashed a modified OTA update package with TWRP. I think I figured out the bug that was giving me Error 7 previously. So I am working on both recent OTA packages, for patch level January 1, 2018 and March 1, 2018. Hopefully now I can get these fixed and posted and make for a simple means to update stock firmware, without having to gruel out 25 fastboot commands and without having to download large files. Wish me luck. I thank you all for your support and encouragement.
Click to expand...
Click to collapse
Rock on bro! Good luck.
Hard brick
My device is bricked flashing update on custom rom AICP
Please help
---------- Post added at 08:42 AM ---------- Previous post was at 08:40 AM ----------
Hard brick
My device is bricked flashing update on custom rom AICP
Please help
Restore in emergency mode
Greetings.
I would like your help to restore a MOTO E4 XT1766. It does not start with fastboot, because the bootloader is corrupt. The phone connects in emergency mode. I need the file "prog_emmc_firehose_8920.mbn" to be able to restore it. Any idea where I can find it?
error cannot load gpt.bin
I have my phone in fastboot/bootloader mode. Should I be in recovery? I can run the command "fastboot oem fb_mode_set" but I cant run the command "fastboot flash partition gpt.bin" I get "error cannot load gpt.bin". Moto E4 XT1766 Qualcomm any help?
Edit: I am sure I have the files in the same folder as adb and fastboot.
UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry bricked my phone
Hey,
I flashed my phone using the zip from the "UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry" thread and bricked my phone.
Won't even power on and is not recognized by adb/fastboot. "waiting for device"
Is there anyway of unbricking it.
Tried holding the down+power button for 10 seconds
Tried holding the up+power button for 10 seconds.
Charging it for 10 minutes and holding the power button for 10 seconds.
Removed battery and reinserted holding for 10 seconds and plug it in my laptop.
Nothing.
Please help if you can, is there another trick I can do.
[email protected] said:
Hey,
I flashed my phone using the zip from the "UPDATE][XT1766] Partition Index & Bootloader Updater for SPerry" thread and bricked my phone.
Won't even power on and is not recognized by adb/fastboot. "waiting for device"
Is there anyway of unbricking it.
Tried holding the down+power button for 10 seconds
Tried holding the up+power button for 10 seconds.
Charging it for 10 minutes and holding the power button for 10 seconds.
Removed battery and reinserted holding for 10 seconds and plug it in my laptop.
Nothing.
Please help if you can, is there another trick I can do.
Click to expand...
Click to collapse
Nope its dead u flash bootloader partitions that were older then your current version that edl'd you're phone
MotoJunkie01 said:
Moto E (4th Gen) xt1766 Sperry
Stock Android 7.1.1 Firmware
Fastboot Restoration Guide
Click to expand...
Click to collapse
Thanks man, worked perfectly.
Got some errors along the way, which I ignored (permissions on Erase Data, etc).
MotoJunkie01 said:
Moto E (4th Gen) xt1766 Sperry
Stock Android 7.1.1 Firmware
Fastboot Restoration Guide
Click to expand...
Click to collapse
After successfully using this method, a few days later I was prompted to install May Security Update NCQS26.69-64-5.
I said ok, it downloaded and prompted me to restart. I did.
I rebooted into the initial boot screen, with "bad key" text.
Then it proceeded to "Installing system update"
Then came the Android on his back, with the error! (red exclamation)
Had to power off/on. It restarted and then showed the screen "Software Update Unsuccessful"
Any idea on how I could successfully install the may update?
Thanks!
mike
resarfekim said:
After successfully using this method, a few days later I was prompted to install May Security Update NCQS26.69-64-5.
I said ok, it downloaded and prompted me to restart. I did.
I rebooted into the initial boot screen, with "bad key" text.
Then it proceeded to "Installing system update"
Then came the Android on his back, with the error! (red exclamation)
Had to power off/on. It restarted and then showed the screen "Software Update Unsuccessful"
Any idea on how I could successfully install the may update?
Thanks!
mike
Click to expand...
Click to collapse
The bad key is just because the bootloader is unlocked. No big deal. Not sure why the ota failed. I just flash the firmware with rsdlite. Just downloaded the latest firmware available, which was not May's patch, then took the update after I booted up and set up the device. What carrier are you on? Mine is virgin mobile, same as op.
Check in "about phone" and see which software version you're on. My wife's failed once, but when I checked, it had updated.
madbat99 said:
The bad key is just because the bootloader is unlocked. No big deal. Not sure why the ota failed. I just flash the firmware with rsdlite. Just downloaded the latest firmware available, which was not May's patch, then took the update after I booted up and set up the device. What carrier are you on? Mine is virgin mobile, same as op.
Check in "about phone" and see which software version you're on. My wife's failed once, but when I checked, it had updated.
Click to expand...
Click to collapse
Thanks for the reply.
I am currently on the March 1 Security Patch, NCQS26.69-64-2
On Sprint network.
I can't figure out how to create a screenshot with this phone, but here is the link from the Update popup: https://support.motorola.com/us/en/solution/MS128968
resarfekim said:
Thanks for the reply.
I am currently on the March 1 Security Patch, NCQS26.69-64-2
On Sprint network.
I can't figure out how to create a screenshot with this phone, but here is the link from the Update popup: https://support.motorola.com/us/en/solution/MS128968
Click to expand...
Click to collapse
Screenshot is just like any vanilla Android device. Power + volume down.
Did you root or modify the system in any way? That will cause an ota to fail.
madbat99 said:
Screenshot is just like any vanilla Android device. Power + volume down.
Did you root or modify the system in any way? That will cause an ota to fail.
Click to expand...
Click to collapse
I was originally rooted, but after running the commands in this OP, I did nothing else.
I did save the results of all the Fastboot commands, please see below. A couple commands toward the end gave errors.
______________________________________________
E:\Phone\E4\Factory_restore_image>fastboot devices
ZY224PTXGW fastboot
E:\Phone\E4\Factory_restore_image> fastboot oem fb_mode_set
...
OKAY [ 0.016s]
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.125s]
finished. total time: 0.140s
E:\Phone\E4\Factory_restore_image>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.515s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.655s]
finished. total time: 1.186s
E:\Phone\E4\Factory_restore_image> fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.531s]
writing 'recovery'...
(bootloader) Image signed with key bad key
OKAY [ 1.970s]
finished. total time: 2.517s
E:\Phone\E4\Factory_restore_image> fastboot flash aboot aboot.mbn
(bootloader) has-slot:aboot: not found
target reported max download size of 536870912 bytes
sending 'aboot' (1536 KB)...
OKAY [ 0.047s]
writing 'aboot'...
OKAY [ 0.203s]
finished. total time: 0.265s
E:\Phone\E4\Factory_restore_image>fastboot flash cmnlib cmnlib.mbn
(bootloader) has-slot:cmnlib: not found
target reported max download size of 536870912 bytes
sending 'cmnlib' (251 KB)...
OKAY [ 0.001s]
writing 'cmnlib'...
OKAY [ 0.078s]
finished. total time: 0.079s
E:\Phone\E4\Factory_restore_image>fastboot flash cmnlib64 cmnlib64.mbn
(bootloader) has-slot:cmnlib64: not found
target reported max download size of 536870912 bytes
sending 'cmnlib64' (251 KB)...
OKAY [ 0.016s]
writing 'cmnlib64'...
OKAY [ 0.078s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image>fastboot flash devcfg devcfg.mbn
(bootloader) has-slot:devcfg: not found
target reported max download size of 536870912 bytes
sending 'devcfg' (128 KB)...
OKAY [ 0.016s]
writing 'devcfg'...
OKAY [ 0.062s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image> fastboot flash dsp dsp.img
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.531s]
writing 'dsp'...
OKAY [ 1.686s]
finished. total time: 2.217s
E:\Phone\E4\Factory_restore_image>fastboot flash modem modem.img
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (102400 KB)...
OKAY [ 3.247s]
writing 'modem'...
OKAY [ 4.921s]
finished. total time: 8.168s
E:\Phone\E4\Factory_restore_image>fastboot erase modemst1
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
OKAY [ 0.062s]
finished. total time: 0.062s
E:\Phone\E4\Factory_restore_image>fastboot erase modemst2
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
OKAY [ 0.062s]
finished. total time: 0.062s
E:\Phone\E4\Factory_restore_image> fastboot flash fsg fsg.img
(bootloader) has-slot:fsg: not found
target reported max download size of 536870912 bytes
sending 'fsg' (8192 KB)...
OKAY [ 0.266s]
writing 'fsg'...
OKAY [ 2.795s]
finished. total time: 3.062s
E:\Phone\E4\Factory_restore_image>fastboot flash keymaster keymaster.mbn
(bootloader) has-slot:keymaster: not found
target reported max download size of 536870912 bytes
sending 'keymaster' (251 KB)...
OKAY [ 0.016s]
writing 'keymaster'...
OKAY [ 0.078s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image>fastboot flash oem oem.img
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'oem' 1/2 (507490 KB)...
OKAY [ 17.457s]
writing 'oem' 1/2...
OKAY [ 28.001s]
sending sparse 'oem' 2/2 (59511 KB)...
OKAY [ 2.081s]
writing 'oem' 2/2...
OKAY [ 6.231s]
finished. total time: 53.804s
E:\Phone\E4\Factory_restore_image> fastboot flash prov prov.mbn
(bootloader) has-slotrov: not found
target reported max download size of 536870912 bytes
sending 'prov' (187 KB)...
OKAY [ 0.016s]
writing 'prov'...
OKAY [ 0.062s]
finished. total time: 0.078s
E:\Phone\E4\Factory_restore_image>fastboot flash rpm rpm.mbn
(bootloader) has-slot:rpm: not found
target reported max download size of 536870912 bytes
sending 'rpm' (256 KB)...
OKAY [ 0.016s]
writing 'rpm'...
OKAY [ 0.078s]
finished. total time: 0.094s
E:\Phone\E4\Factory_restore_image>fastboot flash sbl1 sbl1.mbn
(bootloader) has-slot:sbl1: not found
target reported max download size of 536870912 bytes
sending 'sbl1' (507 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
OKAY [ 0.047s]
finished. total time: 0.078s
E:\Phone\E4\Factory_restore_image> fastboot flash tz tz.mbn
(bootloader) has-slot:tz: not found
target reported max download size of 536870912 bytes
sending 'tz' (1792 KB)...
OKAY [ 0.062s]
writing 'tz'...
OKAY [ 0.265s]
finished. total time: 0.328s
E:\Phone\E4\Factory_restore_image>fastboot erase system
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>fastboot erase system
(bootloader) has-slot:system: not found
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image> fastboot flash system system.img
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/5 (509553 KB)...
OKAY [ 17.319s]
writing 'system' 1/5...
OKAY [ 12.350s]
sending sparse 'system' 2/5 (523636 KB)...
OKAY [ 17.753s]
writing 'system' 2/5...
OKAY [ 11.928s]
sending sparse 'system' 3/5 (519086 KB)...
OKAY [ 17.869s]
writing 'system' 3/5...
OKAY [ 11.983s]
sending sparse 'system' 4/5 (521399 KB)...
OKAY [ 17.949s]
writing 'system' 4/5...
OKAY [ 20.356s]
sending sparse 'system' 5/5 (411602 KB)...
OKAY [ 14.302s]
writing 'system' 5/5...
OKAY [ 35.077s]
finished. total time: 176.895s
E:\Phone\E4\Factory_restore_image> fastboot erase DDR
(bootloader) has-slotDR: not found
erasing 'DDR'...
OKAY [ 0.000s]
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 1.267s]
finished. total time: 1.267s
E:\Phone\E4\Factory_restore_image>fastboot erase cache
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
E:\Phone\E4\Factory_restore_image> fastboot oem fb_mode_clear
...
OKAY [ 0.016s]
finished. total time: 0.016s
E:\Phone\E4\Factory_restore_image>
My story goes.
Had happy running TugaPower Rom
Decided to install MultiRom and Ubuntu.
Then after running for a week or so, decided to wipe and install TugaPower alone.
All has run well for a while. Decided to wipe and make a fresh install.
MultiRom I am unable to fully remove, even trying to replace with original TWRP.
When I try to flash the ROM, I get reported that this cant be installed as the model is . not bacon or A0001. error 7
I have edited the updater-script to not make a check on the model and it then installs.
When i reboot it goes straight back to the recovery!!!
I have tried reinstalling multirom and then flashing but again it keeps going to the recovery.
Ive tried to fastboot the original OS via https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541, but fastboot reports `FAILED (remote: Device not unlocked cannot flash or erase)`
(Full output at bottom)
The install all end with 1 and multirom could see the roms
ive tried extracting just the .img and flashing to get going
im at a loss, any help much appreciated
Code:
[email protected]:sudo fastboot oem unlock
...
OKAY [ 0.009s]
finished. total time: 0.009s
[email protected]:/home/steve/Downloads/cm# ./flash-all.sh
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 1.805s]
writing 'modem'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 1.806s
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.011s]
writing 'sbl1'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.013s
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.004s]
writing 'dbi'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.006s
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.015s]
writing 'aboot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.017s
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.008s]
writing 'rpm'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.010s
target reported max download size of 1073741824 bytes
sending 'tz' (325 KB)...
OKAY [ 0.012s]
writing 'tz'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.015s
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.013s]
writing 'LOGO'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.015s
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.322s]
writing 'oppostanvbk'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.323s
target reported max download size of 1073741824 bytes
sending 'recovery' (9968 KB)...
OKAY [ 0.314s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.315s
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.000s
target reported max download size of 1073741824 bytes
sending 'boot' (7274 KB)...
OKAY [ 0.231s]
writing 'boot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.232s
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.000s
target reported max download size of 1073741824 bytes
erasing 'userdata'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.000s
rebooting...
finished. total time: 0.050s
Boot the phone into fastboot mode and open cmd with administrative rights and go into the adb platform tools folder and enter in cmd fastboot OEM -device info
kallum7 said:
Boot the phone into fastboot mode and open cmd with administrative rights and go into the adb platform tools folder and enter in cmd fastboot OEM -device info
Click to expand...
Click to collapse
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.016s]
finished. total time: 0.016s
now run script
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Windows\system32>fastboot boot C:\Users\Steve\Downloads\twrp-3.2.3-0-bacon.img
downloading 'boot.img'...
OKAY [ 0.438s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.438s
C:\Windows\system32>fastboot oem unlock
...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Windows\system32>fastboot boot C:\Users\Steve\Downloads\twrp-3.2.3-0-bacon.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.438s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.438s
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.016s]
finished. total time: 0.016s
Try another USB micro cable
Thank you for your reply.
I have tried two other cables I have and still having the same issues
Are you using Linux or windows
kallum7 said:
Are you using Linux or windows
Click to expand...
Click to collapse
I have both available,
I am trying each OS at each new try
Ran all three of the files on here to get the triggers to true / true
https://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
I then ran `fastboot boot twrp.img`
This gave me twrp and i then installed a rom as normal...
im back up and running
thanks for all your patience and help
stevieag said:
Ran all three of the files on here to get the triggers to true / true
https://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
I then ran `fastboot boot twrp.img`
This gave me twrp and i then installed a rom as normal...
im back up and running
thanks for all your patience and help
Click to expand...
Click to collapse
Im having problems again..
OTA lineage update came up..
i clicked to install.
Phone restarted and immediately went to the multirom twrp screen.
I have had this in the past and have needed to install from this screen but i couldnt find the file to install
So on phone restart it loops back to the multirom twrp
I can still adb and fastboot see below
Code:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
on fastboot boot twrp.img
it seems to restart but sits on fastboot screen
story:
on fastboot
send command
fastboot screen goes brighter
Any ideas
I have tried windows and linux plus 2 cables
What would be ideal would to completely clear multirom from my phone and get back to stock or stock twrp so i can flash as normal
stevieag said:
Im having problems again..
OTA lineage update came up..
i clicked to install.
Phone restarted and immediately went to the multirom twrp screen.
I have had this in the past and have needed to install from this screen but i couldnt find the file to install
So on phone restart it loops back to the multirom twrp
I can still adb and fastboot see below
Code:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
on fastboot boot twrp.img
it seems to restart but sits on fastboot screen
story:
on fastboot
send command
fastboot screen goes brighter
Any ideas
I have tried windows and linux plus 2 cables
What would be ideal would to completely clear multirom from my phone and get back to stock or stock twrp so i can flash as normal
Click to expand...
Click to collapse
sorted
https://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Ultimate fix
Right, i ended with a boot loop i couldnt sort
so
i downloaded - cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot.zip (to big for upload)
This contains all the files you need including os
Once in fastboot
volume up and power or in recovery
Code:
adb reboot bootloader
In windows in a terminal (search next to start menu for cmd, right click on the pop up cmd and choose open as admin)
Run each of these
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64G.img
fastboot reboot
THIS IS FOR 64GB ONLY with 16GB change userdata_64.img to the file userdata.img
In Linux open terminal, drop to root
Code:
sudo su -
you can then run above files or run flash-radio.sh
Code:
./flash-radio.sh
weirly may still need sudo!!!
This will install the os etc and you are back to stock (although old)
Now you can install twrp as normal
Code:
fastboot flash recovery twrp.img
Code:
fastboot reboot
here you should be back to normal twrp recovery
Copy over your ROM and Gapps
Install as normal twrp and done
im now on pie with 3.2.2 twrp and gapps 9
This installed ROMs that were complaining of not the right model, error 7, error 255 ........ and on
All sorted, in fact ive installed 3 different roms now without fails