Hello All,
DISCLAIMER! I AM NOT RESPONSIBLE FOR ANY DAMAGE THAT MAY OCCUR THROUGH THE USE OF THIS GUIDE!!! YOU FOLLOW THIS AT YOUR OWN RISK WITH THE KNOWLEDGE THAT THIS MAY/WILL VOID YOUR WARRANTY
I wanted to make this post because I was such a little girl about rooting my phone and installing a custom recovery ever. I’m creating a step by step guide with PICTURES/VIDEOS to help anyone else do the rooting AND flashing custom recovery.
ALL INSTRUCTIONS WERE DONE USING THE LG G2 VERIZON VERSION WITH THE OTA UPDATE. That is I rooted it when it was VS98011A.
PLEASE READ THE INDIVIDUAL THREADS TO MAKE SURE YOUR SPECIFIC VERSION IS SUPPORTED.
I would first like to give credit where credit is due to everyone who has helped my sorry butt do this. All specific questions/problems should be directed to the proper threads as I cannot accurately answer them (sorry).
First of all the two guides I used:
Rooting: thecubed
http://forum.xda-developers.com/showthread.php?p=45692679#post45692679
Flashing TWRP: WACOMalt
http://forum.xda-developers.com/showthread.php?t=2449670
Personal help I received via my own thread:
Paranoid Android User: djraimondi
http://forum.xda-developers.com/showthread.php?p=46779203#post46779203
Thank you “jrgilbert79” for all of your responses.
NOTE: I AM NOT PROVIDING LINKS TO THE FILES ON THIS PAGE. PLEASE GO TO THE GUIDE PAGES TO GET THE ROOT FILES AND THE TWRP AND LOKI FILES. THE RESPECTED THREAD POSTERS ARE USUALLY GOOD AT KEEPING THE MOST UPDATED FILES IN THEIR POSTS.
Now for the instructions:
1.Ensure you have the proper USB drivers installed, and your phone is in the proper mode (For Verizon, use Ethernet mode on the PC settings menu)
2.Enable Developer Mode on your phone and enable USB Debugging
3.Extract this zip file somewhere on your PC. (I recommend making a folder on the desktop named “root” and extract everything into that folder.)
4.Run root.bat
5.The phone will ask you to disconnect USB, disable USB debugging, then re-enable it and plug the phone back in, do so when prompted
6.You will then be asked if you would like to have a superuser package installed, which you can accept or decline (I recommend accepting).
If the text instructions scare you please use this video (I did). Follow along exactly as said.
http://www.youtube.com/watch?v=Y45SXPRb31o
BAM! You should be rooted. To check do what the video says:
Go back into the command promp (shift right click inside the “root” folder (if you created it) “open command prompt here”). Type “adb shell”, “su”, “id”.
It should show identical information to this image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Restart your phone.
Now installing TWRP can be a little more confusing. The actual guide gives you 3 options. It is easiest to use just the first one. What you are going to want to do is download the require files. The .img and the loki_flash file. Now unless you have adb installed you will need to put these files in a certain location. (If you do not know if you have adb installed you probably don’t, it’s okay the root folder has a way around this).
So now you should have downloaded the loki zip and extracted it to get the loki_flash file and your specific twrp disk image. Place both these files inside the folder that contained all the root information, like so:
Note: The files in the black box are what allow you to do the adb commands such as “adb devices”, “adb push”, etc. That is why you must shift click and “open command window here”. If you are afraid you did it wrong always test that windows can see your device by typing “adb devices” and verify it sees your LG.
Once you have the command window open and both files inside the same folder you use to root your device you are ready to flash the twrp recovery. It’s actually pretty simple, just like the root method. Essentially you are just copying two files over onto your device.
I’d figure I will add a little information as to what exactly is going on here. These are kind of a sudo linux language commands. I always liked knowing what was actually going on when I did stuff. You can skip this part if you want…
________________________________________________________________________________________________
“adb push” essentially copies a file over to the given location, in these instances /data/local/temp.
Cd means “change directory” it is a way of navigating through folders and sub folders. Windows has the same command.
Chmod pronounced “change mod” is giving rights to the file. Linux has a way of allowing rights to files. You have 3 groups “user” “group” “global/world” and 3 premissions “read” “write” “execute”. Basically all you need to know is “777” gives read write and execute commands to EVERYONE.
./ essentially runs a program or file or whatever. (This is what flashes the custom recovery).
_________________________________________________________________________________________________
Enter the commands as shown: THESE ARE FOR VERIZON. YOU MUST CHANGE THE FILE NAMES IF YOU ARE USING ANY OTHER CARRIER.
Code:
Code:
adb push loki_flash /data/local/tmp/loki_flash
adb push openrecovery-twrp-2.6.3.2-g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
adb shell
(IF YOU DONT SEE A # prompt, type su to get it.)
cd /data/local/tmp
chmod 777 loki_flash
./loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
exit
adb reboot recovery
It will look something similar to this (I had already previously pushed the loki file that is why you do not see that here). When you are done if you don’t want to create a backup right away and just want to turn your phone back on go into “Reboot” -> “System”. It will boot your phone normally.
Now this is also something I wanted to show ya’ll. To get into TWRP recovery using the key combo you have to turn off your phone. Wait 5 seconds. Turn it on while holding the VOLUME DOWN and POWER key. Once the LG logo appears let go and instantly press and hold the VOLEUME DOWN and POWER key again. This scared me at first but it takes you to a factory reset screen. Mind you I took this video with my Droid RAZR HD, excuse the bad quality haha. (Also I was watching the CMA’s don’t hate… Yes it was Taylor Swift Preforming. You don’t need the sound anyway). Of course you can reboot into recovery using the adb command like the second video as well.
http://youtu.be/8EC29byGOvg
http://youtu.be/jLqBC7uWhyI
To create a backup I just did the default suggested by TWRP. This is from their websites:
http://teamw.in/whattobackup
The default backup options in TWRP are system, data, and boot. For most cases, this is sufficient for backing up a ROM. (Note that in some rare cases, boot isn't available for backup on certain devices). If your device has the option, backing up android_secure and/or sd-ext may be a good idea. There's usually no reason to back up cache or recovery (recovery not available for backup on some devices).
Some devices have "special partitions" like WiMAX, pds, efs, etc. These partitions almost never need to be included in a normal backup. It's usually a good idea to make a single backup of these partitions and hang on to them just in case. Make use of TWRP's keyboard feature and name your backup of these special partitions accordingly.
You just swipe you create a backup. It takes some time (took my device about 5 minutes). I did not compress it I did that afterwards. My file in side was relatively large (4GB approx.). Here is a screenshot of the folder with the backup and then the zip file I made of it. You should probably imo keep a copy on your phone for flashing back and a copy on your computer in case something goes horribly wrong and you lose the file (that way you can adb push the file).
Saved for the flashing of a future ROM.
Sent from my VS980 4G using xda app-developers app
Thanks for taking the time to write this, I got stuck in the TWRP loop when I tried to install it a couple weeks ago.
Did you get stuck doing the button combo or through adb. I believe the older version just had a boot loop problem.
Also I never boot to system from twrp recovery. I always turn it off and turn it back on.
Sent from my VS980 4G using xda app-developers app
Easiest Way To Flash TWRP
OP, Easiest way to do this is head to this thread, download YOUR PHONE'S version of TWRP recovery, put it on your SD card, download Flashify and Quickboot via the Play Store, open Flashify, select recovery, find the recovery.img that you placed on your sd card, flash, open quickboot and reboot into recovery. VOILAH! TWRP is now installed I did this on my AT&T D800, but I assume it should work with all other variants. I am not responsible if something goes wrong. This was just the easiest and fastest thing for me! Press thanks if it worked:good:
P.S. make sure you are ROOTED and BUSYBOX IS INSTALLED.
I used 2.6.3.2 but I probably mucked it up because I used flashify. I ended up flashing back to stock.
wizzcap said:
I used 2.6.3.2 but I probably mucked it up because I used flashify. I ended up flashing back to stock.
Click to expand...
Click to collapse
Do you have the At&t version? Also, make sure you are rooted and busybox is installed.
I do not recommend using flashify. Just my opinion. Have heard of so many problems using flashify.
If you read the guide I explain a little in detail what the actual commands to flash twrp actually do. I'm not sure how the internals of flashify flash the recovery. I'm not sure if the app has the equivalent of the "./" command.
Also when booting into recovery I recommend "adb reboot recovery" or using the volume down and power button method. I feel these ways avoid the least amount of problems. But that's just my two cents. I am by no means an expert. Not by any stretch of the imagination.
Sent from my VS980 4G using xda app-developers app
Great guide for any other girls out there. Lots of pictures and hand holding, they usually need that...
djraimondi said:
I do not recommend using flashify. Just my opinion. Have heard of so many problems using flashify.
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Wonder why? Worked fine for me.
jellybear456 said:
Do you have the At&t version? Also, make sure you are rooted and busybox is installed.
Click to expand...
Click to collapse
Yea I'm rooted on verizon. I used the root method OP posted. All I did was put the file on the SD card and flashed the .img with flashify, but I didn't have any of the other apps installed you mentioned. The phone started back up in twrp, but that's all it would do other than download mode. I'll try the tutorial OP made this weekend when I have some time.
If you have any questions just let me know.
Sent from my VS980 4G using xda app-developers app
help
Hey there just started reading through your thread good job. Im pretty new to android and this was the first time i rooted my phone. Worked out great but seeing how my device is the D803 (canadian device) and theres no version of TWRP for mine so should I just wait it out? Plus after I root am I suppose to have some backup program or what? I'm kinda lost right now and hope someone can guide me into the right direction.
I'm not positive if there is twrp for the D803. Rooting just allows you to access all the files and folders on your device. Twrp is called a custom recovery. It is what allows you to create a backup of your current system (see my last two screenshots) and it also allows you to flash new versions of android.
Sent from my VS980 4G using xda app-developers app
djraimondi said:
I'm not positive if there is twrp for the D803. Rooting just allows you to access all the files and folders on your device. Twrp is called a custom recovery. It is what allows you to create a backup of your current system (see my last two screenshots) and it also allows you to flash new versions of android.
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
ok so since theres no twrp version for the d803 shoulld I just continue on and not worry or is twrp important?
You technically don't need a custom recovery but I wouldn't flash any Roms without one. A custom recovery is basically your "oh ****" situation. If for instance you flashed a ROM and something went wrong the recovery would allow you to fix it. If you didn't have a recovery you would essentially be screwed.
I wouldn't do any flashing until twrp is available.
If you want more information about twrp and custom recoveries I recommend going to the twrp thread as they can answer better then me.
Sent from my VS980 4G using xda app-developers app
ok I'll definitely wait till a twrp version comes out for me. Since I already successfully rooted my phone im ok for now right as long as I dont flash anything ?
Yeah root won't hurt. You can actually do a lot of neat things with just root. I will try to find a list of them. One of them is an app which removes all ads. I forget what it is called though.
Sent from my VS980 4G using xda app-developers app
djraimondi said:
Yeah root won't hurt. You can actually do a lot of neat things with just root. I will try to find a list of them. One of them is an app which removes all ads. I forget what it is called though.
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
yea that would be cool if you get get me a list of stuff to have. So far I only have Xposed and using titanium backjup to get arrid of some bloat.:fingers-crossed:
To OP, thanks for taking the time to do this. Yes, I don't mind a bit of handholding as I've never rooted a phone before so I really appreciate it. Installed root and TWRP w/out issue. Was a little surprised at how much space TWRP took up. Anyway now I just need to decide which ROM to flash.
Related
I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.
lbloo said:
I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.
Click to expand...
Click to collapse
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.
I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?
lbloo said:
I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?
Click to expand...
Click to collapse
rooted stock ROM yea. I've also flashed a pure aosp ROM over stock without any reprocussions.
Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.
lbloo said:
Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.
Click to expand...
Click to collapse
I don't know what you picked up, but here's a stock/rooted ROM that you can flash in your cwm recovery http://forum.xda-developers.com/showthread.php?t=1776330
Aosp works too, its your choice
if you know how to use adb you can just boot to recovery and push the stock build.prop to your tab
I downloaded a stock copy of the stock build.prop, used the adb push command to push it into /system rebooted and nothing. Still hangs on black screen upon boot.
I then downloaded the stock ROM which simms22 kindly pointed me to, used the adb push command to copy the zip file into /data/media/Firmware, used CWM v6.0.1.0 to "install zip file from sdcard" and I got an error, here is the output:
Installing:/sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
Finding update package...
Opening update package...
Installing update package...
E:Error in /sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
(Status 0)
Installation aborted.
I tried both the Odexed and Deodexed files, both gave same results.
Am I missing a step in the process?
It's working now!
I was afraid I was messing up some of the adb commands so I downloaded the Nexus 7 Toolkit 2.0 (Great tool for someone like me)
- via Toolkit re-transferred the odexed and deodexed ROM files, reflashed, same errors as above
- via Toolkit re-installed CWM Recovery 6.0.1.0, reflashed, same errors as above
- via ADB Shell used CHMOD to modify file rights of the ROM files (stab in the dark), same errors as above
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Not sure why the other ROMS would not flash, but at this point I'm not going to mess around to try to figure it out.
Many thanks to simms22 and PhxkinMassacre for getting me pointed in the right direction.
prly a bad download.
after pushing the file you need to set the correct mode:
Code:
adb shell chmod 644 /system/build.prop
Me too - also hosed my own build.prop
lbloo said:
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Click to expand...
Click to collapse
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack
Looking back I don't recall resetting the file rights after modifying the file and that was likely the root cause of my problems.
You should try the chmod command a couple of posts back.
JackinNC said:
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack
Click to expand...
Click to collapse
What location did you push it to? /sdcard/?
Sent from my Nexus 7 using xda app-developers app
mvmacd said:
What location did you push it to? /sdcard/?
Click to expand...
Click to collapse
Yes. And, to further test, I created a little zip file called test.zip and pushed it to the tablet. I can see it just fine. It's just the grouper zip that I can't find.
Thanks
Jack
I just noticed a diff in filesize between the JRO03D_grouper.zip file I am using and one shown in a Youtube video entitled "how to put a rom to flash on a semi-bricked nexus 7 with recovery" by Youtube user metroid031993. (I'm too green to post outside links on XDA)
Mine is 261814702 bytes, the one shown in the video is 32650144 bytes.
Perhaps this is my problem, an invalid zip file. What do you think? And, can someone please tell me the correct size of JRO03D_grouper.zip?
Thanks
Jack
[Note to moderator(s): If I am heading off track in this thread, please don't hesitate to move it or to instruct me to create a new thread. I think the issue may have changed, but I have stayed here since this is where the conversation is for my root issue. Thx!]
JackinNC said:
can someone please tell me the correct size of JRO03D_grouper.zip?
Click to expand...
Click to collapse
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.
Visa Declined said:
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.
Click to expand...
Click to collapse
Thanks for the confirmation.
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
---------- Post added at 11:19 AM ---------- Previous post was at 10:51 AM ----------
JackinNC said:
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
Click to expand...
Click to collapse
Well, I got the grouper zip into /sdcard/ and was able to upgrade without losing anything. w00t!
Theory:
I was in the same adb "session" this time since I was using adb from the command line. Meaning, the daemon was still running from the first push I did. So, while I couldn't see the grouper zip after the first push (consistent with your experience, dark_samus), I could see it and upgrade with it after second push (also consistent). And, perhaps my previous attempts didn't work before because I was closing and opening the Nexus 7 Toolkit each time, therefore stopping and restarting the daemon, which meant that each push attempt was the first attempt for that "session."
I don't have any solid technical basis to support or refute that theory, it's just one possible theory that, if true, would result in the experience I had.
My problem is resolved. Thanks to everyone who contributed to this, I truly appreciate your help!
Jack
simms22 said:
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.
Click to expand...
Click to collapse
how to put the stock image if my n7 doesnt boot to android? pls help
i have CWM already
Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
my bad i already flash a fresh stock rom again, but thanks anyways...
Can i install CWM on locked bootloader?
Ben Ling said:
Can i install CWM on locked bootloader?
Click to expand...
Click to collapse
Yes.
An 'exploit' has recently become available for ROOTING the Nexus 7 without unlocking the BOOTLOADER.
This 'exploit' works... I have tested it myself.
Until recently, I believed that because FASTBOOT wasn't an option (as a result of a LOCKED BOOTLOADER), there was no way of FLASHING anything.
Happily, I was disabused of this notion by bftb0... and I can confirm, you can indeed install CWM (or TWRP) with a locked BOOTLOADER.
-----------------------------
Here's how...
First, you need to run this 'exploit' to acquire ROOT.
Upon reboot, you should now be rooted, with Chainfires SuperSU package and associated SU binary installed.
It's important that you are ROOTED before you proceed.
Next, get Android Terminal Emulator from PlayStore.
Download a CUSTOM RECOVERY .img of your choice... either CWM (Both 'Grouper' and 'Tilapia' variants are available)...
...or TWRP for 'Grouper' (N7 WiFi) or TWRP for 'Tilapia' (N7 3G).
Rename it to recovery.img... and copy it to the root of the Nexus 7's internal storage (emulated SD card).
In Terminal Emulator, run the following command...
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Upon completion of this command, shutdown and reboot your device into the BOOTLOADER, and from there, boot into your CUSTOM RECOVERY... in pretty much the same way had you FASTBOOT FLASHED it.
-----------------------------
You are now free to flash whatever ROMs or kernels you like.
However, a word of caution... because the BOOTLOADER remains locked, FASTBOOT is strictly off limits; it simply won't work.
So the first thing you should do after flashing TWRP or CWM is...
*** MAKE A NANDROID BACKUP ***
If the device becomes 'wedged/bootlooped' as a result of some ROM flash gone wrong, then you will have no choice but to unlock the BOOTLOADER (with full wipe) in order to fix it.
But if you have a NANDROID backup... piece of cake... just restore.
-----------------------------
Credits and kudos must go to XDA members, nhshah7, who made this 'exploit' available and bftb0, whose post pointed me in the right direction, with regard to the 'dd' command.
-----------------------------
I can confirm all of this works... my Nexus 7 is currently rooted, running a custom recovery (TWRP), with a custom ROM and Kernel (see sig) installed - all sitting behind a LOCKED BOOTLOADER.
...no Factory Reset (wipe) required...
...and no Unlocked Padlock Symbol upon boot.
Rgrds,
Ged.
Previously I installed cwm and can boot,just 1 time.
I tried to boot into but nothing.
What to do?
Sent from my Sony Xperia™ sola using XDA Premium App
@GedBlake well it works for the first time for me as well,.,., used the TWRP latest..,.,.
afterwards it says "no command"
SSyar said:
@GedBlake well it works for the first time for me as well,.,., used the TWRP latest..,.,.
afterwards it says "no command"
Click to expand...
Click to collapse
This is really peculiar... I had a few problems myself, initially... but I just assumed I made a typo mistake in TE - but I never had a "no command" message. It took me two or three goes before I got it to work.
And it works fine now, without problems.
I recall reading, a while ago, you had to delete a file from /system called recovery-from-boot.p after flashing a custom recovery in order to get the custom recovery to stick. I never had to do this myself, maybe 'cos I'm running a custom ROM.
Are you on stock, or running a custom ROM?
Rgrds,
Ged.
GedBlake said:
This is really peculiar... I had a few problems myself, initially... but I just assumed I made a typo mistake in TE - but I never had a "no command" message. It took me two or three goes before I got it to work.
And it works fine now, without problems.
I recall reading, a while ago, you had to delete a file from /system called recovery-from-boot.p after flashing a custom recovery in order to get the custom recovery to stick. I never had to do this myself, maybe 'cos I'm running a custom ROM.
Are you on stock, or running a custom ROM?
Rgrds,
Ged.
Click to expand...
Click to collapse
I'm on stock JB 4.2.2 JDQ39 Wi-Fi & 3G version,so what to do now?
Sent from my Asus Google Nexus 7 using XDA Premium
Ben Ling said:
I'm on stock JB 4.2.2 JDQ39 Wi-Fi & 3G version,so what to do now?
Sent from my Asus Google Nexus 7 using XDA Premium
Click to expand...
Click to collapse
Have you tried running the dd command again?... As I previously mentioned, it took two or three attempts, before it 'stuck' on my N7.
Now I have no problem booting into TWRP... similarly, I have tested this procedure with CWM - and again no problems.
With a root capable file manager, you could try deleting (or renaming) the file recovery-from-boot.p which can be found in /system, and then try again.
Rgrds,
Ged.
GedBlake said:
Have you tried running the dd command again?... As I previously mentioned, it took two or three attempts, before it 'stuck' on my N7.
Now I have no problem booting into TWRP... similarly, I have tested this procedure with CWM - and again no problems.
With a root capable file manager, you could try deleting (or renaming) the file recovery-from-boot.p which can be found in /system, and then try again.
Rgrds,
Ged.
Click to expand...
Click to collapse
How to boot into cwm?press volume button?
Sent from my Google Nexus 7 using XDA Premium App
Ben Ling said:
How to boot into cwm?press volume button?
Sent from my Google Nexus 7 using XDA Premium App
Click to expand...
Click to collapse
Shut down the tablet completely.
Press and hold the VOL DOWN button... whilst holding, press the POWER button.
This will boot you into the BOOTLOADER.
Using the VOL buttons, navigate to RECOVERY.
Press the POWER button to select.
Rgrds,
Ged.
Just tested this method... again... (using dd to install a Custom Recovery)... with both CWM and TWRP... and in both instances, the installations survived a reboot. So I'm puzzled why there seems to be a problem here.
---------------------------------
I have semi-automated the process in order to avoid typing long complicated commands into Android Terminal Emulator. A process, which, by it's nature, is subject to typographical error.
Here's how...
Download the Custom Recovery of your choice to your Nexus 7.
Rename it to recovery.img
Copy it to the root of the emulated SD card (internal storage).
---------------------------------
Download this script file...
writerecovery.zip
Unzip and copy it to the root of the emulated SD card (internal storage).
(Alongside the recovery.img).
---------------------------------
Install Script Manager from Google Playstore.
Open Script Manager and locate the script file writerecovery.sh on the root of the emulated SD card.
Press ENTER on it...
Select OPEN AS... Script/Executable...
Select SU (root) from the toolbar...
Select Run...
The script will now execute the following command...
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
...writing the recovery.img to the recovery partition.
See attached thumbnails for the sort of thing you should expect to see.
---------------------------------
I have tested this method several times... switching between CWM and TWRP. And performing multiple reboots, to ensure that the Custom Recovery 'stuck' in each instance.
---------------------------------
Hope this works... if it doesn't... then I'm at a loss to explain why.
Maybe somebody with more technical knowledge can assist.
All I know, is it works for me... on my Nexus 7.
Rgrds,
Ged.
well i installed recovery using goo manager ,.,. got this response from other thread and is working for me ,.,., goo manager also has the option to restart in recovery so really good for me
Help with my Condition
OK, I need help with the following Scenario with Nexus 7 2012 Wifi
My USB Port is damaged. Managed to charge batter with external wires. After that I was able to:
> Root my Nexus7 with KingRoot app (several tries does the trick)
> Install CWM (non-touch) with ROM Manager
> Boot into CWM and do a dummy Flash of Update-SuperSU.zip file just to see if it works on Locked Bootloader. It was successful.
Now I came across your thread, What I need help with is:
WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?
This is going to be a one way ride for me, if I brick I have a paperweight.
(I have however a Backup from CWM, which I can restore if the tablet manages to boot into CWM after bricking)
Need assistance, opinions, strategy with this. Response Awaited.
junisheikh said:
OK, I need help with the following Scenario with Nexus 7 2012 Wifi
My USB Port is damaged. Managed to charge batter with external wires. After that I was able to:
> Root my Nexus7 with KingRoot app (several tries does the trick)
> Install CWM (non-touch) with ROM Manager
> Boot into CWM and do a dummy Flash of Update-SuperSU.zip file just to see if it works on Locked Bootloader. It was successful.
Now I came across your thread, What I need help with is:
WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?
This is going to be a one way ride for me, if I brick I have a paperweight.
(I have however a Backup from CWM, which I can restore if the tablet manages to boot into CWM after bricking)
Need assistance, opinions, strategy with this. Response Awaited.
Click to expand...
Click to collapse
Hi, junisheikh...
To answer your question...
junisheikh said:
"WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?"
Click to expand...
Click to collapse
Yes, you should be able to.
---
The bootloader lock state is irrelevant when it comes to flashing stuff via a Custom Recovery (such as CWM or TWRP).
All an unlocked bootloader does, is it allows the device to accept fastboot flash commands from a connected PC or Mac, and which is the usual way of flashing a Custom Recovery, and then subsequently rooting it.
I would, however, advise against using CWM. ClockWorkMod Recovery is old and hasn't been updated for quite some time, and may cause problems.
Instead, you should take a look at TWRP (TeamWin Recovery Project). This Custom Recovery has a better user interface, and is less likely to cause you problems.
---
Although your bootloader is locked, you have managed to acquire root via KingRoot... which means you can flash a Custom Recovery with the Flashify app...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
This app allows you to flash Recoveries and Boot images (stock and custom) directly from the device itself, providing the device is rooted. The free version of Flashify has a limit of 3 flashes per day. This shouldn't be a problem though... Custom Recoveries aren't something you generally flash on a regular basis.
(See my attached screenshots for a flavour of how Flashify works.)
---
You can find the latest version of TWRP for the Nexus 7 WiFi model here...
http://techerrata.com/browse/twrp2/grouper
Download to your Nexus 7, and use the Flashify app to flash.
And then download whatever Custom ROM+GAPPS you like, and flash via TWRP.
Incidentally, the NANDROID backup you've already created with CWM is NOT compatible with TWRP. So you'll need to create a new NANDROID backup, should you choose to flash TWRP.
---
junisheikh said:
This is going to be a one way ride for me, if I brick I have a paperweight.
Click to expand...
Click to collapse
This is possible, because you don't have access to fastboot (due to your broken USB port) you won't be able to fastboot flash back to Google Factory stock should you not be able to boot Android (for whatever reason) after flashing some Custom ROM. But providing you have a NANDROID backup and a Custom Recovery (CWM or TWRP) installed, you **should** be able to recover from softbricks such as bootloops. But having said that, I would tread carefully.
Hope this helps, and good luck.
Rgrds,
Ged.
Hi Everyone,
I've been using these forums for along time and have not really had the opportunity to give back until now. Let me give you all the details to my problem and the solution to help anyone else in the same if not similar situation. Apologies if this thread has any errors just let know and I'll try to fix them. Also I am confident enough to use command line to do the things I talk about below, so you'll have to be as well if you want to use the methods described. I assume you have some level of technical ability to do this.
Phone details:
Nexus 4, bootloader unlocked, twrp custom recovery installed, rooted, running 4.4.2.
Problem:
I managed to drop my phone after having it for a year. The screen on front cracked and i couldn't use the touch. This caused a problem using the custom recovery (I use TWRP) because it was touch as well. Most of the information on my phone was backup up, my whatsapp is set to backup and push to my box account nightly using titanium backup, my pictures get uploaded to dropbox, instagram has my instagram, etc, etc. But, there were a few files I really needed in my downloads folder. I spent the whole weekend looking for articles and forum posts to help get my data off. Many required installing an app of sorts and then remote controlling the device. I could install the apps using the play store, but as couldn't get passed my lock screen, which is a combination of widget locker and the standard pin unlock screen I couldn't authorise or configure anything.
Solution:
Anyway, here is what i did. I already had WUGFresh's Nexus Root Toolkit and used adb to pull the files and fastboot to flash clockworkmod custom recovery with no touch. Here are the details.
I loaded the phone into recovery which allowed me to use adb. To use adb I opened the WUG Fresh Nexus Root Toolkit, clicked launch Advanced utilities (bottom left). Then used Manual Input (Launch CMD Prompt). Here I used the command 'adb pull /sdcard c:/pull' which grabbed all my files and dumped on the c: in a folder called pull. You can probably also use this method to copy other files from the phone, but i didn't try that.
In order to clear all my data (which i needed to do so the insurance company couldn't read it), I needed to flash clockworkmod custom recovery without touch. I got this from the CWM website and downloaded the appropriate img file for my device. I then booted my phone into fastboot. I used the fastboot help command to find out what the command was to flash a new recovery and did it. The command was 'fastbboot flash recovery c:/put/path/to/file.here'. This loaded the CWM recovery so i could wipe all my data. I just loaded into recovery and wiped all my data.
Summary:
I recommend you use a utility like titanium backup to automate a backup of all your important apps and their data on a nightly/weekly basis so if you ever get into a situation like myself you have some data to easily recover.
I hope this helps people going forward.
Arun.
You didn't need wug's, you could have just used adb to pull the files in recovery. You also could have run fastboot -w and it would have wiped your device. No need to put cwm on your device
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You didn't need wug's, you could have just used adb to pull the files in recovery. You also could have run fastboot -w and it would have wiped your device. No need to put cwm on your device
Click to expand...
Click to collapse
Thanks for the extra information, but I only used WUG's NRT because I already had it installed on my computer. The fastboot note is useful though, I don't think I read through the help list properly otherwise I would've done that. I also wrote this for people with a little amount of technical knowledge, and installing WUG's NRT is really simple to do and has a GUI.
Hello everyone,
today I rooted + bootloader unlocked my N4 with Towelroot and after that I installed Multirom because I wanted to try the Android L developer Preview.
After realizing that a rooted device with a custom recovery won't get official OTA updated anymore I want to have my stock N4 back
I did not install any rom.
Is there a way I can get my stock recovery back WITHOUT having to set up my device again?
I mean, only the recovery should have changed.
I have a mac and a Win XP PC for any tools. I am running stock Android 4.4.4 and kernel 3.4.0-perf-ga6edd5e
Very thankful for any help
If all you need to do is get the stock recovery back you can do that in fastboot. The factory image includes recovery.img. Flash that
fastboot flash recovery recovery.img
Sent from my Nexus 5 using XDA Free mobile app
will this bring me back the ability to get OTA updates?
If so.. is there a tutorial or anything like that I can follow? I have not worked with ADB and fastboot before but thanks a lot for your quick answer!
unrealmac said:
will this bring me back the ability to get OTA updates?
If so.. is there a tutorial or anything like that I can follow? I have not worked with ADB and fastboot before but thanks a lot for your quick answer!
Click to expand...
Click to collapse
It's easy to do. First Google 15 second adb install xda. That'll set up fastboot on your pc. Then Google nexus 4 factory image. Download that and then extract it using winrar or 7-zip. In there you'll find a zip file. Extract that too and you'll find recovery.img.
Boot your device into the bootloader and then in a command prompt opened in the same directory as recovery.img is located run the commands I gave you earlier. You'll then have the stock recovery on your device.
Sent from my Nexus 5 using XDA Free mobile app
I do not find a second archive in there.
Could it be that the recovery.img is also called 'boot.img' ?
unrealmac said:
I do not find a second archive in there.
Could it be that the recovery.img is also called 'boot.img' ?
Click to expand...
Click to collapse
no. Boot.img is the kernel. There should be a zip file in there. In there is recovery.img
Edit, out should be called image- something or other
Edit, edit. If you found boot.img, recovery should be in the same directory as it
Sent from my Nexus 5 using XDA Free mobile app
Thanks again for your fast help.
Okay I found the recovery.img
just to be sure: this will not any of my data/apps on the phone, right?
If so I think I am ready to proceed
unrealmac said:
Thanks again for your fast help.
Okay I found the recovery.img
just to be sure: this will not any of my data/apps on the phone, right?
If so I think I am ready to proceed
Click to expand...
Click to collapse
It won't delete any data
Sent from my Nexus 5 using XDA Free mobile app
I tried it several times with fastboot on mac (the 15 sec installer on Win XP did not work) but everytime I open fastboot I am not able to type anything in.
In the last row of the screenshot it says something like "process closed"
Is the any other tool I can use for that?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
unrealmac said:
I tried it several times with fastboot on mac (the 15 sec installer on Win XP did not work) but everytime I open fastboot I am not able to type anything in.
In the last row of the screenshot it says something like "process closed"
Is the any other tool I can use for that?
Click to expand...
Click to collapse
I'm not familiar with the Mac, but another alternative is to do it from your phone. Get flashify from the play store and flash the recovery.img in it. Just copy recovery.img to your phone
Sent from my Nexus 5 using XDA Free mobile app
Ha! This worked instantly. After pressing "reboot now" it tried to reboot but a screen with "no service" appeared.
After rebooting the device manually everything booted normally.
Is there Any way I can now check if I now have the "stock recovery" again?
What are the criteria to get official OTA updates again from Google?
Thanks so much!
unrealmac said:
Ha! This worked instantly. After pressing "reboot now" it tried to reboot but a screen with "no service" appeared.
After rebooting the device manually everything booted normally.
Is there Any way I can now check if I now have the "stock recovery" again?
What are the criteria to get official OTA updates again from Google?
Thanks so much!
Click to expand...
Click to collapse
To check just boot into the bootloader and go to recovery. The stock recovery should be there.
To get the ota you can not have any modified or deleted system files.
Sent from my Nexus 5 using XDA Free mobile app
Mmh the stock recovery is the Android lying on the back, correct?
So If I have the stock recovery+no rom installed I should get updates, correct?
Root and an open bootloader has no effects to it?
unrealmac said:
Mmh the stock recovery is the Android lying on the back, correct?
So If I have the stock recovery+no rom installed I should get updates, correct?
Root and an open bootloader has no effects to it?
Click to expand...
Click to collapse
You are correct. You will lose root when you get the ota
Sent from my Nexus 5 using XDA Free mobile app
Thank you very much.
I think in the past 24 hours I have learnt more than I have reading in the forums silently.
You have really helped someone very desperate
unrealmac said:
Thank you very much.
I think in the past 24 hours I have learnt more than I have reading in the forums silently.
You have really helped someone very desperate
Click to expand...
Click to collapse
Glad i could help
Sent from my Nexus 5 using XDA Free mobile app
Hello @jd1639
I was just trying to sideload the lollypop OTA file via fastbootand I does not install correctly. There is always an error.
Could this have anything to do with the root access and the unlocked bootloader?
I think I read somewhere something like rooted devices will get the OTA update but will not be able to install them correctly.
Is there a way to get that to work without erasing my data?
unrealmac said:
Hello @jd1639
I was just trying to sideload the lollypop OTA file via fastbootand I does not install correctly. There is always an error.
Could this have anything to do with the root access and the unlocked bootloader?
I think I read somewhere something like rooted devices will get the OTA update but will not be able to install them correctly.
Is there a way to get that to work without erasing my data?
Click to expand...
Click to collapse
Are you flashing it in the stock recovery? If not flash the stock recovery in fastboot and try it again. To use adb sideload you need to be booted into recovery not fastboot
Sent from my Nexus 5 using XDA Free mobile app
Yeah I did that.
I got everything stock but have been flashing the recovery back to stock (like I described in the thread).
Getting something like a "status 7" error.
I am booted into recovery mode. The sending process works and then it tries to install the update on my phone and then the installation process stops..
unrealmac said:
Yeah I did that.
I got everything stock but have been flashing the recovery back to stock (like I described in the thread).
Getting something like a "status 7" error.
I am booted into recovery mode. The sending process works and then it tries to install the update on my phone and then the installation process stops..
Click to expand...
Click to collapse
I got that status 7 error myself. I fastboot flashed recovery, system, boot, and cache from 4.4.4. It won't wipe anything. Then the sideload worked
Sent from my Nexus 5 using XDA Free mobile app
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