Hi everyone;
I have a rooted and unlocked Nokia 8 TA-1004 (Security Patch 1 July 2018; 00WW_4_88B_SP02).
I followed the guides on this very forum on how to root and unlock (first) and then how to put TWRP (after I already had rooted and unlocked).
The problem I'm having is exactly what the title says:
I have the possibility to update to SP of August but I just can't; it gives me an installation error as soon as it finishes downloading.
I already tried to Factory Reset the phone and when that didn't solve anything I tried (and succeded) putting TWRP hoping it would solve (hope never dies) the problem but it didn't.
I'm at a loss here, can anyone help me?
Xayar said:
Hi everyone;
I have a rooted and unlocked Nokia 8 TA-1004 (Security Patch 1 July 2018; 00WW_4_88B_SP02).
I followed the guides on this very forum on how to root and unlock (first) and then how to put TWRP (after I already had rooted and unlocked).
The problem I'm having is exactly what the title says:
I have the possibility to update to SP of August but I just can't; it gives me an installation error as soon as it finishes downloading.
I already tried to Factory Reset the phone and when that didn't solve anything I tried (and succeded) putting TWRP hoping it would solve (hope never dies) the problem but it didn't.
I'm at a loss here, can anyone help me?
Click to expand...
Click to collapse
This "problem" happens because the Android OS only updates the other partition set (A/B) when it's all stock and to achieve root thru Magisk we must patch the bootloader, making it unsuitable for the process.
You need to revert back to the official bootloader and then you'll be able to get it updated. After that just apply the patched bootloader to regain root/twrp and unfortunately that's what you gotta do on every update.
So uhhh how and where do I get the stock bootloader?
If I flash the magisk uninstaller I should get the stock boot image back because Magisk backs it up but I don't thing that alone does the trick.
What else do I need and where do I get it?
That's not an issue related to bootloader but rather to the patched boot.img existing on both paritions A/B. You'll have to restore Magisk backup image or reflash official June OTA and start updating the system without Magisk.
So if I just flash the Magisk uninstaller I will regain the ability to update?
Xayar said:
So if I just flash the Magisk uninstaller I will regain the ability to update?
Click to expand...
Click to collapse
Either you'll have ability to update or soft brick 50/50 odds
I don't like those odds ?
I tried restoring the boot image using Magisk's tool (since the version 17 there's the option of restoring the boot.img without actually uninstalling everything but it says it doesn't have any boot.img backed up...
I guess I'm back to square one and need to downgrade to the June update... Can I just flash it?
Related
Hi,
Can someone concisely give the most up to date instructions on how to root the P20 Pro
Confused because some people talk about debranding first? Is this necessary if you, like me, just have a generic non-network branded phone?
Also.. Does rooting require twrp?
A bit unclear on if I should use the offical or unofficial twrp methods.
And if so does twrp prevent OTA updates? I was lead to believe that any OTA updates would simply wipe any root and you just have to go through the steps again, but would twrp prevent an OTA update in the first place?
What are the best instructions to root the P20 Pro to keep the OTA updates going (even if you need to reroot after each update).
Thanks heaps in getting through the confusion!
Here you have manual to root in simple 4 steps. You need adb and fastboot on your computer, bootloader unlock code and Magisk from link in post
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
Does any of the steps,
1/ unlocking the bootloader
2/ debranding
3/ installing TWRP
3/ rooting
Wipe the device?.. I'm assuming yes?
Also. What's the point of debranding?..
I think I'm on a generic P20 Pro that wasn't bought from a carrier - so is that step necessary for me.
Thanks heaps again for the advice - coming over from the Samsung world and maybe I'm so used to the rooting methods there
Also do any of those steps prevent OTA updates?
Or is there somehow to still use OTA updates but simply need to reapply root on every occasion there is ah update?
dgoncalves81 said:
Also do any of those steps prevent OTA updates?
Or is there somehow to still use OTA updates but simply need to reapply root on every occasion there is ah update?
Click to expand...
Click to collapse
Unlocking the bootloader will wipe your device. The other steps won't.
You need to have TWRP installed in order to be able to flash Magisk (for Root), and no you don't have to rebrand if you don't want to. You'll still be able to receive and download OTAs but if TWRP remains installed on your phone it won't be able to install unless you change back to the stock recovery. However there is methods to update with TWRP and you'll be able to get and install updates quicker than waiting for them to be pushed to you phone. That's the main reason people rebrand because generic European models are getting updates the fastest.
What's your device model and current firmware version from 'About Phone' in settings?
..
danifilth4king said:
Unlocking the bootloader will wipe your device. The other steps won't.
You need to have TWRP installed in order to be able to flash Magisk (for Root), and no you don't have to rebrand if you don't want to. You'll still be able to receive and download OTAs but if TWRP remains installed on your phone it won't be able to install unless you change back to the stock recovery. However there is methods to update with TWRP and you'll be able to get and install updates quicker than waiting for them to be pushed to you phone. That's the main reason people rebrand because generic European models are getting updates the fastest.
What's your device model and current firmware version from 'About Phone' in settings?
Click to expand...
Click to collapse
Thanks heaps for the advice - makes sense now!
I'm using the model CLT-L29 on C636 which I think is the Asia Pacific model.. And incidentally just received a OTA upgrade to the 128 firmware
.. So in order to receive OTA updates you simply have to change back to the stock recovery after using TWRP to install magisk and root?
But I imagine every time the OTA update occurs it wipes root?.. Which would mean reinstalling TWRP to regain root and doing the whole process again every time?
dgoncalves81 said:
Thanks heaps for the advice - makes sense now!
I'm using the model CLT-L29 on C636 which I think is the Asia Pacific model.. And incidentally just received a OTA upgrade to the 128 firmware
.. So in order to receive OTA updates you simply have to change back to the stock recovery after using TWRP to install magisk and root?
But I imagine every time the OTA update occurs it wipes root?.. Which would mean reinstalling TWRP to regain root and doing the whole process again every time?
Click to expand...
Click to collapse
Yep you got it in one lol
The other option so that you don't have to flash TWRP then back to stock recovery each time is when you receive an OTA is download the same firmware (Full-OTA version) from Firmware Finder - you would just need the update.zip - then using Huawei update extractor you can extract the ramdisk.img Then copy the ramdisk.img to your phone, use Magisk manager to patch it then copy it back to your PC and flash it via fastboot. But I think this is more work than flashing between TWRP & stock recoveries haha
Hi everyone! I recently bought a LG G6 H872, which still has 10e installed. After crawling the forums for a bit, here's the sequence of things I wanted to do to it:
1.) Update to 8.0 Oreo via OTA.
2.) Unlock bootloader
3.) Root and TWRP using this: https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518
4.) Magisk
Is the latest Oreo update the 20a version that is mentioned in the thread or should I manually update it to something older. I saw that there was anti-rollback so I don't want to update too far. Also, if there is ever another OTA, how does one update the rooted phone?
Edit: I wrote up some steps if it helps you on this post: https://forum.xda-developers.com/showpost.php?p=77513501&postcount=4
I do not believe there is currently a way to root the T-Mobile versions.
patruns said:
I do not believe there is currently a way to root the T-Mobile versions.
Click to expand...
Click to collapse
That is not correct, see: https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518
For future people who come across this thread, here are the steps I took to root this phone:
1.) Factory reset and then update device via OTA incrementally until 20a (which is Android Oreo 8.0)
2.) unlock bootloader: https://www.youtube.com/watch?v=EpaW0-8-QKY
3.) root device: https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518
Note: there is a video tutorial here: https://www.youtube.com/watch?v=-z4CWLikPcI&t=821s. The first steps of flashing the laf partition are very useful to watch before attempting
4.) Factory reset in TWRP
5.) Reset after encryption error, then wipe with TWRP. May give mount error.
6.) Boot into Android Oreo. Device is not yet rooted at this point.
6.) Flash MAGISK via TWRP (SD card or ADB push) ]. Ignore the mount error. Reboot.
7.) Device is rooted! :good:
That's interesting
Without getting into an issue those steps look slightly different in order than the original process.
Or I'm a dumbass and somehow got it out of order. Seems ok now though.
Hello there!
I want to ask if it's the same to do the steps with 20e ?
Curious as well if this works with the latest update.
thendless said:
Curious as well if this works with the latest update.
Click to expand...
Click to collapse
This is an already rooted version of the latest update. I've downloaded but haven't flashed it yet, but the op is good and I've never had an issue with his work.
https://r.tapatalk.com/shareLink?ur...share_tid=3875515&share_fid=3793&share_type=t
Sent from my LG-H872 using Tapatalk
I succeeded in completing the process.
Permanent unlock from Tom via app.
Unlocked bootloader.
Twrp installed to recovery, can boot to recovery via low volume/power button combo.
Magisk installed.
20a working nicely.
I'm getting requests from Tmo to update from 20a to 20d. Is this recommended? Will twrp, root, unlock, etc. be lost?
I am glad to see that the bootloader gets unlocked easily. @alliance1975 how did you go from Unlocked bootloader step to Twrp installed step? That is the big one I think.
There is a good TWRP available, but we can't install it because the phone lacks fastboot commands. Is there a way to install TWRP? Or is it really that the only method is the rather risky runningnak3d method?
interestor said:
I am glad to see that the bootloader gets unlocked easily. @alliance1975 how did you go from Unlocked bootloader step to Twrp installed step? That is the big one I think.
There is a good TWRP available, but we can't install it because the phone lacks fastboot commands. Is there a way to install TWRP? Or is it really that the only method is the rather risky runningnak3d method?
Click to expand...
Click to collapse
I used the procedure summarized in step 3. I agree it is risky, well, the riskiest root & twrp I've ever tried. I neglected to say I only read instructions, the dev who actually came up with the plan deserves all the credit.
When I try to oem unlock nothing happens. What can I do? I have followed all other instructions.
Follow steps from this https://forum.xda-developers.com/tmobile-g6/how-to/unlock-bootloader-tmo-t3578099
Yeah I got my bootloader unlocked
alliance1975 said:
I succeeded in completing the process.
Permanent unlock from Tom via app.
Unlocked bootloader.
Twrp installed to recovery, can boot to recovery via low volume/power button combo.
Magisk installed.
20a working nicely.
I'm getting requests from Tmo to update from 20a to 20d. Is this recommended? Will twrp, root, unlock, etc. be lost?
Click to expand...
Click to collapse
Any info on this? Will updating from 20a mess up the phone (root, etc...)?
I’m sure this is very simple and I’m just not getting it…
got new moto x4 XT1900-1 from b&h
unlocked boot loader with motorola code
using windows fast boot was able to follow the "How to : Moto X4 Root & TWRP Recovery" bu Munchy on youtube to install twrp using payton 3.2.1-1
then installed Magish 17.1 which seems to be what actually rooted the phone as per confirmation by Root Check app shows 8.1.0
now I am getting constant ota notices of a security update OPWS28.3.2 and I download it and it fails which is apparently normal for a rooted phone.
Can I disable the root and update???…can this be done by turning off magic…or uninstalling it…or is this done by tarp?
I believe I should back up the recover image using twrp…then what?…find and boot to a stock image?
???
any info appreciated
tia
PS…I just tried the "topjohnwu Update OTA tutorial for v17" method in tips and tricks on here and it also said update failed???
jojojones said:
I’m sure this is very simple and I’m just not getting it…
got new moto x4 XT1900-1 from b&h
unlocked boot loader with motorola code
using windows fast boot was able to follow the "How to : Moto X4 Root & TWRP Recovery" bu Munchy on youtube to install twrp using payton 3.2.1-1
then installed Magish 17.1 which seems to be what actually rooted the phone as per confirmation by Root Check app shows 8.1.0
now I am getting constant ota notices of a security update OPWS28.3.2 and I download it and it fails which is apparently normal for a rooted phone.
Can I disable the root and update???…can this be done by turning off magic…or uninstalling it…or is this done by tarp?
I believe I should back up the recover image using twrp…then what?…find and boot to a stock image?
???
any info appreciated
tia
PS…I just tried the "topjohnwu Update OTA tutorial for v17" method in tips and tricks on here and it also said update failed???
Click to expand...
Click to collapse
What I did (might be an easier way but this was fast and easy):
1) Uninstall/remove Magisk.
2) Re-flash firmware over current system but don't do 'fastboot erase userdata'
3) Boot into your system and take all the OTA's
4) Re-install Magisk via TWRP
Took about 10 minutes. Longest part was waiting for OTA's to install.
Sorry...I'm new to all this. How do I reflash firmware?....use twrp app that is installed?
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
jhedfors said:
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
Click to expand...
Click to collapse
Did not work for me. Nothing has so far.
jojojones said:
Sorry...I'm new to all this. How do I reflash firmware?....use twrp app that is installed?
Click to expand...
Click to collapse
Use this guide:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
Remove command "fastboot erase userdata" from script flash-all.bat/flash-all.sh.
jhedfors said:
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
Click to expand...
Click to collapse
I've tried this, and it didn't work. Ended up having to boot into TWRP, uninstall Magisk, and then reboot. Haven't bothered trying to update since I attempted that.
jhedfors said:
Magisk 17 supposedly has the ability to do this.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you try this, please let us know. I have been waiting for an update to test this function.
Click to expand...
Click to collapse
I spent a little while trying to apply OTA with magisk. The only way I was able to do it was to flash the stock firmware like everyone says. I could only find 8.0, so I had to flash the firmware, install 3 OTA's, then reinstall twrp/magisk.
The only thing I didn't try was installing magisk without twrp, which I believe is supported but I'm not sure. I think that might be the secret sauce to fixing it, but I'm not sure, and I haven't wanted to reflash and go through the whole process again.
tjololo12 said:
I spent a little while trying to apply OTA with magisk. The only way I was able to do it was to flash the stock firmware like everyone says. I could only find 8.0, so I had to flash the firmware, install 3 OTA's, then reinstall twrp/magisk.
The only thing I didn't try was installing magisk without twrp, which I believe is supported but I'm not sure. I think that might be the secret sauce to fixing it, but I'm not sure, and I haven't wanted to reflash and go through the whole process again.
Click to expand...
Click to collapse
If you have the xt1900-1 retus you can flash the android one firmware which is 8.1 (currently on the Aug 2018 security patch).
ptn107 said:
If you have the xt1900-1 retus you can flash the android one firmware which is 8.1 (currently on the Aug 2018 security patch).
Click to expand...
Click to collapse
I have the android one variant. Do you know where I can get the firmware? There's a new security patch and I'd like to try installing it with stock bootloader + magisk (installed from a temporary twrp boot) to see if that works with the OTA. I'd like to get the method working since android 9 is coming at some point.
tjololo12 said:
I have the android one variant. Do you know where I can get the firmware? There's a new security patch and I'd like to try installing it with stock bootloader + magisk (installed from a temporary twrp boot) to see if that works with the OTA. I'd like to get the method working since android 9 is coming at some point.
Click to expand...
Click to collapse
September 2018 OTA for Android One (Oreo 8.1):
Blur_Version.28.251.17.payton_fi.google_fi.en.US
Click to "Download" and save as ZIP file.
Only way how to apply OTA update with magisk rooted X4 is flash ROM using fastboot (august 2018 ROM is on AFH), remove command 'fastboot erase userdata' from script 'flash-all.bat', install september OTA from adb sideload/SD card and root again.
Comby_sk said:
September 2018 OTA for Android One (Oreo 8.1):
Blur_Version.28.251.17.payton_fi.google_fi.en.US
Click to "Download" and save as ZIP file.
Only way how to apply OTA update with magisk rooted X4 is flash ROM using fastboot (august 2018 ROM is on AFH), remove command 'fastboot erase userdata' from script 'flash-all.bat', install september OTA from adb sideload/SD card and root again.
Click to expand...
Click to collapse
Thanks, the rom is exactly what I was looking for, I just wasn't sure which one to use. I'd hate to install the wrong rom and mess something up.
EDIT: I did get a chance to try it and you're correct, there is no way to install an OTA to this device without fully reflashing the stock rom, taking the OTA, then installing Magisk. I tried the following steps:
1. Flash ROM given from androidfilehost
2. Reboot, wait for OTA notification
3. Boot to bootloader
4. use fastboot to temporarily boot twrp
5. flash magisk 17.1 zipfile
6. reboot to system, verify that magisk/root is installed
7. Uninstall magisk using magisk manager "Restore Images" as given in the tips.md file
8. Take OTA
the OTA still failed, so even though TWRP wasn't installed and it was still the stock recovery, I was unable to install the OTA. Shame, it'd be nice if we could get this to work, but oh well.
I've just installed Magisk on my device. I tried to update my phone via OTA with this tutorial https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation but the update fails.
I didn't flash the recovery image
I solved my problem.
I did few modifications on the system partition with Adaway, so that's why the OTA didn't work. So I reflash the firmware, and I followed the steps for OTA updates, and that works now!
I have that problem again : I tried to update from 7 to 13 and failed all the time. Before that, I installed the November 1st patch and lost the root. So I downgraded to 7 to get root again.
At Step 3, the update stops at 56% before the update fails.
FoxyLove33 said:
I've just installed Magisk on my device. I tried to update my phone via OTA with this tutorial https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation but the update fails.
I didn't flash the recovery image
Click to expand...
Click to collapse
Hey man, can you link a tutorial to update the z3 play with security patches? Mine has bootloader unlocked and no other modifications. All stock. Updated upto july patch. Can you link a tutorial? and link for the patches (RETUS)? Thx.
e4noob said:
Hey man, can you link a tutorial to update the z3 play with security patches? Mine has bootloader unlocked and no other modifications. All stock. Updated upto july patch. Can you link a tutorial? and link for the patches (RETUS)? Thx.
Click to expand...
Click to collapse
First of all, I'm not a man. The first link is how to install magisk, and the second one is how to update via OTA
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
FoxyLove33 said:
First of all, I'm not a man. The first link is how to install magisk, and the second one is how to update via OTA
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Click to expand...
Click to collapse
Thanks. I tried the instructions on the ota link, but am still getting Software Update unsuccessful?
FoxyLove33 said:
First of all, I'm not a man. The first link is how to install magisk, and the second one is how to update via OTA
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Click to expand...
Click to collapse
Hi,
I'm having a similar issue with the OTA installation after getting magisk root using the Boot Image Patching method. The tutorial shows several different methods, but so far I haven't had luck with any of them. I tried the one for "Devices with A/B Partitions" and got as far as flashing the original boot image back but the OTA still wouldn't install. The flashfire method wouldn't work because flashfire says it isn't compatible with "20.1:MAGISKSU". I didn't touch the recovery partition and I am using the same file I used to create the patched magisk boot image (without the alteration) to try to get back to stock boot image. I'm not sure what else to do aside from using LMSA to reflash stock. My concern with that (aside from having to reconfigure everything) is that I don't have the latest boot.img from the 1-9 firmware to patch it in Magisk and I don't yet know if I can use the 1-6 firmware modified boot.img file.
Is there any guide on how to update a (magisk) rooted pixel 4?
My case:
I unlocked my bootloader when I received the phone, as usual
I used magisk manager to modify the boot.img from my fw-image. I flashed it with fastboot and so had root.
Later, I used a custom kernel.
As far as I know, I did not do any changes except boot.img
When the Update hit me early December, I was not able to update. "Update failed" it told me. I managed to flash the original boot.img a short while after. I still could not update my pixel.
Now I do a factory reset while flashing the original fw image again. (I flashed the wrong one and got face-unlock to not work at all. I hope I am downloading the right one right now and can use face unlock again)
mad-murdock said:
Is there any guide on how to update a (magisk) rooted pixel 4?
My case:
I unlocked my bootloader when I received the phone, as usual
I used magisk manager to modify the boot.img from my fw-image. I flashed it with fastboot and so had root.
Later, I used a custom kernel.
As far as I know, I did not do any changes except boot.img
When the Update hit me early December, I was not able to update. "Update failed" it told me. I managed to flash the original boot.img a short while after. I still could not update my pixel.
Now I do a factory reset while flashing the original fw image again. (I flashed the wrong one and got face-unlock to not work at all. I hope I am downloading the right one right now and can use face unlock again)
Click to expand...
Click to collapse
Check the Guides sections, you'll find one there.
mad-murdock said:
Is there any guide on how to update a (magisk) rooted pixel 4?
My case:
I unlocked my bootloader when I received the phone, as usual
I used magisk manager to modify the boot.img from my fw-image. I flashed it with fastboot and so had root.
Later, I used a custom kernel.
As far as I know, I did not do any changes except boot.img
When the Update hit me early December, I was not able to update. "Update failed" it told me. I managed to flash the original boot.img a short while after. I still could not update my pixel.
Now I do a factory reset while flashing the original fw image again. (I flashed the wrong one and got face-unlock to not work at all. I hope I am downloading the right one right now and can use face unlock again)
Click to expand...
Click to collapse
Here ya go :good:
https://forum.xda-developers.com/pi...-4-xl-android-10-q-root-t3996969/post80774791