Related
Hey guys i recently posted a question about whether my i9300t would be able to safely run cyanogenmod 11, the answers i received said that i would not have a problem, i had already flashed the S4 revolution rom successfully, aswell as cyanogenmod 10.2, but when attempting to flash CM11 and AOKP (4.4.2) it just came up with a red 'FAILED!' sign for both of them.. im using the latest TWRP
Any ideas? much appreciated, thanks Guys
smiley118118 said:
Hey guys i recently posted a question about whether my i9300t would be able to safely run cyanogenmod 11, the answers i received said that i would not have a problem, i had already flashed the S4 revolution rom successfully, aswell as cyanogenmod 10.2, but when attempting to flash CM11 and AOKP (4.4.2) it just came up with a red 'FAILED!' sign for both of them.. im using the latest TWRP
Any ideas? much appreciated, thanks Guys
Click to expand...
Click to collapse
not sure if it is also valid for CM, but most rom devs recommend not to use TWRP for flashing a 4.4 rom. Maybe try Philz?
Format System, data, preload and sd card (internal memory) while on TWRP, aswell factory reset wipe all data and dalvik cache and then flash those ROMs
ShltHappens said:
Format System, data, preload and sd card (internal memory) while on TWRP, aswell factory reset wipe all data and dalvik cache and then flash those ROMs
Click to expand...
Click to collapse
yeah i did everything the way youre supposed to.. it just comes up with some error..
will it be safe for me to simply flash the clockworkmod .zip file in TWRP?? will it simply just replace it?
smiley118118 said:
will it be safe for me to simply flash the clockworkmod .zip file in TWRP?? will it simply just replace it?
Click to expand...
Click to collapse
If you want to switch to a cwm based try philz. You can flash it in recovery and simply reboot recovery
Sent from my Nexus 7 (2013)
Hi. I tried to flash newest version of GApps (full modulare which I have never use before, allways the stock) and newest version of CyanogenMod 11 Nightly. I'm also using CWM Recovery 6.0.4.6 in my GT-I9300. Someone in CyanogenMod forums told me to wipe all data/factory, cache and dalvic cache to make CM's trebuchet, before flashing a new ROM and GApps.
I tried that and result was that I'm getting the ****ing "PHONE HAS STOPPED WORKING" - problem.. Huger problem is that I need this phone tommorow in work, and it ruins my day totally if I don't get it work by tommorow.
Because of Wipe ALL data / factory reset, I do not have even any backup file in my device. What to do to fix it!?
MURRRRRRRRRRRRRR said:
Hi. I tried to flash newest version of GApps (full modulare which I have never use before, allways the stock) and newest version of CyanogenMod 11 Nightly. I'm also using CWM Recovery 6.0.4.6 in my GT-I9300. Someone in CyanogenMod forums told me to wipe all data/factory, cache and dalvic cache to make CM's trebuchet, before flashing a new ROM and GApps.
I tried that and result was that I'm getting the ****ing "PHONE HAS STOPPED WORKING" - problem.. Huger problem is that I need this phone tommorow in work, and it ruins my day totally if I don't get it work by tommorow.
Because of Wipe ALL data / factory reset, I do not have even any backup file in my device. What to do to fix it!?
Click to expand...
Click to collapse
Did u format system or just normal factory reset?
Sent from my GT-I9300 using xda app-developers app
JellyYogurt said:
Did u format system or just normal factory reset?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I did format system and wiped all caches. I did everything and ****ed everything up. Now I dont have backup or anything. Flashing and wiping caches doesn't work, allways same prblem when I start my phone again.
What to do to fix the problem?
Can you boot into recovery? Have you got a external sd card?
If yes put another Rom on ext SD (if you have a SD card adapter for computer) boot into recovery and flash again!
If not can you get into download mode? If yes flash a stock Rom with Odin..
Sent from my GT-I9300 using XDA Premium 4 mobile app
tallman43 said:
Can you boot into recovery? Have you got a external sd card?
If yes put another Rom on ext SD (if you have a SD card adapter for computer) boot into recovery and flash again!
If not can you get into download mode? If yes flash a stock Rom with Odin..
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you for helping. I flashed stock 4.3 Jelly Bean with Odin by using XDA's tutorial. Now I need to root my phone again to get CyanogenMod 11 and KitKat, but It's okay. Still don't know how to get CM11's Trebuchet work correctly. Problem is that if I flash PAGapps stock package, I get the phone work correctly, but Trebuchet disappears. If I flash full package of PAGapps, Trebuchet should work, but then this error happends and I need to flash stock rom with Odin.
What to try next?
MURRRRRRRRRRRRRR said:
Thank you for helping. I flashed stock 4.3 Jelly Bean with Odin by using XDA's tutorial. Now I need to root my phone again to get CyanogenMod 11 and KitKat, but It's okay. Still don't know how to get CM11's Trebuchet work correctly. Problem is that if I flash PAGapps stock package, I get the phone work correctly, but Trebuchet disappears. If I flash full package of PAGapps, Trebuchet should work, but then this error happends and I need to flash stock rom with Odin.
What to try next?
Click to expand...
Click to collapse
If you are flashing custom roms you do not need to root, custom roms come already rooted...I'm not sure which gapps are compatible with cm11 but have you tried Banks gapps I use them on Fusion kitkat rom (if they are compatible)..
Obviously there is some app in the full gapps that is causing your problem.As for CM11 launcher can't you use another launcher?
I searched the internet and threads on XDA for this problem but couldn't really find one!
The problem is- My Galaxy S3 (GT-I9300) doesn't boot any AOSP/AOKP/CM ROMs! It's just the bootanimation and DONE! For hours and hours the bootanimation only! But I can flash any Sammy 4.3 / 4.4 ROMs! They boot! They work properly!
I used to change to AOSP to Sammy and vice versa so many times with no issues. One day I downloaded the UltimaAOSP Valhalla ROM and flashed it. This was the first time my S3 didn't boot. I flashed custom Kernels like boeffla on it but all in vain. It was stuck on the bootanimation. I flashed NeatROM AOSP on top of it, which worked properly. Then it was with the fusion sp ROM that it didn't boot again. Again I flashed NeatROM AOSP on top of it (it's my favorite ROM), which I used just to copy some other ROM from my PC to my phone.
Now, I'm on my Stock ROM which came with my phone since so long! I'm shocked to see now NO AOSP ROMs are booting! I've used C-ROM, NeatROM, Resurrection Remix and SOKP Milestone. I have the ROMs' ZIP files and also a Nandroid Backup which I made when I changed to other ROMs. Not the ZIP files neither the Nandroid Backups are helping! ZIP files get flashed succesfully (I wipe the data & cache & dalvik-cache every time) and the Nandroid Backups get restored successfully! But always the phone gets stuck on the bootanimation!
I always moved to AOSP from Sammy (never Sammy to Sammy) but this time I gave it a shot.
Result : All the Samsung ROMs are flashing, working properly, even the Nandroid restores boot. I flashed my newly downloaded FlashingDroid Sammy 4.4 ROM which also works.
BUT I CAN'T GET THE AOSP ROMs onto my phone!
My thought (it could be wrong) : Is it to do something with the data in a partition other than system, data, and cache? Some partition which has stored files needed to boot Sammy ROMs and is preventing AOSP ROMs to start?
HELP!
:crying:
MORE UPDATED INFO ON POST #6
::ROBLEM SOLVED:::
Wipe system, data, cache and preload partitions manually in mounts and storage in CWM Recovery.
DONE! AOSP Working!
Suggests something is being left behind that aosp objects to. Try the rescue firmware in general forum, wipe internal sd and preload.
boomboomer said:
Suggests something is being left behind that aosp objects to. Try the rescue firmware in general forum, wipe internal sd and preload.
Click to expand...
Click to collapse
Have lots of data on my internal memory! Still I deleted lots of unwanted files. Any other way to wipe the hidden preload partition other than using Philz Recovery? I remember I flashed Philz after which I couldn't restore any of my Nandroid Backups backed up with CWM Recovery..
Sent from my GT-I9300 using XDA Premium 4 mobile app
In cwm mounts and storage wipe preload
Press thanx if i helped you in anyway...
Update - Got More Info
Update : Just noticed that when it's the bootanimation on the screen after flashing an AOSP ROM, pressing any of the buttons on the phone vibrates the phone vigorously 2 times.. why??
Also, I want to ask about the connection between a kernel and a bootanimation without starting a new thread 'cause I think it's the solution to my problem here.. The data which I probably suspect that prevents AOSP ROMs from booting is some different bootanimation file? I mean when I'm on a Sammy ROM, I started to flash different bootanimations after flashing some CWM Custom Bootanimation ZIP file. The bootanimation changes on all Kernels on Sammy ROMs -except 1 that is the boeffla kernel. The strange thing is that the first custom bootanimation I had flashed (after flashing Boeffla's Sammy Kernel) when I switched to Sammy from my last AOSP was the hTC One Bootanimation which worked fine (the bootanimation successfully changed). After that, it never changed. My phone always booted up showing the hTC One Bootanimation no matter how many times I flashed another bootanimation ZIP or the CWM ZIPs which enable/disable Custom bootanimations. But! When I changed to any other kernel (the stock that came with the ROM/GoogyMax 2/AGNi), the bootanimation was the last one flashed by me before changing the kernel. I could change the bootanimations successfuly every time after that. Now, I flashed Android Revolution HD ROM and was on Stock Kernel. As soon as I changed to boeffla kernel (without flashing any other ZIP), the bootanimation changed! (automatically!) And it was again the same old hTC One Bootanimation.
Can someone please tell me WHERE is this bootanimation data and the data that prevents AOSP ROMs to boot is stored? Certainly not in the data or system or cache partition...
Update 2 : Just figured out where the automatic htc bootanimation magic happened. The hTC bootanimation.zip file was found in data/local . However, I always knew the bootanimation directory as system/media.. So now, is it safe for me to delete all files in data/local 'cause it seems it is the problem for AOSP ROMs?
Sent from my GT-I9300 using XDA Premium 4 mobile app
the main thing i can think of is your trying to go back to jb roms which you cant do as far as i know try flashing kitkat based roms
jimbobpro87 said:
the main thing i can think of is your trying to go back to jb roms which you cant do as far as i know try flashing kitkat based roms
Click to expand...
Click to collapse
I'm not trying to go back to Jelly Bean! I'm flashing AOSP based ROMs of KitKat 4.4.2 which don't boot!
SOLVED!
Yayy!
I guess I got a solution!
Wiped system, data, cache and preload partitions manually in mounts and storage in my CWM Recovery.
DONE! AOSP Working!
:victory:
THANKS TO ALL WHO HELPED! :angel:
Thank you for your post.
I am having the same problem, phone not booting past boot animations using aosp ROMs. Haven't tried Sammy ROM to test the theory yet but will try soon.
How do you wipe preload? In mounts and storage, I get an error when trying to mount or format preload using CWM 6.0.4.7
I don't see an option to wipe anything other than data, cache, or dalvic.
alaska_ryder said:
How do you wipe preload? In mounts and storage, I get an error when trying to mount or format preload using CWM 6.0.4.7
I don't see an option to wipe anything other than data, cache, or dalvic.
Click to expand...
Click to collapse
Strange- it happened that day but not now. Even I get an error formatting preload. But! I guess the problem is the system partition! There IS an option to format /system in mounts and storage option on the first screen.
Sent from my GT-I9300 using XDA Premium 4 mobile app
This is really an old post i think.
But, can someone answer me please, ive been searching for This maybe for more than a year. Can someone please help me? @Paresh Kalinani
I have the exact same issue.
My device: Grand Prime (G530FXXU1AOJI baseband)
Stock android: 5.0.2
Recovery: TWRP 3.1.0.0
I have booted many Samsung roms and also ported many of them like J5's 5.1.1 , On7's 5.1.1 rom and many other 5.1.1 and 5.0.2 roms and all of them work perfectly. But when it comes to AOSP ROMS each of them keeps loading at the booting animation screen. Ive tried many roms like RR, AOSP Extended, Cyanogenmod, LINEAGEOS, All of these 5.1.1 , 7.1.1.
It booted for others with the exact Same variant as mine too.
Please help me?
Id been really grateful.
Thanks,
Eden532
Eden532 said:
This is really an old post i think.
But, can someone answer me please, ive been searching for This maybe for more than a year. Can someone please help me? @Paresh Kalinani
I have the exact same issue.
My device: Grand Prime (G530FXXU1AOJI baseband)
Stock android: 5.0.2
Recovery: TWRP 3.1.0.0
I have booted many Samsung roms and also ported many of them like J5's 5.1.1 , On7's 5.1.1 rom and many other 5.1.1 and 5.0.2 roms and all of them work perfectly. But when it comes to AOSP ROMS each of them keeps loading at the booting animation screen. Ive tried many roms like RR, AOSP Extended, Cyanogenmod, LINEAGEOS, All of these 5.1.1 , 7.1.1.
It booted for others with the exact Same variant as mine too.
Please help me?
Id been really grateful.
Thanks,
Eden532
Click to expand...
Click to collapse
Have you flashed the rom then factory reset?
Beamed in by telepathy.
shivadow said:
Have you flashed the rom then factory reset?
Beamed in by telepathy.
Click to expand...
Click to collapse
Nope.
I wiped system, data, cache and dalvik cache the flashed the rom and the rebooted?
Do I have to do a factory reset then?
Thanks a lot for the immediate response.
Eden532 said:
Nope.
I wiped system, data, cache and dalvik cache the flashed the rom and the rebooted?
Do I have to do a factory reset then?
Thanks a lot for the immediate response.
Click to expand...
Click to collapse
Well, what you did was butter than a factory reset.
Factory reset means wiping data, cache and dalvik cache.
I would like you to do something first, try downloading the latest stock firmware for your phone from sammobile, and then flash it with Odin, then try flash AOSP roms again, maybe you have an old bootloader.
MigoMujahid said:
Well, what you did was butter than a factory reset.
Factory reset means wiping data, cache and dalvik cache.
I would like you to do something first, try downloading the latest stock firmware for your phone from sammobile, and then flash it with Odin, then try flash AOSP roms again, maybe you have an old bootloader.
Click to expand...
Click to collapse
Im running the latest firmware which id flashed through odin.
AOSP roms still not booting.
I had wiped those partitions before i flashed the rom. I did not wipe after i flashed them.
Eden532 said:
Im running the latest firmware which id flashed through odin.
AOSP roms still not booting.
I had wiped those partitions before i flashed the rom. I did not wipe after i flashed them.
Click to expand...
Click to collapse
Are you sure it's the latest one?
Did you check Sammobile.com?
The latest one was released in 1st Feb 2017.
Also please check the IMEI of your phone by typing *#06#, because if you've a problem with efs partition you may not be able to flash any AOSP Rom (happened to a friend before..he had sim working without IMEI!!)
Also what is your country code?
As stated above, check your imei is still OK then from a working stock state:
Root it.
Flash custom recovery.
Flash the custom rom twice and then wipe data/cache. Do not wipe system!.
If that doesn't work then try the above but instead of wipe data/cache do a factory reset.
Beamed in by telepathy.
MigoMujahid said:
Are you sure it's the latest one?
Did you check Sammobile.com?
The latest one was released in 1st Feb 2017.
Also please check the IMEI of your phone by typing *#06#, because if you've a problem with efs partition you may not be able to flash any AOSP Rom (happened to a friend before..he had sim working without IMEI!!)
Also what is your country code?
Click to expand...
Click to collapse
My country code is XSG but ill try flashing the THL latest version and again report.
I was trying to check my IMEI number it shows UNKNOWN APPLICATION but sim and other modem related stuff works really fine.
Is it something to do with this?
shivadow said:
As stated above, check your imei is still OK then from a working stock state:
Root it.
Flash custom recovery.
Flash the custom rom twice and then wipe data/cache. Do not wipe system!.
If that doesn't work then try the above but instead of wipe data/cache do a factory reset.
Beamed in by telepathy.
Click to expand...
Click to collapse
I did flash the custom rom twice but still no good.
(And also i checked the IMEI via a custom Sammy rom)
Eden532 said:
My country code is XSG but ill try flashing the THL latest version and again report.
I was trying to check my IMEI number it shows UNKNOWN APPLICATION but sim and other modem related stuff works really fine.
Is it something to do with this?
Click to expand...
Click to collapse
This is the latest firmware for United Arab Emirates:
https://androidfilehost.com/?fid=385035244224412750
Flash it and see if the problem solved :good:
MigoMujahid said:
This is the latest firmware for United Arab Emirates:
https://androidfilehost.com/?fid=385035244224412750
Flash it and see if the problem solved :good:
Click to expand...
Click to collapse
Thank you so much for sending the link, Its really difficult to download from sammobile.com . Ill check it right away and report. Thanks.
i have samsung s2 GT-I9100, version of 4.2.2, I9100XXMS2, im using Omega v13 rom, i want to change it to cm11 kitkat version, i dont know the steps, i cant just flash it using cwm 6.4, always says aborted, cant open the zip file of cm11 pls help TIA
yrragarry said:
i have samsung s2 GT-I9100, version of 4.2.2, I9100XXMS2, im using Omega v13 rom, i want to change it to cm11 kitkat version, i dont know the steps, i cant just flash it using cwm 6.4, always says aborted, cant open the zip file of cm11 pls help TIA
Click to expand...
Click to collapse
First make a rom backup of your 4.2.2 incase if something goes wrong and you want to restore back.
Then download the latest recovery version, twrp or cyanogenmod
Download cm11
Flash the newest recovery,
Reboot into recovery
Format data/factory reset
Wipe /system
Wipe /dalvik-cache
Flash cm11
Flash kitkat gapps
Reboot.
Enjoy cm11.
The reason why you need latest recovery is because cm11(kitkat) needs selinux enabled recoveries, else it will say something like aborted, set_metadata_recursive failed.
Goodluck with flashingcm11!
wulsic said:
First make a rom backup of your 4.2.2 incase if something goes wrong and you want to restore back.
Then download the latest recovery version, twrp or cyanogenmod
Download cm11
Flash the newest recovery,
Reboot into recovery
Format data/factory reset
Wipe /system
Wipe /dalvik-cache
Flash cm11
Flash kitkat gapps
Reboot.
Enjoy cm11.
The reason why you need latest recovery is because cm11(kitkat) needs selinux enabled recoveries, else it will say something like aborted, set_metadata_recursive failed.
Goodluck with flashingcm11!
Click to expand...
Click to collapse
tnx for the reply sir, but i already tried this way for many times, the file cm11 nightly always aborted,not continuing the updating, is there any ways or steps?
yrragarry said:
tnx for the reply sir, but i already tried this way for many times, the file cm11 nightly always aborted,not continuing the updating, is there any ways or steps?
Click to expand...
Click to collapse
Is it corrupt maybe?
Did you downloaded cyanogenmod for the right device?(Probably you have but just in case)
Are you really using the latest recovery?
Better way, what error does it shows, why does it aborts.
yrragarry said:
tnx for the reply sir, but i already tried this way for many times, the file cm11 nightly always aborted,not continuing the updating, is there any ways or steps?
Click to expand...
Click to collapse
YOu need to first install Kitkat compatible cwm recovery to install kitkat rom in i9100 .. So first download i9100kitkat compatable recovery (google the same to find it) flash it via odin or normal and reboot recovery now .. Now you can full wipe, wipe cache data partitions format system and flash the laest cm11 + gapps with out any problems
So this is my first post, but whatever.
So it's safe to say I screwed up, I accidentally deleted my stock (rooted) Samsung OS. I somehow managed to download Paranoid Android 6.0.1 onto the Samsung Galaxy S3 GT-I9300 I received. I heavily dislike Paranoid Android, and I would like to give Cyanogen 14.1 a shot. The problem is since I wiped everything, every time I do a factory reset for my device, it goes into a bootloop, even if I flashed CM 14.1.
I have TWRP installed, if that helps, and all files (that I know of) are installed on my computer (Odin, CM14.1 ZIP, and Paranoid is backed up).
I'd like to thank everyone who even comes and reads this thread, and I'd be very grateful if I managed to get CM 14.1 on the Samsung Galaxy S3 GT-I9300.
Which version of TWRP is installed? If you have 2.87, try 3.02. Are you performing a full system and data wipe before installing cm14.1?
Hi bro
I am agree with the first reply to you.
All You need the official CM14.1 ROM
Download here https://download.cyanogenmod.org/?device=i9300
And then download Gapps for android 7.1 pico
Download here http://opengapps.org/
If yoy havn't twrp recovery ! Download it from here
https://dl.twrp.me/i9300/
The file end with (tar) it flashing with Odin.
And the file end with (img) it is update from other version to new with Flashify app (you can find the app in playstore free)
Now You have all requirements files
Let's flashing Your device:
Move the files to Ext.sdcard
Make sure you have 80% battery charge
Then reboot your device to (recovery mode)
Turn off your device and Push (Power+home+volume up) keys at the same time for 5 sec untill u see the recovery icon
Now go to wipe your phone choose advance wipe check the dalvilk + cache + system + data + inernal storage ,, done
Now go back and choose install
Search to your Ext.sdcard then choose the CM14.1 at the same time click on Add more zips
And choose Gapps 7.1 pico
Now swipe to flash
Wait to flash finish and then click on Reboot system
Done
Good luck
audit13 said:
Which version of TWRP is installed? If you have 2.87, try 3.02. Are you performing a full system and data wipe before installing cm14.1?
Click to expand...
Click to collapse
I'm using the latest TWRP, I made sure to install the latest one, and I'm performing a full data and system wipe before I install CM14.1. My question is does it HAVE to be on an external SD card, because I just port it over to a folder in my internal SD card.
It can be installed from the internal memory. Simplest way would be to boot into TWRP, mount storage, copy over CM and gapps, and flash.
Maybe try TWRP 2.87?
audit13 said:
It can be installed from the internal memory. Simplest way would be to boot into TWRP, mount storage, copy over CM and gapps, and flash.
Maybe try TWRP 2.87?
Click to expand...
Click to collapse
I've tried to do that multiple times, but everytime I try it, the S3 goes into a bootloop.
Due to the bootloop issue, I would flash a stock ROM with Odin, perform a factory wipe from stock recovery, and then see if the phone will boot properly.
Is the phone a gt-i9300 in download mode?
audit13 said:
Due to the bootloop issue, I would flash a stock ROM with Odin, perform a factory wipe from stock recovery, and then see if the phone will boot properly.
Is the phone a gt-i9300 in download mode?
Click to expand...
Click to collapse
Yeah, I managed to install the stock OS. I also tried to install CM14.1 again, following the instructions to the letter, but still no CM build. I have no idea what I'm doing wrong, since I've read multiple threads on XDA and the CM site.
Not exactly sure what you mean by in download mode, since I'm new to all this rooting business.
You need download mode to flash a stock ROM; otherwise, Odin can't install a stock ROM.
audit13 said:
You need download mode to flash a stock ROM; otherwise, Odin can't install a stock ROM.
Click to expand...
Click to collapse
Oh if that's the case, then yes. I put it in Odin mode to flash the stock ROM.
Okay, just to confirm but these are the major steps you took:
flashed the latest stock ROM to the phone;
flashed the latest tar version of TWRP using Odin;
booted into TWRP and copied CM14 to the internal memory or an SD card;
wipe data, system, and cache in TWRP;
flash CM14 in TWRP and rebooted.
Yup, those are the exact steps I took. I think I'm just going to tinker around with the Samsung a little longer, until I manage to brick it, or I'll just continue doing research. I'm already happy I managed to get out of a boot loop on my own, with and without OS.
Are you in Canada? Where did you get the i9300? The i747m is sold in Canada and the i747 is sold in the USA.
audit13 said:
Are you in Canada? Where did you get the i9300? The i747m is sold in Canada and the i747 is sold in the USA.
Click to expand...
Click to collapse
My dad got it for his work during his visit in Turkey, is that a factor during flashing of new OS's? What surprises me is that I could install Paranoid Android 6.0.1 onto it without an OS with little or no problem.
A pre-existing OS on the phone is not a requirement to flash a custom ROM.
As long as the ROM is for the i9300, you should be fine.
audit13 said:
A pre-existing OS on the phone is not a requirement to flash a custom ROM.
As long as the ROM is for the i9300, you should be fine.
Click to expand...
Click to collapse
I made sure it was for the i9300. I'm confused to where it doesn't work because I would see the CM battery charging logo, but when I wanted it to boot, it kept bootlooping for 10 minutes on end. The longest I've let it run was whilst I was sleeping, 8 hours, still nothing.
Maybe try a different version of CM14.1 or a different version of TWRP.
audit13 said:
Maybe try a different version of CM14.1 or a different version of TWRP.
Click to expand...
Click to collapse
I'll give those options a shot. I'll try out clockwork and see. I guess I'll keep going until I brick it. Thanks for aiding me, and enjoy having a happy new year.