Related
Hello All,
Hoping someone will be able to assist me, though I'm starting to lose hope.
I have spent all day so far reading threads, and trying various suggestions and fixes, but nothing has really helped and I'm beginning to think the phone may just be kaput.
Initial issue was nothing out of the ordinary; woke up to find the phone was not responding so pulled the battery. After putting the battery back in, the phone would no longer turn on. Uh oh. Did the obvious, repull the battery, try again. Nothing. Connect to charger (nothing happens, no charging icon on screen). At this point I think the battery has died so I bought a new one. No change, phone still won't turn on and nothing happens when I plug it in to charge.
So now I connect it to my PC, and I get the installing hardware message trying to install the APX stuff which fails. After some research, I manage to get the APX drivers installed such that the phone is detected when I plug it in. More research, decide to try the AOI Toolkit to backup everything first. This works ok.
So now I try and enter recovery mode via Power key + Volume Down key. Nothing. Ok, change the recovery image then. Device is not detected via ADB method. NVFlash method instead then. The bootloader loads fine, the screen wakes up and shows the S/W Download... message. I figure this is a hopeful sign. I try all 3 (ics-cwm-5, ics-cwm-6, twrp-2.5). They all flash successfully. However, I can't enter recovery mode with any of them. Once I disconnect the phone, insert the battery and then hold down the Power + Volume Down buttons, nothing ever happens.
I've also tried the LG Update Tool and the Smartflash options, but the phone is never detected.
As a last resort I repartitioned. This also worked ok, but still no recovery mode.
tl;dr
Phone won't turn on, show as charging, or enter recovery mode. Works when connected as APX with AOI Toolkit.
Am I missing something? Doing something wrong? Any assistance is greatly appreciated. Thx.
Bump
Okay, I'm bumping this thread myself (mostly because I'm an idiot and this could happen to me, too), but to give you my two cents: Have you tried the Full Brick Repair tool? You flash it through NVFlash and apparently "it cures any brick". Try it and tell us how it went.
NoDze said:
Okay, I'm bumping this thread myself (mostly because I'm an idiot and this could happen to me, too), but to give you my two cents: Have you tried the Full Brick Repair tool? You flash it through NVFlash and apparently "it cures any brick". Try it and tell us how it went.
Click to expand...
Click to collapse
Thanks for the suggestion. The flash process itself completed without issue, but still nothing once the battery is inserted and the power button is pressed. I'm going to assume there is some sort of hardware issue at this point and consider the phone officially dead. Now, where's my hammer...?
xda_fanboy said:
Thanks for the suggestion. The flash process itself completed without issue, but still nothing once the battery is inserted and the power button is pressed. I'm going to assume there is some sort of hardware issue at this point and consider the phone officially dead. Now, where's my hammer...?
Click to expand...
Click to collapse
Don't give up yet. Try smartflash and flash stock, or whatever. Seriously. Just keep on trying. I had a Samsung Captivate a year back and something similar happened where I woke up one beautiful morning, tried to unlock my phone: no response. I thought I had an SOD, so I pulled the battery out, reinserted: bootloop. Entered recovery, can't flash anything, unable to mount system/data partitions. Turns out my internal memory/ROM got fried. Yay. But until then, I tried every possible option. Wow, this turned out to be a bit depressing. Just try more stuff. After you've tried everything, and I mean everything, declare the phone dead.
I think i have a similar problem. Just woke up to find my phone to be dead. Tried the usual methods, nothing. Best it could do was from time to time show me a battery sign with a red triangle and a whtie exclamation mark in it. Then sometimes i manage to get into the recovery mode, there i tried practically everything. Used restore, it shows that restore was a success, but when i reboot my phone i get into an endless circle of bootloader icon appearing and dissappearing,
EDIT: somehow from the countless attempt it fired up.
Make sure to have the right bootloader before nvflashing unbrick roms....
xda_fanboy said:
Hello All,
Hoping someone will be able to assist me, though I'm starting to lose hope.
I have spent all day so far reading threads, and trying various suggestions and fixes, but nothing has really helped and I'm beginning to think the phone may just be kaput.
Initial issue was nothing out of the ordinary; woke up to find the phone was not responding so pulled the battery. After putting the battery back in, the phone would no longer turn on. Uh oh. Did the obvious, repull the battery, try again. Nothing. Connect to charger (nothing happens, no charging icon on screen). At this point I think the battery has died so I bought a new one. No change, phone still won't turn on and nothing happens when I plug it in to charge.
So now I connect it to my PC, and I get the installing hardware message trying to install the APX stuff which fails. After some research, I manage to get the APX drivers installed such that the phone is detected when I plug it in. More research, decide to try the AOI Toolkit to backup everything first. This works ok.
So now I try and enter recovery mode via Power key + Volume Down key. Nothing. Ok, change the recovery image then. Device is not detected via ADB method. NVFlash method instead then. The bootloader loads fine, the screen wakes up and shows the S/W Download... message. I figure this is a hopeful sign. I try all 3 (ics-cwm-5, ics-cwm-6, twrp-2.5). They all flash successfully. However, I can't enter recovery mode with any of them. Once I disconnect the phone, insert the battery and then hold down the Power + Volume Down buttons, nothing ever happens.
I've also tried the LG Update Tool and the Smartflash options, but the phone is never detected.
As a last resort I repartitioned. This also worked ok, but still no recovery mode.
tl;dr
Phone won't turn on, show as charging, or enter recovery mode. Works when connected as APX with AOI Toolkit.
Am I missing something? Doing something wrong? Any assistance is greatly appreciated. Thx.
Click to expand...
Click to collapse
Try to flash a new recovery image in apx mode.
And edit the /dev/block/mmcblk0p3 partition your self.
seek=6144 count=75 bs=1 / boot-recovery
Thanks for the added input and encouragement folks.
Just reporting an update:
Having been unsuccessful more times than I could count, I decided to physically disassemble the phone (normally Engineering fix #2, but performed out of order on this occasion). I have zero idea why it should have made a difference, as all I did was take it apart and then put it back together, but the phone has groaned back to life.
Of course, then sausage-fingers here managed to tear the digitizer cable when doing the final reassambly... /facepalm
Anyhow, I have a replacement on order, so I'm hopeful that when I receive that in a few days I'm back to a fully functional Optimus 2x!!
Warning: LONG POST incoming ***
So I think I'm having the worst brick I've ever encountered on this phone, had tons of softbricks before and I could almost always sort them out easily, this one I'm having right now unforetunately is not the same case.
Current situation, phone won't boot up, no logo, no nothing, pressing power on button gives two RED blinks, holding power on gives continuous red led blink, now, vol. Up + power wont work anymore, same as hard reset of vol up+pwr with 3vibrates, it does work a few days ago but not anymore (I'm thinking about the issue of hard reset that results in about 50+ hrs or battery draining and recovery but not so sure if thats the case right now).
I've tried going flashmode but it just wont remain in flashmode, I can enter on flashmode briefly, proceed to flash stock ftf then somewhre along the process, (system.sin i think) phone exits flashmode then red led will show up. Fastboot wont work either.
Last observation i have is during wall charging, initially, when I connect to charger, no led light will show for about 3sec, then GREEN led will show and blink around 5times in about 1min, led disappears for a few sec then straight RED led will show for about 2min, and the cycle goes on and on, been monitoring like this for about 3hrs now, will continue until tomorrow.
Note: worst case, I think battery is flat dead thats why it wont charge, or something got fried during usage, never flashed antything for a few months, last thing I remember is I'm having a series of reboots, during long hours of mobile hotspot. Also worth mentioning, this phone auto reboots when it overheats during charging.
This may be a long shot but if anyone miraculously knows a workaround here other than getting a new one, then that'd be a huge help.
That's all, Thanks!
hi
I'm having a similar problem on my Xperia TL (LT30at). It was running on android 4.1.2 and I tried to flash it with a 4.3 ROM (originally built for LT30p, customized for US). During the process, there was an error while the flashtool was processing system.sin. In my case, there's no LED indication, no vibration, no nothing. The phone just won't respond to any button press combo (the battery was about 80% charged).
Plz help.
RESTORED!
Update: After long hours of battling this bricked mode, I've finally restored my phone! Stock FTF won't go through flashmode no matter what I do but luckily "Fastboot Trick" did the work along with numerous Trial and Errors, basically I was able to access fastboot by following and READING all of the instructions on xperia recovery pages here on XDA, from charging cycles, battery disconnect via opening the phone, flashmode/fastboot access, rubber band trick and so on.
Tried flashing kernel.sin from stock FTF (got into boot logo/bootloops with this), system.sin (can't fastboot flash due to huge file size), and lastly using my current roms (CM12.1 by neo) boot.img and flashing it via flashtool fastboot.this one did the trick allowing me to use my previous kernel along with my still un-wiped ROM data resulting to booting into it's previous working state.
Credits to @gregbradley , @Toledo_JAB and all that contributed to their tools and recovery thread (link below)
ALL IN ONE THREAD[Updated 12/3/13]Read me first!
[GUIDE] Recover 2012 and newer XPERIAs from SOFT-brick
The Key is as long as you're getting a response(if you don't get any, wall charge your phone for 4 ~ 24 hours and see if you can get a red led which then means you can still save your phone), vibrate, led blink, then you can bet you can still recover your phone. You just have to try everything you haven't tried before. That's all!
I had my T also similarly "bricked" last summer. Flashing always resulted in errors. Rubber band while powering helped, but only worked with original Sony charger. No luck with a Samsung one. After several reboots flashing went ok. The phone was stable only with battery almost full. After I replaced the battery, everything works well again. I guess the battery has been damaged by different chargers - a Samsung 2A (for tablet), in-car, and external battery pack. Currently evaluating CM 12.1
LiudasP said:
I had my T also similarly "bricked" last summer. Flashing always resulted in errors. Rubber band while powering helped, but only worked with original Sony charger. No luck with a Samsung one. After several reboots flashing went ok. The phone was stable only with battery almost full. After I replaced the battery, everything works well again. I guess the battery has been damaged by different chargers - a Samsung 2A (for tablet), in-car, and external battery pack. Currently evaluating CM 12.1
Click to expand...
Click to collapse
Good thing replacing battery works for you, though I have recovered my phone, I think mines hotspot module got damaged already due to extensive usage and overheating from before (currently experiencing random reboots right now when data is on), gonna check to see if this is kernel or hardware related.
PS: WhiteNeo's NeoWave(KK) and CM12.1 ROM's(development stopped / best version though is 20151010 afaik) are the fastest I have tested yet. You should check them both .
Xperia TL (LT30at) Hard Bricked!!
Well, it’s pretty much obvious that I have hard bricked my phone.
I’ve been searching over the internet (especially on XDA) about this issue and I’ve realized that I’ve caused my phone’s bootloader to be damaged and that’s why it won’t boot at all. Before unlocking the bootloader, I did not make a TA backup (as I’ve seen in some posts that it is required to restore security units in case of boot failure) and now I don’t know how to fix my phone. Most likely, I need a suitable firmware for my phone to flash it with and hence to restore bootloader, but I haven’t found a firmware for my phone anywhere over the internet.
By the way, my phone is recognized as ZEUS flash device when I connect it to my pc, so I feel like there is a chance to recover it from this brick. I took it to a repair center, they tried JTAG but the guy said it didn’t work. The phone takes the dump but still doesn’t boot.
Could anyone help please?
kain_the_sly said:
Well, it’s pretty much obvious that I have hard bricked my phone.
I’ve been searching over the internet (especially on XDA) about this issue and I’ve realized that I’ve caused my phone’s bootloader to be damaged and that’s why it won’t boot at all. Before unlocking the bootloader, I did not make a TA backup (as I’ve seen in some posts that it is required to restore security units in case of boot failure) and now I don’t know how to fix my phone. Most likely, I need a suitable firmware for my phone to flash it with and hence to restore bootloader, but I haven’t found a firmware for my phone anywhere over the internet.
By the way, my phone is recognized as ZEUS flash device when I connect it to my pc, so I feel like there is a chance to recover it from this brick. I took it to a repair center, they tried JTAG but the guy said it didn’t work. The phone takes the dump but still doesn’t boot.
Could anyone help please?
Click to expand...
Click to collapse
Not that sure when it comes to bootloader errors but I'll try to help, if it's detected on your PC, then you might still be able to recover it (mine is not even detected on my PC the last time it got bricked, but I got it fixed(detected) with proper driver installation: [Drivers] FlashTool Xperia Driver Pack (v1.5) [20140318] by @DooMLoRD), check troubleshooting section if you are using Windows 8 as you might encounter driver signature error during installation .
Question: Does it respond to any action? eg, vibrate, pressing power button just once(if it blinks red LED twice = phone is still alive), soft reset & hard reset, wall charging, fastboot or flashmode when connected to PC?
zakcaree said:
Not that sure when it comes to bootloader errors but I'll try to help, if it's detected on your PC, then you might still be able to recover it (mine is not even detected on my PC the last time it got bricked, but I got it fixed(detected) with proper driver installation: [Drivers] FlashTool Xperia Driver Pack (v1.5) [20140318] by @DooMLoRD), check troubleshooting section if you are using Windows 8 as you might encounter driver signature error during installation .
Question: Does it respond to any action? eg, vibrate, pressing power button just once(if it blinks red LED twice = phone is still alive), soft reset & hard reset, wall charging, fastboot or flashmode when connected to PC?
Click to expand...
Click to collapse
No. It doesn't vibrate, no LED blink, no fastboot or flashmode. The phone is non-responsive to every button press. However, red LED blinks just for once when I connect it to my pc and when the battery is unplugged.
So far, I've a pretty sure idea that the phone is in "dead boot" and somehow I've to restore its security units / TA backup, as the boot partition is corrupted. Unfortunately, I don't have a TA backup. However, I could make use of TA backup from another working LT30at.
P.S. I'm using Windows 7 and there are no driver issues. The phone is recognized by my pc as an ZEUS flash device.
zakcaree said:
Good thing replacing battery works for you, though I have recovered my phone, I think mines hotspot module got damaged already due to extensive usage and overheating from before (currently experiencing random reboots right now when data is on), gonna check to see if this is kernel or hardware related.
PS: WhiteNeo's NeoWave(KK) and CM12.1 ROM's(development stopped / best version though is 20151010 afaik) are the fastest I have tested yet. You should check them both .
Click to expand...
Click to collapse
Hi guys.
I have the same problem i tierd flashing the rom stock..it does't work..flash aborted and phone disconnected avain and again.
But when i remove the battery..phone in wallcharger it shows sony logo and keep restarting..no blinking led no vibration.
Any idea???
Mizouradio said:
Hi guys.
I have the same problem i tierd flashing the rom stock..it does't work..flash aborted and phone disconnected avain and again.
But when i remove the battery..phone in wallcharger it shows sony logo and keep restarting..no blinking led no vibration.
Any idea???
Click to expand...
Click to collapse
Try install stock without battery and then plug it in when u start
alial04 said:
Try install stock without battery and then plug it in when u start
Click to expand...
Click to collapse
Yes i did that...still have the same pb...end of flash session..phone keep disconnecting..and flash aborted!!!
Any advice?
Mizouradio said:
Hi guys.
I have the same problem i tierd flashing the rom stock..it does't work..flash aborted and phone disconnected avain and again.
But when i remove the battery..phone in wallcharger it shows sony logo and keep restarting..no blinking led no vibration.
Any idea???
Click to expand...
Click to collapse
Bootloop usually means boot kernel problem, Can you fastboot? try to fastboot flash your previous ROM kernel and check to see if you can boot normally to your previous rom.
im not using an xperia tl but pretty much thw same issue with my xperia e3 d2212
red light keeps blinking its charging(no logo just saying) tried evry key combination triying to connect to pc says connected for a few secs n then it gets disconnected although i say that its connected im sayin it only based on the sound derz actually no new software or unknown software msgs popping plzzz help me out............ ty in advance
Sunderesh said:
im not using an xperia tl but pretty much thw same issue with my xperia e3 d2212
red light keeps blinking its charging(no logo just saying) tried evry key combination triying to connect to pc says connected for a few secs n then it gets disconnected although i say that its connected im sayin it only based on the sound derz actually no new software or unknown software msgs popping plzzz help me out............ ty in advance
Click to expand...
Click to collapse
You mean red LED blinks during charging? Did you flash anything before this occured? Try first charging it for 2~4hrs, (also check if red LED still flashes during charging after a couple of hours), then try powering it ON... does it boot? If not, try soft reset with your phone (hold vol-up + power button for a few sec), it will vibrate ONCE, that means soft reset, power it ON... does it boot? If not, try hard reset this time (same method as soft-reset, this time hold the buttons longer, you will first get 1 vibrate, just hold it still, then you wil get 3 vibrates = hard reset).. power it ON... does it boot? If not.. try charging it a little longer and repeat the process, see if you can get it to boot that way.
zakcaree said:
You mean red LED blinks during charging? Did you flash anything before this occured? Try first charging it for 2~4hrs, (also check if red LED still flashes during charging after a couple of hours), then try powering it ON... does it boot? If not, try soft reset with your phone (hold vol-up + power button for a few sec), it will vibrate ONCE, that means soft reset, power it ON... does it boot? If not, try hard reset this time (same method as soft-reset, this time hold the buttons longer, you will first get 1 vibrate, just hold it still, then you wil get 3 vibrates = hard reset).. power it ON... does it boot? If not.. try charging it a little longer and repeat the process, see if you can get it to boot that way.
Click to expand...
Click to collapse
I will tell u my problem in detail I have a Sony Xperia e3 d2212 running stock 4.4.2 I rooted it without unlocking bootloader with" kingoroot" later saw a few privacy issues with kingo super user and used "supersume pro" to get super su as superuser and to get rid of kingosuper user
then tried an boot loader unlock with an app named "ez unlock" then tried flashing cwm
the mistake I did was that I flashed the cwm file which was made for my phone running 4.4.4
and now if it is low on battery the red led blinks only when I hold the power button
if I put it on charge for a few hours and then unplug the charger the red led keeps blinking all day long
let me know if u understood
sorry for the confusion though
---------- Post added at 03:05 PM ---------- Previous post was at 03:03 PM ----------
thank you for ur interest bro.......
zakcaree said:
Bootloop usually means boot kernel problem, Can you fastboot? try to fastboot flash your previous ROM kernel and check to see if you can boot normally to your previous rom.
Click to expand...
Click to collapse
thanks but i tried that...without result.cause the phone is not reconized and keep disconnecting
is that a driver problem??
Hi guys,
I got a G5S+, which got stuck the other day.
It was booting, showing the blue Motorola screen but ended up with a lying down android with a red questionmark and saying 'no command'.
I read through a couple of threads and finally decided, I need to flash stock again.
I did not have switched on USB debugging and so on, as the phone was quite new to me.
I decided to run with that tutorial here:
https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
Which seemed to be the right one.
Said so, booted into bootloader, installed the driver on my Win10 PC and ran through the steps.
I gut stuck on 'fastboot flash system system.img_sparsechunk.3' (15mins waiting..... after the steps before required about 12 Sec each) and needed to disconnect and connect the phone again.
Started with the same command and it worked.
Anyway when I got to the command 'fastboot flash system system.img_sparsechunk.5' I realized in the Potter Retail, there is no such file (neither there is 6 or 7).
I skipped the commands and continued.
When it came to rebooting the phone disconnected and thats it.
Since then I am not able to turn my phone back on.
Sometimes there seems to be a small notofication led showing up when trying to turn on the phone.
And you can hear the USB connect sound when I connect it to my computer.
Did anyone of you guys experience the same issue or has an idea what to do?
I have no idea what I shall so.
Best regards,
Matt
Which stock ROM did you flash? I'm hoping that following that guide, you flashed a stock ROM for sanders (i.e. the codename for Moto G5S Plus) and not for potter (codename for G5 Plus), which appear to be not compatible with each other.
Your original issue appears to be your device is booting into the stock recovery (which the start of is the 'no recovery' screen).
Do you know what model number or retail software channel, or the software build you had on your device before it failed? If so, we may be able to flash the correct sanders stock ROM to your device and get it going again. Another user appears to have gotten their device working when they incorrectly flashed the potter stock ROM and not sanders. https://forum.xda-developers.com/moto-g5s-plus/help/bricked-moto-g5s-plus-t3747064 Ideally you will want to flash the correct stock ROM for your device.
Oha damn you are right.
I am an idiot and tried to flash Potter to a G5S Plus.
Oh boy. I should not flash a cellphone after a long day at work.
I had the latest safety update installed and the latest release.
I am not sure though which software that used to be.
Unbelievable.....
Anyway, so my screen does not show anything anymore.
I guess the display driver dows not work or something like that.
The cellphone is still working I think, as the USB sound still appears.
Does anyone have an idea what to do if the screen stays black.
I still cannot believe it.....
Thanks though for your help!
EDIT: fastboot still reckognizes the phone. I guess this is good.
But the command 'fastboot oem fb_mode_set' runs into an error.
Edit2:
I skipped the first command and everything ran through (with some error messages though).
I hope it works now.
Device is currently rebooting and showing the blue motorola screen.
Lucky me.....
Okay, at least your device is booting now (ish)... I saw your other post and was wondering if you were able to boot from the bootloader.
1)Boot to fastboot (probably easiest by powering off your device, then hold down power and volume down keys until your device boots).
2)Once in the fastboot menu (with details about your device, like bootloader version), check that 'Start' is selected, and press the Power button to select. If 'Start' is not showing, use the volume keys to scroll through the options until 'Start' appears. Sometimes, this booting via fastboot bypasses an auto-boot to recovery mode.
Failing that, if you're on the 'no command' screen, then hold down the power button and tap the volume up key. Release both and it should let you into the recovery menu. Then, you can try to reboot to system.
Hi there,
I ran through all the steps you said.
But I ended up having the same issue. I always get back to the broken droid.
Is there a way to flash a completely new ROM to the device in its current condition?
I don't mind having a customrom, but I want to get it working again.
Thanks!
Matt
I solved my problem:
It was the SD card. I cannot believe it.
I got myself another G5S Plus and swapped everything:
Same issue.
So I removed the memory card and all good again.
I am quite sad though not having figured that out earlier, becoz all my data is lost now....
Thanks for your help though!
I have my rog 2 stuck in a bootloop. I don't really know why in the first place, because I don't like to change and mess around with custom roms. So i've never done that.
The case was that I was watching a video on YouTube and suddenly the touch screen stopped responding, the phone kept responding to other inputs such as the power button and the volume rocker. So I decided to restart the phone. And then it didn't turn on again. Got stuck in a boot loop.
I've been trying to fix it for a long time. But I just can't do it. Nor am I able to see what is happening with the phone. I have used this guide.
EVERYTHING works perfectly, it doesn't give me any errors during flashing or anything like that. Even the program tells me that the rom has been flashed correctly, and even the rog logo during boot, changes (I suppose because it is a version of the rom prior to the one I had.). The fact is that even with that the phone is still stuck in the bootloop. I have tried more things but this is the one that has taken me the furthest. I don't know what else to try. If anyone has any ideas, please tell me.
P.D. Sorry if my English is a bit rusty.
go back to stock and try other rom.
atoyu said:
go back to stock and try other rom.
Click to expand...
Click to collapse
Any suggestions which rom I can use? I have tried the rom of the guide and the ones that Asus has on their website. None of them have bailed me out.
@Arnau17 Any Updates? I am facing the same issue. Mine reaches till boot logo and then freezes and reboots again. Tried flashing stock ROM as well but no Luck
I am in the same situation, tried several raw rom files, still in bootloop
USB plug correctly on side USB port? can you enter recovery or fastboot mode?
i have same problems before, if fixed after flash RAW rom, hope this help.
is there a guide to fix AVB VERIFY FAIL on Rog Phone 2
Hey!
I was using my phone as normal, and installed an update for PixelPlusUI, it was working fine and all, until earlier today, i tried going into recovery to fix an app issue. After that, the phone just bootlooped. I figured that going into Fastboot would fix that, but the problem is, i can't reach any of those modes. It just goes to the Redmi logo, reboots, and repeats that infinitely.
I heard about EDL mode, but that seems atleast so far, unreacheable.
Is there any way for me to reach it? Maybe by letting the battery dry out and then plug the powered off phone with Volume -, or am i out of luck here? Im pretty sure this is caused by the stupid VBMeta checks XIAOMI phones has.
Matsilagi said:
Hey!
I was using my phone as normal, and installed an update for PixelPlusUI, it was working fine and all, until earlier today, i tried going into recovery to fix an app issue. After that, the phone just bootlooped. I figured that going into Fastboot would fix that, but the problem is, i can't reach any of those modes. It just goes to the Redmi logo, reboots, and repeats that infinitely.
I heard about EDL mode, but that seems atleast so far, unreacheable.
Is there any way for me to reach it? Maybe by letting the battery dry out and then plug the powered off phone with Volume -, or am i out of luck here? Im pretty sure this is caused by the stupid VBMeta checks XIAOMI phones has.
Click to expand...
Click to collapse
Vbmeta means Android Verified Boot.
Vbmeta is default for all android devices and it was made by Google.
It is not specific made by Xiaomi.
Android Verified Boot 2.0
https://source.android.com/security/verifiedboot/avb
What changes did you do when you fixed the app issue?
Couldn't do any, just tried to boot into recovery, then got into that bootlooop cycle, couldn't reach anything.
Managed to get into EDL and SP Flash Tool mode, however, im a bit confused on what i need to flash to get it back to life with stock MIUI or atleast boot to main system to use ADB.
My IMEI is fixed on the phone stickers so i can reasily recover that aswell, any help is appreciated.
EDIT: Now i just need help flashing as it seems, what do i need to do to properly re-flash / re-boot the phone without losing IMEI and that sorta stuff? I plan on switching back to Pixel Plus UI again so, it isn't an issue.
EDIT2: Completely fixed, followed VD's guide on EDL/Mediatek Bypass method and flashed a normal GLOBAL rom, all was fixed, no IMEI lost.