Related
A Boot Animation Taken From Artiven FX6
Nice to See it....
Nothing to Say about it Just copy it and enjoy..
Then you will see!
Please Friends HIT Thanks, If you like.
------------------------------------
Down-link :- "Click Below Link"
https://www.dropbox.com/s/226xjizw4ivbsvt/bootanimation.zip
------------------------------------
If you know how to install boot animation do it if not
do this:-
Note-- if Phone is rooted Its easy....!
Note-- Do Not unzip the zip file.
1, Download AFX6 Bootanimation.zip by Above link.
2, Download a Root Explore from Play Store / Market!
3, Install and give Permissions "Grant" by SU/Superuser
4, Open Root explore and Copy "Bootanimation.zip" which you Downloaded
5, Paste it in Root or System "../system/media".
5/a,There must be a file over write it. Address goes like (.../system/media/bootanimation.zip)
6, Accept all permissions system asked or su/superuser "Grant" All
That's all Reboot and Enjoy AFX6 Bootanimation
HiT Thanks, Please If You Like!
I HOPE YOU UNDERSTAND MY ENGLISH
TUTORIAL ROOT NOTE 10.1 (2014 ) 4G LTE
This manual is based on the same created by fellow forum Alucine2 of note3 of HTCMania and work of the plain root on XDA
But with the changes to the note 10.1 (2014 ) 4G LTE.
I am not responsible of the result to stay your tablet, you are free to follow the tutorial or not.
1 download official rom Sam Mobile.
here has been done with the Spanis hit fetches each of your country
2 download https://mega.co.nz/ #! UgJFUTCL ! NrME13 ... hrksHG0HjTtg4g
3 download root https://mega.co.nz/ Script #! QoQnmAQD ! U_dQMR ... i_gbyPDt9TDmmY
4 downloaded odin 3.07 http://forum.xda-developers.com/showthread.php?t=1738841
5 donwload I installed Cygwin 64 bit http://cygwin.com/setup-x86_64.exe , the original script does not work in Windows 7 64 -bit
7 we put these files in a folder:
root_de_la_vega_sdcard.zip
Odin- 3.07.zip
Universal- RDLV.ZIP
P605XXUAMJ2_P605OXXAMJ1_PHE.zip
Unzip 8th Universal- RDLV.zip in this folder c: \ URDLV
9 Unzip P605XXUAMJ2_P605OXXAMJ1_PHE.zip in this folder c: \ URDLV
10 Run the shortcut you have on the desktop called terminal cygwin64
11 execute these commands :
cd c:
cd URDLV
/ cygdrive / c / URDLV / URDLV.bat full c :/ URDLV/P605XXUAMJ2_P605OXXAMJ1_P605XXUAMJ1_HOME.tar.md5
12th After a couple of minutes will have this result:
code:
$ / Cygdrive / c / URDLV / URDLV.bat full c :/ URDLV/P605XXUAMJ2_P605OXXAMJ1_P605XXUAMJ1_HOME.tar.md5
================================================== =============================
This work is licensed under a Creative Commons
Attribution -NonCommercial - NoDerivs 3.0 United States License .
http://creativecommons.org/licenses/by-nc-nd/3.0/us
================================================== =============================
Root of the Vega Universal v0.2 - By DesignGears
Public Preview
================================================== =============================
MODE : full
FILE TYPE: md5
FILENAME : P605XXUAMJ2_P605OXXAMJ1_P605XXUAMJ1_HOME.tar.md5
Extracting Tar ...
Hex Editing System Image ...
Checking System Image Hook ...
Hooked System Image Successfully
Creating Odin Flashable Tar ...
ODIN FILE: P605XXUAMJ2_P605OXXAMJ1_P605XXUAMJ1_HOME_VEGA.TAR . MD5
DO NOT DISTRIBUTE FILES CREATED WITH UNIVERSAL ROOT OF VEGA
13 º in the output directory will have the file generated :
c: \ URDLV \ output \ P605XXUAMJ2_P605OXXAMJ1_P605XXUAMJ1_HOME_VEGA.tar.md5
14 ° This image is patched with ROOT MJ2 but without the MODEM MJ1 that needs to be thrown with ODIN , you can put the two things at once :
15 º to get the modem P605XXUAMJ2_P605OXXAMJ1_P605XXUAMJ1_HOME_tar.md5 unzip the file with winrar original ROM in any other folder created and then open the odin 3.07 has to be the non tiing 3.07 and flash the generated file in the folder c: \ URDLV \ output \ P605XXUAMJ2_P605OXXAMJ1_P605XXUAMJ1_HOME_VEGA.tar.md5 to place it in the PDA section of odin while flashing moden.bin file that we will remove the created folder to unzip the original rom . P605XXUAMJ2_P605OXXAMJ1_P605XXUAMJ1_HOME_tar.md5 and place it in the box once PHONE odin flashed the two files at the same time.
We hope to start the system.
After extracting the file contents Root_de_la_Vega.zip at the root of the tablet .
My Computer / [ SM- P605 ] / tablet /
root_de_la_vega.sh
root_files ( FOLDER )
RESET VERY IMPORTANT
After restarting delete the files
My Computer / [ SM- P605 ] / tablet /
root_de_la_vega.sh
root_files ( FOLDER )
RESET VERY IMPORTANT
Already Knox root your Tablet with 0x0
DEVICE STATUS CHANGE OFFICIAL KEEPING A COPY OF THE FORUM ROOT METHOD NOTE 3 CREATED BY YOKY_CO
http://www.htcmania.com/showthread.php?t=699145
1 Go to this post
http://forum.xda-developers.com/show....php?t=1574401
2 In the download section to download this link
http://dl.xposed.info/latest.apk
3 Install the downloaded application phone
4 open the application framework in paragraph give to install update
May We downloaded the application Wanam exposed playstore
6 Open the application and security check point system status false.
7 Reboot and we will have the official system .
THIS SYSTEM IS NOT NOTHING HAS CHANGED THE CONFIGURATION OR THE CONTENT OF THE TABLET BUT IN CASE YOU BACKUP
I cannot download the 1st and 2nd link. Thanks
Sent from my SM-N9005
The links for MEGA is corrupted.
But even if I correct them, and get to MEGAs site I get a message that the file(s) dont exist anymore.
Dont even know what files to look for ... :/
zooorgie said:
The links for MEGA is corrupted.
But even if I correct them, and get to MEGAs site I get a message that the file(s) dont exist anymore.
Dont even know what files to look for ... :/
Click to expand...
Click to collapse
Mate, Flash this with ODIN 3.07/09 in AP - http://techerrata.com/bigbiff/openrecovery-twrp-2.8.0.0-lt03wifiue.img.tar
Then reboot into recovery. It should boot into TWRP recovery.
Install the latest SuperSU file. Make sure it's on your device before starting this.
If you haven't changed your recovery this will make your KNOX warranty void = 1.
If you don't want that you should check out Towelroot thread, not sure if it works on the P605 however.
ultramag69 said:
Mate, Flash this with ODIN 3.07/09 in AP
Then reboot into recovery. It should boot into TWRP recovery.
Install the latest SuperSU file. Make sure it's on your device before starting this.
If you haven't changed your recovery this will make your KNOX warranty void = 1.
If you don't want that you should check out Towelroot thread, not sure if it works on the P605 however.
Click to expand...
Click to collapse
Hmm, I prefer CWM to TWRP though...
Rooted and flashed CM11 successfully !
All seems ok for now, except that the camera is not working...
Tried some fixes I found, but all I get is a lot of flickering .
The back camera seems to work though...
Since every "best way to root stock 4.3" guide for LB in this forum involves flashing a deodexed ROM from a region that might not be yours and taken from someone's phone that might be different from yours, I've decided to make this guide which will (I hope) help you make YOUR OWN pre-rooted flashable zip using YOUR OWN phone and an FTF for YOUR OWN region.
Just a mandatory precaution: I'm not responsible for whatever happens to you, your phone, your family, your house, your dog, your car, etc resulting from the use of this guide.
Here goes.
What's needed:
==========================
1. Your SONY Xperia SP running a rooted stock ROM. You might need to downgrade to 4.1.2 and root that.
2. A recovery. See: http://forum.xda-developers.com/showthread.php?t=2649923 (Note: I only use CWM. I have not tried Philz or TWRP.)
3. SONY PC Companion
4. Flashtool
5. su + busybox binaries
6. META-INF
7. SuperSU
8. Stock .266 kernel. You could make this yourself, but for the sake of simplicity, just use this one instead.
8b. Stock .201 kernel.
9. (Optional) be2_album for Bravia Engine fix.
The good part:
=====================
1. Follow this guide to download and make your own FTF file. This file will contain the stock firmware for your own phone and region.
2. Then follow this guide to extract the system folder, but stop at step 9.
3. Navigate to the "bin" folder inside the system folder you just extracted and delete anything that's <10 bytes in size. Those are symlinks which will be recreated automatically in the flashing process. (Ignore this step if there are no files smaller than 10 bytes. Anything larger than 100 bytes should NOT be deleted.)
4. Extract the META-INF.zip file you downloaded above and copy the META-INF Folder in the folder alongside the system folder.
5. You should now have 2 folders, META-INF and system.
6. Extract the su + busybox binaries and put them in system/xbin.
6b. (Optional) Extract be2_album and put it in /system/etc.
7. Zip the two folders (META-INF and system) using store only (no compression).
8. Congrats, you just made your own pre-rooted pure stock ROM. Copy this zip and SuperSU into your sd card and we're good to go.
How to flash:
================
This might sound familiar, because this part is the same as the other guides.
1. Boot into CWM.
2. Clear dalvik cache and wipe cache. (Optional: wipe data)
3. Flash the zip you just made.
4. Flash SuperSU.
5. Power off.
6. Flash kernel using flashtool.
7. Boot up your phone and enjoy (or not) using a ROOTED STOCK firmware that was meant for YOUR phone and not for someone else's phone in another country on the other side of the world.
8. (Optional) If you get a reboot when remounting (e.g. when using Foldermount), apply this fix.
As a side note: Memory management is kinda crappy on 4.3. Dropping dalvik.vm.heapgrowthlimit to 64m and dalvik.vm.heapsize to 96m helps somewhat, but YMMV. Please experiment on your own to find a limit that works best for you.
This guide will (in theory) work for ANY future official release as long as the partitions stay the same. I hope this will at least reduce the nagging the devs (especially DoomLord) gets for a root exploit for stock 4.3.
Nice one
Grrrreeeatt.. This what I looking for all this time..
Whereas just last night I'd stay up finding how the way to put my region stock fw flashed to my device with root via dsixda andro kitchen, but the update script f***ing my brain all day long..
5 times xperimental flashing, but nothing happen. All kind of error Stats 7, 6, 0, etc just appear..
deodexed rom is suck considering it's not came from my own region..
I will try soon..
=============================
Edit :
- in step 3, are u sure to delete <10 "bytes" file? Bcause nothing here below 10 bytes. Just 10 kb are there..
Sent from my C5302 using XDA Premium 4 mobile app
Thanks!
I have ROOT
nasroed said:
- in step 3, are u sure to delete <10 "bytes" file? Bcause nothing here below 10 bytes. Just 10 kb are there..
Click to expand...
Click to collapse
Yes, I'm sure. Ignore this step if there are no files smaller than 10 bytes. Anything larger than 100 bytes should NOT be deleted.
Okay I followed the guide step by step. I have removed anything that was 7 bytes.. The others are min 156 bytes and 178 bytes the others are going to KB. So now I have to put the SU+Busybox into Xbin, make a .zip and flash it, flash Su and kernel?
See attachment for files smaler then 10 bytes
After few flashtattemps i get installtion aborted on touch CWM and TWRP cant even find the files.
Also I got some errors due to missing paths via the updater.script. Worth taking a look there.
mrjraider said:
Okay I followed the guide step by step. I have removed anything that was 7 bytes.. The others are min 156 bytes and 178 bytes the others are going to KB. So now I have to put the SU+Busybox into Xbin, make a .zip and flash it, flash Su and kernel?
See attachment for files smaler then 10 bytes
Click to expand...
Click to collapse
Yes. The zip should contain 2 folders. META-INF and system. Can you give me a listing of what you zipped? This guide is exactly how I rooted my 4.3 and it works fine. Also, try using store only when zipping. Sometimes the recovery doesn't work with zips that are to aggressively compressed.
Sent from my C5302 using xda app-developers app
Followed the guide step by step and the problem I have is it wont flash. It says instalation aborted and there were some errors about paths?
I zipped the meta-inf and system folder.
Added to archive and seleted .zip and store.. After copying to SD and flashing I got instalation aborted.
I will try this later tho. I just need my phone in a few hours
Please send me the directory listing of what you zipped and I'll look into it.
Sent from my C5302 using xda app-developers app
quetzalcoatl2435 said:
Please send me the directory listing of what you zipped and I'll look into it.
Sent from my C5302 using xda app-developers app
Click to expand...
Click to collapse
I can also share the entire zip if you want xD
mrjraider said:
I can also share the entire zip if you want xD
Click to expand...
Click to collapse
Do whichever is easier for you. Hahaha.
Sent from my C5302 using xda app-developers app
edit:
I know the probem xD
It was a sort of my fault
zip file>firmware> meta-inf and System
There was an extra folder that did not needed to be there
Will try it later tho.
Alright back to testing.. Will flash my own zip when downgrading and rooting is done
---------- Post added at 07:22 PM ---------- Previous post was at 06:37 PM ----------
It worked!!! Thank you!
---------- Post added at 08:15 PM ---------- Previous post was at 07:22 PM ----------
http://forum.xda-developers.com/showthread.php?t=2682651
quick one question I'm on doomlord v5 and Ultimate PureXSP (.266). But got some reebots. When I change kernel to stock via flashtool my root will stay? (quite noob question :< )
Awesome - a rather clean method of rooting - inserting a modified meta-inf and su/busybox into the system file and flash it.
LocaMobile said:
quick one question I'm on doomlord v5 and Ultimate PureXSP (.266). But got some reebots. When I change kernel to stock via flashtool my root will stay? (quite noob question :< )
Click to expand...
Click to collapse
I don't think so, as there are very few and 'minor' changes to the system file...
[not going to 4.3 as I didn't like the lag - still mulling about it]
Edit: A question
For the necessary process, one needs to downgrade in order to install CWM, say .254.
If I flash the new modified system+meta-inf, plus the original .266 (kernel only), I am still on hybrid 254+266 system, yes?
[after all there are other sin files not replaced: eg loader, fota, partition, etc]
how big is the zip file after making the compression? is 1,08 GB normal?
noel_din said:
how big is the zip file after making the compression? is 1,08 GB normal?
Click to expand...
Click to collapse
So is mine...
headache59 said:
So is mine...
Click to expand...
Click to collapse
thanks, so its normal, will try in my C5302
Locked bootloader
hello...is this guide is applicable for locked boot loader also ?
Instructions are below. Just a warning that you'll be modifying system files and so things could go wrong. Be careful, take your time, and back up the files you are replacing along with a nandroid backup. I assume no responsibility if your phone breaks though. This process was developed by someone else and I am posting this on their behalf. I will help where I can, but google will be your best friend
Instructions for Nexus 5 running 5.1 ASOP and Nexus 5 running 5.1.1 Cyanogenmod 12.1
1. You need to be rooted with a custom recovery. I won't go into detail on how to do that since there are plenty of threads on xda-developers about it.
2. Download the correct .zip for you system and install them after booting into recovery
Instructions for Nexus 5 running 5.0.1 ASOP and Nexus 5 running 5.0.2 Cyanogenmod 12
1. You need to be rooted with a custom recovery. I won't go into detail on how to do that since there are plenty of threads on xda-developers about it.
2. Copy the correct 2 files to your phone. One set is for a Nexus 5 running 5.0.1 ASOP and the other is for Nexus 5 running 5.0.2 Cyanogenmod 12 . I plugged my phone into my windows computer and just placed them in the root of the "drive". From the phone's point of view this is /sdcard.
3. You now need to change the permissions of the 2 files. You have to put them in the /system/ folder before you can change permissions. /mnt/sdcard doesn't allow you to change permissions. So copy them to /system/ and change their permissions to 0644 (rw-r--r--). I use root browser for this.
4. Use root browser and move libbluetooth_jni.so to /system/lib/ and move bluetooth.default.so to /system/lib/hw. I would copy the original files to somewhere else first as a backup in case something goes wrong. Double check the permissions on the new files after you move them to their respective locations.
5. Reboot.
6. Installed Kevo and it stopped telling my my phone wasn't supported at this point and everything worked fine.
Please join the KEVO ALPHA Google Group to get the most recent version of the app. I have provided a link to the 1.0.15, but it may be out of date.
KevoForAndroid-1.0.15p.apk
KevoForAndroid-1.0.15p.apk 7.91MB
PLEASE CHECK THE FILES BEFORE YOU COPY THE OVER YOUR FILES, ELSE YOU WILL BREAK YOU BLUETOOTH
-As along as you keep a copy of your original files you can always paste them over the broken ones
ANDROID Stock 5.0.1 ASOP ONLY Files from Download Tab
bluetooth.default.so 2015-02-26 12:36 1.26MB is for 5.0.1 ONLY
libbluetooth_jni.so 2015-02-26 12:36 87.63KB is for 5.0.1 ONLY
ANDROID Stock 5.1 ASOP ONLY File from Download Tab
patched-bluetooth.zip
ANDROID 5.0.2 Cyanogenmod 12 Nightly ONLY Files from Download Tab
bluetooth.default.so 2015-02-26 12:33 1.31MB is CM12 5.0.2 ONLY
libbluetooth_jni.so 2015-02-26 12:33 112.45KB is CM12 5.0.2 ONLY
ANDROID 5.1.1 Cyanogenmod 12.1 ONLY(WILL NOT WORK ON CM12.1 running 5.1.0) File from Download Tab
cm12.1-patched-bluetooth.zip
PROCESS IF YOU DONT HAVE EITHER ONE OF THESE OS:
If neither one of these sets of files work for you. You can make your own. This process will take the whole day and a lot of goggling if you have never used Linux, Source Code, or compiled anything. Remember to always have have all files up to date, use Python 2.7 not Python 3+, have >100 gig of hard drive space, and google the errors when you see them in the terminal window.(you will see a lot if this is your first time). If you are familiar with all this then it will likely take about 2 hours and that is just for downloading the source code and compiling.
1. You need to be rooted with a custom recovery. I won't go into detail on how to do that since there are plenty of threads on xda-developers about it.
2. Get the android source code. Follow the instructions from Google or from your ROM on how to do this. Note that you'll need either a Linux system or an OSX system. (I used an Ubuntu and installed it on a extrahardive, but you can use a virtual machine as well) Also note that getting the source takes quite a while. It took around an hour for me and I have 100Mb down.
3. Edit a file from the hammerhead source. If you followed the instructions on getting the source, you'll find the file at device/lge/hammerhead/bluetooth/. The file is called bdroid_buildcfg.h. Open the file and add "#define BLE_VND_INCLUDED TRUE" (without the quotes) above the line "#define BTM_BLE_ADV......". Save the file.
4. Compile, again following the instructions from Google or from your ROM. Obviously this time will vary depending on the speed of your computer. it can take anywhere from 30 min to 2 hours.
5. Once the compile is done, we need to grab 2 files. out/target/product/hammerhead/system/lib/libbluetooth_jni.so and out/target/product/hammerhead/system/lib/hw/bluetooth.default.so. Save the files in a location you can access easily for copy to your phone.
6. Copy the 2 files to your phone. I plugged my phone into my windows computer and just placed them in the root of the "drive". From the phone's point of view this is /sdcard.
7. You now need to change the permissions of the 2 files. You have to put them in the /system/ folder before you can change permissions. /mnt/sdcard doesn't allow you to change permissions. So copy them to /system/ and change their permissions to 0644 (rw-r--r--). I use root browser for this.
8. se root browser and move libbluetooth_jni.so to /system/lib/ and move bluetooth.default.so to /system/lib/hw. I would copy the original files to somewhere else first as a backup in case something goes wrong. Double check the permissions on the new files after you move them to their respective locations.
9. Reboot. Kevo stopped telling my my phone wasn't supported at this point and everything worked fine.
XDA:DevDB Information
Kevo Working on Nexus 5, App for all devices (see above for details)
Contributors
BSME_SWeedon, scorchsta
Version Information
Status: Beta
Current Beta Version: 1.0.15
Beta Release Date: 2015-02-17
Created 2015-02-26
Last Updated 2015-05-21
Any chance you could rebuild for Android 5.1 for the Nexus 5?
ludwigmace said:
Any chance you could rebuild for Android 5.1 for the Nexus 5?
Click to expand...
Click to collapse
You will find the patched files for 5.1 here: https://groups.google.com/forum/m/#!topic/kevo-alpha/-bOQs8V6KU0
Can this be done for other devices? Like the Note series or others?
johnathankong said:
Can this be done for other devices? Like the Note series or others?
Click to expand...
Click to collapse
Yes if you go to https://groups.google.com/forum/m/#!topic/kevo-alpha/-bOQs8V6KU0 you will see the forums for different device support. I saw Note 4 has support.
Step 8 isn't entirely necessary
Just a heads up if you want to simplify your first post, that part of step "8" is not necessary:
8. Reboot into recovery. Using your recovery's file browser (TWRP has one, not sure about others), move libbluetooth_jni.so to /system/lib/ and move bluetooth.default.so to /system/lib/hw. I would copy the original files to somewhere else first as a backup in case something goes wrong. Double check the permissions on the new files after you move them to their respective locations.
Click to expand...
Click to collapse
In fact, as you already are using Root Browser to change the permissions, you can also use Root Browser to move the 2 files. Worked just fine for me and removes the need for TWRP or another reboot.
CJSnet said:
Just a heads up if you want to simplify your first post, that part of step "8" is not necessary:
In fact, as you already are using Root Browser to change the permissions, you can also use Root Browser to move the 2 files. Worked just fine for me and removes the need for TWRP or another reboot.
Click to expand...
Click to collapse
Thanks I have updated the steps. There is also a zip file to install now, which is a lot easier.
@BSME_SWeedon any chance you can update 6.0 marshmallow files?
@Scorchsta was the one who generated the files, but he has not had a working nexus 5 in a while and I am about to jump ship the the Nexus 5x. I might try to push ASH6.0 to my nexus 5 this weekend and see if I can generate the files. I will post them if I am successful
thank you so much. looking forward to it.
BSME_SWeedon said:
@Scorchsta was the one who generated the files, but he has not had a working nexus 5 in a while and I am about to jump ship the the Nexus 5x. I might try to push ASH6.0 to my nexus 5 this weekend and see if I can generate the files. I will post them if I am successful
Click to expand...
Click to collapse
Thank you thank be very much appreciate
Anyone seen updated libs for the n5 with marshmallow yet? For me its either wait to see if kevo works on new nexus or keep snoozing my marshmallow update on my n5
The latest alpha works with an unmodified library, albeit the unlock is sent through the phone not the deadbolt.
https://groups.google.com/forum/m/#!topic/kevo-alpha/8CoLWU4-29Y
Here's a flashable zip for 6.0.1 (MMB29K). BSME_SWeedon's instructions were great and, now that I know how to do it, I'll try to stay on top of future updates.
BSME_SWeedon, could you update the title to include 6.0.1?
Can you post some screenshots?
Got this merged in CM 13 Nightlies
http://review.cyanogenmod.org/#/c/137324/
Should be effective on the Mar 22 Nightly
Hiiiiii frnds......
I know u r in big trouble right now bcz u can't on your wi-fi (i was in trouble so)
If u install some bad rom in your moto g then sometime u can't on your wifi
It only stay at "turning on wi-fi" bt can't on...
If u have a that problem in your moto g ....then this tutorial is for you ...and if u don't have this problem in your moto g, then u will get this problem and u have to come again in this thread MARK MY WORDS
I made a zip file for fix that problem.... so first plz download that file from attachment
Requirements
1 ROOTED MOTO G
2 TWRP 3.0.0.2 (Other also worked)
3 ZIP FILE (in attachment)
4 ES FILE EXPLORER
5 CONCENTRATION AND BASIC KNOWLEDGE OF "TWRPing"
6-write this whole thread in notebook so it useful while TWRPing (else open this thread in computer )
So let's start
Step 1 - First extract zip file ... u will find "1234567890" folder(name)
Step 2 Copy that folder in this path SDCARD/TWRP/BACKUP
Step 3- now reboot in recovery (twrp)
Step 4- wipe data,system,dalvik cache ,cache
Step 5 mount all partitions
Step 6- now go in to restore backup
Step 7 - u will find backup name "skyraj" n two options 1 is Persist n 2 is system
Step 8 restore both partitions
Step 9 now again mount all partitions
Step 10 now go to file manager in twrp
Step 11 go in system path, u will find folder name as "skyraj" rename that folder as "etc"
So final path is system/etc/firmware/wlan/prima
Step 12 - now install cm latest nightly
Step 13 wipe cache n dalvik cache
Step 14- reboot moto g
Step 15- now try to on wi-fi ..... WI-FI ON
Njoy frnds...
NOTE
1- your mac address will change... and it's random set by me
(But u can change it by your self)
2 i m not responsible for anything goes wrong
3 just be sure to make a Nandroid backup
Hit THANKS if found useful.... it's encouraging me to post more threads