I have a Redmi 9c on which I try to install a new rom like many tutorials suggest
So once I switch to bootloader, I run fastboot reboot recovery I get to twrp (3.5.2) but my touch screen doesn't work, I can't do anything.
do you have an idea of the problem ?
(in doubt I tried with PitchBlack but I had the same problem, when it turns itself off, I can't even swipe to unlock it ^^)
I think I forgot something or did something wrong but I don't know what, and I can't boot on the original rom anymore, at best I have the fastboot
rudak987 said:
I have a Redmi 9c on which I try to install a new rom like many tutorials suggest
So once I switch to bootloader, I run fastboot reboot recovery I get to twrp (3.5.2) but my touch screen doesn't work, I can't do anything.
do you have an idea of the problem ?
(in doubt I tried with PitchBlack but I had the same problem, when it turns itself off, I can't even swipe to unlock it ^^)
I think I forgot something or did something wrong but I don't know what, and I can't boot on the original rom anymore, at best I have the fastboot
Click to expand...
Click to collapse
Hi, I think the issue is that twrp and PitchBlack is not compatible for your device. I don't think the error is in your phone, but in those costum revovers.
I tried to put back a stock rom because even with orangefox it didn't work, exactly the same problem.
but i must have done something wrong because the phone doesn't answer anymore, it's always trying to reboot and when i plug it in the pc, it's not visible on the usb.
✝✝ it's the end. ✝✝
we'll all go through it one day, and for the redmi its done.
thank you for reading my sad story^^
rudak987 said:
I tried to put back a stock rom because even with orangefox it didn't work, exactly the same problem.
but i must have done something wrong because the phone doesn't answer anymore, it's always trying to reboot and when i plug it in the pc, it's not visible on the usb.
✝✝ it's the end. ✝✝
we'll all go through it one day, and for the redmi its done.
thank you for reading my sad story^^
Click to expand...
Click to collapse
Try taking the phone in for repair
Related
Q&A for [RECOVERY] TWP 2.7.1.0 for One Mini 2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] TWP 2.7.1.0 for One Mini 2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
new twrp's won't work
Hi there,
I just tried to root my htc mini 2 with and it says that it is tampered now and I can't reboot my recovery. So I tried the newest twrp and some in between because I've read in this forum that somebody had the same problem and he just got the newest twrp but that didn't work for me at all.
Is there any way to undo the whole thing by replacing the twrp with the original one or do I have to wait till there is gonna be a root for the htc mini 2?
When I try to recover everything it says that this build is for development purpose only...
Does somebody have an idea?
I would appreciate it a lot if somebody has an idea.
Hornochse7958 said:
Hi there,
I just tried to root my htc mini 2 with and it says that it is tampered now and I can't reboot my recovery. So I tried the newest twrp and some in between because I've read in this forum that somebody had the same problem and he just got the newest twrp but that didn't work for me at all.
Is there any way to undo the whole thing by replacing the twrp with the original one or do I have to wait till there is gonna be a root for the htc mini 2?
When I try to recover everything it says that this build is for development purpose only...
Does somebody have an idea?
I would appreciate it a lot if somebody has an idea.
Click to expand...
Click to collapse
When the bootloader says "tempered" means that it was unlocked. when you see " this build is for development purpose only" its referring to TWRP because you now using a custom recovery. Not sure the nature of your problem but to undo, simply boot into boot loader and flash original recovery.img you can find in the forum.
I can't you open TWRP?
kativiti said:
When the bootloader says "tempered" means that it was unlocked. when you see " this build is for development purpose only" its referring to TWRP because you now using a custom recovery. Not sure the nature of your problem but to undo, simply boot into boot loader and flash original recovery.img you can find in the forum.
I can't you open TWRP?
Click to expand...
Click to collapse
Thank you for the quick respond and I wanted to try and undo everything but no my problem is that my phone completely froze in the twrp screen. I can't do anything, I can't unlock it nor shut down my phone or start the bootloader... that kind of sucks. Any suggestions now? Is it possible to open the htc one mini 2 and take out the battery? or do I have to wait till it runs out by it self and than start it again?
Hornochse7958 said:
Thank you for the quick respond and I wanted to try and undo everything but no my problem is that my phone completely froze in the twrp screen. I can't do anything, I can't unlock it nor shut down my phone or start the bootloader... that kind of sucks. Any suggestions now? Is it possible to open the htc one mini 2 and take out the battery? or do I have to wait till it runs out by it self and than start it again?
Click to expand...
Click to collapse
Read this tread. Someone had the same problem
http://forum.xda-developers.com/one-mini-2/help/rooting-htc-one-mini-2-t2880936
Unresponsive after boot up from dead battery
THanks to U-ra I get the enjoy my fav DSP Viper!!!
Cheers Man,
I have a small niggling problem that I can't work out, My battery tends to die alot, once I place the phone on charge after a flat battery, the phone auto boots to Twp, I am really cool with that but the annoying thing is buttons and screen are unresponsive? I can't do a thing, just have the Twp menu. The power of button does turn the screen off/on but thats its. Tried doing factory resets, reboots holding down power, vol buttons. Just nothing.
only way around it is to use adb and reboot command.
Is anyone else experiencing this problem.
http://forum.xda-developers.com/one...recovery-twp-2-7-1-0-one-mini-2-t2801370/page 4 here's the answer, so far
@u-ra is there any clue about getting official twrp support? (I was thinking about that problem of the self-booting recovery when phone is off and plugged in)
gibihr said:
@u-ra is there any clue about getting official twrp support? (I was thinking about that problem of the self-booting recovery when phone is off and plugged in)
Click to expand...
Click to collapse
I'll try to get to it this weekend.
HELP TWRP stuck at swipe to unlock
Hello all,
for unknown reason the phone restarded and now is stuck at swipe to unlock but it is not working. I try to hold power+volume down, but no way to turn it off. What can I do?
Thanks in advance
PS: well, it restarted... I don't know what happend but now it's ok
sorry for sounding like a newb
i have the verizon htc one remix, which i believe is the same as the one mini 2 . will this work on it?
akubenz said:
i have the verizon htc one remix, which i believe is the same as the one mini 2 . will this work on it?
Click to expand...
Click to collapse
you can try but i think someone here couldn't unlock bootloader trough HTC Dev.
Help: Stock rom updated between boots, TWRP non responsive, fastboot doesnt recognise
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
snorglamp said:
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
Click to expand...
Click to collapse
A kind member replied to me in another post indicating that fastboot commands only work in the bootloader, and that adb commands only work in TWRP which is why I am having problems re-flashing TWRP (requiring the "fastboot flash recovery TWRP.img" command). However I thought TWRP replaced the bootloader, so I seem to be locked out of re-flashing TWRP because i have TWRP. This seems not to make a lot of sense, can anyone else confirm or otherwise explain what I have misunderstood about that? As stated neither adb nor fastboot recognises the device is attached to the computer any more, so commands are not executing...
snorglamp said:
Hello to anyone that can help or in a similar situation,
Have brand new HTC one mini 2, rooted. Am trying to install cyanogenmod and followed the instructions on their page. All went well and was ready to flash the rom from TWRP. Decided to do a backup to SD first and then apply super user. Forced to reboot and accidentally let it boot to android (stock rom). Didnt notice the last time i had it booted wifi downloaded a system update which was automatically applied next time i booted into the stock rom after backup and Superuser in TWRP. Rebooted to recovery (TWRP) as soon as i could, but TWRP is no longer responding to touch. I realise i have probably updated the phone to a point where TWRP is no longer working, and i have to use something else to flash my rom. Am trying to flash an updated TWRP or Clockworkmod recovery, but fastboot/adb no longer recognise the device when booted into the stock rom, and when i boot into TWRP (non-responsive) it also doesnt recognise the device attached, even if i catch it before the screen goes black from inactivity. Any suggestions greatly appreciated....
Click to expand...
Click to collapse
I think I have found the solution for myself: I went back into the stock rom and did a factory reset (from within android booted up as normal), which after completion rebooted me into TWRP which now works fine (is responding to touch again, and i can flash the Cyanogen image now). Hopefully this helps someone else in this situation one day, or maybe I am the only idiot that needed to ask hehe. I should clarify that after flashing TWRP I lost access to the fastboot screen and could not push anything over ADB or fastboot commands from windows (plugged in via USB). Holding down volume down and power booted directly into TWRP, and i had no way to get to fastboot screen. After doing factory resent from within the Android OS, holding volume down and power booted me to the fastboot screen, and only when I selected "Recovery" did it take me to TWRP, and I was again able to run fastboot and ADB commands from PC. Weird (or maybe not if you know more than me), but there it is...
snorglamp said:
A kind member replied to me in another post indicating that fastboot commands only work in the bootloader, and that adb commands only work in TWRP which is why I am having problems re-flashing TWRP (requiring the "fastboot flash recovery TWRP.img" command). However I thought TWRP replaced the bootloader, so I seem to be locked out of re-flashing TWRP because i have TWRP. This seems not to make a lot of sense, can anyone else confirm or otherwise explain what I have misunderstood about that? As stated neither adb nor fastboot recognises the device is attached to the computer any more, so commands are not executing...
Click to expand...
Click to collapse
Sorry, but it seems to me that you don't know the difference between bootloader and recovery. I apologize if you do. If not, search in CM wikis or ask here for explanations.
corbeau56 said:
Sorry, but it seems to me that you don't know the difference between bootloader and recovery. I apologize if you do. If not, search in CM wikis or ask here for explanations.
Click to expand...
Click to collapse
I do indeed know the difference between the bootloader and recovery, its just that the bootloader (Hboot) was not longer accessible in my situation and TWRP (the recovery) was imposing itself when you would normally expect to find the bootloader (i.e. my bootloader was for all intents and purposes replaced by my recovery, while I am sure this is not true in fact, it was in effect). As I say, doing a factory reset from within the OS restored the bootloader (HBoot) and I was able to continue modding. I am today extremely happy with my fully secured cyanogenmodded HTC One Mini 2 via TWRP recovery method. I hope that is somewhat clearer.
Can you enter bootliader now? I got stuck in a bootloop once and couldn't enter bootloader because I continued pressing power and Volume down like I did on my One S. For Mini 2, we have to hold the Volume UP and Power buttons until HBOOT appears, then release the buttons.
corbeau56 said:
Can you enter bootliader now? I got stuck in a bootloop once and couldn't enter bootloader because I continued pressing power and Volume down like I did on my One S. For Mini 2, we have to hold the Volume UP and Power buttons until HBOOT appears, then release the buttons.
Click to expand...
Click to collapse
That may well have been an alternative solution to my problem, however it was fixed by the factory reset and volume down and power then took me to HBoot (this would appear to contradict what you have said above, but maybe volume down and power does different things depending on how what you have done to the phone, not sure), so I cannot confirm whether or not that also would have worked for me. Good suggestion though, especially if you are not in a position to do a factory reset. and it would certainly be easier if it worked...I am convinced my problem was the result of a conflict between the TWRP version i installed (downloaded from here) and the android update that occurred between boots.
I am indeed able to get into bootloader/hboot and successfully flashed cyanogenmod from TWRP. I can confirm post flashing TWRP and Cyanogenmod, holding volume down and power takes me to HBoot (and then the option to go to fastboot or recovery).
Holding power up and power just loads cyanogenmod for me now as if I had just pressed power.
I thought I should confirm whether or not holding volume up vs volume down with power results in bootloader vs recovery loading. For me, they both took me to TWRP.
Also, TWRP doesnt seem to work on HTC One Mini 2 after you do anything to set up your phone. It just doesnt recognise touch input any more so you cant do anything with it. However the fix i noted earlier (factory reset) even works with other roms installed, confirmed for cyanogenmod 11 and 12 nightlies as at the date of this post. After factory reset TWRP works again, but if you go through the setup steps and start installing apps, TWRP goes unresponsive again. I hope we might get an official TWRP update soon!
Hey, was just setting up my mi5 for custom roms. Got the bootloader unlocked, then installed TWRP via fastboot as per the instructions here (https://twrp.me/devices/xiaomimi5.html).
After I got into TWRP I made a quick backup of the image, and then set the phone to reboot. Now its in a bootloop, flashing the mi logo (and bootloader unlock on the bottom). Doesn't turn off, doesn't do anything when plugged into pc, fastboot reboot doesn't do anything.
Any ideas? Didn't think I had done anything wrong (done this kind of thing a couple times before).
Cheers!
EDIT: Hang on, managed to get into fastboot, I guess I should be able to sort things out from there? What should I aim to do. I can also get into recovery. Still won't boot into system anymore though.
flobbadob said:
Hey, was just setting up my mi5 for custom roms. Got the bootloader unlocked, then installed TWRP via fastboot as per the instructions here (https://twrp.me/devices/xiaomimi5.html).
After I got into TWRP I made a quick backup of the image, and then set the phone to reboot. Now its in a bootloop, flashing the mi logo (and bootloader unlock on the bottom). Doesn't turn off, doesn't do anything when plugged into pc, fastboot reboot doesn't do anything.
Any ideas? Didn't think I had done anything wrong (done this kind of thing a couple times before).
Cheers!
EDIT: Hang on, managed to get into fastboot, I guess I should be able to sort things out from there? What should I aim to do. I can also get into recovery. Still won't boot into system anymore though.
Click to expand...
Click to collapse
Which twrp version are you using?
Did you actually flash any custom rom or do you try to start miui?
Did you change any partition?
Something similar happened to me one time. I solved it by doing the root right after installing the twrp. And magically started my rom.
lanceindie said:
Something similar happened to me one time. I solved it by doing the root right after installing the twrp. And magically started my rom.
Click to expand...
Click to collapse
+1! Thanks :highfive:
Did you solve it? I might have some ideas.
So, ive seen many complaints about this but, so far I havent seen anyone fix it. I know there are youtube videos and ppl have their methods but, these methods arent working for me. Obviously I have a Mi Mix. Whenever I boot into twrp it asks me for a password. Does anyone have a step by step way of helping me fix this? Otherwise, I think im just going to just give up.
The only clue we had as to a solution was this thread
https://forum.xda-developers.com/mi-mix/help/twrp-0mb-t3740252
Not sure what twrp, rom, etc he was using, but he claimed he was encrypted and was able to decrypt in recovery. This has become a real issue with all the oreo roms, but has been an issue for me since day 1 Mi Mix...
Try removing any lockscreen password, including pattern, which is handled like a password.
Try formatting your memory to get rid of encryption.
Try a different TWRP, I use this one by raupe:
https://www.nextgen-networks.de/de/...25-twrp-recovery-3-2-1-0-universal-build.html
msn100dc said:
The only clue we had as to a solution was this thread
https://forum.xda-developers.com/mi-mix/help/twrp-0mb-t3740252
Not sure what twrp, rom, etc he was using, but he claimed he was encrypted and was able to decrypt in recovery. This has become a real issue with all the oreo roms, but has been an issue for me since day 1 Mi Mix...
Click to expand...
Click to collapse
So there isnt really a fix for the specific TWRP (Mr.Raines)?
cobben said:
Try removing any lockscreen password, including pattern, which is handled like a password.
Try formatting your memory to get rid of encryption.
Try a different TWRP, I use this one by raupe:
https://www.nextgen-networks.de/de/...25-twrp-recovery-3-2-1-0-universal-build.html
Click to expand...
Click to collapse
I dont know which Mi Mix that I have. I think its the global version, and so far the only TWRP that I can get on it is the one by Mr.Raines. Everything else seeme to fail. Other than trying a new different TWRP. Do we just have to wait for this to be fixed?
The best solution for now is to decrypt your data partition. This involves formatting your data partition in twrp and ensuring that it doesn't encrypt on first boot into whatever rom your using.
Im not sure on the particulars, but there is plenty of information in this forum to help you proceed if thats the route you plan to take. Its how i get around it for now.
I have the same problem, stuck on the same page...
Mi Mix 256/6 Global Rom
Also for me it's not possible to enter TWRP direct from a boot with VOL+ and POWER... it's then in mi recovery 3.0
So if anyone can help to solve this I would be very thankful. I really want to use this baby in the Dutch language but then I need to install the xiaomi.eu rom first....
ezwets said:
I have the same problem, stuck on the same page...
Mi Mix 256/6 Global Rom
Also for me it's not possible to enter TWRP direct from a boot with VOL+ and POWER... it's then in mi recovery 3.0
So if anyone can help to solve this I would be very thankful. I really want to use this baby in the Dutch language but then I need to install the xiaomi.eu rom first....
Click to expand...
Click to collapse
Try flashing Raupes TWRP. https://forum.xda-developers.com/mi-mix/development/recovery-official-twrp-xiaomi-mi-mix-t3498960/
After flashing it via fastboot, turn the phone off first and then use the volume and power button to boot into recovery rather than going from fastboot straight into recovery mode.
Sent from my Xiaomi Mi Mix using XDA Labs
CidAndroid said:
Try flashing Raupes TWRP. https://forum.xda-developers.com/mi-mix/development/recovery-official-twrp-xiaomi-mi-mix-t3498960/
After flashing it via fastboot, turn the phone off first and then use the volume and power button to boot into recovery rather than going from fastboot straight into recovery mode.
Click to expand...
Click to collapse
Initial booting into recovery(twrp) should be done from fastboot via ''fastboot boot twrp_xxx.img'' code. Otherwise it would get into stock recovery.
Konstantine34 said:
Initial booting into recovery(twrp) should be done from fastboot via ''fastboot boot twrp_xxx.img'' code. Otherwise it would get into stock recovery.
Click to expand...
Click to collapse
When I did that I ended up in stock recovery time after time. Turning of my phone and turn it on again seemed not to cause this issue. For me.
Sent from my Xiaomi Mi Mix using XDA Labs
After flashing recovery, from the fastboot screen you can hold down Vol up and power buttons till it reboots. You will then be taken straight to your custom recovery.
Thank you for your help.. Here is the solution that worked for me..
I am not allowed to post links but the answer is on the xiaomi.eu forum under Mi Mix: topic starter Eddy Zwets
My device is stuck in the initial boot sequence in which the logo will show as if it is booting normally, then it will stay on this screen until it goes completely blank, at which point I have to hold the power button for a long period of time to get it back to the boot sequence. My phone is unlocked and I was trying my first time at flashing a custom recovery and OS, I flashed my device with TWRP and successfully installed it along with a flash of pixel experience, After using pixel experience I wanted to try lineage OS since it wasn't as good as I hoped, so I tried to get into the TWRP and I could not do it at all I tried every method I could search. After an hour of trying different methods of getting to twrp I tried to re-flash the recovery and that is when the phone because unresponsive and does what I have described above. I currently have access to fast boot and I dont want to go ****ing my phone up more than I have. If anyone can give me a step by step guide on how to fix this it would help so much since im new to android and I cant afford another £400 phone.
Thanks
BJack0 said:
My device is stuck in the initial boot sequence in which the logo will show as if it is booting normally, then it will stay on this screen until it goes completely blank, at which point I have to hold the power button for a long period of time to get it back to the boot sequence. My phone is unlocked and I was trying my first time at flashing a custom recovery and OS, I flashed my device with TWRP and successfully installed it along with a flash of pixel experience, After using pixel experience I wanted to try lineage OS since it wasn't as good as I hoped, so I tried to get into the TWRP and I could not do it at all I tried every method I could search. After an hour of trying different methods of getting to twrp I tried to re-flash the recovery and that is when the phone because unresponsive and does what I have described above. I currently have access to fast boot and I dont want to go ****ing my phone up more than I have. If anyone can give me a step by step guide on how to fix this it would help so much since im new to android and I cant afford another £400 phone.
Thanks
Click to expand...
Click to collapse
try booting twrp
'fastboot boot img name' then flash recovery from there. hope it works.
BJack0 said:
My device is stuck in the initial boot sequence in which the logo will show as if it is booting normally, then it will stay on this screen until it goes completely blank, at which point I have to hold the power button for a long period of time to get it back to the boot sequence. My phone is unlocked and I was trying my first time at flashing a custom recovery and OS, I flashed my device with TWRP and successfully installed it along with a flash of pixel experience, After using pixel experience I wanted to try lineage OS since it wasn't as good as I hoped, so I tried to get into the TWRP and I could not do it at all I tried every method I could search. After an hour of trying different methods of getting to twrp I tried to re-flash the recovery and that is when the phone because unresponsive and does what I have described above. I currently have access to fast boot and I dont want to go ****ing my phone up more than I have. If anyone can give me a step by step guide on how to fix this it would help so much since im new to android and I cant afford another £400 phone.
Thanks
Click to expand...
Click to collapse
Don't worry, things can be recovered easily. Until you get more knowledgeable and you understand more about flashing use this failsafe to recover from (almost) anything
Go here and get the latest fastboot ROM for your phone.
https://xiaomifirmwareupdater.com/miui/raphael/
For now make sure you get the one that matches the region for your phone.
Then follow this guide to flash it
https://c.mi.com/thread-1857937-1-1.html
Use the fastboot flashing section.
Make sure you change the flash option to 'clean all' when flashing. The default option will lock the bootloader again after flashing. If you do the default option with any ROM that is not the same region as the phone you will hard brick the phone, this is why I recommend getting the ROM that matches your phone.
When unpacking the fastboot ROM, it is a Linux/Unix zipped tarball, most Windows zip software will need to extract it twice. The first time will give you a single .tar file (if it doesn't have an extension then rename it and add .tar to the end) You will then need to extract everything from the tar file, which you give you the folder, containing the ROM data, to point the Mi Flash Tool at.
After doing this you, if you've remembered to change the flash option to 'clean all', then you'll have restored to stock and kept the bootloader unlocked. Now you're good to try again.
Keep a copy of the fastboot ROM on your PC and back everything up on your phone before flashing. Then if you get in a mess you know how to easily recover things.
Once you get more experienced there will be other things you might be able to do, depending on the situation, that allow you to get things working without losing everything and needing to start from scratch.
Thanks
Robbo.5000 said:
Don't worry, things can be recovered easily. Until you get more knowledgeable and you understand more about flashing use this failsafe to recover from (almost) anything
Click to expand...
Click to collapse
Thank you so much for the details post, I will try what you have said above and will report back with my results. I have one question if you know the answer ( My phone is the UK edition of the Mi 9T pro ) Would I need to download the global or EEA fastboot version.
BJack0 said:
Thank you so much for the details post, I will try what you have said above and will report back with my results. I have one question if you know the answer ( My phone is the UK edition of the Mi 9T pro ) Would I need to download the global or EEA fastboot version.
Click to expand...
Click to collapse
For safety download the EEA ROM.
I also suggest you immediately flash dm_verity (https://forum.xda-developers.com/k20-pro/how-to/flashing-orangefox-recovery-mi-9t-pro-t3980579), after you flash twrp, wipe data and then flash that
Sent from my Redmi K20 Pro using Tapatalk
Robbo.5000 said:
For safety download the EEA ROM.
Click to expand...
Click to collapse
Everything you said worded flawlessly and your a life saver. If you dont mind do you have a link to a set of guides on how to correctly flash a custom recovery and lineage OS? since when I try to research these guides I get 5 different versions of TWRP and lock my phone out :laugh:
ishaqtkr said:
I also suggest you immediately flash dm_verity after you flash twrp, wipe data and then flash that
Click to expand...
Click to collapse
If you dont mind me asking could you go into slightly more detial on that since I have seen orange fox but I dont understand what dm_verity is.
Please ignore all reply's above as I am going to make another separate post about lineage OS
Thank you for replying and resolving my issue.
i tried to install twrp and my !!REDMI 9!! lancelot only A partition MIUI version is 12.0.4.0 bootloader unlocked its now in bootloop with no acces to fastboot or recovery, i fixed before soft brick with fastboot, but with no fastboot, i do not know whar to do. And also adb do not see the device.
WHAT I DID:
flashed twrp unofficial 3.4.2b LANCELOT
i mean
fastboot flash vbmeta vbmeta.img
fastboot flash recovery twrp.img
then entered recovery but it was stock
flashed again then i was in a bootloop on recovery with frozen screen, couldnt do nothing
then i flashed 3.4.1
and got this bootloop and i need to enter fastboot to flash the stock ROM
HAAAAAALP!!!
First thing I expect you tried, but if you get the timing perfect, you try to catch the bootloop going down and with a touch of power and very long press Volume down you might be able to engage fastboot. (Depends on the issue, perhaps, but I have tried sometimes 10 times and it works eventually!)
Flying_Scotsman said:
First thing I expect you tried, but if you get the timing perfect, you try to catch the bootloop going down and with a touch of power and very long press Volume down you might be able to engage fastboot. (Depends on the issue, perhaps, but I have tried sometimes 10 times and it works eventually!)
Click to expand...
Click to collapse
didnt work
Flying_Scotsman said:
First thing I expect you tried, but if you get the timing perfect, you try to catch the bootloop going down and with a touch of power and very long press Volume down you might be able to engage fastboot. (Depends on the issue, perhaps, but I have tried sometimes 10 times and it works eventually!)
Click to expand...
Click to collapse
i gave at service, they said the kernel its corrupted
I would expect the tool you used to unlock the bootloader would be able to flash the phone to "latest" MIUI. I had to do this several times using https://forum.xda-developers.com/t/...oader-of-xiaomi-devices-on-mac-linux.3782444/
Flying_Scotsman said:
I would expect the tool you used to unlock the bootloader would be able to flash the phone to "latest" MIUI. I had to do this several times using https://forum.xda-developers.com/t/...oader-of-xiaomi-devices-on-mac-linux.3782444/
Click to expand...
Click to collapse
did not see it, adb do not see the phone too, i sent it to service and they said that kernel its missing or corrupted