Database Info

fastboot bricked my device and it's not fixing it back

hello.
I tried to test a custom kernel today. So I followed the advice in cyanogenmod's wiki:
If you are developing a kernel, you may find it helpful to delete your boot.img and recovery.img to force booting into fastboot:
fastboot erase boot
fastboot erase recovery
You can then manually boot from your custom kernel and a ramdisk:
fastboot boot <kernel> <ramdisk>
Once you have a working kernel and ramdisk, you can automagically combine them within fastboot:
fastboot flash:raw boot <kernel> <ramdisk>
Click to expand...
Click to collapse
The erase steps worked happily! But when I reached the boot step:
Code:
% fastboot boot boot_old.img-kernel.gz boot_old.img-ramdisk.cpio.gz
creating boot image...
creating boot image - 5416960 bytes
downloading boot.img...
OKAY [ 1.688s]
booting...
FAILED (remote: ()
finished. total time: 1.689s
And now, no matter what I try, I get:
Code:
Unrecoverable bootloader error <0x00000000>.
Flashing the previous (working) boot.img or recovery-jb-touch.img does not work. After finishing what appears to be a successful flash, the device gets unidentified for some reason. So I can't `fastboot reboot`.
Here is the full output:
Code:
% fastboot devices
015d262e983c120f fastboot
% fastboot flash recovery ../recovery-jb-touch.img
sending recovery (6942 KB)...
OKAY [ 1.961s]
writing recovery...
OKAY [ 3.136s]
finished. total time: 5.098s
% fastboot devices
???????????? fastboot
So every time I flash, I have to manually restart to the bootloader. And hence nothing gets fixed, I'm back to square one.
I understand that unlocking voids the warranty. But I expected the extra functionality to actually work if I follow the correct procedure. I didn't expect things to blow up in my face. The fact that I live overseas and there is probably no Asus tech support around here adds an insult to my injury.
I really hope there is a way to fix this.

y2012 said:
hello.
I tried to test a custom kernel today. So I followed the advice in cyanogenmod's wiki:
The erase steps worked happily! But when I reached the boot step:
Code:
% fastboot boot boot_old.img-kernel.gz boot_old.img-ramdisk.cpio.gz
creating boot image...
creating boot image - 5416960 bytes
downloading boot.img...
OKAY [ 1.688s]
booting...
FAILED (remote: ()
finished. total time: 1.689s
And now, no matter what I try, I get:
Code:
Unrecoverable bootloader error <0x00000000>.
Flashing the previous (working) boot.img or recovery-jb-touch.img does not work. After finishing what appears to be a successful flash, the device gets unidentified for some reason. So I can't `fastboot reboot`.
Here is the full output:
Code:
% fastboot devices
015d262e983c120f fastboot
% fastboot flash recovery ../recovery-jb-touch.img
sending recovery (6942 KB)...
OKAY [ 1.961s]
writing recovery...
OKAY [ 3.136s]
finished. total time: 5.098s
% fastboot devices
???????????? fastboot
So every time I flash, I have to manually restart to the bootloader. And hence nothing gets fixed, I'm back to square one.
I understand that unlocking voids the warranty. But I expected the extra functionality to actually work if I follow the correct procedure. I didn't expect things to blow up in my face. The fact that I live overseas and there is probably no Asus tech support around here adds an insult to my injury.
I really hope there is a way to fix this.
Click to expand...
Click to collapse
You need to flash the correct kernel and such for the tf700, don't flash anything available out there, you are asking for bricking! I suggest to flash back to full stock firmware then start over.

buhohitr said:
You need to flash the correct kernel and such for the tf700, don't flash anything available out there, you are asking for bricking!
Click to expand...
Click to collapse
It was a CM10 kernel I compiled myself.
buhohitr said:
I suggest to flash back to full stock firmware then start over.
Click to expand...
Click to collapse
Explaining how this can be done from fastboot would be great. Especially when I can't even make recovery work.

Try flashing NVidia blobs instead of raw images ... AFAIK the TF700 bootloader's fastboot implementation only understands blobs.

You also forget the usb ID. Try this
Code:
fastboot -i 0x0B05 boot boot_old.img-kernel.gz boot_old.img-ramdisk.cpio.gz

ostar2 said:
You also forget the usb ID. Try this
Code:
fastboot -i 0x0B05 boot boot_old.img-kernel.gz boot_old.img-ramdisk.cpio.gz
Click to expand...
Click to collapse
I tried with and without the ID.
Is it really damaging if the ID is not included?

y2012 said:
I tried with and without the ID.
Is it really damaging if the ID is not included?
Click to expand...
Click to collapse
No. There were just some bootloader versions which never showed a serial number, just question marks, when issuing "fastboot devices", and then you needed to specify the ID to get anything to work.
The fastboot implementation in the TF700 is a bit strange. I also could not get "fastboot boot ..." to work, but I never erased my boot and recovery partitions. Just flashing blobs worked fine.

_that said:
The fastboot implementation in the TF700 is a bit strange. I also could not get "fastboot boot ..." to work, but I never erased my boot and recovery partitions. Just flashing blobs worked fine.
Click to expand...
Click to collapse
Can you elaborate on flashing blobs?
What blobs should I flash and where/how can I obtain them?

For reference:
Code:
% fastboot getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 015d262e983c120f
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.082s

y2012 said:
Can you elaborate on flashing blobs?
What blobs should I flash and where/how can I obtain them?
Click to expand...
Click to collapse
TF700 fastboot likes to flash blobs that start with a "-SIGNED-BY-SIGNBLOB-" header, followed by an "MSM-RADIO-UPDATE" header.
Try flashing the TWRP recovery from here (see "Fastboot method"): http://www.teamw.in/project/twrp2/105
y2012 said:
For reference:
Code:
% fastboot getvar all
...
Click to expand...
Click to collapse
I am getting the same output on mine, the only differences are the serial number (greetings from Captain Obvious) and the size of the userdata partition (I have a 64 GB tablet).

_that said:
TF700 fastboot likes to flash blobs that start with a "-SIGNED-BY-SIGNBLOB-" header, followed by an "MSM-RADIO-UPDATE" header.
Try flashing the TWRP recovery from here (see "Fastboot method"): http://www.teamw.in/project/twrp2/105
Click to expand...
Click to collapse
Flashing TWRP didn't work.
I think I'm giving up on this.

y2012 said:
Flashing TWRP didn't work.
Click to expand...
Click to collapse
Details?

Ive started the same thread erased the recovery it says it writed recovery image but i think the tablet freezes as any command after writing recovery will not work but before that it will an example:
try adb reboot the tablet will reboot
but after writing the recovery image try entering that command and see what happens
guess Im not the only one who has this problem now we need solutions
Edit: I just remembered I had plan to use Ubuntu to write recovery image see if you can flash ubuntu as the files are on SD rather then on tablet
also skythra had a similar problem he/she said that the fastboot unlocker for jellybean you cannot write you can only read and boot
I also want to ask you have a 64 GB as well?

_that said:
Details?
Click to expand...
Click to collapse
Same as the OP. Flashing looked like it succeeded. The device gets unidentified in fastboot after that. Manual restart. And choosing recovery shows the same error.
It looks like the only options left are:
1] fastboot flash -- I don't know where to get an update.zip that works with this.
2] fastboot flashall -- I don't know how this command works as it doesn't take any arguments.

4SHR4F said:
Ive started the same thread erased the recovery it says it writed recovery image but i think the tablet freezes as any command after writing recovery will not work but before that it will an example:
try adb reboot the tablet will reboot
but after writing the recovery image try entering that command and see what happens
Click to expand...
Click to collapse
Assuming you meant fastboot not adb. This is true. The device gets unidentified (see `fastboot devices` output). Whether the freeze is caused by the unidentified device, or both symptoms are caused by something else, I don't know.
guess Im not the only one who has this problem now we need solutions
Click to expand...
Click to collapse
Well, Asus will not help. They provide half-assed unlocking feature, broken fastboot, and void your warranty in the process. Way to go winning developers and advanced users!
I also want to ask you have a 64 GB as well?
Click to expand...
Click to collapse
No. 32GB here.

y2012 said:
Assuming you meant fastboot not adb. This is true. The device gets unidentified (see `fastboot devices` output). Whether the freeze is caused by the unidentified device, or both symptoms are caused by something else, I don't know.
Well, Asus will not help. They provide half-assed unlocking feature, broken fastboot, and void your warranty in the process. Way to go winning developers and advanced users!
No. 32GB here.
Click to expand...
Click to collapse
Let me know what happens someone suggested downgrading to ICS then use debugfs and then use custom rom root and terminal to send the recovery that way either way my computers PCI card decided to stop working so I have to tether it and then download the tools which is a problemsince I formatted my whole computer to get this transformer workin best of luck but like I said please post ur method cause im in the same boat

4SHR4F said:
Let me know what happens someone suggested downgrading to ICS then use debugfs and then use custom rom root and terminal to send the recovery that way either way my computers PCI card decided to stop working so I have to tether it and then download the tools which is a problemsince I formatted my whole computer to get this transformer workin best of luck but like I said please post ur method cause im in the same boat
Click to expand...
Click to collapse
Bump any solutions cant use flash or boot so cant do anything could someone send us bootlocker tool or something i dont know please help

y2012 said:
Same as the OP. Flashing looked like it succeeded. The device gets unidentified in fastboot after that. Manual restart. And choosing recovery shows the same error.
It looks like the only options left are:
1] fastboot flash -- I don't know where to get an update.zip that works with this.
2] fastboot flashall -- I don't know how this command works as it doesn't take any arguments.
Click to expand...
Click to collapse
fastboot -b flashall
-b (specify a custom kernel base address)
in the same boat

(bootloader) Preflash validation failed

Hi I've Installed Chainfire(dumbest idea ever) -I had GLTools with only default plugin- ,too check whenever It would be possible to run Portal-So memory is almost full ,so I couldn't do neither full CWM backup ,and Advanced Backup didn't worked for me.
So What I did was flash 4.4.2(and I was on 4.4.4 europe rom -XT1032)
I have Fastboot Reason: UTAG *flashfail* configured as fastboot(no not after installing chainfire)
I was flashing with my premade /.sh file (fastboot flash partition gpt.bin etc.) and it seems like what have been flasheed is:
wirting 'partition'...
(bootloader) Preflash validation failed
FAILED(remote failure)
wirting 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
witing 'boot'...
OKAY
'system' -sparechunk.0
FAILED (data transfer failure (No such file or directory)) - lol? ,I've actually modified VM to have 512 mb of ram instead of 1536mb and cores from 2 to 1.
*fastboot resets*
Fastboot Reason: UTAG *flashfail* configured as fastboot
'system'-sparechunk.1
OKAY
and the rest wasn't flashed ,What can I do ,...I've just clicked factory(up button-congrats idiot-I wanted to go into recovery to say that I can go there and do something from there *facepalm* and clicked Up button ,because I was on factory option).
Okay ,so know I have no UTAG error recovery still works ,phone gets stuck on unlocked bootloader disclamer.
Btw before I started to install chainfire I've followed some instructions:
Code:
Backup
[B] * boot into recovery
* adb backup -f boot.img boot
* adb backup -f system.img system[/B]
Restore
[B] * boot into recovery[/B]
* adb shell echo -n boot > /tmp/ro.bu.restore
* adb restore boot.img
[I][B] * adb shell echo -n system > /tmp/ro.bu.restore
* adb restore system.img[/B][/I]
I've followed ,Failed
As boot.img from 4.4.2 have flashed can I actually flash that( * adb backup -f boot.img boot) boot.img and I don't magic will help me. Or can Actually someone who Have XT1032 falcon_umts do like CWM Backup without any personal stuff and I would try to flash it(Preloader/boot is not corrupted- device unlocked etc.-) ,when I used Used factory then everything seems to be working(expect for the android of course... and I don't know whenever VM will work If I don't have everything flashed).
Btw I can't Flash System.img from before I've destroyed it with Chainfire ,because the size is more than 600/700 mb and it just out numbers max number for sending system partition to fastboot.

Not saying this will definitely work, but if you get the gpt.bin and emmc_appsboot.mbn files from the 4.4.4 OTA zip (probably floating around here) and overwrite the originals from 4.4.2 in your factory image (delete the old ones or rename them to something else), then do the following:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash partition gpt.bin
fastboot reboot-bootloader
Then flash as normal according to the guide that's floating around here, but leave out the gpt.bin and emmc_appsboot.mbn (you already flashed these) and the motoboot.img or it will brick it!

I just installed Paranoid Android ontop of it(adb sideload-I couldn't get into CWM ,and by accidently clicking factory in fastboot I could then go to CWM) and it works-then I launch PA install minimal gapps then factory reset it in cwm delete all data and slowly update pa update by update(installing 4.4RC2 into 4.45 is an bad idea for overall performance and stability) -I just kinda paniced.And I think ,because I was using generic fastboot instead of provided in guide ,preloadder didn't get corrupted(when to look at It only boot have been flashed correctly , and PA have boot.img in package).
So far so good.

This error has been associated with locked bootloader.

I know but my is still unlocked.
Btw that message "Preflash validation failled" supposed to show after booting too fastboot(actually that sounds like a total bull****) or on flasher linux terminal.

Shuttwind215 said:
I know but my is still unlocked.
Btw that message "Preflash validation failled" supposed to show after booting too fastboot(actually that sounds like a total bull****) or on flasher linux terminal.
Click to expand...
Click to collapse
My moto's bootloader is unlocked too, but it still gives the error...
Found an article:
https://giorgiosadventures.wordpres...rom-gpe-4-4-4-to-stock-and-recover-softbrick/
Try this... Lets see if it helps...
BTW, I got this error after converting xt1033 to gpe, then OTA'ing it to 5.0.1, then downgrading to 4.4.2.

@layman806 My moto g allready work look at post #3 this is what I did it[it looks extremly confusing]. It mightn't work for you through
,but if yours moto g have unlocked bootloader then you can do a lot ,and your situation isn't that bad.

lost101 said:
This error has been associated with locked bootloader.
Click to expand...
Click to collapse
i have unlocked my bootloader but i still get that error. every other command executes perfectly but this gpt.bin doesnt
any solution?

khiladi_786 said:
i have unlocked my bootloader but i still get that error. every other command executes perfectly but this gpt.bin doesnt
any solution?
Click to expand...
Click to collapse
I have the exact same problem on my xt1031 motog. I cant get any roms to boot and I cant figure out what version of gpt.bin i need to use. I get the same error.
Driving me crazy.

not solved
I am flashing the stock rom into my moto g3 but it keep tellin preflash validation failed........I did everything ......still not solved.......help me out please..........
on bootloader it shows....
device is unlocked. status code :3
software status: official
it is bit odd.....

heisenberg1546 said:
I am flashing the stock rom into my moto g3 but it keep tellin preflash validation failed........I did everything ......still not solved.......help me out please..........
on bootloader it shows....
device is unlocked. status code :3
software status: official
it is bit odd.....
Click to expand...
Click to collapse
This subforum is not for your phone. https://forum.xda-developers.com/2015-moto-g is the place for you.
If you are getting a 'pre-flash validation' error - even with the latest available firmware image - then you have to either wait for an even newer firmware image or unlock Bootloader and flash a ROM zip.

help me plseeeeeeeeeeeeee i m getting preflash validation failed error on gpt.bin and sparsechunk plseee help me anyone i m using moto g3 xt1550 and trying to flash marshmallow.

Can't enter TWRP

I wanted to flash the latest update of RR7 but when i tried to get into the recovery the phone would reboot and show the twrp starting screen and then it would reboot again and start normally. I figured something must have gone wrong and reflashed twrp from my pc, however the issue persists. Flashify doesn't work either. So aside from a clean install, is there a workaround?

BoredDude said:
I wanted to flash the latest update of RR7 but when i tried to get into the recovery the phone would reboot and show the twrp starting screen and then it would reboot again and start normally. I figured something must have gone wrong and reflashed twrp from my pc, however the issue persists. Flashify doesn't work either. So aside from a clean install, is there a workaround?
Click to expand...
Click to collapse
You can try to boot directly into twrp with "fastboot boot TWRP.img"

zys52712 said:
You can try to boot directly into twrp with "fastboot boot TWRP.img"
Click to expand...
Click to collapse
Just tried it, same thing happens i can see the twrp starting screen but i can get to the main menu.
EDIT.
Changed the twrp version to an older one. No results, tried both flashing and booting from fastboot.
i get the following message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp2.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14796 KB)...
OKAY [ 0.479s]
writing 'recovery'...
OKAY [ 1.566s]
finished. total time: 2.049s

zys52712 said:
You can try to boot directly into twrp with "fastboot boot TWRP.img"
Click to expand...
Click to collapse
BoredDude said:
Just tried it, same thing happens i can see the twrp starting screen but i can get to the main menu.
EDIT.
Changed the twrp version to an older one. No results, tried both flashing and booting from fastboot.
i get the following message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp2.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (14796 KB)...
OKAY [ 0.479s]
writing 'recovery'...
OKAY [ 1.566s]
finished. total time: 2.049s
Click to expand...
Click to collapse
Then something is really wrong with your internal memory. Because that boot command in the post above does not use TWRP installed on your phone, it's a "temporary" TWRP booted from your PC folder.
Even if you've never installed TWRP on your phone (still have stock recovery) you can still boot to TWRP for a one-time/one-off session by using those commands. Do whatever you want, like install SuperSu, and when you reboot, you'll still have stock recovery!

ChazzMatt said:
Then something is really wrong with your internal memory. Because that boot command in the post above does not use TWRP installed on your phone, it's a "temporary" TWRP booted from your PC folder.
Even if you've never installed TWRP on your phone (still have stock recovery) you can still boot to TWRP for a one-time/one-off session by using those commands. Do whatever you want, like install SuperSu, and when you reboot, you'll still have stock recovery!
Click to expand...
Click to collapse
I fixed it erasing the TWRP folder in my internal storage

Recovery installation failed

Hello,
I have a Moto G (XT1032) since 3 years and all of a sudden, it didn't boot. I had the Stock ROM, I never installed a new ROM or Recovery...
I unlocked my phone and then tried to install TWRP to boot on recovery and make a backup of my data.
I tried several recoveries (twrp-2.8.6.0-xt1032, twrp-3.0.0.0_2-falcon, twrp-3.1.0-0-falcon, twrp-3.1.0-0-xt1032 & clockwork-touch-6.0.4.7-falcon).
I have no problem to send the recovery on the phone. In the fastboot mode on the phone, it says the installation is okay and then, I choose "Recovery" in the fastboot mode on the phone.
The phone reboot and I have the android logo with "No Command". I find this blog : https://wasconet.com/solution-moto-g-android-recovery-mode-no-command/ and so I hold the power button and press the volume up button to enter recovery mode screen.
The problem is, I access the default recovery — which is not TWRP, only a basic recovery where I can't mount the phone. This recovery says :
Android system recovery
LPBS23.13-56-2
...
From there I can reboot, apply update from sdcard or ADB, wipe data/factory, wipe cache, reboot to bootloader, power down or view recovery logs.
What can I do to install a good recovery and to mount my phone to make a backup ?
Thanks guys !

Lately it happens with the latest versions of twrp. Do not boot or boot once, then return the Stock Recovery again.
In my case I can not install v3.1 because it throws me max download size error. :silly:
Try the v3.0.2-2. It works without any problem over my old falcon.
https://dl.twrp.me/falcon/twrp-3.0.2-2-falcon.img.html
I'm not sure if the command works on the Falcon, but first try starting it without flashing it
fastboot boot twrp-3.0.2-2-falcon.img
By the way, can i assume that having Lollipop you have the latest version of the bootloader (41.1A)?

Thanks, it worked ! I made a backup of my files.
Now I try since this morning to install a new ROM... I tried "Factory" in the fastboot mode => Phone blocks on "Bootloader unlock".
With TWRP, I havea lot of problem with the mount. I can see the data but to copy files, it was not possible.
I mount the sdcard in Read Write with the terminal on the phone to copy the Lineage ROM. I tried to install it but I receive an error "1001".
I use now the last version of TWRP, the 3.1.0 with the command fastboot boot. This version works but I have the same error to install Lineage.
I also tried to install the stock version EU 5.1 Stock ROM (Untouched) (522mb) (from here https://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510) with adb sideload.
I saw "succesful" but the phone is always block on the "Bootloader unlock" image...
The bootloader version is indeed 41.1A.
Someone should have an idea to install a system ? (any system, I don't care, I just want a phone that I can use )
Thanks a lot !

Usually error 1001 relates to an encrypted or unreadable partition.
Have you used fastboot or mfastboot to install the system again?
Try Repair or Change file system using twrp.
Wipe>>Advanced Wipe>>
Then try to install any ROM.
If doesn't work. Inside of TWRP go to Advanced>Terminal Emulator
Then execute the command df
That should list you the partitions. Share it and if you know how to take it please share the recovery log after doing all this.

I use fastboot to just boot on the recovery.
To install, I don't tried fastboot or mfastboot. I find a guide to flash with mfastboot, I will try.
Yesterday I made all the wipe possible. Today I made a Repair on the system partition.
Here is the result of the df command :
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 446184 20 446164 0% /dev
tmpfs 446184 20 446164 0% /tmp
/dev/block/mmcblk0p33
667328 11836 655492 2% /cache
/dev/block/mmcblk0p36
5789552 5210064 528432 91% /data
/dev/block/mmcblk0p36
5789552 5210064 528432 91% /sdcard
I noticed something strange yesterday. I tried several times to delete files on the "sdcard" partition, where I found the pictures, whatsapp, ... I deleted some files with Windows (MTP Mode) and the files are always there after delete with no error message. I don't know if it's important or not.

lolo1410 said:
I I noticed something strange yesterday. I tried several times to delete files on the "sdcard" partition, where I found the pictures, whatsapp, ... I deleted some files with Windows (MTP Mode) and the files are always there after delete with no error message. I don't know if it's important or not.
Click to expand...
Click to collapse
When you unlock the bootloader, all your personal data should be deleted normally, but that didn't happen. The internal memory partition is recognized (that's good) but is unreadable, obviously corrupted. (Sorry for not noticing before)
Try installing the firmware again using mfastboot avoiding BOOTLOADER (motoboot) AND GPT files to see if works. If didn't, flash it again including GPT file (Partitions table).
If it still doesn't work, you'll have to figure out how to repartition the entire phone memory.
----------
By the way, never try to restore that DATA BACKUP. Like i say before, it's corrupted. Search a way to decompress and takes only the important files.

Thanks a lot for your time !
Indeed, it's seems there is a probleme with the filesystem.
I tried a flash of GPT & Bootloader but it didn't work.
Here is the log :
C:\adb\tmp>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.026s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.320s
&
C:\adb\tmp>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.093s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.370s
But I'm not sure if I choose the good firmware & bootloader.
On this link (http://www.filefactory.com/folder/c6cdedc45a775d27), which version can I take ?
Here is the information that I have for the phone :
Motorola G XT1032 - Type M0DEB - FCCID ihdt56pf1 buyed in Belgium
AP Fastboot Flash Mode (S)
41.1A (2015-04-10)
CPU MSM8226 CS
eMMC : 8GB Sandisk
DRAM : 1024MB Samsung S4

Try with one of these, and again. DONT FLASH BOOTLOADER (Usually cant be flashed after unlock but, I do not think you want a paperweight)
Retail EU 5.1
https://www.androidfilehost.com/?fid=24052804347848287
Retail EU 5.1 (NEWER BUILD)
https://www.androidfilehost.com/?fid=24499762636006646
You can download others from Here
https://forum.xda-developers.com/mo...rmware-t3110795?_e_pi_=7,PAGE_ID10,4937194410

After several tests, I find a good package, this : XT1032_FALCON_RETFR_5.1_LPBS23.13-56-2_cid7_CFC.xml
I had no error.
I see your message too late, I flash the bootloader
But it's a 41.1A version, here is the info on this package :
BUILD REQUEST INFO:
SW Version: falcon_retfr-user 5.1 LPBS23.13-56-2 2 release-keysMSM8626BP_1032.3116.98.00R
MBM Version: 41.1A
Modem Version: MSM8626BP_1032.3116.98.00R
FSG Version: MSM8626BP_FSG_01.101.00R
Build Fingerprint: motorola/falcon_retfr/falcon_umts:5.1/LPBS23.13-56-2/2:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 221.201.2.falcon_umts.Retail.en.FR
Model number: Moto G
Android Version: 5.1
Baseband Version: MSM8626BP_1032.3116.98.00R
Build Number: LPBS23.13-56-2
Build Date: Fri Feb 26 06:59:41 CST 2016
OTHER MISC VERSION INFO:
Subsidy Lock Config: None
Blur Version: Blur_Version.221.201.2.falcon_umts.Retail.en.FR
Version when read from CPV: falcon_retfr-user 5.1 LPBS23.13-56-2 2 release-keys
I followed the guide here https://forum.xda-developers.com/showthread.php?t=2542219 and no error during all the command. I switch off the phone and unfortunately, no boot...
It's block on the "Warning bootloader unlocked" screen...

The phone is still alive and that's good. Keep trying others roms if you want. But as I said before, surely the internal memory of the phone is corrupt. Unfortunately, I can't help you with that.
Maybe here over XDA there's a tutorial about how to solve your problem.

Okay, thanks a lot for your help.
I just tried the Retail EU 5.1 (NEWER BUILD) and same result : no error but blocks on the boot..
I will continue to test other ROM

I ended up in the same situation when trying to flash GPe on MotoG XT1032; the device was only able to boot into fastboot
After booting into TWRP, I formatted the /data partition again (in order to fallback to F2FS instead of ext4) and I used adb sideload to transfer "XT1032_Retail_Brazil_51_Untouched.zip" (you can find it on xda, under "Stock Motorola Lollipop ROM Collection" thread).
Phone was in full working condition once more

[ROOT][GUIDE][NOOB-FRIENDLY]Unlock Bootloader+Root+Stock Firmware for Lenovo K8 Plus

How to unlock bootloader & get root for Lenovo K8 Plus
**********Pre-requirements***********
1. Make sure you have 70% charge or more then that.
2. Follow all steps correctly otherwise you will end up with a bricked phone.
3. I'm not responsible for any damage to your phone.
4. Make sure that you have installed usb drivers.
5. Download ADB & Fastboot Drivers
Steps to Unlock Bootloader
1. First of all, enable the Developer Option
To Enable the Developer Option, Go to your Settings -> About -> Software Information -> More -> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled"
2. Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
3. Download and Extract the Downloaded ADB fastboot Zip file on your phone.
4. Now connect your phone to Computer using USB Cable.
When you connect your Phone to Computer, please wait until all the drivers get installed.
5. In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click
Now type the command in your command window
Code:
adb devices
6. If you see a pop up to allow USB Debugging on your phone, Click OK
Now type the command below to reboot your phone to bootloader
Code:
adb reboot bootloader
7. Once your phone reboot into bootloader, make sure your phone shows the bootloader locked and then type the command below to make sure fastboot drivers are installed properly.
Code:
fastboot devices
8. This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue, you must fix your drivers so that your phone is listed under fastboot devices.
9. If the phone has been recognized by the command above, proceed to unlock the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone. Also you'll loose your warranty!!
Code:
fastboot oem unlock
10. After the above command has finished executing, run the following
Code:
fastboot reboot
The phone will reboot. Wait until the phone has fully booted up into Android.
Root method
Note:- All credits for it goes to @topjohnwu for his amazing magisk
Requirements:-
1. Make sure you are on latest September patch firmware.
2. Download patched_boot.img created from magisk mangaer.
Instructions:-
1. Connect up your phone then type:-
Code:
adb reboot bootloader
2. Copy patched_boot.img in adb folder.
Now type
Code:
fastboot flash boot patched_boot.img
3. Open up you device & install magisk manager from here
Voilla you're rooted.
Stock firmware - here
Now, I'm working on a working TWRP for our device so be patient.
If you want to make help in the development for our device join this telegram group
Credits:-
Dhruv Agarwal (me)
Jwalit Vyas (Orangelalo at telegram)

Wow!!thanks for posting this ??

Great work, good for k8plus user, my brother was waiting for this, going to tell him,
Please add a tutorial on how to flash stock firmware if anything goes wrong,

already shared by XN Logos twrp also available

himfa71 said:
Great work, good for k8plus user, my brother was waiting for this, going to tell him,
Please add a tutorial on how to flash stock firmware if anything goes wrong,
Click to expand...
Click to collapse
Okay I'll post it soon.
mark332 said:
already shared by XN Logos twrp also available
Click to expand...
Click to collapse
I have tried it but that was not working at least for me.

Lenovo k8 plus xt1902-2 bootloader wont Unlock/Lock
I'm using Lenovo k8 plus xt1902-2. I Successfully unlocked my bootloader using command ''fastboot oem unlock'' and in fastboot mode it says Device Status: unlocked (see attachment) but when i try to flash TWRP i'm getting error
platform-tools>fastboot flash recovery r
ecovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (14280 KB)...
OKAY [ 0.428s]
writing 'recovery'...
FAILED (remote: not allowed in locked state)
finished. total time: 0.445s
Even worse when i use command ''fastboot getvar all'' to check my bootloader status it says
(bootloader) partition-typereloader: raw data
(bootloader) serialno: 0123456789ABCDEF
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) efuse: yes
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: MARINO
(bootloader) hwid: 0
(bootloader) version-preloader:
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.896s
I even tried to flash Twrp using sp flash tool with no luck. It gives error STATUS_INSUFFICIENT_BUFFER (0xC0010007)
Then i tried to lock the bootloader just so that i can start the unlock procedure again, but it just doesn't lock. I tried to flash stock Rom thru Sp flash tool using each and every mode (download load only, firmware upgrade, format all + download) the boot loader just doesn't lock again.
Please help me with this as i really want to install TWRP and root my device . Thanks!

Whilst flashing the stock firmware from the above link, it...
Gives me chip hw_code mismatch error
scatter: MT6757D
Device: MT6757
SP flash tool v5.1628_Win
And STATUS_INSUFFICIENT_BUFFER (0xC0010007) whilst using SP Flash Tool v5.1728_Win

AbuUmayr said:
Whilst flashing the stock firmware from the above link, it...
Gives me chip hw_code mismatch error
scatter: MT6757D
Device: MT6757
SP flash tool v5.1628_Win
And STATUS_INSUFFICIENT_BUFFER (0xC0010007) whilst using SP Flash Tool v5.1728_Win
Click to expand...
Click to collapse
same here

ocorner543 said:
I'm using Lenovo k8 plus xt1902-2. I Successfully unlocked my bootloader using command ''fastboot oem unlock'' and in fastboot mode it says Device Status: unlocked (see attachment) but when i try to flash TWRP i'm getting error
platform-tools>fastboot flash recovery r
ecovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (14280 KB)...
OKAY [ 0.428s]
writing 'recovery'...
FAILED (remote: not allowed in locked state)
finished. total time: 0.445s
Even worse when i use command ''fastboot getvar all'' to check my bootloader status it says
(bootloader) partition-typereloader: raw data
(bootloader) serialno: 0123456789ABCDEF
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) efuse: yes
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: MARINO
(bootloader) hwid: 0
(bootloader) version-preloader:
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.896s
I even tried to flash Twrp using sp flash tool with no luck. It gives error STATUS_INSUFFICIENT_BUFFER (0xC0010007)
Then i tried to lock the bootloader just so that i can start the unlock procedure again, but it just doesn't lock. I tried to flash stock Rom thru Sp flash tool using each and every mode (download load only, firmware upgrade, format all + download) the boot loader just doesn't lock again.
Please help me with this as i really want to install TWRP and root my device . Thanks!
Click to expand...
Click to collapse
Please PM me at telegram I have the same username
AbuUmayr said:
Whilst flashing the stock firmware from the above link, it...
Gives me chip hw_code mismatch error
scatter: MT6757D
Device: MT6757
SP flash tool v5.1628_Win
And STATUS_INSUFFICIENT_BUFFER (0xC0010007) whilst using SP Flash Tool v5.1728_Win
Click to expand...
Click to collapse
mdhuma said:
same here
Click to expand...
Click to collapse
Use this version of SP flash tool

lenovo k8 plus stuck at logo and keep rebooting
hi friends today i factory reset my rooted phone lenovo k8 plus
but now its keep rebooting and not starting
pls help

Chip mismatch! Same error continues

Tweak worked
AbuUmayr said:
Chip mismatch! Same error continues
Click to expand...
Click to collapse
Now finally worked, by remaining the MT6757 to MT6757D in all the text files in the Extracted ROM folder... alhamdulillah
---------- Post added at 07:45 AM ---------- Previous post was at 07:43 AM ----------
First showed the same chip mismatch error, but finally worked, by remaining the MT6757 to MT6757D in all the text files in the Extracted ROM folder... alhamdulillah.
Thanks for suggesting this version of tool

Dhruv_Agarwal said:
Okay I'll post it soon.
I have tried it but that was not working at least for me.
Click to expand...
Click to collapse
It is working.
Main thing is you need to be on September/november security patch after that follow the above guide .
You phone will be rooted without TWRP.
Generally root access means patch on stock boot.img which is done by dhruv.
Whenever you flash magisk it patches your boot.img to give you root access. Thanks to Magisk Devs.
After following the OP you call install flashify to flash zips & images further you can also flash twrp image for marino and reeboot to TWRP.(twrp 3.1.1 works perfectly with a little bug , dimmed screen at starting time of TWRP).

How to root Lenovo k8 plus January security patch level?

Sachin franco said:
How to root Lenovo k8 plus January security patch level?
Click to expand...
Click to collapse
.
.
I have same question guys...

platform-tools>fastboot flash recovery r
ecovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (14280 KB)...
OKAY [ 0.428s]
writing 'recovery'...
FAILED (remote: not allowed in locked state)
finished. total time: 0.445s
having same problem. please help

I'm lost in between. please help. I'm new to rooting.
Dhruv_Agarwal said:
How to unlock bootloader & get root for Lenovo K8 Plus
**********Pre-requirements***********
1. Make sure you have 70% charge or more then that.
2. Follow all steps correctly otherwise you will end up with a bricked phone.
3. I'm not responsible for any damage to your phone.
4. Make sure that you have installed usb drivers.
5. Download ADB & Fastboot Drivers
Steps to Unlock Bootloader
1. First of all, enable the Developer Option
To Enable the Developer Option, Go to your Settings -> About -> Software Information -> More -> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled"
2. Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
3. Download and Extract the Downloaded ADB fastboot Zip file on your phone.
4. Now connect your phone to Computer using USB Cable.
When you connect your Phone to Computer, please wait until all the drivers get installed.
5. In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click
Now type the command in your command window
Code:
adb devices
6. If you see a pop up to allow USB Debugging on your phone, Click OK
Now type the command below to reboot your phone to bootloader
Code:
adb reboot bootloader
7. Once your phone reboot into bootloader, make sure your phone shows the bootloader locked and then type the command below to make sure fastboot drivers are installed properly.
Code:
fastboot devices
8. This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue, you must fix your drivers so that your phone is listed under fastboot devices.
9. If the phone has been recognized by the command above, proceed to unlock the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone. Also you'll loose your warranty!!
Code:
fastboot oem unlock
10. After the above command has finished executing, run the following
Code:
fastboot reboot
The phone will reboot. Wait until the phone has fully booted up into Android.
Root method
Note:- All credits for it goes to @topjohnwu for his amazing magisk
Requirements:-
1. Make sure you are on latest September patch firmware.
2. Download patched_boot.img created from magisk mangaer.
Instructions:-
1. Connect up your phone then type:-
Code:
adb reboot bootloader
2. Copy patched_boot.img in adb folder.
Now type
Code:
fastboot flash boot patched_boot.img
3. Open up you device & install magisk manager from here
Voilla you're rooted.
Stock firmware - here
Now, I'm working on a working TWRP for our device so be patient.
If you want to make help in the development for our device join this telegram group
Credits:-
Dhruv Agarwal (me)
Jwalit Vyas (Orangelalo at telegram)
Click to expand...
Click to collapse
In Root Method Steps.
After 2. What do you mean by, ( 3. Open up you device & install magisk manager from here )
Should I use "fastboot reboot" in ADB and then install an APK or something? If not, How to install the Magisk Zip File? Please Help me in detail. I'm Lost. Sorry for the trouble.

Found something useful for development of TWRP
https://m.youtube.com/watch?feature=youtu.be&v=Nb9FmMxQSrQ"]https://m.youtube.com/watch?feature=youtu.be&v=Nb9FmMxQSrQ
I found this for oreo twrp of k8 note. can it be used to make twrp for k8 plus oreo.

Can any one upload the Oreo firmware for k8 plus:good::good:

gurdeep141 said:
hi friends today i factory reset my rooted phone lenovo k8 plus
but now its keep rebooting and not starting
pls help
Click to expand...
Click to collapse
Follow this procedure to install stock rom/unbrick your Lenovo K8 Plus..
https://encoderedge.blogspot.com/2018/01/how-to-flash-stock-romunbrick-lenovo-k8.html?m=1