Affichage des articles dont le libellé est GUIDE. Afficher tous les articles
Affichage des articles dont le libellé est GUIDE. Afficher tous les articles

dimanche 23 août 2015

EXCLUSIVE How To Hack and Bypass Windows Login (GUIDE)



How To Hack and Bypass Windows Login

Have you ever forgot your Win XP, Vista, 7, 8 or 8.1 logon password ? Do you need to entry your pal’s or relative’s laptop

On this information, we are going to present you bypass a Windows XP, Windows Vista, Windows 7, Windows eight, Windows eight.1 and Windows 10 logon password

We’ll use a Software named Kon-Boot….It's paid software program however allmost all softwares are crackable ans so is for Kon-Boot Cracked Software Hyperlink given under

Options of Kon-Boot

Direct Obtain Hyperlink

It Can Bypass Windows XP, Windows Vista, Windows 7, Windows 8, Windows 8.1 and Windows 10
Kon-Boot is now capable of bypass on-line account authorization on Windows 8/8.1
It is not going to overwrite your outdated password …it means that you could simply entry you Good friend’s or relative’s PC with out getting caught :p
Quick, tiny and will get your job finished !
What’s New ?

Windows 10 Supported (Offline solely)
Steps To Bypass Windows Log-on utilizing Pen-Drive

Obtain and Extract Kon-Boot 2.four.rar from the hyperlinks given beneath
Plug in your Pen-Drive (Take away all different Pen-Drives)
Proper click on on “usb_install_RUNASADMIN.bat” situated in kon-bootUSB folder and decide “Run As Administrator” choice.
After Course of Compeletion, Reboot
Select Boot from USB from BIOS settings
Comply with the set up process.
After Booting course of you may login with out password, simply press “Enter”
Simply Take away Kon-Boot PenDrive and Reboot to Get again the unique Windows authentication performance.
Steps To Bypass Windows Log-on utilizing CD

Obtain and Extract Kon-Boot 2.four.rar from the hyperlinks given under
Insert Empty CD in your Optical Disk Drive
Obtain and Set up ImgBurn From the Hyperlinks Given Beneath
Run ImgBurn program
Choose “Write picture file to disc”
Click on “Browse”
Choose “kon-bootCD.iso” – this file is positioned in your “kon-bootCD” listing.
You're prepared to make use of your Kon-Boot
Select Boot from CD from BIOS settings
Observe the set up process.
After Booting course of you possibly can login with out password, simply press “Enter”
Simply Take away Kon-Boot CD and Reboot to Get again the unique Windows authentication performance.
How To Change Profile Password?

Boot with Kon-Boot
Navigate the Start Menu to Control Panel
Choose “User Accounts and Family Safety”
(if the Person Account Control window seems) Click on “Yes” and leave the password field empty
Choose “Create a brand new account”
Create the account (pick a name) and set the permissions (administrator).
Disconnect Kon Boot and restart the pc to revive unique Home windows authentication performance.
After Restart, Choose your new User Account (the account you could have created)
Navigate the Begin Menu to Control Panel
Choose “Consumer Accounts and Family Safety”
Choose the target User Account (the one you need to change)
Choose “Change the password”
Enter the brand new info for the account and click on “Change password”
You might be carried out
Screenshot



Videos

Preview


USB Set up Information


Downloads @ www(dot)gizmoster(Dot)com/how-to-hack-and-bypass-windows-login



samedi 22 août 2015

THE EASIEST GUIDE FOR FLASHING GPe LOLLIPOP 5.1 on XT1033



Hello. In this thread, i will teach you the easiest method for flashing GPe lollipop 5.1 for xt1033

I am not responsible for dead phones.

Needed:
Time :)
ADB and Fastboot(thanks to Snoop05 ): https://drive.google.com/file/d/0B0M...02Q0VBQnc/view
Unlocked Bootloader
Motorola USB Drivers: http://www.motorola.com/getmdmwin
DOWNLOADS:
GPe lollipop flashable zip(thanks to lost101 ): http://forum.xda-developers.com/devd...11835&task=get
TWRP Materialized 2.8.7.0 for GPe(thanks to h2o64 ): https://mega.nz/#!IgUxkKJR!uMI38IeG-...yT8-3J-IppQrAI
No GPS fix flashable zip(thanks again to lost101 ): http://forum.xda-developers.com/atta...4&d=1431252683
Modem fix(thanks to aybarchu ): http://www.mediafire.com/download/3l...r/Lollipop.rar
Recommenned memory leak fix(thanks to xpirt ) : https://mega.nz/#!zcFU3L6T!jbSK3G9Hz...KZXiMoSjjY8xDg

GUIDE :)
1: Your bootloader version should be 41.18

2:Put your phone in fastboot mode( if you are rooted, you don't be needed to use fastboot. Flash the twrp img with Rashr or Flashify app) and flash the recovery.

3:Boot the recovery :eek:

4: (Recommenned)Take a nandroid backup and put it in safe place. BECAUSE ALL YOUR DATA WILL BE DELETED!!!

5:In TWRP,click to wipe

5.1:Select everything except USB OTG, swipe to wipe and go back to wipe menu when its finished
5.2:Click to advanced wipe , select data partition and click fs options.

6:Click to change fs and select EXT4 and swipe

7:Connect your phone to pc. PC will recognise your phone as XT1032 if you havent disabled mtp on TWRP.
You can use 8a,8b or 8c.(Only one of them)

8a:Copy the GPe 5.1 zip and memory leak fix zip(if you want) to XT1032's internal storage.
8b:Use adb sideload commands when you selected in recovery "Advanced/ADB Sideload"
8c:Use USB OTG and flash memory.

9:Flash Them :)

10: When flashing finished,click wipe caches and wipe cache/dalvik.

11:Reboot.

12:When your phone turned on, turn it off and go to fastboot.

13:Click NETWORK FIX.bat in the lollipop folder and reboot.

14:Check the GPS. İf it isnt working, flash no gps zip,wipe cache/dalvik and reboot

ENJOY THE SMOOTH LOLLIPOP :D

I have tested all of the guide with my XT1033.But I am not responsible for dead phones.

Sorry for corrupt English :)

TIP: You can use Spirit2 fm radio app for real fm radio. It is working perfectly with rooted GPe 5.1



vendredi 21 août 2015

[GUIDE] No SIM PIN request with custom lockscreen = No signal



Hello,
I've just installed some of the 3rd party lockscreen apps and what I've noticed is that when using it the phone won't ask for PIN (for SIM card), so as a result it won't connect to the mobile network.
I've managed to solve this problem and I want to share it with you, as I've seen that I'm not the only one.

For this tutorial you will need:
1)Root
2)Xposed framework
3)2 additional apps that are mentioned later

Of course during that process you may damage your device, so don't blame me.
It is highly recommended, that you have some knowledge on how to fix the phone, uninstall xposed framework etc.

Ok, so let us begin.
1) Install AppOpsXposed or any similar program that can block apps from autostart and enable it in xposed.

2)Go to AppOps, select your lockscreen app (in my case Hi Locker) and disable the autostart.

3)Finally install "Llama" from the Play Store (or any other automatation app that has similar functionality) and make a new event like this:


And btw. I've set my system lockscreen to swipe, but it's being skipped anyway.

That's it. Give it a try.



mardi 18 août 2015

[Guide] Make a cool custom back case (Pic Included)



Here's the deal,
Things that you'll need:

1) A transparent back case.

here are a few links:

http://www.amazon.com/Galaxy-Case-Pr...ords=galaxy+s6

http://www.amazon.com/Trianium-Resis...ords=galaxy+s6

http://www.amazon.com/Galaxy-Spigen%...Y88HT4HAZ1ZFRP

In short you need a basic transparent back case, I use the Spigen Ultra-Hybrid Gunmetal.

2) You need a cutout for the back, there are multiple ways of doing it. If you buy a ringke fusion you get a cutout for free. If you dont like it, you can make it yourself. Place the phone on a white paper, outline the case using a pencil. Cut along the outline. you can leave a little space and cut along depending how thick your bumper is. Now place the cutout in the case and see if you need any adjustments. Similarly make a camera viewport cutout. Now you should have piece of paper that exactly fits into the case.

3) Take a good printout of whatever you want to show off and using the cutout you made as a reference, make the printed cutout you want in your case.

4) Voila! you are done. If you do it precisely you should have a flawless custom made back case. Mine almost looks like it is printed on the polycarbonate back.
Here's a Naruto one I made for myself:
Naruto shippuden for galaxy s6

Hit the thanks button if this was helpful :)



dimanche 16 août 2015

Has anyone tried unlocking the basebands through this guide yet?



Source: http://forum.xda-developers.com/gala...ds-to-t2886059

Use your phone anywhere


Have you ever wondered why your phone doesn't work nearly as well when you travel?
Or tried to change carriers only to be told that you'd need to buy a different version of your high end phone for it to work properly?
It's happened to a lot of us and there is no good reason for it. Other than greedy carriers that is.

Most phones should work on a lot more bands. And have good reception when roaming. The S5 in particular is one of the first phones that is fully capable of working on every GSM and LTE frequency in the world. So.. why doesn't it actually do that? Well because your carrier doesn't want to make it easy for you to leave. And because Samsung and other manufacturers want to force you to buy a new phone everytime you change telephone companies. So they put restrictions in your phone to limit how many bands you can use. Wouldn't you rather have your phone work on all carriers?

This guide will show you how to do that.


Okay okay, I'm convinced already.
I don't want to read any more. I'm a power user (or reckless).. just show me how to do the hack!




The lawyers made us do it

We have to post an obligatory warning

We don't think that this mod will cause you any problems. But we can't guarantee that.
You assume all risks if you proceed, including the risk that your phone might object, meltdown, brick or void your warranty.




Quick Start Guide

CLICK TO HIDE CONTENT

This mod makes a night and day difference when you travel, roam or change carriers. It's a dramatic improvement.
But it's not an easy, one click process. There are a lot of steps to add this to your phone.

And due to minor differences between brands (finding the hidden USB settings menu), it may take a little experimenting to succeed. So this mod won't be for everyone. But if you have some patience, you can add a lot of bands to your phone. Just post in the thread and we'll figure it out as we go. This Quick Start guide will show you how to add bands to a Samsung S5. It can also be used on dozens of other Samsung, Sony, LG, HTC, Nexus, etc phones with minor differences in the steps here. I'll add comments for other brands when I have them. If you get stuck anywhere, post in the thread for guidance.



The Mod:

Step by step guide

1. You need a phone with a Qualcomm processor that has been rooted.
2. If you need to root your phone, click on the button below for guidance. Otherwise skip to step 3.
CLICK TO HIDE CONTENT

How to root your phone

There are a lot of XDA threads explaining how to root your phone. Towel root will work with almost all phones (and doesn't increment the Samsung Knox flag, if you care about that). You need a pre June 6, 2014 firmware build for the original Towel Root method to work. Otherwise, downgrade to an older firmware first (Use Odin software for Samsung), then root with Towel root. Or you can look for the modified Towel root that is said to work with newer firmware (unconfirmed by me). Another excellent root method is CF-Autoroot which works with most popular phones.

3. If you are running a custom ROM and kernel that were compiled from source code, well done. Skip to Step 4.
Otherwise click on the button below for more information.
CLICK TO HIDE CONTENT

Custom ROM & kernel

Qualcomm apparently reads XDA too and appears to have added some anti-tamper code to keep this hack or similiar mods from working. Drat! Until we figure out exactly what they added, you will need a custom ROM & kernel for this mod to work. This works because a kernel made from scratch won't have the anti-tamper code in it. Probably you only need the custom kernel and not the full custom ROM (unconfirmed). Configurations known to work include CM11 + Ark kernel. And Phoenix V3 ROM + kernel. But any custom ROM + kernel that is made from source, rather than modified stock will probably work fine. If anyone is still running Jelly Bean (firmware versions 4.2.2. and below), you probably don't have the anti-tamper code and won't need a custom ROM or kernel.

You can go ahead and try adding bands without a custom kernel. It probably won't work, but you can leave the custom kernel as the very last step if you want to and see if adding bands without a custom kernel succeeds. Note that installing a custom kernel on a Samsung phone will increment the Knox flag if you care about that (the Knox flag might affect a warranty claim).

If you have a Verizon or ATT phone, you should know that these two carriers do something that almost no other carrier does. These two carriers lock the bootloader which prevents installing a custom kernel in the normal manner. The Safestrap program can emulate another ROM, but we won't know if that is sufficient or not for this mod. If you are with Verizon or ATT, let us know if you were able to add bands or not.

Follow this link for details about the Phoenix ROM + kernel for the S5.
You can find CM11 downloads here for various phones. Then look for an XDA support thread for your phone.
Ark kernel

4. Download and install QPST. We will use this program to edit your phone settings. This runs best on Windows XP. But you can use Windows 7 (and probably Win 8, if you must). Right click on setup.exe (not the .msi file) and choose run as adminstrator.

5. Download and install QXDM. We will use this program to "write enable" your phone settings. QXDM won't work unless QPST is also installed, so you need both programs. Right click on setup.exe and choose run as administrator to install.
6. Open the USB settings screen on your phone. Change USB from AP to CP. And USB settings from MTP + ADB to RNDIS + DM + Modem mode (after you have finished making edits in your phone's memory, remember to revert the original settings in this screen).

This is the hardest part of this mod as the USB setting menu is usually hidden and the method to access it is slightly different on some brands. For the S5, you can open it by dialing *#0808# . Other phones may use *#7284# , *#8778# , *#*#8778#*#* , ##3424# or something else entirely. If those codes don't work on your phone, try a Google search for keywords like those below to find out how to open the USB settings menu for your phone:

Google: USB settings <brand> xda
Google: how to use QPST <brand> xda

6a. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
For Sony, the following CLI commands have been reported to work. These may or may not work for other brands.
You can enter these using a terminal emulator app or from an adb shell.

From terminal emulator:
Code:
su
setprop persist.usb.eng 1
setprop usb.rndis.enable 1
echo 1 > /sys/class/usb_composite/modem/enable

Or using adb:
Code:
adb start-server
adb shell
su
setprop persist.usb.eng 1
setprop usb.rndis.enable 1
echo 1 > /sys/class/usb_composite/modem/enable
exit

If you use either of these, remember to revert the USB settings after you finish your phone edits. e.g.
Code:
su
setprop persist.usb.eng 0
setprop usb.rndis.enable 0
echo 0 > /sys/class/usb_composite/modem/enable

6b. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you have an LGE phone, try the dialer codes here and change the USB mode from AP to CP (Modem mode). If that doesn't work, then it has been reported that the following commands will also enable diagnostic mode for you:
Code:
su
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
setprop sys.usb.config acm,diag,mtp,adb

6c. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you have an HTC phone, this diagnostic driver may work for your phone.

6d. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you have an Opo phone, it been reported that the following commands will enable diagnostic mode for your phone.

Code:
su
setprop sys.usb.config diag,adb

6e. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you have a custom kernel installed (which has permissive permissions) then you can probably enable diagnostic USB mode from the EFS Professional program menu.

6f. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you cannot find out how to access the USB settings on your phone anywhere, you may be able to force diagnostic mode by installing the Windows USB drivers for your phone in advance. You can download Motorola /Sony/ LG/ HTC/ ASUS/ Huawei /Google, etc drivers here. Otherwise do a Google /XDA search to find USB drivers for your phone. Install the USB driver.

7. Enable USB debugging on your phone. This is a hidden menu. Look for Settings menu > System > About Device > Developer. If you don't see a Developer option, then tap on the firmware build number about ten times to unhide it.
8. Connect your phone to your phone to an USB port on your PC. Do not use an USB hub, connect directly to your computer. Windows will install a diagnostic driver.
9. Open the Windows (Control panel) Device Manager and confirm that you see something like "Samsung Mobile USB Serial Port" listed there. If you see a yellow triangle there > right click and update the driver.

10. Open the "QPST Configuration" program > Ports > Add new port > choose the port labeled diagnostic > OK.
If you do not see a diagnostic port listed and you were not able to explictly able to set USB diagnostic mode earlier, then right click on the driver that Windows has assigned to your phone in the Windows (Control panel) Device Manager > Update Driver Software > Browse. Choose the folder where you extracted the USB driver that you downloaded for your phone. This forces Windows to use the downloaded driver.
11. Now select the QPST Start Clients > Software download > Backup > Start. This saves a backup copy of your phone's stock NV memory to your computer in case you need it later.
12. Navigate to the C:/Program Files/Qualcomm/QPST/bin folder.
13. Right click on ServiceProg.exe > run as administrator.
14. Choose Phone > Read from phone > UMTS System. This will show which 3G bands are currently enabled. Add checkmarks to the additional 3G bands that you would like to add. Resist the temptation to check everything unless you are prepared to troubleshoot possible issues with non-existant bands, slow boot times and other issues. Just add specific bands that you need for another carrier or are missing in the areas you travel. If you aren't sure what to add, then don't check any extra bands for now - you can always come back later after you find out which 3G bands you can actually make use of.

Either way, do not click write to phone yet. And do not close the Service Programming window either.

15. Before we write anything to your phone, we need to write enable the locations we are going to edit. Navigate to the C:/Program Files/Qualcomm/QXDM/bin folder.
16. Right click on QXDM.exe > run as administrator. If you are not adding any new 3G bands at this time, skip to step 21.
17. In the NV Browser window, scroll down to ID 01877 (aka NV 1877) > Read.
Then write "0" to NV 01877 with QXDM. This initializes (write enables) the item for QPST. We need to do the same for several more NV items.
18. Select ID 00441 > Read. > Write "0" to NV 00441 with QXDM. This initializes (write enables) the item for QPST.
19. Select ID 00946 > Read. > Write "0" to NV 00946 with QXDM. This initializes (write enables) the item for QPST.

20. Select ID 02954 > Read. > Write "0" to NV 02954 with QXDM. This initializes (write enables) the item for QPST.
21. If you do not intend to add any new LTE bands, skip to step 24. Otherwise,
Select ID 06828 > Read. > Write "0" to NV 06828 with QXDM. This initializes (write enables) the item for QPST.
22. Select ID 06829 > Read. > Write "0" to NV 06829 with QXDM. This initializes (write enables) the item for QPST.
23. If you wish to add LTE bands and have already calculated a custom value from the instructions in the thread, then use QXDM to write that value to both ID 06829 and ID 06829, writing one item at a time.
Otherwise, write (decimal) "17592185995263" to both ID 06828 and ID 06829, writing one item at a time. This will enable all LTE bands.
Note that LTE edits will only work if your firmware has an LTE modem. If you already have at least one LTE band active, then you are OK. If your current firmware is from a carrier that does not use LTE at all, then you'll also need to update your modem to an LTE capable version as well.
24. Now go back to the Service Programming window that you left open. If you added any new 3G bands, click on write to phone to write the current selection of 3G bands to your phone. Otherwise do not click write, simply continue on to the next step.

25. You are now finished editing the NV values in your phone.
26. Reboot your phone.
27 In the Service Programming screen, choose Phone > Read from phone > UMTS System to confirm that your new 3G band selection are persistent. If they revert and you don't have a custom kernel installed, this confirms that you will need a custom kernel for this mod to work.
28. In the QXDM NV Browser screen, scroll down to ID 06828 > Read. Note the value.
29. In the QXDM NV Browser screen, scroll down to ID 06829 > Read. Note the value.
ID 06828 and ID 06829 should both show the custom value that you wrote. i.e. "17592185995263" (or hex "0xFFFFFFF3FFF") or the custom value, if you had used one.

30. Remember to change your USB settings back to normal mode, e.g. on the S5, dial *#0808# again and choose USB = AP and USB Settings = MTP + ADB > Click OK.
31. Celebrate! And let us know about your success (or sticking points).
32. You can test your results by checking whether your phone uses the new bands when you roam onto other systems that use them. Or if you have a SIM card for an alternate carrier. To tell if your phone is using the new bands, you can look at the current band being used in the Service menu or with various apps, e.g. LTE Discovery.

.


So now what?

Well, if you decided to jump in and follow the Quick Start Guide.. that's it. The Quick Start Guide has everything that you need to add new bands to your phone. Unless you run into difficulties, you don't need anything else. The guide is a bit terse as I don't have a lot of spare time to rewrite or polish it. But all of the important information is there.

If something doesn't make sense or you get stuck somewhere, you can (and should) try a quick search for details. If that doesn't resolve your issue, then post in this thread for help. If you want to learn more about how this works, why more bands is a good thing. Or how to make custom edits that choose particular frequency bands, then keep reading this post and the rest of the thread.

This is a proven working method, despite a few trolls claiming otherwise. It's also new territory and there are model specific quirks.
If you run into problems, most likely you missed a step somewhere. Less likely, you may have discovered something new that needs to be unraveled.

The purpose of this thread is to discuss new findings and suggest ways to improve this method.
This is not a support thread, although if you make an effort to provide enough detail about your situation, someone will probably try to help you.




Is this mod hard to do?

No. There really isn't anything hard about it. But it's not a one click kind of mod either. These are recent discoveries and there are a lot of steps needed to make these changes. Samsung doesn't want to make it easy for you - they'd rather sell you another phone. In particular, there is one hidden menu (USB settings) that is hard to find because it's in a different place on almost every brand of phone. So we have to Google around for details and experiment a bit to find the hidden menu for some brands. But the mod works. If you have a little patience and don't get frustrated at temporary obstacles, then you can add bands to your phone!

One surprising finding was that people with older phones were having better results. Why? It seems that Qualcomm quietly added some anti-tamper code into recent Android versions to keep us from doing this. It's almost like they read our forum and know what we're trying to mod. But they wouldn't spy on us like that, would they?

We don't know where the anti tamper code was added yet but we found that we can avoid it on newer phones by installing a custom kernel & ROM. So until we discover where they added the anti tamper stuff, you also need a custom kernel & ROM (probably the custom kernel is the essential part) to make this mod work. Unless you happen to have an older phone that is still running Jelly bean (4.2.2) firmware. So that's it in a nutshell.



Okay. So give me a quick overview again

Our phones have artificial restrictions in them so that they only work properly on the original carrier. If you travel (roam) or change phone companies, your phone won't work 100% because it will have gaps in coverage. It will be missing some of the frequency bands that the other carrier uses. This isn't a technological limitation. It's just your wireless carrier siphoning more money out of your pocket by forcing you to buy a new phone when you change carriers.

This mod has a lot of steps in it, so it won't be for everyone. But if you have some patience or enjoy a challenge then it's a great way to really improve how well your phone works when you roam onto another carrier. There are three parts to this mod. You need:

1. A phone with a Qualcomm processor, that is rooted.
2. (For now) Install a custom ROM & kernel to get rid of the anti-tamper code
3. Edit six values in your phone's non volatile (NV) memory to enable a lot of additional frequency bands


That's it. It takes about thirty steps to do those three things but nothing really good ever turns out to be easy, right?



RULES and GUIDE for posting threads in Original Development



...



RULES and GUIDE for posting threads in Original Development



...



[GUIDE] Restoring Stock ROM, Recovery, Unbrick, and Rooting 5.0 on Padfone S



I had stuck on ASUS logo, after I do a lot of researches, a lot of trials and errors for 4 hours. I managed to fix them and I wanted to share how I did here.

Easiest way to root lollipop WW-12.2.2.27
use KingRoot from http://www.kingroot.net/down ,It is android app which will run exploit to root the device successfully.
Not Kingoroot Kingoroot was unable to root. Towelroot v1 works only on Kitkat, but not lollipop.

To boot into fastboot mode
adb reboot bootloader
OR turn off device, press and hold power and volume up, until asus logo appear, and stuck at asus logo, that is fastboot mode, to exit fastboot with buttons, press and hold vol down and power button.

To restore stock recovery and ROM after you install TWRP or CWM, or unbrick device
First, note that stock recovery from http://forum.xda-developers.com/show...3&postcount=29, does not work for me (maybe everyone else as well).
I flashed it using fastboot flash recovery recovery.img, when I try to boot into recovery using, vol down and power, then select enter recovery, it stucks at asus logo.

First you need to flash TWRP_2.8.7.0.img from http://quarx2k.ru/asus_padfone_s/recovery/

using fastboot flash recovery TWRP_2.8.7.0.img It will show that flashing FAILED (remote: can't flash unsigned image), it fact, it was succeeded, now you can go ahead and boot to recovery.
Note that this version of TWRP, and 2.8.6.0, and CWM cannot successfully flash stock zip ROM, it may show errors, or when you try to boot the device, it will stuck at ASUS logo. But now, we are going to need TWRP_2.8.7.0 to unlock bootloader.

Let's unlock bootloader
simply flash http://quarx2k.ru/asus_padfone_s/CrowLock_RC3.zip with TWRP
You can check bootloader status with fastboot oem device-info"
Before unlock :
(bootloader) Device unlocked: false
After unlock
(bootloader) Device unlocked: true

Let's flash stock Kitkat Firmware
You have to unlock bootloader becuase, well it is complicated.
The only TWRP recovery that can successfully flash stock .zip firmware from ASUS is http://datbak.com/links/padfone_s/as...rp_2_7_1_1.img
But this recovery has another bug, if you flash recovery and try to boot to recovery, you will get blank screen, but TWRP is indeed working, you touch the screen and it vibrates back. Anyway you have tofastboot flash recovery asus_t00n_twrp_2_7_1_1.img because it will be needed later for upgrading Kitkat to Lollipop.
If you don't unlock bootloader, you will not be able to boot into recovery directly without flashing to recovery partition Now let's get into fastboot mode, and fastboot boot asus_t00n_twrp_2_7_1_1.img, by booting into this recovery directly via fastboot without flashing it first, you will not get black screen bug of this recovery., if you boot to this recovery from recovery partition, you will get black screen as I told previously.
Now let's flash downgrade to 4.4.2 firmware from http://dlcdnet.asus.com/pub/ASUS/Mob...r-wipedata.zip with TWRP 2.7.1.1.
This is for only WW SKU, not TW SKU. And all userdata will be wiped.
Browse all firmwares and there is TW SKU downgrade here : https://www.asus.com/Phone/PadFone_S...Desk_Download/
Ok, now reboot to system, and yeah, it finally boots now.
The recovery is still TWRP, not stock one, let's upgrade to lollipop and restore stock recovery using TWRP. Simply place http://dlcdnet.asus.com/pub/ASUS/Mob....2.27-user.zip to root of Internal Memory, unplug usb, press confirmation in notification to begin install lollipop. After device reboot, it will stay blank screen for 5 minutes, don't worry, it is updating to lollipop, after upgrade is done, it will reboot, and recovery will be restored to stock recovery now.
Bootloader is still unlocked.

Another method to root is
fastboot flash recovery asus_t00n_twrp_2_7_1_1.img (recovery is restored to stock now remember)
then flash https://download.chainfire.eu/696/Su...etrieve_file=1 with TWRP.

To lock bootloader again, boot into fastboot
then fastboot oem reset-dev_info
But I won't recommend you to lock bootloader, you will lose ability to boot to TWRP recovery without replacing stock recovery, unless you are going to send your device to service center and claim warranty.



vendredi 14 août 2015

[GUIDE] Root access on Republic Wireless 4.4.4 Kitkat Moto X



I finally found a root method for the moto x on republic wireless running 4.4.4, I used a chinese app called Kingroot(app is in english). It works pretty well, although if it doesn't work for you, reboot. A few times for me it didn't work but rebooting fixed it.

To use it, just open it up, follow what it says and your rooted.
Note, that in order for it to root it needs WiFi or a data connection so it can get a list of root methods.

You can download Kingroot from multiple sources, I can't put in a link though because I am a new member. Just search it up.



Full guide to use link2sd and link all your apps and data



The Full Guide to use link2sd

root you device before doing any thing



First if your are running on kitkat please disable write protection by flashing this from Custom recovery here is link http://forum.xda-developers.com/desi...el-vm-t2987126


if your are running on lolipop please disable write protection by flashing this from Custom recovery here is link http://forum.xda-developers.com/desi...stock-t3091456


Second partition your memory card as you want here is a tuturial http://forum.xda-developers.com/show....php?t=2142844


You can download full version from here and follow instruction of patcher to get plus version


(Optional) You can get more space by removing bloatware with titanium backup


Latest screens shots attached

that's all congratualtion :D
sorry for my bad english :)


iam sorry for my late
press thanks button if helped ;)








Attached Thumbnails


Click image for larger version<br/><br/>Name:	Screenshot_2015-08-15-16-27-02.jpg<br/>Views:	N/A<br/>Size:	90.2 KB<br/>ID:	3439440
 

Click image for larger version<br/><br/>Name:	Screenshot_2015-08-15-16-27-06.png<br/>Views:	N/A<br/>Size:	215.2 KB<br/>ID:	3439441
 

Click image for larger version<br/><br/>Name:	Screenshot_2015-08-15-16-27-10.png<br/>Views:	N/A<br/>Size:	161.8 KB<br/>ID:	3439442
 

Click image for larger version<br/><br/>Name:	Screenshot_2015-08-15-16-27-23.png<br/>Views:	N/A<br/>Size:	63.3 KB<br/>ID:	3439443
 

Click image for larger version<br/><br/>Name:	Screenshot_2015-08-15-16-28-20.png<br/>Views:	N/A<br/>Size:	124.8 KB<br/>ID:	3439444
 

Click image for larger version<br/><br/>Name:	Screenshot_2015-08-15-16-28-23.png<br/>Views:	N/A<br/>Size:	114.3 KB<br/>ID:	3439445
 














[CWM] Installation guide for PhilZ Touch 6 via Odin for Galaxy Pocket Neo GT-S5310/2



What is PhilZ?
PhilZ Touch recovery is an advanced edition of cwm recovery, that provides more options and you can use the touch.
The original thread was posted by @karthick mostwanted who created this recovery for this device. He did it flashable with Rashr on a .img file, but the developer Leonnard Rai, made it flashable with Odin. In my case, I tried with Rashr but did not flashed the recovery, so I tried the Odin version, and it worked. I think it was due to the ROM I installed to my cell phone, because the developer posted it on the original development section. So in conclusion, this should work in case you have a ROM installed. See the original thread here http://forum.xda-developers.com/pock...touch-t2937983

Requisites: To know how to use Odin :silly:

Instructions
After you flash the recovery,do the following:
-Get into the recovery mode and go to <Recovery Settings>GUI preferences>Toggle Virtual Keys and disable them, because they don´t work, only the one to go back
-In that same menu, select "Menu Height" and select it up to get number 20, wich is the smallest, perfect for the little screen of the phone.
-Go to /sdcard/clockworkmod/ and create the folder "aromafm" and "custom_res"
-Go to /storage/extSdCard/clockworkmod and create the "custom_res" folder too (ih this carpets you can save pictures in .png files and then use those pictures as the background of the recovery)
-Download Aroma filemanager here http://forum.xda-developers.com/show....php?t=1646108 and place it in /sdcard/clockworkmod/aromafm/ and you will can use Aroma filemanager getting in Advanced Options>Aroma filemanager

Features
-Root Explorer built
-Binaries SuperSu
-Target sdcard
-Choose from check Root on/off
-Save and load the Recovery Settings
-Enter password in the Recovery
-Change colors and background
-Gestures
-Virtual buttons
-Size and sensitivity of menus
-Option "Clean to Install a New ROM"
-Custom option BackUp
-Shows Progress
-And much more

Some piece of advice, touch works only for scrolling, when selecting an option, you will NEED to press the home button.

Downloads: https://mega.nz/#!xwZi1DyL!PcK3QNeTX...-kKiSazKSmcrmI



[CWM] Installation guide for PhilZ Touch 6 via Odin for Galaxy Pocket Neo GT-S5310/2



What is PhilZ?
PhilZ Touch recovery is an advanced edition of cwm recovery, that provides more options and you can use the touch.
The original thread was posted by @karthick mostwanted who created this recovery for this device. He did it flashable with Rashr on a .img file, but the developer Leonnard Rai, made it flashable with Odin. In my case, I tried with Rashr but did not flashed the recovery, so I tried the Odin version, and it worked. I think it was due to the ROM I installed to my cell phone, because the developer posted it on the original development section. So in conclusion, this should work in case you have a ROM installed. See the original thread here http://forum.xda-developers.com/pock...touch-t2937983

Requisites: To know how to use Odin :silly:

Instructions
After you flash the recovery,do the following:
-Get into the recovery mode and go to <Recovery Settings>GUI preferences>Toggle Virtual Keys and disable them, because they don´t work, only the one to go back
-In that same menu, select "Menu Height" and select it up to get number 20, wich is the smallest, perfect for the little screen of the phone.
-Go to /sdcard/clockworkmod/ and create the folder "aromafm" and "custom_res"
-Go to /storage/extSdCard/clockworkmod and create the "custom_res" folder too (ih this carpets you can save pictures in .png files and then use those pictures as the background of the recovery)
-Download Aroma filemanager here http://forum.xda-developers.com/show....php?t=1646108 and place it in /sdcard/clockworkmod/aromafm/ and you will can use Aroma filemanager getting in Advanced Options>Aroma filemanager

Features
-Based on ClockWorkMod recovery v6.0.5.1 (lastest)
-Root Explorer built
-Binaries SuperSu
-Target sdcard
-Choose from check Root on/off
-Save and load the Recovery Settings
-Enter password in the Recovery
-Change colors and background
-Gestures
-Virtual buttons
-Size and sensitivity of menus
-Option "Clean to Install a New ROM"
-Custom option BackUp
-Shows Progress
-And much more

Some piece of advice, touch works only for scrolling, when selecting an option, you will NEED to press the home button.

Downloads: https://mega.nz/#!xwZi1DyL!PcK3QNeTX...-kKiSazKSmcrmI



Video Guide : Installing OxygenOS on a Chinese handset.



Hi Guys ,I am still awaiting my OnePlus Two to be delivered but was searching for some info on installing OxygenOS on a Chinese handset running HydrogenOS.

DISCLAIMER - This is not my video , full credit goes to GIZCHINA on YouTube, I just found it on YouTube and thought other like me thinking of buying the Chinese version would benefit.

https://www.youtube.com/watch?v=ast7FA-O_eU

Hope this helps some of you guys as it seems a lot easier than I had expected.



jeudi 13 août 2015

[GUIDE] [INFO] What are GCC Flags and Optimizations?



Note: This is not a guide on how to use flags, what flags are the best, or how to optimize your rom/kernel/etc. This is a guide for users to help them understand what some compiler terms mean and how they affect the rom/kernel/etc they are planning to use.

INTRODUCTION
Hey there XDA Users! In today's Android development world, "optimizations" and "flags" are used to improve performance and many aspects of ROMs, Kernels, apps, and more. Some of these have seemingly become buzzwords, thrown out when developers and ROM chefs want to say that their work is fast. These can be overwhelming, as there are maaaannnnnyyy flags. Here's a small document I've made to help simplify things.

GUIDE <-- That's a link btw
(I used google docs for ease of use, and so its more properly formated)
More information and flags can be found HERE


QUESTIONS
Apropriate questions should be similar to "I don't see blank flag, what does it do?"
If you ask to to use flags or how to optimize your work you will be ignored and laughed at.



[ROOT][NO-PC]LG-D320 and misc L70 devices root guide



Quick guide for people having trouble rooting LG-D320/L70 devices running 4.4.2 with a new 3.4.0+ kernel
This way is easier then any root method and NO PC is required

Simple, straight forward, takes not even 5 minutes.

First download and install these 3 apps.
CPU Benchamark
Terminal Emulator
KingoRoot.apk

Second, download this zip file and extract the "mrw" folder to your phones internal memory(/sdcard)
ReplaceKingoRoot.zip

Third, open CPU Benchtest app and press the "stress test" box, then minimize the app and open Kingo ROOT app and press the "ROOT" bubble

Fourth, Kingo ROOT says your device is rooted open Terminal Emulator and type the following

Code:


su

Your device will ask if Terminal Emulator can be granted root permissions, allow it then proceed to type the following

Code:


sh /sdcard/mrw/root.sh

Then SuperSU will automatically open and ask to update SuperSU binaries, select the "update" box and when it asks you how you want to update it select the "normal" box

Five, Restart your phone when SuperSU says you need to restart for the update to take effect

ENJOY :)

Credits:
wanako1
MrW0lf (i updated the ReplaceKingoRoot files and changed added a few things)



[GUIDE] Android Rooting for Programmers



Author: Apriorit (Device Team)

Permanent link: www(dot)apriorit(dot)com/dev-blog/255-android-rooting

You have an Android Device and you are familiar with Linux based operating systems. Maybe, you like SSH or telnet to communicate with the device; you want to setup your device as a router to connect home PC to the Internet. However, you will be surprised. Android has neither login screen nor possibility to gain privileged user access to the system to do these things. This is one of the Android security principles to isolate applications from the user, each other, and the system.

In this article, I will describe you how to gain root access on an Android device in spite of security. I will delve deeply into one of the Android rooting principles - the adb exhaustion attack, which is simpler to understand than a previous udev exploit. It is suitable for all Android-powered devices with the version 2.2 and lower.

Rooting principles

Overview

In three words, the main rooting idea is to get super user rights on a device shell. Like a standard Linux shell, it allows you to interact with the device by executing commands from the shell. The shell can be accessed via ADB (Android Debug Bridge) command tool. The main purposes of the ADB on Android-powered devices are debugging, helping to develop applications and also, in some cases, it is used for synchronization purposes (when syncing HTC Wildfire, it is required to turn on the USB Debugging). We will use the ADB tool for uploading and executing the exploit, working with rooted device via super user shell with full access to whole device file system, programs and services.

ADB includes three components:

1. A client, which runs on your machine. Windows users can invoke it from the cmd and Linux users - from the shell;
2. A server, which runs as a background process on your machine. It manages communication between the client and the daemon running on the Android-powered device;
3. A daemon, which runs as a background process on the device.

We are interested only in the third component. The daemon runs on a device and communicates with a client through a server. When you issue the ADB command like a shell, the daemon will create a shell instance on a device and redirect its output to the client. Obviously, the shell new instance created by the daemon inherits rights and environment from its parent. As the daemon runs with the AID_SHELL rights, the shell new instance and all processes created by the shell will have the same access rights. Hence, to get super user rights in the shell, we just need the daemon to be running with these rights.

To understand why the ADB daemon has the ADT_SHELL user space, we will consider how it is started up and look at its initialization script.

The first user land process started after the Android device booting is the init process. After initialization and starting of internal services like property service, ueventd service etc., it begins parsing the init.rc configuration script. The ADB daemon is mentioned in the script as the service and it is started by the init service on the boot if the USB Debugging is enabled.

Let’s look at the ADB daemon initialization source code. The main daemon entry point, where it starts its execution, is adb_main. I skipped non significant pieces of code to focus your attention on the daemon security.


Code:


int adb_main(int is_daemon, int server_port)
{
...
    int secure = 0;
...
  /* run adbd in secure mode if ro.secure is set and
    ** we are not in the emulator
    */
    property_get("ro.kernel.qemu", value, "");
    if (strcmp(value, "1") != 0) {
        property_get("ro.secure", value, "");
        if (strcmp(value, "1") == 0) {
            // don't run as root if ro.secure is set...
            secure = 1;
        }
    }

    /* don't listen on a port (default 5037) if running in secure mode */
    /* don't run as root if we are running in secure mode */
    if (secure) {
...
        /* then switch user and group to "shell" */
        setgid(AID_SHELL);
        setuid(AID_SHELL);
...

    return 0;
}


So, what we see here. When the ADB daemon is starting, it has super user rights, like the init process has. However, the daemon reads some properties from the system and decides to set secure flag or not. Usually, if the device is not a development device and it is not an emulator, the properties have such values:

ro.kernel.qemu – “0” // is running on emulator
ro.secure – “1” // secure mode
After properties are checked, the secure flag is set to true, and we hit to such code section:


Code:


if (secure) {
...
        /* then switch user and group to "shell" */
        setgid(AID_SHELL);
        setuid(AID_SHELL);
...


Starting from this point, the daemon continues its execution with the AID_SHELL user id as it drops root privileges. All processes, started by the ADB daemon, like sh, will inherit its rights and will work in very limited environment. It is really sad, isn’t it?

Exhaustion attack


The main rooting principle of the exploit described in this article is the setuid exhaustion attack. The setuid function changes the user id for a process only in case if there are resources available, otherwise it fails and the process remains with that user id, with which it was started. Let’s look at the resources that can be limited by the Linux operating system. We are interested only in the RLIMIT_NPROC resource. This resource limits maximum numbers of processes that can be created with the same user id. If you have reached the limit, you can’t create more processes with this user id. The setuid function doesn’t create processes, but it follows this rule. Once, the NPROC limit for the AID_SHELL user is reached, setuid fails and the process continues its execution with the user id set before the setuid call. It means, when the ADB daemon starts with the AID_ROOT user id and tries to change it for AID_SHELL, for which NPROC is reached, setuid fails and the daemon user id remains AID_ROOT.

It is easy enough, isn’t it?

In files attached to the article, you can find the binary file and sources. They implement the adb exhaustion attack explained above. The rooting process is easy for a user and I will describe how to use it below, but now, I will go into detail about the attack implementation. I will touch upon the source code structure and go into detail about a few important points.

Let’s look at the root() function in the impl.cpp file. It implements the main logic of the exploit.
...

Code:


rlimit s_rlimit = { 0 };
          getrlimit( RLIMIT_NPROC, &s_rlimit );

          printf( "RLIMIT_NPROC: %d.%d\n", s_rlimit.rlim_cur, s_rlimit.rlim_max );

          pid_t adbdPid( get_pid( g_adbd_name ) );


...
At the beginning, after it gets and prints the NPROC limits, it runs the ADB daemon PID and saves it into a variable. It will be used later to kill original process. Next, look at the fork loop:


Code:


pid_t pid( -1 );

  for( int i( 0 ); ; ++i )
  {
      pid = fork();

      if( pid == 0 )
      {
        return ret;
      }


...
The code above represents an infinite loop. It forks calling process and exits from a child. That is enough because PID, allocated for current user, remains active until the parent process exits. The loop works until the fork function returns negative value. It means that we have reached the NPROC limit. Let’s look at the next code piece. The PID is negative, but we have to remember that there is one more shell user process that will be terminated soon. This process is the ADB daemon that is still running. We couldn’t kill it on start because the init process would start it again and it is an advantage for us. So, as soon as we reach that condition, we read the ADB daemon PID and check if its user id is AID_SHELL or AID_ROOT (because we could reach the condition from the second or third iteration).If it is AID_SHELL, the program just sends SIGKILL to it and continues the loop (soon, we will reach it again). Once the daemon is killed, one more PID for this user is freed. We have to allocate this PID for the AID_SHELL user as soon as possible to prevent the daemon setting its user id as AID_SHELL. Ideally, there will be two additional loops: the first one forks and allocates a new PID for the AID_SHELL user and, as the result, the second one reaches the limit again, checks the daemon PID that should be AID_ROOT and exits. However, because of lack of resources or lots of delays, there could be rather more iterations.
...

Code:


else if( pid < 0 )
      {
        printf( "limit reached. kill adbd and wait for its root ...\n" );

        adbdPid = get_pid( g_adbd_name );

        if( adbdPid >=0 )
        {
            if( get_pid_user( adbdPid ) != 0 )
            {
              kill( adbdPid, SIGKILL );
            }
            else
            {
              break;
            }
        }


...
To prevent the exploit infinite loop in case if it is impossible to start the ADB daemon as root, there is a respawn guard for each forked child. Ten iterations and one second timeout have been chosen empirically when I was working with several devices and I found that some devices had a too big NPROC limit. It is obvious. They enquire too much processor resources to handle all created child processes. So, you may change the guard to fit your requirements or device.
...

Code:


else
        {
            static int theRespounGuard( 10 );

            if( --theRespounGuard )
            {
              sleep( 1 );
            }
            else
            {
              break;
            }
  }


...

Configuration & Build


The exploit was configured to be built with the NDK toolset both on Linux, and on the Windows platform. If you are working on Linux, it will be enough for you to download NDK only; however, on the Windows platform, you have to download and install the Cygwin environment on your machine. In this paragraph, I will tell you how to configure and build the exploit on the Windows platform.
First of all, download and install the Android SDK. We need only a platform-tools package from the SDK to communicate with a device through ADB, so, at the SDK root directory, start the SDK Manager and check the platform-tools package. Install it.

You can add a path to platform-tools into your PATH variable or type the absolute path to the adb.exe executable any time later.

The second step is to download and install the Android NDK package and the Cygwin environment. Install them in the same location with SDK and add a path to your NDK package into the PATH variable or into your Cygwin .bash_profile. Then unpack a project archive attached to this article into your working directory available for Cygwin.
The project structure is very simple. In the AndroidExploit root, you will find two directories. In the bin directory, I have placed a precompiled exploit binary and a windows shell script file. The jni directory contains sources and the NDK build scripts.


Code:


/AndroidExploit
  /bin
      exploit          // precompiled binary file
      root.cmd          // windows shell script. It helps to upload and run
                        // the exploit in device. Usualy it is enough run
                        // the script to root device.
  /jni
      Android.mk        // NDK build script
      Application.mk    // some application settings
     
      // the source files
      cmdLine.cpp
      cmdLine.h
      impl.cpp
      impl.h
      main.cpp
      proc.cpp
      proc.h


To build the project, run the Cygwin environment, change a directory to the project/jni directory, and execute ndk-build. The Compiler output should look like this:

You can find an executable at libs/armeabi/exploit. The path is relative to the root of the project.

Running


The next paragraph describes how to use the binary file. You download the Android SDK, install platform-tools and make them available from the PATH variable. At first, enable the USB Debugging on your device. For this, from the main screen, go to Settings -> Applications -> Development and check the USB Debugging option, then connect your device to the PC and check that it has been detected by Windows Device Manager. Otherwise, install the Android USB drivers for your device from the manufacturer site.

Type the adb devices command in the command line. It will show you devices connected to your PC. If there are no devices connected, check that Windows Device Manager and Android USB drivers are installed.

We are on the right way! Let’s go to the device. Type the adb shell command, which will start the device shell, and then check your id to see who you are.

As it was expected, you are a shell user that has no privileges, no access, nothing … The only things you can do are installing programs and listing some directories. In other words, you can perform only permitted actions. I was very surprised when I couldn’t read /data/data directory, it was impossible for me to list it and see what programs were installed on my device.
Break the law. Go to the exploit bin directory and type adb push exploit /data/local/tmp. This command will upload the exploit in the device temporary directory available for the user. Then, type adb shell and change the directory to /data/local/tmp. The ls –l command will show you its content and permissions on recently uploaded files. Make the file executable by executing chmod exploit 776 and run it by ./exploit root.

The output shows NPROC and ADB daemon PID. Then, as soon as RLIMIT is reached, the shell will be disconnected. Wait for ~5 seconds and type adb shell again. As a result, you should see root # shell. Type id to make sure you are a root.

Yes, you are! Now, you can do anything even… let me think … even damage your device! So, all things you will do next are at your risk. Be careful!

One more, I want to add. The exploit works only on Android devices with versions 2.2 and older.



mercredi 12 août 2015

[Guide] How to Use XDA Forums And Threads: For [New Members]



I have had many people ask questions about how to use this website, so i thought i would take the time to make a guide to help out newer members that may be confused or overwhelmed by the wealth of information here. Hopefully this will help you to make a quick transition from a new member to an experienced member. I am basing this off of the website version (Dark theme 2015) on PC as it seems to be the most confusing for people. If you are using the mobile site, or app, then some of these options may not be available or may be located in a slightly different place. I have also left a few things out for the sake of simplicity. After reading this thread feel free to ask any questions that you have and i will try my best to clear things up. Some of the things we will discuss are...

~Settings
~How to set up your profile and preferences
~How to make friends
~How to make a signature
~What does my profile look like to others?
~Notifications
~How to change thread display options
~How to change the theme
~How to keep up to date with interesting threads
~How to find your previous posts
~XDA forum rules
~How to search for what you are looking for
~Your device page
~How to find the right download for your device in threads
~How to get help when you cant find the threads or answers that you are looking for
~How to post, reply, give thanks, etc. in threads
~How to rate threads and participate in polls
~How to report bad behavior
~How to attach photos to a thread
~How to donate to developers
~How to start a new thread
~Sending private messages
~How to upload photos to a private message
~And more!



Settings:
I think setting this up first is best. Click on settings button near the top right of your screen. Then you will find the XDA control panel on the left. Here you can setup/edit your XDA experience.

Edit your details
Here you will find a quick link to change the email affiliated with your XDA account or change your password. You can also add information that will show up to others when they view your profile such as your birthday, what device you are using, your personal website link, how to instant message you on other messaging networks, links to your social media accounts, the phone carrier that you are using, what city and country you are from, a short biography of yourself, your interests and hobbies, your work occupation, and how to donate to you (if you think your contributions to XDA will be worth a donation).

Profile privacy
Here you can edit what information you will allow others to see about you just in case you would like to keep some information more private.

Edit profile picture
Here you can add/edit a profile picture by either uploading a photo from your computer or phone, or entering a link to a photo from another website that you use such as dropbox.

Contacts & friends
Here you can select XDA users to add to your contacts or friends list. You can also find information on how to delete contacts here.

Social groups
Here you can search for social groups to join or start your own social group. Social groups are usually a grouping of people that have the same device, same interests, same cultural background, etc.

Pictures & albums
Here you can add picture albums to upload photos to for sharing with others here on XDA.

Edit avatar
Here you can add a photo that will appear under your username whenever you make a post.

Edit signature
Here you can add/edit a signature (text and/or photo) that will appear at the bottom of every post you make. You can hover over edit options with your cursor to see a description of what they do (like change color of text, change size of text, etc.). You can highlight a part of your signature and select an edit option to change only that part. Things that would be great to include in your signature would be your device model number, which ROM version you are using (stock is what came on your phone from the store, and custom ROM is like Cyanogenmod or other aftermarket ROM that was flashed by you or previous owner of device), which kernel version you are using, which android version you have (like 4.4.2 or 5.1.1), which baseband version you are using, which recovery version you are using (stock is what came on your phone from the store, and custom recovery is like Clockworkmod, team win recovery project, etc), any additional custom framework or modules that have been added to your device (like Xposed, Lspeed, etc. Do not list apps), or anything else that you think is important related to your device. If you are unsure, most of this info is available in android settings-about phone. Entering this info will help us to quickly answer your questions.

Edit email & password
Here you can change the email affiliated with your XDA account, change your password, or connect a Google+ account to your XDA profile.

Edit options
Here you can find additional privacy options, messaging and notification options to keep up with interesting threads, private messaging options, date and time options, and customize how the website looks to you including the theme.

Edit ignore list
Here you can add or delete contacts that you wish to ignore during your XDA experience.

List Messages
Here you can see any private messages that you have received or sent. You can also delete or save messages here as well as change the display options for your message list. An easier way to get to this list is by going into messages from the box labeled "messages" near the top right of your screen.

List subscriptions
Here you can view the threads that you have subscribed to in a nice and neat list.

Edit folders
Here you can add/edit folders that you want to keep subscribed threads organized in case you have a lot of them.

Attachments
Here you can view or delete any attachments that you have attached in previous posts.

Near the top right of the screen there will be a button labeled "notifications". Here you will get quick access to messages, mentions, quotes and statistics (statistics will be shown on same page as quotes. Here you can also find all posts made by you in the past, and all thanked posts made by you in the past), and update alerts for software you are using from subscribed threads.


Near the top right of the screen you will see the button for "Swappa". This is an online store for buying and selling devices and is recommended by XDA
.




Next read XDA forum rules if you haven't yet before going any further. Scroll all the way down to the bottom of the webpage and you will find a link for this as well as some other useful links. Or you can click here.



Finding the forums and threads that you are looking for
Now to find the best forums and threads related to your device, click on the search box near the top left of your screen and start typing any identifying words that relate to your device until you find it. Once your device is selected you will find specifications, forums, threads, information on how to root, ROM's, kernels, and tools/utilities that are related to your device. If you are not able to find your device, then use the search box for searching all forums to find forums and threads that may be related to your device. This may be needed if you have a very new, old, or less common device. You may have to select the settings icon to the right of this search box for advanced search options. If you are still not finding the information you need, then click on the XDA assist tab near the top left of your screen. Here you can start a new thread requesting help to find the information you are looking for. You can find the new thread button near the top left of your screen.

How to operate within threads
Now that you have found a thread that interests you, here is some information on how to utilize your resources to get the most out of it. The original post or OP is where you are going to find the most info and usually any downloads that are related to the thread. This is on the first page of the thread (sdk version is related to which android version you are running. Arm, arm64, and x86 version is related to which processor you have in your device). If you cannot find this info in your android settings, then search for your device specifications online. Read all of the first page now. If you still have questions about the thread, next use the search box at the top of the original post to find specific info within the thread. If you still have questions read through a majority of the thread before posting questions. Unless it is a new thread, most likely the answer to your question is in there somewhere. The newest posts will be towards the last page of the thread. If you still have questions its time to make a post in the thread.

Making a post in a thread
At the bottom of the thread page you will see an option for a quick reply. This is a basic reply with limited options. Not many people are going to notice this post especially in a busy thread. If you want a specific person to be alerted that you have made a post then you either need to mention them by adding text in your post like this... @ZipAddict or you need to quote another persons post by selecting the "reply" button at the bottom right of the post that you are replying to. If you would like to alert multiple people that you have posted, then you need to select the "multi-quote" button at the bottom right of each persons post that you are replying to followed by selecting reply. Once again if you hover over edit options at the top of the reply you are making, you will see a description of what each one does (like change the font, or hide text). Additional options are available below the text box and this is where you can add attachments to your post. If you are wanting to post several photos or videos, it can be easier to post a link to an offsite photo gallery like dropbox in your post itself.

~If someone has posted something that has helped you, then you are urged to hit the "thanks" button under that post regardless if you post a thank you.

~If someone is breaking the forum rules, then you are urged to hit the "!" button at the bottom left of their post and report them.

~If the thread has a poll (at the top of the thread), then you should participate. It only takes a second, and your opinion matters.

~You should rate the thread (at the top of the thread) immediately if it has helped you a lot. If not, give it a little time before rating and dont be quick to give a bad rating.

~If you benefit from software that you have used here, you should donate to the developer. Any amount is appreciated, and this will motivate them to keep providing the service that you use.

~Be patient and do not make another post about the same thing twice. If no one answers within 24 hours you could send a private message to the maker of the thread politely asking for direction.

Sending private messages
To send someone a private message you can either click on their username and select "send message", or you can go to your message list and start a new message by manually entering the username/s of who you wish to send a message to. If you are wanting to send attachments in a private message, then you can include a link to your offsite gallery just like we discussed above.



This is something I put together real quickly to point new members in the right direction and once again i did not go over every single option or detail. Feel free to ask any questions here, or to request more information regarding a certain topic though. And if you see any mistakes please point them out so that i can correct them. Also, if anyone would like to make photos or videos outlining these things, then i will be happy to add them and give credit. In the meantime i will attach photos as requested. Thank you for reading and good luck on your XDA adventures!:good::good:



How to install ze550ml CM12.1 over ze551ml CM12.1. (GUIDE)



Few of us were using the 551ml cm12.1 in 550ml.
Even twrp tends to give error when we try to install cm in 550ml.

The solution is simple.

1. Extract updater script from the zip of CM12.1 of 550ml.
2. Open the file with notepad++(I use this, recommended)
3. In the first line, just change the "Z008" to "Z00A".
4. Save the file, make a zip same as before.
5. Flash and Enjoy


Happy to share information.



[GUIDE] Application for Analysis of the Programs Installed on Android



Author: Apriorit (Device Team)

Permanent link: www(dot)apriorit(dot)com/dev-blog/304-android-package-analyzer

In this article, I will tell you about the process of my research and the results I’ve obtained. I will describe PackageAnalyzer program created as a supplemental tool that displays various data on applications installed in the system. The following is a short summary of its functionality and basic elements implementation.

Research Process. Results

First of all we need to obtain the Android OS source code. The official web-site provides the detailed instruction on downloading the source code from the repository. Following this instruction, I set up the program environment and began the download. At that moment 4.1 was the latest version of the source code available for download. That process took a while, as the overall size of the data received was nearly 15Gb.
What should we begin with? How to find a way to analyze such a volume of data under tight schedule…
It is a well known fact that programmers are rather lazy, which prompts them to optimize their work process in various ways, and I wasn’t an exception to the rule. I came up with an idea how to ease this process a little bit by creating a program that would scan all installed packages and display the information I need, namely activities, services, broadcastservices. What’s the point in it? Firstly, it provides arranged information on packages, which allows to outline those that are of a particular interest to me. But you cannot always define the activity purpose by its name. That’s why I modified the program by adding a function that allows you to run a separate activity from the acquired list.

As the result I outlined the list of Android system applications that might be of a special interest:

• com.android.browser
• com.android.contacts
• com.android.development
• com.android.email
• com.android.mms
• com.android.phone
• com.android.settings
• com.android.packageinstaller

The next step was the research itself.

What should I look for and pay special attention to? As we know, activity is launched with the help of Intent. To do this, we need to call the startActivity(Intent) or startActivityForResult(Intent,int) method, if we expect to obtain certain result, and pass to it the Intent we’ve already created. Intent is a kind of a package, which a sender fills with various data and sends to the recipient (activity) for analysis. Therefore I was tasked with identifying the activities capable of executing the instructions set in Intent, which are not described in the Android manual.
Activity life cycle begins with onCreate() method. In most cases, exactly this method extracts the data included into Intent. The getIntent() method is used for this purpose. Hence, equipped with Far, I started searching for classes with included getIntent() with further research of what happens inside of each class, what data is extracted from Intent, and for what purpose it is used. Using this algorithm, I went through each system package, which was planned to be researched.

Unfortunately, I couldn’t find any hidden possibilities in the system packages of Android OS. Perhaps, it happened due to shallow application research, for which I didn’t have much time, that didn’t allow me to go deep into the features of each application. But negative result is a result after all. I am sure that Google programmers did a great work to eliminate system vulnerabilities by the release of new Android OS – all loopholes, which I was trying to find, were covered.

Program Part. Package Analyzer


As I mentioned earlier, I created the PackageAnalyzer Android application that was mainly tasked with collecting and displaying various information on installed applications. Besides, additional service that checks the requested permissions in newly installed applications and warns about the potential danger was added to the program functionality.
Functionality

• Acquiring the list of installed applications;
• Acquiring the list of Activities, Services, Broadcast Receivers, Permissions;
• Launching a separate activity from the list;
• Notifying about potentially dangerous permissions used by the application;
• Service. Tracking the applications being installed and checking the permissions they request.

Appearance

The user interface consists of two activities.
When launched, the program acquires the list of all installed packages and displays it in the main activity. After a package from the list is selected, the second activity is launched. It displays the detailed information on the internal package components (activities, services, receivers, permissions).
In the “Activities” section, you can initiate the launch of any component from the list by clicking it. In this case, an attempt to launch it with the help of Intent will be made. If everything goes smoothly, the selected activity is displayed on the screen. But not all activities can be launched this way, as an attempt to acquire certain data from Intent that initiated the launched is made in many of them, in onCreate() method, and if some data is not actual or wasn’t found, the activity cannot be launched.
Any Android application requires a permission to perform an action. The list of requested permissions is displayed to a user before each installation. That means that in theory it allows a user to make himself secure against malicious software getting into a phone. But practice shows different results: most users simply do not pay attention to this list. This gives malicious software the opportunity to get into the phone and use the user means as it wants.
That is why the ScannService service was added to PackageAnalyzer program. Its main task is to check the permissions requested by new applications and to inform a user in case any potentially dangerous permissions are detected. Such permissions would include: sending and receiving SMS, making paid phone calls, access to your location, access to personal data (contacts, emails), and so on.
The permissions are checked for new applications, as well as for already installed ones. This check is performed at the PackageAnalyzer launch. Depending on the permissions requested, the indicators in are displayed in the main activity and in the Permissions section in one of three states.
Risk level:
- high;
- middle;
- low.
If a user allowed malicious software to be installed, ScannService shows the corresponding notifications and plays a sound signal.

By clicking the notification, you launch the activity with detailed information on the package. You can start/stop this service by clicking the button on the main activity.
The ScannService registers two BroadcastReceivers at launch. The first one gets the notifications on newly installed applications and initiates the check, and the second one starts the service in case of a mobile device restart.

Implementation

Information on installed applications is located in PackageManager, which can be acquired from the context:


Code:


1        PackageManagerpackageManager = context.getPackageManager();

We acquire the list of installed packages:


Code:


public List<String> getInstalledPackagesList()
{
    List<String> list = new ArrayList<String>();
    List<PackageInfo> packageInfoList = packageManager.getInstalledPackages( 
        PackageManager.GET_ACTIVITIES );
for( PackageInfo packageInfo : packageInfoList )
    {
        list.add( packageInfo.packageName );
    }
return list;
}


We acquire the list of activities located in the indicated package:


Code:


public List<String> getActivities( String packageName )
{
    List<String> list = new ArrayList<String>();
try
    {
        PackageInfo info = packageManager.getPackageInfo( packageName, 
PackageManager.GET_ACTIVITIES );
for( ActivityInfo activityInfo : info.activities )
        {
            list.add( activityInfo.name );
        }
    }
catch( Exception ex )
{
        ex.printStackTrace();
}
return list;
}


We acquire the list of services, receivers, and permissions the same way by passing the corresponding parameter to:


Code:


getPackageInfo(): GET_SERVICES, GET_RECEIVERS, GET_PERMISSIONS

BroadcastReceivers are declared with android: enabled="false" parameter in AndroidManifest.xml file, as by default the service is stopped. The receivers are inactive until a user launches the service. The components activity state is changed in the following way:


Code:


publicintonStartCommand( Intentintent, intflags, intstartId )
{
    setComponentEnabled(true, PackageInstalledReceiver.class );
    setComponentEnabled(true, OnBootDeviceReceiver.class );
...
}
publicvoid onDestroy()
{
    setComponentEnabled(false, PackageInstalledReceiver.class );
    setComponentEnabled(false, OnBootDeviceReceiver.class );
...
}
privatevoid setComponentEnabled(boolean enabled, Class<?> clazz)
{ 
int state = enabled ? PackageManager.COMPONENT_ENABLED_STATE_ENABLED
            : PackageManager.COMPONENT_ENABLED_STATE_DISABLED;
    getApplicationContext().getPackageManager().setComponentEnabledSetting(
new ComponentName( getApplicationContext(), clazz ), state, 
    PackageManager.DONT_KILL_APP );
}


It is necessary to check the activity of the service at program launch. To do this, you need to acquire the list of all started services and perform a search in it:


Code:


publicstaticboolean isServiceRunning( Context context, String serviceClassName )
{
    ActivityManager activityManager = (ActivityManager) context.getSystemService(
        Context.ACTIVITY_SERVICE );
    List<RunningServiceInfo> services = activityManager.getRunningServices(
        Integer.MAX_VALUE );
for( RunningServiceInfo runningServiceInfo : services )
    {
if ( runningServiceInfo.service.getClassName().equals( serviceClassName ) )
        {
returntrue;
        }
    }
returnfalse;
}


Summary

In conclusion, I would like to note that although I didn’t obtain any results after searching for hidden possibilities of Android system applications, I created an application for analysis of programs installed on a mobile device, which can be used in the future. The functionality of the program can be extended to obtain more detailed information on applications, as well as to provide security (detection of malicious software and so on).

All articles, code pieces, example project sources and other materials are the intellectual property of Apriorit Inc. and their authors.
All materials are distributed under the Creative Commons BY-NC License.