Database Info

downgrade problems

hi guys i have ran into some problems on my MOTO G Basically im not sure what happend i was running stock 4.3 rooted, and it bootlooped randomly. me being the idiot as i am factory reset it from recovery, wiped cache etc.. but i also formatted the system in a moment of madness and have now lost my back ups.
so i tried to upgrade to 4.2.2 using cmd prompts & also tried restoring the stock firmware ( 4.3) using cmd prompts all goes well untill it reaches the system.img this is what happens
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Dan>cd C:\
C:\>flashall.bat /eu
Motorola Mobility flashall script version 1.4
Flashing Options:
- flash persist: 0
- flash userdata: 0
- erase userdata: 1
- erase cache: 0
Waiting for fastboot enumeration...
Fastboot device is ready!!
Flashing GPT and bootloader images...
Executing ".\Windows\fastboot.exe flash partition gpt.b
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.438s]
finished. total time: 0.469s
8226 HW detected...
Flashing motoboot
Executing ".\Windows\fastboot.exe flash motoboot motobo
target max-sparse-size: 256MB
sending 'motoboot' (1940 KB)...
OKAY [ 0.109s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.484s]
finished. total time: 1.594s
Flashing modem SW...
Executing ".\Windows\fastboot.exe flash modem NON-HLOS.
target max-sparse-size: 256MB
sending 'modem' (47484 KB)...
OKAY [ 2.094s]
writing 'modem'...
OKAY [ 1.250s]
finished. total time: 3.344s
Executing ".\Windows\fastboot.exe flash fsg fsg.mbn"
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.047s]
writing 'fsg'...
OKAY [ 0.094s]
finished. total time: 0.141s
Executing ".\Windows\fastboot.exe erase modemst1"
erasing 'modemst1'...
OKAY [ 0.016s]
finished. total time: 0.016s
Executing ".\Windows\fastboot.exe erase modemst2"
erasing 'modemst2'...
OKAY [ 0.047s]
finished. total time: 0.047s
Flashing AP Images...
Executing ".\Windows\fastboot.exe flash logo logo.bin"
target max-sparse-size: 256MB
sending 'logo' (619 KB)...
OKAY [ 0.062s]
writing 'logo'...
OKAY [ 0.094s]
finished. total time: 0.156s
Executing ".\Windows\fastboot.exe flash boot boot.img"
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.484s]
writing 'boot'...
OKAY [ 0.844s]
finished. total time: 1.328s
Executing ".\Windows\fastboot.exe flash recovery recove
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.484s]
writing 'recovery'...
OKAY [ 0.844s]
finished. total time: 1.328s
Executing ".\Windows\fastboot.exe flash system system.i
target max-sparse-size: 256MB
error: cannot load 'system.img': Unknown error
.\Windows\fastboot.exe flash system system.img failed!!
anybody have any solutions has my phone is a lying brick at the moment thankyou.

S.O.S

Hello guys, this is my first time being officially on the forum as a user, before I was just reading and viewing information, using some of it as well. The reason I post this thread is to see if anyone can help me out or point me in the right direction of an already existing thread for my issue.
My issue is the following. A week ago I was trying to flash a new rom and by accident I deleted the system part on the advanced option on the TWRP. After that when my phone turned on a weird line starting going up and down on the screen and the phone started to work really really slow. I asked a friend and he told me to just reflash the rom, which I did but the line and slowness still appeared after that even my WIFI stopped working (when I tried to turn it on it would turn itself off immediately) I read on a thread about a similar issue and they reinstalled the firmware of the phone and it worked. obviously I tried doing it myself, I replaced the firmware to my phone used an original copy and everything works fine, except the wifi, it still does not turn on.
Can anyone help me out? Has anyone ever hear of this issue before.
And to let you all know. Me cellphones model is Motorola Moto G TX1032
Any and I mean any assistance or information provided will be very helpful.
Thank you!!

Mr.Nomo said:
Hello guys, this is my first time being officially on the forum as a user, before I was just reading and viewing information, using some of it as well. The reason I post this thread is to see if anyone can help me out or point me in the right direction of an already existing thread for my issue.
My issue is the following. A week ago I was trying to flash a new rom and by accident I deleted the system part on the advanced option on the TWRP. After that when my phone turned on a weird line starting going up and down on the screen and the phone started to work really really slow. I asked a friend and he told me to just reflash the rom, which I did but the line and slowness still appeared after that even my WIFI stopped working (when I tried to turn it on it would turn itself off immediately) I read on a thread about a similar issue and they reinstalled the firmware of the phone and it worked. obviously I tried doing it myself, I replaced the firmware to my phone used an original copy and everything works fine, except the wifi, it still does not turn on.
Can anyone help me out? Has anyone ever hear of this issue before.
And to let you all know. Me cellphones model is Motorola Moto G TX1032
Any and I mean any assistance or information provided will be very helpful.
Thank you!!
Click to expand...
Click to collapse
Did you use a fastboot firmware image? If so what commands did you try?

Did u flash the modem,boot and radio correctly?

lost101 said:
Did you use a fastboot firmware image? If so what commands did you try?
Click to expand...
Click to collapse
What I used was "US_retail_XT1032_KXB21.14-L1.32_CFC.xml" its a zip file, I copied the contents on this to a folder where I had the adb tools and the commands I used where:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot

It's would be helpful if you could provide an actual log of using these commands. Fastboot is not user friendly, and it can be the case you think a command has been successful - when it has not.

Log
lost101 said:
It's would be helpful if you could provide an actual log of using these commands. Fastboot is not user friendly, and it can be the case you think a command has been successful - when it has not.
Click to expand...
Click to collapse
Here is the log of the command process, I had to switch commands and firmware because the rest were giving me more problems aside of the wifi, this is the brazilian firmware 5.0.2 :
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.025s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.370s]
finished. total time: 0.399s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot reboo
t-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.091s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.232s]
finished. total time: 1.326s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.036s]
writing 'logo'...
OKAY [ 0.084s]
finished. total time: 0.123s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.391s]
writing 'boot'...
OKAY [ 0.760s]
finished. total time: 1.156s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.372s]
writing 'recovery'...
OKAY [ 0.750s]
finished. total time: 1.125s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 8.454s]
writing 'system'...
OKAY [ 10.936s]
finished. total time: 19.394s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256754 KB)...
OKAY [ 8.456s]
writing 'system'...
OKAY [ 11.241s]
finished. total time: 19.701s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260090 KB)...
OKAY [ 8.573s]
writing 'system'...
OKAY [ 11.058s]
finished. total time: 19.642s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (165316 KB)...
OKAY [ 5.463s]
writing 'system'...
OKAY [ 7.930s]
finished. total time: 13.401s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.694s]
writing 'modem'...
OKAY [ 1.455s]
finished. total time: 3.154s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase
modemst1
erasing 'modemst1'...
OKAY [ 0.023s]
finished. total time: 0.025s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase
modemst2
erasing 'modemst2'...
OKAY [ 0.022s]
finished. total time: 0.024s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash
fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.072s]
writing 'fsg'...
OKAY [ 5.602s]
finished. total time: 5.679s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase
cache
erasing 'cache'...
OKAY [ 0.359s]
finished. total time: 0.361s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase
userdata
erasing 'userdata'...
OKAY [ 3.168s]
finished. total time: 3.172s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot reboo
t
rebooting...
finished. total time: 0.002s
C:\Users\J\Desktop\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>
Now this firmware works fine and all but I still have the issue with the wifi, I have been reading about replacing a file on the /persist folder, and I have done so multiple times, and the issue still remains

Could you try flashing the GPE 5.1 Firmware Image: http://forum.xda-developers.com/showpost.php?p=59930345&postcount=610
Skip the following command for your own safety: mfastboot flash motoboot motoboot.img

Same?
lost101 said:
Could you try flashing the GPE 5.1 Firmware Image: http://forum.xda-developers.com/showpost.php?p=59930345&postcount=610
Skip the following command for your own safety: mfastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
I did the process here is the log:
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.367s]
writing 'boot'...
OKAY [ 0.712s]
finished. total time: 1.092s
on device appeared: hab check failed for boot
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.384s]
writing 'recovery'...
OKAY [ 0.702s]
finished. total time: 1.092s
on device appeared: hab check failed for recovery
Complete log:
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t partition gpt.bin
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-P enable parallel loading for multi-fla
sh if
there is no enough memory on host to
load
whole image
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.028s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.318s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t reboot bootloader
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-P enable parallel loading for multi-fla
sh if
there is no enough memory on host to
load
whole image
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (76 KB)...
OKAY [ 0.032s]
writing 'logo'...
OKAY [ 0.081s]
finished. total time: 0.118s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.367s]
writing 'boot'...
OKAY [ 0.712s]
finished. total time: 1.092s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.384s]
writing 'recovery'...
OKAY [ 0.702s]
finished. total time: 1.092s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257288 KB)...
OKAY [ 8.507s]
writing 'system'...
OKAY [ 11.266s]
finished. total time: 19.776s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (260812 KB)...
OKAY [ 8.591s]
writing 'system'...
OKAY [ 10.560s]
finished. total time: 19.154s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 8.624s]
writing 'system'...
OKAY [ 12.751s]
finished. total time: 21.378s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (18680 KB)...
OKAY [ 0.693s]
writing 'system'...
OKAY [ 0.783s]
finished. total time: 1.482s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49368 KB)...
OKAY [ 1.677s]
writing 'modem'...
OKAY [ 1.292s]
finished. total time: 2.975s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t erase modemst1
erasing 'modemst1'...
OKAY [ 0.023s]
finished. total time: 0.025s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t erase modemst2
erasing 'modemst2'...
OKAY [ 0.022s]
finished. total time: 0.024s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (708 KB)...
OKAY [ 0.110s]
writing 'fsg'...
OKAY [ 5.614s]
finished. total time: 5.729s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t erase cache
erasing 'cache'...
OKAY [ 0.344s]
finished. total time: 0.345s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t erase userdata
erasing 'userdata'...
OKAY [ 2.976s]
finished. total time: 2.979s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>mfastboo
t reboot
rebooting...
finished. total time: 0.002s
C:\Users\J\Downloads\Moto G\Firmware\GPE_5.1_XT1032_LMY47M.M001_CFC.xml>
I also included what I believe are errors, if you call it like that which are detailed at the beginning. And now when I turn the wifi on, it turns "on" but no networks are recognized ( I have one at home ) and then when the screen locks or I go back, it will appear as off.

Update
After installing this firmware and installing a file explorer with root permission, I went to /persist to modify the WCNSS file, placing a 0 on it, afterwards tried the WIFI and got my hopes up because it recognized my WIFI and it even displayed a MAC Address which I copied. After trying to connect to my wifi...it stopped working and is back to square one.

@Mr.Nomo - I'll do some more research this evening. Is everything else working for you? Calls / data etc.
UPDATE: Sometimes flashing a CyanogenMOD based custom ROM can get WiFi working again. WiFi in XPerience ROM is different again and might be worth a try: http://forum.xda-developers.com/moto-g/orig-development/rom-xperience-9-0-0-t2952466

lost101 said:
@Mr.Nomo - I'll do some more research this evening. Is everything else working for you? Calls / data etc.
UPDATE: Sometimes flashing a CyanogenMOD based custom ROM can get WiFi working again. WiFi in XPerience ROM is different again and might be worth a try: http://forum.xda-developers.com/moto-g/orig-development/rom-xperience-9-0-0-t2952466
Click to expand...
Click to collapse
Yes! Everything else is working absolutely fine, calls, data, texting, everyhing else is awesome. I tried flashing a CyanoGen rom before, it started giving me issues with the playstore and with the UI, but will definitely try it out and update you with the results.
Thank you very much for all your help. :good:

Update on the XPerience Rom
Flashed properly, no errors and aside from it being a little slow at startup everything else works. Except the WiFi Tried modyfing the WCNSS file, no success with that either. One question, if I were to delete the folder /persist and all its contents, how would that affect the phone?

Mr.Nomo said:
Flashed properly, no errors and aside from it being a little slow at startup everything else works. Except the WiFi Tried modyfing the WCNSS file, no success with that either. One question, if I were to delete the folder /persist and all its contents, how would that affect the phone?
Click to expand...
Click to collapse
I don't know what would happen, but I can say that there are some partitions on Moto G that are unique to each handset. For example, if deleting the contents of that partition / folder caused you to loose IMEI - it might be impossible to undo. Without an IMEI you could no longer make calls.

Update on the XPerience Rom #2
It seems the rest of the rom is working fine up to this point, the only problem that I've encountered aside from the WIFI is the messaging app that comes included on the rom stops working whenever I try to reply to a message or create a new one. But I think I will use hangouts for that issue, by the way if I didnt thank already for the information regarding the possible causes of deleting the /persist file...I thank you again. :good:

Possible bricked OnePlus One

I'm trying to fix my cousins OnePlus for him, but having a hard time.
Current problem, and what I have tried so far:
Phone just hangs on Boot logo. When I boot it into Fastboot to flash it back to Stock (http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541) the phone no-longer goes into Fastboot and I have to do this http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 to get it back to be able to boot into Fastboot.
Flashing ROM via TWRP fails as it cannot seem to find/mount the /system partition.
Anyone had this and may be able to help?
Thanks

Not able to mount /system
seems real bad........
How the issue came to being???

therohanchawla said:
Not able to mount /system
seems real bad........
How the issue came to being???
Click to expand...
Click to collapse
Apparently one day the phone just rebooted on itself and got stuck on a continuous loop.
He is not technical and would not be flashing it so I don't think that would have caused it.
I presume all the partitions are on a single chipset in the internal 64 gb drive.
I would have thought it was a dead internal disk, but would that be possible?
It could be as the system partition does take a massive 1gb.
How could one do a diskcheck on the internal space?
Thanks

Bhups said:
Apparently one day the phone just rebooted on itself and got stuck on a continuous loop.
He is not technical and would not be flashing it so I don't think that would have caused it.
I presume all the partitions are on a single chipset in the internal 64 gb drive.
I would have thought it was a dead internal disk, but would that be possible?
It could be as the system partition does take a massive 1gb.
How could one do a diskcheck on the internal space?
Thanks
Click to expand...
Click to collapse
Go into fastboot and type: fastboot oem device-info, what does your device say?

ryanmat said:
Go into fastboot and type: fastboot oem device-info, what does your device say?
Click to expand...
Click to collapse
D:\adb>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
D:\adb>

Bhups said:
D:\adb>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
D:\adb>
Click to expand...
Click to collapse
Good news is that your bootloader is unlocked. Have you tried to load stock CM manually, as listed below?
Download the latest CM fastboot files from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746 and then get into fastboot mode and manually type in each code below:
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
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
If you don't have the 64GB model, then you can do fastboot flash userdata userdata.img for the last one.

ryanmat said:
Good news is that your bootloader is unlocked. Have you tried to load stock CM manually, as listed below?
Download the latest CM fastboot files from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746 and then get into fastboot mode and manually type in each code below:
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
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
If you don't have the 64GB model, then you can do fastboot flash userdata userdata.img for the last one.
Click to expand...
Click to collapse
Hello,
I did the above many times (as per first post). But it keeps failing at flashing the system.img.
Only vary rarely does it actually complete flashing everything, but still hangs on boot logo.

Bhups said:
Hello,
I did the above many times (as per first post). But it keeps failing at flashing the system.img.
Only vary rarely does it actually complete flashing everything, but still hangs on boot logo.
Click to expand...
Click to collapse
Results of running the following
Code:
fastboot flash modem NON-HLOS.bin
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash sbl1 sbl1.mbn
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash dbi sdi.mbn
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash aboot emmc_appsboot.mbn
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash rpm rpm.mbn
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash tz tz.mbn
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash LOGO logo.bin
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash oppostanvbk static_nvbk.bin
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash recovery recovery.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash system system.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot boot.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash cache cache.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash userdata userdata_64G.img
fastboot reboot
echo Press any key to exit...
pause >nul
exit
Code:
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 2.371s]
writing 'modem'...
OKAY [ 0.733s]
finished. total time: 3.104s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
FAILED (remote: flash write failure)
finished. total time: 10.062s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.016s]
writing 'dbi'...
OKAY [ 0.000s]
finished. total time: 0.031s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.031s]
writing 'aboot'...
OKAY [ 0.016s]
finished. total time: 0.047s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ -0.000s]
writing 'rpm'...
OKAY [ 0.031s]
finished. total time: 0.031s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 1073741824 bytes
sending 'tz' (325 KB)...
OKAY [ 0.016s]
writing 'tz'...
OKAY [ 0.016s]
finished. total time: 0.031s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.016s]
writing 'LOGO'...
FAILED (remote: flash write failure)
finished. total time: 10.078s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.437s]
writing 'oppostanvbk'...
FAILED (remote: flash write failure)
finished. total time: 10.483s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 1073741824 bytes
sending 'recovery' (9220 KB)...
OKAY [ 0.390s]
writing 'recovery'...
OKAY [ 0.140s]
finished. total time: 0.530s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.312s]
sending sparse 'system' (1045700 KB)...
OKAY [ 44.399s]
writing 'system'...
OKAY [ 18.127s]
sending sparse 'system' (5584 KB)...
OKAY [ 0.234s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 73.135s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 1073741824 bytes
sending 'boot' (6582 KB)...
OKAY [ 0.265s]
writing 'boot'...
OKAY [ 0.094s]
finished. total time: 0.374s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.016s]
sending 'cache' (56 KB)...
OKAY [ 0.000s]
writing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.078s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 1.310s]
sending 'userdata' (56 KB)...
OKAY [ 0.016s]
writing 'userdata'...
OKAY [ 0.031s]
finished. total time: 1.357s
rebooting...
finished. total time: 0.000s
Press any key to exit...

The following still gets phone stuck on boot logo:
fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 2.356s]
writing 'modem'...
OKAY [ 0.718s]
finished. total time: 3.089s
fastboot flash sbl1 sbl1.mbn
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.016s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.047s
fastboot flash dbi sdi.mbn
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.016s]
writing 'dbi'...
OKAY [ 0.016s]
finished. total time: 0.031s
fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.016s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.047s
fastboot flash rpm rpm.mbn
target reported max download size of 1073741824 bytes
sending 'rpm' (186 KB)...
OKAY [ 0.016s]
writing 'rpm'...
OKAY [ 0.031s]
finished. total time: 0.047s
fastboot flash tz tz.mbn
target reported max download size of 1073741824 bytes
sending 'tz' (325 KB)...
OKAY [ 0.016s]
writing 'tz'...
OKAY [ 0.031s]
finished. total time: 0.047s
fastboot flash LOGO logo.bin
target reported max download size of 1073741824 bytes
sending 'LOGO' (328 KB)...
OKAY [ 0.016s]
writing 'LOGO'...
OKAY [ 0.031s]
finished. total time: 0.047s
fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 1073741824 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.421s]
writing 'oppostanvbk'...
OKAY [ 0.140s]
finished. total time: 0.562s
fastboot flash boot boot.img
target reported max download size of 1073741824 bytes
sending 'boot' (6582 KB)...
OKAY [ 0.265s]
writing 'boot'...
OKAY [ 0.109s]
finished. total time: 0.374s
fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.031s]
sending 'cache' (56 KB)...
OKAY [ 0.016s]
writing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.094s
fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (9220 KB)...
OKAY [ 0.390s]
writing 'recovery'...
OKAY [ 0.140s]
finished. total time: 0.530s
fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.328s]
sending sparse 'system' (1045700 KB)...
OKAY [ 44.492s]
writing 'system'...
OKAY [ 18.143s]
sending sparse 'system' (5584 KB)...
OKAY [ 0.234s]
writing 'system'...
OKAY [ 0.094s]
finished. total time: 63.306s
fastboot flash userdata userdata_64G.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 1.310s]
sending 'userdata' (56 KB)...
OKAY [ -0.000s]
writing 'userdata'...
OKAY [ 0.047s]
finished. total time: 1.373s

How long are you letting your phone sit after you flash everything? It looks like everything flashed fine in your last post. First boot can take some time.

ryanmat said:
How long are you letting your phone sit after you flash everything? It looks like everything flashed fine in your last post. First boot can take some time.
Click to expand...
Click to collapse
I've let it sit for up to an hour.
But it only stays on the boot loop.

Bootloop to Recovery

Hi,
I have a problem whit my device after a flash a rom the device is stuck on bootloop and boot only to the twrp recovery
i tried to flash the stock rom and no seccss the device is still boot to the stock recovery
what shold i do :\ ?
my device i x1032 google play edition

Which ROM are you flashing?

While in fastboot mode enter :
mfastboot oem fb_mode_clear
That will solve that boot to recovery issue.

I do not know if it matters
When I tried to fix the problem so I changed the File system in the twrp
WIPE-ADVANCED WIPE- REPAIR OR CHANGE FILE SYSTEM
cache is in ext4
date is in f2fs
system is in ext4

any help ?
the problem is still exists
upload a video of the problem
https://www.youtube.com/watch?v=AoxwrfIEZQw

blior32017 said:
any help ?
the problem is still exists
Click to expand...
Click to collapse
Flash the latest XT1032 Factory Firmware Image using mFastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
mFastboot download: https://www.androidfilehost.com/?fid=24052804347778493
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219

lost101 said:
Flash the latest XT1032 Factory Firmware Image using mFastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
mFastboot download: https://www.androidfilehost.com/?fid=24052804347778493
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
this is the log
D:\minimal_adb_fastboot_1.4.1_portable>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.328s
D:\minimal_adb_fastboot_1.4.1_portable>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.094s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.344s
D:\minimal_adb_fastboot_1.4.1_portable>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (76 KB)...
OKAY [ 0.063s]
writing 'logo'...
OKAY [ 0.094s]
finished. total time: 0.156s
D:\minimal_adb_fastboot_1.4.1_portable>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.350s]
writing 'boot'...
OKAY [ 0.766s]
finished. total time: 1.116s
D:\minimal_adb_fastboot_1.4.1_portable>
D:\minimal_adb_fastboot_1.4.1_portable>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.359s]
writing 'recovery'...
OKAY [ 0.771s]
finished. total time: 1.130s
D:\minimal_adb_fastboot_1.4.1_portable>
D:\minimal_adb_fastboot_1.4.1_portable>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257288 KB)...
OKAY [ 8.092s]
writing 'system'...
OKAY [ 12.700s]
finished. total time: 20.791s
D:\minimal_adb_fastboot_1.4.1_portable>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (260792 KB)...
OKAY [ 8.192s]
writing 'system'...
OKAY [ 11.742s]
finished. total time: 19.949s
D:\minimal_adb_fastboot_1.4.1_portable>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 8.243s]
writing 'system'...
OKAY [ 13.915s]
finished. total time: 22.158s
D:\minimal_adb_fastboot_1.4.1_portable>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (18704 KB)...
OKAY [ 0.628s]
writing 'system'...
OKAY [ 0.853s]
finished. total time: 1.512s
D:\minimal_adb_fastboot_1.4.1_portable>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49368 KB)...
OKAY [ 1.605s]
writing 'modem'...
OKAY [ 1.459s]
finished. total time: 3.064s
D:\minimal_adb_fastboot_1.4.1_portable>
D:\minimal_adb_fastboot_1.4.1_portable>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.016s]
finished. total time: 0.016s
D:\minimal_adb_fastboot_1.4.1_portable>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.063s]
finished. total time: 0.063s
D:\minimal_adb_fastboot_1.4.1_portable>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (708 KB)...
OKAY [ 0.109s]
writing 'fsg'...
OKAY [ 5.602s]
finished. total time: 5.712s
D:\minimal_adb_fastboot_1.4.1_portable>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.359s]
finished. total time: 0.359s
D:\minimal_adb_fastboot_1.4.1_portable>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 5.993s]
finished. total time: 5.993s
D:\minimal_adb_fastboot_1.4.1_portable>mfastboot reboot
rebooting...
finished. total time: 0.016s
D:\minimal_adb_fastboot_1.4.1_portable>

@blior32017 - Which firmware image - state the zip filename - did you flash?

lost101 said:
@blior32017 - Which firmware image - state the zip filename - did you flash?
Click to expand...
Click to collapse
I have the GPE version so I flash "GPE_5.1_XT1032_LMY47M.M005"

blior32017 said:
I have the GPE version so I flash "GPE_5.1_XT1032_LMY47M.M005"
Click to expand...
Click to collapse
Try the following firmware image instead:
Retail US - XT1032_FALCON_RETUGLB_5.1_LPBS23.13-58-2_cid9 (Newer Build)​

Relocked suceeded...by accident

I OEM unlocked after day 14 second 1 hot the clock....I have never since then in the bootloader seen anything other than UNLOCKED in the second last line...
Today, I flash the stock 233...go to developer options to find oem unlocking disabled...I did three things it could be:
1. Installed CAF - during this I remember turning OEM unlocking off. Could be this.
2. Used qboot to flash the singleimage.bin from the STOCK 233 zip.
3. Flashed (for the first time successfully) the flashall.bat from the 233 stock zip - here is the log:
Code:
Motorola Mobility flashall script version 1.9
Flashing Options:
- flash userdata: 1
- flash preload: 1
- erase userdata: 0
- erase cache: 0
Waiting for fastboot enumeration...
Fastboot device is ready
There are 1 device(s) connected: 1d711912
Trying to flash device 1d711912
Starting flashing device 1d711912...
Flashing partition table ...
Executing ".\Windows\fastboot.exe -s 1d711912 flash partition gpt_both0.bin"
target max-download-size: 512MB
sending 'partition' (33 KB)...
OKAY [ 0.028s]
writing 'partition'...
OKAY [ 0.034s]
finished. total time: 0.063s
Flashing bootloader ...
Executing ".\Windows\fastboot.exe -s 1d711912 flash apdp dp_AP_signed.mbn"
target max-download-size: 512MB
sending 'apdp' (12 KB)...
OKAY [ 0.030s]
writing 'apdp'...
OKAY [ 0.026s]
finished. total time: 0.057s
Executing ".\Windows\fastboot.exe -s 1d711912 flash msadp dp_MSA_signed.mbn"
target max-download-size: 512MB
sending 'msadp' (12 KB)...
OKAY [ 0.028s]
writing 'msadp'...
OKAY [ 0.026s]
finished. total time: 0.055s
Executing ".\Windows\fastboot.exe -s 1d711912 flash prov prov32.mbn"
target max-download-size: 512MB
sending 'prov' (64 KB)...
OKAY [ 0.029s]
writing 'prov'...
OKAY [ 0.040s]
finished. total time: 0.069s
Executing ".\Windows\fastboot.exe -s 1d711912 flash sbl1 sbl1.mbn"
target max-download-size: 512MB
sending 'sbl1' (376 KB)...
OKAY [ 0.027s]
writing 'sbl1'...
OKAY [ 0.047s]
finished. total time: 0.074s
Executing ".\Windows\fastboot.exe -s 1d711912 flash sbl1bak sbl1.mbn"
target max-download-size: 512MB
sending 'sbl1bak' (376 KB)...
OKAY [ 0.039s]
writing 'sbl1bak'...
OKAY [ 0.031s]
finished. total time: 0.070s
Executing ".\Windows\fastboot.exe -s 1d711912 flash rpm rpm.mbn"
target max-download-size: 512MB
sending 'rpm' (171 KB)...
OKAY [ 0.030s]
writing 'rpm'...
OKAY [ 0.044s]
finished. total time: 0.075s
Executing ".\Windows\fastboot.exe -s 1d711912 flash rpmbak rpm.mbn"
target max-download-size: 512MB
sending 'rpmbak' (171 KB)...
OKAY [ 0.039s]
writing 'rpmbak'...
OKAY [ 0.029s]
finished. total time: 0.069s
Executing ".\Windows\fastboot.exe -s 1d711912 flash devcfg devcfg.mbn"
target max-download-size: 512MB
sending 'devcfg' (37 KB)...
OKAY [ 0.033s]
writing 'devcfg'...
OKAY [ 0.040s]
finished. total time: 0.074s
Executing ".\Windows\fastboot.exe -s 1d711912 flash devcfgbak devcfg.mbn"
target max-download-size: 512MB
sending 'devcfgbak' (37 KB)...
OKAY [ 0.039s]
writing 'devcfgbak'...
OKAY [ 0.026s]
finished. total time: 0.066s
Executing ".\Windows\fastboot.exe -s 1d711912 flash lksecapp lksecapp.mbn"
target max-download-size: 512MB
sending 'lksecapp' (56 KB)...
OKAY [ 0.027s]
writing 'lksecapp'...
OKAY [ 0.025s]
finished. total time: 0.053s
Executing ".\Windows\fastboot.exe -s 1d711912 flash lksecappbak lksecapp.mbn"
target max-download-size: 512MB
sending 'lksecappbak' (56 KB)...
OKAY [ 0.039s]
writing 'lksecappbak'...
OKAY [ 0.025s]
finished. total time: 0.065s
Executing ".\Windows\fastboot.exe -s 1d711912 flash tz tz.mbn"
target max-download-size: 512MB
sending 'tz' (1447 KB)...
OKAY [ 0.054s]
writing 'tz'...
OKAY [ 0.065s]
finished. total time: 0.119s
Executing ".\Windows\fastboot.exe -s 1d711912 flash tzbak tz.mbn"
target max-download-size: 512MB
sending 'tzbak' (1447 KB)...
OKAY [ 0.069s]
writing 'tzbak'...
OKAY [ 0.042s]
finished. total time: 0.111s
Executing ".\Windows\fastboot.exe -s 1d711912 flash keymaster keymaster.mbn"
target max-download-size: 512MB
sending 'keymaster' (221 KB)...
OKAY [ 0.031s]
writing 'keymaster'...
OKAY [ 0.042s]
finished. total time: 0.073s
Executing ".\Windows\fastboot.exe -s 1d711912 flash cmnlib cmnlib.mbn"
target max-download-size: 512MB
sending 'cmnlib' (197 KB)...
OKAY [ 0.029s]
writing 'cmnlib'...
OKAY [ 0.042s]
finished. total time: 0.072s
Executing ".\Windows\fastboot.exe -s 1d711912 flash cmnlibbak cmnlib.mbn"
target max-download-size: 512MB
sending 'cmnlibbak' (197 KB)...
OKAY [ 0.039s]
writing 'cmnlibbak'...
OKAY [ 0.028s]
finished. total time: 0.067s
Executing ".\Windows\fastboot.exe -s 1d711912 flash cmnlib64 cmnlib64.mbn"
target max-download-size: 512MB
sending 'cmnlib64' (250 KB)...
OKAY [ 0.028s]
writing 'cmnlib64'...
OKAY [ 0.042s]
finished. total time: 0.071s
Executing ".\Windows\fastboot.exe -s 1d711912 flash cmnlib64bak cmnlib64.mbn"
target max-download-size: 512MB
sending 'cmnlib64bak' (250 KB)...
OKAY [ 0.039s]
writing 'cmnlib64bak'...
OKAY [ 0.027s]
finished. total time: 0.067s
Executing ".\Windows\fastboot.exe -s 1d711912 flash aboot emmc_appsboot.mbn"
target max-download-size: 512MB
sending 'aboot' (855 KB)...
OKAY [ 0.048s]
writing 'aboot'...
OKAY [ 0.057s]
finished. total time: 0.105s
Executing ".\Windows\fastboot.exe -s 1d711912 flash abootbak emmc_appsboot.mbn"
target max-download-size: 512MB
sending 'abootbak' (855 KB)...
OKAY [ 0.049s]
writing 'abootbak'...
OKAY [ 0.038s]
finished. total time: 0.087s
Executing .\Windows\fastboot.exe -s 1d711912 reboot-bootloader
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
Flashing modem SW...
Executing ".\Windows\fastboot.exe -s 1d711912 flash modem NON-HLOS.bin"
target max-download-size: 512MB
sending 'modem' (131072 KB)...
OKAY [ 2.846s]
writing 'modem'...
OKAY [ 1.799s]
finished. total time: 4.646s
Executing ".\Windows\fastboot.exe -s 1d711912 flash fsg fsg.mbn"
target max-download-size: 512MB
sending 'fsg' (304 KB)...
OKAY [ 0.031s]
writing 'fsg'...
OKAY [ 0.030s]
finished. total time: 0.061s
Executing ".\Windows\fastboot.exe -s 1d711912 erase modemst1"
erasing 'modemst1'...
OKAY [ 0.030s]
finished. total time: 0.031s
Executing ".\Windows\fastboot.exe -s 1d711912 erase modemst2"
erasing 'modemst2'...
OKAY [ 0.032s]
finished. total time: 0.032s
Executing ".\Windows\fastboot.exe -s 1d711912 flash dsp adspso.bin"
target max-download-size: 512MB
sending 'dsp' (16384 KB)...
OKAY [ 0.364s]
writing 'dsp'...
OKAY [ 0.135s]
finished. total time: 0.500s
Flashing AP Images...
Executing ".\Windows\fastboot.exe -s 1d711912 flash boot boot.img"
target max-download-size: 512MB
sending 'boot' (23381 KB)...
OKAY [ 0.515s]
writing 'boot'...
OKAY [ 0.360s]
finished. total time: 0.876s
Executing ".\Windows\fastboot.exe -s 1d711912 flash recovery recovery.img"
target max-download-size: 512MB
sending 'recovery' (27119 KB)...
OKAY [ 0.598s]
writing 'recovery'...
OKAY [ 0.408s]
finished. total time: 1.007s
Executing ".\Windows\fastboot.exe -s 1d711912 flash system systemchunk0.img"
target max-download-size: 512MB
sending 'system' (259539 KB)...
OKAY [ 5.610s]
writing 'system'...
OKAY [ 3.718s]
finished. total time: 9.330s
Executing ".\Windows\fastboot.exe -s 1d711912 flash system systemchunk1.img"
target max-download-size: 512MB
sending 'system' (257674 KB)...
OKAY [ 24.309s]
writing 'system'...
OKAY [ 3.523s]
finished. total time: 27.835s
Executing ".\Windows\fastboot.exe -s 1d711912 flash system systemchunk2.img"
target max-download-size: 512MB
sending 'system' (262129 KB)...
OKAY [ 5.678s]
writing 'system'...
OKAY [ 3.551s]
finished. total time: 9.230s
Executing ".\Windows\fastboot.exe -s 1d711912 flash system systemchunk3.img"
target max-download-size: 512MB
sending 'system' (262143 KB)...
OKAY [ 5.669s]
writing 'system'...
OKAY [ 3.589s]
finished. total time: 9.259s
Executing ".\Windows\fastboot.exe -s 1d711912 flash system systemchunk4.img"
target max-download-size: 512MB
sending 'system' (262087 KB)...
OKAY [ 5.668s]
writing 'system'...
OKAY [ 3.923s]
finished. total time: 9.592s
Executing ".\Windows\fastboot.exe -s 1d711912 flash system systemchunk5.img"
target max-download-size: 512MB
sending 'system' (262103 KB)...
OKAY [ 5.697s]
writing 'system'...
OKAY [ 3.673s]
finished. total time: 9.370s
Executing ".\Windows\fastboot.exe -s 1d711912 flash system systemchunk6.img"
target max-download-size: 512MB
sending 'system' (257611 KB)...
OKAY [ 5.575s]
writing 'system'...
OKAY [ 3.801s]
finished. total time: 9.376s
Executing ".\Windows\fastboot.exe -s 1d711912 flash system systemchunk7.img"
target max-download-size: 512MB
sending 'system' (262141 KB)...
OKAY [ 5.677s]
writing 'system'...
OKAY [ 3.727s]
finished. total time: 9.405s
Executing ".\Windows\fastboot.exe -s 1d711912 flash system systemchunk8.img"
target max-download-size: 512MB
sending 'system' (262141 KB)...
OKAY [ 5.661s]
writing 'system'...
OKAY [ 3.554s]
finished. total time: 9.216s
Executing ".\Windows\fastboot.exe -s 1d711912 flash system systemchunk9.img"
target max-download-size: 512MB
sending 'system' (253030 KB)...
OKAY [ 5.475s]
writing 'system'...
OKAY [ 3.461s]
finished. total time: 8.937s
Executing ".\Windows\fastboot.exe -s 1d711912 flash system systemchunk10.img"
target max-download-size: 512MB
sending 'system' (262143 KB)...
OKAY [ 5.672s]
writing 'system'...
OKAY [ 3.588s]
finished. total time: 9.261s
Executing ".\Windows\fastboot.exe -s 1d711912 flash system systemchunk11.img"
target max-download-size: 512MB
sending 'system' (262141 KB)...
OKAY [ 5.667s]
writing 'system'...
OKAY [ 3.624s]
finished. total time: 9.292s
Executing ".\Windows\fastboot.exe -s 1d711912 flash system systemchunk12.img"
target max-download-size: 512MB
sending 'system' (261619 KB)...
OKAY [ 5.656s]
writing 'system'...
OKAY [ 3.653s]
finished. total time: 9.309s
Executing ".\Windows\fastboot.exe -s 1d711912 flash system systemchunk13.img"
target max-download-size: 512MB
sending 'system' (241951 KB)...
OKAY [ 5.232s]
writing 'system'...
OKAY [ 3.463s]
finished. total time: 8.696s
Executing ".\Windows\fastboot.exe -s 1d711912 flash system systemchunk14.img"
target max-download-size: 512MB
sending 'system' (66484 KB)...
OKAY [ 1.441s]
writing 'system'...
OKAY [ 0.906s]
finished. total time: 2.348s
Executing ".\Windows\fastboot.exe -s 1d711912 flash cache cache.img"
target max-download-size: 512MB
sending 'cache' (6632 KB)...
OKAY [ 0.154s]
writing 'cache'...
OKAY [ 0.074s]
finished. total time: 0.229s
Clearing boot mode...
...
(bootloader) Not allowed command
FAILED (remote failure)
finished. total time: 0.012s
Flashing preload...
Executing ".\Windows\fastboot.exe -s 1d711912 flash preload preload.img"
target max-download-size: 512MB
sending 'preload' (8648 KB)...
OKAY [ 0.208s]
writing 'preload'...
OKAY [ 0.090s]
finished. total time: 0.299s
Flashing userdata...
Executing ".\Windows\fastboot.exe -s 1d711912 flash userdata userdata.img"
target max-download-size: 512MB
sending 'userdata' (297806 KB)...
OKAY [ 6.448s]
writing 'userdata'...
OKAY [ 2.084s]
finished. total time: 8.533s
All images flashed successfully
Rebooting device...
rebooting...
finished. total time: 0.010s
All devices are flashed
Press any key to continue . . .
I would just some of you to throw your opinions around and tell me if I found something useful ?

How did you flashed 233? By ota update? Or by flashable zip by twrp?
Inviato dal mio Lenovo P2a42 utilizzando Tapatalk

flashed with the zip available in the thread with all the stock ROMs but it always failed flashing the modem partition cause it was unlocked. I was trying to fix a no signal error and I noticed the OEM was relocked.
if you look inside the folder called mbmi ( or something, I don't remember and in on my phone) there is a blankflash.zip
I remember setting the fastboot to factory (fastboot OEM config bootmode factory). installing Qualcomm drivers with lenovo diagnostic and used the .bat in the blankflash to basically restore the core firmware to factory. it flashed all the partitions it usually can't due to unlocked OEM.

Quite interesting if it's true that you're bootloader was indeed unlocked. Have you tried using Android Pay or Pokemon Go? (assuming you're unrooted)
"CAF"? What does it stand for? Some rom? There are customs roms that don't use verified boot. It seems that if the verified boot flag is removed from the kernel this will prevent the bootloader from passing the flag to SafetyNet. The state of the bootloader will then be hidden.

Has anyone tried it out and found to be working?? if yes then please tell what is the actual procedure and sequence for the same? I have tried many times and couldn't find out what was my mistake? Please help!! Thanks

Can any one give an exact way to relock the bootloader?

I would also love to be able to relock the bootloader. My device is softbricked, and I can only restore system and recovery. Running the allflash.bat gives me an error because the bootloader unlock disables the segments I need to fix the brick. F*** Lenovo, why would you make an unlocked bootloader have less permission? Give me control over my own device, I paid for it.
---------- Post added at 03:07 PM ---------- Previous post was at 02:52 PM ----------
eried1 said:
Quite interesting if it's true that you're bootloader was indeed unlocked. Have you tried using Android Pay or Pokemon Go? (assuming you're unrooted)
"CAF"? What does it stand for? Some rom? There are customs roms that don't use verified boot. It seems that if the verified boot flag is removed from the kernel this will prevent the bootloader from passing the flag to SafetyNet. The state of the bootloader will then be hidden.
Click to expand...
Click to collapse
I found this which gives more info. https://www.reddit.com/r/Android/comments/1rt9md/eli5_what_is_caf_why_is_cm_going_caf_affects_the/
"CAF is a custom Linux kernel branch in place to support Qualcomm hardware. By using a potentially heavily customized kernel (while AOSP Android uses the main Linux kernel), custom kernel developers will have to effectively maintain two separate instances of their customizations."

Can I relock my bootloader or not

Explanation needed
Can you explain the entire process step by step? you haven't mentioned the below step in the first post. It would be helpful if you could rewrite the entire process in order.
SvenRL said:
flashed with the zip available in the thread with all the stock ROMs but it always failed flashing the modem partition cause it was unlocked. I was trying to fix a no signal error and I noticed the OEM was relocked.
if you look inside the folder called mbmi ( or something, I don't remember and in on my phone) there is a blankflash.zip
I remember setting the fastboot to factory (fastboot OEM config bootmode factory). installing Qualcomm drivers with lenovo diagnostic and used the .bat in the blankflash to basically restore the core firmware to factory. it flashed all the partitions it usually can't due to unlocked OEM.
Click to expand...
Click to collapse

@SvenRL Hey? U still alive? Can you please explain to us how you relocked the bootloader?

If this could be elaborated it would mean the world to us who lost our modem/IMEI. I'm still not sure of what CAF means. There seems to be ROMs incorporating it, such as AOSP and HalogenOS.
@SvenRL, please reply once you log in.
EDIT: When looking at the date of the OP and comparing to the date of this post, it appears nothing was solved even though the modem was, supposedly, flashed.