Related
My note 3 is from Vodafone Australia. the model number is SM-N9005. I always assumed it was one of the "International" one. Then i tried flashing the official cyanogen mod nightly for "International" which was called HLTEXX when i tried it it said your phone is an HLTE and not and HLTEXX.
What's the difference? Are there 2 kinds of international?
Wait for a dev to reply this properly, and this should be in the Q&A Section I assume,
Remove the device check in updater-binary, as I guess it means (hlte and xxx) the same device. Some have suggested to use TWRP Recovery as well. This is according to my understanding of the issue.
They are both different ways to say the same thing. Some places the n9005 is referred to as hlte and some places it's hltexx. Now as for why the roms don't flash and give that error, i am not sure. Ppl have been reporting that on ALL roms but i haven't had any issues, the roms seem to flash fine for me. But others have to edit the updater script, also some reported that flashing via cwm worked for them without editing the updater script and others said switching to twrp helped them... This is the weirdest android phone I have owned.
Sent from my SM-N9005 using Tapatalk
I also want to know this, and how to detect if the one i have is hlte or hltexx
JazonX said:
Wait for a dev to reply this properly, and this should be in the Q&A Section I assume,
Remove the device check in updater-binary, as I guess it means (hlte and xxx) the same device. Some have suggested to use TWRP Recovery as well. This is according to my understanding of the issue.
Click to expand...
Click to collapse
Can i move the thead myself to the Q and A section?:
hi,
i had the error flashing a rom and i switched from twrp to cwm now it works!
but i still want to know what the difference is!
Hakired said:
i tried flashing the official cyanogen mod nightly for "International" which was called HLTEXX when i tried it it said your phone is an HLTE and not and HLTEXX.
Click to expand...
Click to collapse
i can also not install the nightly hltexx.
bought my device in germany.
no problem with temasek unoffical and probam.
Hakired said:
My note 3 is from Vodafone Australia. the model number is SM-N9005. I always assumed it was one of the "International" one. Then i tried flashing the official cyanogen mod nightly for "International" which was called HLTEXX when i tried it it said your phone is an HLTE and not and HLTEXX.
What's the difference? Are there 2 kinds of international?
Click to expand...
Click to collapse
I also have Aussie Vodafone stock. hltexx is fine for me. See my answer below. I assume it must read product device and not product name. I have used a number of different firmware now and all good. I would assume yours is from the same place.
johanveld said:
I also want to know this, and how to detect if the one i have is hlte or hltexx
Click to expand...
Click to collapse
Check your Build Prop located in System (use root explorer or a similar app) and you will see this;
ro.product.name=hltexx
ro.product.device=hlte
So this is where people are getting confused because it is both depending on what you read.
Hakired said:
My note 3 is from Vodafone Australia. the model number is SM-N9005. I always assumed it was one of the "International" one. Then i tried flashing the official cyanogen mod nightly for "International" which was called HLTEXX when i tried it it said your phone is an HLTE and not and HLTEXX.
What's the difference? Are there 2 kinds of international?
Click to expand...
Click to collapse
hltexx is product name, hlte is device name
hlte refers to many models, including N9002, N9005, N9006, N9008, N9009
while hltexx is N9005
you can use my app Phone INFO to get more information.
i removed the first line from the updater script and successfully flashed cm nightly in twrp.
johanveld said:
hi,
i had the error flashing a rom and i switched from twrp to cwm now it works!
but i still want to know what the difference is!
Click to expand...
Click to collapse
but im already using CWM tho XiaoLu's custom CWM 6.0.4.5 i think
not-i said:
I also have Aussie Vodafone stock. hltexx is fine for me. See my answer below. I assume it must read product device and not product name. I have used a number of different firmware now and all good. I would assume yours is from the same place.
Check your Build Prop located in System (use root explorer or a similar app) and you will see this;
ro.product.name=hltexx
ro.product.device=hlte
So this is where people are getting confused because it is both depending on what you read.
Click to expand...
Click to collapse
have you tried the cyanogen nightly htlexx?
Are you telling me to edit my build prop?
What i was trying to do was dirty flash the Cyanogen Nightly on top of Temasek. I didnt believe a full wipe would help, Do you reckon I should? Just wanted to try out the Cyanogen but im pretty happy with Temasek's
A.N.Droid said:
i removed the first line from the updater script and successfully flashed cm nightly in twrp.
Click to expand...
Click to collapse
im kinda newbie and this seems difficult. No idea what an updated script is. Is that part of the ROM im flashing or within the recovery?
not-i said:
Check your Build Prop located in System (use root explorer or a similar app) and you will see this;
ro.product.name=hltexx
ro.product.device=hlte
So this is where people are getting confused because it is both depending on what you read.
Click to expand...
Click to collapse
My build prop says this.
ro.product.name=hltexx
ro.product.device=hltexx
So afterall it was hltexx but Cyanogen says it's only hlte.. strange. I'm going to try and do full wipe then flash cyanogen.
Hakired said:
So afterall it was hltexx but Cyanogen says it's only hlte.. strange. I'm going to try and do full wipe then flash cyanogen.
Click to expand...
Click to collapse
if it still doesnt work you could do this:
open the cm nightly archive (i use winrar), navigate to \META-INF\com\google\ and extract the file updater-script.
open in a text editor of your choice.
remove the first line and save the edited file. (you dont need to know a thing about programming to realize that this is the device check)
drag and drop the edited file into that folder in the archive and overwrite the old file.
flash. enjoy !
Thanks it worked. Now to see if it's fully functional with my phone.
Hakired said:
Could you send me your updater script file with the deleted line? When i opened it in notepad they were not in lines and it just goes on and on so I deleted some stuff concerning the checks and it looks like this.
|| abort("This package is for \"hltexx\" devices; this is a \"" + getprop("r ...
I get an error status code: 6
but it does not check for the phone model anymore.
Click to expand...
Click to collapse
great that it works for you now !
please do not use the attached file anymore, its outdated !
sermon edgedai
i have install the rom with the updater-script file
now i have a bootloop with the massage
Kernel is not seandroid enforcing
set warranty bit: kernel
pls help mee
NeoGoku123 said:
i have install the rom with the updater-script file
now i have a bootloop with the massage
Kernel is not seandroid enforcing
set warranty bit: kernel
pls help mee
Click to expand...
Click to collapse
Knox bootloader / kernel not compatible
This arrived to me on another device. I tried flash a Rom MJ2 non Knox over a ML1 Knox. The flashing by Odin was good but the Knox bootloader installed not liked it and give me that error at boot, and the phone not started.
I made a Mod Kernel-ML1.tar.md5 to flash by Odin and problem solved. MJ2 worked whit ML1 kernel.
NeoGoku123 said:
i have install the rom with the updater-script file
now i have a bootloop with the massage
Kernel is not seandroid enforcing
set warranty bit: kernel
pls help mee
Click to expand...
Click to collapse
could be that the attached file is outdated. you have to modify it by yourself next time.
can you get into recovery ? if so, wipe and install a rom.
if not, can you get into download mode ? if so, flash stock rom with odin.
if not, pull the battery and try again.
Hello there,
My new Samsung Galaxy S5 [SM-G900L] just came in.
It wanted to install custom recovery from TWRP so I could make a backup of my Stock Rom and afterwards could install custom Roms, but there doesn't seem to be any support for the G900L.
I'm quite new here, but is it possible someone can help me with this? So that TWRP will aslo provide support to the G900L.
I'm willing to sent al the necessary files. But you'll have to gide me trough it.
Thanks in advance.
Anybody??
Good luck.. i tried looking for anything related to the 900L model but there's barely any support on it.
chaulklet said:
Good luck.. i tried looking for anything related to the 900L model but there's barely any support on it.
Click to expand...
Click to collapse
Thanks, but yeah, that is why I opened this thread. Because I couldn't find anything about my G900L either
And because I'm new I can't post anything in the development section T.T
I hope someone picks this up though.
Yup I fell ya
/Bump for support
SM 900L Support
Another one for 900L support. Got the phone rooted no problem but failed to install CWM or TWRP yesterday so no custom recoveries available . Got a boot loop for my efforts. Hope there is enough love out there for someone to tweak some of the packages for these phones.
Cheers.
Successfully installed TWRP and CyanogeMmod recoveries on my SM-G900L
Sorry for the very long delay. I only got this mobile last month. I am able to install TWRP recovery by using TWRP manager after rooting (Although his device is not supported officially, the recovery image for the international version (SM-G900F) works really fine. I also successfully flash CyanogenMod (both View attachment Snapshot_recovery.tar and View attachment Nigthy_recovery.tar) recovery images using odin.
sunilpaulmathew said:
Sorry for the very long delay. I only got this mobile last month. I am able to install TWRP recovery by using TWRP manager after rooting (Although his device is not supported officially, the recovery image for the international version (SM-G900F) works really fine. I also successfully flash CyanogenMod (both View attachment 3536028 and View attachment 3536027) recovery images using odin.
Click to expand...
Click to collapse
I have tried many times to use TWRP recovery on G900Lmodel but with no success.
I always end up with "COULD NOT DO NORMAL BOOT".
Also I need one help, I was trying to use this Custom ROM "Insanity S7 edge port", I again get the same message " COULD NOT DO NORMAL BOOT".
Someone told me it's the kernel problem and i have to flash stock kernel after flashing ROM zip. But the thing is I don't have the stock kernel.
Please help.
sachin7825 said:
I have tried many times to use TWRP recovery on G900Lmodel but with no success.
I always end up with "COULD NOT DO NORMAL BOOT".
Also I need one help, I was trying to use this Custom ROM "Insanity S7 edge port", I again get the same message " COULD NOT DO NORMAL BOOT".
Someone told me it's the kernel problem and i have to flash stock kernel after flashing ROM zip. But the thing is I don't have the stock kernel.
Please help.
Click to expand...
Click to collapse
TWRP for kltelget (SM-G900L) is available here. You can also use the TWRP for klte (SM-G900F). The details are available in my xda thread (latest version is not tested). You can boot most Phoenix kernel (I hope Insanity too) based ROMs by either flashing the stock ROM boot.img or a custom boot.img sited in my another xda thread located here (check second post).
sunilpaulmathew said:
TWRP for kltelget (SM-G900L) is available here. You can also use the TWRP for klte (SM-G900F). The details are available in my xda thread (latest version is not tested). You can boot most Phoenix kernel (I hope Insanity too) based ROMs by either flashing the stock ROM boot.img or a custom boot.img sited in my another xda thread located here (check second post).
Click to expand...
Click to collapse
Thank you sunil
I tried the recoveries that you are suggesting, both of them, klte and klteskt from the twrp site.
It seems to work on every other device but mine.
Can't figure what I am doing wrong.
sachin7825 said:
Thank you sunil
I tried the recoveries that you are suggesting, both of them, klte and klteskt from the twrp site.
It seems to work on every other device but mine.
Can't figure what I am doing wrong.
Click to expand...
Click to collapse
Not sure abt the latest versions. can you try the one (klte) linked in my xda thread. and hope ur device is rooted properly...
sunilpaulmathew said:
Not sure abt the latest versions. can you try the one (klte) linked in my xda thread. and hope ur device is rooted properly...
Click to expand...
Click to collapse
yes i will try them, I hope they work on latest MM.
And yes the device is rooted properly with latest CFautoroot for G900L, I even checked it with Root Checker basic.
Anyways, I don't have any special liking for TWRP, I wanted it to flash stock boot.img to make the Insanity ROM work.
I am ok with CWM recovery, but I was told it could not flash .img file and I am not equipped to make my own flashable zip form boot.img.
But now I am planning to use your modded boot.img for Phoneix based MM custom ROMs. I hope that will work.
Btw thank you so much...I checked both of your threads...They are awesome....you seem to be lone warrior for these Korean variants. Not much support elsewhere.
Really appreciate your efforts!!!!
Keep up the good work.
sunilpaulmathew said:
TWRP for kltelget (SM-G900L) is available here. You can also use the TWRP for klte (SM-G900F). The details are available in my xda thread (latest version is not tested). You can boot most Phoenix kernel (I hope Insanity too) based ROMs by either flashing the stock ROM boot.img or a custom boot.img sited in my another xda thread located here (check second post).
Click to expand...
Click to collapse
TWRP worked!!!
Finally..
Thank you so much!!!
Also I tried your kernel with Insanity ROM and it works perfect.!!!
Thank you once again.
Hello I'm on CM11 11-20140903-NIGHTLY-hlte. I've read the news about CM splitting off into 3 branch update variants for the Note 3. hlte is now GSM and hltespr Sprint and hltevzw Verizon. I assumed since Sprint and Verizon are CDMA that these variants would would work with my Canadian Bell Note 3. When I update manually it says wrong device. If I do an automatic update in CM11 then I get the same message when it downloads the hlte normal updates passed 903.
Will I have to wait for a hltecan variant version now for CM11 or am I doing something wrong?
Also I have TWRP as my recovery. Thank you to anyone that can help.
bauwoo said:
Hello I'm on CM11 11-20140903-NIGHTLY-hlte. I've read the news about CM splitting off into 3 branch update variants for the Note 3. hlte is now GSM and hltespr Sprint and hltevzw Verizon. I assumed since Sprint and Verizon are CDMA that these variants would would work with my Canadian Bell Note 3. When I update manually it says wrong device. If I do an automatic update in CM11 then I get the same message when it downloads the hlte normal updates passed 903.
Will I have to wait for a hltecan variant version now for CM11 or am I doing something wrong?
Also I have TWRP as my recovery. Thank you to anyone that can help.
Click to expand...
Click to collapse
Flash the hlte recovery on top of your hltecan TWRP recovery. This will fix it.
nicholaschum said:
Flash the hlte recovery on top of your hltecan TWRP recovery. This will fix it.
Click to expand...
Click to collapse
No can do. Same error. The normal hlte recognizes the device as hltecan in the new versions.
bauwoo said:
No can do. Same error. The normal hlte recognizes the device as hltecan in the new versions.
Click to expand...
Click to collapse
I flashed hlte recovery on top of my hltecan 2.7.1.0 recovery and confirmed it changed to the latest version.
Once I installed a de-unified hlte ROM without hltecan in the updater-script, it worked.
Which recovery did you install and on which link?
nicholaschum said:
I flashed hlte recovery on top of my hltecan 2.7.1.0 recovery and confirmed it changed to the latest version.
Once I installed a de-unified hlte ROM without hltecan in the updater-script, it worked.
Which recovery did you install and on which link?
Click to expand...
Click to collapse
2.7.1.0.
bauwoo said:
2.7.1.0.
Click to expand...
Click to collapse
Flash this from your recovery. This is hlte 2.7.2.0
https://goo.im/devs/OpenRecovery/hlte/openrecovery-twrp-2.7.2.0-hlte-4.4.zip/
nicholaschum said:
Flash this from your recovery. This is hlte 2.7.2.0
Click to expand...
Click to collapse
Thank you very much. I've updated my recovery and installed hlte normal version to 906 current.
bauwoo said:
Thank you very much. I've updated my recovery and installed hlte normal version to 906 current.
Click to expand...
Click to collapse
You're welcome, glad to help
PS. next time you can just press the Thanks button :good:
Question
nicholaschum said:
Flash the hlte recovery on top of your hltecan TWRP recovery. This will fix it.
Click to expand...
Click to collapse
Question: I have to flash the link in Odin v3.09, right? Also, when i flash it, will i lose my data?
Thanks!
brian.costa7 said:
Question: I have to flash the link in Odin v3.09, right? Also, when i flash it, will i lose my data?
Thanks!
Click to expand...
Click to collapse
You don't lose data.
nicholaschum said:
You don't lose data.
Click to expand...
Click to collapse
And I flash this in Odinv3.09 under AP, right?
brian.costa7 said:
And I flash this in Odinv3.09 under AP, right?
Click to expand...
Click to collapse
yes
I've gone searching many threads in this section of XDA. search all possible compatible ROM's and Recovery.
Is there a working Recovery for Samsung Note 3 N900l 5.0?
Is there a working ROM for N900l? i searched and saw Darklord S6 is compatible.
but i want to try a CM12 ROM from Temasek.
and what is KNOX? 0x0? 1x0?
My previous Smartphone(LG-D838) has a poor a android development.
Every reply would be very much appreciated!!
Thank you
softbank21 said:
I've gone searching many threads in this section of XDA. search all possible compatible ROM's and Recovery.
Is there a working Recovery for Samsung Note 3 N900l 5.0?
Is there a working ROM for N900l? i searched and saw Darklord S6 is compatible.
but i want to try a CM12 ROM from Temasek.
and what is KNOX? 0x0? 1x0?
My previous Smartphone(LG-D838) has a poor a android development.
Every reply would be very much appreciated!!
Thank you
Click to expand...
Click to collapse
"My previous Smartphone(LG-D838) has a poor a android development"... and the NEW one too
For recovery, you can use the hlteskt/n900s version, which is compatible.
Unfortunately, there are no custom ROMs for your variant,
yeah, most likely i have this really BEST luck with me for smartphones that i really do need to suffer.
Darklord S6 ROM was compatible to my phone, but the CM12 has no reply if compatible with my model.
is there a way for me to use CM 12 since my previous phone also has no update for CM12
softbank21 said:
yeah, most likely i have this really BEST luck with me for smartphones that i really do need to suffer.
Darklord S6 ROM was compatible to my phone, but the CM12 has no reply if compatible with my model.
is there a way for me to use CM 12 since my previous phone also has no update for CM12
Click to expand...
Click to collapse
If you use CM, or any AOSP-based ROM, you won't be able to do voice calls or text messages. That's because of how the LGU+ network is set up in Korea, and your variant is built specifically for that network.
jisoo said:
If you use CM, or any AOSP-based ROM, you won't be able to do voice calls or text messages. That's because of how the LGU+ network is set up in Korea, and your variant is built specifically for that network.
Click to expand...
Click to collapse
Then it is the end for me for a new ROM? damn i should check first XDA before buying new phone.
two mistakes now. thanks btw, Darklord S6 ROM says my phone is supported?
softbank21 said:
Then it is the end for me for a new ROM? damn i should check first XDA before buying new phone.
two mistakes now. thanks btw, Darklord S6 ROM says my phone is supported?
Click to expand...
Click to collapse
I don't know about Darklord, but I doubt it will work. Make sure you have a backup and stock ROM ready, if you do try it, though.
jisoo said:
I don't know about Darklord, but I doubt it will work. Make sure you have a backup and stock ROM ready, if you do try it, though.
Click to expand...
Click to collapse
Ill try it. if ever i get to have my stock ROM ready. just in case.
jisoo said:
I don't know about Darklord, but I doubt it will work. Make sure you have a backup and stock ROM ready, if you do try it, though.
Click to expand...
Click to collapse
Bruh, My note 3 goes on Bootloop after installing CWM.
softbank21 said:
Bruh, My note 3 goes on Bootloop after installing CWM.
Click to expand...
Click to collapse
Did you try the hlteskt version? Which bootloader version you have?
jisoo said:
Did you try the hlteskt version? Which bootloader version you have?
Click to expand...
Click to collapse
what is bootloader anyway?
i installed CF autoroot and installed CWM n900s version using flashify.
i cant go on recovery at first using vol up +home+power then i use flashify reboot on recovery then it went bootloop.
after that i installed again the cwm n900s version kk via odin3 and it went ok but the system.ui crashed when i turn on my device.
i go to cwm recovery and wipe cache hoping to fix the problem then the system.process(i think) not responding and displaying black only.
i really want to fix the phone without wiping or factory resetting but panic comes first to me.
now it is ok.
Thanks, just sharing my really scary exp. its my first bootloop.
Hi
SM-G900F
Sorry but im still a bit of a noob with phones so bare with me.
I use to be with EE network but have now had my phone unlocked and using on another network. I have also rooted my S5 so can not update via settings and software update as get error "the OS on your system has been modified"
I know i can put a custom rom on but just out of interest, can i stick on any stock network rom onto my S5 as i see that Vodafone are the first to have released marshmallow update for there sold S5.
Have hooked my phone up to laptop and ran Samsung kies 3 and it says i have the latest update even though im still on lollypop.
Do i have to unroot my phone before i can get marshmallow update?
Cheers
Flash this with ODIN
Code:
https://mega.nz/#!SMRlERrY!oeOX8W_4tbQbArTN-LzTKWJ1xi_8LLrN_ZoSg-Dzs1Q
6.0.1 for G900F (United Kingdom)
Will trip KNOX
*Detection* said:
Flash this with ODIN
Code:
https://mega.nz/#!SMRlERrY!oeOX8W_4tbQbArTN-LzTKWJ1xi_8LLrN_ZoSg-Dzs1Q
6.0.1 for G900F (United Kingdom)
Will trip KNOX
Click to expand...
Click to collapse
Thanks, im guessing this will wipe my phone and not just an update it to 6?
malice19 said:
Thanks, im guessing this will wipe my phone and not just an update it to 6?
Click to expand...
Click to collapse
No, ODIN doesn't wipe the phone, it just upgrades it, it will remove anything custom like root or recovery though
*Detection* said:
No, ODIN doesn't wipe the phone, it just upgrades it, it will remove anything custom like root or recovery though
Click to expand...
Click to collapse
Cheers, is there anyway of putting root access back along with CWM recovery once i have updated marshmallow? :fingers-crossed:
malice19 said:
Cheers, is there anyway of putting root access back along with CWM recovery once i have updated marshmallow? :fingers-crossed:
Click to expand...
Click to collapse
Yep, but use TWRP 3.0.0.0 recovery with ODIN instead (Much more powerful too)
Then flash SuperSU 2.71 beta from TWRP
*Detection* said:
Yep, but use TWRP 3.0.0.0 recovery with ODIN instead (Much more powerful too)
Then flash SuperSU 2.71 beta from TWRP
Click to expand...
Click to collapse
Thanks for the advise.
I managed to find some time to have a play and have successfully upgraded to Marshmallow :good:
Next step installing TWRP as you recommended, can you point me in the right direct where to download the correct version of TWRP for my S5 as only seem to be finding S4 version or for kitkat?
Also do i need to make sure its rooted before i do this?
Cheers for all your help so far
malice19 said:
Thanks for the advise.
I managed to find some time to have a play and have successfully upgraded to Marshmallow :good:
Next step installing TWRP as you recommended, can you point me in the right direct where to download the correct version of TWRP for my S5 as only seem to be finding S4 version or for kitkat?
Also do i need to make sure its rooted before i do this?
Cheers for all your help so far
Click to expand...
Click to collapse
Managed to figure it out
Rooted it with this CF-Auto-Root-klte-kltexx-smg900f.zip
http://download.chainfire.eu/397/CF-Root1/CF-Auto-Root-klte-kltexx-smg900f.zip?retrieve_file=1
Then installed TWRP from here
https://twrp.me/devices/samsunggalaxys5qualcomm.html
Happy days with Marshmallow, TWRP Recovery and rooted
malice19 said:
Managed to figure it out
Rooted it with this CF-Auto-Root-klte-kltexx-smg900f.zip
http://download.chainfire.eu/397/CF-Root1/CF-Auto-Root-klte-kltexx-smg900f.zip?retrieve_file=1
Then installed TWRP from here
https://twrp.me/devices/samsunggalaxys5qualcomm.html
Happy days with Marshmallow, TWRP Recovery and rooted
Click to expand...
Click to collapse
Nice job, I get my TWRP from here
https://dl.twrp.me/klte/
.tar version and flash with ODIN
3.0.0.0 seems to be the last stable version atm, not sure if the newer ones are bug free yet
That root you used might cause problems, the 2.71 beta systemless is the one for MM ROMs atm, the others either don't work fully or overheat the phone with constant high CPU usage
If you have problems, flash this one from TWRP
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
malice19 said:
Thanks for the advise.
I managed to find some time to have a play and have successfully upgraded to Marshmallow :good:
Next step installing TWRP as you recommended, can you point me in the right direct where to download the correct version of TWRP for my S5 as only seem to be finding S4 version or for kitkat?
Also do i need to make sure its rooted before i do this?
Cheers for all your help so far
Click to expand...
Click to collapse
*Detection* said:
Nice job, I get my TWRP from here
https://dl.twrp.me/klte/
.tar version and flash with ODIN
3.0.0.0 seems to be the last stable version atm, not sure if the newer ones are bug free yet
That root you used might cause problems, the 2.71 beta systemless is the one for MM ROMs atm, the others either don't work fully or overheat the phone with constant high CPU usage
If you have problems, flash this one from TWRP
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
I have one word for you = LEGEND
Thanks for the heads up and instant replies now using beta version, you are a credit to this forum. Cheers mate.
malice19 said:
I have one word for you = LEGEND
Thanks for the heads up and instant replies now using beta version, you are a credit to this forum. Cheers mate.
Click to expand...
Click to collapse
No probs