Database Users

[SOLVED] Unbricking with nvflash

I followed androidroot.mobi's guide to pulling nvflash blobs for a Nexus 7. I was able to successfully do this, but I had problems trying to go back to stock. I flashed the stock recovery and then tried to flash the stock bootloader; first I used "fastboot flash boot bootloader.img" using the bootloader.img from JDQ39 but the bootloader version did not change. I then used "fastboot flash bootloader bootloader.img" and got the signature mismatch error mentioned elsewhere in the guide thread.
By this point for some reason the device would not boot to Android though the bootloader continued to work. I've tried to "unbrick" using wheelie --blob <path to blob.bin> --unbrick <path to bricksafe.img>
It gets stuck here:
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d4a826d48040b
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending BCT
And now the bootloader doesn't seem to work; I can't get into anything other than APX.
This is just a comedy of errors, and of course it isn't my device; I didn't have any trouble with mine. :/ Any ideas on how to recover?

heterodoxy said:
I flashed the stock recovery and then tried to flash the stock bootloader; first I used "fastboot flash boot bootloader.img" using the bootloader.img from JDQ39 but the bootloader version did not change. I then used "fastboot flash bootloader bootloader.img" and got the signature mismatch error mentioned elsewhere in the guide thread.
Click to expand...
Click to collapse
After some more research I'm really starting to suspect that I borked the kernel by doing this (boot vs. bootloader, why was flashing a bootloader to the former allowed?!) and that wheelie then borked the bootloader. If I can get the bootloader back I can get the kernel back, but I need help with the misbehaving nvflash...

U need to rma your tablet to get it fixed and about bootloader flashing every thing u do to your device is your choice no one is forcing u to do so. Thats y every op say i am not responsible.
Please ignore my spelling mistakes. English is not my native language.

xateeq said:
U need to rma your tablet to get it fixed
Click to expand...
Click to collapse
It'd be quicker to do it myself and it should be possible; that's the whole point of the guide to gaining nvflash access (on androidroot.mobi), with which you may or may not be familiar. There's no hardware problem that would make an RMA the only option; I just need a little better of an idea of how to proceed from here with nvflash specifically.
xateeq said:
and about bootloader flashing every thing u do to your device is your choice no one is forcing u to do so.
Click to expand...
Click to collapse
That's a little apropos of nothing. I don't disagree, and I've never said that flashing boot instead of bootloader was anything but a screw-up on my part. But my impression was that this is a community of developers like myself, all of whom I dare say have screwed up at least once (I know this isn't the first time for me), and I figured someone else may have learned or may know the right incantation to recover from this particular situation and may be able to pass it on.
It'd probably have been easier for me to post in the thread that concerns gaining nvflash access and supports some of the tools therefor, but I can't do that yet as it's in a development forum, so I can only hope for the right person to stumble across this thread.
Thanks.

heterodoxy said:
It'd be quicker to do it myself and it should be possible; that's the whole point of the guide to gaining nvflash access (on androidroot.mobi), with which you may or may not be familiar. There's no hardware problem that would make an RMA the only option; I just need a little better of an idea of how to proceed from here with nvflash specifically.
That's a little apropos of nothing. I don't disagree, and I've never said that flashing boot instead of bootloader was anything but a screw-up on my part. But my impression was that this is a community of developers like myself, all of whom I dare say have screwed up at least once (I know this isn't the first time for me), and I figured someone else may have learned or may know the right incantation to recover from this particular situation and may be able to pass it on.
It'd probably have been easier for me to post in the thread that concerns gaining nvflash access and supports some of the tools therefor, but I can't do that yet as it's in a development forum, so I can only hope for the right person to stumble across this thread.
Thanks.
Click to expand...
Click to collapse
Please i mean no disrespect but every night i go to Q&A section and ever were i see is people having bricked device because of screwed bootloader that they flashed wrong, and i have yet to see a proper solution.
Only solution i have seen is that u do a backup of it before u doing any thing and to backup ur device specific files u again need to load custom bootloader and that on its own is scary.

So there isn't a easy way to backup the device specific files? And I tried the nvflash method and flashed the stock bootloader without any issue... I guess I was just lucky to get away with it...

TheDj408 said:
So there isn't a easy way to backup the device specific files? And I tried the nvflash method and flashed the stock bootloader without any issue... I guess I was just lucky to get away with it...
Click to expand...
Click to collapse
If you have correct files then it shouldn't be a problem. If u flash wrong file the **** hits the fan.
Please ignore my spelling mistakes. English is not my native language.

I have exactly the same Problem as the TO...
TheDj408 said:
So there isn't a easy way to backup the device specific files? And I tried the nvflash method and flashed the stock bootloader without any issue... I guess I was just lucky to get away with it...
Click to expand...
Click to collapse
How exactly did you do this? And can you upload the wheelie binary you used, maybe theres only something wrong with our wheelie version...

Partitionator said:
I have exactly the same Problem as the TO...
How exactly did you do this? And can you upload the wheelie binary you used, maybe theres only something wrong with our wheelie version...
Click to expand...
Click to collapse
You're getting the Sending BCT hang/Error 3 with wheelie?
I think there's definitely something wrong with wheelie in general. I've tried the two versions on androidroot.mobi's Web site and the 0.2 version of wheelie posted elsewhere on this forum and had no success with any of them, at least on the bricked device. On a regular device (I'm trying them side by side) it's fine, so there's that.
With the bricked device I've been having more success (and been learning more) just using nvflash with the --blob parameter. I still get errors, but they're actually errors from the device or from the bootloader instead of a generic error sending information to/receiving a response from the device.

Partitionator said:
I have exactly the same Problem as the TO...
How exactly did you do this? And can you upload the wheelie binary you used, maybe theres only something wrong with our wheelie version...
Click to expand...
Click to collapse
I did the method right... I was able to see the files in tab but failed to get them in pc... So Iflashed ooriginal stock bootloader... I meant this...

Yeeeeeaaaaaaaaahhhhhhhhhhhh
I think my Nexus isn't dead... I experimented all day and all night long with nvflash, read much about the emmc partitions and finally something worked... Now it shows Google with the unlock symbol
I think the rest sould be easy..
First I created a flash.cfg. You can do that under linux with bct_dump under Linux. (I used recovery.bct which was created with the blob.bin)
Than I had to remove the line that starts with type= in thefirst section of the flash.cfg file.
here ist my flash.cfg file (16GB Nexus 7)
Code:
[device]
instance=3
[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=3145728
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=PT
id=3
type=partition_table
allocation_policy=sequential
filesystem_type=basic
size=4096
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=EBT
id=4
type=bootloader
allocation_policy=sequential
filesystem_type=basic
size=4194304
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=blob.EBT
[partition]
name=SOS
id=5
type=data
allocation_policy=sequential
filesystem_type=basic
size=5242880
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=blob.SOS
[partition]
name=LNX
id=6
type=data
allocation_policy=sequential
filesystem_type=basic
size=8388608
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=blob.LNX
[partition]
name=BAK
id=7
type=data
allocation_policy=sequential
filesystem_type=basic
size=5242880
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=GP1
id=8
type=GP1
allocation_policy=sequential
filesystem_type=basic
size=1048576
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=APP
id=9
type=data
allocation_policy=sequential
filesystem_type=basic
size=536870912
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=blob.APP
[partition]
name=CAC
id=10
type=data
allocation_policy=sequential
filesystem_type=ext3
size=554700800
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=MSC
id=11
type=data
allocation_policy=sequential
filesystem_type=ext3
size=2097152
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=USP
id=12
type=data
allocation_policy=sequential
filesystem_type=ext3
size=554700800
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=PER
id=13
type=data
allocation_policy=sequential
filesystem_type=basic
size=5242880
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=YTU
id=14
type=data
allocation_policy=sequential
filesystem_type=basic
size=524288
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
[partition]
name=UDA
id=15
type=data
allocation_policy=sequential
filesystem_type=ext3
size=18432
file_system_attribute=0
partition_attribute=0
allocation_attribute=0x808
percent_reserved=0
[partition]
name=GPT
id=16
type=GPT
allocation_policy=sequential
filesystem_type=basic
size=0xFFFFFFFFFFFFFFFF
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
After that I ran this command:
Code:
./nvflash --setbct --create --configfile flash.cfg --bl bootloader.ebt --bct recovery.bct --blob blob.bin
bäääm some output in the terminal (and Google flashed up on the device):
Code:
[email protected]:/home/jan/APX# ./nvflash --setbct --create --configfile flash.cfg --bl bootloader.ebt --bct recovery.bct --blob blob.bin
Nvflash v1.13.87205 started
Using blob v1.13.00000
USB device not found
[email protected]:/home/jan/APX# ./nvflash --setbct --create --configfile flash.cfg --bl bootloader.ebt --bct recovery.bct --blob blob.bin
Nvflash v1.13.87205 started
Using blob v1.13.00000
chip uid from BR is: 0x0000000000000000015d2bc285340e0f
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x83
chip uid: 0x0000000000000000015d2bc285340e0f
macrovision: disabled
hdcp: enabled
jtag: disabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 1
device config fuse: 17
sdram config strap: 0
sending file: recovery.bct
- 6128/6128 bytes sent
recovery.bct sent successfully
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: bootloader.ebt
- 2146912/2146912 bytes sent
bootloader.ebt sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 0 3
failed executing command 11 NvError 0x120002
command failure: create failed (bad data)
bootloader status: specified device is invalid (code: 6) message: nverror:0x4 (0x4) flags: 0
[email protected]:/home/jan/APX#
But you can see there is still a error and I use the create command what should earse everthing so you should only do this if you habe a backup of all imortant partition. But I recommend that you wait while I will test what I can do with that, and look what that error means.
EDIT: Very good in this state I have nvflash acess and can flash partitions...
EDIT2: Yeeeees its booting again, with all data on it, that means no wipe . First i flashed many partitions (i don think that flashing most of them was unecessary). Tomrrow I will brick my device again and then test what exactly to do...
EDIT3:
heterodoxy said:
You're getting the Sending BCT hang/Error 3 with wheelie?
I think there's definitely something wrong with wheelie in general. I've tried the two versions on androidroot.mobi's Web site and the 0.2 version of wheelie posted elsewhere on this forum and had no success with any of them, at least on the bricked device. On a regular device (I'm trying them side by side) it's fine, so there's that.
With the bricked device I've been having more success (and been learning more) just using nvflash with the --blob parameter. I still get errors, but they're actually errors from the device or from the bootloader instead of a generic error sending information to/receiving a response from the device.
Click to expand...
Click to collapse
Sorry I overread your Post... Yes it was the same error (3)
EDIT4: read here for unbricking: http://forum.xda-developers.com/showpost.php?p=48507424&postcount=16

Partitionator said:
Yeeeeeaaaaaaaaahhhhhhhhhhhh
Click to expand...
Click to collapse
You need a CSI gif there.
Partitionator said:
EDIT2: Yeeeees its booting again, with all data on it, that means no wipe . First i flashed many partitions (i don think that flashing most of them was unecessary). Tomrrow I will brick my device again and then test what exactly to do...
Click to expand...
Click to collapse
You are made of brilliant. I think I was on the same track as you but I didn't know about bct_dump and so I don't think my flash.cfg is exactly right. I'll be experimenting all night too. On my working device I backed up ALL THE PARTITIONS but on this device I only have what was pulled during the creation of the blobs (blob.bin, bootloader.ebt, create.bct, recovery.bct, etc.)
Cheers!

heterodoxy said:
You need a CSI gif there.
You are made of brilliant. I think I was on the same track as you but I didn't know about bct_dump and so I don't think my flash.cfg is exactly right. I'll be experimenting all night too. On my working device I backed up ALL THE PARTITIONS but on this device I only have what was pulled during the creation of the blobs (blob.bin, bootloader.ebt, create.bct, recovery.bct, etc.)
Cheers!
Click to expand...
Click to collapse
So ist your device working again? If not:
I think the missing partitions shouldn't be a Problem... if you haf the 1GB Version it think you can use my BCT (I learned of the existence of this tool somewere on the third page on google, aftere reading all pages before). After you habe it on nvflash mode, try holding vol down and nflash --resume --go and it should go into fastboot mode were you can reflash the bootloader from the last Kitkat factory Image... I don't tested this way but i think it should work...
And would you mind hitting the Thanks Button? It costed me many houres to find out how to get it in nvflash mode again and I wrote the post before I rewrote my bootloader
EDIT: OK my device is now bricked again (wrote zeros to mmcblk0boot0) First I made the bootstrap command better:
Code:
./nvflash --setbct --configfile flash.cfg --bl bootloader.ebt --bct recovery.bct --blob blob.bin --go
as you can see I removed --create and addet --go. The create command made the error (an because that my device wasn't wiped). I addet the go because without that I got "no command error". The go command dosen't do anything in my case, so i think the way i mentioned before in this post wouldn't work... And you need to flash something before...
EDIT2: ok the command above doesn't work because the --go command makes it leave nvflash mode, so the command with create in it is the best I found. Creat will fail but, but that ist good (so no wipe), but it was the only one I found that let you use setbct. And you can generate your flash.cfg file from create.bct. If you use create.bct instead auf recovery.bct for generating your flash.cfg file you don't have to remove this one line...

Partitionator said:
So ist your device working again?
Click to expand...
Click to collapse
Yes and no. When I tried the command you gave last night it bounced to the Google screen, which almost made me cry of happy because some of the errors I'd been getting had me dreading the possibility that the blob could have been good but the bootloader.ebt/BCT files weren't. I got "battery is too low" repeated over and over which I've seen before; not surprising given how much I've played with the thing. Wasn't returned to command prompt and --resume commands in another prompt didn't work. Wasn't at all sure that it'd charge in this mode (especially with the screen on) but plugged it into a 2A charger and hoped for the best.
It was off when I got up a few hours later and I had a minor heart attack, but if I run the command now, it bounces to the Google screen and returns me to the command prompt and as you noted, I can download partitions which is HUGE and I'm backing them all up now, UDA first. (As I mentioned, this wasn't my device, so I was dreading having to wipe user data though if that's what it took to unbrick it I'd obviously do it in a heartbeat.)
nvflash --resume --go doesn't seem to be putting me in fastboot with the Vol- button held down, unfortunately. I'm not sure if that functionality is in the bootloader itself or in another partition (e.g. does the bootloader for the Tegra 3 chain to the Android bootloader or is it the same thing?). So I'm going to poke at the partitions on my other device and see what matches bootloader-grouper-*.img and see if it works after I flash that (and boot.img) from the factory image the device was using (JDQ39).
On a technical side note, the flash.cfg you provided is interesting, though clearly it works. I had been basing mine off the partition table of a working device and not only were sizes (which I got by multiplying sectors by sector size) different but IDs were too (e.g. PT was 524288 for me, 4096 for you, partition 5 is SOS for you but EKS for me? Which is somewhat backed up by the androidroot.mobi guide when it suggests backing up partition 5 as EKS. But it may not matter as long as the sizes and numbers are right...)
Partitionator said:
And would you mind hitting the Thanks Button? It costed me many houres to find out how to get it in nvflash mode again and I wrote the post before I rewrote my bootloader
Click to expand...
Click to collapse
Absolutely; in fact, if you have a PayPal (you can PM me), I'd like to buy you a beer or something. I appreciate your help over the holidays after I was feeling ignored (and at a certain point, ridiculed) for a couple days. We're developers, we play with things we're not supposed to, and sometimes that means we brick our devices. But I've certainly learned a lot.

TheDj408 said:
I did the method right... I was able to see the files in tab but failed to get them in pc... So Iflashed ooriginal stock bootloader... I meant this...
Click to expand...
Click to collapse
I'm glad that worked for you! For the record I got a signature verification error when I tried to do this originally; some other users on the androidroot.mobi thread got one too. As mentioned, if you have issues flashing the bootloader with fastboot you can do it with nvflash --download 4; another user said this precluded using fastboot again in the future but I find that somewhat dubious.

How to unbrick
So here is the shorten way to recover your device from a Fullbrick:
First: I´m not an expert for that and this is the result of many houres of testing, so I don´t think its the best way to unbrick, but at the moment its the only one and it works.
And I can saftly say if you don't have the blob bin and you screwed up your bootloader I can't help you, nobody can help you, you have to buy a new Mainboard. If you have your blobs follow this guide:
you need:
your blob.bin with bootloader.ebt and recovery.bct
Linux (only to generate your flash.cfg)
nvflash binarays from here: https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
a working bootloader.img from a factory image and a boot.img (you can use one from a factory image) (I used 4.4, the bootloaders in 4.3 and 4.4.2 are corrupt!)
I recommed to use the boot.img of your actual installed rom/kernel.
First you need to generate your flash.cfg. I've done this wit dump_bcd under Linux. I got this with the package cbootimage under Kubuntu.
I generated it from my recovery.bct. After that you have to remove the line that starts with type from the device section in the flash.cfg.
(maybe someone wants to write this part more accurate because bct_dump doesn't work anymore on my PC)
If you have a 16GB Nexus 7, I think you can use the attached one (you have to rename it), but no guarantee if it doesn't work.
Than you put all this files together in a folder (nvflash, blob.bin, bootloader.ebt, recovery.bct, boot.img, bootloader.img/bootloader-grouper-4.23.img, flash.cfg).
Than you go with a terminal there. Under windows you just have to remove the sudo ./ at the begining of the commands and maybe you should run it as Admin.
First we bootstrap it to the nvflashmode. Of cause your device has to be in APX Mode.
WARNING: If you execute this command you have to reflash the bootloader even if you have a working installed because it will wipe your installed bootloader (I think)
Code:
sudo ./nvflash --setbct --create --configfile flash.cfg --bl bootloader.ebt --bct recovery.bct --blob blob.bin
You can see I used the --creatte command there. It will fail (so nothing will be wiped, but im not responsibile if it will wipe something) and its only there to allow me to use the --setbct command.
After this command you should see Google on your device and your terminal should produce a output like that (the error ist as said from create):
Code:
Nvflash v1.13.87205 started
Using blob v1.13.00000
chip uid from BR is: 0x0000000000000000015d2bc285340e0f
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x83
chip uid: 0x0000000000000000015d2bc285340e0f
macrovision: disabled
hdcp: enabled
jtag: disabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 1
device config fuse: 17
sdram config strap: 0
sending file: recovery.bct
- 6128/6128 bytes sent
recovery.bct sent successfully
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: bootloader.ebt
- 2146912/2146912 bytes sent
bootloader.ebt sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 0 3
failed executing command 11 NvError 0x120002
command failure: create failed (bad data)
bootloader status: specified device is invalid (code: 6) message: nverror:0x4 (0x4) flags: 0
The next command will flash a kernel (however without flashing a kernel it won't go to fastboot mode) and than bring set your device into fastboot mode. You have to hold Vol- after/while hitting enter till its in fastboot mode. If you don't hold vol- it will boot to android and you have to start from the begining.
Code:
sudo ./nvflash --resume --download 8 boot.img --go
Now you should be in fastboot mode and the last step is very easy:
simply reflash the bootloader:
Code:
fastboot flash bootloader bootloader.img
or in case of the lastet bootloader
Code:
fastboot flash bootloader bootloader-grouper-4.23.img
Now your device should be unbricked
If not you can try to bootstrap it again to nvflash mode and than flash your bricksafe.img
Code:
nvflash --resume --rawdevicewrite 0 2688 bricksafe.img
And if you need you can reflash the other backed up Partitions too:
Code:
nvflash --resume --download 5 eks.img
nvflash --resume --download 13 factory-config.img
nvflash --resume --download 14 mda.img
After that your device should at least go to fastboot mode again If not let me know and I will try to help you.
If I helped you please hit the thank button, it took me a few days to test this all and it was a lot of work to write this. And please thank the guys that created flatline too, they are the true geniuses .
EDIT: If you have trouble with this way, try (in nvflashmode) to download the flatline recovery to partition 7 (it will straigth boot to ist) and reinstall the flatlinebootloader.
I onetime I unbricked my device the firstway I hat terrible lags, after, and the only way I found to fix them was to reflash the flatlinebootloader (after that i could flash any bootloader without lags)...

heterodoxy said:
Absolutely; in fact, if you have a PayPal (you can PM me), I'd like to buy you a beer or something. I appreciate your help over the holidays after I was feeling ignored (and at a certain point, ridiculed) for a couple days. We're developers, we play with things we're not supposed to, and sometimes that means we brick our devices. But I've certainly learned a lot.
Click to expand...
Click to collapse
I don't have a Paypal account at the moment but if I had I would donate this http://forum.xda-developers.com/member.php?u=2677399 for his nexushd2 roms. So if you want you can do this donation for me
Or you donate direkt to the flatline guys, as I said they are the true geniuses...
heterodoxy said:
I'm glad that worked for you! For the record I got a signature verification error when I tried to do this originally; some other users on the androidroot.mobi thread got one too. As mentioned, if you have issues flashing the bootloader with fastboot you can do it with nvflash --download 4; another user said this precluded using fastboot again in the future but I find that somewhat dubious.
Click to expand...
Click to collapse
I made download 4 many times for testing with my own backup of this partition. The first time it bricked my device. I made the backup with unlocked bootloader but flashed it back with locked bootloader... You should definetly make the bricksafe.img and a Backup of all Partitions before you flash on this... But after I bricked my device with that I was still able to boot with wheelie and the blob.
But for you I will try to flash an old bootloader on this part an see what happens
EDIT: the 4.3 (JWR66Y) Factory Image for nakasi has a broken bootloader. And if you try to flash it you will get a signature missmatch... (for that reason i recommed the 4.4.2 factory image) Maybe he only tryed to flash this bootloader... And I'm very angry on Google because this faulty bootloader is still online maybe you want to leave a Feedback on the download Page of the factory images: https://developers.google.com/android/nexus/images?hl=de#nakasijwr66y
EDIT2: I flashed bootloader 3.41 via nvflash. It worked and the bootloader booted. But as I tryed to flash the 4.23 from 4.4.2 (KOT49H) and got signature missmatch. But I could reflash the 3.41 again via fastboot now I will try diffrent bootloaders...
EDIT3: Bootloader 4.18 from 4.2.2 (JDQ39) works to... It seems there is something wrong with the 4.23 Bootloader google puts in it factory images...
EDIT4: Bootloader 4.23 from 4.4 (KRT16S) works but 4.23 from 4.4.2 (KOT49H) and 4.23 from 4.3 (JWR66Y) not...

Partitionator said:
The next command will flash a kernel (however without flashing a kernel it won't go to fastboot mode) and than bring set your device into fastboot mode. You have to hold vol- after/while hitting enter till its in fastboot mode. If you don't hold vol- it will boot to android and you have to start from the begining.
Code:
sudo ./nvflash --resume --download 8 boot.img --go
Now you should be in fastboot mode and the last step is very easy:
simply reflash the bootloader:
Code:
fastboot flash bootloader bootloader.img
or in case of the lastet bootloader
Code:
fastboot flash bootloader bootloader-grouper-4.23.img
Now your device should be unbricked
Click to expand...
Click to collapse
Brilliant! Of course I missed the HOLD VOL- part the first time (bolding for everyone else ) and it booted straight into Android, but the fact that it could even do that filled me with glee. Did it again and it put me in the 4.13 bootloader. I flashed the 4.18 stock bootloader that had been on the device before and for some reason it said "Signature match." this time! Don't know why but not complaining!
These instructions should be stickied; we had a guide for getting the nvflash blobs but not for what to do with them, especially when wheelie doesn't work! (I did try --rawdevicewrite early on to flash bricksafe.img back and for some reason it didn't work, but these steps are even more intuitive.) Thanks for saving my life!

heterodoxy said:
Brilliant! Of course I missed the HOLD VOL- part the first time (bolding for everyone else ) and it booted straight into Android, but the fact that it could even do that filled me with glee. Did it again and it put me in the 4.13 bootloader. I flashed the 4.18 stock bootloader that had been on the device before and for some reason it said "Signature match." this time! Don't know why but not complaining!
These instructions should be stickied; we had a guide for getting the nvflash blobs but not for what to do with them, especially when wheelie doesn't work! (I did try --rawdevicewrite early on to flash bricksafe.img back and for some reason it didn't work, but these steps are even more intuitive.) Thanks for saving my life!
Click to expand...
Click to collapse
Read the last edits in my post before: many 4.23 Bootloaders are brocken and that is causing the signiture missmatch, because of that your 4.18 bootloader worked... You can use 4.23 Bootloader from the 4.4 Factory Image
But now the irony: it seems that I fullbricked my device with forcing a flash of a brocken bootloader via nvflash :S I can´t even enter the APX Mode it doesn´t shows up in any kind...
EDIT: Got APX Mode again
EDIT2: Oh you said 4.13 and not 4.23 Bootloader... Where did you get this bootloader from? I couldn´t find one with that version in a Factory image. Or did you used that modified Bootloader that was used to dump the blobs? Because that would make sense, this Bootloader is modified and so the Googles signiture is brocken
EDIT3: After testing all of the grouper factory-images (and indentifying the Bootloader from 4.3 and 4.4.2 as brocken I want to test ALL the OTA Updates from here: http://forum.xda-developers.com/showthread.php?t=1745781 First by flashing the bootloader it contains with fastboot, than flashing the whole OTA-Package over adb-sideload (of course I have to flash the corresponding Android Version before) and than via nvflash...
If you want you can help me, because I have to do things for school and so I don´t have more time for playig with bootloaders, but you should make a Backup of every bit of your device .
And every time I brick my device via flashing a brocken bootloader via nvflash I have trouble entering APX Mode....
EDIT4: I´m not able to enter APX Mode again... I feel just to dump to press two buttons...
EDIT5: I´m trying hard since a houre to get in APX Mode but nothing ;( - but why? APX must work, its in the ROM...

Partitionator said:
Read the last edits in my post before: many 4.23 Bootloaders are brocken and that is causing the signiture missmatch, because of that your 4.18 bootloader worked... You can use 4.23 Bootloader from the 4.4 Factory Image
Click to expand...
Click to collapse
I only ever tried to flash the 4.18 bootloader that was previously on the device. I knew there was a possibility others were broken as mentioned in the original thread. It gave me a signature mismatch before, it doesn't now. Again, I don't know why but c'est la vie.
Partitionator said:
But now the irony: it seems that I fullbricked my device with forcing a flash of a brocken bootloader via nvflash :S I can´t even enter the APX Mode it doesn´t shows up in any kind...
Click to expand...
Click to collapse
Oh no! As we just proved, that shouldn't be able to happen!
Partitionator said:
EDIT2: Oh you said 4.13 and not 4.23 Bootloader... Where did you get this bootloader from? I couldn´t find one with that version in a Factory image. Or did you used that modified Bootloader that was used to dump the blobs? Because that would make sense, this Bootloader is modified and so the Googles signiture is brocken
Click to expand...
Click to collapse
The one on the device (and I guess in bootloader.ebt) was the flatline 4.13 bootloader. I was trying to put 4.18 on top of it. I would think the signature mismatch would be done on the new bootloader not the existing one. But either way, flashing the exact same bootloader on top of the exact same bootloader works now.
Partitionator said:
If you want you can help me, because I have to do things for school and so I don´t have more time for playig with bootloaders, but you should make a Backup of every bit of your device .
Click to expand...
Click to collapse
Sure, I'll try to do that when I have time.
Partitionator said:
EDIT5: I´m trying hard since a houre to get in APX Mode but nothing ;( - buty whay APX must work its in the ROM...
Click to expand...
Click to collapse
I'm wondering if you're just in some really strange run state. Have you tried disconnecting the battery, leaving it disconnected for a minute, re-connecting it, and then trying to boot into APX mode again?

please help

I made a nonsense of wanting to return to jelly bean KitKat with rsd lite and gave me an error and every time I turn on the initial cel fastboot .... as usual do to restart please help

c_v_S said:
I made a nonsense of wanting to return to jelly bean KitKat with rsd lite and gave me an error and every time I turn on the initial cel fastboot .... as usual do to restart please help
Click to expand...
Click to collapse
Are you on an unlocked bootloader? If not, you cannot downgrade.

You can't downgrade even with an unlocked bootloader. Just tried this morning and got a security downgrade error or somesuch.
He's probably getting a flash failed error. Easiest way to fix that is just to successfully flash something simple like the logo.
fastboot flash logo logo.bin

You CAN flash back to JB from KK if you have an unlocked bootloader using RSD, I've done it a few times when I tried KK.
I used VRZ_XT907_9.8.1Q-94-1_CFC.xml and removed these lines.
<step var="max-download-size" operation="getvar"/>
<step var="fb_mode_set" operation="oem"/>
<step operation="flash" MD5="FB3D9083F1B5890BBF2FA8617D31A70A" filename="gpt_main0.bin" partition="partition"/>
<step operation="flash" partition="tz" filename="tz.mbn" MD5="474F31095C8146D1F86D0E5CE72B878F" />
Click to expand...
Click to collapse
Quick Edit: These two posts helped me
http://forum.xda-developers.com/showpost.php?p=52663683&postcount=181
http://forum.xda-developers.com/showpost.php?p=52607724&postcount=222
Goodluck :good:

Seriiez said:
I used VRZ_XT907_9.8.1Q-94-1_CFC.xml and removed these lines.
Click to expand...
Click to collapse
How did you know which lines were safe to omit and which to keep?
I tried just flashing system.img by itself, apparently that alone was not enough for it to boot.

GnatGoSplat said:
How did you know which lines were safe to omit and which to keep?
I tried just flashing system.img by itself, apparently that alone was not enough for it to boot.
Click to expand...
Click to collapse
I updated my post to include where I got the info from.

bricked xt902 (softbank 201m)

Hi everyone!
I have XT902 after trying unlock. Now it is booting up only in fastboot and recovery. Factory firmwares for xt902 are not flashing at all (only recovery partition is). BUT i can flash any partition from VERIZON_XT907_4.4.2_KPA20.10.1 except boot, recovery, system
Does anybody have XT902, updated to official 4.4.2 via OTA? With locked boot?
Please upload dumps of partitions boot, recovery, system
Not yet for 4.4.2 firmware via RSD, but 4.4.2 for this machine like there - information from technical support.
It is necessary to restore my brick.

also any OTA update .zip files for this phone are can be useful.

simbasacuk said:
Does anybody have XT902, updated to official 4.4.2 via OTA? With locked boot?
Click to expand...
Click to collapse
There is no 4.4.2 for the XT902 and according to Motorola never will be.
Here is the latest XML (it's still 4.0.4) and here is the latest OTA to 4.1.2.

simbasacuk said:
Hi everyone!
I have XT902 after trying unlock. Now it is booting up only in fastboot and recovery. Factory firmwares for xt902 are not flashing at all (only recovery partition is). BUT i can flash any partition from VERIZON_XT907_4.4.2_KPA20.10.1 except boot, recovery, system
Does anybody have XT902, updated to official 4.4.2 via OTA? With locked boot?
Please upload dumps of partitions boot, recovery, system
Not yet for 4.4.2 firmware via RSD, but 4.4.2 for this machine like there - information from technical support.
It is necessary to restore my brick.
Click to expand...
Click to collapse
Which bootloader version is installed?
Sent from my XT912 using Tapatalk

sd_shadow, i'm not sure. How to check?

simbasacuk said:
sd_shadow, i'm not sure. How to check?
Click to expand...
Click to collapse
see Attached screenshot

10.9B(*) (sha-61146a2, 2014-08-25
that's i have in this string. not surwe, but look's like 4.4.2 boot.
stock firmwares aren't flashing: boot get "failed preflash validation" and system get "PIV block validation for system failed"
trying OTA by link from recovery FAILed too =(
Any idea?
*boot status code 0

1) Fully charged phone
2) Used Motorola cable
3) Upgrade Moto drivers to latest version
4) Use newest Firmware
5) Used RSDLite 6.6 (newer maybe better) with the following settings:
Flash options: Restart after flexing and TI Blank flash
Use image files and delete files on exit
if flash still fails try
unzip firmware
open file VZW_xxxxxxxxxxxx.xml with a notepad (notepad++)
locate and remove 3 following lines :
Code:
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="....MD5 sum here...." />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="...MD5 sum here...." />
save changes in notepad, close notepad
Open RSD Lite and select edited .xml file to flash [email protected]k3nny2k
simbasacuk said:
10.9B(*) (sha-61146a2, 2014-08-25
that's i have in this string. not surwe, but look's like 4.4.2 boot.
stock firmwares aren't flashing: boot get "failed preflash validation" and system get "PIV block validation for system failed"
trying OTA by link from recovery FAILed too =(
Any idea?
*boot status code 0
Click to expand...
Click to collapse
Sent from my XT912 using Tapatalk

phone retured FAIL =(
BUT 4.4.2_KPA20.10.1 for XT907 IS flashing (all partitions except boot and system)
any idea what to do?

ok, now i need for OTA update for telstra xt905
looks like mainboard of my phone is xt905. need to check by flashing it via recovery.
Can somebody share link for ANY xt905 OTA update?
http://forum.xda-developers.com/showpost.php?p=38054477&postcount=115
link for .zip is dead unfortunatly. looking the same.

sd_shadow said:
1) Fully charged phone
2) Used Motorola cable
3) Upgrade Moto drivers to latest version
4) Use newest Firmware
5) Used RSDLite 6.6 (newer maybe better) with the following settings:
Flash options: Restart after flexing and TI Blank flash
Use image files and delete files on exit
if flash still fails try
unzip firmware
open file VZW_xxxxxxxxxxxx.xml with a notepad (notepad++)
locate and remove 3 following lines :
Code:
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="....MD5 sum here...." />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="...MD5 sum here...." />
save changes in notepad, close notepad
Open RSD Lite and select edited .xml file to flash [email protected]k3nny2k
Sent from my XT912 using Tapatalk
Click to expand...
Click to collapse
Hay I have tried a lott to do it by the total screen looks like this
AP Fastboot Flash Mode ($)
10.9A(*) (sha-03216fb,2012-10-17 20:35:09)
eMMC Info: Size 8GB
Device is LOCKED, Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Sticky bit fastboot
usb connected
Partition (boot) Security Version Downgraded
preflash validation failed for boot
=================================
Please help me, i have tried many ways including using XML to Bat file by Rootjunky

xt902 bricked
talvigi said:
Hay I have tried a lott to do it by the total screen looks like this
AP Fastboot Flash Mode ($)
10.9A(*) (sha-03216fb,2012-10-17 20:35:09)
eMMC Info: Size 8GB
Device is LOCKED, Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Sticky bit fastboot
usb connected
Partition (boot) Security Version Downgraded
preflash validation failed for boot
=================================
Please help me, i have tried many ways including using XML to Bat file by Rootjunky
Click to expand...
Click to collapse
i have xt902 stuck on fastboot mode... and i have ota update tooo... but i dont know how to flash it... via fastboot mode... can i flash this ota update via fastboot mode... help me plx to save my phone
---------- Post added at 12:38 PM ---------- Previous post was at 12:36 PM ----------
simbasacuk said:
Hi everyone!
I have XT902 after trying unlock. Now it is booting up only in fastboot and recovery. Factory firmwares for xt902 are not flashing at all (only recovery partition is). BUT i can flash any partition from VERIZON_XT907_4.4.2_KPA20.10.1 except boot, recovery, system
Does anybody have XT902, updated to official 4.4.2 via OTA? With locked boot?
Please upload dumps of partitions boot, recovery, system
Not yet for 4.4.2 firmware via RSD, but 4.4.2 for this machine like there - information from technical support.
It is necessary to restore my brick.
Click to expand...
Click to collapse
i know there is an update of 4.4.2 and i have it but i dont know how can i flash it becuse boootloader is locked and phone is stuck on fastboot mode... i can upload it if u say

Bricked my Motorola maxx 2

Hi every body I have bricked my Motorola maxx 2. I'm now stucked in bootloader menu. Recovery is not working. Tried to flash with rsd lite but it's not detecting my phone although it is shown in computer. Also tried fastboot but it says permission denied. What to do now?

Are you sure you installed the right drivers so that rsd lite sees your phone?

Yes I am sure I have installed correct drivers. Device manager recognized my device

How is your device showing in the device manager? Please give a screenshot.

yes i have uploaded it

Luckily rsd lite is now detecting my phone but it doesn't flash it, it says 2/23 flash fail gpt.bin. Where is problem? What to do

Jamil169 said:
Luckily rsd lite is now detecting my phone but it doesn't flash it, it says 2/23 flash fail gpt.bin. Where is problem? What to do
Click to expand...
Click to collapse
what does it say on the device screen?
complete screen details.

my device shows following message
cmd: oem fb_mode_clear
cmd: getvar:max-sparse-size
cmd: oem fb_mode_set
cmd: getvar:max-sparse-size
cmd: getvar:max-download-size
cmd: download:00008000
cmd: flashartition
version downgraded for primary_gpt

some where on the form i read to edit xml file by deleting following lines before flashing. but even this didnt work
<step operation="getvar" var="max-sparse-size"/>
<step operation="oem" var="fb_mode_set"/>
<step operation="oem" var="fb_mode_clear"/>
If im flashing after deleting these lines follwing message comes in device
cmd: getvar:max-sparse-size
cmd: getvar:max-download-size
cmd: flashartition
version downgraded for primary_gpt

Stock firmware which i downloaded contains 2 xml files, which i have attched here.

Jamil169 said:
my device shows following message
cmd: oem fb_mode_clear
cmd: getvar:max-sparse-size
cmd: oem fb_mode_set
cmd: getvar:max-sparse-size
cmd: getvar:max-download-size
cmd: download:00008000
cmd: flashartition
version downgraded for primary_gpt
Click to expand...
Click to collapse
The device should have
AP Fastboot version
battery status
usb connection status...

AP Fastboot Flash Mode (Secure)
BL: 80.A7 (sha-b550fb9, 2015-07-01 09:56:25)
Baseband: M8936_2020632.44.03.21.58R LUX_VZW_CUST
Product/Variant: lux XT1565 16GB P2C
Serial Number: ZY2227ZPHD
CPU: MSM8939
eMMC: 16GB Samsung RV=07 PV=01 TY=57
DRAM: 2048MB Elpida S8 SDRAM DIE=4Gb
Console [NULL]: null
Battery OK
Device is locked. Status Code: 0
Software status: Official
Connect USB Data Cable

And when I connect the USB it says USB connected

Jamil169 said:
And when I connect the USB it says USB connected
Click to expand...
Click to collapse
Your using LUX_5.1.1_LCD23.118-21.2_cid2_subsidy-DEFAULT_CFC.xml.zip ?

No i tried all these three zip files none is working
DroidMaxx2_XT1565_LUX_VERIZON_5.1.1_LCD23.118-21.2_cid2_subsidy-DEFAULT_CFC.xml.zip
LUX_5.1.1_LCD23.118-21.2_cid2_subsidy-DEFAULT_CFC.xml.zip
LUX_RETASIA_DS_5.1.1_LPD23.118-22_cid7_subsidy-DEFAULT_CFC.xml.zip
One thing more before i bricked it i update it marshmallow

Jamil169 said:
No i tried all these three zip files none is working
DroidMaxx2_XT1565_LUX_VERIZON_5.1.1_LCD23.118-21.2_cid2_subsidy-DEFAULT_CFC.xml.zip
LUX_5.1.1_LCD23.118-21.2_cid2_subsidy-DEFAULT_CFC.xml.zip
LUX_RETASIA_DS_5.1.1_LPD23.118-22_cid7_subsidy-DEFAULT_CFC.xml.zip
One thing more before i bricked it i update it marshmallow
Click to expand...
Click to collapse
None of those will work, if device was on 6.0/Marshmallow
you cannot downgrade firmware with a locked bootloader
Nothing to do until till the correct firmware is available

Is there anyway to unlock the bootloader?

Jamil169 said:
Is there anyway to unlock the bootloader?
Click to expand...
Click to collapse
Not that I'm aware of
Sunshine app is likely the best hope
but I don't think the Maxx 2 (XT-1565) is currently supported
and it would require a working device

Ya maxx 2 is not supported. plenty of thanks for help

6.0 firmware needed for RSD or fastboot ... who can help ?

[Help Thread][Moto G4 Plus] (2016) Ask Any Question, Noob Friendly

This thread has been created
for
Questions & Answers/Troubleshooting
Specific to
Moto G4 Plus
XT1640, XT1641, XT1642, XT1643 XT1644
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters​@strongst​@sd_shadow​...​...​...​
To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.​If you have ROM-related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!​​Supporters: If you want to be put on or off the list, just make a request here in the thread!​Before posting anything, I strongly advise you to read​
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
[Index]Motorola Flashing Utilities, Firmware, and more
[INDEX] Moto G4 Plus
[HELP] thread for custom ROMs
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here. ​

I'm not planning on adding every Rom or Mod,
but if you have a suggestion for other links
Please post them here.
FAQs
UnLocking the Bootloader
ReLocking the Bootloader
https://forum.xda-developers.com/mo...lus-xt1640-43-athene-npj25-93-t3549369/page43
[Fixing] Baseband <not found> / IMEI=0 / No Network After Flash / Issues
Fixing your Moto stuck in Qualcomm QHSUSB_Bulk or qloader mode
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Using Lenovo's MOTO Smart Assistant to Update/Repair/Backup
Custom Roms/Recovery/Root/
Firmware
https://mirrors.lolinet.com/firmware/moto/
Specs

Karumbaiah said:
@sd_shadow great work brother. I'm badly in need of some help from you.
I've got everything right from your tutorial. Except for, when I try to flash the firmware on RSD lite, flashing stops at with an error "Failed flashing process. 3/27 flash partition "gpt.bin" -> Phone returned FAIL"
I'm assuming this is because of a stupidest mistake that I did while I was trying to flash the nougat update zip on my Moto G4 Plus (XT1634). Out of my right sense, I used the firmware downgrade codes while flashing the updated zip. This might have incorrectly flashed the partition, boot image and the recovery image from the update file.
Now I'm stuck with the bootloader which gives my security version downgrade error when I try to flash even the latest MM firmware.
I was somehow able to flash an extracted recovery image from the nougat update zip. But, it just gives me a blank screen when I select the option ' apply update from SD card '
Attached is a picture of the bootloader and recovery screen. Any help in reviving my phone is greatly appreciated.
Click to expand...
Click to collapse
Did you try removing?
Code:
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="....MD5 sum here...." />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="...MD5 sum here...." />
as described in post #6 of my thread?

sd_shadow said:
Did you try removing?
Code:
no
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="....MD5 sum here...." />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="...MD5 sum here...." />
as described in post #6 of my thread?
Click to expand...
Click to collapse
Hi,
Yes. I tried removing those lines. Still did not work. I get the same error for every file (boot, recovery, oem etc.) that RSD lite tries to flash.

Karumbaiah said:
Did you try removing?
Hi,
Yes. I tried removing those lines. Still did not work. I get the same error for every file (boot, recovery, oem etc.) that RSD lite tries to flash.
Click to expand...
Click to collapse
what files are in the xml.zip ?
Sent from my XT1080 using XDA Labs

sd_shadow said:
what files are in the xml.zip ?
Sent from my XT1080 using XDA Labs
Click to expand...
Click to collapse
Hi,
I'm using the Moto_G4_Plus_XT1643_ATHENS_MPJ24.138-63_Stock _Img.zip file for flashing. Below is the list of files that are in this zip file.
adspso.bin
boot.img
Bootloader.img
Flashfile.xml
Fsg.mbn
Gpt.bin
Logo.bin
NON-HLOS.bin
OEM lock.bat
Oem.img
Recovery.img
regulatory_info_default.png
Servicefile.xml
slcf_rev_d_default_v1.0.nvm
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
system.img_sparsechunk.4
system.img_sparsechunk.5
system.img_sparsechunk.6
system.img_sparsechunk.7
PS - Bootloader is locked and there is no way I can unlock it now. I get the message "enable OEM unlock " error. I can't enable it as my phone doesn't boot.

@sd_shadow I'm willing to support in this thread, you can add me to the list :fingers-crossed:

Karumbaiah said:
Hi,
I'm using the Moto_G4_Plus_XT1643_ATHENS_MPJ24.138-63_Stock _Img.zip file for flashing. Below is the list of files that are in this zip file.
adspso.bin
boot.img
Bootloader.img
Flashfile.xml
Fsg.mbn
Gpt.bin
Logo.bin
NON-HLOS.bin
OEM lock.bat
Oem.img
Recovery.img
regulatory_info_default.png
Servicefile.xml
slcf_rev_d_default_v1.0.nvm
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
system.img_sparsechunk.4
system.img_sparsechunk.5
system.img_sparsechunk.6
system.img_sparsechunk.7
PS - Bootloader is locked and there is no way I can unlock it now. I get the message "enable OEM unlock " error. I can't enable it as my phone doesn't boot.
Click to expand...
Click to collapse
I was hoping there was a service.bat
I would setup adb/fastboot tools
see my setting up adb/ fastboot thread and Rootjunky video
links in my thread
Sent from my sailfish using XDA Labs

Setting up Adb and fastboot
http://forum.xda-developers.com/android/general/index-links-setting-using-adb-fastboot-t3495167
then try flashing boot.img
reboot bootloader
then
some of the other files
Sent from my sailfish using XDA Labs

Code:
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_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
... repeat for the rest of the chunks
fastboot erase cache
fastboot reboot
Sent from my sailfish using XDA Labs

sd_shadow said:
Setting up Adb and fastboot
http://forum.xda-developers.com/android/general/index-links-setting-using-adb-fastboot-t3495167
then try flashing boot.img
reboot bootloader
then
some of the other files
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
Hi,
Thanks a lot for taking time in responding to me. just a bit confused here.
My device is already getting detected as a 'Motorola ADB Device,' under device manager. However, when I enter the code 'adb devices ' in Command window, it does not return any devices. Although my phone responds to all adb codes.
Should I still follow the adb and fastboot setup guide?
PS : 'fastboot devices ' code in Command window will show my device code listed.

Karumbaiah said:
Hi,
Thanks a lot for taking time in responding to me. just a bit confused here.
My device is already getting detected as a 'Motorola ADB Device,' under device manager. However, when I enter the code 'adb devices ' in Command window, it does not return any devices. Although my phone responds to all adb codes.
Should I still follow the adb and fastboot setup guide?
PS : 'fastboot devices ' code in Command window will show my device code listed.
Click to expand...
Click to collapse
adb commands are used in recovery and os
fastboot commands are used in bootloader/fastboot mode

sd_shadow said:
adb commands are used in recovery and os
fastboot commands are used in bootloader/fastboot mode
Click to expand...
Click to collapse
I totally understand that. My phone is responding to both adb and fastboot commands. Just that I get errors while in the process of flashing.

Hi everybody
I have installed cm13 on my moto g4 plus xt1642.
I have flashed elementalx-g4-0.07-cm.zip and installed mod wake gestures in xposed.
Here I'm getting a msg that wake gestures are not supported or they haven't been enabled .
Any suggestion is greatly appreciated.

Unable to call using Jio after updating to Nougat (Android 7.0)
Unable to make any calls using jio sim after updating to nougat of android 7.0 although mobile data is working completely fine. Also Jio4GVoice is online and no errors are shown regarding that app. Please help!

After Nougat update, I don't get navigation bar popping up when fingerprint scanner is touched while in full screen mode. For example while watching videos, I used to touch the scanner and navigation bar would pop up. Has this feature been removed?

shoaib033 said:
After Nougat update, I don't get navigation bar popping up when fingerprint scanner is touched while in full screen mode. For example while watching videos, I used to touch the scanner and navigation bar would pop up. Has this feature been removed?
Click to expand...
Click to collapse
On which rom was this for you working, what was your prior rom?

When we get features like pixel phone
Sent from my Moto G (4) using Tapatalk

strongst said:
On which rom was this for you working, what was your prior rom?
Click to expand...
Click to collapse
Preloaded stock marshmallow.

shivam kapoor said:
When we get features like pixel phone
Click to expand...
Click to collapse
When Motorola decides to implement it. Be happy to receive official N rom now.
---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------
shoaib033 said:
Preloaded stock marshmallow.
Click to expand...
Click to collapse
Maybe it's removed as you can't configure too much as the N Stock rom is really near to aosp. Wait for others to confirm, be patient as the rollout has started