Hey all, so I got the dreaded Func 11 error mode on my device.
I had updated to Oreo, and was attempting to install a Lineage treble build. I think I flashed the wrong one and I tried to flash back to stock by using the oreo update method. Unfortunately what appears to have happened is that I've somehow destroyed my recovery side of things.
I can access Fastboot and tried to flash TWRP, but this fails to load (gets stuck on 'Your device is now booting').
I'm out of ideas as to what to try now. Does anyone have any suggestions? To make matters worse my battery is also now dead.
Any help is much appreciated and apologies if this is just a repeat of another thread.
I had the same error, I sent it to tech service, I have no idea how to fix that, my phone was stuck at "your device is booting now", no way to enter into recovery.
I hope you can fix your phone bro. :/
I did the same as you and got the same problem, I had to send my device away and get it repaired by an authorized repair agent. They ended up having to put in a new main board into my phone.
if you can access fastboot you need wait on error mode screenbattery die,when phone close taje charge your phone wait open otomaticly
---------- Post added at 04:53 AM ---------- Previous post was at 04:49 AM ----------
if you cant access fastboot mode,you need wait battery draind finish, when phone shut down plug the charger and wait phone automatically open,,then try reach fastboot mode,after that flash kernel_ramdik after that flash twrp again for oreo
volpula said:
if you can access fastboot you need wait on error mode screenbattery die,when phone close taje charge your phone wait open otomaticly
---------- Post added at 04:53 AM ---------- Previous post was at 04:49 AM ----------
if you cant access fastboot mode,you need wait battery draind finish, when phone shut down plug the charger and wait phone automatically open,,then try reach fastboot mode,after that flash kernel_ramdik after that flash twrp again for oreo
Click to expand...
Click to collapse
I can access no fastboot no problem. Only problem is battery is completely dead and every time I try to charge it just reboots to error mode when I plug it in. Can't access the recovery unfortunately and I know there isn't any fastboot command for it from what I can find.
if you can access fastboot mode,you need use extractor for your oreo files,extract kernel and ramdisk.img and flash,after that flash twrp recovery again
Well I'm off to work now where I have access to a windows PC. I'll see what I can do, otherwise I'll try DC Unlocker if need be. I don't believe I need to send it back for repair as that seems like a bit much for what's clearly not a hardware issue.
no you dont need send to repair,thats software issues.huawei is really terrible company.kirin chipset its slow then snapdragon or exynos cpu and cpu,camera just take good picture thats all not take good video like galaxy phones,software is very bad recovery system worst in the anroid phones i even use before.developer cant cook custom roms,i never buy huawei phone again and ibcant recoment anybody to buy.they dont deserve that prices
volpula said:
if you can access fastboot mode,you need use extractor for your oreo files,extract kernel and ramdisk.img and flash,after that flash twrp recovery again
Click to expand...
Click to collapse
All images flashed. I still can't get in to recovery however due to the battery being depleted.
It won't simply just charge and reboots to Error Mode. If anyone knows of a way around this that would be great. Are there fastboot instructions to get to recovery?
MrDanMak said:
All images flashed. I still can't get in to recovery however due to the battery being depleted.
It won't simply just charge and reboots to Error Mode. If anyone knows of a way around this that would be great. Are there fastboot instructions to get to recovery?
Click to expand...
Click to collapse
are you sure flash correctly files?you need oreo recovery.img,ramdisk.img and twrp8.img.you need to be access to twrp
volpula said:
if you can access fastboot mode,you need use extractor for your oreo files,extract kernel and ramdisk.img and flash,after that flash twrp recovery again
Click to expand...
Click to collapse
volpula said:
are you sure flash correctly files?you need oreo recovery.img,ramdisk.img and twrp8.img.you need to be access to twrp
Click to expand...
Click to collapse
Yes I have flashed correctly via fastboot. My phone just can't get enough battery charge to be able to boot to recovery it seems.
Ok, I'm on Oreo and I'm gonna give DC Phoenix a shot. Does anyone know which firmware files I need to download? Device is VTR-L09C432
MrDanMak said:
Yes I have flashed correctly via fastboot. My phone just can't get enough battery charge to be able to boot to recovery it seems.
Click to expand...
Click to collapse
you need reach twrp recovery.when you be in twrp take charge your phone %30 or %50.restart your phone press volume up when you see warning you need able to twrp.after that.copy hwota8_update.zip,Mha_recovery nocheck.img and vtr-l09c432b217 files.make new folder HWOTA8 and put this files,make wipe after that flash hwota8_update.zip
---------- Post added at 11:02 AM ---------- Previous post was at 10:59 AM ----------
MrDanMak said:
Ok, I'm on Oreo and I'm gonna give DC Phoenix a shot. Does anyone know which firmware files I need to download? Device is VTR-L09C432
Click to expand...
Click to collapse
if you wanna rollback 7.0 nougat you need VTR-L09B217
Device has been rescued thanks to DC Phoenix and the latest Oreo update.
nice to hear
Related
Okay, I have the HTC One for Sprint. I flashed it using TWRP 2.5 and I can only currently access the bootloader.
I accidentally wiped everything off my phone and when I plug it in my computer sometimes recognizes it has HTCONE or as Android Device, either way I cannot send files over using adb sideload. Gives me the error that there is no device.
Currently my device somehow also got "unrooted" in the process. I am looking at the phone not being able to transfer any roms I want over to install a new OS nor can I restore it to the old OS.
Is there anything I can do?
PS: I did install the drivers and other devices. If someone can please help me even over teamviewer it would absolutely make my day. I have been troubleshooting this device for about 30 hours straight now.
Since you can access bootloader, you'll probably be ok..
What happens when you try to access recovery?
what happens in "fastboot usb" in your bootloader when you command
Code:
fastboot devices
If your device shows just do
Code:
fastboot flash recovery name_of_recovery.img
Download one of these recoveries (since you have the Sprint version) <- this will get you into recovery if you're not already able to access it..
http://techerrata.com/browse/twrp2/m7wls
yup
redbull123 said:
Since you can access bootloader, you'll probably be ok..
What happens when you try to access recovery?
what happens in "fastboot usb" in your bootloader when you command
Code:
fastboot devices
If your device shows just do
Code:
fastboot flash recovery name_of_recovery.img
Download one of these recoveries (since you have the Sprint version) <- this will get you into recovery if you're not already able to access it..
Click to expand...
Click to collapse
Well I have the recovery since thats the only one I can access. Thing is though neither of my computers can recognize the device and I cannot send the rom necessary to boot the OS.
I can access the Bootloader and I can access the Recovery. I cannot access the memory on the phone in order to send files over
Have you tried flashing the RUU? Hopefully this can help:
http://forum.xda-developers.com/showthread.php?t=2250904
sweetnsour said:
Have you tried flashing the RUU? Hopefully this can help:
http://forum.xda-developers.com/showthread.php?t=2250904
Click to expand...
Click to collapse
would I be able to unlock the bootloader after
iivezaj said:
would I be able to unlock the bootloader after
Click to expand...
Click to collapse
important part is getting the phone working again then worry about unlocking bootloader
Can always try flashing a custom ROM using an OTG cable if you've wiped the OS. I always wipe my storage and OS when I do a clean install and then flash the ROM straight from my flash drive ... Obviously you'll need to fastboot a custom recovery, if you are able to.
CheesyNutz said:
important part is getting the phone working again then worry about unlocking bootloader
Click to expand...
Click to collapse
im going to try the method you linked me
When you're in recovery do adb devices. If it shows your phone you can sideload a ROM.
AT&T HTC One
GPe 4.3
hi bro, that happened to me as well, i have installed usb driver but adb cannot detect my device. I was running windows 8 that time but when i used windows 7 adb was able to detect my device with no issues and i was able to transfer custom rom zip file to it. I dont know if that could help you but i'm just sharing my experience.
Sent from my IRON Phone
---------- Post added at 10:32 PM ---------- Previous post was at 10:27 PM ----------
can you even go to recovery? if yes, try using other computer, preferably windows 7 or xp.
Sent from my IRON Phone
---------- Post added at 10:39 PM ---------- Previous post was at 10:32 PM ----------
sorry i didnt read this.
Sent from my IRON Phone
I can access the bootloader and the recovery (switched to PhilZ touch) and sideloaded a couple roms but NONE of them work. One of the roms boots up and goes in a restart loop after hitting the front page (no icons on the screen just top bar) Even the stock version of htc one for sprint didn't work it kept resetting my device.
I tried using the RUU also but it gives me a bootloader error saying it cannot be restored after a few minutes of loading.
Well every rom so far attempted has been a dead end. CM, AOKP, all have booted and started a restart loop. I am not sure if its my kernal or anything else.
I just need some help. What I did notice is that even if the devices were working I had no cell signal. Someone please help lol
iivezaj said:
Well every rom so far attempted has been a dead end. CM, AOKP, all have booted and started a restart loop. I am not sure if its my kernal or anything else.
I just need some help. What I did notice is that even if the devices were working I had no cell signal. Someone please help lol
Click to expand...
Click to collapse
Where are you getting these ROMs from? Have you tried the ones in the Sprint HTC One forums?
Sent from my HTC One using xda premium
The other day I was using my phone and it started to die on me so I plugged it in to charge. I guess it was too low power, so when I plugged it in, it powered down and started charging via phone off. Later I come back to turn it on and it just gets stuck in bootloop. I haveTWRP installed so I cleared the dalvik cache and regular cache. That didn't work. So the next time I just did a factory restore, well after the restore I now have no files on my phone. No OS nothing.
When I plug the phone in via USB the computer chimes and lets me know something was plugged in but I don't get any other messages. If I plug my phone in while in recovery it shows the device with zero folders.
I am sure I can fix it from here, but while using WUGS Root Tool Kit my computer keeps telling me that no "FastBoot Devices" found. How do I fix that?
I would like to just flash an image if possible if someone can walk me through the process or any help would be great.
bannworthrulz said:
The other day I was using my phone and it started to die on me so I plugged it in to charge. I guess it was too low power, so when I plugged it in, it powered down and started charging via phone off. Later I come back to turn it on and it just gets stuck in bootloop. I haveTWRP installed so I cleared the dalvik cache and regular cache. That didn't work. So the next time I just did a factory restore, well after the restore I now have no files on my phone. No OS nothing.
When I plug the phone in via USB the computer chimes and lets me know something was plugged in but I don't get any other messages. If I plug my phone in while in recovery it shows the device with zero folders.
I am sure I can fix it from here, but while using WUGS Root Tool Kit my computer keeps telling me that no "FastBoot Devices" found. How do I fix that?
I would like to just flash an image if possible if someone can walk me through the process or any help would be great.
Click to expand...
Click to collapse
you wiped system, which wipes your rom off your phone. its a VERY easy fix.. just move whatever rom/gapps/supersu to your phone via twrp or adb, then flash it via twrp.
---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------
btw.. dont use toolkits. LEARN how to things yourself, its much easier.
Hello
simms22 said:
you wiped system, which wipes your rom off your phone. its a VERY easy fix.. just move whatever rom/gapps/supersu to your phone via twrp or adb, then flash it via twrp.
---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------
btw.. dont use toolkits. LEARN how to things yourself, its much easier.
Click to expand...
Click to collapse
Could you point me in the direction to the rom/gapps/superu?
bannworthrulz said:
Could you point me in the direction to the rom/gapps/superu?
Click to expand...
Click to collapse
which rom? there are many. even a twrp flashable stock rom.
bannworthrulz said:
Could you point me in the direction to the rom/gapps/superu?
Click to expand...
Click to collapse
Also I installed a stock version of android off the factory images page and copied it over to my phone but TWRP cannot find the zip file?
simms22 said:
which rom? there are many. even a twrp flashable stock rom.
Click to expand...
Click to collapse
Just any stock ROM, I downloaded one from https://developers.google.com/android/nexus/images#fugu but it doesn't show up in TWRP.
bannworthrulz said:
Also I installed a stock version of android off the factory images page and copied it over to my phone but TWRP cannot find the zip file?
Click to expand...
Click to collapse
to flash a factory image, you need to flaah it while in the bootloader, using fastboot. its not a zip.
---------- Post added at 01:15 PM ---------- Previous post was at 01:12 PM ----------
a stock-like rom http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
simms22 said:
to flash a factory image, you need to flaah it while in the bootloader, using fastboot. its not a zip.
Click to expand...
Click to collapse
Honestly man, you are talking to someone who doesn't understand a lot about these things. I need detailed instruction on how to do this. I now don't have twrp installed. I tried to install CM13 and now its stuck in cyanogen recovery mode. This really sucks and need help on how to fix it. Also while in bootloader mode. It says FASTBOOT DEVICE NOT FOUND if it were found I would not be having this issue. I would have a stock rom installed and be on my way. Since it isn't able to find a FASTBOOT DEVICE that is why I am in this current situation.
NVM I figured it out. Had to install adb-setup-1.4.2.exe and now my phone is fixed and up and running.
bannworthrulz said:
Honestly man, you are talking to someone who doesn't understand a lot about these things. I need detailed instruction on how to do this. I now don't have twrp installed. I tried to install CM13 and now its stuck in cyanogen recovery mode. This really sucks and need help on how to fix it. Also while in bootloader mode. It says FASTBOOT DEVICE NOT FOUND if it were found I would not be having this issue. I would have a stock rom installed and be on my way. Since it isn't able to find a FASTBOOT DEVICE that is why I am in this current situation.
NVM I figured it out. Had to install adb-setup-1.4.2.exe and now my phone is fixed and up and running.
Click to expand...
Click to collapse
yup, installing it first helps out, a lot :silly:
bannworthrulz said:
... WUGS Root Tool Kit my computer keeps telling me that no "FastBoot Devices" found. How do I fix that?
Click to expand...
Click to collapse
Boot twrp recovery first....
Hi I have a problem with my honor 5c so I deleted everything from the phone because I wanted to install custom rom but that didnt worked out and now I dont have system on it and twrp recovery was also deleted I unlocked bootloader but every command i type in fastboot is not working even one for oem status but if I type fastboot devices it shows my device and if I go to huawei erecovery and try to recover it it says getting package info failed and when battery discharge and I put it on charger it says
error mode
attention!
Please update system again.
Error!
Func NO: 10(boot image
Error NO: 2(load image)
I am really pissed off and I dont know what to do someone HELP ME PLEASE.:crying:
Simply u can fix
Preview:
Today I faced this issue,and successfully solved,
Shutdown mobile ,then connect to PC and quickly press volume down button automatically goes to bootloader mode , manually flash system,cust,recovery and boot img
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
Then use Dload method u can fix this issue,
Today I post some posts according to this issue on Facebook,
Honor 5c group india
But as I wrote if I go to fastboot/bootloader I cant type any command on every command it says "command not allowed" even the one for oem status and I cant turn on usb debbuging or oem unlock because I dont have os.
Hey @leoleo333, I did exactly the same thing that you did and had exactly the same problem as a result. I considered myself fairly knowledgeable about Android and Huawei/honor mobiles... I tried everything you can think of and spent months trawling the internet for a solution and was unable to fix it. I posted here on XDA and even the most knowledgeable members were unable to help. You should do a search of my XDA posts relating to this.
That said,I am using my honor 5C right now!:laugh: I didn't realise that my warranty was 24 months,I thought it was 12 months. Hence why I spent so many months trying to fix the problem myself. By chance I found out I still had warranty and sent it to the repair centre. It was so easy and straight forward and in a matter of days they had fixed and returned my beloved mobile. I even had a slight defect on the screen as a result of falling over and they even repaired that free of charge!
All I can say is that I hope and pray you have warranty :fingers-crossed: or you can kiss your mobile goodbye. Sorry. Please do let me know if you fix it yourself though, I'd be really interested to know where I went wrong. Thx.
leoleo333 said:
But as I wrote if I go to fastboot/bootloader I cant type any command on every command it says "command not allowed" even the one for oem status and I cant turn on usb debbuging or oem unlock because I dont have os.
Click to expand...
Click to collapse
Is opend erecovery mode
I used Huawei multi tool,
For installing stock recovery,
If you success to flashing stock recovery
Then use dload method
shankarjdhv125 said:
Is opend erecovery mode
I used Huawei multi tool,
For installing stock recovery,
If you success to flashing stock recovery
Then use dload method
Click to expand...
Click to collapse
He has already explained that....!
It doesnt matter if you use multi tool or manual commands...You cant flash stock recovery because every fastboot command comes back 'remote command not allowed' and this is because the os will not boot so you cant enable oem unlock and usb debugging in order to unlock bootloader and have full use of adb/fastboot.
The dload method will install the update.app, it will even go to 100% and say success but it will NOT boot the OS. It will stay stuck on boot animation until the battery dies. Search my posts here on XDA (stuck on boot logo).
I think it has to do with the partitions or the filesystem...I'm afraid i cant help you with that @leoleo333
@leoleo333 , you mention that your bootloader is unlocked...I think you should double check that. if it was unlocked you would be able to use fastboot commands and flash whatever you want. I have read many posts on XDA where members report that their bootloader is unlocked and the device says as much but in fact that is not the case! Let me know how things go. Good Luck.
I managed to fix it couple of days ago with dload method, it actually worked for me i would try it before but i did not had micro sd card
Nice, Im really glad that the dload method was all it took to fix it. Take it easy now.
Bro try this ,added screenshots ,I fixed same issue
iantechie1979 said:
He has already explained that....!
It doesnt matter if you use multi tool or manual commands...You cant flash stock recovery because every fastboot command comes back 'remote command not allowed' and this is because the os will not boot so you cant enable oem unlock and usb debugging in order to unlock bootloader and have full use of adb/fastboot.
The dload method will install the update.app, it will even go to 100% and say success but it will NOT boot the OS. It will stay stuck on boot animation until the battery dies. Search my posts here on XDA (stuck on boot logo).
I think it has to do with the partitions or the filesystem...I'm afraid i cant help you with that @leoleo333
Click to expand...
Click to collapse
Same issue fixed by me
Software install failed but successfully booted
So using a root app disabler I disabled "telephony service" and when I restarted it shutdown immediately, on the newest WW rom it doesnt have a recovery so I cant go in there and wipe to factory reset. Right now I'm getting slot_b is unbootable. My computer recognizes the phone as "Android Bootloader Interface" but when I run "adb devices" it doesnt show up and I cant run fastboot commands even though I'm plugged into the side usb port. Please help me.
trustedenemy said:
So using a root app disabler I disabled "telephony service" and when I restarted it shutdown immediately, on the newest WW rom it doesnt have a recovery so I cant go in there and wipe to factory reset. Right now I'm getting slot_b is unbootable. My computer recognizes the phone as "Android Bootloader Interface" but when I run "adb devices" it doesnt show up and I cant run fastboot commands even though I'm plugged into the side usb port. Please help me.
Click to expand...
Click to collapse
Was the boot img rooted, is that why you have no recovery? If so, just boot to fastboot mode and flash stock boot instead of root, that should have recovery
trustedenemy said:
So using a root app disabler I disabled "telephony service" and when I restarted it shutdown immediately, on the newest WW rom it doesnt have a recovery so I cant go in there and wipe to factory reset. Right now I'm getting slot_b is unbootable. My computer recognizes the phone as "Android Bootloader Interface" but when I run "adb devices" it doesnt show up and I cant run fastboot commands even though I'm plugged into the side usb port. Please help me.
Click to expand...
Click to collapse
Can you go to bootloader screen ?
If you can
Just use the full stock Rom
Flash it
---------- Post added at 04:45 PM ---------- Previous post was at 04:42 PM ----------
https://drive.google.com/file/d/1M2V1Jh2CS5vt1xbQYlDvhxfu0yB6hmZi/view
Download the Full Rom
Extract it
Use the exe file to install with bootloader screen
Ok that was able to get me back to recovery, I tried to wipe and then boot into android, didn't work got the "your device is corrupt and cannot be trusted and will not boot". Still isn't recognized in adb devices so I don't know how I would proceed from here. My device is the Tencent Edition if that helps with raw firmware/rom.
P.S Thank you guys so much for your help I really appreciate it.
trustedenemy said:
Ok that was able to get me back to recovery, I tried to wipe and then boot into android, didn't work got the "your device is corrupt and cannot be trusted and will not boot". Still isn't recognized in adb devices so I don't know how I would proceed from here. My device is the Tencent Edition if that helps with raw firmware/rom.
P.S Thank you guys so much for your help I really appreciate it.
Click to expand...
Click to collapse
Did you fix it ?
rowihel2012 said:
Did you fix it ?
Click to expand...
Click to collapse
No, I still cannot boot into android and it still isnt recognized in adb devices, but I can get into recovery now.
trustedenemy said:
No, I still cannot boot into android and it still isnt recognized in adb devices, but I can get into recovery now.
Click to expand...
Click to collapse
But you get fastboot mode, just plug the USB in side port and flash latest raw WW Rom.
Here's the link to 1908.21
https://drive.google.com/file/d/13Mgz9GhopE-DUsGT3N_5qC283cKkUxYb/view?usp=drivesdk
Once in fastboot mode (the first menu you see, before selecting recovery, start, power off etc is fastboot mode) check your device is recognised with fastboot devices cmd and then run flashall_AFT.cmd that'll get back your working rom . But also, delete or move the original zip from that same extracted folder, the raw rom with the same name confuses the flashall_AFT.cmd
So I flash the most recent firmware you linked and double checked in recovery that it was pushed to the device and it was, but when I try to boot into android I get the asus logo for a second and then it restarts and it will give me a screen that says "Your device is corrupt. It cant be trusted and will not boot" and then has a link to google support .
trustedenemy said:
So I flash the most recent firmware you linked and double checked in recovery that it was pushed to the device and it was, but when I try to boot into android I get the asus logo for a second and then it restarts and it will give me a screen that says "Your device is corrupt. It cant be trusted and will not boot" and then has a link to google support .
Click to expand...
Click to collapse
Did you let the raw rom flash entirely? It should take a minimum of 10 minutes... The phone should reboot twice (I think) as it completes... Maybe try again, but I'm not familiar with that message...
If the phone doesn't reboot, I would let it run for a half hour or so before rebooting...
There we go, I got it to work man, I was just being impatient with the firmware flash but now I got it to work I appreciate your help and patience so much let me got through and thank your comments and then you can flag a mod to take down this thread. Thank you
trustedenemy said:
There we go, I got it to work man, I was just being impatient with the firmware flash but now I got it to work I appreciate your help and patience so much let me got through and thank your comments and then you can flag a mod to take down this thread. Thank you
Click to expand...
Click to collapse
Excellent, glad you got it working again
trustedenemy said:
There we go, I got it to work man, I was just being impatient with the firmware flash but now I got it to work I appreciate your help and patience so much let me got through and thank your comments and then you can flag a mod to take down this thread. Thank you
Click to expand...
Click to collapse
Yes this way always fix bootloap problem
Thanks asus for this easy flashing
Hello Everyone , I have ran into a very bad problem and would appreciate some help. I tried rooting my phone (Razer Phone 2 Atnt varient) with the following method (https://forum.xda-developers.com/razer-phone-2/development/root-pie-update-unlocked-devices-t3905454) after doing so my phone got stuck in bootloop. Therefore, I thought it would be best to unroot the phone (or at least flash the original rom) . So , I tried doing that with the following method (https://forum.xda-developers.com/razer-phone-2/how-to/razer-phone-2-unroot-step-step-t3896529) but that did not solve anything . It still remains stuck on the (Razer logo , Powered by Android) . However, I can still access adb and use fastboot as well. Any quick help would be greatly appreciated . I really can't afford loosing a phone so close to holidays.
Have you read through this whole page yet?
You can flash via fastboot very simply by double clicking the flash_all.bat after extracting the image. Good luck!
https://developer.razer.com/razer-phone-dev-tools/general-instructions/
Hey , thanks for reaching out. I already tried doing the flash all script method through adb. Yet I am still stuck on bootloop. I am really confused.
I can. However, still access fastboot mode. I don't know what I am doing wrong. I should also mention that my bootloader is unlocked. Any further help would be greatly appreciated.
Paradox.7777 said:
I can. However, still access fastboot mode. I don't know what I am doing wrong. I should also mention that my bootloader is unlocked. Any further help would be greatly appreciated.
Click to expand...
Click to collapse
Check your USB port. It might not recognize the device
I'm also having this issue where I have clicked flash all and it either gets stuck on the razer logo or tells me the phone is corrupt and when I hit the power button it just bootloops. I know the port is fine, I have flashed phhusson's Android 10 GSI successfully, but I wanted to change something and it seems that I cannot go back to stock without getting a bootloop.
---------- Post added at 05:55 PM ---------- Previous post was at 05:30 PM ----------
I think I might have solved the issue! In the flash all batch file it flashes two different system images, system.img to partition a and system_other.img to partition b. I edited the flash all file to flash system.img to both partitions cause my phone seems to use partition b instead of a as it's operating partition and it no longer bootloops and in fact has booted to stock! You can give that a try.
Did you flash back to the stick boot image? If not do that first than flash your stock image. If you are still in a boot loop try flashing the old MR0 image to get out of the boot loop. If it works flash the newly released MR2 after.