**When i will get all of the information needed,i will edit this thread and make it as simple for reaching the objective for everyone,as possible.**
Recently i got an OTA update for my nexus 5x device,a security patch form june 2017.
I`ve rooted it with this tutorial: https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
My question is: In order to install that OTA i need to follow "11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)" section from Heisenberg`s tutorial or this "9. How To Update To A New Build Of The Stock ROM" section of the same tutorial?.On the "9. update the build of a stock rom" it says no data will be wiped yet this statement of google offical site still concerns me : "Warning: Installing this factory image will erase all data from the device. While it may be possible to restore certain data backed up to your Google Account, apps and their associated data will be uninstalled. Before proceeding, please ensure that data you would like to retain is backed up to your Google Account."
So what`s the safest way to OTA update your rooted device?Please provide some explanations.
ionut15 said:
**When i will get all of the information needed,i will edit this thread and make it as simple for reaching the objective for everyone,as possible.**
Recently i got an OTA update for my nexus 5x device,a security patch form june 2017.
I`ve rooted it with this tutorial: https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
My question is: In order to install that OTA i need to follow "11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)" section from Heisenberg`s tutorial or this "9. How To Update To A New Build Of The Stock ROM" section of the same tutorial?.On the "9. update the build of a stock rom" it says no data will be wiped yet this statement of google offical site still concerns me : "Warning: Installing this factory image will erase all data from the device. While it may be possible to restore certain data backed up to your Google Account, apps and their associated data will be uninstalled. Before proceeding, please ensure that data you would like to retain is backed up to your Google Account."
So what`s the safest way to OTA update your rooted device?Please provide some explanations.
Click to expand...
Click to collapse
It is very simple actually. Here's a quick lesson for you to try out. Download any factory image then examine the flash-all.sh script inside the zip. Find the line command that begins with "-w." This command will cause the entire phone to be wiped when the script is executed, as Google highlights.
You can edit and remove the entire -w line to leave your internal storage intact. However, TWRP will be replaced because this script installs each partition including the stock recovery.
I don't believe my guide could be any clearer. Manually entering the commands for each partition, as my guide states, does not wipe the device. With fastboot, the primary ways to wipe the device are: executing the flashall script for a factory image, flash the userdata.img, issue fastboot format userdata, or lock/unlock the bootloader.
Follow my guide to update
Sent from my Nexus 5X using Tapatalk
@SlimSnoopOS thank you,very clear response
ionut15 said:
@SlimSnoopOS thank you,very clear response
Click to expand...
Click to collapse
Also, make sure to flash root and any other mods BEFORE booting up once you update.
My pleasure! That's why this great place exists and I'm always happy to pass on information that I've learned.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Also, make sure to flash root and any other mods BEFORE booting up once you update.
My pleasure! That's why this great place exists and I'm always happy to pass on information that I've learned.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Can i ask what are the cons of not doing so? I would flash the factory img that will lead to replacing custom recovery with the stock one and cancelling my root.After flashing it,i asumme that my phone will boot up,so i need to power it off again and proceed to install recovery and root again via adb.How can i install them before the phone will be booting up?
Sent from my Nexus 5X using Tapatalk
I always followed this guide here: http://elementalx.org/how-to-install-android-monthly-security-updates/
Here's the quick summary:
Download the newest factory update for your device
Extract all files
Update system boot vendor bootloader radio
Flash whatever root and/or kernel you want.
Wipe cache/dalik
Reboot
Worked like a charm, and only took me ~10 or so minutes once I knew what I was doing.
crazyates said:
I always followed this guide here: http://elementalx.org/how-to-install-android-monthly-security-updates/
Here's the quick summary:
Download the newest factory update for your device
Extract all files
Update system boot vendor bootloader radio
Flash whatever root and/or kernel you want.
Wipe cache/dalik
Reboot
Worked like a charm, and only took me ~10 or so minutes once I knew what I was doing.
Click to expand...
Click to collapse
in the tutorial provided by @SlimSnoopOS at point "11" it says to enter these commands in adb cmd "fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img" but i didn`t get the cache file with the factory.img.So i just skip erasing the cache then flashing it or i have to download from somewhere else?
ionut15 said:
Can i ask what are the cons of not doing so? I would flash the factory img that will lead to replacing custom recovery with the stock one and cancelling my root.After flashing it,i asumme that my phone will boot up,so i need to power it off again and proceed to install recovery and root again via adb.How can i install them before the phone will be booting up?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
It is just a time saving step. If you manually install each partition excluding recovery.img, you can still boot directly into TWRP from bootloader to flash root and now TWRP will persist. This is more relevant on Nougat and newer, this didn't happen on Marshmallow.
Installing a OTA/factory image will always override every partition including TWRP recovery. But if you manually install each image except recovery, upon booting into the phone the stock recovery will replace TWRP. To get root now you will need to: boot into bootloader, flash TWRP, then boot into TWRP to flash your mods afterwards. Make sense?
ionut15 said:
in the tutorial provided by @SlimSnoopOS at point "11" it says to enter these commands in adb cmd "fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img" but i didn`t get the cache file with the factory.img.So i just skip erasing the cache then flashing it or i have to download from somewhere else?
Click to expand...
Click to collapse
Please do not erase cache. Skip this step when using Nougat and newer. I have to update this part of the guide.
Sent from my Nexus 5X using Tapatalk
ionut15 said:
in the tutorial provided by @SlimSnoopOS at point "11" it says to enter these commands in adb cmd "fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img" but i didn`t get the cache file with the factory.img.So i just skip erasing the cache then flashing it or i have to download from somewhere else?
Click to expand...
Click to collapse
Cache doesn't matter. In TWRP, if you "wipe cache", it just formats the /cache volume, which is all you'll ever need to do. There should be no need to manually flash anything into the cache volume (it rebuilds itself automatically).
crazyates said:
Cache doesn't matter. In TWRP, if you "wipe cache", it just formats the /cache volume, which is all you'll ever need to do. There should be no need to manually flash anything into the cache volume (it rebuilds itself automatically).
Click to expand...
Click to collapse
Thank you,managed to update the security patch and works just fine.
Sent from my Nexus 5X using Tapatalk
crazyates said:
Cache doesn't matter. In TWRP, if you "wipe cache", it just formats the /cache volume, which is all you'll ever need to do. There should be no need to manually flash anything into the cache volume (it rebuilds itself automatically).
Click to expand...
Click to collapse
Thank you again for your time and devotion.You cleared off all of my doubts.Furthermore i hope someone who's in my situation could find this topic helpful.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
It is just a time saving step. If you manually install each partition excluding recovery.img, you can still boot directly into TWRP from bootloader to flash root and now TWRP will persist. This is more relevant on Nougat and newer, this didn't happen on Marshmallow.
Installing a OTA/factory image will always override every partition including TWRP recovery. But if you manually install each image except recovery, upon booting into the phone the stock recovery will replace TWRP. To get root now you will need to: boot into bootloader, flash TWRP, then boot into TWRP to flash your mods afterwards. Make sense?
Please do not erase cache. Skip this step when using Nougat and newer. I have to update this part of the guide.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you again for your time and devotion.You cleared off all of my doubts.Furthermore i hope someone who's in my situation could find this topic helpful.
Sent from my Nexus 5X using Tapatalk
If you want install OTA updates while your device is rooted, use Flashfire.
AFK269 said:
If you want install OTA updates while your device is rooted, use Flashfire.
Click to expand...
Click to collapse
its a straight-forward method,unfortunately my system partition was changed and flashfire can't flash ota.
Sent from my Nexus 5X using Tapatalk
ionut15 said:
its a straight-forward method,unfortunately my system partition was changed and flashfire can't flash ota.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Then flash factory images with adb fastboot commands
Related
For some reason I'm just not able to Google this answer or find it here on XDA.
I'm on 5.0.1 (LRX22C) and want to go to 5.0.2 (LRX22G). I have downloaded an OTA update capture and tried to adb sideload it.
It failed. After a sec I thought, "duh. I'm rooted with franco kernel installed." I then did the following:
* Used SuperSU to unroot
* Booted to bootloader
* Flashed stock recovery and kernel
* Rebooted to recovery
* Attempted adb sideload again
This still gave a failure message.
The only other post I've seen where anyone is attempting the same suggests to use Nexus Root Tookit. I'm running Xubuntu. I've loaded it through wine but all the files it downloads are failing hash checks (though the app).
Can anyone post how to go from rooted 5.0.1 to 5.0.2 (LRX22G from LRX22C) without loosing user land data? I'd really do not want to flash the recovery image.
Notes: When trying to sideload with latest CWM recovery the script says that I'm on 4.0.4 (I think) and with TWRP it says I'm on 4.3. With stock recovery it gives me an error about the recovery script (7) or something similar.
Thanks,
Mike G.
Make sure you have downloaded the proper OTA for Nexus 7(2013).
Hashcheck fails in Nexus Root Toolkit is common.After Hashfails,there will be a dialog box which contains the steps to do it manually with the Link to the files.Download it & follow the instruction.
I hope this helps
I'm having the exact same problem. I'm attaching what's appearing on TWRP.
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
I just used wugfresh's toolbox to do it. A piece of cake. I enjoyed a cup of coffee while I watched being updated.
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
yosmokinman said:
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
So I can just ”fastboot flash system system.img" from the 5.0.2 image and not loose data?
That seems like it would be the easiest. I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Sent from my Nexus 7 using XDA Free mobile app
^Yes. It's a good idea to flash boot as well just to get in the habit of it, it didn't change this time I don't think but I could later. Only flash the bootloader if it's a new version no need otherwise.
I simply ran:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
Done, flash su through twrp to get root back.
You probably don't need to format cache but theres no reason not to and it could save you some trouble.
newkydawg said:
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
Click to expand...
Click to collapse
that worked perfectly for me. thx
mikejr83 said:
I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Click to expand...
Click to collapse
NRT opens a terminal window (a real-time log) and tells you exactly what it's doing while it does its work.
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
I have a n7 2013 I have already rooted and installed twrp and SuperSU. I'm currently running 4.4.2 and to update to 5.02. Currently I'm getting the ota update msg for 4.4.3 which I've continued to ignore. With google not messaging me to update to 5.02 makes me think it's required to go to 4.4.3,4.4.4,5,5.02 is that correct? Or can one jump directly to 5.02? I want to keep root and twrp and my existing data I see mentioning of restoring stock recovery first. Why would one do that? What's the point of installing a custom recovery in the first place?
Long time ago I read that ota will work when rooted, but you'll lose root which then can be restored with twrp without losing data. Is that no longer true? Or is it only true of KitKat but not lollipop?
My recent apps button is no longer working. And when I go to Developer Options, I see Developer Options are not available for this user. Anyone else seeing that?
I installed MHC19J first and that was the incorrect version. I then flashed MMB29V and then the problems above started. I couldn't access quick menu, the recent apps button didn't work, and Developer Options showed as not available for this user. I just did a factory data reset and that seemed to get everything working again, but always a pain to have set everything up again! Damn Google! :-/
Probably due to you flashing the wrong image before flashing the correct one. Had no such problems after flashing this morning
Skickat från min Nexus 5X via Tapatalk
I too am on MHC19J , but why is it the wrong image? I actually find my phone working rather well with it, but I guess I will have to wipe and install MMB29V
granets said:
I too am on MHC19J , but why is it the wrong image? I actually find my phone working rather well with it, but I guess I will have to wipe and install MMB29V
Click to expand...
Click to collapse
Only do that if you are not rooted etc. If you use TWRP recovery and are not prompted for a password when booting into recovery, then you have the right image. It does work, the problem is trying to use Custom Recovery to flash SuperSU. Check that thread below.
https://www.reddit.com/r/nexus5x/comments/49e0ij/601_mhc19j/
I just flashed the J image. Installed TWRP 3.0 and got the pin code request. Cancelled it, mounted OTG, flashed SuperSU 2.68, and Osmosis busybox. Rebooted and all looks great. Restoring from Titanium now and Android Pay still works. It really looks like only TWRP needs to be updated. Haven't flashed a kernel yet, I'll let this one settle in for a few days.
no issues here on 19J. modified boot image here
bobby janow said:
I just flashed the J image. Installed TWRP 3.0 and got the pin code request. Cancelled it, mounted OTG, flashed SuperSU 2.68, and Osmosis busybox. Rebooted and all looks great. Restoring from Titanium now and Android Pay still works. It really looks like only TWRP needs to be updated. Haven't flashed a kernel yet, I'll let this one settle in for a few days.
Click to expand...
Click to collapse
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
mickey4mice said:
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
Click to expand...
Click to collapse
I'm sorry I don't know. I haven't decrypted in quite some time now. I also haven't used xposed in a long time either. I don't ever format userdata or flash the userdata.img unless I absolutely have to. I'm encrypted, systemless, 2.68 SU and twrp 3.0. I'm leery to do anything now until twrp gets fixed for the J build. Although I might flash a J kernel via OTG if there comes one.
mickey4mice said:
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
Click to expand...
Click to collapse
Unless something has changed, you will be encrypted after first boot (same for prior releases). You'd need to sideload and flash SuperSU before booting since TWRP 3.0 currently cannot access internal storage on MHC19J.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Unless something has changed, you will be encrypted after first boot (same for prior releases). You'd need to sideload and flash SuperSU before booting since TWRP 3.0 currently cannot access internal storage on MHC19J.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I always flash google images sans userdata for every monthly security data, my decrypted data/storage has never re-encrypted itself after first boot before I flash systemless SU via TWRP. But those were done with TWRP v2x, has anything changed with TWRP 3x in this regard?
mickey4mice said:
I always flash google images sans userdata for every monthly security data, my decrypted data/storage has never re-encrypted itself after first boot before I flash systemless SU via TWRP. But those were done with TWRP v2x, has anything changed with TWRP 3x in this regard?
Click to expand...
Click to collapse
Are you booting into system or booting into TWRP from bootloader after flashing the monthly factory images?
Sent from my Nexus 5X using Tapatalk
i had some trouble so i clicked the flash all batch file. Anyone know how to root this build? i cant get super su zip file i transfer to show up in twrp. The file is there but twrp doesnt see it.
SlimSnoopOS said:
Are you booting into system or booting into TWRP from bootloader after flashing the monthly factory images?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I was wondering if someone could direct me on how to put Supersu.zip into the /cache as from what I have read so far it is possible to root on mhc19j you just need to move Supersu there as it is not encrypted.
Bump
Dominicano2 said:
I was wondering if someone could direct me on how to put Supersu.zip into the /cache as from what I have read so far it is possible to root on mhc19j you just need to move Supersu there as it is not encrypted.
Click to expand...
Click to collapse
They likely used "ADB push" command to move SuperSU from their computer to the /cache directory.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
They likely used "ADB push" command to move SuperSU from their computer to the /cache directory.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks could you tell me what I am doing wrong I started abd and I do the following command adb push supersu.zip /cache/ and it comes back with Permission Denied
edit: Never mind I booted into twrp with fastboot boot and once there I did the adb push and was able to install Supersu
Dominicano2 said:
Thanks could you tell me what I am doing wrong I started abd and I do the following command adb push supersu.zip /cache/ and it comes back with Permission Denied
edit: Never mind I booted into twrp with fastboot boot and once there I did the adb push and was able to install Supersu
Click to expand...
Click to collapse
Sweet, glad you got that figured out
How is the new update in terms of making the phone better?
gvsukids said:
How is the new update in terms of making the phone better?
Click to expand...
Click to collapse
Seems like the lag pulling down the notification window that happened time to time is gone. Feels a little snappier but will need a week of up time to know for sure.
Notice that the "keep WiFi on during sleep" setting for "never" still doesn't work on the 5x. Also still have an audio bug that duplicates the source a second behind on Bluetooth when a notification is received which is disappointing.
I successfully flashed and booted, during the flaashing process I received a failed to mount in TWRP 3.0.2.0 and upon boot I got "Android System: There is an internal problem with your device please contact manufacturer for details" message.
Any one on 6P received the same message?
As stated in release announcement you need vendor.img. Use May's vendor.img
Finding vendor.img
Pirateghost said:
As stated in release announcement you need vendor.img. Use May's vendor.img
Click to expand...
Click to collapse
I've recently flashed Paranoid Android version 6 and get the same error. Been searched now for an hour trying to find the correct vendor.img, but I'm struggeling with that. Could you please elaborate on where I can find this? That would be great
Thanks a lot!
Erik
goofygofs said:
I've recently flashed Paranoid Android version 6 and get the same error. Been searched now for an hour trying to find the correct vendor.img, but I'm struggeling with that. Could you please elaborate on where I can find this? That would be great
Thanks a lot!
Erik
Click to expand...
Click to collapse
The latest PA version has vendor IMG baked in.
Pirateghost said:
The latest PA version has vendor IMG baked in.
Click to expand...
Click to collapse
That's strange. I tried both the 6.0 and 6.0.1 but I get the corrupted warned nontheless. I noticed the difference in size though, 70 vs 380MB of space. What could the warning be a sign of?
goofygofs said:
That's strange. I tried both the 6.0 and 6.0.1 but I get the corrupted warned nontheless. I noticed the difference in size though, 70 vs 380MB of space. What could the warning be a sign of?
Click to expand...
Click to collapse
The size indicated on the website is messed up. Pay no attention to that.
Pirateghost said:
The size indicated on the website is messed up. Pay no attention to that.
Click to expand...
Click to collapse
That explains a lot. But the warning display upon boot, is that something I should pay attention to and fix, or is it insignificant?
Were you using N developer preview before flashing ROM?
Pirateghost said:
Were you using N developer preview before flashing ROM?
Click to expand...
Click to collapse
I was a few weeks ago, but then I flashed Chroma ROM with Marshmallow that I've been running till today. I remember flashing some boot.img "back then" but I don't recall its name. When installed PA, I wiped dalvik, cache and data twice, then flashed 6.0/6.0.1
You might try wiping /system before flashing too. My top recommendation would be to revert device back to factory image and try again. N dev preview can flash new firmware that is incompatible
Pirateghost said:
You might try wiping /system before flashing too. My top recommendation would be to revert device back to factory image and try again. N dev preview can flash new firmware that is incompatible
Click to expand...
Click to collapse
I'll go ahead and revert to stock, and report back after trying again
Pirateghost said:
You might try wiping /system before flashing too. My top recommendation would be to revert device back to factory image and try again. N dev preview can flash new firmware that is incompatible
Click to expand...
Click to collapse
Tried to revert back to factory image and do it all over - unfortunately same result. Tried to wipe /system before flash too, same result.
goofygofs said:
Tried to revert back to factory image and do it all over - unfortunately same result. Tried to wipe /system before flash too, same result.
Click to expand...
Click to collapse
When flashing, please do
fastboot format cache
fastboot format userdata
fastboot flash cache cache.img
fastboot flash userdata userdata.img
remember to flash all the other files, starting with radio, then bootloader, then fastboot reboot-bootloader and then continue flashing the files
for cache and userdata remember to format them as stated above, worth a try.
benleonheart said:
When flashing, please do
fastboot format cache
fastboot format userdata
fastboot flash cache cache.img
fastboot flash userdata userdata.img
remember to flash all the other files, starting with radio, then bootloader, then fastboot reboot-bootloader and then continue flashing the files
for cache and userdata remember to format them as stated above, worth a try.
Click to expand...
Click to collapse
Sorry for the late reply, I was broad for a week. Looks like something I could try, though the userdata flash will wipe my storage includes photos and such. Could you explain why this would make a difference, as opposed to what I've tried already?
benleonheart said:
When flashing, please do
fastboot format cache
fastboot format userdata
fastboot flash cache cache.img
fastboot flash userdata userdata.img
remember to flash all the other files, starting with radio, then bootloader, then fastboot reboot-bootloader and then continue flashing the files
for cache and userdata remember to format them as stated above, worth a try.
Click to expand...
Click to collapse
went ahead and tried it, same result during boot unfortunately. However, it does work after bootup, and I don't receive any alerts while using it
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!
Edit : Nougat running on my op3.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?
To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!
anshulajain said:
I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!
Click to expand...
Click to collapse
I don't have any issues with ext4, infact i do feel ext4 is more stable than f2fs so file system is my last concern. Thanks for your method, but then how did u root again? Installing nougat is fine but what after that? I have read that you can't use modified twrp without formatting internal memory first, as it'll show you the pin issue. Let me know how do you propose a safe method to achieve root.
Renosh said:
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?
Click to expand...
Click to collapse
Yes i am encrypted, rooted, stock OOS 3.2.8 + Franco kernel. Official TWRP(not modified). I am using ext4, never used f2fs at all. The time to backup data and then to restore it all back is the reason formatting is not an "preferred" option for me. I can do it, but i would have to wait until i find enough time to do the whole process. I am in a full time job, so i hope you would understand.
Puddi_Puddin said:
To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!
Click to expand...
Click to collapse
Well this again defeats the purpose of my original question, but thanks mate. I would definitely read the guide if decide to switch to f2fs.
@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.
I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0
Puddi_Puddin said:
@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.
Click to expand...
Click to collapse
Thanks a lot for informing me mate. I really don't want to decrypt my storage as of now. I guess flashing stock recovery is the only solution now. Will hope someone would pick up the twrp and update it.
anshulajain said:
I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0
Click to expand...
Click to collapse
Seems like stock recovery is the best way as of now. Seems like I'll have to love without root until someone updates twrp to support encrypted storage.
I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...
Zielony360 said:
I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.
Click to expand...
Click to collapse
That i already knew mate. But i WANT my storage to remain encrypted. And that's the issue with modified TWRP. You can't enter into recovery on that if your storage is encrypted.
kpmohamedhussain said:
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...
Click to expand...
Click to collapse
Again, "You can't enter into recovery on modified TWRP if your storage is encrypted." So i won't be able to enter into twrp in the first place, let alone flash anything.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.
Go to twrp. Press backup. Select only data. Save to PC youre backup for safety..
3.2.8 it's Android 6, 4.0 it's Android 7. Some apps might not work from base to base.
If you want to change to F2FS it will format youre phone, wipe phone full internal memory. If you want to change it back to ext4, same.
Clean flash, full wipe it's always better.
dmoses1969 said:
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.
Click to expand...
Click to collapse
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.
anshulajain said:
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.
Click to expand...
Click to collapse
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.
abhibnl said:
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.
Click to expand...
Click to collapse
I dont know. I found this on Oneplus forum. May be worth trying. Just not 100% sure.....
Thanks! Will try and let you know
abhibnl said:
Thanks! Will try and let you know
Click to expand...
Click to collapse
Well, I tried something, waiting on it to finishing booting and see how it went.
I flashed twrp-3.0.2-1.28-oneplus3p version,
Flashed the OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip inside TWRP,
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip right after flashing OTA zip.
Its rebooting and says Android is upgrading. Fingers crossed.
EDIT: Its booted and I am on Nougat, didnt lose my data and phone is still encrypted!
Edit: Ended up having issues with settings app locking up. So, I went a different route and its all working great now.
Downloaded the stock recovery image and renamed it to recovery.img
Make sure after you rename it its not named recovery.img.img, If you have show file extensions enabled on your pc you should already see the file extension.
Rebooted to bootloader - adb flash recovery recovery.img
Using the volume keys and power button selected - reboot recovery.
Now in stock recovery - flashed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
After rom is done flashing, went right back into bootloader. Did not let my phone reboot to start the OS.
Renamed twrp-3.0.2-1.28-oneplus3p.img to recovery.img
adb flash recovery recover.img
Powered off phone and Manually boot it into recovery by holding Power + Volume Down button.
Phone booted into TWRP
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip
Wiped cache / dalvik
Rebooted system from TWRP and waited. System is really smooth now, no issues yet. Been playing with it for awhile now.
During the booting up process it might take a minute and it will reboot twice. Dont get nervous like I did thinking it was going to start bootlooping. It booted just fine. I read in a nother thread that SuperSU is what causes it to boot twice.
So......Now I have OOS 4.0 Nougat, Rooted, Encrypted and everything seems to be working fine.
Hello. Is it any ways to fix that problem? OEM unlocking is not allowed, bootloader locked. IT stuck in bootloop. But recovery and fastboot works. It has the 6.0.1 MM29M "00ww_1_450". Already tried to wipe /cache and facotry data reset + 7.0 OTA via abd sideload (it end with an error "E3006: Not enough free space on /cache to apply patches). Thank you!
Use this Flashing method-> https://forum.xda-developers.com/nextbit-robin/help/how-to-flash-stock-fails-noob-edition-t3584146
Don;t make a mistake don't skip a step. Read through carefully.
valhallen.282 said:
Use this Flashing method-> https://forum.xda-developers.com/nextbit-robin/help/how-to-flash-stock-fails-noob-edition-t3584146
Don;t make a mistake don't skip a step. Read through carefully.
Click to expand...
Click to collapse
Man. I know all of these. My bootloader locked and I can't unlock it.
Fastboot OEM unlock?
valhallen.282 said:
Fastboot OEM unlock?
Click to expand...
Click to collapse
To do that you need to enable it in dev settings. You can't do it unless you can access system.
xBane you seem to find me everywhere. Anyway. If he has adb push working. Attempting to push the update OTA would only make it worse. Pushing the flashable zip of stock ROM should have worked as it is a smaller package.
Stock updates are made to slot 2 and then symlinked to all the data from slot 1. Recovery then reverses the slot so that the back up system partition is always there. But without cache mount it would fail. I was hoping to hear from the OP to ask if fastboot boot TWRP works.