Related
Hello everyone
So here my problems :
I wanted to put Havoc OS on my OP7Pro and i downloaded the TWRP on the official website. After trying to install TWRP but inevitably fail, i followed a thread on how to install TWRP with magisk and after problems after problems arrived.
I cleaned everything and TWRP didn't detect my internal storage, so i tried to put the official rom via a Fastboot rom (since i didn't have access to debug mode and unable to boot) but the fastboot rom rebooted and Qualcom CrashDump (Kernel Restart).
After that i tried MSMdownload tool but was not able to get past "Param Preload" and after i'm stuck with the Kernel_restart of the Crashdump
OnePlus 7 Pro model : GM1913 (France)
If anyone got a solution i'm in
Hilarious! I did the same thing this morning ........ tring to flash cm17 tho but still same kernel flash crash dump etc
So I did the same as you, tried everything....
I was running 10.3.0 originally but after using "flash factory images" with --- https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
and choosing 9.5.13, 7pro fastboot zip, everything is booted now and back to normal
folder with 9.5.13 file-------- https://sourceforge.net/projects/fastbootroms/files/OnePlus 7 Pro/
I even tried manually flash all partitions before using the tool but did not stick, kept booting to crash dump
When I tried the all in one tool and 9.5.13 all is well again.
Very funny you have the same issue as me today but I resolved so you should be able to as well - cheers
jasons1004 said:
Hilarious! I did the same thing this morning ........ tring to flash cm17 tho but still same kernel flash crash dump etc
So I did the same as you, tried everything....
I was running 10.3.0 originally but after using "flash factory images" with --- https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
and choosing 9.5.13, 7pro fastboot zip, everything is booted now and back to normal
folder with 9.5.13 file-------- https://sourceforge.net/projects/fastbootroms/files/OnePlus 7 Pro/
I even tried manually flash all partitions before using the tool but did not stick, kept booting to crash dump
When I tried the all in one tool and 9.5.13 all is well again.
Very funny you have the same issue as me today but I resolved so you should be able to as well - cheers
Click to expand...
Click to collapse
I'm gonna try right now i hope that i can think of you as my savior sir
jasons1004 said:
Hilarious! I did the same thing this morning ........ tring to flash cm17 tho but still same kernel flash crash dump etc
So I did the same as you, tried everything....
I was running 10.3.0 originally but after using "flash factory images" with --- https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
and choosing 9.5.13, 7pro fastboot zip, everything is booted now and back to normal
folder with 9.5.13 file-------- https://sourceforge.net/projects/fastbootroms/files/OnePlus 7 Pro/
I even tried manually flash all partitions before using the tool but did not stick, kept booting to crash dump
When I tried the all in one tool and 9.5.13 all is well again.
Very funny you have the same issue as me today but I resolved so you should be able to as well - cheers
Click to expand...
Click to collapse
I love you sir Everything works
I guess the flash-all.bat was bugged i retry with the programms you linked and everything good right now
ModernLobby said:
I love you sir Everything works
I guess the flash-all.bat was bugged i retry with the programms you linked and everything good right now
Click to expand...
Click to collapse
Great!
However now I am stuck...
When I fastboot boot twrp img I get black screen and nothing happens... so i cant install twrp yet
So I can just re lock bootloader and call it a day and stay on 9 but I like root for Viper at least so I may struggle on.
So I just used the tool instead of doing manual boot / flash twrp. I did the flash recovery and root, choosing Pie twrp and 20.2 magisk options and now working fine.
I am not sure where my error lies but this tool is great LOL..
jasons1004 said:
Great!
However now I am stuck...
When I fastboot boot twrp img I get black screen and nothing happens... so i cant install twrp yet
So I can just re lock bootloader and call it a day and stay on 9 but I like root for Viper at least so I may struggle on.
So I just used the tool instead of doing manual boot / flash twrp. I did the flash recovery and root, choosing Pie twrp and 20.2 magisk options and now working fine.
I am not sure where my error lies but this tool is great LOL..
Click to expand...
Click to collapse
Can i ask you a question i choose the wrong ROM I took gm21aa and i need gm21ba do you think i can reflash the same way or do i need another tool ?
ModernLobby said:
Can i ask you a question i choose the wrong ROM I took gm21aa and i need gm21ba do you think i can reflash the same way or do i need another tool ?
Click to expand...
Click to collapse
just download the file by itself from that folder and select file in the tool instead of download through the tool....if thats what you meant.
jasons1004 said:
just download the file by itself from that folder and select file in the tool instead of download through the tool....if thats what you meant.
Click to expand...
Click to collapse
i'm gonna try since i didn't took the right version it bugged me a little bit ^^
I have had the same issue, getting into edl-mode and start the msm-tool was really a little bit crazy.
Anonymouze said:
I have had the same issue, getting into edl-mode and start the msm-tool was really a little bit crazy.
Click to expand...
Click to collapse
Yeah i got to admit i never had this software working everytime i run into the param preload issue so i tried the issue that jasons1004 told me and now its work fine
It's been 10 days since my oneplus 6 bricked itself and matter of fact i didn't do anything in it although i was gonna flash a custom rom on it and for flashing when i rebooted it into bootloader mode and then connected it to my laptop it just restarted itself and since then it is stuck on oneplus logo i have tried every possible flashing guide available for this device and every flashing getting completed perfectly but result is same it just stuck on logo an by now i have understand the problem is related to hardware until unless some angel in disguise help me out
are u try MsmDownloadTool ? what happen after ? could access to stock rom ?
metrixx02 said:
are u try MsmDownloadTool ? what happen after ? could access to stock rom ?
Click to expand...
Click to collapse
I have tried that too and my device got successfully flashed with bootloader relocked again but device is stuck on logo
Did you try fastboot stock roms?
°Washy said:
Did you try fastboot stock roms?
Click to expand...
Click to collapse
Yup
In that case it would be possible to open the botloader again? If so, try this, it is obvious that you flashed an Android 10 rom ..
step 1: reinstall the twrq maunofrio Q and flash a rom oxygen of android pie the last one if possible 9.0.9 (this only to be able to change twrp, the same will still be in bootlop, but now if you get the twrp of android 9 )
step 2: flashea twrp enchilada 3.3.1-2 img, already in recovery flashea twrp 3.3.1-2.zip and restart in recovery.
step 3: download exactly the rom 34 that would be the rom 9.0.6 I think (OnePlus6Oxygen_22_OTA_032_all_1906251226_0033d1285cf04df0.zip) you flash and do not install anything else you just start the system .. nothing more as long as I stay in bootloop I do that and it has always saved me. pdt, I speak Spanish sorry for my translation
Have you got backup of your EFS partition? If yes you can try use MSM tool and SMT Donwload mode. As password use: te123. It will reflash your phone completely, but there will be no modem, imei, wifi, bluetooth, etc. Don't do that if you didn't backup your modem/efs.
To use SMT Donwload mode you have to click Verify and after that select SMT. After that MSM change border to red. Check also SMT menu in the upper left corner and set checkboxes of all your COM ports in new opened window.
Why not format data. That will fix phone!
Hello guys!
The story began, when I accidently installed a stock OTS update by OP onto my already rooted OP6 with Magsik and TWRP, running a NoLimits ROM...
I just noticed, that the phone said "restart to finish OTS upgrade" or some kind of thing..... I always had the notification on my screen that an update would be available....what surely was ignored because running NoLimits ROM.... but because of some unknown reason, the stock update installed itself magically...
So I ended up finding my phone in complete stock condition, just the unlocked bootloader remained..... F*CK!
I tried to go back to root by trying to install TWRP via fastboot...and that was the beginnig of the end...
By fastboot boot twrp.img, the phone just remained in fastboot mode..... no twrp screen showed up... repeated this a few times, nothing changed....
Somewhere here I read to look up the current slot.... so I did fastboot getvar current-slot.... and after slot b was shown, I flashed twrp into slot b by fastboot flash boot_b twrp.img..... which had the phone stuck in screen "the bootloader is unlocked.....".... so i think that's what is called a BRICK...?
Please guys, help me out...as I don't know how to go on.... I also tried to flash stock boot img from here via fastboot, what didn't work either....
Would be glad for any suggestions...
Thanks!
Alex
dr.zikzak said:
Hello guys!
The story began, when I accidently installed a stock OTS update by OP onto my already rooted OP6 with Magsik and TWRP, running a NoLimits ROM...
I just noticed, that the phone said "restart to finish OTS upgrade" or some kind of thing..... I always had the notification on my screen that an update would be available....what surely was ignored because running NoLimits ROM.... but because of some unknown reason, the stock update installed itself magically...
So I ended up finding my phone in complete stock condition, just the unlocked bootloader remained..... F*CK!
I tried to go back to root by trying to install TWRP via fastboot...and that was the beginnig of the end...
By fastboot boot twrp.img, the phone just remained in fastboot mode..... no twrp screen showed up... repeated this a few times, nothing changed....
Somewhere here I read to look up the current slot.... so I did fastboot getvar current-slot.... and after slot b was shown, I flashed twrp into slot b by fastboot flash boot_b twrp.img..... which had the phone stuck in screen "the bootloader is unlocked.....".... so i think that's what is called a BRICK...?
Please guys, help me out...as I don't know how to go on.... I also tried to flash stock boot img from here via fastboot, what didn't work either....
Would be glad for any suggestions...
Thanks!
Alex
Click to expand...
Click to collapse
i remember that NoLIMIT rom mustbe uninstall before update the oos.In your case i think it was bootloop,softbrick.You boot into fastboob mood and use fastboot rom. and you can root and instant TWRP again.
soihuvuontrang said:
i remember that NoLIMIT rom mustbe uninstall before update the oos.In your case i think it was bootloop,softbrick.You boot into fastboob mood and use fastboot rom. and you can root and instant TWRP again.
Click to expand...
Click to collapse
Hello!
Nothing is working at the moment, just fastboot... not recovery mode, no booting into the OTS...
Tried to use MSM tool but it can't even find the right port....at first, I had COM3 and COM4 showing up, but only N/A....
Now i uninstalled the qualcom drivers as suggested in an unbrick thread of the OP 5T, but that made every port disappear in the MSM tool list.... I'm f*cked I guess...
How can I fix that driver mess again? (driver signing is disabled in bios, testmode is available an working on my pc)
Thanks,
Alex
dr.zikzak said:
Hello!
Nothing is working at the moment, just fastboot... not recovery mode, no booting into the OTS...
Tried to use MSM tool but it can't even find the right port....at first, I had COM3 and COM4 showing up, but only N/A....
Now i uninstalled the qualcom drivers as suggested in an unbrick thread of the OP 5T, but that made every port disappear in the MSM tool list.... I'm f*cked I guess...
How can I fix that driver mess again? (driver signing is disabled in bios, testmode is available an working on my pc)
Thanks,
Alex
Click to expand...
Click to collapse
If you can access fastboot mode you can try follow procedure in next thread:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I could recover my system with this @mauronofrio tool a couple of times. In fact, i never have used MSM tool.
dr.zikzak said:
Hello!
Nothing is working at the moment, just fastboot... not recovery mode, no booting into the OTS...
Tried to use MSM tool but it can't even find the right port....at first, I had COM3 and COM4 showing up, but only N/A....
Now i uninstalled the qualcom drivers as suggested in an unbrick thread of the OP 5T, but that made every port disappear in the MSM tool list.... I'm f*cked I guess...
How can I fix that driver mess again? (driver signing is disabled in bios, testmode is available an working on my pc)
Thanks,
Alex
Click to expand...
Click to collapse
boot in to fastboot mode and your fone is not brick,so msm tool isn't used .
you can download newest driver for oneplus on google.
and you can find on forum. hope you will be successful
Kurtinaitis said:
If you can access fastboot mode you can try follow procedure in next thread:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I could recover my system with this @mauronofrio tool a couple of times. In fact, i never have used MSM tool.
Click to expand...
Click to collapse
I'll have a try..,.thanks for that!
Regards,
Alex
The method of @mauronofrio worked!!! Thanks a lot!
But I still can't boot twrp on the phone....if I do so, the phone boots into fastboot mode again and freezes at "1+ logo" with "Fastboot Mode" below it..... same like before? The device is fully wiped now...
So how can I get TWRP working again...??
I also tried fastboot flash recovery twrp.img -> no such partition..... don't know why it worked the first time I did it, root and custom ROM without any issues...
Thanks,
Alex
dr.zikzak said:
The method of @mauronofrio worked!!! Thanks a lot!
But I still can't boot twrp on the phone....if I do so, the phone boots into fastboot mode again and freezes at "1+ logo" with "Fastboot Mode" below it..... same like before? The device is fully wiped now...
So how can I get TWRP working again...??
Thanks,
Alex
Click to expand...
Click to collapse
It seems a problem with TWRP version or Fastboot command.
Please, describe your method to flash TWRP and which version do you want to flash
Kurtinaitis said:
It seems a problem with TWRP version or Fastboot command.
Please, describe your method to flash TWRP and which version do you want to flash
Click to expand...
Click to collapse
I downloaded latest twrp-3-3-1.2 (I think) for my OP6, copied the belonging .zip file to my phone... started cmd as admin, typed fastboot devices....the device showed up, then fastboot boot twrp...........img.....enter, and afterwards the "1+" logo showed up, below it read Fastboot Mode...and nothing ever happened... till i switched the phone off again after 10 minutes...
Wrong version you think?
Thanks,
Alex
If you are on Android 10 try to download last version from Mauronofrio or last from Blu-Spark (V9.109). I use blu_spark with OOS 10.3.3
Sometimes the command for being able to boot in recovery from Fastboot is:
Fastboot flash boot "nameofTWRPimage".img
Flash a patched boot image of your rom via fastboot and than flash twrp installer through magisk manager. Done.
Kurtinaitis said:
If you are on Android 10 try to download last version from Mauronofrio or last from Blu-Spark (V9.109). I use blu_spark with OOS 10.3.3
Sometimes the command for being able to boot in recovery from Fastboot is:
Fastboot flash boot "nameofTWRPimage".img
Click to expand...
Click to collapse
Yes that worked for me last time I attempted root.
TWRP update - no boot into system
Hello guys....it's me again!
After getting everything working again because of the tremendous help of this forum, i tried to update my twrp recovery via twrp by installing the twrp zip-file...
Afterwards, i tried to upgrade my rom from NoLimits 11.2 to 11.5 - but the phone didn't boot afterwards....i've always ended up in the recovery menue....
I then changed slots (from b to a) in the recovery, and then, the phone booted again....but into the stock ROM...
I can't change slots again now and have stock rom in slot a as it seams.... how can i change that again? how can i flash the custom rom in the right slot again?
Thanks in advance!
Regards,
Alex
dr.zikzak said:
Hello guys....it's me again!
After getting everything working again because of the tremendous help of this forum, i tried to update my twrp recovery via twrp by installing the twrp zip-file...
Afterwards, i tried to upgrade my rom from NoLimits 11.2 to 11.5 - but the phone didn't boot afterwards....i've always ended up in the recovery menue....
I then changed slots (from b to a) in the recovery, and then, the phone booted again....but into the stock ROM...
I can't change slots again now and have stock rom in slot a as it seams.... how can i change that again? how can i flash the custom rom in the right slot again?
Thanks in advance!
Regards,
Alex
Click to expand...
Click to collapse
It's OK. That's the point of having 2 slots system. Be able to recover the other partition if something goes wrong.
So now... Do you have TWRP or stock recovery?
You can dirty flash stock on the inactive Slot.
I would install stock rom in inactive slot through Local Update un System updater, don't reboot, install TWRP retention script in Magisk Manager (of course only if you have a proper TWRP running, if not avoid this step), don't reboot, install magisk to inactive Slot (through Magisk Manager), reboot.
After that you Will have stock on both partitions. You can try again the XXX Update.
Kurtinaitis said:
It's OK. That's the point of having 2 slots system. Be able to recover the other partition if something goes wrong.
So now... Do you have TWRP or stock recovery?
You can dirty flash stock on the inactive Slot.
I would install stock rom in inactive slot through Local Update un System updater, don't reboot, install TWRP retention script in Magisk Manager (of course only if you have a proper TWRP running, if not avoid this step), don't reboot, install magisk to inactive Slot (through Magisk Manager), reboot.
After that you Will have stock on both partitions. You can try again the XXX Update.
Click to expand...
Click to collapse
Thanks for the fast answer!
I think TWRP is working, nur on slot B - the question is: how come that i Installed TWRP Update via TWRP Recovery, was able to reboot Ingo recovery, and after Flash of the ROM via TWRP, only TWRP Recovery was left... No bootable ROM, so i tried Slot A and that was Stock Rom...
How can i install stock ROM into Slot B if Slot A is currently 'running'?
Regards,
Alex
dr.zikzak said:
Thanks for the fast answer!
I think TWRP is working, nur on slot B - the question is: how come that i Installed TWRP Update via TWRP Recovery, was able to reboot Ingo recovery, and after Flash of the ROM via TWRP, only TWRP Recovery was left... No bootable ROM, so i tried Slot A and that was Stock Rom...
How can i install stock ROM into Slot B if Slot A is currently 'running'?
Regards,
Alex
Click to expand...
Click to collapse
Since Oxygen Os Updater > Local Upgrade.
Download 10.3.4 OOS and put in your internal Storage. Then follow procedure i wrote before
Kurtinaitis said:
Since Oxygen Os Updater > Local Upgrade.
Download 10.3.4 OOS and put in your internal Storage. Then follow procedure i wrote before
Click to expand...
Click to collapse
NOTE: don't reboot until you install Magisk to inactive Slot, and of course, as you're rooted must download Full Zip (not incremental)
Kurtinaitis said:
NOTE: don't reboot until you install Magisk to inactive Slot, and of course, as you're rooted must download Full Zip (not incremental)
Click to expand...
Click to collapse
I downloaded Oxygen Updater, also OOS 10.3.4, but in my system stettings, update button is greyed out.... with the nolimits ROM before, I once had issues that the OEM update got installed...so that led to my problem which made me open up this thread in the first place.... so i disabled system update via titanium backup when I had root access...
So now it's greyed out...but as it is the stock rom, it shouldn't be greyed out as titanium backup doesn't work at the moment, without root...
Should i flash via @mauronofrio's method and fully wipe the device?... would be a pain in the a.. as everything gets erased again, setting up from scratch 2 times within 3 weeks
Regards,
Alex
Would it be possible to install magisk without twrp, and then flash the NoLimits ROM via Magisk?
TWRP recovery must be there....only in slot B - i tried to change slot by fastboot --set-active=..... but it didn't work, unknown command
Regards,
Alex
dr.zikzak said:
I downloaded Oxygen Updater, also OOS 10.3.4, but in my system stettings, update button is greyed out.... with the nolimits ROM before, I once had issues that the OEM update got installed...so that led to my problem which made me open up this thread in the first place.... so i disabled system update via titanium backup when I had root access...
So now it's greyed out...but as it is the stock rom, it shouldn't be greyed out as titanium backup doesn't work at the moment, without root...
Should i flash via @mauronofrio's method and fully wipe the device?... would be a pain in the a.. as everything gets erased again, setting up from scratch 2 times within 3 weeks
Regards,
Alex
Click to expand...
Click to collapse
Did you try to install the Update since the app Oxygen Updater?
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
dr.zikzak said:
Would it be possible to install magisk without twrp, and then flash the NoLimits ROM via Magisk?
TWRP recovery must be there....only in slot B - i tried to change slot by fastboot --set-active=..... but it didn't work, unknown command
Regards,
Alex
Click to expand...
Click to collapse
I think there's some thread in Guides and News in which OP uploads some patched boot.img le something like that to have root but i never tried.
Hi!
I have a poco f2 pro that was on the xiaomi.eu MIUI weekly.
Yesterday I installed a module for Magisk and got into a bootloop. From now everything's fine I usually know how to deal with this kind of stuff.
The mistake I did, is when I tried to boot into a new TWRP after flashing.
I did
Code:
fastboot flash boot ./twrp_xxx.img
instead of
Code:
fastboot flash recovery ./twrp_xxx.img
I tried many times flashing different boot.img without success, I didn't managed to install "magisk manager for recovery" so I did a clean flash of the rom, and then I even tried downloading the stock global from from https://xiaomifirmwareupdater.com/ and did a "flashall" without success (the phone boots on bootloader/recovery).
Fortunately I havent yet locked the bootloader so I can still flash everything.
Can someone help me figure out why my phone is doing this even after flashing everything please?
Did you try with Miflash?
try with MiFlash. Flash stock rom in fastboot mode
Hi! Thak you for the quick answer
I don't know why but I believed that the only thing miflash do is to execute the scripts from the folder.... I'll try this now
Thelm76 said:
Hi! Thak you for the quick answer
I don't know why but I believed that the only thing miflash do is to execute the scripts from the folder.... I'll try this now
Click to expand...
Click to collapse
Before MiFlash try delete the Magisk module causing the bootloop, use TWRP File Manager. Magisk modules are located in /data/adb/modules
dhaern said:
Before MiFlash try delete the Magisk module causing the bootloop, use TWRP File Manager. Magisk modules are located in /data/adb/modules
Click to expand...
Click to collapse
Well that the thing I tried when I accidentally replaced my boot partition... And my phone was only booting on twrp or fastboot... also the weird thing I found is that /data/adb didn't exist
But many thanks to you all it works now.
I'll maybe try to make a guide on how to install Magisk on the Xiaomi EU weekly rom, as android 11 is only supported by the canary build. (if I manage to find a way to properly remove defective modules in TWRP :fingers-crossed
Boot twrp via Fastboot. Download Rom, Install ROM (xiaomi.eu). This should fix ist already. Then you could test a bit, and eventually need to wipe data
Tecardo said:
Boot twrp via Fastboot. Download Rom, Install ROM (xiaomi.eu). This should fix ist already. Then you could test a bit, and eventually need to wipe data
Click to expand...
Click to collapse
That was the first thing I tried, but only miflash managed to bring my phone back to life , as current twrp doesn't like encrypted data partition (I don't know why but it won't mount /data and it says wrong password)
I think that's why I couldn't remove the defective module
If you want everything to work you need to format data!!
Thats the point why using android 11 roms is hard, twrp cant decrypt it (until you flash rom with a10 and then a11 because partition is encrypted in a10 style)
Thelm76 said:
That was the first thing I tried, but only miflash managed to bring my phone back to life , as current twrp doesn't like encrypted data partition (I don't know why but it won't mount /data and it says wrong password)
I think that's why I couldn't remove the defective module
Click to expand...
Click to collapse
That's easy to fix, you installed Android 11 or? Don't use pin, use gesture. Twrp can't decrypt android 11 pin right now
Thelm76 said:
Hi!
I have a poco f2 pro that was on the xiaomi.eu MIUI weekly.
Yesterday I installed a module for Magisk and got into a bootloop. From now everything's fine I usually know how to deal with this kind of stuff.
The mistake I did, is when I tried to boot into a new TWRP after flashing.
I did
Code:
fastboot flash boot ./twrp_xxx.img
instead of
Code:
fastboot flash recovery ./twrp_xxx.img
I tried many times flashing different boot.img without success, I didn't managed to install "magisk manager for recovery" so I did a clean flash of the rom, and then I even tried downloading the stock global from from https://xiaomifirmwareupdater.com/ and did a "flashall" without success (the phone boots on bootloader/recovery).
Fortunately I havent yet locked the bootloader so I can still flash everything.
Can someone help me figure out why my phone is doing this even after flashing everything please?
Click to expand...
Click to collapse
NO flash only fastboot boot twrp.img
Unsure if this is the place since its also related to TWRP 3.7, any help is appreicated
Got stuck in a weird situation and wondering if anyone has ideas.
Current State:
Slot_A on OOS 11, can boot TWRP via Fastboot
Slot_B on OOS 12, can only boot into Fastboot
Originally on OOS 11, booted TWRP and made backups of all partitions (data, boot, system image, vendor image, etc.). Forgot to move this to computer so this is all still stored on device.
Proceeded with OOS 12 upgrade (into Slot B). Patched magisk, rebooted, then flashed TWRP 3.7 (FBEv1), direct installed magisk, rebooted. - Everything was functional, but decided to go back to OOS 11.
Thinking I could just use the TWRP backup made on OOS 11, I did the following:
Booted into 3.7 TWRP
Restored the backup for boot, system image, and vendor image
Set active slot to Slot A and reboot
It doesn't allow me to boot into the OS (Presumably because the data was re-encrypted for OOS 12?)
Set active-slot=b and reboot, but it's locked to fastboot.
I've attempted a few things, but I can't boot back into OOS. I would prefer to retrieve my TWRP backups first before doing an MSM reset.
When on Slot_A (older), I can only boot into TWRP 3.6.2 and 3.7. I'm guessing 3.6.2 can't decrypt since it's only configured for A11 and under, but not sure why 3.7 can't decrypt my data.
- It doesn't even ask for pin when TWRP launches; maybe it's reading the System for Slot_A and thinks i'm still on A11?
- running `twrp decrypt {pin}` doesn't seem to work. Unsure if there's something done to my lockscreen pin to be used as the encryption key/password?
When on Slot_A, attempting to boot into either the system or TWRP hangs.
Things I've tried:
Flashing A11 boot.img and magisk-patched boot.img to Slot_A -> Hangs on 1+ Spinning dots
Flashing A12 boot.img and magisk-patched boot.img to Slot_B -> Hangs on 1+ logo (Does show up on ADB though)
Booting Slot_B into TWRP 3.6.2 (Official, and Nebrassy unofficial for A12) and TWRP 3.7 -> Gets stuck on "Fastboot Mode" screen (fastboot cli still responds) or Hangs on snapdragon logo
Edit: Ended up using MSM. Needed device for work
I have a similiar problem to flash twrp to my phone ,
each time i try i get a fastboot loop too and i have to reset/unbrick it with the msm tool back to android 11
i use the OnePlus_7_Pro_Global_OxygenOS_11.0.5.1 package to unbrick the phone , i dont know how long and often i tried now to get twrp to work so that i can flash a custom fw ... i want root and a android 13 based cfw but i dont get it to work :/
I got it working with crdroid. heres some stuff
guacamole - Google Drive
drive.google.com
be carefull
¯\_(ツ)_/¯
------------------------------------
I got stable and decrypted fs RW working on crdroid 9.1 firmware other than some weird bugs
i put it in the 2023-twrp
MissAnthropin said:
I have a similiar problem to flash twrp to my phone ,
each time i try i get a fastboot loop too and i have to reset/unbrick it with the msm tool back to android 11
i use the OnePlus_7_Pro_Global_OxygenOS_11.0.5.1 package to unbrick the phone , i dont know how long and often i tried now to get twrp to work so that i can flash a custom fw ... i want root and a android 13 based cfw but i dont get it to work :/
Click to expand...
Click to collapse
I have the exact same problem! Have you found a fix yet? This seems to happen when I try to install Android 13 based roms, and when I install a rom like Lineage OS, using their recovery, it works just fine.
No, and I don't know why, maybe i do something wrong or it is the Modell that make this trouble.
I thinking to sell my OP7PRO and buy another one ( and then I have the same problem with the new phone )
No no let the jokes aside, it must work, i mailed with OnePlus Support Germany but they only helped me to install A11 w/root and recovery, i thought ok now I can update to A13 so I loaded A13, unpacked the boot.img, Patched the boot.img
Installed A13 w/out errors, rebooted - Fastboot loop
RIP
Started ranting instead
TWRP for guacamole development seems to be fairly scarce, last working recovery I tried was when they started using fastboot boot to enter it. It was pretty hacky even then, currently it seems that nebrassy is the maintainer for twrp for guacamole.
Github: https://github.com/nebrassy Android 12 thread: https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4269551/ Nebrassys Telegram has helpful info as well: https://t.me/NSSFB
last update I found was 2022:10:2 - https://www.pling.com/s/Phones/p/1835156
after a few days of torture I read a thread on here saying if you flashed twrp via magisk like you would if it was a magisk moule it would work normally. It worked on my device so I assume that its universal. I have filled my computer with guacamole related files Im uploading here before im forced to reinstall my os:
guacamole - Google Drive
drive.google.com
Just a fyi from what I have gathered from my experience you can get a stable twrp recovery with persistant / read write access and disabled encryption and basically use it with little error up until you try flashing a newer custom rom. My guess is when flashing a cfw the bootloader gets rewritten causing our boot image to become corrupted. Flashing twrp over / booting to twrp via fastboot or trying to install it via another custom recovery causes boot / recovery failures... meaning you cant really use it for flashing custom roms. I cant find the post with the install instructions I seen that helped me so here is what I think it was,
Found it: https://forum.xda-developers.com/t/how-to-make-twrp-work-in-your-stock-a12.4522667/#post-87985325
~ I have bricked this device constantly while ****ing around so unless youre prepared to go to war with the ****er, Id quit messing with it.
MSM flashing with windows is the only way to recover from the void.
Click to expand...
Click to collapse
using Linux systems for EDL is a bit more difficult to figure out but can be done > EDL https://github.com/bkerler/edl/blob/master/edl | https://github.com/andersson/qdl
Click to expand...
Click to collapse
~If you do brick I created a fastboot flashable A13 Oxygen os recovery rom and uploaded it to my google drive found under recovery_brick_fastboot.zip ~
Click to expand...
Click to collapse
lastly be mindful of a/b partition configuration or youll find yourself lost or bricked
Installation:
1. Obviously unlock the bootloader - OEM Unlock
2. Flash custom recovery (lineage/crdroid/etc)
3. (Personally I root here and again on the active slot so) flash magisk.zip
4. Reboot into installed ROM and install magisk android app and complete setup, reboot system
5. (another thing I like to do before flashing twrp) setup magisk enable all the basic options like prophide, deny list then set root userspace option to global.
6. Flash TWRP .zip (https://dl.twrp.me/guacamolev2/twrp-installer-3.7.0_12-0-guacamolev2.zip) via magisk
Alright! After all that you should be able to reboot into recovery via adb reboot recovery / fastboot or power menu and you find a working twrp recovery installed.
If you need help or want to **** around with the device you can @ me anytime and ill do my best to halp
2600 IRC (cornelius.scuttled.net >Nick captain >channel #guac)
Telegram https://t.me/+pxvpKToFo6pkMGYx
Discord https://discord.gg/MhvWgEfY
Pics
RolandStoner said:
Pics
Click to expand...
Click to collapse
You Confussing me a lot with your Posts before ...
i´m unsure what you mean exactly,
my bootloader is unlocked, with magisk i got a working root but after that i fail
what you mean with flash twrp with magisk ?
after unlocking the bootloader and get root, i tryd to flash twrp like before on other devices but that seems not working because i get then the fastboot loop
on another thread i found here on xda too, the guy wrote dont forget to activate the fastboot loop fix in the advanced options
but i not tried it yet again , so what should i do now ?
for now , i´m back on android11 , with stock oxygen os firmware
i have to do now the things like i did before again , unpack boot.img from the firmware that is installed on the device
patch it with magisk, flash it with "fastboot flash boot boot-patched.img" or is this step senseless ?
i mean you only wrote unlock bootloader and flash a cfw , but i don´t have a chance to flash a custom fw without a custom recovery ??
my recovery on my op7pro have no options for "install zip" or something else
addendum:
like i said you confused me a lot
addendum two:
or i do what i said before .. i sell my op7pro and buy me a one where i havent so much trouble installing twrp and root
i never had a phone before that made so much trouble in installing simple twrp ...
but i don´t found a phone yet that is compatible with kali and the pentest tools or wardriving tools like the oneplus , so i have a problem ,... i think i should drink now my selfmade blackberry liquor ( or blackberry booze ? ) and let the smartphone be a smartphone for now and power off my brain for a while
Yes, you need to patch your boot image via magisk and flash it with fastboot.
After you let magisk do its first time setup and then once it reboots you go to Magisk > Modules and flash the twrp recovery .zip file you got from twrp. link:https://twrp.me/oneplus/oneplus7pro.html just like you would if it was a magisk module.
the password for twrp decryption is your pin. Here are simpler instructions
https://forum.xda-developers.com/t/how-to-make-twrp-work-in-your-stock-a12.4522667/#post-87985325
****... I forgot a step.
after flashing twrp as a module in magisk you dont reboot, you go back to the main screen hit the install button and choose direct install
Now I understand it more, i had before rooted the phone successful with magisk, but then I made a wrong decision and booted into Fastboot and flashed TWRP in Fastboot Mode as I did it before with all my Smarties i had before, coz those way with Fastboot worked before all the time so I never thought that this is the error in the procedure
I give the twrp flashing with magisk a try.
Thx for the help
MissAnthropin said:
Now I understand it more, i had before rooted the phone successful with magisk, but then I made a wrong decision and booted into Fastboot and flashed TWRP in Fastboot Mode as I did it before with all my Smarties i had before, coz those way with Fastboot worked before all the time so I never thought that this is the error in the procedure
I give the twrp flashing with magisk a try.
Thx for the help
Click to expand...
Click to collapse
Thank @yassine2217 because I would never have done so either.... Still many bugs but twrp is twrp