Database Users

Constant FC's on most ROM installations..

Hey guys, I ran into a rather odd issue yesterday and can't for the life of me figure out how to get my phone back to normal..
I upgraded TWRP to 3.0.2-0, wiped data, system, dalvik/cache, and attempted to install AOSiP 4.1 + Banks 4/08 Gapps, but after the boot, I get "Unfortunately SetupWizard has stopped", and after getting through the setup, "Unfortunately Theme Provider has stopped", if I click the Theme app it FC's.
This happens on EVERY single ROM I try to install, except Resurrection Remix. (The ROM I was on before flashing AOSiP.) I have tried going back to stock MHC19Q and starting fresh, but I still get FC's. I have also tried every recent TWRP, and MultiROM TWRP. Nothing is working.
Please help...
Edit: @big nu has the same issue..
https://tapatalk.com/shareLink?url=...share_tid=3357511&share_fid=3793&share_type=t

Are you fastbooting the factory images or trying to flash the stock firmware through twrp? If you haven't, fastboot the images including the recovery.

Eric214 said:
Are you fastbooting the factory images or trying to flash the stock firmware through twrp? If you haven't, fastboot the images including the recovery.
Click to expand...
Click to collapse
I fastboot everything. I flashed the stock image from my PC but still no luck...

Perhaps any layers installed?
If so, try removing them from inside TWPR and see if it boots then without FCs.

Casmo said:
Perhaps any layers installed?
If so, try removing them from inside TWPR and see if it boots then without FCs.
Click to expand...
Click to collapse
No Layers were previously installed at all. I was last on a CMTE ROM. I checked /Vendor, just to be sure..

adzcache said:
No Layers were previously installed at all. I was last on a CMTE ROM. I checked /Vendor, just to be sure..
Click to expand...
Click to collapse
So you fastbooted back to stock and booted into the stock system? And you get those issues in the stock firmware?
Sent from my Nexus 6P

jesssiii said:
So you fastbooted back to stock and booted into the stock system? And you get those issues in the stock firmware?
Sent from my Nexus 6P
Click to expand...
Click to collapse
Yes, exactly. I don't understand how this is even possible,
especially after wiping and going back to stock many times.
Literally every ROM installation ends the same.

adzcache said:
Yes, exactly. I don't understand how this is even possible,
especially after wiping and going back to stock many times.
Literally every ROM installation ends the same.
Click to expand...
Click to collapse
1) When you fastboot flash back to stock after a custom rom, what is your process? Do you perform a factory reset in TWRP prior to using fastboot?
2) Are you verifying the MD5 of the factory image prior to flashing?
3) What is the file name of the factory image you are using?
4) Are you able to reproduce this issue with different gapps packages, say Open gapps or an older/newer version of Banks gapps?
4) Are you downloading each of these files over WiFi or Mobile Data onto your phone?
5) Are you also checking the MD5 of each zip prior to flashing?
Based on your post, it looks like you are using one gapps zip and experiencing this issue on every rom. This sounds like a corrupt gapps zip.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
1) When you fastboot flash back to stock after a custom rom, what is your process? Do you perform a factory reset in TWRP prior to using fastboot?
2) Are you verifying the MD5 of the factory image prior to flashing?
3) What is the file name of the factory image you are using?
4) Are you able to reproduce this issue with different gapps packages, say Open gapps or an older/newer version of Banks gapps?
4) Are you downloading each of these files over WiFi or Mobile Data onto your phone?
5) Are you also checking the MD5 of each zip prior to flashing?
Based on your post, it looks like you are using one gapps zip and experiencing this issue on every rom. This sounds like a corrupt gapps zip.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
1. Yes, before flashing the stock image I boot into TWRP and factory reset, I have also tried wiping everything including internal storage in my many attempts to save this phone.
2. No, in all my years on an Android I have never had to check an MD5 and to be perfectly honest I don't really understand how to check MD5's.
3. angler-mhc19q-factory-f5a4e7a1.tgz
4. Yes every Gapps package causes the same outcome. I have tried Slim Gapps, OpenGapps, and Banks Gapps, I have tried downloading them first on my phone, then tried downloading everything fresh from my PC and moving them to my internal storage.
5. Again, not to sure on how to verify these MD5's..
I have tried multiple ROMs, and multiple Gapps. All flashes end the same. I also tried every newer version of TWRP and gone back to stock over 6 times in the past 2 days.
Edit: I'm starting to think that this issue could be related to my Google Account and restoring my device through the Setup, because I have flashed a ROM (DU 04/08) and made it through the setup with no FC's, so long as I don't sign into my Google Account. If I sign in FC's galore and occasional random reboots. I am also experiencing very slow download speeds on LTE and WiFi when downloading Gapps or a different ROM.

adzcache said:
1. Yes, before flashing the stock image I boot into TWRP and factory reset, I have also tried wiping everything including internal storage in my many attempts to save this phone.
2. No, in all my years on an Android I have never had to check an MD5 and to be perfectly honest I don't really understand how to check MD5's.
3. angler-mhc19q-factory-f5a4e7a1.tgz
4. Yes every Gapps package causes the same outcome. I have tried Slim Gapps, OpenGapps, and Banks Gapps, I have tried downloading them first on my phone, then tried downloading everything fresh from my PC and moving them to my internal storage.
5. Again, not to sure on how to verify these MD5's..
I have tried multiple ROMs, and multiple Gapps. All flashes end the same. I also tried every newer version of TWRP and gone back to stock over 6 times in the past 2 days.
Edit: I'm starting to think that this issue could be related to my Google Account and restoring my device through the Setup, because I have flashed a ROM (DU 04/08) and made it through the setup with no FC's, so long as I don't sign into my Google Account. If I sign in FC's galore and occasional random reboots. I am also experiencing very slow download speeds on LTE and WiFi when downloading Gapps or a different ROM.
Click to expand...
Click to collapse
Did you figure out any way to get around the FCs when signing into your account?
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Did you figure out any way to get around the FCs when signing into your account?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yes sir, I found a more or less, temporary fix to get around the FC's. I wiped my phone completely, several times, and flashed the stock MHC19Q image a few times and used TWRP 3.0.2-0 to flash DU 04/08, Nano OpenGapps 04/14, and totally avoided signing into my Google Account. After rebooting I signed into Google. No FC's!!! Yay! Then waited 3 hours for my contacts to be synced. (App data was also gone from Settings>Accounts for some reason for 3+ hours) after 3 hours of waiting, everything seems to be working again... For the time being. I'm now scared to flash a ROM other then DU, and my Restorations on 3.0.2-0 have taken over 300+ seconds, but before (3.0.0-1) a restoration was just over 60 seconds...
Weird stuff going on here for sure but at least I got DU! ?

adzcache said:
Yes sir, I found a more or less, temporary fix to get around the FC's. I wiped my phone completely, several times, and flashed the stock MHC19Q image a few times and used TWRP 3.0.2-0 to flash DU 04/08, Nano OpenGapps 04/14, and totally avoided signing into my Google Account. After rebooting I signed into Google. No FC's!!! Yay! Then waited 3 hours for my contacts to be synced. (App data was also gone from Settings>Accounts for some reason for 3+ hours) after 3 hours of waiting, everything seems to be working again... For the time being. I'm now scared to flash a ROM other then DU, and my Restorations on 3.0.2-0 have taken over 300+ seconds, but before (3.0.0-1) a restoration was just over 60 seconds...
Weird stuff going on here for sure but at least I got DU!
Click to expand...
Click to collapse
I had a problem like that. What I did was
Boot into Recover - TWRP 2.8 something
Did the Wipe Data / Factor Reset
Flashed The Rom - For me it was Pure Nexus - April 7, 2016
Flashed The Kernel - For Me Element X
Then wiped Davlik/Cache
Then after that I rebooted let it do what it had to do to boot up. Then rebooted to recovery
Then flashed the GAPPS - for me i used BaNkS-Dynamic-GApps-6.x.x-10-20-15
Then wiped DAvlik/Cache
Then rebooted and let it do its thing again. - I did not get any system startup failed.
Maybe you can not flash the GAPPS all together because the phone is a smart phone but it can still be DUMB.. LOL
Then I did not do a restore of apps from the automatic thing when it asks I just went to pla stoer and let it download what I needed from the my app section.

I'm still facing issues, but at least there are painfully long fixes to make everything work normally... Just pissed, every other android phone I have had, never faced such a persistent issue with rooting and flashing custom ROMs. Especially after restoring to stock..

Sorry to bump this thread, just hoping someone may have a suggestion that may fix up this rather odd issue I've been plagued with?

Quick fix for anyone else facing this:
Downgrade to MHC19I and when flashing recovery, flash TWRP 3.0.0-1, then format userdata in fastboot, copy your files over via PC and flash ROM + Gapps.

Bootloops when flashing System, Data

It first started this morning when my phone suddenly started rebooting while I was using it. Then I thought it as a ROM issue and flashed a new ROM over it. Everytime I try to flash something on system. TWRP Hangs and the phone restarts itself.
Tried repairing data, system partitions from TWRP, same thing happens. Bootloops when I try to repair data partition
Tried restoring nandroid backup. When it says flashing data, TWRP freezes and the phone starts bootlooping.
Can anyone help?

I have tried doing the EFS flash via adb from PC.

I'm stuck with the exact same problem since months.

CallMeAldy said:
I'm stuck with the exact same problem since months.
Click to expand...
Click to collapse
No luck?
Have you tried Claiming Warranty?

try doing a re flash of recovery, because your issue will be to get your recovery working properly or else you cant remount anything else.

StarRavier said:
try doing a re flash of recovery, because your issue will be to get your recovery working properly or else you cant remount anything else.
Click to expand...
Click to collapse
I flashed TWRP 3.0.2,3.0.2-2,3.0.2-3
Loads of it. Tried doing full stock + unroot from Nexus toolkit. That usually fixed all my problems Everytime I was in dire problems like this.

TJ_bab said:
I flashed TWRP 3.0.2,3.0.2-2,3.0.2-3
Loads of it. Tried doing full stock + unroot from Nexus toolkit. That usually fixed all my problems Everytime I was in dire problems like this.
Click to expand...
Click to collapse
I've never used that toolkit. Since day 1, ive used skipsoft android toolkit. just keep on trying. Does it crash at all when doing backups?

StarRavier said:
I've never used that toolkit. Since day 1, ive used skipsoft android toolkit. just keep on trying. Does it crash at all when doing backups?
Click to expand...
Click to collapse
Doesn't crash during backup but crashes during restore.

TJ_bab said:
Doesn't crash during backup but crashes during restore.
Click to expand...
Click to collapse
Well in your case what I would do is a backup,
Then wipe, flash custom rom. Use phone til reboot.
If reboot, flash stock IMG. Use till reboot
If still rebooting, then come back. I guess I never asked.what rom.your using

StarRavier said:
Well in your case what I would do is a backup,
Then wipe, flash custom rom. Use phone til reboot.
If reboot, flash stock IMG. Use till reboot
If still rebooting, then come back. I guess I never asked.what rom.your using
Click to expand...
Click to collapse
it doesn't boot at all.
It bootloops

I have the exact same problem. Last week upgraded to 7.0, root, stock room, viper4arise audio and EX kernel and that's it. while taking pictures it froze then that boot loop, somehow I managed through a combination of flashing factory image through fastboot, locking, unlocking, reflahsing, to get it to boot normally, then yesterday I was taking pictures again and it refroze then bootloops. Now I am able to fastboot factory images but it doesn't get me out of the bootloops, and in TRWP same as you, I cannot flash anything on data or system. Repairing the file system doesn'T change anything, I did like on other threads also and flashed factury, restored nandroid then flash factory but the restore on TRWP always hangs up.
I was wondering if there is someone knowing the adb dd commands to impose the raw copying back of the restore ? Maybe that would work.

Did you try wiping system under wipe > advanced in TWRP?

In twrp, can you open a terminal and check the results of this (basically, doing a full read-only test of your flash)
Code:
dd if=/dev/block/mmcblk0 of=/dev/null

Nexus 6p bootloop (NOT same as Infamous BLOD)

Hi! Guys I have a problem, which doesn't resemble the BLOD, so here is what has happened. I was running stock android June build on 6p, rooted. And my phone started random reboots. I thought it could be fixed with either stock or custom rom. So I decided to flash AOSPA. I went into twrp but could not flash it, phone rebooted each time. I tried stock images via flash all command as well as manual. No rom worked although I could flash kernel etc. I used The Flash's custom twrp and fixed data and was able to flash rom easily, but it bootlooped on google logo, and rebooted. Now I can flash roms etc but it bootloops. Although Tesla rom did go into bootanimation before bootlooping.
So what can I do? Is it software related? What do you guys say!
PS. I did look into other threads, nothing was similar, although I did try a few mentioned fixes.

osamaasif786 said:
So what can I do? Is it software related? What do you guys say!
Click to expand...
Click to collapse
Use fastboot to FORMAT system, userdata and cache. Note any errors during the FORMAT process.... and then try flashing a full image from Google using flash-all.bat

v12xke said:
Use fastboot to FORMAT system, userdata and cache. Note any errors during the FORMAT process.... and then try flashing a full image from Google using flash-all.bat
Click to expand...
Click to collapse
It gives no error and did try the flash-all.bat method no luck.

osamaasif786 said:
It gives no error and did try the flash-all.bat method no luck.
Click to expand...
Click to collapse
I'd say you were squarely in a small group of people who are able to access and fully use Recovery but still boot loop after formatting and installing a clean image. If you've already tried a factory reset from the stock recovery I think you are done. Hardware issue. Replacing the motherboard is a fix, but not economically viable.

I had the same issue formatting data and cache to Ext4 and flashing modified stock ROM fixed. It would boot to Google logo freeze reboot and sometimes get to boot animation freeze and reboot.

Exodusche said:
I had the same issue formatting data and cache to Ext4 and flashing modified stock ROM fixed. It would boot to Google logo freeze reboot and sometimes get to boot animation freeze and reboot.
Click to expand...
Click to collapse
Which modified one, can you share the link?

osamaasif786 said:
Which modified one, can you share the link?
Click to expand...
Click to collapse
Cortex ROM it's flashable stock firmware with extras . Though my symptoms where the same I hope I'm not giving you false hope. Worth a shot though.

The only was I recover my phone without replacing is using https://forum.xda-developers.com/nexus-6p/general/boot-images-bootloop-t3633723 < method from here... but the phone is lag af as it is only running 1 core on stock july build. Good luck for that.

I have the same issue going on. i was trying to flash magisx and suddenly it is stuck in bootloop. i tried flashing stock images and everything. i can access twrp and flash eveything and they are getting flashed fine but still it is stuck on the bootloop.

TheTickReborn said:
I have the same issue going on. i was trying to flash magisx and suddenly it is stuck in bootloop. i tried flashing stock images and everything. i can access twrp and flash eveything and they are getting flashed fine but still it is stuck on the bootloop.
Click to expand...
Click to collapse
So have you used fastboot to FORMAT system, userdata and cache? Did each format command complete with no errors?

Stuck in bootloop trying to flash 7.1 custom rom

My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
I had an older version of twrp so I just updated it to the latest one before attempting this ofc...
I tried flashing the latest RR and AICP and both give me boot loops and I always get this one problem where it says
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
I'm not sure if this has anything to do with the bootloop though...
Going to recovery after seeing the bootloop I always get the "keep system read only?" prompt where i swipe to allow modification but i usually just restore back to my backup from there... i dont think allowing it and trying to boot again will get rid of the bootloop...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..

OppaiHeroStar said:
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
Click to expand...
Click to collapse
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36

dzidexx said:
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
Click to expand...
Click to collapse
The first 3 steps I've already done that since the beginning
Where can i get the nougat modem/is it possible to update to it? I guess that's the reason every single 7.1 custom rom I tried in the android development section gave me boot loops...
And could you link the 21.11.2017 version of RR? I'm looking at the download links for RR and I dont see one with that exact date
edit-just saw your edit

Custom roms for MM modem works better.

I fully wiped using TWRP, checked everything I possibly could except my micro SD card and I flashed RR-N-v5.8.5-20171121-clark-Final.zip then gapps arm64, 7.1 nano and it's still giving me boot loops. I'm using TWRP 3.2.1-0
im gonna try using gapps arm64 7.1 mini really quick since you said I should use that one and see if it boot loops... - Edit guess I was too optimistic thinking this would fix it

Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.

dzidexx said:
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
Click to expand...
Click to collapse
changed to 3.1.1-0 and did everything you said, still have boot loop...
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"

OppaiHeroStar said:
changed to 3.1.1-0 and did everything you said, still have boot loop...
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs

dzidexx said:
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
Click to expand...
Click to collapse
I tried crDroidAndroid-7.1.2-20171119-clark-v3.8.3.zip and it still boot loops :\ I also already tried LineageOS and AICP before we started talking
I went back to my backup and it put me in a bootloop which never happened before but changing cache back to ext4 instead of f2fs fixed it..

OppaiHeroStar said:
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
A little late to chime in and this does not help with your current situation, but here's a little advice. I flash a lot of ROMs (how else am I going to test builds right?). This error happens all the time, BUT if you flash a ROM twice it should not show on the 2nd flash.
So flash order goes:
Wipe/Factory reset
Format data x3 (yes I format my data 3 times for every ROM)
Reboot
Wipe/Factory reset
ROM
ROM again
GAPPS
Wipe caches
Reboot
Do the Initial setup
Reboot before use
OPTIONAL Kernel (if its not already build in)
OPTIONAL Magisk (I never flash Magisk on a clean build but heck I'm expecting a NON boot most of the time anyways)

At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.

acejavelin said:
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
Click to expand...
Click to collapse
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.

OppaiHeroStar said:
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
Click to expand...
Click to collapse
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.

acejavelin said:
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
Click to expand...
Click to collapse
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?

OppaiHeroStar said:
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
Click to expand...
Click to collapse
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.

acejavelin said:
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
Click to expand...
Click to collapse
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it

OppaiHeroStar said:
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
Click to expand...
Click to collapse
What custom did you flashed?

dzidexx said:
What custom did you flashed?
Click to expand...
Click to collapse
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now

OppaiHeroStar said:
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
Click to expand...
Click to collapse
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.

dzidexx said:
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
Click to expand...
Click to collapse
I'm using t-mobile and I've checked the access points, clicking on the one im using and hitting save doesn't fix it. Always getting a notification telling me to sign in to network. Not sure what else I can do. I'll give it a day since I had this kind of problem before when I switched sim cards and data didn't work until the next day
Edit - just went back to stock and my data doesn't work now either... just going to stay at RR now and hope my data fixes itself because my access point settings for tmobile should be correct since I looked it up on the official website..

ZE552kL (Soft Bricked)

I have bricked my phone the issue I am facing is I don't own and can't afford an SD card to sideload the rom onto my phone is there a 7.0 stock based rom that is flashable via TWRP or? Really need some ideas need to fix this device.

If you have access to TWRP, then plug your phone into your computer and it'll mount your internal sdcard. Copy any Rom you want onto it and flash as normal (remember to wipe cache and dalvik!). If you get the "error 7" output, edit your updater script and do it again. If you get a bootloop after successfully flashing, flash the latest magisk zip (I assume you use root?) or noverity file if not.

wang1chung said:
If you have access to TWRP, then plug your phone into your computer and it'll mount your internal sdcard. Copy any Rom you want onto it and flash as normal (remember to wipe cache and dalvik!). If you get the "error 7" output, edit your updater script and do it again. If you get a bootloop after successfully flashing, flash the latest magisk zip (I assume you use root?) or noverity file if not.
Click to expand...
Click to collapse
I use root and both but when I decided to remove root and was looking at installing another rom it failed now I don't see any twrp flashable roms for my device would you know of any? I tried stock but it can't be flashed from TWRP sadly I have no bootable rom at the moment.

@mastermarkofroms
EVERY Rom that can be flashed through stock recovery can be flashed through TWRP.
....all you need to do is edit the updater script as I said above. Give it a shot
Edit: you softbricked your phone removing root? Just perform a factory reset, you'll lose your personal data but it'll boot. Remember to wipe cache and dalvik.

wang1chung said:
@mastermarkofroms
EVERY Rom that can be flashed through stock recovery can be flashed through TWRP.
....all you need to do is edit the updater script as I said above. Give it a shot
Edit: you softbricked your phone removing root? Just perform a factory reset, you'll lose your personal data but it'll boot. Remember to wipe cache and dalvik.
Click to expand...
Click to collapse
I have never modified that before what would I need to modify to get it working?

@mastermarkofroms
Open the Rom archive and edit the updater script (/META-INF/com/google/android/updater-script) to remove the first 7 lines (sometimes more or less) of code, so the script starts at "ui_print....." now. Save it, and load it onto your sdcard and flash.

wang1chung said:
@mastermarkofroms
Open the Rom archive and edit the updater script (/META-INF/com/google/android/updater-script) to remove the first 7 lines (sometimes more or less) of code, so the script starts at "ui_print....." now. Save it, and load it onto your sdcard and flash.
Click to expand...
Click to collapse
I will give that a shot turns out a factory reset did not start up device so this is my last choice as I can still access recovery
edit: so after modifying the script it did flash without an issue but it still has failed to boot reloading the bootloader.

Flash magisk or the no verify file

wang1chung said:
Flash magisk or the no verify file
Click to expand...
Click to collapse
the no verify file was flashed when I rooted this device

Which Rom did you flash?
You performed a factory reset and wiped dalvik and cache after flashing? How long did you wait after rebooting? Usually takes 5-10min on the first boot.
Edit: you flashed the no verity file after flashing the rom today, right?

wang1chung said:
Which Rom did you flash?
You performed a factory reset and wiped dalvik and cache after flashing? How long did you wait after rebooting? Usually takes 5-10min on the first boot.
Edit: you flashed the no verity file after flashing the rom today, right?
Click to expand...
Click to collapse
I tried flashing Unofficial LineageOS 14.1 for ZE552KL by basenode with opengapps it just failed to flash not an error 7 it actually gave me a wrong device error although I know I have the ze552kL model. and since then it don' boot it tries to you see the asus logo and it just restarts again in a boot loop

Flash magisk right now, then wipe cache and dalvik

Go back asus nougat 7.0 -> factory reset -> flash LOS 14.1 -> flash gapps -> done. Flash magisk if you want.
Edit: when you go back asus rom and face bootloop then just flash no-verity file, everything will work like normal .

[email protected]@ said:
Go back asus nougat 7.0 -> factory reset -> flash LOS 14.1 -> flash gapps -> done. Flash magisk if you want.
Edit: when you go back asus rom and face bootloop then just flash no-verity file, everything will work like normal .
Click to expand...
Click to collapse
Thanks for the info will give that a shot as soon as I do get home from work. Just ablittle annoyed that first phone I have ever bricked

[email protected]@ said:
Go back asus nougat 7.0 -> factory reset -> flash LOS 14.1 -> flash gapps -> done. Flash magisk if you want.
Edit: when you go back asus rom and face bootloop then just flash no-verity file, everything will work like normal .
Click to expand...
Click to collapse
Any ideas where I can find the no verity file? I dont see it on the forum unless I am blind

mastermarkofroms said:
Any ideas where I can find the no verity file? I dont see it on the forum unless I am blind
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/ze...20kl-ota-upgrade-doesnt-t3706856/post74571792

[email protected]@ said:
Here https://forum.xda-developers.com/ze...20kl-ota-upgrade-doesnt-t3706856/post74571792
Click to expand...
Click to collapse
Problem solved back on stock thanks for all the help @everyone

mastermarkofroms said:
Problem solved back on stock thanks for all the help @everyone
Click to expand...
Click to collapse
I thought you ask for the LOS rom.

I did the thing is had it installed and everything but my phone kept freezing and lagging with it not sure why as I had nothing on there that would of caused it. But the lag once I got it working was just unbearable for me

mastermarkofroms said:
I did the thing is had it installed and everything but my phone kept freezing and lagging with it not sure why as I had nothing on there that would of caused it. But the lag once I got it working was just unbearable for me
Click to expand...
Click to collapse
Which rom?