I seem to have hard bricked my 9T after flashing the MIUI 11 rom from xiaomi.eu. I think culprit is a totally botched/corrupted boot loader and I have no idea how it happened. I've tried reflashing back to stock through stock image .bat files, but no dice. It flashed everything but the device still refuses to boot past the MI screen. If I try to boot into TWRP, my device gets stuck at the TWRP splash screen, no matter which version it is. Does anyone know what I can do or try at this point? Thanks.
So do I, first time I successfully instal first beta v25 miui 11, and than when the v26 comes, stupidly, i flash it from twrp, it tells me that i succeed installing that zip, and than i wipe art and cache and reboot system, but what next i know, my phone brick, i can not instal anyrom, from mi flash tool, or from anywhere. I did everything and still can not fix the problem.
Anyway, you still can enterin TWRP UI, after waiting about 10 to 30 minutes, because after intalling that rom, automatically your data format change from ext4 to f2fs, and twrp will need a lot of time to read your disk.
But, even after doing anything in twrp, still can not make my phone successfully boot into system.
And theres moun I/O error everytime i tried to wipe everything, or fix disk, or change disk format. Everything... and i just dont know what to do anymore.
So may be you can wait patiently until you can entering twrp ui, and please lemme know if you know how to fix this problem
Soapy! said:
I seem to have hard bricked my 9T after flashing the MIUI 11 rom from xiaomi.eu. I think culprit is a totally botched/corrupted boot loader and I have no idea how it happened. I've tried reflashing back to stock through stock image .bat files, but no dice. It flashed everything but the device still refuses to boot past the MI screen. If I try to boot into TWRP, my device gets stuck at the TWRP splash screen, no matter which version it is. Does anyone know what I can do or try at this point? Thanks.
Click to expand...
Click to collapse
i have experience that, then i flash the twrp chinese version and it works.
@flamedrops which one if i may know? I tried 3.3.1-0916-redmi_k20-CN and still not work ?
Soapy! said:
I seem to have hard bricked my 9T after flashing the MIUI 11 rom from xiaomi.eu. I think culprit is a totally botched/corrupted boot loader and I have no idea how it happened. I've tried reflashing back to stock through stock image .bat files, but no dice. It flashed everything but the device still refuses to boot past the MI screen. If I try to boot into TWRP, my device gets stuck at the TWRP splash screen, no matter which version it is. Does anyone know what I can do or try at this point? Thanks.
Click to expand...
Click to collapse
I got exactly the same problem after installing miui 11rom. Installing firmware via fastboot was unsuccessful. God, help us ...
---------- Post added at 07:44 AM ---------- Previous post was at 07:33 AM ----------
Arif Ferdian said:
So do I, first time I successfully instal first beta v25 miui 11, and than when the v26 comes, stupidly, i flash it from twrp, it tells me that i succeed installing that zip, and than i wipe art and cache and reboot system, but what next i know, my phone brick, i can not instal anyrom, from mi flash tool, or from anywhere. I did everything and still can not fix the problem.
Anyway, you still can enterin TWRP UI, after waiting about 10 to 30 minutes, because after intalling that rom, automatically your data format change from ext4 to f2fs, and twrp will need a lot of time to read your disk.
But, even after doing anything in twrp, still can not make my phone successfully boot into system.
And theres moun I/O error everytime i tried to wipe everything, or fix disk, or change disk format. Everything... and i just dont know what to do anymore.
So may be you can wait patiently until you can entering twrp ui, and please lemme know if you know how to fix this problem
Click to expand...
Click to collapse
Just the exact same problem as mine. If you know anything about how to solve this problem, please tell us.
I had the same problem with a miui 10 weekly beta but unfortunately I wasn't able to fix it but lucky me my phone was still in a return period so I returned it back to Amazon and got my money back since then I have always stayed away from beta ROMs . I tried everything but it wasn't booting pass the mi logo as you said
flamedrops said:
i have experience that, then i flash the twrp chinese version and it works.
Click to expand...
Click to collapse
Benfatica said:
I had the same problem with a miui 10 weekly beta but unfortunately I wasn't able to fix it but lucky me my phone was still in a return period so I returned it back to Amazon and got my money back since then I have always stayed away from beta ROMs . I tried everything but it wasn't booting pass the mi logo as you said
Click to expand...
Click to collapse
Ahhhh yes, i was thinking to using my guaranteed card, as i still can relock bootliader with mi flash tools, already trying anything for couples day with zero result, and im giving up hahaha
Arif Ferdian said:
Ahhhh yes, i was thinking to using my guaranteed card, as i still can relock bootliader with mi flash tools, already trying anything for couples day with zero result, and im giving up hahaha
Click to expand...
Click to collapse
did you really reboot it using adb reboot twrp? and reboot system on twrp using twrp cn version?
Yap @flamedrops i already do, and even tried all the TWRP version that exist, and also reflash many Rom, from stock, eu, ct, aosp, miui 11 25, miui 11 26, i flash from adb sideload, from twrp via usb otg, via miflash tool,
I flash boot.img, etc
Still no result.
Already tried everything that i could thinking about
flamedrops said:
did you really reboot it using adb reboot twrp? and reboot system on twrp using twrp cn version?
Click to expand...
Click to collapse
This LR. TEAM is twrp cn version right? And in fact, this version hardly booting to twrp ui version after this problem, easier to entering twrp ui with the ugly themed greek version
Arif Ferdian said:
This LR. TEAM is twrp cn version right? And in fact, this version hardly booting to twrp ui version after this problem, easier to entering twrp ui with the ugly themed greek version
Click to expand...
Click to collapse
ok, yes thats it. have you tried to flash magisk?
@flamedrops not yet, i never tried to flash magisk yet, ill tried next time i could pass twrp splash screen
flamedrops said:
i have experience that, then i flash the twrp chinese version and it works.
Click to expand...
Click to collapse
Can you list your steps to fix this? My data and cache partitions are 0kb and i get i/o errors too.
I have persist problems after installing muiu 11 over the los16.
Thinking about relock it and sens it back to aliexpress seller.
@mvha just go into fastboot mode, and flash persist.img from stock fastboot rom,
With command : fastboot flash persist persist.img
Thats all
Arif Ferdian said:
So do I, first time I successfully instal first beta v25 miui 11, and than when the v26 comes, stupidly, i flash it from twrp, it tells me that i succeed installing that zip, and than i wipe art and cache and reboot system, but what next i know, my phone brick, i can not instal anyrom, from mi flash tool, or from anywhere. I did everything and still can not fix the problem.
Anyway, you still can enterin TWRP UI, after waiting about 10 to 30 minutes, because after intalling that rom, automatically your data format change from ext4 to f2fs, and twrp will need a lot of time to read your disk.
But, even after doing anything in twrp, still can not make my phone successfully boot into system.
And theres moun I/O error everytime i tried to wipe everything, or fix disk, or change disk format. Everything... and i just dont know what to do anymore.
So may be you can wait patiently until you can entering twrp ui, and please lemme know if you know how to fix this problem
Click to expand...
Click to collapse
This makes sense as I remember trying to boot into stock recovery early in the morning. I woke up and it finally booted, but the recovery was in Chinese. I will give 4PDA TWRP about an hour and see what I can do. Thanks.
Soapy! said:
This makes sense as I remember trying to boot into stock recovery early in the morning. I woke up and it finally booted, but the recovery was in Chinese. I will give 4PDA TWRP about an hour and see what I can do. Thanks.
Click to expand...
Click to collapse
If you can not use 4pda, i suggest u to use greek one, thats twrp version the must successfully booting in my experiences
I am thankful that I saw this before updating to newest miui 11
flamedrops said:
ok, yes thats it. have you tried to flash magisk?
Click to expand...
Click to collapse
Can not flash magisk, etc hahahhahaa
Arif Ferdian said:
If you can not use 4pda, i suggest u to use greek one, thats twrp version the must successfully booting in my experiences
Click to expand...
Click to collapse
After you used the Greek twrp did you manage to solve the problem?
Related
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
I had an older version of twrp so I just updated it to the latest one before attempting this ofc...
I tried flashing the latest RR and AICP and both give me boot loops and I always get this one problem where it says
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
I'm not sure if this has anything to do with the bootloop though...
Going to recovery after seeing the bootloop I always get the "keep system read only?" prompt where i swipe to allow modification but i usually just restore back to my backup from there... i dont think allowing it and trying to boot again will get rid of the bootloop...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
OppaiHeroStar said:
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
Click to expand...
Click to collapse
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
dzidexx said:
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
Click to expand...
Click to collapse
The first 3 steps I've already done that since the beginning
Where can i get the nougat modem/is it possible to update to it? I guess that's the reason every single 7.1 custom rom I tried in the android development section gave me boot loops...
And could you link the 21.11.2017 version of RR? I'm looking at the download links for RR and I dont see one with that exact date
edit-just saw your edit
Custom roms for MM modem works better.
I fully wiped using TWRP, checked everything I possibly could except my micro SD card and I flashed RR-N-v5.8.5-20171121-clark-Final.zip then gapps arm64, 7.1 nano and it's still giving me boot loops. I'm using TWRP 3.2.1-0
im gonna try using gapps arm64 7.1 mini really quick since you said I should use that one and see if it boot loops... - Edit guess I was too optimistic thinking this would fix it
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
dzidexx said:
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
Click to expand...
Click to collapse
changed to 3.1.1-0 and did everything you said, still have boot loop...
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
OppaiHeroStar said:
changed to 3.1.1-0 and did everything you said, still have boot loop...
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
dzidexx said:
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
Click to expand...
Click to collapse
I tried crDroidAndroid-7.1.2-20171119-clark-v3.8.3.zip and it still boot loops :\ I also already tried LineageOS and AICP before we started talking
I went back to my backup and it put me in a bootloop which never happened before but changing cache back to ext4 instead of f2fs fixed it..
OppaiHeroStar said:
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
A little late to chime in and this does not help with your current situation, but here's a little advice. I flash a lot of ROMs (how else am I going to test builds right?). This error happens all the time, BUT if you flash a ROM twice it should not show on the 2nd flash.
So flash order goes:
Wipe/Factory reset
Format data x3 (yes I format my data 3 times for every ROM)
Reboot
Wipe/Factory reset
ROM
ROM again
GAPPS
Wipe caches
Reboot
Do the Initial setup
Reboot before use
OPTIONAL Kernel (if its not already build in)
OPTIONAL Magisk (I never flash Magisk on a clean build but heck I'm expecting a NON boot most of the time anyways)
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
acejavelin said:
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
Click to expand...
Click to collapse
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
OppaiHeroStar said:
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
Click to expand...
Click to collapse
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
acejavelin said:
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
Click to expand...
Click to collapse
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
OppaiHeroStar said:
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
Click to expand...
Click to collapse
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
acejavelin said:
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
Click to expand...
Click to collapse
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
OppaiHeroStar said:
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
Click to expand...
Click to collapse
What custom did you flashed?
dzidexx said:
What custom did you flashed?
Click to expand...
Click to collapse
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
OppaiHeroStar said:
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
Click to expand...
Click to collapse
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
dzidexx said:
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
Click to expand...
Click to collapse
I'm using t-mobile and I've checked the access points, clicking on the one im using and hitting save doesn't fix it. Always getting a notification telling me to sign in to network. Not sure what else I can do. I'll give it a day since I had this kind of problem before when I switched sim cards and data didn't work until the next day
Edit - just went back to stock and my data doesn't work now either... just going to stay at RR now and hope my data fixes itself because my access point settings for tmobile should be correct since I looked it up on the official website..
hi you can grab download link from here
https://www.xda-developers.com/android-pie-beta-xiaomi-mi-max-3/
google play store keeps stopping =/
Hi,
I do assume that if I install this, I will get a device that is ARB protected.
Can you confirm that ?
Regards.
Moirae said:
google play store keeps stopping =/
Click to expand...
Click to collapse
i think its china rom and because of that play service stops:/
i cant even flash it...
I think we have to download google apps from the mi store and change permissions for it to work.
Can someone send Bigota link for 8.11.27 OTA? Thanks
NexusPenguin said:
Hi,
I do assume that if I install this, I will get a device that is ARB protected.
Can you confirm that ?
Regards.
Click to expand...
Click to collapse
ARB yes
Has anyone used https://opengapps.org/ to install all Googly things with this ROM yet.
There is no download link
Ignore me I found it? How long does it take to boot? Used red wolf and was on miui.eu latest?
flashed using red wolf was ok but stuck at boot logo. the dots are moving but rom is not booting up
Im using this new pie rom for hours and its super smooth and fluid
full screen gestgures are now super fast and with no stutters
flash this rom and other official miui zip roms using nijel8 twrp recovery otherwise it will not boot
pejji said:
Im using this new pie rom for hours and its super smooth and fluid
full screen gestgures are now super fast and with no stutters
flash this rom and other official miui zip roms using nijel8 twrp recovery otherwise it will not boot
Click to expand...
Click to collapse
going to try this now lets hope you are right as i have tried everything else and various combinations to get this booting...........
it didnt boot so starting to think this is fake rom. i tried clean flash on miui.eu rom then flashed stock gobal and clean flashed again. used this recovery and same results. it sits on boot screen with the dots flashing and nothing else happens...........how long did yours take to boot?
shingers5 said:
going to try this now lets hope you are right as i have tried everything else and various combinations to get this booting...........
Click to expand...
Click to collapse
try it and if didnt boot here are my steps if i remember correctly :
-flash latest global developer fastboot rom with mi flash (flash all , be careful with locking bootloader accidentally )
-wait until first boot before phone setup and don't go through it
-reboot to fastboot mode and flash nijel twrp
-reboot directly to recovery
-wipe->factory reset
-flash 8.11.26 pie
-reboot system
Exatly as for me. Flashed with nigel TWRP, with format data before. Few issues but CN firmware... Google must be installed.
ok will do that now and report
i flashed latest global then tried to flash with that recovery but nothing.
i am now going to flash china dev latest and try again
---------- Post added at 07:31 PM ---------- Previous post was at 07:24 PM ----------
so to be clear
i am gonna flash dev global 8.11.23 via fastboot
then wait for it to get to 1st set up screen but not go through the setup process
will then flash that twrp you mentioned via fastboot
and flash the rom after factory reset
shingers5 said:
ok will do that now and report
i flashed latest global then tried to flash with that recovery but nothing.
i am now going to flash china dev latest and try again
---------- Post added at 07:31 PM ---------- Previous post was at 07:24 PM ----------
so to be clear
i am gonna flash dev global 8.11.23 via fastboot
then wait for it to get to 1st set up screen but not go through the setup process
will then flash that twrp you mentioned via fastboot
and flash the rom after factory reset
Click to expand...
Click to collapse
i did exactly what you said again just to be sure
and it booted up with no problem
- mi flash->global 8.11.23 -> clean all
- first boot until welcome screen
- power off-> volume down+power -> fastboot and run "fastboot flash recovery nijeltwrp.img"
- volume up+power to boot to recovery
(so far if decryption goes well twrp shuold not request decryption password and you could mount data and see internal storage contents in /sdcard with no problem in twrp file manager)
- wipe->factory reset
- install pie zip rom 8.11.26
- wipe dalvik+cache
- reboot system
it took about 4 or 5 minutes for me to boot
If I've gone straight from the latest stock China ROM to xiaomi.eu 10.0.0.6.0 and have since flashed the latest nijel TWRP - which is all working fine.
Can I simply flash to this pie release or do I need to have previously flashed one of the developer ROMs?
Guys, quick conformation, please as I hear conflicting reports about MIUI Pie and my TWRP...
Please, from experience, decryption works, right? How about formatting data with TWRP and boot to Pie? Is MIUI Pie able to encrypt fresh data partition? And if yes is TWRP able to decrypt it again?
Thank you, feedback is really appreciated so I know what needs to be done for full Pie compatibility!!!
eresen said:
has anyone used https://opengapps.org/ to install all googly things with this rom yet.
Click to expand...
Click to collapse
nijel8 said:
Guys, quick conformation, please as I hear conflicting reports about MIUI Pie and my TWRP...
Please, from experience, decryption works, right? How about formatting data with TWRP and boot to Pie? Is MIUI Pie able to encrypt fresh data partition? And if yes is TWRP able to decrypt it again?
Thank you, feedback is really appreciated so I know what needs to be done for full Pie compatibility!!!
Click to expand...
Click to collapse
You can't decrypt it anymore!
nijel8 said:
Guys, quick conformation, please as I hear conflicting reports about MIUI Pie and my TWRP...
Please, from experience, decryption works, right? How about formatting data with TWRP and boot to Pie? Is MIUI Pie able to encrypt fresh data partition? And if yes is TWRP able to decrypt it again?
Thank you, feedback is really appreciated so I know what needs to be done for full Pie compatibility!!!
Click to expand...
Click to collapse
first thanks again for your great work on this recovery
decryption was good with oreo 8.11.15 china rom but right after pie rom boots and rebooting to recovery, decryption fails
from there rebooting to recovery again doesn't change anything ... recovery asks for decryption password every time.
and cuz data partition is not mounted so recovery log will not be saved to internal memory to attach it here
after formatting data miui boots successfully and encrypts data again.setting up the phone and rebooting to recovery ... but same thing happens and decryption fails.
So i was updating my Rom, Havoc OS, Same version, new patch
so i wiped the cache, Dalvik, and system and then installed it, then magisk stopped, and susbstratum stopped so all the apps patched I can't open, ok, i'll install magisk, but when i got to the substratum manager, it was empty, i tried using rescue my system failed, did nothing, and then i tried flashing the rescue me, nothing, and it just won't reboot now, and what's worse i can't access recovery, it's showing an empty battery even though i've been charging it and it will only go to fastboot, hell i tried wiping and factory resetting it trough fastboot it said failed
any help?
Rmdhn said:
So i was updating my Rom, Havoc OS, Same version, new patch
so i wiped the cache, Dalvik, and system and then installed it, then magisk stopped, and susbstratum stopped so all the apps patched I can't open, ok, i'll install magisk, but when i got to the substratum manager, it was empty, i tried using rescue my system failed, did nothing, and then i tried flashing the rescue me, nothing, and it just won't reboot now, and what's worse i can't access recovery, it's showing an empty battery even though i've been charging it and it will only go to fastboot, hell i tried wiping and factory resetting it trough fastboot it said failed
any help?
Click to expand...
Click to collapse
Install an official Rom with Flashtool
Enviado desde mi Redmi Note 7 mediante Tapatalk
Install a new recovery with fastboot flash tool.
Rangdrol said:
Install a new recovery with fastboot flash tool.
Click to expand...
Click to collapse
i tried installing a recovery via Fastboot but when i rebooted to recovery it went back to fastboot
Rmdhn said:
i tried installing a recovery via Fastboot but when i rebooted to recovery it went back to fastboot
Click to expand...
Click to collapse
Maybe bootloader locked?
Than trie mi flash tool. Flash the lastest official mi rom. Make sure that you flash the right rom for your device. I heard, there are problems, if you flash wrong one and downgrade. When flashing don't lock your bootloader again.
Wrong section!!!
Rangdrol said:
Maybe bootloader locked?
Than trie mi flash tool. Flash the lastest official mi rom. Make sure that you flash the right rom for your device. I heard, there are problems, if you flash wrong one and downgrade. When flashing don't lock your bootloader again.
Click to expand...
Click to collapse
My bootloader is unlocked, i reinstalled the custom recovery trough fastboot but it's still like this, i'll do this tommorow, i'm too tired of trying now
This should be on the Q/A thread. Not here.
Rmdhn said:
My bootloader is unlocked, i reinstalled the custom recovery trough fastboot but it's still like this, i'll do this tommorow, i'm too tired of trying now
Click to expand...
Click to collapse
Now you can flash the rom? If not, maybe this treat help you: https://forum.xda-developers.com/redmi-note-7/how-to/guide-steps-to-unbrick-redmi-note-7-t3922543
Also check the helpful post page 2.
Kagamihara said:
This should be on the Q/A thread. Not here.
Click to expand...
Click to collapse
Moved to Q&A section :good:
Hey!
I installed LineageOs on my Xiaomi Mi A1, everything went okay but when I installed the Gapps, it got stuck on the LineageOs logo. The volume button wasn't working right, yet somehow, I manage to enter TWRP and wipe that OS and restore the backup with the original Android One. But when I boot it, it got stuck on Android logo, unable to enter fastboot, TWRP or hard reset because of the volume button not working.
I don't know what else to do, to be honest...
p.d.: I'm new here, sorry if this is not the right section to ask.
Are you 100% sure that you have chosen right version of GApps? because i never had any issues with GApps causing boot loop. BTW what lineage os version 16 or 17 ?
I never had any luck restoring stock rom backup via TWRP either i have no idea why whenever i restore it will stuck on androidone logo.
royalasif said:
Are you 100% sure that you have chosen right version of GApps? because i never had any issues with GApps causing boot loop. BTW what lineage os version 16 or 17 ?
I never had any luck restoring stock rom backup via TWRP either i have no idea why whenever i restore it will stuck on androidone logo.
Click to expand...
Click to collapse
I chose Android 10 GApps since I installed LineageOS 17. I thought it was the right version.
So TWRP can't be used for stock rom? I didn't know, maybe that's what got me stuck on Android One logo.
Any idea on how to get out from that loop? ?
Dont worry bootloop is not a problem download pixel experience it include gapps boot ur phone to twrp copy rom into internal or sd card Wipe system , data , cache and install the rom ..
TWRP should backup and restore stock image but i think there is something with this phone which wont let twrp to apply system restore i have done it 10 times and i failed everytime.
Edit: do let me know how it goes:good:
royalasif said:
Dont worry bootloop is not a problem download pixel experience it include gapps boot ur phone to twrp copy rom into internal or sd card Wipe system , data , cache and install the rom ..
TWRP should backup and restore stock image but i think there is something with this phone which wont let twrp to apply system restore i have done it 10 times and i failed everytime.
Edit: do let me know how it goes:good:
Click to expand...
Click to collapse
Definitely I'll try Pixel Experience! Seems like a good choice. I still need to figure out how to enter Fastboot or TWRP without the volume button.
try adb cmd if it works if not then u have to boot your device to EDL mode by test point method and then flash stock rom
ranjodhricky said:
try adb cmd if it works if not then u have to boot your device to EDL mode by test point method and then flash stock rom
Click to expand...
Click to collapse
Adb cmd won't recognize the device, so I'll have to boot it to EDL mode. Is there any guide here? I don't know how to do it.
hi!
i was in the middle of installing a new custom rom on my mi 9t/k20 (i think global/eu which was running miui 11 previously) and i wiped the partitions as follow: dalvik, cache, data and system
i believe that the only thing concerning on that list would be the system partition being wiped.
currently my device is stuck in fastboot mode (i can still send commands to it and do stuff) but i dont ave a recovery ...
so i have an idea of a plan which is:
1. flash twrp
2. wipe the 4 partitions again
3. reinstall the stock rom
4. update the phone to miui 12
5. wipe the partitions again
6. install custom rom twrp and magisk
is there anything i should know before i do this?
also some links to working twrp version would be nice (lost the original version that i had installed)
The_Wrench said:
hi!
i was in the middle of installing a new custom rom on my mi 9t/k20 (i think global/eu which was running miui 11 previously) and i wiped the partitions as follow: dalvik, cache, data and system
i believe that the only thing concerning on that list would be the system partition being wiped.
currently my device is stuck in fastboot mode (i can still send commands to it and do stuff) but i dont ave a recovery ...
so i have an idea of a plan which is:
1. flash twrp
2. wipe the 4 partitions again
3. reinstall the stock rom
4. update the phone to miui 12
5. wipe the partitions again
6. install custom rom twrp and magisk
is there anything i should know before i do this?
also some links to working twrp version would be nice (lost the original version that i had installed)
Click to expand...
Click to collapse
-When installing custom ROMs (changing ROM types), you have to F O R M A T Data (not Wipe) - it's totally different (stronger) and can be found elswhere in guides
-Wiping System is totally bogus: new ROM will nevertheless replace the System (no matter did you wipe it or not)
However, if you are changing from MIUI CN to Global or so - then totally different procedure applies.
It's not enough to flash the new System but also to change the Vendor.
For that case google for and read about using MIUI Flash
zgfg said:
-When installing custom ROMs (changing ROM types), you have to F O R M A T Data (not Wipe) - it's totally different (stronger) and can be found elswhere in guides
-Wiping System is totally bogus: new ROM will nevertheless replace the System
Click to expand...
Click to collapse
ok cool thx but do you think that i can install twrp rn without a system?
or is that not gonna work? cause idk how else id install a new rom
The_Wrench said:
ok cool thx but do you think that i can install twrp rn without a system?
or is that not gonna work? cause idk how else id install a new rom
Click to expand...
Click to collapse
I don't really know what else you might have (possibly) mesed up. I have just updated the previous post so please read again the part about MIUI Flash
(If you were not changing from CN/EEA/Russia to Global or so but only installing a custom/AOSP ROM, then if you wiped Data instead of formatting - you would be bootlooping niw to TWRP and you would simply need to Format Data to fix it
But if you were really changing from eg CN to Global by just flashing System - that is TOTALLY WRONG way, why didn't you research how to do it properly by MIUI Flash?
In that case you could still try MIUI Flash, if not working you would need somebody with paid EDL support (I cannot help you for that)
Sorry, good night now
zgfg said:
I don't really know what else you might have (possibly) mesed. I have just updated the previous post so please read again the part about MIUU Flash
(If you did not change from CN/EEA/Russia to Global but only installing a custom ROM, then if you wiped Data instead of formatting - then you would be bootlooping to TWRP and you would simply need now to Firmat Data
But if you were really changing from eg CN to Global by just flashing System - that is TOTALLY WRONG way, why didn't you research how to do it by MIUI Flash?
In that case you could try MIUI Flash, if not you would need somebody with EDL (I cannot help you for that)
Sorry, good night now
Click to expand...
Click to collapse
no i havent changed the region form the phone ... however my currently big problem is that im stuck in fastboot mode and i cannot enter recovery i could try and reflash recovery via fastboot but im not sure if that would break it even more. and since there is no OS on the devices either i cant use adb either. my last hope rn is fastboot and idk what to do rn to fix all this back to factory OS state or a similiar state
The_Wrench said:
no i havent changed the region form the phone ... however my currently big problem is that im stuck in fastboot mode and i cannot enter recovery i could try and reflash recovery via fastboot but im not sure if that would break it even more. and since there is no OS on the devices either i cant use adb either. my last hope rn is fastboot and idk what to do rn to fix all this back to factory OS state or a similiar state
Click to expand...
Click to collapse
As said, something more terribly messed up. Please google and research about using MIUI Flash (TG, I didn't need to use hence cannot help, but there are GOOD guides on the Net)
Good luck and good night
i found this and did what he did https://forum.xda-developers.com/t/xiaomi-mi-9t-stuck-in-fastboot.4255741/
helped a lot now imma retry