what i currently have now on my rn8pro is miui11, android10. prior to this, i had android 9 with the anti brick files flashed from the mega thread (if it matters). not sure what happened but i got a message saying i lost root. so i went into twrp 10 and uninstall and reinstalled root. now it just boot to the first redmi screen and it loops. im still able to access bootloader and recovery. what are my options? id prefer to startmoff fresh from scratch starting with android 9 and staying there. wasnt sure if id bricked my phone. im on my back upright now (honor note 10) but currently on stand by waiting to her from someone since this phone is easily bricked. i hope i explained it right. thanks.
My exp: looping is due to older magisk being flashed.
Try download latest magisk & flash it manually via TWRP, it should boot normally.
I bet you're using LR-TWRP? If yes, the bundled one is v20.3 or older. You need v20.4.
Also, stay in A10 my friend, never try to flash back to A9 coz the unbrick files doesn't work on A10 & you'll end up with bricked phone.
Related
Rooted my Honor 7x (Bnd-L21) recently, and I wanted to ues snapchat which wasn't working, due to my root status. So, I decided to try MAGISK, when I tried to unroot I stupidly went to TWRP Recovery and factory reset rather than going the safe route and un-rooting through SUPERSU. Now, when I tried boot up my phone it goes straight to the EMUI eRecovery, and also when I plug my phone into a computer to re-install the stock ROM, it doesn't show up like it was previously when I tried rooting it. Also, sometimes another page shows which is the bootloader with ERROR CODE showing above it. Would appreciate any help on this.
kwabinca said:
Rooted my Honor 7x (Bnd-L21) recently, and I wanted to ues snapchat which wasn't working, due to my root status. So, I decided to try MAGISK, when I tried to unroot I stupidly went to TWRP Recovery and factory reset rather than going the safe route and un-rooting through SUPERSU. Now, when I tried boot up my phone it goes straight to the EMUI eRecovery, and also when I plug my phone into a computer to re-install the stock ROM, it doesn't show up like it was previously when I tried rooting it. Also, sometimes another page shows which is the bootloader with ERROR CODE showing above it. Would appreciate any help on this.
Click to expand...
Click to collapse
Plug in phone while usb is connected to pc, hold down vol - with power until in fastboot, flash this https://androidfilehost.com/?fid=962187416754474601 fastboot flash ramdisk RAMDISK.img
EDIT: assuming you are on oreo, if not do not do this
Not using Oreo
I am not on oreo, I rooted with the intention of being able to get oreo. Any other ideas? Thanks.
Today I flashed the newest OOS 10.0.3. After I had flashed it+TWRP through Magisk and rebooted, Vanced Youtube was not able to be installed correctly. I have fixed this earlier by uninstalling the Youtube app through a root-uninstaller app. Then flash Vanced in Magisk, and reboot.
After doing this, my phone would only bootloop into TWRP/Fastboot. So I tried to boot into TWRP, flash OOS 10.0.3, TWRP then Magisk, in TWRP, but no success. The phone would just bootloop. So I tried my final attempt without having to wipe the whole phone - Flash an old backup (I think it was from October, probably OOS 10.0.1). After doing a full recovery in TWRP with the old backup, my phone boots into Qualcomm CrashDump Mode with a message displaying
dm-verity device corrupted Force Dump
Kernel_restart
Click to expand...
Click to collapse
By holding power+volume up for 10 seconds, my phone reboots displaying the warning message about my phone's bootloader being unlocked, then shows the quoted message above.
Could anyone please help me fix this?
---
Update:
So after trying to reboot for 15+ times, my phone somehow booted into TWRP. What would be the best step now?
Wipe all, flash OOS 10.0.3, Flash TWRP and Flash Magisk?
Which specific model do you have, region? Which twrp was used?
Werchio said:
Today I flashed the newest OOS 10.0.3. After I had flashed it+TWRP through Magisk and rebooted, Vanced Youtube was not able to be installed correctly. I have fixed this earlier by uninstalling the Youtube app through a root-uninstaller app. Then flash Vanced in Magisk, and reboot.
After doing this, my phone would only bootloop into TWRP/Fastboot. So I tried to boot into TWRP, flash OOS 10.0.3, TWRP then Magisk, in TWRP, but no success. The phone would just bootloop. So I tried my final attempt without having to wipe the whole phone - Flash an old backup (I think it was from October, probably OOS 10.0.1). After doing a full recovery in TWRP with the old backup, my phone boots into Qualcomm CrashDump Mode with a message displaying
By holding power+volume up for 10 seconds, my phone reboots displaying the warning message about my phone's bootloader being unlocked, then shows the quoted message above.
Could anyone please help me fix this?
---
Update:
So after trying to reboot for 15+ times, my phone somehow booted into TWRP. What would be the best step now?
Wipe all, flash OOS 10.0.3, Flash TWRP and Flash Magisk?
Click to expand...
Click to collapse
TWRP?! There are no working twrps for 7T series.
gpz1100 said:
Which specific model do you have, region? Which twrp was used?
Click to expand...
Click to collapse
Oneplus 7, EU region (guacamoleb). TWRP that I have managed to boot into is 3.3.1-70.
Aswin08 said:
TWRP?! There are no working twrps for 7T series.
Click to expand...
Click to collapse
My bad. It is a Oneplus 7 Guacamoleb, TWRP version is 3.3.1-70
Oneplus 7T Qualcomm CrashDump Mode
Hi Everyone,
My OnePlus 7T got stuck in QUALCOMM CRASHDUMP MODE.
First, i wanted to know the reason why this crash is happening as i can see many users reporting the same in many forums.
Note : It is my brand new phone purchased 2 days back.
Thanks !!
Restor your firmware with the msmtool
Here are the drivers that are installed on my PC ( I enabled hidden devices, in order to see them ) These were recognizing prior to " qualcomm crash dump" .
Now ADB,Fastbootd and Windows 10 / Mac OSx do not see my device, let alone recognize
It's possible that your phone is corrupted. Double freezer bag phone, express all excess air out from bag, zip both bags tightly, stick phone in freezer for 1 hr to deplete battery, then try buttons and msmtool
Hello folks !
So I just got my hands on a Redmi Note Pro 8:
Model - M1906G7G
MIUI Version - Global 12.0.5 Stable (QGGMIMX)
Android Version - 10 QP1A.190711.020
Kernel Version - 4.14.141-G78546ce
Click to expand...
Click to collapse
Since I'm a longtime custom ROM user on my previous Android devices, I wanted to go for it and install [ROM][CFW][10][begonia] Pixel Experience [OFFICIAL][AOSP] but I ended up being stuck in a bootloop.
The bootloader unlock went fine, but I couldn't find a functioning TWRP recovery that doesn't end up with an infinite bootloop.
Then I stumbled upon a LRTeam recovery and things went fine from there. I was able to access the custom recovery menu.
I taped on the "Install root" feature after that but when rebooting, the phone went bootlooping on that Redmi logo.
Even after pushing recovery and try and install Magisk over zip install, the same thing occurs, eternal bootloop.
Since fastboot was always accessible, I managed to successfully flash the device back to stock with XiamiToolsV2 and even when trying the process again, I couldn't manage to go further in the install.
What seems to be the problem? Am I missing something?
Thanks a lot lads !
Downgrade to android 9 and read the megathread
I tried for like 3 hours to find a boot.img and i had root on my phone, but without wifi and sound.
a quick google search showed me that it was because i had a wrong version of the boot.img, afterwards i found another one and now after i have tried installing twrp, booting and flashing using adb (stock and modified versions of boot.img) but it just keeps bootlooping. in twrp i cant wipe, make a backup, see any files in /storage/ and i have no clue what to do next.
What model 7T do you have? HD1907? What was the rom that you were using before you installed TWRP on? OOS12 does not support TWRP. Custom rom A13 does not support TWRP. Only a few custom rom A12 and OOS11 support TWRP.
Idk but I'm just wondering if flashing the last working rom image (dirty flash)? That would eliminate TWRP(?) and eliminate Magisk(?) while hopefully keeping the device from being wiped possibly?
*** Hopefully someone could/would verify this before you attempt... ***
i was on android 11 but i cant remember the version, i have HD1903 (EU ver). i THINK i had the one from the oneplus website(https://service.oneplus.com/us/search/search-detail?id=2096229) but idk anymore
I JUST RANDOMLY TRIED BOOTING MY PHONE AGAIN AND IT WORKED imma check if everything works and will regardless still look at this thread bc it can prob break easily
nah wifi and sound still dont work, but im not in bootloop anymore
MimKA22 said:
I JUST RANDOMLY TRIED BOOTING MY PHONE AGAIN AND IT WORKED imma check if everything works and will regardless still look at this thread bc it can prob break easily
nah wifi and sound still dont work, but im not in bootloop anymore
Click to expand...
Click to collapse
Msmtool back to oos11
can you describe how to use it or send a link to tutorial or smth thx man <3
MimKA22 said:
can you describe how to use it or send a link to tutorial or smth thx man <3
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
i cant find the file for my current version and it doesnt work if i try it with the only version that is android 11
and i cant turn my phone back on
and after i installed the drivers i had to restart my pc and now there is this thing at the bottom right:
testmode
windows 10 pro
...
i waited until my phone had no more battery charge and now im bootlooping again :/
nvm it just booted
im downgrading it now and i dont get the error "smth communication smth" in msmtool anymore
alr it worked my phone is wiped again but i can turn on wifi and sound
but how do i root my phone now? I have an Idea, im gonna write step by step what i think gets me a rooted phone please confirm if that would not break my phone ^^' (bootloader already unlocked)
1. enable usb debugging and allow my pc
2. download and install the latest magisk version from the github
3. download magisk patched boot.img for ver 11.0.5.1BA BUT since i cant find anything on the internet im gonna have to use the zip file from the unbrick tool thing (https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7T/EU_HD65BA/R/) and then patch the boot.img using magisk myself
4. then use platform tools and type following commands: "adb reboot fastboot", "fastboot flash boot {the patched boot image file}"
5. then use magisk to direct install the root thing
i just realisized the unbrick thing that i wanted to use instead of a boot.img doesnt have a boot.img in it... WHERE CAN I FIND A BOOT.IMG brooo androidfilehost.com doesnt have it the unbrick tool doesnt have it
omg i realized i could update my phone to 11.0.9.1 then download the same version from official website and use the dumper to get the boot.img **** meee
wait it sais its 11.0.9.1HD65 AA and not BA **** me
k nvm i just changed the site settings to germany and now its BA
i just went for it and now my phone is rooted thank you very much for your help i would've prob tried to revert back to stock for like 2 weeks and then cry that i cant root my phone thank you so much xd
2125 AA model OPO9
So my phone has been nagging me to upgrade to A13 for awhile now and I decided to finally bite the bullet and do it, so I backed up everything before I did it.
Now previously, to keep Magisk, I was following the guide to restore the image, do the upgrade, then flash magisk in the inactive slot. But from reading it sounded like after I upgraded to A13, I needed to go into fastboot and boot off the magisk'ed boot image. So I restored the image in magisk and then upgraded to A17 and rebooted, then to A18 (as I had the A18 boot images) and rebooted. Everything came up fine. However, as soon as I boot into the bootloader, I see if for a split second and then it immediately crashes into the Qualcomm crash dump screen. I can still reboot into the OS but I'd really like to have Magisk back if possible.
Edit (More info): When I reboot, I do get a new notice on the pre-boot screen that the device is unlocked that I didn't see before when I was on A12. In addition, in the OS, the OEM unlock is greyed out (with bootloader unlocked) and will not let me lock it again.
My current state is a working phone on A17/F18 with no root but would like to get root back (and a working bootloader for peace of mind).
So I guess my questions are:
1) Is there still a way I can get Magisk in my current state. Without the bootloader I'm assuming I'm SOL...
2) Would a factory reset from within the OS fix the bootloader?
2) If I need to use the MSM tool, where can I find the qualcomm drivers? I found one link but it was a CAB file and I could not get anything working out of that.
jbradshw said:
2125 AA model OPO9
So my phone has been nagging me to upgrade to A13 for awhile now and I decided to finally bite the bullet and do it, so I backed up everything before I did it.
Now previously, to keep Magisk, I was following the guide to restore the image, do the upgrade, then flash magisk in the inactive slot. But from reading it sounded like after I upgraded to A13, I needed to go into fastboot and boot off the magisk'ed boot image. So I restored the image in magisk and then upgraded to A17 and rebooted, then to A18 (as I had the A18 boot images) and rebooted. Everything came up fine. However, as soon as I boot into the bootloader, I see if for a split second and then it immediately crashes into the Qualcomm crash dump screen. I can still reboot into the OS but I'd really like to have Magisk back if possible.
Edit (More info): When I reboot, I do get a new notice on the pre-boot screen that the device is unlocked that I didn't see before when I was on A12. In addition, in the OS, the OEM unlock is greyed out (with bootloader unlocked) and will not let me lock it again.
My current state is a working phone on A17/F18 with no root but would like to get root back (and a working bootloader for peace of mind).
So I guess my questions are:
1) Is there still a way I can get Magisk in my current state. Without the bootloader I'm assuming I'm SOL...
2) Would a factory reset from within the OS fix the bootloader?
2) If I need to use the MSM tool, where can I find the qualcomm drivers? I found one link but it was a CAB file and I could not get anything working out of that.
Click to expand...
Click to collapse
Google for latest Qualcomm 9008 USB drivers
TheGhost1951 said:
Google for latest Qualcomm 9008 USB drivers
Click to expand...
Click to collapse
Is MSM my only option here then?
jbradshw said:
Is MSM my only option here then?
Click to expand...
Click to collapse
If you want a fresh start and try all over again with less hassle!