Database Develop

[Q] How to root?

Hey so guys I want to root my moto but I don't want to wipe my storage. Is there a way I could root? Without losing data and apps?
Thanks for your reply?.

Mohdsultan said:
Hey so guys I want to root my moto but I don't want to wipe my storage. Is there a way I could root? Without losing data and apps?
Thanks for your reply?.
Click to expand...
Click to collapse
Follow any tutorial rooting will not wipe your storage.

gunde2014 said:
Follow any tutorial rooting will not wipe your storage.
Click to expand...
Click to collapse
Can you post a link to one??

gunde2014 said:
Follow any tutorial rooting will not wipe your storage.
Click to expand...
Click to collapse
Dont you need to unlock the bootloader first?

xbs said:
Dont you need to unlock the bootloader first?
Click to expand...
Click to collapse
You only need to unlock the bootloader if you and install custom recovery and flash ROMs.
---------- Post added at 08:55 PM ---------- Previous post was at 08:54 PM ----------
Mohdsultan said:
Can you post a link to one??
Click to expand...
Click to collapse
What phone and carrier are you using?

gunde2014 said:
You only need to unlock the bootloader if you and install custom recovery and flash ROMs.
---------- Post added at 08:55 PM ---------- Previous post was at 08:54 PM ----------
What phone and carrier are you using?
Click to expand...
Click to collapse
I am using dual Sim version XT1068 and bro if you unlock bootloader then your storage will be gone.

Mohdsultan said:
I am using dual Sim version XT1068 and bro if you unlock bootloader then your storage will be gone.
Click to expand...
Click to collapse
That´s true and there is no other way to root the Moto G than unlocking bootloader,boot in or flash custom recovery and flash superSU from there.
Short form:Rooting means loss of internal storage.

Bootloader

Mohdsultan said:
I am using dual Sim version XT1068 and bro if you unlock bootloader then your storage will be gone.
Click to expand...
Click to collapse
With your particular model you'll have to unlock the bootloader. Then since your bootloader is unlocked you can install custom recovery. And most custom Recovery's allow you to root from the recovery somewhere in advance options.

gunde2014 said:
With your particular model you'll have to unlock the bootloader.
Click to expand...
Click to collapse
Yeah ??? damn it now need to back up everything.

1st Unlock Your Bootloader From Here : https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
This will wipe your internal storage and will do a factory reset of the phone after unlocking. This will VOID the WARRANTY !
Root and Install Custom Recovery From Here : http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818
After that you can flash custom ROMs and mods for your XT1068

[Q] Locked bootloader, bootloop... brick?

Hi all! Im not a motorola user of any sorts, but a friend of mine, who's not a great english speaker and doesn't have an xda account, bricked, or at least so it seems, his Moto X 2014 (xt1097).
He tells me that Motorola and Google now include a checkbox in the "developer options" which, without being checked, will not allow the user to unlock the bootloader via the almighty fastboot oem unlock command.
That being said, the problem is now pretty clear: he cant access that dev option setting, because of the initial bootloop, thus being stuck with an unlock-able bootloader...
I know that it's a not good practice to go all gung ho flashing roms, without a unlocked bootloader and TWRP installed; at least I wouldn't sleep easy without them.
So... what's next? Is there a RSD method to flash the phone back to complete stock? Is there a way to check that checkbox via ADB? Any input will be much appreciated.

ad astra said:
He tells me that Motorola and Google now include a checkbox in the "developer options" which, without being checked, will not allow the user to unlock the bootloader via the almighty fastboot oem unlock command.
Click to expand...
Click to collapse
This is only true if he upgraded to 5.1, which it sounds like he did.
ad astra said:
That being said, the problem is now pretty clear: he cant access that dev option setting, because of the initial bootloop, thus being stuck with an unlock-able bootloader.
Click to expand...
Click to collapse
First what did he do to get into the bootloop? Was he part of the 5.1 soak test and then he tried to flash back to 5.0 to take the OTA?
He needs to try to get into bootloader mode. When the screen powers on, he needs to press and hold the power button until the screen turns off. Then immediately press and hold the vol down button, then after 2 seconds or so, w/o releasing the volume down, press and hold the power button. Keep pressing both power and vol down and hold them for about 4 seconds then release them both. That should get him into bootloader mode.
ad astra said:
I know that it's a not good practice to go all gung ho flashing roms, without a unlocked bootloader and TWRP installed; at least I wouldn't sleep easy without them.
Click to expand...
Click to collapse
You in fact cannot flash a ROM with a locked bootloader.
ad astra said:
So... what's next? Is there a RSD method to flash the phone back to complete stock? Is there a way to check that checkbox via ADB? Any input will be much appreciated.
Click to expand...
Click to collapse
First, get him into bootloader mode. Then you need to tell us what version of the bootloader is he on? Is it 60.14 or 60.11? And is this the Brazil XT1097?

JulesJam said:
This is only true if he upgraded to 5.1, which it sounds like he did.
Click to expand...
Click to collapse
Yep, that's exactly the case.
JulesJam said:
First what did he do to get into the bootloop? Was he part of the 5.1 soak test and then he tried to flash back to 5.0 to take the OTA?
Click to expand...
Click to collapse
If i'm not mistaken it was the other way around. He tried to update to 5.1 (I believe that the zip was form a different vendor).
JulesJam said:
He needs to try to get into bootloader mode. When the screen powers on, he needs to press and hold the power button until the screen turns off. Then immediately press and hold the vol down button, then after 2 seconds or so, w/o releasing the volume down, press and hold the power button. Keep pressing both power and vol down and hold them for about 4 seconds then release them both. That should get him into bootloader mode.
Click to expand...
Click to collapse
Already tried. The bootloader is locked. Tried to unlock (with fastboot), error appears which points to the checkbox in developer tools not being set to true.
JulesJam said:
You in fact cannot flash a ROM with a locked bootloader.
Click to expand...
Click to collapse
I understand what you mean, I meant that you can flash updates from sdcard with stock recovery.
JulesJam said:
First, get him into bootloader mode. Then you need to tell us what version of the bootloader is he on? Is it 60.14 or 60.11? And is this the Brazil XT1097?
Click to expand...
Click to collapse
Btw, he ended up sending the phone back to his carrier, for RMA, and got a new one. So.. we didn't check that. What's the difference between both? Now he managed to flash (with unlocked bootloader) the 5.1 rom and his bootloader version shows 60.16.
On the other hand, the phone's argentinian made. The flashing process which resulted in brick was as follows: 1) updated the stock 4.x.x movistar argentina rom with a brazilian 4.4.4 rom over stock recovery (he tells me that, as both roms are latinamerican, recovery update of those roms is possible). Then he seems to have updated to 5.1 soak. And then, and I dont reaaaly understand why.... he flashed another 5.1 soak that should have been only used for upgrading directly from 5.0.
The point is, he got locked out of any possible recovery method by being unable to unlock his bootlader (which we could access but was obviously locked for flashing).
Anyway, I think this thread will be of general interest so I'll continue to provide info on the case.

ad astra said:
Already tried. The bootloader is locked. Tried to unlock (with fastboot), error appears which points to the checkbox in developer tools not being set to true.
Click to expand...
Click to collapse
That wasn't the point of getting into bootloader mode. The point was to flash back to stock system. That would stop the bootloop then he could boot into system, go into settings and enable unlocking.
---------- Post added at 12:28 AM ---------- Previous post was at 12:27 AM ----------
ad astra said:
Btw, he ended up sending the phone back to his carrier, for RMA, and got a new one.
Click to expand...
Click to collapse
That is fine if that was an option, but those CLNR devices from the carriers are crap. All he had to do when he was in bootloader mode was flash back to stock.
---------- Post added at 12:29 AM ---------- Previous post was at 12:28 AM ----------
ad astra said:
The point is, he got locked out of any possible recovery method by being unable to unlock his bootlader (which we could access but was obviously locked for flashing).
Click to expand...
Click to collapse
No he did not. If you can get into bootloader mode then you can flash system back to stock, then you can boot and enable the OEM unlocking.
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
ad astra said:
the 5.1 rom and his bootloader version shows 60.16.
Click to expand...
Click to collapse
OK so this is yet another 5.1 bootloader version. The only one I have seen is 60.14.

JulesJam said:
That wasn't the point of getting into bootloader mode. The point was to flash back to stock system. That would stop the bootloop then he could boot into system, go into settings and enable unlocking.
---------- Post added at 12:28 AM ---------- Previous post was at 12:27 AM ----------
That is fine if that was an option, but those CLNR devices from the carriers are crap. All he had to do when he was in bootloader mode was flash back to stock.
---------- Post added at 12:29 AM ---------- Previous post was at 12:28 AM ----------
No he did not. If you can get into bootloader mode then you can flash system back to stock, then you can boot and enable the OEM unlocking.
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
OK so this is yet another 5.1 bootloader version. The only one I have seen is 60.14.
Click to expand...
Click to collapse
But how? His bootloader was locked, and we even tried to use recovery to flash back a stock image which returned an error. We tried this using adb sideload and it didn't work. We even edited the .xml file and tried the nokia flashing tool, which also resulted in a failed attempt.
Maybe im missing something... but I only know of 3 methods of flashing via bootloader:
1) fastboot command.
2) adb sideload.
3) vendor flash tool (like Odin, and nokias RDS or something like that).

ad astra said:
The flashing process which resulted in brick was as follows: 1) updated the stock 4.x.x movistar argentina rom with a brazilian 4.4.4 rom over stock recovery (he tells me that, as both roms are latinamerican, recovery update of those roms is possible). Then he seems to have updated to 5.1 soak. And then, and I dont reaaaly understand why.... he flashed another 5.1 soak that should have been only used for upgrading directly from 5.0. .
Click to expand...
Click to collapse
Thanks, so he tried to take a different model's 5.1 OTA when already on 5.1.
---------- Post added at 12:36 AM ---------- Previous post was at 12:33 AM ----------
ad astra said:
But how?
Click to expand...
Click to collapse
mfastboot flash system system.img
You need the system.img file of course for your model. This is why I encourage everyone to use Motorola Device Manager to upgrade - it leaves a copy of the image files on your computer.
---------- Post added at 12:37 AM ---------- Previous post was at 12:36 AM ----------
ad astra said:
But how? His bootloader was locked,
Click to expand...
Click to collapse
You don't need an unlocked bootloader to flash a signed image. Unlocking your bootloader is only needed to flash unsigned images and to disable write protection.
---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------
ad astra said:
we even tried to use recovery to flash back a stock image which returned an error. We tried this using adb sideload and it didn't work.
Click to expand...
Click to collapse
You don't do it through recovery - you do it through bootloader mode.

JulesJam said:
Thanks, so he tried to take a different model's 5.1 OTA when already on 5.1.
---------- Post added at 12:36 AM ---------- Previous post was at 12:33 AM ----------
mfastboot flash system system.img
You need the system.img file of course for your model. This is why I encourage everyone to use Motorola Device Manager to upgrade - it leaves a copy of the image files on your computer.
---------- Post added at 12:37 AM ---------- Previous post was at 12:36 AM ----------
You don't need an unlocked bootloader to flash a signed image. Unlocking your bootloader is only needed to flash unsigned images and to disable write protection.
---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------
You don't do it through recovery - you do it through bootloader mode.
Click to expand...
Click to collapse
Nice. I was about to test that :/ But i desisted because i thought it was the same as the normal fastboot... Damn, why didn't I try that when I stumbled upon that yesterday......
Thanks for the info! And also thanks for the tip on the motorola deivce manager upgrade thing. The LG suite does the same thing and so I keep my stock image safely stored.

ad astra said:
Maybe im missing something... but I only know of 3 methods of flashing via bootloader:
1) fastboot command.
Click to expand...
Click to collapse
Yes, this works. You don't need an unlocked bootloader to do it, but you do need mfastboot if the image file you have is a single image file. If you have the system already broken down into chunks, you can use regular fastboot.
ad astra said:
3) vendor flash tool (like Odin, and nokias RDS or something like that).
Click to expand...
Click to collapse
The one you want for a Moto X is the Motorola tool - RSDLite. RSDLite has mfastboot as a part of it.
You needed mfastboot to flash a single file system.img. Regular fastboot from the SDK won't work. mfastboot is motorola's version of fastboot.
Regular fastboot can only flash chunks of system. I think they have to be 256MB or less in size.
---------- Post added at 12:44 AM ---------- Previous post was at 12:41 AM ----------
ad astra said:
Nice. I was about to test that :/ But i desisted because i thought it was the same as the normal fastboot... Damn, why didn't I try that when I stumbled upon that yesterday......
Click to expand...
Click to collapse
I was trying to help you, but you didn't post back.

JulesJam said:
I was trying to help you, but you didn't post back.
Click to expand...
Click to collapse
Dont get me wrong. You did help me (thats why i left u a thanks) :good: My friend just went and did his thing on his own. I probably live in a different time zone, and my work doesn't allow me to be online the whole day. It was really late when I posted, I wasn't expecting a reply on the fly so I went to sleep. I continued this thread just because of curiosity.
On a side note, my friend checked his phone and, it seem'd alright, closed box and all. He worked a time at Motorola so he knows what was getting into. It seems the whole mess happened because of a forum post which indicated that he was flashing a soak test rom, when it was actually a final release (or something like that). This last, ended up messing up his system.

The only way to recover the original phone would have been to flash 5.1 or newer firmware to it. Had the bootloader been unlocked he could have just flashed 5.0.x without an issue(skipping motoboot and gpt).
Nobody should ever mess around with soak files unless they have an unlocked bootloader.

Steve-x said:
The only way to recover the original phone would have been to flash 5.1 or newer firmware to it. Had the bootloader been unlocked he could have just flashed 5.0.x without an issue(skipping motoboot and gpt).
Nobody should ever mess around with soak files unless they have an unlocked bootloader.
Click to expand...
Click to collapse
Agreed. Very poor judgement on behalf of my friend. Lesson learnt I guess, now he's bootloader is unlocked and he managed to flash 5.1 as previously intended.
It seems that the guy who posted the soak mistakenly posted the wrong file and caused a lot of problems for a lot of people... but, nevertheless u cant trust everything to go right... so that's my friends own fault for not unlocking, backing up and investigating enough.

i had the same problem.... any solution for bootloop Moto X 2014 whith Locked Bootloader?

Lussardi said:
i had the same problem.... any solution for bootloop Moto X 2014 whith Locked Bootloader?
Click to expand...
Click to collapse
Have you tried erasing cache and data? If that does not work you could flash your stock firmware.
Could you tell us what you did to get into your bootloop. More info helps us know how to fix your problem.
Sent from my XT1095 using Tapatalk

AGISCI said:
Have you tried erasing cache and data? If that does not work you could flash your stock firmware.
Could you tell us what you did to get into your bootloop. More info helps us know how to fix your problem.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I tried all options, fastboot erase userdata, fastboot erase cache, Flash lollipop 5.1 via RSD nothing seems works

Lussardi said:
I tried all options, fastboot erase userdata, fastboot erase cache, Flash lollipop 5.1 via RSD nothing seems works
Click to expand...
Click to collapse
You still have not told us what you did that caused the bootloop.
Sent from my XT1095 using Tapatalk

AGISCI said:
You still have not told us what you did that caused the bootloop.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I do not know ... a customer came in for repair, so do not know the reason why he stayed so.

[Q]Stuff to do before unlocking bootloader/root

So I just got My OnePlus 3T and like most, would like it rooted! I have had experience with rooting and unlocking bootloader, but since My earlier devices were by Sony, there is a lot of difference. In Sony devices, there was no need to unlock bootloader to root, but it seems that for rooting 3T, I need to unlock bootloader. Even that doesn't seem difficult since there is this great guide with a toolkit. But My concern is that do I need to backup any partition before I unlock bootloader? Like in Sony we had a TA partition, which could be backed up before unlocking bootloader and would get wiped after unlocking bootloader. This is just for keeping it as backup and restore it to device if I decide to lock bootloader again. Also, will I loose anything if I unlock bootloader? Such as anything specific to OEM or camera functionality?

Nope. On OP devices there's no permanent penalty for unlocking. If you ever want to go back, you can re-lock the bootloader. But: unlocking and locking will wipe your phone. So you can't carry over root to a locked bootloader.

dreinulldrei said:
Nope. On OP devices there's no permanent penalty for unlocking. If you ever want to go back, you can re-lock the bootloader. But: unlocking and locking will wipe your phone. So you can't carry over root to a locked bootloader.
Click to expand...
Click to collapse
Okay, that helps! So to return back to locked bootloader everything would need to be like stock(no root, custom recovery etc.)
I had read somewhere about EFS backup and that it is related to IMEI number of the phone. This need to be done before or after the rooting process?
Also, would I need to disable encryption (as it is seen enabled in settings) and remove the fingerprint lock option before unlocking bootloader?
And just to be clear, I'm going to do following steps in the sequence to flash TWRP and root, Please let Me know if it is correct:
1. Unlock bootloader
2. Flash TWRP.
3. Flash SuperUser
all this with the help of ToolKit of OnePlus 3T. I don't need to take backup as the phone is new.
Also, I will be flashing the phh SuperUser for support with Magisk as mentioned here.

Hey, do you guys know if you can get official OTAs if you have TWRP installed?

Former Z2 user here @Mirhawk
I did the advice backup as a precaution. Then did your 1,2,3 steps. May I ask, why Magisk? Is Android Pay currently working with stock ROM + Root + unlocked bootloader?
---------- Post added at 05:47 PM ---------- Previous post was at 05:45 PM ----------
Mirhawk said:
Okay, that helps! So to return back to locked bootloader everything would need to be like stock(no root, custom recovery etc.)
I had read somewhere about EFS backup and that it is related to IMEI number of the phone. This need to be done before or after the rooting process?
Also, would I need to disable encryption (as it is seen enabled in settings) and remove the fingerprint lock option before unlocking bootloader?
And just to be clear, I'm going to do following steps in the sequence to flash TWRP and root, Please let Me know if it is correct:
1. Unlock bootloader
2. Flash TWRP.
3. Flash SuperUser
all this with the help of ToolKit of OnePlus 3T. I don't need to take backup as the phone is new.
Also, I will be flashing the phh SuperUser for support with Magisk as mentioned here.
Click to expand...
Click to collapse
sajed98 said:
Hey, do you guys know if you can get official OTAs if you have TWRP installed?
Click to expand...
Click to collapse
AFAIK stock recovery is required. Otherwise install zip manually via downloads.oneplus.net

23Six said:
Former Z2 user here @Mirhawk
I did the advice backup as a precaution. Then did your 1,2,3 steps. May I ask, why Magisk? Is Android Pay currently working with stock ROM + Root + unlocked bootloader?
---------- Post added at 05:47 PM ---------- Previous post was at 05:45 PM ----------
AFAIK stock recovery is required. Otherwise install zip manually via downloads.oneplus.net
Click to expand...
Click to collapse
OK, thanks for your reply.

23Six said:
Former Z2 user here @Mirhawk
I did the advice backup as a precaution. Then did your 1,2,3 steps. May I ask, why Magisk? Is Android Pay currently working with stock ROM + Root + unlocked bootloader?
---------- Post added at 05:47 PM ---------- Previous post was at 05:45 PM ----------
AFAIK stock recovery is required. Otherwise install zip manually via downloads.oneplus.net
Click to expand...
Click to collapse
I'm not interested in Android Pay, as it doesn't work in My country, It is Pokemon Go I wanted, but I guess it doesn't work. Thanks for the infor though! It was a lot simple in Sony!

HELP: I've lost OEM Unlock

Need help badly:
I Lost OEM unlock option when I installed a custom rom. I have waited for 7 days and the option wouldnt appear in the settings. I believe if I reboot this, Id be stuck in binary blah blah and Id be back in stock rom again and be jailed for 7 days.
Im currently rooted. Ive read an article about DrKetan OEM patch. Can I be able to install that without using TWRP? Like the app Flashify or Flashfire?
Any insights please?
Thanks

I wish to restore my TWRP backup but I cant get to TWRP as I believe id be stuck in " only official binary blah blah"

I first unlocked the boot loader but didn't worked than I was unable to find the one unlock option again in developer mode even after reflashing the firmware.
In the Odin mode it is written oem lock off
Can somebody guide me how to show that option again

sangreal327 said:
Need help badly:
I Lost OEM unlock option when I installed a custom rom. I have waited for 7 days and the option wouldnt appear in the settings. I believe if I reboot this, Id be stuck in binary blah blah and Id be back in stock rom again and be jailed for 7 days.
Im currently rooted. Ive read an article about DrKetan OEM patch. Can I be able to install that without using TWRP? Like the app Flashify or Flashfire?
Any insights please?
Thanks
Click to expand...
Click to collapse
Some roms hide the OEM unlock option to avoid accidentally switching it and then locking you out ie only official binaries. Search in the thread of the rom you are using to see if that is the case.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
Malikzeeshanarif said:
I first unlocked the boot loader but didn't worked than I was unable to find the one unlock option again in developer mode even after reflashing the firmware.
In the Odin mode it is written oem lock off
Can somebody guide me how to show that option again
Click to expand...
Click to collapse
Try using this great guide
https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/

stonedpsycho said:
Some roms hide the OEM unlock option to avoid accidentally switching it and then locking you out ie only official binaries. Search in the thread of the rom you are using to see if that is the case.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
Try using this great guide
https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
Click to expand...
Click to collapse
Does installing a new firmware Will replace the one unlock or not

Temp P20 BL Unlock, What can i do with it?

I followed this guide
HTML:
https://forum.xda-developers.com/showpost.php?p=79383551&postcount=18
It actually does work after bricking the device i was able to restore it by flashing the internals of the update.app. Im able to flash ANYTHING which you can with an unlocked bootloader, after you reset you lose the temp unlock obviously. Im wondering what can i actually do with being able to do this?, Because it relocks after a reboot is it useless? I have tried to root but i imagine the recovery_ramdisk file restores itself to its original state after reboot?
Any help or tips would be nice, thank you!.

frankieuk said:
I followed this guide https://forum.xda-developers.com/showpost.php?p=79383551&postcount=18
It actually does work after bricking the device i was able to restore it by flashing the internals of the update.app. Im able to flash ANYTHING which you can with an unlocked bootloader, after you reset you lose the temp unlock obviously. Im wondering what can i actually do with being able to do this?, Because it relocks after a reboot is it useless? I have tried to root but i imagine the recovery_ramdisk file restores itself to its original state after reboot?
Any help or tips would be nice, thank you!.
Click to expand...
Click to collapse
No I'd say it's not useless. Will check it out..
If you can get TWRP can you flash anything? Custom ROM? Try AOSIP, can you flash magisk?
Try some things, what's possible?

Sadly nothing so far!, TWRP will install but won't show up after the reboot, maybe because the bootloader locks back?. I was able to unbrick the device and downgrade and upgrade etc, thats about it

There's another thread of a chap looking into cracking the bootloader, could your temp unlock help him in any way?
May be worth talking to him.
---------- Post added at 12:21 AM ---------- Previous post was at 12:20 AM ----------
Here's the thread mate
https://forum.xda-developers.com/huawei-p20-pro/help/brute-force-unlock-unlock-codes-t3826968

dladz said:
There's another thread of a chap looking into cracking the bootloader, could your temp unlock help him in any way?
May be worth talking to him.
---------- Post added at 12:21 AM ---------- Previous post was at 12:20 AM ----------
Here's the thread mate
https://forum.xda-developers.com/huawei-p20-pro/help/brute-force-unlock-unlock-codes-t3826968
Click to expand...
Click to collapse
Thanks a lot! i noticed it before gonna try help as much as i can!

frankieuk said:
Thanks a lot! i noticed it before gonna try help as much as i can!
Click to expand...
Click to collapse
Brute forcing the unlock code it's just a waste of time and that "temporary" unlock won't help that guy anyway.

Pretoriano80 said:
Brute forcing the unlock code it's just a waste of time and that "temporary" unlock won't help that guy anyway.
Click to expand...
Click to collapse
It's just a suggestion.