Related
I'm using AOSP 2.1, and I rooted as per the instructions in the topic (I got SetCPU and QuickBoot working just fine). I get this error message when ever I start it up:
Busybox works but the "su" command does not elevate to root: "whoami" reports "whoami: unknown uid 10051" instead of uid 0. I think your "Superuser Whitelist" system app does not work. Please check with your ROM provider.
Click to expand...
Click to collapse
Checking in Better Terminal Emulator, I also get the uid of 10051 when I use whoami. The dev suggested that it was a "Superuser Whitelist" problem, but I have no idea what this is. Could anyone help me out?
TheBiles said:
I'm using AOSP 2.1, and I rooted as per the instructions in the topic (I got SetCPU and QuickBoot working just fine). I get this error message when ever I start it up:
Checking in Better Terminal Emulator, I also get the uid of 10051 when I use whoami. The dev suggested that it was a "Superuser Whitelist" problem, but I have no idea what this is. Could anyone help me out?
Click to expand...
Click to collapse
The Superuser Whitelist is superuser.apk, they're saying it's a problem with that app.
No, though i have heard of it.
Just for safety's sake search this forum on whitelist ( has a bad affect on the cdma hero) , before going to market. Also check superuser.apk, it could be your answer. TB is probably using the uid as a semaphore so as to be responsive to SU permissions programs. Busybox does not have a setuid, so you can't #setuid 0.
http://forums.macosxhints.com/archive/index.php/t-3359.html
Edit: I see someone ( with a similar name ) has already asked the developer.
http://androidforums.com/android-applications/42636-titanium-backup-problems-droid.html
Ask the "superuser.apk" developer.
This might help
Are you using Darchstar's ROM? There is a known issue with it not rooting, and setting up the superuser whitelist. Take a look at these instructions and it might fix your issue:
http://forum.xda-developers.com/showpost.php?p=5741316&postcount=1705
willy900wonka said:
No, though i have heard of it.
Just for safety's sake search this forum on whitelist ( has a bad affect on the cdma hero) , before going to market. Also check superuser.apk, it could be your answer. TB is probably using the uid as a semaphore so as to be responsive to SU permissions programs. Busybox does not have a setuid, so you can't #setuid 0.
http://forums.macosxhints.com/archive/index.php/t-3359.html
Edit: I see someone ( with a similar name ) has already asked the developer.
http://androidforums.com/android-applications/42636-titanium-backup-problems-droid.html
Ask the "superuser.apk" developer.
Click to expand...
Click to collapse
Yeah, that was me. He doesn't know the ins and outs of rooting.
josue85 said:
Are you using Darchstar's ROM? There is a known issue with it not rooting, and setting up the superuser whitelist. Take a look at these instructions and it might fix your issue:
http://forum.xda-developers.com/showpost.php?p=5741316&postcount=1705
Click to expand...
Click to collapse
I am. I will try that out and see if it works.
Ok, when trying to fix the superuser whitelist as described, I get the error:
Code:
Unable to chmod su: No such file or directory
after the command
Code:
chmod 06755 su
I rooted following the instructions in the "How to root topic." Any ideas?
TheBiles said:
Ok, when trying to fix the superuser whitelist as described, I get the error:
Code:
Unable to chmod su: No such file or directory
after the command
Code:
chmod 06755 su
I rooted following the instructions in the "How to root topic." Any ideas?
Click to expand...
Click to collapse
did you get my pm?
darchstar said:
did you get my pm?
Click to expand...
Click to collapse
Yeah, performing a nandroid backup now. I have to root it again, right?
Oh, and should I wipe first?
EDIT: Everything works like a charm!
It also finally asks if I want to allow root access from apps.
ON a stock rom you would apply this update, by Mercado79, it gives you the whitelist and sets your uid to 0 upon activation.
The update is described here:
http://forum.xda-developers.com/showthread.php?t=593952&highlight=mercado79
download update zip here:
http://forum.xda-developers.com/attachment.php?attachmentid=252801&d=1259860872
I tested the process and it sets the uid to 0.
Okay I must the most unlucky man on earth:
I rooted my HTC stock ROM, installed Titanium & Busybox, but I get the same su error...
I tried to install the update from mercado79, but after reboot it freezes on htc logo during first boot...
I don't know what else I could possibly do to finally be able to backup all my data and apps :-(
all you need to do, is get the permission XML for from face camera device rom (used the one from VIVO), and push it system, via recovery.
adb reboot recovery; adb shell mount -a; adb push android.hardware.camera.front.xml /system/etc/permissions/; adb shell fix_permissions; adb reboot
done
....
PROFIT
PS: this is NOT a flashable zip. but anyone wants to make one, be my guest
thanks to Kali- for the tips
Pushed the xml to the permisions folder with no problems. Ran fix_permissions and rebooted, doesn't appear to have done anything. I can verify that the xml is in the correct folder but google + just doesnt want to do hangouts.
Nexus One running CM7
Any ideas?
EDIT: I was wrong, I thought I would be able to start a hangout but once I found an existing one I was able to join no problem. THANKS!
Qestion
Will it happen if you copy the "android.hardware.camera.front.xml" in folder "/ system / etc / permissions /" by Root Explorer, and then restart the phone?
jossna said:
Will it happen if you copy the "android.hardware.camera.front.xml" in folder "/ system / etc / permissions /" by Root Explorer, and then restart the phone?
Click to expand...
Click to collapse
Yes, you'll either need to manually change the permissions in root explorer to match all the other files in there, or run fix permissions as per the guide
Smtih said:
Yes, you'll either need to manually change the permissions in root explorer to match all the other files in there, or run fix permissions as per the guide
Click to expand...
Click to collapse
Thanks, I try it, but doesn't work
This is how I got mine to work
There were some permissions issues and my phone can't adb anymore for some reason (seems common with the Captivate), so I did the following from Terminal Emulator:
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock2
# chmod 777 /system
# cp /mnt/sdcard/Downloads/android.hardware.camera.front.xml /system/etc/permissions/.
# chmod 644 /system/etc/permissions/android.hardware.camera.front.xml
[Restart into recovery mode]
[Advanced]
[Fix Permissions]
And it worked! You just can't create your own Hangouts from the phone. You can join others though using your back-facing camera!
Thanks OP!
Jason Schoenbrun
jason schoenbrun gmail
-------------------
Why does xda developers require we create user names? If there's anyone who knows this, please let me know as I'm curious.
I haven't created a non-email username since the days of AOL. Now I have to make a dumb-sounding faux name like "hotmama2385" all over again? I really wish I could use my e-mail address as my persona. If I can't, at least I'd like to know out of curiosity why the design decision was made to exclude that possibility. of course as a protection from spambots I'd want some of my e-mail address hidden behind a CAPTCHA.
I know some people are privacy focused and/or want to be able to troll anonymously. So why not allow a username which can take whatever form we chose - AOL-esque IDs or an e-mail address - as most login services allow?
As an aside, I have the same question for Twitter, which is the reason I haven't signed up for it. I pushed off signing up for XDA by a couple of years until I absolutely had to because of this, and rarely log in because I can't remember that stupid username. (I just started to a little more because of LastPass.)
Nice work... I'll try this one...
hello,
how to fix permission?
with a terminal
I'm not sure what command that is specifically from a terminal, but you can type adb reboot recovery and then fix permissions via menu option once in recovery.
yep, but the problem I haven t a recovery mode. I want to say no menu.
I have an HTC evo 4g with CM 7.2RC1.
I implemented this fix, and rebooted, but still, when trying to do a video call, it stays on "video initializing" and never seems to finish. I have the latest skype from market.
What to do?
just maybe
So I installed the sdk tools, and opened cmd, and then cd to where adb is. I then copy and pasted the entire string "adb reboot recovery; adb shell mount -a; adb push android.hardware.camera.front.xml /system/etc/permissions/; adb shell fix_permissions; adb reboot" and pasted that into cmd is that all I do. I tried dong just "adb reboot recover" and waiting till it entered recovery, but then I couldn't do anything. after I pasted the entire string, my phone rebooted, and took a sec then started back up normally it seemed. So I think I did it correctly.
Perfect!!! Thanks, works like a charm on my Nexus One
great on arc s for hangouts
It's working great on arc s to create hangouts, but it still does not enable video chat in google talk.
I really don't understand why front camera is a pre-requisite for it. I shall be able to see at least the other's video if he has a front cam, even if they don't see me. Any way to workaround this issue of googletalk? (either to trick it to use front cam or just to display an empty frame, but receive other end's video).
I tried the same to see if it would work for Talk on my Defy, but no success
Hi,
I posted a question in forum about how to connect my A500 tablet to an Ad-hoc networking but after I did some search in the forum I found some steps to solve the issue and it is starting from rooting the device and finalizing by modifying a file in the following path:
sdcard/system/bin/wpa_supplicant
The problem is I can't rename the file (wpa_supplicant) also I can't copy the modified (wpa_supplicant) to the system/bin folder and a message appearing told that this file is "read only" and can not be modified or edited. Note that I used Root Explorer and Root Browser to explore the systems folders.
Please any one can help??
You can't do this because your device is not rooted !
Use Root explorer don't give all super user privilege to your device
my device did not open what shall i do??
As the guy answered, you have to be rooted in order to do that.
Im not sure if you can root tablets, I have never had any interest in this direction because I dont have money to buy one.
But if you can you click on Root explorer, then click mount r/w , go to system/apps.
If it is mounting r/o you can delete system apps, I did that to my SGSII and my battery life lasts much longer.
You also have access to the files that created the applications, the ones you create in Eclipse.If you are a developer , you would know what I'm talkin about.
I dont know any other ways of doing this if you are not rooted and I'm almost sure its not possible, but good luck still.
Im not sure if you can root tablets,
Click to expand...
Click to collapse
You can root tablets, even the a500 as tough as it is to do so. I am running FlexReaper ROM on my Iconia a500 right now. It's flippin' awesome !
As far as editing the system files, the O.P. may need to actually mount the drive as r/w.
In ES File Explorer there is an option to actually mount the file system as 'writable'......(which will be rejected if the device is not rooted).
Do you see any similar option in the file explorer apps you are using ? If so, try to enable it. Just browsing 'up to root' is not enough......at least for ES.
I would use a root check type of app to verify you are up to a 'true root'.
As for custom ROM's the Iconia a500 tab requires flashing with a custom unlocked bootloader and custom recovery image like cwm, then installing/flashing the new custom or stock OTA ROM and any desired app/system packs if needed. The Iconia a500 is pretty tricky, but possible.
If you do go the way of custom ROM's, I HIGHLY recommend the FlexReaper RF-1_rv3 Custom ICS 4.0.3 ROM for users running the Acer Iconia a500 tablet.
Super smooth, and the only custom ROM that doesn't start with a funny snow screen when initially booting up. A couple other ROM's I tried would 'snow' like a bad hardware compatibility issue or something. Flexreaper seems like it is the perfect ROM for the a500, at least for me.
many thanks for all help;
I used an app to check if my A500 is root and it is called "Root Checker" and told me that my device is rooted and I have root access but when I used Root Explorer or Root Browser apps I found there is a button to switch from (r/o) to (r/w) but when i bushed it never changed to (r/w) by the way I used a software to root the A500 from my laptop this software called ( ICS ROOT 2) if this software is not rooting so can anyone tell me about the right way to root my A500 device which it is working on ICS system bcoz really I confused!!
ahmedalbidhany said:
many thanks for all help;
I used an app to check if my A500 is root and it is called "Root Checker" and told me that my device is rooted and I have root access but when I used Root Explorer or Root Browser apps I found there is a button to switch from (r/o) to (r/w) but when i bushed it never changed to (r/w) by the way I used a software to root the A500 from my laptop this software called ( ICS ROOT 2) if this software is not rooting so can anyone tell me about the right way to root my A500 device which it is working on ICS system bcoz really I confused!!
Click to expand...
Click to collapse
I actually used the same method so I am unsure as to what is going on here.
Will read back thru my research and see if I can figure something out. I am still new to this rooting/flashing thing, so I don't want to mislead you. I'd rather find my methods in tangible text online, rather than relying on my fuzzy memory.
I am not sure if this will help, but if you boot into recovery, check if there is an option to fix permissions. Run it then reboot normally.
Should be under the Advanced header.
IMOP,your Root explorer manybe havent get the right from super user.
Or,there is a problem with the root app.
My A500 rooted with the method instead of official Recovery.
@ Valkillmore : thank you for your support I'll try this method and comeback again and post the results
Root + SSH + remount
Here's how I do it.
1) Root your device.. lots of tips on this in the forums and the process depends on your specific phone model.
2) Install SU super user access.
3) SSHDroid - Install from market and allow root access (via SU)
4) Turn on SSHDroid and login to it via an SSH client from your computer (see putty for windows, Linux, Unix , and MAC should have it already).
> ssh [email protected] (for example)
5) remount the system drive (it is typically mounted as read-only
> mount -o remount,rw /system
Then you can go ahead and modify files under /system folder. Note: when you reboot, /system will be mounted normally (read-only).
i had the same issue
i had astro file manager, it doesnt have complete root access.
downlaod efs explorer
go to settings
allow "up to root" click allow when super user dialog box pops up
select "mount" right under "up to root"
then go to efs explorer main manu press the "up" tap
navigate to wherever you want. bne carefull with what you change.
i was changing the APN settings on my evo
As there are again and again discussions concerning the minfree settings in CM12 roms, I decided to open this thread. If a moderator thinks, this is the wrong place for this thread, just move it, to where it belongs.
Obviously, since the last builds of CM12, the settings for minfrees cause some trouble. After a clean install of any rom, the minfree settings in trickstermod and in fauxclock are completely empty. In fauxclock the settings for OOM (out of memory) Score as well. Some people entered them manually, but I'm afraid, this won't help.
To really solve this, you have to do the following steps: open your file explorer, go to sys/module/lowmemorykiller/parameters. There you will find 5 files. Two of them do not have correct permissions. The first one, called adj, is for the OOM Scores. The other one, called minfree, is, you won't guess it, for the minfrees. :fingers-crossed:
As you see, both of them have only write permissions, but no read permissions. So I guess, the system will ignore these settings completely. I checked this, using cool tool from play store, very nice tool to show for example the actual free ram in your status bar. And in deed, the ram went down to 25MB, after I had opened a handful apps, and then my phone stopped working. I only could do a reboot.
Now the solution, which is quite easy: change the permissions into rw-rw-rw (666), and maybe change the group under owners into root (I'm not sure, if this is necessary, but it does make no problems, so why not).
Et voilà - if you now open trickstermod or fauxclock again, you will see the preset parameters. As you can see also, the minfrees there are really high. In another thread, there have been suggested the following settings, which are a good standard:
trickstermod 48/60/72/84/96/120
fauxclock 12288/15360/18432/21504/24576/30720
Important: In fauxclock, the minfree settings are not made in MB. You have to enter the so called "pages" for minfrees, which I can't explain exactly, what this is. In general, if you want to change minfrees in fauxclock, just take the settings in MB, you want to, and multiply by 256. This will give you the correct values.
BTW I don't think, it's a good idea, to change the OOM Scores, as long as you do not know exactly, what you're doing.
So, hopefully I could help a bit and clear some things up. But the final question to the CM devs remains:
is this a bug or is this a feature?
With me, those files were already chmod 666, owner root. I use latest liquidsmooth rom. What i did, prior reading your post, was that i set minfree in trickster, from my presets, than immedatly switched to faux, parameters were there, pressed apply, switched set on boot and rebooted. After that minfree r sticking in faux and trickster. Guess that my actions leaded to what you have described. Anyway, your way is much more convinient - at least one app less to use
I don't get it... The directory you mentioned is empty on my one s as well as on my nexus 10 both with cm12.
However my settings stick since I use fauxclock.
One more thing I don't get is in fauxclock. It says "kilobyte" explicitly in the minfree settings although you said (and it stems to be) this strange pages value....
mariachi62 said:
I don't get it... The directory you mentioned is empty on my one s as well as on my nexus 10 both with cm12.
However my settings stick since I use fauxclock.
One more thing I don't get is in fauxclock. It says "kilobyte" explicitly in the minfree settings although you said (and it stems to be) this strange pages value....
Click to expand...
Click to collapse
You have to use your file manager with root permissions. Depending on which file manager you use, this can be done differently. The inbuilt CM12 file manager can be given root permissions in settings, in Root explorer for example you have to mount the directory as r/w.
An yes, you are right, fauxclock says, the settings are in kilobyte, but this is not correct. If you succeed to open the minfree file with your file manager, you will find there exactly the values, you have entered in fauxclock.
Damnit, you're right. Solid explorer doesn't show the content of the directory.... I use it a long time and always had the feeling solid explorer shows me all files...
Cm file manager works, thanks!
mariachi62 said:
Damnit, you're right. Solid explorer doesn't show the content of the directory.... I use it a long time and always had the feeling solid explorer shows me all files...
Cm file manager works, thanks!
Click to expand...
Click to collapse
It does work with solid explorer as well. The point is, there is no option, to set root permissions manually in solid explorer. So the trick is to create a situation, where solid explorer will ask for root access. For example: long press any folder in your system root, tap properties, tap change (attributes) and now press OK, without changing anything. You will be asked for root access.
Now everything should be fine!
got a problem.
parameter file is empty.
using unofficial cm12 on htc one s with icecode kernel
waver1967 said:
got a problem.
parameter file is empty.
using unofficial cm12 on htc one s with icecode kernel
Click to expand...
Click to collapse
problem solved
For solid explorer, just try to open /data and it will ask for root permissions. I do it every time I flash my phone.
Thanks a lot man! I wasn't aware of the skewed minfree files. Was setting them in Trickster and wondering why the apps keep shutting down on me when multitasking. Great work
oll0 said:
Thanks a lot man! I wasn't aware of the skewed minfree files. Was setting them in Trickster and wondering why the apps keep shutting down on me when multitasking. Great work
Click to expand...
Click to collapse
They will still close even so...just not so obvious
Rapier said:
They will still close even so...just not so obvious
Click to expand...
Click to collapse
Uh yes obviously. However they were actually closing the instant i opened another app. Couldnt even keep two apps open at the same time, that was pretty bad.
oll0 said:
Uh yes obviously. However they were actually closing the instant i opened another app. Couldnt even keep two apps open at the same time, that was pretty bad.
Click to expand...
Click to collapse
Yes, I know what you mean. Was the same for me. Having better minfree settings that stick after a reboot helped but didn't solved the issue completely. But at least now phone is usable. I put my hopes in that Google patch they'll release with 5.0.3
Sent from nowhere over the air...
deleted
Thanks for this thread, I changed the permission with "chmod 666" using adb shell, but after a reboot, the files were back to write-only mode, is it normal ? How do you make it permanent ?
Sylvain_44 said:
Thanks for this thread, I changed the permission with "chmod 666" using adb shell, but after a reboot, the files were back to write-only mode, is it normal ? How do you make it permanent ?
Click to expand...
Click to collapse
If it's reverting, I guess the only way would be through an script that runs at boot time. But it's strange, the permissions should stick once set...
Sylvain_44 said:
Thanks for this thread, I changed the permission with "chmod 666" using adb shell, but after a reboot, the files were back to write-only mode, is it normal ? How do you make it permanent ?
Click to expand...
Click to collapse
I used a file explorer with root permissions like root explorer or ES file explorer. My permissions are actually rw-rw-rw, both for adj and minfree file. I guess, this is 666? And they stick after a reboot. But honestly I am not quite sure, if I changed something else. IIRC, I might have changed the permissions for system/etc/init.d/90userinit to rwxr-xr-x. Maybe you want to check this, too.
Well, they don't stick because init.rc sets them to chmod 0220 on boot. That makes me wonder if maybe it was supposed to be like this? I wanted to change it but I don't want to screw anything up. There is a dedicated section for low memory killer in init.rc and only things there are chmod 0220 for those two files and chown for them - so basically the things that we are fixing in this thread. A bug or a feature?
jakubmi9 said:
Well, they don't stick because init.rc sets them to chmod 0220 on boot. That makes me wonder if maybe it was supposed to be like this? I wanted to change it but I don't want to screw anything up. There is a dedicated section for low memory killer in init.rc and only things there are chmod 0220 for those two files and chown for them - so basically the things that we are fixing in this thread. A bug or a feature?
Click to expand...
Click to collapse
Thanks for this hint! Indeed, this might be the other thing, that I had changed. In CM11 roms, the described permissions in init.rc are 664 - both for adj and minfree file. I am not quite sure, if this helps, but it's worth an attempt. You can change the permissions in init.rc to 644, reboot and see, if the permissions for adj and minfree are sticky now. I just did this ,and everything is fine -so you can try without risk, I guess. But I must say, I hadn't the problem before, that the permissions for adj and minfree were reset after reboot. Could be related to the changes in init.rc, but I am not sure.
A weird thing: I made a backup and tried anyway yesterday but after a reboot my init.rc restores itself to normal. I tried another time: Modified the values and saved. After reopening it's still there and it stays there but only until I reboot the phone. After reboot the permissions are not set correctly and init.rc restores itself to original state. Is there something I do not know about modifying init.rc? Because that is the first time I try to do something with it.
I have this really odd issue with my Z3 in that I cannot, on any network (wireless or carrier), resolve through DNS forum.xda-developers.com. I first noticed it because my XDA premium HD app couldn't connect to the forums at all. I did a bit of digging and managed to uncover that I can't connect to anything related to the forums. I CAN however connect to the main portal on www.xda-developers.com.
What I have tried:
1. Different wireless networks - no luck.
2. Other devices - all work fine on all the tried networks.
3. Carrier network (Rogers CA) - no luck, but again with other devices no problem
4. Ping and nslookup through Fing network tools - not able to resolve
5. Ping and nslookup through terminal emulator - not able to resolve
6. hosts file just has the standard localhost entry
7. Browse with Chrome just gives the standard error for unresolvable DNS
8. So far I have only seen this happen on the forums.xda-developers.com address.
I am running a Z3 (D6603) with a custom ROM per below.
Pre-rooted ROM from this thread: http://forum.xda-developers.com/z3/general/d6603-5-0-2-flashable-stock-23-1-0-690-t3056361
D6603_23.4.A.0.546_Customized_US_SuperSU_XZDR2.8.2 1 thanx to @julianbl
It's an odd one for sure, so if anyone has any creative ideas for me to test out please let me know. Thanks in advance.
use titanium backup or something similar to disable/uninstall "PrototypeProtection".
It's an app that sony uses to block certain sites when the bootloader is unlocked.
Julián
Go in Root Explorer,
Mount in R/W
Go to: system/etc/hosts
Try to add a xdadevs rule,
examp:
#207.244.72.9 http://forum.xda-developers.com
then reboot your device just normal.
i hope it works,
- bram
julianbl said:
use titanium backup or something similar to disable/uninstall "PrototypeProtection".
It's an app that sony uses to block certain sites when the bootloader is unlocked.
Julián
Click to expand...
Click to collapse
I should note that I have not unlocked my bootloader. I tried this and it has unfortunately had no effect. Open to other suggestions though, thanks for trying.
[EDIT] I may have spoken too soon. I tried connecting after disabling (freezing) that app and didn't have any luck. I rebooted the phone, and things are back online. I will do some further testing to get concrete and repeatable behavior documented. Thanks @julianbl
bramybram said:
If you see a rule wiht xda-developers.com in it
Click to expand...
Click to collapse
Thank for the suggestion. As noted in my OP though, the hosts file is empty except for the default localhost entry.
Swaziboy said:
Thank for the suggestion. As noted in my OP though, the hosts file is empty except for the default localhost entry.
Click to expand...
Click to collapse
Try to add a XDA Rule with a "#" before the rule instead?
bramybram said:
Go in Root Explorer,
Mount in R/W
Go to: system/etc/hosts
Try to add a xdadevs rule,
examp:
#207.244.72.9 http://forum.xda-developers.com
then reboot your device just normal.
i hope it works,
- bram
Click to expand...
Click to collapse
bramybram said:
Try to add a XDA Rule with a "#" before the rule instead?
Click to expand...
Click to collapse
Thanks for your desire to help - given what we've found out so far this isn't a HOSTS file issue. There is no entry in the hosts file, and as such any DNS resolution for the domain should leverage DNS servers based on DHCP settings.
In my mind, adding a rule in the HOSTS file to force resolution of the domain, might work but it's not a real fix as to why this is happening.
Refer to my previous note that the suggestion to block the "PrototypeProtection" app is what has resolved the issue so far.
Thanks again though @bramybram, appreciate your willingness to help.
Hey there, I had the same issue... It is quite frustrating, I guess it's some bug in the firmware you installed (since I used the same to flash my z3)... I resolved it by flashing another firmware, I suggest you the D6603_23.4.A.0.546_Customized_NCB_SuperSU_XDR2.8.2 1 (https://mega.co.nz/#!GJQVBL6K!x8bB2HS-TbpbZTb5IamrJB_xduDMHl9j6jQyAqrJpVQ) one, it worked for me