Related
I rooted this tablet last week (just rooted, I left it stock) and this morning I notice there is a system update waiting to be installed. I am reading Lollipop is starting to roll out in Asia somewhere now but I am in the US lol. I thought it wasn't possible to get OTA updates once you root? If I allow this to update will I get unrooted, would it even work?
I foolishly allowed it to update after checking in Supersu to not allow the root to be lost and now I keep booting directly into TWRP lol. How do I wipe this tablet from TWRP so that it is fully stock again (NO ROOT)? I see a factory reset option in TWRP do I need to include all the partitions in the advanced wipe or is just the normal wipe method enough? Or will this not work at all? I already tried to restore the phone using TWRP to my backup and that didn't seem to work.
Anthony-m said:
I rooted this tablet last week (just rooted, I left it stock) and this morning I notice there is a system update waiting to be installed. I am reading Lollipop is starting to roll out in Asia somewhere now but I am in the US lol. I thought it wasn't possible to get OTA updates once you root? If I allow this to update will I get unrooted, would it even work? .
Click to expand...
Click to collapse
Simply rooting a device doesn't keep it from TRYing to update via OTA. Rooting can prevent an OTA from succeeding, plus can hard or soft brick if you try to take an OTA, although usually only if you've gone beyond just rooting by installing a custom recovery or changing the contents of any partition besides Data by, fire example, downgrading your bootloader (aboot.img) or modem, running a custom kernel, debloating system apps, etc.
There are at least three variants of the G Pad 8.3. I have the VK810.4G, which do you have?
I know on the VK810.4G, Verizon just released a very, very minor update from LG build #23A to 24A. Still KitKat.
I foolishly allowed it to update after checking in Supersu to not allow the root to be lost and now I keep booting directly into TWRP lol.
Click to expand...
Click to collapse
There's the main problem, you had a custom recovery installed. OTAs are applied with the stock recovery, that's why it (probably soft) bricked it.
How do I wipe this tablet from TWRP so that it is fully stock again (NO ROOT)? I see a factory reset option in TWRP do I need to include all the partitions in the advanced wipe or is just the normal wipe method enough? Or will this not work at all? I already tried to restore the phone using TWRP to my backup and that didn't seem to work.
Click to expand...
Click to collapse
You might not be able to fix it from TWRP. You could try @autoprime 's fix recovery zip available the same page his flash2 scripts are. You'll have to Google:
autoprime flash2
Click to expand...
Click to collapse
.
Otherwise, you'll have to restore to 100% stock unrooted and start from scratch. Two methods.
One is using LG's official Mobile Tool, which will download the latest official ROM in KDZ format (takes 20+ minutes to download) and flash it with your tablet in Download mode (probably with the tablet off, hold both up and down volume buttons in and while holding them, turn the tablet on.
I've got to go do something so hopefully someone else will help further or I can get back to you later, dont know when though.
Good luck!
Sent from my VK810 4G
I did the TWRP terminal commands from the thread listed below and it got me right out of that jam...
http://forum.xda-developers.com/lg-g-pad-83/help/vk810-download-mode-boot-loop-t2991512
OK now that I am up and running fine the system update message keeps popping up. This time I KNOW not to try and upgrade while rooted. Is there any way I can stop the tablet from constantly giving me the upgrade message? Can I do anything from TWRP to stop this?
Anthony-m said:
... This time I KNOW not to try and upgrade while rooted. Is there any way I can stop the tablet from constantly giving me the upgrade message? Can I do anything from TWRP to stop this?
Click to expand...
Click to collapse
Don't install TWRP. I was rooted (w/ stock recovery) with 23A, and the OTA update worked fine (still rooted).
DeanGibson said:
Don't install TWRP. I was rooted (w/ stock recovery) with 23A, and the OTA update worked fine (still rooted).
Click to expand...
Click to collapse
TWRP is already installed..
Can I uninstall TWRP, keep root , do the update and then reinstall TWRP? If so how? Is there any other way around this issue, any way of not having the tablet continue to ask me to upgrade? Thanks BTW...
Anthony-m said:
TWRP is already installed..
Can I uninstall TWRP, keep root , do the update and then reinstall TWRP? If so how? Is there any other way around this issue, any way of not having the tablet continue to ask me to upgrade? Thanks BTW...
Click to expand...
Click to collapse
Yes, you can do that, but I don't know the steps. Others here do.
Why do you want TWRP? I thought the usual reason was to install custom ROMs (in which case you won't receive any OTA updates). If you just want to root, it's an unnecessary complication (as you have discovered).
DeanGibson said:
Yes, you can do that, but I don't know the steps. Others here do.
Why do you want TWRP? I thought the usual reason was to install custom ROMs (in which case you won't receive any OTA updates). If you just want to root, it's an unnecessary complication (as you have discovered).
Click to expand...
Click to collapse
Thanks Dean, and yes I do agree with you about it being a complication. I was always under the assumption if I rooted a phone that I needed to also use some sort of recovery god forbid I had an issue with the phone not booting up or something so I could possibly fix the issue, make a backup/install a backup etc. Maybe I will ****can it if someone will tell me how to do so without losing my data or root.
Anthony-m said:
Thanks Dean, and yes I do agree with you about it being a complication. I was always under the assumption if I rooted a phone that I needed to also use some sort of recovery god forbid I had an issue with the phone not booting up or something so I could possibly fix the issue, make a backup/install a backup etc. Maybe I will ****can it if someone will tell me how to do so without losing my data or root.
Click to expand...
Click to collapse
FYI I just froze the update using Titanium backup pro and my problem is solved for now..
Hi all, please correct me if I placed this at the wrong thread.
I recently was flasing my phone with stock roms due to some technical difficulties I had. I realize the system will create an Android folder in my ext SD card. Is this normal? Do I need to be worry about it?
By the way, I am currently using 3.32.707.9 as my ROM, when I check my OS version in bootloader, there isn't anything there. Why is that so?
Can I flash back a lower version of ROM? For instance, 1.54.707.7
Thanks for helping in advance!
My responses below, in red font:
jkidz91 said:
I recently was flasing my phone with stock roms due to some technical difficulties I had. I realize the system will create an Android folder in my ext SD card. Is this normal? Do I need to be worry about it? Totally normal, no need to worry.
By the way, I am currently using 3.32.707.9 as my ROM, when I check my OS version in bootloader, there isn't anything there. Why is that so? This is usually due to using an older version of TWRP (known bug). This number is useful for determining your current firmware version (hboot, radio, etc.) but you can also determine that by looking at the hboot number and radio numbers themselves
Can I flash back a lower version of ROM? For instance, 1.54.707.7 Yes. Usually, you want the ROM version (1.x, 2.x etc.) to correspond to your current firmware. But its usually been found that a higher number firmware will usually work with older (smaller number) ROMs
Click to expand...
Click to collapse
redpoint73 said:
My responses below, in red font:
Click to expand...
Click to collapse
Which version of TWRP should I be using for now?
How do I verify which firmware am I using?
jkidz91 said:
Which version of TWRP should I be using for now?
How do I verify which firmware am I using?
Click to expand...
Click to collapse
What are your current hboot and radio baseband numbers?
Do you know what Android version you were on (4.4.2, 4.4.3, etc.) before you unlocked the bootloader and started flashing ROMs?
redpoint73 said:
What are your current hboot and radio baseband numbers?
Do you know what Android version you were on (4.4.2, 4.4.3, etc.) before you unlocked the bootloader and started flashing ROMs?
Click to expand...
Click to collapse
Current hboot is 3.19.0.0000
Radio baseband: 1.25.21331147A1.06G_20.69.4196.01_F
Previously should be on 4.4.2...I guess...ROM version 1.54.707.7
jkidz91 said:
Current hboot is 3.19.0.0000
Radio baseband: 1.25.21331147A1.06G_20.69.4196.01_F
Previously should be on 4.4.2...I guess...ROM version 1.54.707.7
Click to expand...
Click to collapse
Your hboot and radio numbers indicate your phone was either purchased with Lollipop firmware, or updated to LP firmware at some point.
You should use the latest version TWRP 2.8.7.
redpoint73 said:
Your hboot and radio numbers indicate your phone was either purchased with Lollipop firmware, or updated to LP firmware at some point.
You should use the latest version TWRP 2.8.7.
Click to expand...
Click to collapse
Yea, I upgraded to LP through phone update once.
Btw, I installed the latest version of TWRP as u said and was prompt by it by saying "TWRP has detected an unmodified system partition" and for permission to allow modifications...should I allow it?
jkidz91 said:
Yea, I upgraded to LP through phone update once.
Btw, I installed the latest version of TWRP as u said and was prompt by it by saying "TWRP has detected an unmodified system partition" and for permission to allow modifications...should I allow it?
Click to expand...
Click to collapse
I haven't seen this before, its a new feature for 2.8.7 (which you can have Googled just as easily as I just did):
we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery.
https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html
Its actually not at all clear anymore what you are trying to do. You've posted in 2 or 3 different threads, asking about flashing firmware, running the RUU, or now you've flashed TWRP and maybe flashing an old 1.54 based ROM? Can't tell what your plan or end goal is at this time; and I'm not sure you know either.
redpoint73 said:
I haven't seen this before, its a new feature for 2.8.7 (which you can have Googled just as easily as I just did):
we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery.
https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html
Its actually not at all clear anymore what you are trying to do. You've posted in 2 or 3 different threads, asking about flashing firmware, running the RUU, or now you've flashed TWRP and maybe flashing an old 1.54 based ROM? Can't tell what your plan or end goal is at this time; and I'm not sure you know either.
Click to expand...
Click to collapse
Basically my goal is to update my phone to LP..sorry for the confusion caused. I have managed to update the phone according to the link you gave as for the TWRP, I did some Google search as well...and decided not to allow the function...am I doing correct on this?
jkidz91 said:
Basically my goal is to update my phone to LP..sorry for the confusion caused. I have managed to update the phone according to the link you gave
Click to expand...
Click to collapse
Meaning you updated by RUU?
jkidz91 said:
as for the TWRP, I did some Google search as well...and decided not to allow the function...am I doing correct on this?
Click to expand...
Click to collapse
So you updated (apparently) to LP by RUU. Now what are you trying to do? Its still not clear.
Are you trying to root? If so, I'd allow the change, and then flash SuperSU 2.46 to root.
The text and link I provided is pretty clear about the mentioned TWRP function. The main reason to say "no" is to have a fully stock image, of which you can make a nandroid backup. Otherwise, you will probably want to pick "yes".
redpoint73 said:
Meaning you updated by RUU?
So you updated (apparently) to LP by RUU. Now what are you trying to do? Its still not clear.
Are you trying to root? If so, I'd allow the change, and then flash SuperSU 2.46 to root.
The text and link I provided is pretty clear about the mentioned TWRP function. The main reason to say "no" is to have a fully stock image, of which you can make a nandroid backup. Otherwise, you will probably want to pick "yes".
Click to expand...
Click to collapse
Correct me if I am wrong, if I would want to later on update my phone to higher OS, I should not allow TWRP to mount the system..correct?
Currently my situation is, I did not allow TWRP to do the mounting and I rooted the phone...and everything is working fine so far...does that mean I am safe?
jkidz91 said:
Correct me if I am wrong, if I would want to later on update my phone to higher OS, I should not allow TWRP to mount the system..correct?
Currently my situation is, I did not allow TWRP to do the mounting and I rooted the phone...and everything is working fine so far...does that mean I am safe?
Click to expand...
Click to collapse
If its working fine (for whatever purposed you need root), than you're good.
Although obviously, if you want to modify the system partition in the future, you will need write protection for that partition disabled.
You can always make a stock TWRP backup (which you should do, anyway) with the system unmounted, to return to for future OTA. Or return to stock using the RUU.
You also need the stock recovery to update by OTA. So your phone is not going to OTA update (update will fail) in its present configuration (with TWRP installed), regardless.
redpoint73 said:
If its working fine (for whatever purposed you need root), than you're good.
Although obviously, if you want to modify the system partition in the future, you will need write protection for that partition disabled.
You can always make a stock TWRP backup (which you should do, anyway) with the system unmounted, to return to for future OTA. Or return to stock using the RUU.
You also need the stock recovery to update by OTA. So your phone is not going to OTA update (update will fail) in its present configuration (with TWRP installed), regardless.
Click to expand...
Click to collapse
I need the Titanium backup to recover my apps and data ><
Hmmm..TWRP backup of the ROM...this is what you are talking about right?
Before that, does that mean that if the system has been tampered before, the OTA will not go in? This is what the link you gave just now talking about?
About the stock recovery, I am fully aware of this
I am really sorry if I keep causing trouble to you...I just want to double confirm...I have spent few days just to get my phone for working right...really exhausting to the mind ><
jkidz91 said:
Hmmm..TWRP backup of the ROM...this is what you are talking about right?
Before that, does that mean that if the system has been tampered before, the OTA will not go in? This is what the link you gave just now talking about?
Click to expand...
Click to collapse
Yes, the new feature seems to be aimed at ensuring the ROM is untampered, for making a full "stock" backup for OTA purposes.
jkidz91 said:
I am really sorry if I keep causing trouble to you...
Click to expand...
Click to collapse
No trouble at all. If I didn't enjoy helping, I wouldn't bother responding.
redpoint73 said:
Yes, the new feature seems to be aimed at ensuring the ROM is untampered, for making a full "stock" backup for OTA purposes.
No trouble at all. If I didn't enjoy helping, I wouldn't bother responding.
Click to expand...
Click to collapse
Got it! Whenever I do back up, do I need to back up the data? As I already got the Titanium to backup all my user apps.
What I am saying is the recovery let me choose what to back up...I chose only system, and boot i think...
redpoint73 said:
No trouble at all. If I didn't enjoy helping, I wouldn't bother responding.
Click to expand...
Click to collapse
Hi, after updating to Lollipop and using it for past few days, everything seems to be working fine...however, I have got a slight issue with Facebook app...whenever I am on my mobile data, I will have error loading the latest news feed. It is working fine on WiFi.
I have tested loading other apps with Mobile Data only...and they are working fine...I have researched online and some said I shall do a factory reset before and after a major update to OS...should I do this?
jkidz91 said:
Got it! Whenever I do back up, do I need to back up the data? As I already got the Titanium to backup all my user apps.
What I am saying is the recovery let me choose what to back up...I chose only system, and boot i think...
Click to expand...
Click to collapse
If the intent was to just backup a "stock ROM" than no need to backup user data.
If the intent is to make a recovery image, that you can just revert to and start using with no (or very little other actions) than backup data. But as you said, you can restore data (at least app data) with Titanium.
---------- Post added at 09:06 AM ---------- Previous post was at 09:04 AM ----------
jkidz91 said:
Hi, after updating to Lollipop and using it for past few days, everything seems to be working fine...however, I have got a slight issue with Facebook app...whenever I am on my mobile data, I will have error loading the latest news feed. It is working fine on WiFi.
I have tested loading other apps with Mobile Data only...and they are working fine...I have researched online and some said I shall do a factory reset before and after a major update to OS...should I do this?
Click to expand...
Click to collapse
If you updated by RUU then no need to factory reset. RUU already wiped all partitions, in a much more comprehensive way than factory reset.
Try clearing app cache for Facebook; or uninstalling Facebook app, and reinstalling, without restore data for that app with Titanium.
redpoint73 said:
If you updated by RUU then no need to factory reset. RUU already wiped all partitions, in a much more comprehensive way than factory reset.
Try clearing app cache for Facebook; or uninstalling Facebook app, and reinstalling, without restore data for that app with Titanium.
Click to expand...
Click to collapse
Tried doing so...not working...anyway, can I run the RUU again to wipe off the entire phone and set up as new?
jkidz91 said:
Tried doing so...not working...anyway, can I run the RUU again to wipe off the entire phone and set up as new?
Click to expand...
Click to collapse
You can run the RUU until the cows come home, if you want.
redpoint73 said:
You can run the RUU until the cows come home, if you want.
Click to expand...
Click to collapse
What does that mean? >< i tried to do it...it failed...should I just download a stock 4.19.707.2 rom and flash it?
So I've stayed at 2.19.40.20 because I wanted to wait to see if a better way to unlock the bootloader would be found, but I've given up and unlocked my bootloader (the unoffical way).
I want to get up to speed and update to the latest OTA.
Can I just flash the latest one or do I need to download every one til the newest update and sideload them individually?
If I have to do each one can I just load them one after the other, or do I need to reboot the phone and let it fully load to the OS for every update?
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
DiGecko said:
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
Click to expand...
Click to collapse
Azdinflash said:
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
Click to expand...
Click to collapse
Yes that should do it.
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
The_wolf88 said:
Yes that should do it.
Click to expand...
Click to collapse
Azdinflash said:
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
Click to expand...
Click to collapse
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
DiGecko said:
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
Click to expand...
Click to collapse
Does unrooting include removing Xposed?
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Wait, if I flash the 1.1 gig stock ROM, do I lose everything in the internal memory?
DiGecko said:
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Click to expand...
Click to collapse
I did a little digging, and it seems that the bootloop was fixed a few days ago:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476/page26
J M L said:
There's a new Xposed out, v78, which claims to fix a bootloop on 5.0 roms due to a security fix. I haven't tried it yet because I'm running a backup. Here is the thread and changelog.
We want the sdk21-x86 version.
Installed with no problem in TWRP with the flash able zip. Took a few minutes to boot, but seems to be working.
Click to expand...
Click to collapse
Good to know. No, you would not loose anything, at least I did not. Everything migrated over without any issues.
So I've gotten through sideloading the current version with no hiccups. Booted into system fine, it's the right version in the About section, and my internal memory came through intact.
I've flashed TWRP, and booted into it to install SuperSU when I got this message: "TWRP may have detected an unmodified system partition"
It explains that I can keep it as read only and make it easier to take official updates, but then TWRP will not be able to stop the stock ROM from replacing it and will not offer to root my device.
Should I keep it "Read Only" or should I allow the modification?
Hello.
I have a few questions about firmware (MIUI) updates on a root device with an unlocked bootloader and stock ROM.
I know that when the bootloader is unlocked and the device is rooted, OTAs updates don't work.
1. Where can I find that a new version of the miui firmware has been released ? Link please.
2. What should the update file look like? size, file type.
3. How is the new firmware updated? method please.
4. So if the above mentioned firmware update can be installed, I ask if everything in the device remains the same, applications, data, etc.?
That's all I wanted to ask, thank you very much.
Look for xiaomifirmwareupdate on google.
On that site you will find latest firmware files for alioth PocoF3/redmi k40.
You will have a small file ~300mb.You update using TWRP.Just flash the archive and wipe cache.
I don't have twrp.
I'm following a topic about twrp, it's still an alpha version and from what I've read, it's still fully inoperable and backups and restores not work.
I thought that the firmware update (zip) could flash normally from the system, from the phone environment, where the updates are managed.
"still an alpha version and from what I've read, it's still fully inoperable" agree with you
jkmaxfli said:
I don't have twrp.
I'm following a topic about twrp, it's still an alpha version and from what I've read, it's still fully inoperable and backups and restores not work.
I thought that the firmware update (zip) could flash normally from the system, from the phone environment, where the updates are managed.
Click to expand...
Click to collapse
It works for firmware update.You cannot update the firmware from within android.
You could use fastboot to flash the images of the firmware one by one .
jkmaxfli said:
I don't have twrp.
I'm following a topic about twrp, it's still an alpha version and from what I've read, it's still fully inoperable and backups and restores not work.
I thought that the firmware update (zip) could flash normally from the system, from the phone environment, where the updates are managed.
Click to expand...
Click to collapse
Idk what u read.. Backups and restore work perfectly, I just did one backup and restore 2 days ago.
LiNe1771 said:
Idk what u read.. Backups and restore work perfectly, I just did one backup and restore 2 days ago.
Click to expand...
Click to collapse
It is interesting that you can back up and restore.
There were two questions in the topic about whether backup and restore worked and no one was able to answer. It is an official topic and it should be heard there that it can be fully backed up and restored.
is the 168 hrs waiting time when unlocking the bootloader a luck-based thing or will it always ask you to wait 168 hours?
Guan Le said:
is the 168 hrs waiting time when unlocking the bootloader a luck-based thing or will it always ask you to wait 168 hours?
Click to expand...
Click to collapse
Mostly 168 hours.
Old-registered lucky users can have instant unlock, very rare though.
Some bad credit/ unknown reasons Mi-account users can have 360 hours.
168 hours was a minimal time for xiaomi to plants something
LiNe1771 said:
Idk what u read.. Backups and restore work perfectly, I just did one backup and restore 2 days ago.
Click to expand...
Click to collapse
I already have Twrp.
Before the backup, did you check what specifically to make the recovery fully functional?
jkmaxfli said:
I already have Twrp.
Before the backup, did you check what specifically to make the recovery fully functional?
Click to expand...
Click to collapse
You can simply download the OTA, install it manually within the official updater (click the three dot when you're in the update app and choose manual install, then select the OTA in your file manager). After update is installed, DO NOT REBOOT DIRECTLY. Go then on magisk, click on install and choose the OTA way. Don't remember the exact word because my Magisk is in french. By this way, Magisk will install himself on the other partition (a or b, depends of your current partition in the moment of the update) so after the OTA, you will keep Magisk. It's possible because Poco f3 has 2 partition, a and b. On some phone, you have only one partition so you can't do this way.
jkmaxfli said:
I already have Twrp.
Before the backup, did you check what specifically to make the recovery fully functional?
Click to expand...
Click to collapse
By the way, if you don't see the tree dot, tap multiple tile on the miui logo in updater. So you unlock additional update feature
But I asked what all needs to be checked in twrp recovery in order to back it up.
Of course, thank you for the above instructions.
jkmaxfli said:
But I asked what all needs to be checked in twrp recovery in order to back it up.
Of course, thank you for the above instructions.
Click to expand...
Click to collapse
I know, I just gave you a another way to update
DeathStroke47 said:
Go buy a oneplus device if you love oxygen os
Click to expand...
Click to collapse
a little off topic, right?
can we flash Oos through twrp? also can we flash Oos rom from custom rom? if so what are the instructions? thx in advance. yes i have a lot of questions lol
freddienuxx said:
can we flash Oos through twrp? also can we flash Oos rom from custom rom? if so what are the instructions? thx in advance. yes i have a lot of questions lol
Click to expand...
Click to collapse
I'm also curious about this. My current method is to just use the MSM tool whenever I want to go back to stock but it is definitely time consuming. As far as I know TWRP is still early in development and a lot of things that should normally work dont work perfectly
I have definitely flashed OOS through TWRP (from AA to BA, not a custom rom), but haven't had any issues since I did it. That being said I would assume the steps would be to flash, factory reset, then root etc.
Haunt3r said:
I have definitely flashed OOS through TWRP (from AA to BA, not a custom rom), but haven't had any issues since I did it. That being said I would assume the steps would be to flash, factory reset, then root etc.
Click to expand...
Click to collapse
hm that is great to hear, however, when I attempt to flash oos 11.2.7.7AA (from oos 11.2.4.4AA) I get an error saying that I am missing /system_ext, /product, and /odm partitions. did you do anything other than simply install oos via twrp, because I am not sure why I am getting this error
thirtythr33 said:
hm that is great to hear, however, when I attempt to flash oos 11.2.7.7AA (from oos 11.2.4.4AA) I get an error saying that I am missing /system_ext, /product, and /odm partitions. did you do anything other than simply install oos via twrp, because I am not sure why I am getting this error
Click to expand...
Click to collapse
To my knowledge you cannot flash from 2.4.4AA to 2.7.7AA because it is an incremental update, at least through twrp. (I've never flashed anything but full roms via twrp). I actually fully switched to the EU firmware from the Global firmware because of the global version seemingly going fully to OTA updates and not providing full ROMs like the EU version.
Haunt3r said:
To my knowledge you cannot flash from 2.4.4AA to 2.7.7AA because it is an incremental update, at least through twrp. (I've never flashed anything but full roms via twrp). I actually fully switched to the EU firmware from the Global firmware because of the global version seemingly going fully to OTA updates and not providing full ROMs like the EU version.
Click to expand...
Click to collapse
no you are right, but I have the full update via oxygen updater, so these errors of missing partitions are extremely frustrating.
thirtythr33 said:
no you are right, but I have the full update via oxygen updater, so these errors of missing partitions are extremely frustrating.
Click to expand...
Click to collapse
there is no "full" update for 7.7aa it's solely an OTA
Haunt3r said:
there is no "full" update for 7.7aa it's solely an OTA
Click to expand...
Click to collapse
yeah man there is, came out June 28th, check oxygen updater or oneplus software download.
lol either way I can't flash it so fml
Haunt3r said:
there is no "full" update for 7.7aa it's solely an OTA
Click to expand...
Click to collapse
Yes there is, it came out a few days ago about 3gb's on OnePlus website...
Ah ****. Had no idea. Might flash back to aa if they're releasing full updates. Only reason I switched to eu was that reason. Definitely weird you're running into issues with it though
Haunt3r said:
Ah ****. Had no idea. Might flash back to aa if they're releasing full updates. Only reason I switched to eu was that reason. Definitely weird you're running into issues with it though
Click to expand...
Click to collapse
yeah man we have to wait insane long for AA full updates. yeah my issue is very frustrating and I've tried everything short of msm, I just don't see how it is possible that twrp reports I am missing those partitions yet my phone boots, but slot B is f'd, and I can't flash full AA update either through twrp or local upgrade.
Okay so if we do flash the full ota through recovery what's the correct process on this to keep twrp and magisk without needing a PC to push the recovery and root back onto the device?