[TFQ][ROOT]Root Method[4.3][4.4][COOPTX]UPDATE
- Thread starter Cooptx
- Start date
I believed that I had provided all the information and warnings stating that this method is dangerous. But what on this site isn't dangerous? Anything that requires you to unlock your bootloader is dangerous.
Sent from my XT1034 using Tapatalk
Didn't work for me this method. Where it said "REBOOT INTO RECOVERY" the phone would boot up normal.
AFAIK, yes. I am unsure if you have to unroot and relock your bootloader before the update, but ota updates normally strip root rights
Sent from my XT1034 using Tapatalk
Interesting... Perhaps the recovery flash failed? Are you on JB or KK bootloader?
Sent from my XT1034 using Tapatalk
Okay, try connecting your phone to you computer, and type "adb reboot recovery" in Command Prompt
Sent from my XT1034 using Tapatalk
Sent from my XT1034 using Tapatalk
Is your phone booted normally, or in bootloader?
Try these two commands.
adb devices
fastboot devices
And tell me what you get back
Last edited:
In bootloader mode
adb devices come up as "list of devices attached"
fastboot devices come up as "te88309evs fastboot"
Try
fastboot reboot-recovery
fastboot reboot recovery
Or
Reboot normally, and rerun the adb command. Make sure USB debugging is enabled
Sent from my XT1034 using Tapatalk
this is what comes up when i press
fastboot reboot-recovery
fastboot reboot recovery
USB debugging is enabled
C:\Users\zan\Desktop\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastb
oot reboot recovery
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
C:\Users\zan\Desktop\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
Reboot your phone normally. Get out of the bootloader. Then run adb reboot recovery
Sent from my XT1034 using Tapatalk
Did that mate and twrp was showing and u was rite about it being buggy as hell. THXS ALOT MATE!!!!!!! ive tried all the method out there and urs work. THXS for taking the time out to help me mate.
To all the ppl that paul method 1 and 2 did not work this will WORK.:victory::victory::victory::victory::victory:
No problem
just remember to slap that thanks button on your way out :thumbup:Sent from my XT1034 using Tapatalk
Similar threads
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
55
Okay, so I have tested many different root methods on my Moto G. Somehow I managed to screw them all up! So here is how I got my root working. This method should work on Jelly Bean AND KitKat. This is my first guide, so if anything is missing, please notify me. DON'T GUESS! ask others for clarification. So far this is a Windows guide, I am unsure if this will work on Mac or Linux...
Code:#include /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. */
Notice: None of these files are my own, not even the method. I just took different files and methods and messed with them until I was able to get root.
Okay, so here we go.
Files Needed:
My root tools
ADB Tools - make sure to add to your Window's Path (step 4 and on)
Moto G drivers
Be sure to place "supersu.motog.zip" on the root of your device
Directions:
1)Unlock your bootloader
2)Reboot into Bootloader
3)Flash Logo Fix
4)Flash TWRP or CWM
5)Reboot into Recovery
6)Flash "supersu.motog.zip"
7)Reboot
Indepth Look:
UNLOCKING BOOTLOADER
Follow this guide from Motorola
REBOOT INTO BOOTLOADER
1) Type mfastboot reboot-bootloader into Command Prompt and hit enter
FLASH LOGO FIX
1) Type fastboot flash logo logo.bin into Command Prompt and hit enter
FLASH RECOVERY
If on JB 4.3
TWRP
1) Type mfastboot flash recovery trecovery.img into Command Prompt and hit enter
or
CWM
1) Type mfastboot flash recovery crecovery.img into Command Prompt and hit enter
If on KK 4.4
TWRP
1) Type fastboot boot 44trecovery.img into Command Prompt and hit enter
or
CWM
1) Type mfastboot flash recovery 44crecovery.img into Commander Prompt and hit enter
REBOOT INTO RECOVERY
1) Press the volume down button
2) Press the volume up button
FLASH "SUPERSU.MOTOG.ZIP"
1) Wait for screen to time out
2) Awaken device with the power button
3) Tap "Install"
4) Select "supersu.motog.zip"
5) Swipe to install
WARNING! The touch screen will be buggy. Just try the best you can. It is possible to install the zip, I have done it. Good luck!
REBOOT
1) Reboot your phone
[CREDITS]
Motorola - for Moto G
Google - for Android
Redmond Pie - for ADB setup guide
@lost101 - for Moto G USB Drivers
@oasoas014 - for 4.3 Bootloader
@paulobrien - for "supersu.motog.zip"
@a1Pha - for TWRP & CWM
@ffosilva - for Logo Clean Up
@danger2u - for trying with CWM
@Paulskiii - for skipping JB Bootloader flash first Brave man right here.
@daothanhduy1996 - for getting me into Android!
@lokeshsaini94 & @Lifehacker7 - for reminding me that who cares about warranties? Root that phone!
Message me if I used your work and forgot to credit you!4I uploaded a TWRP build that is fully functional on 4.4 bootloaders to the TWRP thread.
No need to downgrade your bootloaders any more.
ALSO:
No need for mfastboot, normal fastboot has worked fine for me for all purposes so far, at least on my Linux boxes.
You don't need to flash recovery, you can just boot it using "fastboot boot <image file>"4I have another method. This method doesn't require you to flash a custom recovery so you can keep the stock recovery if your just wanting to root.
1. I'm not sure if it will work without the bootloader being unlocked because I just did it without testing first. I hope someone can try this without unlocking the bootloaders if not, follow the OP and unlock the bootloaders, install drivers and adb.
2. enable usb debugging in developer settings
3. download the recovery you want to use. I prefer TWRP. http://xdaforums.com/showthread.php?t=2759058
4. download SuperSu and copy the zip to your sdcard. http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip
in a command prompt where ever and however you have adb and fastboot set up on your pc.
enter the following to reboot your phone into fastboot.
To boot a custom recovery without actually flashing it.Code:adb reboot bootloader.
TWRP or CWM will boot and you can flash the Superuser zip and still retain your stock recovery so you can still install OTA updates.Code:fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
OP... Please feel free to add this to the op if you would like.
Thanks and Happy Modding! :good:3
