Related
I upgraded my CWM and then loaded a new Rom to my phone. During the install I had. An issue and the phone rebooted. It will not get past the boot logo. I restarted into recovery but when it loads it just reboots. It doesn't allow me to reinstall a Rom. Can I just reinstall CWM recovery to my sd and would it boot into recovery k like normal?
Sent from my LG-D800 using XDA Free mobile app
I have backed up my Rom but recovery won't stay up for me to load the back up
Sent from my LG-D800 using XDA Free mobile app
Are you s-off?
Before upgrading cwm, I am assuming you could flash different roms.
Let me / us know what you have done so far and in what state you are now in.
Edit: I am quite rusty so I may not be able to help.
Sent from my Desire HD using Tapatalk 2
Still unable to use the phone. Yes I was s off. Yeah I've been installing roms every week for years now. I saw a post about an upgrade cwm recovery and updated. I booted into recovery like normal and installed a Rom. The install went bad and The phone gets stuck on the HTC splash screen. When I boot into recovery it opens for just a second and then the phone just reboots on itself. I Havnt been.able.to do anything to it. I'm not sure what to do.
Sent from my LG-D800 using XDA Free mobile app
If you can access the bootloader still you can flash a new (your old working) recovery with fastboot can't you?
Code:
adb reboot bootloader
Code:
fastboot devices
Code:
fastboot flash recovery FILE.IMG
replace FILE.IMG with your recovery image.
also you can extract your recovery image from your last working nandroid backup. it should be just recovery.img
The way it sounds is that your boot.img got messed up somehow. Maybe try just flashing the boot.img from that rom you last flashed? (the one that doesnt work) but I would just really go about flashing a working nandroid backup/ or recovery with fastboot.
You can restore from a backup with fastboot as well I'm pretty sure...
Anyways here's a link you should check out. https://code.google.com/p/android-roms/wiki/NANDROID_Fastboot
Anyone please help me .
I am using lg g3 d855 with fulmics 7.6 rooted with magisk
Now when I installed the magisk modules it asked me to restart and when I restart it automatically boots into twrp..
I took battery out and restart it again booted into recovery then from twrp I rebooted to system but again it boots into twrp..
Anyone help me to get out of this
I think your system is corrupted... but recovery mode working well. So flash framework
Sent from my SHV-E210S using Tapatalk
[email protected] said:
I think your system is corrupted... but recovery mode working well. So flash framework
Sent from my SHV-E210S using Tapatalk
Click to expand...
Click to collapse
I restored boot of previous backup from twrp and now its stuck on aboot but twrp still working
Google Pixel International Giveaway! Competition https://wn.nr/m7CEbS
I cannot for the life up me update my One Plus 7 Pro from 9.5.3 to 9.5.6 with root/unlock. I've tried the Magisk install to other slot method, tried flashing in twrp, tried full OTA, tried re-installing twrp to both slots after flashing. Basically tried all the 6T methods.
How the hell do you do this? What am I doing wrong?
Not sure what you're doing wrong but what I can do is tell you my steps:
- Upgrade via stock OnePlus Updater inside system settings
- Make sure it downloads the full OTA (over 1GB file size) if you are rooted
- Let it update
- Flash the TWRP retention script found in the Magisk repo if you have TWRP and would like to keep it
- Install Magisk to inactive slot from the main screen in Magisk Manager
-Reboot and profit
Couple things to keep note of
- Uninstall all Substratum overlays before doing this
- Optional: remove lockscreen security
Personally I don't remove lockscreen security but I do uninstall Substratum overlays and I never have issues.
Anyone know how to root if I'm already on 9.5.6?
hachem28 said:
Anyone know how to root if I'm already on 9.5.6?
Click to expand...
Click to collapse
You can flash the Magisk installer zip in TWRP, which is what I did.
Or you can wait until someone posts a patched 9.5.6 boot image.
I posted the 956 magisk image in another thread but here it is again from the gm1917
https://www.dropbox.com/s/0a48lpps6ah90t3/boot956gm1917magisk.img?dl=0
Instructions
(Adb and fastboot on a PC)
(Unlock bootloader): tap build# 6x, Oem unlocking and usb debugging on, connect phone to PC, boot to recovery, "fastboot oem unlock" from PC command prompt which erases phone also, then usb debugging and advanced reboot on again
Download the patched boot image to adb directory
Install the latest version of Magisk Manager to phone
Reboot the phone in fastboot mode
Use the following command via command prompt :
fastboot flash boot boot956gm1917magisk.img
fastboot reboot
The phone will reboot into system, this may take some time be patient
Open Magisk & Install it again[Direct Install]
You've got a rooted OnePlus 7 Pro.
Sent from my GM1917 using Tapatalk
hachem28 said:
Anyone know how to root if I'm already on 9.5.6?
Click to expand...
Click to collapse
@schmeggy929 posted a patched boot image for the US unlocked variant that you can use for rooting and then installing TWRP. I had to switch the active slot for my device before following the instructions for the patched boot image. After getting Magisk and TWRP installed I didn't have WiFi so I wiped everything in TWRP, used the full zip for 9.5.6 followed by the TWRP installer zip, rebooted to recovery, flashed Magisk 19.2, rebooted, and everything worked great. If you get into a bootloop follow this guide
Standard disclaimer: I'm not responsible for damage, etc.
larsdennert said:
I posted the 956 magisk image in another thread but here it is again from the gm1917
https://www.dropbox.com/s/0a48lpps6ah90t3/boot956gm1917magisk.img?dl=0
Instructions
Download the patched boot image to adb directory
Install the latest version of Magisk Manager
Reboot the phone in fastboot mode
Use the following command via command prompt :
fastboot flash boot boot956gm1917magisk.img
fastboot reboot
The phone will reboot into system, this may take some time be patient
Open Magisk & Install it again[Direct Install]
You've got a rooted OnePlus 7 Pro.
Sent from my GM1917 using Tapatalk
Click to expand...
Click to collapse
shadeau said:
@schmeggy929 posted a patched boot image for the US unlocked variant that you can use for rooting and then installing TWRP. I had to switch the active slot for my device before following the instructions for the patched boot image. After getting Magisk and TWRP installed I didn't have WiFi so I wiped everything in TWRP, used the full zip for 9.5.6 followed by the TWRP installer zip, rebooted to recovery, flashed Magisk 19.2, rebooted, and everything worked great. If you get into a bootloop follow this guide
Standard disclaimer: I'm not responsible for damage, etc.
Click to expand...
Click to collapse
OK question does both these methods get us to the same results? Just they are different ways of doing it. Don't beat me up to bad guys.
The key is flashing a boot image that matches what you are currently running.
The second set of instructions also flash TWRP.
Both flash magisk which is essentially root.
I preferred the first method as it was simple and initially only boots to a modified image. If anything goes wrong in that step, nothing permanent has been done. The first method requires you are at least on 9.5.4 as earlier recoveries did not support booting to an image unless it was flashed.
Sent from my GM1917 using Tapatalk
---------- Post added at 10:45 PM ---------- Previous post was at 10:41 PM ----------
The second instructions basically continue where mine left off by flashing TWRP recovery. He then used TWRP to repair having flashed the wrong boot image while rooting and eventually giving up and flashing the whole rom again. I think that's what happened to him.
Sent from my GM1917 using Tapatalk
larsdennert said:
---------- Post added at 10:45 PM ---------- Previous post was at 10:41 PM ----------
The second instructions basically continue where mine left off by flashing TWRP recovery. He then used TWRP to repair having flashed the wrong boot image while rooting and eventually giving up and flashing the whole rom again. I think that's what happened to him.
Click to expand...
Click to collapse
I flashed the correct boot image, but to the wrong slot which led me to a bootloop. After fixing that problem and getting back to stock I switched slots, flashed the boot image, and didn't have WiFi (I triple checked the version was correct and others have had the issue). That's what led me to flashing the full ROM in TWRP and then Magisk.
To the OP:
I like having TWRP with a rooted device, but if you just want root then follow the first set of instructions
OK guys I'm on Verizon I just got my phone Friday and it had the update 9.5.6GM21AA for the Iphone and 7pro problem so I did it. OK now the dumb question when it says Open Magisk & Install it again. There are talking about the boot image right? I'm sorry guys I've not done this in a long time.
OK guys I googled and found what I needed thank you
With the phone only a few weeks old, we are all experimenting with what works. 1+is also releasing a lot of patches all the time so things are a moving Target. Luckily things are settling and the early adopters have sorted out how to get out of a jamb when it happens.
For others clarity open the magisk app after booting to the patched boot image i provided and do a direct install. This is that step that actually permanently patches your boot image for magisk. There are other instructions floating around that instead flash the modified image provided. Those were earlier instructions They are more hazardous in case there is a problem with the supplied image or it doesn't match your rom, or you don't flash to the correct Slot. That's what happened to the other poster but he was experienced enough to simply fix the issue. It's still a sinking feeling when it happens and you wonder how badly you've just bricked your phone. I've been there many times, lol.
Sent from my GM1917 using Tapatalk
skythian said:
I cannot for the life up me update my One Plus 7 Pro from 9.5.3 to 9.5.6 with root/unlock. I've tried the Magisk install to other slot method, tried flashing in twrp, tried full OTA, tried re-installing twrp to both slots after flashing. Basically tried all the 6T methods.
How the hell do you do this? What am I doing wrong?
Click to expand...
Click to collapse
I am in the exact same boat. I went through a bunch of trouble getting my phone rooted for the first time on 9.5.3. Finally got everything setup properly. 9.5.3 with root and twrp 3.3.1-20 (with decryption working).
Wanted to upgrade to 9.5.6 and have been holding off for fear of messing things up and having to wipe and start over.
Decided to go for it. Used the OP system updater. Installed 9.5.6. DID NOT REBOOT. Went to Magisk Manager and installed Magisk using the "After OTA" method. Rebooted. It booted to stock OP recovery.
Frustrated and not quite sure what to do, I went to my computer and installed twrp 3.3.1-20 using "fastboot flash boot twrp.img". I expected it was going to boot into twrp since I installed it on the current slot (A) but to my surprise it booted into system. Unfortunately I lost root, but at least i'm not at the stock recovery.
Then I decided I would try to get root using the patched image that @larsdennert posted on post 5. I went into fastboot and followed his instructions exactly. Waited for it to reboot and ended up at the stock OP recovery screen again. Since the only thing I knew how to get back into my system was flashing the twrp 3.3.1-20, I did that, rebooted, and am now back in Android, but without root.
After reading countless threads about the Slot A and B partitioning, I thought I understood it, but I must not. Or something must be setup wrong. I follow steps exactly and nothing seems to work for me.
Maybe someone can help me out. I'd like to get 9.5.6 rooted, but I am terrified to mess stuff up and have to wipe it clean again.
EDIT:
I got root! Once I got to system I had the idea to boot to recovery to see if twrp was there. Turns out it was, so I flashed Magisk from twrp and rebooted. Saw that it was rooted and direct installed Magisk again from Magisk Manager.
Man, I really have no clue how or why this worked out this way. I feel like i'm going to stay on 9.5.6 for a while out of fear of screwing something up again. This is nothing like my old One Plus 5. lol
Edit x2:
It appears my WiFi isn't working. I don't really know what to do from here.
Blackfireball5 said:
Edit x2:
It appears my WiFi isn't working. I don't really know what to do from here.
Click to expand...
Click to collapse
flash the Sky-Dragon Kernel, it'll fix the wifi
Marco589 said:
flash the Sky-Dragon Kernel, it'll fix the wifi
Click to expand...
Click to collapse
I'm not really interested in going to a different kernel. I'm going to try to dirty flash the update again and reflash twrp and Magisk. Hopefully that will work.
So I've been on the Global Indian MIUI for a while now. And what I usually did was I patched a boot image file using Magisk and then flashed it through fastboot. That way I didn't need a custom recovery and I could get straight updates from MIUI as usual.
After updating to MIUI 10.3.13 I tried to do the same thing once again, but this time I'm met with a Bootloop. The bootlogo shows and the boot animation starts and then suddenly phone reboots and it keeps going on like this until I flash back the stock boot image.
So I installed TWRP and tried flashing Magisk from there but same result. Goes into bootloop. Tried flashing the patched image file from TWRP but end result still same.
So any solution to this? Or any rooting alternative other than magisk?
Is anybody else facing this or are is it just me?
Hello.
After the 12.1.3 update, with the new Magisk app the instructions state that we should extract the recovery.img patch it and flash it to the device in fastboot. After a restart the phone should be rooted. This is however not the case. When I try to flash OrangeFox, and flash the avb patcher from Mauronofrio, OrangeFox remains after a reboot and I can enter it any time holding the volume up at boot. So in theory the recovery partition should not be overwritten to default on restart.
But when I flash over a default-magisk-flashed image, the phone remains un-rooted.
Am I doing something wrong or is this an on-going issue?
Intruder_Alert said:
Hello.
After the 12.1.3 update, with the new Magisk app the instructions state that we should extract the recovery.img patch it and flash it to the device in fastboot. After a restart the phone should be rooted. This is however not the case. When I try to flash OrangeFox, and flash the avb patcher from Mauronofrio, OrangeFox remains after a reboot and I can enter it any time holding the volume up at boot. So in theory the recovery partition should not be overwritten to default on restart.
But when I flash over a default-magisk-flashed image, the phone remains un-rooted.
Am I doing something wrong or is this an on-going issue?
Click to expand...
Click to collapse
When u have a customer recovery, download the last magisk.zip and flash it. Simple
Release Magisk v22.0 · topjohnwu/Magisk
RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN! Another major Magisk release! This time our focus is not the core Magisk implementation, but rather on improving the w...
github.com
In the installation guide they wrote that u have rename only the apk to zip. Very simple
joke19 said:
When u have a customer recovery, download the last magisk.zip and flash it. Simple
Release Magisk v22.0 · topjohnwu/Magisk
RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN! Another major Magisk release! This time our focus is not the core Magisk implementation, but rather on improving the w...
github.com
In the installation guide they wrote that u have rename only the apk to zip. Very simple
Click to expand...
Click to collapse
That is only for the Magisk app, not to root the phone. Rooting the phone is a totally different procedure.
Number ome was the last zip with I root my phone with simple flash and number 2 is the new one.
Look inside.
Here the how to from magisk for a customer recovery.
Download the Magisk APK
Rename the .apk file extension to .zip, for example: Magisk-v22.0.apk → Magisk-v22.0.zip. If you have trouble renaming the file extension (like on Windows), use a file manager on Android or the one included in TWRP to rename the file.
Flash the zip just like any other ordinary flashable zip.
Check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK.
Intruder_Alert said:
Hello.
After the 12.1.3 update, with the new Magisk app the instructions state that we should extract the recovery.img patch it and flash it to the device in fastboot. After a restart the phone should be rooted. This is however not the case. When I try to flash OrangeFox, and flash the avb patcher from Mauronofrio, OrangeFox remains after a reboot and I can enter it any time holding the volume up at boot. So in theory the recovery partition should not be overwritten to default on restart.
But when I flash over a default-magisk-flashed image, the phone remains un-rooted.
Am I doing something wrong or is this an on-going issue?
Click to expand...
Click to collapse
Did you solve it? After I've updated to V12.1.2.0.RFDMIXM Android 11, I can't install Magisk through TWRP, even with the latest canary release
Also tried installing through patching boot.img and recovery.img, with magisk 21.4, 22.0, and latest canary (22006). Everytime system refuses to boot (shows MIUI boot screen for a couple of minutes, then vibrator, then system reboots to recovery).
I've also searched in https://xiaomi.eu/ forums, and the official Magisk general support thread https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/ but can't find any solutions.
wedgehog said:
Did you solve it? After I've updated to V12.1.2.0.RFDMIXM Android 11, I can't install Magisk through TWRP, even with the latest canary release
Also tried installing through patching boot.img and recovery.img, with magisk 21.4, 22.0, and latest canary (22006). Everytime system refuses to boot (shows MIUI boot screen for a couple of minutes, then vibrator, then system reboots to recovery).
I've also searched in https://xiaomi.eu/ forums, and the official Magisk general support thread https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/ but can't find any solutions.
Click to expand...
Click to collapse
Patching the images does not work. But installing the magisk.zip (the latest version) through TWRP or OrangeFox does work (tested and confirmed)! I don't get why it works when installing the zip and does not when patching a recovery.img but this is what we got...
Fun Fact, the instruction manual states you have to hold the HW key to enter recovery until the boot logo shows up, for me now the device is rooted on every boot without any issues, without the need to hold down any buttons.
wedgehog said:
Did you solve it? After I've updated to V12.1.2.0.RFDMIXM Android 11, I can't install Magisk through TWRP, even with the latest canary release
Also tried installing through patching boot.img and recovery.img, with magisk 21.4, 22.0, and latest canary (22006). Everytime system refuses to boot (shows MIUI boot screen for a couple of minutes, then vibrator, then system reboots to recovery).
I've also searched in https://xiaomi.eu/ forums, and the official Magisk general support thread https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/ but can't find any solutions.
Click to expand...
Click to collapse
I just decided to update to V12.1.3 yesterday and got the same problem as yours. Keep trying every version of magisk, from latest and its previous to no avail. It got stuck at MIUI logo even when I left for good half an hour. If I didnt flash magisk zip it loads just as normal but without root, but I still want magisk.
Today I just thought of trying different version of recovery. The current one is TWRP-3.3.2B-0219-XIAOMI_CC9PRO-CN-wzsx150 that got me stuck. Then I flash [email protected]_2.zip recovery. Flash V12.1.3 followed by Magisk-v22-0.zip using OrangeFox worked wonderful. Hope it can help you if you are still stuck like me. Now I can sleep at night.
pawn_broker004 said:
I just decided to update to V12.1.3 yesterday and got the same problem as yours. Keep trying every version of magisk, from latest and its previous to no avail. It got stuck at MIUI logo even when I left for good half an hour. If I didnt flash magisk zip it loads just as normal but without root, but I still want magisk.
Today I just thought of trying different version of recovery. The current one is TWRP-3.3.2B-0219-XIAOMI_CC9PRO-CN-wzsx150 that got me stuck. Then I flash [email protected]_2.zip recovery. Flash V12.1.3 followed by Magisk-v22-0.zip using OrangeFox worked wonderful. Hope it can help you if you are still stuck like me. Now I can sleep at night.
Click to expand...
Click to collapse
Right now I'm still in trouble, after a Magisk update, my phone got stuck in bootloop I had to wipe everything.
But nor the latest .Eu or Global ROM works with Magisk now. I followed the guide by topjonwho (Magisk dev) that says if I don't have a boot.img, I have to modify the recovery.
Well, no luck.
But! If I take the boot.img from the fastboot ROM, and modify that with Magisk, I can boot it up with root. But if I flash that boot.img I'm still stuck on boot. Same with original and TWRP recovery.
You say using [email protected]_2.zip I can just simply flash Magisk 22.1 az a .zip, like in the good old days?
insetta said:
Right now I'm still in trouble, after a Magisk update, my phone got stuck in bootloop I had to wipe everything.
But nor the latest .Eu or Global ROM works with Magisk now. I followed the guide by topjonwho (Magisk dev) that says if I don't have a boot.img, I have to modify the recovery.
Well, no luck.
But! If I take the boot.img from the fastboot ROM, and modify that with Magisk, I can boot it up with root. But if I flash that boot.img I'm still stuck on boot. Same with original and TWRP recovery.
You say using [email protected]_2.zip I can just simply flash Magisk 22.1 az a .zip, like in the goof old days?
Click to expand...
Click to collapse
Yup, tried that boot.img method doesn't work too.
It was magisk 22.0 when I upgraded to 12.1.3 but i guess 22.1 works the same. So nervous waiting the MIUI screen for about 15 minutes, relieved when it finally went through.
Now I'm already upgraded to 12.1.5 magisk 22.1 using the same method. Flash rom followed by magisk zip, like good old days.
pawn_broker004 said:
Yup, tried that boot.img method doesn't work too.
It was magisk 22.0 when I upgraded to 12.1.3 but i guess 22.1 works the same. So nervous waiting the MIUI screen for about 15 minutes, relieved when it finally went through.
Now I'm already upgraded to 12.1.5 magisk 22.1 using the same method. Flash rom followed by magisk zip, like good old days.
Click to expand...
Click to collapse
So I'll have wait at boot for about 15 min? I'm afraid of screen burn-in.
Hi, I always use Orange fox but after the Android 11 update I am not able to see any files after installing custom recovery (Orange fox latest). When I boot my phone into orange fox recovery, it is not showing my files. Files are shown as renamed as fkffqwhfjkfhsf something like that
mdalarian said:
Hi, I always use Orange fox but after the Android 11 update I am not able to see any files after installing custom recovery (Orange fox latest). When I boot my phone into orange fox recovery, it is not showing my files. Files are shown as renamed as fkffqwhfjkfhsf something like that
Click to expand...
Click to collapse
Can you see your files while your phone is booted into OS?
Chances are, the encryption type changed from FDE to FBE, meaning the master key no longer works.
I suggest you backup everything now to a computer, because you can end up like me, and lose access to any file on the phone.
If you saved everything you deem precious from your phone, you need to do a wipe, and then FORMAT /data in recovery.
This will factory reset your phone, but it will work proper with the recovery.