I'm not sure why i have Magisk installed in a way that it cannot find the stock boot image, but that seems to be the case.
a quick search didn't turn up the stock boot image for my existing ROM version (IN2025_11_f.15)
I figure it may be easier to just update and lose root, then re-root with the new boot image, but I've had some issues doing what I thought would be easy, but turned into big issues, so before I start down this path, I wanted to ask what may be the best way to go from where I am...
(rooted with Magisk, but no stock boot.img, running build number IN2025_11_F.15, Baseband version Q_V1_P14)
...to getting onto the latest version my phone is offering (IN2025_11.F.62_2620_202301162204) and get Magisk fixed so that it then has a stock boot image, so I can update later by just uninstalling/restoring images, installing the update, then rebooting to the inactive slot, which worked fine for years.
Thanks in advance for any help/guidance doing so.
Hmmm, I've never uninstalled/restored boot image when updating. I simply disable/uninstall those modules that might cause issues (like Substratum/themes), download the full rom zip file and place it in the root of my internal and make a backup of my apps with Migrate.
Then I do the local upgrade WITHOUT rebooting. Back in Magisk I hit install after the Magisk version -> hit again install -> hit "install to inactive slot.
THEN I reboot.
Afterwards I enable/reinstall my Magisk modules and that's it.
But I just found your stock boot image in our OP 8 group too and am attaching it, in case you want to do it your way lol
XDA didn't like file upload so I put it on GDrive for you. Let me know when you've grabbed it so I can delete it
Nimueh said:
Hmmm, I've never uninstalled/restored boot image when updating. I simply disable/uninstall those modules that might cause issues (like Substratum/themes), download the full rom zip file and place it in the root of my internal and make a backup of my apps with Migrate.
Then I do the local upgrade WITHOUT rebooting. Back in Magisk I hit install after the Magisk version -> hit again install -> hit "install to inactive slot.
THEN I reboot.
Afterwards I enable/reinstall my Magisk modules and that's it.
But I just found your stock boot image in our OP 8 group too and am attaching it, in case you want to do it your way lol
XDA didn't like the .img ending so I had to rename it to .zip - just remove that and you'll be good.
Click to expand...
Click to collapse
I've never done it that way myself. By just restoring images in magisk, I can do a "normal" update, from settings, and it will download just the update, in this case, about 700MB, then Install to inactive slot in Magisk and done.
This avoids me needing to find the full update to download. Probably not a big deal, but this has always worked fine in the past.
I guess i just installed Magisk incorrectly the last time I wiped, which is now causing me this issue.
I appreciate your suggestion, and perhaps that is the better way moving forward.
I didn't see your attachment, but as I'm typing this, i see you edited to say you renamed it, so I'll see if I see it now.
Thank you for your help.
Nimueh said:
Hmmm, I've never uninstalled/restored boot image when updating. I simply disable/uninstall those modules that might cause issues (like Substratum/themes), download the full rom zip file and place it in the root of my internal and make a backup of my apps with Migrate.
Then I do the local upgrade WITHOUT rebooting. Back in Magisk I hit install after the Magisk version -> hit again install -> hit "install to inactive slot.
THEN I reboot.
Afterwards I enable/reinstall my Magisk modules and that's it.
But I just found your stock boot image in our OP 8 group too and am attaching it, in case you want to do it your way lol
XDA didn't like file upload so I put it on GDrive for you. Let me know when you've grabbed it so I can delete it
Click to expand...
Click to collapse
I just downloaded it, thank you again!
Note: I've never upgraded this device.
Uninstalling Magisk from the app restores the stock boot: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87931933
Primokorn said:
Note: I've never upgraded this device.
Uninstalling Magisk from the app restores the stock boot: https://forum.xda-developers.com/t/...epo-of-oxygen-os-builds.4084315/post-87931933
Click to expand...
Click to collapse
Thank you, but that is the issue. I don't seem to have the stock image on the device, so I can't "uninstall Magisk" to restore the stock image.
Once I make the time to deal with this, I believe the stock image Nimueh shared will let me fix this, but I don't have time to troubleshoot this if it doesn't go smoothly, so it needs to wait a bit longer.
JustinChase said:
Thank you, but that is the issue. I don't seem to have the stock image on the device, so I can't "uninstall Magisk" to restore the stock image.
Once I make the time to deal with this, I believe the stock image Nimueh shared will let me fix this, but I don't have time to troubleshoot this if it doesn't go smoothly, so it needs to wait a bit longer.
Click to expand...
Click to collapse
OK I thought Magisk handled the backup of the stock boot.
I'm not in hurry to upgrade lol
Primokorn said:
OK I thought Magisk handled the backup of the stock boot.
I'm not in hurry to upgrade lol
Click to expand...
Click to collapse
It normally does, but I apparently installed it 'abnormally' last time, so I didn't have/save the stock boot image.
I just need to research the best way to get the downloaded stock image onto my phone so that Magisk knows and can use it, without screwing something up, and having to wipe and reinstall everything (again).
I'm not in a huge hurry to upgrade either, but I do like to be on the latest security patches; especially considering the news with the Exynos chips' vulnerability to WiFi calling issues.
JustinChase said:
I'm not in a huge hurry to upgrade either, but I do like to be on the latest security patches; especially considering the news with the Exynos chips' vulnerability to WiFi calling issues.
Click to expand...
Click to collapse
Luckily that doesn't apply to our devices though - according to the articles I've seen it only affects these devices:
Samsung Galaxy S22, M33, M13, M12, A71, A53, A33, A21s, A13, A12 and A04 series.
Vivo S16, S15, S6, X70, X60 and X30 series.
The Pixel 6 and Pixel 7 series.
Any vehicles that use the Exynos Auto T5123 chipset.
Nimueh said:
Luckily that doesn't apply to our devices though - according to the articles I've seen it only affects these devices:
Samsung Galaxy S22, M33, M13, M12, A71, A53, A33, A21s, A13, A12 and A04 series.
Vivo S16, S15, S6, X70, X60 and X30 series.
The Pixel 6 and Pixel 7 series.
Any vehicles that use the Exynos Auto T5123 chipset.
Click to expand...
Click to collapse
I agree. I'm more concerned about the unpublished vulnerabilities that may exist, that we just don't know about yet.
I figure that if I keep my device updated with security patches, that's better than finding out the hard way I could have prevented an issue.
JustinChase said:
I agree. I'm more concerned about the unpublished vulnerabilities that may exist, that we just don't know about yet.
I figure that if I keep my device updated with security patches, that's better than finding out the hard way I could have prevented an issue.
Click to expand...
Click to collapse
I don't use my device much and mostly at home on my wifi, so I'm not overly worried. I'm still on the last OOS 11 version mysel, mostly because 1 mod I use only exists for OOS 11. I'm sure I'll update eventually but for now I'm ok with old security patches.
#priorities and all that
Related
I have not been able to update my shield tv 2015 16gb device to 5.2.
The device is rooted with latest 3.1.1 TWRP recovery. Each time I select upgrade with the stock settings it will reboot into recovery and won't update.
Does anyone have a link to the latest ROM or know where Nvidia stores the OTA file? I would rather flash the image my self if I can find get the ROM.
I'm sure this we'll help a few other people I can't be the only one with this issue. Need the 5.2 image not the 5.0.2 which is the previous version of Shield experience update.
you should not flash TWRP to your device reflash original recovery and remove su then try update again
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
It's a real PItA for just some extra (Non-working) Plex Channels, and making the needed edits to settings.db to prevent it from kicking iPlayer off after each Power Cycle / IP Address reset. (Though that last one... Has more legs on it then just the Plex Channels.)
Ichijoe said:
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
.)
Click to expand...
Click to collapse
i didnt know that :good:
but if he has TWRP installed couldnt he format data pation from TWRP thus saving hours of thumb twiddling
Ichijoe said:
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
It's a real PItA for just some extra (Non-working) Plex Channels, and making the needed edits to settings.db to prevent it from kicking iPlayer off after each Power Cycle / IP Address reset. (Though that last one... Has more legs on it then just the Plex Channels.)
Click to expand...
Click to collapse
Obviously thats a much longer and worse route.
afgok said:
you should not flash TWRP to your device reflash original recovery and remove su then try update again
Click to expand...
Click to collapse
I have upgraded the shield tv many times with OTA updates. Shouldn't need to be stock just to do this. So your saying root has more restrictions....
TWRP is much better than stock recovery, now it might not be finding the OTA update when it gets pushed to recovery.
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
On another thread looks like others are having this same issue with only this version 5.2.. ill just wait for the Dev Images to show up hopefully soon.
I unrooted but still got the same issue, it wont install. But I also have another issue, i can't restore my 2015 shield 16gb by using official recovery rom and official tutorials. It consistently fails to flash system.img and vendor.img by saying that the data is too large. The only way I got my system back was by flashing this file https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-ota-5-1-feb-17-zip-file-t3559062 through twrp
Diehardshorty said:
Obviously thats a much longer and worse route.
I have upgraded the shield tv many times with OTA updates. Shouldn't need to be stock just to do this. So your saying root has more restrictions....
TWRP is much better than stock recovery, now it might not be finding the OTA update when it gets pushed to recovery.
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
Click to expand...
Click to collapse
Again TWRP can not be used to flash an OTA Update. I mean sure feel free to knock yourself out. But, in the end it will fail. (Error 7 IIRC), As it is it seems that it will only work on a stock Recovery, and not on TWRP. I mean if it were this easy, everyone would be doing it. And again if the Update were working over TWRP, we wouldn't have a constant update loop. (e.g. Download Update, restart Shield, wait forever for the Shield to try (and, fail!) at applying said Update, rebooting, and wash rinse, repeat).
BTW: I never said that my way* was the 'best' way, or indeed the 'only' way. Its just the only way I know of to Nuke it from orbit all the time, everytime. And, yes it is a huge PITA. If you count a /system root as being more restrictive. In the case of Netflix making active noises about blocking rooted Devices. Then yes slowly I would say that rooting has more restrictions than stock.
*My way being to Factory wipe the Shield (Pro) which in the case of the Pro most likely means a Two plus Hours of dead time. I would assume it's much MUCH quicker for our 16GB eMMC Cousins though. But, not having One, I'm unable to confirm it.
P.s. You have also mentioned the fact that you have managed to update your rooted Shield TV on multiple occasions. Would you care to share this info with us? I for One would love to know how to do this. As having to Factory Reset the Device is a real time waster. Because after the reset, comes the rebuild. And, thats an even bigger *****.
Ichijoe said:
Again TWRP can not be used to flash an OTA Update. I mean sure feel free to knock yourself out. But, in the end it will fail. (Error 7 IIRC), As it is it seems that it will only work on a stock Recovery, and not on TWRP. I mean if it were this easy, everyone would be doing it. And again if the Update were working over TWRP, we wouldn't have a constant update loop. (e.g. Download Update, restart Shield, wait forever for the Shield to try (and, fail!) at applying said Update, rebooting, and wash rinse, repeat).
BTW: I never said that my way* was the 'best' way, or indeed the 'only' way. Its just the only way I know of to Nuke it from orbit all the time, everytime. And, yes it is a huge PITA. If you count a /system root as being more restrictive. In the case of Netflix making active noises about blocking rooted Devices. Then yes slowly I would say that rooting has more restrictions than stock.
*My way being to Factory wipe the Shield (Pro) which in the case of the Pro most likely means a Two plus Hours of dead time. I would assume it's much MUCH quicker for our 16GB eMMC Cousins though. But, not having One, I'm unable to confirm it.
P.s. You have also mentioned the fact that you have managed to update your rooted Shield TV on multiple occasions. Would you care to share this info with us? I for One would love to know how to do this. As having to Factory Reset the Device is a real time waster. Because after the reset, comes the rebuild. And, thats an even bigger *****.
Click to expand...
Click to collapse
Dirty flashing a dev image is they way I have managed to update my shield but right now the dev images are not updated, still the 5.1.0
If you're rooted, the right answer is to wait for Nvidia to release the 5.2 image.
If you absolutely need 5.2 right now for some reason, several people said that doing a factory restore worked. Just unrooting and restoring stock recovery won't do it, you need to do a full restore.
Diehardshorty said:
Dirty flashing a dev image is they way I have managed to update my shield but right now the dev images are not updated, still the 5.1.0
Click to expand...
Click to collapse
The Dev images are quite a bit different, and are also on an entirely different timeline to either the Preview, (Which I'm on), or the most current version.
But, yeah I could see how those would work. Alas mores the pitty that the rooted asspects of those Dev Images, only go as far as ADB, and not say a full /system wide root. Than again... It's probably for the best that way.
But, that doesn't really change the answer if you want / need to update (From root), than you are going to have to bite the big One, and run a Factory Reset. Which again, on the Pro, means a 2h+ reformating (zeroing out), of the /data Partition.
16gb version doesn't take as long to format but I've always remember flashing SuperSU.zip after ROM just incase. Short response for now at work.
Diehardshorty said:
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
Click to expand...
Click to collapse
Use to be here:
/data/data/com.nvidia.ota/app_download
You obviously need root to reach that folder...
If i have time i will upload later this small OTA update to MEGA.
I uploaded the 5.2 small update OTA for Shield TV 2015 (NON-PRO):
https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-small-update-ota-5-2-t3621886
sammarbella said:
I uploaded the 5.2 small update OTA for Shield TV 2015 (NON-PRO):
https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-small-update-ota-5-2-t3621886
Click to expand...
Click to collapse
Sweet thanks I'll give that a try from the sounds of it it might not work but I'll give a shot after work. Thanks
No luck flashing my own OTA zip I took it out of data\data\com.nvidia.ota flashed it with TWRT 3.1.1.
I might end up doing the factory restore then updating and root. Wouldn't mind a new clean OS
Diehardshorty said:
No luck flashing my own OTA zip I took it out of data\data\com.nvidia.ota flashed it with TWRT 3.1.1.
I might end up doing the factory restore then updating and root. Wouldn't mind a new clean OS
Click to expand...
Click to collapse
Check out https://forum.xda-developers.com/shield-tv/general/how-to-update-ota-5-2-2017-update-t3622540 just posted a guide on how to update
Cameron581 said:
Check out https://forum.xda-developers.com/shield-tv/general/how-to-update-ota-5-2-2017-update-t3622540 just posted a guide on how to update
Click to expand...
Click to collapse
Only difference there is that your using flashfire instead of TWRP. I can't see how that may work but worth a shot.
Diehardshorty said:
Only difference there is that your using flashfire instead of TWRP. I can't see how that may work but worth a shot.
Click to expand...
Click to collapse
Just make sure you flash the right update, and it's because the ota provided by the devs don't support ota due to device fingerprint issues along with partition finding stuff found inside the meta-inf, the reason you can't sideload the room via stock is because there is a check for modified system tables. Granted you could take out that comment and rezip it then it will fail for zip verification, after that I had tried to sign the package to regain that but then it failed due to it only signed the packages not the entire system. Long story short it's super duper picky and ChainFire made one that pleases all of the variables or ignores then.
Cameron581 said:
Just make sure you flash the right update, and it's because the ota provided by the devs don't support ota due to device fingerprint issues along with partition finding stuff found inside the meta-inf, the reason you can't sideload the room via stock is because there is a check for modified system tables. Granted you could take out that comment and rezip it then it will fail for zip verification, after that I had tried to sign the package to regain that but then it failed due to it only signed the packages not the entire system. Long story short it's super duper picky and ChainFire made one that pleases all of the variables or ignores then.
Click to expand...
Click to collapse
Ahhhhh that missing point for "error 7".
So the new app bypass that problem!
Thanks for posting it. :good:
Okay so after getting tired of safetynet and other issues Google has put on us I'm wanting to switch to magiskSU but Everytime I tried I bootloop and have to clean flash my rom. This is what I'm doing
1. Flashed unSU in twrp
2.flashed stock boot.img
3. Flashed the magisk.zip
4.got an error saying it failed to install magisk.zip
But whenever I try to reboot to system (I've tried reinstalling SuperSU and without reinstalling as well) I got a bootloop Everytime can someone instruct me or tell me what I'm doing wrong?
WeUseLord- said:
Okay so after getting tired of safetynet and other issues Google has put on us I'm wanting to switch to magiskSU but Everytime I tried I bootloop and have to clean flash my rom. This is what I'm doing
1. Flashed unSU in twrp
2.flashed stock boot.img
3. Flashed the magisk.zip
4.got an error saying it failed to install magisk.zip
But whenever I try to reboot to system (I've tried reinstalling SuperSU and without reinstalling as well) I got a bootloop Everytime can someone instruct me or tell me what I'm doing wrong?
Click to expand...
Click to collapse
What carrier/rom/update/etc?
WeUseLord- said:
Okay so after getting tired of safetynet and other issues Google has put on us I'm wanting to switch to magiskSU but Everytime I tried I bootloop and have to clean flash my rom. This is what I'm doing
1. Flashed unSU in twrp
2.flashed stock boot.img
3. Flashed the magisk.zip
4.got an error saying it failed to install magisk.zip
But whenever I try to reboot to system (I've tried reinstalling SuperSU and without reinstalling as well) I got a bootloop Everytime can someone instruct me or tell me what I'm doing wrong?
Click to expand...
Click to collapse
In Short. Currently for our device to have magisk, you need to use the boot image that @joemossjr and @Uzephi developed with Magisk support. Then install the magisk app. No zip install.
Refer to Joe's thread for the boot image at this link
https://forum.xda-developers.com/z2-force/how-to/how-to-root-moto-z2-force-t-mobile-t3672933
I would have went into detail and used a short link, but my head is currently throbbing so this is easier lol.
Edit: then realized your replied a minute before I Uzephi haha.
Uzephi said:
What carrier/rom/update/etc?
Click to expand...
Click to collapse
Spring stock rom on the original August update
Sent from my Moto Z (2) Force using XDA Labs
Acoustichayes said:
In Short. Currently for our device to have magisk, you need to use the boot image that @joemossjr and @Uzephi developed with Magisk support. Then install the magisk app. No zip install.
Refer to Joe's thread for the boot image at this link
https://forum.xda-developers.com/z2-force/how-to/how-to-root-moto-z2-force-t-mobile-t3672933
I would have went into detail and used a short link, but my head is currently throbbing so this is easier lol.
Click to expand...
Click to collapse
I know but when I tried that method and just installing the boot.img through twrp it failed and gave me a boot loop as well
Sent from my Moto Z (2) Force using XDA Labs
WeUseLord- said:
Spring stock rom on the original August update
Click to expand...
Click to collapse
I would suggest updating to November. I have a rooted magisk image, but you need to flash the decryption zip to get it to boot. If you update to November, I am going to release a flash-all type zip sometime today (after I fiddle with getting 4.4.107 upstream done) and working on a Google Pixel 2 skinned ROM for us here shortly with oem bloat completely removed
WeUseLord- said:
I know but when I tried that method and just installing the boot.img through twrp it failed and gave me a boot loop as well
Sent from my Moto Z (2) Force using XDA Labs
Click to expand...
Click to collapse
Have to ask this general base question of course lol. are you trying to dirty flash or did you do a full clean install?
But in general, what Uzephi said, as this is his project. I'll let him go ahead and take over. Goodluck
WeUseLord- said:
I know but when I tried that method and just installing the boot.img through twrp it failed and gave me a boot loop as well
Click to expand...
Click to collapse
You using stock kernel? To get crypto changes in 4.4.101-103 added, it breaks encryption on our phones and will cause a boot loop due to Motorola's dirty code. Hopefully when Oreo ROM drops (since Google is kinda telling oems to stay upstreamed) it will fix those issues in our stock ROMs.
Uzephi said:
I would suggest updating to November. I have a rooted magisk image, but you need to flash the decryption zip to get it to boot. If you update to November, I am going to release a flash-all type zip sometime today (after I fiddle with getting 4.4.107 upstream done) and working on a Google Pixel 2 skinned ROM for us here shortly with oem bloat completely removed
Click to expand...
Click to collapse
That's nice I think I'm gonna stick with SuperSU for now this phone is confusing
But one thing I must ask will we have a customisable rom like CM or something like that soon?
Sent from my Moto Z (2) Force using XDA Labs
WeUseLord- said:
That's nice I think I'm gonna stick with SuperSU for now this phone is confusing
But one thing I must ask will we have a customisable rom like CM or something like that soon?
Click to expand...
Click to collapse
Hard to say. Those of us that have tried hard bricked the device. Not readable via USB and wouldn't boot anything after the flash.
WeUseLord- said:
That's nice I think I'm gonna stick with SuperSU for now this phone is confusing
But one thing I must ask will we have a customisable rom like CM or something like that soon?
Sent from my Moto Z (2) Force using XDA Labs
Click to expand...
Click to collapse
To build off what Uzephi said. It's not that rom's wont be capable. It's just working with new things that are being implemented and changed until something starts going right. The jump to Nougat changed a lot of things with security and the switch to Oreo is changing even more that Google is wanting to push for android that inadvertently also affect security and compatibility.
This is speculation, but since they introduced Kotlin, I feel like they are trying to alter everything over the long run to become more streamline and compatible around it. Especially given they can control the progress of the script language to help them better. Which will really show true or false come mid next year.
We are lucky that Motorola sticks to a super close to stock experience because it's one less issue to deal with when playing with the new code and functions to try to get things to work. I'm really optimistic on this stuff because I like doing things that people think can't be done. So I believe that there will for sure be more customization and capabilities as we figure things out. Just takes time and effort. We worked for months and months on the S8 where people said impossible, and ended up getting it. So i have faith on this.
Acoustichayes said:
To build off what Uzephi said. It's not that rom's wont be capable. It's just working with new things that are being implemented and changed until something starts going right. The jump to Nougat changed a lot of things with security and the switch to Oreo is changing even more that Google is wanting to push for android that inadvertently also affect security and compatibility.
This is speculation, but since they introduced Kotlin, I feel like they are trying to alter everything over the long run to become more streamline and compatible around it. Especially given they can control the progress of the script language to help them better. Which will really show true or false come mid next year.
We are lucky that Motorola sticks to a super close to stock experience because it's one less issue to deal with when playing with the new code and functions to try to get things to work. I'm really optimistic on this stuff because I like doing things that people think can't be done. So I believe that there will for sure be more customization and capabilities as we figure things out. Just takes time and effort. We worked for months and months on the S8 where people said impossible, and ended up getting it. So i have faith on this.
Click to expand...
Click to collapse
Motorola already admitted the Z series will not be a part of Project treble meaning we need to try different vendor files to see if builds work. Sadly the ones used for the Z1 and wahoo mixed together cause the phone to go haywire and brick itself.
Uzephi said:
Motorola already admitted the Z series will not be a part of Project treble meaning we need to try different vendor files to see if builds work. Sadly the ones used for the Z1 and wahoo mixed together cause the phone to go haywire and brick itself.
Click to expand...
Click to collapse
And I understand that this means lack of simplicity in developing custom rom's. But it doesn't mean incapability. From what I understand as well, that treble can be implemented at a later date even though it will not be included with the initial Oreo update. You are working on a pixel rom conversion if I am correct right? Because I might have an idea...
But treble is still def exciting to think about being able to have one rom work on many different phones without modification. I honestly haven't divulged too far into it, but what are the odds of tearing apart the code and possible making support for it ourselves? I'm all for ridiculously long spans of working towards absurd goals hah
Acoustichayes said:
And I understand that this means lack of simplicity in developing custom rom's. But it doesn't mean incapability. From what I understand as well, that treble can be implemented at a later date even though it will not be included with the initial Oreo update. You are working on a pixel rom conversion if I am correct right? Because I might have an idea...
But treble is still def exciting to think about being able to have one rom work on many different phones without modification. I honestly haven't divulged too far into it, but what are the odds of tearing apart the code and possible making support for it ourselves? I'm all for ridiculously long spans of working towards absurd goals hah
Click to expand...
Click to collapse
Unless Motorola can repartition the phone, Treble won't come out, it needs a vendor partition. I can say at least on my Sprint phone the OEM block is about 1.5 GB when there is only about 200 MB of data on it, so they can splice that to save user data. Only other way is to repartition /system or /userdata for the space needed for the new partition.
Yes, I am doing a pixel conversion ROM. Tried just booting the pixel /system and it didn't work. I am taking assets from the Tamien and putting them into our November update using SuperR.
Uzephi said:
Unless Motorola can repartition the phone, Treble won't come out, it needs a vendor partition. I can say at least on my Sprint phone the OEM block is about 1.5 GB when there is only about 200 MB of data on it, so they can splice that to save user data. Only other way is to repartition /system or /userdata for the space needed for the new partition.
Yes, I am doing a pixel conversion ROM. Tried just booting the pixel /system and it didn't work. I am taking assets from the Tamien and putting them into our November update using SuperR.
Click to expand...
Click to collapse
I know there are few devs out there working on making it work on non treble phones. Repartitioning and adding a vendor partiion wouldn't be the issue with making it work. Rather trying to get the vendor source for drivers to add to it, and if they need to be reworked to add support. I've been off for a few months with health issues so I'm still getting back into things with oreo, but that seems to be the biggest issue at the moment that I could find.
When my health is back to 100 percent within a couple weeks I will dive into work with you and aid in any way possible for this. To me, trying to get driver source and make it work sounds fun. but we are far off topic now for this post so I'll leave this here haha.
Will someone please help me before i go crazy. I done rooted several phones but i ran into this problem with the G7play. The bootloader is unlocked but Magisk wont install an everytime I modify the system partition (A or B) in TWRP recovery but I boot into Android and nothing changed… I go back to TW RP and it's still showing the files I put are all there but then when I boot back into Android nothing I do affects the actual system partition… why the hell can i modify it in TWRP an it has no effect when booted? is there a 3rd system partition or something's i don't know about??? where is it storing this original copy? someone please help me its drivin me crazy.
I'm having the same problem. I just created a new thread myself on this very issue. It seems some security has been implemented with the most recent stock OTA updates cause on older versions of the stock room, Magisk would flash fine and remain there once the phone started again.
DenhamsOwnSmoky said:
Will someone please help me before i go crazy. I done rooted several phones but i ran into this problem with the G7play. The bootloader is unlocked but Magisk wont install an everytime I modify the system partition (A or B) in TWRP recovery but I boot into Android and nothing changed… I go back to TW RP and it's still showing the files I put are all there but then when I boot back into Android nothing I do affects the actual system partition… why the hell can i modify it in TWRP an it has no effect when booted? is there a 3rd system partition or something's i don't know about??? where is it storing this original copy? someone please help me its drivin me crazy.
Click to expand...
Click to collapse
theburrus1 said:
I'm having the same problem. I just created a new thread myself on this very issue. It seems some security has been implemented with the most recent stock OTA updates cause on older versions of the stock room, Magisk would flash fine and remain there once the phone started again.
Click to expand...
Click to collapse
That is a pain the ass known as FEC hard at work. The only way around it is system root (which magisk doesn't use) or a custom kernel. Twrp is actually using a magisk binary to do root work. Magisk uses mirrors which don't actually change any files. They only simulate changes. So everything you do in twrp will never actually change anything until you root with magisk. If you make changes then root later, they'll show up when you boot the system.
I investigated it a couple months ago. If you want to see the technical side of it, read my posts that start on this page.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/page90
FEC is like ECC RAM, but for system files instead.
Spaceminer said:
That is a pain the ass known as FEC hard at work. The only way around it is system root (which magisk doesn't use) or a custom kernel. Twrp is actually using a magisk binary to do root work. Magisk uses mirrors which don't actually change any files. They only simulate changes. So everything you do in twrp will never actually change anything until you root with magisk. If you make changes then root later, they'll show up when you boot the system.
I investigated it a couple months ago. If you want to see the technical side of it, read my posts that start on this page.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/page90
FEC is like ECC RAM, but for system files instead.
Click to expand...
Click to collapse
Thanks that makes sense now...I managed to get it where I could modify it by installing AOSP. That's why I don't like Magisk confuses the hell outta me. Only reason I was installing it is cuz SuperSU dont usually work on newer systems no more but I have a trick with Magisk I did on my G6...This might be helpful to anyone who wants a system root with Magisk. Backup your boot an dtbo an system partition. Then install magisk. Then you go in an find all the lil files that magisk added that aren't really there (system-less) an create tarfiles of them. /sbin /data/adb /init /init.rc an there mite be more I don't remember fer sure. After you make the tarfiles you reflash the original magisk-free images you backed up earlier an go into TWRP (assuming youre usin the TWRP version that lets you make permanent changes to the system partition) an extract all the tarfiles into the same locations an then you install the magisk apk an if you did it right it'll act like magisk is installed an it manages root fer you an everything but it dont have all that system-less problems you get with regular magisk.
Coming from a Pixel 3 XL, which has been rooted since I got it (same with the Pixel XL before it). I tried fastboot boot magisk_patched (used 23011 as suggested in another post) I get a boot failure, and it kicks me back into fastboot. If I do the /vbmeta command, then I get the "can't load Android System, your data may be corrupt" error. If I sideload the OTA (latest on the Google website, not the day one patch), I can get back into Android, but still unrooted. I was rooted once, pretty sure I just flashed the modified boot.img, then installed in Android, but I wanted to see if I could root via the OTA, and here we are again. I did find this website, however, I'm concerned if I use the fastboot -w command, won't that wipe the device again? I've already lost a lot of stuff from my Pixel 3 XL due to negligance on my part (deleting files after I thought I was setup, then completely wiped the old phone), so I'd rather not do a 4th setup if possible.
[CLOSED] Firmware is out! Get your root on!
Update 12/15/21: Magisk 23016 incorporates fixes for vbmeta header patching; disabling verity/verification is no longer necessary. Update and root should work as it always has - simply patch and flash the boot image. Any update method can be...
forum.xda-developers.com
PERMANENT ROOT CURRENTLY REQUIRES A DATA WIPE.
KiLLiNGDAY said:
[CLOSED] Firmware is out! Get your root on!
Update 12/15/21: Magisk 23016 incorporates fixes for vbmeta header patching; disabling verity/verification is no longer necessary. Update and root should work as it always has - simply patch and flash the boot image. Any update method can be...
forum.xda-developers.com
PERMANENT ROOT CURRENTLY REQUIRES A DATA WIPE.
Click to expand...
Click to collapse
so each OTA/monthly patch I have to wipe my phone? That'll get old super fast. I already wiped it once when I first rooted...
Tmender said:
so each OTA/monthly patch I have to wipe my phone? That'll get old super fast. I already wiped it once when I first rooted...
Click to expand...
Click to collapse
It appears so, at least at this point. Maybe people will find a way to circumvent this.
Even though - with a decent root backup like swift - it shouldn't be that big a hassle, but it's troublesome for sure.
Morgrain said:
It appears so, at least at this point. Maybe people will find a way to circumvent this.
Even though - with a decent root backup like swift - it shouldn't be that big a hassle, but it's troublesome for sure.
Click to expand...
Click to collapse
swift? Here I've been using Titanium Backup for years...
check out and decide:
https://www.reddit.com/r/androidapps/comments/gvdnf1
Hi,
I flashed TWRP on my unlocked Redmi Note 8T with MIUI Global 12.5.5. Everything was great until I rebooted it and saw Bluetooth error which pops every time I try to turn Bluetooth on or just randomly during usage of the device. I also tried to re-flas TWRP with Orange fox but it unfortunatelly did not help. Now I have no idea what to do but there are also some other people with this problem (for example:
https://www.reddit.com/r/Xiaomi/comments/y9zsak
).
Does anybody know any solution? Thanks!
Btw Orange fox is for ginko devices, I did not find version for willow
I had the exact same problem when I tried to root my stock rom in ginkgo. I was getting a lot of "app keeps stopping" pop ups, and that also included bt. My bt was completely broken until I changed rom. Also I'm guessing this had happened when I had rooted my phone with magisk, not by flashing recovery itself. Perhaps you could try to uninstall magsik, and see it it resolves the issue for you. If that would be the case, then you would have found your problem, and maybe you can flash a custom rom to safely root your phone.
Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
So now it tried one of my ideas, which was to install Magisk (root) and uninstall it but it also did not help (I expected that)
vasik006 said:
Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
Click to expand...
Click to collapse
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.
Yeah, that's true. But don't you know how to backup data from these "offline" apps? I was trying to solve this also before unpocking bootloader like a year ago but unsuccessfuly.
Also, which rom should I choose? I'm deciding between LineageOS and Pixel experience.
So I have LOS installed but I can´t install other zip files (like Google apps). Im only getting error: signature verification failed while. Im using LOS recovery so where is the problem?
Solved it!
Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.
Thanks, this might help someone else with this problem. I have already formatted my phone, installed Lineage OS and everything is ok
For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.
Jatin Verma x821 said:
Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.
Click to expand...
Click to collapse
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly? Tks
ennev said:
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly?
Click to expand...
Click to collapse
no need to unroot. simple factory reset the device and you're done.
Jatin Verma x821 said:
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.
Click to expand...
Click to collapse
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.
Alpha_Geek1 said:
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.
Click to expand...
Click to collapse
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.
Jatin Verma x821 said:
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.
Click to expand...
Click to collapse
TWRP does backup personal apps and their settings. Once you restore a TWRP backup, you have everything back except media files - images, videos, documents, etc. The launcher icons, the apps, the system settings - everything is a perfect clone which you can restore on a new device (same model, of course).
I actually came across this thread searching to see if others had a problem where merely flashing TWRP caused Bluetooth to crash (and Atmos).
Use OrangeFox
is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?
I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
s3rv said:
For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.
Click to expand...
Click to collapse
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
starkshadow said:
is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?
Click to expand...
Click to collapse
It looks like this guy didn't have any luck with it either. It may be divice specific
Dredead said:
I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
It looks like this guy didn't have any luck with it either. It may be divice specific
Click to expand...
Click to collapse
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.
starkshadow said:
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.
Click to expand...
Click to collapse
It seems to be a twrp issue. What version do you have? And what version of magisk do you have?
I have recently flashed miui 12 (android 10) after bricking the phone using qtel. I noticed the Bluetooth problem last week and didn't find a fix. I have twrp 3.6.2 and magisk 25.1. I had twrp 3.7.1 but if failed to decrypt data using pattern so I rolled back to 3.6.2. And I thought that magisk had to do with the Bluetooth problem so I rolled back to 25.1 from 26.
I still can't use the Bluetooth, and I don't have time to reset the phone, I just finished restoring everything
I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210
Olfason said:
I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210
Click to expand...
Click to collapse
I can't afford resetting my phone right now , don't have enough time. I'll let it like that for some months.
Edit : I have miui 12.0.6 installed (android 10) and I'm not planning to upgrade since I have much better battery life (even better than every mod I tried). I wander if I flash miui rom from recovery can fix it?
Edit 2: flashing the rom from recovery didn't fix it