Related
Since this is a new setup for Android phones, I am trying to take full advantage of it. I already unlocked the bootloader and installed twrp. I was running under slot a and installed EX kernel and rooted. What I want to ultimately do is have slot A handle anything I want to use root for and slot B to be unrooted with EX kernel to hide the bootloader unlock. Now my question is should I be loading up both slots using adb and fastboot with stock images and then using twrp to install the kernels and root? I tried to install my backup into slot B from A and soft bricked my device. It refused to allow me to mount /system. After 20 minutes of fiddling, I got booted up again but before I try it again, I want to find out from someone who has already done this. Thank you.
so I successfully have the dual boot running on my pixel (verizon edition) with the same configuration you are trying (one is NDE63X image rooted and one is NDE63X image stock/unrooted). Here were my steps:
-> dePixel8 to unlock bootloader (because verizon edition pixel)
-> download NDE63X image from google and modified flash_all.sh to flash stock images to both slots manually
using the --slot _a/_b and --skip-secondary flags. Modified scripts below. At this point I confirmed that I could boot to both slots. I also verified bootloader lock/unlock again to make sure it was stock image on both slots
-> TWRP alpha2 to get recovery on both slots
-> with slot _b selected as active in TWRP, i installed the SuperSU v2.78 SR4 zip
-> with slot _a as active in TWRP, installed ElementalX-P-1.00 zip for the kernel patch to pass SafetyNet
voila, I now have non-rooted on slot _a and rooted on slot _b
Note that TWRP is not really a requirement for doing this. I had the same dual boot configuration working with SuperSU v2.78 SR3 rooting one slot directly. The only reason I needed TWRP is so that I can switch slots easily on the device and don't need a cable and a laptop just to switch the bootloader flag
Although, I got this to work it still falls short of what I really wanted to do. For my use-case I would really want an isolated userdata for the two slots so I can use the rooted slot as a complete sandbox. and then perhaps have a shared folder mechanism between the two. ...so if somebody has an idea on this, I'm all ears.
[UPDATE]: Note that the unrooted slot is still limited in the sense that safetynet checks fail and so AndroidPay etc.. that use that API will still not work. This, however, has little to do with the dual boot setup and more because SafetyNet now fails on just unlocked bootloader and we do need it unlocked. On Conchors' suggestion, I installed ElementalX kernel on slotA from TWRP and now my 'otherwise-stock' non-rooted image on slotA passes SafetyNet while slotB is successfully rooted
flash_all_slot-a.sh
Code:
fastboot flash --slot _a bootloader bootloader-sailfish-8996-012001-1608281716.img
fastboot reboot-bootloader
sleep 5
fastboot flash --slot _a radio radio-sailfish-8996-012511-1609191801.img
fastboot reboot-bootloader
sleep 5
#fastboot -w update image-sailfish-nde63x.zip
fastboot update --slot _a --skip-secondary image-sailfish-nde63x.zip
flash_all_slot-b.sh
Code:
fastboot flash --slot _b bootloader bootloader-sailfish-8996-012001-1608281716.img
fastboot reboot-bootloader
sleep 5
fastboot flash --slot _b radio radio-sailfish-8996-012511-1609191801.img
fastboot reboot-bootloader
sleep 5
#fastboot -w update image-sailfish-nde63x.zip
fastboot update --slot _b --skip-secondary image-sailfish-nde63x.zip
hucqym said:
so I successfully have the dual boot running on my pixel (verizon edition) with the same configuration you are trying (one is NDE63X image rooted and one is NDE63X image stock/unrooted). Here were my steps:
-> dePixel8 to unlock bootloader (because verizon edition pixel)
-> download NDE63X image from google and modified flash_all.sh to flash stock images to both slots manually
using the --slot _a/_b and --skip-secondary flags. Modified scripts below. At this point I confirmed that I could boot to both slots. I also verified bootloader lock/unlock again to make sure it was stock image on both slots
-> TWRP alpha2 to get recovery
-> with slot _b selected as active in TWRP, i installed the SuperSU v2.78 SR4 zip
voila, I now have stock on slot _a and rooted on slot _b
Although, I got this to work it still falls short of what I really wanted to do. For my use-case I would really want an isolated userdata for the two slots so I can use the rooted slot as a complete sandbox. and then perhaps have a shared folder mechanism between the two.
flash_all_slot-a.sh
flash_all_slot-b.sh
Click to expand...
Click to collapse
That is awesome and is exactly what I wanted to do. What I had tried doing was my original stock ROM was in slot A and I tried to fastboot another stock image into slot B. It immediately went into a boot loop in slot B. When I tried booting back to slot A, it also went into boot loop. Upon going into twrp, I found my system partition refused to mount. After several reboots and reinstalls of a backup I had done before I started playing with it, I got it to boot up again, but it was a brand new image instead of the backup which I tried to install. Upon the next reboot, both system and vendor would not mount, which is when I had enough and fastbooted the entire stock image.
Upon looking back at your modifications, I am curious if what happened is the stock image tried first to load into slot A even though I was in slot B, thus corrupting both my slots. Since the slot A I had at the time was rooted with EX kernel, flashing stock directly over it with no wipe is going to cause issues. I will try your changes tonight and get back to you with the results.
unless you use --skip-secondary, you are bound to affect the other slot while updating one. That is the standard behavior of the dual slot update process. If you see inside the update image, there is a system_other.img that gets flashed to the other slot. you can see that on the log output of the flash scripts too.
I found this article on the dual slot design very useful in understanding this.
Also make sure you are using the latest version adb and fastboot (I am using the latest that got updated with android studio/sdk bundle). I ran into some trouble earlier when I was using an older version of fastboot
hucqym said:
unless you use --skip-secondary, you are bound to affect the other slot while updating one. That is the standard behavior of the dual slot update process. If you see inside the update image, there is a system_other.img that gets flashed to the other slot. you can see that on the log output of the flash scripts too.
I found this article on the dual slot design very useful in understanding this.
Also make sure you are using the latest version adb and fastboot (I am using the latest that got updated with android studio/sdk bundle). I ran into some trouble earlier when I was using an older version of fastboot
Click to expand...
Click to collapse
Thank you very much for the tips. I have the latest adb and fastboot already so I am fine there. It is exactly like you said though on making the flash not affect both slots at once. I had not done a whole lot of research on the new dual slot setup yet and was just fiddling with it to see if I could do it myself. I knew with the bootloader unlocked I could always flash it back to stock with fastboot if I soft bricked it. I am going to look up that article tonight before I do the dual boot setup for myself. Never hurts to learn a bit more.
Does flashing bootloader remove TWRP? Or is that only in recovery?
Conchors said:
Does flashing bootloader remove TWRP? Or is that only in recovery?
Click to expand...
Click to collapse
flashing using my modified flash_all.sh does remove TWRP in the selected slot. You still can have TWRP in the other slot.
However, this is all of limited use, given SafetyNet now triggers false on even unlocked bootloader. Sigh!
hucqym said:
flashing using my modified flash_all.sh does remove TWRP in the selected slot. You still can have TWRP in the other slot.
However, this is all of limited use, given SafetyNet now triggers false on even unlocked bootloader. Sigh!
Click to expand...
Click to collapse
If I can reinstall TWRP than it shouldnt be an issue. Also, I'm running unlocked with the ElementX Kernel on my current setup and it keeps safetynet from triggering. My plan is to setup dual boot so I can have one slot for the un-rooted EX kernel for safetynet stuff and Root on the other slot.
Conchors said:
If I can reinstall TWRP than it shouldnt be an issue. Also, I'm running unlocked with the ElementX Kernel on my current setup and it keeps safetynet from triggering. My plan is to setup dual boot so I can have one slot for the un-rooted EX kernel for safetynet stuff and Root on the other slot.
Click to expand...
Click to collapse
ahaa. I must check out this EX kernel thingy then.
yes you can get TWRP back on both slots, no problem. tried and tested
hucqym said:
ahaa. I must check out this EX kernel thingy then.
yes you can get TWRP back on both slots, no problem. tried and tested
Click to expand...
Click to collapse
http://forum.xda-developers.com/pixel/development/kernel-elementalx-p-0-04-t3490086 That's for the small one.
Cool. Thanks! I'll give it a shot soon. I've got slot_a set up how i want, so I'll just flash b and su on that.
Conchors said:
http://forum.xda-developers.com/pixel/development/kernel-elementalx-p-0-04-t3490086 That's for the small one.
Cool. Thanks! I'll give it a shot soon. I've got slot_a set up how i want, so I'll just flash b and su on that.
Click to expand...
Click to collapse
your suggestion to install EX kernel worked. my SlotA now passes SafetyNet and androidpay works. Thanks
hucqym said:
your suggestion to install EX kernel worked. my SlotA now passes SafetyNet and androidpay works. Thanks
Click to expand...
Click to collapse
No prob. Thanks for the dual boot tutorial yourself
Update: I now have full dual boot on my phone. Once I became familiar with the slot command in fastboot, I see how easy it was to get it working. It is nice having the best of both worlds.
Following. Stock rooted with ElementalX kernel right now.
Don't care about Safetynet or Android Pay. Once more roms become available I'd like to dual boot 2 totally different roms.... Because Android.
Great info so far guys!
Sent from my Pixel using Tapatalk
Hey guys, since TWRP is capable of switching slots, couldn't we just make a full backup, switch slots, restore the backup, and reboot? Then you can go back and flash a rom or whatever to that slot.
Would any partitions be missing by doing this?
Sent from my Pixel using Tapatalk
Hey followers of this thread,. I just posted a new topic Here ,. and was wondering what solutions you all are using.
I thought SuperSU was made to install to both slots when flashed in TWRP? Or are you just using the boot to root method?
Hey, I'm just going through that dual boot thread and was wondering if you've come across any issues yet. I'm looking to have one rooted slot and one unrooted. I would like to have one stock slot in case I need safety net for an app like Android pay. The rooted for my many rooted apps and flashing Roms (if I can unlock bootloader and accomplish both objectives!). That's the idea, but just wanted to get any insight on how it has been working out and any major issues thus far.
Thanks a lot for the info in the thread thus far anyway.
zaksimmermon said:
I thought SuperSU was made to install to both slots when flashed in TWRP? Or are you just using the boot to root method?
Click to expand...
Click to collapse
Nope, TWRP installs to both slots, SuperSU will install to whichever boot slot is currently active. Same as Elemental-X kernel for instance.
Are there separate data partitions for each slot that contain user apps and app data or do the slots share that partition?
Shared would be great for a root/non root version of same rom but I could see that causing problems switching between custom Roms or different Android versions (similar to a dirty flash)...
Sent from my Pixel using Tapatalk
I've only recently bought the OnePlus 6; maybe a month or so ago. So, I had the Havoc ROM installed earlier and when i tried to update it with the new version, i got the crashdump mode. I'm not sure what i did wrong, but whatever.
I downloaded the flashboot Pie OTA and installed it, and was able to boot it. I then went back into fastboot and booted up the blu_spark twrp and did a data wipe and installed Havoc and twrp again. and it installed successfully and when i tried to restart recovery, i keep getting a blank screen with the white led light. I googled that and it looks like a kernel issue or whatever. But I'm having trouble figuring out how to fix it. I can't seem to load my Slot A at all. Whenever i switch to slot A, i get the blank screen with the white led, but i restart into fastboot and switch my slot to B, it loads up the Pie OTA.
Is there something I can do to fix this? Or my slot A is just broken from day 1 and i never realized it?
you need pie fw on both slots before flashing a custom pie rom!
flash pie+twrp
reboot twrp and flash pie+twrp
reboot twrp and flash havoc+twrp
reboot twrp and flash others(i.e. gapps+magisk)
reboot system and you should be up and running
https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
snigor said:
you need pie fw on both slots before flashing a custom pie rom!
flash pie+twrp
reboot twrp and flash pie+twrp
reboot twrp and flash havoc+twrp
reboot twrp and flash others(i.e. gapps+magisk)
reboot system and you should be up and running
https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
Click to expand...
Click to collapse
the flashboot OTAs flash pie on both slots. I went through the batch commands and its flashing boot_a and boot_b, system_a and system_b. I'm talking about the fastboot OTAs found here https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
alienwolf426 said:
the flashboot OTAs flash pie on both slots. I went through the batch commands and its flashing boot_a and boot_b, system_a and system_b. I'm talking about the fastboot OTAs found here https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
oh, right.. my bad! did you test both slots with only pie?
So, an update in case someone else has this issue with a busted slot and they want to fix it.
I had to download the unbrick tool from here https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
I ran that, and installed the OxygenOS Pie OB4 (but i guess it can work with whatever pie build) on both slot A and B.
And that fixed it.
I guess, what may have broken the slots for me was that i installed official TWRP and blu_spark TWRP, which probably fked up the boot image.
Not the slot that got ****ed up,it was you that didn't read and follow the guide. It's important to follow the steps when flashing custom ROMs. So,from TWRP you shouöd have flashed pie firmware 2 times. (Yes it says it's flashed to a and b,that is not the case still...that's why the guide tells you to do what it tells you to do) also the TWRP thing is incorrect,but whatever floats your boat.
I've read about some bug on the latest MIUI that makes Magisk bootloop, but I don't know if that means we cant currently root. Any help is appreciated
Spaghetticus said:
I've read about some bug on the latest MIUI that makes Magisk bootloop, but I don't know if that means we cant currently root. Any help is appreciated
Click to expand...
Click to collapse
Chinese ROM on global phone will give you bootloop, probably other way around as well
What if I'm on a global device on its stock software?
Spaghetticus said:
What if I'm on a global device on its stock software?
Click to expand...
Click to collapse
Should be fine. If it bootloops just uninstall magisk
Mackay53 said:
Should be fine. If it bootloops just uninstall magisk
Click to expand...
Click to collapse
So just install magisk through twrp? On latest MIUI?
Oh, it shouldn't wipe my phone right? Sorry just came back to Android after several months.
Install magisk 17.3 via TWRP, work fine.
Spaghetticus said:
So just install magisk through twrp? On latest MIUI?
Oh, it shouldn't wipe my phone right? Sorry just came back to Android after several months.
Click to expand...
Click to collapse
No need to wipe, either go to twrp - advanced - install root OR flash the magisk 17.1 or 17.3 zip.
Hey guys, I am very new to Android since i switched from iPhones now to the Mi Mix 3 (EU Version). I unlocked the bootloader already and have the adb drivers installed and when I try to boot into TWRP using "fastboot flash recovery TWRP.img" into "fastboot boot TWRP.img" it will boot back into MIUI. I also tried some methods mentioned in various forums like
"1. Put phone in the fastboot mode (switch it off, then press and hold power + volume down for a couple of seconds)
2. Flash twrp through fastboot (fastboot flash recovery twrp.img)
3. Boot TWRP (fastboot boot twrp.img)
4. When phone screen become black, hold power + volume up until it vibrate then release all
5. The phone will boot into twrp "
but I never get the phone to go into the TWRP recovery mode. It either boots back into MIUI or into the MIUI Fastboot screen. Has anyone an idea? Should I try to reinstall the drivers or what could be the issue?
Thanks a lot in advance!!
Flashing TWRP
I had a similar issue (could not boot into recovery after flashing TWRP)
Rename twrp.whatever.img to "recovery.img", then,
fastboot flash recovery recovery.img
Magisk 19 works perfect also
I flashed International Firmware
I flashed DP3
OEM UNLOCKED (No Service--- Expected)
Ok now I need to flash a custom rom to get service back which means... flashing TWRP....
Try booting TWRP img nope doesn't work
I talk to people in TWRP they said its because fastboot commands arn't present on DP3 and to download magisk manager and patch a stock boot img.
Grabbed stock IMG from 9.5.10: https://androidfilehost.com/?w=files&flid=294812
moved to Phone, Patched with Magisk Manager, Moved back to pc
adb reboot fastboot
fastboot boot magisk_patched.img (FAILED)
fastboot flash boot magisk_patched.img (Successful)
fastboot reboot
Bootloader (select start option)
Loops into bootloader
Select Recovery
Loops into bootloader
I am literally losing my mind.
I've been trying to get TWRP/ROOT for almost 4 hours I'm starting to Crack someone please dear god help me.
Did you try msm back to stock and start over?
Its a bit of extra work, but it usually works for a non-expert like me when I'm beyond my knowledge.
Also, iirc there's no reason to flash magisk if you're going to flash twrp cuz twrp unroots the device?
I would try msm back to international > unlock bootloader > fastboot flash boot twrp.img > flash twrp installer in twrp > flash magisk in twrp > flash your new rom in twrp.
sydsick42069 said:
Did you try msm back to stock and start over?
Its a bit of extra work, but it usually works for a non-expert like me when I'm beyond my knowledge.
Also, iirc there's no reason to flash magisk if you're going to flash twrp cuz twrp unroots the device?
I would try msm back to international > unlock bootloader > fastboot flash boot twrp.img > flash twrp installer in twrp > flash magisk in twrp > flash your new rom in twrp.
Click to expand...
Click to collapse
You can't flash TWRP from adb on DP3
:/ gives error command
Virus1x said:
You can't flash TWRP from adb on DP3
:/ gives error command
Click to expand...
Click to collapse
So as said before use the msm download tool and start over
Virus1x said:
You can't flash TWRP from adb on DP3
:/ gives error command
Click to expand...
Click to collapse
Right, that's why I was suggesting you msm back to international which would put you on 9.5.3(?)
From there you can unlock your boot loader, flash twrp and magisk, and then flash your rom
https://forum.xda-developers.com/oneplus-7-pro/how-to/how-to-convert-tmobile-op7-to-t3935947
sydsick42069 said:
Right, that's why I was suggesting you msm back to international which would put you on 9.5.3(?)
From there you can unlock your boot loader, flash twrp and magisk, and then flash your rom
https://forum.xda-developers.com/oneplus-7-pro/how-to/how-to-convert-tmobile-op7-to-t3935947
Click to expand...
Click to collapse
Unless your using DP3
so even though I can be on international, Without DP3 you can't bootloader unlock.
You can't unlock the bootloader on T-Mobile phones.
Virus1x said:
Unless your using DP3
so even though I can be on international, Without DP3 you can't bootloader unlock.
You can't unlock the bootloader on T-Mobile phones.
Click to expand...
Click to collapse
I'm not sure where you got that info, but it's definitely wrong.
Tmobile has a standard unlocking procedure, or you can utilize something like this or this if your device is not paid off yet.
However... if you are attempting the dp3 unlock method found here, and as of right now you are still locked, its because you skipped the actual unlock procedure. Which is literally steps 1 & 2 in this guide, attached in the previous dp3 unlock guide.
https://forum.xda-developers.com/on...obile-one-plus-7-pro-msm-tool-revert-t3936528
Step 1- Download the file in the original post, create a folder somewhere you know where it is and extract the downloaded files to that folder
Step 2-Turn off your OP7 Pro
Step 3-Open the folder you created and right click on MsMDownloadTool V4.0.88.exe and select run as administrator, Once open uncheck sha256 check.
Step 4-Plug the Original USB cable that came with your phone into the phone.
Step-5-Hold the Power/Volume up/Volume down button until you see Connected in MsMDownloadTool, the instant you see Connected press start. You only have 5 seconds before it's too late so be quick.
Step-6 Once you see "Download Complete" in green in the Status of Communication box in MsMDownloadTool the phone will automatically reboot and you should have the TMobile splash screen and be able to set the phone up through the set up Wizard.
If you want to use Android 10 with service working on your T-Mobile 7 Pro you NEED to be SIM unlocked.
sydsick42069 said:
From there you can unlock your boot loader, flash twrp and magisk, and then flash your rom
Click to expand...
Click to collapse
That process doesn't work for Android 10 (OB1 and OB2). With OB1/2 the fastboot boot command doesn't work yet (similar to all the 7 Pro devices when it was first released). As the top poster already mentioned the correct method to get TWRP on the device is to flash a patch boot image. Form there, he can flash TWRP within Magisk.
redpoint73 said:
That process doesn't work for Android 10 (OB1 and OB2). With OB1/2 the fastboot boot command doesn't work yet (similar to all the 7 Pro devices when it was first released). As the top poster already mentioned the correct method to get TWRP on the device is to flash a patch boot image. Form there, he can flash TWRP within Magisk.
Click to expand...
Click to collapse
"From that point" would have been 9.5.3 international not 10, and I was assuming he was already carrier unlocked.
Virus1x said:
You can't flash TWRP from adb on DP3
:/ gives error command
Click to expand...
Click to collapse
Right. What you need to do now is download the full latest ota, put it on root of storage. Do local upgrade. After it will boot into stock recovery do a full wipe. Reboot. Then you can install twrp, magisk..ect
This way worked for me ^
(I'm not sim unlocked btw)
If you use msm it will relock your bootloader!
JWnSC said:
Right. What you need to do now is download the full latest ota, put it on root of storage. Do local upgrade. After it will boot into stock recovery do a full wipe. Reboot. Then you can install twrp, magisk..ect
This way worked for me ^
(I'm not sim unlocked btw)
If you use msm it will relock your bootloader!
Click to expand...
Click to collapse
Is there some benefit to keeping the sim locked? Getting the sim unlocked is so easy. Then you don't have to worry about the bootloader relocking, cuz you can just fastboot unlock it.
sydsick42069 said:
Is there some benefit to keeping the sim locked? Getting the sim unlocked is so easy. Then you don't have to worry about the bootloader relocking, cuz you can just fastboot unlock it.
Click to expand...
Click to collapse
No, no benefit. Less headache actually, no need to flash dp3 if sim unlocked already
JWnSC said:
No, no benefit. Less headache actually, no need to flash dp3 if sim unlocked already
Click to expand...
Click to collapse
Exactly, like why go through the trouble of using certain methods of upgrading, etc. to avoid relocking If you can just go to one of the unlocking threads on xda, or just talk to TMobile support on Twitter and get sim unlocked. Like the whole process took me 30 minutes and now I don't have to worry about it because it's officially unlocked. Like, I've had my **** in a boot loop a few times, and being able to msm all the way back to stock and reunlock etc is extremely useful.
Virus1x said:
I flashed International Firmware
I flashed DP3
OEM UNLOCKED (No Service--- Expected)
Ok now I need to flash a custom rom to get service back which means... flashing TWRP....
Try booting TWRP img nope doesn't work
I talk to people in TWRP they said its because fastboot commands arn't present on DP3 and to download magisk manager and patch a stock boot img.
Grabbed stock IMG from 9.5.10: https://androidfilehost.com/?w=files&flid=294812
moved to Phone, Patched with Magisk Manager, Moved back to pc
adb reboot fastboot
fastboot boot magisk_patched.img (FAILED)
fastboot flash boot magisk_patched.img (Successful)
fastboot reboot
Bootloader (select start option)
Loops into bootloader
Select Recovery
Loops into bootloader
I am literally losing my mind.
I've been trying to get TWRP/ROOT for almost 4 hours I'm starting to Crack someone please dear god help me.
Click to expand...
Click to collapse
Download something called "minimal adb and fastboot" (don't have the link handy) and use that fastboot to do the following:
fastboot getvar current-slot
Whichever slot it shows, a or b, you want to switch to the other. So if it says the current slot is A, you would type
fastboot --set-active=b
And if it says slot B, then you want to set A as active slot. Then after it successfully changes slots
fastboot reboot-bootloader
Now when you're back to the fastboot screen after your phone reboots, the fastboot boot command on your twrp img should work fine.
Sent from my OnePlus7Pro using XDA Labs
I installed the Stable Android 10 on my GM1910 via TWRP, totally forgetting about maintaining root and TWRP.
So how do I bring back TWRP and root?
fastboot boot doesn't seem to work, I managed to pull the boot.img and patch it with Magisk from another device but flashing it through fastboot ends up in an endless bootanimation.
Could anyone help me? here's a link of the boot.img i pulled, it works if you flash it without magisk patching it.
Link: https://drive.google.com/file/d/1O8lF1UDwwu0zT8ro5Q1gKKfdxF-HGPEW/view?usp=sharing
(Almost) exactly the same here. I tired flashing a patched boot.img, it actually boots - but magisk manager gets stuck on the splash screen and some apps, including chrome, won't start. Trying to boot TWRP results in the phone getting stuck on the "fastboot mode" screen.
My only solution would be to downgrade, root, keep the upgrade this time. But because my ISP is doing some maintenance work I don't have wifi - and restoring my phone through mobile data does not seem to work correctly.
EDIT: In fastboot, neither bootloader version nor baseband version are show, product name is "msmnile". Has this always been that way?
EDIT 2, solution:
I extracted the boot.img from the device, and patched it using magisk on the same phone:
https://drive.google.com/file/d/1-Gf-6iXSFuYT5xDR-mnLKANvkXUHal9e/view?usp=sharing
Run this command in fastboot so you know which is the CURRENT active slot :
Code:
fastboot getvar current-slot
Run this command so you can flash the correct slot :
Code:
fastboot flash boot_X magisk_patched.img
replace X with the a or b from the command before.
:good:
dmj0shu4 said:
I installed the Stable Android 10 on my GM1910 via TWRP, totally forgetting about maintaining root and TWRP.
So how do I bring back TWRP and root?
fastboot boot doesn't seem to work, I managed to pull the boot.img and patch it with Magisk from another device but flashing it through fastboot ends up in an endless bootanimation.
Could anyone help me? here's a link of the boot.img i pulled, it works if you flash it without magisk patching it.
Link: https://drive.google.com/file/d/1O8lF1UDwwu0zT8ro5Q1gKKfdxF-HGPEW/view?usp=sharing
Click to expand...
Click to collapse
Hi sorry to hear that you got this problem and hopefully it gets fixed. I have another question: does that mean using TWRP to completely clean the device then installing Android 10 via zip will remove TWRP and fastboot everything? Does that mean after installing, everything will be refreshed like a box opened phone?
dmj0shu4 said:
I installed the Stable Android 10 on my GM1910 via TWRP, totally forgetting about maintaining root and TWRP.
So how do I bring back TWRP and root?
fastboot boot doesn't seem to work, I managed to pull the boot.img and patch it with Magisk from another device but flashing it through fastboot ends up in an endless bootanimation.
Could anyone help me? here's a link of the boot.img i pulled, it works if you flash it without magisk patching it.
Link: https://drive.google.com/file/d/1O8lF1UDwwu0zT8ro5Q1gKKfdxF-HGPEW/view?usp=sharing
Click to expand...
Click to collapse
If you have an endless boot animation you might be trying to boot from the wrong slot, try using the fastboot set_active command to change slot, then restart
h0l said:
Run this command in fastboot so you know which is the CURRENT active slot :
Run this command so you can flash the correct slot : replace X with the a or b from the command before.
:good:
Click to expand...
Click to collapse
I got a bit confused.
If the current slot is boot_a, i flash it in boot_b or am I supposed to flash on the one that isn't the current slot?
djsubterrain said:
If you have an endless boot animation you might be trying to boot from the wrong slot, try using the fastboot set_active command to change slot, then restart
Click to expand...
Click to collapse
Which is the default active slot? Is it okay to use either of the 2?
dmj0shu4 said:
Which is the default active slot? Is it okay to use either of the 2?
Click to expand...
Click to collapse
Either one should work if the rom and the rooted boot image is on it (If you are rooting). That's why you should install using TWRP, if you look in the reboot menu it will show you the active slot.
djsubterrain said:
Either one should work if the rom and the rooted boot image is on it (If you are rooting). That's why you should install using TWRP, if you look in the reboot menu it will show you the active slot.
Click to expand...
Click to collapse
I would've used TWRP but it won't let me boot into it
fastboot boot [recovery.img] does not seem to work for android 10, atleast on my case
dmjoshu4 said:
I got a bit confused.
If the current slot is boot_a, i flash it in boot_b or am I supposed to flash on the one that isn't the current slot?
Click to expand...
Click to collapse
You are supposed to flash it in the one that IS the active one. Because you do want to root the slot that you'll be booting.
does that mean using TWRP to completely clean the device then installing Android 10 via zip will remove TWRP and fastboot everything? I.e. everything will be refreshed like a box opened phone?
gh279760559 said:
does that mean using TWRP to completely clean the device then installing Android 10 via zip will remove TWRP and fastboot everything? I.e. everything will be refreshed like a box opened phone?
Click to expand...
Click to collapse
not everything, just twrp and root will be gone if you restarted without installing magisk to the inactive slot
h0l said:
(Almost) exactly the same here. I tired flashing a patched boot.img, it actually boots - but magisk manager gets stuck on the splash screen and some apps, including chrome, won't start. Trying to boot TWRP results in the phone getting stuck on the "fastboot mode" screen.
My only solution would be to downgrade, root, keep the upgrade this time. But because my ISP is doing some maintenance work I don't have wifi - and restoring my phone through mobile data does not seem to work correctly.
EDIT: In fastboot, neither bootloader version nor baseband version are show, product name is "msmnile". Has this always been that way?
EDIT 2, solution:
I extracted the boot.img from the device, and patched it using magisk on the same phone:
https://drive.google.com/file/d/1-Gf-6iXSFuYT5xDR-mnLKANvkXUHal9e/view?usp=sharing
Run this command in fastboot so you know which is the CURRENT active slot :
Code:
fastboot getvar current-slot
Run this command so you can flash the correct slot :
Code:
fastboot flash boot_X magisk_patched.img
replace X with the a or b from the command before.
:good:
Click to expand...
Click to collapse
dude, thanks for this, i was banging my head against a wall trying to get root to work. I used your patched boot img and i had the version mismatch, but i local updated my android and it has root!
dmj0shu4 said:
I would've used TWRP but it won't let me boot into it
fastboot boot [recovery.img] does not seem to work for android 10, atleast on my case
Click to expand...
Click to collapse
I have not been able to boot TWRP either in fastboot mode - got stuck at "OnePlus Logo FastBoot" black screen.
Hi guys.. can you post the steps in rooting android 10??
I've already had bootloader unlocked.
Do i need to.follow the steps intended for android 9??
Like
1. Install TWRP via fastboot.. (2files)
2. Reboot to twrp.
3. Flash magisk via twrp??
Is that it?? If so. Then after reading this thread.. some of. You mentioned about boot. Img?? Patched?? What's that supposed to mean?? Sir??
Thanks. Any advice is highly appreciated..
---------- Post added at 08:30 AM ---------- Previous post was at 08:28 AM ----------
And by the way..
Im on Gm1910 model. Global rom. Gm21AA build.. if that info would matter.. i dont actually need the root on android 9. Coz parallel app is working.. but now in android 10. It isnt working.. so.i need to root to grant su to game guardian.. thanks..
MigbyPie said:
I have not been able to boot TWRP either in fastboot mode - got stuck at "OnePlus Logo FastBoot" black screen.
Click to expand...
Click to collapse
Same.
I've read that Q/10 is different and you can't install TWRP like that anymore. Supposedly you need to use the MSM tool or the all-in-one tool but I've tried both of those and still can't boot to TWRP.
E30Nova said:
Same.
I've read that Q/10 is different and you can't install TWRP like that anymore. Supposedly you need to use the MSM tool or the all-in-one tool but I've tried both of those and still can't boot to TWRP.
Click to expand...
Click to collapse
Hopefully there will be a solution. I had tried to update from Pie to Q10 while staying rooted and it didn't work. So I had to wipe the whole device and decided to wait for a smoother root method for my device. If you have any other ideas about rooting Q10 let me know. Thank you
h0l said:
(Almost) exactly the same here. I tired flashing a patched boot.img, it actually boots - but magisk manager gets stuck on the splash screen and some apps, including chrome, won't start. Trying to boot TWRP results in the phone getting stuck on the "fastboot mode" screen.
My only solution would be to downgrade, root, keep the upgrade this time. But because my ISP is doing some maintenance work I don't have wifi - and restoring my phone through mobile data does not seem to work correctly.
EDIT: In fastboot, neither bootloader version nor baseband version are show, product name is "msmnile". Has this always been that way?
EDIT 2, solution:
I extracted the boot.img from the device, and patched it using magisk on the same phone:
https://drive.google.com/file/d/1-Gf-6iXSFuYT5xDR-mnLKANvkXUHal9e/view?usp=sharing
Run this command in fastboot so you know which is the CURRENT active slot :
Code:
fastboot getvar current-slot
Run this command so you can flash the correct slot :
Code:
fastboot flash boot_X magisk_patched.img
replace X with the a or b from the command before.
:good:
Click to expand...
Click to collapse
You saved my life! Thank you!
But how do we get twrp now? Is there any way?
Me too. Use tool all in one but it doesnt work. Stuck at "waiting twrp boots".
Any help, thanks.
Same here any Solution?
Sent from my GM1911 using Tapatalk
---------- Post added at 08:14 AM ---------- Previous post was at 08:14 AM ----------
Stuck at Fastboot booting when flashed img and also zip
Sent from my GM1911 using Tapatalk
I updated my phone to 10 last night, followed the same guide as I have for every other update but this time I lost root for some reason.
I still have TWRP recovery on there but it can't read internal storage so I can't flash Magisk.
I tried changing file system to ext 2 then back to 4 and then repairing it as I read elsewhere and this wiped the phone obviously but internal storage seemed to be working until I set the phone up again, downloaded Magisk, rebooted to recovery and I'm back where I started, internal storage showing as 0mb in TWRP.
Any ideas how to fix?