I successfully rooted the phone using Magisk, and looking at how to install LineageOS, I saw I needed TWRP first. I followed all the instructions, but when I use fastboot to boot twrp.img, I get the following error message, "Error verifying the received boot.img: Invalid Parameter". Searching for an answer, I saw there was an old issue with TWRP with the Pixel 3a XL and Android 10, but I found nothing more recent about Android 11.
I thought maybe I shouldn't have rooted the phone first, so I reflashed with the stock boot.img and tried TWRP again, but that doesn't solve it. Any idea how I can boot TWRP? Or is there a way to install LineageOS with TWRP? Thanks!
Build # RQ2A.2100505.002
TWRP image twrp-3.5.2_9-0-bonito.img
Twrp doesn't work currently for android 10+
You don't need it to install lineage, just flash the lineage recovery and follow the wiki install guide.
Install LineageOS on bonito | LineageOS Wiki
wiki.lineageos.org
If TWRP does not work on Android 10+ what are we doing about flashing custom roms? Booting the TWRP and then sideloading the ROM?
I need help. When I try to boot TWRP(assuming its possible) I get an error :invalid parameter, error verifying the boot image. I am on Android 11. Yes, Ive used the search function or else I would not have found this thread.
I do not want to flash lineage, but the instructions are vague in other ROM threads.
I just built a TWRP that works on Android 11. I wasn't sure how much interest there was in it, though, so I didn't bother posting it anywhere. I'll consider it once I clean up the source a bit.
Captain_Throwback said:
I just built a TWRP that works on Android 11. I wasn't sure how much interest there was in it, though, so I didn't bother posting it anywhere. I'll consider it once I clean up the source a bit.
Click to expand...
Click to collapse
Please post it! It would be greatly appreciated!
ncrawler said:
Please post it! It would be greatly appreciated!
Click to expand...
Click to collapse
I posted it on Telegram here: https://t.me/pixel3a/161825
Captain_Throwback said:
I posted it on Telegram here: https://t.me/pixel3a/161825
Click to expand...
Click to collapse
Thank You! I've been waiting for this!
I cant get your twrp and magisk to work together? I can only get one or the other working.
ncrawler said:
I cant get your twrp and magisk to work together? I can only get one or the other working.
Click to expand...
Click to collapse
Boot TWRP, copy image to device, use Install Image -> Install Recovery Ramdisk to install TWRP, then flash Magisk.apk.
I've done it a bunch of times and it works fine. Is that what you're doing?
Captain_Throwback said:
Boot TWRP, copy image to device, use Install Image -> Install Recovery Ramdisk to install TWRP, then flash Magisk.apk.
I've done it a bunch of times and it works fine. Is that what you're doing?
Click to expand...
Click to collapse
Done it about 10 times and never boots again
ncrawler said:
Done it about 10 times and never boots again
Click to expand...
Click to collapse
with or without lmza kernel
ncrawler said:
with or without lmza kernel
Click to expand...
Click to collapse
No idea what to tell you. It works for users in the TG group and it works for me. That's the exact process I'm using. You can alternatively try the Advanced -> Flash Current TWRP option and then flash Magisk and see what happens.
Thanks! I think I got it! Think I was using the wrong Magisk! I Guess I still have to use lmza kernel to pass integrity in magisk?
ncrawler said:
Thanks! I think I got it! Think I was using the wrong Magisk! I Guess I still have to use lmza kernel to pass integrity in magisk?
Click to expand...
Click to collapse
I have no idea about any specific kernel or integrity checks in Magisk. I only build TWRP.
Related
Hi there,
I wanted to install the latest image of Nethunter (found on build.nethunter.com/nightly) but when I install it with TWRP I keep getting the message : "Unpacking boot image failed" in the log screen.
What I did in order:
- Unlock fastboot mode
- Flash TWRP recovery (found on build.nethunter.com/twrp)
- Reboot on TWRP
- Install kernel ( kernel-nethunter-oneplus3-nougat-3.15.4-20170126-2226 )
- Install ROM ( nethunter-generic-armhf-kalifs-minimal-rolling-3.15.4-20170202-1604 )
- Reboot
It is when I install the rom that I get the error message "Unpacking boot image failed". Even if at the end it says "install completed - Success", it keep loading (with the nethunter loading screen) indefinitely...
I tried many differents versions of TWRP and even different builds of Nethunter, I found nothing on the net, so what should I do ?
Should I post an issue on the kali-nethunter github ?
Hope you have some ideas of what I can try...
However if you need any other information (log file ...), tell me what.
Aiscargeauh said:
Hi there,
I wanted to install the last image of Nethunter (found on build.nethunter.com/nightly) but when I install it with TWRP (found on build.nethunter.com/twrp) I keep getting the message : "Unpacking boot image failed" in the log screen.
I tried many differents versions of TWRP and even different builds of Nethunter, I found nothing on the net, so what should I do ?
Should I post an issue on the kali-nethunter github ?
Hope you have some ideas of what I can try...
However if you need any other information (log file ...), tell me what.
Click to expand...
Click to collapse
What ROM are you using?
Last time i installed it i was on OOS 3.2.2. You have to flash kernel and then the big file (generic nethunter.....)
Found that in https://forum.xda-developers.com/showpost.php?p=68451978&postcount=6
It worked perfectly but since 3.2.2 i havent touched it again so not sure what rom is compatible atm
fuarkgl3 said:
What ROM are you using?
Click to expand...
Click to collapse
I'm trying with the "nethunter-generic-armhf-kalifs-minimal-rolling-3.15.4-20170202-1604.zip"
Also tried with the full version, instead of minimal but same result.
Aiscargeauh said:
I'm trying with the "nethunter-generic-armhf-kalifs-minimal-rolling-3.15.4-20170202-1604.zip"
Also tried with the full version, instead of minimal but same result.
Click to expand...
Click to collapse
I mean version of OOS, not nethunter overlay. See my screenshot. You have to download one of the following kernels depending if you are on MM or nougat. Flash it before flashing the nethunter overlay
fuarkgl3 said:
I mean version of OOS, not nethunter overlay
Click to expand...
Click to collapse
I'm trying with the latest OTA version, so actually the 4.0.2.
I also installed the kernel before, I'm gonna edit my first post with informations on what I did.
Aiscargeauh said:
I'm trying with the latest OTA version, so actually the 4.0.2.
I also installed the kernel before, I'm gonna edit my first post with informations on what I did.
Click to expand...
Click to collapse
Ok i just read it. And it seems strange indeed. Will try to install it today since i use also oos 4.0.2 and will report back asap
Just out of curiosity what twrp are you using?
fuarkgl3 said:
Ok i just read it. And it seems strange indeed. Will try to install it today since i use also oos 4.0.2 and will report back asap
Just out of curiosity what twrp are you using?
Click to expand...
Click to collapse
Thank's for the support anyway
I'm using the TWRP provided by Nethunter on build.nethunter.com/twrp/oneplus/
Also tried with official 3.0.3 for the OnePlus 3 from twrp.me/devices/oneplusthree.html
Aiscargeauh said:
Thank's for the support anyway
I'm using the TWRP provided by Nethunter on build.nethunter.com/twrp/oneplus/
Also tried with official 3.0.3 for the OnePlus 3 from twrp.me/devices/oneplusthree.html
Click to expand...
Click to collapse
Got it working. Only problem is i dont find the option to enable OTG-USB lol
fuarkgl3 said:
Got it working. Only problem is i dont find the option to enable OTG-USB lol
Click to expand...
Click to collapse
And I'm here sitting with my error and my infinite boot, lol.
Can you please put the installation process you did ? With the files you used ?
I'm getting my phone to full-stock.
Aiscargeauh said:
Can you please put the installation process you did ? With the files you used ?
I'm getting my phone to full-stock.
Click to expand...
Click to collapse
Sure. Just give me time to post what i did, currently restoring my nandroid because something went wrong when updating metapackages, so im going to download full version instead of minimal and enable OGT-USB to check if wifite works. I will post the steps asap :good:
meanwhile..... how the **** do i enable usb-otg? i dont find the option in settings/storage/3dot
Good and bad news: OTG does not work (it worked for me on MM) but nethunter runs "well" ... it stucks while rebooting and some weird things more. It runs laggy as well...
Steps and config i have
-Experience ROM v10.1(oos 4.0.2 with some adds) and custom TWRP by blu_spark v14
1-Download these 2 files from https://build.nethunter.com/nightly/3.15.4-20170202-1604/
-kernel-nethunter-oneplus3-nougat-3.15.4-20170202-1604.zip
-nethunter-generic-arm64-kalifs-full-rolling-3.15.4-20170202-1604.zip
2-Reboot to recovery and install nethunter-generic-arm64.....
3-Not sure if you have to reboot and then install kernel but i flashed nethunter+kernel without rebooting to system
4-Reboot to system and open supersu, then open nethunter app and grant superuser permissions
5-Done.
I Dont really know why my external adapter or pendrive are not recognized, because it did in MM with same hardware lol. Maybe now only works with official usb-c adapter, who knows
I will try this when I can, but it is close to what I already did.
I will edit this post when done.
I seen that you used the arm64 version, perhaps the problem is that I use the armhf ?
Aiscargeauh said:
I will try this when I can, but it is close to what I already did.
I will edit this post when done.
I seen that you used the arm64 version, perhaps the problem is that I use the armhf ?
Click to expand...
Click to collapse
may be, but im not sure. Finally got USB-OTG working but it runs very laggy and dont find any network. So problem is nh build or oos 4.0.2
fuarkgl3 said:
may be, but im not sure. Finally got USB-OTG working but it runs very laggy and dont find any network. So problem is nh build or oos 4.0.2
Click to expand...
Click to collapse
Do you think flashing another ROM before flashing nh-generic will help ?
Aiscargeauh said:
Do you think flashing another ROM before flashing nh-generic will help ?
Click to expand...
Click to collapse
Dont think so. But latest build i installed NH i didnt use arm64 version but armhf. So maybe try what i did but using custom TWRP by blu_spark v14 and armhf.... im not sure
Tested with 2 antennas and result is the same in both (see SS)
FOR SOLUTION READ POST:
[SIZE="5"]https://forum.xda-developers.com/showpost.php?p=71007646&postcount=6[/SIZE]
Long time silent reader here. I always find solutions for my problems in xda-devs, until now.
Hope you guys can help me once again..
So, yesterday I messed up my OP3 and wiped all partitions on my phone.
I've tried many steps, trying to flash a flashable stock rom (the one with boot.img and system img) in fastboot, result= installation succeed, but getting blackscreen on boot.
Installing full OOS rom from adb sideload using stock recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Installing full OOS rom from adb sideload using TWRP recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Copy the rom to my phone, and installing the zip with TWRP, result failed (error=7)
So far these are my references:
https://forums.*neplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip
OnePlus3Oxygen_16_OTA_008_all_1606122244_e0cfc5ffc8bf411a.zip
oxygen-os-3.2.5-fastboot-flashable.zip
twrp 3.0.3
https://forum.xda-developers.com/showthread.[/CODE]php?t=2588979
Click to expand...
Click to collapse
applsaus said:
Long time silent reader here. I always find solutions for my problems in xda-devs, until now.
Hope you guys can help me once again..
So, yesterday I messed up my OP3 and wiped all partitions on my phone.
I've tried many steps, trying to flash a flashable stock rom (the one with boot.img and system img) in fastboot, result= installation succeed, but getting blackscreen on boot.
Installing full OOS rom from adb sideload using stock recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Installing full OOS rom from adb sideload using TWRP recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Copy the rom to my phone, and installing the zip with TWRP, result failed (error=7)
So far these are my references:
Click to expand...
Click to collapse
So twrp is working right?
Flash any rom say lineage os
Flash multirom by BitOBSessiOn
Flash multirom twrp
Flash oos as secondary rom
And then swap oos to primary rom
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Ye sideboard gives me issues aswell, push the zip and manually flash it In twrp: "adb push romzipname /sdcard/", the file is now ib the folder /sdcard/.
Puddi_Puddin said:
Ye sideboard gives me issues aswell, push the zip and manually flash it In twrp: "adb push romzipname /sdcard/", the file is now ib the folder /sdcard/.
Click to expand...
Click to collapse
tried it with OOS 3.2.8 and OOS 4.0.2, both give me ERROR=7
abhi0502 said:
So twrp is working right?
Flash any rom say lineage os
Flash multirom by BitOBSessiOn
Flash multirom twrp
Flash oos as secondary rom
And then swap oos to primary rom
Click to expand...
Click to collapse
Working on it. Flashed lineage os, looks like working.
Still waiting on boot screen tho (15 mins & counting, hope it won't be bootloop)
hyperorb said:
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
Good idea, I'll put ur idea for the next try
applsaus said:
tried it with OOS 3.2.8 and OOS 4.0.2, both give me ERROR=7
Working on it. Flashed lineage os, looks like working.
Still waiting on boot screen tho (15 mins & counting, hope it won't be bootloop)
Good idea, I'll put ur idea for the next try
Click to expand...
Click to collapse
Then it's a twrp issue. I'm currently in Bluspark v16 so
Error 7 in TWRP AFAIK is an issue with using an incompatible recovery, try the latest one 3.0.4-1 I think it is from this forum.
Puddi_Puddin said:
Then it's a twrp issue. I'm currently in Bluspark v16 so
Click to expand...
Click to collapse
ghostofcain said:
Error 7 in TWRP AFAIK is an issue with using an incompatible recovery, try the latest one 3.0.4-1 I think it is from this forum.
Click to expand...
Click to collapse
I flash twrp bluspark as @Puddi_Puddin suggested and flashing Freedom OS. After that, I restore my data using my last Nandroid backup, then the bootloop comes again. Tried it several times using TWRP Bluspark with different ROMs, still no luck. So I suggest, there's nothing I can do to restoring my phone's data.
I read across the XDA forums and Oneplus forums that some people had similar issues for me, and they suspected something's wrong about corrupted partition, not because twrp version. And I also had tried flashing a few ROM in the past using the same TWRP 3.03 version without any problems. Strange.
Anyway, problems solved, my phone's up and running.
CASE CLOSED.
Thanks XDA
P.S: MODS Please Lock/Close this thread
applsaus said:
Anyway, problems solved, my phone's up and running.
CASE CLOSED.
Thanks XDA
P.S: MODS Please Lock/Close this thread
Click to expand...
Click to collapse
And, what was the solution ?
Restarting from Zero I guess.
Donglip said:
And, what was the solution ?
Click to expand...
Click to collapse
This:
hyperorb said:
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
emuandco said:
Restarting from Zero I guess.
Click to expand...
Click to collapse
Better than not starting at all, at least.
Hi all, got TWRP installed OK on my Pixel 2 XL, hit reboot and then it goes straight back into TWRP, but with no Touch. So, thought I could flash a new kernel (Flash?) but... no ADB! I guess the phone hasn't probably booted so ADB can't see the phone.
Any options at this point?!
rendez2k said:
Hi all, got TWRP installed OK on my Pixel 2 XL, hit reboot and then it goes straight back into TWRP, but with no Touch. So, thought I could flash a new kernel (Flash?) but... no ADB! I guess the phone hasn't probably booted so ADB can't see the phone.
Any options at this point?!
Click to expand...
Click to collapse
If your phone boots back to bootloader on reboot, you did something wrong. Reflash system imgs and start over.
Thanks! Is that a matter of following the guides on the official google download page and getting the factory images?
rendez2k said:
Thanks! Is that a matter of following the guides on the official google download page and getting the factory images?
Click to expand...
Click to collapse
Yes. If you don't want your data wiped, open the install.bat file and take off the -w.
Did you unlock your bootloader correctly? Unlock critical? I believe the pixel 2 xl is the only phone where that has to be done.
Boot into bootloader and fastboot flash recovery.img again, once your in recovery, flash the recovery.zip from your storage again, then reboot recovery.... its happened to me, usually when I switch slots, all I have to do is reflash recovery.
Also note, If I am trying to boot at that point (rather than flash a ROM), I usually just flash the kernel and magisk and I'm good to go.
Thanks all! I flashed the patched boot.img again and it seems to be working OK
OK, this whole thing is confusing me now! I get TWRP installed then I have to re-flash my boot.img before I quit TWRP (a magisk patched version of Flash) or the phone keeps booting to TWRP. Thats fine, but when I've flashed the boot.img I loose TWRP!
rendez2k said:
OK, this whole thing is confusing me now! I get TWRP installed then I have to re-flash my boot.img before I quit TWRP (a magisk patched version of Flash) or the phone keeps booting to TWRP. Thats fine, but when I've flashed the boot.img I loose TWRP!
Click to expand...
Click to collapse
Yes you do loose twrp after flashing the boot.img. the reason being that stock recovery resides in the boot.img. So when you flash it, bye..bye twrp! Why not just fastboot twrp, then once in twrp, flash the twrp installer zip, then flash your custom kernel(if used) then flash the magisk zip for root. :good:
Ok! So this is where I'm confused. The Flash Kernel is called boot.img? So I'm flashing it in twrp with the boot option?
rendez2k said:
Ok! So this is where I'm confused. The Flash Kernel is called boot.img? So I'm flashing it in twrp with the boot option?
Click to expand...
Click to collapse
No. Flash kernel is just the kernel, the boot.img is from the factory image. Flash the zip version of Flash kernel in twrp, then flash magisk.zip :good:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
rendez2k said:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
Click to expand...
Click to collapse
Download the 14mb FlashKernel-Taimen-v2.30.zip instead and put it in your phone to flash from within TWRP, followed by the magisk zip
http://nchancellor.net/downloads/kernels/taimen/8.1.0/stable/
rendez2k said:
Ok. So here a shot of my confusion! The file I got from Flash is this one, flashkernel-taimen.v.2.30-boot.img. The three choices I'm being given by TWRP is boot, system or vendor?
Click to expand...
Click to collapse
DON'T DO THAT! You'll bootloop for sure!! Do what the post below says, and what I told you earlier!
Pyr0x64 said:
Download the 14mb FlashKernel-Taimen-v2.30.zip instead and put it in your phone to flash from within TWRP, followed by the magisk zip
http://nchancellor.net/downloads/kernels/taimen/8.1.0/stable/
Click to expand...
Click to collapse
Thanks all! All sorted! Now, to Xposed or not to Xposed. That's the question. Seems to be tripping safetynet but that's another quandary
rendez2k said:
Thanks all! All sorted! Now, to Xposed or not to Xposed. That's the question. Seems to be tripping safetynet but that's another quandary
Click to expand...
Click to collapse
There is no solution for that. Xposed always fails SafetyNet.
Is Xposed worth having these days? Are people still actively developing useful mods?
rendez2k said:
Is Xposed worth having these days? Are people still actively developing useful mods?
Click to expand...
Click to collapse
I think it's worth it, for the following apps:
I've had so many problems with TWRP on this phone that I don't even flash it anymore. If I need to flash a zip file I just fastboot into TWRP and flash it that way. Kind of a pain in the ass but I don't flash many zip files anyway.
Fuse8499 said:
I've had so many problems with TWRP on this phone that I don't even flash it anymore. If I need to flash a zip file I just fastboot into TWRP and flash it that way. Kind of a pain in the ass but I don't flash many zip files anyway.
Click to expand...
Click to collapse
No problems with TWRP here. Maybe you are flashing to the wrong slot.
rendez2k said:
Is Xposed worth having these days? Are people still actively developing useful mods?
Click to expand...
Click to collapse
I keep hoping Xposed will go die in a fire. It causes more problems than it solves, to the point ROM developers will tell you not to bother reporting issues with it installed. Rovo knows his stuff, but his creation has caused more damage to custom ROM development than Cyanogenmod did in its last three years.
I have attempted :
-Fastboot boot TWRP.img
-Reboot Recovery
-TWRP Flash Magisk v16.4
-Reboot into System
Am i missing a Kernel? If so, where is the Kernel for PDP3?
Am i missing a Patched_Boot.img? If so, where is the PDP3 Patched_Boot.img?
What is the correction instruction for gaining ROOT on PDP3?
What else may i be missing from the recipe?
I have searched and asked others via PM or in the Thread, and have received half-ass replies.... So would someone please lay it out, if not, i guess i will go back to 8.1.0....where i had ROOT, Recovery, and Viper4Android... Thank God I made a back-up....
Thanks in advance,
T
AndroidDevices said:
I have attempted :
-Fastboot boot TWRP.img
-Reboot Recovery
-TWRP Flash Magisk v16.4
-Reboot into System
Am i missing a Kernel? If so, where is the Kernel for PDP3?
Am i missing a Patched_Boot.img? If so, where is the PDP3 Patched_Boot.img?
What is the correction instruction for gaining ROOT on PDP3?
What else may i be missing from the recipe?
I have searched and asked others via PM or in the Thread, and have received half-ass replies.... So would someone please lay it out, if not, i guess i will go back to 8.1.0....where i had ROOT, Recovery, and Viper4Android... Thank God I made a back-up....
Thanks in advance,
T
Click to expand...
Click to collapse
I'm generally curious how many times, and in how many threads, you're going to ask this question.
1) Flash DP3. Let the device boot, log in, set it up, etc.. I do NOT enable a pin/pattern yet.
2) Reboot to the bootloader & fastboot TWRP.
3) Flash Magisk 16.4.
4) Boot into the system & have root.
I've done this process damn near 10x going between dp2/8.1/dp3. There is no special trick to it.
EvilDobe said:
I'm generally curious how many times, and in how many threads, you're going to ask this question.
1) Flash DP3. Let the device boot, log in, set it up, etc.. I do NOT enable a pin/pattern yet.
2) Reboot to the bootloader & fastboot TWRP.
3) Flash Magisk 16.4.
4) Boot into the system & have root.
I've done this process damn near 10x going between dp2/8.1/dp3. There is no special trick to it.
Click to expand...
Click to collapse
If he wants recovery, he needs to flash twrp-Pixel2XLinstaller-.zip before flashing magisk 16.4
Tulsadiver said:
If he wants recovery, he needs to flash twrp-3.2.1-2-taimen.zip before flashing magisk 16.4
Click to expand...
Click to collapse
OP didn't ask for recovery. OP asked how to get root. While you are 100% correct on how to get a static TWRP instance it is not relevant to the OP getting root.
EvilDobe said:
OP didn't ask for recovery. OP asked how to get root. While you are 100% correct on how to get a static TWRP instance it is not relevant to the OP getting root.
Click to expand...
Click to collapse
He did mention that he would want to go back because he had root and recovery.....
EvilDobe said:
OP didn't ask for recovery. OP asked how to get root. While you are 100% correct on how to get a static TWRP instance it is not relevant to the OP getting root.
Click to expand...
Click to collapse
I'll take TWRP as well, wasnt sure if there was an unofficial version for P or not...
Tulsadiver said:
He did mention that he would want to go back because he had root and recovery.....
Click to expand...
Click to collapse
Semantics. OP's post, and general boggle, is that they cannot obtain root on DP3. My response was directly related to the OPs post, and last like 10 comments across this sub. What OP had is presently irrelevant since the current goal is to obtain root. If the OP had an additional question as to how to obtain static TWRP I would have addressed that at a later date/time or your response would have been appropriate. Perhaps I took it for granted that the OP had an understanding on how to get static TWRP but, again, the point of this thread is getting root on DP3 which my response answers & yours does not.
Tulsadiver said:
If he wants recovery, he needs to flash twrp-Pixel2XLinstaller-.zip before flashing magisk 16.4
Click to expand...
Click to collapse
After i flash the TWRP Installer, do i reboot and change slots, or no?
EvilDobe said:
Semantics. OP's post, and general boggle, is that they cannot obtain root on DP3. My response was directly related to the OPs post, and last like 10 comments across this sub. What OP had is presently irrelevant since the current goal is to obtain root. If the OP had an additional question as to how to obtain static TWRP I would have addressed that at a later date/time or your response would have been appropriate. Perhaps I took it for granted that the OP had an understanding on how to get static TWRP but, again, the point of this thread is getting root on DP3 which my response answers & yours does not.
Click to expand...
Click to collapse
I appreciate BOTH of your help, no need to get all technical!
AndroidDevices said:
After i flash the TWRP Installer, do i reboot and change slots, or no?
Click to expand...
Click to collapse
No, flash Magisk unless you want to try a custom kernel. If so, flash it before Magisk, flash Magisk, then reboot.
After flashing magisk, the phone will not reboot, instead keeping me in a bootloop and sending me back into TWRP. Any ideas? Im happy to go back to stock if thatll make my phone work again!
Jameswebb97 said:
After flashing magisk, the phone will not reboot, instead keeping me in a bootloop and sending me back into TWRP. Any ideas? Im happy to go back to stock if thatll make my phone work again!
Click to expand...
Click to collapse
Hi James what exactly did you flash before magisk and I'm guessing you were flashing from stock and also not p?Also how did you flash?
all43 said:
Hi James what exactly did you flash before magisk and I'm guessing you were flashing from stock and also not p?Also how did you flash?
Click to expand...
Click to collapse
Hey,
I was installing from P (9.0 DP3)
I installed TWRP first by flashing the image and then installing the zip file on to the phone.
Next i installed magisk, the installation all went through absolutely fine.
When i hit reboot, it goes onto the white splash screen, then brings up a small progress bar that goes across. This lasts for a minute or two, then dumps me back into TWRP.
I attempted all ways listed, and i end up Booting into Stock Recovery with a corrupt message forcing me to Power Off or Factory Reset or i got stuck at the Loading "G". Ended up restoring my June 8.1.0 Back up. Thanks for trying to help... I'll wait till there is more info on the subject...
AndroidDevices said:
I attempted all ways listed, and i end up Booting into Stock Recovery with a corrupt message forcing me to Power Off or Factory Reset or i got stuck at the Loading "G". Ended up restoring my June 8.1.0 Back up. Thanks for trying to help... I'll wait till there is more info on the subject...
Click to expand...
Click to collapse
A complete wipe when going to P is the best way to ensure there are no problems but what has worked for me is after installing dp3, rebooting to fastboot, booting to TWRP and doing a factory reset in TWRP. You will not lose data but will have to set your phone up as new. Then, boot back to fastboot and following the instructions as stated in the prior posts to gain root and recovery.
Tulsadiver said:
A complete wipe when going to P is the best way to ensure there are no problems but what has worked for me is after installing dp3, rebooting to fastboot, booting to TWRP and doing a factory reset in TWRP. You will not lose data but will have to set your phone up as new. Then, boot back to fastboot and following the instructions as stated in the prior posts to gain root and recovery.
Click to expand...
Click to collapse
Thanks, i'll give it a try again with a Factory Reset 1st...
AndroidDevices said:
I attempted all ways listed, and i end up Booting into Stock Recovery with a corrupt message forcing me to Power Off or Factory Reset or i got stuck at the Loading "G". Ended up restoring my June 8.1.0 Back up. Thanks for trying to help... I'll wait till there is more info on the subject...
Click to expand...
Click to collapse
Which version of TWRP are you using (twrp-3.2.1-2 is the latest)? Are you seeing errors in the twrp gui while flashing? I'm not sure what you mean by "more info on it" because it's literally just flash the Magisk zip then reboot. The only things I can think of are that you're using an older version of twrp or the magisk zip is corrupt giving you a bad install.
EvilDobe said:
Which version of TWRP are you using (twrp-3.2.1-2 is the latest)? Are you seeing errors in the twrp gui while flashing? I'm not sure what you mean by "more info on it" because it's literally just flash the Magisk zip then reboot. The only things I can think of are that you're using an older version of twrp or the magisk zip is corrupt giving you a bad install.
Click to expand...
Click to collapse
Yes, always using the latest TWRP Official Builds. No errors in the script. What i mean by more info, is just that, when someone posts a thread, and i see it is working for users without issue, i will take the plunge if this doesnt work this time. And im using Magisk v16.4beta...
I think i am so use to Fastboot boot TWRP3212.img, then flashing the installer and rebooting to switch slots. I'm sure i am just not following something. Do i need to reboot after flashing Installer and before flashing Magisk, or NO reboot?
AndroidDevices said:
Yes, always using the latest TWRP Official Builds. No errors in the script. What i mean by more info, is just that, when someone posts a thread, and i see it is working for users without issue, i will take the plunge if this doesnt work this time. And im using Magisk v16.4beta...
I think i am so use to Fastboot boot TWRP3212.img, then flashing the installer and rebooting to switch slots. I'm sure i am just not following something. Do i need to reboot after flashing Installer and before flashing Magisk, or NO reboot?
Click to expand...
Click to collapse
Don't reboot, TWRP installer installs to both slots.
Flash installer, hit back button, find magisk.zip, flash it.
AndroidDevices said:
Yes, always using the latest TWRP Official Builds. No errors in the script. What i mean by more info, is just that, when someone posts a thread, and i see it is working for users without issue, i will take the plunge if this doesnt work this time. And im using Magisk v16.4beta...
I think i am so use to Fastboot boot TWRP3212.img, then flashing the installer and rebooting to switch slots. I'm sure i am just not following something. Do i need to reboot after flashing Installer and before flashing Magisk, or NO reboot?
Click to expand...
Click to collapse
What happens when you just do this:
Get DP flashed & configured. No passwords/patterns/security features.
fastboot boot TWRP3212.img
Flash your magisk 16.4 file.
Reboot.
Hi all,
I've updated my 3xl to the december update like usual, flash-all.bat without -w. Afterwards, it boots fine, and in settings it clearly states that I'm running the December security patch.
However, when I boot into twrp (not installed) and flash magisk, android boots to just before asking my SIM PIN, says "Shutting Down", then reboots and gives me the message "Can't load Android System. Your data may be corrupt." etc. inside stock recovery.
Did the December update somehow break magisk? Anyone gotten it to work? I'd rather not do a factory reset if it's not needed.
Works fine for me.
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Working fine for me as well.
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
mikepopo99 said:
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Click to expand...
Click to collapse
jd1639 said:
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
TonikJDK said:
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
Click to expand...
Click to collapse
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Flash the stock boot.img to both slots.
Reboot and check it.
Copy the Magisk zip to your phone.
Fastboot boot the TWRP img file, don't install it.
Use TWRP to install the Magisk zip, and you are done.
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
RogerXIII said:
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
Click to expand...
Click to collapse
Good deal. That is why I always keep a copy of the Magisk uninstaller on the phone itself. As long as I can get to BL/temp TWRP .img, the worst I am out is the time it takes me to reconfigure Magisk.
RogerXIII said:
However, when I boot into twrp (not installed)
Click to expand...
Click to collapse
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Shaftamle said:
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Click to expand...
Click to collapse
The TWRP image from the official website, and then simply fastboot boot twrp.img
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
Ok cool. Wasn't sure if there was an app like fashify or something.
Fire Hound 8.1
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
you are godsend my friend.
Touz604 said:
you are godsend my friend.
Click to expand...
Click to collapse
Glad you got it figured out.
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
You ca't yet.
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
Thread is from 2018
I am gonna check the official TWRP website for the workable TWRP for my Pixel 3 till I see your post
wangdaning said:
Thread is from 2018
Click to expand...
Click to collapse