Hey Everyone ! I have an interesting issue. My girlfriend's old Razr M took a nasty hit a long time ago. Screen shattered, and even split on the upper left corner. After that we couldn't tell if it would power up or any thing. Since than she had gotten a new one and it works great except it was after the OTA update where you can't unlock the bootloader. I kept the old one for "possible parts" as I told her but deep down it was the hate to fully throw out any kind of amazing device and admit it had been defeated entirely, plus I had been researching and learning alot about rooting, flashing unlocking, etc. since then and I also enjoy fixing things. Also me and her both remembered that it took that nasty hit before the OTA update and wanted to see not only if I could get it working again but also see how far we could get with it ! I'm somewhat noobish but have alot of research and trial and error hours under belt. The Dev's threads helped me completely and they are right when they say Research and FOLLOW DIRECTIONS step by step !
Here's how far we got ...
It would power up but freeze halfway through boot animation and bootloop.
Factory Reset, Wiped everything countless times still same.
Charged it to 100% powered it up and it did the same.
Left the house longer than expected while it was plugged in and still bootlooping and came home to it actually to the welcome screen.
Set it up and rooted successfully using Matt's Utility but it did the same after restart.
( Matt's the **** and does awesome work ! Girlfriend rolled her eyes and laughed that the utility I was using was made by a fellow "obsessed" fan of the one and only Dark Knight ! )
Again left it bootloop for at least an hour til it eventually worked again.
Quickly got OTA rootkeeper just in case i couldn't prevent the OTA update.
( just playing it safe ya know )
Unlocked the Bootloader with Motopocalypse and that also worked great.
( Dan Rosenberg's Great time and effort to do the impossible on this one ! )
Then I figured ok ... Now I can jump to any version I want thinking it might be just the one it was on.
I flashed back to Stock ICS 4.0 using House of Moto
( Amazing work by Samurhi ! Another great Developer I owe a huge thanx to ! )
Rebooted after flashing back to Stock ICS flawlessly and no issues at all doing so after that.
After that I tried every firmware from Stock to JB remaking every House of Moto folder for each one the exact same as before and the boot animation would freeze halfway through like before.
Flashed back to Stock ICS 4.0 again and it continued to have no problems at all ! I even rooted using Matt's Utility 1.20 putting it at 4.1 and still same boot animation freeze.
Then I tried custom roms like Cyanogenmod, Validus, MoKee and Liquid Smooth following all instructions and using correct GApps when needed and with those the boot animation goes all the way to where it seems like it would switch to the welcome screen or lock screen but freezes on the animation just before that, than after about 10 secs reboots ....
What could it be ? I've looked every where for any kind of possibility imaginable and would hate to believe after resurrecting this phone from the dead, rooting it and even unlocking the bootloader that it can only live on as a Stock ICS 4.0 version for ever after beating the odds and going so far !!!
Any insight, ideas or help of any kind is greatly appreciated !!!
Related
Hello.
First off i will start with the fact that i've read most of topics proposed by Google and Xda forum search, so please don't treat me like an idiot.
From what I've noticed there's quite a few people with similar problem - after going back to stock ICS everything was fine for a week then boom, this morning i wake up and my TF101 is refusing to turn on. First off I've thought its just a fail and i will fix it easily but now I'm seriously scared. So far I've wiped device around 10 times, and so did i tried to install other system software (I've had couple zip files with other rooms stored on my SD, and Clockwork recovery works fine except for the fact that when i use "Super wipe" from android revolver it's getting stuck on clearing DATA).
Some detailed info :
After installing energy ICS device does not even go to loading screen, just keeps on boot loop.
After installing CM10 there's no boot animation change...
After installing any ROM and rebooting there's this installation bar... it progresses instantly.
Did anybody had similar problem which they got fixed by some magic method... or should i just throw my transformer into the bin? I'm clueless now, hope you can help me out.
Regards Nekyo.
Edit : 2h later , Fixed it through the NVFlash... thanks for all support.
nekyo said:
Edit : 2h later , Fixed it through the NVFlash... thanks for all support.
Click to expand...
Click to collapse
You wait 2 hours and then complain there was no support?
If you run into a problem you can't fix on your own, you're not going to make many friends expecting people to jump on your issue within 2 hours.
This is XDA, basically a DIY forum, if you want support here, expect a few days delay for an answer that helps.
EDIT: 12/23/2012 3:19AM.. Doing a little research I figured out what the issue was. Used Brian Gove's Guide
[How To] Reset your phone in order to return to Verizon(Updated 12/11/2012)
From Step 5 Onwords and everything works great.
.. I am still stumped on exactly what happen. I am almost positive it was because of the new file structure..
Just Proves that with a little patience and smarts anyone can use the resourced and tools here to solve their own android problems without bothering anyone haha.
Thank you all for your articles and Merry Xmas / Happy Holidays to Everyone!!
now.. I gotta unlock my boot loader and start all over..
Soft Brick.....
I was looking around and I cant seem to find a post that really solves my problem.
I have a Verizon S3 that I rooted and flashed to CyanogenMod Nightly build and everything was working great.
I used Rom Manager Premium and it updated me to update to CMW 6023. I went ahead and updated.
I saw that there was an update for my Daily As well 12/22/12 so I went ahead and used Rom Manager to download it and install it for me like It did with my last 16 Roms. That Rom had some strange things going on so I flashed to an older rom 12/20/12 and that rom was buggy as well.
Finally I decided that I should just stop with the Daily's and use the stable. When I loaded the Stable things started to still act strange. Mostly the Keyboard would not work and keep crashing. I decided then to just reload my original backup from Verizon.
Before I went in to recovery i took a look at my files and backed everything up. However then I noticed something that was not there before, a folder /0 with most of my main files inside.
I went into CWM v6.0.2.3. and tried to do a restore to my original nandroid backup from verizon but it looks like it failed.
It Says "Error While Restoring System" and kicked me back to CWM
Now when I reboot all I see is the White "Samsung Galaxy s3"
Did I Screw the pooch on this? Kinda nervous haha.
I am Posiive its a Soft Brik and hoping there is a way to fix it.
I can however get to Download mode. If anyone knows a great guide to help me reflash with Odin that would be fantastic.
thanks guys, been a long time reader and this is the first problem I have really had.
I apologize if this has already been over in a post.
Just a quick step breakdown would be great. I am really hoping that I didnt brick my phone.
Thanks for the help and Merry Christmas / Happy Holidays to everyone.
I had browsed this forum for awhile and was having major issues with AT&T because my phone, as it sat in the eyes of ATT, decided that I needed to be on towers in another county which completely rendered reaching me by land line impossible and my service was such garbage, that I went through five phone numbers in as many phones. My iPhone 4 was screwed, I got a 1st run Nokia Lumina Windows Phone, but the case and windows 8 killed it for me (you had antennae right where you'd normally rest your fingers and so talking on it was a chore. I decided to get another iphone, and another, all met with failure. I stumbled onto these forums one day and discovered the word "root." My iphone was again giving me trouble and my wifes android seemed to do more....way more.
So I'm on my way home with my first android- a cheap motorola atrix HD. When they finally fixed my tower issue I was on my fifth number and I had read on these forums about root. So I get home around Christmas, and promptly rooted my atrix without knowing anything and figured I would learn as I went. I used the motochopper root by djrbliss and Dan Rosenthal (I think) with the fix bootloader screen. I figured I would learn half assed and learn as I go. I download TIBU, and proceeded to brick my phone. I got verification at customer care that the atrix may have been modified, and if it wasnt defective, swap it at the store.
TIBU Brick
Ran on 70 apps total. Removed the wrong one, Brick.
Rooted and botched something stupid, BRICK.
Tried to flash Cyanogenmod. Brick.
Flashed Cyanogenmod and thought I didn't do it right: Grew Frustrated and formatted the phone. ( I was getting as many replacements as I wanted and my wife continued to get irritated with my new hobby which she still hates.
Take my hard bricked HD to ATT store just to find out that I am eligible for the next program.
I shied away from rooting, Got rid of the mega and then got a Galaxy S4. That fever came right back and the next thing I know I am reading, retaining and absorbing as I bricked my S4 four times- twice by not paying attention and twice by not understanding safestrap recovery. The fever of modding finnally got me off of my rear when the guy at best buy reflashed my s4 for the second time and told me about RSD Lite. I go, download RSD Lite, Install my motorola drivers, Install my Operating System via sideload, download CWM recovery, flash CM 10x.x and forget my gapps...no worries, as I had discovered goo.im and f-droid and a few other places where I just found the correct jb gapps moving up from ICS obviously. I then hard brick the Atrix HD and I reinstalled my OS, got the anysoft keyboard from f-droid (the motorola keyboard kept dying) and I flash CM 10 and the JB gapps and bam, I feel like i'm no longer a noob. I was gone for a few months when I did all of this and as soon as I got home, I bought my brothers note 2 which I promptly rooted using cf autoroot and odin and then I flashed the Pacman Rom Stable 4.3. I experienced a soft brick moving up to kit-kat and unstable nightlies of Pacrom, but I moved everything to my SD card and rom installer still had my 4.3 gapps, and stable 4.3 pac rom. I was short on money and had to get a loan on the note 2 which I m getting back.
Now, I'm staring at my S4 for weeks...thinking "god I hate this stupid thing because it has no root on NC1.
Finally, yesterday, I found the towelroot apk and I rooted my i337 NC1. I set up the phone in a few moments, hooked up the proper wanam modules, and I tried with no success to put CWM Philz touch recovery. I was almost resigned to just using the apex launcher but I couldn't stay away from pushing myself to the limit and finally installing safestrap and a touchwhiz rom. So tonight, I finally installed safestrap after reading the steps to get version 3.72 running. Now I was trying to find a compatible touchwhiz based rom that suited me because I finally safestrapped my s4 and ran a backup to my SD, followed by a full wipe (excluding the SD card) and I went right here to read more (on NC1 get the new ODEXED version and I flashed fine without odin, and not rebooting into DL mode, and am now running the Venom v3.02 Safe Strap rom on my S4 like a boss.
Now for the clincher if you're still reading...I don't even know linux, let alone how to use a terminal emulator but for some strange reason, I now know what to do and what not to do to brick a device, and most importantly of all,
super noobs take note:
I FOLLOW THE DIRECTIONS EXACTLY.
I know little to nothing regarding the finer workings of phones (I now know better than to try to mess with things I know nothing about) but I paid attention.
And the payoff is being able to do this to almost any device...but now I am going to read up more because I want to build a nasty rom that gives the user so much access that it borders on criminally sick.
In short, the moral is to PAY ATTENTION. KNOW YOUR LIMITATIONS. FOLLOW INSTRUCTIONS.
Shout out here:
http://forum.xda-developers.com/showthread.php?t=2447482
And Here:
http://forum.xda-developers.com/showthread.php?t=2447482&page=109
Mad props for the simple instruction. I'm gonna go play with my.....new touchwhiz ROM on my S4.
Hello XDA!
I have some questions about my n8010. It is a tablet that I bought in Greece, in case that is necessary to know, and has an interesting background. It started late May. The tablet was unrooted and without any mods whatsoever. I was running the latest Jelly Bean update and had A TON of lag. I had replaced TouchWiz Launcher with Nova and a different gallery and music app with still a lot of lag. So I decided to flash CM11 since it would be lighter for the tablet. After some research I followed the root guide from Zedomax and everything was fine. I had root and so I proceeded doing a backup. This where everything got weird. The backup started but was stuck for long periods of time. After some time being stuck in a screen I decided I should force restart. After the Galaxy Note 10.1 logo appeared it just hanged there without booting into Jelly Bean. I checked recovery and download mode and they where all working fine so I flashed TWRP. It worked and so I took a backup and proceeded installing CM11. I had it already in my SD. I had followed the instructions in the XDA thread that said about removing a line to make it work on the n8010. The flash went great and after factory resetting I rebooted the tablet and everything was OK. At the first boot WiFi wouldn't work but after a reboot it was. The only thing that wasn't working was the video recording. It is a deal-breaker as I use it a lot. I had to switch ROMs. I tried CM10.2 and it still wouldn't. Same goes for Revolt. At lat I switched to a TouchWiz based ROM. Specifically Hyperdrive RLS8. Video was working so I stayed there. I was noticing that since I flashed CM11 my tablet showed up as an n8013 which was very weird but since these ROMs where designed for the n8013 I thought it was normal.
One ROM also had the front facing camera able to record. Upon further inspection I found that Download Mode had my tablet as an n8010 but with the flash count 0 and the status official! Now, I'm either super lucky or the completely opposite! It also says official under About Device! Fast forward a few months and I am now in a situation where the tablet lags once again like crazy. I uninstalled a couple of apps and also installed lighter alternatives and it's somewhat bearable. I was reading the Official OmniROM thread and saw that others also had issues, most of which had the new KitKat bootloader that I don't have, with YouTube and the Video Recording. The latest nightlies are said to have a fix. So I am thinking of installing OmniROM since I am lagging a lot and I would like Screen Mirroring to the Chromecast. My only concern is that I will either brick the tablet or the camcorder won't work. Many people have bricked their Notes and can't go back without the Samsung Service. Most have the new KitKat bootloader which I don't and I'm happy about. My tablet is in a weird situation, what should I do? Anybody else experiencing these issues? Any advice is appreciated!
Thanks in advance,
Chris
Edit: Forgot to say that I flashed Carbon ROM in September and I got a status 7 while flashing with PhilzCWM that I had installed in order to flash Hyperdrive. I had to flash back to Hyperdrive as it wouldn't boot after the status 7. It probably happened because it didn't have SE Linux support. If I do anything I'll flash the latest TWRP.
chrismin13 said:
Hello XDA!
I have some questions about my n8010. It is a tablet that I bought in Greece, in case that is necessary to know, and has an interesting background. It started late May. The tablet was unrooted and without any mods whatsoever. I was running the latest Jelly Bean update and had A TON of lag. I had replaced TouchWiz Launcher with Nova and a different gallery and music app with still a lot of lag. So I decided to flash CM11 since it would be lighter for the tablet. After some research I followed the root guide from Zedomax and everything was fine. I had root and so I proceeded doing a backup. This where everything got weird. The backup started but was stuck for long periods of time. After some time being stuck in a screen I decided I should force restart. After the Galaxy Note 10.1 logo appeared it just hanged there without booting into Jelly Bean. I checked recovery and download mode and they where all working fine so I flashed TWRP. It worked and so I took a backup and proceeded installing CM11. I had it already in my SD. I had followed the instructions in the XDA thread that said about removing a line to make it work on the n8010. The flash went great and after factory resetting I rebooted the tablet and everything was OK. At the first boot WiFi wouldn't work but after a reboot it was. The only thing that wasn't working was the video recording. It is a deal-breaker as I use it a lot. I had to switch ROMs. I tried CM10.2 and it still wouldn't. Same goes for Revolt. At lat I switched to a TouchWiz based ROM. Specifically Hyperdrive RLS8. Video was working so I stayed there. I was noticing that since I flashed CM11 my tablet showed up as an n8013 which was very weird but since these ROMs where designed for the n8013 I thought it was normal.
One ROM also had the front facing camera able to record. Upon further inspection I found that Download Mode had my tablet as an n8010 but with the flash count 0 and the status official! Now, I'm either super lucky or the completely opposite! It also says official under About Device! Fast forward a few months and I am now in a situation where the tablet lags once again like crazy. I uninstalled a couple of apps and also installed lighter alternatives and it's somewhat bearable. I was reading the Official OmniROM thread and saw that others also had issues, most of which had the new KitKat bootloader that I don't have, with YouTube and the Video Recording. The latest nightlies are said to have a fix. So I am thinking of installing OmniROM since I am lagging a lot and I would like Screen Mirroring to the Chromecast. My only concern is that I will either brick the tablet or the camcorder won't work. Many people have bricked their Notes and can't go back without the Samsung Service. Most have the new KitKat bootloader which I don't and I'm happy about. My tablet is in a weird situation, what should I do? Anybody else experiencing these issues? Any advice is appreciated!
Thanks in advance,
Chris
Edit: Forgot to say that I flashed Carbon ROM in September and I got a status 7 while flashing with PhilzCWM that I had installed in order to flash Hyperdrive. I had to flash back to Hyperdrive as it wouldn't boot after the status 7. It probably happened because it didn't have SE Linux support. If I do anything I'll flash the latest TWRP.
Click to expand...
Click to collapse
I would have fixed the original lag issues first. I would get it back to factory stock 100 percent, once back to factory I would do A factory reset and start all over. Get the system running stock as it should then reinstall apps one at a time. if it can't run stock for whatever reason other roms not going to fix the problem.
at least with factory stock you know what should be working. Instead of guessing if the problem is part of the new ROM
shaun298 said:
I would have fixed the original lag issues first. I would get it back to factory stock 100 percent, once back to factory I would do A factory reset and start all over. Get the system running stock as it should then reinstall apps one at a time. if it can't run stock for whatever reason other roms not going to fix the problem.
at least with factory stock you know what should be working. Instead of guessing if the problem is part of the new ROM
Click to expand...
Click to collapse
Thanks for the response!
Good idea! I was thinking of going back to stock and repeating everything. It should fix all my issues. It's too bad that I don't have a working stock backup and I will have to flash through Odin. The reason that I am not doing this is because I am afraid of making it even worse from the official status state that I have in Download Mode and my device is an n8013 under About Device. A flash back to stock through Odin would probably flash most of the system parts which would be kinda dangerous. But on the other hand that would mean that I could give it a brand new try with better luck possibly! It's not that TouchWiz ROMs don't work, it's AOSP that doesn't. I played a lot with Hyperdrive and seems like it's doing better from the lag prospective. But that's only gonna last 15 days. I am sure! So, I'll have your response in mind! Might try it out when I have some free time. Unfortunately, that will probably be Christmas.
Thanks,
Chris
Going back to stock is good advice.Should certainly fix the video problem which you said was important.
Phil789 said:
Going back to stock is good advice.Should certainly fix the video problem which you said was important.
Click to expand...
Click to collapse
I don't have any video playback issues. It's just the camcorder that doesn't work in AOSP ROMs.
Yes.My use of the word "video" should have been "video recording".
The time has come!
Hello everyone, happy holidays!
The time has come that I follow your instructions. I've done my research and here's how I'll do it. Do you agree? Do you have any other suggestions?
Take full backups with my current configuration (Hyperdrive RLS8, PhilzCWM)
Factory reset the device and clean it up so that there is a lot of space
Install Samsung Drivers
Flash Stock Greek 4.1.2 Frimware (N8010XXUCMK2_N8010OXXCMK2_HOME.tar.md5) through ODIN v3 1.85
Let it boot up and do a factory reset from stock recovery
Flash TWRP 2.8.1.0 for the GT-N8010 (openrecovery-twrp-2.8.1.0-gt-n8010) (I chose this version since it has the most downloads)
Make a full backup once again
Flash Omni ROM 4.4.4 (omni-4.4.4-20141222-n801x-NIGHTLY)
Flash SuperSU (UPDATE-SuperSU-v2.40)
Flash PA GApps (pa_gapps-modular-mini-4.4.4-20141214-signed.zip)
Factory reset
REBOOT!
Check everything (Video, model, download mode, bugs, etc.)
REPORT!
If everything goes correctly I believe I should be OK! Hope my issues will be over since the tablet is slow once again. Kinda scared, so that's why I'm asking you. Will I be (mostly) brick safe? Hope so!
Thank you very much for your support,
Chris
P.S.: Should I root before leaving stock? I mean through TWRP.
chrismin13 said:
Hello everyone, happy holidays!
The time has come that I follow your instructions. I've done my research and here's how I'll do it. Do you agree? Do you have any other suggestions?
Take full backups with my current configuration (Hyperdrive RLS8, PhilzCWM)
Factory reset the device and clean it up so that there is a lot of space
Install Samsung Drivers
Flash Stock Greek 4.1.2 Frimware (N8010XXUCMK2_N8010OXXCMK2_HOME.tar.md5) through ODIN v3 1.85
Let it boot up and do a factory reset from stock recovery
Flash TWRP 2.8.1.0 for the GT-N8010 (openrecovery-twrp-2.8.1.0-gt-n8010) (I chose this version since it has the most downloads)
Make a full backup once again
Flash Omni ROM 4.4.4 (omni-4.4.4-20141222-n801x-NIGHTLY)
Flash SuperSU (UPDATE-SuperSU-v2.40)
Flash PA GApps (pa_gapps-modular-mini-4.4.4-20141214-signed.zip)
Factory reset
REBOOT!
Check everything (Video, model, download mode, bugs, etc.)
REPORT!
If everything goes correctly I believe I should be OK! Hope my issues will be over since the tablet is slow once again. Kinda scared, so that's why I'm asking you. Will I be (mostly) brick safe? Hope so!
Thank you very much for your support,
Chris
P.S.: Should I root before leaving stock? I mean through TWRP.
Click to expand...
Click to collapse
I did it! It worked. Everything went OK but:
- Flash count is 0 and status official
- Back camera records in slow-mo
- Chromecast mirroring does not work
However:
-My device is an N8010
-I use the front camera instead
-Mirroring was not really needed
-LAG IS HISTORY!!! [emoji50] [emoji2] [emoji2] [emoji2]
I am so impressed by the performance, still doesn't best my nexus 4 with KK 4.4.4 but it's a GIGANTIC IMPROVEMENT! Veeery happy! Thank you for your support, I wouldn't be here without you!
Merry Christmas and happy holidays!
Chris.[emoji2]
Hey Folks,
got some messy Prob's with my old nVidia Shield LTE Tablet.
The Facts:
-KillSwitch not Triggered and it was succesfully Rooted in November 2015, TEGRA-OTA was also Removed (nomoreota)
-worked for Months (beneath one year), only Super-SU penetrated me periodely that it needs to be Updated, but it couldnt be done, it said "not enough Space" after trying to install a newer Version. :silly:
-past Month (January 2017) i decided to do a Factory-Reset, because Girlfriend should get the Shield, thats where the Problem started:
After clicking Factory-Reset, it began to work. After 4 Hours and nothing happening, i decided to Power it Off and start fresh with Installing a clean Stock-ROM and remove the TEGRA-OTA as i done a year before.
But from now on things get messy and to complicated for me.
In the Past i rooted and flashed it with "Shield-RAM", found here on xda.
But this Time it didnt ended with a working Shielt-Tablet. It stucks alwas in a Bootloop, in Recoverymode also as in normally booting the flashed OS.
Confused an disturbed by this, i tried different Recoverys (TWRP 2.8 and 3.0, also a CWM), all with the same Effect: Bootloop
Now i only can acces the Bootmenue which says Bootloader Unlocked.
I dont now what to do from here on and would be very happy and glad, if someone can help me figuring out whats going wrong.
If further Details are needed i will do my best to provide things i forgot here to mention.
With kind regards - ToxicFighter1
Ps.: excusy my bad spelling, bit rusty in flawless english typing:good:
Hi !
There is this thread where you can try to get it back to stock https://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541
This nice index may help as well
Good luck !
Thanks, but that's not the problem. If I boot into Fastboot / Bootloader, it's totally fine. In fact, I can plug the tablet up to my PC when it's in any state and doesn't experience the issue. It only occurs when I have it plugged into AC. SO far, I've tried 3-4 different cables and power supplies for 2.4A, 2.1A, and 1.2A - all adapters which worked 100% prior to updating.
Suggestions?
OK - Finally fixed it...
I replaced everything as shown above, but ran into the issue again as soon as FlashFire installed the OTA. So, I tried a different way to upgrade and no longer have the issue. Below is what I did...
- Installed 4.4.0 via ADB/fastboot wirhOEM recovery
- Completed initial setup and upgraded to 5.0 via built in system update
- Rebooted
- Booted to bootloader and flashed TWRP recovery
- Booted to TWRP
- Installed SuperSU via sideload
I would have started out applying 5.0 via adb/fastboot, but have yet to see a full image available yet. Used same TWRP and SuperSU as originally used. Just eliminated GlashFire from process. Once I rebooted and everything loaded, plugged into 2.4a power, and it worked without going into boot loop.
Hope this may help someone else - Thanks
Hey Folks,
thx for the few answers, i'll try these Tips out the upcomig Days.
Lot'a Stuff to do atm, bit Busy.
With kind regards - Toxic
xanthrax said:
Hi !
There is this thread where you can try to get it back to stock https://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541
This nice index may help as well
Good luck !
Click to expand...
Click to collapse
Hey there, and personally Thx for the provided Link.
As announced i did try it, but with no Success.
I'll or explicit the Tablet gets Stuck at Step 17, the Bootsreen doesn't disapear.
Dont know whats Wrong, cause i did all as menitioned in the Post, every ADB/Fastbootstep with Succes-Message, and because Bootloader was already Unlocked, i took the Rooted Image.
But now, im still on Bootscreen, sick
With kind regards!