Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Link575 said:
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Click to expand...
Click to collapse
Lineage is using own kernel and boot.img on A11 so in the short run it is not going too make any difference, but when Lineage moves forward to A12 the OEM Firmware has newer drivers and is updated sooner, has more OEM features and bugfixes as well as no carrier bloatware.
It is possible that OP will neuter the Carrier firmware with an OTA update to prevent cross flashing device away from the Carrier rom in the next OTA update by preventing fastbootd from flashing the us oem from a carrier phone.
They have already removed fastboot boot command to boot a boot image without flashing it for test before you flash and to allow Magisk to make a backup of the original boot.img before adding Magisk.
I would convert NOW, before they decide to slam the door on this ability with a future OTA that will not allow you to downgrade and prevent this as they are under contract with the carriers to not allow this to be done.
Ok, thank you for the explanation. Guess I'll back everything up and convert it.
scanman0 said:
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Click to expand...
Click to collapse
This worked perfectly after following your convert guide and upgrading to 12. Downgraded back to 11 so I could install lineageOS. Thanks again!
This reddit post has a link to an English version of the downgrade apk which makes it a little easier.
keeps saying verification failed
weirdfate said:
keeps saying verification failed
Click to expand...
Click to collapse
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
I m trying as well .. but stuck with verification failed message just as scanman0 I m on stock android12 no root if anyone know how to fix it ... please assit
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
radekmazur said:
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
Click to expand...
Click to collapse
I did not have to remove root. I used the version posted that does not check for root but maybe there's a different reason.
Does the downgrade apk have to be sideloaded via ADB?
T3CHN0T33N said:
Does the downgrade apk have to be sideloaded via ADB?
Click to expand...
Click to collapse
Just place apk in phones working directory, same path where your downloads folder is. Then install from there like any other apk and run. I also kept the FW file in the same directory but I'm not sure if that was necessary.
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
T3CHN0T33N said:
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
Click to expand...
Click to collapse
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Link575 said:
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Click to expand...
Click to collapse
When you say "screwed things up" what do you mean? How did it effect the install?
T3CHN0T33N said:
When you say "screwed things up" what do you mean? How did it effect the install?
Click to expand...
Click to collapse
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Link575 said:
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Click to expand...
Click to collapse
Weird, for me it just closes the app and does nothing, both the official and emergency ones. I even tried adding it to magisk's deny-list.
But I just restored the boot image via magisk (didn't restart) and it works now...
scanman0 said:
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
Click to expand...
Click to collapse
Yes I factory restored the phone and tried again. Still fails every time
Has anybody had any luck figuring out the verification failed message? I too have tried both the official and emergency apps, of course I can't read the actual message in what I presume is Chinese, but it doesn't do anything and the other version says verification failed. Have not rooted. Kind of at a loss right now and all I want to do is install Lineage! I've already got my unlock token from OnePlus, but my understanding is that the phone still needs to be on A11 before installling Lineage.
Related
Hello
I have a new M10 Pro (BLA-A09) here in the US, and I haven't activated it yet as I remain undecided about using it. The activity in this thread is limited, and I thought that there were more ROMS available. Perhaps I'm wrong, but I see very little activity for this phone. My current phone is an LG V10 which is unrootable, therefore moving to the M10P would be a good change since I can at least root the M10P and remove the bloatware.
I have a bootloader unlock code that I got on the last day! And I am on build 8.0.0.65 (C567).
I've read most of the current threads in this forum and the ROMS/kernels forum, and I remain confused as to what can be done with this phone.
I ask:
1. Can the phone truly be rooted? If yes, what for? To remove bloatware only? Or are there rooms (xirin, etc)?
2. I think that I read that rooting removes the data partition. Is that true? And how does that hurt?
3. I know that I can rebrand the phone with funkyhuawei. Why would I want to do that here in the US?
4. An OTA that follows a root, requires re-rooting the phone after the OTA, right?
Thank you for the help. I am excited about using this very powerful phone, I superficially read some threads before buying it, and I thought that it would be a very rootable and ROMable phone; I am not sure if that is the case.
nabril15 said:
Hello
I have a new M10 Pro (BLA-A09) here in the US, and I haven't activated it yet as I remain undecided about using it. The activity in this thread is limited, and I thought that there were more ROMS available. Perhaps I'm wrong, but I see very little activity for this phone. My current phone is an LG V10 which is unrootable, therefore moving to the M10P would be a good change since I can at least root the M10P and remove the bloatware.
I have a bootloader unlock code that I got on the last day! And I am on build 8.0.0.65 (C567).
I've read most of the current threads in this forum and the ROMS/kernels forum, and I remain confused as to what can be done with this phone.
I ask:
1. Can the phone truly be rooted? If yes, what for? To remove bloatware only? Or are there rooms (xirin, etc)?
2. I think that I read that rooting removes the data partition. Is that true? And how does that hurt?
3. I know that I can rebrand the phone with funkyhuawei. Why would I want to do that here in the US?
4. An OTA that follows a root, requires re-rooting the phone after the OTA, right?
Thank you for the help. I am excited about using this very powerful phone, I superficially read some threads before buying it, and I thought that it would be a very rootable and ROMable phone; I am not sure if that is the case.
Click to expand...
Click to collapse
1: yes. For anything you need root for, really.
Most bloatware can be removed without root, unless you want to start removing system apps. There are a few treble roms available over at the treble forum https://forum.xda-developers.com/project-treble.
Most, if not all, should be compatible. And you have https://openkirin.net/ which are for Huawei phones.
2. It does not. Well, it depends on where you read it. TWRP couldn't decrypt /data before, so you had to Format it and remove the encryption flag in fstab, but that is not needed anymore. (Official TWRP still can't, see download link below)
3. Do not rebrand. A09 is not compatible with L09/L29/AL and you will brick.
Also, if you had used it you would now be bootloader locked. What FH does is that it flashes an included oeminfo that has dualsim enabled. This also changes your IMEI, IMEI2 and SN in fastboot, making your old unlock code invalid. And right now there is no way to get a new one (I'm not sure if DC still works with A09, it doesn't on C432 as of B145.)
4. Yes. As ramdisk is overwritten you have to flash Magisk again (I suggest Magisk as SuperSU is not updated anymore)
Basically, you want to:
Go here to download TWRP: https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Or Beta Magisk, can be buggy: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Backup your sdcard contents.
Go to Settings -> System -> About Phone -> Tap Build number until Developer options is enabled
Go to Settings -> System -> Developer options
Enable OEM Unlocking
Reboot to fastboot.
Unlock bootloader using: fastboot oem unlock ##unlock_code##
Use Volume key to move to 'Yes' on phone, then power to accept.
Wait for format to finish, setup phone again.
Transfer magisk zip to sdcard.
Reboot to fastboot again
Flash TWRP using: fastboot flash recovery_ramdisk twrp_bla_alp_0.7.img
Reboot to recovery by holding Power and Volume Up.
Enter your Pin
Now flash Magisk
Finished.
ante0 said:
1: yes. For anything you need root for, really.
Finished.
Click to expand...
Click to collapse
Thanks a lot ante0. I really appreciate it.
1. You pasted
Enable OEM Unlocking
Reboot to fastboot.
How do I reboot into fastboot?
2. So, can I use twrp? I really like it and have been using it for years on other phones and tablets.
3. I will use magisk and not SU, right?
4. I've been using the phone on wifi only and without a sim card, so it's not active on ATT here in the US. In the twrp thread I see that for OTA I need the following:
Flash with TWRP Magisk Uninstaller
Flash in Fastboot Mode recovery_ramdisk.img (=EMUI Recovery) + ramdisk.img + kernel.img
In Systemupdate settings (dot menu) use "Download and install current full package" (=FullOTA-MF, some GB) instead of only OTA (some MB)
Wow. How complicated, but I'm sure it's not that difficult. Although, in that same thread, I also read that some people have installed the OTA without removing magisk.
5. Kirin or treble roms? I can't see screenshots of either, so how do we decide?
Thanks again
nabril15 said:
Thanks a lot ante0. I really appreciate it.
1. You pasted
Enable OEM Unlocking
Reboot to fastboot.
How do I reboot into fastboot?
2. So, can I use twrp? I really like it and have been using it for years on other phones and tablets.
3. I will use magisk and not SU, right?
4. I've been using the phone on wifi only and without a sim card, so it's not active on ATT here in the US. In the twrp thread I see that for OTA I need the following:
Flash with TWRP Magisk Uninstaller
Flash in Fastboot Mode recovery_ramdisk.img (=EMUI Recovery) + ramdisk.img + kernel.img
In Systemupdate settings (dot menu) use "Download and install current full package" (=FullOTA-MF, some GB) instead of only OTA (some MB)
Wow. How complicated, but I'm sure it's not that difficult. Although, in that same thread, I also read that some people have installed the OTA without removing magisk.
5. Kirin or treble roms? I can't see screenshots of either, so how do we decide?
Thanks again
Click to expand...
Click to collapse
1. Either you can use adb: adb reboot bootloader
Or power off phone then hold volume down and plug in usb
Or plug in usb, reboot, hold volume down.
2. Yes, it's fully functional.
3. Magisk is preferable. Mainly because it's being updated, and can pass Safetynet if any of your apps need it to pass.
4. You *should* only need to flash recovery_ramdisk (I guess you can use the one from the last update on http://pro-teammt.ru/firmware-database/?firmware_model=BLA-A09&firmware_page=0)
To get recovery_ramdisk you need to download update.zip from pro-teammt.ru, then extract update.app from it.
Download Huawei Update Extractor https://forum.xda-developers.com/showthread.php?t=2433454
Extract Huawei Update Extractor zip and run the exe. Go to settings in the program and disable header check.
Next open up update.app in it, rightclick on recovery_ramdisk and click on Extract Selected.
Now you can flash that image using fastboot (fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img)
This will restore stock recovery and will let you flash OTA directly from System Update.
The reason you have to restore stock recovery is because phone will reboot to recovery to update, but if you have TWRP flashed it won't update at all
You would have to flash back both TWRP and Magisk after update finishes.
(You can actually flash FULLOTA Update.zip directly in TWRP if you use HuRUpdater, but seeing as the US Mate 10 Pro rarely get any updates it's not really needed.)
5. Kirin is treble, they are built for Huawei devices rather than being just for treble enabled devices.
I've only really used Lineage, but moved back to stock as TWRP does not work with Treble roms. It should work once we get 8.1 firmware though.
ante0 said:
5. Kirin is treble, they are built for Huawei devices rather than being just for treble enabled devices.
I've only really used Lineage, but moved back to stock as TWRP does not work with Treble roms. It should work once we get 8.1 firmware though.
Click to expand...
Click to collapse
thanks again Ante
Would you say that it makes sense for me to, when I put the sim in the phone and use it (if I decide to), to attempt an OTA update first, and then do root and whatever else? My phone's build is from December 2017, so I assume that ATT will have some sort of update for the phone.
You mentioned that the US Mate10 rarely gets updates. So, then how would any of us get any updates , security or otherwise? How will we get 8.1, for example? Are you in the US, btw? What ROM are you using on this phone?
ante0 said:
5. Kirin is treble, they are built for Huawei devices rather than being just for treble enabled devices.
I've only really used Lineage, but moved back to stock as TWRP does not work with Treble roms. It should work once we get 8.1 firmware though.
Click to expand...
Click to collapse
thanks again Ante
Would you say that it makes sense for me to, when I put the sim in the phone and use it (if I decide to), to attempt an OTA update first, and then do root and whatever else? My phone's build is from December 2017, so I assume that ATT will have some sort of update for the phone.
You mentioned that the US Mate10 rarely gets updates. So, then how would any of us get any updates , security or otherwise? How will we get 8.1, for example? Are you in the US, btw? I assume that you have the device; what ROM are you using?
nabril15 said:
thanks again Ante
Would you say that it makes sense for me to, when I put the sim in the phone and use it (if I decide to), to attempt an OTA update first, and then do root and whatever else? My phone's build is from December 2017, so I assume that ATT will have some sort of update for the phone.
You mentioned that the US Mate10 rarely gets updates. So, then how would any of us get any updates , security or otherwise? How will we get 8.1, for example? Are you in the US, btw? I assume that you have the device; what ROM are you using?
Click to expand...
Click to collapse
I do not have a US Mate 10 Pro (A09), but the global (L29) on C432.
You can read a bit in this thread about the US version updates:
https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-bla-a09-c567-usa-t3775258
I guess the lack of updates is due to the problems Huawei has with the US government. :/
You do get updates, but there seem to be a few months between them.
I would update and then root. There is an update in that thread which is fairly new, but it has not been indexed by Firmware Finder (pro-teammt.ru). You could flash it using TWRP and HuRUpdater as I don't think you have Nocheck recovery for A09.
FOR MOTO G7 PLUS ONLY!!!
Hello, everyone.
I created a .bat file "executable " For those who want to flash the stock rom on your Moto G7 Plus.
Just put it in the stock Rom folder along with the fastboot files and run the file.
For those who want the file, just download it by the following link or download the file that is on the thread.
http://www.mediafire.com/file/q836uaerr17pn0f/Flash_ROM_G7%252B.zip/file
Could you share where to get the Stock ROM fein?
---------- Post added at 11:13 PM ---------- Previous post was at 10:25 PM ----------
Tried the same sequence with a Stock ROM last week, but didn't achieve to get back to original ROM. I always get the prompt in the initial boot, that a different OS is installed than the original. This has the consequence that I cannot upgrade wit OTA anymore. And there is an upgrade already available (Jan security patch)
moto g7 G7........
any one have a flash rom.bat stock rom for moto g7.......
Which stock rom did you flash on your Moto g7 plus?
Where can I find the stock rom?
Nes.
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
Didn't you just find it yesterday on the telegram group?
What was the problem that you asked again here today?
Latest Stock ROM RETAIL at that link is the one we have all been using.
You'll need to download it to a computer, unzip it in a folder with the fastboot/ADB files, then fastboot flash it with phone attached in bootloader mode.
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
You have a model of the XT1965-3 smartphone and region of the software is reteu? Then this your last firmware.
"Your device has loaded a different operating system."
baikal0912 said:
You have a model of the XT1965-3 smartphone and region of the software is reteu? Then this your … .
Click to expand...
Click to collapse
Thank you very much!
I guess that the software channel was reteu.
A second moto g7 phone I bought - and is unmodified - says "software channel: reteu".
The information on the package of my phone says XT1965-3.
I flashed this image already, the result is a 'working' system except for the message at the start "Your device has loaded a different operating system." .
NesNol said:
Thank you very much!
I guess that the software channel was reteu.
A second moto g7 phone I bought - and is unmodified - says "software channel: reteu".
The information on the package of my phone says XT1965-3.
I flashed this image already, the result is a 'working' system except for the message at the start "Your device has loaded a different operating system." .
Click to expand...
Click to collapse
This will get rid of that message we all got too:
[Bootlogo] Modded Bootlogo from unlocked bootloader
The new RETEU stock version was just updated in last few days, before that not available and you could have used the RETAIL channel that I mentioned above, it worked fine for several users on RETEU channel.
Dahenjo said:
This will get rid of that message we all got too:
The new RETEU stock version was just updated in last few days, before that not available and you could have used the RETAIL channel that I mentioned above, it worked fine for several users on RETEU channel.
Click to expand...
Click to collapse
Get rid of the message?
Does that also mean that OTAs will work? That banking apps will not complain about the integrity of the system?
Thanks!
NesNol said:
Get rid of the message?
Click to expand...
Click to collapse
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
After unlocking bootloader there is some message like this on starting device, keep in mind we all got these too and everything is fine but we like to cover it up with a different bootlogo, just looks better that is its only purpose. This message is because you also upgraded the firmware, meaning it's not really a different OS but only a different version of your correct OS.
Does that also mean that OTAs will work? That banking apps will not complain about the integrity of the system?
Click to expand...
Click to collapse
For G7 Plus we are not getting the OTAs properly after unlocking or rooting, I was originally rooted on PPW29.98-28 and repeatedly got the notifications of upgrading to 29.98-66-2 but it kept failing, the only way to stop it was freezing the Moto Update Process using Titanium Backup. So my only remaining option to upgrade was to fastboot flash the full firmware, as you just did, it wipes your data but gets you to the same place.
With future updates we may be able to capture them and then a dev can make them into a TWRP flashable zip with no wiping of internal data. We had that on G5 Plus which was a nice thing and they are still doing that. But until that might happen the best we can do is the same for now - when your channel has an update just get it from lolinet (these are all official stock firmwares there) and fastboot flash after backing up your data.
Usually it is more from the rooting (if you did that too) that may mess up your banking or other apps, but in Magisk there are settings that may work on that, you'll just have to try and see but there are mixed results. My choice is to not use banking apps on my devices anyway even if not unlocked or rooted, I just do it from home on a computer that I won't forget and leave out in public somewhere. :crying:
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
Click to expand...
Click to collapse
Hi,
thank you very much for your elaborate answer!
I will come back on it soon.
Nes
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
After unlocking bootloader there is some message like this on starting device, keep in mind we all got these too and everything is fine but we like to cover it up with a different bootlogo, just looks better that is its only purpose. This message is because you also upgraded the firmware, meaning it's not really a different OS but only a different version of your correct OS.
For G7 Plus we are not getting the OTAs properly after unlocking or rooting, I was originally rooted on PPW29.98-28 and repeatedly got the notifications of upgrading to 29.98-66-2 but it kept failing, the only way to stop it was freezing the Moto Update Process using Titanium Backup. So my only remaining option to upgrade was to fastboot flash the full firmware, as you just did, it wipes your data but gets you to the same place.
With future updates we may be able to capture them and then a dev can make them into a TWRP flashable zip with no wiping of internal data. We had that on G5 Plus which was a nice thing and they are still doing that. But until that might happen the best we can do is the same for now - when your channel has an update just get it from lolinet (these are all official stock firmwares there) and fastboot flash after backing up your data.
Usually it is more from the rooting (if you did that too) that may mess up your banking or other apps, but in Magisk there are settings that may work on that, you'll just have to try and see but there are mixed results. My choice is to not use banking apps on my devices anyway even if not unlocked or rooted, I just do it from home on a computer that I won't forget and leave out in public somewhere. :crying:
Click to expand...
Click to collapse
So you expect that in future my phone will be OK again? And receive OTAs while having Magisk installed.
I tried indeed to Magisk my phone, as I did with my old OnePlus One.
Which leads to TWRP, but then I discovered that the recovery has disappeared on this Moto!?
Then I was lost, and read about A/B and treble(?).
Concerning the banking applications: Even if I handle the banking transactions on my Mac, I still need the banking app on my phone for authentication.
Which is also true for accessing my medical data (GP, hospitals, etc), insurance companies, taxes, etc.
Last question: Is there a full description of how to magisk my phone?
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
…
…
Click to expand...
Click to collapse
I have replied to this messages twice.
None has arrived?!
Nes
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
…
…
…
…
Click to expand...
Click to collapse
I have replied to this message twice.
None has arrived?!
Nes
NesNol said:
So you expect that in future my phone will be OK again? And receive OTAs while having Magisk installed.
I tried indeed to Magisk my phone, as I did with my old OnePlus One.
Which leads to TWRP, but then I discovered that the recovery has disappeared on this Moto!?
Then I was lost, and read about A/B and treble(?).
Concerning the banking applications: Even if I handle the banking transactions on my Mac, I still need the banking app on my phone for authentication.
Which is also true for accessing my medical data (GP, hospitals, etc), insurance companies, taxes, etc.
Last question: Is there a full description of how to magisk my phone?
Click to expand...
Click to collapse
Sorry not to reply yet, I sometimes have other things going on besides my phone. Also I thought I gave you a good answer on the situation, based on what I know as just another user (not a dev, not with Moto).
Yes, there have been changes since your last phone, it was the same for me. So it's good to find out as much as possible before deciding to unlock & root again, because the results may not be like before. We used to unlock and flash TWRP directly but we can't do that now or maybe brick the phone. It is always the risk when choosing not to remain fully stock/locked/etc as when you bought it, and with that is a responsibility to do the research first and not just expect other users to tell you every step.
So I don't know if things will change, but for now we can't get OTAs anymore after unlocking. For me I didn't mind and I am willing to upgrade manually if that let's me work with the device the way I like with root & using custom ROMs etc. I didn't plan to ever go back to how I bought it and don't need banking apps or other types that rooting might mess up. For others that may not be the case so they must learn the situation then decide for themselves.
As for installing Magisk, now we have TWRP working enough to just put the Magisk zip on your SD card and install it in TWRP. Before we had a functional TWRP we had another method by installing Magisk Manager and using it to patch the boot.img then fastboot flash that, but it's not needed anymore since TWRP, just do it the old way now.
Flashing the roms from lolinet, in my case ( RETEU[/URL) is a complete reset of the phone, I assume.
To flash, these steps should be right:
Copying the firmware to sdcard.
Boot in TWRP
Flashing the lolinet firmware.
Delete Dalvik Cache.
Should TWRP and Magisk be reinstalled immedeately after this procedure? Or renew the developer mode, reinstall twrp and magisk?
Woif said:
Flashing the roms from lolinet, in my case RETEU is a complete reset of the phone, I assume.
To flash, these steps should be right:
Copying the firmware to sdcard.
Boot in TWRP
Flashing the lolinet firmware.
Delete Dalvik Cache.
Should TWRP and Magisk be reinstalled immedeately after this procedure? Or renew the developer mode, reinstall twrp and magisk?
Click to expand...
Click to collapse
It won't work to flash full firmware in TWRP, so far the only way is using fastboot with phone connected to a computer in bootloader (unlocked) mode. Unzip firmware into your fastboot/ADB folder and also the batch file available in this thread, then run the batch file.
Yes this will reset/wipe your phone (except for SD) so backup your data first, and it will be like when you first bought it. You can reinstall TWRP and then Magisk, but boot to system first and set things up including enabling USB debugging setting in developer options again.
I am going to try and update now as the notifications are much too annoying.
Moto G7 Plus - lake Stock rom / firmware download here
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
Moto G7 Plus - lake
Download the Moto G7 Plus - lake stock firmware according to the Country/region/retail/carrier for example US Retail > T-Mobile, Verizon or Amazon, and everything is flashed through fastboot mode
XT1965-2 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-2-stock-rom/
XT1965-3 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-3-stock-rom/
XT1965-4 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-4-stock-rom/
XT1965-6 > https://boycracked.com/2019/07/26/official-motorola-moto-g7-plus-xt1965-6-lake_retcn-stock-rom/
XT1965-9 > https://boycracked.com/2019/07/26/official-motorola-moto-g7-plus-xt1965-9-lake-stock-rom/
XT1965-T > https://boycracked.com/2019/07/26/o...-g7-plus-xt1965-t-lake-us-t-mobile-stock-rom/
Remove the line
'fastboot erase userdata'
from the flashROM.bat file and it won't factory reset. It will act like an upgrade.
Sent from my Moto Z (2) using XDA Labs
vickbuitenzorg said:
Moto G7 Plus - lake
Download the Moto G7 Plus - lake stock firmware according to the Country/region/retail/carrier for example US Retail > T-Mobile, Verizon or Amazon, and everything is flashed through fastboot mode
Click to expand...
Click to collapse
Can I use a different retail code than current stock? My phone is XT1965-2, PPW29.98-28, RETLA. The system reminders are all in Spanish. Could I update to PPW29.98-66, EEGB (UK English) without a problem?
Also, if this is possible, could I update by removing the 'fastboot erase userdata' line from the BAT file, or, due to the language change, would I need to leave that line and do a factory reset?
https://developers.google.com/android/ota
Ota is live too...
Where I found the changelog?
Thanks
shark147 said:
Where I found the changelog?
Thanks
Click to expand...
Click to collapse
Same place as always: https://source.android.com/security/bulletin/pixel/2019-05-01.html
There doesn't seem to be much though:
This quarterly release contains many functional updates and improvements to various parts of the Android platform and supported Pixel devices.
Click to expand...
Click to collapse
No issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
sliding_billy said:
No issues installing my wife's P3 with flash-all (minus -w), rooted with Magisk 19.1 and TWRP 3.3.0-0 fully installed using Advanced > Install Recovery Ramdisk method.
Click to expand...
Click to collapse
Could you give me some more details on what you did to install Magisk? For the first time with my P3 I cannot get anything to work. I flashed the May update minus -w, but every method of installing Magisk 19.1 that I've tried ends up with a bootloop.
CSX321 said:
Could you give me some more details on what you did to install Magisk? For the first time with my P3 I cannot get anything to work. I flashed the May update minus -w, but every method of installing Magisk 19.1 that I've tried ends up with a bootloop.
Click to expand...
Click to collapse
1) flash-all (minus -w). Phone reboots to system automatically.
2) shut down and boot to BL
3) fastboot boot twrp-3.3.0-0-blueline.img (be sure to have a copy of the .img file on your phone)
4) install twrp using Advanced > Install Recovery Ramdisk > twrp-3.3.0-0-blueline.img
5) boot to system
6) shut down and boot to BL>recovery (TWRP loads)
7) install Magisk-v19.1 (I did already have 19.1 installed on this phone via Magisk Manager update/Magisk update from before the May image came out in case it matters, so if necessary install 18.1 and then update to 19.1 with Magisk Manager)
8) reboot to system
9) confirm root and install kernel (for me that was ElementalX automated install using EX Kernel Manager app but installing the kernel by going back to TWRP and flashing should do the same)
The two things I might be doing different than others are not using ADB to get back to BL or recovery (I always use the key combo) and booting to system before next step (I don't stack my TWRP/Magisk/kernel installs). Hope this helps.
Whew! Back in business. Thanks!
CSX321 said:
Whew! Back in business. Thanks!
Click to expand...
Click to collapse
That's cool. Which part was the culprit?
sliding_billy said:
That's cool. Which part was the culprit?
Click to expand...
Click to collapse
Well, I don't really know. I initially did what I always do: extract the new boot.img from the update, patch it with MM, run flash-all without -w, let the update finish, reboot and flash the patched boot to boot_a and boot_b. That bootlooped. I flashed stock boot.img and ran like that for a day. Next I booted (but didn't install) TWRP, and tried to install 19.1 (bootloop), and 18.1 (wouldn't install). I decided to try to downgrade to the April update and did flash-all from there (without -w). Big mistake, because then it stuck on the G screen and wouldn't boot at all. I ultimately was able to flash back to the May update, get it to boot, then followed your directions. I did have to install 18.1 first, because even after following your directions, 19.1 still bootlooped when installed from TWRP. MM was able to update to it fine, though, from 18.1. Who knows what the problem really was.
CSX321 said:
Well, I don't really know. I initially did what I always do: extract the new boot.img from the update, patch it with MM, run flash-all without -w, let the update finish, reboot and flash the patched boot to boot_a and boot_b. That bootlooped. I flashed stock boot.img and ran like that for a day. Next I booted (but didn't install) TWRP, and tried to install 19.1 (bootloop), and 18.1 (wouldn't install). I decided to try to downgrade to the April update and did flash-all from there (without -w). Big mistake, because then it stuck on the G screen and wouldn't boot at all. I ultimately was able to flash back to the May update, get it to boot, then followed your directions. I did have to install 18.1 first, because even after following your directions, 19.1 still bootlooped when installed from TWRP. MM was able to update to it fine, though, from 18.1. Who knows what the problem really was.
Click to expand...
Click to collapse
I'd just be spit balling at this point like you are, but at least you are up and running. I do think there is possibly something going on with Magisk going from 18.1 to 19.1 without Manager doing the back end work (even if it happened previously) since Magisk still does retain some data even if root is lost during the upgrade. There are certainly some changes that occured between 18.1 and 19.0 beta since coming from 18.1 you would need to redo your Magisk hide check marks. Either that or using MM to patch boot may have completely changed.
sliding_billy said:
There are certainly some changes that occured between 18.1 and 19.0 beta
Click to expand...
Click to collapse
I probably just had something in some weird state, because I ran 18.1, 19.something beta, 19.something canary, then back to 19.1 stable when it came out. I forgot, I also ran the uninstaller at some point in my previous attempts.
I have a PIXEL 3 (Bought directly from Google) and AT&T is my carrier in Central VA. Been trying for a couple of days to get the May update, but nothing avail. Something I should be concerned about?
Same question
djboydva1 said:
I have a PIXEL 3 (Bought directly from Google) and AT&T is my carrier in Central VA. Been trying for a couple of days to get the May update, but nothing avail. Something I should be concerned about?
Click to expand...
Click to collapse
I was coming to ask the same question, only I am in WA and have T-mobile. Stock, not rooted. Not had an issue before.
Same here. New P3 during April, so awaiting first security update for my new device. Carrier is AT&T, but why would that matter, right? Just seems strange having to wait. I got the impression that monthly updates for Pixels would come out the same day they were announced as being available. Live and learn I guess.
Finally popped this evening (5/16/2019). No clue why the delay.
djboydva1 said:
I have a PIXEL 3 (Bought directly from Google) and AT&T is my carrier in Central VA. Been trying for a couple of days to get the May update, but nothing avail. Something I should be concerned about?
Click to expand...
Click to collapse
I have a Pixel 3 on Google Fi and still haven't gotten the update. Contacted support yesterday and they couldn't find anything wrong. They "promised" I'd get it. Always gotten them within a day or two before.
I guess I just never looked into this before since I'm a new Pixel user or I'm just naive but I assumed when I got a Pixel phones updates would not have to be pushed through my carrier anymore? No May update here on my stock Pixel 3 on T-Mobile.
Always get OTA on the day of release, stock phone, T-Mobile, the Netherlands.
(Pixel didn't launch in the Netherlands, I got it from Germany)
Just installed the may update OTA.
Anyone else having issues with apps accessing the gallery. Both WhatsApp and stock messenger now taking ages to display the thumbnails of the images and videos in my gallery when I add them to a message.
ok could I get some hints here on how to update?
I have rooted and I have magisk.
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
noxarcana said:
I'd like to keep this simple. I tried rooting and not a single tutorial on here has ended with root privileges for various reasons. I'm done with it. I flashed stock firmware in hopes of removing any trace of files that may have been altered during the various root tutorials I followed, but Samsung Pass says the device is still rooted.
What do I need to do to return to 100% stock?
Click to expand...
Click to collapse
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
This method works perfectly on T860.
***********************
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
jhill110 said:
I assume you unlocked the bootloader. Try Relocking and flash the firmware again.
Weather that will work is anybodys guess.
Rooting is a pretty simple procedure I can't think of any reason it didn't work except user error.
Click to expand...
Click to collapse
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
noxarcana said:
Well, this isn't the first time I've rooted a device and I followed every step of every tutorial I found on here and, for some reason, it would not root. This is the first, and only, device I've had this much trouble with.
The tutorial for rooting without TWRP: I made the patched AP file and flashed it; however, I could not boot into recovery or download mode and it always stuck on the boot logo.
The tutorial for installing TWRP didn't have a link for the encryption disabler and the one I found did absolutely nothing and the folders in storage just showed as a string of numbers and letters.
Maybe, if someone could put together a full tutorial with the files being used within the tutorial, it would have worked.
Click to expand...
Click to collapse
Did you get the bootloader unlocked?
Unlocking the bootloader:
https://www.getdroidtips.com/how-to...to_Unlock_Bootloader_on_Samsung_Galaxy_Tab_S6
To get to download mode it's volume up and volume down then plug your pc into device. NOT POWER AND VOLUME DOWN. This can be a pain in the back side.
If you do it this way you'll get the option unlock / lock bootloader or go to bootloader mode.
If you follow the instructions perfectly and then follow the instructions for rooting it will work.
Move on to root.
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Install TWRP.
TWRP :
https://forum-xda--developers-com.c...b-s6/development/recovery-twrp-3-3-1-t3975587
I hope this helps you out.
If you have anymore questions just ask.
Disable DM VERITY ENCRIPTION DISABLER
PATCHED ODIN
jhill110 said:
Did you get the bootloader unlocked?
Click to expand...
Click to collapse
Yep, bootloader unlock was easy. I'll give root another try with your steps in a couple of days when I'm off work. Sorry if I came across a bit aggressive in my previous posts; I have a tendency to do so even when I'm not frustrated.
This has been so frustrating to me because I know rooting is usually a simple process; as you said previously.
jhill110 said:
ROOTING :
https://forum-xda--developers-com.c...-to/root-guide-t860-root-twrp-method-t4095677
AP SLOT = PATCHED FILE
BL SLOT = BL FILE
CP SLOT = CP FILE (T865) NOT T860... T860 HAS NO CP FILE
CSC SLOT =HOME CSC FILE
DON'T forget to setup WiFi before installing magisk manager. ^^^^^^^^^
Click to expand...
Click to collapse
So, yea, I'm a bit late getting around to this. Sorry.
This is where things get hung up. Everything flashes just fine and I can even get into TWRP; however, when I try to boot the tablet i get the Galaxy Tab S6 screen, then the warning about the bootloader being unlocked, and back to the Galaxy Tab S6 screen but with a "unofficial software" warning....and repeat. It just boot loops and this is where I've since I started this thread.
Also, returning to stock doesn't completely remove root traces as I can't use Samsung Pass and I simply get a warning about the device seemingly being rooted even though it isn't.
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
bartleby999 said:
If you installed TWRP, then you tripped Knox tripping Knox will permentally disable Samsung Pay as far as I'm aware. You'll never get it back, regardless of root or no root access.
Also, I'm not sure why you're installing TWRP AND trying to flash a Magisk patched OS. It's one or the other, you don't need to do both. Unless something has changed in Android 10?
If you're flashing TWRP, you just need to flash Magisk in TWRP(along with the other files!), no need to patch AP.
Click to expand...
Click to collapse
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
noxarcana said:
Not Samsung Pay, I couldn't care less about that, but Samsung Pass; I guess it looks for knox being tripped now too. That sucks, but I'll make do without it.
I was following the guides posted above. The root guide said to flash a Magisk patched OS and then there was a guide for installing TWRP. I never had this many issues or this much confusion with my 1st gen Tab S; maybe I just haven't kept as close of an eye on these things since I've been without a tablet for awhile before getting the Tab S6.
Anyway, for clarification, all I need to do is flash TWRP and then flash magisk from within TWRP? Or, just install the magisk apk after booting into Android?
Click to expand...
Click to collapse
My bad for some reason I just read that as Samsung Pay. But yeah Samsung Pass also doesn't work with root, I'm not sure if that is permanent though as I've never used Samsung Pass, but did come across this thread https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977 it is possible to get some components of Knox to function again, (I have a working Secure Folder) so might be worth taking a look.
As for you question...
You should give this thread a good read... https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587
Basic steps are... Unlock the bootloader and then boot into system and ensure it's unlocked in settings. You may need to connect to the web, I can't remember tbh
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
bartleby999 said:
First you need to install TWRP, once that is done you need to reboot but YOU HAVE TO boot directly back into TWRP. You cannot boot into system, or TWRP will be overwritten by stock recovery and you'll need to start over again. Once TWRP is installed, boot into TWRP and format data then reboot recovery, flash Kernel then flash encryption disabler then unmount the system and flash Magisk 20.4 - Finally reboot to system.
I'd seriously and strongly suggest reading that TWRP thread to ensure things go smoothly.
Click to expand...
Click to collapse
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
noxarcana said:
I'll give those threads a thorough reading over tonight and tomorrow night while at work and then see if I can get this all sorted out Monday when I'm off. I remember Pass still working with root on the original Tab S so I'm hoping it hasn't changed.
Thanks for jumping in to try and help me with this. I'll update within a few days instead of months like my last update. ?
Click to expand...
Click to collapse
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
bartleby999 said:
It has definitely changed. Pass doesn't work on my Tab S6 and I'm rooted, I guess Knox is now integrated with alot of Samsung apps now. Not sure if it's possible or not to get it working again though, I've never bothered to research it as I don't need it for anything - But as I said, I got Secure Folder working again, so there's some hope for Pass I guess - That first thread I linked looked promising, but I only skimmed it, because frankly I'm not interested.
If you need anymore help, report back -I'll try my best. Also, the TWRP thread I linked is full of helpful people. :good:
Click to expand...
Click to collapse
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
noxarcana said:
Perhaps I'm just not meant to have root with this device. Flashing that kernel causes Wifi not to work, but it does boot. Not flashing the kernel also booted, but I couldn't install Magisk Manager. Other than the bootloader still being unlocked, I'm back on stock firmware.
Click to expand...
Click to collapse
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
bartleby999 said:
What firmware are you running?
I remember seeing something about one of the newer Kernels effecting WIFI on Android 10. Assume you're running that?
If that's the case, give the TWRP thread a browse - You maybe able to find an older version of the Kernel that'll work - As far as I'm aware, an older Kernel than what you currently installed will work, but a newer version than currently installed will possibly cause bootloop.
I can't help much with Android 10 specific stuff as I'm still running Android 9 because it's stable.
Click to expand...
Click to collapse
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
noxarcana said:
I am definitely on the latest Android 10 update so I'll see if I can find an earlier version that will work. I'll see what I can find out on the TWRP thread.
Click to expand...
Click to collapse
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
bartleby999 said:
If you can't find an older Kernel (I'm not sure there is one for Android 10), it may be the case that you'll need to wait for the Kernel to be updated.
Click to expand...
Click to collapse
Yea, it looks like Samsung made some "wifi improvements" in OneUI 2.5 and that's causing some kernel issues preventing wifi from working. I think I could find a kernel fairly easily, but I think I'm just going to wait for a kernel update. If it never comes, I'll find an older kernel. Thanks for the help!
Build number
DE2117_11_C.17
Hardware version
DE2117_11
I keep seeing T-Mobile version, INTL version, DE18 and all that. I'm so confused, I just need root.
I believe that's the international version since mine is DE2117. Not sure because of the "_11" at the end of yours. Maybe that signifies you updated it, in which case you will probably have to downgrade it.
Rooting this phone is a headache btw. I'm not even sure if I should be providing instructions because I bricked mine multiple times while attempting and had to keep restoring with MSMtools, and now I'm not even sure I can update it without losing root. I don't even think I did anything differently when it finally worked, it's just luck.
Anyway, first step is to download the international version of the MSMtools and payload dumper. look up how to dump the boot image with payload dumper from the MSMtools. And make sure you don't attempt to do anything to the device before unlocking your bootloader (and you'll have to unlock it again everytime you restore with MSMtool).
From there you should be able to follow guides.
@swee08315
I downloaded the latest update available from https://www.oneplus.com/support/softwareupgrade/details?code=PM1630638351161
But the phone is updated to July. Hmmmm.....
I've extracted the boot.img from there. Patched it with magisk. I'm about to fastboot flash it..... Wish me luck, I'm going in.
Unless there's a way to extract the boot.img that's currently installed. I think I'll poke around and look for that rather than simply hoping this is the right one.
jova33 said:
I downloaded the latest update available from https://www.oneplus.com/support/softwareupgrade/details?code=PM1630638351161
But the phone is updated to July. Hmmmm.....
I've extracted the boot.img from there. Patched it with magisk. I'm about to fastboot flash it..... Wish me luck, I'm going in.
Unless there's a way to extract the boot.img that's currently installed. I think I'll poke around and look for that rather than simply hoping this is the right one.
Click to expand...
Click to collapse
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
A1.1 will get the boot.img your device currently has.
Edit: if you flashed the boot.img from the official site, then your device is most likely bricked. I'll fetch my boot.img and link it here (won't be magisk patched).
justauserthatusesaphone said:
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
A1.1 will get the boot.img your device currently has.
Edit: if you flashed the boot.img from the official site, then your device is most likely bricked. I'll fetch my boot.img and link it here (won't be magisk patched).
Click to expand...
Click to collapse
yeah, I bricked it
Nothing a few beers won't cure.
Once I unbrick, I will do A1.1 though.
jova33 said:
yeah, I bricked it
Nothing a few beers won't cure.
Once I unbrick, I will do A1.1 though.
Click to expand...
Click to collapse
here's the boot.img (not rooted)
I hope you haven't wiped yet
boot.img
drive.google.com
justauserthatusesaphone said:
here's the boot.img (not rooted)
I hope you haven't wiped yet
boot.img
drive.google.com
Click to expand...
Click to collapse
nah, I don't wipe until I get into the shower.
But yeah, I completely reset everything with MSM tools. In the process of letting all the updates go through. Thanks for the boot img though, It'll save me the trouble of having to pull it using the msm tools.
Edit: I forgot to do the vbmeta stuff after flashing the magisk patched. How do I fix? Can I borrow your vbmeta, @justauserthatusesaphone ?
justauserthatusesaphone said:
here's the boot.img (not rooted)
I hope you haven't wiped yet
boot.img
drive.google.com
Click to expand...
Click to collapse
So I can update my oneplus and then patch and use this bootimg to regain root? Or will trying to update my rooted device brick it and I'd have to wipe everything and start from scratch anyway?
jova33 said:
nah, I don't wipe until I get into the shower.
But yeah, I completely reset everything with MSM tools. In the process of letting all the updates go through. Thanks for the boot img though, It'll save me the trouble of having to pull it using the msm tools.
Edit: I forgot to do the vbmeta stuff after flashing the magisk patched. How do I fix? Can I borrow your vbmeta, @justauserthatusesaphone ?
Click to expand...
Click to collapse
I'll get it when I'm on my PC
the c17 one, correct?
justauserthatusesaphone said:
I'll get it when I'm on my PC
the c17 one, correct?
Click to expand...
Click to collapse
Don't worry about it. I redid the MSM tool since the phone wasn't even setup yet, no big loss.
swee08315 said:
So I can update my oneplus and then patch and use this bootimg to regain root? Or will trying to update my rooted device brick it and I'd have to wipe everything and start from scratch anyway?
Click to expand...
Click to collapse
So, I don't know how this phone handles updates. I've had previous phones that if it was rooted, the OTA would fail to install, and others that the OTA would install and replace the boot.img, so root would be removed.
The first case, I would have to unroot, restore the stock boot.img, and then it could take the OTA update.
The other case I would have to block OTAs until I could get the boot.img for it, so that I could root the update.
The guide posted here https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/
part B explains how to update and maintain root. Seems like it's the first case. Restore stock boot.img.
jova33 said:
So, I don't know how this phone handles updates. I've had previous phones that if it was rooted, the OTA would fail to install, and others that the OTA would install and replace the boot.img, so root would be removed.
The first case, I would have to unroot, restore the stock boot.img, and then it could take the OTA update.
The other case I would have to block OTAs until I could get the boot.img for it, so that I could root the update.
The guide posted here https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/
part B explains how to update and maintain root. Seems like it's the first case. Restore stock boot.img
Click to expand...
Click to collapse
You could turn off automatic system updates so it doesn't reboot automatically and then you install the update and when it asks you to restart, go into magisk and click install and install to inactive slot then you go back to the system update page and click restart. I don't know whether Google's ota system makes it easier or not.
Late reply but I can confirm that all updates fail on this device and you would have to unroot to get the update, and then root again. Very annoying that it's constantly notifying me that an update is available or that it tried to update last night and failed
swee08315 said:
Late reply but I can confirm that all updates fail on this device and you would have to unroot to get the update, and then root again. Very annoying that it's constantly notifying me that an update is available or that it tried to update last night and failed
Click to expand...
Click to collapse
I never had that issue but if you do, press uninstall and restore images (DON'T REBOOT), then after installing the updates (DON'T REBOOT) press install and install to inactive slot. Press the reboot button and you're done.