Related
Unlocked Bootloader.
CWM.
Root.
Fail in updating, with message something like assert fail apply_update_check status 7.
Revert to Stock Recovery and Unroot (bootloader is still unlock), update again, result in error with the android robot and red exclamation.
Happen to my Nexus 7 and Galaxy Nexus as well (same unlock bootloader cwm root, same revert method, same error).
Has anyone face this and any solution to make OTA works?
Get back to stock, then try again
Sent from my Nexus 4 using xda premium
Had the same problem. This will answer all your questions
http://forum.xda-developers.com/showthread.php?t=2145848
thanks for the link. it did not directly make my device can be updated, but incase others have this problem and looking for solution, here are the things I did and fix it:
flash boot.img and flash system.img
these 2 files are needed to be at STOCK, I extract from the factory image, and flash through fastboot.
flashing these 2 files WILL NOT CAUSE application to be formatted (like what I thought at the first time).
It will simply remove any tweak done to system such as ads blocking (adaway, etc), battery icon mod, etc.
Then, you can update just fine.
Again, BIG THANKS to xda community.
raijinshou said:
thanks for the link. it did not directly make my device can be updated, but incase others have this problem and looking for solution, here are the things I did and fix it:
flash boot.img and flash system.img
these 2 files are needed to be at STOCK, I extract from the factory image, and flash through fastboot.
flashing these 2 files WILL NOT CAUSE application to be formatted (like what I thought at the first time).
It will simply remove any tweak done to system such as ads blocking (adaway, etc), battery icon mod, etc.
Then, you can update just fine.
Again, BIG THANKS to xda community.
Click to expand...
Click to collapse
Sorry, but I searched and searched but I still don't understand. I removed all my mods.
I wanted to update to 4.2.2 but it says apply_patch_check error about Currents.
How do I flash that boot.img and system.img? Trough custom recovery or stock? And where can I find those files? Thanks.
Guzanni said:
Sorry, but I searched and searched but I still don't understand. I removed all my mods.
I wanted to update to 4.2.2 but it says apply_patch_check error about Currents.
How do I flash that boot.img and system.img? Trough custom recovery or stock? And where can I find those files? Thanks.
Click to expand...
Click to collapse
boot.img and system.img can be founded in the STOCK ROM, here is the link for STOCK 4.2.1 for Nexus 4:
https://docs.google.com/open?id=0B_zuNWpIf1ujNlFDVnZ3dzg2WEU
(Source: http://www.randomphantasmagoria.com/firmware/nexus-4/occam/ )
Extract the file, you can find boot.img and system.img inside it.
To flash these 2 files, since I am not familiar with fastboot, I am using Nexus 4 Toolkit to help with it.
You can download Nexus 4 Toolkit: http://goo.im/devs/mskip/toolkit/google_nexus4/Google_Nexus_4_ToolKit_v1.3.0.exe
(Source: http://forum.xda-developers.com/showthread.php?t=1995688 )
Copy boot.img and system.img to Nexus 4 Toolkit folder of "put_img_files_to_flash_here"
then using "11. Boot or Flash .img Files to Device option", flash the file to the correct partition
(when flashing boot.img, to boot partition | when flashing system.img, to system partition).
For some reason I can't flash a franco kernel, I tried using CWM, CWM Touch, TWRP recoveries to flash, but nothing works.
Help please :[
arlay said:
For some reason I can't flash a franco kernel, I tried using CWM, CWM Touch, TWRP recoveries to flash, but nothing works.
Help please :[
Click to expand...
Click to collapse
It is a .boot file and not a zip file and you cannot flash it with CWM, flash it with fastboot duh. adb command: fastboot flash boot [name file].
gee2012 said:
It is a .boot file and not a zip file and you cannot flash it with CWM, flash it with fastboot duh. adb command: fastboot flash boot [name file].
Click to expand...
Click to collapse
I used the zip version of the kernel file not the .boot file
arlay said:
I used the zip version of the kernel file not the .boot file
Click to expand...
Click to collapse
Try the img boot file. What message do you get if the install fails? Download the kernel again, maybe a corrupt download.
gee2012 said:
Try the boot file. What message do you get if the install fails? Download the kernel again, maybe a corrupt download.
Click to expand...
Click to collapse
I don't get any message. The kernel flashes, but when I check the kernel version it lists my old kernel.
I just started using the Nexus 7 (WiFi) and I am on 4.2.1 and I am rooted. I rooted with the Wug's Toolkit. Anyway I want to update to 4.2.2 and I don't want to use any custom rom's, I just want to have an original update that I can flash without having to unroot. I have flashed my nexus with Clockwork Mod Recovery. Any places were I can get this rom and how I can install it?
Help Please!!
hettige677 said:
I just started using the Nexus 7 (WiFi) and I am on 4.2.1 and I am rooted. I rooted with the Wug's Toolkit. Anyway I want to update to 4.2.2 and I don't want to use any custom rom's, I just want to have an original update that I can flash without having to unroot. I have flashed my nexus with Clockwork Mod Recovery. Any places were I can get this rom and how I can install it?
Help Please!!
Click to expand...
Click to collapse
Hello there!
What about a little search? is a search bar in every part of the forum!!!
Anyway there you go:
http://forum.xda-developers.com/showthread.php?t=1745781
Just don't get used to it :good:
Read the forum rules!
So I downloaded the zip but it won't install properly it says error code 7??
Sent from my Nexus 7 using xda app-developers app
n/m
hettige677 said:
So I downloaded the zip but it won't install properly it says error code 7??
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
That's because you are using a custom recovery. You can either flash a stock recovery or edit some files in the zip so you can flash it in the custom recovery.
Leonhan said:
That's because you are using a custom recovery.
Click to expand...
Click to collapse
Possibly, but probably not. In most of the reports that have been coming in - when the users actually report the full error message rather than saying something ambiguous like "I got a Status 7 error" - the problems revolve around altered/removed files in /system, or having a custom kernel (boot or LNX partition) installed. That suggests that the recovery version is not causing assert() failures.
The other thing to rememder is that the program that is interpreting the edify updater-script is the "updater-binary" program which is shipped inside the OTA - so it is virtually identical independent of the choice of recovery (other than perhaps kernel behavior differences).
Leonhan said:
You can either flash a stock recovery or edit some files in the zip so you can flash it in the custom recovery.
Click to expand...
Click to collapse
Even though what you are saying here does only require being able to operate a plain-text editor and a zip tool, it's way above the heads of most folks who think that OTAs should work on non-stock ROMs. And I'm not sure how these folks would be better off with partially-patched ROMs. In any event, if this course is taken indeed a custom recovery would need to be used for this, as modifying the zip contents will break the OTA package signing, so the stock recovery couldn't be used.
The OP should just
- make a full nandroid backup of what they have now
- download the factory 4.2.2 images from Google
- extract the system.img file and boot.img images
( hint for windoze users: 7-zip understands .tgz files)
fastboot flash boot boot.img
fastboot flash system system.img
- reflash a basic SuperSU or Superuser root kit
Sort of crude, but it's a decent hack for the lazy or poorly informed. It won't "erase my data", but presumably it will break whatever it was that altered the stock system and/or boot partitions - the very things that are causing the OTA to fail on them with their rooted & modified ROMs.
If they don't like the result, they can simply restore their nandroid backup.
Is it possible on an unlocked nexus 7 to effectively install a custom ROM from fastboot with the command "fastboot update </path/to/your/RomFile.zip>" without using a custom recovery such as TWRP?
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Fastboot is used to flash .img file not .zip
norcal61 said:
Is it possible on an unlocked nexus 7 to effectively install a custom ROM from fastboot with the command "fastboot update </path/to/your/RomFile.zip>" without using a custom recovery such as TWRP?
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
What you can do is fastboot flash system system.img.
system.img can come from a backup, a google stock image or make it yourself
So there is no way to flash an actual zip file via fastboot? I found this article here on xda http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Why would you want to? Flash recovery with fastboot and flash your ROM from there.
Sent from my Nexus 7 using Tapatalk HD
korockinout13 said:
Why would you want to? Flash recovery with fastboot and flash your ROM from there.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I want to be able to format my internal SD from TWRP which would wipe everything off the SD including any zip files then flash the zip from my computer from a command prompt with the tablet booted into the boot loader.
Sent from my Nexus 7 using Xparent Green Tapatalk 2
norcal61 said:
I want to be able to format my internal SD from TWRP which would wipe everything off the SD including any zip files then flash the zip from my computer from a command prompt with the tablet booted into the boot loader.
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
That's quite pointless to format everything... But in this case, you can adb sideload the zip from recovery. No need for the file on the sd card.
Sent from my Nexus 7 using Tapatalk HD
norcal61 said:
So there is no way to flash an actual zip file via fastboot? I found this article here on xda http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Only STOCK factory ROMs are flashable this way...
cf. this line from the flash-all.* script for the full factory image of Jellybean 4.2.2.. for 'grouper'.
Code:
fastboot -w update image-nakasi-jdq39.zip
In image-nakasi-jdq39.zip the following files are found...
boot.img
recovery.img
system.img
userdata.img
----
CUSTOM ROMs, however, can only be flashed via a CUSTOM RECOVERY, such as CWM or TWRP.
And as korockinout13 alludes to, it's a trivial matter to FASTBOOT FLASH a custom recovery... and then flash the ROM of your choice.
If you already have FASTBOOT (and your question suggests that you do)... then what's the problem?
Rgrds,
Ged.
The bootloaders of different Android devices have differing capabilities precisely because they are proprietary. Moreover, it is the bootloader that actually implements the heavy lifting of installs etc - the PC fastboot program does little more than send ASCII commands and push blobs of data across the USB cable.
Some Android devices have had bootloaders that understand how to unpack .zip files that contain other types of archives (.tar files, et cetera) but required that the .zip file is placed onto an external SD card using a standardized name for that device. (When the bootloader starts up, it would look for that file automatically). But this was for signed factory bundles, not for arbitrary aftermarket customization. In any event, this doesn't apply to the N7 afaik.
None of these behaviors are standardized though; each vendor decides how it will interpret and respond to fastboot commands from the PC.
The N7 bootloader clearly understands what a sparse ext4 image file is (for use with system.img and userdata.img files) - if it handled them as a pure binary blob, how would it be possible to use the same userdata.img file with 8Gb, 16Gb, and 32Gb devices? Moreover, the N7's "fastboot format" command clearly is capable of creating ext4 filesystems.
So would it be possible to create "sparse ext4" system.img/userdata.img image files corresponding to a custom ROM that could flashed in exactly the same way as the factory image using fastboot? Yes, absolutely. (I've done just that.)
But this is NOT the same thing as taking a custom ROM .zip file (intended to be processed by a recovery using an "edify" script) and flashing it with fast boot; it ain't that easy.
hi,
i have a nexus 7 and i want to flash a custom rom but i wiped everything and the zip gone from my tablet now the tablet is without os,please help!!
paul20 said:
hi,
i have a nexus 7 and i want to flash a custom rom but i wiped everything and the zip gone from my tablet now the tablet is without os,please help!!
Click to expand...
Click to collapse
Better to stick with stock and not attempt to flash custom ROMs if you don't know how to use a custom recovery or toolkit.
paul20 said:
hi,
i have a nexus 7 and i want to flash a custom rom but i wiped everything and the zip gone from my tablet now the tablet is without os,please help!!
Click to expand...
Click to collapse
Not a big deal. You need to download the factory image for your nexus 7 and find instructions on how to restore with fastboot. That will take you back to factory stock. Or another option is to fastboot flash TWRP custom recovery and use the adb sideload feature within TWRP to flash a custom ROM of your choice. You can find instructions on both of these procedures here at xda or with a simple Google search. Let me know if that works out for you. If you need more help I can give you a hand when I get home from work
Sent from my Nexus 7 using Xparent Green Tapatalk 2
everything okay i flashed stock rom with the toolkit and then the custom one,it's ok now i am not so noob but it's my first tablet without external sd card and i got panik
thanks everyone
paul20 said:
hi,
i have a nexus 7 and i want to flash a custom rom but i wiped everything and the zip gone from my tablet now the tablet is without os,please help!!
Click to expand...
Click to collapse
Fastboot flash a custom recovery. Then, there are many threads showing how to get the .zip to the device for flashing.
Sent from my Nexus 7 using xda premium
norcal61 said:
Not a big deal. You need to download the factory image for your nexus 7 and find instructions on how to restore with fastboot. That will take you back to factory stock. Or another option is to fastboot flash TWRP custom recovery and use the adb sideload feature within TWRP to flash a custom ROM of your choice. You can find instructions on both of these procedures here at xda or with a simple Google search. Let me know if that works out for you. If you need more help I can give you a hand when I get home from work
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Hey guys,
I made the same mistake as paul20 with my HTC ONE and your answer saved my morning, thanks! adb sideload feature rocks!
rebel1699 said:
Fastboot flash a custom recovery. Then, there are many threads showing how to get the .zip to the device for flashing.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Can you point me to one of those threads?
fastboot error
GedBlake said:
Only STOCK factory ROMs are flashable this way...
cf. this line from the flash-all.* script for the full factory image of Jellybean 4.2.2.. for 'grouper'.
Code:
fastboot -w update image-nakasi-jdq39.zip
In image-nakasi-jdq39.zip the following files are found...
boot.img
recovery.img
system.img
userdata.img
----
CUSTOM ROMs, however, can only be flashed via a CUSTOM RECOVERY, such as CWM or TWRP.
And as korockinout13 alludes to, it's a trivial matter to FASTBOOT FLASH a custom recovery... and then flash the ROM of your choice.
If you already have FASTBOOT (and your question suggests that you do)... then what's the problem?
Rgrds,
Ged.
Click to expand...
Click to collapse
========================================
the fastboot says --
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
i m porting the stock rom (it is a zip file) which has boot.img ,recovery.img ,system.img ,userdata.img into it yet the error comes.
the prob is that the rom is not detecting my sd card and neither the CWM i tried a different sd card yet it isnt detecting...i alst tried mounting sd card it showed error there also! plz help me! everything was working sommoth! this problem came after i ported droid_dd_gb_13.3 v3 ...my device is micromax a57 plz help mee!!!
GedBlake said:
Only STOCK factory ROMs are flashable this way...
cf. this line from the flash-all.* script for the full factory image of Jellybean 4.2.2.. for 'grouper'.
Code:
fastboot -w update image-nakasi-jdq39.zip
In image-nakasi-jdq39.zip the following files are found...
boot.img
recovery.img
system.img
userdata.img
----
CUSTOM ROMs, however, can only be flashed via a CUSTOM RECOVERY, such as CWM or TWRP.
And as korockinout13 alludes to, it's a trivial matter to FASTBOOT FLASH a custom recovery... and then flash the ROM of your choice.
If you already have FASTBOOT (and your question suggests that you do)... then what's the problem?
Rgrds,
Ged.
Click to expand...
Click to collapse
where do you get those .img files from?? bY the way im using sony xperia sp and bricked i guess ;(
no adb, can't enable USB debugging
korockinout13 said:
That's quite pointless to format everything... But in this case, you can adb sideload the zip from recovery. No need for the file on the sd card.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
What if you can't enable USB debugging because you accidentally formated /persist and can't get into your system? 16 hours of that arrow turning and nothing...
Can someone help me, I have same problem but i extracted my Zip file and have Boot.img if i flash that will it work again
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!!!