Yestaday I upgrade Oneplus 8 IN2010 OxygenOS International to 11 and working just fine
But I regret it because there is no root
So I flash official rollback package from:https://forums.oneplus.com/threads/oxygenos-11-for-the-oneplus-8-pro-and-oneplus-8.1312654/
After local package flash,I reboot my phone and this thing happened
When it displays the oneplus logo, it becomes a black screen instead of a boot animation
I tried using twrp to flash OxygenOS,no error but still black screen
I tried many different versions with MSM tool
But there is no way to solve my problem
I tried to talk to oneplus service staff online
But because I was in Taiwan, they couldn’t perform the session with China region?
Taiwan is not even part of China!(Digress
Anyway, I regret disappointed and sad now
I really hope I can save my phone :crying:
I had a similar problem and fixed it this way, you can check if you have a bootable image in the alternative 'slot' (A/B):
Code:
1. start in fastboot mode
2. command: [I]fastboot getvar current-slot[/I]
3. note current slot (A or B)
4. change slot
5. command: [I]fastboot --set-active=a[/I] [B]OR[/B] [I]fastboot --set-active=b[/I] <- you want to change from your current slot
6. command: [I]fastboot reboot[/I]
You need an unlocked bootloader to change slots manually.
djmcnz said:
I had a similar problem and fixed it this way, you can check if you have a bootable image in the alternative 'slot' (A/B):
Code:
1. start in fastboot mode
2. command: [I]fastboot getvar current-slot[/I]
3. note current slot (A or B)
4. change slot
5. command: [I]fastboot --set-active=a[/I] [B]OR[/B] [I]fastboot --set-active=b[/I] <- you want to change from your current slot
6. command: [I]fastboot reboot[/I]
You need an unlocked bootloader to change slots manually.
Click to expand...
Click to collapse
Thanks for your help but MSM tool locked my bootloader
I don't know what to do now
Maybe wait for OxygenOS 11 MSM tool have the opportunity to fix it
oliver802 said:
Thanks for your help but MSM tool locked my bootloader
I don't know what to do now
Maybe wait for OxygenOS 11 MSM tool have the opportunity to fix it
Click to expand...
Click to collapse
Can you access fastboot? If so...
Code:
command: [I]fastboot oem unlock[/I]
First of all there is root on oos11, there is a magisk guide here on the forum, i did it myself & flashed magisk & was able to gain root access & installed custom kernel too
luscharsch said:
First of all there is root on oos11, there is a magisk guide here on the forum, i did it myself & flashed magisk & was able to gain root access & installed custom kernel too
Click to expand...
Click to collapse
I know but too late
djmcnz said:
I had a similar problem and fixed it this way, you can check if you have a bootable image in the alternative 'slot' (A/B):
Code:
1. start in fastboot mode
2. command: [I]fastboot getvar current-slot[/I]
3. note current slot (A or B)
4. change slot
5. command: [I]fastboot --set-active=a[/I] [B]OR[/B] [I]fastboot --set-active=b[/I] <- you want to change from your current slot
6. command: [I]fastboot reboot[/I]
You need an unlocked bootloader to change slots manually.
Click to expand...
Click to collapse
Thanks, I can boot to slot b and have crash dump on slot a, can't recognise in MSM and reluctant to use it after doing the rollback from A11 as afraid to lock the bootloader without successfully restoring as happened to OP
xdtyui said:
Thanks, I can boot to slot b and have crash dump on slot a, can't recognise in MSM and reluctant to use it after doing the rollback from A11 as afraid to lock the bootloader without successfully restoring as happened to OP
Click to expand...
Click to collapse
If you can boot for either slot you're fine, don't worry about the other, if you have a bootable slot you can recover to a factory image from it, you don't need to rely on the other (non-bootable) slot.
djmcnz said:
Can you access fastboot? If so...
Code:
command: [I]fastboot oem unlock[/I]
Click to expand...
Click to collapse
FAILED (remote: 'Flashing Unlock is not allowed')
djmcnz said:
If you can boot for either slot you're fine, don't worry about the other, if you have a bootable slot you can recover to a factory image from it, you don't need to rely on the other (non-bootable) slot.
Click to expand...
Click to collapse
Yeah thanks, I have a factory image on b so is it alright that a boots to crash dump? Could that be a problem in the future?
xdtyui said:
Yeah thanks, I have a factory image on b so is it alright that a boots to crash dump? Could that be a problem in the future?
Click to expand...
Click to collapse
That's okay. Often the alternative slot is unbootable. The next time you do a system update it will make the alternative slot bootable and boot from there.
---------- Post added at 12:59 ---------- Previous post was at 12:56 ----------
oliver802 said:
FAILED (remote: 'Flashing Unlock is not allowed')
Click to expand...
Click to collapse
Okay, if you can't unlock the bootloader, can't get into EDL mode and you can't use ADB then you need to chat with OP technical support again and hope they can help.
djmcnz said:
That's okay. Often the alternative slot is unbootable. The next time you do a system update it will make the alternative slot bootable and boot from there.
---------- Post added at 12:59 ---------- Previous post was at 12:56 ----------
Okay, if you can't unlock the bootloader, can't get into EDL mode and you can't use ADB then you need to chat with OP technical support again and hope they can help.
Click to expand...
Click to collapse
I can get into EDL mode and no error on MSM tool
But I have tried flashing with MSM tool, it shows that the flashing is successful and the Bootloader is also locked.
But I still can’t enter the system
In addition, flashing the version before instantnoodle_15_O.20_200716 will enter Qualcomm Dump mode
I used to suffer like you on oxygenos 11. Maybe you haven't installed Qualcomm HS-USB correctly. You should reinstall many times to wish you success.
Make sure it's latest MSMtool, that was the issue for me. Also can you get to the other slot? If so you can boot there and enable OEM unlocking from there, than unlock in fastboot.
greendragon527 said:
Make sure it's latest MSMtool, that was the issue for me. Also can you get to the other slot? If so you can boot there and enable OEM unlocking from there, than unlock in fastboot.
Click to expand...
Click to collapse
Unfortunately, because the bootloader of my device is locked by MSMtool, I can't switch partitions
Not sure if this is helpful, but I had trouble getting MSM to work after upgrading to OOS11 because I couldn't get into EDL mode. Something changed with boot in OOS11 so the normal up+down key combination didn't work it just always put me into fastboot. 'adb reboot edl' didn't work either it just went into fastboot. What I finally found that worked was a patched version of fastboot.exe that has the reboot-edl command. After that I was able to MSM successfully.
Here's the patched fastboot I used: https://forum.xda-developers.com/an.../guide-how-to-reboot-to-edl-fastboot-t3394292
I used the MSM tool of OxygenOS 11 to successfully repair my device
Thanks to everyone who helped me
oliver802 said:
I used the MSM tool of OxygenOS 11 to successfully repair my device
Thanks to everyone who helped me
Click to expand...
Click to collapse
Can you share the lino to MSM for 11 please
firoz3321 said:
Can you share the lino to MSM for 11 please
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4085877
I'm having same issue only fastboot and crashdump mode lol msm don't spot my phone probably too many other drivers I hold volume up and down for crash dump any ideas I've tried 11 no luck I updated to 11 using the oxygen updater
Related
Enchilada Partition Resizer for OnePlus 6!
What does this tool do? And what are the benefits? Well. This tool will resize Your system partition size to 6GB allowing You to flash any sGSI (some of them are huge) and my future roms that will require more than 3GB (2850mb roughly) system size. It's pretty problematic for many roms and I just delay them because of this.
DO NOT use it on 7 Pro, OP7 or anything else. (6T Tested and works)
I also added a backup feature of Your stock partition table just in case. Might be useful for some people.
Known Issues
You might get stuck in fastboot until You flash a ROM
How to Use:
MAKE SURE TO BACKUP EFS, DATA AND PERSIST (if possible) BEFORE USING IT!
Also make sure You're not currently using EPR! (If You already used 1.0 and Your system is still 6GB, no need for 2.0)
Boot into TWRP (Tested on BluSpark)
Flash EPR zip that matches Your storage
Reboot to bootloader (fastboot menu)
Run any force wipe flasher of a rom that You want to use.
Wait till it finishes flashing and done!
If You want to go back, simply flash EPR Remover and Format data + wipe system.
Download:
Enchilada Partition Resizer 2.0.1 TWRP Flashable
If You have any other problems, just ask here on XDA or for the fastest support PM me or ask someone in my group on Telegram
Join my group!
If You want to motivate me to work more, buy me a coffee!
https://www.paypal.me/protodevnano
Credits:
Alternative415 for testing 2.0 all day! :highfive:
Amir and Geci for testing and providing 256 and 64GB sizes!
Manan Gupta for Initial Windows version.
Adarsh for testing Windows version and having to use EDL 7 times
CosmicDan for original guide that helped me a lot!
OnePlus for creating OP6!
My friend Dylan for always supporting me
If I forgot anyone, just PM me on Telegram!
XDA:DevDB Information
Enchilada Partition Resizer, Tool/Utility for the OnePlus 6
Contributors
ProtoDeVNan0
Version Information
Status: Stable
Created 2019-09-01
Last Updated 2019-09-01
Changelog:
02.09.19 - Added Windows Support
22.03.20 - Corrected guide in EPR 2.
Added windows batch compatibility. Haven't tested on an android device but seems to work.
https://drive.google.com/file/d/1IS8cfD59okX9qwaXUKxxVQedNzmpHhmt/view?usp=sharing
its not working for me on windows. but thanks anywya
Can't get into TWRP after resizing (Windows) ?? Always reboot to bootloader.
EDIT ; Maybe doing wrong.. Will edit again soon.
WrathChild08 said:
Can't get into TWRP after resizing (Windows) ?? Always reboot to bootloader.
EDIT ; Maybe doing wrong.. Will edit again soon.
Click to expand...
Click to collapse
same for me. now im tring to unbrick my phone.
WrathChild08 said:
Can't get into TWRP after resizing (Windows) ?? Always reboot to bootloader.
EDIT ; Maybe doing wrong.. Will edit again soon.
Click to expand...
Click to collapse
synk48 said:
same for me. now im tring to unbrick my phone.
Click to expand...
Click to collapse
When You're in a fastboot lock, You have to check what partition is active and then set it as active again.
So on windows if You resize A. And end up in fastboot lock.
You should use
fastboot --set-active=
(It will show You current slot)
and then
fastboot --set-active=a
If Your slot is a.
I have no idea why this happens but oh well. One day we will have 3 slots so let's appreciate 2 :silly:
Gonna try this to install OP7 Android 10 Rom Port, thanks. I Was on it all night long wondering why I couldn't make it working.
EDIT : Still stuck in fastboot mode even after typing fastboot --set-active=a (I resized a, yep), can't go to recovery. But maybe it's related to Android Q ? was on Q DP3 before resizing. Or Maybe it's because the OP7 ROm Port is hard to install aha. After cheking, system is 6Gb size so I guess your software is okay.
WrathChild08 said:
Gonna try this to install OP7 Android 10 Rom Port, thanks. I Was on it all night long wondering why I couldn't make it working.
EDIT : Still stuck in fastboot mode even after typing fastboot --set-active=a (I resized a, yep), can't go to recovery. But maybe it's related to Android Q ? was on Q DP3 before resizing. Or Maybe it's because the OP7 ROm Port is hard to install aha. After cheking, system is 6Gb size so I guess your software is okay.
Click to expand...
Click to collapse
follow this steps
if you are stuck in bootloader bootloop do this
1. msm download tool than back to OOS 5.1.11
2. unlock bootloader
3. manual update to OOS Q DP3
4. install patched boot to get magisk without root there you can find partched boot.img https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
4. this step is because android Q dont let you boot to TWRP by bootloader
5. install TWRP Zip with magisk
6. boot to recovery and open ERP Script to resize your partition and chose partition a
7. in bootloader put fastboot set_active b and then boot to recovery
8. select partition a
9. do a factory reset, wipe data
10. boot to bootloader
11. open OP7 Android 10 Port scrip
12. in bootloader put fastboot set_active a
13. done
if you phone still doesnt boot go to bootloader set_active b go to recovery, chose partition a in twrp and do a factory reset and wipe data again and reinstall OP7 port.
is the only way its worked for me. i hope it works for you.
sorry about my english.
The command window just vanishes after typing in the partition and hitting enter. Have tried entering both `a` and `b` and even tried running the batch file as an administrator. Anyone else facing this issue on Windows?
you forgot to type 'system'
sahu.prashant said:
The command window just vanishes after typing in the partition and hitting enter. Have tried entering both `a` and `b` and even tried running the batch file as an administrator. Anyone else facing this issue on Windows?
Click to expand...
Click to collapse
you wrote system first and next the partition letter?
synk48 said:
you wrote system first and next the partition letter?
Click to expand...
Click to collapse
LMAO I feel stupid. I just typed in the letter. :silly:
synk48 said:
follow this steps
if you are stuck in bootloader bootloop do this
1. msm download tool than back to OOS 5.1.11
2. unlock bootloader
3. manual update to OOS Q DP3
4. install patched boot to get magisk without root there you can find partched boot.img https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
4. this step is because android Q dont let you boot to TWRP by bootloader
5. install TWRP Zip with magisk
6. boot to recovery and open ERP Script to resize your partition and chose partition a
7. in bootloader put fastboot set_active b and then boot to recovery
8. select partition a
9. do a factory reset, wipe data
10. boot to bootloader
11. open OP7 Android 10 Port scrip
12. in bootloader put fastboot set_active a
13. done
if you phone still doesnt boot go to bootloader set_active b go to recovery, chose partition a in twrp and do a factory reset and wipe data again and reinstall OP7 port.
is the only way its worked for me. i hope it works for you.
sorry about my english.
Click to expand...
Click to collapse
after step 3 fastboot commands dont work, flashing twrp fails
Makhosi Mayisa said:
after step 3 fastboot commands dont work, flashing twrp fails
Click to expand...
Click to collapse
i sent you a PM...
synk48 said:
i sent you a PM...
Click to expand...
Click to collapse
Can you share?
Rishwan said:
Can you share?
Click to expand...
Click to collapse
what do you need?
synk48 said:
what do you need?
Click to expand...
Click to collapse
Same as above. I get the same error. Can't make EPR work, I end up in bootloader bootloop.
Rishwan said:
Same as above. I get the same error. Can't make EPR work, I end up in bootloader bootloop.
Click to expand...
Click to collapse
tell me what are you doing? step by step
synk48 said:
tell me what are you doing? step by step
Click to expand...
Click to collapse
tried a lot of ways.
1) MSM to go to 9.0.8
2) unlock bootloader and install twrp
3) boot twrp (with 9.0.8)
4) install dp 3 + twrp, reboot to recovery and repeat for both slots
5) on slot A, run EPR
6) at fastboot with no other way except to use msm because no command (such as set_active) makes it boot. at this point, i can't even go to recovery/bokt recovery (as Q doesn't support boot command)
method 2)
repeat the same except i ran EPR with 9.0.8 same issue. goes to bootloader always
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?
Guys , I am new on Op7 , I had a stuck in fastboot because of unable to use boot command, then using msm tool I went back to 9.5.3 . I re did the unlock and then whenver I tried to install twrp using fastboot , it shows remote : unknown error
How I can install twrp and magisk ?? And update to 10 ?
I need step by step please . Considering I am on 9.5.3 OEM unlocked but I am unable to use fastboot boot option.
U can only install twrp through booted TWRP
also pie and q version of OOS need proper boot.img TWRP from this thread https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
new_world_2006 said:
Guys , I am new on Op7 , I had a stuck in fastboot because of unable to use boot command, then using msm tool I went back to 9.5.3 . I re did the unlock and then whenver I tried to install twrp using fastboot , it shows remote : unknown error
How I can install twrp and magisk ?? And update to 10 ?
I need step by step please . Considering I am on 9.5.3 OEM unlocked but I am unable to use fastboot boot option.
Click to expand...
Click to collapse
Upgrade to 10, then Root.
blas4me said:
Upgrade to 10, then Root.
Click to expand...
Click to collapse
So how i can root, if i have damaged fastboot boot command?
new_world_2006 said:
So how i can root, if i have damaged fastboot boot command?
Click to expand...
Click to collapse
First thing is to OTA update to anything other than 9.5.3. Seemed to me I remembered when I first got the device (many months ago) somebody mentioned there was a fastboot issue on 9.5.3. So just take whatever OTA is availabe to you. Probably 9.5.13
If you still can't boot the twrp.img after that then try manually changing the active slot in fastboot;
fastboot getvar current-slot *(take note of the current slot this command returns)*
fastboot --set-active= *(=a or =b to change slot to the opposite the first command returned)*
fastboot reboot bootloader
So you should end up with something like this;
fastboot --set-active=a
fastboot reboot bootloader
fastboot boot "C:\Adb\twrp-3.3.1-4-guacamole.img"
new_world_2006 said:
So how i can root, if i have damaged fastboot boot command?
Click to expand...
Click to collapse
Bootloader is not damaged, did you enable usb debugging.
Please read, most of us have been there, and a lot of us are coming from some other OnePlus device. Project treble was discussed a lot on 5T forums. If your bootloader detects custom firmware while locked, it will lock the phone. You can't run fastboot commands because you missed a step somewhere.
Hello wonderful xda peeps,
My
-
Mi A2
Running Android 10
xiaomi/jasmine/jasmine_sprout
10/QKQ1.190910.002/V11.0.5.0.QDIMIXM
is stuck in bootloop, how can I fix it or at least how do extract my files?
Thank you kind regards!
Micklo said:
Hello wonderful xda peeps,
My
-
Mi A2
Running Android 10
xiaomi/jasmine/jasmine_sprout
10/QKQ1.190910.002/V11.0.5.0.QDIMIXM
is stuck in bootloop, how can I fix it or at least how do extract my files?
Thank you kind regards!
Click to expand...
Click to collapse
What did you do before this happened? Is it your bootloader locked? Can you enter to recovery and/or fastboot?
SubwayChamp said:
What did you do before this happened? Is it your bootloader locked? Can you enter to recovery and/or fastboot?
Click to expand...
Click to collapse
Yes, I can enter Android Recovery and Fastboot.
Yes, the bootloader is locked.
I mistakenly clicked on "Run Graphics Test" in android recovery and it installed some update and my phone has been stuck eversince
Update
I've wiped my phone to factory reset and it is still stuck in bootloop
Micklo said:
Update
I've wiped my phone to factory reset and it is still stuck in bootloop
Click to expand...
Click to collapse
If you have enabled USB debugging and OEM unlock then you can unlock bootloader to get an easy way to send it to EDL mode and you can flash the stock ROM using MiFlash tool.
For future reference this is the first that any user have to do before to "play" with the device so you have more ways to recover it.
There is some probability that your device is trying to boot to the wrong slot, first update your platform-tools if needed https://developer.android.com/studio/releases/platform-tools then see if these commands work:
To identify your current slot type
Code:
fastboot getvar current-slot
then set as active the opposite slot with
Code:
fastboot --set-active=a
changing a for b as opposite slot
Also it exists this tool that can help you but you would need to previously enable USB debugging: https://www.xiaomitool.com/V2/ this tool allows adb (disabled by Xiaomi) to work through recovery stock.
In the case you can't unlock bootloader cause your USB debugging and OEM unlock were not previously toggled then you should have to use MiFlash tool through EDL mode using test point, also there is other tool called QFlash/Qfil.
SubwayChamp said:
If you have enabled USB debugging and OEM unlock then you can unlock bootloader to get an easy way to send it to EDL mode and you can flash the stock ROM using MiFlash tool.
For future reference this is the first that any user have to do before to "play" with the device so you have more ways to recover it.
There is some probability that your device is trying to boot to the wrong slot, first update your platform-tools if needed https://developer.android.com/studio/releases/platform-tools then see if these commands work:
To identify your current slot type
Code:
fastboot getvar current-slot
then set as active the opposite slot with
Code:
fastboot --set-active=a
changing a for b as opposite slot
Also it exists this tool that can help you but you would need to previously enable USB debugging: https://www.xiaomitool.com/V2/ this tool allows adb (disabled by Xiaomi) to work through recovery stock.
In the case you can't unlock bootloader cause your USB debugging and OEM unlock were not previously toggled then you should have to use MiFlash tool through EDL mode using test point, also there is other tool called QFlash/Qfil.
Click to expand...
Click to collapse
Thank you for your kind assistance.
Before it was stuck in boot loop:
- I enabled USB Debugging
- I did not enable OEM Unlocking
Using:
Code:
fastboot getvar current-slot
returned
Code:
current-slot: a
Now running
Code:
./fastboot --set-active=b
i got the following:
Code:
Setting current slot to 'b' FAILED (remote: 'Slot Change is not allowed in Lock State')
fastboot: error: Command failed
Micklo said:
Thank you for your kind assistance.
Before it was stuck in boot loop:
- I enabled USB Debugging
- I did not enable OEM Unlocking
Using:
Code:
fastboot getvar current-slot
returned
Code:
current-slot: a
Now running
Code:
./fastboot --set-active=b
i got the following:
Code:
Setting current slot to 'b' FAILED (remote: 'Slot Change is not allowed in Lock State')
fastboot: error: Command failed
Click to expand...
Click to collapse
You are using PowerShell, try to switch firstly to CMD and then type the commands but open it as admin, and check if you have the latest platform-tools.
Also check if the tool provided with link works for you and report back.
SubwayChamp said:
You are using PowerShell, try to switch firstly to CMD and then type the commands but open it as admin, and check if you have the latest platform-tools.
Also, check if the tool provided with link works for you and report back.
Click to expand...
Click to collapse
I am using the correct code because that's how you run the command on Linux or Mac. I'm on a Mac.
The tool did not work for me.
I can't upload an image here
Micklo said:
I am using the correct code because that's how you run the command on Linux or Mac. I'm on a Mac.
The tool did not work for me.
I can't upload an image here
Click to expand...
Click to collapse
I know this is the correct command just I thought you used PowerShell from a Windows some times give errors.
The tool by Francesco Tescari works either through recovery or fastboot so you can try flashing a ROM.
But if for some reason the tool doesn't work your last chance it's either MiFlash tool or Qfil using a Windows machine.
SubwayChamp said:
I know this is the correct command just I thought you used PowerShell from a Windows some times give errors.
The tool by Francesco Tescari works either through recovery or fastboot so you can try flashing a ROM.
But if for some reason the tool doesn't work your last chance it's either MiFlash tool or Qfil using a Windows machine.
Click to expand...
Click to collapse
Thank you for your time and assistance, I eventually got a windows laptop to try it out, I got the Same Error.
I have tried MiFlash tool and I keep getting
Code:
error:"Flash bluetooth_a_error"
or
Code:
error:FAILED (remote: Flashing is not allowed in a Lock State)
I have tried XiaoMiTool V2 and it straight up didn't work.
Let me look up Qfil.
Micklo said:
Thank you for your time and assistance, I eventually got a windows laptop to try it out, I got the Same Error.
I have tried MiFlash tool and I keep getting
Code:
error:"Flash bluetooth_a_error"
or
Code:
error:FAILED (remote: Flashing is not allowed in a Lock State)
I have tried XiaoMiTool V2 and it straight up didn't work.
Let me look up Qfil.
Click to expand...
Click to collapse
It seems you are trying MiFlash tool in fastboot mode but while your device is locked fastboot mode won't work, you have to open the back cover and try test point method to send device to EDL (Emergency Download mode).
SubwayChamp said:
It seems you are trying MiFlash tool in fastboot mode but while your device is locked fastboot mode won't work, you have to open the back cover and try test point method to send device to EDL (Emergency Download mode).
Click to expand...
Click to collapse
Thank you very much, for still staying put.
I just did.
I downloaded the official Mi A2 fast boot ROM from https://bigota.d.miui.com/V11.0.14.....QDIMIXM_20200928.0000.00_10.0_62d0264480.tgz
I entered EDL mode following this guide: youtube.com/watch?v=34Zoevm-Wxc
I flashed it successfully but my phone is still stuck in the boot loop
Micklo said:
Thank you very much, for still staying put.
I just did.
I downloaded the official Mi A2 fast boot ROM from https://bigota.d.miui.com/V11.0.14.....QDIMIXM_20200928.0000.00_10.0_62d0264480.tgz
I entered EDL mode following this guide: youtube.com/watch?v=34Zoevm-Wxc
I flashed it successfully but my phone is still stuck in the boot loop
Click to expand...
Click to collapse
Use this link, there are other ways to unbrick it https://youtu.be/-B_YseC5kLk
Download from the official site linked in the video guide the recovery stock ROM, you can put it in some place in your PC and use the ADB sideload option through recovery to flash it or also you can use an USB OTG. Additionally try with other firmware, taking care to not downgrading it.
And if this doesn't work you should use other Windows version, some users report better results on Windows 7. And keep trying to switch slot.
Edit: before all try if this command work on fastboot mode: https://forum.xda-developers.com/showpost.php?p=75963934&postcount=25