Database Users

Help me root :)

What do I do wrong? - using this guide: http://forum.xda-developers.com/showthread.php?t=612858
My bootloader is unlocked.
Settings -> applications -> unknown sources enabled
- recovery-RA-nexus-v1.6.2.img is in my tool folder
- nexus-addon-0.1-signed.zip is on my sdcard
SHIFT + rightclick and open CMD from the tool folder.
Run two commands:
fastboot devices
fastboot flash recovery recovery-RA-nexus-v1.6.2.img
Go into bootloader and choose recovery - and I get a triangle with an android every time.
What do I do wrong?

try this:
1) fastboot boot recovery recovery-RA-nexus-v1.6.2.img, you're trying to force RA to run without actually having it "flashed".
2) once RA is up and running, use RA to flash the root image
3) your phone is now rooted
4) reboot
5) Test to see if it's rooted by downloading the N1 torch or something
6) Once root is confirmed, reboot into fastboot again
7) fastboot flash recovery recovery-RA-nexus-v1.6.2.img
I had the same issue as you. The problem is that the RA recovery doesn't flash because the phone is not rooted. However, you need RA running in order to flash the root image. So here we're going to load RA without having it flashed, then use it to root, then flash RA afterwards.

help with cyanogen Rom upgrade from 5.0.7 to 6.0.0

I have a rooted mytouch original with cyanogen 5.0.7/android 2.1 and want to upgrade to cyanogen 6.0.0/android 2.2.
Can I just install the new rom, or are their prior steps to prepare for this.
Thanks
DAve

Check CM wiki.. all the info is there!

yes, I had already read through the cm wiki before posting. I just read through it a second time, though the specific question that I had asked was not addressed as far as I could tell. Don't want to flash a new rom without first knowing its the right step to take. So if someone doesn't mind answering the question...

Just do a nandroid backup. Then you flash the CM 6 over the old one, do a cache+dalvic wipe and start it up.... It should be ok.
If not, then just revert back with the knowledge that you have to do a complete wipe, meaning that you need to start from scratch.

I now have initiated flashing new rom, starting with backing up data and wiping cash. However, I am now unable to go into recovery mode, whereas the phone is stuck on the logo when attempting to do so. I had installed through rom manager clockworkmod 2.5.0.1, got the message it installed correctly.
Here are the methods I have used to go into recovery:
1. click on "reboot into recovery"
2. backup current rom
3. flash alternative recovery with RA Recovery v.1.7.OH downloaded by rom manager, and use rom manager to restart into recovery mode
4. turn phone off, try to press home and power button together, for the new RA and the new clock work mod programs.
will not go into recovery mode, gets stuck on the boot up logo. Phone otherwise works fine, on the older Cyanogen Rom..., just can't go into recovery mode which I need to do to upgrade.
My original recovery was RAv1.2.0G.img, but this was I assume replaced by the rom manager.
In case this is important, my other software versions I have been using the past year:
Hboot 1.33.2005 (sapp30000), Cpld 10, Radio 2.22.19.261
will not go into recovery mode, gets stuck on the boot up logo. Phone otherwise works fine, on the older Cyanogen Rom...
any suggestions?

You flashed wrong recovery version...
You need RA Recovery v.1.7.OG and not H as stated above.
If all ****s up, then use my guide (check my signature) to flash a custom recovery... just skip the steps about root since you already got that!
Remember, G and NOT H.

lost recovery
mumilover
I do actually have v.1.7.0G installed, not H (my bad).
it just will not go into recovery.
Please let me know where your guide is, but right now I have been unable to communicate with my device through my xp desktop, get the "device not found" error (I assume you are suggesting that). Not sure how this will help though, since I already seem to have the correct recovery image installed.
Any help you can offer would be appreciated.
Dave
mumilover said:
You flashed wrong recovery version...
You need RA Recovery v.1.7.OG and not H as stated above.
If all ****s up, then use my guide (check my signature) to flash a custom recovery... just skip the steps about root since you already got that!
Remember, G and NOT H.
Click to expand...
Click to collapse

Download my fastboot commander (CHECK MY SIGNATURE, magic version).
Restart into fastboot mode.
Download this recovery image:
http://rapidshare.com/files/387932919/recovery-RA-sapphire-v1.7.0G.img
Using the tool and your eng spl, you can just flash the recovery image on the phone.
Just use the first tab -> recovery button -> navigate to the above image -> click "flash recovery". Done.
Restart into recovery by home + power combo.
You could also try this command:
Code:
adb shell reboot recovery
to force it to boot into recovery from the system.

[Problem is fixed. Thanks for your help.
I used my mac bootcamp (could not get sdk to run on my desktop or mac), and could find my device through adb. Then I pushed a separate version of the RA 1.7.0 G (the one the came with rom manager did not work!) to my phone via flash command. Voila, I am now able to go into recovery mode. 6.0 is installed and running.
QUOTE=mumilover;10252460]Download my fastboot commander (CHECK MY SIGNATURE, magic version).
Restart into fastboot mode.
Download this recovery image:
http://rapidshare.com/files/387932919/recovery-RA-sapphire-v1.7.0G.img
Using the tool and your eng spl, you can just flash the recovery image on the phone.
Just use the first tab -> recovery button -> navigate to the above image -> click "flash recovery". Done.
Restart into recovery by home + power combo.
You could also try this command:
Code:
adb shell reboot recovery
to force it to boot into recovery from the system.[/QUOTE]

[Q] MT3G bad recovery flash, stuck

Hi,
I have a mt3g, TMobile. CyanogenMod 6.1.0, ClockWork recovery. Used ROM Managed to flash Amon Ra recovery, since I needed to re-calibrate the battery. It asked me to pick phone model, picked Ion/MyTouch 3G. After reboot:
- Stuck on splash screen if I try to go to recovery
- When booted up - a bunch of force closures, keeps playing a ringtone over and over and...
Everything I tried to do through ROM Manager didn't help.
Any help is appreciated.
Thanks.

truss said:
Hi,
I have a mt3g, TMobile. CyanogenMod 6.1.0, ClockWork recovery. Used ROM Managed to flash Amon Ra recovery, since I needed to re-calibrate the battery. It asked me to pick phone model, picked Ion/MyTouch 3G. After reboot:
- Stuck on splash screen if I try to go to recovery
- When booted up - a bunch of force closures, keeps playing a ringtone over and over and...
Everything I tried to do through ROM Manager didn't help.
Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
Do you still have root? If you can get into ROM manager, reflash clockwork recovery, then wipe cache, dalvik, and run a fix permissions. That should get you back up and running long enough to try again to flash amon ra.
Not sure if the oem spl will let you fastboot flash a new recovery but that's your most reliable bet.
It sounds like it might be time to do a full wipe and reflash anyway. Have you heard of Ohsaka's SuperWipe?

I tried reflashing Clockwork through ROM Manager. It says "root granted", "clockwork flashed" immediately. When I try to boot into recovery - I get stuck on green MyTouch screen forever. Battery pull is the only way out.
I guess the problem is that I cannot get to any recovery anymore. Any ideas?

Do you have fastboot. If so you can flash recovery from there.

kodjo said:
Do you have fastboot. If so you can flash recovery from there.
Click to expand...
Click to collapse
Can I do that through adb shell? I don't think I built fastboot.

truss said:
Can I do that through adb shell? I don't think I built fastboot.
Click to expand...
Click to collapse
Fastboot is a different mode. Boot into hboot (vol down + power I think) and then select fasboot from the menu. Then plug into computer. From a command prompt type:
fastboot flash recovery recovery.img
The recovery needs to be in your tools or platform-tools folder and named recovery.img for this to work. Otherwise it would be fastboot flash recovery c:\path\to\recoveryfilename.img. Make sense?
Link to Amon_Ra Recovery 1.7 for MT3G 32B. http://www.filefactory.com/file/caa48b0/n/recovery-RA-sapphire-v1.7.0G-cyan.img
Otherwise keep trying with ROM Manager. Might take a few attempts to get recovery to stick, even temporarily. It did for me. Flash once then flash again. There's also an option in ROM Manager settings to erase recovery prior to flashing. Check that and see if it helps.

Phateless said:
Fastboot is a different mode. Boot into hboot (vol down + power I think) and then select fasboot from the menu. Then plug into computer. From a command prompt type:
fastboot flash recovery recovery.img
The recovery needs to be in your tools or platform-tools folder and named recovery.img for this to work. Otherwise it would be fastboot flash recovery c:\path\to\recoveryfilename.img. Make sense?
Link to Amon_Ra Recovery 1.7 for MT3G 32B.
Otherwise keep trying with ROM Manager. Might take a few attempts to get recovery to stick, even temporarily. It did for me. Flash once then flash again. There's also an option in ROM Manager settings to erase recovery prior to flashing. Check that and see if it helps.
Click to expand...
Click to collapse
I appreciate your help.
When I try to flash recovery.img, I get this: error: cannot load `recovery.img`
When I try running fastboot with absolute path, I get: FAILED (remote: not allow). Is there a way to fix this?
Tried flashing through ROM Manager many times - no result.

truss said:
I appreciate your help.
When I try to flash recovery.img, I get this: error: cannot load `recovery.img`
When I try running fastboot with absolute path, I get: FAILED (remote: not allow). Is there a way to fix this?
Tried flashing through ROM Manager many times - no result.
Click to expand...
Click to collapse
Interesting... Where are you trying to flash recovery.img and getting that error? What method are you using? Are you sure you have the path to recovery.img correct?
As for fastboot, you need an S-OFF/engineering spl so I guess that's out.
What happens if you use Terminal Emulator?
su
flash_image recovery sdcard/recovery.img
Does that work? Keep at it, you have root so not all is lost. Eventually you will get there.
EDIT - make sure you rename the recovery to "recovery.img" and leave it on the root of your sdcard for my italicized instructions above to work. What ROM are you running? If flash_image doesn't work I need to know which version of the binary to give you.

Phateless said:
Interesting... Where are you trying to flash recovery.img and getting that error? What method are you using? Are you sure you have the path to recovery.img correct?
As for fastboot, you need an S-OFF/engineering spl so I guess that's out.
What happens if you use Terminal Emulator?
su
flash_image recovery sdcard/recovery.img
Does that work? Keep at it, you have root so not all is lost. Eventually you will get there.
EDIT - make sure you rename the recovery to "recovery.img" and leave it on the root of your sdcard for my italicized instructions above to work. What ROM are you running? If flash_image doesn't work I need to know which version of the binary to give you.
Click to expand...
Click to collapse
Thank you very much.
Running flash_image recovery command using adb shell a few times did the trick. I was able to boot to Amon RA recovery, wipe and flash CyanogenMod 6.1.0.

truss said:
Thank you very much.
Running flash_image recovery command using adb shell a few times did the trick. I was able to boot to Amon RA recovery, wipe and flash CyanogenMod 6.1.0.
Click to expand...
Click to collapse
Nice! Glad you got it sorted out.

[Q] stuck on recovery screen.

Hello,
I've rooted my device and installed the hellfire Kitkat rom. Since I was not fully satisfied I wanted to go back to stock rom and then install the latest update from LG.
But now the device only boots into recovery (CWM V6.0.4.7)
I can install a backup ROM but when I reboot it enters recovery again.
I tried entering download mode by pressing "volume UP key" and then plugin usb but it enters recovery again.
Can someone help me please?!

sander-w said:
Hello,
I've rooted my device and installed the hellfire Kitkat rom. Since I was not fully satisfied I wanted to go back to stock rom and then install the latest update from LG.
But now the device only boots into recovery (CWM V6.0.4.7)
I can install a backup ROM but when I reboot it enters recovery again.
I tried entering download mode by pressing "volume UP key" and then plugin usb but it enters recovery again.
Can someone help me please?!
Click to expand...
Click to collapse
I'm going to be cautious replying here because I'm a noob, but did you try using ADB to issue commands through adb sideload in cwm? If you go to "load zip" (or something along those lines) then "load using adb" (or something similar) in CWM, you can use adb to issue these commands with your computer and it should fix it (at least, it fixed a boot loop for me when I was stuck with TWRP). Here's the link:
http://forum.xda-developers.com/showthread.php?t=2451696

First of all. DON'T PANIC!
And even before that - make a nandroid backup! Go in CWM and make a full backup.
You have recovery working so you should be able to load System on it ok.
I am not an expert but let me try to guide you step by step.
1. Make a backup!
2. Download a rom on your computer. MAKE SURE ITS FOR YOUR MODEL # of LG G2
List of roms here:
3. Make sure you have over 70% battery
4. Go into recovery CWM
5. Use Wipe > Swipe to Factory Wipe
(go back on bottom right corner)
6. Go Advanced from HOME screen of CWM
7. Click ADB sideload
7b. (I assume you have the drivers loaded. If not make sure ADB is loaded in windows and device manager shows it. Download basic ADB package so you have "adb.exe" file in it)
8. put your rom in the same folder where you have "Adb.exe"
9. Open command prompt on windows. Goto the folder where ADB.exe is. Then Type "adb push (filename) /sdcard/(filename)". Example, "adb push rom.zip /sdcard/rom.zip"
10. Wait until it finishes its transfer(a message will appear saying the filename, file size and the speed of the transfer per sec when it finishes)
11. Wait for a while or reboot your cwm so that the filename will appear
12. just reflash the file in CWM (Install > choose file). Wipe after again.
13. Voila!

By any chance did you successfully go back to stock 4.2.2 and then took the OTA and then got the recovery loop? If so this will help http://forum.xda-developers.com/showthread.php?t=2451696

Drachenminister said:
By any chance did you successfully go back to stock 4.2.2 and then took the OTA and then got the recovery loop? If so this will help http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
I did manage to restore the backup rom of 4.2.2 Then I downloaded the 4.4 OTA update and installed it. Then it hangs in recovery.
Do I need to have TWRP installed or does this work with CWM too?!

sander-w said:
I did manage to restore the backup rom of 4.2.2 Then I downloaded the 4.4 OTA update and installed it. Then it hangs in recovery.
Do I need to have TWRP installed or does this work with CWM too?!
Click to expand...
Click to collapse
Basically what you need is a root shell whether it's via adb or built into recovery (cwm or twrp)
Searching the forum for "cwm bootloop ota" might give you detailed instructions for your case

Drachenminister said:
By any chance did you successfully go back to stock 4.2.2 and then took the OTA and then got the recovery loop? If so this will help http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
When I try to run "adb shell" I get a message "error: closed" what does it mean?
When I run adb devices it returns a serial number. so it looks like it is able to communicate with my g2.

sander-w said:
When I try to run "adb shell" I get a message "error: closed" what does it mean?
When I run adb devices it returns a serial number. so it looks like it is able to communicate with my g2.
Click to expand...
Click to collapse
Weird, you can try and add the commands directly enclosed in parentheses like adb shell "dd if=...."

Drachenminister said:
Weird, you can try and add the commands directly enclosed in parentheses like adb shell "dd if=...."
Click to expand...
Click to collapse
It seems that my device was in sideload mode. when I disabled sideload mode I followed the instructions on this pag
http://forum.xda-developers.com/showthread.php?t=2451696
And it worked!!!
Thanks for your help all!!!!

[Root] Zenfone 2 Official Android 6.0 Root + Xposed and Downgrade

**WARNING** You need to have background knowledge of adb, fastboot, twrp, sideload.. before you can go on with this thread.
1. All credits go to @shakalaca. If you like his work, please make him a small donation for encouragement.
2. This is a systemless root. Yet you need to unlook Lollipop before upgrading to Marshmallow.
3. Flashing the attached SuperSU file modifies stock boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** to unroot before upgrading to official Android 6.0.
Root:
1. Unlock your device in Lollipop, then upgrade to Android 6.0
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. This TWRP is recommended.
HTML:
adb reboot-bootloader
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp. /OR install the SuperSU in twrp if you saved it in device storage.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Unroot:
Just flash back stock boot.img
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: Download Xposed Installer here
Downgrade to Lollipop:
In case you need to downgrade to Lollipop, follow the instructions with care. Do it at your risk.
Refer to Asus Zentalk Forum and grab the required files from there.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
fastboot reboot-bootloader
Now you are back in Lollipop. You can flash back stock recovery(.184 recommended), wipe the device(cache/userdata/system) and then sideload back stock LP or MM as you wish. OR, you can flash custom recovery/boot/system.img start from here.
Good luck!

It worked!Thank you master!I bow now....

I just need root on 6.0.1. Is this going to achieve that?

MikeyLee said:
I just need root on 6.0.1. Is this going to achieve that?
Click to expand...
Click to collapse
According to op it will
Sent from my ASUS_Z00AD using Tapatalk

It does work, but YMMV, my phone is one of the few that works completely with the beta software. But before running fastboot cmd in adb. Use adb reboot recovery, then fastboot cmd. Phone will reboot twice after sideload of SU.

pokey006 said:
It does work, but YMMV, my phone is one of the few that works completely with the beta software. But before running fastboot cmd in adb. Use adb reboot recovery, then fastboot cmd. Phone will reboot twice after sideload of SU.
Click to expand...
Click to collapse
Hi Brother would you like be so patient and provide us with detailed toturial for less advanced users?

samcjtsai said:
1. All credits go to @shakalaca and I just try to recap his threads posted in Taiwan Asus Zentalk forum. Although this is reported working in the forum but, as usual, do it at your risk and I won't be able to answer your questions.
2. Android 6.0 is still not unlocked. Device will be locked once you upgrade to 6.0
3. You can downgrade to Lollipop and unlock again.
4. The following SuperSU file contains a modified boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** before upgrading to official Android 6.0.
Root:
1. Make sure your zenfone 2 is unlocked before upgrading to Android 6.0 from Lollipop.
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. Version 2.8.7.7 is recommended.
HTML:
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: link
Downgrade to Lollipop:
Refer to this and get the files from the links. Note the first commnad line is the revised one by @shakalaca and it should work.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
Click to expand...
Click to collapse
Works like a charm !! Thanks !!

kamyk70 said:
Hi Brother would you like be so patient and provide us with detailed toturial for less advanced users?
Click to expand...
Click to collapse
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users

when update to 6.0. bootloader unlocked again ! how can i flash twrp ?

pokey006 said:
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users
Click to expand...
Click to collapse
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.

Vouga said:
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.
Click to expand...
Click to collapse
No it does not

Vouga said:
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.
Click to expand...
Click to collapse
He's using whats called "tethered TWRP". It's basically running twrp on your phone from your computer instead of actually installing it (which would require unlocking).
Sent from my ASUS_Z00A using Tapatalk

kenbo111 said:
He's using whats called "tethered TWRP". It's basically running twrp on your phone from your computer instead of actually installing it (which would require unlocking).
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Thank You for explaining that to me, appreciated!

To downgrade to Lollipop, is it possible to just use AsusFlashToolInstaller and flash raw firmware? Any harms by doing that?
Thank you in advance.

euthic said:
To downgrade to Lollipop, is it possible to just use AsusFlashToolInstaller and flash raw firmware? Any harms by doing that?
Thank you in advance.
Click to expand...
Click to collapse
You need to adb sideload all LP .184 images first then use Asus FlashTool to flash RAW Firmware.
Sent from my ASUS_Z00AD using XDA-Developers mobile app

root works perfect along with systemless xposed, but i still cant pass safenet check..(super su disabled, and also xposed) so no AP.. is that normal ?

pokey006 said:
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users
Click to expand...
Click to collapse
Maybe I'm doing something wrong but my phone isn't recognised when trying to flash twrp from the dead bot before recovery? Just says waiting for device. Already checked device manager as well

ponhei9502 said:
Maybe I'm doing something wrong but my phone isn't recognised when trying to flash twrp from the dead bot before recovery? Just says waiting for device. Already checked device manager as well
Click to expand...
Click to collapse
Guess your ZF2 is not unlocked in LP first, so that you can't see twrp booting. Since you are in Android 6.0 now, try to downgrade to LP, Unlock it, upgrade to 6.0 and then root.

samcjtsai said:
**WARNING** You need to have background knowledge of adb, fastboot, twrp, sideload.. before you can go on with this thread.
1. All credits go to @shakalaca and I just recap his threads posted in Taiwan Asus Zentalk forum. Although this is reported working in the forum, as usual, do it at your risk and I won't be able to answer your questions.
2. Android 6.0 is still not unlocked. Device will be locked once you upgrade to 6.0
3. You can downgrade to Lollipop and unlock again.
4. The following SuperSU file contains a modified boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** before upgrading to official Android 6.0.
Root:
1. Make sure your zenfone 2 is unlocked before upgrading to Android 6.0 from Lollipop.
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. Version 2.8.7.7 is recommended.
HTML:
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: link
Downgrade to Lollipop:
Refer to this and get the files from the links. Note the first commnad line is the revised one by @shakalaca and it should work.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
Click to expand...
Click to collapse
Where are these files again? They aren't in the zip

thanks, works great, was able to downgrade to lollipop with no problem what so ever. Install twrp, gain root again, and rockin custom roms...