I'm on VZW 4.4 non-DE rooted. I just started dabbling with Xposed and GravityBox. I figured out that I need to boot into recovery in order to install the framework and make any module changes stick. But, when I restart into normal (non-recovery) mode, I lose all of the Xposed tweaks that I have made. Is that normal? I thought I read a thread that said that you can make your changes in recovery mode and then go day-to-day in non-recovery mode with all the benefits. Am I wrong?
*Edit* - I reviewed jcase's [Root/Write Protection Bypass] thread, and saw several people asking the same questions there, but no answers.
eyc said:
I'm on VZW 4.4 non-DE rooted. I just started dabbling with Xposed and GravityBox. I figured out that I need to boot into recovery in order to install the framework and make any module changes stick. But, when I restart into normal (non-recovery) mode, I lose all of the Xposed tweaks that I have made. Is that normal? I thought I read a thread that said that you can make your changes in recovery mode and then go day-to-day in non-recovery mode with all the benefits. Am I wrong?
*Edit* - I reviewed jcase's [Root/Write Protection Bypass] thread, and saw several people asking the same questions there, but no answers.
Click to expand...
Click to collapse
Most people who have had this have a locked BL. I have it myself, but I have safestrap installed. No problems with XPosed or XBlast module thus far. There is a thread in the Dev section to permanently kill read/write protection off. Maybe give that a go?
anirudh412 said:
Most people who have had this have a locked BL. I have it myself, but I have safestrap installed. No problems with XPosed or XBlast module thus far. There is a thread in the Dev section to permanently kill read/write protection off. Maybe give that a go?
Click to expand...
Click to collapse
If we are rooted on SlapMyMoto, is there some way for us to check to see if our phone is booted in recovery or not? At this moment, I have no idea if I have booted in recovery or non-recovery, and someone said in another thread that it is "not recommended" to go day-by-day in recovery mode.
eyc said:
If we are rooted on SlapMyMoto, is there some way for us to check to see if our phone is booted in recovery or not? At this moment, I have no idea if I have booted in recovery or non-recovery, and someone said in another thread that it is "not recommended" to go day-by-day in recovery mode.
Click to expand...
Click to collapse
Just boot into recovery mode and go run the tool in the development section to kill write protection. Then you don't have to worry about it and can just always boot normally.
eyc said:
If we are rooted on SlapMyMoto, is there some way for us to check to see if our phone is booted in recovery or not? At this moment, I have no idea if I have booted in recovery or non-recovery, and someone said in another thread that it is "not recommended" to go day-by-day in recovery mode.
Click to expand...
Click to collapse
I dont see why it is 'not recommended' to have write protection permanently turned off. I might be wrong, but dont all the rooted phones with unlocked bootloader essentially do the same thing?
As for your first question, unless you specifically boot into recovery by going into fastboot mode and such, every time you reboot, you have write protection enabled.
Related
This might be crystal clear for most of you, but I will ask this to avoid any unwanted scenarios. Coming from a SGS2, I flashed almost anything without worrying, but I see lots of people bricking their phones here, so I'd like to be on the safe side with this.
How do I root my Moto X with 4.4.2 and unlocked bootloader?
I've read a couple of articles, where they casually mention to flash TWRP, and then SuperSu, and that's it. I can't find a TWRP 4.4.2, only 4.4. Will that work?
I'm also reading the "The Complete Moto X Guides/Information Thread", where under "Unlocked bootloader" there are some instructions, which seem a bit... complicated. Should I follow those?
Thanks guys! :silly:
TheSaw said:
This might be crystal clear for most of you, but I will ask this to avoid any unwanted scenarios. Coming from a SGS2, I flashed almost anything without worrying, but I see lots of people bricking their phones here, so I'd like to be on the safe side with this.
How do I root my Moto X with 4.4.2 and unlocked bootloader?
I've read a couple of articles, where they casually mention to flash TWRP, and then SuperSu, and that's it. I can't find a TWRP 4.4.2, only 4.4. Will that work?
I'm also reading the "The Complete Moto X Guides/Information Thread", where under "Unlocked bootloader" there are some instructions, which seem a bit... complicated. Should I follow those?
Thanks guys! :silly:
Click to expand...
Click to collapse
That's good you did the reading first!
According to the TWRP thread, version 2.6.3.1 (by posted Hashcode) works fine for 4.4.2. Look for the thread in the "Android Development" section with the green square before the thread title. I know it's long but you really should read through the whole thread to get a feel for what people have been doing wrong, etc. For example, you NEED to flash it with Moto's fastboot.exe (often called mfastboot but it's not actually called that when you download it from Moto).
The guide you are referring to seems fine, except the mfastboot command assumes you changed the name of the Moto fastboot executable to mfastboot...
I don't mean to be one of those trolls around here but if the guide seems too complicated, I would encourage you to wait for Moto to release the SBF files for 4.4.2 before rooting. I say this because, without those files, things could get tricky of you're not an expert (I'm not) and you do something wrong. When those files come out, you can follow the simple guide on the Moto site for returning your phone completely to factory specs, should you mess up /system or something.
I'm actually doing what I'm recommending to you. I'm confident I wouldn't mess things up but on the other hand this is my only phone, I'm too poor to replace it, and I'm living abroad so sending it back would be tricky.
[EDIT]: By SBF I mean either the real SBF or the package you can download from the Motorola "return to factory" page. I'm not actually sure if they are the same thing or not as I haven't downloaded. But you don't need RSDLite for them...
droib said:
That's good you did the reading first!
According to the TWRP thread, version 2.6.3.1 (by posted Hashcode) works fine for 4.4.2. Look for the thread in the "Android Development" section with the [...]
Click to expand...
Click to collapse
Hey, thanks for the detailed answer! I'm in a very similar situation to yours. I live in Europe, so returning the phone is not an option, and I don't want to brake it either .
I've flashed a lot of things on my old phone, so I can't say I'm a beginner, but some of these things are new to me, so I'm a bit cautious. For example: what are the SBF file? Those are not needed to root, they are only as backup, right?
If following those instructions correctly are 100% fail-proof, then I would try it.
TheSaw said:
Hey, thanks for the detailed answer! I'm in a very similar situation to yours. I live in Europe, so returning the phone is not an option, and I don't want to brake it either .
I've flashed a lot of things on my old phone, so I can't say I'm a beginner, but some of these things are new to me, so I'm a bit cautious. For example: what are the SBF file? Those are not needed to root, they are only as backup, right?
If following those instructions correctly are 100% fail-proof, then I would try it.
Click to expand...
Click to collapse
Given your experience I don't think there is any real chance of phone death by following those instructions. The issue is, as you say, backup, or what happens AFTER you successfully root. Motorola's SBF files are everything your phone needs to go back to stock, and 4.4.2 is not available yet. So for example if you were on 4.4 and you corrupted something important like your partition table, you could just go to Motorola's website, request the files for 4.4 and flash them all using fastboot (mfastboot as they say here) to get back to a pristine phone. Right now, you can make a recovery backup of /system, etc. right after rooting which SHOULD be fine for correcting OS tinkering errors, but you never know... People have posted on the possibility of flashing, for example, the 4.4 recovery.img on top of 4.4.2 in order get future OTAs, etc, but this sort of thing is very risky. Maybe it works or maybe you hard-brick.
This guide will work on 4.4.2 and has all the files you need to download. If you're already unlocked you can skip those steps of course
http://www.elementalxdesigns.com/ec...our-Moto-X-Developer-Edition-and-install-TWRP
It doesn't tell you how to root, but when you exit TWRP it will ask "would you like to install supersu?" so select yes. Once you're in Android go to Google play and download supersu from the market. Open it and it will ask if you want to install binaries. Select yes and the twrp/cwm option. Your phone will reboot then you're done
This still works to root if your bootloader is already unlocked -> https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP
Now there is a newer version of SuperSU. See this thread -> http://forum.xda-developers.com/showthread.php?t=1538053 and use the link for the CWM / TWRP / MobileODIN installable ZIP.
TheSaw said:
This might be crystal clear for most of you, but I will ask this to avoid any unwanted scenarios. Coming from a SGS2, I flashed almost anything without worrying, but I see lots of people bricking their phones here, so I'd like to be on the safe side with this.
How do I root my Moto X with 4.4.2 and unlocked bootloader?
I've read a couple of articles, where they casually mention to flash TWRP, and then SuperSu, and that's it. I can't find a TWRP 4.4.2, only 4.4. Will that work?
I'm also reading the "The Complete Moto X Guides/Information Thread", where under "Unlocked bootloader" there are some instructions, which seem a bit... complicated. Should I follow those?
Thanks guys! :silly:
Click to expand...
Click to collapse
Follow these instructions with clickable links to TWRP and SuperSU
Step-By-Step Instructions for Unlocking and Rooting a Moto X Dev Ed
works for both 4.4 and 4.4.2.
Okay, I have rooted my phone. I've read several articles on the subject, and this is the easiest method I've found to do it:
Cozume said:
1) Put device in bootloader mode while not connected to PC using the buttons (Volume Down + Power);
2) Connect device to PC using USB cord;
3) mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
4) fastboot reboot-bootloader
5) Disconnect device from PC;
6) Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and then pressing the Volume Up button to select the recovery mode; and
7) You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
Click to expand...
Click to collapse
After you downloaded the files needed for this from here (make sure they're not outdated, if you're reading this somewhere in the future), you can just follow these steps for a quick root access. UNLOCKED BOOTLOADER ONLY.
I'll admit, I didn't fully understand the root process back when I did this. I don't even remember all the steps I took. I got a locked Verizon (black 16GB) for an upgrade back in March. I always wanted this phone but never had an upgrade available. Well I forgot they had a Dev model out and stupidly got the free one with a new contract renewal.
I am running android 4.4 KK and am currently rooted with Xposed installed. I'm pretty sure the only way I can have write protection disabled is by booting into recovery, correct? Even though I select recovery at the fastboot screen, it just boots like normal. I guess my question is, is there any reason for me to be booting into recovery every time? Is there a way to tell if I have WP disabled on /system and root after a normal boot process? I swear I've had Xposed stop working after a normal boot.
EDIT: I'm seriously considering swapping this out for a new Dev model if they go on sale. I could use the extra storage and can easily just unlock the bootloarder and have root when L comes out for the first gen X.
IEcansuckit said:
I'll admit, I didn't fully understand the root process back when I did this. I don't even remember all the steps I took. I got a locked Verizon (black 16GB) for an upgrade back in March. I always wanted this phone but never had an upgrade available. Well I forgot they had a Dev model out and stupidly got the free one with a new contract renewal.
I am running android 4.4 KK and am currently rooted with Xposed installed. I'm pretty sure the only way I can have write protection disabled is by booting into recovery, correct? Even though I select recovery at the fastboot screen, it just boots like normal. I guess my question is, is there any reason for me to be booting into recovery every time? Is there a way to tell if I have WP disabled on /system and root after a normal boot process? I swear I've had Xposed stop working after a normal boot.
EDIT: I'm seriously considering swapping this out for a new Dev model if they go on sale. I could use the extra storage and can easily just unlock the bootloarder and have root when L comes out for the first gen X.
Click to expand...
Click to collapse
You can try installing something as a system app (App Ops for Root comes to mind https://play.google.com/store/apps/details?id=droidmate.appopsinstaller&hl=en) and see if it works. If it does, than write protection is off. The app on Play store is actually an installer that will put App Ops into your /system folder. If you have Xposed working properly, it might be OK already.
I remember when I rooted my VZW Moto Maker Edition on 4.2.2 (I think) I used SlapMyMoto and MotoWPNoMo (or something weird like that). I ran both and then installed Xposed and the framework failed to install properly (the version numbers in the app were red). I tried a few times and it didn't work. I ran the WP script a second time then Xposed worked fine. I must have missed a step in the WP off procedure.
If you boot normally and Xposed doesn't work, or you can't install to /system then I'd say you don't have WP off when booting normally.
fury683 said:
You can try installing something as a system app (App Ops for Root comes to mind https://play.google.com/store/apps/details?id=droidmate.appopsinstaller&hl=en) and see if it works. If it does, than write protection is off. The app on Play store is actually an installer that will put App Ops into your /system folder. If you have Xposed working properly, it might be OK already.
I remember when I rooted my VZW Moto Maker Edition on 4.2.2 (I think) I used SlapMyMoto and MotoWPNoMo (or something weird like that). I ran both and then installed Xposed and the framework failed to install properly (the version numbers in the app were red). I tried a few times and it didn't work. I ran the WP script a second time then Xposed worked fine. I must have missed a step in the WP off procedure.
If you boot normally and Xposed doesn't work, or you can't install to /system then I'd say you don't have WP off when booting normally.
Click to expand...
Click to collapse
Ok, I installed what you suggested, went into the app and tapped the "Install AppOps Root" button. It asked for root access and then rebooted my phone. So I guess this means that by default on a normal reboot, I have WP disabled and root access? Thanks for help clearing this up! I guess the phone was just acting weird that one time when the Xposed modules wouldn't work.
One last question, is there a reason why I can't get to recovery? Whenever I reboot into Recovery, it just starts up like normal? Is that because the normal recovery has been overwritten by a custom one in the root process?
IEcansuckit said:
Ok, I installed what you suggested, went into the app and tapped the "Install AppOps Root" button. It asked for root access and then rebooted my phone. So I guess this means that by default on a normal reboot, I have WP disabled and root access? Thanks for help clearing this up! I guess the phone was just acting weird that one time when the Xposed modules wouldn't work.
One last question, is there a reason why I can't get to recovery? Whenever I reboot into Recovery, it just starts up like normal? Is that because the normal recovery has been overwritten by a custom one in the root process?
Click to expand...
Click to collapse
If your bootloader isn't unlocked I don't think you can change recovery. You may be able to reflash the stock recovery from fastboot/mfastboot for your proper version, but don't quote me on that.
Someone with more experience can chime in. How are you rebooting to recovery? With an app/button, or via fastboot?
fury683 said:
If your bootloader isn't unlocked I don't think you can change recovery. You may be able to reflash the stock recovery from fastboot/mfastboot for your proper version, but don't quote me on that.
Someone with more experience can chime in. How are you rebooting to recovery? With an app/button, or via fastboot?
Click to expand...
Click to collapse
Correct. No unlock - no custom recovery.
It also depends on which method you used to achieve wp-off. Is rather not get into the finer details because it's really not important...
Are you using VOL+ to select recovery in the bootloader?
Edit: yes, when you rooted your phone, the stock recovery was overwritten to give you Android with write protection off. Looks like normal Android, but you have write access to system.
Couldn't find much about this varient just wanted to ask a few questions.
1. Do I treat it like every other google play nexus? Unlock boot loader, flash twrp, boot, backup, reboot, wipe, install ROM? No different partition weirdness?
2. Cm12, are the hotspot checks removed? Fiance is limited data plan I'm not so while out she normally uses my data via hotspot.
3. Cm12 have notification light activated and customizable?
Don't really care about the Sim lock honestly. Been with ATT forever and poor so not leaving the country anytime soon.
Thanks, sorry for repeat questions just didn't get solid answers from things I found.
No partition weirdness. Root as normal. It does have its own boot logo-thing though, which is lame.
Unfortunately I don't know about CM12. Sorry
squattingdonkey said:
No partition weirdness. Root as normal. It does have its own boot logo-thing though, which is lame.
Unfortunately I don't know about CM12. Sorry
Click to expand...
Click to collapse
At least you answered my bricking level question! Thanks!
CM 12 does have working hot spot on AT&T and customizable notification light. And, boot logo is easily removed after root.
Somehow I soft bricked my n6. I unlocked boot loader, installed twrp, went to backup and it couldn't find any partitions. Tried the flash all script from google factory image and that failed as well. Had to flash boot radio recovery etc images each manually to get back to a booting phone. Then installed twrp again and backup and flashing worked.
It was an adventure but I'm good now. Weird not sure why it did that. Must have been an encryption issue.
On the stock ROM you have to tick a box in developer options to enable OEM unlock. I forgot to mention that earlier. That may have been the issue.
ajjames01 said:
On the stock ROM you have to tick a box in developer options to enable OEM unlock. I forgot to mention that earlier. That may have been the issue.
Click to expand...
Click to collapse
Oops yeah that may have been it. I just did the usual fastboot OEM unlock code. Mild panic attack but when I saw I could get to the bootloader I knew I could save it.
Just received the n6 today and there was a notification to update to 5.1. I downloaded and updated it and now it is in an infinite bootloop- keeps on saying optimising 125 apps. (BTW this was completely stock- I didn't even sign in to my Google account) . I tried recovery mode wipes and endless reboots but nothings working- help please?
Btw I am a complete noob who doesn't know anything about root etc so I really don't know what to do.
Anyone
Anyone here
Dry Bones said:
Did your phone die mid installation?
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
heres a thread that could help you if factory resetting or wiping the dalvik/cache isnt working.
Click to expand...
Click to collapse
It didn't die,no. I want a way of fixing the bootloop- without voiding my warranty
Derp12340 said:
Anyone
Click to expand...
Click to collapse
Derp12340 said:
Anyone here
Click to expand...
Click to collapse
Greetings,
Please refrain from bumping a thread until at least 24 hours have passed. XDA Assist is a very busy forum and the Assist RC's have lives outside of XDA as well.
Regards,
The_Merovingian
Forum Moderator
look up how to flash a factory image.. because as i see it, you only have two choices, flashing a factory image, or getting an exchange from wherever you bought your n6.
Did you ever let it finish optimizing apps? Any time an OTA is installed the first boot takes what seems like forever aka 10+ mins depending on number of apps installed. If you interrupt the process I guess it's possible to corrupt something.
Otherwise like @simms22 said install the factory image to reset it entirely or take it back to in for repairs.
If you'd like to run the factory image install yourself follow Google's instructions and download 6.0.1 image for shamu (Nexus 6) at https://developers.google.com/android/nexus/images.
And also I did not enable developer settings nor did I root my device (it is completely stock) so my bootloader is locked and USB debugging is not enabled
Guys these are my options
1) sideload an ota through root toolkit
2)
Wipe data and reset using nexu
S root toolkit
Thing is, my bootloader is locked and USB debugging is disabled.
Go ahead and enable usb debugging and unlock the bootloader.
Once you have everything updated and you don't plan to root or want to do manual installs or take back ups just relock the bootloader when you're done and turn off usb debugging.
janjanrex said:
Go ahead and enable usb debugging and unlock the bootloader.
Once you have everything updated and you don't plan to root or want to do manual installs or take back ups just relock the bootloader when you're done and turn off usb debugging.
Click to expand...
Click to collapse
I think you missed the point... The device is bootlooping = impossible to enable USB debugging and unlock the bootloader.
Derp12340 said:
Guys these are my options
1) sideload an ota through root toolkit
2)
Wipe data and reset using nexu
S root toolkit
Thing is, my bootloader is locked and USB debugging is disabled.
Click to expand...
Click to collapse
I think you need to go with option 3 - get a new phone under warranty, which shouldn't be a problem.
With your new phone, before doing anything else, unlock your bootloader. That will save you a lot of headache.
Edit: Did you try doing a factory reset in recovery? Check this link for instructions: http://www.digitaltrends.com/mobile/use-recovery-mode-android/
The Final Answer
If you aren't going to replace the phone under warranty, then this is your only option.
1. Download Nexus Toolkit. http://www.wugfresh.com/nrt/
2. Use the toolkit to download the latest factory image.
3. Boot into Bootloader
4. Flash factory image
pr0ndigy said:
If you aren't going to replace the phone under warranty, then this is your only option.
1. Download Nexus Toolkit. http://www.wugfresh.com/nrt/
2. Use the toolkit to download the latest factory image.
3. Boot into Bootloader
4. Flash factory image
Click to expand...
Click to collapse
well, he has multiple options to choose from.. the other option being flashing the factory image the right way :silly:
simms22 said:
well, he has multiple options to choose from.. the other option being flashing the factory image the right way :silly:
Click to expand...
Click to collapse
My way is the right way!
How do i know?
Because i've done it, and it works.
So take your **** talk somewhere else kid :good:
These little spats are what keep the community interesting, and I enjoy them when they happen. As Dame Edna Everage said: "I have the fortunate gift of being able to laugh at other people's misfortunes." But personally, I go with experience.
simms22 32,086 posts Thanks Meter: 25,801
pr0ndigy 79 posts Thanks Meter: 22
But hey, what do I know...?
As it happens, I'm a big fan of NRT, having praised, recommended and contributed to it a number of times, but I don't rely on it solely. And I would not go so far as to say "My way is the right way".
Just saying...
Its not a boot loop if you were able to get to the "optimizing apps" message. and the fact that it got to the "optimizing apps" message means your system partition is functioning properly.
Ive had optimization run for 35+ minutes before booting when i took my first official update. You may have messed the phone up if you forced Reboot/power off while it was optimizing.
try and let it boot, if you get the optimizing message then plug it up and let it sit overnight if you have to, i promise IT WILL BOOT.
worse comes to worse, just google "nexus 6 back to stock". your boot loader doesnt have to be unlocked, and usb debugging does not have to be enabled to return to stock
Derp12340 said:
Guys these are my options
1) sideload an ota through root toolkit
2)
Wipe data and reset using nexu
S root toolkit
Thing is, my bootloader is locked and USB debugging is disabled.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=0nDLvy8F5qk
Using ADB mode, you can flash latest factory images: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
https://developers.google.com/android/nexus/images?hl=en
pr0ndigy said:
My way is the right way!
How do i know?
Because i've done it, and it works.
So take your **** talk somewhere else kid :good:
Click to expand...
Click to collapse
LOL. you have no idea who you're taking to
Sent from my Nexus 6 using Tapatalk
Seems I solved the problem myself. I used the rootkit- I basically just unlocked the bootloader and then reset it and flashed marshamallow 6.0.1 and I'm gonna relock the bootloader tomorrow. It was easy enough even for a noob like me.
I wonder how you did it. I can't imagine that such toolkit is able to unlock a bootloader when "OEM unlocking" wasn't enabled in your rom. Or did you enable that before?
(stock firmware)
1) How do I enter recovery mode? I need to install Xposed and I can't figure out how to boot into this.
2) Why is the advanced reboot disabled? I went through all of the developer options and it's just not there :-O
Root?
You did root your phone?
WalrusInAnus said:
(stock firmware)
1) How do I enter recovery mode? I need to install Xposed and I can't figure out how to boot into this.
2) Why is the advanced reboot disabled? I went through all of the developer options and it's just not there :-O
Click to expand...
Click to collapse
The XZ's are nothing like any Sony phone before. Sony have given developers the finger with this boot partition, You can't just Root you phone any more. Unlocking your phone destroys a partiton and the DRM keys are gone forever. The good news is that there's a fix that fools the phone into thinking the keys are still present.
Yes it's possible to load recovery and exposed. You need to unlock the phone first, then (retro)flash .75 firmware, as that is the only one that works with Xposed. Then I would use Xperiafix to mount TWRP and Magisk and the drm fix. Once Magisk is installed you can use the Xposed Magisk module.
It's a long complicated road compared to the old phones and having done it, I'd say the advantages are not worh the effort.
Oh ****, what the hell It's the only higher end compact phone out there, so there's no alternative for me.
I already unlocked the bootloader and now my camera is ****ed, and apparently it's impossible to relock it.
Unfortunately I don't understand anything you wrote in your post. I've dealt with Samsung phones until now and that's piss easy.
What does "mount twrp" mean? What is Magisk?
I managed to install TWRP but it asks for a password, so I think something went tits up there.
WalrusInAnus said:
I think something went tits up there.
Click to expand...
Click to collapse
Read the Xperiafix thread, this will help you find the drivers you need to connect to the phone via ADB. (Hint: Google ADB drivers). Geting the drivers to work with your phone is fiddly because a) Windows10 lies to you when it says it's installed the drivers and b) Windows then chooses the wrong drivers when you plug your phone (running twrp) in.
Buy Xperiafix. Yes there are free versions to be found but getting everything to work is fiddly as f*ck and I'm going to guess you want the easy option.
Install the drivers, follow instuctions on Xperiafix, easy.
Your TWRP is asking for the pin number you set to unlock your phone.