This is merely a guide, I do not take credit for any methods or apps listed below. I am not a developer. The great people working on these apps and methods deserve all the credit and your donations, so please disparse accordingly.
BIG THANKS to @iKrYpToNiTe, @jcase, @geohot who worked on these apps. Also thanks to @mschumacher69 for some constructive discussions.
YOU AGREE BY PERFORMING ANY OF THE ACTIONS BELOW THAT I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE. EVERY DISCLAIMER STATED ON THE LINKS PROVIDED IS STILL 100% VALID.
A RECAP OF THOSE DISCLAIMERS IS THAT YOU WILL VOID YOUR PHONE'S WARRANTY AND NOONE ELSE BUT YOURSELF ARE RESPONSIBLE IF YOU DAMAGE YOUR PHONE!!!
I decided to compile a root guide for the Cricket variant of the Moto G falcon xt1032 running 4.4.2 (may work on other variants as well, not sure). I obtained full, permanent root with philz touch recovery (but it would work for any other recovery you may choose to use).
THIS METHOD DOES NOT REQUIRE A COMPUTER/PC/MAC/LINUX USB CONNECTION
1. Enable USB debugging
2. From the setting tab "security". Check the " unknown sources" box, so you can install apk outside of play store
3. In addition to all things below, you will need a file explorer. I find es file explorer to be the golden standard, but your preferred file manager will do
4. This Link below is for you to install towelpieroot.apk
http://forum.xda-developers.com/moto-x/themes-apps/root-towelpieroot-motorola-devices-t2825059.
The version 1.2 supports the xt1032 falcon. Big thanks to @iKrYpToNiTe for adding support for the Moto G! You will need this temporary or "tethered" root before you go to the next step, which is unlocking the bootloader with this app called Sunshine (link to thread given below). Towelpieroot is buggy at times, but if it doesn't work the first time, try a few more. It WILL work.
5. http://theroot.ninja/
Note that running Sunshine is not free, but the $25 is well spent! Just so you know, Sunshine will NOT charge you if the process fails.
6. After the bootloader is unlocked, UNINSTALL towelpieroot. This is important in order for you to proceed to the next step.
7. Once you unlock the bootloader, you need to run towelroot (link below)
https://towelroot.com/
This step will grant you full, permanent root. Tap on the "welcome to towel root V3" three times, then you should see a box where you can modify the modstring. By experimentation and trial, I found the modstring 1337 0 0 0 4 0 to be the one. Click "Make it ra1n" and you should have permanent, full root privileges!!!
8. Download your favorite root checker to verify root access!
9. Go to play store and install SuperSU, and do any necessary updates.
10. Go to play store and install busybox and do all necessary binary updates.
11. Go to play store and download a terminal emulator. This will aid you in flashing your recovery.
12. My personal preference is Philz Touch recovery, but I think it it fair to assume that any compatible recovery of your choice is appropriate to flash with this method (link below)
http://forum.xda-developers.com/showthread.php?t=2639583
Download the latest .IMG from the OP
13. Before you flash you may want to back up your stock recovery.
Open the terminal emulator.
(do not include quote marks, only what's inside them, including spaces)
Type "su" and hit the ENTER key
This will get you superuser access
Type "dd=if/dev/block/mmcblk0p32 of=/sdcard/stock-recovery-backup.img"
This will create a backup of your current STOCK recovery.
14. Now ,using your file manager, go to the philz touch recovery .img file you just downloaded and rename it into "recovery.img", then move it to the sdcard folder (storage root folder)
Note: there you should also see the backup recovery file "stock-recovery-backup.img" you just created
15. Open the terminal emulator
Type "su" to gain superuser access
Type "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p32
16. THAT'S IT!!!
Verify by powering off your phone, hold volume down and power button for 5 seconds, select recovery and you should have Philz touch recovery in your phone.
NEXT LOGICAL STEP WOULD BE TO BACKUP YOUR STOCK FIRMWARE IMMEDIATELY!
BE MINDFUL WHEN YOU HOP BETWEEN ROMS THIS PHONE HAS ONLY AN INTERNAL STORAGE, SO BE CAREFUL WHAT YOU FORMAT
Other than that, whoohoo!!!!
NOTE: ACCORDING TO SOME DEVS I HAVE COME ACROSS ARE TELLING ME STEP 7 IS NOT NECESSARY. YOU CAN TRY SKIPPING IT. UNFORTUNATELY MY BOOTLOADER AND ROOT ARE IN EFFECT, THEREFORE I CANNOT VERIFY THIS. YOU COULD TRY[emoji3]
Please, when you need app-specific support, you may get better answers in the respective forums, but don't be discouraged posting questions here. It took me great effort finding a way to root without a PC, and although i am not a developer, I have stumbled in enough obstacles to be of some assistance
XT 1032 Falcon from Cricket GSM 4.4.2 stock
Once you unlock ur bootloader, u don't need exploit apps such as towelroot to gain root, all you need is a custom recovery such as twrp. Once you flash it and reboot from it, it will tell you that you're not rooted, do u want to flash supersu to gain root access? Swipe to intall supersu and u're rooted...
mschumacher69 said:
Once you unlock ur bootloader, u don't need exploit apps such as towelroot to gain root, all you need is a custom recovery such as twrp. Once you flash it and reboot from it, it will tell you that you're not rooted, do u want to flash supersu to gain root access? Swipe to intall supersu and u're rooted...
Click to expand...
Click to collapse
Yes that is true if you wanna fastboot via USB, which means connecting the phone to a PC. I was under the impression that I could not flash a custom recovery from the stock one. I have been struggling to gain root because of non-access to a computer. It is a little more lengthy but I find this to be the only no PC guide around, since I've been looking for one for 4 months now. And most certainly I would not be able to flash a recovery from the terminal emulator if I did not have su.
Towelpieroot only gives a tethered, temp root with no r/w privileges to system. It would make it impossible to flash a recovery from the terminal without gaining full root. This is why you need to run the original towelroot with the modified modstring.
REMINDER: THIS METHOD DOES NOT REQUIRE A USB CONNECTION WITH A COMPUTET. ITS ALL DONE ON THE PHONE.
XT 1032 Falcon from Cricket GSM 4.4.2 stock
Thanks for the guide. I ran towelroot 1.2 and it crashes my phone ;( and v3 says it's not compatible
lmf said:
Thanks for the guide. I ran towelroot 1.2 and it crashes my phone ;( and v3 says it's not compatible
Click to expand...
Click to collapse
Towelpieroot is buggy (the dev states in his post). I had to try the process numerous times. What i think may work (or may have worked). Is you have to make sure that before running towelpieroot again youbhave to clear it from the recents. What i have done was clear it from recents, uninstall. Reboot phone. Install and run again. Once you get temp root you can continue the process.
On towelroot v3. It will say your device is not supported. Tap on "welcome to towelroot v3" twxt three times and a modstring modification box will appear showing numbers. Input the modstring posted above in the OP "1337 0 0 0 4 0" (with the spaces). Then it will give you root
Note: According to some devs i have come across are telling me step 7 is not necessary. You can try skipping it. Unfortunately my bootloader and root are in effect, therefore i cannot verify this. You could try. [emoji3]
THIS NOTE ADDED TO THE OP AS WELL
BBobby said:
Note: According to some devs i have come across are telling me step 7 is not necessary. You can try skipping it. Unfortunately my bootloader and root are in effect, therefore i cannot verify this. You could try. [emoji3]
THIS NOTE ADDED TO THE OP AS WELL
Click to expand...
Click to collapse
It is definitely unnecessary. Once you unlock ur bootloader, all you need to do is flash custom recovery and it would flash supersu for u which would give u root...
Towelroot uses an exploit to root, exploits are only needed on a locked bootloader. Unlocked bootloaders don't need exploits to be rooted...
mschumacher69 said:
It is definitely unnecessary. Once you unlock ur bootloader, all you need to do is flash custom recovery and it would flash supersu for u which would give u root...
Towelroot uses an exploit to root, exploits are only needed on a locked bootloader. Unlocked bootloaders don't need exploits to be rooted...
Click to expand...
Click to collapse
Would it be OK to download super su from play store directly?
BBobby said:
Would it be OK to download super su from play store directly?
Click to expand...
Click to collapse
You wouldn't be able to download it directly. Once you unlock the bootloader, you flash custom recovery such as twrp, then when u reboot from twrp (or any other custom recovery), it would tell you that you're not rooted, would you like to install supersu? Swipe to install it and you're rooted. Then you can update supersu from the play store.
mschumacher69 said:
You wouldn't be able to download it directly. Once you unlock the bootloader, you flash custom recovery such as twrp, then when u reboot from twrp (or any other custom recovery), it would tell you that you're not rooted, would you like to install supersu? Swipe to install it and you're rooted. Then you can update supersu from the play store.
Click to expand...
Click to collapse
But my questions continue to be:
1. How do I flash a custom recovery from the stock one?. Will the terminal commands still be effective? Or an .IMG file flasher app like rashr will be effective without initial root?
2. Is it bad to just run towelroot V3 and gain permanent root in less than a minute, then just download super su and continue?
I just posted what has worked for me. I am thankful for your input and persistent suggestions. But like I said it has worked for me the way it is described in the OP. I just don't think it is necessary to fix what is not broken.
BBobby said:
But my questions continue to be:
1. How do I flash a custom recovery from the stock one?. Will the terminal commands still be effective? Or an .IMG file flasher app like rashr will be effective without initial root?
2. Is it bad to just run towelroot V3 and gain permanent root in less than a minute, then just download super su and continue?
I just posted what has worked for me. I am thankful for your input and persistent suggestions. But like I said it has worked for me the way it is described in the OP. I just don't think it is necessary to fix what is not broken.
Click to expand...
Click to collapse
1. Yes you can flash a custom recovery via a terminal emulator, but you would need root to be able to do it without using a PC.
2. I wouldn't say bad, it's rather unnecessary especially that it uses an exploit to gain root. You wouldn't know what unnecessary changes it makes to your system in order to be able to gain root.
mschumacher69 said:
1. Yes you can flash a custom recovery via a terminal emulator, but you would need root to be able to do it without using a PC.
2. I wouldn't say bad, it's rather unnecessary especially that it uses an exploit to gain root. You wouldn't know what unnecessary changes it makes to your system in order to be able to gain root.
Click to expand...
Click to collapse
The guide is about NOT using a PC. Its in the topic, in the OP, in my posts... Then yes, its necessary to gain some sort of root (permanent, in the towelroot case) to run the terminal emulator.
Two birds with one shot.
Moto G (XT 1032) from Cricket. Unlocked Bootloader, Rooted, Stock ROM (4.4.2) with Xposed tweaks
BBobby said:
The guide is about NOT using a PC. Its in the topic, in the OP, in my posts... Then yes, its necessary to gain some sort of root (permanent, in the towelroot case) to run the terminal emulator.
Two birds with one shot.
Moto G (XT 1032) from Cricket. Unlocked Bootloader, Rooted, Stock ROM (4.4.2) with Xposed tweaks
Click to expand...
Click to collapse
Fair enough, but I don't see why you wouldn't want to use a PC. It's safer if u use a PC because u wouldn't be using any exploits...
mschumacher69 said:
Fair enough, but I don't see why you wouldn't want to use a PC. It's safer if u use a PC because u wouldn't be using any exploits...
Click to expand...
Click to collapse
Do you even read the posts? I have not had a PC or access to one (yes, people like me exist). I have looked for months on end and once I came across towelpieroot it all became possible. Then jcase released sunshine and that all put it together in a working method. This is the collection of hour of searching. If anyone like me does not have PC access it is still possible. But I wouldn't want others to have to go through that frustration
Moto G (XT 1032) from Cricket. Unlocked Bootloader, Rooted, Stock ROM (4.4.2) with Xposed tweaks
Thanks for the useful guide.
Once you do all of this what can be done . Does this mean the device is carrier free or just allows to install any variant of android on it.
Also even after doing all of these things how one can activate it on a different network than it is bought to be used on.
Sorry i am newbie to flashing software.
Thanks
Mars
This is a guide to root this device. That means you have access to the operating system files. By getting this access it allows you to modify the system in many ways. It also allows you to install custom ROMs. Gaining root has so many uses I cannot list here.
But no, this is not a carrier/SIM unlock.
How about the 4.4.4 cricket XT1046 seems to be impossible at this point?
When I get to the step on gaining temporary root it just keeps loading and loading and it never gives me root.. Like I went on and off multiple times and it still won't work
BBobby said:
But my questions continue to be:
1. How do I flash a custom recovery from the stock one?. Will the terminal commands still be effective? Or an .IMG file flasher app like rashr will be effective without initial root?
Click to expand...
Click to collapse
Rashr needs root to flash images and zips
Edit: I didn't saw that you already have been answered
Related
[GUIDE] Root & recovery WITHOUT oem unlock & wipe (2.3.2 & older, plus now 2.3)
UPDATE #2 - Fitchman has reported successful root and rom flash without unlocking the bootloader by using Ginger Break. Full details in this post: http://forum.xda-developers.com/showpost.php?p=13236136&postcount=135
UPDATE - IMPORTANT: This method does not work with Android 2.3.3. Search the forum or this post in this thread for a way to update to 2.3.3 and root without unlocking if you haven't updated yet.
Alternatively, use this method on 2.3.2 and lower, then use titanium to back up everything, store it on your laptop (along with all your sdcard's data), then do the oem unlock step first and then continue from there with the rest of the guide.
Not my original idea, but a consolidation of a discussion between inakipaz and shrivelfig and myself in another thread and being posted here for easier finding by future root-seekers.
Shrivelfig's tested the method to re-root a previously rooted pone with a re-locked bootloader, and inakipaz has done it on a phone that's never had the bootloader unlocked.
The advantage here is that those who chose not to root when they first got the phone won't lose any app data or sdcard data like the methods that have you unlock the bootloader do. The disadvantage is your bootloader remains locked, which may prevent you flashing certain things in the future.
edit: see ravidavi's posts below; he's shown you can even flash custom roms that are clockwork compatible while having a locked bootloader with this method.
Download these two files:
clockwork recovery v3.0.0.5 or clockwork recovery v3.0.0.5 mirror if above not working
su-2.3.6.1-ef-signed.zip
Koush's blog for the latest clockwork updates (find Nexus S in the list).
Also, if you don't already have the necessary android sdk and drivers on your computer, get them from here: http://developer.android.com/sdk/index.html and install them. Some Windows users report better luck just installing pdanet. There's a decent guide for Windows users on installing the sdk here.
Place the recovery file on your laptop where you can access it while using the sdk fastboot commands.
Place the su zip one in the top level folder of your sdcard.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the excellent instructions that Allgamer gives in this GUIDE, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps below.
To navigate in the clockwork recovery, you use the volume keys to scroll up/down through the menus, and the on/off button to select what's highlighted.
(note: some report success without these first 3 steps, others don't get a succesful root without, I recommend doing them)
select mounts and storage.
select mount /system
select go back
select install ZIP from sdcard
select choose zip from sdcard
select su-version#-signed.zip file you downloaded earlier
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
After the phone reboots, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
This method doesn't install busybox, so go to the Market and download/install busybox directly, or get Titanium Backup and check it's "problems?" button and let it install busybox for you. There's also an app called root checker that supposedly verifies you have a working root on your phone.
Once you have a successful root installed, I'd suggest getting back into clockwork recovery and running a nandroid back up from clockwork's backs and restore menu. Then copy that file from your sdcard (in the /clockwork/backups folder) to your laptop for safe-keeping and an easy full system restore to a known working config.
Usual disclaimers about I'm not responsible for damage to your phone or loss of data apply. Use any rooting method at your own risk.
Thanks and all the real credit go to inakipaz, shrivelfig and allgamer, and of course to koush, and ChainsDD for the superuser apk.
Worked perfectly. I used fastboot from my Mac (outlined in the stickied Mac Root thread). Root checker verifies that I have root.
And by the way, my phone and I are both root/ROM cherry. First android phone, first time rooter. Will work up the guts to flash a ROM soon, but of course there's no chance of doing THAT without unlocking the bootloader.
Thanks to all involved in this!
yeah! good work!
Srsly. Awsom.
Someone sticky this....
Question: When you do the fastboot boot command, does that overwrite the stock recovery with Clockwork? Or is it just booting into the recovery img without actually flashing it?
I would think this method also gives you a way to back up before unlocking the bootloader.
1) fastboot boot into Clockwork as described here
2) Full nandroid backup from Clockwork
3) Mount "SD" from Clockwork over USB, copy everything to computer (since it wipes everything)
4) Go back and unlock the bootloader as usual, resulting in a full wipe
5) Flash Clockwork Recovery again through whichever method
6) Mount "SD" from Clockwork over USB, copy the backup back to phone
7) Restore nandroid
And now you've unlocked the bootloader without amnesia =)
ravidavi said:
And by the way, my phone and I are both root/ROM cherry. First android phone, first time rooter. Will work up the guts to flash a ROM soon, but of course there's no chance of doing THAT without unlocking the bootloader.
Thanks to all involved in this!
Click to expand...
Click to collapse
Are you sure you need to unlock the bootloader to flash a ROM? Now that you have root, try installing ROM Manager from the Market, and see if it lets you flash custom recovery with bootloader still locked. If so, then yes you can install a ROM!
Also, the fact that you're able to boot into Clockwork using "fastboot boot" - that also means you can install a ROM .zip file right from there.
cmstlist said:
Question: When you do the fastboot boot command, does that overwrite the stock recovery with Clockwork? Or is it just booting into the recovery img without actually flashing it?
Click to expand...
Click to collapse
"fastboot boot" only launches the recovery no unlock needed. "fastboot flash" flash the recovery
cmstlist said:
Are you sure you need to unlock the bootloader to flash a ROM? Now that you have root, try installing ROM Manager from the Market, and see if it lets you flash custom recovery with bootloader still locked. If so, then yes you can install a ROM!.
Click to expand...
Click to collapse
It worked! Here's the process I used, starting from a completely unmodded Nexus S.
1: Use the method detailed here to gain root access without unlocking the bootloader.
2: Using a root-enabled file explorer (I used Super Manager), rename install-recovery.sh (in /etc) to install-recovery.sh.old . You'll need to remount as r/w to do this. NOTE: You don't *have* to do this step, but if you don't, then you can only use clockwork once after which it will be erased on reboot.
3: Using ROM Manager, install Clockwork Recovery.
4: Pleasure yourself, because your bootloader is still locked and nothing was erased.
I have yet to try actually flashing a custom ROM. Does this mean that it can also be done without unlocking bootloader?
Well damn, whaddaya know. I just flashed MoDaCo r10 without unlocking the bootloader, and without losing any personal data on /sdcard.
I figure someone at XDA should like this.
Pretty much followed distortedloop's advice. Starting from a fully stock Nexus S with Android 2.3.2 (GRH78C):
* Root using the method on this thread.
* Rename install-recovery.su to install-recovery-old.su. (in /bin)
* Install Clockwork Recovery from ROM Manager.
* Download whatever ROM you want (compatible with Clockwork), rename to update.zip, and copy to sdcard.
* Reboot into Clockwork.
* Wipe cache, reset to factory (IF REQUIRED BY NEW ROM). This was my first install of MoDaCo, and that requires it. This step does NOT erase your personal files on sdcard, just all android-related files.
* Install update.zip from Clockwork.
* Continue self-pleasuring ... you now have a custom rom without touching your bootloader or wiping your personal sdcard data.
Maybe it's just because I'm a noob here, but it seems to me that this is a BIG deal. All root/ROM installation methods that I've seen so far have required an unlocked bootloader. This seems to be the first time a Nexus S has been unlocked and custom-ROM'd without unlocking the bootloader and wiping the entire /sdcard.
Ravi
Yeah, it's pretty clear that the unlock the bootloader step isn't necessary for most of what we want to do. Just a habit from earlier devices, perhaps?
What's really odd is now we have to wonder what's the purpose of the oem unlock erasing your sdcard? Speculation was that it was a security feature to keep people from accessing your data if they stole your phone; they couldn't flash something on the phone to get access, but clearly they can. Fastboot into a custom recovery and you own the phone.
Perhaps this is a security hole Google will try to fix some day?
At any rate, I wish we'd discovered this sooner, it would have saved several people some grief in having to lose saved games (Angry Birds!) when they finally decided to root.
distortedloop said:
Yeah, it's pretty clear that the unlock the bootloader step isn't necessary for most of what we want to do. Just a habit from earlier devices, perhaps?
...
At any rate, I wish we'd discovered this sooner, it would have saved several people some grief in having to lose saved games (Angry Birds!) when they finally decided to root.
Click to expand...
Click to collapse
You say "for most of what we want to do." Could you think of a case where you would need to unlock it now? It's now shown to be unnecessary for rooting and installing custom recovery/ROM.
Is there any way to get the word out? This thread isn't stickied, and all the stickied threads on rooting & custom ROMs currently assert that you have to unlock the bootloader.
Ravi
ravidavi said:
You say "for most of what we want to do." Could you think of a case where you would need to unlock it now? It's now shown to be unnecessary for rooting and installing custom recovery/ROM.
Click to expand...
Click to collapse
I'm thinking that something like Superboot might need to have the bootloader unlocked, since it replaces the boot image, right? But I'm not sure.
ravidavi said:
Is there any way to get the word out? This thread isn't stickied, and all the stickied threads on rooting & custom ROMs currently assert that you have to unlock the bootloader.
Ravi
Click to expand...
Click to collapse
There's only a page and a half of posts in the development section right now, so it's not likely to disappear any time soon, but you could ask a mod (theimpaler747 is ours) via PM to sticky it. I thought about asking myself, but seemed a bit tacky to ask for my own thread.
Meanwhile, I'd been linking people to various posts I'd made in other threads suggesting this might work, but once inakipaz and shrivelfig confirmed it, I'm just now pointing people here. I just hope people see this before wiping their phones unnecessarily.
Really, the other guides should just be updated to skip the oem unlock step. That's really the only different thing we're doing here.
i'm just waiting for more people "newbies" to confirm this actually works for them, before making it a sticky
In theory if you really really screw up your phone, you might need fastboot flash in order to recover it. But if fastboot also lets you boot into an img recovery... then you still have a recovery route that doesn't require unlocking.
Sent from my Nexus One using XDA App
I know it's a noob question and all since all you're doing is flashing a custom recovery but will you still be able to get OTA updates after doing this as well?
Sent from my Nexus S using XDA App
qreffie said:
I know it's a noob question and all since all you're doing is flashing a custom recovery but will you still be able to get OTA updates after doing this as well?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
yes because you still have the original recovery installed
distortedloop said:
Perhaps this is a security hole Google will try to fix some day?
Click to expand...
Click to collapse
This would be my guess.
But how? Is it possible to plug this with just a software update? Time will show, I guess.
This (security hole) should also make it possible to do perfect out-of-the-box OS backups. And restores. The problem is that nobody's going to do a backup without playing with their shiny new toy first.
shrivelfig said:
This would be my guess.
But how? Is it possible to plug this with just a software update? Time will show, I guess.
This (security hole) should also make it possible to do perfect out-of-the-box OS backups. And restores. The problem is that nobody's going to do a backup without playing with their shiny new toy first.
Click to expand...
Click to collapse
I can confirm that the Nexus One does not allow this "fastboot boot" on a locked bootloader. Maybe this was just an oversight?
It is entirely possible to plug this with a software update: Samsung/Google could issue a signed update that includes a bootloader upgrade. This has been done many times by HTC for example.
I can confirm that this method works, without unlocking the BL or erasing the SD part.
This is pretty cool. I wish I new about this before I unlocked the bootloader days after I received my phone. I too wonder if this was intentional or an oversite. Google did want this phone to be for developers, but like other's said, this is also a bit of a security hole. The wiping of the sd card on unlock would protect the person if the phone was stolen, like if there was confidential corporate stuff on there. Even if you password protect your phone, someone could fastboot clockwork, mount the sd card and retrieve all the information that was on there.
cmstlist said:
It is entirely possible to plug this with a software update: Samsung/Google could issue a signed update that includes a bootloader upgrade. This has been done many times by HTC for example.
Click to expand...
Click to collapse
It's also been done by Samsung with some versions of the Galaxy S line (some of the "leaked" roms, and even one official kies push (IIRC) changed the bootloader, causing people the ability to use 3 button mode for Odin access, and causing others to lose it.
Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
tigas68 said:
Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Click to expand...
Click to collapse
spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
thanks. :good:
tigas68 said:
thanks. :good:
Click to expand...
Click to collapse
Still isn't working...
When i tried to fastboot the recovery img the device turns off and never turns on again on is own!
Help please!
I like my root...!
here's the screens of waht happens.
This his what happens when i try to go into recovery mode...
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
zephiK said:
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
Click to expand...
Click to collapse
zephiK,
Already done that! I flashed the CWM recovery throught fastboot. The device turned off. When i turn it on again and tried to go into recovery mode, so i can flash the SU from chain fire, but got the image on my post!
The phone is unlocked!
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Johnsonyc said:
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
Click to expand...
Click to collapse
I used the sctock rom downloaded from the google developers website!
Johnsonyc said:
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Click to expand...
Click to collapse
What he said. The recovery flash isn't going through.
Sent from my Nexus 4 using Tapatalk 4 Beta
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Johnsonyc said:
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
Click to expand...
Click to collapse
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
sn0warmy said:
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
Click to expand...
Click to collapse
I don't even really use root explorer anymore just like having the ability to make nandroid backups. But after doing a clean install of 4.3 in fastboot and it only took 30 minutes from start to finish including app and data restores nandroids to me are not that useful anymore (I don't flash custom ROMs anymore). Google automatically re-installed all my apps as soon as I reconfigured my WIFI, they also restored my APN and my work WIFI settings but not Bluetooth. And I used Helium to restore the user app data and all my texts and helium doesn't need root access to work.
Here is the start of Koush's post on Google+ where he talks about superuser on 4.3.
I finally had a chance to dig into seeing why Superuser is broken on Android 4.3. https://android.googlesource.com/platform/dalvik/+/9907ca3cb8982063a846426ad3bdf3f90e3b87c2
Basically /system is mounted as nosuid to any zygote spawned process (ie, all Android apps). Root will still continue to work via adb shell, etc.
This is a pretty nasty change. It seems that SuperSU works around this by replacing install-recovery.sh to run a su daemon that pipes subsequent through it. Pretty hacky, but understandable why it was done this way.
Will need to look into how to do this in a less invasive fashion, if that is even possible. Of course, if building from source, this change can simply be reverted.
Here's a better explanation about superuser from Android Police.
http://www.androidpolice.com/2013/0...n-but-chainfires-supersu-works-and-heres-why/
Rooting for me is used for restoring my apps and stuffs using titanium backup. Another useful thing about rooting is the ability to check saved wifi passwords.
Just install twrp from fastboot and then flash the su zip file in twrp
Sent from my Nexus 4 using Tapatalk 2
EddyOS said:
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
Click to expand...
Click to collapse
@EddyOS
Your answer is what forums are not about! Instead of helping you had an atitude of an ass...!
@ Everyone else
After 5 or 6 attemps, doing it by the book, the CWD worked and i now have a Recovery mode! I didn´t did anything different, so i couldn´t really understand what went wrong before... SU from chainfire works perfectly! It´s now Rooted! And yes, the tuturials are idiot proof!
There´s something that´s bothering my mind... I can´t unistall some trash that cames with the 4.3 version using titanium backup, because he can´t find the apk files...! I could do it with the 4.2.2 version, but not with this one. I'm using the deoxed version.
Does anyone has the same problems?
This is not my work, and I can not vouch if it works or not as I am a US Cellular customer and don't have a working version of 4.4 on my device. This was posted on Reddit. Link and entire post to follow:
Video "proof":
http://www.youtube.com/watch?v=NP9WXLIzhTY&feature=youtu.be
http://www.reddit.com/r/MotoX/comments/1r3y30/root_achieved_for_44_kitkat_on_my_dev_edition/
------------------------------------------------------------------------------------------
[–]8bitremixguy 1 point 33 minutes ago*
I want to first say that I did not figure out this method on my own, I saw it on Google+ via Matthew Pierce and modified it to make it easier to follow
Second, do not try this on a device with a locked bootloader. You need the unlocked bootloader to do this.
You'll want to first download these 2 things
1) Superuser zip to be installed in recovery (from Chainfire) -> http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
2) New TWRP for 4.4 KitKat (from Hashcode)-> http://forum.xda-developers.com/showthread.php?t=2534850
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues. After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (use the motorola fastboot binary)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!
If you do this correctly you will regain root.
------------------------------------------------------------------------------------------
Again, don't kill the messenger! I figured I would pass this information along.
i.Design said:
This is not my work, and I can not vouch if it works or not as I am a US Cellular customer and don't have a working version of 4.4 on my device. This was posted on Reddit. Link and entire post to follow:
Video "proof":
http://www.youtube.com/watch?v=NP9WXLIzhTY&feature=youtu.be
http://www.reddit.com/r/MotoX/comments/1r3y30/root_achieved_for_44_kitkat_on_my_dev_edition/
------------------------------------------------------------------------------------------
[–]8bitremixguy 1 point 33 minutes ago*
I want to first say that I did not figure out this method on my own, I saw it on Google+ via Matthew Pierce and modified it to make it easier to follow
Second, do not try this on a device with a locked bootloader. You need the unlocked bootloader to do this.
You'll want to first download these 2 things
1) Superuser zip to be installed in recovery (from Chainfire) -> http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
2) New TWRP for 4.4 KitKat (from Hashcode)-> http://forum.xda-developers.com/showthread.php?t=2534850
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues. After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (use the motorola fastboot binary)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!
If you do this correctly you will regain root.
------------------------------------------------------------------------------------------
Again, don't kill the messenger! I figured I would pass this information along.
Click to expand...
Click to collapse
I tried yesterday and it works flawlesly, just to remenber that you need an unlocked BL , basically you will gain root on any unlocked boatloader as you can install TWRP or CWM
unlocked bootloader </thread>
jcase said:
unlocked bootloader </thread>
Click to expand...
Click to collapse
Ha. Classic.
I wasn't aware that this was the case with unlocked bootloaders. I just came from my S3 where an unlock method was readily available when I purchased the phone. In either case, I think this information is useful for noobs (such as myself) if unlocking the bootloader is an option (like myself).
Also, I hope you're having luck with the new root method for non-dev variants, jcase.
Fastboot
beelzebu said:
I tried yesterday and it works flawlesly, just to remenber that you need an unlocked BL , basically you will gain root on any unlocked boatloader as you can install TWRP or CWM
Click to expand...
Click to collapse
Where can I find info for installing Motorola fastboot files for KitKat?
downloading the tmo retail 4.4 from motorola has the necessary files.
Fastboot
beelzebu said:
downloading the tmo retail 4.4 from motorola has the necessary files.
Click to expand...
Click to collapse
I am looking for the fastboot command file to flash the TWRP image. Can you please provide me with the link.
Thanks.
rooting a phone with an unlocked bootloader is something a toddler could do
Fastboot
BaconDrips said:
rooting a phone with an unlocked bootloader is something a toddler could do
Click to expand...
Click to collapse
Agree.
Usually flash using the fastboot command in the SDK-platform-tools.
Comments suggest that that will not work and I need mfastboot, motorola binary. Unfamiliar with that one.
Appreciate a constructive comment. We all have to start somewhere.
Thanks.
Searched a lot of forums and couldn't really find anything.So basically the problem is I rooted my nexus 4(Using Kingo Android root) and everything went quite successfully.I saw the bootloader screen and the menu came up,etc.However once I installed some applications which require super root access It gave the error "The phone is not rooted" so I downloaded a root checker and it also confirmed this.However I can access the Android recovery if I hold the right keys and there is an unlock icon when I boot up my phone.Not really sure why this is happening.
p.s:I'm not really used to the technical jargon as I am a relatively new user to android.
Thanks
Omegao said:
Searched a lot of forums and couldn't really find anything.So basically the problem is I rooted my nexus 4(Using Kingo Android root) and everything went quite successfully.I saw the bootloader screen and the menu came up,etc.However once I installed some applications which require super root access It gave the error "The phone is not rooted" so I downloaded a root checker and it also confirmed this.However I can access the Android recovery if I hold the right keys and there is an unlock icon when I boot up my phone.Not really sure why this is happening.
p.s:I'm not really used to the technical jargon as I am a relatively new user to android.
Thanks
Click to expand...
Click to collapse
do you have Superuser or SuperSu on your phone. Do you have busybox installed? Do you have a custom recovery installed? Personally I never heard of the the toolkit you used. I used Wugs when I did mine
playya said:
do you have Superuser or SuperSu on your phone. Do you have busybox installed? Do you have a custom recovery installed? Personally I never heard of the the toolkit you used. I used Wugs when I did mine
Click to expand...
Click to collapse
Umm I don't know if I have Superuser,I got a notification when I attempt to use applications which require superuser access stating I do not have superuser access.Also no I did not download any of the above applications as they all require root access which my phone( for some reason) says I don't have.Which is the main problem.
I can access that screen where there is an android having open-heart surgery(Is that the bootloader?)
Thats pretty much it.I didn't install any additional software after rooting it with that.And tbh the only reason I used that is because it was a one-click root process
Toolkits are pretty useless. All that is needed to root a nexus device is to unlock the bootloader, flash a custom recovery (technically optional), use custom recovery to flash supersu.
The unlock icon means bootloader is unlocked, do you have a custom recovery yet such as TWRP or clockworkmod?
Omegao said:
Umm I don't know if I have Superuser,I got a notification when I attempt to use applications which require superuser access stating I do not have superuser access.Also no I did not download any of the above applications as they all require root access which my phone( for some reason) says I don't have.Which is the main problem.
I can access that screen where there is an android having open-heart surgery(Is that the bootloader?)
Thats pretty much it.I didn't install any additional software after rooting it with that.And tbh the only reason I used that is because it was a one-click root process
Click to expand...
Click to collapse
none of them are truly one click and rooting this phone is not that difficult. To be honest if you have a problem following rooting instructions for a Nexus may I say rooting may not be for you and quit while your a head. If you used a toolkit you might be able to download Superuser from playstore and test your root.
DrFredPhD said:
Toolkits are pretty useless. All that is needed to root a nexus device is to unlock the bootloader, flash a custom recovery (technically optional), use custom recovery to flash supersu.
The unlock icon means bootloader is unlocked, do you have a custom recovery yet such as TWRP or clockworkmod?
Click to expand...
Click to collapse
lets be honest toolkits are useful for most that need a little help. For more advanced users of course its an issue. Flashing a recovery would still require downloading of software and understand adb slightly.
DrFredPhD said:
Toolkits are pretty useless. All that is needed to root a nexus device is to unlock the bootloader, flash a custom recovery (technically optional), use custom recovery to flash supersu.
The unlock icon means bootloader is unlocked, do you have a custom recovery yet such as TWRP or clockworkmod?
Click to expand...
Click to collapse
I'm not sure if I have.But when I hold certain keys when turning it on it does bring an interface which says clockwork something at the bottom(Maybe the mod?)
This guide covers ALL Moto G 2015 models (including the G Turbo) that can be bootloader unlocked and have TWRP available, it doesn't matter if it is the XT1540, XT1541, XT1543, etc., the method is identical. In fact, this method will work on all 2015 and 2016 series Moto phones running Marshmallow, including the Moto E, X, G3, G4, and Z.
Please read completely and make sure you understand each step and how to do it, if you don't get something search the thread or ask an open question.
tl;dr version for advanced users: Skip to "How to do it" section
I am writing this tutorial because there are still lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover the details of rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread.
Prerequisites:
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: Performing this prerequisite will give you all the tools (fastboot) and drivers needed to continue, and wipe your device, meaning erase all your information and programs. Make sure to backup any important data first. This step will also permanently void your warranty once an unlock code has been issued by Moto, it doesn't matter if you even use it, your warranty is done.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP for the Moto G 2015 or TWRP for Moto G Turbo.
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device.
4) Reboot and start TWRP recovery, the method you use to do this doesn't matter (boot or flash).
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.
If you need assistance, we need detailed information about what what's going on and what you have tried to do... Please provide details including:
1) Device model number and Android version
2) TWRP version
3) SuperSU version
4) Output of 'cat /data/.supersu' from TWRP terminal
And a copy of recovery.log if possible, and any other pertinent information you can think of. Without specific information there is nothing that I can do to assist you and request for help may be ignored.
Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
EDIT: I no longer own or use this device, but will keep this thread open and will check it periodically for assisting the few people left out there who haven't rooted their Moto G 2015 yet.
Alternate Method
Some users have noted that the above method doesn't seem to work, we don't know why as it seems inconsistent but we can't pin it down specifically to user error, certain model number or build, or anything else, as it works 95% of the time...
But if the above method fails, the alternative is to download and copy to SD card or internal storage SuperSU 2.62-3 ßeta version available here and flash it through TWRP like normal.
After this is complete and boot is verified, update the SuperSU app via the Play Store to the current version, then open the SuperSU app and it should prompt you to update the su binary, go ahead and do that via the "Normal" process and reboot when complete.
can confirm, a simple flash won't work, phone stays on the splash screen, had to type op's command for root to work
Sent from my Nexus 6 using Tapatalk
After successful flashing super su it is not showing in app drawer , should I flash it again
25vikasp said:
After successful flashing super su it is not showing in app drawer , should I flash it again
Click to expand...
Click to collapse
SuperSU should show up in the app drawer after a successful flash.
Make sure you enabled changes to system, did the terminal command, and when you flash the zip for SuperSU watch the recovery log, it should say something about "systemless". If not, please attach a copy of recovery.log file
acejavelin said:
SuperSU should show up in the app drawer after a successful flash.
Make sure you enabled changes to system, did the terminal command, and when you flash the zip for SuperSU watch the recovery log, it should say something about "systemless". If not, please attach a copy of recovery.log file
Click to expand...
Click to collapse
[/QUOTE]
See this.i don't know
25vikasp said:
See this.i don't know
Click to expand...
Click to collapse
Hmm... looks like it patched the boot.img successfully. Try installing the SuperSU app from the Play Store and see if it says the binary is properly installed.
I haven't tried this with the 2.77beta yet, I know it had some changes specifically for the Note 7 because Samsung tried to make it unrootable (but failed), I have been using the latest stable build of 2.76
acejavelin said:
See this.i don't know
Hmm... looks like it patched the boot.img successfully. Try installing the SuperSU app from the Play Store and see if it says the binary is properly installed.
I haven't tried this with the 2.77beta yet, I know it had some changes specifically for the Note 7 because Samsung tried to make it unrootable (but failed), I have been using the latest stable build of 2.76
Click to expand...
Click to collapse
At last solved.that latest super su has some bugs so I just tried below version and now it is showing.thanks mate
Click to expand...
Click to collapse
25vikasp said:
At last solved.that latest super su has some bugs so I just tried below version and now it is showing.thanks mate
Click to expand...
Click to collapse
Thank you... I will update the OP to show that 2.77beta is not compatible.
stuck in Boot screen after flashing SU in My MOTO g TE 6.0.1
Pls help Me
krisbeowolf said:
stuck in Boot screen after flashing SU in My MOTO g TE 6.0.1
Pls help Me
Click to expand...
Click to collapse
Stuck on boot screen is classic case of not being a systemless install. Review your SuperSU version and make sure you entering the terminal command EXACTLY as shown in OP. If entered correctly the SuperSU script will "fix" a standard flash with a systemless one.
Otherwise, please give me more information... What version of SuperSU and TWRP, and recovery.log or a snapshot/pic of the recovery terminal screen after flashing SuperSU.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Stuck on boot screen is classic case of not being a systemless install. Review your SuperSU version and make sure you entering the terminal command EXACTLY as shown in OP. If entered correctly the SuperSU script will "fix" a standard flash with a systemless one.
Otherwise, please give me more information... What version of SuperSU and TWRP, and recovery.log or a snapshot/pic of the recovery terminal screen after flashing SuperSU.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
Latest version of twrp 3.0.0 r2 and super SuperSU version v2.62-3 recommended one...
krisbeowolf said:
Latest version of twrp 3.0.0 r2 and super SuperSU version v2.62-3 recommended one...
Click to expand...
Click to collapse
Please read the first post in this thread again and get the current stable version. No where do I recommend that version with my procedure, current stable release is 2.76
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Please read the first post in this thread again and get the current stable version. No where do I recommend that version with my procedure, current stable release is 2.76
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
can you give me the link
krisbeowolf said:
can you give me the link
Click to expand...
Click to collapse
Read the first post of this thread, completely, paying attention to prerequisite #3!!! If you are using SuperSU v2.62-3 Beta you are NOT following my instructions for rooting, are you sure you are posting in the correct thread?
acejavelin said:
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device. As of this posting UPDATE-SuperSU-v2.76-20160630161323.zip is the current stable version.
NOTE: Version 2.77 BETA is intended specifically for the Note 7 and should not be used for rooting Moto devices, in testing it doesn't brick or stop boot, it just doesn't show up or work.
Click to expand...
Click to collapse
How to make backup before unlocking bootloader?
@acejavelin,
I am not rooted, bootloader is not unlocked. I am planning to root my phone. But do you know of anything that can be used to backup my data before unlocking bootloader? If you do know, please tell me about it or maybe provide the link.
Thanks in advance.
sanchith.hegde said:
@acejavelin,
I am not rooted, bootloader is not unlocked. I am planning to root my phone. But do you know of anything that can be used to backup my data before unlocking bootloader? If you do know, please tell me about it or maybe provide the link.
Thanks in advance.
Click to expand...
Click to collapse
Backup photos and videos with Google Photo app, and SMS with SMS Backup & Restore app. All system information should be stored in your Google account along with apps you have installed. You can also use ADB with this method http://www.technipages.com/how-to-backup-your-entire-android-device
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Backup photos and videos with Google Photo app, and SMS with SMS Backup & Restore app. All system information should be stored in your Google account along with apps you have installed. You can also use ADB with this method http://www.technipages.com/how-to-backup-your-entire-android-device
Click to expand...
Click to collapse
Thanks man for your help.
By the way, will ADB work without root?
sanchith.hegde said:
Thanks man for your help.
By the way, will ADB work without root?
Click to expand...
Click to collapse
Yes, just enable it in Developer options.
I absolutely can not get Super User Root, I followed this OP to the letter, I have tried to root, in TWRP Recovery, using the linked SuperSu from both storages ie.. internal storage, and one I placed on my adaptive/portable/ExtSdcard. Went to advanced, terminal typed the "echo.....etc", then flashed, and it says while flashing the Super Su file it's installing "systemless" and looks fine, goes through the whole process tells me to reboot, and then just loads right up no wait, BUT NO Super Su file, tried downloading SuperSu apk from playstore manually, after boot up and it doesn't recognize any root[emoji30]
I have tried this on both allowing the changes at the beginning of recovery, and also not allowing the changes, at the beginning of the recovery, lucky I backed up at first boot of TWRP, which I went into immediately after flashing it via adb/fastboot
I am at a loss, and completely frustrated at this point, any assistance would be so so thankful, thanks
Sent from my MotoG3 using XDA-Developers mobile app