Develop Bugs

[Q] Bootloop (softbrick to hardbrick back to softbrick)

Long story short:
EDIT: I somehow magically (after 2 hours of trying) got into recovery, cleaned and wiped everything and booted into MIUI. Switched to CM 12.1, leaving this thread for anyone that experiences the same problem.
1. I was running CM11-R24, with an early version of the Xcelerate kernel. All was fine and well but today it restarted on its own a couple of times. It would enter a bootloop that I managed to get out of by going into recovery and rebooting from there.
2. Bootloop happened again, couldn't get into recovery.
3. Installed newest twrp recovery via fastboot. No change.
4. Managed to hardbrick my phone by installing a wrong .img of a global version.
5. Managed to revert back to a softbrick by installing the right (hopefully) global version of my mobile phone.
6. I did manage to read a logcat inbetween and I remember there being something about the kernel settings being nulled to default, because there was a failed boot 2 times in a row.
Links:
Hard-brick to soft-brick procedure I followed - http en.miui.c o m thread-54139-1-1.html
Used global version: Singapore 50? Going to try other versions
Settings in MiFlash tool (using 2014.11 version). - http postimg.o r g /image/hh122e54j
Current problems:
1. When powering up the phone, it will not go beyond the Mi logo.
2. When trying to enter recovery (volup+power) I enter another loop. It is normally 10-15 seconds of Mi logo, power down, 3-5 seconds of Mi logo, power down. Repeat. I do not stop holding the recovery combination while this happens.
3. I have installed via fastboot all of these recoveries - TWRP 2830, TWRP 2860, Philz latest recovery. After installing each of them, I can not enter recovery mode again. Flashing a new recovery doesn't seem to change that.
I have access to fastboot, currently I installed the stable fastboot rom version "armani_images_JHCCNBH45.0_4.3_cn_e7e373f319".
I can not get adb to recognize the device, only fastboot. Can't get a logcat because of it. If you think I might be doing it wrong, please walk me through the process.
How do I get it back to working condition? The phone was bought in Bulgaria from a retailer, but I don't know which country it was originally shipped from, only that it's a WCDMA version.

Throw it away and get your self some reliable phone unlike redmi , it's a crap lots of issue ... I prefer Motorola .

ford.sushil said:
Throw it away and get your self some reliable phone unlike redmi , it's a crap lots of issue ... I prefer Motorola .
Click to expand...
Click to collapse
Oh oh oh don't be rude everyone has his own priorities and financial limitations

Bootloop
Dude, I have the same problem, can you help plus?

Soft Bricked Huawei Watch

Hi everyone
Saw some threads related to Huawei watches getting bricked. But mine is kinda ok. Here is my case:
My Huawei watch was running Android 2.0
I wanted to try out the Negalite Rom. I have some experience in flashing android phones so I went ahead and did as follows:
Booted into fastboot (using adb)
Unlocked oem
Flashed boot image
Flashed twrp
Then flashed system image
I rebooted to system but it took me back to twrp
I tried sideloading adb in twrp and flash the Negalite rom but it gives me the Error 7
Any hope left for me :crying:

[Help] Oneplus 7T Qualcomm CrashDump Mode

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

What Are My Options?

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.

Question TWRP and the current version of OS as right now, both OEM and bootloader already unlocked

Unfortunately, I already did open TWRP by CMD: C:\fastboot boot TWRP.img and I didn't understand at all because there were no partitions in there, plus I already did flash TWRP 3 times. So itself, TWRP won't take to OS itself (stuck boot loop), and it was awful because there was no way I could flash it back to where it was because of NO partitions in TWRP at ALL!... I do NOT UNDERSTAND at ALL!!! So I had to force it to do MsmDownloadTool V4.0 because there is only one way to restore it to my phone because it seems to work fine, but... I am still puzzled about what is going on because this is my first time. It never happened to me before, this is NOT NORMAL because I knew I had my phone U11 and M8 with that TWRP, and it worked fine until now with OP9P, those very different designs I never had before!
Model: LE2127
Android Version: 12 (LE2127_11_C.17) - - April 2022 update
(OP9P = OnePlus 9 Pro)

TWRP doesn't work with A12.

ffejy462 said:
TWRP doesn't work with A12.
Click to expand...
Click to collapse
This, decryption isn't supported AT ALL by any recovery running on A12. I've seen modified recoveries for A12 for other devices and it seems they try to disable forced encryption which is a BAD idea!
If you want to decrypt, would recommend either staying with OOS 11 or a custom ROM on A11. Bear in mind there have been numerous reported issues with TWRP hence why most custom ROMs for the OP9P choose to stick to LineageOS recovery.

cat139lyleb said:
Unfortunately, I already did open TWRP by CMD: C:\fastboot boot TWRP.img and I didn't understand at all because there were no partitions in there, plus I already did flash TWRP 3 times. So itself, TWRP won't take to OS itself (stuck boot loop), and it was awful because there was no way I could flash it back to where it was because of NO partitions in TWRP at ALL!... I do NOT UNDERSTAND at ALL!!! So I had to force it to do MsmDownloadTool V4.0 because there is only one way to restore it to my phone because it seems to work fine, but... I am still puzzled about what is going on because this is my first time. It never happened to me before, this is NOT NORMAL because I knew I had my phone U11 and M8 with that TWRP, and it worked fine until now with OP9P, those very different designs I never had before!
Model: LE2127
Android Version: 12 (LE2127_11_C.17) - - April 2022 update
(OP9P = OnePlus 9 Pro)
Click to expand...
Click to collapse
It's because you flashed an incompatible TWRP (not compatible with Android 12 ROMS)

Okay, maybe TWRP is already aware of this problem with 12 ROMS, plus I already did tried a few times with OEM unlock in 11, but no luck. So that's why OEM unlocked in 12... very weird...
The bootloader won't unlock until OEM unlocks in any android versions. So first, that's why.

I have a question about that. Do you think it's why -> SECURE BOOT - YES?
Then how do we make it say NO?
Because we are aware that it is FULLY unlocked as DEVICE STATE - UNLOCKED, correct?