Lets start off with telling you i am a newbie and was just following tutorials without really knowing what i was doing.
That said, i tried to install a custom ROM but got an error (7) in TWRP. Decided to reflash my old rom and update TWRP using the official TWRP app.
So i did that but when i wanted to boot into recovery it was stuck on the oneplus screen. I went into fastboot and typed fastboot oem unlock because i thought i could flash TWRP that way if the bootloader was unlocked.
When i tried to restart it gave me nothing but the oneplus screen, even the bootloader wont start. I shut it off completely and now it doesn't give me anything at all - just black.
Can someone help me out?
EDIT:
Issue resolved using THIS. Tyvm
I really don't know what is left to do, I always end up with a bootloop and have to repair my phone with flashtool. I have tried flashing twrp by adb/fastboot, temporarily booting to twrp, flashing different twrp files after repair.... I always get boot loop. Help please :/
Once I had my phone rooted by oneclickroot support, then I started to get play store crashed constantly. Once I booted to recovery and when try to reboot, got a bootloop. I tried to flash a new rom, so found a stock rom for Z5C and flashed it by twrp. But after a reboot I lost the twrp recovery this time. Then I tried to flash the recovery myself using abd, following the basics; fastboot flash boot boot.img/recovery recovery.img But I again stuck into a bootloop. Repaired again... I thought flashing a custom recovery breaks the phone, so I decided to just boot the recovery and install supersu. but again a bootloop in the end.
Is your bootloader already unlocked?
Gewiz said:
Is your bootloader already unlocked?
Click to expand...
Click to collapse
yes sir, already.
flash complete stock, no modifications.
confirm if it loads to usermode
NeoBeum said:
flash complete stock, no modifications.
confirm if it loads to usermode
Click to expand...
Click to collapse
I have flashed the lastest stock ftf by flashtool, that is what I do after everytime I brick it while trying to obtain root. And if you mean switching to another user, yes it does.
that's good. it means hardware is fine.
it's your root method.
try this
https://forum.xda-developers.com/showthread.php?t=3609358
Hey guys ,
I unlocked bootloader and flashed official twrp via fastboot . I successfully booted into twrp but when I click reboot my phone stuck on mi boot logo . I personally tried many thing to tackle this problem. But every time I got same thing . Can anyone solve this ?
Redwolf twrp is working fine .
Yes, happend the same to me, basically what's happening is that your phone can't decrypt itself in the boot.
What's the fix? Flash twrp, go into it
Then wipe EVERYTHING,even format.
That will be you new partitions (new encryption) in your phone.
Then with everything formated, plug your phone in twrp and copy whatever you want, and viola.
You're done, copy the rom you want to flash and will boot.
Please let me know when your phone is fixed.
Or you can just root your device
I had the same issue as you yesterday.
You can try lazyflasher to prevent bootloop
hi
my phone is stuck on the teamwin bootlogo.
cant do anything
can you please help
Yeahmään said:
hi
my phone is stuck on the teamwin bootlogo.
cant do anything
can you please help
Click to expand...
Click to collapse
What were u doing when u got stuck?
I flashed a recovery then a rom after that I made a reboot and and got stuck
Hi there,
Mine is doing the same, did you find a fix for this?
LDP12 said:
Hi there,
Mine is doing the same, did you find a fix for this?
Click to expand...
Click to collapse
What you did it to get stuck on the teamwin bootlogo?
Even for me it gets stuck. I usually get it stuck if i use recovery option under twrp (for e.g. recover anything via twrp backup, may be my nandroid backup). The device successfully recovers, but thereafter twrp is no longer usable even after uninstalling and reinstalling it. The only way I am left out with is to remove twrp and perform a factory reset(but via erecovery) or just dload again.
there are 2 different twrp recovery, one is which work only with emui, other are which works with emui and custom rom (maybe decryption will not work with second)
if you will use second twrp what are treble enabled, then you shuld be able to use twrp with custom rom
ofcorse, if you flash wrong twrp, what isnt meant for your device, you will be stuck on twrp logo too!
there are twrp treble for p20 lite : https://forum.xda-developers.com/huawei-p20-lite/development/recovery-twrp-3-2-1-0-t3782866
kilroystyx said:
What you did it to get stuck on the teamwin bootlogo?
Click to expand...
Click to collapse
Hi, thanks for your reply. I actually found a twrp that works fine (no decryption though, as you mentioned, which is a bit of a pain but at least it works). I just fastboot flashed recovery_ramdisk - sorted.
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
AhmedRadowan25 said:
Do you have any suggestions on what I can do?
Click to expand...
Click to collapse
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
AhmedRadowan25 said:
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
Click to expand...
Click to collapse
Here's a complete explanation what I have done:
Initially, I was running stock MIUI with root access and TWRP recovery. However, I decided to switch to the Pixel Experience ROM. I downloaded the Pixel Experience Android 11 version and flashed it directly from TWRP since I didn't have access to a PC at that time. I only flashed the ROM file and didn't install the Pixel Experience recovery image, assuming that my TWRP would remain intact. But when I rebooted into recovery after the ROM installation, it booted into the Pixel Experience recovery instead. I couldn't find an option to flash the recovery image, only an option to apply an update through ADB sideload.
Fortunately, I managed to use a friend's computer and installed all the necessary ADB and Fastboot drivers. The computer could detect my phone in ADB sideload mode, but when I tried to boot into the bootloader, the PC couldn't detect my phone. Despite multiple attempts of booting into the Pixel Experience recovery and enabling ADB sideload, the PC couldn't recognize the fastboot mode. Strangely, every time I booted into the bootloader, my phone automatically powered off after displaying the Redmi logo. Holding the power button didn't help as it consistently powered off after showing the logo, without accessing the bootloader or recovery mode. I was afraid my phone had become completely unresponsive.
After numerous attempts, my phone unexpectedly booted into the bootloader again. This time, I connected my phone to another device using BugJagger, which successfully detected my phone. I used the command "fastboot flash recovery twrp.img" followed by "fastboot boot twrp.img" to open TWRP. However, I couldn't decrypt it using my password. I then flashed TWRP again and tried to boot into the system, but it always reverted back to the bootloader. I went back into recovery, selected partitions A to B, and flashed Magisk ZIP, DM variety ZIP, and LazyFlasher ZIP (without fully understanding their purpose).
Finally, my phone successfully booted into the system. However, upon rebooting into TWRP and then rebooting the system without any changes, my settings app and bluetooth stoped working. To resolve this, I had to boot into TWRP once again, format the data, and flash Magisk to restore normal operation.
alonsoj636MW said:
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
Click to expand...
Click to collapse
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
AhmedRadowan25 said:
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
Click to expand...
Click to collapse
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
Thank you very much.Flashing miui will solve all probem?what do you think?
AhmedRadowan25 said:
what do you think?
Click to expand...
Click to collapse
it should
at least when i mess up with my phone flashing stock fixes all problems
Hi mate! Did you resoved the problem? What about the rom? All good?
gabsvm1 said:
Hi mate! Did you resoved the problem? What about the rom? All good?
Click to expand...
Click to collapse
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
AhmedRadowan25 said:
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
Click to expand...
Click to collapse
No problem mate, besides that everything is working good? You have tried a13 roms before?
gabsvm1 said:
No problem mate, besides that everything is working good? You have tried a13 roms before?
Click to expand...
Click to collapse
No
Who told you to flash DM Verity and Lazy Flasher
We don't need these things in our device
Don't mess up with Active Slot
If you try to change your Active slot into Inactive slot, once you Reboot to system, you will go straight to fastboot
You need Android Bootloader Interface to detect your phone in bootloader and ADB Composite to detect your phone in ADB, such as : Google USB Driver r13
Why you don't ask before doing anything, we have global community chat in telegram, for sure, we will help you in possible way
I assume you need back to stock rom to fix this issue
hit me on tele t.me/super_img