Database Users

root Tattoo with Mac

Hey Boys and Girls,
where i can find an manual to root the tattoo with a mac?
sorry, i have search for this, but i cant find information for this

I don't thing that there is a difference.
As soon as you have SDK installed and adb works, the commands are the same.

hi,
i'm also doing all the rooting process from mac, just put the directory contain 'adb' shell into your home/user places and executing it with 'terminal'..

Same here, using a Mac ever since and also using it for Android development. Due to the underlying Unix core of OS X you just have to follow the steps as described for Linux. If it's just adb commands it's the same on every platform anyway.
You might want to add a
Code:
export PATH=${PATH}:/Users/yourusername/android.sdk/tools
to your .bash_profile file in your home folder so you don't have to cd to the SDK tools folder everytime. Happy rooting!

Mod. edit: not dev related, moved to general

Okay thanks for yours answers but i'm a newbie.
the background story is, I want to edit the boot.mp3. Because the startsound is really annoying
So i have download SDK, open the terminal and switch to usb-debbugging mode on my tattoo.
And now? sorry, I'm still missing a few knowledge
thanks for your help

well just use the various adb commands in Terminal Just type in "adb", press enter and you'll get a list of all possible commands. Assuming you've added the path to your sdk tools folder to your bash profile. Otherwise just drag & drop the adb binary from the tools folder onto your Terminal window, et voila.
The most used commands are probably push and pull where you can, well, push stuff to your phone or pull it to your computer.
So if you want to modify the boot.mp3 you would pull the original from the phone to your computer, modify it and push it back, overwriting the original file. In Terminal speak: ;-)
adb pull /system/media/bootscreen/boot.mp3
adb push /path/to/boot.mp3 /system/media/bootscreen/boot.mp3
Please note depending on the ROM you're using the paths may be different. To browse the device via Terminal type in "adb shell" and make a simple "ls" to list the directories, "cd" to change directories etc.
Or if you just want to use another mp3:
adb push /path/to/whatever.mp3 /system/media/bootscreen/boot.mp3
Again, on the Mac you can just drag & drop files onto the Terminal to get their full Unix paths like to your custom mp3

Thanks a lot. i love it its really simple
and now i have load and edit the the boot.mp3. But i can't push it to my tattoo, because i can only read but not write
I have tried to root my phone with "adb root" but it is the message "adbd cannot run as root in production builds"

Terminal: "adb remount", then push again

damn the next bad message "remount failed: Operation not permitted"

You need to root your phone first.
http://forum.xda-developers.com/showthread.php?t=637927

Okay i have executed the instructions. But I've stop at this part:
You should get something like this:
Code:
# id
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
uid=0(root) is important.
Click to expand...
Click to collapse
Yes i've root but i'cant download the "su binary" because its doesnt exist.
But its absolute essential to need the "su binary" to only copy the boot.mp3 to my phone? Or there is an other way? What are the commands to push the boot.mp3 back to may tattoo then i'm in the root mode like >> "#".
okay hope you understand me

You need "su" to do root stuff... no other way.
Download the package from 1 click root thread and find "su" there...
http://forum.xda-developers.com/showthread.php?t=644279

now, i have install the su binary. Then i does this command
user:~ user$ /Users/user/android-sdk-mac_86/tools/adb shell
$ /data/local/bin/su
#
Click to expand...
Click to collapse
And now? Is there a comand to push the boot.mp3 back to the phone in this mode >> "#" ?
I have try to open an new terminal window and type
adb push /path/to/boot.mp3 /system/media/bootscreen/boot.mp3
Click to expand...
Click to collapse
but the answer is
failed to copy '/Users/android-sdk-mac_86/boot.mp3' to '/system/media/bootscreen/boot.mp3': Permission denied
Click to expand...
Click to collapse
and adb remount doesnt work to

You also need tattoo-hack.ko file and do insmod tattoo-hack.ko to make /system writable.
Or even better... flash custom amon_ra recovery image and then a custom rom with all this already included.
Mine for example http://forum.xda-developers.com/showthread.php?t=702401
It doesnt have boot sound enabled

Okay thank you very much.
now it was successful

cmd error flashing custom recovery

Someone please tell me what I'm doing wrong:
C:\Users\[my name]> cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools> adb devices
List of devices attached
HT9ADHG05719 device
C:\android-sdk-windows\tools> adb shell
# mount -o rw,remount /dev/block/mtdblock3 /system
mount -o rw,remount /dev/block/mtdblock3 /system
# adb push recovery-ra-eris.img /sdcard
adb push recovery-ra-eris.img /sdcard
adb: not found
#
I had to enter adb shell and hit enter before inputting the rest of that command just to get past that step. I tried doing the same with the next step and entering adb push separately but I got this:
# adb push
adb push
adb: not found
#
Does anyone know what I'm doing wrong or leaving out? I have the recovery and flash saved to the tools folder of my sdk.

you cant use adb push from inside a shell

That's what the "how to root" instructions are telling me to do.

joshw0000 said:
That's what the "how to root" instructions are telling me to do.
Click to expand...
Click to collapse
looks like you are "separating" steps...
3. Open up a command prompt and go to your tools directory, and execute these commands:
* adb shell mount -o rw,remount /dev/block/mtdblock3 /system
* adb push recovery.img /sdcard
* adb push flash_image /system/bin
* adb shell chmod 755 /system/bin/flash_image
* adb shell flash_image recovery /sdcard/recovery.img
(Taken from this thread: http://forum.xda-developers.com/showthread.php?t=647707)
your command is "adb shell" (which is going to shell... in which, anonomouse is correct, you cannot "adb" inside a shell). instead, type 1 command like this:
- adb shell mount -o rw,remount /dev/block/mtdblock3 /system
re-read the thread (link i posted) again... you're close
from your post... you'd have to exit shell... then get back to a DOS prompt... then do the "adb push" command

If I type the adb shell mount command together I get an error. That's why I broke them up.
So basically, once in the tools directory, I should be able to copy and paste the commands (which is what I was doing)? I would need to get back in front of my home pc and I'll tell you what error I'm getting. I believe it was "adb: not found".

If I type the adb shell mount command together I get an error. That's why I broke them up.
So basically, once in the tools directory, I should be able to copy and paste the commands (which is what I was doing)? I would need to get back in front of my home pc and I'll tell you what error I'm getting. I believe it was "adb: not found".

Linux or windows
Nevermind.... i reread your post. Sorry.

joshw0000 said:
If I type the adb shell mount command together I get an error. That's why I broke them up.
So basically, once in the tools directory, I should be able to copy and paste the commands (which is what I was doing)? I would need to get back in front of my home pc and I'll tell you what error I'm getting. I believe it was "adb: not found".
Click to expand...
Click to collapse
Make sure your sdcard is not mounted, it should be in charge only mode. Also make sure USB Debugging is on.

My phone was in charge mode and USB debugging was enabled, thanx.

joshw0000 said:
My phone was in charge mode and USB debugging was enabled, thanx.
Click to expand...
Click to collapse
You can use the application in this thread to help ease the process. They automated the commands through scripts to help in these situations. Plus, ECLIPS3 and Jamezelle do great work!
http://forum.xda-developers.com/showthread.php?t=661413

joshw0000 said:
If I type the adb shell mount command together I get an error. That's why I broke them up.
So basically, once in the tools directory, I should be able to copy and paste the commands (which is what I was doing)? I would need to get back in front of my home pc and I'll tell you what error I'm getting. I believe it was "adb: not found".
Click to expand...
Click to collapse
First the solution and then the explanation; note that I have included the command prompts here:
C:\android-sdk-windows\tools> adb shell
# mount -o rw,remount /dev/block/mtdblock3 /system
# exit
C:\android-sdk-windows\tools> adb push recovery-ra-eris.img /sdcard
C:\android-sdk-windows\tools> adb push recovery-ra-eris.img /sdcard
So, here's what is happening.
When you "break up the command", by making the first part the single line
Code:
adb shell
What you are getting is an interactive shell running on the phone. That shell does not terminate immediately; you can type an unlimited number of commands into it, one after another.
When you issue a command (from the PC's command window) which looks like this:
Code:
adb shell programname arg1 arg2 arg3 arg4
something a little different happens than in the first example: the program "programname" is launched on the phone, with the arguments "arg1", "arg2", et cetera - and the "shell" on the phone terminates as soon as "programname" is finished running
Note that the command prompt changed!
C:\android-sdk-windows\tools>
vs
#
So what happened? "adb" is a program on the PC, and NOT ON THE PHONE. When you typed "adb blah blah blah" into the interactive shell on the phone - guess what? you see "command not found".
If you insist on "splitting up the command", then go ahead (although I really don't see any reason why it wouldn't work in it's original format); just bear in mind you are typing commands into an interactive "command prompt" that is running on the phone. When it comes time to run other "adb" commands - you need to be at the PC's command prompt
bftb0

Thanks for the info. You were right. I had just screwed something up when I typed it in the first time. Explaining the steps really helped me to understand what I was doing. I entered the commands as you had them in the tutorial and it worked perfect. So after that I created a backup and attempted to flash a custom rom:
I just ran a nandroid backup for my Eris which was at stock 2.1 w/ root. I first partitioned the sd to swap - 3072 MB, ext2 swap 3072 MB, and fat32 - remainder. Realizing this was stupid, I went back and changed the partition to swap - 0, ext2 - 512 MB, fat32 - remainder 7680 MB or 7.5 GB. I moved ext2 to ext3 and booted the phone. All my sd was cleared so I copied everything back on (I saved all sd contents to my computer prior to this). I went back to recovery and flashed Eris Lightning 3.02. Everything went successful and when it rebooted, I saw the droid guys, then the "quietly brilliant", then "Verizon" screens. It then began running the "quietly brilliant" and "verizon" screens over and over. I pulled the battery and powered up again but it's still running those two screens over and over. I booted into recovery and attached my phone to the computer. I opened command prompt, entered " sd C:\android-sdk-windows\tools" and then entered "adb devices". It reads "List of devices attached" but there are none. I attempted to add the driver back to my device but when I go to device manager and click "update driver" and point it to the tools directory in SDK, it says that "Windows could not find driver software for your device".
If I can't communicate with my phone via usb and it wont boot, how can I get it to recover?
Any suggestions would help, I'm scratching my head here. I really don't want to have to buy another phone.

It turns out I was just having another newbie moment. I did a wipe and reflashed the rom and it worked perfectly.

[TIPS] Fastboot and adb on linux

I have a tip for everyone who use adb and fastboot in linux.
In most of the tutorials i see that you have go to exac folder to use them, but there is quite simple think you can do to use them from anywhere in your consol. All you have to do is
1. go in consol to the folder where you have adb and fastboot
2. then give command
Code:
sudo nautilus
or
Code:
su
nautilus
This should open a window with root permissions
3. in this windows you need to create shourtcats for adb and fastboot by right click mouse menu.
4. Next you need to cut shourtcats you created and place in folder /bin (you need to do this in the same window beacose you need to have root permissions to paste anything there.
5. And last think you need to do when you paste them it`s change there name`s for adb and fastboot.
Now you can use this commands without "./" and firstly you do not need to go to the folder where they realy are.
Now let say you have an system.img in /home/user/data you can now flash your phone in this way
Code:
su
cd /home/user/data
fastboot flash system system.img
or
Code:
su
fastboot flash system /home/user/data/system.img
su gives root permitions
Now i want to apologize for my english
If any one want to add this to his tutorial please give link for this thread or just write it`s made by me

abrams89 said:
I have a tip for everyone who use adb and fastboot in linux.
In most of the tutorials i see that you have go to exac folder to use them, but there is quite simple think you can do to use them from anywhere in your consol. All you have to do is
1. go in consol to the folder where you have adb and fastboot
2. then give command
Code:
sudo nautilus
or
Code:
su
nautilus
This should open a window with root permissions
3. in this windows you need to create shourtcats for adb and fastboot by right click mouse menu.
4. Next you need to cut shourtcats you created and place in folder /bin (you need to do this in the same window beacose you need to have root permissions to paste anything there.
5. And last think you need to do when you paste them it`s change there name`s for adb and fastboot.
Now you can use this commands without "./" and firstly you do not need to go to the folder where they realy are.
Now let say you have an system.img in /home/user/data you can now flash your phone in this way
Code:
su
cd /home/user/data
fastboot flash system system.img
or
Code:
su
fastboot flash system /home/user/data/system.img
su gives root permitions
Now i want to apologize for my english
If any one want to add this to his tutorial please give link for this thread or just write it`s made by me
Click to expand...
Click to collapse
Sometimes SU alone wont switch to the root user in some distributions (eg. Ubuntu Variants) If you want to switch to root, type sudo su or type "sudo <name of program>" and it will run that program as root.
Jack

[TUTORIAL] How to change Model ID and CIDNUM of HTC One without parsing errors

Anyone getting parsing error while trying to change the Model ID of their device using enghboot should follow these instructions:
Make sure you have the latest version of adb.exe and fastboot.exe files on your PC and that your device is S-OFF and rooted.
1. Navigate to the folder where adb is stored using command line.
2. Backup the original bootloader using the following commands.
Code:
adb shell
dd if=/dev/block/mmcblk0p12 of=/sdcard/mmcblk0p12.bin
adb pull /sdcard/mmcblk0p12.bin mmcblk0p12.bin
exit
Make sure you have a new file mmcblk0p12.bin in your fastboot and adb folder.
3. Download hboot.img from the link below and place it in the same folder as adb and fastboot.
https://www.dropbox.com/s/b695866du2dez3c/hboot.img
4. Place file on your device's sdcard using this command:
Code:
adb push hboot.img /sdcard/hboot.img
5. To write enghboot onto the device, use the following commands
Code:
adb shell
su
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p12
exit
adb reboot bootloader
6. Once in fastboot, use the commands below to change to the desired MID and cidnum.
Code:
fastboot oem writemid PN07xxxxx
fastboot oem writecid xxx__xxx
fastboot reboot
Thanks to the developers of eng hboot for creating such a wonderful utility!

Wow thanks for that!!
will try soon!

Tried 'fastboot oem writemid' it says unknown command...?>??

HTC ONe 802w
adb reboot bootloader
After this command phone went black screen and not responding hence in my device manager on PC i can see it android usb

HTCONE802W said:
adb reboot bootloader
After this command phone went black screen and not responding hence in my device manager on PC i can see it android usb
Click to expand...
Click to collapse
I followed the instructions and my phone has been bricked. I am getting snow error. Can anyone help?

[GUIDE][ROOT]How to install TWRP and ROOT your X507, X509 (PC Guide)

Okay, I have seen many people using the unofficial TWRP on their device, and that's a little dangerous because it may be malicious, and you might not even know that.
I am not saying it is, but it can be.
Now, back to the topic here,
HOW TO INSTALL TWRP[2] AND GET ROOT ACCESS[3] and more​Here goes..
Before anything, you need to get ADB and FASTBOOT programs on your PC and get your drivers installed so you can communicate with the device through your computer.
To Download ADB and fastboot program, you can download this file (not my upload)
Extract it anywhere you want(and remember that location).
(lets say "C:\workspace\ADB" and I will use this path for this guide).​Typically, the driver for ADB will install the first time you connect your device to your computer and:
Internet is available
USB Debugging is enabled on your phone
But the FASTBOOT driver would probably not be available yet. to get fastboot drivers, follow these steps:
Turn on and Unlock your device and connect it to PC via the USB cable.
Open CMD and execute "cd C:\workspace\ADB".(or you can open C:\workspace\ADB in file explorer and type CMD in the address bar to open CMD directly there.
Type "adb devices".
Now, your phone will ask something(permission to allow ADB access on the connected PC)allow it. After you allow it, the CMD will show a list of attached devices and the mode they are attached in, your device should show "device" for now.
If it does not, there is some problem, search on internet or ask for help here
Now type "adb reboot bootloader".
now your Phone will shutdown and open in a different state. It will say Fastboot on the screen.
Now the driver is installing or is already installed, to check, type this:
"adb devices" and it should show a list and your device's mode should change to "fastboot".
That's it for the ADB and FASTBOOT. You have the necessary things to continue.
Continue to next post for TWRP and the post next to it for ROOT ACCESS.

Now, we will talk about how to install TWRP​
@DroidThug has been kind enough to get Official support of TWRP for this device.
Head over to this thread to download the official image file of the TWRP Recovery and keep it on your computer, this is the very first step you need to take.
Here is the thread: https://forum.xda-developers.com/leeco-le-1s/development/official-twrp-t3527566
If you are lazy enough to go through the thread, which i suggest you to visit, here is the direct link to the download page: https://dl.twrp.me/x3/
And here is the direct download link of the v3.0.3(latest as of 31st Jan, 2017): https://dl.twrp.me/x3/twrp-3.0.3-0-x3.img
Once you have the recovery image, you need to flash it through fastboot.
If you are following this guide from start, you should already be in fastboot and have CMD open on your PC in adb folder.
Now, a few things you might want to follow strictly if you are unsure how to do it:
Copy the recovery image file to "C:\workspace\ADB" (adb folder).
Rename that file to "twrp.img"
Now you need to execute this command from CMD to flash the file:
"fastboot flash recovery twrp.img" and press enter.
This will take a few seconds and will will be over soon.
Now you need to reboot directly into RECOVERY, because if you will boot to the system first, the Device will replace your newly flashed recovery with the stock recovery and all this will be wasted. But if you reboot to recovery first, it will patch those things up and will stay.
So, to reboot to recovery, you need to use the key combo to get into the recovery,
Press and hold "Volume UP" and "Power" Buttons till the screen goes off(from fastboot mode) and is lit up again and then leave the power key and 2-3 seconds later, leave the Volume key too.
You will enter into recovery mode and it will ask you "if you want to keep the System partition to read only or not?"
I'd recommend keeping it to read only unless you know what you are doing.
There you have it!
You have successfully installed TWRP on your device!

GET ROOT ACCESS​
Okay, So you have the RECOVERY installed already
Now go to this page and download the latest "Recovery Flashable ZIP" from there. (Here is the latest one as on 31st Jan, 2017).
You can do this in two ways through Phone(with TWRP already present) and through PC.
Through Phone​All you need to do is flash it through the recovery and thats it, you will have root access!
Here are the steps to flash ZIPs from Recovery:
Get the zip file you want to flash(the one downloaded above) and place it somewhere in the Phone's internal storage.
Reboot to recovery(Power off and then hold "Vol UP" and "Power" keys till the screen is lit up.).
Tap on "Install".
Navigate to the ZIP file you placed in your phone's internal storage.
Select it and swipe to flash it.
The last step might take a few seconds and will be done then.
After its done, that't it!
Reboot to system and you have ROOT ACCESS!
Through PC​Okay, you would still need to reboot to recovery, but you can follow this guide if you don't want to copy the zip file on your phone for whatever reason you may have.
Here are the steps:
Enter recovery.
Select "Advanced->ADB Sideload" and swipe to start sideload.
Now connect your phone to PC.
Now open CMD in ADB folder.
Check if your device is detected by typing "adb devices". It should show a device with sideload state.
Now type "adb sideload " and drag the zip file into the cmd window.
OR
you can copy the zip to the adb folder and rename it to supersu.zip and write "adb sideload supersu.zip" in the CMD.
Now Press enter.
After this, in a few seconds, it will be over and you can reboot to system(it might automatically reboot to system too).
And that's it! There you have it!
You have ROOT ACCESS on your device!

5. Now the driver is installing or is already installed, to check, type this:
"adb devices" and it should show a list and your device's mode should change to "fastboot".
Click to expand...
Click to collapse
If the phone is on fastboot mode, "adb devices" supposed to not give any output. "fastboot devices" will show the device and mode as fastboot.
You will enter into recovery mode and it will ask you "if you want to keep the System partition to read only or not?"
I'd recommend keeping it to read only unless you know what you are doing.
Click to expand...
Click to collapse
My screen is broken (that's only white light and no digitiser). I dont have any other Le 1S to get idea.
1. Are you sure Vol Up + Power will enter into Recovery? Mine is 5.5.014S.
2. I want to make my system partition as writable. Can you tell how to achieve with hardware keys like Vol Up or down & power.
3. After step 2. Can I flash SuperSu from PC without enabling sideload. While on custom recovery , "adb devices" will show mode as recovery. So flashing supersu from here. Not sure if this is correct. On my Moto G falcon. whenever I go into TWRP, adb recovery and MTP works.
Also can you check whats the combination Vol Up+Vol Dn+Power. When it starts I can connect to adb but all partitions are read only and not allowing to make any change to device. Not sure if its due to encryption.
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb devices
List of devices attached
0123456789ABCDEF device
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb shell
[email protected]_HK:/ $ cat /data/misc/adb/adb_keys
/system/bin/sh: cat: /data/misc/adb/adb_keys: Permission denied
1|[email protected]_HK:/ $ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
[email protected]_HK:/ $ su
/system/bin/sh: su: not found
[email protected]_HK:/ $ cd
[email protected]_HK:/data $ pwd
/data
[email protected]_HK:/ $ exit
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb reboot bootloader
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>fastboot devices
0123456789ABCDEF fastboot
**
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb devices
List of devices attached
0123456789ABCDEF device
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb install mirror.apk
[100%] /data/local/tmp/mirror.apk
Error: java.lang.NullPointerException: Attempt to invoke interface method 'android.os.IBinder android.os.IServiceManager.getService(java.lang.String)' on a null object reference
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb shell am start -n com.android.settings/.wifi.WifiSettings
java.lang.NullPointerException: Attempt to invoke interface method 'android.os.IBinder android.os.IServiceManager.getService(java.lang.String)' on a null object reference
at android.os.ServiceManager.getService(ServiceManager.java:55)
at android.app.ActivityManagerNative$1.create(ActivityManagerNative.java:2494)
at android.app.ActivityManagerNative$1.create(ActivityManagerNative.java:2492)
at android.util.Singleton.get(Singleton.java:34)
at android.app.ActivityManagerNative.getDefault(ActivityManagerNative.java:88)
at com.android.commands.am.Am.onRun(Am.java:295)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
at com.android.commands.am.Am.main(Am.java:99)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:250)
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb shell dumpsys wifi
adb shell dumpsys wifi^C
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb shell
[email protected]_HK:/ $ ls -ld sdcard
lrwxrwxrwx root root 2017-03-21 11:12 sdcard -> /storage/sdcard0
[email protected]_HK:/ $ cd /storage/sdcard0
/system/bin/sh: cd: /storage/sdcard0: Permission denied
2|[email protected]_HK:/ $ ls -ld
drwxr-xr-x root root 2017-03-21 11:12 .
[email protected]_HK:/ $ ls -ld /storage/sdcard0
d--------- system system 2017-03-21 11:12 sdcard0
[email protected]_HK:/ $
Update:
I some how managed to side load. My Phone got bootlop after installing twrp. Then flashed userdata by following http://forum.le.com/in/index.php?th...op-restart-solution-letv-le1s-x507-x509.1155/ . Now its factory reset as I can see the screenshot from PC.
Still interested in knowing what's that Vol Up+Vol Down + Power.

If any one have le 1s related problem and solution or any one want to try new rom or kernal asap then all of u are welcome in our group on telegram so plz join with us
Requriemt
1. Download telegram from play store
2. Just click below link
https://telegram.me/LeSuperGroup
Thanks all of u