Question Bricking randomly - Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40

I have been in the andorid moding since the clockworkmod recovery era.(andorid 4) I have nvr seen something so unusual. I was booting into recovery(twrp), I was about to install magisk but i couldnt find the zip file, so I was going to boot into system. And when it was booting. The first time boot bar thingy showed up(pixel experience) which mean it is usually bricked in the os. Has anyone have the same experience? Now I have to reinstall Pixel experience and lose data. Wow.

ClockWorkModEra said:
I have been in the andorid moding since the clockworkmod recovery era.(andorid 4) I have nvr seen something so unusual. I was booting into recovery(twrp), I was about to install magisk but i couldnt find the zip file, so I was going to boot into system. And when it was booting. The first time boot bar thingy showed up(pixel experience) which mean it is usually bricked in the os. Has anyone have the same experience? Now I have to reinstall Pixel experience and lose data. Wow.
Click to expand...
Click to collapse
Bruh.
It's hard to understand what you're getting at. What is a Boot bar thingy? Please describe in proper english.

cyanGalaxy said:
Bruh.
It's hard to understand what you're getting at. What is a Boot bar thingy? Please describe in proper english.
Click to expand...
Click to collapse
Haha. Im new to the xda thingy sorry! So the boot bar im refering to is when the rom is booting for the first time and there will be a little bar at the bottom.

ClockWorkModEra said:
I have been in the andorid moding since the clockworkmod recovery era.(andorid 4) I have nvr seen something so unusual. I was booting into recovery(twrp), I was about to install magisk but i couldnt find the zip file, so I was going to boot into system. And when it was booting. The first time boot bar thingy showed up(pixel experience) which mean it is usually bricked in the os. Has anyone have the same experience? Now I have to reinstall Pixel experience and lose data. Wow.
Click to expand...
Click to collapse
i dont understand much about flashing custom roms without formating but apparently Android 11 and Android 12 are encrypted, so, you cant flash/boot any custom roms without formatting the data.

Related

Stuck at Google logo

I searched "stuck at google logo" and "stuck in bootloop on start up" and the only real suggestion I found was using Duece's bootloop tool, but I was hoping to not have to wipe all my data if ipossible.
here's my set up.
Jan factory image
latest twrp
the flash kernel 2.14
and latest magisk
nova launcher
not other mods or xposed
Getting stuck at logo has happened once or twice before, but restarting by pressing the power button has always brought it back.
Tonight, I had to hard restart 6 or 7 times before it rebooted successfully.
Any suggestions other than running the bootlooping script? I'd like to learn the manual way of fixing stuff if possible.
Thank you for any help.
andy6685 said:
I searched "stuck at google logo" and "stuck in bootloop on start up" and the only real suggestion I found was using Duece's bootloop tool, but I was hoping to not have to wipe all my data if ipossible.
here's my set up.
Jan factory image
latest twrp
the flash kernel 2.14
and latest magisk
nova launcher
not other mods or xposed
Getting stuck at logo has happened once or twice before, but restarting by pressing the power button has always brought it back.
Tonight, I had to hard restart 6 or 7 times before it rebooted successfully.
Any suggestions other than running the bootlooping script? I'd like to learn the manual way of fixing stuff if possible.
Thank you for any help.
Click to expand...
Click to collapse
Maybe try fastbooting the factory image with the -w removed out of the flash-all.bat file and then run the script. It won't wipe your data. Let the phone boot up, then go back to bootloader mode and fastboot twrp. Then you can flash the twrp zip, custom kernel, and magisk. Don't know if that'll solve your rebooting problem, but it's a start ?
On 8.0 Unlocked
Did everything you had done and got the same issue. Been over 40 minutes at the G logo with the loading thing on the bottom. Any advice on how to proceed?
DreyX said:
On 8.0 Unlocked
Did everything you had done and got the same issue. Been over 40 minutes at the G logo with the loading thing on the bottom. Any advice on how to proceed?
Click to expand...
Click to collapse
Any luck with a hard restart by holding the power button down?? What exactly did you try flashing?
First attempt was done via TWRP, Second attempt was done via Magisk. With both of them the message was shown that it had completed successfully. Though, after rebooting, the OS would get stuck at the G logo.
No idea on how to proceed honestly
DreyX said:
First attempt was done via TWRP, Second attempt was done via Magisk. With both of them the message was shown that it had completed successfully. Though, after rebooting, the OS would get stuck at the G logo.
No idea on how to proceed honestly
Click to expand...
Click to collapse
What attempt are you referring to?? Updating magisk???? ?
Badger50 said:
What attempt are you referring to?? Updating magisk???? ?
Click to expand...
Click to collapse
An attempt at installing Xposed. Both attempts after installing Xposed, doesn't allow me to get past the G logo anyhow.
I have factory restored the device a few times with the same results.
DreyX said:
An attempt at installing Xposed. Both attempts after installing Xposed, doesn't allow me to get past the G logo anyhow.
I have factory restored the device a few times with the same results.
Click to expand...
Click to collapse
Ah...gotchya. I don't do exposed, but these guys do. Best place for you to seek help my friend. Good luck :good:
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Sounds like you have tried to install a boot/dtbo that is a previous release instead of what is currently on the device. This happened to me. Flashing the correct version fixed my problem.
Sent from my Pixel 2 XL using Tapatalk
andrewjt19 said:
Sounds like you have tried to install a boot/dtbo that is a previous release instead of what is currently on the device. This happened to me. Flashing the correct version fixed my problem.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
p.s.: outdated Android Tools could be at fault...
If it is current, there is a flashing tool called Deuce's at https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761.
It has saved my bacon more than once while fiddling with rooting and recoveries.
andrewjt19 said:
Sounds like you have tried to install a boot/dtbo that is a previous release instead of what is currently on the device. This happened to me. Flashing the correct version fixed my problem.
Click to expand...
Click to collapse
I second this. Same thing happened to me. I had to reflash the previous image to get it to boot.

Cannot root my S9

Hi everyone,
this is crazy. I followed different guides on how to root my phone but I get the idea I really have to wait for 7 days to have another chance at rooting, or is this just a myth?
I installed twrp, flashed resurrection remix. I had problems with my camera when trying to record video. I always got green flickering on screen. also not able to record more than 60fps (why? isn't s9 supposed to?).
But what struck me most was the fact that my phone wasn't rooted. When installing supersu in the recovery I get the message "sepolicy failed" or something. I guess this is why I cannot root my phone? Installing superuser from the playstore shows me also that I am indeed not rooted.
What can I do? I am all out of ideas and websites...
Should I reflash stock and do the OEM and odin procedure again, and wait 7 days?
Nairozed said:
Hi everyone,
this is crazy. I followed different guides on how to root my phone but I get the idea I really have to wait for 7 days to have another chance at rooting, or is this just a myth?
I installed twrp, flashed resurrection remix. I had problems with my camera when trying to record video. I always got green flickering on screen. also not able to record more than 60fps (why? isn't s9 supposed to?).
But what struck me most was the fact that my phone wasn't rooted. When installing supersu in the recovery I get the message "sepolicy failed" or something. I guess this is why I cannot root my phone? Installing superuser from the playstore shows me also that I am indeed not rooted.
What can I do? I am all out of ideas and websites...
Should I reflash stock and do the OEM and odin procedure again, and wait 7 days?
Click to expand...
Click to collapse
Try use magisk 16.6 for root issues, ofc when you use custom rom you dont get full camera potential and these green flickers are just minor cosmic bugs.
"Myth" might want to read up more.
You need to flash twrp and flash the no verity file then flash the custom rom
Or even better, flash soldiers rom instead of the resurrection remix. Didnt you read that theres a camera problem?
Better use magisk for rooting btw, use the 16.6
Now I am in a never ending boot sequence loading resurrection remix. I can only hard reset and enter twrp.
I don't know if the installation or magisk did it, because I cannot boot to the system.
anyideas?
Nairozed said:
Now I am in a never ending boot sequence loading resurrection remix. I can only hard reset and enter twrp.
I don't know if the installation or magisk did it, because I cannot boot to the system.
anyideas?
Click to expand...
Click to collapse
try flash rom + gapps and boot system after that boot recovery and flash magisk 16.6 and boot system
Thanks for the advice. I flashed back to stock firmware to have the zerocam mod working perfectly. But now my lockscreen freezes after a few minutes. So I tried to deactivate my phone going into lockscreen. I get the Black screen of Death now instead when the display turns off into sleep mode. Only way out is rebootingby hard reset, power button+volume down.
What can I do?.... Thanks for Any further advice.

UNABLE TO BOOT ANY ROM AFTER LATEST GApps INSTALLATION

Hi people,
Today I unlocked my Lenovo ZUK Z2 Plus and installed latest twrp recovery 3.3.1 successfully(no errors until now, butter smooth). After that I flashed "CARBON-CR-7.0-OPAL-RELEASE-z2_plus-20200122-0608" without installing GApps. This time the ROM booted successfully. I was able to use the phone and make calls.
Then I installed the GApps " open_gapps-arm64-9.0-stock-20200131.zip" downloaded from OpenGApps.org. This time around, when I booted after installing GApps, the phone showed the welcome screen, but got suddenly turned off. After that the phone just shows ZUK logo and keeps rebooting.
To fix this, I went to recovery again, wiped clean DATA & DALVIK CACHE & CACHE & SYSTEM & VENDOR partitions, hoping I would start from the beginning and again install only ROM and not GApps and hoping I would be able to use the phone.
Now this time around, even though I wiped every partition that TWRP shows, the phone just kept rebooting without starting Android OS. So I cleaned again everything using TWRP(cleaning DATA procedure) and then transferred ROM zip files to phone and again flashed only ROM. Still the phone kept rebooting.
Now I got pissed off. I flashed factory ROM using QFIL method. This time after the boot animation it went straight to "Shutting Down" dialogue and again the phone restarted.
CAN SOMEBODY TELL ME WHAT THE HELL IS EXACTLY WRONG WITH MY PHONE?
WHAT COULD HAVE GONE WRONG THAT EVEN AFTER CLEANING ALL THE PARTITIONS AND FLASHING USING THE FACTORY PROCEDURE, THE PHONE STILL KEEPS REBOOTING?
Is there any other partition that needs to be cleared(which the TWRP does not list)?
Can somebody just tell me how to get out of this?
(Please explain the steps and the reason for each, as I am a noob in this matter).
WAITING FOR ANYBODY'S PROMPT RESPONSE AS MY PHONE IS COMPLETELY UNUSABLE. THANKS IN ADVANCE.
what ZUI version you flashed with QFIL ?
AndroidUser5 said:
Hi people,
Today I unlocked my Lenovo ZUK Z2 Plus and installed latest twrp recovery 3.3.1 successfully(no errors until now, butter smooth). After that I flashed "CARBON-CR-7.0-OPAL-RELEASE-z2_plus-20200122-0608" without installing GApps. This time the ROM booted successfully. I was able to use the phone and make calls.
Then I installed the GApps " open_gapps-arm64-9.0-stock-20200131.zip" downloaded from OpenGApps.org. This time around, when I booted after installing GApps, the phone showed the welcome screen, but got suddenly turned off. After that the phone just shows ZUK logo and keeps rebooting.
To fix this, I went to recovery again, wiped clean DATA & DALVIK CACHE & CACHE & SYSTEM & VENDOR partitions, hoping I would start from the beginning and again install only ROM and not GApps and hoping I would be able to use the phone.
Now this time around, even though I wiped every partition that TWRP shows, the phone just kept rebooting without starting Android OS. So I cleaned again everything using TWRP(cleaning DATA procedure) and then transferred ROM zip files to phone and again flashed only ROM. Still the phone kept rebooting.
Now I got pissed off. I flashed factory ROM using QFIL method. This time after the boot animation it went straight to "Shutting Down" dialogue and again the phone restarted.
CAN SOMEBODY TELL ME WHAT THE HELL IS EXACTLY WRONG WITH MY PHONE?
WHAT COULD HAVE GONE WRONG THAT EVEN AFTER CLEANING ALL THE PARTITIONS AND FLASHING USING THE FACTORY PROCEDURE, THE PHONE STILL KEEPS REBOOTING?
Is there any other partition that needs to be cleared(which the TWRP does not list)?
Can somebody just tell me how to get out of this?
(Please explain the steps and the reason for each, as I am a noob in this matter).
WAITING FOR ANYBODY'S PROMPT RESPONSE AS MY PHONE IS COMPLETELY UNUSABLE. THANKS IN ADVANCE.
Click to expand...
Click to collapse
Greetings buddy,
For my interest, i would like to know that the carbon rom u flashed was based on Android 9 or Android 10????
arielcasari said:
what ZUI version you flashed with QFIL ?
Click to expand...
Click to collapse
zui 2.5 st which is meant for indian users.
Naresh Rawat said:
Greetings buddy,
For my interest, i would like to know that the carbon rom u flashed was based on Android 9 or Android 10????
Click to expand...
Click to collapse
android 9.0.
what could be the problem... what do you think?
AndroidUser5 said:
android 9.0.
what could be the problem... what do you think?
Click to expand...
Click to collapse
I m at job so i reply late. No offense please ???
Ok plz let me know that if ur device boots up to fastboot mode. If yes then repeat the whole process but this time try installing different twrp. U can also use (https://www.androidfilehost.com/?a=show&w=files&flid=38683) tool kit for flashing. (DO NOT TRY TO RELOCK BOOTLOADER USING THIS TOOL) Also use flame gapps.
Will catch u soon regarding ur issue.
Peace out n TY???
Naresh Rawat said:
I m at job so i reply late. No offense please
Ok plz let me know that if ur device boots up to fastboot mode. If yes then repeat the whole process but this time try installing different twrp. U can also use (https://www.androidfilehost.com/?a=show&w=files&flid=38683) tool kit for flashing. (DO NOT TRY TO RELOCK BOOTLOADER USING THIS TOOL) Also use flame gapps.
Will catch u soon regarding ur issue.
Peace out n TY
Click to expand...
Click to collapse
i have already tried using twrp 3.2, but no luck. I will try flame gapps and will let you know. i will try this coming saturday.
Dhanyavad.
Naresh Rawat said:
I m at job so i reply late. No offense please
Ok plz let me know that if ur device boots up to fastboot mode. If yes then repeat the whole process but this time try installing different twrp. U can also use (https://www.androidfilehost.com/?a=show&w=files&flid=38683) tool kit for flashing. (DO NOT TRY TO RELOCK BOOTLOADER USING THIS TOOL) Also use flame gapps.
Will catch u soon regarding ur issue.
Peace out n TY
Click to expand...
Click to collapse
I again flashed the Stock ZUI 2.5. ST ROM using QFIL. But before doing this I had moved the SIM Card to another fone, so this fone was without any connection. This time the fone booted up successfully. Then I reflashed the Carbon ROM mentioned before and flashed Flame GApps Basic edition as suggested by you. This time the fone booted up successfully. But as soon as I connected the fone to internet, it downloaded something from Google Play Services in the background and again it started the same problem.
SO BASICALLY WHEN IT DOWNLOADS SOMETHING FROM GOOGLE IN BACKGROUND, IT STARTS THE REBOOTING NONSENSE.
I searched the internet for this and some articles on the internet suggested that "Google Dialer" component is causing reboot. Those articles suggested that if the "Google Dialer" is not set as the default dialer, it reboots. BUT HOW TO SET IT AS DEFAULT, WHEN IT STARTS REBOOTING IMMEDIATELY AND IT DOES NOT GIVE ENOUGH TIME?
EVEN THE EARLIER GApps 9.0 stock package that I flashed had warned to set the "Google Dialer" as default, but upon boot up it kept rebooting.
Even initially I started this UNLOCKING AND CUSTOM ROM FLASHING exercise after the factory ROM started rebooting after updating "Google play services".
So this seems to me an issue from Google.
Has Google done this on purpose to make people switch older phones to new ones?(Because I own a total of 3 android devices and only this device is rebooting not the other ones).
Looking forward to your reply.
Greetings Buddy..how's life going??
Ok once again I hv read ur op regarding ur problems. Let's start from the beginning. Boot up to twrp and format the data first before wiping everything. Try flashing lineageOS 16 using official gapps. (Flash gapps along with the flashing ROM, same time. Because flashing gapps after ROM's 1st reboot may result synchronise error or sometime bootloop). If successful, then flash ur carbon ROM and see whether it boots up to normal or still gives such error.
BTW sorry for my late replies. Till then peace out
Naresh Rawat said:
Greetings Buddy..how's life going??
Ok once again I hv read ur op regarding ur problems. Let's start from the beginning. Boot up to twrp and format the data first before wiping everything. Try flashing lineageOS 16 using official gapps. (Flash gapps along with the flashing ROM, same time. Because flashing gapps after ROM's 1st reboot may result synchronise error or sometime bootloop). If successful, then flash ur carbon ROM and see whether it boots up to normal or still gives such error.
BTW sorry for my late replies. Till then peace out
Click to expand...
Click to collapse
I am now not able to boot any ROM. Just keeps rebooting after the ZUK splashscreen. Hence, I again reflashed the Recovery properly, using the procedure as before. Now I am not able to boot into the recivery, too.

TWRP for Sony XZ2c instead of Lineage Recovery?

Hi everyone
After some research, I can't find a succeful way to install TWRP recovery instead of Lineage stock recovery.
It's really embarasing because I'm currently setting up my brand new XZ2c compact to run the way I want it to on Lineage OS 17.1 with Magisk and Xposed modules, and I experienced 3 or 4 endless bootloop that led me to fully format my phone after bunch of hours setting it and tailoring it up... Huge waste of time, frustration overload, as you could expect. So, I really miss tremendous TWRP backup fonctionnality I used to run frequently on my old Z5c... :crying:
Does anyone here as figured out how to replace Lineage stock recovery on this device? Is so, I'd really to hear him out
Have a good week-end!
tomboudiboudi said:
Hi everyone
After some research, I can't find a succeful way to install TWRP recovery instead of Lineage stock recovery.
It's really embarasing because I'm currently setting up my brand new XZ2c compact to run the way I want it to on Lineage OS 17.1 with Magisk and Xposed modules, and I experienced 3 or 4 endless bootloop that led me to fully format my phone after bunch of hours setting it and tailoring it up... Huge waste of time, frustration overload, as you could expect. So, I really miss tremendous TWRP backup fonctionnality I used to run frequently on my old Z5c... :crying:
Does anyone here as figured out how to replace Lineage stock recovery on this device? Is so, I'd really to hear him out
Have a good week-end!
Click to expand...
Click to collapse
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
kurtn said:
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
Click to expand...
Click to collapse
Thanks for replying!
Ok, but if I want this recovery bootable permently away from my computer?
kurtn said:
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
Click to expand...
Click to collapse
Thanks for your (minimalist) advice. Literally just lost 1 hour fixing the bootloop it just caused by following it, I'm delighted.
Behind my post, I was hoping to find someone who could explain a bit more the process of replacing/flashing/booting/(wateveryouwanti'mnotanexpert) a recovery, and at the same time avoiding me wasting more hours in bootlooping/formating/reinstalling. Hopefully, this time I succeed to came out of the bootloop without formating and reseting eveything, but I almost lost my nerves.
All of this is a bit cloudy for me, could you (or someone else that would give me a little of his time to) be pedagogue and explain clearly the whole proccess (and especially what you should avoid if you don't want to get stuck in a bootloop/getting scarying corrupted device message) ?
No one?
tomboudiboudi said:
No one?
Click to expand...
Click to collapse
Wrong forum. Search in you device section.
Hi guys!
Today I tried again to install TWRP on my Sonyh Xperia XZ2C because LineageOS Recovery doesn't provide Nandroid backup, which is a shame.
I tried many ways described over the web, none of those worked, and I ended up with a boot loop at startup with that naughty message "your device is corrupted it cannot be trusted and will not boot". I can't boot to Lineage, neither to recovery. I'm stuck.
With device turned off, I can eventually press volume down, plug it to computer, access fastboot mode (blue led), flash+boot the LineageOSrecovery.img, then the device restart, Sony logo appears... and that's all, I'm stuck with logo in boot loop, and I can't go anywhere further.
I tried to change boot slot (without knowing if it could help with this problem at all) but I alway get "unknown option".
I'm panicking right now, I can't find any way out to this bootloop, if someone could help it will be sooo appreciated!
I tried hard to find a solution for 4 hours now, I'm completly stuck and I can't even sleep. That's why I finally reached out here.
tomboudiboudi said:
Hi guys!
Today I tried again to install TWRP on my Sonyh Xperia XZ2C because LineageOS Recovery doesn't provide Nandroid backup, which is a shame.
I tried many ways described over the web, none of those worked, and I ended up with a boot loop at startup with that naughty message "your device is corrupted it cannot be trusted and will not boot". I can't boot to Lineage, neither to recovery. I'm stuck.
With device turned off, I can eventually press volume down, plug it to computer, access fastboot mode (blue led), flash+boot the LineageOSrecovery.img, then the device restart, Sony logo appears... and that's all, I'm stuck with logo in boot loop, and I can't go anywhere further.
I tried to change boot slot (without knowing if it could help with this problem at all) but I alway get "unknown option".
I'm panicking right now, I can't find any way out to this bootloop, if someone could help it will be sooo appreciated!
I tried hard to find a solution for 4 hours now, I'm completly stuck and I can't even sleep. That's why I finally reached out here.
Click to expand...
Click to collapse
In fastboot mode you should be able to flash stock rom
Is there any way to make the device boot on the Lineage partition without wiping everything?
For an unknown reason, I succed to boot on Lineage Recovery (not TWRP) this morning. I flashed LineageOs rom.zip using adb sideload. After rebooting, the recovery tolds me that I had to wipe everything because the system partition seems to be corrupted, so I did.
I'm a bit tired to lost everything since I made all of this to do Nandroid backups with TWRP........ but I have a fresh new install, my phone works again so it's fine.
But I still need to make Nandroid backups.
Kurtn, you seem to have skills and knowledge. As you can see, I didn't succeed to boot Twrp since october 2020. I don't see why it would be impossible with my device, I'm probably messing something somewhere.
Would you share your knowledge and help me booting/flashing TWRP without bricking everything again?
Could you make an answer instead of a single smiley?
tomboudiboudi said:
Could you make an answer instead of a single smiley?
Click to expand...
Click to collapse
Sorry, i cant. I don't backup and I don't have an a/b device.
Ok, thanks anyway!
tomboudiboudi said:
I didn't succeed to boot Twrp since october 2020. I don't see why it would be impossible with my device, I'm probably messing something somewhere.
Would you share your knowledge and help me booting/flashing TWRP without bricking everything again?
Click to expand...
Click to collapse
Btw.
Code:
fastboot flash boot recovery.img
DOES install the recovery, since it's permanently flashed. Don't know why they (lineage) didn't change that.
kurtn said:
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
Click to expand...
Click to collapse
However @tomboudiboudi , you could boot twrp manually using
Code:
fastboot boot twrp.img
With that, twrp should appear and ask for a password to decrypt your userdata partition.
If that works, you could try to flash boot this very same twrp.img. Maybe you need an additional twrp.zip too which will be sideloaded within twrp itself.
A note for you which might help: I wanted to update my lineage recovery manually using fastboot (older lineage recovery to newer one) and found that nothing (except fastboot) was booting at all after flashing this.
However, after dirty flashing lineageOS.zip, everything worked fine again.
Keep in mind that flashing a recovery will modify your boot.img. If this one doesn't work / is corrupt etc., your os won't boot up.
User699 said:
Btw.
Code:
fastboot flash boot recovery.img
DOES install the recovery, since it's permanently flashed. Don't know why they (lineage) didn't change that.
However @tomboudiboudi , you could boot twrp manually using
Code:
fastboot boot twrp.img
With that, twrp should appear and ask for a password to decrypt your userdata partition.
If that works, you could try to flash boot this very same twrp.img. Maybe you need an additional twrp.zip too which will be sideloaded within twrp itself.
A note for you which might help: I wanted to update my lineage recovery manually using fastboot (older lineage recovery to newer one) and found that nothing (except fastboot) was booting at all after flashing this.
However, after dirty flashing lineageOS.zip, everything worked fine again.
Keep in mind that flashing a recovery will modify your boot.img. If this one doesn't work / is corrupt etc., your os won't boot up.
Click to expand...
Click to collapse
I fear you still haven't realized, what a/b means. The classic concept of having a recovery partition, where you can boot twrp at any time - doesn't apply.
kurtn said:
I fear you still haven't realized, what a/b means. The classic concept of having a recovery partition, where you can boot twrp at any time - doesn't apply.
Click to expand...
Click to collapse
You're right, there is no recovery partition.
As I said: Flashing a recovery.img will modify the boot.img.

Question Soft brick no backup

Hi all!
Long story short, I beefed it...
I tried flashing the unofficial twrp and accidentally did format all on spflashtool.
I'm two months in and for the life of me I can't fix my phone... I've even tried to learn how to write a custom OS myself to fix it but I'm definitely not smart enough.
So, here's where I'm at right now:
When I flash the engineering ROM, the phone boots normally and all that seems to work, but flashing the official MIUI causes a bootloop to the stock recovery.
In there, there's the message "NV data is corrupted".
I'm 2 months in now, so I've seen almost all google pages, so yes, I've tried flashing using the official tool, flashed vbmeta with --disable-verity and --disable-verification.
It's my phone and I have the box here, so I have both IMEI numbers which I managed to flash in the engineering ROM, but flashing the normal MIUI somehow deletes the IMEI numbers again.
I can get into fastboot so the bootloader is unlocked, but I can't boot into the system so I can't enable dev options.
please, if you can help I'm more than happy to answer any other questions and being called an idiot :')
help me, XDA, you're my only hope
check the link
BootLoop not letting me access fastboot
Okay so when I flashed Magisk boot image my device activated boot problems. And when I tried to access recovery mode via adb (from Android Studio), my phone entered a bootloop from which I cannot exit. Vol down + power buttons does not work...
forum.xda-developers.com
I'm in the same exact boat as you...That guide was absolute trash and I can't find anything.
historypm said:
I'm in the same exact boat as you...That guide was absolute trash and I can't find anything.
Click to expand...
Click to collapse
Hold tight, I'm very close to fixing it!
Got everything working except mobile network. As soon as I figure that out, I'll post a fix here
RadixMalum said:
Hi all!
Long story short, I beefed it...
I tried flashing the unofficial twrp and accidentally did format all on spflashtool.
I'm two months in and for the life of me I can't fix my phone... I've even tried to learn how to write a custom OS myself to fix it but I'm definitely not smart enough.
So, here's where I'm at right now:
When I flash the engineering ROM, the phone boots normally and all that seems to work, but flashing the official MIUI causes a bootloop to the stock recovery.
In there, there's the message "NV data is corrupted".
I'm 2 months in now, so I've seen almost all google pages, so yes, I've tried flashing using the official tool, flashed vbmeta with --disable-verity and --disable-verification.
It's my phone and I have the box here, so I have both IMEI numbers which I managed to flash in the engineering ROM, but flashing the normal MIUI somehow deletes the IMEI numbers again.
I can get into fastboot so the bootloader is unlocked, but I can't boot into the system so I can't enable dev options.
please, if you can help I'm more than happy to answer any other questions and being called an idiot :')
help me, XDA, you're my only hope
Click to expand...
Click to collapse
Good evening, sorry for my bad English, but I have the same problem when this happened, I had miui V13.0.7.0 there, I got bootlop, I loaded V12.5.2.0 there and the phone worked everything except the network, try and let me know
You have to download the firmware and paste it into the platform tools folder and click flash all.bat

Categories

Resources