Hi...
I would like to upgrade my phone which has the systemless root.
I tried flashing the current stock recovery to see if OTA goes thru, but it doesn't. (It's a shame, since the OTA is only 11mb and I tend to like conciseness... but oh well.)
Since the OTA didn't go thru, I'd like to flash the upgrade myself - I have downloaded it.
It has the following images - is the following right if I want to upgrade stock ROM, without erasing my data -
radio-bullhead-m8994f-2.6.30.0.68.img - Flash
bootloader-bullhead-bhz10k.img - Flash
userdata.img - Do not flash - Will erase user data.
vendor.img - Flash? - I have Project Fi. Does it matter?
recovery.img - Do not flash - But it's okay if you flash, reflash TWRP.
cache.img - Flash? - Is it same as erasing cache?
boot.img - Flash - And reroot from TWRP.
Edit: There are a couple of threads which are on similar lines, but they are all about some other objective and not specifically on upgrading, e.g. "unroot and rever to stock", etc.
Yes. I usually flash recovery, wipe cache, then flash twrp image, and re-root via TWRP.
https://www.androidpit.com/how-to-get-android-m-preview
You forgot to flash the most important partition: system.
For manually updating to the latest build without losing your data or having to reinstall everything you will pretty much always be able to get away with doing the following:
flash radio, vendor, system and boot.
reflash supersu (and every other module you flashed in twrp)
wipe cache/dalvik
reboot.
Works like a charm and you will not even have to setup anything again. Should take you max 15 minutes total.
I do reccommend starting with a nandroid backup beforehand just in case.
Ya i just updated (flashed) to 6.0.1 myself too last week. Systemless root. And now this 11mb ota happens.
So unroot, revert back to stock recovery, and apply ota update MMB29P?
How do i revert back to stock recovery?
^ one mentions flash recovery....flash recovery, wipe cache, flash twrp recovery, and then reroot.
^one doesnt mention flash recovey....flash radio, flash vendor, flash system, and flash boot?
vypinoy said:
Ya i just updated (flashed) to 6.0.1 myself too last week. Systemless root. And now this 11mb ota happens.
So unroot, revert back to stock recovery, and apply ota update MMB29P?
How do i revert back to stock recovery?
^ one mentions flash recovery....flash recovery, wipe cache, flash twrp recovery, and then reroot.
^one doesnt mention flash recovey....flash radio, flash vendor, flash system, and flash boot?
Click to expand...
Click to collapse
Just follow the steps I mentioned using the files from mmb29p factory image.
It's a method that has proven itself as working. No need messaging with the ota.
If you want to try to force the ota by flashing stock recovery by all means try that.
Keep in mind to check what build you are on and take the stock recovery from the factory image of your current build.
If you installed anything (exposed eg) to system partition the ota still won't work probably.
I'm saying just update from factory image mmb29p instead of ota since your basically will be downloading and extracting a factory image anyway so you won't save much time time by trying to run the ota.
peltus said:
Just follow the steps I mentioned using the files from mmb29p factory image.
It's a method that has proven itself as working. No need messaging with the ota.
If you want to try to force the ota by flashing stock recovery by all means try that.
Keep in mind to check what build you are on and take the stock recovery from the factory image of your current build.
If you installed anything (exposed eg) to system partition the ota still won't work probably.
I'm saying just update from factory image mmb29p instead of ota since your basically will be downloading and extracting a factory image anyway so you won't save much time time by trying to run the ota.
Click to expand...
Click to collapse
ok thanks
hopefully itll work. ill try it soon. I just had to go back to factory when i tried to flash to 6.0.1 from 6.0... and i kept getting the error when flashing system about it could not allocate ***** bytes. and then there was always an error flashing the vendor. so had to flash all the way back to what it was out of box i think. then go to 6.0.1.. only have time on the weekend. ill update then.... i also edited my build.prop... is that gna revert when i update?
vypinoy said:
ok thanks
hopefully itll work. ill try it soon. I just had to go back to factory when i tried to flash to 6.0.1 from 6.0... and i kept getting the error when flashing system about it could not allocate ***** bytes. and then there was always an error flashing the vendor. so had to flash all the way back to what it was out of box i think. then go to 6.0.1.. only have time on the weekend. ill update then.... i also edited my build.prop... is that gna revert when i update?
Click to expand...
Click to collapse
Yep there build.prop is on system. Back that up and restore it later.
It might also keep the ota from executing.
Google Nexus 5 Android 5.1 does come with lots of bug fixes, performance improvements, menu tweaks, and much much more.
pankaj554 said:
Google Nexus 5 Android 5.1 does come with lots of bug fixes, performance improvements, menu tweaks, and much much more.
Click to expand...
Click to collapse
think you posted in the wrong forum, this is the 5X forum not the 5. Also, 5.1 is old...
peltus said:
Yep there build.prop is on system. Back that up and restore it later.
It might also keep the ota from executing.
Click to expand...
Click to collapse
Got that "could not allocate ____bytes" error again when trying to flash system again. So just did it thru wugfreshs advanced utilities.
Other than that. It worked. Twrp was still there too. Which was weird. Installed SuperSU. And back and running again. Thanks!
Related
So im on 4.4.2 right now with twrp and timur's kernel FI 2013 installed on the tablet. I keep getting an update message, and it will download 4.4.3 and restart, but it restarts into twrp, which is why, I'm guessing, the update doesn't install. What would be a good solution to updating the tablet to 4.4.3, or.4 if it is available? thanx.
[email protected] said:
So im on 4.4.2 right now with twrp and timur's kernel FI 2013 installed on the tablet. I keep getting an update message, and it will download 4.4.3 and restart, but it restarts into twrp, which is why, I'm guessing, the update doesn't install. What would be a good solution to updating the tablet to 4.4.3, or.4 if it is available? thanx.
Click to expand...
Click to collapse
Assuming you haven't modified any /system files the ota wants to update, the next time the update boots you into twrp, it will not automatically install, you must flash the ota manually, you will find the ota zip in /cache...you will have to flash the stock kernel before doing anything though...and if you get an error about a modified file in /system, you will have to revert the change or dirty flash the stock system.img...wipe dalvik though...after flashing the ota wipe dalvik and cache.
mdamaged said:
Assuming you haven't modified any /system files the ota wants to update, the next time the update boots you into twrp, it will not automatically install, you must flash the ota manually, you will find the ota zip in /cache...you will have to flash the stock kernel before doing anything though...and if you get an error about a modified file in /system, you will have to revert the change or dirty flash the stock system.img...wipe dalvik though...after flashing the ota wipe dalvik and cache.
Click to expand...
Click to collapse
If I flash the stock kernel wouldnt that get rid of timurs that I have now. That kernel is the only reason I have this thing. Just correct me if im wrong but your saying flash back to stock, install updatesthen reflash timurs? Why cant I just try and find a clean 4.4.4 zip which I have looked for but never found, and flash it through twrp instead of relying on the nexus' s self update. I looked in the destination u gave me and it wasnt there. Could this be because /cache is a temporary storage location and I have to do this immediately after the download
[email protected] said:
If I flash the stock kernel wouldnt that get rid of timurs that I have now. That kernel is the only reason I have this thing. Just correct me if im wrong but your saying flash back to stock, install updatesthen reflash timurs? Why cant I just try and find a clean 4.4.4 zip which I have looked for but never found, and flash it through twrp instead of relying on the nexus' s self update. I looked in the destination u gave me and it wasnt there. Could this be because /cache is a temporary storage location and I have to do this immediately after the download
Click to expand...
Click to collapse
There are multiple ways to update, you asked about OTA, in order for OTA to work, the OTA expects the device to have certain files at a certain version, one of the things it checks, besides files in /system, when there is a change to it, is the kernel, so a OTA will fail if it checks the kernel and finds timur's in its place, which is why I suggested you just flash the stock boot and system (yes, you can always go back to timur's afterward assuming it is compatible with the new ROM, you will also have to reroot/redo changes to /system).
The OTA is downloaded into /cache, and if the cache is wiped the OTA file will not be there, so once it is downloaded, use a root filemanager, and copy it to your sdcard, then it won't get wiped.
The other way to update is to just flash the changed images individually from the factory images using fastboot, making sure not to flash the images which would wipe any boot, userdata, or custom recoveries...as long as you do not flash boot.img, you will keep timur's kernel, but you will have to reroot/redo changes to /system.
You can also use the factory image flash-all.bat to do this, BUT you must delete the -w option in the bat file, not doing so will result in your device being wiped, you will still have to reflash timur's kernel using this method as well as reroot/redo changes to /system.
Either way, when you update, wipe dalvik and cache before rebooting.
Just from the way you described that to me i can tell that its going to take some time for me to relearn how to do all of this. Are there really any huge benefits to updating from 4.4.2 to .4 that would really make this worth it? Also if I did decide to put all of this effort into it, is there a way that i can save things like my preferences and my homescreen setup and widgets when i do attempt it? thanks
[email protected] said:
Just from the way you described that to me i can tell that its going to take some time for me to relearn how to do all of this. Are there really any huge benefits to updating from 4.4.2 to .4 that would really make this worth it? Also if I did decide to put all of this effort into it, is there a way that i can save things like my preferences and my homescreen setup and widgets when i do attempt it? thanks
Click to expand...
Click to collapse
Yeah, you can use TiB to backup apps and appdata. I would also advise you do a full nandroid (no need to backup cache though). Save them all to your PC.
As for whether it's worth it, you'll have to read the changelogs for yourself and find out if it is to you or not. Really it's not much work at all to update.
You can always wait around for Android L.
I rooted using PurpleDrake...
That said my questions are:
If I restore the Stock boot.img & Stock recovery.img then perform a *full Unroot in SuperSU can I install the OTA without issue?
How about system files... Does PurpleDrake change them in any way that could cause the OTA to fail even after reverting back to stock boot, stock recovery and Un-rooting?
* not positive this step is necessary or will even work?
TIA to anyone with input!
AndroidUzer said:
I rooted using PurpleDrake...
That said my questions are:
If I restore the Stock boot.img & Stock recovery.img then perform a *full Unroot in SuperSU can I install the OTA without issue?
How about system files... Does PurpleDrake change them in any way that could cause the OTA to fail even after reverting back to stock boot, stock recovery and Un-rooting?
* not positive this step is necessary or will even work?
TIA to anyone with input!
Click to expand...
Click to collapse
Wondering same thing. How to get update, the reroot without having to do a full return to stock first.
Try it and let us know. As long as you don't have twrp installed you won't bootloop. If it does get hung up at all just battery pull and boot normally. At worst it won't take and you'll stay on c.
It worked!
Swizzle82 said:
Try it and let us know. As long as you don't have twrp installed you won't bootloop. If it does get hung up at all just battery pull and boot normally. At worst it won't take and you'll stay on c.
Click to expand...
Click to collapse
Here's the steps that worked for me, your mileage may vary.
Made sure all factory apps were present and or defrosted.
Restored the factory recovery and factory boot image (thanks autoprime) with Flashify.
Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip" to the Cache folder.
Re-Enabled OTA using dialer code for hidden menu.
Opened Settings > About phone > Update Center > System updates and was met with the Android System Update screen showing the update "Downloaded and verified 154.6MB", hit the "Restart & install" button and it rebooted to factory recovery installed the update without issue.
No data was lost, No reflashing factory "c" image wiping all your data and having to upgrade from there.
I did lose root but it took <2 minutes to get it back.
I know I could have waited for a TWRP update zip but I ran out of patience.
AndroidUzer said:
Here's the steps that worked for me, your mileage may vary.
Made sure all factory apps were present and or defrosted.
Restored the factory recovery and factory boot image (thanks autoprime) with Flashify.
Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_00-D85110m_00_update.zip" to the Cache folder.
Re-Enabled OTA using dialer code for hidden menu.
Opened Settings > About phone > Update Center > System updates and was met with the Android System Update screen showing the update "Downloaded and verified 154.6MB", hit the "Restart & install" button and it rebooted to factory recovery installed the update without issue.
No data was lost, No reflashing factory "c" image wiping all your data and having to upgrade from there.
I did lose root but it took <2 minutes to get it back.
I know I could have waited for a TWRP update zip but I ran out of patience.
Click to expand...
Click to collapse
Hey, I've been searching through the forums trying to find the stock recovery/boot images for the last hour to no avail. Would it be possible for you to post links to where you found them? Thanks!
EDIT: Annnnnnnnnnd of course as soon as I ask, I find it in another thread I was reading http://forum.xda-developers.com/showpost.php?p=55359856&postcount=125
Where can i found the stock boot.image and stock recovery.img
bjg020683 said:
Where can i found the stock boot.image and stock recovery.img
Click to expand...
Click to collapse
Link in post just above yours...
Thanks
Hi, I think I follow all of your steps except confused about this one:
"Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_ 00-D85110m_00_update.zip" to the Cache folder."
Can someone explain what the above means? Thanks!
laoh said:
Hi, I think I follow all of your steps except confused about this one:
"Then I restored "b1847cae892006ffa11c6822a408fe8528142a54.D85110c_ 00-D85110m_00_update.zip" to the Cache folder."
Can someone explain what the above means? Thanks!
Click to expand...
Click to collapse
That is the actual "m" build OTA update zip file. Why not go straight to "r"?
The only reason I had to restore it was because I had deleted it in the 1st place.
Check your Cache folder for any update zip that may be waiting already.
I did it this way only because I was too impatient to wait for the update zips to be posted here.
But now they exist...
Here is a better way:
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and follow the TWRP instruction for flashing KK builds D85110 C, M, R Untouched_Stock_Restore.zip or even Lollipop D85120B
This will allow you to go straight to "r" skipping "m" all together.
If you are feeling brave and competent you could go straight to Lollipop...
Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
Good luck!
AndroidUzer said:
That is the actual "m" build OTA update zip file. Why not go straight to "r"?
The only reason I had to restore it was because I had deleted it in the 1st place.
Check your Cache folder for any update zip that may be waiting already.
I did it this way only because I was too impatient to wait for the update zips to be posted here.
But now they exist...
Here is a better way:
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and follow the TWRP instruction for flashing KK builds D85110 C, M, R Untouched_Stock_Restore.zip or even Lollipop D85120B
This will allow you to go straight to "r" skipping "m" all together.
If you are feeling brave and competent you could go straight to Lollipop...
Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
Good luck!
Click to expand...
Click to collapse
Thanks for the lengthy explanation. Can I verify if what I'm trying to do is same as what you've done? Here's my situation.
- I have the stock LG 4.4.2 KK rom for D851. Not stock AOSP or CM or any other "custom ROM".
- It is rooted and have TWRP
- The only thing I've really done to the rom is to debloat - used Titanium to freeze lots of apps that came with the LG rom. I have not deleted any since I've read before that if you delete them, it will make it a pain to upgrade to newer Android versions.
So I've learned the hard way trying to update my phone from 4.4.2 to 5.0.1 LG rom.
- I took the OTA and tried to install it. Big mistake. I ended up in a TWRP bootloop. Had me cringing thinking I just lost everything until I found this post http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508 and fixed it with LG_G3_Flash2FixStuckRecovery.zip (flashed it with TWRP). What a godsend it was. Got me out of bootloop and I didn't have to do factory reset or anything. All my apps and data are intact just the way it was before I began OTA.
- So now I'm back to where I started originally before attempting to OTA to Lollipop.
If I'm reading correctly, what I need to do are:
- Unfreeze all apps
- Restore stock recovery (recovery.img) and boot file (boot.img) - this essentially reverses root and custom recovery. Use Flashify to do so.
- Flash the stock LG Lollipop update (btw - the phone says that the new ROM is already downloaded and ready to go but there's nothing in the cache folder... is there somewhere else I should be looking?)
- Before I reboot - I should flash SuperSU and TWRP which restores root and custom recovery
- Reboot phone, cross fingers.
Somewhere in the middle, am I reading that you need to restore LG stock Kitkat rom first (which I already am on), then update to Lollipop? I'm reading that from this part "This will allow you to go straight to "r" skipping "m" all together. If you are feeling brave and competent you could go straight to Lollipop..."
I'm confused here...
One last thing - Once I'm upgradded to Lollipop, is there an easy way to freeze all the apps I had frozen before instead of going one by one? I have the paid Titanium version but I can't figure out if it has a batch/mass freeze feature.
Thanks!!
No, sorry but you are way off base. I think you either did not read my post carefully or you totally misunderstood what I was trying to say.
You don't have to do the steps I did, they are not necessary with the files available at the linked post below.
Yes you can go straight to lollipop but for someone like yourself I would reccomend downloading and flashing KK build "r"
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and READ THE ENTIRE OP CAREFULLY then follow the TWRP Files/flashing guide for flashing KK build D85110R-Untouched_Stock_Restore.zip
*Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
This will at least update you to the last build "r" of Kit Kat
Lollipop for the D851 still has some bugs to be worked out but you can flash it if you want.
You are on your own now...
Good luck!
AndroidUzer said:
No, sorry but you are way off base. I think you either did not read my post carefully or you totally misunderstood what I was trying to say.
You don't have to do the steps I did, they are not necessary with the files available at the linked post below.
Yes you can go straight to lollipop but for someone like yourself I would reccomend downloading and flashing KK build "r"
If you are already rooted go Here > http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 and READ THE ENTIRE OP CAREFULLY then follow the TWRP Files/flashing guide for flashing KK build D85110R-Untouched_Stock_Restore.zip
*Be sure to also flash SuperSu and TWRP after flashing the restore zip and before rebooting or you will lose root and your custom recovery.
This will at least update you to the last build "r" of Kit Kat
Lollipop for the D851 still has some bugs to be worked out but you can flash it if you want.
You are on your own now...
Good luck!
Click to expand...
Click to collapse
I appreciate all of your advice. The thing is, I'm trying to upgrade to Lollipop... I'm already on Kitkat and not really interested in upgrading to a latter dot version of Kitkat.... It just seems like a difficult proposition to do OTA upgrade if you rooted and have non-stock recovery. Since I'm on tmobile d851 stock Kitkat (rooted with frozen apps), I should've never put put TWRP. I thought I might put custom ROM on it but never got around to it and since you pretty much lose wifi calling with non-Tmobile ROMs, I just never did... More of a pain now....
Hi XDA friends
I have a Nexus 5x on build MDB08I. It's rooted and encrypted with the encryption-compatible TWRP.
I really want to update to 6.0.1 but I don't want to have any data loss (i made a Nandroid backup recently but it's just a pain in the ass to set up a phone from scratch). Is this safe slash possible currently? I don't care about losing root, I just want to get the update, and keep all data and TWRP intact.
If so, can anyone help me out with what files I need and where to get them? I've got android SDK, familiar with fastboot, etc. but I just don't know what to flash and not flash. I do know that I can't just flash the OTA zips, tried that a few times
From what I've found looking around, it seems possible if I extract the files from the factory image of MMB29K and do the following:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
wipe cache/dalvic in TWRP
reboot
flash SuperSu in recovery
Click to expand...
Click to collapse
And... that's it? Do I have to flash radio, bootloader, recovery, etc? Will TWRP work with MMB29K? If it fails, I can revert to my nandroid backup. BUT I want to confirm that the above plan does not risk a brick.
Thanks!!
Read this thread http://forum.xda-developers.com/showpost.php?p=64253043&postcount=289
That specific post has the list of steps you should do to upgrade and regain root without losing your data. You can find the modified MMB29K boot.img file in another post on this forum.
solara1973 said:
Read this thread http://forum.xda-developers.com/showpost.php?p=64253043&postcount=289
That specific post has the list of steps you should do to upgrade and regain root without losing your data. You can find the modified MMB29K boot.img file in another post on this forum.
Click to expand...
Click to collapse
I followed that list but my phone has been booting for 20+ minutes. I'll restore from nandroid, but any idea what I did wrong? Should i fastboot flash iteratively from I to L to M and then to K instead of directly from I to K? do i have to boot into the OS after each build flash?
thanks!
edit: hah, wow. didn't even have to nandroid, just re-flashed all the I img's and all is back to normal. next i'll try the L, M, K sequence and report back unless you have any other ideas what i did wrong
You do not need to flash each version if you are flashing the images from the full firmware you download from Google. When you say it takes 20 mins where is it hanging at? It took a while for my 54 apps to get updated after flashing and clearing cache before booting into the system. You should not boot into system until you've flashed everything. You do reboot to bootloader after you flash the new bootloader.
Make sure you flash MODIFIED boot image for MMB29K if you were rooted with /system SU on L, otherwise you'll get boot loop. Also flash new radio too if you want Tmo band 12.
mickey4mice said:
Make sure you flash MODIFIED boot image for MMB29K if you were rooted with /system SU on L, otherwise you'll get boot loop. Also flash new radio too if you want Tmo band 12.
Click to expand...
Click to collapse
oops, that's it -- i had flashed the boot.img from the google image. found another XDA thread w/ modified MMB29K boot.img so trying that
@Solara i left it at the new boot animation for like an hour, the one with the 4 cute circles acting all busy.
also what does flashing cache and then wiping it do? why flash if if your'e gonna wipe it right after? new file format?
thanks so much guys!
edit: all set! did the same thing with the modified boot.img this time. also discovered i had to re-flash TWRP. still wondering what the deal with the cache/dalvik is but i flashed and wiped and everything seems great.
I didn't mean flash the cache image then clear it. I mean flash all the specified images then clear the cache. Just look at that original link I posted. Pretty clear and easy steps.
solara1973 said:
I didn't mean flash the cache image then clear it. I mean flash all the specified images then clear the cache. Just look at that original link I posted. Pretty clear and easy steps.
Click to expand...
Click to collapse
deffo, very simple and it's awesome that this **** is even possible due to all the work devs and volunteers do i've seen elsewhere people saying they flashed cache.img and then wiped it so it sounds like they were flashing it unnecessarily
Hi,
I am currently in OOS 4.0.1 rooted with superSU 2.79 and official TWRP 3.0.3. I got ota update OOS 4.0.2 few days back which I downloaded and clicked install. After reboot, it showed couldn't install update and I was back to OOS 4.0.1 without any side effects.
However, today I again got ota notification for 4.0.2 but this time its full 1.4 GB size. I haven't downloaded it yet. I just wanted to ask the community why is this happening. I don't mind ota update but my impression is I can't install ota while I am rooted.
Has anyone experienced this before? If I try installing, will it have any severe side effect in case of failures?
Nilay
Your phone recognised that the smaller OTA file failed because your system had been modified. So it tries to flash the full OTA file in order to prevent any conflicts with the modifications you made by completely removing them all. It's a safety mechanism. If you flash the full OTA, you should be fine, but you'll lose root.
cohaolain said:
Your phone recognised that the smaller OTA file failed because your system had been modified. So it tries to flash the full OTA file in order to prevent any conflicts with the modifications you made by completely removing them all. It's a safety mechanism. If you flash the full OTA, you should be fine, but you'll lose root.
Click to expand...
Click to collapse
Will it also replace TWRP with stock recovery? What about my apps, data, settings etc.? I don't want to reconfigure everything right now and worry about backups. I can wait for bigger update (maybe with 7.1.x) to re flash full zip.
Also, is this update going to be like dirty flash?
Thanks
Sent from my OnePlus 3 using XDA Labs
mit2nil said:
Will it also replace TWRP with stock recovery? What about my apps, data, settings etc.? I don't want to reconfigure everything right now and worry about backups. I can wait for bigger update (maybe with 7.1.x) to re flash full zip.
Also, is this update going to be like dirty flash?
Thanks
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
Its easier if you just download the full rom from oneplus's website and dirty flash it over your current setup and flash supersu immediately without rebooting to maintain root. You wont loose any data or custom settings on your device although its still advisable to make a backup of your data.
mit2nil said:
Will it also replace TWRP with stock recovery? What about my apps, data, settings etc.? I don't want to reconfigure everything right now and worry about backups. I can wait for bigger update (maybe with 7.1.x) to re flash full zip.
Also, is this update going to be like dirty flash?
Thanks
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
If you want to do an OTA upgrade, you have to flash stock recovery first, TWRP won't work.
After download before perform installation, you can find the downloaded full 1.4GB zip in your internal storage under ".OnePlusH2Ota" or "Android/data/com.oneplus.ota/files/.OnePlusOta", copy it out and flash it through TWRP. You won't lose your apps and settings unless you wipe /data or do a factory reset, you do needed to re-flash supersu though.
Hello.
I tried to update my OP3 to 4.0.3 but after downloading the update phone restarted and went into TWRP recovery mode and i couldn't go pass i that point. Went home and I tried to flush stock recovery with Tool All In One but now I cant get into stock or TWRP recovery. I contacted OP technical support but next remote session available is for next Friday!!! I'm downloading their files at the moment i assume stock ROM (file in 1GB size) and drivers and certifications .
Please somebody help me!!!
u can't flash an OTA with Trwp, just download the full zip and dirty flash, wipe cache and dalvik, not data, some say u can do system but I don't, don't try to update via OTA if u have twrp and don't try to re lock bootloader u will mess up and brick. Since u have twrp I would recommend flashing Experience ROM of FreedomOS, they are easier to work with, Experience rom seems to be faster with updates, feel free PM me if u need any help
ALWAYS DO A NANDROID BACK UP 1ST BEFORE FLASHING!!!!!!
Bradl79 said:
u can't flash an OTA with Trwp, just download the full zip and dirty flash, wipe cache and dalvik, not data, some say u can do system but I don't, don't try to update via OTA if u have twrp and don't try to re lock bootloader u will mess up and brick. Since u have twrp I would recommend flashing Experience ROM of FreedomOS, they are easier to work with, Experience rom seems to be faster with updates, feel free PM me if u need any help
ALWAYS DO A NANDROID BACK UP 1ST BEFORE FLASHING!!!!!!
Click to expand...
Click to collapse
Thx for reply, I managed to flash TWRP and the system is up and running. So to get system updates I have go back to Stock Recovery is that correct? I have made system back up just in case, but lets say anything go wrong again and I wont be able to restore the system with TWRP what then? Do you have a link to full rom? I found only for 3T.
wesoly75 said:
Thx for reply, I managed to flash TWRP and the system is up and running. So to get system updates I have go back to Stock Recovery is that correct? I have made system back up just in case, but lets say anything go wrong again and I wont be able to restore the system with TWRP what then? Do you have a link to full rom? I found only for 3T.
Click to expand...
Click to collapse
with a nandroid backup through twrp u back up data, system, cache and boot, so if anything goes wrong u can just restore back to where u left off, i don't use stock OTA to update, but i believe u have to unroot and flash stock recovery then u can update.
https://forum.xda-developers.com/oneplus-3/how-to/4-0-2-coming-tonight-t3539895