I just got my Verizon (910v) note 4, and I want to unlock the bootloader, but it is running CQE1 as well as the may 2017 security patch, and I want to make sure it is safe to follow the downgrade and unlock.
***UPDATE***
According to @DesertRatBiggs it is possible to downgrade and unlock your bootloader on CQE1. here is a link to the thread.
https://forum.xda-developers.com/no...wngrade-mm-t3573012/post73344263#post73344263
Me, too. I'm very curious to know if this stock baseband has been unlocked ... or if we (and the countless others in our specific situation) will simply never be able to fully unleash these powerful Note 4 Beasts like we'd like. (I'd sure pay some cash for the privilege...)
ibcdub said:
Me, too. I'm very curious to know if this stock baseband has been unlocked ... or if we (and the countless others in our specific situation) will simply never be able to fully unleash these powerful Note 4 Beasts like we'd like. (I'd sure pay some cash for the privilege...)
Click to expand...
Click to collapse
If I had any money I could pay I would be more than willing to do so, unfortunately I could not afford it right now.
In my current situation my screen gets very hot(not sure if it is supposed to) and so I would really like to flash a Note 7 port so I could scale down my resolution to 1080p to see if that helps with the heat. I know no one asked I just figured that if I made my situation known maybe someone could/would help me/us out.
BTW I got mine second hand, but it is in fantastic shape. Also the indicator under the battery show no signs of water damage. I say this because I know water damage can definitely cause heat problems
Is there anyone that knows anything that could help us?
In the general section it looks as though it has already been confirmed as doable... check this link and if it helps give me a thanks.
https://forum.xda-developers.com/no...ctory-binary-successful-downgrade-mm-t3573012
Thank you very much I will check it out!
But I didn't see anything about cqe1
Does anyone know?
I just realized I misspoke in my last comment. I want to know if unlocking your bootloader is safe on cqe1. please guys are really need to know.
As it turns out...YES! can downgrade and unlock you bootloader safely. At least as far as I understand, i have not yet tried it BUT in the thread which i have linked in the OP @DesertRatBiggs was kind enough to confirm that it can indeed be done. I will try it tonight and give you my results. I encourage anyone who benefits from @DesertRatBiggs information to give him thanks.
bucs9115 said:
I just realized I misspoke in my last comment. I want to know if unlocking your bootloader is safe on cqe1. please guys are really need to know.
Click to expand...
Click to collapse
No but you can downgrade to bpa1 and run the gauntlet
Related
I know it was only released yesterday, but I know nothing about the current Desire models. I come from the realm of CDMA Hero's and am moving to the Samsung Epic. My brother just picked up a desire and wants to root it.
Is the current Desire a GSM or CDMA phone?
And has anyone who has gotten the new USC Desire, have you tried the current root method to see if it works. I have doubts that it will.
I am going to assume after looking through this forum a little bit that the current model being developed for here is GSM.
The US Cellular Desire is the first CDMA phone to be called "HTC Desire". Tread carefully. But please also report any positive/negative results so that others can learn from your win/fail.
cmstlist said:
The US Cellular Desire is the first CDMA phone to be called "HTC Desire". Tread carefully. But please also report any positive/negative results so that others can learn from your win/fail.
Click to expand...
Click to collapse
Thankfully I am pretty Android savvy. I just wasn't sure if it was CDMA or GSM - No radio updates for this phone .
If the current root method does not work I will attempt the ones for other devices running 2.1 and might even try the new EVO/Epic root for 2.2.
I'll get this thing rooted if I have to find my own.
Kcarpenter said:
Thankfully I am pretty Android savvy. I just wasn't sure if it was CDMA or GSM - No radio updates for this phone .
If the current root method does not work I will attempt the ones for other devices running 2.1 and might even try the new EVO/Epic root for 2.2.
I'll get this thing rooted if I have to find my own.
Click to expand...
Click to collapse
I can't wait to get my US Cellular Desire and I'm really hoping for root. Let us know if you have any luck.
So what are the actual chances that it will work on the uscc desire? I got mine so I guess ill just have to try it tonight.
The us desire has a bootloader 0.98.xxxx you will have to downgrade to a different hboot plus I'm pretty sure all the roms only support a gsm radio.
Odd_Sam said:
The us desire has a bootloader 0.98.xxxx you will have to downgrade to a different hboot plus I'm pretty sure all the roms only support a gsm radio.
Click to expand...
Click to collapse
Again, tread with caution... if a different HBOOT bricks the phone... there's not much recourse!
From what I have read/observed, the USCC Desire is basically the same phone as the Nexus One. I would like to know what is different about this thing that would prevent me from rooting and/or upgrading to 2.2.
Anyone have any advice? I can't wait to upgrade this piece.
CreepingDeath said:
From what I have read/observed, the USCC Desire is basically the same phone as the Nexus One. I would like to know what is different about this thing that would prevent me from rooting and/or upgrading to 2.2.
Anyone have any advice? I can't wait to upgrade this piece.
Click to expand...
Click to collapse
Well, Desire is CDMA. Nexus one is not. completely different cellular radio HARDWARE. and that pesky slcd is also a problem.
Gonna have better luck adapting a cdma android root. (incredible, evo, etc..) at least they use the same radio technology.
i thought the incredible was supposed to get the slcd also...... that would help alot.
I know this doesn't provide any technical information, but just as an FYI I did ask HTC what their policy on rooting is. They said:
"Of course the Desire is your phone. If you would like to root the phone or install 3rd party software to it, you are more than welcome to. It's just that with any 3rd party software, HTC did not create it so we do not have information on how it works therefore, we can not support it. As far as voiding any warranties, I do not have that information. You may contact our Warranty Deparment at 1-800-229-1235 (8:30 AM - 5 PM EST M-F). They will be able to verify that information with you. HTC has repaired some phones that had the incorrect ROM on them. There may have been a fee for this, I am not certain."
I hadn't gotten around to calling about the warranty. I had read elsewhere that as long as the damage wasn't a result of the rooting that they would still repair a rooted phone under warranty, but I don't know if there's any truth to that.
Anyway, I don't know if this helps alleviate any concerns about experimenting with it or not. I had gotten as far as making a gold card for it yesterday, but I'm kind of afraid to go any further until I can get some more information on this specific phone. I feel like there may be a chance with this method since it takes information from your actual device. Anyone have any thoughts on that?
psychache said:
I know this doesn't provide any technical information, but just as an FYI I did ask HTC what their policy on rooting is. They said:
"Of course the Desire is your phone. If you would like to root the phone or install 3rd party software to it, you are more than welcome to. It's just that with any 3rd party software, HTC did not create it so we do not have information on how it works therefore, we can not support it. As far as voiding any warranties, I do not have that information. You may contact our Warranty Deparment at 1-800-229-1235 (8:30 AM - 5 PM EST M-F). They will be able to verify that information with you. HTC has repaired some phones that had the incorrect ROM on them. There may have been a fee for this, I am not certain."
I hadn't gotten around to calling about the warranty. I had read elsewhere that as long as the damage wasn't a result of the rooting that they would still repair a rooted phone under warranty, but I don't know if there's any truth to that.
Anyway, I don't know if this helps alleviate any concerns about experimenting with it or not. I had gotten as far as making a gold card for it yesterday, but I'm kind of afraid to go any further until I can get some more information on this specific phone. I feel like there may be a chance with this method since it takes information from your actual device. Anyone have any thoughts on that?
Click to expand...
Click to collapse
Once you make a gold card, which rooting technique are you going try? Unrevoked is the simplest overall but I think HBOOT 0.98 fixed the exploit that Unrevoked uses.
I tried unrevoked the other day and it said that it was unsupported. I don't know that I'll go as far as trying to root at this point. I was kind of hoping that someone else would try it first, ha . . . Initially I was doing the gold card just to see if I could at least unbrand it so I could install the OTA update. But then I run into the original issue of whether or not it supports CDMA and/or SLCD. Is there any way to tell aside from actually attempting to flash it? Maybe it would be safer to try one of the methods for the Incredible? Not sure what version of HBOOT that has on it. Honestly, I'm pretty far from being any kind of expert on this. So far I've only had experience with rooting the Moto Droid and that was pretty much cake since the phone is so old at this point.
psychache said:
I tried unrevoked the other day and it said that it was unsupported. I don't know that I'll go as far as trying to root at this point. I was kind of hoping that someone else would try it first, ha . . . Initially I was doing the gold card just to see if I could at least unbrand it so I could install the OTA update. But then I run into the original issue of whether or not it supports CDMA and/or SLCD. Is there any way to tell aside from actually attempting to flash it? Maybe it would be safer to try one of the methods for the Incredible? Not sure what version of HBOOT that has on it. Honestly, I'm pretty far from being any kind of expert on this. So far I've only had experience with rooting the Moto Droid and that was pretty much cake since the phone is so old at this point.
Click to expand...
Click to collapse
There's only one set of RUU that support CDMA at this point. Pretty much any other attempt will brick your desire. You could try one of those RUU's and see if it downgrades where you could root then.
Yeah, I think I'm going to wait until some sort of tested method is worked out. I'm not at any kind of skill level to be figuring this stuff out on my own. Overall I'm pretty pleased with how the phone worked right out of the box. My only major complaint is the lack of internal storage for apps and the fact that you can't remove any of the preinstalled crap. This is the only reason I was really even looking into rooting or unlocking at this point. I just hope that the fact that the EVO and Incredible got their updates means that one can't be far off for the Desire.
psychache - I feel ya there. I got mine and I love it. However, was kinda skiddish on testing on this new unit. Whether or not the insurance would cover it if I bricked it. Even then, would still be another $100 deductible.
I am willing to try something. I already tried the Universal Androot to no avail... no brick or anything, it just didnt take.
Well, if anyone else is up to the challenge you could always call the number I posted above to get a definite answer on whether you would still have coverage if you did brick. I had actually had several replies back and forth with them before I asked specifically about rooting and was very impressed by how responsive and open-minded they were. I'd say of any of the manufacturers they're probably the most likely to be "cool" about it. And you're right, primerorico, worst case scenario is you could do an insurance claim and pay the $100 (you know, because you "lost" it). I know that's not cheap but it's a heck of a lot less than paying the full retail for a new one. Just food for thought for anyone who actually knows what they're doing . . . (unlike myself)
Someone has made some progress in rooting. Not sure if he needs some help but here is the thread: http://forum.xda-developers.com/showthread.php?p=7917553
heavymetalmage said:
Someone has made some progress in rooting. Not sure if he needs some help but here is the thread: http://forum.xda-developers.com/showthread.php?p=7917553
Click to expand...
Click to collapse
Thanks for the link. I'll definitely keep an eye on it.
The thing is, we weren't even going to root it. I thought that Teamviewer Quicksupport supported all S3's.
I looked and he is running 4.1.1. So...I'm not sure what the big deal is, but no matter what, Quicksupport is not "supported" when we go to the Play Store. If there is a simple fix, I would love this, because he is not tech-savvy and this is why we got this model.
However -
I've only rooted one phone in my life before, when there was only really one way of rooting. It seems I have read that problem abound with these S3 models - more specifically, IMEI may be lost, and choosing exactly which way to root, since there are varying stock kernels.
I see this thread here on the IMEI backup/injection. Am I safe to assume, that is where I start? (I have read that the Bell is just a ATT version, so will the ATT version instructions work here? I will ask in that thread but not sure).
Then - once that is done - I have to pick a way to root it that works for Bell's SIII SGH-1747M. That is where I am running into a bit of a wall. I wonder if I can get someone who has done this with this model to help me out and pick a safe way to mod it? Do I need to post more info to help decide this? I can get on his device and get whatever info is needed.
I also read, that perhaps Bell's stock kernels either do or do not need unsecuring (not quite sure after a lot of reading) before doing anything else. I really am trying to learn - it's just all very daunting and when I'm reading and not understanding, I can still read til the sun explodes and never be able to do this correctly. Well, maybe if I had an unending supply of phones.
Thank you for your help...
I would just ask in the IMEI and other forums but they are not available to me (either post count too low or I'm not sure).
Sincerely,
Foxdev
foxdev said:
The thing is, we weren't even going to root it. I thought that Teamviewer Quicksupport supported all S3's.
I looked and he is running 4.1.1. So...I'm not sure what the big deal is, but no matter what, Quicksupport is not "supported" when we go to the Play Store. If there is a simple fix, I would love this, because he is not tech-savvy and this is why we got this model.
However -
I've only rooted one phone in my life before, when there was only really one way of rooting. It seems I have read that problem abound with these S3 models - more specifically, IMEI may be lost, and choosing exactly which way to root, since there are varying stock kernels.
I see this thread here on the IMEI backup/injection. Am I safe to assume, that is where I start? (I have read that the Bell is just a ATT version, so will the ATT version instructions work here? I will ask in that thread but not sure).
Then - once that is done - I have to pick a way to root it that works for Bell's SIII SGH-1747M. That is where I am running into a bit of a wall. I wonder if I can get someone who has done this with this model to help me out and pick a safe way to mod it? Do I need to post more info to help decide this? I can get on his device and get whatever info is needed.
I would just ask in the IMEI and other forums but they are not available to me (either post count too low or I'm not sure).
Sincerely,
Foxdev
Click to expand...
Click to collapse
You can root without worrying about losing your IMEI.. Give this thread a look over.. Click
BAM1789 said:
You can root without worrying about losing your IMEI.. Give this thread a look over.. Click
Click to expand...
Click to collapse
Thanks, I just added it as a part of the research I did I am not worried so much about that anymore, but the other things are like....making my mind explode. All I've ever done so far is my Thunderbolt 2 years ago and that was so easy.
foxdev said:
Thanks, I just added it as a part of the research I did I am not worried so much about that anymore, but the other things are like....making my mind explode. All I've ever done so far is my Thunderbolt 2 years ago and that was so easy.
Click to expand...
Click to collapse
this is actually a pretty simple device to root too. Just pick a method and read it over and it'll be pretty hard to screw anything up
Sent from my R800i using xda app-developers app
Also make a backup of your imei just in case something goes sideways.
Sent from my SAMSUNG-SGH-I747 using xda premium
d3athsd00r said:
Also make a backup of your imei just in case something goes sideways.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks, going to do that for sure
Also, does anyone know with this model if Teamviewer Quicksupport just doesn't work at all? I cant get answers from Teamviewer. If it did I wouldn't need to root the stupid thing!
i don't understand why you believe you need to root to have this app supported. i attempted to use the app and it told me i needed to download an app from here. try that before you root?
edit: also i am rooted and it still did not allow me to use the app. rooting isn't your solution here
sent from my I747
HI everyone,
My girlfriend has a T-Mobile Samsung Galaxy T-999 phone and she is using Straight Talk as her provider. She is using Android Version 4.1.2 ( which I wanted to root before I factory reset her phone- which I did before via the Dial Pad but at the last option after I wait the 30 seconds to a minute the last option isn't there; so I left it alone. and updated her phone to 4.3 ) But it isn't necessary to root her phone today unless it's very easy.
What I wanted to know is, is it safe to Factory Reset her Phone and than allow Kies to upgrade her firmware to 4.3 and still be able to use Straight Talk as long I put back in her APN settings that she is using right now?
Now as for me,
I own a
Verizon S4
AT&T S4 - Which was blacklisted because I bought it off Craigslist and a man called it in stolen and got me for $550.That's a story in itself
2x AT&T S3-One has a cracked screen but the digitizer is working fine, it's just the outer screen that is cracked, and I have a working S# which I use on a daily basis.
My issues, I will look up and spend some more time on XDA today and learn how to do everything correctly.
I wouldn't mind testing everything I learn either on the cracked S3 or my blacklisted S4 which are both on AT&T network.
I have rooted only phone back in the day,( a long time ago via dial pad which i think it might of been on 4.1.1. firmware) .- phone that would cause an issue on my part. Now, when I am not working I search and have read MANY MANY times on XDA and wanted to let everyone know that I appreciate everything that you all do on your own free time. But most importantly today, i need to work on her phone and get it updated and working correctly.
Thanks in advance for anyone who responds to this post.:good:
Are you trying to root or unlock? The first part about the dial pad and option not being there sounds like the unlock method, I don't know of any root method involving the dial pad
Sent from my SGH-M919 using Tapatalk
reply
what i really need to know is this part..
"My girlfriend has a T-Mobile Samsung Galaxy T-999 phone and she is using Straight Talk as her provider. She is using Android Version 4.1.2
What I wanted to know is, is it safe to Factory Reset her Phone and than allow Kies to upgrade her firmware to 4.3 and still be able to use Straight Talk as long I put back in her APN settings that she is using right now? "
thanks
Yes, that should be fine, but if it is rooted or modified it may fail to initiate the flash. In this case go to the firmware thread linked in my sig and flash the firmware via Odin. (Let me know if you have any questions about that)
Off topic but I have to ask if you'd be willing to try something on that spare AT&T device. But if you are at all skeptical or uncomfortable doing this, it is perfectly fine to decline....
In case you dont know, AT&T once again seems to have decided to withhold the stock firmware for the new 4.4.2 update. This causes tons of problems for users here on xda! I have built the stock firmware for the I747 myself, but have no way to test it, so ive been sitting on it for nearly 2 weeks! If this is something you'd be willing to consider, please let me know. (I will tell you everything I know about the possible negatives before you do).
Like I said, if you're not comfortable doing that, its perfectly fine. Im just trying to find someone with a spare S3 willing to take the risk of testing it. (Risk is minimal imo, or I wouldn't even bother asking). But please do not be afraid to tell me no! (And you dont have to explain yourself if you do!)
Sorry for going OT, I just have to take the opportunity to ask when I can! I just dont want to ask someone to test on their primary device because there's always a chance things can go wrong.
DocHoliday77 said:
Yes, that should be fine, but if it is rooted or modified it may fail to initiate the flash. In this case go to the firmware thread linked in my sig and flash the firmware via Odin. (Let me know if you have any questions about that)
Off topic but I have to ask if you'd be willing to try something on that spare AT&T device. But if you are at all skeptical or uncomfortable doing this, it is perfectly fine to decline....
In case you dont know, AT&T once again seems to have decided to withhold the stock firmware for the new 4.4.2 update. This causes tons of problems for users here on xda! I have built the stock firmware for the I747 myself, but have no way to test it, so ive been sitting on it for nearly 2 weeks! If this is something you'd be willing to consider, please let me know. (I will tell you everything I know about the possible negatives before you do).
Like I said, if you're not comfortable doing that, its perfectly fine. Im just trying to find someone with a spare S3 willing to take the risk of testing it. (Risk is minimal imo, or I wouldn't even bother asking). But please do not be afraid to tell me no! (And you dont have to explain yourself if you do!)
Sorry for going OT, I just have to take the opportunity to ask when I can! I just dont want to ask someone to test on their primary device because there's always a chance things can go wrong.
Click to expand...
Click to collapse
Yes i am willing to help you out. I just need to run out to BJ's and get some food for my kids and the Cat food I should be back in about an hr or so, once I am back , i am willing to help you out with this. I will do a simple backup of the phone but you will have to walk me through the steps since I haven't rooted a phone nor done any flashing, if you don't mind doing something like a Google Plus hangout, i am more than willing to help you out with this project.Is that ok with you?
Yup that'll be fine. Thank you! Ill pm you in the meantime to let you know about any potential negatives before actually committing to flashing it.
Just so you know now though, worst case scenario is a hard brick. And we have not been able to get our debrick method to work on kk yet.
I am confident that will not be the result, but there is always that chance when flashing anything, tested or not. Just be aware that currently we cannot recover a hard brick updated with kk. You can pay for a jtag service, but if it did come to that I wouldnt be able to help on the cost more than just a few bucks.
Like I said, that is the worst that can happen, but if I thought there was a good chance of it, I wouldnt bother asking to begin with.
Thanks again and check your PM's when you get back.
DocHoliday77 said:
Yup that'll be fine. Thank you! Ill pm you in the meantime to let you know about any potential negatives before actually committing to flashing it.
Just so you know now though, worst case scenario is a hard brick. And we have not been able to get our debrick method to work on kk yet.
I am confident that will not be the result, but there is always that chance when flashing anything, tested or not. Just be aware that currently we cannot recover a hard brick updated with kk. You can pay for a jtag service, but if it did come to that I wouldnt be able to help on the cost more than just a few bucks.
Like I said, that is the worst that can happen, but if I thought there was a good chance of it, I wouldnt bother asking to begin with.
Thanks again and check your PM's when you get back.
Click to expand...
Click to collapse
Right now, the way I am looking at it, is I have another phone S3 running 4.2.1 and those S4's, People like you have committed their time over and over again, it's the least I can do. And if it does get hard bricked, when there is a time and it is fixed, you could just help me or by than I will know exactly what I am doing, and can do it myself. But I am willing to help you out and take the chance. I will PM you when I get back bud.
When I get back I will finish talking to you and than we can start.
1) Is this phone likely to get root soon after release? Just based on LG history or whatever is known about the phone so far.
2) Does being on Verizon usually mean waiting longer or not getting root access at all? If Verizon-rooted phones are rare, please let me know some good alternatives.
Thanks all for putting up with me.
89titanium said:
1) Is this phone likely to get root soon after release? Just based on LG history or whatever is known about the phone so far.
2) Does being on Verizon usually mean waiting longer or not getting root access at all? If Verizon-rooted phones are rare, please let me know some good alternatives.
Thanks all for putting up with me.
Click to expand...
Click to collapse
Im sure there will be root. but it will take a while, and i dont see anybody posting on the dev section talking about root. so probobly in afew months, once they read the source of the OS, and figure out how to make root.
Im from big red, and they always lock there bootloaders. so thats alittle more work and codeing which turns into abit more waiting time if you want custom roms. but G4 seems like a pretty popular phone, so im sure root will come eventually
89titanium said:
1) Is this phone likely to get root soon after release? Just based on LG history or whatever is known about the phone so far.
2) Does being on Verizon usually mean waiting longer or not getting root access at all? If Verizon-rooted phones are rare, please let me know some good alternatives.
Thanks all for putting up with me.
Click to expand...
Click to collapse
This phone hasn't been fully released yet. It will def get root. I'd give it a month or so.
I have Verizon and the G3 was unlocked within 3 months. I'm hoping since this is Qualcomm's first hexa-core, there'll be some exploits to gain root/unlock BL faster. Take it from a Sammy guy, WAIT THE FEW MONTHS. Samsung hasn't seen an unlocked BL for Verizon in 2 years.
Sent from my S5 using your mom
yep, probably gonna pull the trigger on the att g4 with their nasty corporate locked BL crap. I'd normally be concerned about root, but in this case I'm not terribly worried, because this phone will have SO much attention in the dev community. now, getting the att BL unlocked to run twrp... that's another story and could be a very long time if at all (just for the att version).
I bought a used HTC One M9, and everything seems to work fine until I try to update it (Its on Android 5.0.2) it looks normal but then goes to this screen (See attached photo). I guess the phone has S-off? I'm not really very good with any of this stuff, if anyone can help me get back to stock so I can get OTA's that'd be great. I tried doing all the research I could but have gotten nowhere. The phone is an unlocked model, I was told it's a developers edition but IDK how to tell the difference. There is no carrier branding so I'm assuming he didn't lie, and that the phone actually is unlocked. If anyone can help it'd be very greatly appreciated, I planned to use this phone as my main phone but I cant use it on almost 3 year old software.
Apollonit said:
I bought a used HTC One M9, and everything seems to work fine until I try to update it (Its on Android 5.0.2) it looks normal but then goes to this screen (See attached photo). I guess the phone has S-off? I'm not really very good with any of this stuff, if anyone can help me get back to stock so I can get OTA's that'd be great. I tried doing all the research I could but have gotten nowhere. The phone is an unlocked model, I was told it's a developers edition but IDK how to tell the difference. There is no carrier branding so I'm assuming he didn't lie, and that the phone actually is unlocked. If anyone can help it'd be very greatly appreciated, I planned to use this phone as my main phone but I cant use it on almost 3 year old software.
Click to expand...
Click to collapse
I strongly suggest you to read this thread. There's more you can find in helping you're situation
Greetings
Marko Indaco said:
I strongly suggest you to read this thread. There's more you can find in helping you're situation
Greetings
Click to expand...
Click to collapse
MAN THAT WAS ALOT OF GUESSWORK AND CLINKING LINKS BUT I THINK I DID IT HAHA! Thanks so much man it wasn't actually that hard I just needed to get pointed in the right direction, I'll let you know if it all goes through well. Thanks again.
Marko Indaco said:
I strongly suggest you to read this thread. There's more you can find in helping you're situation
Greetings
Click to expand...
Click to collapse
Damn nevermind, its still screwed up. Gonna try some new stuff
Apollonit said:
Damn nevermind, its still screwed up. Gonna try some new stuff
Click to expand...
Click to collapse
Not to be polemic but, writing: "its still screwed up" don't help at all. Too much links and redirects? Well, write it about. Suggest some own ideas, if you have one.
Maybe you lost THIS.
Greetings