I got my MotoX about a year ago, non-dev edition on VZW. I installed Hashcode's SafeStrap custom recovery and flashed Kryptonite's "stock" 4.4.2 rom to the stock slot. That satisfied me for the time being and I lost track of current development on the Moto X.
I've been itching for a change though and a software update is just the fix. Since I haven't kept up thoug, I really don't know how to go about it. I've been reading about the options but I don't know where my phone stands. Can I go the CM11-> CM12 route with Safestrap even though my bootloader is locked? Or do I need to use SunShine to unlock my bootloader and install a different custom recovery? And do I need to revert to stock to stock at any point? I'm pretty comfortable with all of this, I just need some nudging in the right direction.
llsmith said:
I got my MotoX about a year ago, non-dev edition on VZW. I installed Hashcode's SafeStrap custom recovery and flashed Kryptonite's "stock" 4.4.2 rom to the stock slot. That satisfied me for the time being and I lost track of current development on the Moto X.
I've been itching for a change though and a software update is just the fix. Since I haven't kept up thoug, I really don't know how to go about it. I've been reading about the options but I don't know where my phone stands. Can I go the CM11-> CM12 route with Safestrap even though my bootloader is locked? Or do I need to use SunShine to unlock my bootloader and install a different custom recovery? And do I need to revert to stock to stock at any point? I'm pretty comfortable with all of this, I just need some nudging in the right direction.
Click to expand...
Click to collapse
If you NEVER took the 4.4.4 OTA you might want to consider unlocking your bootloader via "Sunshine" Then you can flash CM or anything you want with a real recovery and not safestrap. Just know that unlocking your bootloaer on a reatail device will void your warranty.
Travisdroidx2 said:
If you NEVER took the 4.4.4 OTA you might want to consider unlocking your bootloader via "Sunshine" Then you can flash CM or anything you want with a real recovery and not safestrap. Just know that unlocking your bootloaer on a reatail device will void your warranty.
Click to expand...
Click to collapse
Right, my phone has never seen 4.4.4. So I'm going to go ahead and use Sunshine to unlock my boot loader as the first step. The warranty I'm not too concerned about.
I guess the next question is how do I go about replacing safestrap with TWRP? Is it the same as installing TWRP from stock?
llsmith said:
Right, my phone has never seen 4.4.4. So I'm going to go ahead and use Sunshine to unlock my boot loader as the first step. The warranty I'm not too concerned about.
I guess the next question is how do I go about replacing safestrap with TWRP? Is it the same as installing TWRP from stock?
Click to expand...
Click to collapse
You should be familiar with flashing a custom recovery via adb if you have used TWRP on other devices. Once you have the bootloader unlocked you would need the correct recovery image of TWRP for the Moto X and then in bootloader mode use the command "fastboot flash recovery 'recovery.img'" where 'recovery.img' is the exact name of the file. If it flashed and it works properly then you could flash CM12 and Safestrap should be gone if you followed the flashing directions exactly. Don't forget to make a Nandroid of your current setup before you begin! Factory Resetting the device would be crucial if jumping from one ROM to another so it kind of takes care of itself.
I rooted my VZW XT1096 via the mofo method. I was thinking that after I flashed my system with a rooted system I would be able to flash a custom recovery and then flash a ROM. There's a CM12.1 build for the Victara but I don't know how to flash it.
Also, it seems like you can only flash IMG files and not zips with mofo.exe. This makes things very difficult because I haven't seen any ext4 system ROMs out there.
jsbenson said:
I rooted my VZW XT1096 via the mofo method. I was thinking that after I flashed my system with a rooted system I would be able to flash a custom recovery
Click to expand...
Click to collapse
Did you read my noob guide? If you had, you would see that root doesn't unlock your bootloader and you need an unlocked bootloader to flash a custom recovery.
There is a link to my noob guide in the OP of the MoFo support thread on the paid software forum.
jsbenson said:
Also, it seems like you can only flash IMG files and not zips with mofo.exe.
Click to expand...
Click to collapse
Correct. Your bootloader is locked and you have no way of unlocking it - you cannot install a zip b/c you don't have a custom recovery and you can't have a custom recovery unless your bootloader is unlocked.
jsbenson said:
This makes things very difficult because I haven't seen any ext4 system ROMs out there.
Click to expand...
Click to collapse
Did you read the OP of the MoFo thread before you purchased? There are custom images for the XT1096 and links to them in the OP of the MoFo thread.
Also, this is your only option if you have an XT1096. So it is this or nothing.
JulesJam said:
Did you read my noob guide? If you had, you would see that root doesn't unlock your bootloader and you need an unlocked bootloader to flash a custom recovery.
There is a link to my noob guide in the OP of the MoFo support thread on the paid software forum.
Correct. Your bootloader is locked and you have no way of unlocking it - you cannot install a zip b/c you don't have a custom recovery and you can't have a custom recovery unless your bootloader is unlocked.
Did you read the OP of the MoFo thread before you purchased? There are custom images for the XT1096 and links to them in the OP of the MoFo thread.
Also, this is your only option if you have an XT1096. So it is this or nothing.
Click to expand...
Click to collapse
I was a little confused so I wanted to make sure I wasn't missing anything. Thanks for the info. I'll read through the posts again.
I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
evolefty said:
I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
Click to expand...
Click to collapse
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
The OTA will not install when the device is rooted
cam30era said:
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
Click to expand...
Click to collapse
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
evolefty said:
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
Click to expand...
Click to collapse
You'll get the notification. You just can't flash it.
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
DogzOfWar said:
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
Click to expand...
Click to collapse
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Supplementing that: using the "unroot" function in SuperSU is not sufficient with Lollipop. It still leaves the vestiges of a few modified files that will cause an OTA to fail.
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
evolefty said:
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
Click to expand...
Click to collapse
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
evolefty said:
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
Click to expand...
Click to collapse
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
gee2012 said:
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
Click to expand...
Click to collapse
Will do, and that is the method I used to root for the simple fact to learn.
evolefty said:
Will do, and that is the method I used to root for the simple fact to learn.
Click to expand...
Click to collapse
Good luck
gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
needoZ said:
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
Click to expand...
Click to collapse
Yes, use the LMY47Z build.
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Bootloader does not have to be locked to take an OTA. You can not be rooted or modified in any way however.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
While I agree, once you have "paid your dues" and flashed without automation then the NRT is a great tool, so long as you have an understanding of what it is doing.
Hi there everyone! I am absolutely 100% noob when it comes to LG. Always had an HTC phone but with the horrible reviews for the M9 I chose the G4. Its a great phone stock but the rooting itch has gotten to strong lol. Read plenty of threads and watched a few videos on how to root this beautiful phone. Yet, questions pop into my head...... I know most likely rule number one is to unlock the bootloader. For HTC I would then boot into Fastboot mode to flash TWRP with the famous command "fastboot flash recovery twrp.img" and then proceed to flash my favorite ROM that is pre-rooted. Would the steps be about the same? If not, what is different? Is there any way to hide root from the T-Mobile Account app that checks for root or should I just get rid of the app? Also, I am still on the 10H build. Should I update to 10N first or would I not be able to root? So sorry for the amount of questions presented here it is just that I'm afraid of bricking. Any help is appreciated.
Upgrade to 10N then follow the instructions here:
http://forum.xda-developers.com/tmobile-g4/development/h81110n-stock-rooted-image-t3191038
Make sure you set OEM bootloader unlocked as well in Developer options.
Then use flashify to install TWRP
I would install debloated ROM here but thats up to you: http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-10n-stock-rooted-rom-t3188858
xhunter187 said:
Hi there everyone! I am absolutely 100% noob when it comes to LG. Always had an HTC phone but with the horrible reviews for the M9 I chose the G4. Its a great phone stock but the rooting itch has gotten to strong lol. Read plenty of threads and watched a few videos on how to root this beautiful phone. Yet, questions pop into my head...... I know most likely rule number one is to unlock the bootloader. For HTC I would then boot into Fastboot mode to flash TWRP with the famous command "fastboot flash recovery twrp.img" and then proceed to flash my favorite ROM that is pre-rooted. Would the steps be about the same? If not, what is different? Is there any way to hide root from the T-Mobile Account app that checks for root or should I just get rid of the app? Also, I am still on the 10H build. Should I update to 10N first or would I not be able to root? So sorry for the amount of questions presented here it is just that I'm afraid of bricking. Any help is appreciated.
Click to expand...
Click to collapse
tk424 said:
Upgrade to 10N then follow the instructions here:
http://forum.xda-developers.com/tmobile-g4/development/h81110n-stock-rooted-image-t3191038
Make sure you set OEM bootloader unlocked as well in Developer options.
Then use flashify to install TWRP
I would install debloated ROM here but thats up to you: http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-10n-stock-rooted-rom-t3188858
Click to expand...
Click to collapse
Thanks for the help! Flashed your stock rooted image so I could Flashify TWRP. I have been a part of the HTC fan club since the Droid Incredible. All the way to the One Max and M8 while I was on Verizon. This LG stuff is all new to me lol.
Hi guys.
Well I am very confused about this. I don't know how to fix it and it locks like there is not a alot of people who had the same problem.
I rooted the device, backed up drm keys, unlocked bootloader.
So and now if I want to install custom roms it installs them but as soon as I reboot it is soft bricked.
I tried it with resurrecting remix lollipop and marshmallow.
I would appreciate it if you could help me.
Thanks
thefanofmusic said:
Hi guys.
Well I am very confused about this. I don't know how to fix it and it locks like there is not a alot of people who had the same problem.
I rooted the device, backed up drm keys, unlocked bootloader.
So and now if I want to install custom roms it installs them but as soon as I reboot it is soft bricked.
I tried it with resurrecting remix lollipop and marshmallow.
I would appreciate it if you could help me.
Thanks
Click to expand...
Click to collapse
Are you sure that your phone can be unlocked? some can't.
You've done the right thing backing up your TA partition.
With an unlocked phone, after you've flashed the rom you will need to flash a kernel .img in flashtool or it won't boot.
I've never tried to unlock my bootloader, so I'm not sure I can give much advice.
Perhaps someone who's got a CM rom working can help?
Didgesteve said:
Are you sure that your phone can be unlocked? some can't.
You've done the right thing backing up your TA partition.
With an unlocked phone, after you've flashed the rom you will need to flash a kernel .img in flashtool or it won't boot.
I've never tried to unlock my bootloader, so I'm not sure I can give much advice.
Perhaps someone who's got a CM rom working can help?
Click to expand...
Click to collapse
Yes it is already unlocked. I looked it up.
Maybe it is kernel which is missing but before I never needed to flash a kernel and the custom Rom. I mean on other Sony devices.
I really need help. I don't know how to solve this.
Have you tried flashing boot.img using fastboot flash boot boot.img command?
mrrflagg said:
Have you tried flashing boot.img using fastboot flash boot boot.img command?
Click to expand...
Click to collapse
Yeah I thought about it to. Will try it later. But why can't I just flash it like a regular zip file