Related
Currently on VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4
kernel: [email protected]#1
system: 140.45.5.ghost_verizon.Verizon.en.US
build: 13.11.1Q2.X-69-3
NO ROM And I only changed two items:
1. VzwEntitlementService.apk via [http://forum.xda-developers.com/showthread.php?t=2536166] by changing the originalVzwEntitlementService.apk to VzwEntitlementService.apk.bak
2. Remove bootloader warning image
Question: for the 4.4.2 update (hopefully coming soon)
1. Can I just get the 4.4.2 update via OTA with my current setup
2. Or do I have a to flash back to stock
Thank you much.
and I'm new to xda.
you need to flash the stock recovery and then run the OTA. after it installs flash your custom recovery back.
dray_jr said:
you need to flash the stock recovery and then run the OTA. after it installs flash your custom recovery back.
Click to expand...
Click to collapse
Thanks, if someone has an unlocked bootloader but is not rooted and they removed the bootloader unlocked message using the command:
fastboot flash logo logo.bin
and used a logo.bin file that has the original kitkat 4.4 logo in it, can they take the OTA without doing anything else?
Also, when you flash the stock recovery, you become unrooted and so then if you flash your custom recovery after the OTA, you reroot, right?
Are you supposed to wipe the davlik/cache or anything else like that before you take the OTA?
Cozume said:
Thanks, if someone has an unlocked bootloader but is not rooted and they removed the bootloader unlocked message using the command:
fastboot flash logo logo.bin
and used a logo.bin file that has the original kitkat 4.4 logo in it, can they take the OTA without doing anything else?
Also, when you flash the stock recovery, you become unrooted and so then if you flash your custom recovery after the OTA, you reroot, right?
Are you supposed to wipe the davlik/cache or anything else like that before you take the OTA?
Click to expand...
Click to collapse
as for the logo i am not sure i think you should be ok .
as for when you flash the stock recovery yes you loose root but when you reflash the custom recovery if you still dont have root just reinstall SuperSU and you will be good to go,
and anytime i flash something i always wipe the cache/davlik
dray_jr said:
and anytime i flash something i always wipe the cache/davlik
Click to expand...
Click to collapse
really so when I flashed my custom recovery to root for the first time, I should have wiped that?
Cozume said:
really so when I flashed my custom recovery to root for the first time, I should have wiped that?
Click to expand...
Click to collapse
you dont have too but it is recommended
dray_jr said:
as for when you flash the stock recovery yes you loose root but when you reflash the custom recovery if you still dont have root just reinstall SuperSU and you will be good to go
Click to expand...
Click to collapse
Hmm, I have a VZW DE, unlocked bootloader, flashed TWRP then SuperSU to get root, then flashed the stock recovery and still have root. I honestly can't remember if I re-rooted after flashing back to stock recovery, but I don't think that I did. Are you saying that flashing to stock recovery should have unrooted the phone? What does it mean if it didn't? I hope I'm remembering correctly.
I'd like to be able to get the OTA 4.4.2 update from VZW when available but I keep reading it's not possible with root. How do I remove root if reflashing the stock recovery didn't do it? I'm coming from a GNex which was much simpler so I want to make sure I'm prepared for the OTA when it arrives. Thanks!
Melarsa said:
Hmm, I have a VZW DE, unlocked bootloader, flashed TWRP then SuperSU to get root, then flashed the stock recovery and still have root. I honestly can't remember if I re-rooted after flashing back to stock recovery, but I don't think that I did. Are you saying that flashing to stock recovery should have unrooted the phone? What does it mean if it didn't? I hope I'm remembering correctly.
I'd like to be able to get the OTA 4.4.2 update from VZW when available but I keep reading it's not possible with root. How do I remove root if reflashing the stock recovery didn't do it? I'm coming from a GNex which was much simpler so I want to make sure I'm prepared for the OTA when it arrives. Thanks!
Click to expand...
Click to collapse
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
flashallthetime said:
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Got it, that's what I'll do when the time comes. Thanks!
flashallthetime said:
OK,listen and listen closely, by far the best way to accept the ota is flash stock recovery and also flash your system.img, I don't care what other folks say, I've been here for 3 ota's , this will prevent any chances of having issues when accepting the ota. You may also flash Verizon's sbf firmware when available, the later is what I prefer
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
fbiryujin said:
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
Click to expand...
Click to collapse
Why would you need to do that? /data isn't going anywhere in the process of flashing system and recovery and then taking an OTA
piccit said:
Why would you need to do that? /data isn't going anywhere in the process of flashing system and recovery and then taking an OTA
Click to expand...
Click to collapse
I thought it might be different because I'm rooted, and encrypted.
fbiryujin said:
Could I do a TWRP backup of /data and just flash the entire system back to new, take the OTA and TWRP restore /data?
Or does /data contain some stuff that is linked to the version of Android I did the backup with?
Click to expand...
Click to collapse
You can try to restore your data after you upgrade, there is no guarantee you won't have any issues but it won't be a huge problem, you'll just have to factory reset. It no different when you flash a custom ROM , if the developer uses a new base then often they request you to do a clean fresh install, otherwise you'll have issues
Sent on my Gummy running Lenoto X
flashallthetime said:
You can try to restore your data after you upgrade, there is no guarantee you won't have any issues but it won't be a huge problem, you'll just have to factory reset. It no different when you flash a custom ROM , if the developer uses a new base then often they request you to do a clean fresh install, otherwise you'll have issues
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I'm not using a custom ROM though.
fbiryujin said:
I'm not using a custom ROM though.
Click to expand...
Click to collapse
I understand that, try it and see what happens, you might be OK restoring your data , no harm in trying
Sent on my Gummy running Lenoto X
flashallthetime said:
I understand that, try it and see what happens, you might be OK restoring your data , no harm in trying
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
So far no official update available to me even after flashing the stock image from Moto. My biggest goal here is to find a way to backup and restore nandroids from the encrypted phone.
Flash and relock Moto X manually
No lie my a$$hole did pucker up though the whole process but... success woohoo!
I followed the instruction on Motorola website [https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images] one thing I did not have is 'Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory)' had to do some searching; came across [http://forum.xda-developers.com/showthread.php?t=1138092] Thanks for that.
DETAILS (So this is what I was working with):
VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4 | system: 140.45.5.ghost_verizon.Verizon.en.US | build: 13.11.1Q2.X-69-3
Did this on my Mac, NOT on PC
Steps:
1. got recovery image
2. got Motorola fastboot utility from | http://forum.xda-developers.com/showthread.php?t=1138092 moto-fastboot-osx.zip
3. used the fastboot from Darwin folder
4. follow steps from motorola website, but did not oem lock [$ fastboot oem lock]
5. last step reboot [$ fastboot reboot] a$$hole pucker up
But success, everything booted up properly even had the warning bootloader unlocked image
There was one point when it got to the Verizon boot image; it took abit longer a$$hole pucker up but finished booting.
Then phone went through the setup process (like new).... It's Miller time!
Come on 4.4.2 update via OTA
_slam said:
No lie my a$$hole did pucker up though the whole process but... success woohoo!
I followed the instruction on Motorola website [https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images] one thing I did not have is 'Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory)' had to do some searching; came across [http://forum.xda-developers.com/showthread.php?t=1138092] Thanks for that.
DETAILS (So this is what I was working with):
VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4 | system: 140.45.5.ghost_verizon.Verizon.en.US | build: 13.11.1Q2.X-69-3
Did this on my Mac, NOT on PC
Steps:
1. got recovery image
2. got Motorola fastboot utility from | http://forum.xda-developers.com/showthread.php?t=1138092 moto-fastboot-osx.zip
3. used the fastboot from Darwin folder
4. follow steps from motorola website, but did not oem lock [$ fastboot oem lock]
5. last step reboot [$ fastboot reboot] a$$hole pucker up
But success, everything booted up properly even had the warning bootloader unlocked image
There was one point when it got to the Verizon boot image; it took abit longer a$$hole pucker up but finished booting.
Then phone went through the setup process (like new).... It's Miller time!
Come on 4.4.2 update via OTA
Click to expand...
Click to collapse
I just want to make sure that when you did this all it did was remove root and replace the bootloader, not any data or settings you had on your phone. That is the only thing that worries me before I decide to do the 4.4.2 update.
_slam said:
Currently on VZN, XT1060, MotoX, DEV unlocked bootloader, TWRP, SuperSU:
version: 4.4
kernel: [email protected]#1
system: 140.45.5.ghost_verizon.Verizon.en.US
build: 13.11.1Q2.X-69-3
NO ROM And I only changed two items:
1. VzwEntitlementService.apk via [http://forum.xda-developers.com/showthread.php?t=2536166] by changing the originalVzwEntitlementService.apk to VzwEntitlementService.apk.bak
2. Remove bootloader warning image
Question: for the 4.4.2 update (hopefully coming soon)
1. Can I just get the 4.4.2 update via OTA with my current setup
2. Or do I have a to flash back to stock
Thank you much.
and I'm new to xda.
Click to expand...
Click to collapse
1) You don't need to do much. Revert the Entitlement hack you did, you need the one that came on the device, not a hacked one.
2) Flash the stock recovery back to your phone. You'll need the stock recovery to install the OTA. Just do it the same way you flashed TWRP to your phone but use the stock recovery.img file from the 4.4 .sbf ( http://sbf.droid-developers.org/download.php?device=0&file=5 )
You will NOT lose root flashing the stock recovery, you will NOT lose root taking the OTA.
After updating, use Xposed and the Moto Tether module for tethering instead of using a hacked version of the app.
shadowmonk36 said:
I just want to make sure that when you did this all it did was remove root and replace the bootloader, not any data or settings you had on your phone. That is the only thing that worries me before I decide to do the 4.4.2 update.
Click to expand...
Click to collapse
If you have the Dev edition from VZW, it's simple to install the OTA.
This is what I did as I had root and xposed installed.
1. Download 4.4.2 file from XDA and cut and paste it from download folder to root of sdcard
2. Flash stock 4.4 recovery image via fastboot.
3. Flash 4.4 system image using mfastboot (must use mfastboot)
4. Boot into recovery
5. Apply update and selected the OTA zip.
6. Reboot
7. Power down and boot back into fastboot.
8. Flash TWRP, allow it to root, reboot.
9. Reinstall Xposed framework.
All my data and settings were still there. Even my xposed modules reactivated. No additional setup and my phone was exactly the same but had 4.4.2.
Only caveat is only do this if you've never installed other OS's and have only taken official OTAs from VZW. You need to be on the right bootloader. Don't brick your phone.
Sent from my Dev Edition Moto X
Hello. Can you tell me if flashing FUU.zip and then stock rom nand backup(/system) of the same version in recovery, then flashing stock recovery.img to replace custom recovery is the same and will result the same as flashing ruu.zip from the beginning? ( exemple: i dont want to go through all OTA updates right to lollipop, and waste 3 hours, as the last avaliable RUU is so old, so i consider install FUU of latest kitkat along with nand backup of /system and then updating to lollipop via OTA will be faster and result the same) thanks.
pankozin said:
Hello. Can you tell me if flashing FUU.zip and then stock rom nand backup(/system) of the same version in recovery, then flashing stock boot.img to replace custom recovery is the same and will result the same as flashing ruu.zip from the beginning? ( exemple: i dont want to go through all OTA updates right to lollipop, and waste 3 hours, as the last avaliable RUU is so old, so i consider install FUU of latest kitkat along with nand backup of /system and then updating to lollipop via OTA will be faster and result the same) thanks.
Click to expand...
Click to collapse
Yes that will work just fine
clsA said:
Yes that will work just fine
Click to expand...
Click to collapse
Thanks. So, the FUU.zip will erase and clear all remains left after 100500 modified firmware and Rom flashes? Will it clear root directory? It's the main reason, why I want to do a reset. I start to get some weird bugs with the phone. Need to clear all, but have no time for all the OTAs after a RUU
pankozin said:
Thanks. So, the FUU.zip will erase and clear all remains left after 100500 modified firmware and Rom flashes? Will it clear root directory? It's the main reason, why I want to do a reset. I start to get some weird bugs with the phone. Need to clear all, but have no time for all the OTAs after a RUU
Click to expand...
Click to collapse
do a factory reset from stock recovery
clsA said:
do a factory reset from stock recovery
Click to expand...
Click to collapse
How can i do it? Launch reset from the ROM settings when stock recovery is installed? Can this do better then just a FUU+/system stock flash?
pankozin said:
How can i do it? Launch reset from the ROM settings when stock recovery is installed? Can this do better then just a FUU+/system stock flash?
Click to expand...
Click to collapse
After flashing stock recovery, boot to the bootloader and choose recovery.
Hold volume up and tap power, you'll see the stock recovery. Choose factory reset, this will format the /data partition and all user data
i need to do OTA update , already with twrp and root , so in order to do ota update i need to fastboot stock recovery !
upload a stock recovery.img if anybody having it.
download shamu image , extract to get the recovery.IMG
It's a Nexus load what you wish. Images here :
https://developers.google.com/android/nexus/images#shamu
Sent from my Google N6 on VZ
yes i know that , i thought rather downloading whole image if somebody could provide me the recovery image only well thanks. ill do it.
ashupulse said:
yes i know that , i thought rather downloading whole image if somebody could provide me the recovery image only well thanks. ill do it.
Click to expand...
Click to collapse
It needs to be more than just "stock recovery". It needs to be the exact version the ota will expect. So you'll have to download the matching image to your version you're on now...
Which if you're doing that, hadn't you just as well download the latest 5.1 image and just flash all that?
I would just flash the factory image..... less chance of a mess....
Never done an official OTA on my old N5, N10, or N6. I just fastboot the update radio, bootloader, system, and twrp recovery. Boot into recovery, reboot and install su when prompted. Always on the latest android version without losing data
mymusicathome said:
Never done an official OTA on my old N5, N10, or N6. I just fastboot the update radio, bootloader, system, and twrp recovery. Boot into recovery, reboot and install su when prompted. Always on the latest android version without losing data
Click to expand...
Click to collapse
I hear you. if anything, back in the days, we used to avoid the OTA. I'm not sure why everybody has such a hard on for it.
Sent from my Google N6 on VZ
Only ota I took was when my n5 forced one on me out of the box. Never intentionally took one since android 1.5
recovery from 5.0.1
rootSU said:
It needs to be more than just "stock recovery". It needs to be the exact version the ota will expect. So you'll have to download the matching image to your version you're on now...
Which if you're doing that, hadn't you just as well download the latest 5.1 image and just flash all that?
Click to expand...
Click to collapse
yes you are right actually i downloaded 5.1 exctracted recovery , flashed via fastboot.... and i hit error.
so lesson is recovery from 5.0.1 is needed.
ashupulse said:
yes you are right actually i downloaded 5.1 exctracted recovery , flashed via fastboot.... and i hit error.
so lesson is recovery from 5.0.1 is needed.
Click to expand...
Click to collapse
How are you flashing?
mymusicathome said:
Never done an official OTA on my old N5, N10, or N6. I just fastboot the update radio, bootloader, system, and twrp recovery. Boot into recovery, reboot and install su when prompted. Always on the latest android version without losing data
Click to expand...
Click to collapse
When updated to 5.1 from 5.0.1 -- I had to do Factory Data Reset, since after update N6 was showing 32GB instead of 64GB.
Was there a way to avoid Factory Data Reset ? Thank you!
Many of you have heard by now that 5.1.1 is out, and we should receive an update soon on our stock rom Nexus 6. I just bought a Nexus 6 64gb, XT1103, and it is running the stock rom, rooted, and un-encrypted. I'm wondering if we'll lose root and un-encrypt if we take the update, and loose data if we re-unencrypt. What have your experiences been on the stock rom 5.1 update?
bovineyard said:
Many of you have heard by now that 5.1.1 is out, and we should receive an update soon on our stock rom Nexus 6. I just bought a Nexus 6 64gb, XT1103, and it is running the stock rom, rooted, and un-encrypted. I'm wondering if we'll lose root and un-encrypt if we take the update, and loose data if we re-unencrypt. What have your experiences been on the stock rom 5.1 update?
Click to expand...
Click to collapse
While the update will download, it will not install with root and an unencrypted kernel.
IF you want to take the OTA, then you will need to fastboot flash the boot.img and system.img from the factory image. Boot.img will encrypt your kernel, but you will not loose data (but you will have to factory reset, again, if you want to unencrypt, which will wipe data). Flashing the system.img will remove root and flash stock recovery.
cam30era said:
While the update will download, it will not install with root and an unencrypted kernel.
IF you want to take the OTA, then you will need to fastboot flash the boot.img and system.img from the factory image. Boot.img will encrypt your kernel, but you will not loose data (but you will have to factory reset, again, if you want to unencrypt, which will wipe data). Flashing the system.img will remove root and flash stock recovery.
Click to expand...
Click to collapse
i think with root but encrypted will do the update
HitNrun_ said:
i think with root but encrypted will do the update
Click to expand...
Click to collapse
Nope, not on Lollipop. Kitkat and before, yes. Not anymore.
cam30era said:
Nope, not on Lollipop. Kitkat and before, yes. Not anymore.
Click to expand...
Click to collapse
so unroot and encypted will do the trick? what about the bootloader, will it work with unlocked or should it be relocked too?
5.1.1 is NOT officially out for the nexus 6. it is in aosp though. thats two differing things. stock is on 5.1.
HitNrun_ said:
so unroot and encypted will do the trick? what about the bootloader, will it work with unlocked or should it be relocked too?
Click to expand...
Click to collapse
The OTA package only looks at system.img and boot.img. Of course you need stock recovery to install it. And the "unroot" option inside SuperSU is insufficient. It leaves some traces around that will prevent the OTA from loading. Flash the stock system.img.
And afterwards, when unencrypting, you'll have to fastboot format userdata. Which will wipe your SDcard again.
HitNrun_ said:
so unroot and encypted will do the trick? what about the bootloader, will it work with unlocked or should it be relocked too?
Click to expand...
Click to collapse
Bootloader status has no effect on the OTA.
I have rooted, but encrypted 5.1, and got OTA5 5.1.1, I am on custom recovery,
should I flash stock recovery before flashing? plus, after installing, I will need to regain root access right? my data/apps will stay intact right?
ibraheeemz said:
I have rooted, but encrypted 5.1, and got OTA5 5.1.1, I am on custom recovery,
should I flash stock recovery before flashing? plus, after installing, I will need to regain root access right? my data/apps will stay intact right?
Click to expand...
Click to collapse
As it says above, you cannot FLASH the update if you are rooted, even with a stock recovery.
You will have to flash the system.img and boot.img of the Stock factory image. IF the full factory image of the version you want is available here: https://developers.google.com/android/nexus/images
...download it, extract the system and boot.img and fastboot flash them. Job done. If the version you need is only available in an OTA file, you'll need to flash the system and boot of the expected version (i.e. the one you're on now) AND flash the recovery to accept the OTA
danarama said:
As it says above, you cannot receive the update if you are rooted, even with a stock recovery.
You will have to flash the system.img and boot.img of the Stock factory image. IF the full factory image of the version you want is available here: https://developers.google.com/android/nexus/images
...download it, extract the system and boot.img and fastboot flash them. Job done. If the version you need is only available in an OTA file, you'll need to flash the system and boot of the expected version (i.e. the one you're on now) AND flash the recovery to accept the OTA
Click to expand...
Click to collapse
I am using a custom recovery, on a rooted but STOCK 5.1, and I already got OTA, I downloaded it as well, but needed to make sure before upgrading, that it doesn't cause data lose if I move to stock recovery, and want to regain root after flashing 5.1.1,
anyway, i flashed stock recovery, then proceeded with the update, it tried flashing but showed "error" at the android screen, so, I don't whats missing, as I was using stock 5.1, just unlocked it, rooted it, and flashed customer recovery,
ibraheeemz said:
I am using a custom recovery, on a rooted but STOCK 5.1, and I already got OTA, I downloaded it as well, but needed to make sure before upgrading, that it doesn't cause data lose if I move to stock recovery, and want to regain root after flashing 5.1.1,
anyway, i flashed stock recovery, then proceeded with the update, it tried flashing but showed "error" at the android screen, so, I don't whats missing, as I was using stock 5.1, just unlocked it, rooted it, and flashed customer recovery,
Click to expand...
Click to collapse
When I said receive, I meant flash. You cannot FLASH the update if you are rooted. Period. Read my post again but substitute the word receive for flash.
danarama said:
When I said receive, I meant flash. You cannot FLASH the update if you are rooted. Period. Read my post again but substitute the word receive for flash.
Click to expand...
Click to collapse
got it, but still looking for the answer, will I loose data after flashing system.img? or while regaining root after 5.1.1 update?
ibraheeemz said:
got it, but still looking for the answer, will I loose data after flashing system.img? or while regaining root after 5.1.1 update?
Click to expand...
Click to collapse
No. Only factory reset or unlocking the bootloader loses data. System.img is the rom, flashing to /system. Boot.img is the kernel, flashing to /boot. if you flash these separately, userdata.img is not flashed to /data, so your /data partition remains in tact.
root doesn't touch /data either. Just /system
HitNrun_ said:
i think with root but encrypted will do the update
Click to expand...
Click to collapse
How do you get root while leaving it encrypted?
Arfyness said:
How do you get root while leaving it encrypted?
Click to expand...
Click to collapse
No OTA update will flash with any mods to system, boot, or recovery. No way, no how.
Evolution_Tech said:
No OTA update will flash with any mods to system, boot, or recovery. No way, no how.
Click to expand...
Click to collapse
Yeahhh I get that now. It's got to verify that what's already there matches what it's supposed to be updating.
I'm looking here because I'm on Fi now, and there are more implications there than I realized before. Not that those matter too much, I do want stock. Just trying to see how I can stay current, be rooted, and not break Fi. Thankfully it's a Nexus device so it's not throwing up insane device restrictions blocking root access.
I want to be able to update system and boot, as they come available, with a recovery like TWRP or CWM. Then reapply SuperSU flash after that. What I'm not sure of is whether I can even do that. I'm fuzzy on the whole " encrypted device" thing. Does that apply to the images at https://developers.google.com/android/nexus/images#shamu
Would I be hosed if I took the system and boot images and flash those to update from one version to the next?
Arfyness said:
Yeahhh I get that now. It's got to verify that what's already there matches what it's supposed to be updating.
I'm looking here because I'm on Fi now, and there are more implications there than I realized before. Not that those matter too much, I do want stock. Just trying to see how I can stay current, be rooted, and not break Fi. Thankfully it's a Nexus device so it's not throwing up insane device restrictions blocking root access.
I want to be able to update system and boot, as they come available, with a recovery like TWRP or CWM. Then reapply SuperSU flash after that. What I'm not sure of is whether I can even do that. I'm fuzzy on the whole " encrypted device" thing. Does that apply to the images at https://developers.google.com/android/nexus/images#shamu
Would I be hosed if I took the system and boot images and flash those to update from one version to the next?
Click to expand...
Click to collapse
You absolutely can, it's just that if you wish to decrypt, you'll have to format data. I've had this device, since launch and I'm still encrypted. Not an issue for me. But you can just flash, individually, everything but userdata and keep your data intact, each time a new image becomes available. Then just flash TWRP and then SuoerSu from TWRP. If you've unencrypted, OTA won't flash. You can always update manually.
edit - this was a duplicate. i can't delete it.
Evolution_Tech said:
You absolutely can, it's just that if you wish to decrypt, you'll have to format data. I've had this device, since launch and I'm still encrypted. Not an issue for me. But you can just flash, individually, everything but userdata and keep your data intact, each time a new image becomes available. Then just flash TWRP and then SuoerSu from TWRP. If you've unencrypted, OTA won't flash. You can always update manually.
Click to expand...
Click to collapse
Oohhh, wait, so flash from fastboot, except flash SuperSU from TWRP? (update.zip style?) Is only the data partition encrypted then? If that's the case why are folks decrypting? Unlocking the bootloader requires it, but what is that required for?
And thank you loads BTW! I'm so far behind! I'm coming off 3 years of rooted, stable SGS3 stock, last updated to 4.1.2. There were no further stock updates that I wanted, (too many bugs) and everything was working so I left well enough alone.
(I probably would have messed about with CM and other roms, if I had not initially bricked the thing trying to put TWRP on... and had to send it for somebody to JTAG reprogram it. Thought about it several times, but never wanted to chance it again.)
Thanks again!
I want a clean install on my mate 20.
I have unlocked bootloader and want to install stock rom with root prevs.
My current install process:
I first
flash with twrp
then remove encryption
then wipe cache/dalvik
then format data,
then install romaur v1.x from twrp.
when get into emui i use emui flasher1.1apk to go to the firmware i want.
This process takes to long and what file-format does the firmware need to be in order to install stock rom from twrp??
I love the romaur, but there are some components removed from the rom that i have gotten used to in emui.
The rom is ultra fast tough! (sorry Aur)
So how to makes this work:
TWRP
Format data
clear cache/dalvik
install 9.0.0.xxx (optional rom)
Finish with a clean install and then root with patched_boot.img
Then install magisk ++++
Any ideas? Hope my post makes sense.
Regards, Kenneth, Norway
#mate20problackincludeNMstorage
I guessing there is no way to install stock rom from twrp then??
???
how about using hstool to upgrade to the latest firmware and then unlock bootloader and flash patched magisk to recovery_ramdisk partition.
and if you want twrp you can flash it to ercovery partition
Daniehabazin said:
how about using hstool to upgrade to the latest firmware and then unlock bootloader and flash patched magisk to recovery_ramdisk partition.
and if you want twrp you can flash it to ercovery partition
Click to expand...
Click to collapse
With HStool does The bootloader get locked again?
Sure that sounds good. I Will try. Does it update or wipe clean to install??
fromiOS2Android said:
With HStool does The bootloader get locked again?
Sure that sounds good. I Will try. Does it update or wipe clean to install??
Click to expand...
Click to collapse
i'm not sure but i think the bootloader get's locked, and when you unlock the bootloader the phone get's wiped.
when i had locked bootloader and used hstool to update between versions my data was not wiped.
Daniehabazin said:
i'm not sure but i think the bootloader get's locked, and when you unlock the bootloader the phone get's wiped.
when i had locked bootloader and used hstool to update between versions my data was not wiped.
Click to expand...
Click to collapse
Ok. Thanks. Just grotten used to using twrp now, but i'll try HStool next update?? thanks again
fromiOS2Android said:
Ok. Thanks. Just grotten used to using twrp now, but i'll try HStool next update?? thanks again
Click to expand...
Click to collapse
no problem