Related
Hi all,
There is just to much info here and I cant find what I'm looking to do... tried other sites also but not the same.
I have in the UK a stock Wifi GED Jelly Bean Xoom.
I would like to flash a custom ROM.
Am I correct in thinking I need to:-
Root - still not found a guide that does JB
Install Clockwork Mod Recovery
Boot into recovery mode and select wipe... install from .zip within CMR?
Pointers would be greatly appreciated...
I think unlocking and rooting would be the same regardless of the OS.
I also suggest you flash TWRP instead of CWM, both are fine either way.
Once you boot into recovery wipe cashe, dalvik cache, and data (factory restore).
Then flash ROM and GAPPS (for the specific ROM).
Just make sure the ROM you flash is designed for your device (there are many flavors of XOOM, each a little different from the others).
Geeba said:
Root - still not found a guide that does JB
Click to expand...
Click to collapse
Irrelevant if you plan on using a custom rom.
1. unlock bootloader via fastboot - fastboot oem unlock
2. flash custom recovery via fastboot - fastboot flash recovery recovery.img
3. flash custom rom via the custom recovery you just flashed
Plenty of guides that go over this much.
Cubanluke88 said:
Irrelevant if you plan on using a custom rom.
1. unlock bootloader via fastboot - fastboot oem unlock
2. flash custom recovery via fastboot - fastboot flash recovery recovery.img
3. flash custom rom via the custom recovery you just flashed
Plenty of guides that go over this much.
Click to expand...
Click to collapse
Any pointers on what would cover a stock JB Wifi? - its all pretty bewildering if I'm honest.. I have no issues flashing my HD2 phone with Droid Clockwork Mod --> instal from zip... but the xoom doesnt appear to be that straightforward
Look at this guide that I came across. xoomforums.com/forum/motorola-xoom-development/15179-how-rookie-rooting-flashing-unrooting-under-one-roof.
Sorry it would not me post the link to the guide.
Just a thought..... Xooms sold in the UK do not have a JB update yet, so I would assume the Xoom may already have had its bootlaoder unlocked to convert it to a GED device and as part of that a custom revoery (like ClockworkMod) installed.
Is it worth trying to reboot into recovery to find out if you already have a Custom Recovery installed ? Might simplify the process somewhat......
I must admit, I've no idea what the stock recovery would look like though seeing as I GEDified my Xoom within a week of getting it
I apologize for the noob question but I've never found myself in this particular situation...
I've decided to stick with the 4.3 JWR66V factory image while I wait for a working rooted version to be released or even an updated SuperSU or Superuser zip (that doesn't drain the battery or lose root with certain apps).
I used the factory image found HERE and followed the detailed instructions found HERE. I followed the instructions under section "D" vigorously which meant that I installed the stock recovery image as well. Everything is running as it should. However, I was curious if it was safe to flash TWRP 2.6.0.0 recovery through fastboot with my current setup. I'd like to use that recovery to wipe cache/dalvik and possibly fix permissions. However, I'm not sure if this will break something so I am hesitant to try it.
I have made sure the bootloader is unlocked. But I am curious if it's safe to flash and use TWRP while I am not rooted.
You can install recovery with no problem, root has nothing to do with it. however i think upon a reboot your recovery will be replaced with factory.
Interesting. I wonder why/how the system would flash back to stock recovery if I've pushed the TWRP recovery image over the factory image?
I flashed twrp from fastboot and it's still there. Just waiting on root
Sent from my Nexus 4 using xda app-developers app
otariq said:
I flashed twrp from fastboot and it's still there. Just waiting on root
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Without root would there be any functionality within TWRP that I shouldn't touch? Or does recovery functionality have no dependency on root?
What is there you wanna do? I just replaced stock with twrp so I can just flash the su zip when its out because I don't always have access to a PC. Also, Franco released his initial 4.3 kernel which I'm thinking about flashing.
When rebooting from twrp it'll ask if you wanna flash the su.apk because you don't have root I chose no because it wouldn't do anything for us right now without the binaries
Sent from my Nexus 4 using xda app-developers app
Good point. As of right now I guess I don't have a huge need for it. I'll just leave everything as is until a proper SuperSU is released. At which point I'll install the latest TWRP and root.
Just a question, wasn't nexus root toolkit supposed to be able to revert to stock?
I did it in previous android versions.
now I am running slim rom with CWM and "reverting to stock 4.3" using NRT doesn't work, the process finishes but nothing is done.
skinniezinho said:
Just a question, wasn't nexus root toolkit supposed to be able to revert to stock?
I did it in previous android versions.
now I am running slim rom with CWM and "reverting to stock 4.3" using NRT doesn't work, the process finishes but nothing is done.
Click to expand...
Click to collapse
No idea. I use a Mac and flash back to stock via Fastboot. You should just learn to do that anyway so you have a better sense of exactly what is going on and if something fails you'll know exactly which step is failing in order to correct it. Relying on a toolkit is like never taking the training wheels off your bike.
First let me apologise if this is in the wrong section. I could not decide if this was the best place for it or q a&a. As the title sais. If i flash twrp will it prevent me from receiving ota updates from Google. I have an HTC sensation XE and if i flash a custom recovery i know from past experience that it prevents ota updates. This nexus 7 however is my first "Google" device you could call it and as such i do not know that.
Can any one inform me on this issue. Also if it will an ota cause loss of root on this nexus like it did on my smartphone or will it stay? If it is gone i suppose it will simply be a matter of using chainfires root tool again when it gets updated for it.
Thanks in advance.
Sent from my Nexus 7 using Tapatalk 4
Q&A would be the best place for the post, but I can offer some insight. Any time you flash a custom rom you will forfeit the option of an ota update from your carrier or Google. This doesn't affect your play store apps as they will update when needed. The information that gets sent to your carrier identifies it as being non-official software so only a few custom ROMs that are well maintained will point the ota updates to its own servers. If you wish to receive official ota updates you should perform a nandroid backup of your stock rom to have a restore point for when a new release comes out. Aside from that, you would have to flash everything back to stock (probably stock recovery too) in order to be seen by the carrier as an eligible device.
Sent from my SGH-I727 using Tapatalk 2
Who said anything about flashing a custom rom. I know i didn't. Sorry but that reply is no insight at all. I asked if flashing twrp a custom recovery would prevent ota updates like on my phone. Nothing else. I did not say one word about custom recovery.
Sent from my Nexus 7 using Tapatalk 4
Ch3vr0n said:
Who said anything about flashing a custom rom. I know i didn't. Sorry but that reply is no insight at all. I asked if flashing twrp a custom recovery would prevent ota updates like on my phone. Nothing else. I did not say one word about custom recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
If you install a custom recovery like twrp, you wouldn't be able to install an OTA from Google. You need stock recovery for OTAs.
now that's more of an answer i was hoping to get, can some other users confirm this? I suppose i'll lose root aswell but i imagine that would simply be a case of waiting for an updated root tool then. Say i do flash a recovery, does google have a page where you can manually download the update files to flash? But that would probably cause a lose of root as well but the custom recovery would remain intact, correct?
Ch3vr0n said:
now that's more of an answer i was hoping to get, can some other users confirm this? I suppose i'll lose root aswell but i imagine that would simply be a case of waiting for an updated root tool then. Say i do flash a recovery, does google have a page where you can manually download the update files to flash? But that would probably cause a lose of root as well but the custom recovery would remain intact, correct?
Click to expand...
Click to collapse
This has already been brought up many times e.g.
http://forum.xda-developers.com/showthread.php?t=2404833
I thought as much. I'll stick with stock recovery then until i need a custom recovery for some specific reason. For now root access is enough. And if an ota comes out and i lose recovery well I'll just wait for chainfire to update his root tool
i received the jss15j -> jsl36c update on my razorg with twrp recovery installed.
after the update stock recovery was back.
you can boot every recovery or kernel image without flashing it using fastboot:
fastboot boot nameofrecovery.img
I think you can have your cake and eat it too.
Instead of "fastboot flash recovery recovery.img" to flash the custom recovery, you can "fastboot boot recovery.img".
Every time you want the custom recovery, use fastboot boot command on the pc. This way you can make nandroid backups and flash superSU to root. But, you will not be replacing the stock recovery.
I did this on my HTC phone, when I wanted to remain stock, rooted, yet able to receive OTA updates.
HowardZ said:
I think you can have your cake and eat it too.
Instead of "fastboot flash recovery recovery.img" to flash the custom recovery, you can "fastboot boot recovery.img".
Every time you want the custom recovery, use fastboot boot command on the pc. This way you can make nandroid backups and flash superSU to root. But, you will not be replacing the stock recovery.
I did this on my HTC phone, when I wanted to remain stock, rooted, yet able to receive OTA updates.
Click to expand...
Click to collapse
Good to know.
Sent from my Nexus 7 using Tapatalk 4
I've taken OTAs using custom recoveries before on any number of devices. If you're not careful you can lose your recovery and have to reflash again, but sometimes you don't even lose that.
Well, there might be complications installing an OTA with custom recovery if it comes with a newer bootloader version/radio. Sometimes it works, but there were also reported problems.
Well i just had an ota update to jss15r and lost root as kinda expected. Now ill just have to find out if rerunning the root tool will be enough. Since it is already OEM unlocked i suppose i can simply modify that bat file and remove that line and run it again?
Here is a dedicated thread for Q&A and general info on OTA's for the Motorola Nexus 6. Please feel free to discuss all things OTA related and ask any questions you may have.
*Bootloader lock status has no effect on OTA pass or fail.*
To summarize, an OTA (Over The Air) is a software update pushed to nexus devices directly from Google. You will receive a notification when one is available for your device. The files are generally large in size and downloading via WiFi is recommended.
With Android 5.0 and up, OTA updating has changed significantly from previous versions. In the past, you could be stock, rooted, with stock recovery and OTA's would flash successfully. This is no longer possible in lollipop. Absolutely no system or kernel modifications can be present in order for the OTA to flash. This means that if you have unencrypted the stock kernel, the OTA will fail. The phone must be in a "out of box" state.
As always, you are not required to take the OTA as there are other options available. If you are already rooted, unlocked and using a custom recovery, you can use an updated custom ROM provided by the amazing development community here at XDA. Factory images are released by Google prior to OTA's being pushed out so most, if not all, of the custom ROMs are updated before you'll even see an OTA notification. Also, there are stock, rooted ROMs available as well.
*Factory images*
You can always update or return to stock via factory images direct from Google. Link to this guide provided in post #2
*Sideloading*
Another feature available to use is the sideload option. With the use of a few simple ADB commands, you can apply the OTA via sideload. Sideloading will require connecting to your PC and a working ADB/fastboot connection. Directions for sideloading are in post #3.
*Updating while rooted, unlocked, and having a custom recovery via fastboot*
This is quite simple with basic knowledge of fastboot/ADB. Download the factory image, extract the system image and flash with fastboot. Then flash TWRP and SuperSU again. You can also flash the boot image if desired. However if you are unencrypted, this will encrypt the device.
Many, MANY thanks to the development community, themers, modders and other talented people here at XDA.
Thanks @El Daddy for guidance and advice.
Helpful links:
*Please hit the thanks button for the OP's of the XDA threads below if the threads were helpful in any way.*
Beginners guide:
Thanks @xBeerdroiDx
http://forum.xda-developers.com/showthread.php?t=2948481
Setting up and using ADB and fastboot:
Thanks @rootSU
http://forum.xda-developers.com/showthread.php?t=3006500
Factory images installation instructions:
(Including the fastboot flash method for flashing individual images):
Thanks @Mr hOaX
http://forum.xda-developers.com/showthread.php?t=2954008
OTA files:
Thanks @oldblue910
http://forum.xda-developers.com/showthread.php?t=2906493
*For rooted/unlocked users only*
OTA zip files and radio files (TWRP flashable):
Thanks @Q9Nap
http://forum.xda-developers.com/showthread.php?t=3066052
Radio thread (fastboot flashable):
Thanks @zephiK
http://forum.xda-developers.com/showthread.php?t=2969380
Directions for sideloading
*These directions are based on Android SDK, Windows OS and a 100% stock Nexus 6*
This is just a simple, well known, user guide to using sideload.
Make sure your SDK is updated!
Download the OTA file to your PC, rename it to update.zip and transfer into the platform-tools folder of your SDK.
Connect your Nexus to your PC with your OEM USB cable.
Hold shift and right click on platform-tools folder and select open command prompt here.
Type: adb devices
If your serial number comes up, you are good to go. If not, check out your drivers in device manager. You may need to manually point your PC to their location. Also, you may need to uninstall any other Android drivers that are not associated with your Nexus.
Type: adb reboot bootloader
Select recovery mode from your phone using the volume down key. Once you've highlighted recovery mode, press power to select it.
It looks like a restart but the the dead android appears with red exclamation point. When that happens, hold power button and press volume up once.
Once in recovery, use the volume down key to select apply update from adb and push power to select it.
When your phone says now send file,
type: adb sideload update.zip
If all goes well, you'll see things progress and your Nexus will restart when complete. If you encounter the device not found error after beginning, unplug your USB and reconnect. I had to do it twice, but it works.
How do we install ota zip
if you are running stock you should be able to use wug toolkit and have it flash this zip file
What about stock-ish? I'm assuming since I'm rooted with my device unencrypted, that I can't flash this, right?
Flashing now. Will post back when done.
EDIT: Flash went perfect ^.^ 5.1 is all set.
knitler said:
Flashing now. Will post back when done.
EDIT: Flash went perfect ^.^ 5.1 is all set.
Click to expand...
Click to collapse
Were you completely stock?
Sent from my Nexus 6 using XDA Premium 4 mobile app
instructions for mac
http://www.androidcentral.com/how-manually-upgrade-your-nexus#slide5
I have a modded boot image and it failed to install. Guess ill have to nuke and start over to get this OTA in place.
http://www.androidpolice.com/2015/0...gs-android-5-1-ota-roundup-for-nexus-devices/ I just want to flash the radio but it looks line it's 20 MB bigger than the last
Is anyone creating a flashable zip that works with TWRP?
@oldblue910,
Thank you very much. ADB sideload went flawlessly (completely stock 5.0.1 of course).
I probably already know the answer but here is my situation... I am on the stock image but unlocked boot loader, rooted, and twrp recovery. The only way I can remain stock and not lose my current state other than root and a few apps that rely on root is to... Unroot, relock boot loader and put back stock recovery... Then OTA or side load? Theres no other option right?
I think I'm on the same situation as edif30
Stock image
rooted
unlocked bootloader
TWRP recovery
How can i sideload w/o losing root?
edif30 said:
I probably already know the answer but here is my situation... I am on the stock image but unlocked boot loader, rooted, and twrp recovery. The only way I can remain stock and not lose my current state other than root and a few apps that rely on root is to... Unroot, relock boot loader and put back stock recovery... Then OTA or side load? Theres no other option right?
Click to expand...
Click to collapse
You could flash the 5.0.1 factory image except for the userdata.img and radio.img and side load the OTA. Or you can wait for the 5.1 factory image and remove the "-w" from the flash-all script.
You will lose root and TWRP. but your data will remain intact.
So I'm all stock, unrooted, with a still-locked bootloader. I can flash the OTA without unlocking and without losing my data, right?
stevexyz0 said:
So I'm all stock, unrooted, with a still-locked bootloader. I can flash the OTA without unlocking and without losing my data, right?
Click to expand...
Click to collapse
Yep, just use ADB sideload.
So I had stock 5.0.1 with a custom kernel. I flashed the stock boot.img from the factory image using TWRP and I unrooted from in the SuperSU app, so I should be stock all around except for recovery. When I try to flash the OTA in TWRP it gives the following error message:
Package expects build fingerprint of google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys or google/shamu/shamu:5.1/LMY47D/1743759:user/release-keys; this device has google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy01130854:eng/test-keys.
Any idea why TWRP would think I was running 5.0.2?
cam30era said:
@oldblue910,
Thank you very much. ADB sideload went flawlessly (completely stock 5.0.1 of course).
Click to expand...
Click to collapse
Mine too but how long did it stay on the GOOGLE screen before booting?
I recently unlocked the bootloader and rooted my Nexus 6P and just this evening received an update for the November Security Update. This downloads fine but when the phone reboots to install, it just goes to TWRP and doesn't install.
This is most likely incredibly simple and stupid for me even to ask, but is it possible to install one I've unlocked/rooted?
Any advice will be much appreciated.
You need the stock recovery to take otas Thats why it won't work
Sent from my Nexus 6P using XDA Free mobile app
Before, it initiates an update install. It checks root status. If it finds the device is rooted then it stops OTA install, to prevent any further damage to the phone.
In the least number of steps, what is the best way with chainfire modified boot image, and twrp? I love updates, but I loathe having to undo what I've accomplished in the way of customization. I know I'm not the only one who finds it a pain.
Sent from my Nexus 6P using Tapatalk
Thanks for the quick answers guys. Many thanks.
rborg said:
In the least number of steps, what is the best way with chainfire modified boot image, and twrp? I love updates, but I loathe having to undo what I've accomplished in the way of customization. I know I'm not the only one who finds it a pain.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you have gone as far as unlocking and rooting your phone, then you must have decided to go with some sort of ROM. If you do that, youll actually "typically" get the updates quicker from the developer than OTA. Just saying. And you dont lose your mods.
Does anyone have the stock recovery img handy? Should be easy to get OTA's with flashify that way.
HyperM3 said:
If you have gone as far as unlocking and rooting your phone, then you must have decided to go with some sort of ROM. If you do that, youll actually "typically" get the updates quicker from the developer than OTA. Just saying. And you dont lose your mods.
Click to expand...
Click to collapse
I was hoping to stay stock and use xposed when it is ready. So, no, I haven't gone that far in a long time.
Sent from my Nexus 6P using Tapatalk
The best way to get the ota updates for you would be to download the factory image from Google and Fastboot flash. If you dont wipe user data you should be able to keep most of your settings. You will also need to reflash chainfire's boot Img.
rborg said:
In the least number of steps, what is the best way with chainfire modified boot image, and twrp? I love updates, but I loathe having to undo what I've accomplished in the way of customization. I know I'm not the only one who finds it a pain.
Click to expand...
Click to collapse
Here is what I do. So long as you do not flash or wipe userdata, this method should maintain all your app data and settings:
1. Download files:
* Latest factory image from: https://developers.google.com/android/nexus/images?hl=en and extract .img files to a folder on your computer with fastboot.
* Modified boot.img from: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344 and extract boot.img to the same folder (I usually rename it to modifiedboot.img so I have have the original boot.img and modified images in the same folder).
* Latest version of TWRP from: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976 (direct link: https://dl.twrp.me/angler/) to the same folder
* Systemless SuperSU from: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (do not unzip) to /sdcard/download folder on phone
2. Flash .img files using the following commands:
fastboot flash bootloader bootloader.img [using current name of bootloader image - not necessary if no change to bootloader from prior factory image]
fastboot reboot-bootloader
fastboot flash radio radio-angler.img [using current name of radio image - not necessary if no change to radio from prior factory image]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot modifiedboot.img
fastboot flash recovery twrp-2.8.7.x-angler.img [replace x with the current version]
3. Boot into recovery (TWRP), flash SuperSU.zip from /sdcard/download, wipe davlik and regular caches and reboot to system.
Upon reboot, Android will optimize all of your apps, so the first boot will take a while. However, the whole process usually takes me about 20 minutes - perhaps a bit more if I do a TWRP backup before upgrading (recommended).
---------- Post added at 10:25 AM ---------- Previous post was at 10:12 AM ----------
OR - as I suggested in another thread, if you really want to take the OTA, instead of the above method, you probably could do the following (note I haven't tested this, but I assume it would work) - files can be downloaded using the same links listed above:
1. Flash stock boot.img and recovery.img from current factory image (e.g., if you are currently running MDB08K, you will want to download the MDB08K factory image (not the newer one) and extract the boot.img and recovery.img files from that archive - note that this step will temporarily disable root and TWRP)
2. Boot into system, download and install OTA
3. Reflash modified boot.img from Chainfire and TWRP recovery (i.e., fastboot flash boot boot.img, fastboot flash recovery twrp-2.8.7.x-angler.img)
4. Install SuperSU using TWRP
rsmolen said:
Here is what I do. So long as you do not flash or wipe userdata, this method should maintain all your app data and settings:
1. Download files:
* Latest factory image from: https://developers.google.com/android/nexus/images?hl=en and extract .img files to a folder on your computer with fastboot.
* Modified boot.img from: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344 and extract boot.img to the same folder (I usually rename it to modifiedboot.img so I have have the original boot.img and modified images in the same folder).
* Latest version of TWRP from: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976 (direct link: https://dl.twrp.me/angler/) to the same folder
* Systemless SuperSU from: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (do not unzip) to /sdcard/download folder on phone
2. Flash .img files using the following commands:
fastboot flash bootloader bootloader.img [using current name of bootloader image - not necessary if no change to bootloader from prior factory image]
fastboot reboot-bootloader
fastboot flash radio radio-angler.img [using current name of radio image - not necessary if no change to radio from prior factory image]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot modifiedboot.img
fastboot flash recovery twrp-2.8.7.x-angler.img [replace x with the current version]
3. Boot into recovery (TWRP), flash SuperSU.zip from /sdcard/download, wipe davlik and regular caches and reboot to system.
Upon reboot, Android will optimize all of your apps, so the first boot will take a while. However, the whole process usually takes me about 20 minutes - perhaps a bit more if I do a TWRP backup before upgrading (recommended).
---------- Post added at 10:25 AM ---------- Previous post was at 10:12 AM ----------
OR - as I suggested in another thread, if you really want to take the OTA, instead of the above method, you probably could do the following (note I haven't tested this, but I assume it would work) - files can be downloaded using the same links listed above:
1. Flash stock boot.img and recovery.img from current factory image (e.g., if you are currently running MDB08K, you will want to download the MDB08K factory image (not the newer one) and extract the boot.img and recovery.img files from that archive - note that this step will temporarily disable root and TWRP)
2. Boot into system, download and install OTA
3. Reflash modified boot.img from Chainfire and TWRP recovery (i.e., fastboot flash boot boot.img, fastboot flash recovery twrp-2.8.7.x-angler.img)
4. Install SuperSU using TWRP
Click to expand...
Click to collapse
Thanks. This is helpful, even though it makes me feel like a baby. It's sad, considering we old-timers have been flashing **** that, at the time, seemed more complex. Or maybe it didn't. Never bricked a windows CE device. This isn't really 'complex' anyway. Just feels like far too many steps. I want a twrp flashable image, simply.
Sent from my Nexus 6P using Tapatalk
rborg said:
Thanks. This is helpful, even though it makes me feel like a baby. It's sad, considering we old-timers have been flashing **** that, at the time, seemed more complex. Or maybe it didn't. Never bricked a windows CE device. This isn't really 'complex' anyway. Just feels like far too many steps. I want a twrp flashable image, simply.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Just use a custom rom and update as it gets updated.
More features, updated more often, flashable.
Easiest way to go.
Phazmos said:
Just use a custom rom and update as it gets updated.
More features, updated more often, flashable.
Easiest way to go.
Click to expand...
Click to collapse
Uhh how is flashing a custom ROM easier than just fastboot flashing system.img and vendor.img?
Cares said:
Uhh how is flashing a custom ROM easier than just fastboot flashing system.img and vendor.img?
Click to expand...
Click to collapse
Uhhh the most obvious answer would be no other peripherals required.
Phazmos said:
Uhhh the most obvious answer would be no other peripherals required.
Click to expand...
Click to collapse
Think about that for a second...you would have needed fastboot already to get a custom recovery onto your phone in the first place. You are flashing an entire ROM versus 2 files so it takes longer already. You'll need to update more files on first boot. Not faster or easier so not sure where your argument comes from.
Cares said:
Think about that for a second...you would have needed fastboot already to get a custom recovery onto your phone in the first place. You are flashing an entire ROM versus 2 files so it takes longer already. You'll need to update more files on first boot. Not faster or easier so not sure where your argument comes from.
Click to expand...
Click to collapse
Sorry, but if ya think it's slower or harder to download a rom and flash it, I don't know what to tell ya.
I really just want stock + xposed. So, I should really be looking for flashable security updates. Rooting doesn't necessarily imply that someone wants a custom ROM. *Not* needing a custom ROM to customize the OS is what xposed is all about. Making this choice doesn't mean we are idiots.
Sent from my Nexus 6P using Tapatalk
rborg said:
I really just want stock + xposed. So, I should really be looking for flashable security updates. Rooting doesn't necessarily imply that someone wants a custom ROM. *Not* needing a custom ROM to customize the OS is what xposed is all about. Making this choice doesn't mean we are idiots.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Xposed is very unstable. Most of the time causes reboots.
rsmolen said:
[/COLOR]
OR - as I suggested in another thread, if you really want to take the OTA, instead of the above method, you probably could do the following (note I haven't tested this, but I assume it would work) - files can be downloaded using the same links listed above:
1. Flash stock boot.img and recovery.img from current factory image (e.g., if you are currently running MDB08K, you will want to download the MDB08K factory image (not the newer one) and extract the boot.img and recovery.img files from that archive - note that this step will temporarily disable root and TWRP)
2. Boot into system, download and install OTA
3. Reflash modified boot.img from Chainfire and TWRP recovery (i.e., fastboot flash boot boot.img, fastboot flash recovery twrp-2.8.7.x-angler.img)
4. Install SuperSU using TWRP
Click to expand...
Click to collapse
Did anyone try this? Did it work? I am rooted but I have stock recovery (instead of flashing TWRP I just booted into it with fastboot for the SU install). Do I still need to flash the stock boot and recovery img's? I'm not sure what changes when SU is intalled. Thanks!
Edit - Does the "full unroot" button on SuperSU work? Is this all I would need to do since I did not permanently flash TWRP?
just did this. works perfectly. all data still there.
thanks!!!