Database Users

vz 1060 dev &*^()(**^

I am unlocked
fast boot still works
ok I downloaded the OTA
went to root it and everthign went to hell
the recovery dlahed but would nto entere recoivery
tried a couple differnt twrp
tried cwm
tried other 5.1 recovereis after verifying that they had the same sizes
still wont entere recovery
treid to use the kk factoryu image and "most of it flashed
Code:
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.249s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.114s
C:\Users\Zookeeper\Desktop\android_sdk\XT1060 Moto X\VZW_212.56.26.ghost_verizon.Verizon.en.US>fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.383s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.137s
flashed a different boot image and moto boot image form 5.1 t mobile
still no joy
there is a brazil 1053 which I am told Mosley works. but I cant find it
no 1060 factory image yet.
so has anybody created a factory type image yet. NOT a flashable zip. unless I can get twrp working that wont help me.
FAST BOOT WORKS

I'm not 100% sure, but you may have to use "mfastboot" which is the motorola version of fastboot. You can find it with a quick search.

So you were on 5.1 and downgraded to Kit Kat? You can't downgrade the bootloader.

dcooterfrog said:
I am unlocked
fast boot still works
ok I downloaded the OTA
went to root it and everthign went to hell
the recovery dlahed but would nto entere recoivery
tried a couple differnt twrp
tried cwm
tried other 5.1 recovereis after verifying that they had the same sizes
still wont entere recovery
Click to expand...
Click to collapse
I'm going to stop you right there,.
To install an OTA, you need STOCK reocvery. If you have a 3rd party recovery like TWRP or CWM, the OTA process might reboot your phone into Recovery but it will fall to install.
If you have 4.4.4 on your phone, you need to get that exact Recovery.img and flash it. You can't use a 5.1 recovery because the pre-flash validation checks that happen as part of the OTA will likely complain that its not the right version.
dcooterfrog said:
treid to use the kk factoryu image and "most of it flashed
Code:
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.249s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.114s
C:\Users\Zookeeper\Desktop\android_sdk\XT1060 Moto X\VZW_212.56.26.ghost_verizon.Verizon.en.US>fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.383s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.137s
flashed a different boot image and moto boot image form 5.1 t mobile
still no joy
there is a brazil 1053 which I am told Mosley works. but I cant find it
no 1060 factory image yet.
so has anybody created a factory type image yet. NOT a flashable zip. unless I can get twrp working that wont help me.
FAST BOOT WORKS
Click to expand...
Click to collapse
You can't downgrade from 4.4.4 to 4.4.2 without risking turning your phone into a brick.
What state is your phone in now? WHat bootloader version does it have on it?
If you have bootloader 30.B7, consider downloading the 4.4.4 XT1060 SBF/FXZ moto has on their web site, and visit -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 read post 1 and 2... From Post 2, use the Requirements section, then skip to option 5 to get to stock 4.4.4. then try the OTA

ok lest start over
i was rooted with twrp
i returned to stock and flashed system and recovery from
VZW_212.56.26.ghost_verizon.Verizon.en.US
took both OTAs got onto lolipop seemd to be working
went to flash twrp it said flashed OK
but I could not boot into recovery
tried to laod a cuple differnt recoveries.
then tried to restore the whoel thing
VZW_212.56.26.ghost_verizon.Verizon.en.US
gpt failed
recovery failed
then I tried to install a recovery boot and moto boot frfom a different 5.1. ( after verifying that a couple 5.1 roms had the same size moto boot and boot) flashed but gpt is messed up and wont restore.
either I have broke it or I need a factory image from lollipop
i will try to check my boot loader version. but i bet its updated as a resultof th OTA

got twrp working
does any one have a complete nanadroid of verizon lolipop

got twrp working
does any one have a complete nanadroid of verizon lolipop
slowly am getting back up.
i am not at VZW_212.55.26.ghost_verizon.Verizon.en.US
not 56
Blur_Version.212.166.3.ghost_verizon.Verizon.en.US seems to fail.
ill try flashing system and recovery again.
flashd system, revcovery, boot and motoboot
moto boot failed
update unsuccessful so somthing in moto boot muts ba failing the assert. I think I have a NEWER moto boot.

How did you get TWRP working under 5.1? Someone else had similar issues here:
http://forum.xda-developers.com/moto-x/moto-x-qa/xt1060-recovery-5-1-t3201391

Well that was me... Eventually I got twrp working but I don't know what kind of bastard kitkat lolipop Frankenstein thing it was. Phone will not boot. It is on its way back to motorolla
Sent from my Venue 8 7840 using Tapatalk

Hey bud, when you say the phone won't boot do you mean you can't even boot into the bootloader, or do you mean the screen goes black after the boot animation?
If it's the latter the same thing happened to me today and I know how to fix it.

Won't boot. It went back to Motorola yesterday. Love extended warranty. Backup phone droid incredible 1 with KitKat . loving the 3g
Sent from my ADR6300 using Tapatalk

dcooterfrog said:
Won't boot.
Click to expand...
Click to collapse
I was asking you to clarify what you meant by "won't boot" since that could mean multiple things, but it doesn't matter if you already sent the phone back. Glad you have the extended warranty.

yes extended warranty is great.
sorry by wont boot i meant complete brick, not boot loop. no boo tlogo, no motorolla logo, no bootloader unlocked warning screen. just dark dead, as a doornail.
it wold not even get int eh boot loader.
i have never bricked a phone before. i want trying to downgrade. i have been rooting ( the hard way) since eclair on my lg ally, so not a newb.

[ROM] [STOCK] KDZ V20L 6.0 H901 T - Mobile

Update V20E 6.0 T - Mobile
H901 - T Mobile
V20e (6.0)
https://drive.google.com/open?id=0B3R77elw9JjNSmVsVjhjbWdLcEU
V20j (6.0)
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW1FRFU652MMA4P3503B0ON/H90120j_00_0712.kdz
V20l (6.0)
http://pkg03.lime.gdms.lge.com/dn/d...1478794859&h=59e2525cdab042c7ac78e39941ad3362

Woww. Thánks for sharing

reachedxyz said:
Woww. Thánks for sharing
Click to expand...
Click to collapse
Bày đặt nói tiếng anh

My question you have this here as ROM we are happy is here as promised. But is it rooted or is it just the official download untouched ?
Sent from my LG-H901 using XDA-Developers mobile app

diamantericos said:
My question you have this here as ROM we are happy is here as promised. But is it rooted or is it just the official download untouched ?[/URL]
Click to expand...
Click to collapse
KDZs are factory firmware files, untouched.

Is it possible to root? Bootloader remains unlocked?

jonsat said:
Is it possible to root? Bootloader remains unlocked?
Click to expand...
Click to collapse
Bootloader can be unlocked. No word on root yet

Do you have to have stock recovery to used the kdz file

I'll wait for the rooted stock version, but I'm sure we'll be seeing it this week!

shawn1 said:
Do you have to have stock recovery to used the kdz file
Click to expand...
Click to collapse
I nand back to a stock build thru twrp. Booted to Android ran LG bridge and it worked fine
Sent from my LG-H901 using XDA-Developers mobile app

shawn1 said:
Do you have to have stock recovery to used the kdz file
Click to expand...
Click to collapse
You need to use LGUP for flashing KDZ:
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803

First of all, flashing this KDZ will re-lock the bootloader. It is important to know because if you want unlocked bootloader, you need to execute "fastboot oem unlock" which will wipe all user data.
Secondly, I am surprised to see that TWRP is no longer working after MM update:
Code:
O:\LG\H901>fastboot boot twrp-2.8.7.1-h901.img
downloading 'boot.img'...
OKAY [ 0.732s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.749s
Same error if I try to flash TWRP as well. Did somebody successfully manage to root this version?
Edit: I've also tried with latest TWRP available from this thread:
http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-updated-twrp-v3-0-1-0-t3350825
Maybe we need a newer build of TWRP based on MM sources?

sikander3786 said:
First of all, flashing this KDZ will re-lock the bootloader. It is important to know because if you want unlocked bootloader, you need to execute "fastboot oem unlock" which will wipe all user data.
Secondly, I am surprised to see that TWRP is no longer working after MM update:
Code:
O:\LG\H901>fastboot boot twrp-2.8.7.1-h901.img
downloading 'boot.img'...
OKAY [ 0.732s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.749s
Same error if I try to flash TWRP as well. Did somebody successfully manage to root this version?
Edit: I've also tried with latest TWRP available from this thread:
http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-updated-twrp-v3-0-1-0-t3350825
Maybe we need a newer build of TWRP based on MM sources?
Click to expand...
Click to collapse
i got that same error when trying to fastboot boot TWRP. however, i then realized that my bootloader had been relocked. i assume you re-unlocked yours tho. i have tons of Google Play music downloaded for offline listening, so i'm trying to see if i can back that up before unlocking.
edit: moving google music to sdcard, will unlock and give it a try later on

YrrchSebor said:
i got that same error when trying to fastboot boot TWRP. however, i then realized that my bootloader had been relocked. i assume you re-unlocked yours tho. i have tons of Google Play music downloaded for offline listening, so i'm trying to see if i can back that up before unlocking.
edit: moving google music to sdcard, will unlock and give it a try later on
Click to expand...
Click to collapse
Yes, I unlocked the bootloader again. As per siraltus' post in the thread linked below, we need a new MM compatible TWRP:
http://forum.xda-developers.com/tmo...recovery-updated-twrp-v3-0-1-0-t3350825/page2
Means no rooting for now.

sikander3786 said:
You need to use LGUP for flashing KDZ:
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Click to expand...
Click to collapse
LG Flash tool won't work?
Sent from my LG-H901 using XDA-Developers mobile app

SmileBigNow said:
LG Flash tool won't work?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
No I don't think so. Not with MM KDZ.

sikander3786 said:
First of all, flashing this KDZ will re-lock the bootloader. It is important to know because if you want unlocked bootloader, you need to execute "fastboot oem unlock" which will wipe all user data.
Secondly, I am surprised to see that TWRP is no longer working after MM update:
Code:
O:\LG\H901>fastboot boot twrp-2.8.7.1-h901.img
downloading 'boot.img'...
OKAY [ 0.732s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.749s
Same error if I try to flash TWRP as well. Did somebody successfully manage to root this version?
Edit: I've also tried with latest TWRP available from this thread:
http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-updated-twrp-v3-0-1-0-t3350825
Maybe we need a newer build of TWRP based on MM sources?
Click to expand...
Click to collapse
YrrchSebor said:
i got that same error when trying to fastboot boot TWRP. however, i then realized that my bootloader had been relocked. i assume you re-unlocked yours tho. i have tons of Google Play music downloaded for offline listening, so i'm trying to see if i can back that up before unlocking.
edit: moving google music to sdcard, will unlock and give it a try later on
Click to expand...
Click to collapse
sikander3786 said:
Yes, I unlocked the bootloader again. As per siraltus' post in the thread linked below, we need a new MM compatible TWRP:
http://forum.xda-developers.com/tmo...recovery-updated-twrp-v3-0-1-0-t3350825/page2
Means no rooting for now.
Click to expand...
Click to collapse
BadNews: I hate to be the one to tell you all this, But LG locked some of the fastboot commands... It has nothing to do with TWRP..
you all gota understand that twrp has its own kernel regrdless of what rom you run............. So ROM and Recovery dont tie into eather other..
Nexus 7 did this same thing some time ago.. the fastboot commands are locked up.. LG did the same on the G3 when we figured out how to get around the download mode.........
anyhow, if you even use< fastboot continue >
you will get same error:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.018s
So now, we are all should I say, F----d Up............. I even use my G3 rooting knowledge to gain root... But that method failed tooo, and it uses the download mode come port way..
seems LG though of everything this time around........ But you can count on one thing,, WE WILL HAVE ROOT again.................
We have something the other devices dont have.,. We can unlock our bootloaders.. So, we just gota wait a bit.....................

Eliminater74 said:
BadNews: I hate to be the one to tell you all this, But LG locked some of the fastboot commands... It has nothing to do with TWRP..
you all gota understand that twrp has its own kernel regrdless of what rom you run............. So ROM and Recovery dont tie into eather other..
Nexus 7 did this same thing some time ago.. the fastboot commands are locked up.. LG did the same on the G3 when we figured out how to get around the download mode.........
anyhow, if you even use< fastboot continue >
you will get same error:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.018s
So now, we are all should I say, F----d Up............. I even use my G3 rooting knowledge to gain root... But that method failed tooo, and it uses the download mode come port way..
seems LG though of everything this time around........ But you can count on one thing,, WE WILL HAVE ROOT again.................
We have something the other devices dont have.,. We can unlock our bootloaders.. So, we just gota wait a bit.....................
Click to expand...
Click to collapse
That's bad, real bad.
The first thing most of us will want to know here is if downgrade to 5.1.1 is safe? If yes, which build? I don't think we have many options there.
For rooting, can we try opening the LG Com port using the old 9% method? Maybe then we can try flashing a root injected system image? I am away from PC so can't try this right now. Won't be asking otherwise.

I will wait for a flashable zip. And hope it will have root. Or maybe stick with the Korean Mm port
Sent from my LG-H901 using XDA-Developers mobile app

Yep. Flashable zip is the way to go for now (if it somehow becomes available). I am not sure how to read system dump from a locked-down device and create a Flashable zip.
I will try downgrading to 5.1.1 in the morning.
Just wondering, why allow bootloader unlock if LG and T-Mobile want to lock down everything else?

Screwed up phone while rolling back Android 7 - help?

So for some background, I was on EMUI 4.1 and successfully flashed to EMUI 5.
Then, I wanted to rollback so I flashed recovery again and stock firmware. I tried flashing with fastboot and didn't work. I tried using Huawei recovery 3-button method, no luck either.
Errors using fastboot flashing:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system "F:\SYSTEM.img"
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (445721 KB)...
OKAY [ 17.780s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 17.822s
Click to expand...
Click to collapse
Error with 3-button method:
Software install failed!
Incompatibility with current version.
Please download the correct update package.
Click to expand...
Click to collapse
When I was booting into Revolution recovery, I could not mount SD card and some other partitions so maybe that has something to do with the 3-button method problem... Furthermore, I don't know how to check which version exactly my phone is, all I know is that it was VNS-L31.
Now I'm stuck with a phone that is constantly rebooting so how do I proceed?

First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.

Schlengge said:
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Click to expand...
Click to collapse
Have just solved the problem with the steps from here.
From my understanding, it seems that I lost almost everything, device info, OEM info, recovery... So no technique was working.
The solution in brief was:
1. Go into bootloader to flash recovery (I used Revolution Recovery)
2. In recovery, flash OEM info.
3. Then used the 3-button method to install stock version for the appropriate model (which I could see from OEM info).
4. Unlocked bootloader, triggering a factory reset. (I was stuck in infinite boot before this point.)
As you say Schlengge, it is a matter of using the right files! Thanks. Problem solved.

[Solved] Bricked and can't write system

I erased everything in an attempt to unbrick it but that was a mistake. What I have tried and results:
-twrp recovery tried to install the latest stock firmware but got error with mounting system.
-fastboot flash update update.zip didn't solve it
-fastboot seperatly flashing each image, extracted by the update extractor tool. Result:
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (451240 KB)...
OKAY [ 23.882s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 23.958s​-fastboot -w to reformat and try again. Result:
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.012s​OEM is unlocked, I have tried updating from the SD and using the three buttons but I get the wrong format error. Downloaded the MM version as well but I get the incompatible error. Can't download from the erecovery or Hi-Suite. Help please

Have you tried flashing the original oeminfo and then installing with dload? Or maybe try fastboot update method

d0nefufe said:
Have you tried flashing the original oeminfo and then installing with dload? Or maybe try fastboot update method
Click to expand...
Click to collapse
Which original one though? I've been trying and downloaded any Full firmware I could find using a firmware finder, for my VNS-L31 but using the force update method in download so far all of them return an error: Incompatible with current version. I have also tried the fastboot update and separately flashing each file in the update.app . None work so far. I keep trying.

Badwolf9 said:
Which original one though? I've been trying and downloaded any Full firmware I could find using a firmware finder, for my VNS-L31 but using the force update method in download so far all of them return an error: Incompatible with current version. I have also tried the fastboot update and separately flashing each file in the update.app . None work so far. I keep trying.
Click to expand...
Click to collapse
If you're on Nougat, try flashing it's files through fastboot. It worked for me, MM system.img gave me an error, but nougat flashed fine.

I believe ur in nougat beta... Just flash oem info and flash again the nougat from there you can start again and downgrade peacefully

your bootloader is locked

Sh0m1 said:
If you're on Nougat, try flashing it's files through fastboot. It worked for me, MM system.img gave me an error, but nougat flashed fine.
Click to expand...
Click to collapse
Thank you! I followed the instructions here with a slight variation. Because trying to install the update.zip file always gave me errors I extracted the update.APP with the update extractor tool and flashed cache,system,boot with fastboot. Then I opened the custom recovery, installed the other zip file and continued as instructed.

mjz2cool said:
your bootloader is locked
Click to expand...
Click to collapse
No it wasn't. This was my first thought as well.

Badwolf9 said:
No it wasn't. This was my first thought as well.
Click to expand...
Click to collapse
how did you check if it was unlocked? if it says so in fastboot mode it can be incorrect, even when you relock the bootloader it still says unlocked

mjz2cool said:
how did you check if it was unlocked? if it says so in fastboot mode it can be incorrect, even when you relock the bootloader it still says unlocked
Click to expand...
Click to collapse
fastboot oem device-info
Also if it was locked I wouldn't be able to flash anything.

d0nefufe said:
Have you tried flashing the original oeminfo and then installing with dload? Or maybe try fastboot update method
Click to expand...
Click to collapse
where can I find the oeminfo file?

islandman75 said:
where can I find the oeminfo file?
Click to expand...
Click to collapse
This is the L21 - SingleSIM:
https://www.dropbox.com/s/97uad8vc3pwppnq/oeminfoORIGINAL.img?dl=0
And the L21 - DualSIM:
https://www.dropbox.com/s/fq99atzszg2sq1y/oeminfoDUAL.img?dl=0

Hard bricked moto g4 plus x1664?

I started my root journey with twrp super user and elementalx i flashed super user with the intention of installing magisk then i realized magisk is a root thing and i had to uninstall super user so i flashed stock rom and tried to install magisk again but then it failed i'm not 100% sure why it just wouldn't boot after install so i tried updating my device and then it hard bricked and i had to reinstall the bootloader and now when i try to flash stock the partition table is messed up and people on xda say i need the version that was meant for my phone but i've tried every 7.0 version i can find for x1664 and nothing works, so my question is, How can i get my phone working again, and how can i install magisk from here?

greekgodx said:
I started my root journey with twrp super user and elementalx i flashed super user with the intention of installing magisk then i realized magisk is a root thing and i had to uninstall super user so i flashed stock rom and tried to install magisk again but then it failed i'm not 100% sure why it just wouldn't boot after install so i tried updating my device and then it hard bricked and i had to reinstall the bootloader and now when i try to flash stock the partition table is messed up and people on xda say i need the version that was meant for my phone but i've tried every 7.0 version i can find for x1664 and nothing works, so my question is, How can i get my phone working again, and how can i install magisk from here?
Click to expand...
Click to collapse
Were you able to sucessfully use blankflash and load a different bootloader?
Have you ever updated to soak test?

Heeth21 said:
Were you able to sucessfully use blankflash and load a different bootloader?
Have you ever updated to soak test?
Click to expand...
Click to collapse
I do have bootloader up and running from blankflash but the partition table is non existent so i can't even flash anything like twrp to recovery

Also, no i do not have soak test

greekgodx said:
Also, no i do not have soak test
Click to expand...
Click to collapse
Download the stock rom from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
and follow that thread. First flash bootloader and gpt then reboot bootloader and then flash stock rom

Heeth21 said:
Download the stock rom from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
and follow that thread. First flash bootloader and gpt then reboot bootloader and then flash stock rom
Click to expand...
Click to collapse
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.070s
whenever it gets to gpt.bin

greekgodx said:
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.070s
whenever it gets to gpt.bin
Click to expand...
Click to collapse
Were you able to flash bootloader first??
Also I hope you are just flashing bootloader and gpt.bin only from the downloaded stock rom only from the link i posted earlier.

Heeth21 said:
Were you able to flash bootloader first??
Also I hope you are just flashing bootloader and gpt.bin only from the downloaded stock rom only from the link i posted earlier.
Click to expand...
Click to collapse
I got the thing you post earlier and was able to boot and do all that stuff then when i tried flashing magisk from twrp it said it worked then when i went to reboot it just goes to black and no longer boots but i can still go into twrp and all that

greekgodx said:
I got the thing you post earlier and was able to boot and do all that stuff then when i tried flashing magisk from twrp it said it worked then when i went to reboot it just goes to black and no longer boots but i can still go into twrp and all that
Click to expand...
Click to collapse
That's because Magisk causes boot issues on Stock Nougat without custom kernel.
Reboot to TWRP then flash Magisk uninstaller (from magisk thread xda) and check if it boots. If it does not boot, then flash boot.img only from the Stock ROM and it should boot fine:
Code:
fastboot flash boot boot.img
After that install Elemental X Kernel first and then install Magisk and you will be able to boot properly.

Heeth21 said:
That's because Magisk causes boot issues on Stock Nougat without custom kernel.
Reboot to TWRP then flash Magisk uninstaller (from magisk thread xda) and check if it boots. If it does not boot, then flash boot.img only from the Stock ROM and it should boot fine:
Code:
fastboot flash boot boot.img
After that install Elemental X Kernel first and then install Magisk and you will be able to boot properly.
Click to expand...
Click to collapse
Thank you sir it now works fine and i have magisk installed.