Develop Bugs

A new thread for some knox only question. Maybe in thisvone place for reference. Beca

So... This knox @$€&s.
Please confirm the following so that people will be confident in upgrading.
1. You can rwmove it. It is not still stealthy hidden in background to shaft you.
2. Once removed you can do whatever you want to the phone like before.
Anymore questions.

Knox locked bootloader not only app u can uninstalled it what ever u like
Sent from my GT-N7100 using Tapatalk

This is one point of confusion I had. Various post say its a bootloader but then if you google it on the samsung supports page it details a way to dsiable it in a similar way as one would disable an app.
If its a bootloader aswell, would it mean a extra step to flash a compatible booloader as well as disabling the app.
Is there a guide on how to do all this, other than that vroot stuff which is said to be spyware.
It is everytime a new ota comes out we talk about rooting. Why cant they just give us root for everyone.

emgluon said:
So... This knox @$€&s.
Please confirm the following so that people will be confident in upgrading.
1. You can rwmove it. It is not still stealthy hidden in background to shaft you.
2. Once removed you can do whatever you want to the phone like before.
Anymore questions.
Click to expand...
Click to collapse
The way I understand it:
once you have KNOX and get rid of it, you will NEVER be able to use KNOX again
Hope this is correct?

http://www.samsung.com/global/business/mobile/solution/security/samsung-knox

Help me with 4.4 kit Kat root

My bootloader is still locked and I've never had root on this phone got it too late to unlock. I'd like to root and if I can get a custom recovery and flash a rom. Can anyone help?
Sent from my XT907 using Xparent Cyan Tapatalk 2

Gblake13 said:
My bootloader is still locked and I've never had root on this phone got it too late to unlock. I'd like to root and if I can get a custom recovery and flash a rom. Can anyone help?
Click to expand...
Click to collapse
Right now, there is no way to root or unlock the bootloader in your situation. It sucks, but it's where we are.
Don't hold your breath for an exploit, either. Motorola/Verizon closed all known holes for BL-unlocking in the penultimate Jellybean OTA, and the only root method that worked in the last JB no longer works here.

Enough with the KK unlock and root threads.
I'm going to start reporting people that make these threads without doing some homework first.
If you have a locked bootloader, you're pretty much up the creek without a paddle. End of discussion
If there is an exploit available, trust me, you'll know about it.

gtmaster303 said:
Enough with the KK unlock and root threads.
I'm going to start reporting people that make these threads without doing some homework first.
If you have a locked bootloader, you're pretty much up the creek without a paddle. End of discussion
If there is an exploit available, trust me, you'll know about it.
Click to expand...
Click to collapse
We can say this in every thread where they ask about root. We put warnings out prior to the OTA. Heck, we could probably put a sticky thread in this section about there being no root on KK, yet people will still ask. Why? Because they refuse to take 5 minutes to read through the other 37 KK related threads.

RikRong said:
We can say this in every thread where they ask about root. We put warnings out prior to the OTA. Heck, we could probably put a sticky thread in this section about there being no root on KK, yet people will still ask. Why? Because they refuse to take 5 minutes to read through the other 37 KK related threads.
Click to expand...
Click to collapse
I of course can't speak for anyone else, but I knew the risks well before taking the update, and updated anyway.
I knew it was the very un-XDA thing to do, but frustration with the short battery life and UI lag on my phone was nearing a breaking point.
I tried to make the most of it; hence the "list of changes" thread, which hopefully has scared away locked users who are still n JB.

Any luck with a rootkeeper/root survival of any kind?

pnwsr6 said:
Any luck with a rootkeeper/root survival of any kind?
Click to expand...
Click to collapse
Haven't seen it yet.

Strife89 said:
I of course can't speak for anyone else, but I knew the risks well before taking the update, and updated anyway.
Click to expand...
Click to collapse
My story is somewhat different. I tried to find a way to get rooted KK on my phone (trying to play junior hacker again), ended up soft-bricking my phone to where the only way to fix it was to flash stock KK using RSDLite (did try RSD'ing JB first, but my bootloader was having none of that).
So now I'm hopelessly stuck with a completely stock phone without root.
I feel like the only way to get past this is to attack it politically, like if every single Verizon XDA user banded together and flooded Verizon corporate inboxes with legitimate reasons why we need unlocked bootloaders.
Or maybe if someone is good friends with a politician who is more left of center and concerned about consumer rights over corporations. Maybe convince them that it's better for the environment because potentially millions of phones could be saved from going into landfills if we mandate companies must allow bootloader to be unlocked when certain conditions are fulfilled, like if a phone reaches 1-year of age.

Strife89 said:
I of course can't speak for anyone else, but I knew the risks well before taking the update, and updated anyway.
I knew it was the very un-XDA thing to do, but frustration with the short battery life and UI lag on my phone was nearing a breaking point.
I tried to make the most of it; hence the "list of changes" thread, which hopefully has scared away locked users who are still n JB.
Click to expand...
Click to collapse
I new I was losing root with it as well. I liked the features that KK brought with the update and still did it. The update finally got me using Smart Actions and I'm getting pretty decent battery life, nothing mind blowing, but pretty good. Buying a portable battery pack has pretty much solved the problem I had with nonroot. Now I can go about 2 days as long as I carry it around, lol. Luckily it's small.

if I have an unlocked BL, and the latest stock version on KK, how would I get root? Is it possible?
thanks.

Ahoalton said:
if I have an unlocked BL, and the latest stock version on KK, how would I get root? Is it possible?
thanks.
Click to expand...
Click to collapse
Flash a custom recovery via fastboot, and then flash SuperSU zip in recovery.

http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623 <-- this thread (not saying it works) is getting popular with Motorola devices. I attempted it myself and got errors just like some other people. Only difference is they still had root and I don't. I suggest following the thread and seeing if it does someday work for us or somebody could attempt it themselves. I'm currently on windows 8.1 so that could be a problem.

megaghostgamer said:
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623 <-- this thread (not saying it works) is getting popular with Motorola devices. I attempted it myself and got errors just like some other people. Only difference is they still had root and I don't. I suggest following the thread and seeing if it does someday work for us or somebody could attempt it themselves. I'm currently on windows 8.1 so that could be a problem.
Click to expand...
Click to collapse
^^^He doesn't need an exploit since he has an unlocked BL. Also, this has been checked on the M and HD family of devices, it WILL NOT work because the the current KK updates have already patched the hole that this exploit is meant to take advantage of.

Ahoalton said:
if I have an unlocked BL, and the latest stock version on KK, how would I get root? Is it possible?
thanks.
Click to expand...
Click to collapse
Yes!.. Just use URL="http://androidhosting.org/Devs/Dhacker29/msm8960/CWM6049-RAZR-HD_M-KITKAT.img"]custom recovery[/URL] and flash Superuser zip

And what about aka test points? Many Motorola models had such special test points using which you could get unlock of BL. How about our XT907? Any ideas about test points or shortcircuit of contacts?

No need now! Towelroot will root stock KK, and what magic it does allows Motopocalypse to unlock BL again.

http://www.droid-life.com/2014/06/16/motorola-bootloader-unlock-razr-hd-towelroot/
Confirmed working!
Root and bootloader unlock!
Sent from my Droid RAZR M

GnatGoSplat said:
No need now! Towelroot will root stock KK, and what magic it does allows Motopocalypse to unlock BL again.
Click to expand...
Click to collapse
Towel Root only allows the root access that Motopocalypse needs. The old trust zone was accidentally (or purposely) put back into this OTA, that's what Motopocalyse exploits.
Sent from my HTC6525LVW using Tapatalk

RikRong said:
Towel Root only allows the root access that Motopocalypse needs. The old trust zone was accidentally (or purposely) put back into this OTA, that's what Motopocalyse exploits.
Click to expand...
Click to collapse
Ah, I see. Good to know. :good:

Is root possible for SAMSUNG-SM-N910A on 5.1.1 build number LMY47X.N910AUCU2DOI3 ?

I have been searching for a few days and can't seem to find any available method to root this build number. It's my own fault for accepting the most recent update, I should have known better. If anyone knows of a root method for this build I would love to know how to do it.

from where have you downloaded N910AUCU2DOI3

Latest update from AT&T through system update.

At this time there is none. There likely will never be permanent root for this device, either. Best hope is for a future update of KingRoot to come that gives a very buggy temp-root.

naverone said:
I have been searching for a few days and can't seem to find any available method to root this build number. It's my own fault for accepting the most recent update, I should have known better. If anyone knows of a root method for this build I would love to know how to do it.
Click to expand...
Click to collapse
i rooted the SM-N910A NOTE4 using root king and it said root successful then after reboot it bricked itself anda screen came out saying warning at&t has detected ilegal custom software on your device please turn of your device and head to the nearest at&t support center. Honestly you have two choices from what i understand There is 2 U.S. carriers that put what they call a boot lock on their device bootloaders. there is a way to remove the boot lock. google it or ask XDA to assist you . GOOD LUCK. Me personally posted many threads requesting help being that im a noobie and dont know jack sh... about unlocking rooting anything and nobody ever bothered to help me or maybe they just too busy devoloping what ever the case was i had my phone for atleast 2 weeks and i did research during that whole time in different forums like android central etc. and finally figured how to do it. For get about going to AT&T they will tell you your warranty is void and that your phone is permanantly hard bricked and all they do is lie to you so you can purchase a new device. I finally restored my device by installing official firmware that you can download free from sammobil.com via odin 3.10.6 they will give you a complete guide. and the correct download links for the proper tools needed to complete the job NOTE: this worked for me its not a hundred percent sure that it will work for you. Please note and understand that you can do this at YOUR OWNE RISK I will not take responsibility for any damage that you may do to your device by using this method and there is a possibility if you dont do it right you can hard brick your phone PERMANENTLY!!!!!!! proceed at your owne risk if you try to blame me for damages to your phone i will laugh at you HARD!!!
---------- Post added at 07:11 PM ---------- Previous post was at 06:51 PM ----------
teddyherrera1 said:
i rooted the SM-N910A NOTE4 using root king and it said root successful then after reboot it bricked itself anda screen came out saying warning at&t has detected ilegal custom software on your device please turn of your device and head to the nearest at&t support center. Honestly you have two choices from what i understand There is 2 U.S. carriers that put what they call a boot lock on their device bootloaders. there is a way to remove the boot lock. google it or ask XDA to assist you . GOOD LUCK. Me personally posted many threads requesting help being that im a noobie and dont know jack sh... about unlocking rooting anything and nobody ever bothered to help me or maybe they just too busy devoloping what ever the case was i had my phone for atleast 2 weeks and i did research during that whole time in different forums like android central etc. and finally figured how to do it. For get about going to AT&T they will tell you your warranty is void and that your phone is permanantly hard bricked and all they do is lie to you so you can purchase a new device. I finally restored my device by installing official firmware that you can download free from sammobil.com via odin 3.10.6 they will give you a complete guide. and the correct download links for the proper tools needed to complete the job NOTE: this worked for me its not a hundred percent sure that it will work for you. Please note and understand that you can do this at YOUR OWNE RISK I will not take responsibility for any damage that you may do to your device by using this method and there is a possibility if you dont do it right you can hard brick your phone PERMANENTLY!!!!!!! proceed at your owne risk if you try to blame me for damages to your phone i will laugh at you HARD!!!
Click to expand...
Click to collapse
forgot to tell you the two U.S. carriers that put locks on their bootloaders is AT&T and VERIZON so i wouldnt recommend root unless you unlock bootloader or else your phone will continueously stay in boot mode without letting you exit. that i believe is a bootloop good luck

teddyherrera1 said:
Honestly you have two choices from what i understand There is 2 U.S. carriers that put what they call a boot lock on their device bootloaders. there is a way to remove the boot lock. google it or ask XDA to assist you . GOOD LUCK.
Click to expand...
Click to collapse
You CANNOT unlock our bootloader and DO NOT ask XDA. Googling it will not result in anything useful either.
Our bootloader is still not able to be unlocked and thus Googling for an answer will only bring up scams, false information, or just no results.
teddyherrera1 said:
Me personally posted many threads requesting help being that im a noobie and dont know jack sh... about unlocking rooting anything and nobody ever bothered to help me or maybe they just too busy devoloping what ever the case was i had my phone for atleast 2 weeks and i did research during that whole time in different forums like android central etc. and finally figured how to do it.
Click to expand...
Click to collapse
Not sure if you're referring to unlocking the bootloader still or about fixing the soft brick caused by Kingroot. Either way, the reason why no one answered you here on XDA is because both questions are asked at least every other week by people who either can't use the search function or just don't even try to. We here in the XDA community are more than happy to help noobs, but if we see the EXACT same questions being asked over and over again, then we will begin to ignore them since the answers are readily available already.
teddyherrera1 said:
For get about going to AT&T they will tell you your warranty is void and that your phone is permanantly hard bricked and all they do is lie to you so you can purchase a new device. I finally restored my device by installing official firmware that you can download free from sammobil.com via odin 3.10.6 they will give you a complete guide. and the correct download links for the proper tools needed to complete the job NOTE: this worked for me its not a hundred percent sure that it will work for you. Please note and understand that you can do this at YOUR OWNE RISK I will not take responsibility for any damage that you may do to your device by using this method and there is a possibility if you dont do it right you can hard brick your phone PERMANENTLY!!!!!!! proceed at your owne risk if you try to blame me for damages to your phone i will laugh at you HARD!!!
Click to expand...
Click to collapse
Yes, for our phones- since there is no possibility to root and thus no risk of doing very serious software damage- Odin is usually the cure-all for most problems. You can find the latest available Odin file in our phone's thread, and use Google to find tutorials on how to use Odin itself.

How I root Samsung Galaxy note 4 SM n910a 4.4.4

spexwood said:
You CANNOT unlock our bootloader and DO NOT ask XDA. Googling it will not result in anything useful either.
Our bootloader is still not able to be unlocked and thus Googling for an answer will only bring up scams, false information, or just no results.
Not sure if you're referring to unlocking the bootloader still or about fixing the soft brick caused by Kingroot. Either way, the reason why no one answered you here on XDA is because both questions are asked at least every other week by people who either can't use the search function or just don't even try to. We here in the XDA community are more than happy to help noobs, but if we see the EXACT same questions being asked over and over again, then we will begin to ignore them since the answers are readily available already.
Yes, for our phones- since there is no possibility to root and thus no risk of doing very serious software damage- Odin is usually the cure-all for most problems. You can find the latest available Odin file in our phone's thread, and use Google to find tutorials on how to use Odin itself.
Click to expand...
Click to collapse
"Our bootloader" ... "our phones" You make it sound as if you're a rep or employee of AT&T. And if so then wth is so wrong with simply allowing people root access to the phones they bought n own? I understand stupid people with powerful tools make powerful stupid mistakes. But smart people who can fix their own few mistakes would still greatly appreciate being allowed to adjust the phone to drastically increase efficency, or at least remove the bloated optimization cap.
Or those who want root so that they can utilize a form of genuine location and privacy protection. To choose whether or not the app they haven't used in weeks still needs to run in the background all the time or still check your location.
Idk... I'll step off my soap box now. Maybe I'll just say screw it and swap the note 4 for another rootable note 3. Since my straight talk phone service is reliant on the AT&T tower near me for any service.

Spooters said:
"Our bootloader" ... "our phones" You make it sound as if you're a rep or employee of AT&T. And if so then wth is so wrong with simply allowing people root access to the phones they bought n own? I understand stupid people with powerful tools make powerful stupid mistakes. But smart people who can fix their own few mistakes would still greatly appreciate being allowed to adjust the phone to drastically increase efficency, or at least remove the bloated optimization cap.
Or those who want root so that they can utilize a form of genuine location and privacy protection. To choose whether or not the app they haven't used in weeks still needs to run in the background all the time or still check your location.
Idk... I'll step off my soap box now. Maybe I'll just say screw it and swap the note 4 for another rootable note 3. Since my straight talk phone service is reliant on the AT&T tower near me for any service.
Click to expand...
Click to collapse
1) That post was made back in 2016. That was over 2 years ago!!! Why did you necro such an old thread? The last post made here was Dec 5, 2016.
2) I no longer have the n910a. Got rid of it a long time ago
3) I do not, nor never have worked for ATT nor am affiliated with them in any way.
4) When I used the word "our" I was referring to the fact that I too owned the n910a. So "our phone" obviously meant "my n910a and everyone else's" and same for the "our bootloader"
5) At the time of my post, root was not available for rhe n910a AT ALL. (If I recall, a temporary root eventually became available though, but it reset everytime you restarted your phone). On a daily basis, people were asking whether root was available or not and people were getting sick of answering the same question over and over again when the answer fould easily be found through a simple search here on XDA.
There were also scams going on at the time BECAUSE this was such a popular topic. Websites claimed to give walkthroughs on how to root your n910a, but all they really did was brick your phone. Kingroot was one of them.

Help - Bricked HTC m9 - Not rooted - Advice needed -

Hi,
My wife HTC m9(UK, Vodaphone, latest stock ROM, No root) was turned off last night to charge.
When booted up it does the below. It does not load into the OS. Every boot loops into the below.
https://drive.google.com/file/d/0B8n21CQX7535cjF4MnZqV2E1dGM/view?usp=sharing
It says the software has been modified?
My wife was very insistent that I never root or change ROMS on her phone.
Does anyone have a fix or is this send off for replacement?
Any advice would be greatly appreciated.
Thanks
Ca1v

ca1v said:
Hi,
My wife HTC m9(UK, Vodaphone, latest stock ROM, No root) was turned off last night to charge.
When booted up it does the below. It does not load into the OS. Every boot loops into the below.
https://drive.google.com/file/d/0B8n21CQX7535cjF4MnZqV2E1dGM/view?usp=sharing
It says the software has been modified?
My wife was very insistent that I never root or change ROMS on her phone.
Does anyone have a fix or is this send off for replacement?
Any advice would be greatly appreciated.
Thanks
Ca1v
Click to expand...
Click to collapse
What happens if you try to boot to Download Mode? I guess you see the black screen that is mentioned in Q7, right? If that's the case there isn't much you can do...

Download mode seems to be working (https://drive.google.com/file/d/0B8n21CQX7535cEFhTlpnajF5anM/view?usp=sharing)
If this is the case, can you point me in the right direction to get resolved?
Many thanks for the help

Flippy498 said:
What happens if you try to boot to Download Mode? I guess you see the black screen that is mentioned in Q7, right? If that's the case there isn't much you can do...
Click to expand...
Click to collapse
Download mode seems to be working (https://drive.google.com/file/d/0B8n...ew?usp=sharing)
If this is the case, can you point me in the right direction to get resolved?
Many thanks for the help

Interesting. Your video in post 1 shows a security warning. That means that the OS got deleted. This is only possible if you unlock the bootloader and delete it manually via TWRP or if the EMMC gets broken. Since the phone's S-ON and its bootloader is locked and not unlocked or relocked I assumed that the latter happened*.
As long as the download mode is working you can restore the system with the help of a RUU. Instructions can be found in the thread I linked in my last post. Be aware that all data on the phone is going to get erased.
* Well, it is possible to get the phone's status back to S-ON and locked with S-OFF but you said you never tinkered with that phone...

Flippy498 said:
Interesting. Your video in post 1 shows a security warning. That means that the OS got deleted. This is only possible if you unlock the bootloader and delete it manually via TWRP or if the EMMC gets broken. Since the phone's S-ON and its bootloader is locked and not unlocked or relocked I assumed that the latter happened*.
As long as the download mode is working you can restore the system with the help of a RUU. Instructions can be found in the thread I linked in my last post. Be aware that all data on the phone is going to get erased.
* Well, it is possible to get the phone's status back to S-ON and locked with S-OFF but you said you never tinkered with that phone...
Click to expand...
Click to collapse
Just thought I'd bring to your attention that apps are now being written that will try to obtain root without you knowing. The reason is that they can steal any information they want and sell it to corporations for as little as 4 pence/6c a record.
It is possible that it is a failed root by an app.
"I'm safe, I only download my apps from google playstore" - nope, you're not.
"I only use signed apps and the checksum is always correct" - nope, checksum can be matched with padding.
"I only use external sources to update genuine apps" - nope, see the Google playstore comment above.
"I have all my security and privacy set to super strict, I have my apps verified by google" - nope, still not secure because alerts are only written when the malicious/bad code is found.
Be warned, my fellow xda'ers. There is a whole new breed of security breach and it is terminal to root as a whole. Apps like kingoroot etc are issuing the wrong type of people with the wrong type of information and they are using it for the wrong purposes.
Google will stuggle to put a lid on these types of apps because they attack the hardware for access to software (a simple memory buffer overflow attack), inject a few lines of code and you're in, permanently. It will eventually result in a total lockdown at the manufacturer and bye bye root access, roms, mods etc, you'll get what you're given.
How do we prevent this?. We don't and we can't. We just have to sit back and watch as the world takes our privacy while bricking our devices one by one just to "try" to earn a poxy 4p.
Beamed in by telepathy.

@shivadow: I'm actually not sure what you're trying to achieve with your post. Malicious apps that can root your device without letting the user know about that exist since several years now. (Click here for a random example from 2011) Smartphones aren't completely safe and they never were. Everyone who's claiming the opposite either doesn't know what he/she is talking about or is simply lying.
To name just a few more android security flaws/exploits that emerged in the past: rageagainstthecage, gingerbreak, heartbleed, stagefright, the master key vulnerability, the futex bug, rootnik...
All of these have more or less been used for manipulating android phones. There is no absolute security. Android is still as secure/insecure as it's always been.
In addition, several OEMs are already trying to prevent their customers from rooting their phones since several years. Samsung's KNOX is a perfect example. (I don't want to discuss whether they're successful. That's a whole different topic.)
But let's get back to the deleted OS of the OP's phone: I've never heard about failed root attempts that erase a complete system partition. Therefore, I highly doubt that a malicious app caused all the trouble. Failed root attempts may cause a bootloop but they don't wipe your phone. Just think about the following: How should the dev of such app gain money if the app deletes OSes? Without OS there is no information you can steel and if you have no information you could sell/abuse/whatsoever you don't gain any money. Oh and not to forget that most apps on the play store already collect more than enough data from your phone they can sell afterwards without having to root it.

I meant failed root could be the cause, if the op didn't then who did?. If no-one modded it then dead nand is the only player..
I agree with every thing else but I don't trust those apps that try to gain root in the background to steal data and I think it's too easy for them to bugger your phone just for the sake of making a few coins. Face it, if I was doing it, once I had what I wanted I wouldn't care about the device. Sod the gracious exit and all that jazz.. No evidence, no conviction.
Maybe I'm being ott but my questions and points are still valid.
This is a proper "who dunnit" because I doubt it died of its own accord.
Knox is for businesses btw. If knox is triggered, which is very easy to do, the business is advised not to buy the device as it "may" have been compromised. But if no company secrets are being held on the device then it's still good to use. Knox protection was counteracted by supersu. In a nutshell, unless you run a company knox is of no concern to the everyday user.
Just thought I'd chuck that in there, I'm versed in the arts of the s3 i9300. I moved from that phone to this m9.
Beamed in by telepathy.

Is there any instruction how to unlock bootloader of LG-H818P?

Is there any safe method to unlock it for noob like me? I found something herehttps://forum.xda-developers.com/g4/general/unlock-bootloader-h818-t3564238 but it's very risky and there are no clear instructions. Can you help me? Maybe they exist but IDK where.

pranciskus2 said:
Is there any safe method to unlock it for noob like me? I found something herehttps://forum.xda-developers.com/g4/general/unlock-bootloader-h818-t3564238 but it's very risky and there are no clear instructions. Can you help me? Maybe they exist but IDK where.
Click to expand...
Click to collapse
There is no safe way to unlock the boatloader of the H818P at this point in time and that is unlikely to change. It can be unlocked unofficially with steadfasterX's UsU method but unfortunately you would lose the touch function of your screen, rendering the phone basically useless. Do not ask on his thread there again, as you will see it has been asked and answered far too many times already. If steadfasterX couldn't do it, no one can, IMO.
Do not attempt to do it with any method you come across - you will have serious issues with a high probability of very hard bricking your phone, turning it into a fancy paperweight.

sdembiske said:
There is no safe way to unlock the boatloader of the H818P at this point in time and that is unlikely to change. It can be unlocked unofficially with steadfasterX's UsU method but unfortunately you would lose the touch function of your screen, rendering the phone basically useless. Do not ask on his thread there again, as you will see it has been asked and answered far too many times already. If steadfasterX couldn't do it, no one can, IMO.
Do not attempt to do it with any method you come across - you will have serious issues with a high probability of very hard bricking your phone, turning it into a fancy paperweight.
Click to expand...
Click to collapse
I see, it's pretty weird that the only obstacle is touch stopping to work. Hard to believe that such problem wasn't solved.