Related
I'm so confused with this phone. Google sent me a 128gb Pixel XL which I activated on my Sprint account. I'm fairly comfortable with rooting, flashing, TWRP, SuperSU, etc., however for the life of me I cannot get TWRP to stick.
Background...
Phone came to me straight from Google, and updated to 8.0 immediately (this was in August). Since, the phone doesn't appear to have been updated as I was still on 8.0 from August I believe
Here's what I did...
Unlocked the phone, using TWRP image, boot to it via fastboot, flash the installer TWRP zip, and then issues happen.
On 3.2.1.0-0 it reboots to system (even if I go back into TWRP's main setting and Reboot Recovery). If I use 3.2.0.0-0, it gives me an ERROR 1 code. I've tried using systemless root method (with the modified TWRP img, Aroma Installer for SU, etc.). I've tried using the 2 most recent TWRP images from their website. I initially started with this guide ([GUIDE] Pixel XL Android 8(OREO) Unlock/Install Stock Images + Kernels/Recovery +). I then tried this method using Systemless root ([Guide] How to systemlessly root your Pixel XL on Android 8.0 (SuperSU)).
I even tried flashing the OTA manually, which caused other issues, mainly bootloops. I finally got the most recent 8.0 OTA to work after multiple errors (which appear to be caused by outdated platform_tools). When trying to flash the OTA, only OPR1 would flash, OPR3 would always just hang or throw errors (sorry, no changelog, which I know is not helpful). Am I not correct that OPR3 is what is needed for a Sprint (US carriers) based phone? Regardless, everything is up, and running now in 8.0, however I can't take the OTA (it fails when trying to download), and I still can't get TWRP to stick.
Is there anything obvious I'm missing? I can boot to TWRP, but can't flash it, regardless of what I do. I've searched and most issues I've found in getting TWRP to stick either has to do with flashing the boot.img from an OTA or using 3.2.1.0 instead of 3.2.2.0. Funny thing, I don't see the 3.2.2.0 img file, just the flashable zip. Someone please help me, even if it is to tell me I'm in over my head and should stick to a stock rom.
I think you should simplify your life.
Each month grab the full image. Edit the flash-all bat file and remove the -w you will see near the end. Reboot the phone into fastboot mode and run the flash-all bat file.
That will update your phone, but leave settings a data in tact. Again, remove the -w so you don't wipe user data.
Then boot to TWRP and root it. Skip installing TWRP, too many hassles on this phone.
FYI, on the January update SuperSU no longer works, you will need to root with Magisk.
I do it each month this way. It takes 15 minutes and I have zero problems.
To make your life even more simplicit, you can use Skipsoft Toolkit. Its automated and does all the heavy lifting for you. I have TWRP install without any issue.
TonikJDK said:
Each month grab the full image. Edit the flash-all bat file and remove the -w you will see near the end. Reboot the phone into fastboot mode and run the flash-all bat file..
Click to expand...
Click to collapse
So you're saying grab the Full OTA? Should I start with the last month before the version I'm on? Currently on OPR1.170623.023 (Nov 2017). Does it make a difference that I'm a Sprint service, as in using OPR1 vs OPR3?
TonikJDK said:
Then boot to TWRP and root it. Skip installing TWRP, too many hassles on this phone.
Click to expand...
Click to collapse
So fastboot into TWRP img everytime I want to flash a custom ROM?
TonikJDK said:
FYI, on the January update SuperSU no longer works, you will need to root with Magisk.
Click to expand...
Click to collapse
January update of SuperSU or the OTA? I was under the impression Magisk couldn't be flashed on stock kernels, I'm guessing this changed?
Chance Ill said:
To make your life even more simplicit, you can use Skipsoft Toolkit. Its automated and does all the heavy lifting for you. I have TWRP install without any issue.
Click to expand...
Click to collapse
I will try this. Between yours and Tonik's advice, one of these is bound to work, right?
vestaviajag said:
So you're saying grab the Full OTA? Should I start with the last month before the version I'm on? Currently on OPR1.170623.023 (Nov 2017). Does it make a difference that I'm a Sprint service, as in using OPR1 vs OPR3?
Click to expand...
Click to collapse
So fastboot into TWRP img everytime I want to flash a custom ROM?
January update of SuperSU or the OTA? I was under the impression Magisk couldn't be flashed on stock kernels, I'm guessing this changed?
I will try this. Between yours and Tonik's advice, one of these is bound to work, right?[/QUOTE]
2 different methods, same result. Make sure to thoroughly follow instructions with whatever method you try and you'll be fine.
vestaviajag said:
So you're saying grab the Full OTA? Should I start with the last month before the version I'm on? Currently on OPR1.170623.023 (Nov 2017). Does it make a difference that I'm a Sprint service, as in using OPR1 vs OPR3?
Click to expand...
Click to collapse
So fastboot into TWRP img everytime I want to flash a custom ROM?
January update of SuperSU or the OTA? I was under the impression Magisk couldn't be flashed on stock kernels, I'm guessing this changed?
I will try this. Between yours and Tonik's advice, one of these is bound to work, right?[/QUOTE]
I use the full image, after taking out the -w from this link. Since you are flashing the whole image you can just get the latest.
https://developers.google.com/android/images
I can't help you on ROMs, I don't do them. Are there any 8 ROMs for this phone?
But I would never flash anything on this phone without being near a computer. So I skip flashing TWRP. Just as easy to fastboot it.
SU is not being updated any more. So I mean the Google January update breaks SU. I have been using Magisk on stock for several months now. If you want to stick with SU you will need to flash December Google.
TonikJDK said:
So fastboot into TWRP img everytime I want to flash a custom ROM?
January update of SuperSU or the OTA? I was under the impression Magisk couldn't be flashed on stock kernels, I'm guessing this changed?
I will try this. Between yours and Tonik's advice, one of these is bound to work, right?
Click to expand...
Click to collapse
I use the full image, after taking out the -w from this link. Since you are flashing the whole image you can just get the latest.
https://developers.google.com/android/images
I can't help you on ROMs, I don't do them. Are there any 8 ROMs for this phone?
But I would never flash anything on this phone without being near a computer. So I skip flashing TWRP. Just as easy to fastboot it.
SU is not being updated any more. So I mean the Google January update breaks SU. I have been using Magisk on stock for several months now. If you want to stick with SU you will need to flash December Google.[/QUOTE]
Hmmmm.......SU not being updated anymore? I've been using magisk for awhile now so I haven't been keeping up. What's your source?
Chance Ill said:
I
Hmmmm.......SU not being updated anymore? I've been using magisk for awhile now so I haven't been keeping up. What's your source?
Click to expand...
Click to collapse
SU beta thread, Chainfire announced he is no longer involved at all. He stopped by a few days ago, got rather upset at some of the posts. We have not heard a word from the new owners in two years.....
TonikJDK said:
SU beta thread, Chainfire announced he is no longer involved at all. He stopped by a few days ago, got rather upset at some of the posts. We have not heard a word from the new owners in two years.....
Click to expand...
Click to collapse
Oh ok. I do remember coming across Chainfire's announcement awhile ago but was unaware that the new owners hadn't been active with the community. That's disappointing to say the least.
Chance Ill said:
To make your life even more simplicit, you can use Skipsoft Toolkit. Its automated and does all the heavy lifting for you. I have TWRP install without any issue.
Click to expand...
Click to collapse
Tried this, for some reason wouldn't work. Tried the TWRP and it wouldn't due to OpenSourceScript or something. Then tried rooting and installing busybox, it wouldn't do this either. It attempted to flash it to sd card, another place, and finally in the right storage for this device, and it wouldn't for some error. No specifics on the error were given.
TonikJDK said:
I use the full image, after taking out the -w from this link. Since you are flashing the whole image you can just get the latest.
Click to expand...
Click to collapse
Tried this next, removed the -w, and used flash-all in fastboot. This worked, however after I upgraded to 8.1 OPM1, I left it alone. Will try again tonight to root, and attempt flashing magisk for the first time.
Thanks for all the advice!
Anyone has the latest(released Feb 16th) oreo OTA full stock firmware from T-Mobile?
I tried pulling it from a logcat. Was going to fastboot flash it since I can't install it while rooted. Every url I found in the logcat gave me a 405 error though.
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
droidgreg said:
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
Click to expand...
Click to collapse
Pulling the log through ADB will yield the OTA download link. That's how @joemossjr and I grabbed the Oreo update from nougat for TMO and Sprint.
Uzephi said:
Pulling the log through ADB will yield the OTA download link. That's how @joemossjr and I grabbed the Oreo update from nougat for TMO and Sprint.
Click to expand...
Click to collapse
Step by step instructions would be appreciated.
droidgreg said:
Step by step instructions would be appreciated.
Click to expand...
Click to collapse
It's hard to explain. You have to capture the moment the phone grabs the OTA file from Motorola's update website.
Enable developer options
Enable ADB
Plug phone up to a PC that has updated ADB binaries
Open terminal/command prompt
Adb shell
Logcat
After you do that your terminal of choice will start spitting out the log.
Run the system updater.
Download the OTA. At that moment, one of the logs should give you a VERY long URL. That's the download link you're looking for.
Copy and paste into your browser. You should be auto downloading it.
Done
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
joesee said:
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
Click to expand...
Click to collapse
I used titanium backup to freeze the update service as it's named in the notification.
charlatan01 said:
I used titanium backup to freeze the update service as it's named in the notification.
Click to expand...
Click to collapse
Thank you. I looked under U for update. I should have searched... It's actually called Motorola Update Services.
joesee said:
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
Click to expand...
Click to collapse
You won't be able to update through OTA if you're rooted
https://we.tl/B4j816Z2n8
Here's the link to the TMO OCX27.1 OTA firmware if anyone needs it.
Hi, I am wondering, if I am on ocx 27 do you guys think the 27.1 ota will install in adb sideload as it won't install in ota and I am not rooted. Also, is there a way to extract the bin in the ota?
droidgreg said:
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
Click to expand...
Click to collapse
Did you get your second Z2 rooted and if so did you use magisk v16? I just got a Z2 today that is on the December 1, 2017 security patch, OCX27.1, Android 8.00 and I'd like to root but hesitant. I have already unlocked the bootloader, placed magisk and twrp-3.2.1-1-nash zip(s) in internal storage, and know how to fastboot boot into recovery, I just don't want to brick my new phone. Any help with step by step instructions once I'm in TWRP to flash magisk is greatly appreciated! Do I need to do any of the following: Keep system read only or allow modifications before flashing magisk? wipe data/factory reset, mount storage, wipe cache and dalvik after flashing? Thanks in advance!
climbhigh77 said:
Did you get your second Z2 rooted and if so did you use magisk v16? I just got a Z2 today that is on the December 1, 2017 security patch, OCX27.1, Android 8.00 and I'd like to root but hesitant. I have already unlocked the bootloader, placed magisk and twrp-3.2.1-1-nash zip(s) in internal storage, and know how to fastboot boot into recovery, I just don't want to brick my new phone. Any help with step by step instructions once I'm in TWRP to flash magisk is greatly appreciated! Do I need to do any of the following: Keep system read only or allow modifications before flashing magisk? wipe data/factory reset, mount storage, wipe cache and dalvik after flashing? Thanks in advance!
Click to expand...
Click to collapse
All you need to do is grab the latest twrp img and zip file from twrp. Should be version 3.2.1-1
Then fastboot boot the img file, then once in twrp you want to flash the zip file, then when that is done reboot back into recovery
Then simply flash Magisk and reboot. Done.
How should I properly Flash Stock Firmware?
New to Moto phones and wondering what the correct method is for reverting to stock? I downloaded the 27.1 Oreo zip from this thread, do I flash it in twrp or should I flash it in adb from the bootloader? I get the following error message in twrp whenever I wipe dalvik/cache, try to install a zip, or do a backup which always says fail. I need a fresh install and re root, etc. Thank you!!
climbhigh77 said:
New to Moto phones and wondering what the correct method is for reverting to stock? I downloaded the 27.1 Oreo zip from this thread, do I flash it in twrp or should I flash it in adb from the bootloader? I get the following error message in twrp whenever I wipe dalvik/cache, try to install a zip, or do a backup which always says fail. I need a fresh install and re root, etc. Thank you!!
Click to expand...
Click to collapse
you can not flash with twrp. open the zip and see if there is a "flash-all.bat" file as well as adb and fastboot files. if not then pull them from one of the other flashall zips and add them to 27.1 zip. boot your phone to the bootloader, connect usb cable to your device and pc, then run the .bat file.
mattlowry said:
you can not flash with twrp. open the zip and see if there is a "flash-all.bat" file as well as adb and fastboot files. if not then pull them from one of the other flashall zips and add them to 27.1 zip. boot your phone to the bootloader, connect usb cable to your device and pc, then run the .bat file.
Click to expand...
Click to collapse
Factory reset gets the same error message shown in the attached photo. Thanks for the info, unfortunately I'm still a bit confused. Is this the only method to return to stock? I've searched but I'm not finding much and this method is completely new to me. In the past I've used Odin and LG up with my other devices, this is my first motorola. If I wipe internal storage in twrp will that erase the OS and need a new install? I am thinking that may clear up my issues but nervous that the phone won't boot up after that. Thanks and my apologies for my noob questions.
climbhigh77 said:
Factory reset gets the same error message shown in the attached photo. Thanks for the info, unfortunately I'm still a bit confused. Is this the only method to return to stock? I've searched but I'm not finding much and this method is completely new to me. In the past I've used Odin and LG up with my other devices, this is my first motorola. If I wipe internal storage in twrp will that erase the OS and need a new install? I am thinking that may clear up my issues but nervous that the phone won't boot up after that. Thanks and my apologies for my noob questions.
Click to expand...
Click to collapse
unfortunately other than manually fastbooting each img file to your phone this is the only way. check out this https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
BROKEN
droidgreg said:
https://we.tl/B4j816Z2n8
Here's the link to the TMO OCX27.1 OTA firmware if anyone needs it.
Click to expand...
Click to collapse
Please upload again. Thx
sd_N said:
Please upload again. Thx
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=673956719939833411
Here's the official 27.1 firmware. The flashfile.xml has the correct order and commands to flash in fastboot, or search xda for the converter to a flashall.bat.
Sent from my Moto Z (2) using XDA Labs
I am sure this has been asked and answered 100 times but for the life of me I can't find a definite answer. I have a Pixel 2 XL and it is rooted and I have Magisk and TWRP installed on it. I want to be able to install the OTA for this month, but I do not want to lose anything on the phone. I also would rather not lose Magisk or TWRP. Normally on my android phones I use ROMs and can just update through TWRP, but I want to stay on stock because I don't want to lose Active Edge. So can someone please help me by giving me step by step instructions or point me to instructions that are simple to follow so I can take the OTA?
I really appreciate the help.
I was having the same problem and was helped by some of the members here.. Best way is to flash the firmware after removing the -w from the flash all file. Then flash twrp and magisk.
Ota
Thanks for your help. I will try that.
magicmaker said:
Thanks for your help. I will try that.
Click to expand...
Click to collapse
Here's a quick little guide I made for updating monthly factory images. Hopefully it'll help you out :good:
Sorta related...
Are there any ROMS that come rooted so I don't have to go through the monthly process of backup/unroot/update/root/restore?
Would love to just flash a ROM update and be done.
rank78 said:
Sorta related...
Are there any ROMS that come rooted so I don't have to go through the monthly process of backup/unroot/update/root/restore?
Would love to just flash a ROM update and be done.
Click to expand...
Click to collapse
Not that I'm aware of, but maybe some on the horizon...
Badger50 said:
Here's a quick little guide I made for updating monthly factory images. Hopefully it'll help you out :good:
Click to expand...
Click to collapse
Hi, quick question
I am only able to do them steps above if I have done 'fastboot unlock_critical'? I have only done 'fastboot unlock'
Also I would need to boot into TWRP and flash a kernel + magisk to retain root?
You have to issue the "fastboot unlock_critical" command in order for the bootloader to update, since the bootloader is included in both factory images and full OTAs. Speaking of full OTA's, one of our recognized developers, @elliwigy, revealed (thread here) that it is possible to flash a full OTA image through TWRP, which eliminates the need to open the factory image and remove the -w flag from the last line. Flashing the OTA works because TWRP doesn't check signatures like the stock recovery. You will lose both root and TWRP upon reboot however, so you will still need to connect to a PC in order to reinstall TWRP so you can subsequently replace the stock Kernel with the Flash Kernel and then root.
I can verify this works, as I tried it with the May update.
Hey guys. I accidentally (don't ask) installed the update for Android 10 from 9 stock and lost my twrp and root. Is there any way to at least get root back without having to reinstall everything?
More details will be needed to help. Bootloader unlocked? Guessing yes since you say you had twrp. Check the guide section for root instructions.
Yes I have it unlocked. I looked at the guide and it looks like I will have to reflash the stock rom which I'd like to avoid.
Kreuger said:
Hey guys. I accidentally (don't ask) installed the update for Android 10 from 9 stock and lost my twrp and root. Is there any way to at least get root back without having to reinstall everything?
Click to expand...
Click to collapse
Since, twrp is not available yet for Android 10 (Q), I suggest one of the three following options:
1. If you have to re-flash the Pixel 3 XL Android 10 (Q) Factory image, do #4 'keep data' in this Guide.
2. If your Pixel 3XL has the latest Android 10 (Q) Factory image installed, just do #9 A. in this Guide to root.
3. If you are on a Custom ROM follow the OP Instructions in the Custom ROM thread to root.
Apparently I have the Sept update (QP1A.19711.020.C3) but I currently have no available updates. Am I good to just use your step 2?
Kreuger said:
Apparently I have the Sept update (QP1A.19711.020.C3) but I currently have no available updates. Am I good to just use your step 2?
Click to expand...
Click to collapse
Yes!
Why not do #1 update your Pixel 3 XL to the February Factory image (QQ1A.200205.002). You will not lose your data (need to reinstall anything). Then do #2 to root.
I guess I can do it that way. Thanks.
Edit: Do I need to use a custom kernel? I don't really require one. Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Kreuger said:
Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Click to expand...
Click to collapse
Some people are reporting that issue. You can set the custom channel to canary/canary debug manually. Check the magisk thread.
Thank you. I tried to find it on the github site and found nothing.
Kreuger said:
Thank you. I tried to find it on the github site and found nothing.
Click to expand...
Click to collapse
It is under the magisk files repo.
Kreuger said:
I guess I can do it that way. Thanks.
Edit: Do I need to use a custom kernel? I don't really require one. Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Click to expand...
Click to collapse
Kernel/Kernel Managers are optional. #10 B ,in the guide, updated.
Hey so I patched the image and flashed the file, I'm stuck on the screen with the google logo and progress bar. Also, does it matter that I used adb reboot fastboot to get to the fastboot menu? I noticed it said fastbootd which ive never seen before. It seemed easier to do it that way.
Edit: Ive decided to try flashing another rom.
Kreuger said:
Hey so I patched the image and flashed the file, I'm stuck on the screen with the google logo and progress bar. Also, does it matter that I used adb reboot fastboot to get to the fastboot menu? I noticed it said fastbootd which ive never seen before. It seemed easier to do it that way.
Edit: Ive decided to try flashing another rom.
Click to expand...
Click to collapse
For flashing boot.img you should reboot bootloader. Fastboot is a separate thing now for system files to be flashed. Boot, bootloader, and radio are flashed in bootloader, others in fastbootd.
wangdaning said:
For flashing boot.img you should reboot bootloader. Fastboot is a separate thing now for system files to be flashed. Boot, bootloader, and radio are flashed in bootloader, others in fastbootd.
Click to expand...
Click to collapse
Ah I was unaware. Thanks
Seeing a lot of issues with Android 11 and 12 unlocking the bootloader and applying root. Is now not a good time to upgrade or should I wait for a boot image?
Not quite sure what you're referring to, but there are zero issues with unlocking the bootloader or rooting your device...
I can't speak for TWRP. I have had issues with it the last few versions so I had to make due without it. If I am mistaken about having twrp on the OP9 Pro on the newest LE2125 c61 update, I'd be interested.
Anyway, my response is mostly to address your question regarding root. Here are the steps that worked for me.
[OnePlus 9 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
I have been rooted since day one on both A11 & A12. I'm running stock and haven't had a single issue.
Avoid TWRP, it's known to not work properly on A12
If you like to flash a custom ROM. Follow the instructions and you will be fine.
I am coming off the oneplus 7pro was enjoying TWRP and Magisk, with Exposed now I am hearing TWRP isn't working on anything above 10.0 ver. Guess I have to do so more research or pay Monfrio a ransom to work on TWRP.
intense21 said:
I am coming off the oneplus 7pro was enjoying TWRP and Magisk, with Exposed now I am hearing TWRP isn't working on anything above 10.0 ver. Guess I have to do so more research or pay Monfrio a ransom to work on TWRP.
Click to expand...
Click to collapse
there is no need for TWRP...
Smedslund said:
I have been rooted since day one on both A11 & A12. I'm running stock and haven't had a single issue.
Avoid TWRP, it's known to not work properly on A12
If you like to flash a custom ROM. Follow the instructions and you will be fine.
Click to expand...
Click to collapse
How do you root without twrp? or you mean to just boot twrp and not install it?
CtrlValCanc said:
How do you root without twrp? or you mean to just boot twrp and not install it?
Click to expand...
Click to collapse
Use Magisk, patch bootimg , install and reboot.
Read this usefull guide.
Smedslund said:
Use Magisk, patch bootimg , install and reboot.
Read this usefull guide.
Click to expand...
Click to collapse
thank you, i couldn't find what boot.img to download (and how), but this guide has already all!
CtrlValCanc said:
thank you, i couldn't find what boot.img to download (and how), but this guide has already all!
Click to expand...
Click to collapse
I always just sideload. (downdload magisk apk & rename to zip before)
this way you do not need the extra boot.img I think.
vincemue said:
I always just sideload. (downdload magisk apk & rename to zip before)
this way you do not need the extra boot.img I think.
Click to expand...
Click to collapse
could you explain better? I never used sideload before. What commands do you use?
CtrlValCanc said:
could you explain better? I never used sideload before. What commands do you use?
Click to expand...
Click to collapse
If you want to install any add-ons, Reboot to Recovery, then when your device reboots, click Apply Update, then Apply from ADB, then adb sideload filename.zip those packages in sequence. (GAPPS or Magisk for example)
for example for magisk:
download the newest magisk apk version
after download, rename it and instead of .apk do it .zip
go into revovery and click Apply Update, then Apply from ADB
command is : "adb sideload Magisk-v2X.X.zip"
you must exchange X for your version.
Boot images gets patched
please note that I am not an expert, that is just what I found somewhere and use since then.
if you need more information you could also check the install instructions for lineageOS to get to know some basics: https://wiki.lineageos.org/devices/lemonadep/install