I desperately need help! let me start off by saying that I'm usually decent at figuring problems out myself I've lurked on XDA for awhile and have had many a phone that I was able to root or fix myself.
However this issue is impossible. I've made a mistake and tried to root my phone without upgrading to the version the root was originally intended for. I was using the CF auto root that I've found here at XDA. Now I am stuck on the "Recovery is not seandroid enforcing" error whenever my phone reboots. Everywhere I've searched says to boot into recovery but this is the message I get when I try to go into recovery?
Also how can I flash the stock firmware when my phone was not successfully rooted? CWRM or TWRP won't work without root access. So that leaves me as follows, I can't flash firmware without root access, I can't get root access or stock firmware without booting into recovery, and I can't boot into recovery without un-corrupted firmware? Do you see this giant loop of impossible I've roped myself into? I've tried using Odin to flash the firmware and I always get the "FAIL! (Auth) message right away. And as far as rooting goes I know of no other way other than with my original firmware.
Sometimes I am able to boot into my phone if I am lucky but I can never get into recovery or factory reset. This is all so frustrating as I had an old phone exactly like this one that I was able to root correctly not before finding out it wasn't unlocked and had to send it back! Is my phone screwed?
My phone is a Galaxy s5 SM-900w8 4.4.2
DJBTB said:
I desperately need help! let me start off by saying that I'm usually decent at figuring problems out myself I've lurked on XDA for awhile and have had many a phone that I was able to root or fix myself.
However this issue is impossible. I've made a mistake and tried to root my phone without upgrading to the version the root was originally intended for. I was using the CF auto root that I've found here at XDA. Now I am stuck on the "Recovery is not seandroid enforcing" error whenever my phone reboots. Everywhere I've searched says to boot into recovery but this is the message I get when I try to go into recovery?
Also how can I flash the stock firmware when my phone was not successfully rooted? CWRM or TWRP won't work without root access. So that leaves me as follows, I can't flash firmware without root access, I can't get root access or stock firmware without booting into recovery, and I can't boot into recovery without un-corrupted firmware? Do you see this giant loop of impossible I've roped myself into? I've tried using Odin to flash the firmware and I always get the "FAIL! (Auth) message right away. And as far as rooting goes I know of no other way other than with my original firmware.
Sometimes I am able to boot into my phone if I am lucky but I can never get into recovery or factory reset. This is all so frustrating as I had an old phone exactly like this one that I was able to root correctly not before finding out it wasn't unlocked and had to send it back! Is my phone screwed?
My phone is a Galaxy s5 SM-900w8 4.4.2
Click to expand...
Click to collapse
TWRP doesn't actually require root, it can do what it wants without it. It needs root to use adb while booted into TWRP but that isn't because TWRP requires root to do it, it is because adb requires root.
Root is sometimes used to flash TWRP via an app.
Have you tried flashing TWRP via Odin then seeing if you can boot to recovery?
Also, if you get lucky and the device boots into system, try going to system settings>backup and reset then find the factory reset setting, try factory reseting it that way and then see if you can flash TWRP or your stock firmware via Odin.
Are you booted into download mode when you are flashing stock firmware in Odin?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
TWRP doesn't actually require root, it can do what it wants without it. It needs root to use adb while booted into TWRP but that isn't because TWRP requires root to do it, it is because adb requires root.
Root is sometimes used to flash TWRP via an app.
Have you tried flashing TWRP via Odin then seeing if you can boot to recovery?
Also, if you get lucky and the device boots into system, try going to system settings>backup and reset then find the factory reset setting, try factory reseting it that way and then see if you can flash TWRP or your stock firmware via Odin.
Are you booted into download mode when you are flashing stock firmware in Odin?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I've tried doing a factory reset if I get lucky and it takes me into the main screen but immediately it gives me the "seandroid" error message the same as if I press volume up, menu, and power. I am able to boot onto download mode ive tried this to flash firmware but Odin gives me a Fail (Auth) message each time. I'm not even sure if TWRP has a version for my phone yet I'm not sure much about TWRP. If there's a way I can break this chain I'll try anything.
TWRP working so far
I found a custom version of TWRP and thankfully was able to flash it on my phone using odin. I was also able to get the Root working with TWRP as well. I'm going to play around with the phone awhile longer to see if everything is fine. I no longer get the "seandroid" error message while booting up the phone however it does briefly appear upon loading into the recovery but so far TWRP takes its place after a few seconds. It worried me at first but as long as TWRP kicks in each time it's a good sign. I'll leave the thread as unresolved for a while longer in case anyone has any further suggestions or in case something goes wrong but all my thanks goes out to Droidriven!
DJBTB said:
I found a custom version of TWRP and thankfully was able to flash it on my phone using odin. I was also able to get the Root working with TWRP as well. I'm going to play around with the phone awhile longer to see if everything is fine. I no longer get the "seandroid" error message while booting up the phone however it does briefly appear upon loading into the recovery but so far TWRP takes its place after a few seconds. It worried me at first but as long as TWRP kicks in each time it's a good sign. I'll leave the thread as unresolved for a while longer in case anyone has any further suggestions or in case something goes wrong but all my thanks goes out to Droidriven!
Click to expand...
Click to collapse
Good to good, glad you made progress, hopefully that's all you'll need to do.
I don't see how I was much help though. All I did was explain TWRP not needing root.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Good to good, glad you made progress, hopefully that's all you'll need to do.
I don't see how I was much help though. All I did was explain TWRP not needing root.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Understandable, however I never would of thought to try TWRP without your suggestion. It seems when you are stumped the answer is right there all it needs is someone else to chime in and point it out. Like trying to beat a hard level over and over sometimes just give the controller to someone else and they will get it their first try lol.
DJBTB said:
Understandable, however I never would of thought to try TWRP without your suggestion. It seems when you are stumped the answer is right there all it needs is someone else to chime in and point it out. Like trying to beat a hard level over and over sometimes just give the controller to someone else and they will get it their first try lol.
Click to expand...
Click to collapse
By the way, when flashing stock firmware via Odin, root is not required. The only time root is required to flash stock ROM is when flashing a stock firmware that has been converted into a custom recovery stock flashable.zip. It is not uncommon for someone in this community to convert stock firmware into a recovery flashable .zip. This is used so that the device doesn't lose root or custom recovery. When flashing stock the normal way via PC, it removes root and reverts the device back to stock recovery. Then the device has to be rooted and flash recovery again. The stock flashable .zip avoids all of that because it gets flashed in custom recovery, this way, recovery is not lost and root is not lost.
This only applies "IF" someone converts the firmware to flashable .zip. Not all devices have a stock flashable .zip available though.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Related
So. I'm sorry to say, but this phone has given the biggest headache. Here's the background:
I really only use this phone for entertainment and stuff. BUT I decided to root and unlock the bootloader, somehow or another the phone apparently lost root a few times (According to some users here) but never lost SuperUser or anything. I've never been able to flash a rom on this thing. Then a few weeks ago the phone just encountered an error of some sort and would only get to the ICS boot animation and loop over and over. I just gave up on it. Then one day I decided to play with it. I got it into fastboot and then into recovery, (Not CWM Recovery) and was able to get it all set up again. So I figured I'd give it one more shot. I downloaded CWM and downloaded recovery, and a custom rom. tried to flash through fastboot>recovery but it's still the stock recovery, not CWM recovery. So I factory resetted it etc and started from scratch. Now if I download CWM it WILL NOT download recovery. It gets about 99% of the way and tells me: "An error occurred while attempting to run privileged commands!" If I download it from a link I can't open the file....... Someone help I just want a good JellyBean Rom. :crying:
Edit: I've Googled as much as I could stand and still haven't come across anything entirely helpful. Please explain so I could understand. Pictures help if needed lol
Anyone?
You can't use clockworkmod app to flash recovery without root.
Get the fastboot image of cwm recovery ( not the app). Or twrp. Flash it with fastboot.
Boot directly into it and flash what you want. If you boot up a stock os it overwrites the custom recovery on boot.
clockworkmod app sucks IMHO and should never be used for anything period. Not fond of the recovery itself either.
Tried looking everywhere, but couldn't really find anything. Any help is appreciated!
Alright some background info
I rooted my phone and unlocked the bootloader successfully. I wanted to do more, so I flashed TWRP onto my phone using JRummy's ROM Installer. I followed all the steps and successfully booted into TWRP recovery. I created a Nandroid backup and when I tried rebooting my phone it gets stuck on the 4G LTE boot animation.
I then tried wiping the cache etc. and restoring the backup I had just created. To no avail, the phone kept getting stuck on the boot animation. I've tried restoring the backup multiple times with no success.
On my last attempt I checked another box on the TWRP restore page, I think it was the VG5 verification or something. Halfway through what I though was going to be a successful restore, my phone reset and got stuck in the boot animation again. Now when I boot into recovery it's the stock recovery, not the custom TWRP as before. Tried clearing everything/factory reset and it still stuck on boot animation.
As a college student I'd like to get this figured out as soon as possible (hopefully before midweek, Friday at latest). If I can figure this out with your help I'll be very grateful.
If I can't find any other way, I'm willing to flash stock back using ODIN and seeing how that turns out. Also my home button is a little sticky so I doubt the Verizon worker would be able to boot into recovery or download mode.
Any suggestions?
For those of you TL;DR
1) Rooted phone / unlocked bootloader
2) Flashed custom TWRP recovery onto phone
3) Created a Nandroid backup from recovery
4) Tried rebooting and gets stuck on 4G LTE boot animation screen
5)Wiped cache etc. and retried multiple times. Doesn't work
EDIT: I flashed stock through ODIN and everything seems to be in order. I'll be trying to root and recover everything through TWRP again and if it doesn't work oh well. My end goal is to have a custom ROM
Maybe this will help you
Okay for your problem, if you can go to Download Mode and your recovery back to its stock form, your last option will be flashing it through Odin. There are several method and guides How to Flash via Odin. I will link to you all the guide and try it so your phone will be back to normal. Choose only 1 method
1.) [HOW-TO] Unbrick your soft bricked Galaxy S III (+ bootloader brick)
2.) Verizon Offcial VRBMB1 Odin Files, VRBMF1 Odin Files, and VRBMF1 Update Files
Must read first the guide and download all the necessary.
If your phone gets revived, you can try this method and choose TWRP recovery and update the recovery.
Click Here If Your Ready To Root/Unlock Bootloader/Flash Recovery
Note: You know the responsibility when you root your phone, I am not nor them who created this thread have responsibility to your phone, it is your choice.
Thanks for replying
I've got everything back in order now. I'll try installing AOKP or something
Your Welcome
That's good to hear
I have a Moto G X1032 rooted with TWRP installed. I've been using the stock firmware for 4.4.2 without any issues for a while, but after June 6th's OTA update to 4.4.3, my phone has gotten stuck in a boot loop. It turns on and runs Android as usual, without any issues, for less than a minute and then shuts down. It then continues to boot back up and continue the process. The only way to stop the loop is to boot into the bootloader from TWRP and power off the phone from there. Luckily I have a backup to that reverts me back to 4.4.2, which successfully stops the loop. But after several attempts to update to 4.4.3, it has become quite clear that this boot loop is inevitable unless I stick with 4.4.2. I read an article that seems to address some conflict with rooted phones and 4.4.3, but I'm not quite sure what the conflict is. Can anyone explain to me why this boot loop is most likely happening, what I could do to fix it, or if it is even possible to have a rooted X1032 with 4.4.3 installed? Any help whatsoever would be greatly appreciated. Thank you.
Are you saying you tried to install the OTA with TWRP installed and not the stock recovery?
Just go into recovery clear all cache,kavik cache that should do
NerdNoob1210 said:
I have a Moto G X1032 rooted with TWRP installed. I've been using the stock firmware for 4.4.2 without any issues for a while, but after June 6th's OTA update to 4.4.3, my phone has gotten stuck in a boot loop. It turns on and runs Android as usual, without any issues, for less than a minute and then shuts down. It then continues to boot back up and continue the process. The only way to stop the loop is to boot into the bootloader from TWRP and power off the phone from there. Luckily I have a backup to that reverts me back to 4.4.2, which successfully stops the loop. But after several attempts to update to 4.4.3, it has become quite clear that this boot loop is inevitable unless I stick with 4.4.2. I read an article that seems to address some conflict with rooted phones and 4.4.3, but I'm not quite sure what the conflict is. Can anyone explain to me why this boot loop is most likely happening, what I could do to fix it, or if it is even possible to have a rooted X1032 with 4.4.3 installed? Any help whatsoever would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
secretkloud said:
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
Click to expand...
Click to collapse
Thank you. I will try that. Before I do though, do you know of any places I could find 4.4.3 online, so I could just download it from my PC and flash it over via sideload? I usually prefer to flash things that way, rather than straight from the phone.
bozzykid said:
Are you saying you tried to install the OTA with TWRP installed and not the stock recovery?
Click to expand...
Click to collapse
Yes. This is my first time doing so, excuse my lack of knowledge on the subject. In retrospect, I suppose I should have known there must be a different method with which I install it. Secretkloud gave me a good suggestion though. Is there a reason in particular as to why I can't do OTA updates with custom recovery installed?
secretkloud said:
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
Click to expand...
Click to collapse
I just downloaded the zip from my phone and flashed it from Phillz recovery. It worked very well and the update was successful. Thanks for pointing me to Phillz recovery by the way. It's the only functional recovery image that allows me to mount the sdcard.
NerdNoob1210 said:
Thank you. I will try that. Before I do though, do you know of any places I could find 4.4.3 online, so I could just download it from my PC and flash it over via sideload? I usually prefer to flash things that way, rather than straight from the phone.
Click to expand...
Click to collapse
Copy the one you have in your phone onto your PC. Smallest chance of error if you do it that way...
it's not easy getting out of the loop.
I did a factory reload of a rooted phone with CWM.
Now for the CWM issue the Moto G loaded OK and then said there was an update for android to fix some bugs. This was 4.4.3. I loaded it and it gets half way and it then says
"Signature verification fail"
at the bottom of the screen and
" Install Untrusted Package"
The options are yes, no or go back
at the top....
whichever one I try it then tries to boot shows the Android / Motorola screen and starts up gets a txt message for 2-3 seconds... it then goes back to Android CWM recovery with the same options as above and repeats the process. again and again and again. No function keys will stop this cycle which just repeats again. This continues until the battery dies.
any ideas ? how can I override this action in CWM v6.0.4.6 and force it to do a factory reload ? any help or advice much appreciated.
If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose.
Sent from my XT1032 using XDA Premium 4 mobile app
NerdNoob1210 said:
If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
unfortunately I can't get into bootloader. I can connect usb and it makes no difference. therefore adb commands dont work. it just goes straight into screen described with those three options. I'm hoping that there is an override action in CWM which isn't power and volume down which do nothing.
thanks for the suggestion tho. it was a good idea.
Hm... Without access to the boot loader, I'm not sure there's much of anything you can do anymore... You've completely lost the ability to communicate any sort of commands to your phone save for the 3 options that menu provides. I assume that what CWM is trying to do is install the zip from your cache and is failing to do so. The only viable option would be to flash a new recovery image and install the zip manually, but that's impossible for you given your current circumstances. I would give up looking for an override command for CWM, your best hope is to find an alternative means with which you can access your boot loader. I suggest you start a thread dedicated to your issue and see if a more experienced user can provide you with the information you need. Sorry, I hope you get the help you need. :/
Sent from my XT1032 using XDA Premium 4 mobile app
Thanks for trying to help. I have followed your advice and opened a thread
NerdNoob1210 said:
Hm... Without access to the boot loader, I'm not sure there's much of anything you can do anymore... You've completely lost the ability to communicate any sort of commands to your phone save for the 3 options that menu provides. I assume that what CWM is trying to do is install the zip from your cache and is failing to do so. The only viable option would be to flash a new recovery image and install the zip manually, but that's impossible for you given your current circumstances. I would give up looking for an override command for CWM, your best hope is to find an alternative means with which you can access your boot loader. I suggest you start a thread dedicated to your issue and see if a more experienced user can provide you with the information you need. Sorry, I hope you get the help you need. :/
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey guys. I'm in a hell of a bind and could use some help.
My Galaxy Note 5 (N920T, rooted) was running fine on this ROM: https://forum.xda-developers.com/tm...m-qc6-lite-rom-bloated-knoxed-odexed-t3598686 ; however, I had disabled OEM unlock at one point to try and fix a random app I was playing with. The battery died not long after, causing the phone to reboot. On power, it failed to boot due to custom binary block from FRP, so I decided to try and run the usual troubleshooting of flashing a stock ROM via Odin. Stock images will flash (tried 5.1.1, 6.1, and 7); however, when they try to install I get the error for no DRK. Sometimes I'll also get a dm-verity error as well... So I then tried to flash TWRP or any recovery via Odin to let me fix this issue; however, any custom recoveries I try to flash are being blocked by FRP.
So, I'm in a loop. I can't use my initial ROM because FRP, however I also can't install a stock ROM because of missing DRK, AND I can't fix the DRK or verity errors because I can't install a recovery capable of doing so because of FRP.
IMEI is intact when I look into Download mode, but I can't seem to get anything to work. I've tried the FRP Tool and crack, but that gives me FRP blocks as well (USERDATA).
Am I boned?
B U M P
Anyone?
same situation, going to try flashing it to stock. Can we just flash a stock bootloader or do we need to start over?
Got it working by flashing stock rom with odin so maybe not exact same situation as you. Hard to find a filehosting site with good download speeds and spent all day trying to get latest stock note 5 firmware. Well good for now.. All started because of a wrong flip of a switch *bangs head on desk*
You need to do a few things. First you need to wipe everything in TWRP including format data, so love your files to some other storage. In Odin go to options and turn off auto reboot. Turn on f reset time, phone bootloader update and Nand Erase All. You need to know that this doesn't always work, if you can't unlock it this way try disabling encryption after flashing stock and TWRP and flash Magisk. Let me know how it goes.
Metabolic12 said:
You need to do a few things. First you need to wipe everything in TWRP including format data, so love your files to some other storage. In Odin go to options and turn off auto reboot. Turn on f reset time, phone bootloader update and Nand Erase All. You need to know that this doesn't always work, if you can't unlock it this way try disabling encryption after flashing stock and TWRP and flash Magisk. Let me know how it goes.
Click to expand...
Click to collapse
Got as far as getting the firmware flashed via Odin, but when I first boot I get "Device does not have DRK" error. I cannot install TWRP or any custom recovery through Odin due to FRP lock.
x24veggie said:
Got as far as getting the firmware flashed via Odin, but when I first boot I get "Device does not have DRK" error. I cannot install TWRP or any custom recovery through Odin due to FRP lock.
Click to expand...
Click to collapse
if all you are getting is frp lock just flash back to stock like I did and start over rooting etc.
craig198 said:
if all you are getting is frp lock just flash back to stock like I did and start over rooting etc.
Click to expand...
Click to collapse
That's not all. Basically, it goes,
Flash back to stock
Reboot
Can't finish ROM install because DRK is unavailable
Can't install anything in locked, stock android recovery
TWRP, autoroot, etc. is blocked from Odin by FRP
craig198 said:
same situation, going to try flashing it to stock. Can we just flash a stock bootloader or do we need to start over?
Got it working by flashing stock rom with odin so maybe not exact same situation as you. Hard to find a filehosting site with good download speeds and spent all day trying to get latest stock note 5 firmware. Well good for now.. All started because of a wrong flip of a switch *bangs head on desk*
Click to expand...
Click to collapse
No. It started because you didn't back up your phone properly with twrp before going flash crazy
---------- Post added at 08:52 AM ---------- Previous post was at 08:47 AM ----------
x24veggie said:
That's not all. Basically, it goes,
Flash back to stock
Reboot
Can't finish ROM install because DRK is unavailable
Can't install anything in locked, stock android recovery
TWRP, autoroot, etc. is blocked from Odin by FRP
Click to expand...
Click to collapse
https://www.google.ca/amp/s/forum.x...to-solve-dm-verity-verification-t3293306/amp/ have you tried this? If we can figure this out please don't ever play with oem or have a stock recovery ? that's your security blanket
I hope someone reads this as I'm lost for ideas. First time trying to root a device, I'm using an s8+ and somehow managed to mess up installing twrp using Odin.
Now when I try to re flash twrp it comes up with error, 'only official released binaries are allowed to be flashed'. Also I think I managed to erase the recovery program that comes with the phone as when I try to boot in recovery it now comes up with error message 'No command'.
I have reinstalled the stock firmware using Odin but that hasn't fixed anything.
Anyone got any ideas or insite into this problem. Any advice would be very appreciated as I'm so keen to discover rooting!!
Philnicolls89 said:
I hope someone reads this as I'm lost for ideas. First time trying to root a device, I'm using an s8+ and somehow managed to mess up installing twrp using Odin.
Now when I try to re flash twrp it comes up with error, 'only official released binaries are allowed to be flashed'. Also I think I managed to erase the recovery program that comes with the phone as when I try to boot in recovery it now comes up with error message 'No command'.
I have reinstalled the stock firmware using Odin but that hasn't fixed anything.
Anyone got any ideas or insite into this problem. Any advice would be very appreciated as I'm so keen to discover rooting!!
Click to expand...
Click to collapse
Seeing No command is normal, with an icon of a dead android lol, thats stock recovery, blue screen, i got that all time, but after waiting about 30 seconds and pressing the buttons, i got the mnue to pop up to reset cache, reboot phone, wipe data etc.
As for TWRP, are you flashing the correct one, dream2lte??, download the latest one, the dream2lte.img .tar file, from the TWRP official website - - https://dl.twrp.me/dream2lte/twrp-3.3.1-0-dream2lte.img.tar.html.
I had this issue trying to flash TWRP with standard odin, i had to use a modded version of odin to flash it, even prince cosmy version didnt work for me.
I have attatched the ODIN i use, its a 7zip file.
Thank you, after trying a few more things the twrp file you gave me worked. I now have a fully rooted s8!!!! Your a legend.