Hoping to get this fixed, after flashing a twrp tar file my phone cannot boot to rom or even recovery, but bootloops, is there a potential fix? Do I need to bootlock and unlock my phone?
What do you mean by "bootlock"?
Did you unlock your bootloader before flashing?
V0latyle said:
What do you mean by "bootlock"?
Did you unlock your bootloader before flashing?
Click to expand...
Click to collapse
Yes I did unlock my bootloader before flashing, what I mean by bootlock is locking the bootloader through download mode.
wavetsuname said:
Yes I did unlock my bootloader before flashing, what I mean by bootlock is locking the bootloader through download mode.
Click to expand...
Click to collapse
Never lock your bootloader unless you have flashed back to factory stock. Locking the bootloader on modified firmware will brick your device.
When you are in download mode, look at the upper left corner of the screen. There should be a line that reads OEM LOCK. Is this ON or OFF?
Which TWRP build are you using?
Factory stock is the only firmware I'm able to flash successfully, in download mode it says "OEM LOCK: OFF(U)", I attempted to flash TWRP 3.5.2, here's the file if needed, I have also attempted to flash other TWRP versions, but none worked.
I managed to get orange fox working, and it turned out I flashed the wrong stock ROM for my phone.
To flash TWRP with odin - one of previous version of stock ROM required. On the latest versions of stock ROM it is impossible to flash TWRP - the device goes into the bootloop.
Related
Tried to unlock my bootloader with official method and i perform all my steps correctly after that i got stuck in booloop that time i tried to boot in recovery but fail my device dont boot in recovery mod after that i flash stock 4.3 firmware on my xpetria using flashtool n i started my device (everything wiped)
then again i tried to boot in recovery but fail i again tried to unlock it but again stuck in bootloader and again flash stock rom
please help me developers where am i mistaken my device bootloader unlock status is yes
and i have lost my drm key too
Are you trying to access Fastboot mode or the actual recovery? Because the stock ROM doesn't contain accessible recovery, which is why you have to flash a custom recovery separately.
I ****ed up.
I was coming from miui weekly eu version, I wanted to flash a GSI image. I did in twrp, GSI pixel experience arm a only. Didn't boot further till mi logo. So fastboot flashed miui10 stable and booted till setup screen. Boot asked for a password after GSI boot. So I wanted to try a different GSI and reflashed. Didn't work also. Again fastboot flashed miui10, this time I forgot to unselect 'format and lock' didnt saw that. Now it won't boot in system and twrp, and also can't unlock bootloader anymore with mi unlocked as my phone is somehow not linked to my account anymore.
What am I supposed to do now?
Roykooiman said:
I ****ed up.
I was coming from miui weekly eu version, I wanted to flash a GSI image. I did in twrp, GSI pixel experience arm a only. Didn't boot further till mi logo. So fastboot flashed miui10 stable and booted till setup screen. Boot asked for a password after GSI boot. So I wanted to try a different GSI and reflashed. Didn't work also. Again fastboot flashed miui10, this time I forgot to unselect 'format and lock' didnt saw that. Now it won't boot in system and twrp, and also can't unlock bootloader anymore with mi unlocked as my phone is somehow not linked to my account anymore.
What am I supposed to do now?
Click to expand...
Click to collapse
Did you tried to flash recovery? Cuz if you unlocked it with official way I think it can be used also why u install again with miflash via fastboot? With recovery its safe...
Oops
xmixmaster said:
Did you tried to flash recovery? Cuz if you unlocked it with official way I think it can be used also why u install again with miflash via fastboot? With recovery its safe...
Click to expand...
Click to collapse
Yes I tried flashing custom recovery. Says it can't flash it as my bootloader is not unlocked. Did the fastboot flash again because I wanted to do a deep clean flash again. But forgot to unselect the lock button. Now its locked and only booting in standard miui recovery and fastboot.
Roykooiman said:
I ****ed up.
I was coming from miui weekly eu version, I wanted to flash a GSI image. I did in twrp, GSI pixel experience arm a only. Didn't boot further till mi logo. So fastboot flashed miui10 stable and booted till setup screen. Boot asked for a password after GSI boot. So I wanted to try a different GSI and reflashed. Didn't work also. Again fastboot flashed miui10, this time I forgot to unselect 'format and lock' didnt saw that. Now it won't boot in system and twrp, and also can't unlock bootloader anymore with mi unlocked as my phone is somehow not linked to my account anymore.
What am I supposed to do now?
Click to expand...
Click to collapse
Roykooiman said:
Yes I tried flashing custom recovery. Says it can't flash it as my bootloader is not unlocked. Did the fastboot flash again because I wanted to do a deep clean flash again. But forgot to unselect the lock button. Now its locked and only booting in standard miui recovery and fastboot.
Click to expand...
Click to collapse
Try Misuite I had fixed one time the mi max 3 that I sold but don't remember how exactly cuz I used like everything but worked with 1 program from mi tomorrow I will be back home I will try to find it
Roykooiman said:
Yes I tried flashing custom recovery. Says it can't flash it as my bootloader is not unlocked. Did the fastboot flash again because I wanted to do a deep clean flash again. But forgot to unselect the lock button. Now its locked and only booting in standard miui recovery and fastboot.
Click to expand...
Click to collapse
Why did you keep using fastboot to flash stock most of these need xiaomi.eu ROM as a base which can be flashed via twrp whatever version you use and it's because you chose flash all and lock hence your stuck now as can't unlock bootloader. I just recovered mine from ARB EDL brick as invought it cheap in that state. You need to flash a stock version version that's suitable to get stock working then attach your account in settings so bootloader unlock can work. My model was Chinese so I needed flash Chinese stock and started again. If your phone was originally Chinese start there then unlock the bootloader etc.
---------- Post added at 08:53 AM ---------- Previous post was at 08:51 AM ----------
shingers5 said:
Why did you keep using fastboot to flash stock most of these need xiaomi.eu ROM as a base which can be flashed via twrp whatever version you use and it's because you chose flash all and lock hence your stuck now as can't unlock bootloader. I just recovered mine from ARB EDL brick as invought it cheap in that state. You need to flash a stock version version that's suitable to get stock working then attach your account in settings so bootloader unlock can work. My model was Chinese so I needed flash Chinese stock and started again. If your phone was originally Chinese start there then unlock the bootloader etc.
Click to expand...
Click to collapse
In a nutshell flash and lock with stock version for phone as if Chinese flash and lock won't work with a global stock ROM. Flash a Chinese stock to get back into system and start over again
shingers5 said:
Why did you keep using fastboot to flash stock most of these need xiaomi.eu ROM as a base which can be flashed via twrp whatever version you use and it's because you chose flash all and lock hence your stuck now as can't unlock bootloader. I just recovered mine from ARB EDL brick as invought it cheap in that state. You need to flash a stock version version that's suitable to get stock working then attach your account in settings so bootloader unlock can work. My model was Chinese so I needed flash Chinese stock and started again. If your phone was originally Chinese start there then unlock the bootloader etc.
---------- Post added at 08:53 AM ---------- Previous post was at 08:51 AM ----------
In a nutshell flash and lock with stock version for phone as if Chinese flash and lock won't work with a global stock ROM. Flash a Chinese stock to get back into system and start over again
Click to expand...
Click to collapse
Yes it is Chinese version. Will try flashing the Chinese rom. Just with fastboot I guess?
Roykooiman said:
Yes it is Chinese version. Will try flashing the Chinese rom. Just with fastboot I guess?
Click to expand...
Click to collapse
Yes flash the latest official Chinese not global stock using mi flash tool as that will get your phone back up and running on stock. Then add your account in settings so bootloader unlock can see it. Enable dev setting tick OEM unlock and add account. Unlock your boot loader and your back again mate. If you could have unlocked your boot loader the global would boot but not while it's locked.
1. Flash latest CN firmware
2. Add account in settings after set up
3. Try bootloader unlock again should not have to wait if unlocked before
4. Flash twrp and keep copy of xiaomi.eu ROM on your micro SD card as that's all you need to flash in recovery to return to stock. It's flashed via recovery without errors
shingers5 said:
Yes flash the latest official Chinese not global stock using mi flash tool as that will get your phone back up and running on stock. Then add your account in settings so bootloader unlock can see it. Enable dev setting tick OEM unlock and add account. Unlock your boot loader and your back again mate. If you could have unlocked your boot loader the global would boot but not while it's locked.
1. Flash latest CN firmware
2. Add account in settings after set up
3. Try bootloader unlock again should not have to wait if unlocked before
4. Flash twrp and keep copy of xiaomi.eu ROM on your micro SD card as that's all you need to flash in recovery to return to stock. It's flashed via recovery without errors
Click to expand...
Click to collapse
Just tried flashing "nitrogen_images_V10.0.6.0.OEDCNFH_20181019.0000.00_8.1_cn" with fastboot and it instantly gives me an error: "Erase boot error".
What must I do now?
Roykooiman said:
Just tried flashing "nitrogen_images_V10.0.6.0.OEDCNFH_20181019.0000.00_8.1_cn" with fastboot and it instantly gives me an error: "Erase boot error".
What must I do now?
Click to expand...
Click to collapse
use Mi Flash tool mate should be fine
flash a more recent chinese rom on android 9 mate as thats 8.1
shingers5 said:
use Mi Flash tool mate should be fine
Click to expand...
Click to collapse
I did with Mi flash tool. Will try a newer versoin of miflash tool just in case.
shingers5 said:
use Mi Flash tool mate should be fine
flash a more recent chinese rom on android 9 mate as thats 8.1
Click to expand...
Click to collapse
Tried both versions. Same error. :crying:
Roykooiman said:
Tried both versions. Same error. :crying:
Click to expand...
Click to collapse
Try newer version of Chinese ROm as will flash. No reason why it wouldn't as that the stock version for phone
shingers5 said:
Try newer version of Chinese ROm as will flash. No reason why it wouldn't as that the stock version for phone
Click to expand...
Click to collapse
I tried the newest version of chinese rom: "nitrogen_images_V10.2.1.0.PEDCNXM_20190214.0000.00_9.0_cn". Same error. It simply can't flash it as my bootloader is locked......
Anyone who can fix this hard brick gets $10 worth of Bitcoin or Ethereum from me.
Hmmm, if you bootloader can be unlocked. I can help you because I hard-bricked my phone because of the Anti Rollback by flashing an earlier version of global pie beta over the current one (10.2.1.0). I had someone from the s-unlock website unbrick my device for me because my Mi account had no authorization to finish the Mi Flash process. So instead, the tech guy used his authorized mi account to bypass the Mi Flash install remotely on my computer to make my phone work again.
Wmateria said:
Hmmm, if you bootloader can be unlocked. I can help you because I hard-bricked my phone because of the Anti Rollback by flashing an earlier version of global pie beta over the current one (10.2.1.0). I had someone from the s-unlock website unbrick my device for me because my Mi account had no authorization to finish the Mi Flash process. So instead, the tech guy used his authorized mi account to bypass the Mi Flash install remotely on my computer to make my phone work again.
Click to expand...
Click to collapse
My account is verified but I am not signed into it on my phone as I can not boot into system.
Basically you need to flash the latest version of the Chinese stock miui but I haven't seen any tool that does that while bootloader is locked. You won't be able to unless you have bootloader unlocked. It bootloader gets unlocked phone will boot normal but your account should still been linked as phone was signed into it previously. Strange that it won't recognise your account when using the bootloader unlock tool
shingers5 said:
Basically you need to flash the latest version of the Chinese stock miui but I haven't seen any tool that does that while bootloader is locked. You won't be able to unless you have bootloader unlocked. It bootloader gets unlocked phone will boot normal but your account should still been linked as phone was signed into it previously. Strange that it won't recognise your account when using the bootloader unlock tool
Click to expand...
Click to collapse
That is the problem. I was booted into system but skipped the option for logging into my mi account as it was only to get past the unlock screen. Then did the clean flash again but then with the flash all and lock then I couldn't boot into system anymore. I'm seriously in trouble now, I loved this phone. Thankfully I still have a Mi A1 which I use now but it kinda sucks tho.
I guess its the end for this device.
I cant boot into system. I cant flash TWRP as my bootloader is locked (Token verify failed).
Getting error while flashing with fastboot: https://imgur.com/a/VAa7R9o
Mi Max 3 was a good one, RIP
I restored the newest stock Android One ROM using MiFlash, but the phone only boots if the bootloader is unlocked. I need the bootloader to be locked for various apps. Can someone help me
I haven't found any threads that talk about this issue so I have no idea of what to do
Regarding your signature, I believe you have Magisk installed ? If you have Magisk or TWRP installed or if you've changed anything in the system, you can not lock the bootloader, as it will prevent the device from booting. All the partitions of the device should be stock and you should not have root, in order to lock the bootloader. My advice is to flash the stock rom via MiFlash again, but choose 'Clean All and Lock' option while flashing.
Install stock 10.0.13 version with edl mode:
fastboot oem edl , and flash with miflash,then reboot the system in fastboot mode to lock bootloader with : fastboot lock oem , then boot the system and update your device with ota.
Hey i was attempted to install TWRP and got stuck in download mode boot loop. Fixed it by flashing stock firmware. I noticed a small error with my camera so i tried to lock bootloader again to see if that would fix the issue. But after flashing stock firmware a second time after locking the bootloader it didnt work and im stuck in download mode boot loop again. Only this time i dont get the option to unlock the bootloader and i cant enter the OS in order to enable OEM Unlock.
Here is the error screen: https://prnt.sc/q8vmG--mTHxY
Anyone know how to get out of this mess? Thanks
Am i doomed?
cheen11 said:
Hey i was attempted to install TWRP and got stuck in download mode boot loop. Fixed it by flashing stock firmware. I noticed a small error with my camera so i tried to lock bootloader again to see if that would fix the issue. But after flashing stock firmware a second time after locking the bootloader it didnt work and im stuck in download mode boot loop again. Only this time i dont get the option to unlock the bootloader and i cant enter the OS in order to enable OEM Unlock.
Here is the error screen: https://prnt.sc/q8vmG--mTHxY
Anyone know how to get out of this mess? Thanks
Click to expand...
Click to collapse
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
BlackMesa123 said:
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
Click to expand...
Click to collapse
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
cheen11 said:
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
Click to expand...
Click to collapse
Shouldn’t be a big deal unless there’s something Carrier specific required by your phone. Just make sure you don’t lock your bootloader again while using custom binaries or you might soft brick your device again. To bypass the camera lock you can use a SafetyNet fix module for Magisk which will spoof the bootloader status to the camera HAL
cheen11 said:
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
Click to expand...
Click to collapse
You can try also the NEE for Nordic Countries...
BlackMesa123 said:
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
Click to expand...
Click to collapse
Am i supposed to flash only AP or all of them? I have only ever flashed AP and worked without problems but after locking the bootloader i only get the above error boot loop.
cheen11 said:
Am i supposed to flash only AP or all of them? I have only ever flashed AP and worked without problems but after locking the bootloader i only get the above error boot loop.
Click to expand...
Click to collapse
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
BlackMesa123 said:
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
Click to expand...
Click to collapse
Ah, once choosing all the files it worked, thanks a bunch
BlackMesa123 said:
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
Click to expand...
Click to collapse
I dont know if im using the right files but i still get the same boot loop (https://prnt.sc/1lCk2FQEymPn) after adding twrp-3.7.0_12-2-a52sxq.img.tar to AP and vbmeta_disable.tar to USERDATA.
cheen11 said:
I dont know if im using the right files but i still get the same boot loop (https://prnt.sc/1lCk2FQEymPn) after adding twrp-3.7.0_12-2-a52sxq.img.tar to AP and vbmeta_disable.tar to USERDATA.
Click to expand...
Click to collapse
Are you flashing the patched vbmeta in the TWRP XDA thread or another one? Also the latest TWRP version is 3.7.0-3 so flash that one.
BlackMesa123 said:
Are you flashing the patched vbmeta in the TWRP XDA thread or another one? Also the latest TWRP version is 3.7.0-3 so flash that one.
Click to expand...
Click to collapse
Im using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-note10-lite-exynos.4350891/
I tried flashing that along with this: twrp-3.7.0_12-3-a52sxq.img.tar
But i still get the boot loop. Not sure if i can keep trying to re-flash these if the boot loop already happened
cheen11 said:
Im using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-note10-lite-exynos.4350891/
I tried flashing that along with this: twrp-3.7.0_12-3-a52sxq.img.tar
But i still get the boot loop. Not sure if i can keep trying to re-flash these if the boot loop already happened
Click to expand...
Click to collapse
You must use the patched vbmeta linked in the a52s TWRP thread, flash that one and you should boot fine in TWRP.
BlackMesa123 said:
You must use the patched vbmeta linked in the a52s TWRP thread, flash that one and you should boot fine in TWRP.
Click to expand...
Click to collapse
Hmm i tried using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-3-for-galaxy-a52s-5g.4488419/
But this time i got a fail with odin: https://prnt.sc/9HfVrQtC-gSO
cheen11 said:
Hmm i tried using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-3-for-galaxy-a52s-5g.4488419/
But this time i got a fail with odin: https://prnt.sc/9HfVrQtC-gSO
Click to expand...
Click to collapse
I think it has something to do with the space in “New folder” name, try to copy the TWRP tar in a path that has no spaces
BlackMesa123 said:
I think it has something to do with the space in “New folder” name, try to copy the TWRP tar in a path that has no spaces
Click to expand...
Click to collapse
Oh yeah good catch, i renamed the folder and didnt consider that it might not be updated it odin. It finally worked, thanks again for the help very much appreciated
Hmm i guess problems keep popping up. I guess its best that i just post here instead of creating a new thread. Im successfully in the TWRP UI but now i cant boot to system, it will just restart 2 times and then boot to TWRP. Also it fails to backup the boot image (with the error "Unable to mount storage") which i read in a tutorial that you were supposed to do.
cheen11 said:
Hmm i guess problems keep popping up. I guess its best that i just post here instead of creating a new thread. Im successfully in the TWRP UI but now i cant boot to system, it will just restart 2 times and then boot to TWRP. Also it fails to backup the boot image (with the error "Unable to mount storage") which i read in a tutorial that you were supposed to do.
Click to expand...
Click to collapse
As mentioned in the TWRP thread guide, you must format your data partition in TWRP in order to be able to boot back in the OS.
So I wanted to relock my bootloader so that I could use Netflix, Hulu, etc... When I fastboot flashing lock it only boots to bootloader. I can't flash anything with bootloader locked. When I unlocked again and flashed the stock boot and init_boot and stock recovery image I just get a bootloop into bootloader. I think the recovery image I flashed is not good. I can't even power the phone off through the bootloader power off option, it just reboots back to bootloader.
Can I get back to original stock rom and recovery?
Update. So now I'm completely bricked. I managed to switch the active slot to a, relocked the bootloader and now I just get a boot screen with red text that says the boot/recovery images have been destroyed and can not boot.
This happened because you failed to restore to full stock before locking locking bootloader. Well you could unlock bootloader again and fix it.
MrSteelX said:
This happened because you failed to restore to full stock before locking locking bootloader. Well you could unlock bootloader again and fix it.
Click to expand...
Click to collapse
Thanks for the reply. I can't unlock again because it's stuck in a bootloop and won't boot into bootloader.
I will point out that recover and kernel both live in boot.img since there is no custom recovery for our phone.
MrSteelX said:
I will point out that recover and kernel both live in boot.img since there is no custom recovery for our phone.
Click to expand...
Click to collapse
recovery is it's own file, not part of boot.img. at least that's what the rollback and developer preview is showing.